In Oracle® Clusterware Administration and Deployment Guide 11g Release 2 (11.2), the section, Enabling Additional Tracing for Oracle Clusterware High Availability, says that:
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 Oracle Support.
Enabling Debugging for Oracle Clusterware Resources
You can enable debugging for Oracle Clusterware resources by issuing crsctl set log and crsctl set trace commands, using the following syntax:
crsctl set {log | trace} resource "resource_name=debugging_level"
Run the crsctl set 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.
You can dynamically change the debugging level in the crsctl command or you can configure an initialization file for changing the debugging level, as described in "Creating an Initialization File to Contain the Debugging Level".
Note:
You must run this crsctl set log or crsctl set trace command as the root user.
To obtain a list of resources that can be used for debugging, run the crsctl status resource command.
Example 1
To generate a debugging log for the VIP resource on node1, issue the following command:
crsctl set log resource "ora.node1.vip:1"
Example 2
To generate a trace file for a SCAN listener, use the following command:
crsctl set trace resource "ora.LISTENER_SCAN1.lsnr=3"
The section, Creating an Initialization File to Contain the Debugging Level, says that:
This section describes how to specify the debugging level in an initialization file. This debugging information is stored for use during the next startup.
For each process to debug, you can create an initialization file that contains the debugging level.
The initialization file name includes the name of the process that you are debugging (process_name.ini). The file is located in the Grid_home/log/host_name/admin/ directory. For example, the name for the CLSCFG debugging initialization file on node1 would be:
Grid_home/log/node1/admin/clscfg.ini
You can also use an initialization file when using OCR utilities. The initialization file for ocrconfig, ocrdump, and ocrcheck is:
Grid_home/srvm/admin/ocrlog.ini
The format of the initialization file is as follows:
mesg_logging_level=2
comploglvl="OCRAPI:0;OCRSRV:0"
comptrclvl="OCRAPI:0;OCRSRV:0"
You can specify component names, logging, and tracing levels.