Re: v$open_cursor view still populated after cursors are released

cursors are not deallocated until the connection to the server is closed. you can reuse an allocated cursor, that is, open, fetch from, and close a cursor multiple times. allocate the cursor one time only (each time the app connects to the database),

HTH "James A. Rooke" <berj4_at_earthlink.net> wrote in message news:3AA87B05.9E83D70D_at_earthlink.net...
> Hi.
>
> I am facing a problem with Oracle 8.1.7 EE on Sun OS where Oracle does
> not free up context areas from cursors
> after the calling program (in this case a ProC app) explicitly closes
> the cursor.
>
> The setup is this: I created a package with a type definition for a REF
> Cursor and a stored procedure to pass
> that REF Cursor back to the application; From there the application
> fetches the cursor values (stored proc is
> returning multiple rows) and when it is finished, it closes the cursor.
> After the app makes the call to close the
> cursor, that cursor is still visible (and allocated) in v$open_cursors;
> Eventually the application errors out with an
> ORA-01000 "maximum open cursors exceeded" error, even though the app
> explicity closes each cursor it
> opens.
>
> Has anyone seen this? If so, any way to fix it? Is it a but in Oracle?
>
> Thanks in advance,
>
> James
> berj4_at_earthlink.net
>
>
Received on Sat Mar 10 2001 - 07:11:58 CST