Skip to Content

TSV_TNEW_PAGE_ALLOC_FAILED dump

Dear Experts,

we have tried to run payroll simulation by program HIECALC0 program in production system but for one particular PERNER we are facing the the dump TSV_TNEW_PAGE_ALLOC_FAILED.other perners are working fine.

We have reset the buffers and checked parameters everything seems perfect.

anybody please help us to sort it out.

ST22:

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=HIECALC0\DATA=PTEXT[]" 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: 1096

Number of rows: 5297876

Allocated rows: 5297876

Newly requested rows: 8 (in 1 blocks)

Last error logged in SAP kernel

  1. Component............ "EM"

  1. Place................ "SAP-Server <HOSTNAME>_<SID>_<INSTANCE_NO>on host <HOSTNAME> (wp 3)"
  2. Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

  1. Description.......... " "

System call.......... " "

  1. Module............... "emxx.c"

  1. Line................. 2232

The error reported by the operating system is:

Error number..... " "

Error text....... " "

How to correct the error

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

Roll area...................... 0

Extended memory (EM)........... 3930039904

Assigned memory (HEAP)......... 2000065904

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

Paging area.................... 57344

Maximum address space.......... 18446696697067731007

Regards,

Pradeep

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    May 09, 2013 at 07:35 AM

    Hi,

    Indeed, we had the same problem in our servers last week. I was extending the parameters on timely fashion every time and then ruled out the option (Seriously kicked out by Manager for the every downtime :-) )

    However we understood that its not a permanent one, then we knocked the doors of SAP and they provided the exact note for us (Needs to disable the logs)

    Solution is – needs to disable the logs as per the sap note 393820. 

    TSV_TNEW_PAGE_ALLOC_FAILED or STORAGE_PARAMETER_WRONG_SET

         These dumps occur mostly in connection with an internal table, for example TEXTBUFFER. In the standard system, only the log can cause this type of table to overflow. To solve the problem, you can restrict either the number of logged personnel numbers or the log itself. For this purpose, you can reduce the log by individual functions: Menu -> Settings -> Restrict log. You can deselect individual components and save your choice as a display variant.
    The internal table may also overflow due to remuneration statements.

    Hope this should work for you

    Thanks and Regards

    Vijay Kumar G

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Try to use

      package size select and end select

      put your processing  logic in select and endselect.

      package will fetch all data on to application sever and processing logic can be partioned into records

        SELECT *
          INTO TABLE T_1LOG PACKAGE SIZE 50000
          FROM /OPT/VIM_1LOG FOR ALL ENTRIES IN gt_1head
          WHERE DOCID EQ gt_1head-docid.
      REFRESH: t_1head,gt_1log.
      t_1head[] = gt_1head[].
      gt_1log[] = t_1log[].

      SORT gt_1log BY docid.
      DELETE ADJACENT DUPLICATES FROM gt_1log COMPARING docid.

      CLEAR: gs_1head.
      LOOP AT t_1head INTO gs_1head.
         gv_tabix = sy-tabix.
         READ TABLE gt_1log WITH KEY docid = gs_1head-docid
            TRANSPORTING NO FIELDS.
         IF sy-subrc IS NOT INITIAL.
           DELETE t_1head INDEX gv_tabix.
         ENDIF.

      ENDLOOP.

        PERFORM get_data.

        PERFORM calc_data.

        PERFORM save_data.

        REFRESH: t_1log.
      ENDSELECT

  • avatar image
    Former Member
    May 06, 2013 at 01:26 PM

    Hi Pradeep,

    Try to increase the parameter value from your present value ( i think 2 GB is your current value) and try to increase it to 4GB

    ztta/roll_area 

       


    o  ztta/roll_extension 

     

    o  abap/heap_area_total   

    Thanks and Regards,

    Vimal

    Add comment
    10|10000 characters needed characters exceeded

  • May 06, 2013 at 04:57 PM

    Hi Pradeep,

    Please check below notes which may help.

    Note 693661 - Performance - HCM (currently only payroll)

      1684553  - Cost Center Report (RPCPCC00) dumping or timing out

    Thanks,

    Ranjith

    Add comment
    10|10000 characters needed characters exceeded

  • May 06, 2013 at 08:13 PM

    Hello,

    Dump means you are using 4Gb of extended memory then 2Gb of heap for a dialogue process

    Extended memory (EM)........... 3930039904

    Assigned memory (HEAP)......... 2000065904

    You could increase heap parameter

    abap/heap_area_dia by 1Gb and restart instance.

    Also increase abap/heap_area_total     by 1Gb

    regards,

    John Feely

    Add comment
    10|10000 characters needed characters exceeded

  • May 06, 2013 at 01:26 PM

    Hi Pradeep,

    Please provide the details about your system memory.

    total memory ,heap allocation ,extended memory allocation no of work process in system .

    Which plateform your system running .

    Best Regards,

    Atul

    Add comment
    10|10000 characters needed characters exceeded