ODI 11g Smart Import does not Handle KM Options
(Doc ID 2526623.1)
Last updated on APRIL 14, 2021
Applies to:
Oracle Data Integrator - Version 11.1.1.9.0 to 11.1.1.9.99 [Release 11gR1]Information in this document applies to any platform.
Symptoms
When Smart Importing an Interface into an Oracle Data Integrator (ODI) 11g environment, the values of the Knowledge Module (KM) options are not taken into account.
For reproducing the behavior:
- In ODI environment <ODI 1>, have an Integration Interface that uses a Knowledge Module where options are set to values other then **Default**.
For example:
- INTERVAL_COMMIT: true
- ALLOW_DELETE: false
- Smart Export the Integration Interface above, and Smart Import into a new ODI 11g environment, <ODI 2>, where the Interface and used KMs do not exist yet.
Observe the KM options are keeping their original values:
- INTERVAL_COMMIT: true
- ALLOW_DELETE: false
- Edit the Integration Interface in <ODI 2>, and change the value of one of options:
- INTERVAL_COMMIT: true
- ALLOW_DELETE: true
Apply the changes.
- Re-smart Import into <ODI 2> the Interface exported at point #2 above.
Observe that post import, the values of KM options above remain unchanged:
- INTERVAL_COMMIT: true
- ALLOW_DELETE: true
... while ODI should have imported / updated the KM options to the values it has in the environment from where the smart export has been extracted:
- INTERVAL_COMMIT: true
- ALLOW_DELETE: false
Note: This issue can be reproduced every time a KM option is changed from true or false to the default value.
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 |