How To Fix ESH_DB034 - The runtime load is currently being refreshed

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_DB - ES: Dashboard

• Message number: 034

• Message text: The runtime load is currently being refreshed

What causes this issue?

For one of many reasons, a new version of the runtime load is currently
built. Until this process is completed, all search requests are handled
based on the current version of the runtime load.

System Response

Search is operational.
As soon as the new version got built, new sessions will make use of it,
thus running on the potentially updated connectors.

How to fix this error?

No action required.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_DB034 - The runtime load is currently being refreshed ?

  The SAP error message ESH_DB034 ("The runtime load is currently being refreshed") typically occurs in the context of the SAP Enterprise Search (SAP ESH) when there is an ongoing refresh of the runtime load for the search index. This can happen during scheduled updates or when a manual refresh is initiated.
  Cause:
  
  Ongoing Refresh: The most common cause of this error is that a refresh of the search index is currently in progress. During this time, the system locks certain operations to ensure data consistency.
  Long-running Processes: If the refresh process takes longer than expected, it can lead to this error being displayed when users attempt to access the search functionality.
  System Configuration: Misconfiguration of the search system or issues with the underlying database can also lead to this error.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait for the ongoing refresh process to complete. You can check the status of the refresh in the SAP system.
  Monitor Background Jobs: Use transaction codes like SM37 to monitor background jobs related to the search index refresh. Look for jobs that are currently running and check their status.
  Check Logs: Review the logs for any errors or warnings that might indicate why the refresh is taking longer than expected. You can check the logs in transaction SLG1 for application logs related to the Enterprise Search.
  Manual Refresh: If the refresh seems to be stuck, you may need to manually trigger a refresh or restart the process. This can be done through the relevant transaction for managing the search index.
  System Configuration: Ensure that the system is properly configured for the search functionality. This includes checking settings related to the search index and database connections.
  Consult Documentation: Refer to SAP documentation or notes related to Enterprise Search for any specific recommendations or troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as EHS_SEARCH for managing search settings and EHS_INDEX for index management.
  SAP Notes: Check for any SAP Notes that might address known issues or provide patches related to the ESH functionality.
  Performance Tuning: If refreshes are frequently taking too long, consider performance tuning of the database or the search configuration to improve efficiency.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.