From Oracle Warehouse Builder to Oracle Data Integrator fast and safe

Database & Technology was founded in Milan, Italy in 1999.

since 2008 we have been performing OWB to ODI migrations, having designed and developed a semi-automated tool that allows any company to migrate to

ODI, saving then a great deal of time and money compared to a manual migration.

Database & Technology

From Oracle Data Integration Statement of Direction: So if client has to migrate or wants to migrate from OWB to ODI, a transfer of the OWB components to equivalent ODI components needs to be planned

From Oracle Data Integration Statement of Direction: So if client has to migrate or wants to migrate from OWB to ODI, a transfer of the OWB components to equivalent ODI components needs to be planned

• No major enhancements are planned for Oracle Warehouse Builder beyond the OWB 11.2 release.

• OWB 11.2 continues to be available and supported by Oracle, and patches and bug fixes will continue to be offered at regular intervals

• OWB is certified on the Oracle Database 12c Release 1 which gives customers a long window in which to migrate to ODI

• Future database releases beyond Oracle Database 12c Release 1 will not be certified with OWB 11.2

OWB2ODI Converter is a semi-automatic tool developed by D&T to assist the migration of OWB projects into ODI projects

OWB2ODI Converter can speed up the migration process significantly The conversion can be done either at the customer or in outsourcing,

starting from export of the OWB project OWB2ODI Converter is a service, so the developed tool for conversions is not

for sale. We sell the service, not the tool.

About the Converter

OWB2ODI Converter acquires OWB repository’s metadata and it generates the corresponding ODI repository.

Objects in OWB are transferred in ODI and OWB operators are transformed

in corresponding ODI operators.

Product overview

Supported versions

OWB v. 9.2 or higher ODI v. 10g or higher

1. An export of OWB repository (.mdl), containing all projects to be converted

2. An export (data pump or exp) of all involved physical schemas. We need only the structures (tables, views, etc.). We don’t need any data.

What do we need

Export file

OWB

Process Flows

Mappings

OWB Repository DB Schemas

.mdl file

After initial assessment phase with the client, a specific Converter component extracts metadata from the OWB .mdl file. In their own laboratories, D&T uses the OWB2ODI Converter to generate automatically the corresponding ODI project from the original OWB one. The generated ODI project is sent to the client for the acceptance test.

Conversion process

• In order to give the Customer an estimation report abut timing and costs of the conversion, we perform a preliminary check of OWB repository

• Approach 1: We ask the Customer to provide us with an export of OWB

project (.mdl file) • Approach 2: We send to the Customer a package of integrated scripts,

asking the Customer to install them and run, then give us the results.

Assessment Report

1/2 days .mdl file

export

Assessment report

OWB

Process Flows

Mappings

Assessment Report Approach 1

Customer D&T

Sent back for evaluation

1/2 days

results

Assessment report

Assessment Report Approach 2

Customer D&T

Sent for evaluation

OWB

Process Flows

Mappings TCL Scripts

Assessment Report Mappings

Assessment Report Process Flows

General architecture

How Converter Migrates OWB Metadata

OWB2ODI Converter can migrate:

• OWB Project ODI Project

• OWB Location ODI Topology Logical Schema

• OWB Module ODI Folder

• OWB Mapping

ODI 11g: ODI Packages ODI Interfaces ODI Temporary Interfaces

ODI 12c: ODI Package ODI Mapping

Migration to ODI 11g

Complex Mappings need to be split into several interfaces to generate the same SQL Code

How Converter Migrates OWB Metadata

Migration to ODI 12c

Many similarities between ODI 12c and OWB mapping. Little rework for particular combination of operators

How Converter Migrates OWB Metadata

SOME EXAMPLES OF MAPPING CONVERSION

Example 1 – MULTI TARGET MAPPING

Example 1 – MULTI TARGET MAPPING (11g)

Since Oracle Data Integrator does not allow a mapping flow to end in multiple targets owb2odi converter generates as many interfaces as the OWB target Table Operator.

Example 1 – MULTI TARGET MAPPING (11g)

The Package will contain the correct sequencing of interfaces maintaining the native semantic of the mapping

Example 1 – MULTI TARGET MAPPING (12c)

Example 1 – MULTI TARGET MAPPING (12c)

Example 2 – MULTI STAGING MAPPING

Example 2 – MULTI STAGING MAPPING ODI 11g

Also in this example owb2odi Converter generates two interfaces to manage the intermediate loading of the SRC_CITY table

Example 2 – MULTI STAGING MAPPING ODI 12c

Example 3 – SETOP

Example 3 – SETOP ODI 11g

Set Operator is converted using the ODI Dataset feature

Example 3 – SETOP ODI 12c

In ODI 12c is similar

Example 4 – Using premapping

Example 4 – Using premapping: our approach

Example 4 – Using premapping: other approach

How Converter Migrates OWB Metadata

OWB2ODI Converter can also migrate Process Flows:

• OWB Process Flow ODI Load Plan

How Converter Migrates OWB Metadata

OWB Process Flow ODI Load Plan

How Converter Migrates OWB Metadata

ODI Load Plan - An example

PARENT

CHILD_1 CHILD_2

How Converter Migrates OWB Metadata

ODI Load Plan - An example

How Converter Migrates OWB Metadata

ODI Load Plan and use of START_LOAD_PLAN_PRC procedure

• It’s a Groovy script • It calls SDK API library • Allows starting a load plan inside a load plan • Variables values are forwarded recursively to all children • Allows restarts from failures checking children status • If some child has finished correctly, then a restart will not execute it again

Where is it semi-automatic?

OWB

Process Flows

Mappings

DT Analyze

ODI

Load Plans

Mappings

KM Topology

Conversion

Why is it semi-automatic?

Locations vs Topology

• Usually an OWB location is converted to an ODI data server and a physical schema

• Such a case would lead to an unefficient topology: two different data servers

10.1.1.15 = server1

Why is it semi-automatic?

Locations vs Topology

10.1.1.15 = server1

Datastore Management Management of NOT BOUND operators Management of operators with NO LOCATIONS Synchronization between NOT BOUND operators and BOUND operators Customize Models organization (SubModel hierarchy)

Why is it semi-automatic?

KM Management

• Setting Customize KM on Mapping

• Ready to run mappings

Why is it semi-automatic?

OWB to ODI Conversion

Manual process Automatic process

Assessment

Conversion

Test

Manual recognition

Manual coding

Manual verification

Automatic

Automatic

Manual verification

Conversion standard timing

Conversion

1/2 days

Assessment

.mdl file

Assessment report

5/10 days .mdl file

DB’s schema (no data)

ODI Project xml

ODI Topology xml

Assessment meeting

To summarize: ASSESSMENT

Task 1: Generate a Conversion Assessment and Statistics Report Task 2: Decide on exceptions handling Task 3: Define the topology Task 4: Compare the possible conversion modes Task 5: Define the Knowledge Modules (KM) Task 6: Decide on configuration management

Task 1: Generate a Conversion Assessment and Statistics Report

The .mdl file is analyzed, a report is generated and sent to the client

To summarize: ASSESSMENT

Task 2: Decide on exceptions handling

Decide how to handle the rare but possible case in which an automatic conversion is not possible.

To summarize: ASSESSMENT

Task 3: Define the topology

In ODI, the definition of the topology,

the logical architecture, and the

physical architecture are necessary to

indicate where the data are physically

located

To summarize: ASSESSMENT

Task 4: Compare the possible conversion modes

providing the client with a detailed

explanation of the conversion mode

To summarize: ASSESSMENT

Task 5: Define the Knowledge Modules (KM)

Decide which KM to use for each

mapping

To summarize: ASSESSMENT

Task 6: Decide on configuration management

What will be the operative protocol to adopt

during the conversion period?...

Roles, Responsabilities, actions, etc.

To summarize: ASSESSMENT

To summarize: CONVERSION

Task 7: Conversion of mappings and Process Flows Task 8: Execute formal tests Task 9: Generate the ODI project’s metadata

Task 7: Conversion of mappings and Process Flows

Mappings and process flows are converted

according to what decided in previous steps

To summarize: CONVERSION

Task 8: Execute formal tests

Run all ODI mappings on empty data

structures.

To summarize: CONVERSION

Task 9: Generate the ODI project’s metadata

XML files are generated from ODI export, in

order to be delivered to the client.

To summarize: CONVERSION

To summarize: ACCEPTANCE TESTS

Task 10: Set up the ODI Test Environment Task 11: Execute acceptance tests Task 12: Tune the new ODI project’s performance

Task 10: Set up ODI Test Environment

• installing the OWB product

• installing the ODI product

• copying the OWB project’s components

• importing the .xml files supplied by D&T’s

Services Centre into the ODI repository and

• copying the production databases twice:

one copy for the OWB project and another

copy for the ODI project.

To summarize: ACCEPTANCE TESTS

Task 11: Execute acceptance tests

The ODI project is tested to ensure that there

are no regression issues

To summarize: ACCEPTANCE TESTS

Task 12: Tune the ODI project’s performances

Tune the ODI project’s performances in

collaboration with the client’s Database

Administrator

To summarize: ACCEPTANCE TESTS

To summarize: PRE-PRODUCTION

Task 13: Set up the ODI Production Environment Task 14: Execute additional tests (privileges, configuration, missing patches) Task 15: Verify performance

To summarize: PRODUCTION

Task 16: Clean the Production Environment Deinstall OWB Deinstall unnecessary software component Task 17: Switch from OWB to ODI and set up new schedules

OWB to ODI Conversion project

Scenario PEDW (Pirelli Enterprise DW)

OWF (400 flows)

OWB v. 10.2 (2.300 mappings)

Oracle DB v. 10g

ODI v. 11.1.1.6

Platforms (Oracle, Sql Server, SAP, sequential files, …)

Success Story

TRY US

Largo Promessi Sposi 4. 20142 Milano, Italy Phone: +39 02 8950 0080 Fax: +39 02 8954 9736 Mobile: +39 348 6979791

Emails: massimo.sposaro@databtech.com dt.marketing@databtech.net

Websites: www.owb2odiconverter.com www.databtech.com

OWB to ODI Migration Group

Database & Technology