Re: "Ora-01000 maximum open cursors exceeded" after update from 10.2.0.1 to 10.2.0.3

On Jun 4, 10:25 am, poschma <marti..._at_utanet.at> wrote:
> Hi all!
>
> After updating our Database from 10.2.0.1 to 10.2.0.3 I get the error
> Ora-01000 in our application (we use the proC precompiler).
>
> When I look at the v$open_cursor, I see the number of cursors
> increasing all the time.
> In our application we have a lot of select statements and every
> statement is a cursor. But the cursor is always closed after the
> statement. And we also have a lot of transactions. And after a
> rollback the cursors should be closed automatic (am I right?).
>
> It seams that neither a "EXEC SQL CLOSE ..." nor a "rollback" close
> the cursors any more!
>
> The parameter session_cached_cursors is 20, the parameter open_cursors
> is set to 300.
>
> With 10.2.0.1 we have no problems.
> Has anyone an idea whats running wrong? Is there a new parameter?
>
> Thanks in advance

Afaik, ROLLBACK doesn't close any cursors, it just rolls back current transaction (and COMMIT doesn't close cursors either.) Try closing unneeded cursors explicitly after rollback. Why you started hitting the issue only after patching I can't say. Maybe there's some regression in the patchset that causes cursor leakage, but I couldn't find any similarly looking bugs on MetaLink except your very own forum post...

Hth,

   Vladimir M. Zakharychev
   N-Networks, makers of Dynamic PSP(tm)    http://www.dynamicpsp.com Received on Mon Jun 04 2007 - 08:14:48 CDT