EXPORT_NO_SHARED_MEMORY SAP ABAP Runtime Error export no shared memory

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

EXPORT_NO_SHARED_MEMORY ABAP Runtime Error

These sized can be changed using the profile parameters "rsdb/esm/buffersize_kb" and "rsdb/esm/large_object_size". You can find more information about these parameters in transaction RZ11.
Note that for performance reasons one object cannot occupy too much of the buffer. The maximum permitted object size is therefore much smaller than the total size of the buffer. Error code...............: <runtime parameter>.
Table...................: <runtime parameter>.
Key.......................: <runtime parameter>.
Data length..............: <runtime parameter>. The EXPORT data cluster is too large for the SHARED 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.

The SHARED MEMORY can only save objects of up to a maximum size (1) and has a limited size itself (2).
The size (<runtime parameter>) has been exceeded here. Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.