如何使用ErrorStack進行錯誤跟蹤及診斷

144次閱讀

共計 4441 個字符，預計需要花費 12 分鐘才能閱讀完成。

這篇文章主要為大家展示了“如何使用 ErrorStack 進行錯誤跟蹤及診斷”，內容簡而易懂，條理清晰，希望能夠幫助大家解決疑惑，下面讓丸趣 TV 小編帶領大家一起研究并學習一下“如何使用 ErrorStack 進行錯誤跟蹤及診斷”這篇文章吧。

使用 ErrorStack 進行錯誤跟蹤及診斷

在使用

數據庫的過程中，可能會遇到各種各樣的錯誤或異常，很多異常的提示并不具體，我們有必要了解一下的跟蹤方式。

是提供的一種對于錯誤堆棧進行跟蹤的方法，通過設置跟蹤可以將一些錯誤的后臺信息詳盡地轉儲出來，寫入跟蹤文件，對于錯誤的研究與診斷非常有效。

ErrorStack40 1 2 Level1 + ProcessState

（顯示所有，著重顯示當前）

可以在實例級或會話級別設置，也可以在參數文件中設置，這個設置僅當某個特定的錯誤出現時才被觸發，如設置事件的跟蹤：

一個客戶曾經出現如下錯誤，提示數據的精度超過允許值，是后臺調度的任務：

Errors in file /admin/erpdb/bdump/erpdb1_j000_447020.trc:
ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at line 1

SQLErrorStackSQLalter system set events= 1438 trace name errorstack forever,level 3

alter system set events= 1438 trace name errorstack off

Oracle 10gMon Jul 13 10:48:392009
Mon Jul 13 10:56:06 2009
ORA-01438: value larger than specified precision allowed for this column
Trace dumping is performing id=[cdmp_20090713105608]
OS Pid: 541528 executed alter system set events 1438 trace name Errorstackoff

SQLSQLSQLNumber***SESSION ID:(857.16304) 2009-07-13 10:56:06.429
ksedmp: internal or fatal error
Current SQL statement for this session:
—– PL/SQL Call Stack —–
handle number name
700000336a1a070 236 procedure ERP.PROC_AUTOBATPROC
700000342eb7c20 1 anonymous block

可以很容易地測試這一功能的使用，比如使用如下代碼中的測試過程：

SQL connect eygle/eygle
Table created.
insert into t values(a,1)
ERROR at line 1:
SQL alter system set events 984 trace name errorstack off

Mon Jul 13 22:55:592009
Mon Jul 13 22:59:12 2009
ORA-00984: column not allowed here
OS Pid: 2431 executed alter system set events 984 trace name errorstack off

insert*** 2009-07-13 22:59:12.928
ORA-00984: column not allowed here
insert into t values(a,1)
calling call entry argument values in hex
——————– ——– ——————– —————————-

以下引用在 ITPUB 上的一個討論，是使用 ErrorStack 跟蹤解決問題的典型案例（原文鏈接指向 ITPUB）

Import: Release 10.2.0.1.0 – Production on Tue Mar 18 14:19:49 2008

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – 64bit Production

Export file created by EXPORT:V10.02.01 via conventional path

. importing DBA_MGR s objects into DBA_MGR

IMP-00058: ORACLE error 1438 encountered

IMP-00028: partial import of previous table rolled back: 20501 rows rolled back

System altered

然后重新執行 IMP；

2、查看 UDUMP 下日志, 如下:

/opt/oracle/admin/orcl/udump/orcl_ora_32355.trc

With the Partitioning, OLAP and Data Mining options

System name:Linux

Release:2.6.9-22.ELsmp

Machine:x86_64

Redo thread mounted by this instance: 1

Unix process pid: 32355, image: oracle@zhx25.cccc.com (TNS V1-V3)

*** SESSION ID135.949) 2008-03-18 17:11:02.014

ksedmp: internal or fatal error

Current SQL statement for this session:

(PRTNO , SEQNO , SEQDESC , PRTEFLAG , SEQCC , SEQNXTNO , SEQDEPT , WKCCODE , WKCALTCODE , SEQSETHR , LAB_SEQSETHR , SEQRUNHR , LAB_SEQRUNHR , SEQQUEHR , LAB_SEQQUEHR , SEQTRANHR , LAB_SEQTRANHR , SEQNOQLTRAT , SEQCHGDAT , SEQCHGRSN , SEQCHGCTLR , MACHCODE , MACHALTCODE , RESCODE , KEYSEQ , SEQCRYLOT , INITOVERRATE , COMWORK , SEQLOTFLAG , SEQEFDAT , SEQIEFDAT , SEQEFLOTNO , SEQIEFLOTNO , SEQECONO , PRTSEQCST , SEQSELFCST , INVYORN , SEQQTY , SEQNOTE , NOPRTAVELZ , OUTSEQFLAG , WXCST , SEQGSCHGCTLR , SEQGSCHGDAT , SEQSHCTL , SEQSHDAT , SEQSHSIGN , PRICE , ACCNO , ROUSTAT , FIXMFLAG , BANCL (:1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14, :15, :16, :17, :18, :19, :20, :21, :22, :23, :24, :25, :26, :27, :28, :29, :30, :31, :32, :33, :34, :35, :36, :37, :38, :39, :40, :41, :42, :43, :44, :45, :46, :47, :48, :49, :50, :51, :52)

calling

entry

location

point

…………

Offsi = 48, Offsi = 1440