4 Reviewing Your Migration

Reviewing your migration includes reviewing logs and report files.

The following topics are addressed here:

4.1 Reviewing Log and Report Files

You can use the log and report files to review, refine, and troubleshoot your migration.

Two files are created after migration is complete or after you perform a test migration. By default, the files are named migration.log and migration.report. Use these files to review, refine, and troubleshoot your migration.

By default, the files are saved in the same location as the migration utility configuration file. You can specify a different file name and location using the MIGRATION_LOG_FILE parameter in the configuration file. For more information about this parameter, see MIGRATION_LOG_FILE in Configuration File Parameters.

The following topics are addressed here:

4.1.1 Reviewing the Migration Utility Log File

The migration utility log file contains details about objects that were migrated, rejected, or skipped, and error messages if any errors occurred.

The log file is organized in the following sections:

  • Log file header with migration mode, log file creation time, OWB and ODI details, full path to the log file, and configuration options.

  • Migration start time.

  • Detailed information about the migration status of each object (whether migration succeeded, was rejected, or skipped) and error messages if errors occurred. For more information about informational, warning, and error messages that you might encounter when you run the migration utility, see Message Reference.

  • Summary information organized by object type, including the path to each object.

  • Log file footer with total execution time and migration end time.

Example 4-1 Sample Migration Utility Log File

This example shows a sample migration utility log file, with MIGRATION_MODE set to RUN.

*******************************************************************************
* Oracle Warehouse Builder - Migration Utility - Log
* Created: 9/26/16 7:42 PM
* Migration Report Style - RUN
* 
* OWB Release:11.2.0.4.0 - OWB Repository:
OWB_REPO_MIG/machine.example.com:1521:orcl11204 - OWB Workspace:
OWB_REPO_MIG.OWB_REPO_WKSP1
*
* ODI Release:12.2.1.2.6 - ODI Master mig12c/jdbc:oracle:thin:@machine:1521:orcl11203 - ODI User/Work Repository:SUPERVISOR/WORKREP1
* 
* Log File: /tmp/migration.log
* 
* Configuration Options
*
 ---------------------
* MIGRATION_REPORT_INCLUDE=ALL
* MIGRATION_MODE=RUN
* MIGRATE_DEPENDENCIES=true
* STOP_ON_ERROR=true
* SPLIT_JOIN_FOR_ANSI_SYNTAX=true
* MIGRATE_UNBOUND_OPERATOR=true
* FLUSH_BATCH_SIZE=50
* MIGRATION_STRATEGY=NODUP
* MIGRATION_OBJECTS=PROJECT.DIM_PROJECT
********************************************************************************

Migration started at 9/26/16 7:42 PM Pacific Standard Time
 
********************************************************************************
----START MIGRATE LOCATION REP_TARGET.
----SUCCESSFULLY MIGRATED REP_TARGET. 
----START MIGRATE PROJECT DIM_PROJECT.FLUSH OdiDataServer[1]  COST(MS):1178
-------START MIGRATE MODULE_FOR_LOGICALSCHEMA DIM_MOD.
-------SUCCESSFULLY MIGRATED DIM_MOD.
----START MIGRATE MODULE DIM_MOD.FLUSH OdiLogicalSchema[1]  COST(MS):744
-------START MIGRATE TABLE AT_009_DIM_LEV1.
-------SUCCESSFULLY MIGRATED AT_009_DIM_LEV1. 
-------START MIGRATE TABLE AT_009_DIM_LEV2.
-------SUCCESSFULLY MIGRATED AT_009_DIM_LEV2.
-------START MIGRATE TABLE AT_009_DIM_LEV3.
-------SUCCESSFULLY MIGRATED AT_009_DIM_LEV3.
-------START MIGRATE TABLE AT_009_SRC_LEV1. 
-------SUCCESSFULLY MIGRATED AT_009_SRC_LEV1.
-------START MIGRATE TABLE AT_009_SRC_LEV2. 
-------SUCCESSFULLY MIGRATED AT_009_SRC_LEV2.
-------START MIGRATE TABLE AT_009_SRC_LEV3.
----SUCCESSFULLY MIGRATED AT_009_SRC_LEV3. 
----START MIGRATE SEQUENCE AT_009_SEQ_SCD1.FLUSH OdiDataStore[6]  COST(MS):2084
----SUCCESSFULLY MIGRATED AT_009_SEQ_SCD1.
----SUCCESSFULLY MIGRATED DIM_MOD.
----START SECOND PASS FOR TABLE.
--------FOREIGN KEY CREATED: AT_009_DIM_LEV2.LEV2_FOREIGN_KEY --> AT_009_DIM_LEV1.LEV1_ID 
--------FOREIGN KEY CREATED: AT_009_DIM_LEV3.LEV3_FOREIGN_KEY2 --> AT_009_DIM_LEV2.LEV2_ID
----END SECOND PASS.
----START MIGRATE DIMENSION_MODULE DIM_MOD.
----START MIGRATE STAGE_TABLE LEVEL3_AT_009_DIM_STG.FLUSH OdiDimensionalModel[1]  COST(MS):455
----SUCCESSFULLY MIGRATED LEVEL3_AT_009_DIM_STG.
--------START MIGRATE STAGE_TABLE LEVEL1_AT_009_DIM_STG.
--------SUCCESSFULLY MIGRATED LEVEL1_AT_009_DIM_STG. 
--------START MIGRATE STAGE_TABLE LEVEL2_AT_009_DIM_STG.
----SUCCESSFULLY MIGRATED LEVEL2_AT_009_DIM_STG.
----START MIGRATE DIMENSION AT_009_DIM.FLUSH OdiDataStore[2]  COST(MS):1888
----SUCCESSFULLY MIGRATED AT_009_DIM. 
----SUCCESSFULLY MIGRATED DIM_MOD.
----START MIGRATE CUBE_MODULE DIM_MOD.
---------[INFO][Migration][MU-1010]DIM_MOD is skipped because it already exists.
----END MIGRATE DIM_MOD.
----START MIGRATE MAPPING_MODULE DIM_MOD.
----START MIGRATE MAPPING AT_009_MAP_TEMP_SCD1.FLUSH MAPPING, MIGRATED 0 COST(MS):181
----SUCCESSFULLY MIGRATED AT_009_MAP_TEMP_SCD1
----SUCCESSFULLY MIGRATED DIM_MOD.SUCCESSFULLY MIGRATED DIM_PROJECT.

**************************************************************************

----LOCATION[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[PUBLIC_PROJECT].LOCATION[REP_TARGET].PROJECT[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].
----MODULE_FOR_LOGICALSCHEMA[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[TOTAL:6 MIGRATED:6 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[AT_009_DIM_LEV1].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[AT_009_DIM_LEV2].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[AT_009_DIM_LEV3].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[AT_009_SRC_LEV1].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[AT_009_SRC_LEV2].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].TABLE[AT_009_SRC_LEV3].SEQUENCE[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].SEQUENCE[AT_009_SEQ_SCD1].DIMENSION_MODULE[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].DIMENSION[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].DIMENSION[AT_009_DIM].STAGE_TABLE[TOTAL:3 MIGRATED:3 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].DIMENSION[AT_009_DIM].LEVEL[LEVEL1_AT_009_DIM_STG]:98267.
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].DIMENSION[AT_009_DIM].LEVEL[LEVEL2_AT_009_DIM_STG]:98271.
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].DIMENSION[AT_009_DIM].LEVEL[LEVEL3_AT_009_DIM_STG]:98276.CUBE_MODULE[TOTAL:1 MIGRATED:0 REJECTED:0 SKIPPED:1].
------SKIPPED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].MAPPING_MODULE[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].MAPPING[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0].
------PASSED: PROJECT[DIM_PROJECT].MODULE[DIM_MOD].MAPPING[AT_009_MAP_TEMP_SCD1].

*****************************************************************************

Migration ended at 9/26/16 7:43 PM Pacific Standard Time

Total migration time (hh:mm:ss): 00:00:51

4.1.2 Reviewing the Migration Utility Exclusion Report

The migration utility exclusion report contains a summary of the objects migrated, and lists whether migration succeeded, was rejected, or skipped for each object.

The exclusion report is organized in the following sections:

  • Exclusion report header with migration mode, report creation time, OWB and ODI details, full path to the report file, and configuration options.

  • Migration start time.

  • Migration statistics including how many projects were migrated, and total number of objects migrated for each project.

  • Detailed migration status for each selected object (whether migration succeeded, was rejected, or skipped).

  • Exclusion report footer with total execution time and migration end time.

Example 4-2 Sample Migration Utility Exclusion Report

This example shows a sample migration utility exclusion report, with MIGRATION_MODE set to RUN.

*******************************************************************************
*Oracle Warehouse Builder - Migration Utility - Summary Report
*Created: 10/10/16 1:00 AM
*Migration Report Style - RUN
*
*OWB Release:11.2.0.4.0 - OWB Repository:
OWB_REPO_MIG/machine.example.com:1521:orcl11204 - OWB Workspace:
OWB_REPO_MIG.OWB_REPO_WKSP1
*
*ODI Release:12.2.1.2.6 - ODI Master Repository:
mig12c/jdbc:oracle:thin:@machine:1521:orcl11204 - ODI User/Work Repository:
SUPERVISOR/WORKREP1
*
*Report File: /tmp/migration.report
*
Configuration Options
---------------------

*MIGRATION_REPORT_INCLUDE=ALL
*MIGRATION_MODE=RUN
*MIGRATE_DEPENDENCIES=true
*STOP_ON_ERROR=true
*SSPLIT_JOIN_FOR_ANSI_SYNTAX=true
*MIGRATE_UNBOUND_OPERATOR=true
*FLUSH_BATCH_SIZE=50
*MIGRATION_STRATEGY=NODUP
*MIGRATION_OBJECTS=PROJECT.DIM_PROJECT.MODULE.DIM_MOD.MAPPING.AT_009_MAP_TEMP_SCD1
********************************************************************************

Migration started at 10/10/16 1:00 AM Pacific Standard Time

Statistics
------------

Total Projects Migrated: 2

********************************************************************************
PROJECT: PUBLIC_PROJECT
Object Types                  Migrated     Rejected     Skipped
--------------------------    ---------    ---------    --------
MODULE:                          1            0           0
MODULE_FOR_LOGICALSCHEMA:        1            0           0
TABLE:                           6            0           0
SEQUENCE:                        1            0           0
 DIMENSION_MODULE:               1            0           0
DIMENSION:                       1            0           0
STAGE_TABLE:                     3            0           0
CUBE_MODULE:                     0            0           1 
MAPPING_MODULE:                  1            0           0   
MAPPING:                         1            0           0

Details
--------
********************************************************************************
PROJECT: PUBLIC_PROJECT

Object Types                 Status
---------------------------  -------
LOCATION   REP_TARGET        SUCCESS

********************************************************************************
PROJECT: DIM_PROJECT

Object Types                 Status
---------------------------  -------
MODULE
  DIM_MOD                    SUCCESS
MODULE_FOR_LOGICALSCHEMA
  DIM_MOD                    SUCCESS
TABLE
  AT_009_DIM_LEV1            SUCCESS
  AT_009_DIM_LEV2            SUCCESS
  AT_009_DIM_LEV3            SUCCESS
  AT_009_SRC_LEV1            SUCCESS
  AT_009_SRC_LEV2            SUCCESS
  AT_009_SRC_LEV3            SUCCESS
SEQUENCE
  AT_009_SEQ_SCD1            SUCCESS
DIMENSION_MODULE
  DIM_MOD                    SUCCESS
DIMENSION
  AT_009_DIM                 SUCCESS
STAGE_TABLE
  LEVEL1_AT_009_DIM_STG      SUCCESS
  LEVEL2_AT_009_DIM_STG      SUCCESS
  LEVEL3_AT_009_DIM_STG      SUCCESS
CUBE_MODULE
  DIM_MOD                    [INFO][Migration][MU-1010]DIM_MOD is skipped because it already exists.
MAPPING_MODULE
  DIM_MOD                    SUCCESS
MAPPING
  AT_009_MAP_TEMP_SCD1       SUCCESS
 

Migration ended at 10/10/16 1:00 AM Pacific Standard Time

Total migration time (hh:mm:ss): 00:00:33

4.2 Verifying Your Migration

Follow these steps to verify that the mappings that were migrated from OWB.

When migration is complete, perform the following steps in ODI to verify the mappings that were migrated from OWB:

  • Use ODI Studio to connect to the ODI environment. See Connecting to a Work Repository in the Administrator’s Guide for Oracle Data Integrator.

  • Navigate to Topology Navigator and review the data server settings. You may need to edit some of the information such as user names, passwords, or JDBC URLs depending on your environment. Test each connection to make sure that each migrated data server is correctly configured. See Setting Up a Topology in the Administrator’s Guide for Oracle Data Integrator.

  • Navigate to Designer Navigator and review the migrated models and datastores in the Models panel. See Creating and Using Data Models and Datastores in the Developer's Guide for Oracle Data Integrator.

  • Navigate to Designer Navigator and verify the migrated mappings in the Projects panel by running the mappings. See Creating and Using Mappings in the Developer's Guide for Oracle Data Integrator.

Note:

Using the Migration Utility to migrate OWB objects to ODI is one of the many phases of migration. Please refer to the roadmap of migration as described in Understanding the Migration Process chapter for follow-up phases after the migration utility is run. Also, please note in all circumstances, manual work to fix up migrated artifacts in ODI shall be expected.