jdbc cursor problem

Please help.

We are unable to avoid a "maximum open cursors exceeded" problem when using JDBC prepared statements to Oracle 8 Enterprise. The problem manifests itself in the following ways:

(1) The exception is thrown after running 5 or 6 transactions using our
server object that contains the database accesses.
(2) Using a JDBC-ODBC bridge, we need to close the prepared statements in
order not to get the exception. If we simply close the result sets, the exception is thrown.
(3) Using the Oracle JDBC thin driver, closing the prepared statements
doesn't help either. The exception is always thrown.
(4) Discarding the database connection between transactions closes the
cursors and avoids the problem.
(5) In both cases, if we query the database using (for example) select
count(*) from v$_open_cursor in SQL+, we are told that there is only one open cursor, even immediately before and immediately after the exception is thrown.
(6) We have set max cursors to 500, and our code opens substantially fewer
in each transaction.

Has anyone else experienced these problems? Are there any diagnostics that will help us to pinpoint the problem, assuming it is in our code or in our settings for the database?

Thanks,

Ron Received on Tue Nov 24 1998 - 10:12:09 CST