My Oracle Support Banner

Incorrect Handling Of COMMIT for Transaction with ODI IKM Oracle Incremental Update (Doc ID 2927090.1)

Last updated on AUGUST 06, 2024

Applies to:

Oracle Data Integrator - Version 12.2.1.4.0 and later
Oracle Data Integrator on Marketplace - Version 12.2.1.4.200123 and later
Information in this document applies to any platform.

Symptoms

When executing an Oracle Data Integrator (ODI) mapping using IKM Oracle Incremental Update (build 49), data is committed even after commit is disabled. It is expected that the commit should not occur.

The issue can be reproduced at will with the following steps:

  1. Open Studio connection to schema with a TABLE_SOURCE populated and TABLE_TARGET created and not populated.
  2. Then open the KM settings of the mapping where the IKM is "IKM Oracle Incremental Update.GLOBAL"
    1. Insert True use default
    2. Update False
    3. Commit False
    4. Create_flow_index True use default
    5. Constraints None use default
    6. Indexes None use default
  3. After execution of mapping – operator log (no commit step is visible).
  4. Perform Select * from TABLE_TARGET. Observe data shown in the query result.

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.