Skip to Content
0
Former Member
Jul 04, 2007 at 11:26 AM

Shortdump - 'MEMORY_NO_MORE_PAGING'

522 Views

Hi

We are implementing ECC 5.0 in a phased approach accross regions, we have just implemented a large region and gone from about 100 concurrent users to 200 concurrent users, we are now getting shortdumps 'MEMORY_NO_MORE_PAGING', when I look at the shortdump it says 'you attempted to allocate a new SAP paging block, but no more blocks were available'. I am monitoring memory block usage through SM04 and we we do have large blocks being used occassionally, yesterday we got about 40 shortdumps in a 1 hour period, then no more for 2 hours, so I'm guessing a user used a particularly large chunk of page memory, is there any way to find paging usage historical per user? through ST03 or STAD? i've had a look and can't find it ?

Looking at parameter rdisp/PG_MAXFS it is set at 32768, which is 8K blocks, so about 262 MB, in ST02 this shows as paging area at 131072 in memory and 131072 on disk, if I was to quadruple this parameter to 131072, would that mean 524288 in memory and 524288 on disk ? or would the initial in memory still be 131072 with the remiander 917504 on disk? the parameter documentation makes it sound like all paging is on disk not memory?

The .DAT page file is in the /usr/sap/ we have plenty of free disk space there (15GB), is there any problems with making the page file so big? I can only do 1 downtime to implement this parameter, so I need to make sure its the correct setting as the project team are getting nervous !

We are runnings on WIndows 2003 64 Bit & MS SQL 2000.

Thanks for any help.