on 11-18-2008 9:12 AM
HI ,
While running background jobs getting st22 dumps and getting below error,
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 17.11.2008 12:17:05
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:
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.
-
PLease could some one let me which parametres need to change or any pathes need to apply.
Thnaks in advance,
Kishore
Firstly can you please apply note 611536 as this can cause the short
dump.
The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested
because the program needed to expand an internal table, but not is
available.
When Extended Memory is used up, the process will go into PRIV mode
as it starts using Heap Memory (or vise-versa). No other user will
be able to use this wp while it is in PRIV mode. If there is enough
heap for it to finish, you will not see the error
TSV_NEW_PAGE_ALLOC_FAILED and the wp will be freed.
Are you using a 64-bit or a 32-bit system if it is a 64 bit system then
please check note 146289. This note shows how to
Implement the SAP profile parameters.
See SAP Note 425207 for parameter limitations
Setting of em/initial_size_MB usually depends on the physical RAM
on the server and if you have any other instanecs on that same
server. According to note #146289 this can be increased to very high
values if there is sufficent RAM on the box.
Also, see notes:
020527 Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
217262 Runtime error text for TSV_TNEW_PAGE_ALLOC_FAILED
185185 Application: Analysis of memory bottlenecks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.