Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
Information in this document applies to any platform.
Oracle Clusterware

Goal

To document the logs that should be uploaded for diagnosing Oracle Clusterware issue.

For more information about diagcollection, check out "diagcollection.sh -help"

This note will be obsolete in future, it's strongly recommended to use tfa to prune and collect files from all nodes:

note 1513912.1 - TFA Collector - Tool for Enhanced Diagnostic Gathering

Solution

Linux/UNIX 11gR2

1. Execute the following as root user:

# script. /tmp/diag.log
# id
# env
# cd
# $GRID_HOME/bin/diagcollection.sh
# exit

The following .gz files will be generated in the current directory and need to be uploaded along with /tmp/diag.log:

crsData_.tar.gz,
ocrData_.tar.gz,
oraData_.tar.gz,
coreData_.tar.gz (only --core option specified)
os_.tar.gz

Please ensure all above information are provided from all the nodes.

Linux/UNIX 10gR2/11gR1

1. Execute the following as root user:

# script. /tmp/diag.log
# id
# env
# cd
# export CH=
# export ORACLE_HOME=
# export HOSTNAME=
# $OCH/bin/diagcollection.pl -crshome=$OCH --collect
# exit

The following .gz files will be generated in the current directory and need to be uploaded along with /tmp/diag.log:

crsData_.tar.gz,
ocrData_.tar.gz,
oraData_.tar.gz,
coreData_.tar.gz (only --core option specified)

2. For 10gR2 and 11gR1, if getting an error while running root.sh, please collect /tmp/crsctl.*

Please ensure all above information are provided from all the nodes.

Windows 11gR2:

set GRID_HOME=<11gR2_GRID_HOME>
%GRID_HOME%\perl\bin\perl %GRID_HOME%\bin\diagcollection.pl --collect

The following .zip files will be generated in the current directory and need to be uploaded:

crsData_.zip,
ocrData_.zip,
oraData_.zip,
coreData_.zip (only --core option specified)

Windows 10gR2/11gR1

set ORACLE_HOME=
set CH=
set ORACLE_BASE=
$OCH%\perl\bin\perl %OCH%\bin\diagcollection.pl --collect

CVU

Depend on whether CRS/GI is configured or not, run either one of the following as clusterware user:

(a) GI/CRS has been installed

$ script. /tmp/cluvfy.log
$ $GRID_HOME/bin/cluvfy stage -pre crsinst -n -verbose
$ $GRID_HOME/bin/cluvfy stage -post crsinst -n all -verbose
$ exit

(b) GI/CRS has not been installed

run runcluvfy.sh from the installation media or download from OTN http://www.oracle.com/technetwork/products/clustering/downloads/index.html
set the environment variables CV_HOME to point to the cvu home, CV_JDKHOME to point to the JDK home and an optional CV_DESTLOC pointing to a writeable area on all nodes (e.g /tmp/cluvfy)

$ cd $CV_HOME/bin
$ script. cluvfy.log
$ cluvfy stage -pre crsinst -n
$ exit

For more information about CVU, refer to note 986822.1 and note 316817.1

diagcollection options

o To collect only a subset of logs, --adr together with --beforetime and --aftertime can be used, i.e.:

# $GRID_HOME/bin/diagcollection.sh --adr /tmp/collect -beforetime 20120218100000 -aftertime 20120218050000

This command will copy all logs contain timestamp 2012-02-18 05:00 - 10:00 to /tmp/collect directory. Time is specified with YYYYMMDDHHMISS24 format. --adr points to a directory where the logs are copied to.

o From 11.2.0.2 onwards, Cluster Health Monitor(CHM/OS) note 1328466.1 data can also be collected, i.e.:

# $GRID_HOME/bin/diagcollection.sh --chmos --incidenttime 02/18/201205:00:00 --incidentduration 05:00

This command will collect data from 2012-02-18 05:00 to 10:00 for 5 hours. incidenttime is specified as MM/DD/YYYY24HH:MM:SS, incidentduration is specified as HH:MM.

Scalability RAC Community

To discuss this topic further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Scalability RAC Community.

References

NOTE:314422.1 - Remote Diagnostic Agent (RDA) - Getting Started
NOTE:785907.1 - diagcollection.pl errors "Mandatory argument 'crshome' is missing"

NOTE:289690.1 - Data Collecting for Troubleshooting Oracle Clusterware (CRS or GI) And Real Application Cluster (RAC) Issues