Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
-none-

-none-

2005-03-15       - By -not available-
Reply:     <<     271     272     273     274     275     276     277     278     279     280     >>  

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Oracle9i Database Server
Patch Set Notes
Release 2 Patch Set 4 Version 9.2.0.5.0 for 32-Bit Windows March 2004=20


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.=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D