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

/usr/sap/<SID>.new
cd /
unmount /usr/sap/<SID>
MaxDB Database Step: MD040
This step can be skipped for MaxDB instances starting with versions 7.6 and higher.
NOTE: Make sure you have mounted a sharable logical volume on /sapdb/<DBSID>/wrk as discussed
in section MaxDB Storage Considerations in Chapter 2.
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 ..
rmdir /sapdb/data/wrk/<DBSID>
dbmcli -d <DBSID> -u control,control
dbmcli on <DBSID>> param_directget RUNDIRECTORY
OK
RUNDIRECTORY /sapdb/data/wrk/<DBSID>
dbmcli on <DBSID>> param_directput RUNDIRECTORY
/sapdb/<DBSID>/wrk
OK
dbmcli on <DBSID>>
Installation Step: IS050
The usage of local executables with Serviceguard Extension for SAP on Linux is required.
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 file system layout with sapcpe activated for two Application Servers.
Linux Configuration 65