The document discusses migrating Oracle Warehouse Builder (OWB) projects to Oracle Data Integrator (ODI) projects using a tool called OWB2ODI Converter. The tool can convert OWB mappings, modules, and data modules to ODI packages, folders, and models. It supports migrating many common mapping operators and patterns between the two platforms, handling issues like mappings with multiple target tables. The document provides examples of how complex OWB mappings involving set operators, pivoting, and temporary tables would be converted.

1. From Oracle Warehouse Builder
to Oracle Data Integrator
fast and safe
®

2. SUMMARY
Introduction
General Architecture
What do we Need
How We Migrate OWB Mapping
Supported Operators
KMs Customizable Choosing Grid
OWB & ODI Releases Compliance
Some Migration Examples and Typical Issues

3. INTRODUCTION
OWB2ODI Converter is a semiautomatic tool
developed by D&T to assist the migration of OWB
projects into ODI projects
OWB2ODI Converter can speed up the migration
process
90% of migration’s manual activities can be cut
back
The conversion can be done either at the
customer or in outsourcing, starting from export
of the OWB project

4. WHAT DO WE NEED
An OWB .mdl export file of the project to convert
An Oracle physical export of all involved target schema.
Note: We don't need data, only the structures
(exp…ROWS=N or expdp…CONTENT= METADATA_ONLY)

5. GENERAL ARCHITECTURE
export of schemas
(only structures)
OWB2ODI Converter
Converter
mdl export file
DB
Repository
OWB
Process
flows
Mappings
ODI Project
xml
ODI Topology
xml

6. HOW WE MIGRATE OWB MAPPINGS
OWB2ODI Converter can migrate:
OWB Project ODI Project
OWB “data module” ODI Model
OWB Module ODI Folder
OWB Mapping ODI Packages with one
or more Interfaces /
Temporary Interfaces

7. SUPPORTED OPERATORS

8. KMs CUSTOMIZABLE CHOOSING GRID

9. KMs CUSTOMIZABLE OPTIONS
D&T customized KMs can also manage other aspects like:
management of ANALYZE on target table
management of the maximum number of errors
management of loading HINT
management of selecting HINT
setting Mapping Update Keys
etc…

10. OWB & ODI RELEASES COMPLIANCE
OWB release >= 9.2
ODI release >= 10

11. SOME EXAMPLES OF MAPPING CONVERSION

12. Example 1 – MULTI TARGET MAPPING

13. Example 1 – MULTI TARGET MAPPING ( Converted )
Since Oracle Data Integrator does not allow a mapping flow to end in multiple targets
owb2odi converter generates as many interfaces as the OWB Table Operator Targets.

14. Example 1 – MULTI TARGET MAPPING ( Converted )
The Package will contain the correct sequencing of interfaces maintaining the native
semantic of the mapping

15. Example 2 – MULTI STAGING MAPPING

16. Example 2 – MULTI STAGING MAPPING ( Converted )
Also in this example owb2odi Converter generates two interfaces to manage the
intermediate loading of the SRC_CITY table

17. Example 3 – SET OPERATOR

18. Example 3 – SET OPERATOR ( Converted )
Set Operator is converted using the ODI Dataset feature

19. Example 4– PIVOT / UNPIVOT OPERATOR
A D&T Customized IKM manage the PIVOT and UNPIVOT behavior

20. Example 5 – TEMPORARY INTERFACES

21. Example 5 – TEMPORARY INTERFACES ( Converted )
owb2odi converter generate automatically temporary interfaces to
keep the semantic between OWB and ODI in some particular
situations like Aggregator, Pivot/Unpivot, Deduplicator, etc…

22. Largo Promessi Sposi, 4
20142 Milano (Italy)
Phone +39 02 8950 0080
Fax +39 02 8954 9736
Email:
dt.marketing@databtech.net
Websites:
www.databtech.com
www.owb2odiconverter.com
Database & Technology s.r.l.
®