Incorrect Field Mappings when Using Oracle External Tables and a Subset of Delimited Flat File Fields with ODI
(Doc ID 424013.1)
Last updated on OCTOBER 04, 2022
Applies to:
Oracle Data Integrator - Version 3.2.03.01 and laterInformation in this document applies to any platform.
Symptoms
After having created an Oracle external table based on a subset of fields contained in a delimited flat file, SQL instructions (SELECT, ...) to consult this table are incorrect.
For example, given a delimited flat file consisting of the following fields C1, C2, C3, C4 and C5.
If an Oracle External table is specified to include fields C3 and C5 in an external table, an SQL "SELECT C3, C5..." instruction to this table results in :
- the values for the table.C3 columns match data values in the C1 flat file field;
- and the values for the table.C5 columns match values in the C2 flat file field.
Is there a work around for such a problem when loading data using the LKM File to Oracle External Table 9i with ODI ?
Changes
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 |
Changes |
Cause |
Solution |
References |