Difference between ODI 11g and ODI 12c.

Answer:- 

S.No	ODI 11g	ODI 12c
1	No Component Palette	Component Palette Added
2	No Debugger	Debugger
3	Interface for loading source to target Sub Tabs: ·         Overview ·         Quick Edit ·         Flow ·         Control	Mapping for Loading Source to Target Sub Tabs: ·         Overview ·         Logical ·         Physical
4	In interface we will have only one target datastore	Mappings we can have more than one data store (i.e., we can load more than one data store at a time)
5	OWB jobs can’t execute	OWB jobs can be executed in ODI 12c
6	To perform Incremental and Initial Load we need to create two different interfaces	To Perform Incremental and initial Load we can accomplish with single mapping (Using Deployment Specification)
7	No Wallet Password	Wallet Password is available
8	Temporary Interface	Reusable Mappings

ODI 12c Features which were not present in ODI 11g:-

1) New mappings

2) Reusable Mappings

3) Debugger

4) In-Session Parallelism

With ODI 12c, it is now possible to have the extract tasks (LKMs) running in parallel. It's actually done by default. If two sources are located in the same execution unit on the physical tab, they will run in parallel. If you want a sequential execution, you can drag and drop one of your units onto a blank area. A new execution unit will be created and ODI will choose in which order it will be loaded.

5) Parallel Target Table Load

With ODI 11g, if two interfaces loading data in the same datastore are executed at the same time or if the same interface is executed twice, you can face some problem. For instance a session might delete a worktable in which the other session wants to insert data.

This now belongs to the past. With 12c, a new "Use Unique Temporary Object Names" checkbox appears in the Physical tab of your mapping. If you select it, the worktables for every session will have a unique name. You are now sure that another session won't delete it or insert other data.

6) Datastore Change Notification

7) Wallet

8) Release Management :- Using Version control system(VCS)

Managing ODI Releases

You can manage ODI releases using deployment archives. A deployment archive is an archived file (zip file) that contains a set of ODI objects in the form of XML files and metadata. You can create deployment archives that can be used to either initialize an ODI repository or to update a deployed ODI repository.

If ODI is integrated with a VCS, deployment archives can be created from the VCS labels. If ODI is not integrated with a VCS, deployment archives can be created from the current ODI repository.

See also, Types of Deployment Archives.

Types of Deployment Archives

You can create the following types of deployment archives in ODI:

• Initial Deployment Archives

  Initial deployment archives contain all the ODI objects that are necessary to initialize an ODI repository. You can create an initial deployment archive and use it to deploy an ODI repository in an environment where the ODI objects are not modified, for example, in a testing or a production environment.

• Patch Deployment Archives

  Patch deployment archives contain only the ODI objects that need to be updated in an ODI repository. You can create a patch deployment archive and use it to update an ODI repository that is already deployed. For example, when you update any ODI objects in a development environment, the updates can be applied in a testing or a production environment using a patch deployment archive.