short DUMP: EXSORT_NOT_ENOUGH_MEMORY

[Former Member]

Hello everyone,

Our user is running some reports using Transaction IQ09-

Display Material Serial Number List, and its going to the dump

by giving error message as "STORAGE_PARAMETERS_WRONG_SET"

or "TSV_TNEW_PAGE_ALLOC_FAILED" or EXSORT_NOT_ENOUGH_MEMORY.

We have tried to execute this transaction in background mode

and still getting the same dump/error message. We are getting

this error in our Production R/3 system (PU1) and it is

affecting business operations.

"In the what you can do" section in DUMP log, this is what I find:

Set the system profile parameters

- abap/heap_area_dia

- abap/heap_area_nondia

to a maximum of 687977744. Then reduce the value by 10.000.000 to be on the

safe side.

Then restart the SAP System.

Our system is 32-bit SAP kernel and what these DUMPs means is additional memory is required to extend the internal table, but none is available. This error is usually due to a lack of system resources for the roll area where internal tables are processed.

Below are the profile parameters we have set in our PRD system.

ztta/roll_first 1024

ztta/roll_area 2000896

abap/heap_area_dia 2000683008

abap/heap_area_nondia 2000683008

abap/heap_area_total 2000683008

abap/heaplimit 40894464

abap/swap_reserve 20971520

ztta/roll_extension 2000683008

em/initial_size_MB 5765

em/blocksize_KB 1024

Do I need to change any of the above profile parameters in RZ10 to get rid of the dump? Do you think this will have any adverse effect on our production system such are system may run out of shared memory.

Any help will be greately appreciated and points will be rewarded.

Thanks,

Shahid Anjum

[Former Member · Accepted solution]

Hi Shahid,

To understand how the system performs sorting and the EXSORT_NOT_ENOUGH_MEMORY error, see SAP Note 193529 Sort as of 4.5A/EXSORT_NOT_ENOUGH_MEMORY.

The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested because the program needed to expand an internal table, but the memory was not available.

When Extended Memory is used up, the process will go into PRIV mode as it starts using Heap Memory (or vise-versa). No other user will be able to use this wp while it is in PRIV mode. If there is enough heap for it to finish, you will not see the error TSV_NEW_PAGE_ALLOC_FAILED and the wp will be freed.

You should check your settings for the profile parameters abap/heap_area_total and abap/heap_area_nondia against the Notes:

146289 Parameter Recommendations for 64-Bit SAP Kernel

425207 SAP memory management, current parameter ranges

Also, see the Notes:

20527 Runtime error TSV_TNEW_PAGE_ALLOC_FAILED

217262 Runtime error text for TSV_TNEW_PAGE_ALLOC_FAILED

185185 Application: Analysis of memory bottlenecks

649327 Analysis of memory consumption

However, often the problem may not be with memory settings, but with the selection values the user is entering for the report. That is, they may be entering a very wide range against a very large table. In these cases, check the selection values and reduce them. Also, check the affected table size and consider if parts of it may be archived.

Best Regards,

Matt

[Former Member · Accepted solution]

Hello Matt,

Thanks for your quick response, we have set profile parameter for abap/heap_area_total and abap/heap_area_nondia as per the note

146289.

As you said, "often the problem may not be with memory settings, but with the selection values the user is entering for the report. That is, they may be entering a very wide range against a very large table. In these cases, check the selection values and reduce them. Also, check the affected table size and consider if parts of it may be archived."

We already tried this method and this method didn't work.

We have opned a OSS message to SAP. Let us see if they recomend something else.

Thanks for your imput.