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

james...

i dunno about why the cursor view is still displayin the cursors there of whether the cursors are really gettin released....however i think i may have a workaround...there is an initialization parameter called MAX_OPEN_CURSORS....try n set that to a higher number in the init.ora file and see if it works...

ciao
venkat

"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 - 05:41:36 CST