3.2 Collecting Cluster Health Monitor Data

Collect Cluster Health Monitor data from any node in the cluster by running the Grid_home/bin/diagcollection.pl script on the node.

When an Oracle Clusterware error occurs, run the diagcollection.pl diagnostics collection script to collect diagnostic information from Oracle Clusterware into trace files.

Run the diagcollection.pl script as root from the Grid_home/bin directory.

Note:

  • Oracle recommends that you run the diagcollection.pl script on all nodes in the cluster to collect Cluster Health Monitor data. Running the script on all nodes ensures that you gather all information needed for analysis.

  • Run the diagcollection.pl script as a root  privileged user.

To run the data collection script only on the node where the cluster logger service is running:

  1. Run the command $ Grid_home/bin/oclumon manage -get master.
  2. Log in as a user with xx privilege, and change directory to a writable directory outside the Grid home.
  3. Run the command diagcollection.pl --collect.
    For example:
    Linux:
    $ Grid_home/bin/diagcollection.pl --collect
    Microsoft Windows:
    C:\Grid_home\perl\bin\perl.exe
    C:\Grid_home\bin\diagcollection.pl --collect

    Running the command mentioned earlier collects all the available data in the Oracle Grid Infrastructure Management repository, and creates a file using the format chmosData_host_name_time_stamp.tar.gz.

    For example: chmosData_stact29_20121006_2321.tar.gz.

  4. Run the command $ Grid_home/bin/diagcollection.pl --collect --chmos --incidenttime time --incidentduration duration  to limit the amount of data collected.

In the command mentioned earlier, the format for the --incidenttime argument is MM/DD/YYYY24HH:MM:SS and the format for the --incidentduration argument is HH:MM.

For example:
$ Grid_home/bin/diagcollection.pl --collect --crshome Grid_home
   --chmos --incidenttime 07/21/2013 01:00:00 --incidentduration 00:30