User's Guide

In the subsection for the DB component there is an optional paragraph for Oracle and SAPDB/MAXDB
database parameters. Depending on your need for special HA setups and configurations have a look at
those parameters and their description.
Preparation Step: MS410
The generic Serviceguard parameters of the configuration file need to be edited.
Refer to the Managing Serviceguard User's Guide for general information about the generic file content: At
least you’ll want to specify package_name, node_name, ip_address and monitored_subnet in
the file that you created with step MS400.
CFS based file systems are made available through the corresponding multinode packages as defined in
Chapter 2 - Planning the Storage Layout. Package dependencies on the multinode CFS mountpoint packages
should be defined to make sure the SAP file system(s) are available. For example:
dependency_name SG-CFS-MP-SAPEXE
dependency_condition SG-CFS-MP-SAPEXE=up
dependency_location same_node
For non-CFS shares, the volume groups as defined in Chapter 2 – Planning the Storage Layout might be
directly connected to the SAP packages. That is usually the case for the instance and database homedirectories.
Example:
vg vgC11
fs_name /dev/vgC11/lvol1
fs_directory /oracle/C11
:
fs_name /dev/vgC11/lovl2
fs_directory /usr/sap/C11/SCS01
:
Installation Step: MS420
The SGeSAP parameters of the configuration file need to be edited that influence the behavior for all instances
that will be clustered by the package.
Only one mandatory parameter has to be specified: the SAP System ID sap_system. Each SGeSAP package
can only failover instances that belongs to one and the same SAP System. Thus, the parameter needs to be
specified exactly once. Example:
sap_system C11
Optional Step: OS421
The rem_comm and priv_comm values define the method to be used to remotely execute commands for
SAP Application Server handling.
Setting the parameter rem_comm is optional. It can be set to ssh to rely on secure encrypted communications
between untrusted hosts over an insecure network. Information on how to set up ssh for each node refer to
Section Cluster Node Configuration. Default value of rem_comm is remsh.
The parameter priv_comm is a placeholder for future use. It will become effective if SAP clusters get supported
that allow cross-subnet setups.
Optional Step: OS422
It is possible to influence the system cleanup behavior of SGeSAP.
Prior to any instance startup attempts the SGeSAP tries to free up unused or unimportant resources to make
the startup more likely to succeed. A database package only frees up database related resources, a SAP
Instance package only removes IPCs belonging to SAP administrators.
58 Step-by-Step Cluster Conversion