Chinaunix首页 | 论坛 | 博客
  • 博客访问: 82761
  • 博文数量: 38
  • 博客积分: 10
  • 博客等级: 民兵
  • 技术积分: 360
  • 用 户 组: 普通用户
  • 注册时间: 2012-07-11 14:02
文章分类
文章存档

2017年(38)

我的朋友

分类: Oracle

2017-12-07 13:48:14

 When the issue occurred, please perform. the following:
1. Please provide the OSWatcher output
You can refer following note for details:
Note:301137.1 OS Watcher User Guide
2. please systemstate and hanganalyze dump
A. Identify the SID you want to trace
export ORACLE_SID=PROD
Replace PROD with the SID you want to trace
B. Using SQL*Plus connect as "/ AS SYSDBA" using the following command:
sqlplus -prelim / as sysdba
C. Execute the following:
SQL> oradebug setmypid
SQL> oradebug unlimit
SQL> oradebug -g all hanganalyze 3
SQL> oradebug -g all dump systemstate 266
D. Wait at least 2 minutes to give time to identify process state changes.
E. Execute the following:
SQL> oradebug -g all hanganalyze 3
SQL> oradebug -g all dump systemstate 266
Verify that the the "diag" background process trace file has been updated in the
background_dump_destination on each node. Examine each "diag" file to ensure that it
contains 2 hanganalyze dumps and a systemstate dump.
阅读(2042) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~