Re: Stored procedure failed: maximum open cursors exceeded
- From: "Anurag Varma" <avoracle@xxxxxxxxx>
- Date: 26 Jan 2006 14:14:21 -0800
PL/SQL has the optimization where cursors are not closed. Instead they
are reused.
However, if the open cursors start approaching the max, then pl/sql
automatically starts closing them when it hits the limit.
The optimization is a good thing. Sybrand has opinions which
might not be backed by evidence/proof.
In your case, for that function you are just talking about couple of
implicit cursors.
I cannot believe you would be hitting the limit on just a couple of
them.
So my guess is that you might be diagnosing this wrong. Maybe you are
calling/using
this function from a jdbc app and not properly closing cursors.
You need to tell the whole story .. not just part of it.
Anurag
.
- Follow-Ups:
- Re: Stored procedure failed: maximum open cursors exceeded
- From: thomas . kyte
- Re: Stored procedure failed: maximum open cursors exceeded
- References:
- Stored procedure failed: maximum open cursors exceeded
- From: Serguei . Goumeniouk
- Re: Stored procedure failed: maximum open cursors exceeded
- From: Joel Garry
- Re: Stored procedure failed: maximum open cursors exceeded
- From: Serguei . Goumeniouk
- Stored procedure failed: maximum open cursors exceeded
- Prev by Date: Re: Stored procedure failed: maximum open cursors exceeded
- Next by Date: Re: strange quesion about listener
- Previous by thread: Re: Stored procedure failed: maximum open cursors exceeded
- Next by thread: Re: Stored procedure failed: maximum open cursors exceeded
- Index(es):
Relevant Pages
|