ABAP Runtime Errors

SYSTEM_NO_SHM_MEMORY SAP ABAP Runtime Error system no shm memory







SYSTEM_NO_SHM_MEMORY 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_NO_SHM_MEMORY ABAP Runtime Error

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.

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

No more memory available for <runtime parameter> bytes in the shared object memory. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.

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

One of the following three situations has occurred:
1. There is not enough free memory available in the shared object memory to store further data.
2. The maximum size for a version of this area specified in area administration will be exceeded in this version if more data is stored.
3. The maximum size for all versions of all instances of this area specified in area administration will be exceeded if more data is stored.

An attempt was made to store the data object in the following area instance: <runtime parameter>

Size of the version (currently being built) .. <runtime parameter>
Maximum size of the version ........................ <runtime parameter>

Shared objects memory in total:
Size used...... ........................... <runtime parameter>
Size allocated ........................... <runtime parameter>
Free memory ............................. <runtime parameter>

(All values in bytes.)

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

Note: Termination does not generally occur immediately after a memory limit has been exceeded. Normally it occurs during a subsequent ABAP statement that might have nothing do with shared objects. The shared object memory is full, or a memory limit specified in area administration has been reached.