Hi,
I have an problem with the cursors in Oracle that remain open after the connection to the databse is closed.
Let me explain the "cursor" that I am talking about.
In a Stored procedure we can explicitly OPEN a cursor for a select statement, FETCH etc. That is one cursor.
But, even if you execute a simple SQL statement, from say SQL PLUS or TOAD, Oracle basically open a cursor internally to get the data and once it is displayed the cursor gets closed. So in our oracle environment I did try to execute a SQL statement from TOAD and could see oracle openeing cursor and close it immediately after the statement is executed. So it definitely is not a Oracle Issuse.
Now if I execute a SQL statement from the Java application, under Weblogic 8.1 that uses connection pools, the cursors remain open in the oracle and never gets closed..
did someone else encounter similar issues before?
nims
I have an problem with the cursors in Oracle that remain open after the connection to the databse is closed.
Let me explain the "cursor" that I am talking about.
In a Stored procedure we can explicitly OPEN a cursor for a select statement, FETCH etc. That is one cursor.
But, even if you execute a simple SQL statement, from say SQL PLUS or TOAD, Oracle basically open a cursor internally to get the data and once it is displayed the cursor gets closed. So in our oracle environment I did try to execute a SQL statement from TOAD and could see oracle openeing cursor and close it immediately after the statement is executed. So it definitely is not a Oracle Issuse.
Now if I execute a SQL statement from the Java application, under Weblogic 8.1 that uses connection pools, the cursors remain open in the oracle and never gets closed..
did someone else encounter similar issues before?
nims