The above forces the DIAG background process on each node to generate systemstate dump on a local node. Hence this time the results won′t be in ′ user_dump_dest′ directory - you should look for systemstate dump info in ′ background_dump_dest′, trace file of DIAG process - like ′myrac1_diag_7056.trc′ in the example. Make sure you have it generated on all nodes – collect DIAG trace files from all nodes. If the above procedure does not work for any reason, then get systemstate dump individually on every node – see below. 数据挖掘研究院
Individual systemstate dumps:
If you have to generate systemstate information individually on each cluster node, use following the procedure: 数据挖掘研究院
dbhost:/home/oracle > sqlplus / as sysdba SQL*Plus: Release 10.2.0.1.0 - Production on Fri Sep 23 15:14:44 2005 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, Real Application Clusters, OLAP and Data Mining options SQL> alter session set tracefile_identifier=′sysstatedump′; Session altered. SQL> oradebug setmypid Statement processed. SQL> oradebug unlimit Statement processed. SQL> oradebug dump systemstate 10 Statement processed. ... wait a minute or two here... SQL> oradebug dump systemstate 10 Statement processed. SQL> exit 数据挖掘实验室
The dump files are generated in the $ORACLE_BASE/admin/<DB_name>/udump directory. It′s easy to locate the trace file as it will have ′systemstate′ suffix in its name:
dbhost:/usr/home/oracle/admin/myrac/udump > ls -l | grep systemstate -rw-r----- 1 oracle oinstall 2352795 Sep 22 16:57 myrac1_ora_16571_sysstatedump.trc
Have a look inside the trace file to make sure the file contains what we need. You should see the following somewhere at the beginning of the file:
*** SESSION ID:(93.7828) 2005-09-23 09:29:35.901
===================================================
SYSTEM STATE
------------
System global information:
