Fusion Middleware Documentation
Advanced Search


Migrating From Oracle Warehouse Builder to Oracle Data Integrator
Close Window

Table of Contents

Show All | Collapse

3 Using the Migration Utility to Migrate

This chapter describes how to use the migration utility to migrate objects from OWB to ODI.

Migration is performed using the settings specified in the migration utility configuration file. For more information about this file, see Creating the Migration Utility Configuration File.

Note:

The OWB workspace and the ODI repository should not be in use when you run the migration utility and perform the migration.

The following topics are addressed here:

Migration Utility Syntax and Parameters

The migration utility is started from the command line and takes several parameters as inputs to perform the migration.

The migration utility file is named migration.sh and is executed from the OWB_HOME/owb/bin/unix directory, where OWB_HOME is your OWB installation directory.

The syntax to run the migration utility and perform the migration is as follows:

./migration.sh <odi_master_password> <odi_user_password> <owb_workspace_owner_password> <configuration_file>

For example:

./migration.sh odi_master supervisor migration /scratch/jsmith/Migration/owb_migration.properties

The command parameters are as follows:

  • odi_master_password: ODI master repository password

  • odi_user_password: ODI user password

  • owb_workspace_owner_password: OWB workspace owner password

  • configuration_file: Full path to the migration utility configuration file and the file name

See Also:

For more information about the migration modes used to test and perform the migration, see MIGRATION_MODE in Configuration File Parameters.

After migration is complete, you are returned to the command prompt. You can then review the migration utility log file and exclusion report for details about the migration. For more information about these files, see Reviewing Log and Report Files.

Migrating an OWB Workspace

To migrate an entire OWB workspace, use the wild card asterisk (*) as the value for the MIGRATION_OBJECTS parameter in the migration utility configuration file. For example:

MIGRATION_OBJECTS=*

All projects and supported objects in the OWB workspace specified by the OWB_WORKSPACE_NAME parameter in the configuration file will be migrated.

Note:

You can migrate just one workspace at a time. Edit the configuration file and run the migration utility for each workspace that you want to migrate.

Migrating Specific Objects in an OWB Workspace

To migrate specific objects in an OWB workspace, configure the MIGRATION_OBJECTS parameter in the migration utility configuration file to migrate just those objects. You can specify a project, folder, or single non-folder object, or a set of objects that share the same type and the same folder.

Use a string that concatenates the qualifying names of all objects included in the object's path, from the top-level object to the leaf object. Qualifying names are specified as OBJECT_TYPE.OBJECT_PHYSICAL_NAME, with a period (.) separating the object type from its physical name. For example, to select table T_1 in Oracle module MOD_1 in project PRO_1, set the value of the MIGRATION_OBJECTS parameter to PROJECT.PRO_1.MODULE.MOD_1.TABLE.T_1.

The following values can be used for OBJECT_TYPE:

  • EXTERNAL_TABLE

  • FLAT_FILE_MODULE

  • FLAT_FILE

  • GENERIC_FOLDER

  • GENERIC_MODULE

  • LOCATION

  • MODULE

  • MAPPING

  • MATERIALIZED_VIEW

  • PLUGGABLE_MAPPING

  • PLUGGABLE_MAPPING_FOLDER

  • PROJECT

  • SAP_MODULE

  • SEQUENCE

  • TABLE

  • VIEW

Use a semicolon (;) to separate multiple items, for example:

MIGRATION_OBJECTS=PROJECT.PRO_1.MODULE.MOD_1.TABLE.T_1;PROJECT.PRO_2.MODULE.MOD_2;

Use a backslash (\) at the end of a line to improve readability of the configuration file if there are multiple items, for example:

MIGRATE _OBJECTS=
PROJECT.OWB_MIGRATION.SAP_MODULE.MY_SAP_MOD;\
PROJECT.MY_PROJECT.MODULE.ORA_MOD;\
PROJECT.MY_PROJECT.MODULE.DB2_MOD

Use the wild card asterisk (*) at the end of a string instead of an object name to select all objects of a specific type in a folder. The following example selects all tables in module MOD_1:

MIGRATION_OBJECTS=PROJECT.PRO_1.MODULE.MOD_1.TABLE.*

Use the wild card asterisk (*) at the end of an object name to select all objects with that name. The following example selects all tables in module MOD_1 with a name that starts with MYTEST:

MIGRATION_OBJECTS=PROJECT.PRO_1.MODULE.MOD_1.TABLE.MYTEST*

The following uses are not supported:

MIGRATION_OBJECTS=PROJECT.*.MODULE.MOD_1.TABLE.T_1;
MIGRATION_OBJECTS=PROJECT.PRO_1.MODULE.*.TABLE.T_1;
MIGRATION_OBJECTS=PROJECT.*.MODULE.*.TABLE.*;
MIGRATION_OBJECTS=PROJECT.PRO_1.MODULE.*.TABLE.MYT*;
MIGRATION_OBJECTS=PROJECT.PRO_1.MODULE.MYMOD*.TABLE.MYT_1;

When an invalid object is specified, an error is returned:

[ERROR][Migration][MU-1005] The selected object {0} does not exist or the
selection is invalid. It will be skipped.

For more information about error messages that you might encounter when you run the migration utility, see Error Message Reference.

Example 3-1 Migrating Specific Objects

This section provides additional examples of migrating specific objects.

The following example migrates Oracle Database module ORACLE_EBS_D in project SSAD:

MIGRATION_OBJECTS=PROJECT.SSAD.MODULE.ORACLE_EBS_D;

The following example migrates pluggable mapping DEBS_EDW_MAP1 in pluggable mapping folder DWPR_SUB:

MIGRATION_OBJECTS=PROJECT.PROJ_DW.PLUGGABLE_MAPPING_FOLDER.DWPR_SUB.PLUGGABLE_MAPPING.DEBS_EDW_MAP1;

The following example migrates standalone pluggable mapping PLUGGABLE_MAPPING_1 in project SSA:

MIGRATION_OBJECTS=PROJECT.SSA.PLUGGABLE_MAPPING.PLUGGABLE_MAPPING_1

Performing a Test Migration

To test your migration before executing it, set the MIGRATION_MODE parameter in the migration utility configuration file to FAST_CHECK or DRY_RUN.

The FAST_CHECK option checks which objects can and cannot be migrated. The DRY_RUN option checks whether the specified objects can be created in the target ODI repository, and executes the migration without committing the objects to the repository. For more information about these options, see MIGRATION_MODE in Configuration File Parameters.

After performing a test migration, review the migration utility log file and exclusion report for details. You can use these files to identify objects that can and cannot be migrated and to address any issues before performing the actual migration. For more information about these files, see Reviewing Log and Report Files.