Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Regarding short dump memory

Former Member
0 Likes
829

Hi experts,

I am getting data from the FBL3N transaction into my report and manipulating but it is fetching more than 2 lac records and giving short memory dump how to resolve it please help me.

1 ACCEPTED SOLUTION
Read only

former_member195383
Active Contributor
0 Likes
758

Hi Naveen..

In ST22 do the dump analysys to see where exeactly dump is coming...If its becoz of any select query

written by you then just try to enhance it..may be..u can replace the join with fo all entries..and try...

5 REPLIES 5
Read only

former_member195383
Active Contributor
0 Likes
759

Hi Naveen..

In ST22 do the dump analysys to see where exeactly dump is coming...If its becoz of any select query

written by you then just try to enhance it..may be..u can replace the join with fo all entries..and try...

Read only

0 Likes
758

It is not due to select query due to lot of records

how to increase the size of internal table

Read only

Former Member
0 Likes
758

Naveen,

As FBL3n is standard one.so am sure there will we a OSS NOTE for same pls search.

else paste your Dump info for us to further analysis

Amit.

Read only

0 Likes
758

Hi amit I am pasting the error

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The program had already requested 109152368 bytes from the operating

system with 'malloc' when the operating system reported after a

further memory request that there was no more memory space

available.

hat can you do?

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and admin

termination messages, especially those beyond their normal deletion

date.

Set the system profile parameters

- abap/heap_area_dia

- abap/heap_area_nondia

to a maximum of 109152368. Then reduce the value by 10.000.000 to b

safe side.

Then restart the SAP System.

abap/heap_area_nondia and abap/heap_area_dia:

Set smaller than the memory achieved for each process

with 'malloc' and smaller than abap/heap_area_total

You should also check whether the available memory (file system

swap and main memory) is sufficient for the started program

and its data.

Error analysis

When the program was running, it was established that more

memory was needed than the operating system is able to provide savely.

To avoid a system crash, you must prevent this

situation.

Read only

Former Member
0 Likes
758

Execute This report in background.

got to

PROGRAM->>EXECUTE IN BACKGROUND

rgds

rajesh