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

Table 2 Summary of methods that allow SAP instance stop operations during package uptime
(continued)
Usecase exampleEffectHow achieved?GranularityMethod
non-production SGeSAP
cluster trouble-shooting
All SGeSAP package
service monitoring is
Create debug flag file
touch
SGeSAP PackageSGeSAP debug
flag
temporarily suspended;debug_<packagename>
SGeSAP modules arein the SG run directory
skipped during package
start
location, which is
/usr/local/cmcluster/run
on Red Hat and
/opt/cmcluster/run
on SUSE)
Serviceguard patch
installation
Package can fail, but
cannot yet failover
cmhaltnode –dSerivceguard NodeLive Application
Detach
Package conversion
The deploysappkgs(1) command of SGeSAP/LX A.06.xx can still be used to create
modular-based cluster configuration files for NFS, database, SAP central and SAP replication
services of existing clusters if there are SGeSAP/LX A.03.00 legacy configurations. Thus, for the
majority of existing clusters, no additional migration tool is required to move from legacy to modular.
For other cases, like liveCache, SAP external instance and SAP infrastructure tool clusters, the
conversion of SGeSAP/LX 3.xx legacy configurations to SGeSAP/LX A.06.xx module configurations
requires manual steps. Preparatory effort lies in the range of 1 hour per package.
The cmmigratepkg(1) command can be applied to SGeSAP legacy packages. The output file
will lack SAP-specific package configurations of the sap*.config file, but the resulting configuration
file can be used to simplify the creation of a modular SGeSAP package:
cmmakepkg –i <cmmigratepkg_output_file> \
-m sgesap/all\> \
<modular_sap_pkg.config>
The configuration of the SGeSAP specific parameters to modular_sap_pkg.config can be
done manually. For more information on configuring modular package configuration, see “Clustering
SAP using SGeSAP packages” (page 42).
Caution needs to be taken in clusters that alter any unofficial SGeSAP parameter that is not described
in the official product documentation and in clusters that use customized code as part of the SGeSAP
customer.functions hooks. In these cases, an individual analysis of the required steps is needed.
Package conversion 29