Last updated on MARCH 08, 2017
Applies to:JDBC - Version 188.8.131.52 to 184.108.40.206 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 18-Jan-2013***
An application runs in a version 1.5 JVM on a WebLogic application server and connects to a version 10.2.0.4 database via JDBC/Thin 220.127.116.11 ojdbc5.jar. The application uses connection pooling, WebLogic statement caching, and setQueryTimeout.
Intermittently, a prepared statement fails with
java.sql.SQLException: ORA-01006: bind variable does not exist
java.sql.SQLException: ORA-01008: not all variables bounded
Once an error occurs it repeats, continuing to occur on future logical connections that use the same physical connection and run the same query as the logical connection on which the error first occurred.
Sometimes only ORA-01006 errors occur.
Sometimes only ORA-01008 errors occur.
Sometimes ORA-01006 and ORA-01008 errors alternate. In this case, two prepared statements are involved.
The ORA-01006 and/or ORA-01008 errors are always preceded by one or more "ORA-01013: user requested cancel of current operation" errors due, either primarily or exclusively, to queries timing out (the expected behavior of setQueryTimeout).
The ORA-01006 and ORA-01008 errors do not occur when WebLogic statement caching is not used.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms