Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Serviceguard Extension for SAP on Linux Cluster Administration
Change Management
Chapter 5212
NOTE If the database package with HA NFS services is halted, you cannot log
in as <sid>adm unless you keep a local copy of the SAP binaries using
sapcpe.
To allow proper troubleshooting the level of information logged can be
adjusted by changing the parameter DEBUG_LEVEL in the sap.config
file. If problems with a Serviceguard package startup remain, a more
general debug mode can be activated by creating a “debug” file
touch ${SGCONF}/debug
All Serviceguard Extension for SAP on Linux packages on that cluster
node will now be in debug mode. If the file is created in the package
directory ${SGCONF}/<SID>, it will only turn on the debug mode for
packages in that directory.
The debug mode allows a SGeSAP/LX package start up (mounts the
appropriate storage volumes and enables virtual IP addresses) without
executing any of the SAP specific startups commands form within that
package. Service monitors will be started, but they will not report
failures as long as the debug mode is turned on.
With the debug mode enabled it then is possible to attempt manual
startups of the database and/or SAP software. All rules of manual
troubleshooting of SAP instances now apply. As the storage volumes for
this package have know been mounted it is possible to access the SAP
application work directories to check trace files. After the error has been
diagnosed the “debug” files has to be removed to resume normal
operation:
rm ${SGCONF}/debug
If the package still runs, all monitors will begin to work immediately and
the package failover mechanism is restored.