Hi,
we were having that problem too, long time ago. You should use the 'Oracle9i' Platform setting in your jdbc-connection-descriptor instead of the Oracle
'Platform', that should fix the problem. IIRC the 'Oracle' Platform does a caching of PreparedStatements, however the Oracle Driver has its own
PreparedStatements cache, having this double caching causes too many cursors to stay open.
The Oracle9i Platform should not make use of the local PreparedStatements cache.
Furhtermore the 'Oracle9i' offers better performance and correct handling for
BLOBs > 4kB, for 9i or later Oracle versions.
Good luck
cheers
Danilo
Bruno CROS wrote:
Hi all,
Experiencing some MAX OPEN CURSOR oracle errors (ORA -01000) , i'm looking
for the cursors leaks ( unclosed ResultSet it seems) in code.
I guess that broker queries well close the result set. So when report
queries results iteration are closed ? on HasNext()==false ?
Is it possible to check open cursors when releasing connections ? and by
the
way, close them if needed ?
Note : MAX_OPEN_CURSOR Oracle parameter is actually set at 500 by
connection
( and 1000 sooner )
Oracle 10, OJB 1.0.4 with some litle updates
Regards.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
