on 03-22-2011 6:07 PM
Dear friends,
In one of our BW production system, 2 instance of hourly job SAP_COLLECTOR_FOR_PERFMONITOR is dumping MEMORY_NO_MORE_PAGING.
I have already checked this thread :
But I am unable to find out the reason and also i do not find any Moni Key in abap dump. Please suggest.
PART OF ABAP DUMP :
40 SEGMT = SEGMT.
41 * exceptions
42 * others = 1.
43
44 EXPORT TS TO MEMORY ID 'RSORAT2M'.
45 EXPORT TD110 TO MEMORY ID 'RSORAT4M'.
>>>>> EXPORT SEGMT TO MEMORY ID 'RSORAT6M'.
47
48 * INCLUDE rsorat0b. T.S. 11/96
49 * INCLUDE rsorat0m. T.S. 11/96
50 * INCLUDE rsorat0f. T.S. 11/96
51 *INCLUDE RSORAT2F.
thanks
ashish
Hi,
Check your memory parameter settings & also check if you have scheduled the report( Table TCOLL) as mention in sap notes for your sap release. Sometime it happens that some additional report are scheduled which are not required any more.
Regards,
Neeraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like you are running out of sap paging. Please check for parameter rdisp/PG_MAXFS.
You may want to look at following note.
Note 133909 - Maximum value for PG_MAXFS, PG_SHM, ROLL_MAXFS, ROLL_SHM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello friends,
Of-Course MEMORY_NO_MORE_PAGING is a memory dump and it can be avoided if i increage paging sizes. We have smaller value for this parameter and I am not convinced if it is required now to increase it. This was working nicely sometime back.
So, When we say we have abap statement EXPORT which is causing MEMORY_NO_MORE_PAGING. But the same abap statement was working fine sometime back and we did not had this problem. So i assume if there is something like large number of history records as per SAP Note 713211 is troubling us.
Now, i want to findout what is causing so much of memory requirement & page files.
We also get similar dumo when we manually try to perform DB Checks & update histories with transaction DB02OLD. This is the same this what Collector Job also doing and dumping.
Any new suggestion please..
thanks
ashish
Hi,
Check you ST22 dump. Generally this error occurs when there is no available extended memory. Can you increase the extended memory and give it a try.
Regards,
Vamshi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.