Managing Serviceguard Extension for SAP Version B.05.10, September 2010

All directories below /export have an equivalent directory whose fully qualified path comes
without this prefix. These directories are managed by the automounter. NFS file systems get
mounted automatically as needed. Servers outside of the cluster that have External Dialog
Instances installed are set up in a similar way. Refer to /etc/auto.direct for a full list of
automounter file systems of SGeSAP.
It enhances the security of the installation if the directories below /export are exported without
root permissions. The effect is, that the root user cannot modify these directories or their contents.
With standard permissions set, the root user cannot even see the files. If changes need to be done
as root, the equivalent directory below /export on the host the package runs on can be used
as access point.
If the system is badly configured, it might be possible that the system hangs if a logon is attempted
as <sid>adm user. The reason for this is, that /usr/sap/<SID>/SYS/exe is part of the path
of <sid>adm. Without local binaries this directory links to /sapmnt/<SID> which in fact is
handled by the automounter. The automounter cannot contact the host belonging to the relocatable
address that is configured because the package is down. The system hangs. To avoid this, always
keep local copies of the executables.
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 there is a verbose package startup log in the package directory.
It should be checked first in case of trouble. The level of information can be adjusted by changing
the parameter LOGLEVEL in the sap.config file. If problems with package startup remain, a
general debug mode can be activated by creating a file:
touch /var/adm/cmcluster/debug — debug mode for all modular SGeSAP package
touch /var/adm/cmcluster/debug - <packagename> — debug mode for the SGeSAP
modules of package <packagename>
touch /etc/cmcluster/debug - debug mode for all legacy SGeSAP packages
touch /etc/cmcluster/ <SID>/debug - debug mode for the SGeSAP legacy SGeSAP
packages of SAP system<SID>
The whole SGeSAP node will now be in debug mode. If the file is created in the package directory
/etc/cmcluster/<SID>, it will only turn on the debug mode for packages in that directory.
The debug mode allows package start up to the level of SAP specific steps. All instance startup
attempts will be skipped. Service monitors will be started, but they don't report failures as long
as the debug mode is turned on.
In this mode it is possible to attempt manual startups of the database and/or SAP software. All
rules of manual troubleshooting of SAP instances apply now. It is possible to access the application
work directories to have a look at the trace files. After removal of the error cause it is vital to
remove the debug file that got created:
If the package still runs, all monitors will begin to work immediately and the package failover
mechanism is restored.
SAP Software Changes
During installation of the SGeSAP Integration for SAP releases with kernel < 7.0, SAP profiles
are changed to contain only relocatable IP-addresses for the database as well as the Central
Instance. You can check this using transaction RZ10. In the DEFAULT.PFL these entries are
altered:
SAPDBHOST= <relocatible_db_name>
rdisp/mshost= <relocatible_ci_name>
rdisp/vbname= <relocatible_ci_name>_<SID>_<INR>
rdisp/enqname= <relocatible_ci_name>_<SID>_<INR>
178 SGeSAP Cluster Administration