How To Fix CSM_VMC090 - Size of the old cache entries deleted in the background

SAP Error Message - Details

• Message type: E = Error

• Message class: CSM_VMC - Messages for VM Container Monitoring

• Message number: 090

• Message text: Size of the old cache entries deleted in the background

What causes this issue?

When saving an object in the cache causes another object to be deleted,
this is called eviction. Objects can be evicted synchronously or
asynchronously. Synchronous eviction means that when the cache is full,
an old object is deleted in order to save the new one. Asynchronous
means that a cleanup job deletes the old objects without a new object
being stored directly.
This number specifies the size in megabytes of the cache entries evicted
asynchronously.
You can find more information in the online documentation under
<DS:KENO.001560AA0E081DEB9290E35086BF84D6>Caching in the VM Container</>

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 CSM_VMC090 - Size of the old cache entries deleted in the background ?

  The SAP error message CSM_VMC090, which states "Size of the old cache entries deleted in the background," typically relates to issues with the cache management in the SAP system, particularly in the context of the SAP Cache Service Manager (CSM). This message indicates that the system is managing its cache entries, and it may be deleting old or unused cache entries to free up space.
  Cause:
  
  Cache Size Limit: The cache may have reached its configured size limit, prompting the system to delete older entries to make room for new ones.
  Configuration Settings: The cache settings may not be optimized for the current workload, leading to frequent deletions of cache entries.
  High Load: A sudden increase in system load or data requests can lead to rapid cache usage, causing older entries to be deleted.
  Background Job: The message may be a result of a background job that is specifically designed to manage cache entries.
  
  Solution:
  
  Review Cache Configuration: Check the cache configuration settings in the SAP system. You may need to adjust the size limits or parameters to better suit your workload.
  Monitor Cache Usage: Use transaction codes like SM12 (for lock entries) or SM21 (for system logs) to monitor cache usage and identify patterns or issues.
  Increase Cache Size: If the cache is frequently reaching its limit, consider increasing the cache size in the system settings.
  Optimize Queries: Review and optimize the queries or processes that are causing high cache usage. This may involve tuning SQL queries or adjusting application logic.
  Regular Maintenance: Implement regular maintenance tasks to clear unnecessary cache entries and optimize performance.
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as these may contain improvements or fixes related to cache management.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to cache management and performance tuning for specific guidance and best practices.
  Documentation: Refer to the official SAP documentation for detailed information on cache management and configuration settings.
  Performance Monitoring Tools: Utilize SAP performance monitoring tools to analyze system performance and identify bottlenecks related to cache usage.
  
  If the issue persists after taking these steps, it may be beneficial to consult with SAP support or your system administrator for further assistance.