DQ Jobs Are Not Releasing Database Cursors

(Doc ID 2261308.1)

Last updated on MAY 02, 2017

Applies to:

Siebel Public Sector Call Center - Version 8.2.2.4.11 [IP2013] to 16.10 [IP2016] [Release V8 to V16]
Information in this document applies to any platform.

Symptoms

Siebel is integrated with OEDQ 12c. While running Data Quality jobs, jobs are failing with error "ORA-01000: maximum open cursors exceeded"

After re-start of DQ component, some jobs are successful and failing with error ""ORA-01000: maximum open cursors exceeded"

Upon analyzing the issue, once DQ job is completed, it is not releasing the cursors.

Steps

---------

1. Start siebel servers

2. Validate the cursors at Database level

select a.USERNAME, a.PROCESS, a.SID, a.SERIAL#, count(*) "open_cursors" from v$session a, v$open_cursor c where a.PROGRAM like 'sieb%' and c.SID=a.SID group by a.USERNAME,a.PROGRAM,a.PROCESS, a.SID,a.SERIAL#;

3. Start DQ job

4. Once completed, check for cursors at DB level

select a.USERNAME, a.PROCESS, a.SID, a.SERIAL#, count(*) "open_cursors" from v$session a, v$open_cursor c where a.PROGRAM like 'sieb%' and c.SID=a.SID group by a.USERNAME,a.PROGRAM,a.PROCESS, a.SID,a.SERIAL#;

5. Cursors for DQ component PID are increasing, it is not releasing cursors after job completion

 

Cause

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 hundreds of Community platforms