My Oracle Support Banner

ODI Integration Interfaces Lock Objects on AS400 Systems (Doc ID 424222.1)

Last updated on DECEMBER 19, 2019

Applies to:

Oracle Data Integrator - Version 4.1.01.05 and later
Generic (Platform Independent)

Symptoms

When launching sequentially programmed Integration Interfaces with Oracle Data Integrator (ODI) on AS400 / iSeries systems in a multi-application environment, it appears that these programs are not releasing their locks and, as a result, other concurrent applications are denied access.

This problem is persistant even after having applied Sunopsis recommendations described in <Note.423988.1>.

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
Cause
Solution
 What Is a Pseudo Closed Cursor?
 When Is a Cursor Pseudo Closed?
 How Many Pseudo Closed Cursors Are Cached? Can This Be controlled?
 What Happens When the Limit Is Reached?
 What Are the Impacts of Pseudo Closed Cursors?
 How Do I Force Pseudo Closed Cursors to Hard Close?
 How Can I Track Pseudo Closed Cursor Reuse?
 What are Common Reasons for Not Reusing a Pseudo Closed Cursor?
References

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