Dynamic Debugging

You can use crsctl set log commands as the root user to enable dynamic debugging for Cluster Ready Services (CRS), Cluster Synchronization Services (CSS), and the Event Manager (EVM), and Clusterware subcomponents. 

Debugging information remains in the Oracle Cluster Registry (OCR) for use during the next startup. 

You can also enable debugging for resources. The crsctl lsmodules crs| css|evm commands are used to list the module’s components that can be used for debugging. The example in the slide lists the ones for CSS. Nondefault logging levels are best interpreted with access to the source code and are designed for Oracle Support needs. When asked by Oracle Support, you can use commands such as the following to enable additional logging:

The example below shows you how to dynamically enable additional logging (level 5) for the following CRS components: CRSEVT, CRSAPP, CRSTIMER, and CRSRES.

$ crsctl lsmodules css

# crsctl set log crs "CRSEVT=1","CRSCOMM=2","CRSTIMER=5"

# crsctl set log res "myResource1=1"