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

Use ftp(1) to copy the file over to the secondary node. On the secondary node:
su - <sid>adm
mkdir -p /usr/sap/<SID>/SYS
cd /usr/sap/<SID>/SYS
cpio -id </tmp/SYS.cpio
Installation Step: IS192
Create a mountpoint for the Central Instance directory on the backup node so the node can run the Central
Instance. For example:
mkdir -p /usr/sap/<SID>/DVEBMGS<INSTNR>
Installation Step: IS210
Create a local directory for the saposcol temporary data on possible the backup nodes.
For 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" to have a "NFS" access point.
Refer to the tables in chapter 2 for LOCAL, SHARED or NFS mountpoints 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.
su - <sid>adm
mkdir -p /sapmnt/<SID>
mkdir -p /usr/sap/trans
mkdir -p /usr/sap/<SID>/<component><INSTNR>exit
MaxDB Database Step: MD230
MaxDB database specific:
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: MD235
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: MD236
For releases starting with MaxDB 7.5
Verify that the symbolic links listed below in directory/var/spool/sql exist on all cluster nodes running
the database:
dbspeed -> /sapdb/data/dbspeed
diag -> /sapdb/data/diag
fifo -> /sapdb/data/fifo
ipc -> /sapdb/data/ipc
pid -> /sapdb/data/pid
pipe -> /sapdb/data/pipe
ppid -> /sapdb/data/ppid
Linux Configuration 69