Oracle support request hang analysis and system state dumps when rasing SR.
One 10.1 or higher versions login as
To do a hanganalyze
Wait 60 - 90 seconds and run the last command again to identify the process state changes.
To get a systemstate dump
Wait 60 - 90 seconds and run again to identify the system state changes.
If it is taking too long then cancel and run with level 258.
One a cluster environment use
for hang analyze
for system state dumps.
get dump trace file path
One 10.1 or higher versions login as
sqlplus -prelim / as sysdba
To do a hanganalyze
oradebug setmypid;
oradebug unlimit;
oradebug hanganalyze 3;
Wait 60 - 90 seconds and run the last command again to identify the process state changes.
To get a systemstate dump
oradebug setmypid;
oradebug unlimit;
oradebug dump systemstate 266;
Wait 60 - 90 seconds and run again to identify the system state changes.
If it is taking too long then cancel and run with level 258.
One a cluster environment use
oradebug -g all hanganalyze 3
for hang analyze
oradebug -g all dump systemstate 266
for system state dumps.
oradebug tracefile_name
get dump trace file path
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。




