Intermitently we get the error below for simble db selects. The query is executed from a simple Spring JDBC call. Because of this error we eventually run out of connections.
Most of the occurances of this error I have read about corrected it through upgrading the JDBC driver.
Here are my versions. Is there a known problem with this configuration?
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
Implementation-Version: "Oracle JDBC Driver version - 10.1.0.5.0"
Specification-Title: "Oracle JDBC driver classes for use with JDK1. 4"
Specification-Version: "Oracle JDBC Driver version - 10.1.0.5.0"
java version "1.5.0_20"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_20-b02, mixed mode)
ERROR ody.comp.dao.JDBCTemplateHandler - PreparedStatementCallback; uncategorized SQLException for SQL [ SELECT FLG1, FLG2 FROM db1.STNS WHERE ID1 = ? ]; SQL state [null]; error code ; Bigger type length than Maximum; nested exception is java.sql.SQLException: Bigger type length than Maximum
ERROR org.springframework.transaction.interceptor.TransactionInterceptor - Application exception overridden by rollback exception
ody.comp.exception.ApplicationException: Unknown DB Error. Underlying message is:Bigger type length than Maximum
ERROR ody.comp.dao.JDBCTemplateHandler - PreparedStatementCallback; uncategorized SQLException for SQL [ SELECT 'Y' FROM db1.STNS WHERE ID1 = 'ET' AND ID2 = ? ]; SQL state ; error code ; OALL8 is in an inconsistent state.; nested exception is java.sql.SQLException: OALL8 is in an inconsistent state.
I agree it is probably a driver issue. The code works fine most of the time, but when we see this issue it seems to put the majority of db connects in a stale state.
I have read many forums discussing this problem. There were several other possibilities such as an array lenght that is not long enough. But for this case an array is not being used.
It is a big deal for me to update the production driver so I was hoping for proof that this is a known problem for my exact driver version.
Thanks for the advice.