No more memory available to extend internal table

[ratana_pouy]

Dear Expert,

i am facing an error for a z report as following:

try to find parameters to allocate more memory, but couldn't find it.

Please help.

Thanks,

RTN

[Sandra_Rossi]

It means 99.9% of the time that your program is consuming TOO MUCH memory, not that the computer has insufficient memory.

Please edit your question, and explain why you need to load more than 7 million rows into an internal table. It's usually something that you can easily avoid as you can find by searching the forum.

(load and processing of packages with each a limited size)

[ratana_pouy]

it is sale reports that retrieve from billing, delivery and sale orders for nation wide. i have around 20 sale org and 17 plants.

Is there another ways to get such report?

[Sandra_Rossi]

If you search the forum, you can see that if it happens for standard programs, and if there's no patch available, the only solution is to reduce the scope of the report and run it several times with each part of the scope, or to contact SAP Support to request a developer to do a patch.

I think you now have all the key information to solve by yourself.

[S_Sriram]

Hi RTN,

Enable the ST12 trace to check the overall expensive SQL statement, if it is required to create the Z-Index to avoid the dumps.

Regards

SS

[ratana_pouy]

Please give me instruction for Z-Index.

Thanks!

[matt]

The problem here is not that the program is taking too long (e.g. because of an expensive SQL statement), but it's running out of memory.

[DominikTylczyn]

Hello ratana.pouy

ratana.pouyRefer to the note 2180736 - TSV_TNEW_PAGE_ALLOC_FAILED short dump for detailed explanation of the TSV_TNEW_PAGE_ALLOC_FAILED and how to analyze them.

I guess yours is a custom sales report. Therefore the best bet would be to optimize the report and reduce its memory consumption.

Best regards

Dominik Tylczynski

[S_Sriram]

Hi RTN,

For that first enable the ST12 trace, as mentions in the blog after that check the MS SQl summary. in that which table select statement taking long duration and check the Z-index requirements.

https://blogs.sap.com/2013/07/17/st12-trace-step-by-step-instruction-on-how-to-use-it-for-analysis/

Regards

SS

[matt]

The problem here is not that the program is taking too long (e.g. because of an expensive SQL statement), but it's running out of memory.