Re: Maximum Open Cursors Exceeded
From: <la_at_datani.dk>
Date: 1995/10/02
Message-ID: <1995Oct2.170037.139_at_datani.dk>#1/1
>
> I would check with Oracle support. I've had problems with 7.1.3 on
> Netware not always releasing resources after it's done with them too.
>
> In my case it's been the temporary tablespace. Since I'm not in a
> production environment it's not been a problem for me to shutdown and
> restart which always clears up the problem. I've been told this is a
> known bug with 7.1.3. Your's may be the same case.
> --
> Chuck Hamilton
> chuckh_at_ix.netcom.com
>
> If at first you don't succeed, sky-diving isn't for you.
>
Received on Mon Oct 02 1995 - 00:00:00 CET
Date: 1995/10/02
Message-ID: <1995Oct2.170037.139_at_datani.dk>#1/1
It was bug # 210202
la_at_datani.dk in Oracle 7.0.16.4
In article <44k1c9$lmo_at_ixnews3.ix.netcom.com>, chuckh_at_ix.netcom.com (Chuck Hamilton) writes:
> Lorrie Gagnon <gagnon_at_dsr.com> wrote:
>
>>I'm using Oracle 7.1.3 and PL/SQL. I'm having a problem with my stored procedures >>exeeding the maximum open cursors value, which is currently set to 300. It appears, >>by looking in V$OPEN_CURSOR, that all of my implicit cursors are remaining active, >>rather than being reused.
>>Does anyone have any insight as to how I can work around or solve this problem? >>I would prefer not to rewrite all of my implicit cursors to be explicit, at this time.
>>Thanks in advance, >>Lorrie Gagnon >>gagnon_at_dsr.com
>
> I would check with Oracle support. I've had problems with 7.1.3 on
> Netware not always releasing resources after it's done with them too.
>
> In my case it's been the temporary tablespace. Since I'm not in a
> production environment it's not been a problem for me to shutdown and
> restart which always clears up the problem. I've been told this is a
> known bug with 7.1.3. Your's may be the same case.
> --
> Chuck Hamilton
> chuckh_at_ix.netcom.com
>
> If at first you don't succeed, sky-diving isn't for you.
>
Received on Mon Oct 02 1995 - 00:00:00 CET