How To Fix ESH_EX101 - Indexing has been suspended globally

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_EX - Extraction

• Message number: 101

• Message text: Indexing has been suspended globally

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 ESH_EX101 - Indexing has been suspended globally ?

  The SAP error message ESH_EX101: Indexing has been suspended globally typically occurs in the context of the SAP Enterprise Search (SAP ESH) when the indexing process is halted due to various reasons. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  System Configuration Issues: There may be misconfigurations in the search system or the underlying database that prevent indexing from proceeding.
  Resource Limitations: Insufficient system resources (CPU, memory, disk space) can lead to the suspension of indexing.
  Errors in Indexing Jobs: Previous indexing jobs may have failed, causing the system to suspend further indexing operations.
  Locking Issues: If there are locks on the index tables or related objects, this can prevent indexing from occurring.
  Database Issues: Problems with the database, such as connectivity issues or corruption, can also lead to this error.
  
  Solutions:
  
  Check Indexing Status: Use transaction code /IWFND/ERROR_LOG or /IWFND/SEARCH to check the status of the indexing jobs and identify any errors.
  Review Logs: Look at the logs for any specific error messages that can provide more context on why indexing was suspended. You can check the logs in transaction SLG1 for the application log.
  Restart Indexing: If the issue is resolved, you can restart the indexing process. This can be done through the transaction /IWFND/SEARCH or /IWFND/INDEX.
  Check System Resources: Ensure that the system has adequate resources (CPU, memory, disk space) available. If necessary, allocate more resources or optimize existing usage.
  Clear Locks: If there are locks on the index tables, you may need to clear them. You can use transaction SM12 to check for and delete any unnecessary locks.
  Database Health Check: Perform a health check on the database to ensure it is functioning correctly. This may involve checking for connectivity issues or running database consistency checks.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches and updates.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for Enterprise Search for detailed information on configuration and troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Support Tickets: If the issue persists and cannot be resolved through the above steps, consider opening a support ticket with SAP for further assistance.
  
  By following these steps, you should be able to diagnose and resolve the ESH_EX101 error effectively.