How To Fix SHMM035 - Memory snapshot & written

SAP Error Message - Details

• Message type: E = Error

• Message class: SHMM - Shared Objects Monitor

• Message number: 035

• Message text: Memory snapshot & written

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SHMM035 - Memory snapshot & written ?

  The SAP error message SHMM035 typically relates to issues with memory management in the SAP system, specifically concerning the shared memory management (SHMM) component. This error indicates that a memory snapshot has been taken and written, which can be a part of the system's memory management processes.
  Cause:
  
  Memory Allocation Issues: The error may arise due to insufficient memory allocation for the SAP instance, leading to problems when the system attempts to manage shared memory.
  Configuration Errors: Incorrect configuration settings in the instance profile related to memory parameters can lead to this error.
  Resource Limits: Operating system-level resource limits (like ulimit settings) may restrict the amount of memory that can be allocated to the SAP instance.
  High Load: A sudden spike in load or memory usage can trigger this error, especially if the system is not adequately sized for the workload.
  
  Solution:
  
  
  Check Memory Configuration:
  
  Review the instance profile parameters related to memory, such as abap/heap_area_dia, abap/heap_area_nondia, and enque/table_size.
  Ensure that the parameters are set according to the recommended values for your system's workload.
  
  
  
  Increase Memory Allocation:
  
  If the system is running out of memory, consider increasing the memory allocation for the SAP instance. This can be done by adjusting the parameters in the instance profile.
  
  
  
  Monitor System Load:
  
  Use transaction codes like ST03N or ST06 to monitor system performance and memory usage. Identify any processes that are consuming excessive memory and optimize them.
  
  
  
  Check Operating System Limits:
  
  Verify the operating system's memory limits (e.g., using ulimit on Unix/Linux systems) and adjust them if necessary to allow for more memory allocation.
  
  
  
  Review SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on memory management best practices.
  
  
  
  Restart the SAP Instance:
  
  In some cases, a restart of the SAP instance may help clear temporary memory issues.
  
  
  
  Related Information:
  
  SAP Memory Management: Understanding how SAP manages memory can help in troubleshooting. SAP uses different types of memory (heap memory, shared memory, etc.) for various processes.
  Transaction Codes: Familiarize yourself with transaction codes like SM04 (User Overview), ST02 (Tune Summary), and SM50 (Process Overview) to monitor and manage memory usage.
  SAP Basis Administration: Knowledge of SAP Basis administration is crucial for managing memory settings and resolving related issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with SAP support or a qualified SAP Basis administrator for further assistance.