Serviceguard Extension for SAP Version B.05.00 Release Notes (April 2010)

Database (versions as
supported by SAP)
OSSGeSAPSAP Kernel SAP
WAS
CESRM EBPSEMKWCRM
Oracle MAXDBHP-UX 11i v34.507.005.06.07.05.0
6.404.04.05.0 4.0
SR1
6.203.04.0 3.1
Oracle MAXDB DB/2
(up to 8.1)
HP-UX 11i v24.017.005.05.07.05.0
6.40 6.304.04.05.0 4.0
SR1
6.20 6.103.04.0 3.1
For the following technical components additional failover support has been implemented.
These components are not based on any SAP kernel release.
Table 1-4 T2803BA SGeSAP Support Matrix for liveCache
HP-UX ReleaseSGeSAPLivecache with hot standbyliveCache
HP-UX 11i v3 HP-UX 11i v24.51 and 5.007.7, 7.6 and 7.5 (on Integrity)7.7, 7.6, 7.5 and 7.4
HP-UX 11i v34.507.6 7.5 7.4
HP-UX 11i v14.027.6 7.5
HP-UX 11i v1 HP-UX 11i v24.017.6 7.5 7.4
*: *: Clustering of SAP kernel 7.10 based components with SGeSAP 4.51 requires installation of PHSS_38922
on HP-UX 11i v2 or PHSS_38923 on HP-UX 11i v3.
**: The Livecache-based lock server for BI 7.0 is not yet supported
Port Requirements
In principle, SGeSAP does not have specific port requirements. For ports that are generally required by HP
Serviceguard, please refer to the release notes of these products. SAP port settings need to become available
on all cluster nodes. In certain use cases, well-known ports of secure shell or remote shell are utilized. For
details, please refer to Managing Serviceguard Extension for SAP, part number T2803-900013.
Installing
Serviceguard Extension for SAP has to be installed on all nodes that will run an SAP database or SAP instance
package in the cluster.
Use swinstall(1m) to install Serviceguard Extension for SAP. The legacy package script templates are
installed to a preliminary location. You manually integrate these templates as described in the document
T2803-900013. All modular package functionality is effective immediately, with no additional staging steps
required.
▲ If the software bundle is not installed on a Dynamic Root Disk (DRD), but is intended to be installed as
part of a rolling upgrade, then do the following:
• The cluster must be running
• Make sure no package that uses the cmenqord resource is running on the node that is to be
patched.
• Only packages for SAP [A]SCS or SAP [A]REP/ERS instances can make use of cmenqord. To
check if a package uses the cmenqord resource type
cmviewcl -v -p <packagename>
14 Serviceguard Extension for SAP Version B.05.00 Release Notes