标题: ORA-16651: requirements not met for enabling fast-start failover [打印本页] 作者: admin 时间: 2016-8-29 10:46 标题: ORA-16651: requirements not met for enabling fast-start failover ORA-16651:requirements not met for enabling fast-start failover Cause: The attempt to enable fast-start failover could not becompleted 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-startfailover,
and more than one standby database exists in the Data Guard configuration. Action: Retrythe 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 theconfiguration
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 theconfiguration
protection mode is set to MaxPerformance.
- Ensure that both the primary database and the fast-start failover targetstandby
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 targetstandby
database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of
the primary database.