Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration
SGeSAP Administration Aspects
Chapter 6306
Upgrading SAP Software
Upgrading the version of the clustered SAP application does not
necessarily require changes to SGeSAP. Usually SGeSAP detects the
release of the application that is packaged automatically and treats it as
appropriate. Make sure that you have a valid SGeSAP version in place
by issuing the command:
On HP-UX 11iV2 or higher type:
swlist -l bundle T2357BA T2803BA
On HP-UX 11i type:
swlist -l bundle T7885BA
Review the release notes of the SGeSAP version that gets reported and
make sure that the target SAP application release is supported with the
SGeSAP version that is already installed. If this is not the case, you
should first get an update for the HP Serviceguard Extension for SAP
installed and activated before continuing.
For a safe upgrade, SGeSAP can be switched off like is described in the
section below.
Perform failover tests for all potential failure scenarios before putting
the system in production.
If the setup has a mixed cluster of PA-RISC and IPF nodes, then he will
have two sets of SAP central executables. In this case it is required to
make sure that after successful upgrade on one platform, the second
kernel directory gets upgraded manually. Both kernel directories need to
have the same kernel revision and patch level.
Sometimes, upgrades come with additional configuration options. ASCS
and Replicated Enqueue is possible beginning with ABAP kernel 4.6.
SCS instances are introduced with J2EE engine 6.40. Refer to Chapter
Three on how to configure packages for the additional components.