Saturday, August 30, 2008

Overview of Using ORADEBUG Command

1. ORADEBUG command is used to diagnose the Database Hanging Issues

2. All the ORADEBUG should be executed as sysdba


3. We can use the following command to list the commands available in ORADEBUG

SQL> ORADEBUG HELP

4. We can use the following command to analyze the system hang, oradebug hanganalyze

1-2 - Only HANGANALYZE output, no process dump at all

3 - Level 2 + Dump only processes thought to be in a hang (IN_HANG state)

4 - Level 3 + Dump leaf nodes (blockers) in wait chains (LEAF,LEAF_NW,IGN_DMP state)

5 - Level 4 + Dump all processes involved in wait chains (NLEAF state)

10 - Dump all processes (IGN state)

Example

To perform cluster wide HANGANALYZE use the following syntax:

ORADEBUG setmypid
ORADEBUG setinst all
ORADEBUG -g def hanganalyze

5. The command we can use to stop the ORADEBUG is

SQL> ORADEBUG suspend

6. The command we can use to get the trace file name is

SQL> ORADEBUG tracefile_name

1 comment:

tikitodo said...

maybe the service of not a pdf or corrupted better suits your needs? I have recently tested several data recovery applications and I think it is the easiest one