Solution : https://service.sap.com/sap/support/notes/133909 (SAP Service marketplace login required)
Summary :
This SAP Note addresses transaction terminations due to overflows in the SAP paging file, particularly under heavy use of ABAP EXTRACT statements. The terminations are flagged by SYSTEM_NO_MORE_PAGING, EXTRACT_NO_MORE_PAGING, and MEMORY_NO_MORE_PAGING errors. These issues primarily affect special applications where the pre-set paging file size is inadequate. The recommended fix involves adjusting the profile parameter 'rdisp/PG_MAXFS' to increase server paging area. Limitations on 32-bit systems restrict the paging file size to 2GB. On 64-bit systems, this limitation does not apply if the file system supports larger files. The note also covers the settings for roll files and shared memory configurations affecting roll buffer and paging buffer, with adjustments recommended based on system architecture and kernel versions.
Key words :
usethe abap extract language constructs excessively, free blocks<roll-fl> put block, sap paging file occurs, parameter rdisp/pg_shm = <size>, 000 + rdisp/pg_shmon 64-bit platforms, parameter rdisp/pg_shm, recommended global setting, cst patch collection 17 2006, symptom transactions terminate, address space restriction
Related Notes :
| 1081722 | SAP Paging in shared memory |
| 182201 | SAPFGVTR: EXTRACT_NO_MORE_PAGING (-> account modification) |