[sap-basis] error TSV TNEW PAGE ALLOC FAILED while generating the report BSIS
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by Satish_Ahirkar (BASIS) on Mar 15 at 1:50 AM |
Hi All,
I am using ECC6.0, with Windows 2003 64bit, 16GM RAM and Database SQL Server 2005. Today when i am i was generating the Report BSIS with Tx. SE11, got the error message "TSV_TNEW_PAGE_ALLOC_FAILED". I looked the Tx ST22, the error message is below:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 15.03.2010 10:30:53
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 memoryrelevant parameters are:
em/initial_size_MB: (351200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Error analysis
The internal table "{O:23*\CLASS=CL_GUI_ALV_GRID}\DATA=MT_DATA" 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: 320
Number of rows: 9281648
Allocated rows: 9281648
Newly requested rows: 32 (in 1 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 5320432
Extended memory (EM)........... 2002747984
Assigned memory (HEAP)......... 2000701088
Short area..................... " "
Paging area.................... 57344
Maximum address space.......... " "
If the error occures in a nonmodified 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" " "
"SAPLSLVC" or "LSLVCF05"
"DATA_TABLE_GET"
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)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System>List>Save>Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities>More
Utilities>Upload/Download>Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks & Regards,
Satish
__.____._ I am using ECC6.0, with Windows 2003 64bit, 16GM RAM and Database SQL Server 2005. Today when i am i was generating the Report BSIS with Tx. SE11, got the error message "TSV_TNEW_PAGE_ALLOC_FAILED". I looked the Tx ST22, the error message is below:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 15.03.2010 10:30:53
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 memoryrelevant parameters are:
em/initial_size_MB: (351200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Error analysis
The internal table "{O:23*\CLASS=CL_GUI_ALV_GRID}\DATA=MT_DATA" 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: 320
Number of rows: 9281648
Allocated rows: 9281648
Newly requested rows: 32 (in 1 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 5320432
Extended memory (EM)........... 2002747984
Assigned memory (HEAP)......... 2000701088
Short area..................... " "
Paging area.................... 57344
Maximum address space.......... " "
If the error occures in a nonmodified 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" " "
"SAPLSLVC" or "LSLVCF05"
"DATA_TABLE_GET"
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)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System>List>Save>Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities>More
Utilities>Upload/Download>Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks & Regards,
Satish
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
In the Spotlight
White Papers
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
