The Upgrade Assistant automates many of the upgrade tasks, but there are cases where you must manually modify the configuration settings after running the Upgrade Assistant. Review Table 4-1 to determine if you need to perform any additional upgrade procedures:
|If you...||Then do this to finalize the upgrade...|
Selected the Upgrade Oracle Data Integration Schemas option to upgrade the master and Work Repository schemas
Update the connection parameters to the Work Repositories as defined in the ODI topology.
Chose not to Update Topology and Security Metadata during the upgrade
Manually upgrade the ODI 10g metadata so that it can be used with ODI 11g.
Updated the Topology and Security Metadata using Upgrade Assistant
Manually re-apply modifications made in Oracle Data Integrator 10g to the new ODI 11g built-in metadata objects. (The automated upgrade process erases any changes that were made to the ODI 10g objects.)
Created Open Tools in ODI 10g, and you want to continue to use them in ODI 11g
Add Open Tools to the classpath and then add as an Open Tool in ODI Studio.
Chose not to Replace KMs with Mandatory Updates during the upgrade
Manually upgrade the ODI 10g KMs so that they can be used with ODI 11g.
You must update the connection parameters to the upgraded Work Repositories as defined in the ODI topology.
To update the Work Repository Connection Parameters:
Launch the Oracle Data Integrator Console and connect to the Master Repository using Oracle Data Integrator Studio.
Expand the Work Repositories node in the Repositories accordion of the Topology Navigator.
Edit each Work Repository that is now hosted on a new server and edit its connection parameters by clicking the Connection button in the Work Repository editor toolbar.
Modify the connection parameters, User and Password, on the Definition tab. Modify the JDBC Driver and URL on the JDBC tab. Save the changes.
Validate your changes by creating and testing Repository Connections for these Work Repositories in Studio.
odiparams.sh (on UNIX operating systems) or
odiparams.bat (on Windows operating systems) script to reflect the new connection parameters to your Master Repository. This script is located in the
/oracledi/agent/bin directory, where
ODI_HOME is the Oracle Data Integrator installation directory.
odiparams script with a text editor to set the configuration parameters as shown in the following example. (Note that the values are provided for example only; be sure to enter your own parameters):
ODI_MASTER_DRIVER=oracle.jdbc.driver.OracleDriver ODI_MASTER_URL=jdbc:oracle:thin:@ours:1521:ORA9 ODI_MASTER_USER=ODI_11G ODI_MASTER_ENCODED_PASS=gxfpqkz074jeaCpL4XSEFzxoj8E0p ODI_SECU_WORK_REP=WORKREP ODI_SUPERVISOR=SUPERVISOR ODI_SUPERVISOR_ENCODED_PASS=fJya.vR5kvNcu9TtV,jVZEt
For each ODI Agent configuration update the
odiparams.sh script as indicated in step 5.
By default, the Upgrade Assistant enables you to import the same ODI 10g technologies, data types, data type conversions, and languages when upgrading to ODI 11g. If, however, you have selected not to have them upgraded automatically by the Upgrade Assistant, you should upgrade them manually to take advantage of the ODI 11g features. The following ODI 10g metadata should be manually updated using Oracle Data Integrator import features:
Data types and data type conversions
Oracle Data Integrator 11g Topology and Repository Metadata exports are located in the
ODI_HOME/oracledi/xml-reference directory. These objects must be imported in 'Synonym Insert-Update' mode.
For more information on importing and exporting ODI metadata, see "Exporting/Importing" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.
The ODI 11g upgrade process will automatically upgrade your ODI 10g topology and security metadata objects. However, if you modified the topology and security objects that were provided by default with ODI 10g, such as user defined profiles or technologies, you must reapply your changes manually by editing the objects.
For information on modifying topology and security metadata, see "Introduction to the Oracle Data Integrator Topology" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.
If you created Open Tools in ODI 10g, and you want to continue to use them in ODI 11g, you must add Open Tools to the classpath and then add as an Open Tool in ODI Studio.
For more information on using ODI tools, see "Oracle Data Integrator Tools Reference" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.
By default, the Upgrade Assistant enables you to update ODI 10g Knowledge Modules (KMs) when upgrading to ODI 11g. Most ODI 10g KMs can be used with ODI 11g, so the update is not mandatory for all KMs.
Only the KMs shipped with ODI 11g or upgraded to their 11g version using Upgrade Assistant are supported in this release.
Specifically the following KMs must be manually updated using KM Import/Replace before using ODI 11g:
LKM File to Oracle (EXTERNAL TABLE)
LKM File to Netezza (EXTERNAL TABLE)
LKM File to Oracle (SQLLDR)
LKM File to DB2 UDB (LOAD)
LKM SQL to Teradata (TTU)
IKM SQL to Teradata (TTU)
LKM File to Teradata (TTU)
IKM File to Teradata (TTU)
IKM Teradata to File (TTU)
LKM File to Sybase IQ (LOAD TABLE)
These Knowledge Modules listed above must be updated because they use calls to the
odiRef.getTableList APIs to request field or row separators for a file datastore. In ODI 10g, the returned values were inverted when requesting hexadecimal (
XFILE_SEP_FIELD, XFILE_SEP_ROW) and ASCII (
FILE_SEP_FIELD, FILE_SEP_ROW) separators. To address this issue, the ODI 10g KMs were implemented to work around this issue.
OdiRef APIs return the correct values; therefore, the KMs have been modified to request the correct hexadecimal or ASCII separators.
odiRef.getTargetTable("FILE_SEP_FIELD") was replaced with
odiRef.getTargetTable("XFILE_SEP_FIELD") was replaced with
odiRef.getTargetTable("XFILE_SEP_ROW") was replaced with
odiRef.getTargetTable("FILE_SEP_ROW") was replaced with
If you customized KMs using these methods, you must make the appropriate changes to the API calls.
Also note that the following KMs are no longer available:
LKM File to SAS
LKM SAS to SQL
LKM File to MSSQL (BCP)