The following topics are addressed here:
ODI is Oracle's strategic product for heterogeneous data integration. Because many Oracle Database customers have significant investment in OWB, Oracle supports a phased migration from OWB 11gR2 (188.8.131.52) to ODI 12c (12.1.2). The following features are provided to make the transition to ODI easier:
ODI 12c supports the execution and administration of OWB 11gR2 jobs directly within ODI Studio and ODI Console, providing a single orchestration and monitoring solution. This feature enables you to migrate OWB objects over a longer period of time and in a way that makes sense for your business. For more information about this feature, see "OdiStartOwbJob" in the tools reference section of the Developer's Guide for Oracle Data Integrator.
ODI 12c supports an easier mapping between OWB 11gR2 concepts and objects and their ODI 12c counterparts. A migration utility is provided that automatically translates many OWB objects and mappings into their ODI equivalents. For more information about the migration utility, see About the Migration Utility.
The migration utility is a command-line tool that enables you to migrate design-time metadata from OWB to ODI. Runtime data and physical objects are not migrated. The migration utility uses the settings in the migration utility configuration file to perform the migration.
For information about obtaining the patch, see Migration Requirements.
The migration utility is an aid to migration only, and not all types and variants of OWB objects are migrated. Manual effort should be expected as well.
The following topics are addressed here:
The following OWB objects are supported for migration when you run the migration utility:
modules (source and target)
table (columns, keys, indexes)
view (columns, keys)
materialized view (columns, keys, indexes)
external table (columns)
file (records, fields)
Code Template mappings
Mapping Input Parameter
Pre/Post Mapping Process
The following OWB objects are not supported for migration when you run the migration utility:
table (partitions, attribute sets, data rules)
view (attribute sets, data rules)
materialized view (partitions, attribute sets, data rules)
external table (data rules, locations)
dimensional modeling metadata
Oracle Discoverer metadata and derived Oracle Business Intelligence Suite Enterprise Edition (OBI EE) metadata
custom PL/SQL (procedure, package, and so on)
queues, streams, CDC (Change Data Capture) configurations, user-defined types
mappings using dimension and cube, cursor-based maps, name and address, match-merge, data rules, data auditors, iterators, expand, construct, Anydata Cast
data quality, data profiles, data auditors
configuration details (security, user extensions, transportable modules, schedules/collections, user folders)
Table 1-1 provides a high-level summary of the steps required to migrate from OWB to ODI. The table also lists where to find more information for each step.
Verify your system environment
Before running the migration utility, verify that your system meets requirements.
Review supported and unsupported objects
Make sure you understand what will and will not be migrated.
Edit the migration utility configuration file
Edit the migration utility configuration file and make sure the settings are correct for your environment.
The configuration file contains connection information and other details required for migration.
Run the migration utility
Run the migration utility to migrate OWB objects to ODI using the settings in the migration utility configuration file.
Review the migration utility log file
After migration is complete, review the migration utility log file.
The file contains details about objects that were migrated, and error messages if errors occurred.
Review the migration utility exclusion report
After migration is complete, review the migration utility exclusion report.
The report provides a summary of objects that were migrated, and lists whether migration succeeded or failed for each object.
Verify your migration
In ODI Studio, connect to your ODI environment and perform post-migration testing to verify your migration.