Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

jdbc

 
namrata rane
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using preparedStatement to execute some queries .
and inspite of closing result, statement i am getting
"maximum cursors open exceeded".
What can be the reason?
 
Jamie Robertson
Ranch Hand
Posts: 1879
MySQL Database Suse
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If Oracle it your database, This might help:
even after resultset.close(), statement.close(),resultset = null and statement=null, all cursors were not being closed in the DB. A service call in to oracle seemed to imply that there were some bugs in their jdbc implementations - any Statement you created would internally spawn cursors in the db (from their drivers) that weren't getting closed. apparently this has been fixed in the 8.1.7 release, classes12.zip. I still found that we needed to set our open_cursors (in init.ora, on the db server) to a fairly high number (i think default is 40 or something), and do a forced conn.rollback() every time we returned the Connection interface object back to our connection pool.
another way to clean up the cursors is to close the connection. But this process is too time consuming for our implementation.
seemed to help... but not totally solve
Jamie
 
Fred Abbot
Ranch Hand
Posts: 300
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
if you use prepared statments it will reuse the cursors
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic