How To Fix RS_DB_DB6602 - Aggregate &1: F and E fact tables in different database partition groups

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 602

• Message text: Aggregate &1: F and E fact tables in different database partition groups

What causes this issue?

The F and E fact tables of an InfoCube aggregate must be in the same
database partition group; otherwise you will experience considerable
performance issues.

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?

Report an incident on component BW-SYS-DB-DB6.

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 RS_DB_DB6602 - Aggregate &1: F and E fact tables in different database partition groups ?

  The SAP error message RS_DB_DB6602 indicates that there is a mismatch between the fact tables (F and E) of an aggregate in different database partition groups. This typically occurs in the context of SAP BW (Business Warehouse) when dealing with aggregates and their underlying fact tables.
  Cause:
  The error arises when the fact tables that are part of an aggregate are stored in different database partition groups. In SAP BW, aggregates are used to improve query performance by pre-calculating and storing summarized data. However, for an aggregate to function correctly, all the fact tables that contribute to it must reside in the same database partition group. If they are in different groups, the system cannot access them simultaneously, leading to this error.
  Solution:
  To resolve the RS_DB_DB6602 error, you can follow these steps:
  
  
  Check Database Partition Groups:
  
  Identify the database partition groups for the fact tables involved in the aggregate. You can do this by checking the settings in the Data Warehousing Workbench (transaction RSA1) or using relevant BW transaction codes.
  
  
  
  Reassign Fact Tables:
  
  If the fact tables are indeed in different partition groups, you will need to reassign them to the same partition group. This may involve:
  
  Modifying the data model to ensure that all relevant fact tables are in the same partition group.
  Re-creating the aggregates if necessary.
  
  
  
  
  
  Rebuild the Aggregate:
  
  After ensuring that the fact tables are in the same partition group, you may need to rebuild the aggregate. This can be done by:
  
  Deleting the existing aggregate and creating a new one.
  Using the "Manage Aggregates" functionality in the Data Warehousing Workbench.
  
  
  
  
  
  Check for Data Consistency:
  
  After making changes, ensure that the data is consistent and that the aggregate is functioning as expected. You can run queries against the aggregate to verify that it returns the correct results.
  
  
  
  Consult Documentation:
  
  If you are unsure about the steps or the implications of changing partition groups, consult the SAP documentation or reach out to your SAP Basis or BW team for assistance.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might provide additional guidance or patches related to this error.
  Performance Considerations: Be aware that changing partition groups or rebuilding aggregates can have performance implications, so it’s advisable to perform these actions during off-peak hours.
  Backup: Always ensure that you have a backup of your data and configurations before making significant changes to the data model or aggregates.
  
  By following these steps, you should be able to resolve the RS_DB_DB6602 error and ensure that your aggregates function correctly within SAP BW.