DUMP TSV_NEW_PAGE_ALLOC_FAILED

[Former Member]

Hello Everybody,

We are getting the dump DUMP_TSV_NEW_PAGE_ALLOC_FAILED in our SAP R/3 4.6C application 32 bits

No storage space available for extending table "IT_16".

What happened?

You attempted to extend an internal table, but the required space was

not available.

Anybody now the solution to this dump?

Should we increase the memory in our Windows operational system?

Best Regards,

Fábio Karnik

Edited by: Fio Tchobnian on Aug 20, 2009 3:18 PM

[Sriram2009]

Hi Rajeshkumar.

Kindly create the new question about you dump and also attach the full dump as text format.

Regards

SS

[former_member592460]

Hi,

Basically TSV_NEW_PAGE_ALLOC_FAILED dump will occur if some other Jobs or transaction can consume all the memory space in your system .If its consumed then obviously we will end with up with this dump.

EX : we have 3 GB memory for all our process. Also we have different server in that. For particular server we are running two to three jobs. At that time one Long running job will consume all the memory and another Two jobs end with memory dumps (TSV_NEW_PAGE_ALLOC_FAILED). At that we need to find the long running job and kill that.

[anindya_bose]

You can increase Virtual Memory ( Page file) of your OS.

and Also increase temporary tablespace.

Check if you are still getting the dump.

[Former Member]

Dear All,

The problem was solved with an Upgrade of the Harware.

RAM 4GB to 8GB

S.0 -2K to 3K

Proc PIII 1.13ghz to Intel Xeon 3.20gHZ

Thanks,

Best Regards,

Fábio Karnik Tchobnian

[markus_doehr2]

> We are getting the dump DUMP_TSV_NEW_PAGE_ALLOC_FAILED in our SAP R/3 4.6C application 32 bits

> Anybody now the solution to this dump?

>

> Should we increase the memory in our Windows operational system?

There is no general solution.

That dumps means, that you have reached the maximum amount of RAM imposed by the operating system. By default a 32bit application can only allocate 2 GB of memory in total.

You have various options - like enable /3GB option in your boot.ini or trying to reduce the amount of memory needed for the program. However, the long term solution would be to migrate to 64bit (and to upgrade 4.6c).

Markus

[Former Member]

Hi,

This dump is generated 9 times out of ten by a poorly written abap program which tries to load all selected data in an internal table.

So 9 times out of ten, the programmer has to rewrite his program.

And of course the program ran perfectly on the test system with very small data. The prodcution system is usually an other story.

The problem begins when the dump happens with SAP standard code...

Regards,

Olivier

[Former Member]

check out various notes from following link

[;