If that's the problem, how do I force OJB to close the statement? -----Original Message----- From: Ribi Roland [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 05, 2004 11:08 AM To: 'OJB Users List' Subject: RE: Maximum open cursors exceeded
This is'nt the problem of the query, this is because the close() Method of a java.sql.Statement-Object is'nt called after the query. Oracle needs to close all open cursers after the query is finished. This occurs after too many SQL-Calls to the database without closing the cursor. You can also create this behavior whith stored procedures in Oracle. Perhaps ojb does'nt closes the Statements in this QueryBySQL ? Roland Ribi > -----Original Message----- > From: Mindy Pereira [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 05, 2004 5:02 PM > To: OJB Users List > Subject: Maximum open cursors exceeded > > > I'm getting a collection beans using a QueryBySQL. > > Previously, it worked with no problems, however, when I added another > filter to the data set ("where X = Y and Z = 2 and W = 3"), I got the > following error: > > [org.apache.ojb.broker.accesslayer.StatementsForClassImpl] ERROR: > ORA-01000: max > imum open cursors exceeded > > Any help would be appreciated. > Mindy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
