Solution : https://service.sap.com/sap/support/notes/972757 (SAP Service marketplace login required)
Summary :
The SYSTEM_NO_SHM_MEMORY runtime error indicates that an application server lacks adequate shared memory for storing data in its shared objects area, observed through transaction SHMM. To address potential memory constraints, adjusting the 'abap/shared_objects_size_MB' parameter is recommended. Efficient application diagnostics are possible by examining the area through transaction SHMA, reviewing usage history and object attributes. For programmers, avoiding errors involves employing methods like CL_SHM_UTILITIES=>GET_CURRENT_USAGE to monitor and manage memory usage effectively. Crucially, from SAP Basis Release 7.10, handling this error via CX_SHM_OUT_OF_MEMORY exception has been streamlined, providing robust controls like DETACH_ROLLBACK.
Key words :
class method cl_shm_utilities=>get_current_usage, system writing additional data, system_no_shm_memory runtime error occurs, system_no_shm_memory runtime error means, sufficient shared objects memory, insufficient shared objects memory, system_no_shm_memory runtime error, shared objects memory, shared object memory, shared objects area
Related Notes :
| 1322182 | Memory consumption of ABAP Shared Objects |
| 1232973 | SYSTEM_NO_SHM_MEMORY short dump |
| 1125941 | FCC Shared Memory Check |