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

#-------------------------------------------------------------------
enque/process_location = REMOTESA
rdisp/enqname = $(rdisp/myname)
enque/serverinst = $(SCSID)
enque/serverhost = <[J]CIRELOC>
Here is an example template for the startup profile START_ERS<INSTNR>_<AREPRELOC>
#-----------------------------------------------------------------------
SAPSYSTEM = <INSTNR>
SAPSYSTEMNAME = <SID>
INSTANCE_NAME = ERS<INSTNR>
#--------------------------------------------------------------------
# Special settings for this manually set up instance
#--------------------------------------------------------------------
SCSID = <INR>
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/ <SID>_ERS<INSTNR>_<[A]REPRELOC>
SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
_ER = er.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = local rm -f $(_ER)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enrepserver$(FT_EXE) $(_ER)
Start_Program_00 = local $(_ER) pf=$(_PF) NR=$(SCSID)
Linux Configuration
The valid Linux kernel to deploy to the servers needs to be certified with the SAP LinuxLab and at the same
time needs to be supported with HP Serviceguard Extension for SAP on Linux.
The SAP LinuxLab publishes kernels to deploy on its FTP server. The latest kernel to deploy can be obtained
from SAP. Instructions from where to download these kernels can be found on
http://www.sap.com/linux/. Additional information on how to contact the SAP LinuxLab can also
be found there.
All supported Serviceguard Extension for SAP on Linux setups were tested with drivers that are supported
by HP Serviceguard for Linux and at the same time are part of an SAP certified Linux distribution. For these
setups, it is not required to install any driver in addition to those that come with the Linux distribution. LVM,
network bonding and multi-pathing are supported via the software that comes with the Linux distribution.
Activities that would endanger SAP support are:
• Recompiling/remaking the Linux kernel after installation.
• Adding drivers that are not part of the installed Linux distribution.
• Adding kernel modules that are not delivered with an open source license.
A correct Linux configuration ensures that all cluster nodes provide the environment and system configuration
required to run SAP. Several of the following steps must be repeated on each node. Record the steps completed
for each node, as you complete them. This helps identify errors in the event of a malfunction later in the
integration process. The Linux configuration task is split into the following sections:
NOTE: The above step should only be performed once on the primary host.
1. Directory Structure Configuration - This section describes the changes that need to be done in order to
distribute the SAP file systems across logical volumes on local and shared disk systems. The primary
host is the host where the SAP Central Instance was installed. If your database is currently running on
Linux Configuration 63