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

Create a symbolic link that acts as a hook that informs SAP software where to find the liveCache monitoring
software to allow the prescribed interaction with it.
ln -s ${SGCONF}/<LCSID>/saplc.mon /sapdb/<LCSID>/db/sap/lccluster
liveCache installation Step: LC215
For the following steps the SAPGUI is required. Logon to the APO central instance as user SAP*. Start
transaction /nlc10 and enter LCA for the logical connection.
/nlc10 -> Logical connection -> LCA -> liveCache -> Create/Change/Delete
Connection
Change liveCache server name to the virtual IP name for the liveCache (<relocls_s) and save it. Change
the liveCache instance name to <LCSID>. Redo the above steps for LDA.
APO Setup Changes
Running liveCache within a Serviceguard cluster package means that the liveCache instance is now configured
for the relocatable IP of the package. This configuration needs to be adopted in the APO system that connects
to this liveCache.
liveCache installation Step: GS220
Run SAP transaction LC10 and configure the logical liveCache names LCA and LCD to listen to the relocatable
IP of the liveCache package.
liveCache installation Step: GS230
Do the following:
1. Configure the XUSER file in the APO user home and liveCache user home directory. If a .XUSER file
does not already exist, you must create it.
2. The XUSER file in the home directory of the APO administrator and the liveCache administrator keeps
the connection information and grant information for a client connecting to liveCache. The XUSER
content needs to be changed to the relocatable IP the liveCache is running on.
▲ To list all mappings in the XUSER file, run the following command as <lcsid>adm of the APO user:
su - <lcsid>adm
dbmcli -ux SAPR3,SAP -ul
For liveCache 7.6 or higher:
su - <lcsid>adm
dbmcli -ux SAP<LCSID>,<password> -ul
This command produces a list of MaxDB user keys that may be mapped to the liveCache database schema
via a local hostname. Keys commonly created by SAP include c, w and DEFAULT. If a mapping was created
without specifying a key, entries of the form <num><LCSID><hostname>, e.g. 1LC1node1 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.
Run the following command as APO Administrator:
dbmcli -U <user_key>
quit exits the upcoming prompt:
dbmcli on <hostname> : <LCSID>> quit
<hostname> should be relocatable. If it is not, the XUSER mapping has to be recreated. Example:
mv .XUSER.62 .XUSER.62.ORG
The following commands require ksh for them to work.
DEFAULT key
dbmcli -n <reloclc_s> -d <LCSID> -u SAP<LCSID>,SAP -uk DEFAULT -us\
SAP<LCSID>,SAP -up SQLMODE=SAPR3; TIMEOUT=0; ISOLATION=0;
COLD key
116 SAP Supply Chain Management