[unixODBC-dev] Too many cursors open

anand.vasudevan at wipro.com anand.vasudevan at wipro.com
Tue Nov 8 10:09:46 GMT 2005


>From the ODBC API documentation I found that the application has to
explicitly call SQLCloseCursor after every query execution.
In our code we do call SQLFreeHandle each time we need to free the
statement handle but not SQLCloseCursor.
Should the application call SQLCloseCursor after it calls SQLFetch to
fetch the query results? Will SQLFreeHandle not take care of it?

Thanks in advance.


-----Original Message-----
From: unixodbc-dev-bounces at easysoft.com
[mailto:unixodbc-dev-bounces at easysoft.com] On Behalf Of Nick Gorham
Sent: Tuesday, November 08, 2005 3:07 PM
To: Development issues and topics for unixODBC
Subject: Re: [unixODBC-dev] Too many cursors open

anand.vasudevan at wipro.com wrote:

>We are using easysoft's ODBC oracle driver. We get this error after our
>application runs a few hundred queries: -
>'ORA-01000: maximum open cursors exceeded'.
>What could cause this error in the ODBC context?
>Should this be handled in the application code or at database
>administration level?
>This kind of error never ocurred with Ingres database.
AFAIK There is a server configuration parameter that sets this.

Also I would check your code to make sure it is closing connections. But

I seem to remember the server will cache them as well.

Nick Gorham
Easysoft Limited
unixODBC-dev mailing list
unixODBC-dev at easysoft.com

Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.

More information about the unixODBC-dev mailing list