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

All SAP Instances (CI, SCS, ASCS, D,...) must have instance numbers that are unique for the whole
cluster. Exceptions are (A)REP instances that follow an old naming convention of sharing the instance
ID with their corresponding (A)SCS instance. This naming convention should no longer be used,
since it cannot be combined with the SAP startup framework. For a clustered instance with instance
number <INSTNR>, execute the command:
ls -d /usr/sap/???/*<INSTNR>
It should not reply any match on any node. Otherwise, refer to the SAP documentation how to
change instance IDs for the relevant instance type. It might be simpler to reinstall one of the
conflicting instances.
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 .
Also, make sure that there are no remaining entries for file systems converted in IS009.
MaxDB Database Step: SD040
This step can be skipped for MaxDB instances starting with versions 7.6 .
MaxDB is not supported on CFS, but can be combined with SAP instances that use CFS. In this
case, make sure you have mounted a sharable logical volume on /sapdb/<DBSID>/wrk as
discussed in section “MaxDB Storage Considerations” in chapter 2.
NOTE: dbmcli commands only work for users that have correct XUSER settings in place.
Change the path of the runtime directory of the MaxDB 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
... db_cold
... param_directget RUNDIRECTORY
OK
RUNDIRECTORY /sapdb/data/wrk/<DBSID>
---
... param_directput RUNDIRECTORY /sapdb/<DBSID>/wrk
OK
---
...
NOTE: The commands prefixed with “...” are executed from within the dbmcli shell.
Installation Step: IS049
If it does not yet exist, create a CVM/CFS system multi-node package and start it .
58 Step-by-Step Cluster Conversion