Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 3 November 21, 2022 Updated advsiory with inforatmion regarding a general release patch update HPE Serviceguard Extension for SAP version 12.80.03 available to fix the issue. 2 July 28, 2022 Updated password in Resolution. 1 May 25, 2022 Original Document Release. SAP Netweaver and S4/HANA systems running HPE Serviceguard Extension for SAP version 12.40 (or later) on SUSE Linux Enterprise Server 15 and version 12.50 (or later) on Red Hat Enterprise Linux 8 may not be able to start SAP packages after upgrading the SAP components to the versions listed below or later. A general release patch update HPE Serviceguard Extension for SAP version 12.80.03 is available to fix the issue. More information on the fix is in the Resolution below. This may occur with the components and HPE Serviceguard and SAP Netweaver or S4/HANA in the below list on a particular Linux OS version: HPE Serviceguard and Serviceguard Extension for SAP components: SUSE Linux Enterprise Server 15 - HPE Serviceguard for Linux and HPE Serviceguard Extension for SAP versions 12.40 through 12.80 Red Hat Enterprise Linux 8 - HPE Serviceguard for Linux and HPE Serviceguard Extension for SAP versions 12.50 through 12.80 SAP components: S/4 kernels: 7.77 PL441, 7.81 PL241, 7.85 PL115 Netweaver kernels: 7.53 PL1011, 7.22 PL1119 Hostagent: 7.22 PL56 Refer to SAP note 3139184 for more information: Title: Linux: systemd integration for sapstartsrv and SAP Host Agent SAP/SGeSAP running on HP-UX is not affected SAP HANA running on Linux is not affected If this occurs, the typical behavior is that the SAP package will start (using fallback method) then very quickly fail after the monitor starts. To verify if the system is susceptible to the issue, run the following command as the <sid>adm user: <sid>adm@node1:/usr/sap/<SID>/ASCS00> sapstartsrv -h The system is susceptible to the issue if the "sapstartsrv -h" command returns a string containing "-pf=<Instanceprofile> [-nosystemd] -reg Register in /usr/sap/sapservices" (note the "-nosystemd" option is displayed). Analysis of the package log for the failed start will typically display a successful start (using fallback method) but then immediately after that, the package monitors will start and soon fail with output similar to the following. In this example, sapms.mon is shown but other monitors display similar output: <code block> Apr 12 02:57:40 root@node1 master_control_script.sh[18591]: ###### Package start completed for ASCS ###### ... Apr 12 02:57:44 root@node1 sapms.mon[11473]: (sapms.mon,init_params_sap_inst): No static Instance Agent configured for <INSTANCE> Apr 12 02:57:44 root@node1 sapms.mon[11473]: (sapms.mon,init_params_sap_inst): Package will handle registration entry for Instance Agent of <INSTANCE> ... Apr 12 02:58:15 root@node1 master_control_script.sh[25349]: ###### Halting package ASCS ###### </code block> Note : The <INSTANCE> will be replaced by the appropriate instance name and instance number for example, ASCS00. The first monitor line will be displayed even though there is an entry for <INSTANCE> in /usr/sap/services. The second line indicates the error. The expected output should be "Package will handle Instance Agent of <INSTANCE>" ("registration entry for" in the message is NOT expected to be displayed). The registration check involved with handling the false registration condition will bring the instance down and the monitor will either try to restart the instance or fail, resulting in a package halt.
Any HPE system running HPE Serviceguard Extension for SAP version 12.40 (or later) on SUSE Linux Enterprise Server 15 or version 12.50 (or later) on Red Hat Enterprise Linux 8.
This issue is resolved in HPE Serviceguard Extension for SAP version 12.80.03. To install HPE Serviceguard Extension for SAP version 12.80.03 you must first update to HPE Serviceguard for Linux (including HPE Serviceguard Extension for SAP) 12.80.00 using one of the normal methods. 12.80.03 can only be installed on top of an existing 12.80.00 installation and you cannot upgrade from an earlier version directly to 12.80.03. Note that while Rolling Upgrades are possible for both 12.80.00 and 12.80.03 itself, the whole cluster should be stabilized on 12.80.00 before patching the nodes further to 12.80.03. The fix is not fully implemented until all nodes are running 12.80.03. To download the HPE Serviceguard for Linux version 12.80.00 (or later), perform the following steps: Click the following link: Hewlett Packard Enterprise Support Center Enter a product name (e.g., "HPE Serviceguard for Linux") in the text search field and wait for a list of Suggested Products to display. From the Suggested Products list displayed, identify the desired product and select it. The page should refresh to display the "DRIVERS AND SOFTWARE" tab and the components that support the selected product. From the "DRIVERS AND SOFTWARE" expandable filter menus on the top of the page: Locate and select the appropriate HPE Serviceguard for Linux edition (Base, Advanced, or Enterprise) and version (12.80.00 or later). Note: To ensure that you have selected the latest version of the firmware/driver, click the Revision History tab to check if a new version of the firmware/driver is available. For more important information, review the Release Notes tab. Click the Download button. Once the cluster is fully updated to 12.80.00 on all nodes, go to https://myenterpriselicense.hpe.com/ and search for “12.80.03” to locate and download the appropriate matching .tar file for the version of HPE Serviceguard you are licensed to run (either Advanced or Enterprise). Unpack the tar file into a temporary directory and view the README.txt file included in the tar archive for a complete discussion of patch update methods and alternatives. Update all cluster member nodes to 12.80.03 to get the official fix for this issue. After Modification: Start the SAP packages and confirm that they are up and running. If further assistance is needed with this issue, contact HPE Customer Support, and reference this number: a00124486. If the Resolution does not resolve the issue, contact your local country HPE Customer Support or log a case via the HPE Support Center .