on 11-07-2011 11:28 AM
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Short text
No more storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
-
If the error persists, ask your system administrator to check the
following profile parameters:
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.
Error analysis
The internal table "\FUNCTION=MBEW_EXTEND\DATA=SEARCH_MBEWH_TAB[]" 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.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 372
Number of rows: 1157808
Allocated rows: 1157808
Newly requested rows: 32 (in 1 blocks)
to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 5720752
Extended memory (EM)........... 2002747344
Assigned memory (HEAP)......... 2000756464
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 4294967295
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLMG27" or "LMG27F02"
"SEARCH_EXIT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
-
ANy ideas ?
Thanks to help.
hi Jordy,
buy another hard disk for your PI server, or clean physicall data, like old log files...
Seriously, see with your Basis team, because your file disk system has no more space... so SAP cannot stored the action you did.
That's a classical issue, they know how to solve it.
regards.
Mickael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
How did you know that ?
In which line did you see it ? -> No more storage space available for extending an internal table. ?
So you suggest to increase the disk on AIX level ? -> /usr/sap/SID ... right ?
[:root:/usr/sap/SID:] df -m .
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/lvusrsapSID 6272.00 2837.27 55% 1607 1% /usr/sap/SID
Thanks in advance,
J.
Edited by: Jordy_tof on Nov 7, 2011 12:38 PM
Edited by: Jordy_tof on Nov 7, 2011 12:48 PM
hi Jordy,
> In which line did you see it ? -> No more storage space available for extending an internal table. ?
Yes.
> So you suggest to increase the disk on AIX level ? -> /usr/sap/SID ... right ?
I'm not a basis consultant, but yes I think it's one of the solution. Another is eventually to find old log file (of adapter for instance), and too delete or archive them.
question: in your dev system, when you exchange files to outside where these files have been stored ? in an file server ? or directly in PI server (wich is a bad idea) ? if it's PI itself, delete old test files.
Once again, see with your basis team.
Regards
Mickael
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.