Re: jdbc cursors

I seem to remember a bug with the JDBC drivers that does not close a connection properly after use and that you must explicitly close it. Ahh yes, here is the text from the original email:

 Yes you should use jdbc. But you should beware of the pitfalls. The  biggest one is:
 Last time I checked, you had to actually close the connection in jdbc  and
then reopen another connection if you changed the sql statement.  In theory you should be able to:

1. open a connection
2. associate a sql statement with that connection
3. execute it
4. close the *statement*
5. associate another statement with that connection and execute it But if you don't close/reopen the *connection* when you change the sql statement, then the open cursors on the database just mount up until you eventually blow the max_open_cursors (or whatever it's called).

"Lane W. Sharman" wrote:

> Hi,
>
> Actually, cursors are a scarce resource. Increase the your initXXXX.ora file:
>
> OPEN_CURSORS=xxxx
>
> where xxxx > 500 for minimum production systems.
>
> -Lane
>
> Ed Zappulla wrote
Received on Tue Jan 05 1999 - 08:02:40 CST