8 Tuning systems with saptune #

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

Note: Combining optimizations

It is possible to combine solutions and notes. However, only one solution can be active at a time. In rare cases, notes can have conflicting options or parameters. Arrange your notes carefully to avoid conflicts. The last note always takes priority over conflicting options or parameters of previous notes.

To disable and stop saptune, run:

# saptune service disablestop

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

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.

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

# saptune note customise NOTE

# saptune note create NOTE

# 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

# 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

# saptune note show NOTE

# saptune note simulate

# saptune solution simulate

# saptune note revert NOTE

# saptune note revert all

# saptune note edit NOTE

# saptune note enabled

# saptune note applied

This chapter explains how to work with SAP Solutions.

# saptune solution create SOLUTION

# 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

# 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]:

# saptune solution show SOLUTION

# saptune solution revert SOLUTION

# saptune solution edit SOLUTION

# saptune solution enabled

# saptune solution applied

To see the current status of saptune, run the following command:

# saptune status

The output contains the following:

If a problem occurs, use the saptune_check command (in version 3.1, you can also use the command saptune check) that runs checks, reports problems and offers advice on how to solve them.

Starting with version 3.1, saptune supports machine-readable output (JSON) for the following commands:

The machine-readable output makes it possible to integrate saptune into scripts and configuration management solutions.

To generate JSON output, add --format json as the first option, for example:

> saptune --format json note applied | jq
{
"$schema": "file:///usr/share/saptune/schemas/1.0/saptune_note_applied.schema.json",
"publish time": "2023-08-29 17:05:45.627",
"argv": "saptune --format json note applied",
"pid": 1538,
"command": "note applied",
"exit code": 0,
"result": {
    "Notes applied": [
    "941735",
    "1771258",
    "1980196",
    "2578899",
    "2684254",
    "2382421",
    "2534844",
    "2993054",
    "1656250"
    ]
},
"messages": []
}

If a command does not yet support JSON output, the command fails with the result block set to "implemented": false:

[+]
> saptune --format json staging status | jq
{
"$schema": "file:///usr/share/saptune/schemas/1.0/saptune_staging_status.schema.json",
"publish time": "2023-08-29 17:08:16.708",
"argv": "saptune --format json staging status",
"pid": 1653,
"command": "staging status",
"exit code": 1,
"result": {
    "implemented": false
},
"messages": []
}

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. In certain situations, it is preferable to deploy bug fixes and new features while leaving modifications to the system configuration out.

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

Important

With the current implementation, a package update overwrites the staging if staging is enabled.

Staging is disabled by default, and it can be enabled with the following command:

# saptune staging enable

From that point, SAP Note and SAP Solution changes shipped by a saptune package are put in the staging area. To view the staging area, run:

# saptune staging list

You can print a tabular overview of the differences of the SAP Note and SAP Solution in the staging and working area with the following command:

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

After reviewing the differences, you can perform an analysis to see if a release has potential issues or requires additional steps. To do this, run the following command:

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

To release an SAP Note or an SAP Solution from the staging area, use the command as follows:

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

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

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: 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).

See the following man pages:

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