Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration
SGeSAP Administration Aspects
Chapter 6304
SGeSAP Administration Aspects
SGeSAP needs some additional information about the configuration of
your SAP environment. It gathers this information in the file
/etc/cmcluster/<SID>/sap.config. In more complicated cases there
might be additional files
/etc/cmcluster/<SID>/sap<pkg_name>.config. A
sap<pkg_name>.config file is sometimes used to create a package
specific section two of sap.conf in order to achieve proper Application
Server handling. In principle this file serve the same purpose and has
the same syntax as the generic sap.conf file.
It is very important that the information in this file is consistent with
the way your system is configured. This file must be available on all
nodes of the cluster. Under normal operation there is no need to touch
this file. But it is a good idea for a system administrator to have a look at
it to prevent you from doing things that can cause the setup to be no
longer able to failover successfully. Comments are provided within the
file and most things are self-explanatory for people trained to
understand shell scripts. The following administration activities are
possible but they must be accompanied by an adaptation of the sap.conf
file on all cluster nodes:
• changing the SAP System ID
• changing the name of the SAP System Administrator
• migrating to another database vendor
• adding/deleting Dialog Instances
• changing an Instance Name
• changing an Instance Number
• changing the network name belonging to a relocatable address
• changing the name of a SGeSAP package
• changing hostnames of hosts inside the cluster
• changing hostnames or IP addresses of hosts that run additional
application servers
• changing the location of any SAP-specific directory in the file system
• changing the name of the ORACLE listener