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: 

Deletion of record from internal table and memory dump

0 Kudos
1,803

Hi All,

I have a statement which looks like below in one of Z programs.

delete lt_table index lv_index.

This program runs in background for long and it is giving a memory allocation dump.When i checked the dump , system displays that the above line is causing the dump. I understand when we try to insert something into a table then memory dump would come , but what would cause a delete statement to give a memory dump('TSV_TNEW_PAGE_ALLOC_FAILED') ? If something was with lv_index it should have been a overflow dump not a memory allocation dump. Can any one help me in understanding what would cause this dump.

Thanks and Regards

Dushyanth .

1 ACCEPTED SOLUTION

retired_member
Product and Topic Expert
Product and Topic Expert
631

There can be several reasons. One might be that the internal table was shared after an assignment or parameter passing and that deleting a line ends the sharing and the table is physically copied.

Or, less probable, some lazy or delayed internal administration costs for secondary keys.

See http://help-legacy.sap.com/abapdocu_751/en/index.htm?file=abensharing_glosry.htm

2 REPLIES 2

retired_member
Product and Topic Expert
Product and Topic Expert
632

There can be several reasons. One might be that the internal table was shared after an assignment or parameter passing and that deleting a line ends the sharing and the table is physically copied.

Or, less probable, some lazy or delayed internal administration costs for secondary keys.

See http://help-legacy.sap.com/abapdocu_751/en/index.htm?file=abensharing_glosry.htm

Jelena_Perfiljeva
Active Contributor
631

Google -> TSV_TNEW_PAGE_ALLOC_FAILED site:sap.com -> 1000+ results

There are many posts explaining that the statement that immediately precedes the memory short dumps is not always the main culprit.

There are tools available in SAP for memory analysis. Kindly make some effort to troubleshoot in your system.