How To Fix ESH_DB020 - There are erroneous Data Sources

ESH_DB020 - Overview

• Message type: E = Error

• Message class: ESH_DB - ES: Dashboard

• Message number: 020

• Message text: There are erroneous Data Sources

What causes this issue?

Some Data Sources have a status other than 'active' and 'inactive'. This
can be either be an intermediate status (like the former 'prepared for
indexing', or a real error that occurred during the activation process.

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?

Use the consistency check feature in the ES-Cockpit ('Actions' ->
'Consistency Check') to analyze and to repair the Data Sources in
question. Schedule indexing where this is relevant.
Alternatively, task list (transaction STC01) SAP_ESH_CONSISTENCY_CHECK
can be used for analyzing the issues (no implicit repair).

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 ESH_DB020 - There are erroneous Data Sources ?

  The SAP error message ESH_DB020, which indicates "There are erroneous Data Sources," typically arises in the context of the SAP Enterprise Search (SAP ESH) framework. This error suggests that there are issues with the data sources configured for the search application, which may prevent the search from functioning correctly.
  Causes:
  
  Invalid Data Source Configuration: The data source may be incorrectly configured or may point to a non-existent or inaccessible database.
  Connection Issues: There may be connectivity issues between the SAP system and the data source, such as network problems or incorrect credentials.
  Data Source Deletion: The data source might have been deleted or is no longer available in the system.
  Metadata Issues: There could be issues with the metadata of the data source, such as missing or incorrect definitions.
  Authorization Problems: The user may not have the necessary authorizations to access the data source.
  
  Solutions:
  
  
  Check Data Source Configuration:
  
  Go to the SAP ESH configuration and verify the settings