ORA-16660: fast-start failover operation attempted in absence

admin

ORA-16660: fast-startfailover operation attempted in absence of a broker
configuration
Cause: An attempt was made to enable or disable fast-startfailover when
connected to a standby database for which broker configuration details are
currently unavailable. For instance, the standby database may currently require
re-creation (or flashback reinstantiation) before it may respond to brokerclient
commands.
Action: 1)An attempt to enable or disable (non-FORCE) fast-start failover at this
standby database will be rejected until such time that the broker configuration
details have been made available to that standby database from the primary
database. This normally occurs when the standby database is successfully
re-created or flashed back, and then reenabled at the primary database. 2) Usethe
FORCE option to override fast-start failover that has been enabled at thestandby
database even when the broker configuration details are currently unavailableto
the standby database. In this case, this status message is only a warning. Notethat
fast-start failover is not formally disabled in the broker configuration. Theeffect of
this command issued under these circumstances may or may not be permanent,
depending upon when the primary and standby databases regain full
communication between each other and if the state of fast-start failover hasbeen
altered at the primary database in the meantime.