Oracle^® Solaris Cluster Data Service for Oracle Communications ASAP Guide

Debugging the Oracle Communications ASAP

The Oracle Communications ASAP has an extension property named debug_level. This extension property enables you to activate and deactivate debugging for Oracle Communications ASAP resources.

This property indicates the level to which debug messages for the ORCL.asap resources are logged. When the debug level is increased, more debug messages are written to the terminal, the console, and the system log /var/adm/messages as follows:

0

No debug messages

1

Function Begin and End messages

2

All debug messages and function Begin and End messages

3

Prints all debug messages to the debug log file /var/cluster/logs/DS/ORCL.asap/message_log_$resource_name

where resource_name is the name of the ASAP resource

Perform the following steps to ensure that messages appear in the system log:

1. Edit the /etc/syslog.conf file and ensure that the debug level is set.

   *.err;kern.debug;daemon.debug;mail.crit /var/adm/messages

2. Disable the system log.

   # svcadm disable system-log

3. Enable the system log.

   # svcadm enable system-log

4. To activate debugging, set the property debug_level to level 2.

   # clresource set -p debug_level=2 asap-app-rs

How to Deactivate Debugging for Oracle Communications ASAP

1. Edit the /etc/syslog.conf file on the appropriate node to change daemon.debug to daemon.notice.
2. Determine if debugging for the Oracle Communications ASAP is not active.

   # grep daemon /etc/syslog.conf
   *.err;kern.debug;daemon.notice;mail.crit /var/adm/messages
   *.alert;kern.err;daemon.err operator

3. Restart the syslogd daemon.

   # svcadm refresh svc:/system/system-log:default

4. Set the property debug_level to level 0.

   # clresource set -p debug_level=0 asap-app-rs