HANG分析与SYSTEMDUMP分析
来源:互联网 发布:淘宝退款贴吧 编辑:程序博客网 时间:2024/05/22 04:24
Collection commands for Hanganalyze and Systemstate: Non-RAC:
Sometimes, database may actually just be very slow and not actually hanging. It is therefore recommended, where possible to get 2 hanganalyze and 2 systemstate dumps in order to determine whether processes are moving at all or whether they are "frozen".
Hanganalyze
sqlplus '/ as sysdba'
oradebug setmypid
oradebug unlimit
oradebug hanganalyze 3
-- Wait one minute before getting the second hanganalyze
oradebug hanganalyze 3
oradebug tracefile_name
exit
Systemstate
sqlplus '/ as sysdba'
oradebug setmypid
oradebug unlimit
oradebug dump systemstate 266
oradebug dump systemstate 266
oradebug tracefile_name
exit
Collection commands for Hanganalyze and Systemstate: RAC
There are 2 bugs affecting RAC that without the relevant patches being applied on your system, make using level 266 or 267 very costly. Therefore without these fixes in place it highly unadvisable to use these level
For information on these patches see:
Document 11800959.8 Bug 11800959 - A SYSTEMSTATE dump with level >= 10 in RAC dumps huge BUSY GLOBAL CACHE ELEMENTS - can hang/crash instances
Document 11827088.8 Bug 11827088 - Latch 'gc element' contention, LMHB terminates the instance
Note: both bugs are fixed in 11.2.0.3.
Collection commands for Hanganalyze and Systemstate: RAC with fixes for bug 11800959 and bug 11827088
For 11g:
sqlplus '/ as sysdba'
oradebug setorapname reco
oradebug unlimit
oradebug -g all hanganalyze 3
oradebug -g all hanganalyze 3
oradebug -g all dump systemstate 266
oradebug -g all dump systemstate 266
exit
Collection commands for Hanganalyze and Systemstate: RAC without fixes for Bug 11800959 and Bug 11827088
sqlplus '/ as sysdba'
oradebug setorapname reco
oradebug unlimit
oradebug -g all hanganalyze 3
oradebug -g all hanganalyze 3
oradebug -g all dump systemstate 258
oradebug -g all dump systemstate 258
exit
For 10g, run oradebug setmypid instead of oradebug setorapname reco:
sqlplus '/ as sysdba'
oradebug setmypid
oradebug unlimit
oradebug -g all hanganalyze 3
oradebug -g all hanganalyze 3
oradebug -g all dump systemstate 258
oradebug -g all dump systemstate 258
exit
In RAC environment, a dump will be created for all RAC instances in the DIAG trace file for each instance.
- HANG分析与SYSTEMDUMP分析
- IE hang 分析
- Hang Detect 问题分析案例
- Oracle shutdown immediate hang住 现象分析
- 系统Hang住时用oradebug分析的方法
- mysql连接hang住问题分析
- 系统HANG住分析工具及方法
- 实战Java分析:Hang in maven test
- 使用v$wait_chains分析当前数据库hang
- 系统HANG住分析工具及方法
- oracle ORA-32701 hang分析(一)
- 【转】系统Hang住时用oradebug分析的方法
- oracle ORA-32701 hang分析(二)---hugepage优化
- 一条hang住数据库的SQL的分析
- 一篇分析诊断被"hang"住数据库的资料(Oracle Performance Diagnostic Guide——Hang/Locking)
- WinDbg+SOS:Web服务器High CPU Hang(100%)实例分析
- WinDbg+SOS:Web服务器High CPU Hang(100%)实例分析
- 分析多线程并发写HashMap线程被hang住的原因
- proxy-target-class="true" 与proxy-target-class="false"的区别
- 关于信息增益、信息熵、条件熵
- Ant生成war包
- spring中使用quartz框架(基于内存)
- 使用Python发送邮件
- HANG分析与SYSTEMDUMP分析
- Ubuntu 修复 grub
- 有关Android Handler内存泄漏分析及解决办法
- 如何在github上发起一个pull request,如何贡献代码,参与开源项目
- 动态创建多个KindEditor编辑器
- 8.3 Prove that STINGY SAT is NP-complete.
- MVC 三层架构
- mysql高性能优化零碎记忆--方便后续整理
- 实模式、保护模式、大真实模式