INCL_NOT_ENOUGH_ROLL SAP ABAP Runtime Error incl not enough roll

INCL_NOT_ENOUGH_ROLL is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: & - Text Include (no Short Dump, only Text Module)

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

INCL_NOT_ENOUGH_ROLL ABAP Runtime Error

Perform an analysis to find out whether this request makes sense or whether a program error has occurred. Pay particular attention to the internal table entries listed below. Please see memory size for more details about the possible cause of this runtime error and how it could be avoided.

Include: SAP memory too small. Try to find out (using specific data selection for example) whether the transaction will run with less main memory.

If the problem is due to a temporary bottleneck, run 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 session o ztta/roll_extension (10.000.000 - 500.000.000) available memory/user in extended memory EM o ztta/max_memreq_MB maximum size of an individual memory request (in MB) o abap/heap_area_total (100.000.000 - 1.500.000.000) available memory (malloc) for all users of an application server. If several background processes are running on one server, temporary bottlenecks can 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.

o abap/heap_area_dia: (10.000.000 - 1.000.000.000) restriction of the memory that can be allocated to the heap with malloc per dialog process.

Parameter for background processes:

o abap/heap_area_nondia: (10.000.000 - 1.000.000.000) restriction of the memory that can be allocated to the heap with malloc per background process.

Other memory-relevant parameters are:

o em/initial_size_MB: (35 - 1200)
Extended memory area from which all users of an application server can meet their memory needs.

o abap/shared_objects_size_MB:
Size of the shared memory area that can be used to save shared objects area instances. This memory area is global for all users of the application server. The amount of memory requested is no longer available. Each transaction requires some main memory space to process application data. If the operating system does not have any more memory, the transaction is terminated.