Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« Job Scheduler | Main | HR Leaders at 'cross roads' again, but third time's the charm ! »

ODI 12C Miscellaneous concepts:

In this blog I want to share the concepts related on the below topics


Export and import in ODI normally export only specific component and child components. Components under the selected mappings like temporary interfaces, reusable mappings and scenarios etc.

The exported components saved in the XML file format. Usually this process is preferred when there is a very minor change in the particular object and all environments are in sync.


Smart process:

Usual best practice of export and import is smart import/export process.Just drag the components to the wizard to be exported , it will automatically pick all the designer ,topology and dependencies used by  information related to corresponding component. Import action is similar vice versa process . Response file will track the log of import process.



Solutions in ODI:

Solutions are used to group the scenarios which were created for mappings, packages, procedures etc. and then we can synchronize the changes to the particular group and easily export and import to the respective environments. This would be helpful if a project contains more number of scenarios its difficult to find the changes and manually doing the migration process. So solutions are useful in grouping the required objects in the migration process. Mainly it was used in production support



Deployment in ODI:

Under every mapping in physical tab we can create new deployment option for the same mapping. Like changing the options in the knowledge modules or changing the type of KM's. Mostly it would be useful to run the full load or incremental load by creating new deployment and opting whichever is needed. This deployment is newly introduced in the 12c which was not present in 11g.


Commit and Isolation levels in Procedures:

Commit levels: Procedure is made up of group of tasks which are executed step by step .Each task is an SQL statement which needs to be committed. To manage the commit levels we have options like Auto commit and Transaction 0 to Transaction 9. Auto commit simply commits particular task in procedure. Transactions 0 to 9 are used to group the tasks need to commit at a time sequentially. This way we can manage the commit levels in ODI.

Isolation Levels: These levels are classified into four Committed, Uncommitted (Dirty), Repeatable, Serialazable.

Committed: The Tasks in the procedure will read the only committed data from the source.

Uncommitted (Dirty): The Tasks in the Procedure will read uncommitted data from the source (oracle doesn't support)

Repeatable: The Tasks in the Procedure while reading the huge amount of data it will lock the rows not to update at the point of time to avoid inconsistency.

Serialazable: The Tasks in the Procedure while reading the huge amount of data it will lock the respective table not to update at the point of time to avoid inconsistency.


Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles