Managing Serviceguard Extension for SAP Version B.05.10, December 2012
Specify
SAPCCMSR_START=1
if there should be a CCMS agent started on the DB host automatically.
You should also specify a path to the profile that resides on a shared
lvol.
Example:
SAPCCMSR_START=1
SAPCCMSR_CMD=sapccmsr
SAPCCMSR_PFL="/usr/sap/ccms/${SAPSYSTEMNAME}_${CINR}/sapccmsr/${SAPSYSTEMNAME}.pfl”
Global Defaults
The fourth section of sap.config is rarely needed. It mainly provides various variables that allow
overriding commonly used default parameters.
Optional Step: OS770
If there is a special demand to use values different from the default, it is possible to redefine some
global parameters
.
Depending on your need for special HA setups and configurations, take a look at those parameters
and their description in the SAP specific configuration file sap.config.
When using the HP Serviceguard Storage Management Suite with CFS and shared access Option
3 (chapter 2—“Planning the Storage Layout”) it is required to set the CTEXERELOC variable ,
because otherwise the default initialization value would be NFSRELOC (DEFAULT: ${NFSRELOC}).
CTEXERELOC should get initialized to DBRELOC or CIRELOC.
Optional Step for Netweaver 2004s: NW04S780
This installation step only applies if Netweaver 2004s with SAP Application Server 7.0 is installed
.
SAP introduced a control framework with Netweaver 2004s and SAP Application Server 7.0 that
enables the management of SAP instances from third party products using a defined application
interface. This control framework is implemented using a daemon process that is either started by:
• the operating system during boot time or
• the SAP startup script when the instance is started.
During the installation of a SAP Netweaver 2004s Web AS, the SAPIinst installer edits a file in
/usr/sap/sapservices and adds a line for each sapstartservice instance. During boot
time an init script is executed located in:
/sbin/init.d/sapinit
referenced by
/sbin/rc3.d/S<###>sapinit
The sapinit script reads the content in file /usr/sap/sapservices and starts a sapstartsrv
for each instance during OS boot time. This can lead to error output in the boot messages log file
as file systems for exclusive shared storage is not available at that time.
If the use of the SAP control framework is not required, then remove the reference link from the
sapinit script. Furthermore, any running sapstartsrv processes can be killed from the process
list. Example:
# rm /sbin/rc3.d/S<###>sapinit
# ps -ef | grep sapstartsrv# kill {PID of sapstartsrv }
To make use of the sapstartservice configure the SAPSTARTSRV_START and
SAPSTARTSRV_STOP values. The sapstartsrv daemon is started and stopped accordingly.
Example:
SAPSTARTSRV_START=1
SAPSTARTSRV_STOP=1
Optional Step: OS790
To enable the Workload Management (WLM) support of the dispatcher monitors
specify:
WLM_PROCMAP=1
102 Step-by-Step Cluster Conversion