ABAP dump triggers in S4HANA - TSV_TNEW_PAGE_ALLOC_FAILED runtime error

[Jananie_Rajesh3]

Dear Experts,

We are in the latest version of ABAP agent (24.5). In S4HANA system, we noticed a runtime error getting triggered every hour.

We identified the related KPI and disabled it. But customer needs permanent solution, because it is related to SOST (Mail monitoring)

TSV_TNEW_PAGE_ALLOC_FAILED | No more memory available to add rows to an internal table. | SAPLSX11 | LSX11F02

Any idea on permanent solution?

Thanks

Jananie

[iamryan]

Hi @Jananie.Rajeshwari,

Thanks for asking your question on the Community. I was able to find some existing information to give you a lead, but you may want to contact Support for this one.

TSV_TNEW_PAGE_ALLOC_FAILED which means no more virtual memory can be allocated.

Paging area is virtual memory and is used to store data for ABAP processing on disk space. It is stored as IL<inst>.DAT files. For better analysis, you can check transaction ST02 SAP Memory section (check attached 'image.png').

Check your MaxUse(peak usage) column for page area and extended memory. If MaxUse is nearing the sum of In Mem + OnDisk, you might want to increase your maximum allowed page area parameter to prevent running out of memory in future. Additional info can be found in note:
https://launchpad.support.sap.com/#/notes/133909

Also this issue can also be raised if file system on OS level is full therefore we recommend checking if you have enough physical memory free to accommodate all memory allocations. List of them can be found in note https://launchpad.support.sap.com/#/notes/88416