OWB to ODI Migration Utility Does Not Migrate Bound Name of Mapping Table Operator To ODI Datastore
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Warehouse Builder - Version 220.127.116.11 and later
Oracle Data Integrator - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
You have OWB mappings where some table operators are not bound to the table in the project tree.
This works fine in OWB: 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.
Migration from OWB to ODI.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms