Database Error Messages

The primary database could not be opened because one of the following reasons. A fast-start failover has occurred, and there was another primary. Data Guard had detected a possible fast-start failover but could not contact the observer or target standby to verify. The database was configured for maximum protection and no standby database was available to support the protection mode.

Check if a failover did occur. If it did, reinstate the database. If the failover did not occur and fast-start failover is enabled, ensure that connectivity exists between the primary database and either the observer or the target standby database, then retry opening the database.

An attempt to open the primary database was made either after a failover occurred or was likely to have occurred due to the fast-start failover feature processing, or the configuration was in maximum protection mode and a standby database was not available to support the mode.

Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between the primary database and either the observer or the target standby database. Then, try opening the database again. If it is in maximum protection mode, the database is opened by Data Guard broker when a standby database that supports the mode becomes available.

An attempt to open the primary database was made either after a failover occurred, or when it was likely to have occurred as the result of the primary being isolated from the fast-start failover target standby database and from the fast-start failover observer.

Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between the primary database and either the observer or the target standby database. Then, try opening the database again.