My Oracle Support Banner

ODI 12c Mapping Execution Performance Caused by Gaps Between the Session Tasks and/or Steps (Doc ID 2857308.1)

Last updated on AUGUST 07, 2024

Applies to:

Oracle Data Integrator - Version 12.2.1.4.211011 to 12.2.1.4.220426 [Release 12c]
Oracle Data Integrator on Marketplace - Version 12.2.1.4.211011 to 12.2.1.4.220426
Information in this document applies to any platform.

Symptoms

An Oracle Data Integrator (ODI) Package is designed to implement a loop on a Mapping which reads a source text file, and loads data into a target Oracle table.

For each of the loop iterations, an OdiStartScen command is implemented to start a new / dedicated child Session and execute the Mapping.

The following two issues are observed when executing the flow:

  1. The child Session completes, however the duration of OdiStartScen task in the parent Session occasionally exceeds the child Session execution by 30 seconds or more...
      
  2. In the child Session which executes the Mappings, a few seconds occasionally add between the completion of a Task / Step, and the start of next Task / Step...

EXPECTED BEHAVIOR:

  1. The time reported in the parent Session for completion of the OdiStartScen task should not exceed the duration of corresponding child Session by more than 1 or 2 seconds...
       
  2. The time reported for starting a Session Task / Step should not exceed by more than 1 or 2 seconds the completion of Session previous Task / Step...

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.