SAP paging overflow when storing data in the ABAP/4 memory.

[Former Member]

I am trying to create a data source in BI7.0 in the Datawarehousing Workbench. But along the process when i need to select a view i get an error detailed in the following error file extract: Please go through and assist.

untime Errors MEMORY_NO_MORE_PAGING

Date and Time 06.06.2009 14:21:35

-

---

-

---

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 20 of different IDs.

Please note:

To facilitate error handling, the ABAP/4 memory was

deleted.

-

---

-

---

How to correct the error

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 8176

Extended memory (EM)........... 13587912

Assigned memory (HEAP)......... 0

Short area..................... " "

Paging area.................... 40960

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" " "

"SAPLWDTM" or "LWDTMU20"

"TABC_ACTIVATE_AND_UPDATE"

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)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

-

---

[former_member21257 · Accepted solution]

Hi,

The dump MEMORY_NO_MORE_PAGING come when the page memory on filesystem

level is exhausted.

Please increase the parameter rdisp/PG_MAXFS and restart the system.

Please note that you must have enough free space on the harddisk.

More information in SAP Note 133909 - Maximum value for PG_MAXFS, PG_SHM, ROLL_MAXFS.

Rgds,

Colum

[Former Member · Accepted solution]

Hi Colum. Where realy do i modify the value of the parameter "rdisp/PG_MAXFS". is this done at database level. I am sorry i do not have access to SAP Note 133909 as i do not have an account on the service market place. Please assist.

[former_member21257 · Accepted solution]

Hi,

You should be able to adjust that parameter by using SE38 report RSPARAM. You may want to contact your Basis colleagues about this.

Rgds,

Colum

[Former Member · Accepted solution]

Thanks for the response Colum. Unfortunately i am learning SAP BW all by myself so i happen to be the "Basis Team".

I have found this parameter in RSPARAM but i need a guide in the value that i can assign. My Laptop has 1GB memory and now has about 22GB free space. The current value of the parameter rdisp/PG_MAXFS is specified as 32768 which happens to be a system default value.

Please assist.

[Former Member · Accepted solution]

hi,

Just for info only, a similar transaction exist,

RZ10

where you can choose your profile then at the extended maintenance and from there you can see the maintained rdisp/PG_MAXFS.

[Former Member]

Hi Huggins,

Maintenance of the Paging File is owned by your basis team.

They should increase this in order for your transaction to process successfully.

Just for your reference, in case the OS used is windows server 2003, paging file value can be checked through;

Right click in the My Computer>properties.

Then go to Advance tab;

Then there should be a performance section, click the settings

Then Advance tab again. The paging file can be seen from there.

(and can be adjusted from there also)

The value of the paging file in general will be dependent with the available RAM from the hardware.

Hope this helps. Thanks a lot.

- Jeff

[Former Member]

This message was moderated.

[dennis_scoville4]

Contact your Basis team and ask to have the paging file parameter value increased.

[Former Member]

Hi,

The Basis people should be able to help you out with this. Refer this error to them.

Cheers,

Kedar