Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Using MS-CDC as source and Oracle as target. Getting case sensitive data in the Oracle side.
Scenario 1:
When running this query,
select count(*) from db."Table_name";
Output: 552816
Scenario 2:
When running query without quotes,
select count(*) from db.Table_name;
Output: Throwing Error telling
Table or view doesn't exist
I want this query to run without quotes.
Hello @Supriya_I ,
Welcome to Qlik Community forum and thanks for reaching out here!
This is because the table name in Oracle is in upper case by default. If the table name is mixed by some lower case characters, then we have to quote the table to let Oracle query processor works.
The most easy way is defining a Global Transformation to convert the table name to upper case. A sample:
Hope this helps.
John.
Hello @Supriya_I ,
Welcome to Qlik Community forum and thanks for reaching out here!
This is because the table name in Oracle is in upper case by default. If the table name is mixed by some lower case characters, then we have to quote the table to let Oracle query processor works.
The most easy way is defining a Global Transformation to convert the table name to upper case. A sample:
Hope this helps.
John.
This is standard Oracle behavior. In fact MS SQL is just about the only DB Trying to 'help' by making stuff implicitly case insensitive.
The topic mentions case sensitive data, but the text asks about meta-data.
Replicate can easily be told to transform mixed case to upper or lower case, for data and Metadata, for specific objects (tables, columns) or whole groups. As per John's reply. One could argue that you loose data accuracy and readability for all for the convenience of a few.
Good luck!
Hein