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, 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: 4/3/14 11:26 PM * 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.3.0.0 - 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=false * SPLIT_JOIN_FOR_ANSI_SYNTAX=true * MIGRATE_UNBOUND_OPERATOR=false * FLUSH_BATCH_SIZE=50 * MIGRATION_STRATEGY=NODUP * MIGRATION_OBJECTS=PROJECT.PRO_MIGRATION ******************************************************************************** Migration started at 4/3/14 11:26 PM Pacific Standard Time ******************************************************************************** ----START MIGRATE LOCATION MIGRATION_SRC_MOD_LOC. ----SUCCESSFULLY MIGRATED MIGRATION_SRC_MOD_LOC. ----START MIGRATE LOCATION OPERATOR_MIGRATION_LOC. --------[INFO][Migration][MU-1010]OPERATOR_MIGRATION_LOC is skipped because it already exists. ----END MIGRATE OPERATOR_MIGRATION_LOC. START MIGRATE PROJECT PRO_MIGRATION. FLUSH OdiDataServer[1] COST(MS):47 ----START MIGRATE MODULE_FOR_LOGICALSCHEMA TEST_MOD. ----SUCCESSFULLY MIGRATED TEST_MOD. ----START MIGRATE MODULE TEST_MOD. FLUSH OdiLogicalSchema[1] COST(MS):27 --------START MIGRATE TABLE DEPT. --------SUCCESSFULLY MIGRATED DEPT. --------START MIGRATE TABLE EMP. --------SUCCESSFULLY MIGRATED EMP. --------START MIGRATE TABLE TGT_EMP. --------SUCCESSFULLY MIGRATED TGT_EMP. --------START MIGRATE TABLE TGT_EMP_CONSTRAINTS. --------SUCCESSFULLY MIGRATED TGT_EMP_CONSTRAINTS. --------START MIGRATE VIEW TGT_V_EMP. --------SUCCESSFULLY MIGRATED TGT_V_EMP. ----SUCCESSFULLY MIGRATED TEST_MOD. ----START MIGRATE MODULE_FOR_LOGICALSCHEMA TEST_SRC_MOD. FLUSH OdiDataStore[5] COST(MS):373 ----SUCCESSFULLY MIGRATED TEST_SRC_MOD. ----START MIGRATE MODULE TEST_SRC_MOD. --------START MIGRATE TABLE EMPLOYEES. FLUSH OdiModel[1] COST(MS):78 --------SUCCESSFULLY MIGRATED EMPLOYEES. ----SUCCESSFULLY MIGRATED TEST_SRC_MOD. ----START SECOND PASS FOR TABLE. --------FOREIGN KEY CREATED: TGT_EMP_CONSTRAINTS.DEPTNO --> DEPT.DEPTNO --------FOREIGN KEY CREATED: TGT_V_EMP.DEPTNO --> DEPT.DEPTNO ----END SECOND PASS. ----START MIGRATE MAPPING_MODULE TEST_MOD. --------START MIGRATE MAPPING BASIC_JOIN. FLUSH MAPPING, MIGRATED 0 COST(MS):57 --------SUCCESSFULLY MIGRATED BASIC_JOIN. --------START MIGRATE MAPPING TLO_MAP. --------SUCCESSFULLY MIGRATED TLO_MAP. --------START MIGRATE MAPPING UNSUPPORT_MAP. ------------[INFO][Migration][MU-5001]Migration of mapping with mapping operator MATCHMERGE:MATCHMERGE is not supported. --------FAILED MIGRATE UNSUPPORT_MAP. ----SUCCESSFULLY MIGRATED TEST_MOD. ----START MIGRATE MAPPING_MODULE TEST_SRC_MOD. FLUSH Mapping[2] COST(MS):880 ----SUCCESSFULLY MIGRATED TEST_SRC_MOD. SUCCESSFULLY MIGRATED PRO_MIGRATION. ******************************************************************************** TABLE[TOTAL:5 MIGRATED:5 REJECTED:0 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].TABLE[DEPT]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].TABLE[EMP]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].TABLE[TGT_EMP]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].TABLE[TGT_EMP_CONSTRAINTS]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_SRC_MOD].TABLE[EMPLOYEES]. LOCATION[TOTAL:2 MIGRATED:1 REJECTED:0 SKIPPED:1]. ----PASSED: PROJECT[PUBLIC_PROJECT].LOCATION[MIGRATION_SRC_MOD_LOC]. ----SKIPPED: PROJECT[PUBLIC_PROJECT].LOCATION[OPERATOR_MIGRATION_LOC]. MAPPING_MODULE[TOTAL:2 MIGRATED:2 REJECTED:0 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_SRC_MOD]. VIEW[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].VIEW[TGT_V_EMP]. MODULE[TOTAL:2 MIGRATED:2 REJECTED:0 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_SRC_MOD]. PROJECT[TOTAL:1 MIGRATED:1 REJECTED:0 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION]. MAPPING[TOTAL:3 MIGRATED:2 REJECTED:1 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].MAPPING[BASIC_JOIN]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].MAPPING[TLO_MAP]. ----FAILED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD].MAPPING[UNSUPPORT_MAP]. MODULE_FOR_LOGICALSCHEMA[TOTAL:2 MIGRATED:2 REJECTED:0 SKIPPED:0]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_MOD]. ----PASSED: PROJECT[PRO_MIGRATION].MODULE[TEST_SRC_MOD]. ******************************************************************************** Migration ended at 4/3/14 11:27 PM Pacific Standard Time Total migration time (hh:mm:ss): 00:00:56
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: 4/3/14 11:26 PM *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.3.0.0 - ODI Master mig12c/jdbc:oracle:thin:@machine:1521:orcl11203 - 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=false *SPLIT_JOIN_FOR_ANSI_SYNTAX=true *MIGRATE_UNBOUND_OPERATOR=false *FLUSH_BATCH_SIZE=50 *MIGRATION_STRATEGY=NODUP *MIGRATION_OBJECTS=PROJECT.PRO_MIGRATION ******************************************************************************** Migration started at 4/3/14 11:26 PM Pacific Standard Time Statistics ------------ Total Projects Migrated: 2 ******************************************************************************** PROJECT: PUBLIC_PROJECT Object Types Migrated Rejected Skipped -------------------------- --------- --------- -------- LOCATION: 1 0 1 ******************************************************************************** PROJECT: PRO_MIGRATION Object Types Migrated Rejected Skipped -------------------------- --------- --------- -------- TABLE: 5 0 0 MAPPING_MODULE: 2 0 0 VIEW: 1 0 0 MODULE: 2 0 0 MAPPING: 2 1 0 MODULE_FOR_LOGICALSCHEMA: 2 0 0 Details -------- ******************************************************************************** PROJECT: PUBLIC_PROJECT Object Types Status --------------------------- ------- LOCATION MIGRATION_SRC_MOD_LOC SUCCESS OPERATOR_MIGRATION_LOC [INFO][Migration][MU-1010]OPERATOR_MIGRATION_LOC is skipped because it already exists. ******************************************************************************** PROJECT: PRO_MIGRATION Object Types Status --------------------------- ------- TABLE DEPT SUCCESS EMP SUCCESS TGT_EMP SUCCESS TGT_EMP_CONSTRAINTS SUCCESS EMPLOYEES SUCCESS MAPPING_MODULE TEST_MOD SUCCESS TEST_SRC_MOD SUCCESS VIEW TGT_V_EMP SUCCESS MODULE TEST_MOD SUCCESS TEST_SRC_MOD SUCCESS MAPPING BASIC_JOIN SUCCESS TLO_MAP SUCCESS UNSUPPORT_MAP [INFO][Migration][MU-5001]Migration of mapping with mapping operator MATCHMERGE:MATCHMERGE is not supported. MODULE_FOR_LOGICALSCHEMA TEST_MOD SUCCESS TEST_SRC_MOD SUCCESS Migration ended at 4/3/14 11:27 PM Pacific Standard Time Total migration time (hh:mm:ss): 00:00:56
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.