Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Database Configuration
Chapter 3184
Additional Steps for MAXDB
Logon as root to the primary host of the database where the db or dbci
package is running in debug mode.
SD930 MAXDB Database Step:
If environment files exist in the home directory of the MAXDB user on
the primary node, create additional links for any secondary. For example:
su - sqd<sid>
ln -s .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln -s .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
SD940 MAXDB Database Step:
Make sure that /usr/spool exists as a symbolic link to /var/spool on
all cluster nodes on which the database can run.
SD950 MAXDB Database Step:
Configure the XUSER file in the <sid>adm user home directory.
The XUSER file in the home directory of the SAP Administrator keeps the
connection information and grant information for a client connecting to
the SAPDB database. The XUSER content needs to be adopted to the
relocatable IP the SAPDB RDBMS is running on. To list all mappings in
the XUSER file, run the following command as <sid>adm :
# dbmcli -ux SAPR3,SAP -ul
for MAXDB 7.6:
su - <sid>adm
dbmcli -ux SAP<SID>, <password> -ul
This command produces a list of SAPDB user keys that may be mapped to
the SAPDB database schema via a local hostname. SAP created keys
commonly include c, w and DEFAULT. If a mapping was created without
specifying a key, entries of the form <num><SAPDBSID><hostname>, e.g.
1SDBrhpcc072 exist. These will only work on one of the cluster hosts.
To find out if a given user key mapping <user_key> works throughout
the cluster, the relocatable address should be added to the primary host
using cmmodnet -a.