Database Reference
In-Depth Information
If the node is evicting due to some mysterious network heartbeat (NHB) issues and the default information
is not sufficient to diagnose the cause, you can increase the CSSD tracing level to a higher number. To troubleshoot
NHB-related issues, you can set the log level to 3 as the root user, as shown in the following example:
$ crsctl set log css ocssd=4
The following examples disable the tracing:
$ crsctl set log crs crsmain=0
$ crsctl set log res ora.rondb.db:0
$ crsctl set log res ora.crs:0
-init
The
-init
flag must be specified while modifying the debug mode of a key cluster daemon process. To list the
current logging and tracing levels of a particular component and its subcomponents, use the following example:
$crsctl stat res ora.crsd -init -f |grep LEVEL
Tracing levels also can be set by specifying the following environmental variables on the local node (however,
you need to restart the cluster on the local node to enforce the logging/tracing changes):
$ export ORA_CRSDEBUG_ALL=1 --sets debugging level 1 to all modules
$ export ORA_CRSDDEBUG_CRS=2 --sets debugging level 2 to CRS module
OS Level Tracing
You should also be able to use the OS-specific tracing utility (
gdb, pstack, truss, strace
, and so on) to dump the
debug information of an OS process. The following exercise demonstrates the procedure:
Identify the process ID that you want to set the OS level tracing; for example:
$ps -ef |grep oraagent.bin
Attach the process with the OS-specific debug utility; for example, on the HP-UX platform:
$pstack /u00/app/12.1.0/grid/bin/orarootagent.bin 4558
You can then provide the information to Oracle Support or consult your OS admin team to help you identify any
issues that were raised from the OS perspective.
Diagnose cluvfy Failures
The
cluvfy:runCluvfy
utility can be used to accomplish pre-component and post-component verification checks,
including OS, network, storage, overall system readiness, and clusterware best practices. When the utility fails
to execute for no apparent reason, and in addition the
-verbose
argument doesn't yield sufficient diagnostic
information about the issue, enable the debugging mode for the utility and re-execute the command to acquire
adequate information about the problem. The following example demonstrates enabling debugging mode:
$ export SRVM_TRACE=true
Rerun the failed command after setting the preceding environmental variable. A detailed output file will be
generated under the
$GRID_HOME/cv/log
location, which can be used to diagnose the real cause. When debug settings
are modified, the details are recorded in the OCR file and the changes will be affected on that node only.
