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

If the SAP profiles configure the SAP startup service to autostart an instance, the package startup will trigger
and monitor the autostart process and starts up the instance independent of the startup service, in case the
startup service fails to successfully finish the operation.
Support of Oracle Listener Password
SGeSAP B.05.00 module packages allow to specify a password for Oracle listener maintenance. The
password will be maintained in the internal cluster database of Serviceguard. Access to the information is
only possible for users with configured Serviceguard access rights. The password access prevents unauthorized
administration of the Oracle listener process.
Support of IPv6
SGeSAP B.05.00 enables clusters based on ipv6 networking for all SAP application components.
Compatibility Information and Installation Requirements
This section describes the hardware and software that is required and/or supported with Serviceguard
Extension for SAP.
Hardware Requirements
The following HP StorageWorks XP arrays are supported with HP Businesscopy pvol/svol pairs for hot
standby liveCache data volumes and SGeSAP B.05.00:
XP256 microcode 52-46-xx or over
XP512 microcode 01-10-00/xx or over
XP1024/XP128
XP10000
XP12000
XP24000
The restriction to XP storage arrays is only required if the hot standby liveCache functionality is used.
The hardware and configuration requirements for HP Serviceguard apply in any case.
OS Platform and Version Compatibility
Version B.05.00 installs on HP-UX 11i v2 and HP-UX 11i v3.
NOTE: The highest product version with support for HP-UX 11i v1 is SGeSAP Version B.04.02.
SAP Software License Requirements
A valid SAP license for each node on which the message server will be running has to be acquired from
SAP. Additional licenses for high availability usage are free of charge for standby nodes.
You will have to use the SAP license program provided by SAP to acquire a unique customer key on every
host of the cluster. To get a SAP license:
Gather customer keys by runningsaplicense -get as <sid>adm on each machine where you want
the SAP message server to reside.
1. Fax the keys, the name of the SAP system, the installation date, and your phone and fax number to
SAP License Administration using the form provided with the standard SAP installation kit.
To speed up the process, add a note that indicates you need the additional licenses for a failover
solution using Serviceguard.
2. Receive your License Key from SAP and install it in the system using saplicense -install on each
appropriate hosts.
Compatibility Information and Installation Requirements 11