Skip to Content
Product Information
Author's profile photo Soeren Schmidt

saptune 3 is here!

A few weeks ago I announced the upcoming release of saptune 3 https://blogs.sap.com/2021/09/28/saptune-3-is-on-the-horizon/ and what it will bring.

Now the time is up!

Around the end of last week saptune 3.0.0 turned up (almost) in the official repositories for:

  • SUSE Linux Enterprise Server for SAP Applications 12 SP3
  • SUSE Linux Enterprise Server for SAP Applications 12 SP4
  • SUSE Linux Enterprise Server for SAP Applications 12 SP5
  • SUSE Linux Enterprise Server for SAP Applications 15 (in a few days)
  • SUSE Linux Enterprise Server for SAP Applications 15 SP1
  • SUSE Linux Enterprise Server for SAP Applications 15 SP2
  • SUSE Linux Enterprise Server for SAP Applications 15 SP3

The SLES for SAP Applications Guide (https://documentation.suse.com/) as well as SAP Note 1275776 have been updated.
As always the man pages shipped with the package are the most detailed source of information.

For those who love to lean back and watch some videos to see how things work, I plan to start with a technical saptune series on the YouTube SUSE Products channel very soon. Watch out for a blog post here about it!

Assigned Tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Achim Vornberger
      Achim Vornberger

      Hello Soeren,

      I had some issues with saptune 3 and systems running in the cloud (Azure, GCP) with the official SUSE images.

      The first one is not really a saptune issue.But saptune_check reports failed services. And one of them is apparmor. From my perspective the service is not able to run because the image seems to be a minimal installation and the pattern "apparmor" is not completely installed. And so the service could not start because of missing profiles. And the profiles are part of a package which is not installed in the image. So maybe you could forward this issue to the colleagues who are responsible for building the images for the marketplaces of the hyperscaler. According to the SAP notes the apparmor pattern should be installed starting with SLES15.

      But is a failed service a problem for saptune? In my case I also had an failure in the fstab, causing a panic during the startup of saptune. Because of the two failures I'm not sure if the [FAIL] because of the services was also a showstopper or not.

      So I fixed both issues and saptune was running. But not all parameters were applied. "saptune solution enabled" said "HANA (partial)". I tried it with "saptune solution apply HANA" but the answer war "There is already one solution applied". At the end I had to revert the solution to be able to apply it again. Is this the correct way to correct an already, but only partially, applied solution?

      Kind Regards

      Achim

      Author's profile photo Soeren Schmidt
      Soeren Schmidt
      Blog Post Author

      Hello Achim,

      We are preparing an update package for saptune (3.0.1) currently which should be available within the next few weeks. Besides some minor bug fixing it also contains a new version of saptune_check.

      That version will report a degraded system (services failed) only as a warning not a fail. If sapconf.service or saptune.service failed, this will reported as an error by the service check itself.

      It is hard to tell if a failed service (besides saptune itself of cause) can be a problem. At least it indicates, that something is not right on the system and this needs to be investigated. It might cause issues, it might not. We decided to keep this degradation check in saptune_check to point to ( potential) problems.

      I guess the partial applied solution is one of the bugs I mentioned. If a solution is applied, the update to v3 adds the new Cloud Notes, but marks them as manualy removed. This leads to a partial solution. The only workaround is exactly that would you did. Revert everything and re-apply the solution. Sorry for that.
      The upcoming update will fix this.

      Regarding the Marketplace images. Would you please open a SR or SAP Incident (BC-OP-LNX-SUSE) for this? This should ensure proper attention.

       

      Sören