Skip to Content
avatar image
Former Member

Run-time error "TSV_TNEW_PAGE_ALLOC_FAILED" occurred

Hi all,

I am running BDLS report in background after system copy. Its getting failed. On checking the failed job log in SM37 am getting the TSV_TNEW_PAGE_ALLOC_FAILED runtime error and message as below.

I have checked and all memory parameters looks fine and similar to other systems, No other program/report is running on the server. Please help.

Memory low. Leave the transaction before taking a break!

Message no. 00072

Diagnosis

The memory on your application server is running low.

System Response

You are exclusively using one of the few work processes running on the application server. So that this does not hinder the other users too much, the work process is released if you do not work with it for a few minutes. The system terminates the transaction, causing you to lose data that you previously entered.

Procedure

Continue to work as normal and exit the transaction before you take a long break

memory parameter settings as below

ztta/roll_area 3000320 Byte

ztta/roll_first 1024 Byte

ztta/short_area 1600000 Byte

rdisp/ROLL_SHM 16384 8 kB

rdisp/PG_SHM 8192 8 kB

rdisp/PG_LOCAL 150 8 kB

em/initial_size_MB 6144 MB

em/blocksize_KB 4096 kB

em/address_space_MB 4092 MB

ztta/roll_extension 2000683008 Byte

abap/heap_area_dia 2147483648 Byte

abap/heap_area_nondia 2147483648 Byte

abap/heap_area_total 2147483648 Byte

abap/heaplimit 83886080 Byte

abap/use_paging 0

WP trace info

A *** ERROR => User SSeeeN reached avail. heapsize = 2047 MB: see ST22 [abstor.c 1766]

A *** ERROR => Increase abap/heap_area_total [abstor.c 1768]

A *** ERROR => heap memory WP0: 2047 MB [abstor.c 1771]

A *** ERROR => heap memory WP1: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP2: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP3: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP4: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP5: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP6: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP7: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP8: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP9: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP10: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP11: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP12: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP13: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP14: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP15: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP16: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP17: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP18: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP19: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP20: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP21: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP22: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP23: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP24: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP25: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP26: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP27: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP28: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP29: 0 MB [abstor.c 1771]

A *** ERROR => heap memory WP30: 0 MB [abstor.c 1771]

Please help.

Regards,

Sandeep

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jan 21, 2009 at 12:58 PM

    Hai,

    You have problem with the Memory, it is getting exhausted in order to execute the transaction.

    Try increasing the Heap memory parameters, check SAP Note 20527,790099,146289 (if 64 bit).

    Regards,

    Yoganand.V

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      We have got the root cause of the issue. When you run BDLS for BW/APO systems where you have implemented process chains apart from changing logical system names in tables it recreates the function methods for DTP - Data transfer processes for the new logical system for which it asks for transport request numbers.

      if you run BDLS in bg mode, then as it is not able to show the input screen, it goes into some kind of loop and keeps on writing to the job log file and when it exceeds 1 gb size its unable to write further and job terminates.

      in such cases you have to run the BDLS in dialog mode only for inputting the transport request number.

      Thanks for your help!!!

      Regards,

      Sandeep.