background process going to " abap/heap limit"

[Former Member]

Hi All,

When i check the trace file of the workprocess which is a background process it shows that the

" WP has reached abap/heap limit"

Does this trigger the dialog process into PRIV mode? or is it OK for a background process to reach the heap limit.

Please advise.

Best Regards,

DVRK

[ImtiazKaredia · Accepted solution]

Memeory for Background process is allocation in steps like Roll, Heap and then Extended,

Whereas in Dialog process it is Roll, Extended and then Heap.

Background process will first exhaust heap memeory. This is done so that dialog processes are not impacted.

A background process eating up heap will not result in dialog process going in PRIV mode.

Dialog WP will go into PRIV mode only when it used allocated extended memory controlled by paratmeter ztta/roll_extension

[Former Member]

Hi Ramakrishna,

The trace you are seeing is for the background process and is no longer related to dailog process.

Some times we can see the abap/heaplimit issues due to background jobs running parallely on the same host.

When the abap/heaplimit reaches max. the job gets cancels

Try to trigger the job on low load instance

(or).

If this occurs on a regular basis. Try to find out the jobs which are failing and tune them accordingly

(or)

Take the help of Basis in fine tuning the abap heap memory parameters.

Hope I answered your query.

Regards

Sandy