Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

Make sure that /usr/spool exists as a symbolic link to / var/spool on all cluster nodes on which the
database can run.
MaxDB Database Step: MD950
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.
For all previously listed user keys run the following command as <sid>adm Administrator:
# dbmcli -U <user_key>
quit exits the upcoming prompt:
# dbmcli on <hostname> : <DBSID>> quit
<hostname>should be relocatable. If it is not, the XUSER mapping has to be recreated.
For example:
# dbmcli -d <DBSID> -n <reloclc_s> -us <user>,<passwd> -ux SAP<SID>,SAP -uk
<user_key>
Entries of the form <num><DBSID><reloclc_s> could be created by omitting the -ukoption.
NOTE: Refer to the SAP documentation to learn more about the dbmcli syntax.
After recreation always check the connection:
# dbmcli -U <user_key>
# dbmcli on <reloclc_s> : <DBSID>> quit
MaxDB Database Step: MD960
Distribute the XUSER mappings by distributing the file /home/<sid>adm/.XUSER.<version> to all
database package nodes.
SAP WAS System Configuration
This section describes some required configuration steps that are necessary for SAP to become compatible
to a cluster environment.
NOTE: The following configuration steps do not need to be performed if the SAP System was installed
using virtual IPs. The steps are only required to make a non-clustered installation usable for clustering.
• SAP ABAP Engine specific configuration steps
• SAP J2EE Engine specific configuration steps
SAP ABAP Engine specific configuration steps
Logon as <sid>adm on the primary node on which the Central Instance has been installed. The appropriate
Serviceguard package should still run on this host in Serviceguard debug mode.
SAP WAS System Configuration 97