ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC Driver (文档 ID 752297.1)

In this Document

Symptoms

Cause

Solution

References

APPLIES TO:

JDBC - Version 11.1.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 26-Apr-2013*** 

SYMPTOMS

On 11.1.0.6 in Production, when attempting to run an application using the JDBC thin driver 11.1.0.6 against a database version 11.1.0.6, the following error occurs:

ORA-03137: TTC protocol internal error : [12333] [10] [83] [74] [] [] [] []

The stack trace in the database alert log is:

ORA-03137: TTC protocol internal error : [12333] [7] [120] [108] [] [] [] []

----- Current SQL Statement for this session (sql_id=c0czhbm4hcz98) -----

DELETE FROM PORTAL_CONCURRENT_USER_SCRATCH

WHERE LAST_LOGIN < :intervalStartDate

----- Call Stack Trace -----

calling call entry argument values in hex

location type point (? means dubious value)

-------------------- -------- -------------------- ----------------------------

skdstdst()+002c bl 105e2771c

ksedst1()+0064 bl 101fad134

ksedst()+0028 bl ksedst1() 60000B8104C4A30 ?

600000002050032 ?

dbkedDefDump()+07fc bl 101fae954

ksedmp()+0048 bl 101fad130

opiierr()+0168 bl ksedmp() 000000000 ?

opitsk()+1344 bl 103ec9a5c

opiino()+09a0 bl opitsk() 110098B40 ? 000000000 ?

opiodr()+0b48 bl 103ec7a30

opidrv()+0440 bl opiodr() 3C61672F72 ? 41032E668 ?

FFFFFFFFFFFF7E0 ? 073702F74 ?

sou2o()+0090 bl opidrv() 3C05C04AEC ? 4A09A9924 ?

FFFFFFFFFFFF7E0 ?

opimai_real()+01b0 bl 101face8c

main()+0090 bl opimai_real() 000000000 ? 000000000 ?

__start()+0098 bl main() 000000000 ? 000000000 ?

This problem does not happen if the 10.2.0.3 driver is used.

CAUSE

According to Bug 7390077 ORA-3137: TTC PROTO INTERNAL ERROR: [12333] [8]
[80] [65] reported for JDBC 11.0.6.0, this bug is an RDBMS bug and not JDBC.

SOLUTION

The solution is to upgrade the database to version 11.1.0.7 where the problem is fixed.

Note: Although upgrading to database version 11.1.0.7 has been confirmed to have solved this issue in a high number of cases, error ORA-3137 [12333] accompanied by Protocol Violation messages may still occur intermittently in database versions prior to 11.2,
including database 10.2.0.4 and 11.1.0.7. 

This has been reported in unpublished bug:8625762 ORA-3137 [12333] due to bind data not read from wire, in which case ORA-3137 [12333] can occur intermittently for SQL which uses user binds due to bind data being left unread on the Net connection. The bug suggests
the workaround of setting "_optim_peek_user_binds"=false to avoid this problem (workaround to be used with caution as it can affect execution plans chosen by CBO), and also provides the fix by the application of Patch:8625762.
 

Further information:

Suggestions For Troubleshooting ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver (Document 1361107.1)

 

Join the Java Development MOS Community forum for general discussions, questions, best practices, and other valuable information on: Oracle JDeveloper and ADF, Oracle WebLogic - JEE Programming (EJB, JMS etc), Oracle JDBC, Oracle Web Services (incl. DBWS Callout Utility), Oracle Web Services Manager (OWSM), Oracle Service Registry (OSR), Oracle Toplink (EclipseLink), Sun NetBeans IDE / Java Studio Creator & Java Studio Enterprise, OC4J, KODO.

REFERENCES

BUG:7445550 - ORA-03137:
TTC PROTO INTERNAL ERROR : [12333] [21] [106] [110] [] [] [] []

NOTE:1361107.1 - Troubleshooting
ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver
NOTE:8625762.8 - Bug 8625762 - ORA-3137
[12333] due to bind data not read from wire