How To Fix DB6PM437 - Incremental backups are used, adding a new tablespace will discard them

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring

• Message number: 437

• Message text: Incremental backups are used, adding a new tablespace will discard them

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 DB6PM437 - Incremental backups are used, adding a new tablespace will discard them ?

  The SAP error message DB6PM437 indicates that you are attempting to add a new tablespace while incremental backups are in use. This situation can lead to the loss of the incremental backups because the database management system (DBMS) may not be able to properly track changes across the new tablespace.
  Cause:
  The error occurs because:
  
  Incremental backups rely on the state of the database at the time of the backup. When a new tablespace is added, it can disrupt the backup chain, making it impossible to restore the database to a point in time that includes the new tablespace without losing the incremental backups.
  The database system may not support incremental backups with the addition of new tablespaces, leading to potential data inconsistency.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Complete Full Backup: Before adding a new tablespace, perform a full backup of the database. This will ensure that you have a complete and consistent state of the database, including all existing tablespaces.
  
  
  Stop Incremental Backups: If you are currently running incremental backups, consider pausing or stopping them until after the new tablespace has been added and a new full backup has been taken.
  
  
  Add the New Tablespace: Once you have completed the full backup, you can proceed to add the new tablespace without risking the integrity of your incremental backups.
  
  
  Re-establish Incremental Backups: After adding the new tablespace and ensuring that everything is functioning correctly, you can resume your incremental backup strategy.
  
  
  Related Information:
  
  Backup Strategy: It's essential to have a well-defined backup strategy that includes full, differential, and incremental backups. Understanding how these types of backups interact with each other is crucial for maintaining data integrity.
  Database Documentation: Refer to the documentation for your specific database management system (e.g., Oracle, SQL Server, etc.) to understand how it handles tablespaces and backups.
  SAP Notes: Check SAP Notes and Knowledge Base Articles for any specific recommendations or updates related to this error message and your version of SAP.
  
  By following these steps, you should be able to resolve the error and maintain a consistent backup strategy.