Serviceguard Extension for SAP Release Notes Version B.05.10, December 2012

The HP Serviceguard Manager configuration screen for SGeSAP database packages now includes
a radio button which enables you to select Sybase as database technology. Easy deployment of
the SGeSAP package is also enabled for Sybase ASE.
SGeSAP/dbinstance supports IBM DB2 UDB
The db_vendor modular-style package attribute allows db2 as valid attribute value. The
sapdatab.mon monitoring is enabled to monitor DB2 databases. The HP Serviceguard Manager
configuration screen for SGeSAP database packages now features a radio button to select DB2
as the database technology.
Easy deployment of the SGeSAP package is enabled for DB2.
Graceful database package shutdown
SGeSAP can now differentiate a manual database package halt attempt from an emergency
database package shutdown caused by a package failure. The sgesap/dbinstance module supports
planned package shutdown attempts to be triggered for SAP Sybase, Oracle, IBM DB2, and SAP
MaxDB packages by using the cmhaltpkg -a command.
Now you can specify a halt operation to potentially abort the package halt sequence upon
encountering an error during the shutdown sequence. If a package is halted with the -a option
and if a planned graceful database package halt operation detects a failure that prevents a
successful standard database shutdown, then the halt will be aborted and the package is moved
to a partially_down status in a halt_aborted state.
Partially_down status of a package allows administrative interventions and prevents subsequent
module execution.
Halting a package with the -a command helps to avoid the emergency abort operations required
during failover of the database. You can continue the graceful package shutdown after fixing the
failure issue manually.
NOTE: Starting with Serviceguard A.11.20, March 2012 Feature Patch, the cmhaltpkg -a
command is added to Serviceguard.
SAP-specific node-local cluster verification
SGeSAP maintains a list of rules that specify local configuration requirements on potential secondary
nodes. These requirements are checked with every execution of the command cmcheckconf(1m)
or cmapplyconf(1m) on a modular-style SGeSAP package. Regular execution of
cmcheckconf(1m) for a running SGeSAP package helps to detect erroneous local configurations
that would negatively impact the capability to failover a SAP package to a certain node.
Configurable intra-module parallelization
Executing parts of the package control script of a module in parallel can significantly speed up
SGeSAP package failover. But starting all SAP instances of large environments simultaneously
might lead to timeout issues in some cases. Parallel startup and parallel shutdown of all JAVA and
all ABAP instances that are configured in the sgesap/sapinstance and sgesap/sapextinstance
modules is available. The parallel startup can be turned on or off individually for each package
with a new package parameter sgesap/sap_global/parallel_startup.
Operation with HP-UX Containers for Oracle databases
SGeSAP can operate in environments that are set up with workload containers - previously called
HP Secure Resource Partitions (SRP) - according to the HP Secure Resource Partition Reference
Architecture for Oracle databases. These setups restrict the number of available CPU cores for
Oracle databases in SAP cluster environments. The workload containers of the HP-UX Container
A.03.00 product are backwards compatible with SRP A.02.00 compartments.
8 Serviceguard Extension for SAP Version B.05.10 Release Notes