Kbase P68755: Will the Oracle DataServer take advantage of the session_cursor_cache because it is an OCI applicati
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Unverified
GOAL:
Will the Oracle DataServer take advantage of the session_cursor_cache because it is an OCI application
GOAL:
What is the session_cursor_cache parameter
FACT(s) (Environment):
Oracle DataServer
FIX:
If an application repeatedly issues parse calls on the same set of SQL statements, then the reopening of the session cursors can affect system performance. Session cursors can be stored in a session cursor cache.
Oracle checks the library cache to determine whether more than three parse requests have been issued on a given statement. If so, then Oracle assumes that the session cursor associated with the statement should be cached and moves the cursor into the session cursor cache. Subsequent requests to parse that SQL statement by the same session then find the cursor in the session cursor cache.
To enable caching of session cursors, you must set the initialization parameter SESSION_CACHED_CURSORS. The value of this parameter is a positive integer specifying the maximum number of session cursors kept in the cache. An LRU algorithm removes entries in the session cursor cache to make room for new entries when needed.
You can also enable the session cursor cache dynamically with the statement:
ALTER SESSION SET SESSION_CACHED_CURSORS = <value>