Re-parsing for SQL associated with PL/SQL cursor variables

I have a number of utility functions in a PL/SQL package which return cursor variables - they essentially do some massaging of their arguments, then do an OPEN FOR, always with the same SQL statement (apart from bind variable values). The caller then FETCHes rows as required and finally CLOSEs the cursor variable.

From my tkprof output, it would appear that the parse count and execution count of the SQL used by the cursor variables is always the same - even though my shared pool is not full, and all other SQL from the package (i.e. that associated with CURSOR declarations) is successfully cached, and not re-parsed.

Is this to be expected? Is there something about cursor variable SQL that causes it not to be cached?

Ta for any help

Adrian Bowen Received on Tue Sep 21 1999 - 07:11:05 CDT