My Oracle Support Banner

OWB to ODI Migration Utility Does Not Migrate Bound Name of Mapping Table Operator To ODI Datastore (Doc ID 2036792.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Warehouse Builder - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Oracle Data Integrator - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

There are Oracle Warehouse Builder (OWB) mappings where some table operators are not bound to the table in the project tree.
This works fine in OWB: the code is generated correctly and mappings run fine.

However, migrating these mappings to ODI shows that these tables are not pointing to the correct data store (comparable with the bound name in OWB).
The resulting ODI datastore has the value of the Physical Names property of the OWB table operator.

Changes

 Migration from OWB to ODI.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.