How To Fix /STMC/CR_MSG847 - Create text search index

SAP Error Message - Details

• Message type: E = Error

• Message class: /STMC/CR_MSG -

• Message number: 847

• Message text: Create text search index

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 /STMC/CR_MSG847 - Create text search index ?

  The SAP error message /STMC/CR_MSG847 typically relates to issues encountered when trying to create a text search index in the SAP system. This error can arise due to various reasons, and understanding the cause is crucial for finding an appropriate solution.
  Cause
  
  Missing Configuration: The text search index may not be properly configured in the system.
  Database Issues: There could be issues with the underlying database, such as connectivity problems or insufficient permissions.
  Insufficient Authorizations: The user attempting to create the index may not have the necessary authorizations.
  Data Issues: There may be inconsistencies or issues with the data that is being indexed.
  System Performance: The system may be under heavy load, causing timeouts or failures during the index creation process.
  
  Solution
  
  
  Check Configuration: Ensure that the text search configuration is correctly set up in the SAP system. This includes verifying the settings in transaction codes like SE11 (Data Dictionary) and SE78 (SAP ArchiveLink).
  
  
  Review Authorizations: Make sure that the user has the necessary authorizations to create text search indexes. This can be checked in transaction SU53 or by consulting with your security team.
  
  
  Database Connectivity: Verify that the database is up and running and that there are no connectivity issues. Check the database logs for any errors.
  
  
  Data Consistency: Review the data that is being indexed for any inconsistencies or errors. You may need to clean or correct the data before attempting to create the index again.
  
  
  System Performance: If the system is under heavy load, consider scheduling the index creation during off-peak hours or optimizing the system performance.
  
  
  Check Logs: Review the application logs (transaction SLG1) and system logs (transaction SM21) for any additional error messages or warnings that could provide more context about the issue.
  
  
  Recreate the Index: If the index creation failed, you may need to delete any partially created indexes and attempt to recreate them.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates available that resolve known issues.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11, SE78, SLG1, and SM21 for troubleshooting.
  SAP Documentation: Refer to the official SAP documentation for detailed information on text search and indexing.
  SAP Community: Engage with the SAP Community forums for insights and solutions shared by other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.