2524578 - Standstill scenario caused by lack of EG (extended global memory) | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2524578 - Standstill scenario caused by lack of EG (extended global memory)

Symptom

  • The affected instance suffers from an apparent standstill situation.
  • Most actions will just hang and new users cannot logon to the application server.
  • The following warning entry is noticed at work process trace files:

 *** WARNING => MtxLock xxYYxxYYxxYY EMADM owner=<wp number> deadlock ? [mtxxx.c 2574]

  • By extracting the C-STACK from the work process number displayed as the mutex holder (above), the following (or similar) is seen:

(SemRq+0x596)[0x1565506]
(EgIGlobalLock+0x18)[0x1fc63b8]
(EgGetPtr+0x2d)[0x1fc65dd]
(EmHyperContextCreate+0x90)[0x1fbad20]
(ThEmInit+0xac)[0x15ab14c]
(ThSessionInit+0x2f1)[0x1573661]
(TskhLoop+0x1362)[0x1589af2]
(ThStart+0x2bc)[0x4ab317]
(DpMain+0x3b3)[0x1530a03]

  • You also notice that a few processes seem to be waiting for semaphore 39, through DPmon output or through the work process table (Transaction SM50).

Read more...

Environment

  • SAP Netweaver release independent

Product

SAP NetWeaver all versions

Keywords

semaphore 36, mutex, freeze, hanging situation, extended global, SAP memory , KBA , BC-CST-DP , Dispatcher, Task Handler , 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 ONE Support launchpad (Login required).

Search for additional results

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