Post Ehp7 Upgrade we are getting the below dump, found the given SAP Notes to match
133909 - Maximum value for PG_MAXFS, PG_SHM, ROLL_MAXFS, ROLL_SHM
1563748 - MEMORY_NO_MORE_PAGING" dump occurs
The current value of rdisp/PG_MAXFS parameter is 32768, is it okay to increase this parameter or any other possible solutions are available for this.
Thanks in advance!!!
Category Resource Shortage
Runtime Errors MEMORY_NO_MORE_PAGING
SAP Paging overflow when storing data in the ABAP memory
In the current program, memory has been requested from SAP Paging. This
request could not be complied with.
What can you do?
Note which actions and entries caused the error to occur.
Consult your SAP administrator.
Using transaction ST22 for ABAP dump analysis, you can view, manage,
and retain termination messages for longer periods.
The ABAP runtime system and the ABAP Compiler store different types of
data using a common interface in various parts of SAP Paging. These
types of data include the ABAP memory (EXPORT TO MEMORY), the
parameters for SUBMIT REPORT, CALL DIALOG and CALL TRANSACTION USING
aswell as internally defined macros (DEFINE).
To store further data in SAP Paging, a new SAP Paging block needs to be
allocated. No more blocks were available in SAP Paging however.
When the SAP Paging overflow occurred, the ABAP memory contained
entries for 39 different IDs.
The ABAP memory has been deleted to allow error handling.
How to correct the error
The amount of memory (in bytes) used at termination time was:
Roll area...................... 0
Extended memory (EM) 779879376
Assigned memory (HEAP) 0
Paging area.................... 40960
Maximum address space.......... 4294967295
You can use transaction SM04 and then choose Goto -> Memory to display
an overview of roll memory usage and paging memory usage by the active
users and their transactions. Clarify whether either this program or
another one is using too much memory.
The system log shows you more information about the current
termination. Check whether an unexpected recursion has occurred.
Determine whether the error also occurs when the data volume is low.
Check the profile (parameter "rdisp/PG_MAXFS", -> Installation Guide).
Is the disk or file system where the paging file is located too full to
be extended, even if the size specified in the profile has not been
reached? Is the operating system configured so that files can actually
be this large?
The ABAP processor saves various types of data in SAP Paging memory:
(1) Datencluster (EXPORT ... TO MEMORY ...)
(2) Parameters when calling programs (SUBMIT REPORT ...), dialog
modules (CALL DIALOG ...) and transactions (CALL TRANSACTION USING
(3) Macros defined internally in programs (DEFINE ...)
Wherever programs cause an overflow in SAP Paging, the relevant
statements should therefore be checked.
The EXPORT statement is particularly critical, especially if many large
internal tables are written to internal memory, possibly using
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:
"CL_IM_FI_ITEMS_PT_CBR=========CP" bzw. CL_IM_FI_ITEMS_PT_CBR=========CM001
If you cannot solve the problem yourself, please send the following
information to SAP:
1. This description of the problem (short dump)
To do this, choose System -> List -> Save -> Local File (unconverted)
on the screen you are in now.
2. A suitable system log
To do this, call the system log in transaction SM21. Restrict the time
interval to ten minutes before the short dump and five minutes after
it. In the display, choose System -> List -> Save -> Local File
3. If these are programs of your own, or modified SAP programs: Source
code of these programs
To do this, choose More Utilities -> Upload/Download -> Download in
4. Details regarding the conditions under which the error occurred or
which actions and input caused the error.
SAP Release..... 740
SAP Basis level 0004