Code: ORA-16651
Description:
 requirements not met for enabling fast-start failover
Cause:
 The attempt to enable fast-start failover could not be completed because one or
more requirements were not met: - The Oracle 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 either SYNC or FASTSYNC 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 Oracle Data Guard
configuration. - fast-start failover target standby database did not receive redo data
directly from the primary database or from a far sync instance.
Action:
 The attempt to enable fast-start failover could not be completed because one or
more requirements were not met: - The Oracle 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 either SYNC or FASTSYNC 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 Oracle Data Guard
configuration. - fast-start failover target standby database did not receive redo data
directly from the primary database or from a far sync instance.