SUSE Linux Enterprise Server for SAP Applications 12 SP2

Release Notes

SUSE Linux Enterprise Server for SAP Applications combines SUSE Linux Enterprise Server and its High Availability Extension with additional software specifically meant to simplify running and managing SAP applications. These are the release notes of SLES for SAP Applications.

Manuals can be found in the docu directory of the installation media for SUSE Linux Enterprise Server for SAP Applications. Any documentation (if installed) can be found in the /usr/share/doc/ directory of the installed system.

Publication Date: 2017-08-18, Version: 12.2.20170817

1 SLES for SAP Applications

Make sure to also review the release notes for the base product, SUSE Linux Enterprise Server 12 SP2 which are published at

1.1 Support Statement for SLES for SAP Applications

Support requires an appropriate subscription from SUSE. For more information, see

General Support Statement

The following definitions apply:

  • L1: Installation and problem determination - technical support designed to provide compatibility information, installation and configuration assistance, usage support, on-going maintenance and basic troubleshooting. Level 1 Support is not intended to correct product defect errors.

  • L2: Reproduction of problem isolation - technical support designed to duplicate customer problems, isolate problem areas and potential issues, and provide resolution for problems not resolved by Level 1 Support.

  • L3: Code Debugging and problem resolution - technical support designed to resolve complex problems by engaging engineering in patch provision, resolution of product defects which have been identified by Level 2 Support.

SUSE will only support the usage of original (unchanged or not recompiled) packages.

2 Features

This section includes an overview of major new features provided by SUSE Linux Enterprise Server for SAP Applications.

2.1 saptune: Comprehensive System Tuning Management for SAP Applications

Automatically adjust system parameters to allow running SAP applications at satisfactory performance.

SLES for SAP Applications 12 SP2 now ships with the system tuning utility saptune. It can be used to replace sapconf (which is still available, however). The utility unleashes the full potential of system hardware for all SAP workloads by optimizing the CPU scheduler, memory management, disk/network I/O and more. saptune can also tune for the following scenarios:

  • SAP S/4 HANA: These applications use the same tuning techniques that also apply to SAP HANA and SAP NetWeaver and they do not require special tuning techniques.

  • Virtualized environments: You are advised to carefully review tuning techniques described by SAP in various SAP notes with regard to virtualized environments, especially the parameters involving the hypervisor software itself. saptune helps implement SAP Note 2161991 by adjusting the I/O scheduler. This technique is generally favorable in all virtualized guests and cloud instances.

For information about the usage of saptune, see the saptune documentation.

2.2 Benchmarking HANA Performance Under Optimized System Configuration

Optimize the operating system configuration for running SAP HANA benchmarks.

The new program saptune can automate system optimization to unleash the full potential of your SAP HANA deployment. Explore all tuning options of the program and find the best combination for your system with SAP HANA benchmarks. For information about the usage of saptune, see the saptune documentation.

2.3 Accessing SUSE Product Registration, Modules, and Extensions from the Desktop

In SLES for SAP 12 SP2, the desktop includes a shortcut Product Registration which allows starting YaST's SCC Registration module. This enables you to easily discover software and services that support SAP solutions.

2.4 Monitor and Control saprouter via systemd

You can now monitor and control the SAP Network Interface Router via systemd with the new service saprouter.service (contained in the software package saprouter-systemd).

Make sure to install the SAP Network Interface Router first, then install the package saprouter-systemd. You can then control the SAP router daemon via standard systemd mechanisms and commands.

2.5 New Features in HANA Firewall Configuration Editor

The revamped HANA Firewall configuration editor in YaST offers a simplified user interface and enhanced configuration capabilities:

  • If there are new SAP HANA instances installed after an initial firewall configuration, a dialog will prompt you to apply a firewall setup to the new instances.

  • The editor can generate a default set of firewall rules that open running SAP HANA services on all network interfaces, including the services required for a high availability setup.

2.6 Support for SAP HANA TDI Environments in the SAP Installation Wizard

The SAP Installation Wizard now follows SAP's recommendation for partitioning and creates the following setup:

  • /hana/data, size: RAM*1

  • /hana/log, size: RAM*1, with a maximum of 512 GB

  • /hana/shared, size: RAM*1, with a maximum of 1 TB

  • /usr/sap, size: 52 GB

2.7 cryptctl: New Disk Encryption Utility

The new disk encryption utility cryptctl helps set up LUKS-based disk encryption using randomly generated keys and safely keeps them on a dedicated key server.

cryptctl comprehensively and transparently protects application data including configuration files, logs, and databases. It does so fulfilling many encryption compliance requirements. The encryption mechanism takes full advantage of hardware acceleration to improve speeds, incurring only negligible overhead to applications such as SAP NetWeaver.

2.8 Support for Scale-Out Scenarios in SAPHanaSR

The SAPHanaSR resource agents now also support SAP HANA System Replication for scale-out in the performance optimized scenario (package SAPHanaSR-ScaleOut).

3 Systems Management

3.1 Requirements for Installation of SAP HANA SPS 12

Before installing HANA SPS 12 on SLES for SAP 12 SP2, make sure that your hardware meets all prerequisites. The root partition must have a size of at least 25 GB to fit the operating system and a copy of the SAP HANA installer. Ideally, use a size of 50 GB for the root partition.

For more information, see SAP Note 1944799 ( and the Configuration Guide attached to it.

3.2 Cannot Log In to SAP HANA Graphical User Interface

When a SAP HANA database is installed on SLES for SAP, the database administrator user is not able to log in to the graphical interface. This issue also occurs when installing with the newest available release of the SAP HANA installer.

There are currently no workarounds available.

3.3 Enrolling in a Microsoft Active Directory Domain via YaST

You can configure a SLES computer to become a member in Microsoft Active Directory to leverage its user account and group management. In previous versions of SLES, enrolling a computer in a Microsoft Active Directory was a lengthy and error-prone procedure.

In SLES 12 SP2, YaST ships with the new configuration tool User Logon Management (previously Authentication Client) which offers a powerful yet simple user interface for joining an Active Directory domain and allows authenticating users using those domain accounts. In addition to Active Directory, the editor can also set up authentication against a generic Kerberos or LDAP service.

4 Miscellaneous

4.1 MSR Cannot Be Modified When UEFI Secure Boot Is On

Write access to MSRs (model-specific registers) allows userspace applications to modify the running kernel which runs counter to the goals of UEFI Secure Boot. Therefore, MSRs cannot be written to by tools like cpupower to control processor performance when UEFI Secure Boot is enabled on a system.

This also prevents tuning tools, such as saptune and sapconf from working correctly.

The only current workaround is disabling Secure Boot.

5 How to Obtain Source Code

This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at Also, for up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Requests should be sent by e-mail to or as otherwise instructed at SUSE may charge a reasonable fee to recover distribution costs.

6 More Information and Feedback

  • Read the READMEs on the media.

  • Get detailed changelog information about a particular package from the RPM:

    rpm --changelog -qp FILE_NAME.rpm

    FILE_NAME is the name of the RPM.

  • Check the ChangeLog file in the top level of the first medium for a chronological log of all changes made to the updated packages.

  • Find more information in the docu directory of first medium of the SLES for SAP Applications media.

  • contains additional or updated documentation for SLES for SAP Applications.

  • For the latest product news from SUSE, visit

Copyright © 2010- 2017 SUSE LLC.

Thank you for using SUSE Linux Enterprise Server for SAP Applications in your business.

The SUSE Linux Enterprise Server for SAP Applications Team.

Print this page