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


RSD_TREX060 - Overview

  • Message type: E = Error

  • Message class: RSD_TREX - Messages from TREX Aggregate Area

  • Message number: 060

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

  • Show details Hide details
  • 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

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author