ODI on Exadata

Moving Oracle Data Integrator to Exadata can provide a big boost in reliability and performance to your data integration processes. There are quite a few different ways that you can configure your ODI environment. Each configuration has its own pros and cons for each environment. You will have to play around with different configurations to find the right one for your environment and that meets your requirements for high availability, performance, security, organizational best practices and so on.

Below is a sample configuration of ODI on Exadata. In this configuration, the WebLogic ODI Agent is used for high availability and load balancing of ODI jobs. Because I want the actual jobs to run on the same server as the database instance I have put the ODI Standalone Agents on the DBMS servers in the Exadata rack. The is one ODI Standalone Agent on each node of the RAC cluster. The WebLogic ODI agent is configured to load balance between each ODI Standalone Agent in the cluster. The WL ODI Agent is also configured to not run any jobs itself. I don't want any data flowing across the network from the Exadata DBMS servers to the WL ODI Agent on the WebLogic server. My goal is to keep everything local to the Exadata rack.

ODI- Installation Guide-12c

Table of Contents

1        ODI Installation. 3

2        Create the ODI Repositories 11

ODI Installation:-

Oracle Data Integrator 12c is finally available. Now the hard part begins - learning how to use it. Some things to consider as you go through the installation of ODI 12c are:

1. Will your ODI 11g objects work in ODI 12c?
2. Should you upgrade your existing ODI 11g environment or install a brand new environment?
3. What is the best way to learn about the new features of ODI 12c?
4. And you probably have a hundred other questions that need to be answered.

In this tutorial, my goal is to install ODI Studio 12c on my laptop and configure the repositories in an Oracle Database. 

Step 1: Download ODI 12c

Download the installation media for ODI 12c from Oracle.

Step 3: Design a Topology

ODI 12c consists of several components - ODI Studio, WebLogic (Agent, Console), Standalone Agent. In a production environment, these components will be installed on different computers. For my tutorial, I plan to install ODI Studio on the same computer as the Oracle Database. If time allows then I will also install a standalone agent on the same computer.

Step 4: Install Java SDK 7 

You need to install the JDK before you can install ODI 12c. Why? The ODI 12c is a jar file that requires the SDK to run. Install Java SDK 7 on each computer where you will need to install an ODI component. This example will install everything on a single computer. 

Step 5: Configure a Database

A database serves two purposes. The first purpose is to hold the ODI repositories that ODI uses to store metadata (aka configuration information and source code). The second is to hold data used for data integration flows (source and target).

There are two types of repositories that ODI uses - a master repository and a work repository. The space requirement for a master repository is 200 MB. The space requirement for a work repository is 400 MB. Make sure that you have enough hard disk space to hold the repositories you need. Consider one master repository, a development work repository, a test work repository, a hot fix work repository and a production work repository. This configuration supports a basic SDLC workflow.

You should be safe with Oracle Database 11g or Oracle Database 12c. For any other database you will need to check the Fusion Middleware 12c certification matrix to see if it is compatible with Fusion Middleware 12c.

Once your database is ready, make note of the credentials for the sys user or any sysdba account. You will need to have access to the sys schema when you create the ODI repositories.

Step 6: Configure ODI Repositories

ODI repositories reside in the database that you configured in the previous step. There are two methods of creating repositories - using the Oracle Repository Creation Utility (RCU) or using ODI Studio. Both methods have the same result.

I use ODI Studio to create/populate the repositories after the installation of ODI 12c is complete.