Sap Note

SAP Note 133909 Maximum value for PG_MAXFS, PG_SHM,
ROLL_MAXFS, ROLL_SHM
Note Language: English

Version: 8 Validity:

Valid Since 22.07.2010

Summary
Symptom
Transactions terminate withmessages such as:
SYSTEM_NO_MORE_PAGING, EXTRACT_NO_MORE_PAGING, MEMORY_NO_MORE_PAGING
Transactions terminate and refer to problems in the roll memory such as:
get block: no more free blocks
putblock: BlockId %ld too high (%ld)

Other terms
PAGFIL.DAT (Windows) or PAGFIL (Unix and Linux)
ROLL, roll file, roll buffer

Reason and Prerequisites
Due to special applications, especially whenyou use
the ABAP EXTRACT language constructs excessively, an overflow
of the SAP paging file occurs.
However, since "normal" internal tables are no longer stored
in the paging area as of Release3.0B, this problem only affects special
applications in which the predefined size of the page file is not large
enough.

Solution
Use the following profile parameter to increase the size of thepaging area
of the application server:
rdisp/PG_MAXFS =
Here, stands for the size of the paging area in blocks of 8 KB. Up
to a value of 250,000, you must simply make sure that there issufficient
space for the paging file in the data directory of the application server.
If the value is 250,000, the size of the paging file can be up to 2GB.
(See also Note 0097497 for the recommended globalsetting)
If the parameter value is greater than 250,000, you must take into account
other restrictions, which are explained below:
On 32-bit platforms, the size of the paging file is limited to 2GB.
A part of the paging area can be buffered in the shared memory, but the
buffering is severely limited by the address space restriction on 32-bit
platforms. The size of the buffered portion inthe paging is determined by
parameter rdisp/PG_SHM = . Its value is also specified in 8 KB
blocks.
Therefore, the following applies to the maximum value of rdisp/PG_MAXFS:
rdisp/PG_MAXFS must be...