Program giving dump when run in background

Former Member — Mon, 17 Aug 2009 15:45:54 GMT

Hi All,

I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.

The report works perfectly in foreground. But when I execute in background I am getting dump.

Dump details are given below.

ShrtText

Unable to fulfil request for 134217728 bytes of memory space.

What happened?

Each transaction requires some main memory space to process

application data. If the operating system cannot provide any more

space, the transaction is terminated.

What can you do?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

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 administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

More main memory area was requested.

However, all the available space has been used up.

Possible reasons:

- Many (large) internal tables.

- Many (large) programs active.

- Deep nesting of subroutines with a lot of local data.

Can you please help on this ?

Re: Program giving dump when run in background

Former Member — Mon, 17 Aug 2009 15:50:33 GMT

Hi,

Check you code properly.

The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.

Check teh same.

regards,

Ankur Parab

Re: Program giving dump when run in background

swaroop_g2 — Mon, 17 Aug 2009 21:18:17 GMT

Hi,

In the Dump you can look at the internal table size, which will tell you exactly what table is occupying so much memory. Check that out, it should help to find the infinite loop. thx

topic Re: Program giving dump when run in background in Application Development and Automation Discussions

Program giving dump when run in background

Re: Program giving dump when run in background

Re: Program giving dump when run in background