Re: Open cursors

From: steven <zhang.bin_at_sssltd.cn>
Date: 6 May 2005 01:47:58 -0700
Message-ID: <1115369278.746316.310080@f14g2000cwb.googlegroups.com>

Hi dk,
this's from document.
[quote]

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. This feature can be particularly useful for applications that use Oracle Forms, because switching from one form to another closes all session cursors associated with the first form.

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.

[/quote]

So session_cached_cursors like a used/soft closed(cached).

Your can catch unclosed cursor from v$open_cursor . Then you can focus on your java code. Received on Fri May 06 2005 - 03:47:58 CDT