TSV_TNEW_PAGE_ALLOC_FAILED

[#1]

Hello All,

I have observed that our ECC 6.0 EHP 7 is regularly throwing dumps

TSV_TNEW_PAGE_ALLOC_FAILED

for different users.

Please let me know what parameter is affected and needs a change.

-------------------------------------------

What happened?
An attempt was made to add rows to an internal table. There was no
memory available for this however.

No more rows could be added to internal table
"\PROGRAM=/SSC/DO_LIST_IMC_DOCS_NEW\FORM=READ_DATA_FROM_DB\DATA=LT_00102ID[]".
To make
troubleshooting possible, the table had to be deleted before this log
could be compiled. This means that the table will either be displayed
further down or, if you call the ABAP Debugger from here, with 0 rows.

When the program was terminated, the internal table had the following
characteristics:

Memory location: Session memory
Row width: 3492
No. of rows: 1477632
Allocated rows: 1477632
Newly requested rows: 4 (in 1 blocks)

How to correct the error
The amount of memory (in bytes) used at termination time was:

Roll area...................... 0
Extended memory (EM) 2623781296
Assigned memory (HEAP) 2623329136
Short area.....................
Paging area.................... 401408
Maximum address space.......... 4294967295
If the error occurs in a non-modified SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:

"TSV_TNEW_PAGE_ALLOC_FAILED"
"/SSC/DO_LIST_IMC_DOCS_NEW" or /SSC/DO_LIST_IMC_DOCS_NEW
"READ_DATA_FROM_DB"
If you cannot solve the problem yourself, please send the following
information to SAP:

System environment
SAP Release..... 740
SAP Basis level 0020

Application server... XXXXX
Network address...... XXXXXXXXX
Operating system... AIX
Release.............. 7.1
Hardware type....... XXXXXXXXXXX
Character length..... 16 Bits
Pointer length........ 64 Bits
Work process number... 18
Shortdump setting. full

Database server... XXXXXX
Database type..... ORACLE
Database name..... SID
Database user ID SAPSR3

Terminal.......... XXXXXXXXXXXX

Character set C

SAP kernel....... 753
Created on....... Jun 23 2018 02:49:46
Created at....... AIX 1 6 00F747694C00 use-pr20180623
Database version OCI_112, 12.2.0.1.0, V1, default
Patch level....... 215
Patch text.......

Database............. ORACLE 11.2.*.*.*, ORACLE 12.*.*.*.*
SAP database version. 753
Operating system... AIX 1 6, AIX 1 7, AIX 2 7

Memory consumption
Roll.... 0
EM...... 2623781296
Heap.... 2623329136

Page.... 401408
MM used. 5234134240
MM free. 5527952

User and Transaction
Client................. 001
User.................. FINAPTMA
Language key.......... E
Transaction......... /SSC/TANGRO_IM
Transaction ID...... 3608D81BF1D100D0E005D6142ED2312B

EPP whole context ID...... 6E0EE40AED0A1EE9BCFA13D2C953D69E
EPP connection ID........ 00000000000000000000000000000000
EPP call counter......... 0

Program.............. /SSC/DO_LIST_IMC_DOCS_NEW
Screen.............. SAPMSSY0 1000
Screen line.......... 6
Active debugger..... "none"

Information on where terminated
The termination occurred in ABAP program "/SSC/DO_LIST_IMC_DOCS_NEW", in
"READ_DATA_FROM_DB". The main program
was "/SSC/DO_LIST_IMC_DOCS_NEW".

In the source code, the termination point is in line 4788 of (Include)
program "/SSC/DO_LIST_IMC_DOCS_NEW".

[raquel_gomez]

Hi.

The TSV_TNEW_PAGE_ALLOC_FAILED dump appears when the work process has taken its Extended Memory quota and Heap Memory quota and has no more memory to allocate.
It's explained on KBA 2180736 - TSV_TNEW_PAGE_ALLOC_FAILED (S-user needed)

Checking information fromt he dump:
The amount of memory (in bytes) used at termination time was:
Extended memory (EM) ......2623781296
Assigned memory (HEAP) ....2623329136

Do those values match qith defined EM and Heap quota (around 2.5GB each)?
Further information should be seen on work process 18 trace file (dev_w18) from involved application server.

Dump can normally be solved either increasing relevant memory parameters, either reducing selection criteria so less memory is consumed.
Regards,
Raquel

[S_Sriram]

Hi Udaya.

1. Is this transaction is having any selection range? Check with user what selection range selected?

2. Enable the transaction code ST12 trace, check the overall performance usage, in that which select statement taken long duration, check with function /ABAPer guy to further fine turning possible or not.

3. If it is standard SAP code better you can raise the support ticket to SAP find the root case.

Regards

SS