An ODI 12c Mapping Fails With 'ORA-00904: "xxxx"."xxxx": invalid identifier' Due to Wrong Datastore Alias Starting From Second Column in a Select
(Doc ID 2060132.1)
Last updated on APRIL 06, 2021
Applies to:
Oracle Data Integrator - Version 12.1.3.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Oracle Data Integrator (ODI) 12.1.3, a Mapping that uses "LKM Sql to Oracle" generates incorrect Datastore alias from the second column on in the Select statement that selects from the source Datastore:
select
<ALIAS>_1.COL1 COL1,
<ALIAS>.COL2 COL2
from<DBSCHEMA>.<TABLE_NAME>@<DBLINK> <ALIAS>_1
where (1=1)
and (<ALIAS>_1.<COLUMN_NAME> = 'E');
<ALIAS>_1.COL1 COL1,
<ALIAS>.COL2 COL2
from<DBSCHEMA>.<TABLE_NAME>@<DBLINK> <ALIAS>_1
where (1=1)
and (<ALIAS>_1.<COLUMN_NAME> = 'E');
The Mapping thus fails with this error:
ODI-1227: Task Load data-LKM SQL to Oracle- fails on the source connection XXX.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: "<ALIAS>"."<COLUMN_NAME>": invalid identifier
Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: "<ALIAS>"."<COLUMN_NAME>": invalid identifier
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |