Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Database Configuration
Chapter 3 173
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.
MD930 MaxDB Database Step:
Create additional links in /sapdb/<DBSID> on the primary node. For
example:
su - sqd<sid>
ln -s .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln -s .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
MD940 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.
MD950 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 MaxDB database. The XUSER content needs to be adopted to the
relocatable IP the MaxDB 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 - <lcsid>adm
dbmcli -ux SAP<SID>, <password> -ul
This command produces a list of MaxDB user keys that may be mapped to
the MaxDB 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><DBSID><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.