HP Serviceguard Extension for SAP (SGeSAP) manual Maxdb Database Step SD040

ls

#Example: rm -r SYS

#rm -r D00

cd DVEBMGS<INSTNR>

find . -depth -printcpio -pd /usr/sap/<SID>/DVEBMGS<INSTNR> 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. For 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.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 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.

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

---

...>

HP-UX Configuration 49