How to recover from tablespace errors on an HADR Standby database
In an HADR environment, when a Standby database has a tablespace in an invalid or error state, the replay of transactions on this tablespace will stop, while the replay of transactions on other valid tablespaces will continue. The Primary database will not be affected, and the condition of this tablespace on the Standby may go unnoticed.
If this tablespace condition exists on the Standby database, then sometime later when a TAKEOVER operation is performed on the Standby database, applications may be impacted by the unavailability of this tablespace.
The erroneous tablespaces can be recovered on the Standby database by either reinitializing the affected tablespaces, or the entire database.
Resolving the problem
The content of this technote has been transplanted into the Knowledge Center. Please see "How to recover from tablespace errors on an HADR standby database":
Recovering from table space errors on an HADR standby
Developerworks article "DB2 Basics: Demystifying table
Monitoring and Identifying tablespaces in invalid or er
Initializing high availability disaster recovery (HADR)
More support for:
DB2 for Linux, UNIX and Windows
High Availability - HADR
Software version: 9.7, 10.1, 10.5, 11.1
Operating system(s): AIX, Linux, Windows
Software edition: Advanced Enterprise Server, Advanced Workgroup Server, Enterprise Server, Express, Express-C, Personal, Workgroup Server
Reference #: 1993389
Modified date: 30 June 2017
Translate this page: