Do you have any question about this error?
Message type: E = Error
Message class: ESH_DB - ES: Dashboard
Message number: 020
Message text: There are erroneous Data Sources
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.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
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).
Error message extract from SAP system. Copyright SAP SE.
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 for the data sources. Ensure that all required parameters are correctly set.
- Check if the data source is still valid and accessible.
Test Connectivity:
- Use transaction codes like
DBACOCKPIT
orSM59
to test the connection to the database or external system.- Ensure that the database is up and running and that there are no network issues.
Review Authorizations:
- Ensure that the user has the necessary authorizations to access the data sources. Check roles and permissions.
Check for Deletions:
- Verify if any data sources have been deleted or modified recently. If so, you may need to recreate or reconfigure them.
Update Metadata:
- If there are issues with the metadata, you may need to refresh or update the metadata for the data sources. This can often be done through the ESH administration tools.
Consult Logs:
- Check the application logs (transaction SLG1) for more detailed error messages that can provide additional context about the issue.
Re-indexing:
- If the data sources are valid but still causing issues, consider re-indexing the search index to ensure that all data is correctly indexed.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
ESH_DB019
Personalization is switched off
What causes this issue? The personalization features of Enterprise Search are switched off.System Response This is not a problem, Enterprise Search ...
ESH_DB018
Query logging is switched off
What causes this issue? The anonymized query logging has been switched off.System Response This is not a problem, Enterprise Search works. But switc...
ESH_DB021
Consolidation after system-/ client-copy missing
What causes this issue? The current client was created via system- or client-copy. Enterprise Search content was copied along with the origin, but ha...
ESH_DB022
ODP-mode set, no Enterprise Search possible
What causes this issue? The Enterprise Search connection is set to 'NO TREX'.System Response This setting allows only for running ODPs, ba...
Click on this link to search all SAP messages.