Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009
# prevent shmem pool creation
#----------------------------------
ipc/shm_psize_16 = 0
ipc/shm_psize_24 = 0
ipc/shm_psize_34 = 0
ipc/shm_psize_66 = 0
This template shows the minimum settings. Scan the old <SID>_DVEBMGS<INSTNR>_<local_ip> profile
to see whether there are additional parameters that apply to either the Enqueue Service or the Message
Service. Individual decisions need to be made whether they should be moved to the new profile.
Here is an example template for the startup profile START_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
SAPSYSTEMNAME =<SID>INSTANCE_NAME =ASCS<INSTNR>
-----------------------------------------------------------------------
# start SCSA handling
#-----------------------------------------------------------------------
Execute_00 =local $(DIR_EXECUTABLE)/sapmscsa -n pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
# start Message Server
#-----------------------------------------------------------------------
MS =ms.sap<SID>_ASCS<INSTNR>
Execute_01 =local rm -f $(_MS)
Execute_02 =local ln -s -f $(DIR_EXECUTABLE)/msg_server $(_MS)
Start_Program_01 =local $(_MS) pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
# start syslog collector daemon
#-----------------------------------------------------------------------
CO =co.sap<SID>_ASCS<INSTNR>
Execute_03 =local rm -f $(_CO)Execute_04 =local ln -s -f $(DIR_EXECUTABLE)/rslgcoll $(_CO)
Start_Program_02 =local $(_CO) -F pf=$(DIR_PROFILE)/<SID>_ASCS<INSTNR>_<CIRELOC>
#-----------------------------------------------------------------------
# start Enqueue Server
#-----------------------------------------------------------------------
EN = en.sap<SID>_ASCS<INSTNR>Execute_05 = local rm -f $(_EN)
Execute_06 = local ln -s -f $(DIR_EXECUTABLE)/enserver $(_EN)
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>
#-----------------------------------------------------------------------
Replicated Enqueue Conversion: RE060
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:
SAP Preparation 59