SQL COMMAND_TYPE 170 (CALL METHOD) SUBJECT TO CHILD CURSOR CREATION ON BIND VARIABLE MISMATCHES
Database 11.2.0.1
OS Oracle Solaris on SPARC (64-bit)
We have entries in V$SQL subject to a huge variation of child cursors. These entries are for command_type 170, e.g. CALL package.procedure(:bind1, :bind2). New versions are being created based on the bind contents changing (visible in v$sql_shared_cursor). This would be expected behaviour for SQL statements of the correct type, but not procedure calls. I would expect the same cursor to be re-used each time.
I would appreciate if anyone could clarify this issue further,
Thanks,
Rou
We have entries in V$SQL subject to a huge variation of child cursors. These entries are for command_type 170, e.g. CALL package.procedure(:bind1, :bind2). New versions are being created based on the bind contents changing (visible in v$sql_shared_cursor). This would be expected behaviour for SQL statements of the correct type, but not procedure calls. I would expect the same cursor to be re-used each time.
I would appreciate if anyone could clarify this issue further,
Thanks,
Rou
0