Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Hi,
can anyone explain the following error message:
SQL Error: no more cursors remaining?
This Message is generated from an ODBC access with Informix ClientSDK 2.5 on a
client.
There is no entry in the Informix online.log.
I found in the Informix 9.30fc3x3 release notes, that the number of cursor per
user session is a machine specific parameter, but no more information.
We are using Informix 9.30FC3X3 on HP Tru64 Unix
Does this message mean a programming error/limitation in the application, or
is it an error/limitation from the Informix Client SDK?
Thank you
Wolfgang
↪ replying to WOLFGANG NEUMAR
Eric Rowell — — source: IIUG Forums & Mailing Lists
Check
the number of cursors you have open. I cannot stress this enough.
The reason for the vague answer by Informix for how many you can have open is
because it is depended on the size of hardware given to the database server. I
would bet if you look at your servers configuration you would have to find
that there are some resources that are just maxed out.
onstat -g segonstat -g ses ##SESSION##
Changing Buffers and stacksize may help with this but I would have to say
closing cursors when they are not being used would be the best thing for you.
onstat -g stmonstat -g stm ##SESSION##
This should you all of the open cursors for a given server or sid.
Note the more open cursors doing large sets of work the more memory that can
be used and may not be released until the cursor is. Virtual segments could be
added if there is room for the server to grow.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.