Systemstate Dump

Systemstate is the one of most important dump files that Oracle Support uses to analyze the database hang conditions. This requires that the maxdump file size be set to unlimited, as this will generate large trace files depending on the size of the SGA. The systemstate dump contains a separate section with information for each process. Normally, you need to take two or three dumps in regular intervals. Expect HUGE trace files!

Syntax

Systemstate dump can be produced using following methods .

Using ALTER SESSION

The first ALTER SESSION command below removes any restrictions on the dump file size. The second ALTER SESSION command produces an immediate systemstate dump at level 10.

 alter session set max_dump_file_size = unlimited; 
 alter session set events 'immediate trace name systemstate level 10';

Using oradebug

The following oradebug command produces an immediate systemstate dump at level 10. The select statement is to avoid problems on pre-Oracle 8.0.6 databases, sometimes connect internal may not have a complete process initialized :

 select * from dual; 
 oradebug setmypid 
 oradebug unlimit 
 oradebug dump systemstate 10

Controlling the Dump Information Using Levels

Not applicable . Systemstate dumps are always taken at level 10. There is no code in the Oracle kernel for other levels.