SAP Knowledge Base Article - Preview

3639087 - SUSE: dispatcher is not started due to the error "e=28 semget" in Oralce + SUSE Linux env

Symptom

  • The disp+work dispatcher failed to start, and the following error was observed in the dev_disp file:
    *** ERROR => e=28 semget(20216,1,2016) (28: No space left on device) [semux.c 500]
    *** ERROR => ThrRegisterSem: SemInit(16) failed [thxxrun1.c 373]
    *** ERROR => ThCallHooks: event handler ThrRegisterSem for event BEFORE_DB_CONNECT failed (-1).

  • The sapconf or saptune is already enabled and started in the system but kernel.sem is not set properly by sapconf or saptune.

  • In the log (ex, boot.txt), it it observed "oracle-setup" program is changing these values:
    sysctl-logger[903]: oracle-setup[1891](systemd[1]) initated change of kernel/shmmax from 18446744073709551615 to 3294967296
    oracle-setup[1891]: Shared memory:      SHMMAX=3294967296  SHMMNI=4096  SHMALL=2097152
    sysctl-logger[903]: oracle-setup[1891](systemd[1]) initated change of kernel/shmall from 1152921504606846720 to 2097152
    oracle-setup[1891]: Semaphore values:   SEMMSL=1250  SEMMNS=32000  SEMOPM=100  SEMMNI=256


Read more...

Environment

  • SAP + Oracle on SUSE Linux
  • SUSE Linux in VMware

Product

SAP NetWeaver all versions

Keywords

dispatcher not starting, semaphore error, e=28 semget, SUSE Linux, kernel.sem, oracle_server pattern, orarun , KBA , BC-OP-LNX-SUSE , SUSE Linux , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.