on 12-12-2011 7:18 AM
Hi Experts,
The dump MEMORY_NO_MORE_PAGING is due to overload of SAP paging memory.
Short text
SAP paging overflow when storing data in the ABAP/4 memory.
I have check profile parameter with rz11
rdisp/PG_MAXFS
Dflt value 32768
ProfileVal 32768
Current value 32768
Al so I am not able to change rdisp/PG_MAXFS parameter in rz10 bcs itu2019s not shown in profile list.
Thanks in advance.
Regards,
Rahul.
Hi,
Please follow the checklist below
1) Tune your SAP buffer using tcode ST02
2) Ensure that you have sufficient RAM in your system and swap size is configured by a thumb rule of Swap = 3 * RAM
3) Check for proper shared memory segment configuration using the command
sappfpar -check pf=<path of instance profile>
Hope above steps are useful.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear experts,
Even i am facing the same problem,
We are encountering a system dump “MEMORY_NO_MORE_PAGING” while maintaining the table ZXXF_PC_MAPPING using SM30 in ERA 310 and ERO 100 system.
There is a statement EXPORT TO MEMORY which is exporting an internal table with 800,000+ records.
According to our analysis, it seems that this is related to Profile parameter “rdisp/PG_MAXFS”.
please do the needful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make your file simple and set PHYS_MEMSIZE as per SAP note 88416 and delete mentionned parameters from that note.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello all.
To Eric Brunelle
Make your file simple and set PHYS_MEMSIZE as per SAP note 88416 and delete mentionned parameters from that note.
I'm think this will not work because the rdisp/PG_MAXFS are not controled in zero memory management.
P.S. my mistake , i recheck and this parameter are controlled in Zero m.m.
so Solution from Eric are more elegance.
to Orkun Gedik
No need to change rdisp/PG_SHM value. This is value will be allocated from physical memory
and you think this is are bad if this will be allocated from memory ? This is good if you not have general problem with memory
For first time i will suggest you to set both parameters (create this parameters in instance profile if you not do it yet) :
rdisp/PG_MAXFS = 100000
rdisp/PG_SHM = 80000
If you do not want to use PHYS_MEMSIZE
And check in st02 utilization at later point in time.
Regards.
Hi Sergo,
I am not same way with this you, by 16 Gb physical machine. This is because, I would rather to give more physical to the extended memory area rather than paging area. During the runtime, extended memory is utilizing more than paging area.
So, assume that no longer physical memory left on the system, then the extended memory will be allocated from swap memory which will lead more performance problem, over the system.
In short, you should take a look at to the memory utilization statistics, before you choose to use paging memory from disk or memory.
Because of this reason by the 16 Gb configuration, I recommended to use disk instead of physical memory, first.
Best regards,
Orkun Gedik
Hello Orkun Gedik.
We do not know for which this system is used, how memory are configured and so on.
In general I try to use all possible memory that would be less I / O .
Now we only know -- SAP paging memeory is used up.
Yes this memory are less critical in terms of performance but if OS haves this 640 MB (this is are not so big)
for free , why not use it ?
I see many Dev and Qas systems witn 8 and 10 gb memory at all and 5GB free for example.
Regards.
increasing parameters might not help!
if the request that failed is trying to fetch all the data from a table with billions of entries, it is completely normal to fail.
Rahul must investigate what was chosen in the selection screen and validate this with a functional specialist. IF this is a Z program, it should also be investigated with an abapper.
if alll looks fine, then, yes, increase parameters and/or RAM and/or pagefile.
Hi,
There are only two parameters related with the issue, as below;
rdisp/PG_MAXFS = Paging file size on the OS
rdisp/PG_SHM = Paging buffer size
>> Al so I am not able to change rdisp/PG_MAXFS parameter in rz10 bcs itu2019s not shown in profile list.
If it is not exist, then you should add this parameter after you imported latest profile parameters into the system.
You can check the note 1081722 - SAP Paging in shared memory, for the further details.
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you pls explain how much value requires for the same?
disp/PG_MAXFS = Paging file size on the OS ?
rdisp/PG_SHM = Paging buffer size ?
My system default sizing
rdisp/PG_MAXFS
Dflt value 32768
ProfileVal 32768
Current value 32768
rdisp/PG_SHM
Dflt value 16384
ProfileVal 16384
Current value 16384
Thanks & waiting for help.
Regards,
Rahul.
Hi Rahul,
you should set up your system in a way, that the SAP AS should not use the Roll Mem.
Please check ST02 of your app servers and tell us the value for "Extended memory" Max use and In Mem.
As a rule of thumb, the Max use of your extended mem sould not be more than 2/3 of your In mem.
Please tell us your values for:
ztta/roll_first (should be 1 which means, do not uses roll buffer)
ztta/roll_extension (maximum roll extension)
em/initial_size_MB (maximum
abap/heap_area_dia
abap/heap_area_nondia
If your DB Server is on the same host, the Memory settings for it (e.g. Max/min Data cache)
Kind regards
Manuel
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.