Hello
I have an memory issue. Acctually it happens only in Outbound delivery transaction "Vl02n" in case of an material.
The dump we get is:
Runtime Errors MEMORY_NO_MORE_PAGING
Date and Time 22.05.2013 14:30:05
Short text
SAP paging overflow when storing data in the ABAP/4 memory.
What happened?
The current program requested storage space from the SAP paging area,
but this request could not be fulfilled.
of this area in the SAP system profile.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
The ABAP/4 runtime system and the ABAP/4 compiler use a common
interface to store different types of data in different parts of
the SAP paging area. This data includes the
ABAP/4 memory (EXPORT TO MEMORY), the SUBMIT REPORT parameters,
CALL DIALOG and CALL TRANSACTION USING, as well as internally defined
macros (specified with DEFINE).
To store further data in the SAP paging area, you attempted to
allocate a new SAP paging block, but no more blocks were
available.
When the SAP paging overflow occurred, the ABAP/4 memory contained
entries for 239 of different IDs.
Please note:
To facilitate error handling, the ABAP/4 memory was
deleted.
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 16192
Extended memory (EM)........... 58657760
Assigned memory (HEAP)......... 0
Short area..................... " "
Paging area.................... 16384
Maximum address space.......... " "
By calling Transaction SM04 and choosing 'Goto' -> 'Block list',
you can display an overview of the current roll and paging memory
levels resulting from active users and their transactions. Try to
decide from this whether another program requires a lot of memory
space (perhaps too much).
The system log contains more detailed information about the
termination. Check for any unwanted recursion.
Determine whether the error also occurs with small volumes of
data. Check the profile (parameter "rdisp/PG_MAXFS", see
Installation Guidelines).
Is the disk or the file system that contains the paging file
full to the extent that it cannot be increased, although it has
not yet reached the size defined in the profile? Is the
operating system configured to accommodate files of such a
size?
The ABAP processor stores different types of data in the SAP
paging area. These include:
(1) Data clusters (EXPORT ... TO MEMORY ...)
(2) Parameters for calling programs (SUBMIT REPORT ...),
Dialog modules (CALL DIALOG ...) and transactions
(CALL TRANSACTION USING ...)
(3) Internally defined program macros (DEFINE ...)
Accordingly, you should check the relevant statements in a program
that results in an overflow of the SAP paging area.
It is critical when many internal tables, possibly with
different IDs, are written to memory (EXPORT).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MEMORY_NO_MORE_PAGING" " "
"SAPLCTMS" or "LCTMSF1Q"
"BUILD_MERKMALE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
.....
when trying sappfpar check I get (but do not know how to solve this issue /especially as it happens on production on an cluster node):
F:\usr\sap\PR2\SYS\exe\uc\NTAMD64>sappfpar check
pf=F:\usr\sap\PR2\SYS\profile\
PR3_DVEBMGS03_SAP-6A
===============================================================================
== Checking
profile: F:\usr\sap\PR2\SYS\profile\PR2_DVEBMGS03_SAP-6A
===============================================================================
***WARNING: Unexpected parameter: SAPFQDN =quteks.si
***ERROR: Maximum shared memory segment size exceeded
================================================================
Shared memories exceeding size limit
Key: 6
Size: 3194880000 (-1050.9 MB)
ABAP program buffer
Key: 42
Size: 2200192992 (-1998.3 MB) DB
TTAB buffer
SOLUTIONS: (1) reconfigure your operating system for shared
memory
segment
size of 2048.0 MB minimum
(2)
configure smaller SAP buffers
Shared memory disposition overview
================================================================
Key: 1
Size: 2500 ( 0.0 MB) System administration
Key: 2
Size: 29714812 ( 28.3 MB) Disp. administration tables
Key: 3
Size: 13714400 ( 13.1 MB) Disp. communication areas
Key: 4
Size: 528448 ( 0.5 MB) statistic area
Key: 5
Size: 4096 ( 0.0 MB) SCSA area
Key: 6
Size: 3194880000 (-1050.9 MB)
ABAP program buffer
Key: 7
Size: 14838 ( 0.0 MB) Update task administration
Key: 8
Size: 134217828 ( 128.0 MB)
Paging buffer
Key: 9
Size: 268435556 ( 256.0 MB) Roll
buffer
Key: 11
Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12
Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.
Key: 13
Size: 60500000 ( 57.7 MB) Alert Area
Key: 14
Size: 66400256 ( 63.3 MB) Presentation buffer
Key: 16
Size: 22400 ( 0.0 MB) Semaphore activity monitoring
Key: 17
Size: 2760892 ( 2.6 MB) Roll administration
Key: 18
Size: 1029604 ( 1.0 MB) Paging adminitration
Key: 19
Size: 820002304 ( 782.0 MB)
Table-buffer
Key: 30
Size: 46080 ( 0.0 MB) Taskhandler runtime admin.
Key: 31
Size: 4806000 ( 4.6 MB) Dispatcher request queue
Key: 33
Size: 61440000 ( 58.6 MB) Table buffer, part.buffering
Key: 34
Size: 33554432 ( 32.0 MB) Enqueue table
Key: 41
Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 42
Size: 2200192992 (-1998.3 MB) DB
TTAB buffer
Key: 43
Size: 949423608 ( 905.4 MB) DB
FTAB buffer
Key: 44
Size: 583363064 ( 556.3 MB) DB
IREC buffer
Key: 45
Size: 556465656 ( 530.7 MB) DB
short nametab buffer
Key: 46
Size: 20480 (
0.0 MB) DB sync table
Key: 47
Size: 70657024 ( 67.4 MB) DB CUA buffer
Key: 48
Size: 500000 ( 0.5 MB) Number range buffer
Key: 49
Size: 2968344 ( 2.8 MB) Spool admin (SpoolWP+DiaWP)
Key: 51
Size: 3200000 ( 3.1 MB) Extended memory admin.
Key: 52
Size: 40000 ( 0.0 MB) Message Server buffer
Key: 54
Size: 94511104 ( 90.1 MB) Export/Import buffer
Key: 55
Size: 8192 ( 0.0 MB) Spool local printer+joblist
Key: 57
Size: 1048576 ( 1.0 MB) Profilparameter in shared mem
Key: 58
Size: 4096 ( 0.0 MB) Enqueue ID for reset
Key: 62
Size: 85983232 ( 82.0 MB) Memory pipes
Key: 63
Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64
Size: 4202496 ( 4.0 MB) Online Text Repository Buf.
Key: 65
Size: 4202496 ( 4.0 MB) Export/Import Shared Memory
Key: 1002
Size: 400000 ( 0.4 MB) Performance monitoring V01.0
Nr of operating system shared memory segments: 41
Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....: 41
Shared memory segment size required min..: 3194880000
(-1050.9 MB)
Swap space requirements estimated
================================================
Shared memory....................: 659.2 MB
- Processes........................: 563.4 MB
Extended Memory .................: 4096.0 MB
------------------------------------------------
Total, minimum requirement.......: 5318.7 MB
Process local heaps, worst case..: 5860.7 MB
Total, worst case requirement....: 11179.4 MB
Errors detected..................: 1
Warnings detected................: 1
F:\usr\sap\PR2\SYS\exe\uc\NTAMD64>
Thank yo u a lot in advance
kr
Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.