This chapter describes how to review and verify your migration.
The following topics are addressed here:
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:
The migration utility log file contains details about objects that were migrated, 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, and full path to the log file.
Migration start time.
Detailed information about the migration status of each object (whether migration succeeded or failed) and error messages if errors occurred. For more information about error messages that you might encounter when you run the migration utility, see Error 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/30/13 10:17 AM * Migration Report Style - RUN * * OWB Release:11.2.0.4.0 - OWB Repository: OWB_REPO_MIG/machine.oracle.com:1521:orcl11204 - OWB Workspace: OWB_REPO_MIG.OWB_REPO_WKSP1 * * ODI Release:12.1.2 - ODI Master Repository: mig12c/jdbc:oracle:thin:@machine:1521:orcl11203 - ODI User/Work Repository: SUPERVISOR/WORKREP1 * * Log File: /scratch/jsmith/Migration/migration.log ******************************************************************************* Migration started at 9/30/13 10:17 AM Pacific Standard Time ******************************************************************************* ----START MIGRATE LOCATION ORACLE_WH_LOCATION. ----SUCCESSFULLY MIGRATED ORACLE_WH_LOCATION. START MIGRATE PROJECT MY_PROJECT. FLUSH OdiDataServer[1] COST(MS):80 ----START MIGRATE MODULE AA_UNBOUND_TEST. FLUSH OdiLogicalSchema[1] COST(MS):16 ----SUCCESSFULLY MIGRATED AA_UNBOUND_TEST. ----START MIGRATE MAPPING_MODULE AA_UNBOUND_TEST. ------------START MIGRATE TABLE TAB2. FLUSH OdiFolder[1] COST(MS):343 ------------SUCCESSFULLY MIGRATED TAB2. ------------START MIGRATE TABLE TAB1. ------------SUCCESSFULLY MIGRATED TAB1. --------START MIGRATE MAPPING MAP_UO_CASE2. FLUSH MAPPING, MIGRATED 0 COST(MS):31 --------SUCCESSFULLY MIGRATED MAP_UO_CASE2. ----SUCCESSFULLY MIGRATED AA_UNBOUND_TEST. SUCCESSFULLY MIGRATED MY_PROJECT. ****************************************************************************** TABLE[TOTAL:2 MIGRATED:2 SKIPPED:0]. ----PASSED: PROJECT[MY_PROJECT].MODULE[AA_UNBOUND_TEST].MAPPING[MAP_UO_CASE2].OPERATOR[TAB1]. ----PASSED: PROJECT[MY_PROJECT].MODULE[AA_UNBOUND_TEST].MAPPING[MAP_UO_CASE2].OPERATOR[TAB2]. LOCATION[TOTAL:1 MIGRATED:1 SKIPPED:0]. ----PASSED: PROJECT[PUBLIC_PROJECT].LOCATION[ORACLE_WH_LOCATION]. MAPPING_MODULE[TOTAL:1 MIGRATED:1 SKIPPED:0]. ----PASSED: PROJECT[MY_PROJECT].MODULE[AA_UNBOUND_TEST]. MODULE[TOTAL:1 MIGRATED:1 SKIPPED:0]. ----PASSED: PROJECT[MY_PROJECT].MODULE[AA_UNBOUND_TEST]. PROJECT[TOTAL:1 MIGRATED:1 SKIPPED:0]. ----PASSED: PROJECT[MY_PROJECT]. MAPPING[TOTAL:1 MIGRATED:1 SKIPPED:0]. ----PASSED: PROJECT[MY_PROJECT].MODULE[AA_UNBOUND_TEST].MAPPING[MAP_UO_CASE2]. ******************************************************************************* Migration ended at 9/30/13 10:17 AM Pacific Standard Time Total migration time (hh:mm:ss): 00:00:07
The migration utility exclusion report contains a summary of the objects migrated, and lists whether migration succeeded or failed 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, and full path to the report file.
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 or failed).
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: 9/30/13 10:17 AM
* Migration Report Style - RUN
*
* OWB Release:11.2.0.4.0 - OWB Repository:
OWB_REPO_MIG/machine.oracle.com:1521:orcl11204 - OWB Workspace:
OWB_REPO_MIG.OWB_REPO_WKSP1
*
* ODI Release:12.1.2 - ODI Master Repository:
mig12c/jdbc:oracle:thin:@machine:1521:orcl11203 - ODI User/Work Repository:
SUPERVISOR/WORKREP1
*
* Report File: /scratch/jsmith/Migration/migration.report
******************************************************************************
Migration started at 9/30/13 10:17 AM Pacific Standard Time
Statistics
-----------
Total Projects Migrated: 2
******************************************************************************
PROJECT: PUBLIC_PROJECT
Object Types Migrated Not-Migrated
------------- --------- ------------
LOCATION: 1 0
******************************************************************************
PROJECT: MY_PROJECT
Object Types Migrated Not-Migrated
------------- --------- ------------
TABLE: 2 0
MAPPING_MODULE: 1 0
MODULE: 1 0
MAPPING: 1 0
Details
-----------
******************************************************************************
PROJECT: PUBLIC_PROJECT
Object Types Status
------------ -------
LOCATION
ORACLE_WH_LOCATION SUCCESS
******************************************************************************
PROJECT: MY_PROJECT
Object Types Status
------------ -------
TABLE
TAB1 SUCCESS
TAB2 SUCCESS
MAPPING_MODULE
AA_UNBOUND_TEST SUCCESS
MODULE
AA_UNBOUND_TEST SUCCESS
MAPPING
MAP_UO_CASE2 SUCCESS
MAPPING
UNBOUND_LOOKUP_MAP [ERROR][Migration][MU-5011]Unable to find bound table for
output attribute group OUTGRP1 in Lookup DEPT_LOOKUP.
Migration ended at 9/30/13 10:17 AM Pacific Standard Time
Total migration time (hh:mm:ss): 00:00:07
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 Developer'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 the Topology" in the Developer'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.