How To Fix RSDD_ZA070 - Restart preprocessor

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD_ZA - Messages from TREX Aggregate Area

• Message number: 070

• Message text: Restart preprocessor

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 RSDD_ZA070 - Restart preprocessor ?

  The SAP error message RSDD_ZA070, which indicates "Restart preprocessor," typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with the data loading process or the data extraction process. This error can arise due to various reasons, including system resource issues, data inconsistencies, or configuration problems.
  Causes:
  
  System Resource Issues: Insufficient memory or CPU resources can lead to the preprocessor failing to execute properly.
  Data Inconsistencies: Issues with the data being loaded, such as missing or corrupt records, can cause the preprocessor to fail.
  Configuration Problems: Incorrect settings in the InfoPackage or data source configuration can lead to this error.
  Locks: If there are locks on the data or objects being processed, it can prevent the preprocessor from completing its task.
  Network Issues: Problems with network connectivity can interrupt the data loading process.
  
  Solutions:
  
  Check System Resources: Monitor the system's memory and CPU usage. If resources are low, consider optimizing the system or scheduling the data load during off-peak hours.
  Review Data: Check the data being loaded for any inconsistencies or errors. Ensure that the data source is correctly configured and that there are no missing or corrupt records.
  Reconfigure InfoPackage: Review the settings in the InfoPackage and ensure that all configurations are correct. You may need to adjust the settings or re-create the InfoPackage.
  Release Locks: Use transaction codes like SM12 to check for and release any locks that may be affecting the data loading process.
  Restart the Process: Sometimes, simply restarting the data load process can resolve transient issues. You can do this by re-running the InfoPackage.
  Check Logs: Review the application logs (transaction SLG1) for more detailed error messages that can provide insights into the specific cause of the failure.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), SLG1 (Application Log), and SM37 (Job Monitoring) to help diagnose and resolve issues.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to data loading and the preprocessor for best practices and configuration guidelines.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation and support.