Do you have any question about this error?
Message type: E = Error
Message class: DT - Table activation (incl. indexes)
Message number: 547
Message text: Index &-& is of type Full Text; table must be in Column Store
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.
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.
DT547
- Index &-& is of type Full Text; table must be in Column Store ?The SAP error message DT547 indicates that there is an issue with the data structure of a table that is being used in a query or operation. Specifically, it states that the index you are trying to use is of type "Full Text," but the table must be in "Column Store" format. This typically occurs in the context of SAP HANA, which supports both row and column store tables.
Cause:
- Table Type Mismatch: The error arises when a full-text index is created on a table that is not in column store format. Full-text indexes are only supported on column store tables in SAP HANA.
- Incorrect Table Definition: The table may have been defined as a row store table, which does not support full-text indexing.
- Query or Operation: The query or operation you are trying to perform is attempting to access a full-text index on a table that is not compatible.
Solution:
Check Table Definition: Verify the definition of the table in question. You can do this by checking the table properties in the SAP HANA Studio or using SQL commands to inspect the table structure.
SELECT * FROM M_TABLES WHERE TABLE_NAME = 'your_table_name';
Convert Table to Column Store: If the table is indeed a row store and you need to use full-text indexing, you will need to convert the table to a column store. This can be done using the following SQL command:
ALTER TABLE your_table_name SET (TABLE_TYPE = 'COLUMN');
Note: Converting a table from row store to column store may require data migration and could have implications on performance and storage.
Recreate the Index: After ensuring that the table is in column store format, you may need to recreate the full-text index.
CREATE FULLTEXT INDEX your_index_name ON your_table_name (your_column_name);
Review Documentation: Consult the SAP HANA documentation for more details on full-text indexing and table types to ensure compliance with best practices.
Related Information:
By following these steps, you should be able to resolve the DT547 error and successfully utilize full-text indexing in your SAP HANA environment.
Get instant SAP help. Start your 7-day free trial now.
DT546
Index &-& is not in a namespace for partners
What causes this issue? The R/3 System is configured as a partner system. Index names for partner developments should begin with J.System Response T...
DT545
Index &-& is in a namespace for partner developments
What causes this issue? An index was created for a table in the partner namespace. This namespace should only be used in development systems of SAP p...
DT548
Index &-& is of type Full Text. This is supported on: &
What causes this issue? You have defined a Full Text Index. However, this kind of index is not supported on all databases.System Response The index ...
DT549
Check exception list for index &-&
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.