How To Fix ESH_HANA_ADMIN228 - Cannot create full-text index on &1.&2 - attribute &3 does not exist

ESH_HANA_ADMIN228 - Overview

• Message type: E = Error

• Message class: ESH_HANA_ADMIN - ESH HANA Index Administration

• Message number: 228

• Message text: Cannot create full-text index on &1.&2 - attribute &3 does not exist

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_HANA_ADMIN228 - Cannot create full-text index on &1.&2 - attribute &3 does not exist ?

  The SAP error message ESH_HANA_ADMIN228 indicates that there is an issue with creating a full-text index in the SAP HANA database. Specifically, the error states that the attribute specified does not exist in the context of the entity you are trying to index. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause
  
  Non-Existent Attribute: The attribute specified in the error message does not exist in the data model or the table you are trying to create the full-text index on.
  Typographical Error: There may be a typo in the attribute name, leading to the system not recognizing it.
  Model Changes: The data model may have been changed (e.g., attributes added or removed) after the index was defined, leading to inconsistencies.
  Incorrect Configuration: The configuration for the full-text index may not be set up correctly, pointing to an attribute that is not part of the entity.
  
  Solution
  
  
  Verify Attribute Existence:
  
  Check the data model or the