Managing Serviceguard Extension for SAP Version B.05.10, December 2012
Import the shared volume groups using the minor numbers specified in Table 4 (page 32) in chapter
“Planning the Storage Layout” (page 30) .
The whole volume group distribution should be done using the command line interface. Do not use
SAM. SAM will not create minor numbers in the intended fashion. Specify the device minor numbers
explicitly by creating the group file manually.
On possible failover nodes, for example:
mkdir /dev/vgdb<SID>
mknod /dev/vgdb<SID>/group c 64 0x080000
Now you can use vgimport(1m) with the map file created on the primary host during Step
IS020.
Installation Step: IS210
Create a local directory for
saposcol
temporary data on all cluster nodes
.
Example:
mkdir -p /usr/sap/tmp
Installation Step: IS220
Create a local mount point for each file system that was specified in chapter "Planning the Storage
Layout to have shared disk" or HA NFS" access point
.
Refer to the tables in chapter 2 for Instance, System ,and Environment specific volume groups, and
the corresponding tables that represent entries for the required database type. Depending on the
past usage of the hosts, some of the directories might already exist.
For non-CFS options only:
su - <sid>adm
mkdir -p /sapmnt/<SID>
mkdir -p /usr/sap/trans
mkdir -p /usr/sap/<SID>/<INSTNAME><INSTNR>
exit
MaxDB Database Step: SD230
su - sqd<SID>
mkdir -p /sapdb/programs
mkdir -p /sapdb/data
mkdir -p /usr/spool/sql
exit
Ownership and permissions of these directories should be chosen equally to the already existing
directories on the primary host.
MaxDB Database Step: SD235
For releases starting with MaxDB 7.5: Copy file
/etc/opt/sdb
to the alternate cluster nodes
.
This file contains global path names for the MaxDB instance.
MaxDB Database Step: SD236
For releases starting with MaxDB 7.5
:
If /var/spool/sql exists, verify that the symbolic links in the directory exist on all cluster nodes
running the database.
Cluster Node Configuration
Repeat the steps in this section for each node of the cluster.
Logon as root.
SGeSAP needs remote login to be enabled on all cluster hosts. The traditional way to achieve this
is via remote shell commands. If security concerns prohibit this, it is also possible to use secure
shell access instead.
Installation Step: IS240
66 Step-by-Step Cluster Conversion