Oracle Clusterware Diagnosis - Expert Oracle RAC Performance Diagnostics and Tuning - page 557

Depending on the module and the functionality provided by it, the debug operation can be performed at
different levels. Based on the usefulness of the output provided, setting the operation to level two would provide the
most useful information. Outputs of several of these modules are illustrated in the following:

b. Debug all CRS application-level activity. The debug output is generated using the

following:

[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl get log crs CRSAPP
Get CRSD Module: CRSAPP Log Level: 0
[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl set log crs CRSAPP:2
Set CRSD Debug Module: CRSAPP Level: 2
[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl get log crs CRSAPP
Get CRSD Module: CRSAPP Log Level: 0
The preceding output is the debug information for the CRS application activity. The output provides the
frequency of the context construction and destruction.

c. Debug all CRS timer activity. The debug output is generated using the following:

[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl get log crs CRSTIMER
Get CRSD Module: CRSTIMER Log Level: 0
[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl set log crs CRSTIMER:2
Set CRSD Debug Module: CRSTIMER Level: 2
[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl get log crs CRSTIMER
Get CRSD Module: CRSTIMER Log Level: 2
The output from this module generates scheduler-related information for all the resources executed by the CRS
on the cluster.

d. Debug all CRS log activity. The debug output is generated using the following:

[root@ssky3l11p1 ~]# /u01/app/12.1.0/grid/bin/crsctl set log crs CRSD:3
Set CRSD Debug Module: CRSD Level: 3
Oracle Clusterware has several sub-components (one being the event manager) that are modules and perform
specific actions on behalf of the cluster services. The crsctl utility provides several options for debugging the
activities performed by these modules and sub-components.
A few of the EVM-related modules and their functionalities are listed in Table 16-4 . Debug data for these modules
can be generated similar to the CRS modules discussed earlier.