-none- 2005-03-15 - By -not available-
==================================================================
Oracle9i Database Server
Patch Set Notes
Release 2 Patch Set 4 Version 9.2.0.5.0 for 32-Bit Windows
March 2004
PL/SQL Cursor Caching
Prior to release of the 9.2.0.5.0 patch set, the maximum number of
cursors that could be cached for fast lookup by PL/SQL was bounded by
the value of the init.ora parameter open_cursors. If you currently
have open_cursors set to a high value (for example, greater than
1000), it is likely that this is causing large numbers of PL/SQL
cursors to be cached in the shared pool. This could lead to issues
with memory management, frequent reloading of library cache objects
and ORA-04031 (See ORA-04031.ora-code.com) errors.
Patch set 9.2.0.5.0 alleviates the issue by changing the init.ora
parameter which determines the upper bound for PL/SQL cursor caching
from open_cursors to session_cached_cursors.
Most users will not need to modify the value of either of these
parameters. If you already have session_cached_cursors set to a value
greater than the open_cursors parameter, then this change will have no
performance impact upon your system.
However, if you have session_cached_cursors set to zero, or set at a
value significantly lower than the open_cursors parameter, and you are
concerned that PL/SQL cursors need to be cached for optimal
performance, then you should ensure that the session_cached_cursors
parameter is increased appropriately.
This issue is bug number 3150705.
==================================================================
|
|
