Just a quick note, I'm a certfied Oracle DBA, and while you should be calling close(), this rarely truly means "close", especially if you're using statement caches (and if you aren't, you probably should :).
In oracle it's most scalable to cache open Statements for as long as possible. Ideally this should be done by the JDBC driver or whatever connection pool infrastructure you have, but you could also do it in your application if you're doing manual connections. On high volume applications I often set OPEN_CURSORS to upwards of 10000. It's a threshold to prevent runaway apps from killing the database, that's all. Sorry for the JDBC off topic, but just thought I'd chime in.. Cheers Stu On Tuesday, August 02, 2005, at 06:04AM, Celinio Fernandes <[EMAIL PROTECTED]> wrote: >Thanks, >That is the information I needed to remember: > >"every SQL statement you run against an ORACLE server opens a database >cursor implicitly" > >The solution should never be to increase the number of cursors open in >the Oracle server parameters, >that would be a mistake (poor performances, use of a lot memory, etc ) > >I had not closed the PreparedStatement after executing the request and >that was a mistake (close() ). >That was more some JDBC related stuff than XMLbeans. >Sorry. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
