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

rm -r * # be careful with this
cd ..
rmdir DVEBMGS<INSTNR>
2. Mark all shared volume groups as members of the cluster. This only works if the cluster
services are already available.
Example:
cd /
# umount all logical volumes of the volume group
vgchange -a n <vg_name>
vgchange -c y <vg_name>
vgchange -a e <vg_name>
# remount the logical volumes
3. 3. The device minor numbers must be different from all device minor numbers gathered on
the other hosts. Verify this by comparing numbers listed in Table 1-3 “Hosts and Device
Minor Numbers” to the numbers listed in the tables contained in chapter 2.
Create map files with the vgexport command and distribute them to all nodes in the cluster
for all shared volume groups.
Installation Step: IS030
Comment out the references to any file system that is classified as a shared directory in chapter
2 from the /etc/fstab.
MAXDB Database Step: SD040
Make sure you have mounted a sharable logical volume on /sapdb/<DBSID>/wrk as discussed
in section “MAXDB Storage Considerations” in chapter 2.
NOTE: This step can be skipped for MAXDB instances starting with versions 7.6.
Change the path of the runtime directory of the SAPDB and move the files to the new logical
volume accordingly.
cd /sapdb/data/wrk/<DBSID>
find . -depth -print | cpio -pd /sapdb/<DBSID>/wrk
cd ..
rm -r /sapdb/data/wrk/<DBSID>
dbmcli -d <DBSID> -u control,control
...> param_directget RUNDIRECTORY
OK
RUNDIRECTORY /sapdb/data/wrk/<DBSID>
---
...> param_directput RUNDIRECTORY /sapdb/<DBSID>/wrk
OK
---
...>
Installation Step: IS050
This step describes how to create a local copy of the SAP binaries. The step is mandatory for
legacy packages. It is also required to do this, if a module-based package is used for a system
with SAP kernel <7.0.
Check if the Central Instance host and all application servers have a directory named
/usr/sap/<SID>/SYS/exe/ctrun. If the directory exists, this step can be skipped. The system
is already using local executables through sapcpe.
To automatically synchronize local copies of the executables, SAP components deliver the sapcpe
mechanism. With every startup of the instance, sapcpe matches new executables stored centrally
with those stored locally. Figure 3-1 shows a SAP filesystem layout with sapcpe activated for
two Application Servers.
54 Step-by-Step Cluster Conversion