Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Database Configuration
Chapter 3 185
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 -uk option.
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
SD960 MAXDB Database Step:
Distribute the XUSER mappings by distributing the file
/home/<sid>adm/.XUSER.<version> to all database package nodes.
SD965 MAXDB Database Step:
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.