Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

existence of a file ${SGRUN}/debug_sapverify_<packagename> skips verification only for
a single package on that cluster node. Generic and SGeSAP clustering specific check routines
which are not related to SAP requirements towards local operating environment configurations are
not deactivated and are executed as part of both cmcheckconf(1) and cmapplyconf(1)
commands.
The deploysappkgs(1) command is used during initial cluster creation. It is also called after
system level or SAP application configuration change operations to verify if any of the performed
changes must be reflected in the cluster package configuration. deploysappkgs(1) command
is aware of the existing package configurations and compares them to settings of the SAP
configuration and the operating system.
Upgrading SAP software
SAP rolling kernel switches can be performed in a running SAP cluster exactly as described in the
SAP Netweaver 7.x documentation and support notes.
Upgrading the application version of the clustered SAP application to another supported version
does rarely require changes to the cluster configuration. Usually SGeSAP detects the release of
the application that is packaged automatically and treats it as appropriate.
A list of supported application versions can be taken from the SGeSAP release note document.
The list of currently installed Serviceguard Solution product versions can be created with the
command
rpm -qa |grep -i serviceguard
For a safe upgrade of SAP with modular-style packages, put all impacted SGeSAP packages in
package maintenance mode and perform a partial package start before the first SGeSAP specific
module becomes executed. Now, you can manually handle the SAP startup or shutdown operations,
the upgrade happens without interference from the cluster software.
deploysappkgs(1) and cmcheckconf(1) issued on the existing packages after upgrade give
hints on whether cluster configuration changes are required. Perform failover tests for all potential
failure scenarios before putting the system back in production.
Table 2 Summary of methods that allow SAP instance stop operations during package uptime
Usecase exampleEffectHow achieved?GranularityMethod
SAP rolling kernel switchSAP Instance service
monitoring of the
Ensure that package
parameter setting
SAP InstanceSAP stop block
deactivation
package is temporarilysap_stop_blocked no is
suspended for stoppedapplied and stop the
instances; Stoppedinstance as <sid>adm
instances cause alerts in
Serviceguard Manager
with standard SAP
methods, for example by
calling sapcontrol …
–function Stop
SAP software version
upgrade
All package service
monitoring is suspended;
cmmodpkg –m on
<pkgname>
Serviceguard
Package
Package
maintenance
mode Package cannot fail or
switch nodes while in
maintenance mode
28 SAP cluster administration