SAP note 1771258 and nofile parameter for HANA

[frepkovsky]

Hello,

In saptune v2, note 1771258 is activated with HANA and NETWEAVER solution. Current nofile ulimit 65536 recommendation from SAP note 1771258 is not valid for HANA anymore.

HANA Lifecycle Manager (hdblcm) manually enters nofile value 1048576 to /etc/security/limits.conf (seems since at least HANA1 SPS122.24s1). On our question raised to SAP support, why this change in HANA recommended parameters is not reflected in SAP Note 1771258, they replied the note is only for SAP Application servers not for HANA.

According to SAP support, recommended OS parameters for HANA are described in SAP note 2600030. Chapter 3 "Operating system parameter recommendations" contains the reference to "nofile".

The correct size can then be found in the documentation:
https://help.sap.com/viewer/2c1988d620e04368aa4103bf26f17727/2.0.05/en-US/82e4575eec664846a9918e9ed1d90d41.html

Parameter     Description                        Value          Location
nofile        Open file descriptors per user     1048576        /etc/security/limits.conf

Do you plan to update saptune HANA solution by this recommendation? As note 1771258 is still valid for NETWEAVER maybe the best way is do not activate 1771258 with HANA solution but create new note with correct nofile parameter for HANA and activate the new note with HANA solution.

Thanks

Frantisek

[angelabriel]

Hi Frantisek,

yes I know. This is an ongoing discussion with SAP at the moment.
But yes, with the next version of saptune we will remove the SAP Note 1771258 from the HANA solution(s), as this was really a fault. Note 1771258 is only a Netweaver, but NOT a HANA note.
Regarding the value of nofile there are still discussions, if there will be a separate HANA Note for this setting or what else will be the reference for saptune and what will be the expected value, as some newer versions of systemd seem to raise this value too.
So it's under investigation and a result will be part of the next saptune version.

[frepkovsky]

Hi Angela,

Perfect, many thanks for quick confirmation this known problem and will be addressed in next release!

Best regards
Frantisek