Managing Serviceguard Extension for SAP Version B.05.10, December 2012

directory. For each additional file in the central executable directory it needs to contain a line with
the following format:
<filename> local_copy check_exist
SAP also delivers template file lists within the central executable directory. These files have a
filename of the format *.lst. The following files override sapcpeft: instance.lst,
instancedb.lst, tools.lst, and inhouse.lst. Either the *.lst files should get removed,
or they should be used instead of sapcpeft. In this case, they need to be changed to include all
executables and libraries.
If the local executable directory only holds links, sapcpe is not configured correctly. It is not an
option to manually copy the local executables in this case. The next instance restart would replace
the local copies with symbolic links.
For latest information on how to utilize sapcpe, refer to the SAP online documentation.
Installation Step: IS060
Clustered SAP Instances must have instance numbers that are unique for the whole cluster .
For a clustered instance with instance number <INSTNR>, execute the command:
ls -d /usr/sap/???/*<INSTNR>
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 16 (page 63) 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.
62 Step-by-Step Cluster Conversion