cancel
Showing results for 
Search instead for 
Did you mean: 

TSV_TNEW_PAGE_ALLOC_FAILED

Former Member
0 Kudos

Hello

An job (SPI_PS_ASSEMBLE_DSP) generates short dumps in an XI systems TSV_TNEW_PAGE_ALLOC_FAILED. However I do not know how to cope with this issue as memory parameters are the default one. In ABAP dump I get message following parameter have to be adjusted. I have 8GB of physical memory(based on st06).

However when I put em/initial_size_MB to 4096 the server crashes after 1 hour of job beeing running(it seems all memory is exausted)

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

If you are running with default parameters there is likely to be scope for tuning.

Try SAP Notes 789477, 941735 & 146289

You should check ST02 for paging and adjust anything that is over 10,000 a day.

If this is a new system you should order a going-live report from SAP. They will recommend parameter values as part of that.

I have never got into the monitoring side of XI but all those SPI jobs are part of that. Have a look at transaction SPIP.

Answers (2)

Answers (2)

former_member312776
Discoverer
0 Kudos

It is a 64 bit system running on virtual server linux(Red hat)/oracle.

In the meantime I increase em/initial_sizeMB and the TSV_TNEW_PAGE_ALLOC_FAILED does not occurs any more.

However the database is increasing rapidly. Does anyone knows relation and meaning of jobs:

-job 3903134AA6F8AC4BE1000000C0A81A8Z

with step SPI_PS_ASSEMBLE_DSP

(this one finished completely for first time this night). As I understood it prepares data to be deleted with following jobs

-job SPI_REORG_CS

-job SPI_REORG_PS

-job SAP_BC_XMB_DELETE_001

steps

RSXMB_DELETE_MESSAGES ABAP

RSXMB_TABLE_SWITCH ABAP

-job SAP_BC_XMB_HIST_DELETE_001

Steps

RSXMB_DELETE_HISTORY

-job SPI_TRANSPORT

Thank you in advance for furder help

markus_doehr2
Active Contributor
0 Kudos

> An job (SPI_PS_ASSEMBLE_DSP) generates short dumps in an XI systems TSV_TNEW_PAGE_ALLOC_FAILED. However I do not know how to cope with this issue as memory parameters are the default one. In ABAP dump I get message following parameter have to be adjusted. I have 8GB of physical memory(based on st06).

Is this a 32bit system?

Markus