on 06-03-2013 6:43 PM
Hi All,
I am getting dump in ECC production system which runs on windows 2003/sql2005 on 64 bit platflorm. Kernel -700-patch347. We have set all parameters as below. Do we need to increase physical memory or any other parameter? Batch jobs failing with memory related dumps TSV_TNEW_PAGE_ALLOC_FAILED. The program causing is SAPLV70A. Affected table is NAST. Please help ASAP. Distributed system with CI +App server has 16+16 GB RAM. In CI
Physical main memory (RAM) 16378
PHYS_MEMSIZE 16378
em/initial_size_MB 20,000
em/blocksize_KB 4096
em/max_size_MB 100000
ztta/roll_area 6500000
em/address_space_MB 4096
ztta/roll_first 1
ztta/roll_extension 2000000000
abap/heap_area_dia 2000000000
abap/heap_area_nondia 0
abap/heap_area_total 17173577728
rdisp/ROLL_MAXFS 32768
rdisp/ROLL_SHM 32768
rdisp/PG_MAXFS 262144
rdisp/PG_SHM 16384
em/global_area_MB 512
From ST22
Error analysis
The internal table "\PROGRAM=SD70AV2A\DATA=MSGS[]" 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: 2208
Number of rows: 1748948
Allocated rows: 1748948
Newly requested rows: 4 (in 1 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6221152
Extended memory (EM)........... 2002743520
Assigned memory (HEAP)......... 1932740608
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... " "
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" " "
"SAPLV70A" or "LV70AU03"
"WFMC_MESSAGES_SELECT_ALL_FALSE"
Please help ASAP.
Thanks,
Kavitha
Hi
how many records has your nast?
Let me know
a
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kavitha
you are in a kind of grey area. The table is really big but it could be a temp bottleneck (if in parallel there are other things that are affecting all night runs) or a not good statement in the program you use
Can you give me more info regarding program and variant you use?
Are Note 1629669 or KBA 1580605 applicable for you? What sp level have you in your system?
Is something that happens always or sometimes?
Even if i don't like to change parameter to allow management of big tables, have you seen Matteo Stocco 's recommendation?
Let me know and i'll help you
a
Hi Andrea,
Note 1629669 is already applied. KBA1580605, I think is not applicable. Program runs every 10 minutes. It causing issue during day time as well. It sometimes caused issue before but now it became adequate and everyday dumping affecting business. Program has 4 steps. 3&4 has issues.
1 RSNAST00 ABAP ZADR BATCH EN
2 RSNAST00 ABAP YADR BATCH EN
3 SD70AV2A ABAP ZADR_3 BATCH EN
4 SD70AV2A ABAP YADR_4 BATCH EN
I replied to Matteo's response, however, my messages and replies are being moderated and taking so long to get posted. It is ECC 6.0 SPS17. Please help ASAP.
Thanks,
Kavitha.
Hi Andrea,
We rebuilt index on table NAST and that did not work. Our issue is resolved now, as we reduced the number of entries in table NAST only for YADR variant. We reduced around 2 million records and also changed processing mode to 4, which creates less entries compared to processing mode 3 in NAST.
Thank you so much for the time.
Kavitha Rajan.
Try to increase these parameter:
abap/heap_area_dia 2000000000 --> 4000000000
abap/heap_area_nondia 0 --> 4000000000
abap/heap_area_total 17173577728 --> 4000000000
Restart your AS after the modification to activate it.
Regards
Matteo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Some time the parameter of notes Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel and Note 88416 - Zero administration memory management are not sufficient.
In my experience the parameter that I suggested you don't create any issue.
A suggestion should be to change the parameter, execute the job that you need, and after that retur to the original value.
Hi Kavitha,
Could you check below SAP note.
Note 654901 - Short dump occurs when updating the message language
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
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.