on 10-02-2009 2:44 PM
Hi All,
While executing GD13 transaction code for some functional activity, the below dump is occurring:
TSV_TNEW_PAGE_ALLOC_FAILED.
Neither we can not change any memory parameter for a temporary activity which is consuming high memory, nor the activity can be splitted in steps for business criticality. From BASIS point view what can be done to make the GD13 activity successful avoiding the memory issue?
System ECC 6.0 (Netweaver 2004s)
(One SAP note: 600176, is available, but that is for lower version, not applicable for ECC 6.0)
Please share your ideas.
Thanks & Regards,
Sujit.
It is solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Neither we can not change any memory parameter for a temporary activity which is consuming high memory, nor the activity can be splitted in steps for business criticality. From BASIS point view what can be done to make the GD13 activity successful avoiding the memory issue?
That close most of the options... I would have splitted the task or tweaked the memory parameters, so theres no much for me to add.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But, unfortunately, the activity can not be splitted and the respective team is asking for solution
From your point of view the solution is very simple, you need to tweak the memory so it can handle the volume, if thats not possible then you arrived to a bottleneck. If the note does not apply to ECC is because the code was corrected so as far as code corrections to prevent the dump I believe you could be wasting your time.
Also can you post the details of the dump?
Regards
Juan
Hi Juan,
Thanks for reply.
Below is the dump details:
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.
Error analysis
The internal table "\FUNCTION=G_GLU1_ACCUMULATE_FOR_GD13\DATA=E_T_GLU1_CUM"
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: 4764
Number of rows: 966
Allocated rows: 966
Newly requested rows: 2 (in 1 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server gvaaps51_PRD_51 on host gvaaps51 (wp 5)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
The error reported by the operating system is:
Error number..... " "
Error text....... " "
I am not pasting the SAP recommendation for increasing memeory parameter values, which is generic.
I have to find some way to help the team to execute the activity.
Your suggestion will be highly appreciated.
Thanks & Regards,
Sujit.
User | Count |
---|---|
87 | |
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.