ABAP dump TSV_TNEW_PAGE_ALLOC_FAILED

[#1]

Hi Gurus,

Recently we've been receiving a bunch of TSV_TNEW_PAGE_ALLOC_FAILED abap dumps.

The dump will always mention "No storage space available for extending table "IT_XXXXX"." XXXXX are various numbers.

This is a server memory issue, NOT a DB space issue. An internal table is a table that resides in server memory.

Also i noticed in ST02, Free Space & Free Directory for NAMETAB (NTAB) Table definition is RED and 0.00. Could this be related to the abap dump???

I'm trying to pinpoint which parameter to increase the value, I rounded it down to:-

abap/heap_area_total

abap/heap_area_dia

abap/heap_area_nondia ...

em/initial_size_MB

ztta/roll_extension

Would this solve this problem???

[Former Member]

Hi Keat,

Can you let us know the exact situation when you are getting this dump and also the system details. In my experience this dump you see freaquently in BW system in production support after over a period of time, as the data grow's and accordingly user request for the data grows. In that case you need to do memory tuning. But also as Alivier recommonded its better to look for the provision where you can reduce the selection criterea or some time's there could be a problem with program that you are using then u have to reach out programmer.

If this memory demand is from SAP standard programs, then give the complete senario of the problem. Like what you are trying to run and the steps you are following for that. So that its easy to narrow down the problem and to find the cause.

Also if you decided to change the memory parameters, then dont forget to run the 'sappfpar' to check your profile.

Thanks & Regards,

N.Amarnath

[Former Member]

Hi all,

These are the related parameters currently set in the system.

ztta/roll_area = 6500000

ztta/roll_extension = 2000000000

abap/heap_area_total = 2000000000

abap/heap_area_dia = 10000000

abap/heap_area_nondia = 1073741824

em/initial_size_MB = 6144

here is a sample storage usage at termination time of the abap dump.

Roll area...................... 6178768

Extended memory (EM)........... 2001260211

Assigned memory (HEAP)......... 10096240

Short area..................... 16079

Paging area.................... 262144

Maximum address space.......... "-1"

As you can see, the usage of the Extended memory (EM) of the batch jobs have exceeded the specified value of 2000000000.

This is the reason why the batch jobs got terminated with error message "No storage space available for extending table "IT_XXXXXX"."

We can't do much here as we're not allowed to increase the value of parameter ztta/roll_extension further.

[Former Member]

Hi,

So I would say why is this program stuffing in 2GB data into an internal table?

Is this a SAP standard program or bespoke customer one?

Question does this program do inserts or update...if so, how often does the program commit to the DB.

Mark

[Former Member]

Increase abap/shared_objects_size_MB to 100MB.This will solve the issue. Its inital size is 20MB.

[Former Member]

>Increase abap/shared_objects_size_MB to 100MB.This will solve the issue. Its inital size is 20MB.

Text removed by moderator Keep it civil please

This parameter has nothing to do with the problem...

Edited by: Matt on Dec 13, 2011 10:54 AM

[Former Member]

Are you check your JOB work's fine or not? As mr.Olivier say usually is are badly writen code ....

About memory configuration .... --->> You not say how much memory you have on your BOX, are DB on same host, any other application are used? Try to give as this information, or we need buy magic ball ? Regards.

[Former Member]

here is a sample storage usage at termination time of the abap dump. 
Roll area...................... 6178768 
Extended memory (EM)........... 2001260211 
Assigned memory (HEAP)......... 10096240 
Short area..................... 16079 
Paging area.................... 262144 
Maximum address space.......... "-1" 

Hi KeatSeong,

Based on the values from your ABAP dump, I can definitely say this is a BAD program. At the time of termination, Extended memory is fully utilized upto 2GB which is allowed per process as per ztta/roll_extension.

Please ask ABAPer to check the ABAP code where the program terminates .... many times if there is a nested query where first query results in internal table and that becomes source for another query , the issue is previous query generated a NULL internal table and that triggers a full table read of the next query on a huge table and that becomes this ERROR.

A simple, IF InternalTable not NULL, condition may resolve this issue, if the symptoms I mentioned are correct in your case.

Thanks

Yatin

[Former Member]

Hello,

If this dump is about a background job, why it uses less heap and more of the EM.

As per your parameters:

ztta/roll_extension = 2000000000 
abap/heap_area_total = 2000000000 
abap/heap_area_dia = 10000000 
abap/heap_area_nondia = 1073741824 
em/initial_size_MB = 6144

Your non_dia heap is set to 1GB, its only after using this 1GB would the background process look for Extended memory. Most probably this dump is not of a background process.

Also, I see that your total extended memory is just 6GB how much memory does your server have? Make good use of the available server memory by setting up large chunks of EM, if you increase the initia_size_MB to say 8GB or 12GB you can increase ztta/roll_extension to accommdate those programs that are dumping.

However the first priority is to talk to developers on improving the code rather than increasing parameters.

Regards,

Siddhesh

[Former Member]

This message was moderated.