Wednesday, April 16, 2008

CRS - Tracing and logging

1.Enable debugging for the Oracle Clusterware:
crsctl debug log crs "CRSRTI:1,CRSCOMM:2"

2.Enable debugging for EVM is:
crsctl debug log evm "EVMCOMM:1"

3.Enable debugging for resources :
crsctl debug log res "resname:1"

* You do not have to be the root user to run the crsctl command with the
lsmodules option.

4. set ORA_CRSDEBUG_ALL level

Valid values for level are 1, which provides the least amount of debugging output, and 5 which provides the most debugging output.

5.Command to obtain the list of modules that one can debug where module is crs, evm, or css:
crsctl lsmodules module

6.Command to enable tracing for a specific sub-module where modulename is the name of the sub-module for which you want to enable tracing:
set ORA_CRSDEBUG_modulename

7.Diagnostics Collection Script

* run this script as the root user
6. The location crs alert log on UNIX-based systems is


where CRS_Home is the name of the location of the Oracle Clusterware.

7.Commands to enable resource debugging using the following syntax:
crsctl debug log res ""

This has the effect of setting the environment variable USER_ORA_DEBUG, to 1, before running the start, stop or check action scripts for the resource.
* You must run this crsctl command as the root user.

8. Checking the Health of the Clusterware

i.crsctl check crs
This command displays the status of the CSSD, EVMD, and CRSD processes.

ii. crsctl check daemon

Command to determine the health of individual daemons where daemon is crsd, cssd or evmd.

9. Log file locations

(a) Log files for the CRSD process (crsd) :CRS_home/log/hostname/crsd

(b) Oracle Cluster Registry (OCR) Log Files:CRS_Home/log/hostname/client

(c) Cluster Synchronization Services (CSS) Log Files:CRS_Home/log/hostname/cssd

(d) Event Manager (EVM) Log Files:CRS_Home/log/hostname/evmd

(e) RACG Log Files:


No comments:

Post a Comment