Oracle11gR2数据库出现ORA-03137:TTC protocolinternal error [12333]报错的解决方案

教程发布:风哥 教程分类:ITPUX技术网 更新日期:2022-02-12 浏览学习:33

Oracle11gR2数据库出现ORA-03137:TTC protocolinternal error [12333]报错的解决方案

1、最近在数据库Oracle 11g R2日志中经常看到ORA-03137: TTC protocolinternal error : [12333]报错,日志如下:JUL 09 15:41:20 2013Errors in file /u01/app/oracle/diag/rdbms/tsdb/tsdb/trace/tsdb_ora_28329.trc (incident=60746):ORA-03137: TTC protocolinternal error : [12333] [19] [3] [14] [] [] [] []
2、经查询,该问题与Bug9445675非常像。Bug 9445675 NO MOREDATA 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 orthe 11.2.0.1 JDBC driver; the bug does not affect 10.2.x.x, or 11.1.x.xversions of the driver, nor versions 11.2.0.2 or above2) You are using end-to-endmetrics in your Java code3) The server side ORA-3137[12333] error is accompanied by the client side Java exception "No moredata to read from socket"This bug is fixed in the11.2.0.2 version of the JDBC driver and above.
而当前版本的JDBC Driver 也是:11.2.0.1.0。 所以将JDBC DRIVER升级到11.2.0.2 之后,故障解决。以下关于ORA-03137: TTC protocolinternal error : [12333] [19] [3] [14] [] [] [] []报错的官方解释:
Troubleshooting ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver (文档 ID 1361107.1)

Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.1.0.1 [Release 10.2 to 12.1]
JDBC - Version 10.2.0.1 to 12.1.0.1.0 [Release 10.2 to 12.1]
Information in this document applies to any platform.
PurposeOracle 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 StepsKnown Database IssuesUnpublished Bug 8625762 - ORA-3137 [12333] due to bind data not read from wireThis 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 PeekingThis 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:12333This 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]

https://support.oracle.com/epmos/faces/BugDisplay?id=7390077]Bug 7390077 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: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 ?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: https://support.oracle.com/epmos/faces/BugDisplay?id=7573690]Bug 7573690 https://support.oracle.com/epmos/faces/BugDisplay?id=7607470]Bug 7607470 https://support.oracle.com/epmos/faces/BugDisplay?id=8490909]Bug 8490909 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:https://support.oracle.com/epmos/faces/DocumentDisplay?id=9373370.8]Note:9373370.8 Bug 9373370 - The wrong cursor may be executed by JDBC thin following a query timeout / ORA-3137 [12333] https://support.oracle.com/epmos/faces/DocumentDisplay?id=9967872.8]Note:9967872.8 Bug 9967872 - The wrong cursor may be executed by JDBC thin following a query timeoutWhile 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 Issueshttps://support.oracle.com/epmos/faces/BugDisplay?id=9445675]Bug 9445675 NO MORE DATA TO READ FROM SOCKET WHEN USING END-TO-END METRICSThis 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 above2 You are using end-to-end metrics in your Java code3 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:https://support.oracle.com/epmos/faces/DocumentDisplay?id=9445675.8]Note 9445675.8 Bug 9445675 - "No more data" / ORA-3137 using end to end metrics with JDBC Thinhttps://support.oracle.com/epmos/faces/DocumentDisplay?id=1081275.1]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 PeekingA 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:SQL> alter system set "_optim_peek_user_binds"=false;
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.Note: disabling bind peeking can have an impact on the database. Specifically, it can alter the explain plan for some queries that use bind variables. This should be taken into account, particularly before considering the use of this option as a long-term workaround.

2. Apply Relevant Database PatchesWhenever 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 https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=12419384]Patch 12419384 includes https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=9703463]Patch:9703463.

For 11.1.0.7, https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=9243912]Patch 9243912 can be applied on top of 11.1.0.7.8 ( no conflict).

https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=9703463]Patch:9703463 can also be applied individually but requires PSU 11.1.0.7.6

https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=8625762]Patch:8625762 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.3All of the above bugs are fixed in version 11.2.0.3 of the database.

4. Contact Oracle Support if the problem still persistsFor 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.

本文标签:
网站声明:本文由风哥整理发布,转载请保留此段声明,本站所有内容将不对其使用后果做任何承诺,请读者谨慎使用!
【上一篇】
【下一篇】