User's Guide

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: SD950
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.
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> : <SAPDBSID>> quit
<hostname>should be relocatable. If it is not, the XUSER mapping has to be recreated.
For example:
# dbmcli -d <SAPDBSID> -n <reloclc_s> -us <user>,<passwd> \ -ux SAPR3,SAP -uk
<user_key>
Entries of the form <num><SAPDBSID><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> : <SAPDBSID>> quit
MAXDB Database Step: SD960
Distribute the XUSER mappings by distributing the file /home/<sid>adm/.XUSER.<version> to all
database package nodes.
MAXDB Database Step: SD965
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.
SAP Application Server Configuration
This section describes some required configuration steps that are necessary for SAP to become compatible
to a cluster environment. 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 Application Server Configuration 87