ORA-03137: TTC protocol internal error : [12333]错误一例

Oracle Solaris上的一套11.2.0.1.0最近出现以下告警记录:

<a href="http://blog.51cto.com/maclean/1277549#">?</a>

<code>Dump file /cnbbs01/app/oracle/diag/rdbms/nbbsprd1/nbbsprd1/incident/incdir_373041/nbbsprd1_ora_24754_i373041.trc</code>

<code>Oracle </code><code>Database</code> <code>11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production</code>

<code>ORACLE_HOME = /cnbbs01/app/oracle/product/11.2.0/db_1</code>

<code>System </code><code>name</code><code>: SunOS</code>

<code>Node </code><code>name</code><code>: ut06db03</code>

<code>Release: 5.10</code>

<code>Version: Generic_142901-12</code>

<code>Machine: i86pc</code>

<code>Instance </code><code>name</code><code>: nbbsprd1</code>

<code>Redo thread mounted </code><code>by</code> <code>this instance: 1</code>

<code>Oracle process number: 130</code>

<code>Unix process pid: 24754, image: oracle@ut06db03</code>

<code>*** 2010-08-25 02:01:19.169</code>

<code>*** SESSION ID:(1203.16390) 2010-08-25 02:01:19.169</code>

<code>*** CLIENT ID:() 2010-08-25 02:01:19.169</code>

<code>*** SERVICE </code><code>NAME</code><code>:(SYS$USERS) 2010-08-25 02:01:19.169</code>

<code>*** MODULE </code><code>NAME</code><code>:() 2010-08-25 02:01:19.169</code>

<code>*** </code><code>ACTION</code> <code>NAME</code><code>:() 2010-08-25 02:01:19.169</code>

<code>Dump continued </code><code>from</code> <code>file: /cnbbs01/app/oracle/diag/rdbms/nbbsprd1/nbbsprd1/trace/nbbsprd1_ora_24754.trc</code>

<code>ORA-03137: TTC protocol internal error : [12333] [11] [120] [110] [] [] [] []</code>

<code>========= Dump </code><code>for</code> <code>incident 373041 (ORA 3137 [12333]) ========</code>

<code>*** 2010-08-25 02:01:19.170</code>

<code>dbkedDefDump(): Starting incident </code><code>default</code> <code>dumps (flags=0x2, </code><code>level</code><code>=3, mask=0x0)</code>

<code>----- Current SQL Statement for this session (sql_id=8ath6p5cx60q2) -----</code>

<code>SELECT</code> <code>eventtime, messageid, result, userid, username, userdomainid, objid, objname, objdomainid, data, data0, obj2id, server </code><code>FROM</code> <code>eventlog a </code><code>WHERE</code> <code>1 = 1 </code><code>AND</code> <code>EVENTTIME &lt; :1 </code><code>AND</code> <code>EVENTTIME &gt; :2 </code><code>AND</code> <code>messageid </code><code>IN</code> <code>(</code><code>'AdminUIAudit'</code> <code>, </code><code>'NBIAudit'</code><code>) </code><code>ORDER</code> <code>BY</code> <code>EVENTTIME </code><code>DESC</code>

<code>----- Call Stack Trace -----</code>

<code>ksedst1 &lt;- ksedst &lt;- dbkedDefDump &lt;- ksedmp &lt;- dbgexPhaseII</code>

<code>&lt;- dbgexProcessError &lt;- dbgePostErrorKGE &lt;- 1438 &lt;- opiierr &lt;- opitsk</code>

<code>&lt;- opiino &lt;- opiodr &lt;- opidrv &lt;- sou2o &lt;- opimai_real</code>

<code>&lt;- ssthrdmain &lt;- main &lt;- start</code>

<code>----------------------------------------</code>

<code>SO: 0x5fb961a98, type: 4, owner: 0x5fff8fd60, flag: INIT/-/-/0x00 if: 0x3 c: 0x3</code>

<code>proc=0x5fff8fd60, </code><code>name</code><code>=session, file=ksu.h LINE:11467 ID:, pg=0</code>

<code>(session) sid: 1203 ser: 16390 trans: 0x0, creator: 0x5fff8fd60</code>

<code>flags: (0x41) USR/- flags_idl: (0x0) -/-/-/-/-/-</code>

<code>flags2: (0x40008) -/-</code>

<code>DID: , short-term DID:</code>

<code>txn branch: 0x0</code>

<code>oct: 3, prv: 0, sql: 0x5b08829c0, psql: 0x5d799a460, </code><code>user</code><code>: 67/NBBS_MTS</code>

<code>ksuxds </code><code>FALSE</code> <code>at</code> <code>location: 0</code>

<code>service </code><code>name</code><code>: SYS$USERS</code>

<code>client details:</code>

<code>O/S info: </code><code>user</code><code>: , term: , ospid: 1234</code>

<code>machine: ut06nbbs01 program:</code>

<code>Current</code> <code>Wait Stack:</code>

<code>Not</code> <code>in</code> <code>wait; </code><code>last</code> <code>wait ended 1.274194 sec ago</code>

以上Select语句在sqlplus或sql developer等工具远程登录后执行均没有出错，仅在使用jdbc驱动连接时出现ORA-03137: TTC protocol internal error : [12333] [11]错误；提交SR，MOS认为该应用使用的JDBC API version 2.1过旧，建议升级到最新版本。 这个case通过升级jdbc驱动解决了。

本文转自maclean_007 51CTO博客，原文链接:http://blog.51cto.com/maclean/1277549