How To Fix 00861 - High-water mark of extended memory management slots since last query

SAP Error Message - Details

• Message type: E = Error

• Message class: 00 -

• Message number: 861

• Message text: High-water mark of extended memory management slots since last query

What causes this issue?

Each internal session needs one such extended memory slot. (Each
external session can contain up to 9 internal sessions).

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 00861 - High-water mark of extended memory management slots since last query ?

  The SAP error message "00861 High-water mark of extended memory management slots since last query" typically indicates that the system has reached a limit in the allocation of extended memory slots. This can occur when there are too many memory requests or when the memory is not being released properly after use.
  Cause:
  
  Memory Allocation Limits: The system has a predefined limit for the number of extended memory slots that can be allocated. If this limit is reached, the error will be triggered.
  Long-Running Transactions: If there are long-running transactions or processes that hold onto memory without releasing it, this can lead to exhaustion of available memory slots.
  Memory Leaks: Applications or custom code that do not properly release memory can lead to memory leaks, causing the system to run out of available slots.
  Configuration Issues: Incorrect configuration settings for memory management in the SAP system can also lead to this error.
  
  Solution:
  
  Monitor Memory Usage: Use transaction codes like SM50 or SM66 to monitor the processes and their memory usage. Identify any long-running or stuck processes that may be consuming memory.
  Restart Processes: If you identify processes that are consuming excessive memory, consider restarting them to free up memory slots.
  Adjust Memory Parameters: Review and adjust the memory parameters in the SAP profile (e.g., abap/heap_area_total, abap/heap_area_dia, abap/heap_area_nondia) to allocate more memory if necessary.
  Check for Memory Leaks: Analyze custom code or third-party add-ons for potential memory leaks. Use tools like the SAP Memory Inspector or transaction ST02 to analyze memory usage.
  Increase Extended Memory: If the system is consistently running out of memory, consider increasing the extended memory allocation in the SAP profile parameters.
  System Restart: In some cases, a system restart may be necessary to clear memory and reset the memory management slots.
  
  Related Information:
  
  Transaction Codes: 
  
  SM50 / SM66: Monitor active processes.
  ST02: Analyze memory usage and buffer statistics.
  ST04: Monitor database performance and memory usage.
  
  
  SAP Notes: Check for relevant SAP Notes that may provide additional guidance or patches related to memory management issues.
  Documentation: Review SAP documentation on memory management for best practices and configuration guidelines.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with SAP support or a technical consultant who can provide deeper insights into the specific configuration and usage patterns of your SAP system.