2 Oracle Data Integrator 11g for 10g Users

The following sections introduce some key concepts of the Oracle Data Integrator environment for 10g Release 3 (10.1.3.x) users:

2.1 Components of the Oracle Data Integrator Installation

Oracle Data Integrator 10g Release 3 (10.1.3) provided the following components:

  • Oracle Data Integrator

  • Oracle Data Profiling

  • Oracle Data Quality for Data Integrator

Oracle Data Integrator 11g provides updates to all of these components, but not in a single installation. In Oracle Data Integrator 11g, Oracle Data Profiling and Oracle Data Quality components are packaged and installed separately, but they still provide the same resources and services.

Specifically, Oracle Data Integrator 11g provides the following installation options:

  • Oracle Data Integrator Client Components

    • ODI Studio

      This component replaces the Oracle Data Integrator 10g graphical modules (Designer, Operator, Topology and Security Manager), which are all merged into a single Fusion Common Platform (FCP) user interface.

    • ODI Software Development Kit (SDK)

      This new component is a Java API for performing run-time and design-time operations.

  • Oracle Data Integrator Standalone Agent

    • Standalone Agent

      This component corresponds to the ODI 10g run-time agent. It runs on a Java Machine.

  • Oracle Data Integrator Java EE Components

    • Java EE Agent

      This component is a Java EE version of the run-time agent, for deployment within an application server.

    • Oracle Data Integrator Console

      This component replaces the ODI 10g Repository Explorer (Metadata Navigator) and Lightweight Designer components. It also installs the Oracle Enterprise Manager Plug-in for ODI.

    • Public Web Service

      This component is a web service that allows context and scenario listing. Other run-time web service operations (executing scenarios and sessions) are available on the Standalone and Java EE agent components.

      For more information, see "Working with Web Services in Oracle Data Integrator" in Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator

2.2 Important Changes for Oracle Data Integrator 10g Users

Although the overall product architecture has not changed, 10g users should be aware the following changes to plan for their updates.

2.2.1 Upgrade Considerations

Before you begin the upgrade process, consider the following:

  • Upgrading to ODI 11gR1 is performed using the Upgrade Assistant. It is not possible to upgrade repositories from the Oracle Data Integrator user interface.

  • The Upgrade Assistant does not support the upgrade of externally authenticated repositories. If your repository was authenticated externally, the authentication has to be switched from external to internal before upgrade. After upgrade the authentication can be switched back to external.

    For more information see "Switching the Authentication Mode" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

  • The database that contains the Oracle Data Integrator repositories must be supported by Oracle Fusion Middleware 11g. For the latest list of supported databases, see:


  • For instructions on verifying that your database meets the requirements of Oracle Fusion Middleware 11g, see "Upgrading and Preparing Your Databases" in the Oracle Fusion Middleware Upgrade Planning Guide. Oracle recommends that you refer to your database-specific upgrade documentation for additional information.

  • During the upgrade process Work Repositories must reside on the same database server as their Master Repository. The repositories can be manually redistributed after the upgrade.

    For more information on cloning repositories, see Cloning Existing Master and Work Repositories.

  • Beginning with ODI you can export a single ODI project from 10g and import into an ODI repository using the ODI Smart Export and Import feature.

    For more information on upgrading your ODI projects through export/import, see "Exporting/Importing" in Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

2.2.2 Changes in the Run-Time Agent

The run-time agent is available as a standalone agent or a Java EE agent. Both of these agents are now connected to a single Work Repository and act as schedulers. The agents connect systematically to the Master Repository at startup.

For these agents to start properly:

  • For the standalone agent the connection configuration (using the odiparams file) must be performed. Running the agent.bat starts a scheduler agent.

  • For the Java EE agent, the connection configuration is made in the agent template, and the agent connects to the repositories using JDBC data sources defined in the application server.

The agent now uses the HTTP protocol rather than its own protocol. In addition, the standalone agent is no longer started as a service using the Wrapper tool. To configure the agent for high availability, Oracle Process Manager and Notification Server (OPMN) is used and can be configured using some built-in scripts.

2.2.3 Changes in the Logging Files for Command Line Tools and the Standalone Agent

The standalone agent and command line tools will create log files with static names. This change affects Oracle Data Integrator 10g users who are using the -NAME parameter in command line tools to create dynamic log files.

For example:

  • The startscen.sh or startscen.bat tool will always create the scartscen.log file.

  • The standalone agent log messages are always written to odiagent.log.

2.2.4 Other Changes

Oracle Data Integrator 10g users should also be aware of the following changes in Oracle Data Integrator 11g:

  • With ODI version, the names of the ODI binding variables must be uppercase. If you are using lower or mixed case variables, you can use double quotes as a workaround (SELECT 'odi 11' AS "txt" FROM dual ). Note, however, that you may have to redevelop your code as a result of this change.

  • The getObjectName method now automatically truncates object names to the maximum object length allowed for the technology. Prior to ODI 11g, object names were not truncated. To prevent object names from truncating and to reproduce the 10g behavior you must add the server a property OBJECT_NAME_LENGTH_CHECK_OLD and set its value to "true". This property can be added in the Properties tab of the data server.

    NOTE: If your object names continue to truncate after upgrading to 11g, consider changing the code and only use the method above as a temporary workaround.

  • The ODI login files snps_login_security.xml and snps_login_work.xml are now merged into a single file called snps_login_work.xml. The snps_login_work.xml file is located in the %APPDATA%/odi/oracledi directory for Windows operating systems and USER_HOME/.odi/oracledi on Unix operating systems.

  • With ODI version, ODI ships with a bundled HSQL database version 2.0. Previous versions of ODI shipped with a HSQL database version 1.7.3. The HSQL database is used for the memory engine, the demonstration environment, and the memory storage for the XML and LDAP drivers. You may have your own HSQL 1.7.3 database instances connected from ODI. If so, once you upgrade the HSQL database to version 2.0, ODI can no longer connect to HSQL database version 1.7.3 databases. You must upgrade your HSQL database version 1.7.3 to version 2.0 before upgrading to ODI

    For more information on upgrading databases, see the HSQL database documentation at http://www.hsqldb.org/doc/2.0/guide/deployment-chapt.html#deployment_upgrade-sect

    See also the HSQL database Changelog at http://www.hsqldb.org/web/changelog.html

  • Knowledge modules and technologies are available in a directory called /xml-reference.

  • The demonstration environment is delivered separately from the ODI Installer on the ODI Companion CD.

  • Host and Modules are removed from the Security. This entire feature is deprecated.

  • The following scripts are deprecated: Jython, agentscheduler, agentweb, designer, topology, security, and operator.

  • Repository creation for Oracle, DB2 and Microsoft SQL Server can be performed using Repository Creation Utility (RCU). This tool allows creation and management of schemas for multiple Oracle products.

  • Repository creation and import is possible from the ODI Studio. The mimport and mupgrade scripts are deprecated.

  • ODI is now shipped with DataDirect JDBC drivers to connect to technologies such as MSSQL and DB2. Note that the other ODI drivers can still be used to connect to the database. The additional drivers for the Standalone Agent are in the /drivers directory, but the drivers for the ODI Studio are in the DOMAIN_HOME.

    For more information, see "Add Additional Drivers and Open Tools" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.


For a detailed list of the new features in Oracle Data Integrator 11gR1, see "What's New In Oracle Data Integrator?" in Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

2.3 Upgrading From Sunopsis to Oracle Data Integrator 10g

If you are currently using a Sunopsis or later environment and want to upgrade to Oracle Data Integrator 11g, you must first upgrade your environment to Oracle Data Integrator 10g, the follow the instructions in this guide to upgrade from 10g to 11g.

To upgrade from Sunopsis to Oracle Data Integrator 10g, follow the directions provided in "Upgrading Sunopsis to Oracle Data Integrator" in Oracle Data Integrator Installation Guide for 10g Release 1 (10.13.), available at the following URL: