cancel
Showing results for 
Search instead for 
Did you mean: 

Report MB5L giving runtime error TSV_TNEW_PAGE_ALLOC_FAILED

Former Member
0 Kudos

Hi,

While running the Report MB5L we are getting the runtime

error "TSV_TNEW_PAGE_ALLOC_FAILED"

We tried to schedule this report at non-peak hours but it again got

terminated with same error.

We are using 12GB of RAM.

ztta/roll_area 6500000

ztta/roll_extension 4000317440

abap/heap_area_total 3001024512

abap/heap_area_dia: 5000683008

abap/heap_area_nondia: 2000000000

em/initial_size_MB: 8192

Please find the attached screenshot of ST22 dump analysis.

Regards,

Prashant

Edited by: Prashant Shukla on Feb 25, 2009 11:10 AM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I've seen this error occur for two reasons. One is that there is too much data, and that is usually the problem. The other is when there's no data but that has been program-specific.

Note 843776 should help you with your issue.

You can extend your roll area or whatever memory you want but if you keep doing that, your users will eventually stop complaining about reports not working and start complaining about everything being really slow because of their massive reports.

There is one parameter I like to point out.

ztta/max_memreq_MB

This is, by default, 64MB. In most cases, that's fine. I work with IS-OIL and it's a hog and needs more. Basically, you can set your roll as high as you want, but once it gets past this number you crash. I don't know how much this applies outside of IS-OIL. I never saw it before this project.

Good Luck.

JPReyes
Active Contributor
0 Kudos

Not much information here,

Try reducing the scope of the report.

regards

Juan

Former Member
0 Kudos

Hi Juan,

We also tried to reduce the scope of the report but still we are facing the same issue.

Do we require any tuning in the mentioned parameters or we need to go for RAM upgradation as this is related to memory.

Correct me if I am wrong.

What else you require to analyze the issue?pls let me know

Regards,

Prashant

Edited by: Prashant Shukla on Feb 25, 2009 11:27 AM

JPReyes
Active Contributor
0 Kudos

This is certainly a tweaking problem... I don't think you need more RAM.

I think you need to reduce the scope of the report as said before. Also can you post the errors on the dump.

Regards

Juan

Former Member
0 Kudos

Hello,

The dump itself will be very useful if you go through it properly.

You can find the details of the memory parameters and their values at the time of termination in the dump this will help in analysing the issue from memory perspective. Also the dump shows at which line of the program the termination occured, etc.,

Since this is related to memory you can always ask your ABAPer to first check the code of the program to reduce if any expensive statements.

Regards,

Yoganand.V

Former Member
0 Kudos

Hi Juan,

Pls find the details below-:

Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED

Date and Time 24.02.2009 23:31:32

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.

If the error persists, ask your system administrator to check the

following profile parameters:

Error analysis

The internal table "\FUNCTION=MBEW_EXTEND\DATA=SEARCH_MBEWH_TAB[]" 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: 372

Number of rows: 354608

Allocated rows: 354608

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...................... 6203136

Extended memory (EM)........... 4001304840

Assigned memory (HEAP)......... 2000059568

Short area..................... " "

Paging area.................... 32768

Maximum address space.......... 18446697160833538863

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" " "

"SAPLMG27" or "LMG27F02"

"SEARCH_EXIT"

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.

System environment

SAP-Release 700

Application server... "ecprdciclu"

Network address...... "172.25.1.34"

Operating system..... "Linux"

Release.............. "2.6.18-53.el5"

Hardware type........ "x86_64"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 19

Shortdump setting.... "full"

Database server... "isrecprdb2"

Database type..... "ORACLE"

Database name..... "RPD"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Nov 18 2008 20:45:39"

create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 185

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Linux 2.6"

Memory consumption

Roll.... 6203136

EM...... 4001304840

Heap.... 2000059568

Page.... 32768

MM Used. 5803144952

MM Free. 199241240

User and Transaction

Client.............. 610

User................ "SANCHIT"

Language key........ "E"

Transaction......... " "

Transactions ID..... "49A289F286FA2313E1000000AC190122"

Program............. "SAPLMG27"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where terminated

Termination occurred in the ABAP program "SAPLMG27" - in "SEARCH_EXIT".

The main program was "RM07MBST ".

In the source code you have the termination point in line 558

of the (Include) program "LMG27F02".

The program "SAPLMG27" was started as a background job.

Job Name....... "RM07MBST"

Regards,

Prashant

Former Member
0 Kudos

Hi Yoganand,

This is a standard SAP Report MB5L.....do we require any kind of tuning for that?

Please let me know to what extent I need to change the parameters listed in Dump. Is there any kind of calculation for that?

Regards,

Prashant