Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 101
RE020 Replicated Enqueue Conversion:
A volume group needs to be created for the ASCS instance. The physical
device(s) should be created as LUN(s) on shared storage. Storage
connectivity is required from all nodes of the cluster that should run the
ASCS. For the volume group, one logical volume should get configured.
For the required size, refer to the capacity consumption of
/usr/sap/<SID>/DVEBMGS<INSTNR>. This should provide a conservative
upper limit that leaves reasonable headroom.
Mount the new logical volume to the mountpoint created in RE010.
RE030 Replicated Enqueue Conversion:
Create instance subdirectories in the mounted logical volume. They will
be switched between the cluster nodes later.
su - <sid>adm
cd /usr/sap/<SID>/ASCS<INSTNR>
mkdir data log sec work
RE040 Replicated Enqueue Conversion:
If the used SAP kernel has a release older than 6.40:
Download the executables for the Standalone Enqueue server from the
SAP Service Marketplace and copy them to /sapmnt/<SID>/exe.
There should be at least three files that are added/replaced: enserver,
enrepserver and ensmon.
Make sure these files are part of the sapcpe mechanism for local
executable creation (see Chapter 2).
This step will create a version mix for the executables. The Standalone
Enqueue executables get taken from the 6.40 kernel. Special caution has
to be taken to not replace them with older releases later on. This might
happen by accident when kernel patches get applied.
RE050 Replicated Enqueue Conversion:
Create instance profile and startup profile for the ASCS Instance.
These profiles get created as <sid>adm in the NFS-shared
/sapmnt/<SID>/profile directory.
Here is an example template for the instance profile
<SID>_ASCS<INSTNR>_<CIRELOC>: