oracle 3137,OERR: ORA-3137 "TTC protocol internal error

[Release:

11.1 to 11.2]

Information in this document applies to any platform.

Purpose

This article provides information about error ORA-3137 and possible

actions.

Scope

This note is intended for general audience as initial starting

point for beginning diagnosis of ORA-3137.

OERR: ORA-3137

"TTC protocol internal error : [n] []" Master Note

Error: ORA-03137 (ORA-3137)

Text: TTC protocol internal

error : [arg1] [arg2] ...

Cause: TTC protocol internal

error.

Description

Client / server message exchanges use an Oracle specific protocol

(TTC). ORA-3137 is reported if something unexpected is seen that

does not conform to the expected protocol. The arguments in the

error indicate what sort of issue was seen. Specifically "arg1" may

be a number or a string indicating the problem seen, and arg2

onwards may give additional information about the error. The error

can be raised by the client or server side of a connection.

ORA-3137 was introduced in 11g and replaces some earlier ORA-600

errors.

eg: A problem in 11g which reports ORA-3137 may have reported an

ORA-600 with a similar

first argument in 10g and earlier releases.

eg: An issue causing ORA-3137 [12333] in 11g may have reported

as ORA-600 [12333] in 10g.

Some common example arguments are:

[12333]

This is one of the most common forms of the error. It indicates

that we are about to read an new function request from the message

but the function code seen is not a valid code. This can typically

happen if the current message position has gotten out of sync for

some reason.

[1010]

Similar to 12333 this typically implies that the message asked to

execute some invalid operation.

[12209]

The message asked to map a cursor but the cursor number requested

to be mapped is not valid.

As the error is typically related to some problem in the message

exchange then for investigation purposes it is usually helpful to

know:

Client version and product (eg: OCI, JDBC Thin, Pro, JDBC OCI

etc..)

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 session

around the failure time

If a problem is reproducible then it can be helpful to have NET

trace from the client and server side for the problem dialogue as

often an error depends on some sequence of events earlier in the

message exchange. See Note:219968.1 for details of NET trace options.

Known Bugs

You can restrict the list below to issues likely to

affect one of the following versions by clicking the relevant

button:

NB

Bug

Fixed

Description

12.1.0.0

ORA-3137 [3149] on server due to bad bind attempt in

client

V11020001 V11020002 V11020003 ERROR

OCI

11.1.0.7.8, 11.2.0.1.BP12, 11.2.0.2, 12.1.0.0

ORA-3137 [12333] or ORA-600 [kpobav-1] When Using Bind

Peeking

V11010006 V11010007 V11020001 CBO ERROR

OERI

11.2.0.3, 12.1.0.0

ORA-3137 [12333] using DRCP

V11010006 V11010007 V11020001 V11020002

ERROR OCI

11.2.0.2, 12.1.0.0

"No more data" / ORA-3137 using end to end metrics with JDBC

Thin

V10010005 V10020002 V10020003 V10020004

V10020005 V11010006 V11010007 V11020001 JDBC

11.2.0.3, 12.1.0.0

The wrong cursor may be executed by JDBC thin following a query

timeout / ORA-3137 [12333]

V10020002 V10020003 V10020004 V10020005

V11010006 V11010007 V11020001 V11020002 ERROR JDBC OERI

WRONGRES

11.2.0.2, 12.1.0.0

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

V11010006 V11010007 V11020001 DIAG

OERI

11.2.0.2, 12.1.0.0

ORA-3137 / ORA-600 [12333] from INSERT .. RETURNING / Procedure

with OUT parameter

V10020002 V10020003 V10020004 V10020005

V11010006 V11010007 V11020001 ERROR OCI OERI PLSQL

11.1.0.7.3, 11.2.0.1

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

V10020002 V10020003 V10020004 V10020005

V11010006 V11010007 ERROR OERI

11.2.0.1

Unexpected errors (ORA-3137 [12209]) after incorrect

OCIStmtRelease following OCISessionRelease with DRCP

V11010006 V11010007 ERROR OCI

10.2.0.5, 11.2.0.1

OERI [12333] / ORA-3137 possible from multi table insert SQL

with long binds

V10010005 V10020002 V10020003 V10020004

V11010006 V11010007 ERROR OERI

10.2.0.5, 11.1.0.7

OERI:12333 / client hang using OCILob() in multithreaded OCI

client

V10020002 V10020003 V10020004 V11010006

HANG LOB OCI

'*' against a bug indicates that an

alert exists for that issue.

'+' indicates a particularly notable

bug.

'P' indicates a port specific bug.

Fixed versions use "BPnn" to indicate Exadata

bundle nn.

"OERI:xxxx" may be used as shorthand for

ORA-600 [xxxx].

References

NOTE:1361107.1

- Troubleshooting ORA-3137 [12333] Errors Encountered When Using

Oracle 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 rights

reserved. Legal Notices and Terms of Use | Privacy Statement