1827960 - Adjusting operating system limits for SAP instances

You are confused about operating system limits of <sid>adm user and known for SAP.
When you run 'csh -c limit' on operating system level with <sid>adm user, the result is similar to:

> csh -c limit
cputime      unlimited
filesize     unlimited
datasize     unlimited
stacksize    8192 kbytes
coredumpsize 0 kbytes
memoryuse    unlimited
vmemoryuse   unlimited
descriptors  100000
memorylocked 64 kbytes
maxproc      31841
maxlocks     unlimited
maxsignal    31841
maxmessage   819200
maxnice      0
maxrtprio    0
maxrttime    unlimited

However, if you run the same command on SAP level, i.e. RSBDCOS0 report, the result is different:

[1]csh -c limit
cputime      unlimited
filesize     unlimited
datasize     unlimited
stacksize    unlimited
coredumpsize 0 kbytes
memoryuse    unlimited
vmemoryuse   unlimited
descriptors  65536
memorylocked 64 kbytes
maxproc      31841
maxlocks     unlimited
maxsignal    31841
maxmessage   819200
maxnice      0
maxrtprio    0
maxrttime    unlimited

You want to know the reason of difference.

• SAP NetWeaver 7.0 (SAP NetWeaver 2004s, SAP NetWeaver 2007) or above and associated products running on it
• UNIX operating systems (AIX, HP-UX, Linux, Oracle Solaris)

sapcontrol , sapstartsrv , SAP Start Service, limit , ulimit , KBA , BC-OP , Operating System Platforms , BC-OP-LNX , Linux , BC-OP-AIX , IBM AIX , BC-CST-STS , Startup Service , BC-OP-HPX , HP-UX , BC-OP-SUN , SUN Solaris , How To