How To Fix RSDU_REPART736 - Reclustering request for InfoCube &1 was reset

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDU_REPART - Messages for Repartitioning InfoProviders

• Message number: 736

• Message text: Reclustering request for InfoCube &1 was reset

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 RSDU_REPART736 - Reclustering request for InfoCube &1 was reset ?

  The SAP error message RSDU_REPART736 indicates that a reclustering request for an InfoCube has been reset. This typically occurs during the process of data loading or when managing the data in the InfoCube. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Data Load Issues: The reclustering process may have encountered issues during data loading, such as data inconsistencies or errors in the data source.
  Locking Issues: If another process is locking the InfoCube or if there are concurrent requests that interfere with the reclustering process, it can lead to a reset.
  System Performance: High system load or performance issues can cause the reclustering process to fail or be reset.
  Configuration Issues: Incorrect settings in the InfoCube or the data model can lead to problems during the reclustering process.
  
  Solution:
  
  Check Logs: Review the application logs (transaction SLG1) for more detailed error messages that can provide insights into why the reclustering was reset.
  Monitor Data Load: Ensure that there are no ongoing data load processes that might be conflicting with the reclustering. You can check the status of data loads in the Data Warehousing Workbench (transaction RSA1).
  Re-run the Process: If the issue was transient, you can try to re-run the reclustering process. This can be done through the transaction code RSA1 or by using the appropriate process chain.
  Check for Locks: Use transaction SM12 to check for any locks on the InfoCube that might be preventing the reclustering from completing.
  System Performance: Monitor system performance and resource utilization. If the system is under heavy load, consider scheduling the reclustering during off-peak hours.
  Data Consistency: Ensure that the data being loaded into the InfoCube is consistent and adheres to the defined data model. Validate the data sources and transformations.
  Configuration Review: Review the configuration of the InfoCube and ensure that all settings are correct. This includes checking the InfoCube structure and any related transformations.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), SLG1 (Application Log), and SM12 (Lock Entries).
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to reclustering or InfoCube management.
  Documentation: Review SAP documentation on InfoCubes and data loading processes for best practices and troubleshooting tips.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation and support.