SYSTEM_SHM_NO_ROLL SAP ABAP Runtime Error system shm no roll

SYSTEM_SHM_NO_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: O - Resource Shortage

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.

SYSTEM_SHM_NO_ROLL ABAP Runtime Error

Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

The memory request for <runtime parameter> bytes could not be complied with. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.

A memory bottleneck occurred while writing to the following area instance:
<runtime parameter>

More main memory area was requested.
The total available space has already been assigned however. Possible causes:
- Lots of (large) internal tables
- Lots of (large) programs active
- Deep nesting of subroutines with large amounts of local data.

The size of the shared objects memory is set by profile parameter abap/shared_objects_size_MB.

The amount of memory still available for internal sessions is displayed in transaction ST02. Either the shared objects memory is full, or a memory limit specified in area administration was reached. No more memory could be allocated in the internal session before the system could trigger the (catachable) exception CX_SHM_OUT_OF_MEMORY either. The transaction therefore had to be terminated.