My Oracle Support Banner

The Database Sessions Are Not Closed or Not Managed Correctly when Running ODI 10g Jobs (Doc ID 472767.1)

Last updated on JUNE 16, 2022

Applies to:

Oracle Data Integrator - Version 10.1.3.2.0 to 10.1.3.6.0_01
Information in this document applies to any platform.



Symptoms

Case 1 OdiWaitForLogData Does Not Close Connections To the Source

An ODI Package has an OdiWaitForLogData step that waits for changed data in an ODI Model journalized with JKM Oracle 9i Consistent (Logminer) or JKM Oracle 10g Consistent (Logminer).

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!

In this Document
Symptoms
 Case 1 OdiWaitForLogData Does Not Close Connections To the Source

 Case 2 ODI Event Based Tools Does Not Close Connection To The Repositories

 Case 3 Journal Package Leaves Database connections to ODI Master Repository In Inactive Status.

 Case 4 Inconsistently Repository Connections Are Abruptly Closed Causing "closed connection" Exception While Updating A Session Task.
Changes
Cause
Solution
 ODI Version Fixed for Each Case:
 Our Recommendations:
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.