on 05-07-2013 9:04 AM
Hi All,
I am getting Abap Dumps in my production system:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED ( When Application Team run Transaction : VA05N in Dialog)
Runtime Errors TSV_BTR_PAGE_ALLOC_FAILED ( When Application Team run Transaction : VA05N in Background)
Runtime Errors TSV_BTR_PAGE_ALLOC_FAILED
Date and Time 06.05.2013 22:10:56
Short text
No memory available to enhance the index of an internal table.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
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 index of a table - organized as tree-type - was to be enhanced, bu
the requested memory of 8712 bytes was not available.
Storage location: "Session memory"
How to correct the error
Try to decide by analysis whether this request is
reasonable or whether there is a program error. You should pay
particular attention to the internal table entries listed below.
Current System Parameter Values:
Roll, extended and heap memory EXTM
ztta/roll_area 7500000 Byte Roll area per workprocess (total)
ztta/roll_first 1 Byte First amount of roll area used in a dialog WP
ztta/short_area 4000000 Byte Short area per workprocess
rdisp/ROLL_SHM 20280 8 kB Part of roll file in shared memory
rdisp/PG_SHM 40960 8 kB Part of paging file in shared memory
rdisp/PG_LOCAL 150 8 kB Paging buffer per workprocess
em/initial_size_MB 40960 MB Initial size of extended memory
em/blocksize_KB 4096 kB Size of one extended memory block
em/address_space_MB 4092 MB Address space reserved for ext. mem. (NT only)
ztta/roll_extension 3000000000 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia 3000000000 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia 3000000000 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total 6000000000 Byte Max. usable heap memory
abap/heaplimit 40000000 Byte Workprocess restart limit of heap memory
abap/use_paging 0 Paging for flat tables used (1) or not (0)
Please help me out.
Thanks and Regards
Vijay
Hello Vijay,
These are your options:
1) Increase the parameters abap/heap_area_dia, abap/heap_area_nondia and abap/heap_area_total;
2) Reduce the selection criteria, when using the affected transaction;
3) Find a way (at application level, e.g., tcode VA05N) to split the process/job into two or more processes/jobs.
Regards,
Isaías
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Isaías,
Thanks for your reply. I can go with only 1st option of yours, as application team said that they cannot decrease selection criteria or they cannot split data.
1. I have run the report and checked transaction SM04(Memory) and SM50, please find their values below.
SM04 :
Client User Transaction Roll Page Mem(Total) Mem(Priv.)
800 EDBADM VA05N 8.331.264 81.920 4.222.110.556 3.000.012.896
SM50 :
Dialog Process went to On-Hold and PRIV Mode.
2. Suggested client to increase the parameter "ztta/roll_extension" by 2 GB. Will the increase in the value of Parameter have any side effects ?? as it is a production system.
Current Value :
ztta/roll_extension | 3000000000 Byte Max. extended mem. per session (external mode) |
(or)
2. Do I need to suggest Client to increase below parameters, if I need to increase below parameter by how much GB i need to increase ?? and is there any particular note which describes about these values(I have gone through the Note - 146289) (or) I need to go with Trail and Error basis.
abap/heap_area_dia | 3000000000 Byte Max. heap memory for dialog workprocesses |
abap/heap_area_nondia | 3000000000 Byte Max. heap memory for non-dialog workprocesses |
abap/heap_area_total | 6000000000 Byte Max. usable heap memory |
Awaiting for the Reply.
Thanks
Vijay
Hello Vijay,
We usually recommend to not touch ztta/roll_extension, and increase the "heap" parameters instead (your point #2, above).
If you increase ztta/roll_extension, you're allowing each work process to allocate more memory from the Extended Memory (em/initial_size_MB). This could cause the Extended Memory to become exhausted, making the work processes go to "PRIV" mode.
Regards,
Isaías
Thanks every one ....!
Issue is Resolved .
We have changed abap/heap_area_dia to 5 GB (earlier it was 3 GB) and executed Transaction VA05N.
It got successful. (SE38 --> RSMEMORY and changed the parameter and after the transaction is completed changed parameter value to previous value i.e, 3GB).
Thanks Again for your Support..!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijay,
TSV_TNEW_PAGE_ALLOC_FAILED is a typical memory dump.Check the values of the memory settings regarding to following notes:
649327 Analysis of memory consumption
185185 Investigating memory bottlenecks w/o the Memory Inspector
425207 SAP memory management, current parameter ranges
712664 Extended memory memory areas larger than 2GB
369726 TSV_TNEW_PAGE_ALLOC_FAILED
It is also important to have the correct package size in in the OLTP system according to note 417307.
Furthemore in case of a 64 bit system use can use heap settings of 8gb.
Regards
Shrikant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
10 | |
7 | |
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.