Error importing table metadata with quoted column names

Hey folks,
I have a strange problem with the table metadata import wizard. It refuses to import column names that are quoted. I am using OWB 11.1.0.6 on Oracle 11g/Linux
For example, given this table
create table mytest (id integer, "Name" varchar2(50))
OWB imports the ID column just fine but chokes on the "Name" column ("Created with second class object failure").
However if I define the table as
create table mytest (id integer, Name varchar2(50))
everything goes smoothly. Does anyone know if this is a bug or a feature? Can't find any information on this, and it's highly annoying as I'm importing definitions of automatically generated tables that contain tons of these quoted column names :(.
I appreciate your help!!
Thanks,
Stefan

I noticed that myself in our project.
Our varchars2 are defined as VARCHAR2(xxx CHAR) - OWB puts the size*4
In fact if you have special characters like umlauts (ü,ä,ö,...) it will use 4 bytes per character.
You can try it yourself. Define a Varchar2(1 CHAR) and manually change the size of the Column in your mapping inside OWB (in filters, joins or your target table).
Then shoot an umlaut through the mapping and will end up with a "too small" error.
Dont mind the size*4 issue - we totally ignored it and run without error since 4 years now.

Similar Messages

How To Create Table View With Same Column name But Different Table?

Hi All,
I have the problem to create a tableview with same column name but in different table.
The Table that i have:-
Table - PAC051MPROFORMA
Column - mrn,visitid
Table - PAC051TPROFORMA
Column - mrn,visitid
Table - PAC052MTRANSBILL
Column - mrn,visitid
Then i want to create a table view to view that table. This is my SQL
CREATE VIEW pacviewproforma (mrn,visitid,mrn,visitid,mrn,visitid)
As Select PAC051MPROFORMA.mrn,PAC051MPROFORMA.visitid,PAC051TPROFORMA.mrn,PAC051TPROFORMA.visitid,PAC052MTRANSBILL.mrn,PAC052MTRANSBILL.visitid
where
*(a.PAC051MPROFORMA.mrn=PAC051TPROFORMA.mrn)*
and
*(a.PAC051TPROFORMA.mrn=PAC052TRANSBILL.mrn)*
That SQL Return this error = ORA-00957: duplicate column name
Then I modify that SQL to
CREATE VIEW pacviewproforma (mrn,visitid)
As Select PAC051MPROFORMA.mrn,PAC051MPROFORMA.visitid,PAC051TPROFORMA.mrn,PAC051TPROFORMA.visitid,PAC052MTRANSBILL.mrn,PAC052MTRANSBILL.visitid
where
*(a.PAC051MPROFORMA.mrn=PAC051TPROFORMA.mrn)*
and
*(a.PAC051TPROFORMA.mrn=PAC052TRANSBILL.mrn)*
This time this error return = ORA-01730: invalid number of column names specified
What should i do?
Thanks...

Hi,
SQL> CREATE VIEW pacviewproforma (mrn,visitid,mrn,visitid,mrn,visitid)
2 As Select
3 PAC051MPROFORMA.mrn,
4 PAC051MPROFORMA.visitid,
5 PAC051TPROFORMA.mrn,
6 PAC051TPROFORMA.visitid,
7 PAC052MTRANSBILL.mrn,
8 PAC052MTRANSBILL.visitid
9 from PAC051MPROFORMA,PAC051TPROFORMA,PAC052MTRANSBILL
10 where
11 (PAC051MPROFORMA.mrn=PAC051TPROFORMA.mrn)
12 and
13 (PAC051TPROFORMA.mrn=PAC052MTRANSBILL.mrn);
CREATE VIEW pacviewproforma (mrn,visitid,mrn,visitid,mrn,visitid)
ERROR at line 1:
ORA-00957: duplicate column namePlease give different names to each column.
Something like this..
SQL> CREATE OR REPLACE VIEW pacviewproforma (MPROFORMA_mrn,MPROFORMA_visitid,TPROFORMA_mrn,TPROFORMA
_visitid,MTRANSBILL_mrn,MTRANSBILL_visitid)
2 As Select
3 PAC051MPROFORMA.mrn,
4 PAC051MPROFORMA.visitid,
5 PAC051TPROFORMA.mrn,
6 PAC051TPROFORMA.visitid,
7 PAC052MTRANSBILL.mrn,
8 PAC052MTRANSBILL.visitid
9 from PAC051MPROFORMA,PAC051TPROFORMA,PAC052MTRANSBILL
10 where
11 (PAC051MPROFORMA.mrn=PAC051TPROFORMA.mrn)
12 and
13 (PAC051TPROFORMA.mrn=PAC052MTRANSBILL.mrn);
View created.
SQL> DESC pacviewproforma;
Name                                      Null?    Type
MPROFORMA_MRN                                      NUMBER
MPROFORMA_VISITID                                  NUMBER
TPROFORMA_MRN                                      NUMBER
TPROFORMA_VISITID                                  NUMBER
MTRANSBILL_MRN                                     NUMBER
MTRANSBILL_VISITID                                 NUMBER
ORA-01730: invalid number of column names specifiedThe list of column nmae you specified during the CREATE VIEW should match with the SELECT list of the view.
Twinkle

Is this a bug in OWB 11.2 - importing table metadata for character columns

The Oracle® Warehouse Builder Data Modeling, ETL, and Data Quality Guide provides an overview of the data types supported.
http://docs.oracle.com/cd/E11882_01/owb.112/e10935/orcl_data_objx.htm
It says that for VARCHAR2 data type it saws (http://docs.oracle.com/cd/E11882_01/owb.112/e10935/orcl_data_objx.htm#CHDFIADI )
"Stores variable-length character data. How the data is represented internally depends on the database character set. The VARCHAR2 data type takes a required parameter that specifies a maximum size up to 4,000 characters"
That means , I guess, it says that when I import a table, any columns of type VARCHAR2(10) in the database should have its length show as characters in OWB, so a column of type Varchar2(10) in the Oracle database, should be shown as Varchar2(10) when imported into OWB table metadata via the OWB import function.
However, if I have a database that set-up as a single-byte and import a table using the OWB import function a column that has a size of e.g. 10 in the database, is imported as OWB table metadata and the size is 10. Correct, I am happy.
However, if the database is modified to support multi-byte characters, ALTUF16 encoding with the semantics set to "CHAR", then when I import the same table into OWB, OWB reports the size as 40, I guess its 40 bytes as in 10 characters @ 4 bytes per character.
Is this a bug in OWB, as the datatype in the Oracle DB is varchar2(10), should OWB after importing a table not also report the column as VARCHAR2(10) ? Currently, is shows the column as varchar2(40).

I noticed that myself in our project.
Our varchars2 are defined as VARCHAR2(xxx CHAR) - OWB puts the size*4
In fact if you have special characters like umlauts (ü,ä,ö,...) it will use 4 bytes per character.
You can try it yourself. Define a Varchar2(1 CHAR) and manually change the size of the Column in your mapping inside OWB (in filters, joins or your target table).
Then shoot an umlaut through the mapping and will end up with a "too small" error.
Dont mind the size*4 issue - we totally ignored it and run without error since 4 years now.

Many to many join table with different column names

Hi have a joint table with different column names as foreign keys in the joining
tables...
e.g. i have a many to many reltnshp btwn Table A and Table B ..and join table
C
both have a column called pk.
and the join table C has columns call fk1 and fk2
does cmd require the same column name in the join table as in the joining table?
are there any workarounds?
thanks

HI,
No, the foreign key column names in the join table do not have to match the primary
key names in the joined tables.
-thorick

Selecting from a SQL Server 2005 with long column names ( 30 chars)

Hi,
I was able to set up a db link from Oracle 11.2.0.1 to SQL Server 2005 using DG4ODBC.
My problem is that some column names in the Sql Server are longer than 30 chars and trying to select them gives me the ORA-00972: identifier is too long error.
If I omit these columns the select succeeds.
I know I can create a view in the sql server and query it instead of the original table, but I was wondering if there's a way to overcome it with sql.
My select looks like this:
select "good_column_name" from sometable@sqlserver_dblink -- this works
select "good_column_name","very_long_column_name>30 chars" from sometable@sqlserver_dblink -- ORA-00972Thanks

I tried creating a view with shorter column names but selecting from the view still returns an error.
create view v_Boards as (select [9650_BoardId] as BoardId, [9651_BoardType] as BoardType, [9652_HardwareVendor] as
HardwareVendor, [9653_BoardVersion] as BoardVersion, [9654_BoardName] as BoardName, [9655_BoardDescription] as BoardDescription,
[9656_SlotNumber] as SlotNumber, [9670_SegmentId] as SegmentId, [MasterID] as MasterID, [9657_BoardHostName] as BoardHostName,
[9658_BoardManagementUsername] as BoardManagementUsername, [9659_BoardManagementPassword] as BoardManagementPassword,
[9660_BoardManagementVirtualAddress] as BoardManagementVirtualAddress, [9661_BoardManagementTelnetLoginPrompt] as
MANAGEMENTTELNETLOGINPROMPT, [9662_BoardManagementTelnetPasswordPrompt] as MANAGEMENTTELNETPASSPROMPT,
[9663_BoardManagementTelnetCommandPrompt] as MANAGEMENTTELNETCOMMANDPROMPT FROM Boards)performing a select * from this view in sqlserver works and show the short column names
this is the error i'm getting for performing a select * from v_boards@sqlserver_dblink
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Microsoft][SQL Native Client][SQL Server]Invalid column name 'BoardManagementTelnetLoginProm'. {42S22,NativeErr = 207}[Microsoft]
[SQL Native Client][SQL Server]Invalid column name 'BoardManagementTelnetPasswordP'. {42S22,NativeErr = 207}[Microsoft][SQL Native
Client][SQL Server]Invalid column name 'BoardManagementTelnetCommandPr'. {42S22,NativeErr = 207}[Microsoft][SQL Native Client][SQL
Server]Statement(s) could not be prepared. {42000,NativeErr = 8180}
ORA-02063: preceding 2 lines from sqlserver_dblinkI also tried replacing the * with specific column names but it fails on the columns that have a long name (it doesn't recognize the short names from the view)
what am I doing wrong?
Edited by: Pyrocks on Dec 22, 2010 3:58 PM

CREATE INDEX WITH DUPLICATE COLUMN NAME

Hi,
i need to interface our application with an Orale Bridge to CREATE INDEX with duplcate column Name.
For Example
CREATE index NLOT_FOURNLOT_idx ON NLOT(FOURNISSEUR ,NOLOT ,FOURNISSEUR ,NOBLFOUNISSEUR,NOLIGNEBL ,NOLOT ,QTECOLISRECUES ,CODENONQUALITE ,QTECOLISACCEPTE);
CREATE table NLOT(
FOURNISSEUR VARCHAR2(09)
,NOBLFOURNISSEUR VARCHAR2(13)
,NOLIGNEBL VARCHAR2(03)
,NOLOT VARCHAR2(20)
,QTECOLISRECUES VARCHAR2(10)
,CODENONQUALITE VARCHAR2(02)
,QTECOLISACCEPTE VARCHAR2(10)
,NOMBREDECOLISRE VARCHAR2(10)
,NOMBREDECOLISAC VARCHAR2(10)
,FILLER VARCHAR2(1)
,FILLE1 VARCHAR2(1)
,TYPEREFERENCE VARCHAR2(01)
,REFERENC1 VARCHAR2(15)
,CONTROLERECEPTI VARCHAR2(01)
,DATEDEPEREMPTIO VARCHAR2(8)
,CONTROLEPROCHAI VARCHAR2(1)
Thanks
Philippe

Well, you can't do it. ORA-957 is one of those irrevocable errors for which the solution is to remove the duplicate name from the SQL statement.
But, anyway, why do you want to do this? I would guess there's no performance benefit from having the same column indexed twice (of course it's impossible to test this, so it's just my opinion).
Cheers, APC

Is it possible to create a Synonym with different column names

Hi,
I want to create a Synonym with different columns names (Columns not in original table) . I am not sure if this can be done . Any suggessions...
Thanks in advance....

Synonyms are not limited to tables. Accroding to the SQL Reference, a synonym is:
an alternative name for a table, view, sequence, procedure, stored function, package, materialized view, Java class schema object, user-defined object type, or another synonym.
In fact, synonyms are not even validated until they are used:
SQL> create synonym my_synonym for table_which_does_not_exist;
Synonym created
SQL> select * from my_synonym;
select * from my_synonym
ORA-00980: synonym translation is no longer valid

BPC - "Error occurs during UpdateRemainData. Invalid column name formula4

Hi All,
After creating a new dimension, I am trying to add members in it.
I am not sure why, but first I got message to include FORMULAH1 and FORMULAH2 as properties to the dimesion. I added those two properties although I do not have any formula for my Dim members.
When I try to process the dimension, I get the error message,
"Error occurs during UpdateRemainData. Invalid column name 'formula4'."
Can anybody throw some light as to why I might be getting this message and how to fix it.
I do not have any column named 'formula4'.
Thanks in advance.
Anurag

Hello,
You have to have only one property named Formula into the dimension. The formulah1, formulah2, ... should be added corresponding with the number of hierarchies defind in your dimension.
To have an idea more clear, just look to the AcountL on ApShel, which has 3 hierarchies and 3 formulas, but only one FORMULA property.
Best regards,
Mihaela

Error generating report job with the task name 'FSRM_Report_Task

Since this morning we have been having a problem with FSRM on Windows Server 2008 R2, it is no longer running storage reports (both scheduled and on-demand).
We get the following in the event logs:
Log Name: Application
Source: SRMREPORTS
Date: 09/06/2014 08:09:55
Event ID: 752
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: FILESERVER2.curriculum.riddlesdown.local
Description:
Error generating report job with the task name 'FSRM_Report_Task{3add1760-4e79-4141-baba-cb53391bef3e}'.
Context:
- Exception encountered = Invalid argument: StorageType = '101'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SRMREPORTS" />
<EventID Qualifiers="0">752</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-06-09T07:09:55.000000000Z" />
<EventRecordID>42920</EventRecordID>
<Channel>Application</Channel>
<Computer>FILESERVER2.curriculum.riddlesdown.local</Computer>
<Security />
</System>
<EventData>
<Data>Error generating report job with the task name 'FSRM_Report_Task{3add1760-4e79-4141-baba-cb53391bef3e}'.
Context:
- Exception encountered = Invalid argument: StorageType = '101'
</Data>
</EventData>
</Event>
We have uninstalled and reinstalled the FSRM role service but are still having the same problem.
Anybody have any ideas?

Hi,
From the error message, it failed because of "invalid argument: storagetype = '101' ".
101 means the storage type is "system" + "cache". Is there any change on your storage before the issue occurs? For example whether the source storage is changed?
FsrmStorageModuleType enumeration
http://msdn.microsoft.com/en-us/library/dd392346(v=vs.85).aspx
If you have any feedback on our support, please send to [email protected]

Error ora-604 ora-904 invalid column name

Someone knows how to fix this problem?
Error ora-604 ora-904 invalid column name.

Asif, to add another question to the list of things to check. Is the version of the exp utility you are using to perform the export operation the same version as the database? If not, that would explain the error.
If you are trying to export using a newer version of the export utility that generally will not work. You should switch to using the db version.
If you are exporting using an older version because the target is an older version then usually you need to run the catexp# where # is the version number script for the target version that Oracle provides in the $ORACLE_HOME/rdbms/admin directory.
HTH -- Mark D Powell --

Membership rules does not work with UDF column name having the max length

Found a bug in OIM .
Membership rules does not work with UDF column name having the maximum length
Steps to Reproduce
1.Create a UDF having max column name length for eg UDF_USR_PERSONAL_SUB_DOMAIN_CO (lable = Personal Code)
2. Create a simple Rule like Personal Code = 7000
3. Assign this Rule as a member ship rule of a Group.
4. Create a user with Personal Code = 7000.
5. User doesnot get the group membership.
Thanks
Suren

Yes , i verified logs as well .
If you just decrease the column name length , w/o making change to any other attributes , it starts working ..
Thanks
Suren

View of tables with double column names

Hello,
my problem is that in my database schema the name of the primary-key-column in one table has the same name as the corresponding foreign key-column in another table. Now i want to create a view of those two tables and get an error (double column names).
Is there any chance to avoid this error without rename all my column names (cause this happens many many times)?
Thanks for any help.
Christoph

Hi,
In SQL you cas prefix the column with its data container. Use this and it'll be OK. This is not an error, it's expected and absolutely normal behaviour.
SQL> desc dual
Name Null? Type
DUMMY VARCHAR2(1)
SQL> select D1.DUMMY, D2.DUMMY
2 FROM DUAL D1, DUAL D2
3 WHERE D1.DUMMY = D2.DUMMY;
D D
X XRegards,
Yoann.

Where statement on two different tables with same column name

Hello,
I have 2 financial tables:
tblincome, tblexpenses
in each table I have column name "monthPayed" (have values of all the months of the year).
I would like to create a balance view table that will show me the financial status for the Q1 (for example).
I have a column totalIncome and totalExpended respectively.
I've create a view table that shows me the financial balance at the moment but I want it to be devide to Quarters of the year...
Regards

Please post DDL, so that people do not have to guess what the keys, constraints, Declarative Referential Integrity, data types, etc. in your schema are. Learn how to follow ISO-11179 data element naming conventions and formatting rules. Temporal data should
use ISO-8601 formats. Code should be in Standard SQL as much as possible and not local dialect.
This is minimal polite behavior on SQL forums. Where is the code you already tried? Or are you so lazy, so rude or so privileged that you did not do anything for yourself?
In fact that silly “tbl-” prefix is so bad that it has a name! It is called Tibbling and Phil Factor even wrote a humor article on bad programmers that use it.
Your narrative is vague; it sounds like this is the DDL:
CREATE TABLE Incomes
(payment_month CHAR(10) NOT NULL PRIMARY KEY,
income_amt DECIMAL(12,2) NOT NULL
CHECK (income_amt > 0.00),
CREATE TABLE Expenses
(payment_month CHAR(10) NOT NULL PRIMARY KEY,
expense_amt DECIMAL(12,2) NOT NULL
CHECK (expense_amt > 0.00),
>> in each table I have column name "monthPayed" (have values of all the months of the year). <<
I hope not! 2014 has not gotten to September, November or December yet! And the ISO-11179 data element name should be “payment_month”; but it is still wrong! An expense is not a payment! An income is not a payment!
>> I would like to create a balance view table that will show me the financial status for the Q1 (for example). <<
Report Period Table
Since SQL is a database language, we prefer to do look ups and not calculations. They can be optimized while temporal math messes up optimization. A useful idiom is a report period calendar that everyone uses so there is no way to get disagreements in the DML.
The report period table gives a name to a range of dates that is common to the entire enterprise.
CREATE TABLE Something_Report_Periods
(something_report_name CHAR(10) NOT NULL PRIMARY KEY
CHECK (something_report_name LIKE <pattern>),
something_report_start_date DATE NOT NULL,
something_report_end_date DATE NOT NULL,
CONSTRAINT date_ordering
CHECK (something_report_start_date <= something_report_end_date),
etc);
These report periods can overlap or have gaps. I like the MySQL convention of using double zeroes for months and years, That is 'yyyy-mm-00' for a month within a year and 'yyyy-00-00' for the whole year. The advantages are that it will sort with the ISO-8601
data format required by Standard SQL and it is language independent. The pattern for validation is '[12][0-9][0-9][0-9]-00-00' and '[12][0-9][0-9][0-9]-[01][0-9]-00'
Now figure it out for yourself, show us what effort you put into this, then we will help you.
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

SSIS 2012 - Importing multiple files with different columns (where columns are stored in a table)

Hi everyone,
I have been tasked to upgrade an existing DTS package into an SSIS package.
The old package uses 3 tables.
Table 1) Has a list of file names
Table 2) Has a list of columns per file
Table 3) Is the data destination.
So what is supposed to happen is:
Step 1) the package should load the files into a resultset
Step 2) for each file in the resultset, the package should get the related columns
Step 3) the package should now map the columns to the destination table (variable column numbers here)
Step 4) the import should take place.
I have gotten to step 2 but am not sure how to dynamically map the columns to the destination table.
Any pointers anyone?
Thanks in advance!

Hi Tonyhektic,
What’s the nature of Table 2, does it only store the column names for each file? I don’t know how it is implemented in DTS package, however, in SSIS package, dynamic columns mapping is not supported. To work around this issue, we need to use Script component
to do the columns mapping. You can refer to Sorna’s script above or have a look at the following blogs:
http://munishbansal.wordpress.com/2009/06/09/dynamic-columns-mapping-%E2%80%93-script-component-as-destination-ssis/
http://blog.quasarinc.com/ssis/best-solution-to-load-dynamically-change-csv-file-in-ssis-etl-package/
Regards,
Mike Yin
TechNet Community Support

How to join two columns between two tables with different column names

Hi
How i can join 2 columns with different names between the 2 tables.
Can any one please give solution for this.
Thanks
Manu

Hi,
basic understanding of joins:
If you want to join 2 tables there should be matching column w.r.t. data and it's data type. You need not to have same column names in both the tables...
so, find those columns which has got same values..

Error importing table metadata with quoted column names

Similar Messages

Maybe you are looking for