MEMORY_NO_MORE_PAGING

[Former Member]

AM getting this dumps for SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR.

I checked the parameters rdisp/PG_SHM=16384

rdisp/PG_MAXFS=52678

which are more than the defaults specified

System Info

SAP Netweaver 7.0

Oracle version 9i

AIX OS

memory consumption

Roll.... 16192

EM...... 913386864

Heap.... 0

Page.... 8192

MM Used. 890883848

MM Free. 5698424

any suggestions

[Former Member · Accepted solution]

Hai,

This is a memory problem, is the the job failing at any particular time of the day or it fails always.

If it fails at any particular time then check other jobs running at that time which might consume all the paging memory. This can also happen with some RFC's waiting for some dialog steps leaving the user context in page area which makes the page area full and restricting others to use the Roll/Page area.

You can use ST02 to check the maximum Roll/Page area used by the system.

Also use ST03N to analyse the system load further.

If the job always fails then you should tune the parameters in concern.

Regards,

Yoganand.V

[Former Member · Accepted solution]

This job has continously failed from 20thfeb to 27th feb

At the start time of this job 5 more jobs are scheduled but they were finished within a span of few 100 secs so i dont think they must have consumed more paging memory

Roll memory Dialog session kB 6.348

Nondialog sess. kB 6.348

Available kB 262.144

in shared memory kB 131.072

on disk kB 131.072

Used kB 23.312

Maximum used kB 37.032

Paging memory Session buffer kB 1.200

Available kB 422.144

in shared memory kB 131.072

on disk kB 291.072

Used kB 11.130

Maximum used kB 422.136

[Former Member · Accepted solution]

abap/heap_area_total 2000683008 Byte

I checked in ST06

max swap space size = 23GB

• FORM force_refresh_main_dynpro.

• should not be used any longer. Use the functions

• 'DB02_ORA_FILL_TS' and 'DB02_ORA_FILL_TD110' instead !

• PERFORM force_refresh_ts_analysis.

• PERFORM force_refresh_main_dynpro.

CALL FUNCTION 'DB02_ORA_FILL_TS'

EXPORTING

FLAG_REFRESH = 'Y'

• IMPORTING

• CURR_TIME =

• CURR_DATE =

• DATETIME =

TABLES

TS = TS.

• EXCEPTIONS

• others = 1.

CALL FUNCTION 'DB02_ORA_FILL_TD110'

EXPORTING

FLAG_REFRESH = 'Y'

IMPORTING

TD110 = TD110

TABLES

SEGMT = SEGMT.

• exceptions

• others = 1.

EXPORT TS TO MEMORY ID 'RSORAT2M'.

EXPORT TD110 TO MEMORY ID 'RSORAT4M'.

==>EXPORT SEGMT TO MEMORY ID 'RSORAT6M'. (Occurence of termination)

• INCLUDE rsorat0b. T.S. 11/96

• INCLUDE rsorat0m. T.S. 11/96

• INCLUDE rsorat0f. T.S. 11/96

*INCLUDE RSORAT2F.

Edited by: Ameya Joshi on Feb 27, 2009 1:07 PM

[Former Member · Accepted solution]

Hi,

Is there a Z report in this job since 20th Feb?

Thanks,

Manoj

[Former Member · Accepted solution]

No the report name is

RSORAT0D

In the source code you have the termination point in line 4

of the (Include) program "RSORAT0D".

The program "RSORAT0D" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "HOUSEKEEPING"

Job Number..... 06455300

Edited by: Ameya Joshi on Feb 27, 2009 1:42 PM

[Former Member · Accepted solution]

Hai,

Is this job failing only twice a day in a particular time?

Since this report in concern collects DB02 data only twice a day.

I guess you can try deleting the old DB02 table statistics.

Check the SAP Note: 1000275 - DB02: history data backup.

Also check SAP Notes:1283931 and 713211.

Regards,

Yoganand.V

[Former Member · Accepted solution]

Yes

This job is failing at 7:45 CET and 20:45 CET respectively

due to MEMORY_NO_MORE_PAGING dump

Can somebody explain what exactly this statement is doing

EXPORT TS TO MEMORY ID 'RSORAT2M'.

EXPORT TD110 TO MEMORY ID 'RSORAT4M'.

==>EXPORT SEGMT TO MEMORY ID 'RSORAT6M'. (Occurence of termination)

Old statistics record from 31st dec are present....I dont think thats causing problem

Also the parameters

rdisp/PG_MAXFS = 52678 and rdisp/ROLL_MAXFS=32768

should there value be same??

We r using AIX OS 64 bit version

Configured physical memory is 62GB and swap space is 23GB

Edited by: Ameya Joshi on Mar 3, 2009 5:36 PM

[Former Member · Accepted solution]

Hai,

Did you go through the notes providing the solution for this problem.

Note 713211, 1000275 has the solution for this problem.

In note 713211 point no:3 is in relation to your problem, you can implement the corrections or you can

proceed with the points 3 and 4 under 'solutions' part.

Please go through the notes and let us know.

Regards,

Yoganand.V

[Former Member]

Hi,

How much is the virtual memory (swap space) on your system? Please post ST22 dump?

Make sure you have paging file 2.5/3 times of RAM.

Thanks,

Manoj

Edited by: Manoj Chintawar on Feb 27, 2009 11:53 AM