This chapter lists migration requirements and describes how to create the configuration file used for migration.
The following topics are addressed here:
Migration is supported on Linux and Windows 64-bit x86 systems only. Before migrating, ensure that the following requirements are met:
OWB 11.2.0.4 installed (OWB 11.2.0.4 plus patch number 17830453)
ODI 12.1.2.0.0 installed with both of the following:
Patch number 17053768
ODI 12.1.2.0.1 bundle patch (patch number 17836908)
OWB workspace exists
ODI repositories exist
ODI_HOME
and JAVA_HOME
environment variables set. The ODI_HOME
variable should be set to the ODI installation directory, such as /home/oracle/Middleware
. The JAVA_HOME
variable should be set to the JDK installation directory, such as /java/jdk1.7.0_25/
.
Migration utility configuration file created
Also ensure that you have the following information:
ODI master repository password
ODI user password
OWB workspace owner password
Full path to the migration utility configuration file and the file name
Note:
Download the required patches from My Oracle Support (https://support.oracle.com
). Apply the patches using the instructions in the patch readme files.
Before migrating, you must first create the configuration file used to perform the migration. The configuration file is a text-based properties file that contains connection information and other details.
The following topics are addressed here:
A template file is provided to make creation of the migration utility configuration file easier. Use this template as your starting point and edit the settings to fit your specific environment and needs.
The template file is named migration.config
and is located in the OWB_HOME/bin/admin
directory, where OWB_HOME is your OWB installation directory.
To create the migration utility configuration file:
Open the migration.config
file in a text editor.
Edit the settings to fit your specific environment and needs. For more information about each parameter, see Configuration File Parameters.
Save the file. The file can be named whatever you like and saved to the location of your choice.
Make note of the file name and its path, because you will need this information when you run the migration utility.
Table 2-1 lists the parameters in the migration utility configuration file.
Table 2-1 Migration Utility Configuration File Parameters
Parameter | Mandatory | Description |
---|---|---|
|
Yes |
User name for the ODI master repository connection. |
|
Yes |
JDBC URL used to connect to the ODI master repository. This URL must be quoted if it contains one of the following characters:
The default value is |
|
Yes |
JDBC driver used to connect to the ODI master repository. The default value is |
|
Yes |
Supervisor user name for ODI. The default value is |
|
Yes |
User name used to connect to the ODI work repository. The default value is |
|
Yes |
OWB workspace owner. |
|
Yes |
URL used to connect to the OWB workspace. The default value is |
|
Yes |
Name of the OWB workspace to connect to, specified in one of the following formats:
The migration utility can be used to migrate just one workspace at a time. Edit this parameter (and others as necessary) and run the migration utility for each workspace that you want to migrate. If the workspace owner owns just one workspace, you do not need to specify this parameter. If the workspace owner owns multiple workspaces and no value is specified for this parameter, an error is returned. If a workspace has the same name as the workspace owner, the workspace is migrated. If the specified workspace does not exist, the connection fails. |
|
No |
Full path to the migration utility log file, which is generated when you run the migration utility. The migration utility exclusion report is also generated, and uses the same prefix as the log file, with a This parameter is used to specify the name and location for both the log file and the report file. If no path is specified, the log and report files are generated in the same directory from which the migration utility was executed, for example, OWB_HOME For more information about these files, see Reviewing Log and Report Files. |
|
No |
Content to be included in the migration utility exclusion report. Options are:
The default value is |
|
No |
Migration mode. Options are:
The default value is For more information about using the |
|
No |
Controls whether dependent objects are migrated with the objects selected for migration. The default value is Recursive dependency is supported when Mapping |
|
No |
Indicates whether to continue the migration process or stop when an error occurs. When set to The default value is |
|
No |
Indicates whether to split the join operator to binary join when the property The default value is |
|
No |
Determines whether mappings that contain unbound operators (excluding Code Template mappings) are migrated. Unbound operators include external table, table, view, materialized view, lookup, and pluggable mapping. When set to For an unbound pluggable mapping operator, an ODI reusable mapping is created in an ODI folder named The default value is |
|
No |
Specifies the OWB objects to be migrated. The default value is the wild card asterisk ( For more information about migrating specific objects, see Migrating Specific Objects in an OWB Workspace. |
|
No |
Indicates the number of mappings to be processed or migrated at a time. Use this parameter to avoid out of memory issues if the OWB workspace has a very large number of mappings. The default value is |
This example shows values for a sample migration utility configuration file.
Example 2-1 Sample Migration Utility Configuration File
ODI_MASTER_USER=ODIREP ODI_MASTER_URL=jdbc:oracle:thin:@localhost:1521:machine ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver ODI_USERNAME=SUPERVISOR ODI_WORK_REPOSITORY_NAME=WORK0 OWB_WORKSPACE_OWNER=rep_0 OWB_URL=localhost:1521:machine.oracle.com OWB_WORKSPACE_NAME=REP_0_WS_0 MIGRATION_LOG_FILE=/tmp/migration.log MIGRATION_REPORT_INCLUDE=ALL MIGRATION_MODE=RUN MIGRATE_DEPENDENCIES=TRUE STOP_ON_ERROR=FALSE SPLIT_JOIN_FOR_ANSI_SYNTAX=TRUE MIGRATE_UNBOUND_OPERATOR=TRUE MIGRATION_OBJECTS=PROJECT.MY_PROJECT FLUSH_BATCH_SIZE=50