Upgrade to ODI 12c Changes the Order of Reusable Mapping Target Datastore Columns
(Doc ID 2290746.1)
Last updated on APRIL 24, 2020
Applies to:Oracle Data Integrator - Version 184.108.40.206.0 and later
Oracle Data Integrator Cloud Service - Version 17.1.3 and later
Information in this document applies to any platform.
NOTE: In the images below, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Having an Oracle Data Integrator (ODI) 11g Temporary Interface that reads data from a source File Datastore, using the out-of-box "LKM File to Netezza (NZLOAD)" knowledge module.
Since this LKM does not pass the File METADATA along with the data (/*$$SNPS_START_KEY..............$$SNPS_END_KEY*/), the order of columns in the source File Datastore must match the order of columns in the target Datastore.
Or, when upgrading to ODI 12c, the order of target Datastore columns in the _RMT and _RMS Reusable Mappings no longer matches the order of columns in the source File Datastore, therefore leading to either invalid data, or error messages if the type of columns are incompatible (for example, "Bad numeric input format 'my string' " when loading a string into numeric).
To illustrate the above, the screen copy below shows the order of columns in the 11g Temporary Interface:
The screen copy below shows the order of columns post upgrade (or smart import) into ODI 12c:
Upgrade from 11g to 12c.
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