MEMORY_NO_MORE_PAGING
criticalSAP Paging Area Completely Exhausted
Module: BASIS / Memory
What this means
MEMORY_NO_MORE_PAGING fires when the SAP paging area — a disk-based overflow area used when the extended memory (EM) is full — has itself been completely exhausted. This is a system-wide condition, not just a single user or program. When this dump occurs, multiple users are likely experiencing failures simultaneously. Root causes: an abnormal spike in concurrent memory-intensive programs; memory parameters that have not been scaled with growing data volumes or user count; a runaway program that has consumed all EM and is now depleting the paging area; or a memory leak in a long-running background job.
Check SM50 immediately to identify which work processes are consuming the most memory. Check AL08 for the number of concurrent active sessions. Review RZ11 for em/initial_size_in_MB and the paging area configuration (rdisp/PG_MAXFS, rdisp/PG_SHM). Kill runaway work processes if identified. Increase the paging area size as an emergency measure, then investigate the root cause program. This is a Basis emergency — consider a system restart if the paging area cannot be freed.
Quick Info