« 斷電故障導(dǎo)致 ASM DiskGroup 故障及恢復(fù)案例 |Blog首頁| 10g Profile FAILED_LOGIN_ATTEMPTS如何計(jì)數(shù)? »
Mon Jul 13 10:27:31 2009跟蹤文件中缺省的不會記錄具體的SQL、綁定變量等信息,我們可以通過ErrorStack進(jìn)行后臺跟蹤,獲得更詳細(xì)的信息,執(zhí)行如下SQL:
Errors in file /admin/erpdb/bdump/erpdb1_j000_447020.trc:
ORA-12012: error on auto execute of job 22
ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at "ERP.TIMRDU", line 13
ORA-06512: at line 1
alter system set events='1438 trace name errorstack forever,level 10';然后可以手工執(zhí)行以下存儲過程,獲得跟蹤文件,再關(guān)閉跟蹤:
alter system set events='1438 trace name errorstack off';在Oracle 10g中,這樣的操作會被記錄到日志文件中:
Mon Jul 13 10:48:39 2009接下來分析獲得的跟蹤文件,就可以獲得SQL文本線索,找到根本問題。
OS Pid: 541528 executed alter system set events '1438 trace name Errorstack forever,level 10'
Mon Jul 13 10:56:06 2009
Errors in file /admin/erpdb/udump/erpdb1_ora_267056.trc: ORA-01438: value larger than specified precision allowed for this columnMon Jul 13 10:56:08 2009
Trace dumping is performing id=[cdmp_20090713105608]
Mon Jul 13 10:57:15 2009
OS Pid: 541528 executed alter system set events '1438 trace name Errorstack off'