SAP Error: "Roll-In failed, Session Terminated" Step by Step

 The Error "Roll-In failed, Session Terminated" or similar like "Roll-Out failed" or "No more roll area" etc all originates due to incorrect memory parameters' settings.

PS: THIS ACTIVITY WILL NEED RESTART OF SERVER INSTANCE SAP SERVICES. 

Follow the following steps to rectify:

1. Check memory usage

tcode: ST02

and concentrate on "Extended memory" as highlighted. If this exceeds 95% on peak load then you are most likely to face these errors.

Main culprit for these errors is "HARDCODING THE MEMORY PARAMETER VALUES" instead of using derived value.

so with time memory consumption/requirements of system increases but memory parameters holds the same old value.

SAP has introduced zero administration memory management for the ABAP server. a concept which uses parametrized values or formulaeted values in memory parameters.

2. Defining the Parameters

tcode: RZ10

select applicable instance profile using F4 help and select extended maintenance and click on change. 

First and major parameter is PHYS_MEMSIZE. Default value of this parameter is equal to [RAM] and its value can be changed as PHYS_MEMSIZE = 50%.

Here is the catch, how much value it should have. 

Normal memory in sap system will be used by OS, database (if instance contains both DB and application server on a single node), SAP application server backup services etc. Normally backup services will run in non peak hours so we can ignore this. 

We can leave 50% to OS, DB and other emergency services.

50% of rest must be alloted to sap application server.

so parameter will be PHYS_MEMSIZE = 50%

Default values of zero administration memory management up to kernel version 7.2x

[RAM] = size of the physical main memory
[PM] = value of the profile parameter PHYS_MEMSIZE (standard value=[RAM])
[US] = factor dependent on [PM] - calculated automatically

Profile parameter	Standard 32-bit	Standard 64-bit	Unit:
em/initial_size_MB	[PM]	[PM]	MB
em/max_size_MB	20000	1.5 * [PM]	MB
em/address_space_MB	512	4096	MB
ztta/roll_first	1	1	byte
ztta/roll_area	2000000	3000000	byte
ztta/roll_extension	2000000000	2000000000	byte
abap/heap_area_dia	2000000000	2000000000	byte
abap/heap_area_nondia	2000000000	0	byte
abap/heap_area_total	2000000000	[PM]*1048576	byte
rdisp/ROLL_MAXFS	[US] * 100	[US] * 100	8KB block
rdisp/ROLL_SHM	[US] * 100	[US] * 100	8KB block
rdisp/PG_MAXFS	32768	32768	8KB block
rdisp/PG_SHM	[US] * 50	[US] * 50	8KB block

Important (only valid for kernel < 7.40):

em/global_area_MB + abap/share_objects_size_MB + ztta/roll_extension
    must fit in the following address window: 
em/address_space_MB

If ("em/global_area_MB" + "abap/shared_objects_size_MB") > "em/address_space_MB", the system does not start (error in "dev_disp" dispatcher).

If ("em/global_area_MB" + "abap/shared_objects_size_MB") < "em/address_space_MB", ("em/address_space_MB" – "em/globa_area_MB" – "abap/shared_objects_size_MB") is available for the extended memory. The value of "ztta/roll_extension" acts as a quota.

At present, "em/address_space_MB" cannot be calculated automatically taking into account the specified parameters in kernel versions < 7.40.

Default values of zero administration memory management as of kernel version 7.40

As of kernel version 7.40, certain profile parameters are calculated for all operating system platforms in accordance with the available memory. It is also now possible to calculate parameter values with formulas.

[RAM] = size of the physical main memory

In 7.40, parameter values can contain formulas. The expression $(Parameter) in the value of a parameter references the value of the parameter with the name Parameter.

Profile parameter	Standard 64-bit	Unit:
PHYS_MEMSIZE	(1.0 * [RAM])	MB
em/initial_size_MB	(0.7 * $(PHYS_MEMSIZE))	MB
em/max_size_MB	(1.5 * $(PHYS_MEMSIZE))	MB
abap/buffersize	($(em/initial_size_MB) * 1024 * 0.15)	KB
abap/programs	($(abap/buffersize) / 4)	Entries
abap/heap_area_dia	2000000000	Bytes
abap/heap_area_nondia	0	Bytes
abap/heap_area_total	(1048576 * $(PHYS_MEMSIZE))	Bytes
abap/shared_objects_size_MB	($(em/initial_size_MB) * 0.02)	MB
em/address_space_MB	($(em/initial_size_MB))	MB
em/max_size_MB	($(PHYS_MEMSIZE) * 1.5)	MB
rdisp/wp_ca_blk_no	($(rdisp/elem_per_queue) * 3)	Entries
rdisp/PG_SHM	(max(min(1000+40*max(5,floor(($(PHYS_MEMSIZE)-128)   *25/128)),16384),1024))	8KB block
rdisp/PG_MAXFS	32768	8KB block
rsdb/ntab/entrycount	($(zcsa/db_max_buftab))	Entries
rsdb/ntab/ftabsize	(min(500000, ($(rsdb/ntab/entrycount))))	KB
rsts/ccc/cache07	($(rsts/ccc/cachesize) * 0.1)	Bytes
rtbb/buffer_length	($(zcsa/table_buffer_area) * 0.1 / 1024)	KB
rtbb/max_tables	($(zcsa/db_max_buftab) * 0.1)	Entries
zcsa/table_buffer_area	(min(3333333333, (max(30000000,($(em/initial_size_MB) * 1024 * 1024 * 0.1)))))	Bytes
ztta/roll_extension	2000000000	Bytes

1. The formulas in the table are based on the 7.45 kernel version. They might be adjusted in later kernel versions in line with observations from EarlyWatch sessions.
2. The calculated values from the kernel you use can differ from these. For detailed information, see transaction SE38, report rsparam - either column 3 (System Default (Unsubs. Form)) or by double-clicking on the parameter line, 1.1 C kernel.
3. In individual cases, customer-specific requirements may demand an individual parameterization. Here, we normally recommend the setting of deviating values following an EarlyWatch Session.
4. If you want to use the default values that were calculated automatically, you must not list the relevant profile parameter in the instance profile or Default.pfl. If you want to use transaction RZ10 to delete or deactivate the above mentioned profile parameters, use the "Extended maintenance" function in RZ10. "Basic maintenance" is not suitable for deleting these parameters.
5. Zero administration memory management on Windows intends to reduce the number of parameters entered into the profiles. As a result, the maintenance and configuration of the application server is simplified, and the available resources are optimally used.

SAP Note 88416 can be checked.