HP Serviceguard Extension for SAP (SGeSAP) manual If the used SAP kernel has a release older than

They will be switched between the cluster nodes later.

su - <sid>adm

cd /usr/sap/<SID>/ASCS<INSTNR>

mkdir data log sec work

Replicated Enqueue Conversion: RE040

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.

Replicated Enqueue Conversion: RE050

Create instance profile and startup profile for the ASCS Instance.

These profiles get created as <sid>adm in the NFS-shared /sapmnt/<SID>/profiledirectory.

Here is an example template for the instance profile <SID>_ASCS<INSTNR>_<CIRELOC>:

#----------------------------------

# general settings

#----------------------------------

SAPSYSTEMNAME=<SID> INSTANCE_NAME=ASCS<INSTNR> SAPSYSTEM=<INSTNR> SAPLOCALHOST=<CIRELOC> SAPLOCALHOSTFULL=<CIRELOC>.<domain>

#----------------------------------

# enqueueserver settings

#----------------------------------

enque/server/internal_replication = true enque/server/replication = true enque/server/threadcount = 1 enque/enrep/keepalive_count = 0 enque/process_location = local enque/table_size = 4096 ipc/shm_psize_34 = 0

#----------------------------------

# messageserver settings

#----------------------------------

rdisp/mshost=<CIRELOC>

#----------------------------------

# 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>

40 Step-by-Step Cluster Conversion