How To Fix UGMD390 - Object is too large for shared memory

SAP Error Message - Details

• Message type: E = Error

• Message class: UGMD - FIN Master Data: Messages

• Message number: 390

• Message text: Object is too large for shared memory

What causes this issue?

The internal object is too large for the shared memory.

System Response

The system has temporarily deactivated use of the shared memory on the
application server &V1&. This has a negative effect on performance.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Increase the memory space reserved for the shared memory. Call up
transaction <DS:TRAN.RZ11>Profile Parameter Maintenance</> and change
the parameter "rsdb/esm/large_object_size".

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UGMD390 - Object is too large for shared memory ?

  The SAP error message UGMD390, which states "Object is too large for shared memory," typically occurs when an attempt is made to load an object into shared memory that exceeds the maximum size limit set for shared memory in the SAP system. This can happen with various objects, such as large internal tables, data structures, or other memory-intensive operations.
  Cause:
  
  Object Size: The object being processed is larger than the maximum allowed size for shared memory.
  Configuration Limits: The configuration settings for shared memory in the SAP system may be set too low to accommodate the size of the object.
  Memory Allocation: Insufficient memory allocation for shared memory in the SAP kernel or operating system settings.
  
  Solution:
  
  
  Increase Shared Memory Limits:
  
  You can increase the shared memory limits in the SAP system configuration. This typically involves adjusting parameters in the instance profile (e.g., abap/shared_objects_size_MB).
  Use transaction RZ10 to modify the instance profile and increase the shared memory size.
  
  
  
  Optimize Object Size:
  
  Review the object that is causing the error and see if it can be optimized. For example, consider breaking down large internal tables into smaller chunks or using more efficient data structures.
  
  
  
  Check Memory Settings:
  
  Ensure that the operating system settings for shared memory are configured correctly. This may involve adjusting kernel parameters (e.g., shmmax, shmall on Unix/Linux systems) to allow for larger shared memory segments.
  
  
  
  Use Alternative Storage:
  
  If the object is too large to fit into shared memory, consider using alternative storage methods, such as database tables or temporary files, to handle the data.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may provide additional guidance or patches related to this error. You can search for notes in the SAP Support Portal.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for details on memory management and configuration settings.
  Transaction Codes:
  
  RZ10: To change instance profile parameters.
  RZ11: To check and modify profile parameters dynamically.
  
  
  Monitoring Tools: Use transaction ST02 (Tune Summary) to monitor memory usage and identify potential bottlenecks in shared memory.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.