How To Fix RSD_TREX060 - Indexing for InfoCube '&1' restarted

SAP Error Message - Details

• Message type: E = Error

• Message class: RSD_TREX - Messages from TREX Aggregate Area

• Message number: 060

• Message text: Indexing for InfoCube '&1' restarted

What causes this issue?

A previous indexing job terminated or was terminated. The new job starts
at the location where the old job terminated or runs up to the data that
was saved with COMMIT. It might be necessary to perform a rollback in
order to delete data that was not commited. The rollback can take some
time for large data packages.
If the indexing job terminated when filling the fact index (E and F
tables) and a compression job ran for this InfoCube in the meantime, you
might get incorrect data.

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?

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 RSD_TREX060 - Indexing for InfoCube '&1' restarted ?

  The SAP error message RSD_TREX060 indicates that the indexing process for an InfoCube has been restarted. This can occur for various reasons, and understanding the cause and potential solutions is essential for resolving the issue.
  Causes:
  
  System Resource Issues: Insufficient memory or CPU resources can lead to the indexing process being interrupted and restarted.
  Database Locking: If there are locks on the database tables that the indexing process needs to access, it may cause the process to restart.
  Network Issues: Network interruptions between the SAP system and the TREX (Text Retrieval and Extraction) server can lead to indexing failures.
  Configuration Issues: Incorrect configuration settings for the InfoCube or TREX can lead to problems during the indexing process.
  Data Volume: Large volumes of data being indexed can sometimes cause timeouts or resource exhaustion.
  
  Solutions:
  
  Check System Resources: Monitor the system's CPU and memory usage. If resources are low, consider increasing them or optimizing other processes.
  Review Locks: Use transaction codes like SM12 to check for any locks on the database tables related to the InfoCube. If locks are found, investigate and resolve them.
  Network Stability: Ensure that the network connection between the SAP system and the TREX server is stable. Check for any network issues or interruptions.
  Configuration Review: Verify the configuration settings for the InfoCube and TREX. Ensure that they are set up correctly and according to best practices.
  Data Volume Management: If the data volume is too large, consider breaking it down into smaller batches for indexing or optimizing the data model to reduce the volume.
  Check Logs: Review the logs for more detailed error messages that can provide insights into why the indexing was restarted. You can check the TREX logs and the SAP application logs (transaction SLG1).
  Re-indexing: If the issue persists, you may need to manually trigger a re-indexing of the InfoCube. This can be done through the Data Warehousing Workbench (transaction RSA1).
  
  Related Information:
  
  TREX Documentation: Refer to the official SAP documentation for TREX for detailed information on configuration and troubleshooting.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address specific issues related to the RSD_TREX060 error.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can provide insights or solutions.
  
  By following these steps, you should be able to identify the cause of the RSD_TREX060 error and implement a suitable solution.