TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

Hello All,

From few days we are receiving the Dump TSV_TNEW_PAGE_ALLOC_FAILED in st22.

Any idea why is that so. Any appropriate note would be much helpful.

Regards,

Ravi

[Former Member]

Hai,

Normally this dump occurs when your Paging memory gets exhausted.

You can get the hint from your Dump itself, it will be showing the amount of Memory it had used when the program terminated. Using this you can arrive to a conclusion on what to do to overcome this issue.

Please go through the dump to get more information.

This can also occur when the program uses infinite loop or long Select statements so you can find the potential problem if any in your program using the dump.

Take help from your ABAPer if this dump was produced due to the program.

or Increase the memory parameter in concern.

Regards,

Yoganand.V

[Former Member]

Below is the error analysis:

Error analysis

The internal table "\FUNCTION=FAVOS_EVENT_MOVE_IN_SHELF\DATA=CHANGED_NODES[]"

could not be further extended. To enable

error handling, the table had to be delete before this log was written.

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "Session memory"

Row width: 681

Number of rows: 5807721

Allocated rows: 5807728

Newly requested rows: 16 (in 1 blocks)

-

---

Any idea how to proceed now.

[Former Member]

Hai,

As seen from your dump the Internal Table in question was not able to accomodate the amount of data in memory, memory got exhausted. So better you can take the help of ABAPer to check what makes this to terminate whether it is infinite loop or Big select statement or the amount of data, etc.,

You have to arrive to a conclusion with the above points which makes the termination and dumps.

If any of the above is not the cause then you have to carefully tune the memory parameters to accomodate the data in the Internal table.

But first try to sort out what exactly is the problem for the dump.

Regards,

Yoganand.V

[joo_migueldimas]

Hi,

I´m faccing with the same problem during an importing phase XPRA_EXECUTION.

When I check the error in st22 it show me a dump: TSV_TNEW_PAGE_ALLOC_FAILED

In the field "Error analysis" it´s shown me this:

The internal table "AREA=CL_UGMD_META2INSTANCE=UGMD_FIELDINFO_LOCALVERSID=9

OBJ=DATA=DT_DFIES" could not be

further extended. To enable

error handling, the table had to be delete before this log was written.

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "AREA=CL_UGMD_META2INST=UGMD_FIELDINFO_LOCALCLNT="

Row width: 1342

Number of rows: 0

Allocated rows: 1

Newly requested rows: 3048 (in 381 blocks)

Any idea? I already had this error in past in other system with exactly the same importing queue and I solved that after I create in instance profile this two parameter:

abap/buffersize

PHYS_MEMSIZE

In this particulary case I already tune the system and apply them to instance profile but after I continuing the import from that phase this stop again with the same error, so I realize unfortunately this isn´t work with the same correction!!

Can you help me please how can I solve this problem?!

Thank you

Best regards

João Dimas - Portugal

[Former Member]

Hi,

Please check the SAP notes 794257, 700549.

Also check the links:

This may help you.

Regards.

Rajat