User Interface and Terminology Changes in ODI 12c - Part 1

Oracle Data Integrator 12c introduces several new exciting and powerful features, for a complete list please look at the New Features Overview document available on OTN. While working on major enhancements we have also made several smaller tweaks to improve the overall user experience. In this blog post series I will describe some of those minor changes, highlighting some of the differences between ODI 11g and ODI 12c. This will help ODI 11g users get up and running quickly with ODI 12c.

Terminology Changes

The following table lists some of the key terminology changes that have been made in ODI 12c when compared to ODI 11g:

Changes at the Model level

Slowly Changing Dimension Behavior

Setting the Slowly Changing Dimension Behavior in ODI 11g was tedious, you had to open individually each column, go to their Description tab and finally set the SCD Behavior.

In ODI 12c you can now simply set the SCD Behavior for all your datastore’s attributes directly from its Attributes panel.

Changes at the Mapping level

Flow Control

The Flow Control settings have been reorganized; the Controls tab found in ODI 11g Interfaces has been removed.

The Check Knowledge Modules can now be selected in the Physical tab of a 12c Mapping: click on one of your target datastores and select the Check Knowledge Module panel in the Properties window.

You will find the constraints checked by Flow Control in the Logical tab of a Mapping. Click on a target datastore and select the Constraints panel in the Properties window as shown below.

The ‘Maximum Number of Errors Allowed’ and ‘Integration Errors as Percentage’ options have also moved to the Logical tab of a Mapping and are found in the Target panel of a target datastore in its Properties window.

Temporary Indexes

Temporary indexes which were previously defined in the Diagram tab of an Interface are now found in the Physical tab of a Mapping. Click on a Component such as Join or Filter in the Physical diagram to access the Temporary Indexes panel in the Properties window and set the Index Type for each of the nodes.


The Quick-Edit panel which was a separate tab in an ODI 11g Interface is replaced by the Attributes panel in a Mapping. You can access it easily: simply click on one of your Target datastores and select the Attributes panel in its Properties window as shown below.

Execution Location

ODI 12c replaces the ‘Execute on’ parameter from ODI 11g with ‘Execute on Hint’. The ‘Execute on Hint’ parameter can be set from the Properties window of all Mapping Components such as Join, Filter or Pivot as you can see below.

This ‘Execute on Hint’ parameter can also be set for specific Expressions from the Attributes panel of a datastore or when selecting a given attribute in the Mapping diagram.

Note that this parameter is a hint and as such it can be overridden by ODI if it finds a better execution location at runtime. Execution location changes made directly in the Physical tab of a Mapping, for example by moving a Filter component from one Execution Unit to another one, will take the precedence over any hints provided in the Logical tab.

Staging Location

In ODI 11g you could set the Staging Area location in the Definition tab of an Interface. In 12c you can set a hint called ‘Staging Location Hint’ in the Logical tab of a Mapping. Similarly to the ‘Execute on Hint’ we saw earlier, it can be overridden in the Physical tab.

You can also set the Staging location explicitly in the Physical tab of a Mapping, the ‘Preset Staging Location’ field is found in the Deployment Specification properties panel as shown below:

There are many more changes to talk about, stay tuned for the second blog post in this series!


Thank you very much for this post and other posts here. I am starting to plan near future move to ODI after almost 10 years with OWB. This will certainly help with the transition.


Posted by Julian on May 02, 2014 at 08:44 AM PDT #

Thanks for the feedback! There are a couple of resources that can help you with your migration:
- OTN article:
- OWB Migration Guide:


Posted by Julien on May 02, 2014 at 09:32 AM PDT #

Thank you again!

Posted by Julian on May 02, 2014 at 09:39 AM PDT #

Is there anyway using the ODI 12c SDK to upgrade 11g KM's to 12c. I am having a hard time finding good reference on this subject. I would like to use something like jenkins or hudson / and create a job that would update 11g objects to 12c w/o the hassle of creating a 11g repository and upgrading the objects via the Patch Assistant or Installer.

Any help would be much appreciated!

Posted by Luke on October 06, 2014 at 10:49 AM PDT #

Hi Luke,

Upgrade Assistant is the recommended way of upgrading your 11g repositories to 12c. Export from 11g then import into 12c using the SDK should also perform an upgrade but again the recommended approach is Upgrade Assistant.
Your 11g KMs will most likely work as-is in 12c, there are a few restrictions when you use KMs which refer to internal IDs such as RKMs.
I hope this helps.


Posted by Julien on October 06, 2014 at 04:37 PM PDT #

hello,Am Getting the error of knowledge modules. they are not shown to me when the dialog box opens up. can any one help me.

Posted by guest on September 22, 2015 at 03:33 AM PDT #


Can you add more info about what you're experiencing? In order to import KMs you need to browse to the following folder: <ODI_HOME>/odi/sdk/xml-reference. Once you've selected that directory then the KMs should be displayed. The ODI_HOME is where you installed ODI.


Posted by Julien on September 22, 2015 at 11:16 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

Learn the latest trends, use cases, product updates, and customer success examples for Oracle's data integration products-- including Oracle Data Integrator, Oracle GoldenGate and Oracle Enterprise Data Quality


« November 2015