How To Fix RS_DB_DB6601 - Aggregate &1: F and E fact tables in the same database partition group

SAP Error Message - Details

• Message type: E = Error

• Message class: RS_DB_DB6 - DB6-Specific Messages in SAP BW

• Message number: 601

• Message text: Aggregate &1: F and E fact tables in the same database partition group

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 RS_DB_DB6601 - Aggregate &1: F and E fact tables in the same database partition group ?

  The SAP error message RS_DB_DB6601 indicates that there is a configuration issue with the database partition group for an aggregate in SAP BW (Business Warehouse). Specifically, it points out that both F (fact) and E (event) tables are present in the same database partition group, which is not allowed.
  Cause:
  In SAP BW, fact tables (F tables) and event tables (E tables) should be stored in separate database partition groups. This is because they have different characteristics and usage patterns, and mixing them can lead to performance issues and inconsistencies in data processing.
  Solution:
  To resolve this error, you need to ensure that the F and E tables are assigned to different database partition groups. Here are the steps you can take:
  
  
  Identify the Tables: Determine which F and E tables are causing the issue. You can do this by checking the aggregate definition and the associated database partition groups.
  
  
  Reassign Tables: 
  
  If you have access to the Data Warehousing Workbench (transaction RSA1), navigate to the InfoProvider that contains the aggregate.
  Check the settings for the database partition group.
  If necessary, create a new database partition group for either the F or E tables, ensuring that they are separated.
  
  
  
  Adjust Aggregates: After reassigning the tables, you may need to adjust the aggregates to ensure they are correctly defined and do not reference both F and E tables in the same partition group.
  
  
  Rebuild Aggregates: Once the tables are correctly assigned, you may need to rebuild the aggregates to ensure that they are functioning correctly without the error.
  
  
  Test: After making the changes, test the aggregates to ensure that they are working as expected and that the error message no longer appears.
  
  
  Related Information:
  
  Database Partition Groups: These are used in SAP BW to optimize the performance of queries and data loading by separating different types of data.
  Fact Tables: These tables store quantitative data for analysis and are typically large in size.
  Event Tables: These tables store data related to specific events or transactions and are often used for detailed reporting.
  
  Additional Considerations:
  
  Always back up your data and configurations before making changes to the database partition groups.
  Consult SAP documentation or support if you are unsure about the changes or if the issue persists after following the above steps.
  Consider performance implications when designing your data model and partitioning strategy in SAP BW.