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

• QXCR 1000999617 “SGeSAP 5.00 sap_functions.sh stop_db function logs output
to the incorrect file”
Resolution: The wrong shell variable setting for the output file and the log message of stopdb
in SGeSAP 5.00 patches PHSS_[39357|39358] got corrected.
• QXCR 1001006257 “start_direct() does not handle INSTANCE_AUTOSTART=1 as it
should“
Resolution: SGeSAP 5.10 does not issue warnings about already running instances, if a
customer configures the SAP sapstartsrv agent to autostart SAP. SAP autostarts are
monitored for proper operation. An additional start attempt is made by SGeSAP, in case the
SAP autostart fails.
This section lists defects that have been fixed in SGeSAP 5.10 legacy packages:
• QXCR 1000992323 “SGeSAP patch changes stopsap command incorrectly“
The issue is fixed after configuration of SGeSAP 5.10 based legacy packages. Any legacy
package defect gets checked for relevance in modular environments. Modular packages never
showed the defect.
Patches
A range of SGeSAP 5.10 enhancements were added after the initial release of the software and
only becomes available after enhancement patch installation. All the features as described in this
document can be utilized after installation of PHSS_42569 and PHSS_42558. The following list
describes the added features in more detail.
• DB2 9.x support and SAP Diagnostic Agent support becomes available only after the installation
of PHSS_40911 or any superseding cumulative patch, like PHSS_41881 or PHSS_42151.
DB2 10.x support becomes available only after the installation of PHSS_43196 or any
superseding cumulative patch.
• The DB2 enhancement of PHSS_40911 will not be in effect before a SGeSAP package gets
configured to include them. In package configuration ASCII files of existing SGeSAP database
packages, it is possible to change the sgesap/dbinstance module version to 2 before running
cmapplyconf(1m) on the package.
Example entry:
module_name sgesap/dbinstance
module_version 2
• The package does not need to be halted to change the module version. The package needs
to be halted in order to change the value of sgesap/db_vendor to db2.
• The SAP Diagnostic Agent enhancement of PHSS_40911 will not be in effect before a SGeSAP
package gets configured to include them in module sgesap/sapextinstance. There might be
one or more Diagnostic Agents for each relocatable IP of the package. These Agents can be
moved with the package. A best-effort startup attempt will be triggered as part of the package
start. Diagnostic Agent instances won't be automatically included in already existing packages
as part of the patch installation. They need to be added to package configurations manually.
Example configuration parameters for a Diagnostic Agent instance SMDA97 are like follows:
sgesap/sapextinstance/sap_ext_instance SMDA97
sgesap/sapextinstance/sap_ext_system DAA
sgesap/sapextinstance/sap_ext_host reloc1
sgesap/sapextinstance/sap_ext_treat yynnn
fs_name /usr/sap/DAA/SMDA97
• Add the parameters to the package configuration ASCII file of the package that handles the
relocatable IP for reloc1 and apply with cmapplyconf(1m). The daaadm UNIX user needs
to exist on all failover nodes. The /home/daaadm directory can be local on all failover nodes.
16 Serviceguard Extension for SAP Version B.05.10 Release Notes