Chapter 5. New features and enhancements
5.1. Red Hat Enterprise Linux 9.0 for SAP Solutions
RHEL System Roles for SAP
Ansible Core support for the RHEL System Roles
As of the RHEL 9 GA release, Ansible Core is provided, with a limited scope of support, to enable RHEL supported automation use cases. Ansible Core replaces Ansible Engine which was provided on previous versions of RHEL in a separate repository. Ansible Core is available in the AppStream repository for RHEL. For more details on the supported use cases, see Scope of support for the Ansible Core package included in the RHEL 9 AppStream.
If you require Ansible Engine support, or otherwise need support for non-RHEL automation use cases, create a Case at Red Hat Support.
Full Support for role
sap_hana_installWith the role
sap_hana_install, installing SAP HANA standalone or scale-out is simple and reliable and requires no interactive user input, and there is no need to learn how to configure thehdblcm configfilefor doing an unattended installation. This role had initially been shipped in Technology Preview support and is now fully supported.SELinux file labeling for SAP
The roles
sap_general_preconfigureandsap_hana_preconfigurenow support setting SELinux file labels for running SAP HANA or SAP ABAP application instances on RHEL systems with SELinux in enforcing or permissive mode.SAP HANA Pacemaker
System roles have been enhanced to allow the setup of two-node SAP HANA pacemaker clusters. For Red Hat Enterprise Linux 9.0, it is provided as Technology Preview. For information on Red Hat’s scope of support for Technology Preview features, see Technology Preview Features Support Scope.
HA solutions for SAP
SAP HANA Multitarget System Replication
SAP HANA Multitarget System Replication is now supported in combination with the HA solution for managing SAP HANA Scale-Up System Replication. See Configuring SAP HANA Scale-Up Multitarget System Replication for disaster recovery for more information.
resource-agents-sap-hanaThe following enhancements have been made in version 0.162.1:
-
A new parameter,
HANA_CALL_TIMEOUT`has been added. It fixes the issue of hard-coded timeouts for most `HANA_CALLcommands. - Provision of systemd support.
-
Start and stop resource operation timeouts can now be used for increased
WaitforStarted/WaitforStoppedtimeouts. The minimum timeout remains 3600s. - The logging has been improved.
- The error handling has been improved.
-
A new parameter,
5.2. Red Hat Enterprise Linux 9.3 for SAP Solutions
HA solutions for SAP
- When using the HA solutions for managing HANA Multitarget System Replication, it is also possible to set up a separate inactive cluster for managing the HANA instances at the DR site, which can be activated manually in the event of the primary cluster becoming unavailable. For more details, please refer to Configuring SAP HANA Scale-Up Multitarget System Replication for disaster recovery.
- RHEL HA solutions for SAP now support managing SAP HANA Multitarget System Replication for both HANA Scale-Up and HANA Scale-Out environments, allowing for automated failover with 3 and more replicates. For more details, please refer to Multitarget System Replication.
5.3. Red Hat Enterprise Linux 9.4 for SAP Solutions
HA solutions for SAP
Enabling the SAP HANA
srServiceStateChanged()hook forhdbindexserverprocess failure actionStarting with version 0.162.3, the
resource-agents-sap-hanapackage provides a new SAP HANA hook script for dealing with situations where the HANAhdbindexserverprocess has crashed or is hanging:-
The
ChkSrv.pyhook script uses the SAP HANAsrServiceStateChanged()hook to process HANA events and allow the HA cluster to react to dying or hanging SAP HANAhdbindexserverprocesses. -
The
CHkSrv.pyhook script provides the option to choose the reaction to a crashed or hanging HANAhdbindexerverprocess: either stop or kill the HANA DB, or only log events for monitoring purposes. -
All activity related to the
srServiceStateChanged()HANA hook is logged in a dedicated SAP HANA tracefile.
-
The
The minimum required SAP HANA version to enable this feature is SAP HANA 2.0 SPS4. For more details, refer to Enabling the SAP HANA srServiceStateChanged() hook for hdbindexserver process failure action (optional).
In addition to the new feature, version 0.162.3 (and later) of the
resource-agents-sap-hanapackage also provides the following enhancements:-
Avoids explicit and implicit usage of the
/tmpfile system to keep theSAPHanaSRresource agents working even in situations where the/tmpfile system is full. -
If the
SAPHanaSR.pyhook script successfully reports asrConnectionChanged()event to the cluster, a still existing fallback state file is removed to prevent an override of an already reported SR state. - Improves supportability as it provides the current process ID of the resource agent, logged in resource agent output, and HANA tracefiles.
- Improves the logging of status and actions that the resource agents perform.
-
Avoids explicit and implicit usage of the
RHEL System Roles for SAP
The following enhancements have been made for the roles given below:
-
collection: Ensures Ansible 2.16.1, 2.15.8, 2.14.12 (cve-2023-5764) compatibility. -
collection: Minimum Ansible version is now 2.14. -
preconfigure: Includes SLES related code. Configuring SLES managed nodes is nevertheless unsupported by Red Hat. -
sap_hana_preconfigure: Implements SAP HANA requirements for RHEL 8.8 and RHEL 9.2 and is less restrictive with RHEL versions that are not yet supported for SAP HANA. -
sap_ha_pacemaker_cluster: Improves VIP resource and constraint setup per platform.
-
For more details refer to Red Hat Enterprise Linux System Roles for SAP.
Security
You can now learn about processes and practices for securing Red Hat Enterprise Linux systems against local and remote intrusion, exploitation, and malicious activity. These approaches and tools can create a more secure environment for running SAP HANA. For more details, refer to:
