Cause: The attempt to enable fast-start failover could not be completed because one or more requirements were not met:
- The Data Guard configuration must be in either MaxAvailability or MaxPerformance protection mode.
- The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to SYNC if the configuration protection mode is set to MaxAvailability mode.
- The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to ASYNC if the configuration protection mode is set to MaxPerformance mode.
- The primary database and the fast-start failover target standby database must both have flashback enabled.
- No valid target standby database was specified in the primary database FastStartFailoverTarget property prior to the attempt to enable fast-start failover, and more than one standby database exists in the Data Guard configuration.
Error solution: Retry the command after correcting the issue:
- Set the Data Guard configuration to either MaxAvailability or MaxPerformance protection mode.
- Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to SYNC if the configuration protection mode is set to MaxAvailability.
- Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to ASYNC if the configuration protection mode is set to MaxPerformance.
- Ensure that both the primary database and the fast-start failover target standby database have flashback enabled.
- Set the primary database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the desired target standby database and the desired target standby database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary database.
Database version: Oracle 11g Release 2 (11.2)