Can any one explain, why we are getting the following error? We are using weblogic server with JDBC driver version 10.1.0.2.

Thanks,

Nov 8, 2004 12:01:38 PM com.tmobile.sqlmgr.rv.RequestHandler sendErrorResponse
INFO: Sending error response: { STATUS={ CODE=101 MESSAGE="java.sql.SQLException: OALL8 is in an inconsistent state.
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.T4C8Oall.init(T4C8Oall.java:308)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:166)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:543)
at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:915)
at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:452)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:978)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2888)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2929)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:80)
at com.tmobile.sqlmgr.engine.SQLPreparedStatement.executeQuery(SQLPreparedStatement.java:94)
at com.tmobile.sqlmgr.rv.RequestHandler.handleQuery(RequestHandler.java:266)
at com.tmobile.sqlmgr.rv.RequestHandler.run(RequestHandler.java:78)
" } }

I'm also having this problem and this is what I've found so far:

http://www.orindasoft.com/public/PL-SQL%20Recordstwo.php4?siteloc=PL-SQL%20Recordstwo#probva

This is known to occur under when you are using too big an array size. How big your array can be depends on the length of each record and the Driver/Database combination. If you exceed the maximum size you will get the "OALL8" SQLException and your connection object may become unusable.

This message is also created if you are using the following:
9.0.1 Database
10.1.0 JDBC Driver
Generated Code that passes in an ARRAY or VARRAY of VARCHAR2 as a Parameter

+1 with such intermittent problems eventually resulting in an OALL8 is in an inconsistent state message.

JDBC driver: 10.2.0.1.0
Database: Oracle9i Enterprise Edition Release 9.2.0.6.0

Will post something back if I manage to discover the cause.

JDBC 10.1.0.2 seems definitely a little old (I don't what is the latest mino version number). 10g drive seems having various issues. We use 10.1.0.3 to access 10g database (forgot what is mino version number), when SQL MERGE statement combine with JDBC batch execution, it had serious problme (socket stopped communication). Oracle fixed this and made it in 10.1.0.4. But seems still having other random problmes. Then we switch driver back to 9.x, everything worked fine (so 9.x dirve against 10g db).

Seems your case is 9.x db and 10g drive. It seems to me enven more dangerous. If possible, why don't you use 9.x drive against 9.x db?

Just my thoughts

Any one has a fix or work around for this.Please post if any one has more info regarding this

The bug is also fixed in 10.2.0.1.

This is known to occur under when you are using too big an array size. How big your array can be depends on the length of each record and the Driver/Database combination. If you exceed the maximum size you will get the "OALL8" SQLException and your connection object may become unusable.

This message is also created if you are using the following:

9.0.1 Database
10.1.0 JDBC Driver
Generated Code that passes in an ARRAY or VARRAY of VARCHAR2 as a Parameter

Hi All,

We have two applications running with the same ojdbc14 (10.2.0.2.0) driver. One of them uses apache-commons-dbcp, another spring's DriverManagerDataSource, and only the one which uses commons-dbcp encounters this problem.

Can anyone help?

Thank you,

Julius.