Register Login

MEMORY_NO_MORE_PAGING dump in tcode ST22

Updated May 18, 2018

Hello SAP Experts,

While checking the short dump in transaction code ST22 I found a short dump MEMORY_NO_MORE_PAGING.

Some time this short dump MEMORY_NO_MORE_PAGING as a result of program executon 

  • In order to regenerate this dump, a high load must be present on the system which might result in the paging memory being exhausted.
  • This issue can also be regenerated by filling the filesystem at usrsapSIDDVEBMGSXXdata in order to make sure there is no more free space.

Please help me to resolve this issue


Comments

  • 26 Jul 2017 1:31 pm Romil Tripathi Helpful Answer

    In order to resolve this issue please do the following:

    First please try to verify the SAP paging usage via t-code ST02 (Buffer Statistics).

    You will notice information about "page area" at the bottom of the screen as shown below

    • Now if the "max usage" value reaches the sum of "in memory" plus "on disk" you are required to increase the parameter rdisp/PG_MAXFS;
    • But before increasing the parameter please check if their is enough space aviailable in your local SAP kernel file system.
    • It is possible to load the entire paging buffer area in the memmory setting rdisp/PG_SHM = rdisp/PG_MAXFS.
  • 26 Jul 2017 1:34 pm Abhijeet Mudgal Helpful Answer

    This short dump MEMORY_NO_MORE_PAGING means that the SAP paging file as dictated by parameter rdispPG_MAXFS is full.


×