Managing HP Serviceguard Extension for SAP for Linux, December 2013

Table 19 DB Configuration Files
Fields/DescriptionPathFile(s)DB type
(HOST = hostname)$ORACLE_HOME/network/admintnsnames.oraOracle
/oracle/client/<vers>/network/
admin
/sapmnt/<SID>/profile/oracle
(HOST = hostname)$ORACLE_HOME/network/adminlistener.ora
Nodename in xuser list output. If
necessary recreate userkeys with xuser …
-n vhost
/home/<sid>adm.XUSER.62MaxDB
Fourth column of master and query entry
for each server
$SYBASEinterfacesSybase
Variable dbs_syb_server/home/<sid>admdbenv.*
Second Column/db2/db2<dbsid>/sqllibdb2nodes.cfgDB2
NOTE: The db2nodes.cfg contains the physical hostname even though the installation is
executed by using a virtual hostname.
DB2: Disable fault monitor
The DB2 installation configures the fault monitor to startup at boot time. The fault monitor runs out
of the instance directory and keeps the filesystem busy when halting the package. The command
to disable the fault monitor is:
/db2/db2<sid>/sqllib/bin/db2fmcu –d
DB2: Configure db2nodes.cfg
The db2nodes.cfg file contains either a physical host or the virtual host of the database. Both
alternatives have implications on the setup.
When using a physical host, ensure that db2nodes.cfg resides on each physical host in the
cluster. HP recommends that you use physical host. The db2nodes.cfg file must not be located
on the shared filesystem. Instead, it must be located on a local filesystem. The db2nodes.cfg on
the shared filesystem must be a softlink to the local version.
For example:
A dbnodes.cfg link in the database instance directory points to a db2nodes file. The
<dbsid>.cfg in the local or db2 directory. Each cluster-node has a local copy with different
contents.
db2nodes<dbsid>.cfg on nodeA0 nodeA 0
db2nodes<dbsid>.cfg on nodeB0 nodeB 0
You can create the link by using the following command:
ln -s /db2/db2nodes.<dbsid>.cfg /db2/db2<dbsid>/sqllib/db2nodes.cfg
When configuring a virtual host into the shared db2nodes.cfg, the DB2 database considers this
node as remote because this node is not equal to the local hostname. DB2 uses a remote
communication mechanism to start and stop the database. The DB2 DB2RSHCMD configuration
parameter determines the communication mechanism. It can be either rsh or ssh. The default
value is rsh.
When you use rsh for the virtual host configuration, the remote access commands must be installed
and configured. Password-less rsh must be allowed for db2<dbsid> user from the virtual host.
68 Clustering SAP Netweaver using SGeSAP packages