Oracle ORA-03137: TTC protocol internal error: [12333] Fault Analysis

Source: Internet
Author: User

Oracle ORA-03137: TTC protocol internal error: [12333] an error occurs when the analytics program connects to the database through JDBC and reports ORA-03137 [12333. The JDBC driver version of the current program: ojdbc16-11.2.0.1.0.jar database version: 11.2.0.3. log info 1.1 alert logTNS-12637: Packet receive failed ns secondary err code: 12532 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 opiodr aborting process unknown ospid (28518) as a result of ORA-609Fri Aug 09 15:41:20 2013 Errors in file/u01/app/oracle/diag/rdbms/tserpdb/trace/tserpdb_ora_28329.trc (incident = 60746): ORA-03 137: TTC protocolinternal error: [12333] [19] [3] [14] [] [] [] [] Incident details in: /u01/app/oracle/diag/rdbms/tserpdb/incident/incdir_60746/Jun Aug 09 15:41:21 2013 Sweep [inc] [60746]: completedSweep [inc2] [60746]: completedFri Aug 09 15:41:21 2013 Dumping diagnostic data indirectory = [cdmp_20130809154121], requested by (instance = 1, osid = 28329), summary = [inciden T = 60746]. fri Aug 09 15:59:42 2013 1.2 trace file Dump file/u01/app/oracle/diag/rdbms/tserpdb/incident/incdir_60746/explain Database 11g Enterprise EditionRelease 11.2.0.3.0-64bit ProductionWith partitioning, automatic StorageManagement, OLAP, Data Miningand Real Application Testing optionsORACLE_HOME =/u01/app/oracle/product/11.2.0/dbhome_1System name: LinuxN Ode name: sh-tsiagent-003180Release: 2.6.18-308. el5Version: # 1SMP Tue Feb 21 20:06:06 EST 2012 Machine: x86_64Instance name: tserpdbRedo thread mounted by this instance: 1 Oracle process number: 92 Unix process pid: 28329, image: oracle @ sh-tsiagent-003180 *** 15:41:20. 138 *** session id: (1911.53519) 2013-08-0915: 41: 20.138 *** client id :() 15:41:20. 138 *** service name :( tsdb3180.deve Lop) 15:41:20. 138 *** module name :( JDBC Thin Client) 15:41:20. 138 *** action name :() 15:41:20. 138 Dump continued from file:/u01/app/oracle/diag/rdbms/tserpdb/trace/tserpdb_ora_28329.trcORA-03137: TTC protocol internal error: [12333] [19] [3] [14] [] [] [] [] ========= Dump for incident 60746 (ORA 3137 [12333]) ======== *** 15:41:20. 139 dbkedDefDump (): Starting incident defaultdumps (flags = 0x2, level = 3, mask = 0x0) ----- Current SQL Statement for thissession (SQL _id = 35tr4jfq0x3jw) ----- select mpzone0 _. ZONEID as ZONEID83_0 _, mpzone0 _. AREACODE as AREACODE83_0 _, mpzone0 _. CARDTYPE as CARDTYPE83_0 _, mpzone0 _. city as city83_0 _, mpzone0 _. province as province83_0 _ fromIAGENT. MPZONE mpzone0 _ where mpzone0 _. ZONEID =: 1 ----- Call Stack Trace ----- calling call en Try argument values in hex location type point (? Means dubious value) -------------------- -------------------------------------------------- skdstdst () + 36 call kgdsdst () 000000000? 000000000? 7FFF91403248? 000000001? 000000001? 000000002 ?... _ Libc_start_main () call main () 000000002? 7FFF91414458? + 244 000000001? 000000000? 009B910C0? 000000000? _ Start () + 36 call _ libc_start_main () 000A0AF38? 000000002? 7FFF91414448? 000000000? 009B910C0? 000000002 ?... --------------------- Binary Stack Dump ------------------- ========= FRAME [1] (skdstdst () + 36-> kgdsdst ()) ========== defined by frame pointers0x7fff91407b00 and 0x7fff91407af0CALL TYPE: call error signaled: no COMPONENT: (null) RDI 0000000000000000 RSI rj0000000000007fff91403248rcx 0000000000000001 R8 0000000000000001 r900000000000000000002rax 0000000000000000 RBX 00000000000000000003rbp 00007 201710000r11 00000000000000000000000000000003r13 0000000000000002 R14 0000000000000000000000000000000000000001rsp 00007FFF91407B00 RIP 0000of memory from 0000000091407b00 00007FFF 06772B3D00000000 [. {@..... = + w...] ========= FRAME [2] (ksedst1 () + 98-> skdstdst ()) =========== defined by frame pointers0x7fff91407bb0 and 0x7ff F91407b00CALL TYPE: call error signaled: no COMPONENT: KSE 1.3 Java ERROR org. springframework. transaction. transactionSystemException: cocould not commit Hibernate transaction; nested exception isorg. hibernate. transactionException: JDBC commit failed org. springframework. orm. hibernate3.HibernateTransactionManager. doCommit (HibernateTransactionManager. java: 660) org. springframework. transaction. support. region CtPlatformTransactionManager. processCommit (AbstractPlatformTransactionManager. java: 754) org. springframework. transaction. support. abstractPlatformTransactionManager. commit (AbstractPlatformTransactionManager. java: 723) org. springframework. transaction. interceptor. transactionAspectSupport. commitTransactionAfterReturning (TransactionAspectSupport. java: 394 )... java. SQL. SQLRecoverableException: No more da Ta to read from socketoracle. jdbc. driver. t4CMAREngine. unmarshalUB1 (T4CMAREngine. java: 1200) oracle. jdbc. driver. t4CMAREngine. unmarshalSB1 (T4CMAREngine. java: 1155) oracle. jdbc. driver. t4CTTIfun. receive (T4CTTIfun. java: 279) oracle. jdbc. driver. t4CTTIfun. doRPC (T4CTTIfun. java: 186) oracle. jdbc. driver. t4C7Ocommoncall. doOCOMMIT (T4C7Ocommoncall. java: 75) oracle. jdbc. driver. t4CConnection. doCommit (T4CConnection. java: 55 8) oracle. jdbc. driver. physicalConnection. commit (PhysicalConnection. java: 3674) oracle. jdbc. driver. physicalConnection. commit (PhysicalConnection. java: 3680) org. apache. tomcat. dbcp. dbcp. delegatingConnection. commit (DelegatingConnection. java: 334) org. apache. tomcat. dbcp. dbcp. poolingDataSource $ PoolGuardConnectionWrapper. commit (PoolingDataSource. java: 211) org. hibernate. transaction. JDBCTransaction. commitAndReset AutoCommit (JDBCTransaction. java: 166) II. The solution is searched on MOS. This problem is very similar to Bug9445675. Bug 9445675 no moredata 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 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 se Rver 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. the current JDBC Driver version is 11.2.0.1.0. Therefore, after the jdbc driver is upgraded to 11.2.0.2, the fault is resolved.
 

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.