TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

Hi,

Can someone please help me to understand / troubeshoot this dump in ST22??

TSV_TNEW_PAGE_ALLOC_FAILED

The internal table "\PROGRAM=RSSTAT26\DATA=ALL_STATS" 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.

How to proceed with handling such kind of dumps??

regards,

Arul S

[Former Member · Accepted solution]

Hi,

To investigate further, please note the responsible work process (it is indicated in the short dump) and go to the corresponding developer trace (ST11). There you can see the actual cause of the short dump.

Kind regards,

Christophe

[Former Member]

Hi Rishi / all ,

@ all: Thanks for all your answers.

@ Rishi:

I have noticed the below details from the ST22 dump and would like to share this with you.

The amount of storage space (in bytes) filled at termination time was: ( Taken from ST22 dump)

Roll area...................... 2718352

Extended memory (EM)........... 2002756912 --> Extended memory max limits have been reached.

Assigned memory (HEAP)......... 950 025 088

Short area..................... " "

Paging area.................... 0

Maximum address space.......... 4242729616

Please find below the following parameters that are currently active in our system. ( from RZ10)

ztta/roll_first 1

ztta/roll_area 3000000

em/initial_size_MB 17000

ztta/roll_extension 2000000000

ztta/roll_extension_dia 2000000000

ztta/roll_extension_nondia 2000000000

abap/heap_area_total 2500853760

From the above, it can be noted that EM consumption was more than the current value set at the system.

Also, the below user and transaction details can be obtained from the dump

Client.............. 445

User................ "NLV17531"

Language Key........ "E"

Transaction......... " "

Program............. "CL_SWNC_STATREC_SET_TABLE_SWNCCP"

Screen.............. "SAPMSSY1 3004"

Screen Line......... 2

Can you please suggest/ provide your comments on how can i proceed in resolving this issue,as this is a very frequent dump

in our system (occuring almost everyday)?

What are the parameters that need to be changed to avoid the occurence of this dump??

Thanks in advance,

Arul Sekar

[Former Member]

Hi Arul

TSV memory error is a common error in SAP , mainly occurring when a particular work process exceeds the maximum allowed memory for a single individual work process.

To troubleshoot :

1. Which user and T-code generated this error, is it occurring repeatedly .

2. Check the memory conditions filled up at the time of error ( available in the Dump itself )

Check in ST02 if the extended memory max limits have been reached , if not .. then check the above info in ST22 Dump itself.

We have observed many times that it is due to faulty selection criterion leading to excess memory usage and that needs to be corrected by the user. If it is occurring repeatedly , then consider increasing the memory .

Thanks

Rishi

[markus_doehr2]

What operating system are you using? Is this 32bit?

Markus