Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3106
Start_Program_03 = local $(_EN) pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
# start syslog send daemon
#-----------------------------------------------------------------------
SE =se.sap<SID>_ASCS<INSTNR>
Execute_07 =local rm -f $(_SE)
Execute_08 =local ln -s -f $(DIR_EXECUTABLE)/rslgsend $(_SE)
Start_Program_04 =local $(_SE) -F pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
OS060 Replicated Enqueue Conversion:
Adopt instance profile and startup profile for the DVEBMGS<INSTNR>
instance. The goal of this step is to strip the Enqueue and Message
Server entries away and create a standard Dialog Instance. A second
alteration is the replacement of the Instance Number of the Central
Instance which now belongs to ASCS and AREP.
The new Dialog Instance profile <SID>_D<INSTNR_2>_<DRELOC> differs
from the original <SID>_DVEBMGS<INSTNR>_<ip_address> profile in
several ways:
All configuration entries for Message and Enqueue Service need to be
deleted, e.g.
rdisp/wp_no_enq=1
must be removed. Several logical names and address references need to
reflect a different relocatable address, a different Instance Name and a
different Instance Number. For example:
INSTANCE_NAME=D<INSTNR_2>
SAPSYSTEM=<INSTNR_2>
rdisp/vbname = <DRELOC>_<SID>_<INSTNR_2>
SAPLOCALHOST=<DRELOC>
SAPLOCALHOSTFULL=<DRELOC>.domain