How To Fix /IWFND/MED036 - Metadata cache (shared memory) was cleaned up by user '&1'

SAP Error Message - Details

• Message type: E = Error

• Message class: /IWFND/MED -

• Message number: 036

• Message text: Metadata cache (shared memory) was cleaned up by user '&1'

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 /IWFND/MED036 - Metadata cache (shared memory) was cleaned up by user '&1' ?

  The SAP error message /IWFND/MED036 Metadata cache (shared memory) was cleaned up by user '&1' typically indicates that the metadata cache used by the SAP Gateway has been cleared or invalidated by a user. This can happen for various reasons, and understanding the cause and potential solutions can help in managing this error effectively.
  Cause:
  
  Manual Cleanup: A user with the necessary authorizations has manually cleared the metadata cache. This can be done through transaction codes like /IWFND/CACHE or through specific administrative actions.
  System Maintenance: Regular system maintenance or updates may involve clearing the cache to ensure that the latest metadata is loaded.
  Configuration Changes: Changes in the configuration of OData services or the underlying data model can trigger a cache invalidation.
  Performance Optimization: Sometimes, cache clearing is performed as a part of performance optimization efforts to ensure that the system is using the most current data.
  
  Solution:
  
  Repopulate the Cache: After the cache has been cleared, the system will automatically repopulate the cache as requests for metadata are made. Users may need to wait for the cache to be rebuilt or may need to trigger specific actions that require metadata.
  Check User Actions: If the cache was cleared unexpectedly, check the user logs to identify who performed the action and why. This can help in understanding if it was a necessary action or if it needs to be avoided in the future.
  Monitor Cache Usage: Use transaction /IWFND/CACHE to monitor the cache usage and performance. This can help in identifying patterns or issues related to cache clearing.
  Educate Users: If the cache is being cleared frequently by users, consider providing training or guidelines on when and how to clear the cache appropriately.
  Review System Configuration: Ensure that the system configuration is optimal and that any changes made to OData services are well-documented to avoid unnecessary cache clearing.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /IWFND/CACHE for cache management and /IWFND/MAINT_SERVICE for managing OData services.
  SAP Notes: Check SAP Notes for any known issues or updates related to metadata caching and OData services.
  Performance Monitoring: Regularly monitor the performance of your OData services and the metadata cache to ensure optimal operation.
  User Authorizations: Review user authorizations to ensure that only authorized personnel can clear the cache, preventing unintended disruptions.
  
  By understanding the cause and implementing the suggested solutions, you can effectively manage the /IWFND/MED036 error and maintain the performance of your SAP Gateway services.