Deadlock Detected when Globally Committing Multiple Sequentially Executing Integration Interfaces / Mapping with ODI
(Doc ID 423988.1)
Last updated on DECEMBER 08, 2023
Applies to:
Oracle Data Integrator - Version 3.2.03.01 and laterOracle Data Integrator on Marketplace - Version 1.0.2 and later
Information in this document applies to any platform.
Symptoms
When sequentially executing multiple Oracle Data Integrator (ODI) Integration Interfaces / Mappings / Procedures, I would like to globally commit the entire job only after all Interfaces / Procedures have been correctly executed.
In order to do this, the "COMMIT" options of the Procedures and Knowledge Modules used in the Package have been set to:
- TRUE - for the final Interface / Procedure to be executed;
- FALSE - for all previous Interfaces / Procedures.
However, a deadlock situation arises at runtime.
Remarks: An Interface / Procedure IP2 needs to read data inserted into a datastore by a previous one (IP1), even if IP1 has not been committed.
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! |