SAP Knowledge Base Article - Preview

2903167 - Standalone Enqueue Server (ENSA) MEMORY LOW

Symptom

Any of following symptoms is noticed:

  • A lot of enqueue locks in the system even Lock Table Overflow
  • work processes running "enqueue response" for short period
  • enqueue locks which are supposed to be released are still in SM12

The following error is reported in the Standalone Enqueue Server (ENSA) trace file dev_enqio_X:

[Thr XX] *** WARNING => MEMORY LOW ==> only 0 slots of <Max memory blocks> left (warning limit 0) [ensutil.cpp ]
[Thr XX] Please refer to note 920979
[Thr XX] *** ERROR => IOThread::WalkNet(): the request failed to initialize correctly: send response to client [eniothread.c ]
[Thr XX] QueuedIORequest:handleFatalError: fatal error on request enqueue request:XXXXXXX with error 103 called
[Thr XX] send error response to client
[Thr XX] *** ERROR => EnqReqClass::initrec: no memory for netdata conversion [ensenque.cpp]
[Thr XX] *** ERROR => IOThread::WalkNet(): the request failed to initialize correctly: send response to client [eniothread.c ]
[Thr XX] QueuedIORequest:handleFatalError: fatal error on request enqueue request:XXXXXXX with error 103 called
[Thr XX] delete request


Read more...

Environment

  • Standalone Enqueue Server (ENSA)
  • ASCS
  • SCS

Keywords

 Locks, Lock table, MEMORY LOW, SM12, Snapshots, Load, Overflow, Query, REMOTESA, enqueue/dequeue request, enque/server/req_block_count, enque/server/query_block_count. . , KBA , BC-CST-EQ , Enqueue , 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.