TSV_TNEW_PAGE_ALLOC_FAILED ABAP runtime error

[Former Member]

Hi Experts,

iam geting ABAP runtime error TSV_TNEW_PAGE_ALLOC_FAILED  in PRD system.

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

Error analysis
    The internal table "\PROGRAM=YKE_DEPO_INTERFACE\DATA=TB_MSEG[]" 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: 410
    Number of rows: 0
    Allocated rows: 16
    Newly requested rows: 4703488 (in 146984 blocks).

Please find the Above Dump Attahced.

Regards

Ashok

[Former Member]

Hi Ashok,

     As the dump says, there is no space available for extending the interenal table. One possible way to resolve the problem is by asking basis folks to provide more memory space for processing. The other way is to see if we can reduce the number of records being processed. Check if there are duplicate entries in the table, avoid having unused columns in the internal table etc..

~Hope this helps,

Athreya

[Former Member]

Hi Athreya,

We have Space in the Database.Beacuse Iam Thinking its not an Space Problem..Can u  tell me is there anyother problem can cause this Dump.Due to this one of our Job geting Failed daily.

Regards

Ashok

[Former Member]

Check the length and structure of internal table and the fields you are selecting.

[Former Member]

Hi,

is finished the table space in your system.

send the dump to your basis team, they resolve, adding more space.

best regards

[RaymondGiuseppi]

There is usually much more data in production systems than in quality or development system. And user will not always fill selection criteria (not without constraint) So If you load a very huge database table in memory without selecting required fields or restriction on record to load this kind of message is prone to be raised.

If you are sure that the request storage space is correct, BC team can change some system parameters (Those are listed in the standard dump) but there are limit to server memory and this is not always a correct selection.

Try to add mandatory selection criteria, load only required fields, free memory once no longer required...

Also, use search tool at scn, this question was already widely posted in the forum.

Regards,

Raymond