Serviceguard Extension for SAP Version B.04.02 and B.04.51 Release Notes, December 2007

Serviceguard Extension for SAP Versions B.04.02 and B.04.51 Release Notes
Patches and Fixes in this Version
Chapter 122
JAGaf92445 (SR 8606433948): Package script kills itself during startup
• What is the problem? Parallel SAP application server handling may cause a package
startup or shutdown operation to fail. Adjacent empty entries in internal process lists may
cause background watchdogs to send a SIGKILL to the package control script after timing
out.
For adjacent empty entries to happen, several conditions need to be met:
1. At least two external SAP application servers need to be configured in the SGeSAP
configuration.
2. Parallel SAP application server handling needs to be activated.
3. Two or more external SAP application servers need to be already running during
startup of the package or already stopped during shutdown of the package.
4. Alternatively, the node on which these application servers run needs to be
unaccessible.
5. The application servers need to be specified in adjacent entries of the AS*[] arrays of
the SGeSAP configuration.
• Resolution: The process list parsing of SGeSAP A.04.51 got altered to allow proper
handling of adjacent empty entries.
JAGaf95806 (SR 8606437636): Example SQL script for Oracle 8i databases incomplete
• What is the problem? If an Oracle 8i database fails during online backup, the table spaces
remain in "begin backup" mode. Oracle logs increase in size much faster than before.
• Resolution: A script execution statement got added to the SQL script example that is
provided to put Oracle table spaces in "end backup" mode after failover.