Managing Serviceguard Extension for SAP Version B.05.10, September 2010

It should not reply any match on all nodes. Otherwise, refer to the SAP documentation how to
change instance IDs for the relevant instance type. It might be simpler to reinstall on of the
conflicting instances.
Installation Step: IS065
If local executables are created (refer to step IS050) and failover nodes have no internal application
server with local executables installed, distribute the directory tree /usr/sap/<SID>/SYS
from the primary node.
Do not use rcp(1), it will follow all links and copy files from the shared disks that are not
needed.
For example, on the primary node:
cd /usr/sap/<SID>/SYS
find . -depth -print | cpio -o >/tmp/SYS.cpio
Copy the file over to secondary nodes. On each alternate node:
su - <sid>adm
mkdir -p /usr/sap/<SID>/SYS
cd /usr/sap/<SID>/SYS
cpio -id </tmp/SYS.cpio
exit
Cluster Node Synchronization
Repeat the steps in this section for each node of the cluster that is different than the primary.
Logon as root to the system where the SAP Central Instance is installed (primary host) and
prepare a logon for each of its backup hosts if not already available.
Installation Step: IS070
Open the groupfile, /etc/group, on the primary side.
If any of the groups listed in Table 3-2 — “Groupfile File Groups” exist on the primary node and
they do not exist on the backup node, copy them from the primary node to the backup node. If
any group exists, verify that it has the same GID on both the primary and backup nodes. Merge
the group members lists.
Table 3-2 Groupfile File Groups
Group membersGIDGroups
sapsys
sapinst
sdba
oper
db<dbsid>adm
db<dbsid>mnt
db<dbsid>ctl
db<dbsid>mon
Installation Step: IS080
Open the password file, /etc/passwd, on the primary side.
If any of the users listed in Table 3-3 “Password File Users” exist on the primary node, recreate
them on the backup node. Assign the users on the backup nodes the same user and group ID as
the primary nodes.
56 Step-by-Step Cluster Conversion