SAP Knowledge Base Article - Preview

3244524 - "ERROR => <ES> em/initial_size_MB = xxxxxx too big" in dev_disp

Symptom

There is error in dispatcher trace (the em/initial_size_MB value may be any value larger than 256GB).

dev_disp

<ES> client 0 initializing ....
<ES> EsILock: use Semphore 33 for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
*** ERROR => <ES> em/initial_size_MB = 336496 too big [esxx.c       1671]
*** ERROR => <ES> -or-  em/blocksize_KB = 4096 too small [esxx.c       1675]
<ES> (em/initial_size_MB < 262144) or (em/blocksize_KB = 6144) advised
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
*** ERROR => <EsNT> ES_ADM_SLOTS exceeded, first free: 65408 new: 511 max: 65536 [esnti.c      13
*** ERROR => <EsNT> new Blocks reset to: 128 [esnti.c      1336]
*** ERROR => <EsNT> ES_ADM_SLOTS exceeded, first free: 65536 new: 511 max: 65536 [esnti.c      13
*** ERROR => <EsNT> new Blocks reset to: 0 [esnti.c      1336]


em/initial_size_MB = xxxxxx too big" in dev_disp"> Read more...

Environment

SAP Kernel 7.22 or lower

Keywords

em/initial_size_MB, EM memory , KBA , BC-CST-MM , Memory Management , 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.