OERR: ORA-3137 "TTC protocol int…

OERR: ORA-3137"TTC protocol internal error : [n] []" Master Note [ID1388487.1]

---

 修改时间01-FEB-2012     类型REFERENCE     状态PUBLISHED 

In this Document
  Purpose
  Scope
  OERR:ORA-3137 "TTC protocol internal error : [n] []" MasterNote
     Description
  References

---

Applies to:

Oracle Server - Standard Edition - Version: 11.1.0.6 to 11.2.0.3 -Release: 11.1 to 11.2
Oracle Server - Enterprise Edition - Version:11.1.0.6 to 11.2.0.3   [Release:11.1 to 11.2]
Information in this document applies to any platform.

Purpose

This article provides information about error ORA-3137 and possibleactions.

Scope

This note is intended for general audience as initial startingpoint for beginning diagnosis of ORA-3137.

OERR: ORA-3137"TTC protocol internal error : [n] []" Master Note

Error:  ORA-03137 (ORA-3137)
Text:   TTC protocol internalerror : [arg1] [arg2] ...
Cause:  TTC protocol internalerror.


Description

Client / server message exchanges use an Oracle specific protocol(TTC). ORA-3137 is reported if something unexpected is seen thatdoes not conform to the expected protocol. The arguments in theerror indicate what sort of issue was seen. Specifically "arg1" maybe a number or a string indicating the problem seen, and arg2onwards may give additional information about the error. The errorcan be raised by the client or server side of a connection.

ORA-3137 was introduced in 11g and replaces some earlier ORA-600errors.
eg: A problem in 11g which reports ORA-3137 may have reported anORA-600 with a similar
first argument in 10g and earlier releases.
eg: An issue causing ORA-3137 [12333] in 11g may have reportedas ORA-600 [12333] in 10g.


Some common example arguments are:

• [12333]
  This is one of the most common forms of the error. It indicatesthat we are about to read an new function request from the messagebut the function code seen is not a valid code. This can typicallyhappen if the current message position has gotten out of sync forsome reason.
  
• [1010]
  Similar to 12333 this typically implies that the message asked toexecute some invalid operation.
  
• [12209]
  The message asked to map a cursor but the cursor number requestedto be mapped is not valid.

As the error is typically related to some problem in the messageexchange then for investigation purposes it is usually helpful toknow:

• Client version and product (eg: OCI, JDBC Thin, Pro, JDBC OCIetc..)
• Server version
• Details of patches applied at either end
  
• Client and server traces and incident traces produced
• Details of the logic / SQL of the code executing in the sessionaround the failure time
  
• If a problem is reproducible then it can be helpful to have NETtrace from the client and server side for the problem dialogue asoften an error depends on some sequence of events earlier in themessage exchange. See Note:219968.1 for details of NET trace options.
  

Known Bugs

You can restrict the list below to issues likely toaffect one of the following versions by clicking the relevantbutton:

NBBugFixedDescription1308706612.1.0.0ORA-3137 [3149] on server due to bad bind attempt inclientV11020001 V11020002 V11020003 ERROROCI970346311.1.0.7.8, 11.2.0.1.BP12, 11.2.0.2, 12.1.0.0ORA-3137 [12333] or ORA-600 [kpobav-1] When Using BindPeekingV11010006 V11010007 V11020001 CBO ERROROERI957165911.2.0.3, 12.1.0.0ORA-3137 [12333] using DRCPV11010006 V11010007 V11020001 V11020002ERROR OCI944567511.2.0.2, 12.1.0.0"No more data" / ORA-3137 using end to end metrics with JDBCThinV10010005 V10020002 V10020003 V10020004V10020005 V11010006 V11010007 V11020001 JDBC937337011.2.0.3, 12.1.0.0The wrong cursor may be executed by JDBC thin following a querytimeout / ORA-3137 [12333]V10020002 V10020003 V10020004 V10020005V11010006 V11010007 V11020001 V11020002 ERROR JDBC OERIWRONGRES924391211.2.0.2, 12.1.0.0Additional diagnostics for ORA-3137 [12333] / OERI:12333V11010006 V11010007 V11020001 DIAGOERI864331111.2.0.2, 12.1.0.0ORA-3137 / ORA-600 [12333] from INSERT .. RETURNING / Procedurewith OUT parameterV10020002 V10020003 V10020004 V10020005V11010006 V11010007 V11020001 ERROR OCI OERI PLSQL862576211.1.0.7.3, 11.2.0.1ORA-3137 [12333] due to bind data not read from wireV10020002 V10020003 V10020004 V10020005V11010006 V11010007 ERROR OERI690068111.2.0.1Unexpected errors (ORA-3137 [12209]) after incorrectOCIStmtRelease following OCISessionRelease with DRCPV11010006 V11010007 ERROR OCI673770610.2.0.5, 11.2.0.1OERI [12333] / ORA-3137 possible from multi table insert SQLwith long bindsV10010005 V10020002 V10020003 V10020004V11010006 V11010007 ERROR OERI666780010.2.0.5, 11.1.0.7OERI:12333 / client hang using OCILob() in multithreaded OCIclientV10020002 V10020003 V10020004 V11010006HANG LOB OCI

• '*' against a bug indicates that analert exists for that issue.
• '+' indicates a particularly notablebug.
• 'P' indicates a port specific bug.
• Fixed versions use "BPnn" to indicate Exadatabundle nn.
• "OERI:xxxx" may be used as shorthand forORA-600 [xxxx].

References

NOTE:1361107.1- Troubleshooting ORA-3137 [12333] Errors Encountered When UsingOracle JDBC Driver
NOTE:389713.1 - Understanding and Diagnosing ORA-00600 [12333]/ ORA-3137 [12333] Errors
NOTE:219968.1 - SQL*Net & Oracle Net Services -Tracing and Logging at a Glance

相关内容

---

产品

---

• Oracle Database Products > Oracle Database> Oracle Database > Oracle Server -Standard Edition
• Oracle Database Products > Oracle Database> Oracle Database > Oracle Server -Enterprise Edition

关键字

---

BUGTAG_ADDBUGS错误

---

ORA-600[12333]; ORA-3137

返回页首

Copyright (c) 2007, 2010, Oracle. All rightsreserved. Legal Notices and Terms of Use | Privacy Statement

 为此文档评级