Hello all,

Does anyone encountered mentioned ORA when using Hibernate 2.0 ?
It seems, that after few hours of working a'ok, Oracle throws this exception and only restart of web app is helping.

I have found following in the FAQ, that PreparedStatements should be disabled on Oracle and we have done so, but it didnt help.

I have also found here [url]http://www.hibernate.org/hib_docs/api/net/sf/hibernate/cfg/Environment.html#
STATEMENT_CACHE_SIZE[/url] info, that PreparedStatements aren't cached, so maybe it's not where the problem is.

Would appreciate any help :-)

thanks,
Leszek

Hibernate version:
2.0

Name and version of the database you are using:
Oracle 9i

Did you consider searching the forum first?

Well, known issue with Oracle vs. connection pools that do prepared statement caching.

It is not an issue if pool closes "old" statements, you just need to configure correct limits. There is a way to debug cursor leaks on oracle too (system tables), just paste error code to google.

Hmm...

Let me quote myself:



So, any idea if setting hibernate.statement_cache.size=0 is not helping ? :-)

thanks,
Leszek

See system table to debug leaks, as I remember it is v$open_cursors . See "open" SQL queries and find related code, this error means you have cursor leak (unclosed statement or result set). Workaround can be to configure oracle to close cursors at the end of transaction before you find this leak in code.

Btw.

How should I put the statement hibernate.statement_cache.size=0 into hibernate.cfg.xml ? Maybe we are doing it wrong ?

Currently we have something like this:

<property name="statement_cache.size">0</property>

Is it ok ?

thanks,
Leszek

Hibernate must print configuration options to log file in debug mode.
BTW you can try to deploy application without connection pooling, it can scale better if you will tune connection startup (domain name resolving lags in the most of cases).