Oracle Clusterware Main Log Files
Oracle Clusterware uses a unified log directory structure to consolidate the Oracle Clusterware component log files. This consolidated structure simplifies diagnostic information collection and assists during data retrieval and problem analysis.
- CRS logs are in $ORA_CRS_HOME/log/<hostname>/crsd/. The crsd.log file is archived every 10 MB (crsd.l01, crsd.l02, …).
- CSS logs are in $ORA_CRS_HOME/log/<hostname>/cssd/. The cssd.log file is archived every 20 MB (cssd.l01, cssd.l02, …).
- EVM logs are in $ORA_CRS_HOME/log/<hostname>/evmd.
- Depending on the resource, specific logs are in $ORA_CRS_HOME/log/<hostname>/racg and in $ORACLE_HOME/log/<hostname>/racg. In that last directory, imon_<service>.log is archived every 10 MB for each service. Each RACG executable has a subdirectory assigned exclusively for that executable. The name of the RACG executable subdirectory is the same as the name of the executable.
- SRVM (srvctl) and OCR (ocrdump, ocrconfig, ocrcheck) logs are in $ORA_CRS_HOME/log/<hostname>/client/ and in $ORACLE_HOME/log/<hostname>/client/.
- The important Oracle Clusterware alerts can be found in alert<nodename>.log present in the $ORA_CRS_HOME/log/<hostname> directory.
Diagnostics Collection Script
Use the diagcollection.pl script to collect diagnostic information from an Oracle Clusterware installation. The diagnostics provide additional information so that Oracle Support can resolve problems. This script is located in $ORA_CRS_HOME/bin. Before executing the script, you must be logged in as the root user, and you must set the following environment variables: ORACLE_BASE, ORACLE_HOME, ORA_CRS_HOME, HOSTNAME.
When invoked with the –collect option, the script generates, in the local directory, the four files. Mainly, basData.tar.gz contains log files from the $ORACLE/BASE/admin directory. The crsData.tar.gz file contains log files from the $ORA_CRS_HOME/log/<hostname> directory. The ocrData.tar.gz files contains the results of an ocrdump, ocrcheck, and the list of ocr backups. The oraData.tar.gz file contains log files from the $ORACLE_HOME/log/<hostname> directory. If you invoke the script with the -collect option, and you already have the four files generated from a previous run in the local directory, the script asks you if you want to overwrite the existing files.
You can also invoke the script with the –clean option to clean out the files generated from a previous run in your local directory. Alternatively, you can invoke the script to just capture a subset of the log files. You can do so by adding extra options after the –collect option: -crs for collecting Oracle Clusterware logs, -oh for collecting ORACLE_HOME logs, -ob for collecting ORACLE_BASE logs, or –all for collecting all logs. The –all option is the default. The –coreanalyze option allows you to extract to text files only core files found in the generated files.
Example:
$ su -
# export ORACLE_HOME=/u01/oracle/product/11.1.0/db
# export ORA_CRS_HOME=/u01/oracle/product/crs
# export ORACLE_BASE=/u01/oracle/product
# $ORA_CRS_HOME/bin/diagcollection.pl -crshome=$ORA_CRS_HOME --collect