Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: How Oracle processes close cursor/cursor variable which were not

Re: How Oracle processes close cursor/cursor variable which were not

From: Ramamohan B N <ramamohan.bn_at_tatainfotech.com>
Date: Tue, 19 Dec 2000 14:12:49 +0530
Message-Id: <10715.124905@fatcity.com>


Hi Bala,

In the PL/SQL procedure, you have to close the cursors you've opened. Also Check wether you are closing the Cursors in the exception part.

BTW I heard when you configure ODBC there is an option to release the cursors held by a session I am not very sure on this.

Regards,
Mohan

Muru Bala wrote:
>
> Hello Lists,
>
> I am using REF CURSOR for running a query and
> retrieving data. The REF CURSOR is coded inside a
> PL/SQL procedure which is called by a C++ application
> through Oracle ODBC. The C++ application is using a
> open() method to call this stored procedure and assign
> the result to a RecordSet object.
>
> We running into ORA-01000 maximum number of open
> cursors reached error. I increased open_cursors from
> 50 to 500. Still after about 35000 number of procedure
> calls, we are getting this error.
>
> My question is: Somehow, the C++ applicaion is not
> closing the opened REF CURSOR after its use. How does
> Oracle SMON or PMON close these opened cursors
> periodically? How frequent the closing is done? Is
> there a way to check this using dictionary tables? Is
> it possible to increase the frequency of closing?
>
> I feel I am going wrong somewhere, I would like to get
> this clarified from you. Any level of help would be
> highly appreciated.
Received on Tue Dec 19 2000 - 02:42:49 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US