• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

CallableStatement (Oracle JDBC)

 
Phyllis @systemetrix
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The close of the CallableStatement and the Connection are leaving open cursors in my database. Any ideas what I can do to tighten up the code so that the cursors are closed?

Is there another route other than callablestatement? The call is to a procedure within a package that has an output parameter.

Thanks.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64716
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Phyllis @systemetrix",

We're pleased to have you here with us on the Ranch, but there are a few rules that need to be followed, and one is that proper names are required. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks!
bear
Forum Bartender
 
Avi Abrami
Ranch Hand
Posts: 1141
1
Java Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Phyllis,
If your "CallableStatement" is returning a "ResultSet", I suggest you also close the "ResultSet" -- preferrably in the following order:
  • ResultSet
  • CallableStatement
  • Connection


  • Good Luck,
    Avi.
     
    • Post Reply
    • Bookmark Topic Watch Topic
    • New Topic