How to use ErrorStack for error tracking and diagnosis 02/24 Update SLTechnology News&Howtos

How to use ErrorStack for error tracking and diagnosis

2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Shulou(Shulou.com)05/31 Report--

This article mainly shows you "how to use ErrorStack for error tracking and diagnosis", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "how to use ErrorStack for error tracking and diagnosis" this article.

Error tracking and diagnosis using ErrorStack

In use

In the process of the database, we may encounter a variety of errors or exceptions, and many of the exception tips are not specific, so we need to know how to track them.

It provides a method to trace the error stack. By setting the trace, some background information of the error can be dumped in detail and written into the trace file, which is very effective for the research and diagnosis of errors.

ErrorStack40 1 2 Level1 + ProcessState

(show all, highlight current)

It can be set at the instance or session level, or in a parameter file, which is triggered only when a specific error occurs, such as setting the trace of an event:

A customer has encountered the following error, indicating that the precision of the data exceeds the allowable value, which is a task scheduled by the backend:

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 1014 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

You can easily test the use of this feature, such as the test process in the following code:

SQL > connect eygle/eygle

Table created.

Insert into t values (aPhone1)

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 5912.928

ORA-00984: column not allowed here

Insert into t values (aPhone1)

Calling call entry argument values in hex

The following quote, a discussion on ITPUB, is a typical case of using ErrorStack to track problem resolution (original link to 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

Then re-execute the IMP

2. Check the log under UDUMP, as follows:

/ 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 purl 1115 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,: 36,: 37,: 38,: 39,: 40,: 41,: 42,: 44,: 45,: 46,: 47,: 48,: 49,: 50,: 51,: 52)

Calling

Entry

Location

Point

Offsi = 48, Offsi = 1440