How To Fix RSDA369 - Total size: &1 GByte; Number of rows &2; Compression: &3%

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 369

• Message text: Total size: &1 GByte; Number of rows &2; Compression: &3%

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 RSDA369 - Total size: &1 GByte; Number of rows &2; Compression: &3% ?

  The SAP error message RSDA369 typically relates to issues with data volume in a DataStore Object (DSO) or InfoProvider in SAP BW (Business Warehouse). This message indicates that the total size of the data is quite large, and it provides information about the number of rows and the compression percentage of the data.
  Cause:
  
  Large Data Volume: The error is triggered when the data volume exceeds certain thresholds, which can lead to performance issues during data processing or reporting.
  Inefficient Compression: The compression percentage indicates how well the data is compressed. A low compression percentage may suggest that the data is not being stored efficiently, leading to larger storage requirements.
  Data Model Design: Poorly designed data models or excessive data retention can contribute to large data sizes.
  
  Solution:
  
  Data Archiving: Consider archiving old or unnecessary data to reduce the size of the DSO or InfoProvider.
  Data Compression: Review the compression settings and ensure that data is being compressed effectively. You may need to adjust the settings or perform a manual compression.
  Data Model Optimization: Analyze the data model for inefficiencies. This may involve:
  
  Reducing the number of fields in the DSO.
  Implementing better data aggregation strategies.
  Using aggregate tables where appropriate.
  
  
  Partitioning: If applicable, consider partitioning large tables to improve performance and manageability.
  Monitoring and Maintenance: Regularly monitor data growth and perform maintenance tasks such as data cleansing and archiving to keep the data size manageable.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or patches related to this error.
  BW Administration: Familiarize yourself with BW administration tasks, including data loading, monitoring, and performance tuning.
  Performance Tuning: Look into performance tuning techniques for BW, such as optimizing queries and using aggregates effectively.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further analysis and support.