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

When using raw devices, the database installation on the primary node might have modified
the access rights and owner of the device file entries where the data and logs reside.
These devices were changed to be owned by user sdb, group sdba. These settings also have to
be applied on the secondary, otherwise the database will not change from ADMIN to ONLINE
state.
Additional Steps for DB2
DB2 Database Step: DB1000
If environment files exist in the home directory of the DB2 instance user for the primary node, create
additional links for any secondary.
Example:
su - db2<sid>
ln -s .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln -s .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
DB2 Database Step: DB1010
Adapt db2nodes.cfg to reflect package setup.
The DB2 installation creates a dbnodes.cfg (/db2/<db2instance>/sqllib) containing the
name of the physical host, where the installation took place. With the instance directory being
shared, db2nodes.cfg is shared too.
There are two ways to adapt it to the cluster.
1. Replace db2nodes.cfg on the shared filesystem by a link pointing to a copy residing in a
local file system on each clusternode. Enter the local hostnames on each clusternode.
2. Use the hostname for the virtual IP—or the virtual IP itself—of the ServiceGuard database
package.
If anything else than the local hostname is used in db2nodes.cfg (option 1), DB2 will use
remote communication mechanisms to startup the database mananger. ssh can be configured to
be used instead of remsh. In this case the key of each physical hosts configured to run the DB
package has to be stored with the hostname and the IP of the relocateable address in ssh
known_hosts file (either systemwide or for db2<dbsid> user only).
DB2 Database Step: DB1020
Disable fault monitor coordinator daemon.
The DB2 installation may have configured the fault monitor coordinator daemon by adding the
line fmc:234:respawn:/db2/db2<sid>/db2_software/bin/db2fmcd #DB2 Fault
Monitor Coordinator to /etc/inittab. This daemon keeps the DB instance file system
busy and should be stopped and disabled by running the command
/db2/db2<sid>/sqllib/bin/db2fmcu –d.
DB2 Database Step: DB1030
Adapt partition host(s) in db2nodes.cfg.
The DB2 installation creates a dbnodes.cfg (/db2/<db2instance>/sqllib) file containing
the name of the physical host and where the installation took place. There are two ways to adapt
it to the cluster.
1. Replace db2nodes.cfg on the shared filesystem by a link pointing to a copy residing in a
local filesystem on each clusternode. Enter the local hostnames on each clusternode.
2. Use the virtual IP, or the hostname of the virtual IP that is configured in the Serviceguard
database package.
102 Step-by-Step Cluster Conversion