Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration
Change Management
Chapter 6 299
If remote shell access is used, never delete the mutual .rhosts entries of
the root user and <sid>adm on any of the nodes. Never delete the secure
shell setup in case it is specified for SGeSAP.
Entries in /etc/hosts, /etc/services, /etc/passwd or /etc/group
should be kept unified across all nodes.
If you use an ORACLE database, be aware that the listener
configuration file of SQL*Net V2 is kept in a local copy as
/etc/listener.ora by default, too.
Files in the following directories and all subdirectories are typically
shared:
/usr/sap/<SID>/DVEBMGS<INR>
/export/usr/sap/trans (except for stand-alone J2EE)
/export/sapmnt/<SID>
/export/informix or /oracle/<SID> or /export/sapdb
Chapter Two can be referenced for a full list. These directories are only
available on a host if the package they belong to is running on it. They
are empty on all other nodes. Serviceguard switches the directory
content to a node with the package.
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.