OdiReverseSetMetaData Does Not Set Storage Type and Table Options for ERP Cloud Models
(Doc ID 2708454.1)
Last updated on SEPTEMBER 14, 2020
Applies to:
Oracle Data Integrator - Version 12.2.1.0.0 to 12.2.1.4.200721 [Release 12c]Information in this document applies to any platform.
Symptoms
When using a custom reverse knowledge module (RKM) in Oracle Data Integrator (ODI) Studio to reverse engineer ERP Cloud Reports metadata to a model, it returns successful, however, it does not correctly set the table storage type and table options.
The OdiReverseSetMetaData tool was attempted with "-USE_TABLE_NAME_FOR_UPDATE" set to both YES and NO, with no change in behavior. It does not set storage type to delimited despite it is inserted into as -SNP_REV_TABLE.I_TABLE_FORMAT_TYPE=2. Similarly, table options are set by inserting into SNP_REV_TABLE.TABLE_PROP in the form {"BIPReportLocation"="/Financials/Payables/Invoices/PayablesInvoicesSuppliersExtract.xdo"}
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 |
| Workaround |
| References |