Abap Runtime Error TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

Hi All,

We are getting Abap run time error :

Runtime Errors         TSV_BTR_PAGE_ALLOC_FAILED ( when application team run Transaction : VA05N in Background)

Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED  ( when application team run Transaction : VA05N in Dialog)

Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED

Date and Time          06.05.2013 18:15:47

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 memory-relevant parameters are:

    em/initial_size_MB:         (35-1200)

           Extended memory area from which all users of an

           application server can satisfy their memory requirement.

Error analysis

    The internal table "\PROGRAM=SAPMS380\DATA=FT[]" 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: 520

    Number of rows: 10204

    Allocated rows: 10204

    Newly requested rows: 16 (in 1 blocks)

How to correct the error

    The amount of storage space (in bytes) filled at termination time was:

    Roll area...................... 6738368

    Extended memory (EM)........... 2002720576

    Assigned memory (HEAP)......... 3000012704

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

    Paging area.................... 81920

    Maximum address space.......... 4294967295

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

    "SAPMS380" or "MS380F10"

    "EXTRACT_STRINGS_FROM_SNAP"

Current Parameter values

Roll, extended and heap memory EXTM

ztta/roll_area                7500000    Byte  Roll area per workprocess (total)

ztta/roll_first               1          Byte  First amount of roll area used in a dialog WP

ztta/short_area               4000000    Byte  Short area per workprocess

rdisp/ROLL_SHM                20280      8 kB  Part of roll file in shared memory

rdisp/PG_SHM                  40960      8 kB  Part of paging file in shared memory

rdisp/PG_LOCAL                150        8 kB  Paging buffer per workprocess

em/initial_size_MB            40960      MB    Initial size of extended memory

em/blocksize_KB               4096       kB    Size of one extended memory block

em/address_space_MB           4092       MB    Address space reserved for ext. mem. (NT only)

ztta/roll_extension           3000000000 Byte  Max. extended mem. per session (external mode)

abap/heap_area_dia            3000000000 Byte  Max. heap memory for dialog workprocesses

abap/heap_area_nondia         3000000000 Byte  Max. heap memory for non-dialog workprocesses

abap/heap_area_total          6000000000 Byte  Max. usable heap memory

abap/heaplimit                40000000   Byte  Workprocess restart limit of heap memory

abap/use_paging               0                Paging for flat tables used (1) or not (0)

Awaiting for your reply.

Vijay

[Former Member]

Hi Vijay

As Samuli said limit the amount of data you are looking to process. You can do this by creating a variant and run it in the background.

Thanks

AZ

[Former Member]

According to the dump, only 2 GB of ext. memory was used although 3 GB was available. I think it was actually the heap limit that caused the dump. In other words just increasing ztta/roll_extension won't help. You will have to figure out why the instance is not using ext. memory upto ztta/roll_extension but switching to heap memory instead. If you are unable to figure it out, increasing the heap limits should get rid of the short dump. See the attached link for details on the SAP Memory Management for UNIX.

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/49/32f0b9e92e3504e10000000a421937/frameset.htm

[Former Member]

Thanks every one ....!

Issue is Resolved .

We have changed abap/heap_area_dia to 5 GB (earlier it was 3 GB) and executed Transaction VA05N.

It got successful. (SE38 --> RSMEMORY and changed the parameter and after the transaction is completed changed parameter value to previous value i.e, 3GB).

Thanks Again for your Support..!

[Former Member]

What Operating System? Windows? 32-bit or 64-bit? Your instance profile parameters currently limit you from running the transaction. Before increasing the instance profile parameters find out if you can limit the amount of data processed by the transaction and see if there are any SAP notes describing programming errors with the transaction.

[Former Member]

Hi Samuli,

We are using AIX 64 bit. I have asked Application team to decrease amount of Data selection but they said it is not possible. So I have suggested Clients to increase below parameter by 2 GB.

Current Parameter values

Roll, extended and heap memory EXTM

ztta/roll_extension           3000000000 Byte  Max. extended mem. per session (external mode)

Thanks and Regards

Raghavendra

[Former Member]

Hi Rag

Thats a big jump. Try increasing by 500MB.

Did the Developer explain why the variant could not be reduced?

Thanks

AZ