Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise Server for SAP Applications 15

9 Tuning systems with saptune Edit source

This chapter presents information about tuning SUSE Linux Enterprise Server for SAP Applications to work optimally with SAP applications.

Using saptune, you can tune a system for SAP NetWeaver, SAP HANA/SAP BusinessObjects, and SAP S/4HANA applications.

Important
Important

This chapter describes saptune version 3 which does not use tuned anymore.

9.1 Enabling saptune Edit source

To enable saptune to tune an SAP application, use the following procedure:

  1. To tune a system, first find a tuning solution. To find the appropriate solution, use:

    tux > saptune solution list

    saptune knows the following tuning solutions (groups of SAP Notes):

    • BOBJ Solution for running SAP BusinessObjects.

    • HANA Solution for running an SAP HANA database.

    • MAXDB Solution for running an SAP MaxDB database.

    • NETWEAVER Solution for running SAP NetWeaver application servers.

    • S4HANA-APPSERVER Solution for running SAP S/4HANA application servers .

    • S4HANA-APP+DB Solution for running both SAP S/4HANA application servers and SAP HANA on the same host .

    • S4HANA-DBSERVER Solution for running the SAP HANA database of an SAP S/4HANA installation .

    • SAP-ASE Solution for running an SAP Adaptive Server Enterprise database.

    • NETWEAVER+HANA Solution for running both SAP application servers and SAP HANA on the same host.

    Alternatively, you can tune the computer according to recommendations from specific SAP Notes. A list of notes that you can tune for is available via:

    root # saptune note list
    • To set up saptune with a preconfigured solution, use:

      root # saptune solution apply SOLUTION
    • To set up saptune for the recommendations of a specific SAP Note, use:

      root # saptune note apply NOTE
    Note
    Note: Combining optimizations

    You can combine solutions and notes. However, only one solution can be active at a time. In rare cases, notes can have conflicting options or parameters. To avoid conflicts, order your notes, keeping in mind that the last note always overrides conflicting options or parameters of previous notes.

  2. To start saptune and enable it at boot, make sure to run the following command:

    root # saptune service enablestart

    To make sure that sapconf and tuned gets stopped and disabled too, run instead:

    root # saptune service takeover

9.2 Disabling saptune Edit source

To disable and stop saptune, run:

root # saptune service disablestop

9.3 Updating saptune Edit source

To update saptune to a new version, just update the package.

Since a package update can contain updates of SAP Notes and SAP Solutions, restart saptune with saptune service restart to re-apply the tuning. Check afterwards with saptune note verify if all recommendations are still met.

Important
Important

The saptune tool does not rely on tuned anymore. Configuring tuned to set up saptune 3 will not work. To start and enable saptune 3 use one of the following methods:

  • saptune service enablestart

    Enables and starts the saptune.service.

  • saptune service takeover

    Enables and starts the saptune.service and also disables sapconf as well as tuned.

  • saptune daemon start

    Deprecated. Gets redirected to saptune service takeover.

9.4 Managing SAP Notes Edit source

In the following sections you will learn how to create, delete, and rename SAP Notes and much more.

9.4.1 Customizing an SAP Note Edit source

Every SAP Note can be configured freely with:

root # saptune note customise NOTE

The command includes changing a value or disabling a parameter.

9.4.2 Creating a new SAP Note Edit source

It is possible to create a new SAP Note with:

root # saptune note create NOTE

All features of saptune are available.

9.4.3 Deleting an SAP Note Edit source

This command allows deleting a created note, including the corresponding override file if available:

root # saptune note delete test
Note to delete is a customer/vendor specific Note.
Do you really want to delete this Note (test2)? [y/n]: y

The note may not be applied at the time. Keep in mind the following points:

  • A confirmation is needed to finish the action.

  • Internal SAP Notes shipped by saptune cannot be deleted. Instead, the override file is removed when available.

  • If the note is already applied, the command will be terminated with the information, that the note first needs to be reverted before it can be deleted.

9.4.4 Renaming an SAP Note Edit source

This command allows renaming a created note to a new name. If a corresponding override file is available, this file will be renamed too:

root # saptune note rename test test2
Note to rename is a customer/vendor specific Note.
Do you really want to rename this Note (test) to the new name 'test2'? [y/n]: y

The note may not be applied at the time. Keep in mind the following points:

  • A confirmation is needed to finish the action.

  • Internal SAP Notes shipped by saptune cannot be renamed.

  • If the note is already applied, the command will be terminated with the information, that the note first needs to be reverted before it can be deleted.

9.4.5 Showing the configuration of an SAP Note Edit source

The shipped configuration of a note can be listed with:

root # saptune note show NOTE

9.4.6 Verifying an SAP Note or an SAP Solution Edit source

The commands saptune note verify NOTE and saptune solution verify SOLUTION list the following data for each active or requested note:

  • The parameter name

  • The expected value (default)

  • A configured override (created using saptune customise)

  • The current system value

  • Whether the current state is in accordance with the SAP recommendation

9.4.7 Simulating the application of an SAP Note or an SAP Solution Edit source

To show each parameter of a note, use:

root # saptune note simulate

To show each parameter of a solution, use:

root # saptune solution simulate

It lists the current system value and the expected values (default and override).

9.4.8 Reverting a SAP Note Edit source

To revert a SAP Note, run:

root # saptune note revert NOTE

All parameters of this SAP Note will be restored to their values at the time of apply.

To revert anything, run:

root # saptune note revert all

9.4.9 Editing a SAP Note Edit source

Each custom SAP Note can be edited by:

root # saptune note edit NOTE

9.4.10 Listing all enabled or applied SAP Notes Edit source

To list all enabled SAP Notes, run:

root # saptune note enabled

To list all applied SAP Notes, run:

root # saptune note applied

9.5 Managing SAP Solutions Edit source

In the following sections you will learn how to create, delete, and rename SAP Solutions and much more.

9.5.1 Creating a new SAP Solution Edit source

To create a new SAP Solution, run:

root # saptune solution create SOLUTION

9.5.2 Deleting a SAP Solution Edit source

To delete a SAP Solution, run:

root # saptune solution delete myHANA

Solution to delete is a customer/vendor specific Solution.
Do you really want to delete this Solution 'myHANA'? [y/n]: y

The SAP Solution may not be applied at the time. Keep in mind the following points:

  • A confirmation is needed to finish the action.

  • SAP Solutions shipped by saptune cannot be deleted.

  • If the SAP Solution is already applied, the command will be terminated with the information, that the SAP Solution first needs to be reverted before it can be deleted.

9.5.3 Renaming a SAP Solution Edit source

To rename a SAP Solution, run:

root # saptune solution rename myHANA myHANA2

Solution to rename is a customer/vendor specific Solution.
Do you really want to rename this Solution 'myHANA' to the new name 'myHANA2'? [y/n]:

The SAP Solution may not be applied at the time. Keep in mind the following points:

  • A confirmation is needed to finish the action.

  • SAP Solutions shipped by saptune cannot be renamed.

  • If the SAP Solution is already applied, the command will be terminated with the information, that the SAP Solution first needs to be reverted before it can be renamed.

9.5.4 Showing the configuration of a SAP Solution Edit source

To list the configuration of a SAP Solution, run:

root # saptune solution show SOLUTION

9.5.5 Reverting a SAP Solution Edit source

To revert a SAP Solution, run:

root # saptune solution revert SOLUTION

The SAP Solution must be applied. All SAP Notes part of that SAP Solution which still are applied will be reverted.

9.5.6 Editing a custom SAP Solution Edit source

To edit a custom SAP Solution, run:

root # saptune solution edit SOLUTION

9.5.7 Listing enabled/applied SAP Solution Edit source

To list enabled SAP Solution, run:

root # saptune solution enabled

To list applied SAP Solution, run:

root # saptune solution applied

If SAP Notes from an applied SAP Solution have been reverted, the string (partial) has been added to the solution name.

9.6 Verification and troubleshooting Edit source

The see the current status of saptune, run:

root # saptune status

The output contains:

  • status of the saptune, sapconf, and tuned service

  • version of package and running saptune

  • details about configured SAP Solution and SAP Notes

  • details about staging

In case of a problem, run:

root # saptune_check

The script does a deeper analysis, reports any problems and gives advice how to rectify them.

9.7 Staging Edit source

It is possible, that a new saptune package can contain both: binary changes (for example, bug fixes) and new or altered SAP Notes and SAP Solutions. This can be unfavorable for some customers. Installation of bug fixes or new features might be wanted, but altering the systems configuration at the same time might not.

With staging enabled, SAP Note and SAP Solution changes shipped with a package update are not active immediately. They are placed in a staging area, which can be reviewed and released later.

Important
Important

With the current implementation a package update will overwrite the staging if staging is enabled.

Staging is disabled per default. To enable it, run:

root # saptune staging enable

From now on, SAP Note and SAP Solution changes shipped by a saptune package will put in the staging area. To view the staging area, run:

root # saptune staging list

You can print a tabular overview of the differences of the SAP Note and SAP Solution in the staging and the working area by running:

root # saptune staging diff [NOTE...|SOLUTION...|all]

After reviewing the differences you can do an analysis to see if a release has potential issues or might require additional steps afterwards by running:

root # saptune staging analysis [NOTE...|SOLUTION...|all]

To releasea SAP Note or a SAP Solution from the staging area, run:

root # saptune staging [--force|--dry-run] [NOTE..|SOLUTION...|all]

The previous command presents an analysis (see saptune staging analysis) and do the release after asking for confirmation.

9.8 Tuning kernel parameters manually using sysctl Edit source

In addition to or instead of tuning kernel parameters using saptune, you can also use sysctl to make manual adjustments to kernel parameters. However, such changes using sysctl do not persist across reboots by default. To make them persist across reboots, add them to one of the configuration files read by sysctl.

Tip
Tip: sysctl and saptune

If you plan to configure sysctl parameters for your SAP system, consider using saptune as the central tool for managing such configurations.

For more information about sysctl, see the man pages sysctl(8), sysctl.conf(5), and sysctl.d(5).

9.9 For more information Edit source

See the following man pages:

  • man 8 saptune

  • man 8 saptune-migrate

  • man 8 saptune-note

Also see the project home page https://github.com/SUSE/saptune/.

Print this page