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

Patches, Fixes, Known Problems, and Workarounds
For a current list of patches, known problems, and workarounds, contact your HP support
representative or go to the appropriate Hewlett-Packard Support Centre website: http://
www.hp.com/go/hpsc.
Known Limitations
The SAP dbmcli hss_removestandby command is only supported with liveCache 7.7.04.37
and above. A hot standby database configuration can be deleted from earlier revisions by removing
the HS* parameters with param_directput instead. For additional info on potential issues with
SAP function module LC_GET_INSTANCE_STATE, see oss note 1400272.
Fixes
This section lists defects that have been fixed in the initial release of SGeSAP 5.10 modular
packages:
• QXCR1000849715 “startdb.sqlplus should use different commands”
Resolution: The SGeSAP startdb.sqlplus example script got enhanced to offer two
implementation alternatives. The product manual discusses both alternatives.
• QXCR 1000948703 “start_ORACLE_jdb/stop_ORACLE_jdb return code may not return
successful operation”
Resolution: The sqlplus statement WHENEVER SQLERROR gets utilized to enforce non-zero
exit-codes for failing sqlplus statements.
• QXCR 1000948712 “SGeSAP does not handle Oracle startup properly when both pfile and
spfile exist“
Resolution: If a system specific SPFILE exists for the PFILE—the configuration parameters are
now read and set from it instead of a generic init.ora. The SPFILE has preference.
• QXCR 1000971124 “SGeSAP shutdown hangs in ‘Waiting for cleanup of resources....’ ”
Resolution: Refer to the latest version of SAP Note 966416 —"Inst. SAP NetWeaver based
on Kernel 7.10 - Unix": Remove all krnlreg entries from profiles.
1. Log on as user <sid>adm.
2. Go to /usr/sap/<SAPSID>/SYS/Profile.
3. Edit the instance profiles for all SAP system instances
<SAPSID>_<INSTANCE_NAME>_<host_name>, for example
KB1_DVEBMGS01_pwdf2308.
4. Remove all 'krnlreg' entries from all instance profiles.
NOTE: If you do not remove these krnlreg entries, a deadlock situation may occur while
restarting the central services instance.
After installation of SGeSAP 5.10, the modular cluster packages will continue to shutdown
the package even after deadlock situations caused by issues in SAP configuration.
• QXCR 1000976488 “Service monitors may fail in maintenance mode - online return to running
refused“
Resolution: SGeSAP 5.10 monitors stop monitoring while a package is in maintenance mode
and continue to operate once the monitor leaves package maintenance mode.
Patches, Fixes, Known Problems, and Workarounds 15