Internal session terminated with a runtime error TSV_LIN_ALLOC_FAILED (see ST22)
This is part of the ST22 error analysis.
How to correct the error
Perform an analysis
to find out whether this request makes sense or
whether a program
error has occurred. Pay particular attention to the
internal table
entries listed below.
The amount of
memory (in bytes) used at termination time was:
Roll area......................
0
Extended memory
(EM) 4000907120
Assigned memory
(HEAP) 8001854720
Short area.....................
Paging area....................
802816
Maximum address
space.......... 18446744073709551615
If the error
occurs in a non-modfied 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_LIN_ALLOC_FAILED"
"SAPLMG36" bzw.
LMG36U14
"MPGD_ARRAY_READ"
---
Solution:
BD22 Delete Change Pointers
Program RBDCPCLR
It is advisable to reorganize change pointer tables at regular intervals for better performance of programs accessing the BDCP* tables.
BD22 is a standard report delivered by SAP and it is absolutely safe to run this report. It also has a test run option. You could always run the report in test mode to analyze the data the report had selected for deletion.
Obsolete change pointers are those which have been created up to the specified date and time. In BD22, if this checkbox is marked, obsolete change pointers will be reorganized regardless of whether they have yet been processed.
Processed change pointers are those which have been processed in the specified period (date and time). If this checkbox is marked, the processed change pointers are reorganized.
Field Message Type, you should check your own company idoc setup.
