Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

TSV_TNEW_BLOCKS_NO_ROLL_MEMORY / in variance calculation RKKKS1N0


I am getting a dump if we execute the variance calculation in the background.

The roll memory is not enough:

At the moment I having this parameters, two time enlarged

ztta/roll_area 100000000

ztta/roll_extension 4000000000

abap/heap_area_total 4000000000

abap/heap_area_dia 4000000000

abap/heap_area_nondia 4000000000

em/initial_size_MB 4096

I checked the note and enlarge the parameter

1578916 - The system dumps with the runtime error TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

Any ideas ??

Dump Description:

Category               Resource Shortage


Date and Time          06.07.2015 00:06:21

Short text

     No roll storage space of length 4853808 available for internal storage.

What happened?

     Each transaction requires some main memory space to process

     application data. If the operating system cannot provide any more

     space, the transaction is terminated.

What can you do?

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


          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 -

          Restriction of memory allocated to the heap with malloc

          for each dialog process.

   Parameters for background processes:

   abap/heap_area_nondia:        (10.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.

   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.

Error analysis

   The internal table "\FUNCTION-POOL=KALI\DATA=ITCSSL[]" could not be enlarged


   Memory location: "Session memory"

   You attempted to extend the data structure for the management of the

    memory blocks for table "\FUNCTION-POOL=KALI\DATA=ITCSSL[]". However, the

     4853808 bytes required for

    this were no longer available in the specified memory area.

    The amount of memory requested is no longer available.

How to correct the error

    Try to decide by analysis whether this request is

    reasonable or whether there is a program error. You should pay

    particular attention to the internal table entries listed below.

    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



    "SAPLKALI" or "LKALIU03"


    If you cannot solve the problem yourself and want to send an error

    notification to SAP, include the following information:

    1. The description of the current problem (short dump)

       To save the description, choose "System->List->Save->Local File



   2. Corresponding system log

      Display the system log by calling transaction SM21.

      Restrict the time interval to 10 minutes before and five minutes

   after the short dump. Then choose "System->List->Save->Local File


   3. If the problem occurs in a problem of your own or a modified SAP

   program: The source code of the program

      In the editor, choose "Utilities->More


   4. Details about the conditions under which the error occurred or which

   actions and input led to the error.

Information on where terminated

    Termination occurred in the ABAP program "SAPLKALI" - in


    The main program was "RKKKS1N0 ".

Former Member replied

Helpful Answer

Not what you were looking for? View more on this topic or Ask a question