Troubleshooting ORA-3137 [12333] Errors When Using Oracle JDBC Driver

In this Document

APPLIES TO:

PURPOSE

Oracle Customer Support has observed a large volume of issues reported by customers experiencing ORA-3137 [12333] and occasionally ORA-3137 [1010] errors when connecting to an Oracle RDBMS using the Oracle JDBC driver.  This document enumerates troubleshooting approaches that have proven successful.   

Note that while this problem may be encountered when making a JDBC connection to the database, it is rare that the problem actually comes from the JDBC driver itself.  Instead, the problem usually is caused from one of a small number of database bugs.

TROUBLESHOOTING STEPS

Known Database Issues

Unpublished Bug 8625762 - ORA-3137 [12333] due to bind data not read from wire

This bug affects RDBMS version lower than version 11.2.  It is fixed in version 11.2 of the database.

It can occur intermittently, due to bind data being left unread database connection.  This is a bind peeking bug.

This bug is also known for causing
ORA-3137: TTC protocol internal error : [1010] [] [] [] [] [] [] []

Unpublished Bug 9703463 - ORA-3137 [12333] or ORA-600 [kpobav-1] When Using Bind Peeking

This bug affects versions 11.1.0.6, 11.1.0.7, and 11.2.0.1 of the RDBMS.  It is fixed in version 11.2.0.2 of the database.

It can also occur intermittently; similarly to unpublished Bug:8625762, this is a bind peeking bug.

Unpublished Bug:9243912 - Additional diagnostics for ORA-3137 [12333] / OERI:12333

This bug affects versions of the RDBMS lower than version 11.2.0.2.  It is fixed in version 11.2.0.2 of the database.

This bug addresses scenarios in which the ORA-3137 [12333] error occur bind issues during the client/server communication process.  When this particular bug is fixed, the result may be the uncovering of an additional, more descriptive error:  ORA-600 [kpobav-1]

  ORA-03137: TTC PROTO INTERNAL ERROR: [12333] [8] [80] [65]

This bug affects the RDBMS 11.1.0.6 and is resolved with RDBMS 11.1.0.7.

typical errors:
ORA-03137: TTC protocol internal error : [12333] [10] [83] [74] [] [] [] []
ORA-03137: TTC protocol internal error : [12333] [7] [120] [108] [] [] [] []

example stack:

This problem does not happen if the JDBC 10.2.0.3 driver is used but is nevertheless considered a database bug.

The following bugs have been marked as potential duplicates of this case:
  

Unpublished Bug 9373370  - Data Base Returns Wrong CURSORID When There Is an ORA-1013

This bug affects the 10.2, 11.1, 11.2.0.1, and 11.2.0.2 databases.  It is discussed in the following notes:

Note:9373370.8 Bug 9373370 - The wrong cursor may be executed by JDBC thin following a query timeout / ORA-3137 [12333]
Note:9967872.8 Bug 9967872 - The wrong cursor may be executed by JDBC thin following a query timeout

While the bug primarily manifests in ORA-1006 or ORA-1008 errors, the problem may also result in ORA-600 [12333] or ORA-3137 [12333] errors appearing on the server side.

Known JDBC Issues

  NO MORE DATA TO READ FROM SOCKET WHEN USING END-TO-END METRICS

This bug does affect the JDBC driver.  This bug may be the cause when all of the following conditions are met:

1. You are using the 10.1.x.x or the 11.2.0.1 JDBC driver; the bug does not affect 10.2.x.x, or 11.1.x.x versions of the driver, nor versions 11.2.0.2 or above
2. You are using end-to-end metrics in your Java code
3. The server side ORA-3137 [12333] error is accompanied by the client side Java exception "No more data to read from socket"

This bug is fixed in the 11.2.0.2 version of the JDBC driver and above.  It is discussed in the following notes:

Note 9445675.8 Bug 9445675 - "No more data" / ORA-3137 using end to end metrics with JDBC Thin

Note 1081275.1 "java.sql.SQLRecoverableException: No more data to read from socket" is Thrown When End-to-end Metrics is Used

Troubleshooting Approaches

1.  Disable Bind Peeking

A common thread through the database bugs listed above is that the problem does not occur if bind peeking is shut off.  Temporarily disabling bind peeking allows you to confirm whether this is the case in your environment as well.  

This can be done dynamically:

If the ORA-3137 [12333] error no longer reproduces after disabling bind peeking, then in most cases, the problem is due to one of the database bugs listed above, or due to some variant of one of those bugs.

2.  Apply Relevant Database Patches

Whenever possible, the recommended solution when running a database version 11.1.0.7 is to apply the most recent PSU patch.
PSU 11.1.0.7.8  includes .

For 11.1.0.7,  can be applied on top of 11.1.0.7.8 ( no conflict).

  can also be applied individually but requires PSU 11.1.0.7.6 

  may also be applicable to databases version 11.1.0.7

If you have disabled bind peeking as a test, and the error no longer reproduces, then applying one of these patches would be the next step.

Alternatively, if you are unable to disable bind peeking for some reason, you may consider applying one of these patches as a diagnostic test in itself, to confirm whether the patch fixes the problem for you.

3.  Upgrade the Database to Version 11.2.0.3

All of the above bugs are fixed in version 11.2.0.3 of the database.

4.  Contact Oracle Support if the problem still persists

For JDBC connections that have resulted in the ORA-3137 error, the above database-centric approaches have resolved the issue almost all of the time.  If disabling bind peeking has no effect and the ORA-3137 [12333] still occurs, please contact Oracle Support, as this is a relatively rare scenario in which further investigation is needed.

REFERENCES