ORA-03137: TTC 協議內部錯誤: [12333] [48] [9] [91] [] [] [] []
檢查trc檔案發現有如下問題:
ump file /oracle/app/db/diag/rdbms/oracle1/oracle1/incident/incdir_7497/oracle1_ora_17113_i7497.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/app/11.2.0/db_1
System name: Linux
Node name: d4jttisvprd01
Release: 2.6.32-358.el6.x86_64
Version: #1 SMP Tue Jan 29 11:47:41 EST 2013
Machine: x86_64
VM name: VMWare Version: 6
Instance name: oracle1
Redo thread mounted by this instance: 1
Oracle process number: 37
Unix process pid: 17113, image: oracle@d4jttisvprd01
*** 2015-04-10 14:31:42.994
*** SESSION ID:(77.17211) 2015-04-10 14:31:42.994
*** CLIENT ID:() 2015-04-10 14:31:42.994
*** SERVICE NAME:(oracle1) 2015-04-10 14:31:42.994
*** MODULE NAME:(SQL Loader Conventional Path Load) 2015-04-10 14:31:42.994
*** ACTION NAME:(d:\hrHFM\ctl\periodic.ctl) 2015-04-10 14:31:42.994
Dump continued from file: /oracle/app/db/diag/rdbms/oracle1/oracle1/trace/oracle1_ora_17113.trc
ORA-03137: TTC ?????’?©????????????????: [12333] [4] [71] [65] [] [] [] []
========= Dump for incident 7497 (ORA 3137 [12333]) ========
*** 2015-04-10 14:31:43.063
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skdstdst()+41 call kgdsdst() 000000000 ? 000000000 ?
7FFF3A97E6F0 ? 7FFF3A97E7C8 ?
7FFF3A983270 ? 000000002 ?
ksedst1()+103 call skdstdst() 000000000 ? 000000000 ?
7FFF3A97E6F0 ? 7FFF3A97E7C8 ?
7FFF3A983270 ? 000000002 ?
搜了一下,網上太多解決方案,最後在MOS上看到如下解決方案,與我的問題極為相似,資料庫版本都是一致的。
The alert logfile shows the following error:
Sat Jul 05 11:42:48 2014
Errors in file /oracle_base/diag/rdbms/ORCL/ORCL/trace/ORCL_ora_16057148.trc (incident=247676):
ORA-03137: TTC protocol internal error: [12333] [50] [9] [7] [] [] [] []
Incident details in: /oracle_base/diag/rdbms/ORCL/ORCL/incident/incdir_247676/ORCL_ora_16057148_i247676.trc
Sat Jul 05 11:42:52 2014
Dumping diagnostic data in directory=[cdmp_20140705114252], requested by (instance=1, osid=16057148), summary=[incident=247676].
...
The errors are occasional: if the load is re-run then it is likely that the sqlldr job now succeeds without errors.
Other possible errors:
ORA-25402: transaction must roll back
ORA-12152: TNS:unable to send break message
ORA-12592 TNS: Bad Packet
CHANGES
You recently upgraded to 11.2.0.4 and are loading data to the database server with SQL*Loader.
The problem is caused by a inconsistency in the SQL*Net layer on the server side, when a data package from the client is read in two different modes (first part in non-fast path mode and second part in fast path mode).
As a result of that, the first part of the package data is lost, resulting in:
ORA-03137: TTC protocol internal error : [12333] [50] [9] [7] [] [] [] []
or
ORA-12592: TNS:BAD PACKET
References:
Bug 18841764 - ORA-12592 TNS:BAD PACKET OR ORA-3137 OR ORA-1 (not a public bug), fixed in 12.2.0.1
Note 18841764.8 - Bug 18841764 - Network related error like ORA-12592 or ORA-3137 or ORA-3106 may be signaled
Other references:
- ORA-25408, ORA-25402, ORA-12152 AND ORA-12592 AFTER UPGRADE TO 11.2.0.4, closed as a duplicate of Bug 18841764
- SQL*LOADER FAILS WITH ORA-3137, fixed with fix of Bug 18841764, closed as a duplicate of Bug 18841764
- ORA-12592 ERRORS AFTER DATABASE UPGRADE TO 11.2.0.4
SOLUTION
1. Confirm that the workaround of Bug 18841764 actually fixes the problem.
Set in the Server side sqlnet.ora file following parameter:
--------------------------------
...
SQLNET.SEND_TIMEOUT=600
This file is located in the directory: $ORACLE_HOME/network/admin
2. Retest the issue by re-running the SQL*Loader loads.
3. If the problem is fixed, and you need to remove the entry SQLNET.SEND_TIMEOUT from the sqlnet.ora file on the server, then apply if available for your platform and version (or request this fix from Oracle Support), and re-run the SQL*Loader job.
4. Migrate the solution as appropriate to other environments.
參考自:Occasional ORA-12592 (TNS:BAD PACKET) and ORA-03137 [12333] When Running SQL*Loader Jobs (Doc ID 1905674.1)
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28612416/viewspace-1821257/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-03137: TTC 協議內部錯誤: [12333] [7] [0] [0] [] [] [] []協議
- 資料庫alert日誌報ORA-03137 TTC 協議內部錯誤故障分析處理資料庫協議
- ORA-03137: TTC protocol internal error: [12333]分析及處理ProtocolError
- ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC DriverProtocolErrorJDBC
- ORA-03137: TTC protocol internal error : [12333] [7] [120] [115] [] [] [] []ProtocolError
- ORA-00600: 內部錯誤程式碼, 引數: [12333]
- ORACLE ORA-03137錯誤處理Oracle
- RA-03137:TTC protocol internal error:[12333]ProtocolError
- 蓄意協議錯誤:蘭利法則協議
- onvif soap 協議的錯誤程式碼協議
- PHP HTTP 500 - 內部伺服器錯誤PHPHTTP伺服器
- 伺服器內部錯誤500的原因伺服器
- ora-600內部錯誤的型別型別
- 關閉ubuntu討厭的內部錯誤提示Ubuntu
- zt_ora-600內部錯誤的型別型別
- win10 mstsc出現內部錯誤怎麼修復_win10 mstsc出現內部錯誤解決方法Win10
- http協議內容HTTP協議
- ORA-12560:TNS:協議介面卡錯誤協議
- ORA-12560: TNS: 協議介面卡錯誤協議
- NEO改進協議提案9(NEP-9)協議
- 什麼是http500內部伺服器錯誤?HTTP伺服器
- 伺服器出現遠端內部錯誤的原因伺服器
- 虛擬機器VMware“內部錯誤”的解決方法虛擬機
- Sql server內部函式fn_PhysLocFormatter存在解析錯誤SQLServer函式ORM
- 解決IIS5 HTTP500內部錯誤 (轉)HTTP
- Swift---協議和擴充套件、 錯誤處理、泛型Swift協議套件泛型
- ORACLE登入出現“ORA-12560:TNS:協議介面卡錯誤”錯誤修復Oracle協議
- IDEA報錯java: 編譯失敗: 內部 java 編譯器錯誤IdeaJava編譯
- ORA-00600: 內部錯誤程式碼, 引數: [19004]
- 華納雲內部伺服器500錯誤原因和解決方法伺服器
- 華納雲:解決WordPress伺服器內部錯誤的方法伺服器
- Sql server內部函式fn_PhysLocFormatter存在解析錯誤(續)SQLServer函式ORM
- 遇到ORA-00600: 內部錯誤程式碼, 引數: [kzsrgpw]
- ORA-12161: TNS:內部錯誤:收到部分資料
- Windows下ORA-12560: TNS: 協議介面卡錯誤Windows協議
- 解決ORA-12560: TNS: 協議介面卡錯誤協議
- day48:django前戲之HTTP協議&自定義web框架DjangoHTTP協議Web框架
- ORA-00600: 內部錯誤程式碼, 引數: [ktspfmdb:objdchk_kcbnew_3], [9], [93111], [4],OBJ