oracle deadlock死鎖trace file分析之一增補

結論

1,基於oradebug 的alter system set events='60 trace name errorstack forever,level 3';
  是分析或獲取死鎖資訊的一處重要手段


2,errorstack適用於診斷某種特定的ORACLE錯誤
3,且記是alter system set events,而非set event,否則會報錯  


4，還有一點，透過10046也可以分析死鎖

測試

--oracle version
SQL> select * from v$version where rownum=1;


BANNER
----------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Prodoction




---event parameter
SQL> show parameter event


NAME                                 TYPE                   VALUE
------------------------------------ ---------------------- ------------------------------
event                                string


SQL> oradebug setospid 15936
Oracle pid: 184, Unix process pid: 15936, image: oracle@seconary (TNS V1-V3)
SQL> alter system set events='60 trace name errorstack forever,level 3';


System altered.


SQL> alter system set events='60 trace name errorstack off';


System altered.


SQL> oradebug tracefile_name
/oracle/diag/rdbms/guowang/guowang/trace/guowang_ora_15936.trc


產生的TRACE FILE我再列舉，和前文格式相同，內容一致