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":
Was this topic helpful?
16 June 2018