Database Error Messages

The attempt to enable fast-start failover could not be completed because one or more requirements were not met:

• The effective redo transport mode 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 was set to MaxAvailability mode.
• The effective redo transport mode for both the primary database and the fast-start failover target standby database must be set to either SYNC if the configuration protection mode was set to MaxProtection mode.
• The effective redo transport mode for both the primary database and the fast-start failover target standby database must be set to ASYNC if the configuration protection mode was set to MaxPerformance mode.
• 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 existed in the Oracle Data Guard configuration.
• fast-start failover target standby database did not receive redo data directly from the primary database when the protection mode was set to MaxPerformance.
• The primary database has multiple routes to the fast-start failover target standby database.
• Logical standby databases could not be the fast-start failover targets because the configuration protection mode was set to MaxProtection.

Retry the command after correcting the issue:

• Ensure that the effective redo transport mode for both the primary database and the fast-start failover target standby database are either SYNC or FASTSYNC if the configuration protection mode is set to MaxProtection or 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 the RedoRoutes property of the primary includes the name of the fast-start failover target standby database when the protection mode is set to MaxPerformance.
• Ensure the RedoRoutes property of the primary database has only one route to the fast-start failover target standby database.

The attempt to enable fast-start failover could not be completed because one or more requirements were not met:

• The effective redo transport mode 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 MaxProtection or MaxAvailability mode.
• The effective redo transport mode 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.
• 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 when the protection mode was set to MaxPerformance mode.
• The primary database has multiple routes to the fast-start failover target standby database.
• Logical standby databases could not be the fast-start failover targets because the configuration protection mode was set to MaxProtection mode.

Retry the command after correcting the issue:

• Ensure that the effective redo transport mode for both the primary database and the fast-start failover target standby database are either SYNC or FASTSYNC if the configuration protection mode is set to MaxProtection or MaxAvailability mode.
• 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 mode.
• Ensure the RedoRoutes property of the primary includes the name of the fast-start failover target standby database when the protection mode is set to maximum performance mode.
• Ensure the RedoRoutes property of the primary database has only one route to the fast-start failover target standby database.

The attempt to enable fast-start failover could not be completed because one or more requirements were not met:

• The effective redo transport mode 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 MaxProtection or MaxAvailability mode.
• The effective redo transport mode 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.
• 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 when the protection mode was set to MaxPerformance mode.
• The primary database has multiple routes to the fast-start failover target standby database.
• Logical standby databases could not be the fast-start failover targets because the configuration protection mode was set to MaxProtection mode.

Retry the command after correcting the issue:

• Ensure that the effective redo transport mode for both the primary database and the fast-start failover target standby database are either SYNC or FASTSYNC if the configuration protection mode is set to MaxProtection or MaxAvailability mode.
• 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 mode.
• Ensure the RedoRoutes property of the primary includes the name of the fast-start failover target standby database when the protection mode is set to maximum performance mode.
• Ensure the RedoRoutes property of the primary database has only one route to the fast-start failover target standby database.