Skip to Content
avatar image
Former Member

A job cancelled with runtime error TSV_TNEW_PAGE_ALLOC_FAILED

A job processing idocs cancelled everyday at same time only once. The job frequency is 1 hr and it cancelled with runtime error "TSV_TNEW_PAGE_ALLOC_FAILED". Please help to solve this issue.

Add comment
10|10000 characters needed characters exceeded

  • Former Member

    Error analysis
    No more rows could be added to internal table
    "\PROGRAM=/BAY1/AN_IDOC_MSG_GET_DATA\DATA=GT_IDOC_ST_SHORT". To make
    troubleshooting possible, the table had to be deleted before this log
    could be compiled. This means that the table will either be displayed
    further down or, if you call the ABAP Debugger from here, with 0 rows.

    When the program was terminated, the internal table had the following
    characteristics:

    Memory location: Session memory
    Row width: 724
    No. of rows: 509260
    Allocated rows: 509260
    Newly requested rows: 16 (in 1 blocks)

    How to correct the error
    The amount of memory (in bytes) used at termination time was:

    Roll area...................... 0
    Extended memory (EM) 502512128
    Assigned memory (HEAP) 447794976
    Short area.....................
    Paging area.................... 24576
    Maximum address space.......... 18446744073709551615
    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:

    "TSV_TNEW_PAGE_ALLOC_FAILED"
    "/BAY1/AN_IDOC_MSG_GET_DATA" bzw. /BAY1/AN_IDOC_MSG_GET_DATA_F01
    "GET_WORKLOAD_RFC_STATUS"
    If you cannot solve the problem yourself, please send the following
    information to SAP:

    1. This description of the problem (short dump)
    To do this, choose System -> List -> Save -> Local File (unconverted)
    on the screen you are in now.

    2. A suitable system log
    To do this, call the system log in transaction SM21. Restrict the time
    interval to ten minutes before the short dump and five minutes after
    it. In the display, choose System -> List -> Save -> Local File
    (unconverted).

    3. If these are programs of your own, or modified SAP programs: Source
    code of these programs
    To do this, choose More Utilities -> Upload/Download -> Download in
    the Editor.

    4. Details regarding the conditions under which the error occurred or
    which actions and input caused the error.

    Information on where terminated
    The termination occurred in ABAP program "/&&&/AN_IDOC_MSG_GET_DATA", in
    "GET_WORKLOAD_RFC_STATUS". The main program
    was "/&&&/AN_IDOC_MSG_GET_DATA".

    In the source code, the termination point is in line 1266 of (Include)
    program "/&&&/AN_IDOC_MSG_GET_DATA_F01".
    Program "/&&&/AN_IDOC_MSG_GET_DATA" was started as a background job.

    Job name....... /&&&/AN_IDOC_MONI
    Job initiator.. ****
    Job number...... 00002100

  • Hi - I have changed your tag from SAP Mentors to ABAP so you can get a faster response.

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Feb 01, 2017 at 07:42 AM

    Check the variant of job and try to reduce the frequency of the criteria.

    If that is not possible change the values of profiles parameters "abap/heap_area_dia" and "abap/heap_area_non_dia" for particular application server.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 01, 2017 at 07:46 AM

    Hello Rohan,

    Can you copy past st22 log?

    thanks

    Tabrayz

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Error analysis
      No more rows could be added to internal table
      "\PROGRAM=/BAY1/AN_IDOC_MSG_GET_DATA\DATA=GT_IDOC_ST_SHORT". To make
      troubleshooting possible, the table had to be deleted before this log
      could be compiled. This means that the table will either be displayed
      further down or, if you call the ABAP Debugger from here, with 0 rows.

      When the program was terminated, the internal table had the following
      characteristics:

      Memory location: Session memory
      Row width: 724
      No. of rows: 509260
      Allocated rows: 509260
      Newly requested rows: 16 (in 1 blocks)

      How to correct the error
      The amount of memory (in bytes) used at termination time was:

      Roll area...................... 0
      Extended memory (EM) 502512128
      Assigned memory (HEAP) 447794976
      Short area.....................
      Paging area.................... 24576
      Maximum address space.......... 18446744073709551615
      If the error occurs in a non-modfied SAP program, you might be able to
      find a solution in the SAP Notes system. If you have access to the SAP
      Notes system, check there first using the following keywords:

      "TSV_TNEW_PAGE_ALLOC_FAILED"
      "/BAY1/AN_IDOC_MSG_GET_DATA" bzw. /BAY1/AN_IDOC_MSG_GET_DATA_F01
      "GET_WORKLOAD_RFC_STATUS"
      If you cannot solve the problem yourself, please send the following
      information to SAP:

      1. This description of the problem (short dump)
      To do this, choose System -> List -> Save -> Local File (unconverted)
      on the screen you are in now.

      2. A suitable system log
      To do this, call the system log in transaction SM21. Restrict the time
      interval to ten minutes before the short dump and five minutes after
      it. In the display, choose System -> List -> Save -> Local File
      (unconverted).

      3. If these are programs of your own, or modified SAP programs: Source
      code of these programs
      To do this, choose More Utilities -> Upload/Download -> Download in
      the Editor.

      4. Details regarding the conditions under which the error occurred or
      which actions and input caused the error.

      Information on where terminated
      The termination occurred in ABAP program "/&&&/AN_IDOC_MSG_GET_DATA", in
      "GET_WORKLOAD_RFC_STATUS". The main program
      was "/&&&/AN_IDOC_MSG_GET_DATA".

      In the source code, the termination point is in line 1266 of (Include)
      program "/&&&/AN_IDOC_MSG_GET_DATA_F01".
      Program "/&&&/AN_IDOC_MSG_GET_DATA" was started as a background job.

      Job name....... /&&&/AN_IDOC_MONI
      Job initiator.. ****
      Job number...... 00002100