Thursday 31 March 2016

Oracle Incremental Update(merge) in ODI 11g.

When we want to run an incremental load in ODI 11g, which is the best IKM that will improve our performance.
  • IKM Oracle Incremental Update (Merge).
IKM Oracle Incremental Update(Merge) uses mainly the following logic for incrementally load the data.

  • First load data to the C$ table from source.
  • Then minus C$ table from target table(In this step updated records and inserted records are selected). 
  • Then load the updated and newly inserted records to I$ table.
  • In the last step it does a merge operation with I$ and Target table.
So go for oracle incremental update(Merge) for optimizing your Incremental update.




Tuesday 22 March 2016

Timezone Issue while scheduling Scenarios using agent in ODI 11g.


Issue:

I scheduled my scenario to a particular date and time and when i checked it's scheduled time from ODI Agent it's scheduling is stamped for 12:30 hours ahead of the current time.

Cause:

ODI retrieves the start date of a Session with a Java function executed on the machine that is running the Agent/Scenario. This Java function, based on the local Time Zone information, is "System.currentTimeMillis", and this is recorded in the Agent log file.

The datetime shown in Operator however, is computed from the timestamp of the Repository server, not the client/Agent server.

Solution:

As our The ODI client machine and the Repository database machine have in different time zone we have to change the time zone of our agent to the same time zone that our Repository database machine resides.


For that include the -Duser.timezone Java variable in the odiparams.bat/.sh.


odiparams.bat location: D:\MW_HOME\Oracle_ODI\oracledi\agent\bin

Depending on your location add the timezone.

Some Examples:

set ODI_ADDITIONAL_JAVA_OPTIONS="-Duser.timezone=Europe/Paris"
set ODI_ADDITIONAL_JAVA_OPTIONS="-Duser.timezone=GMT+2:00"



I changed the ODI_ADDITIONAL_JAVA_OPTION to "-Duser.timezone= GMT+5:30"

After updating this restart the ODI agent and schedule your Scenario.

It will execute fine.

Courtesy: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=272099324577098&id=424236.1&displayIndex=2&_afrWindowMode=0&_adf.ctrl-state=rqriev3hs_4#CAUSE