Too many child cursors when the engine calls UPDATE PPROCINSTANCE.

(Doc ID 1163053.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version: 10.3.1 to 10.3.1 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 3-Apr-2012***


You see a problem where Bind variables have multiple types used within oracle cursors. You may also see a great deal of child cursors for the UPDATE PPROCINSTANCE statement because of this. For example:

Running the following select: - where '0fvtcfw2ahwxb' is the sql_id of
the update statement in question

select distinct name, datatype_string, max_length
from v$sql_bind_capture
where sql_id = '0fvtcfw2ahwxb'
order by 1, 2;

You would see a result and observe the duplicates such as:

:V0 NCHAR(128) 128
:V0 NCHAR(32) 32
: : : :
:V14 NCHAR(128) 128
:V14 NCHAR(32) 32
: : : :
:V23 BLOB 4000
:V23 RAW(4000) 4000
: : : :
:V25 NCHAR(128) 128
:V25 NCHAR(2000) 2000
:V25 NCHAR(32) 32
:V26 CHAR(32) 32
:V26 NCHAR(128) 128
:V26 NCHAR(32) 32


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