Component Level Debugging

You can enable debugging for Oracle Clusterware modules and their components, and for resources, by setting environment variables or by running crsctl set log commands, using the following syntax:

crsctl set {log | trace} module_name "component:debugging_level
[,component:debugging_level][,...]"

Run the crsctl set command as the root user, and supply the following information:

• module_name: The name of one of the following modules:

  • mdns: Multicast ___domain name server
  • gpnp: Grid Plug and Play service
  • css: Cluster Synchronization Services
  • crf: Cluster Health Monitor
  • crs: Cluster Ready Services
  • ctss: Cluster Time Synchronization Service
  • evm: Event Manager
  • gipc: Grid Interprocess Communication

• component: The name of a component for one of the modules. See Table E-73 for a list of all of the components.

• debugging_level: A number from 1 to 5 to indicate the level of detail you want the debug command to return, where 1 is the least amount of debugging output and 5 provides the most detailed debugging output. The default debugging level is 2.

The following commands show examples of how to enable debugging for the various modules:

• To enable debugging for Oracle Clusterware:

  crsctl set log crs "CRSRTI:1,CRSCOMM:2"
  

• To enable debugging for OCR:

  crsctl set log crs "CRSRTI:1,CRSCOMM:2,OCRSRV:4"
  

• To enable debugging for EVM:

  crsctl set log evm "EVMCOMM:1"
  

• To enable debugging for resources

  crsctl set log res "resname:1"
  

To obtain a list of components that can be used for debugging, run the crsctl lsmodules command, as follows:

crsctl lsmodules {mdns | gpnp | css | crf | crs | ctss | evm | gipc}

Table E-73 shows the components for the CRS, CSS, and EVM modules, respectively. Note that some component names are common between the CRS, EVM, and CSS daemons and may be enabled on that specific daemon. For example, COMMNS is the NS layer and because each daemon uses the NS layer, you can enable this specific module component on any of the daemons to get specific debugging information.

CRSUI
CRSCOMM
CRSRTI
CRSMAIN
CRSPLACE
CRSAPP
CRSRES
CRSCOMM
CRSOCR
CRSTIMER
CRSEVT
CRSD
CLUCLS
CSSCLNT
COMMCRS
COMMNS

CSSD
COMMCRS
COMMNS

EVMD
EVMDMAIN
EVMCOMM
EVMEVT
EVMAPP
EVMAGENT
CRSOCR
CLUCLS
CSSCLNT
COMMCRS
COMMNS

^Footnote 1 Obtain the list of CRS components using the crsctl lsmodules crs command.

^Footnote 2 Obtain the list of CSS components using the crsctl lsmodules css command.

^Footnote 3 Obtain the list of EVM components using the crsctl lsmodules evm command.

For example, use the following command to set debugging levels on specific cluster nodes, include the -nodelist keyword and the names of the nodes, as follows:

crsctl set log crs "CRSRTI:1,CRSCOMM:2" -nodelist node1,node2

Table E-74 describes the Cluster Synchronization Services modules.

Table E-75 describes the function of each communication (COMM) module.

Table E-76 describes the functions performed by each CRS module.

Using the crsctl set log crs command, you can debug the OCR components listed in Table E-77. The components listed in Table E-77 can also be used for the Oracle Local Registry (OLR) except for OCRMAS and OCRASM. You can also use them for OCR and OLR clients, except for OCRMAS and OCRSRV. Some OCR and OLR clients are OCRCONFIG, OCRDUMP, and so on.

Table E-78 describes the OCR tool modules.

You can enable debugging for Oracle Clusterware resources by running the crsctl set log command, using the following syntax:

crsctl set log res "resource_name=debugging_level"

Run the crsctl set log command as the root user, and supply the following information:

• resource_name: The name of the resource to debug.

• debugging_level: A number from 1 to 5 to indicate the level of detail you want the debug command to return, where 1 is the least amount of debugging output and 5 provides the most detailed debugging output. The default debugging level is 2.

To obtain a list of resources that can be used for debugging, run the crsctl status resource command.

Example

To generate a debugging log for the VIP resource on node1, issue the following command:

crsctl set log res "ora.node1.vip:1"

My Oracle Support may ask you to enable tracing to capture additional information. Because the procedures described in this section may affect performance, only perform these activities with the assistance of My Oracle Support.

You can enable tracing for Oracle Clusterware resources by running the crsctl set trace command, using the following syntax:

crsctl set trace module_name "component_name=tracing_level,..."

Run the crsctl set trace command as the root user, and supply the following information:

• module_name: The name of one of the following modules:

  • mdns: Multicast ___domain name server
  • gpnp: Grid Plug and Play service
  • css: Cluster Synchronization Services
  • crf: Cluster Health Monitor
  • crs: Cluster Ready Services
  • ctss: Cluster Time Synchronization Service
  • evm: Event Manager
  • gipc: Grid Interprocess Communication

• component_name: The name of the component for one of the modules. See Table E-73 for a list of components.

• tracing_level: A number from 1 to 5 to indicate the level of detail you want the trace command to return, where 1 is the least amount of tracing output and 5 provides the most detailed tracing output.

For example, you can use the following command to generate a trace file for Cluster Synchronization Services:

crsctl set trace "css=3"