TSV_TNEW_PAGE_ALLOC_FAILED with SAPLXRSA

[Former Member]

HI,

When I try to load BI system (report: SAPLXRSA running on the ECC system on an another machine), I got the error below

I configured heap = 4GB and em = 4GB

Why the storage was 2G when it crashed ?

What could be the problem ?

Thanks in advance (NW700)

================================================================================

Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          25.05.2012 21:40:39

  Error analysis
     The internal table "\FUNCTION-POOL=ARFC\DATA=SENDDATA[]" 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: 1918
     Number of rows: 859491
     Allocated rows: 859491
     Newly requested rows: 8 (in 1 blocks)

How to correct the error
     The amount of storage space (in bytes) filled at termination time was:

     Roll area...................... 1617472
     Extended memory (EM)........... 2002747344
     Assigned memory (HEAP)......... 2000091296
     Short area..................... " "
     Paging area.................... 0
     Maximum address space.......... 4294967295

===============================================================================

[former_member189725 · Accepted solution]

Can you please extend the ztta/roll_extension to 4GB , so that temporarily you can get out of the issue

Please check if you can reduce the range of data selection .

Regards

Ratnajit

[Former Member]

Hi ,

Please check what are the parameter settings for below and try to increase them.

ztta/roll_area,

abap/heaplimit,

abap/heap_area_dia,

abap/heap_area_nondia = 0,

abap/heap_area_total,

ztta/short_area

Thanks,

Ravi

[Former Member]

Hi ,

Please check what are the parameter settings for below and try to increase them.

ztta/roll_area,

abap/heaplimit,

abap/heap_area_dia,

abap/heap_area_nondia = 0,

abap/heap_area_total,

ztta/short_area

Thanks,

Ravi

[former_member185954]

Hello,

Simply beefing up memory without investigating the root cause is generally not recommended.

Your BI extactors running on source system crashing due to memory problems would mean that you would need someone from ABAP skill set to have a look into the extractors in CMOD transaction.

please ask your ABAP team to debug as to why the extraction program is picking up so much memory from the pool.

Regards,

Siddhesh

[Former Member]

Hi,

You can find the exact time and the work process number in the shortdump.

Please check the WP log when the shortdump created.

You can find there the parameter which you should increase.

Laszlo

[Former Member]

Hi,

It does not look like a custom transaction. Use RZ10 to increase the profile parameters below
(assuming you have 64 bit OS/machin):

(First test on test server)

========

parameter: rdisp/PG_SHM

value: 262144

parameter: rdisp/PG_MAXFS

value: 262144

========

You could trace the running process through SM66 and how much memory it is allocating.

Above values should resolve the issue. As Rajnit said, data selection criteria is very important which exhausts the available memory assigned to dialog process. try executing the transaction in background if it is a possibility.

Regards,