Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose

To explain the cause of differences between OS and SAP limits and help to set them correctly.

Overview

What limit is setup on OS level for SAP system administrator user (sidadm) and what is known for SAP in fact? What steps are necessary to set them in a correct way? We'll check this.

What limit is setup on OS level for SAP system administrator user (sidadm)?

This can be checked this way:

  • login by sidadm user
  • run ''ulimit -a' or 'limit' command (depends on the shell - sh, bash, csh, ksh, etc...)

An example:

What limit is known for SAP in fact?

There are two cases.

  1. The same as on OS level
  2. Other (usually lower) than on OS level - in this case e.g. Too many open files error could occur

Case 1.

Case 2.

How could be the limit different?

The limit is determined by sapstartsrv process. This is started automatically while OS boot by sapinit script. As this is executed by root, root's limit is taken instead of sidadm's.

To overcome this follow the recommendations of SAP note 1437105 and 1827960. Steps (among others, for details see the notes) 

  • install newest sapinit
  • add limit.<...>=<value> parameter in /usr/sap/sapservices
  • restart sapstartsrv

Related Content

Related SAP Notes/KBAs

SAP Note 1437105: Operating system limits for SAP instances
SAP KBA 1827960: Operating system limits for SAP instances

  • No labels