Inconsistent Execution Order Of ODI Scenario Session Steps Leading To Various Issues

(Doc ID 1924565.1)

Last updated on JUNE 28, 2016

Applies to:

Oracle Data Integrator - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Following intermittent behavior could be observed under stress condition when an Oracle Data Integrator (ODI) parent session executes many child scenarios in synchronous mode:

  1. Unexpected repetitions of the same Session step.

    For example:
      
    1. A Variable refresh Package step is successfully executed, and then re-executed spontaneously.
        
    2. A Procedure Package step fails, and is unexpectedly re-executed 5 minutes later after the initial/unsuccessful attempt.

    See [1] in the screen copy below.

  2. The order of session steps is incorrect.

    This is not just a *display* issue, but:

    1. The values in the EXECUTION_ORDER column of SNP_STEP_LOG Repository table do effectively correspond to the order of steps shown in ODI Operator, but the STEP_BEG and STEP_END values are incorrect...
        
    2. Duplicate SNP_STEP_LOG.EXECUTION_ORDER values found for a same Session...

    See [2] in the screen copy below.

  3. The Session start time is posterior to the time shown for the execution of some of its steps.

    In fact, almost all the steps appear to have been executed prior to the Session start time...

    See [3] in the screen copy below.


       
  4. The "No. of failed child sessions" shown in ODI Operator for the parent Session is incorrect.

    When manually counting the number of child Sessions - running, successful or failed (in ODI Operator, or from the Repository tables directly), this doesn't match the "No. of failed child sessions" field displayed in the parent Session.

    For example, Session 1384520300 (POC_CR_IF_PRODUIT_V16_M) in the screen copy below indicates: 0 running Sessions, 401 successful child Sessions, and 178 failed child Sessions, which is incorrect. Should have shown 400 successful child Sessions, and 2 failed child Sessions instead.


        
  5. ODI Agent frequently freezes, and requires to be restarted.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms