cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime error - TSV_TNEW_PAGE_ALLOC_FAILED - how to track down the causing parameter(s)?

behlau_carlos
Contributor
0 Kudos

Hello SAP Experts,

is there a way to identify, in case of runtime error TSV_TNEW_PAGE_ALLOC_FAILED, the parameter/buffer (like ztta/roll_area, ztta/roll-extension, etc.) out of runtime error log, that was causing the failure?

I am having a hard time, to identify later on, via ST02 (buffer history), what parameter was the reason for the failure, because it/they ran out of resources (like memroy, SWAP, etc.).

So I was wonderning if the parameter, that needs to be monitored/adjusted, is already recorded inside the DUMP log.

Thanks for your help.

Best regards

Carlos Behlau

Accepted Solutions (1)

Accepted Solutions (1)

Sriram2009
Active Contributor
0 Kudos

Hi Carlos

1.  Could you refer the SCN Wiki link How to solve the runtime issue.

How to solve the Runtime Errors  TSV_TNEW_PAGE_ALLOC_FAILED - Netweaver Technology - SCN Wiki

2. Before that you have to find the root case of the transaction / Report / any function module? for this you can enable the trace and check the DB statistics. 

BR

SS

behlau_carlos
Contributor
0 Kudos

Hi S Sriram,

I have to track it down mostly for data loads in BW.

The failure is happening in the night and next day it is very hard to track down the causing parameter, via ST02.

Therefore I was wondering if the information, about the effected buffer/memory slot, is already located in the runtime error log.

Best regards

Carlos

isaias_freitas
Advisor
Advisor
0 Kudos

Hello Carlos,

You can see the memory usage at the dump itself, under the "system environment" section.

Look for the "EM" and "heap" memory areas.

Most likely they will be very near to the limit configured in your system.

For Extended Memory (EM), the parameter is "ztta/roll_extension".

For heap memory, the parameter can be:

  • abap/heap_area_dia - for dialog work processes
  • abap/heap_area_nondia - for non-dialog work processes (which seems to be the case, as it seems the affected process runs as a job, based on your description of the issue)
  • abap/heap_area_total - the total of heap memory that the SAP instance can use (not a single work process, but the entire instance)

Check out the WIKI page below.

TSV_TNEW_PAGE_ALLOC_FAILED - Application Server Infrastructure - SCN Wiki

Best regards,

Isaías

Sriram2009
Active Contributor
0 Kudos

Hi Carlos

1.  In your case you have to check and redefine  the Memory and buffer values.

2. Could you share the full dump as attachment? and ST02 screenshot?

BR

SS

behlau_carlos
Contributor
0 Kudos

Hello S Sriram,

we extened EM already and SWAP space.

The effected SAP App Server has 64 GB RAM (16 dialog; 30 background; 3 update; 3 update2; 1 spool process).

Best regards

Carlos

Answers (1)

Answers (1)

behlau_carlos
Contributor
0 Kudos

I think I found it. In the section "system environment" of the run time log (ST22) there is the section "Memory consumption". That is what I was looking for ...