ORA-16660: FSFO operation attempted in absence of a broker configuration

Cause : An attempt was made to enable or disable Fast-Start Failover 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 broker client commands.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

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's DMON process from the primary's DMON process. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) You may use the FORCE option to override Fast-Start Failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that FSFO is not formally disabled in the broker configuration. The effect 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 at a later point in time and if the state of Fast-Start Failover had been altered at the primary database in the meantime.

update : 28-06-2017

ORA-16660 - FSFO operation attempted in absence of a broker configuration
ORA-16660 - FSFO operation attempted in absence of a broker configuration

  • ora-13251 : duplicate entry string in metadata table
  • ora-13461 : the interleaving type is not supported
  • ora-02754 : osnfsmmap: cannot change shared memory inheritence
  • ora-12436 : no policy options specified
  • ora-29540 : class string does not exist
  • ora-00071 : process number must be between 1 and string
  • ora-29378 : invalid consumer group mapping priorities
  • ora-19201 : Datatype not supported
  • ora-27084 : unable to get/set file status flags
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-01030 : SELECT ... INTO variable does not exist
  • ora-38477 : attribute set cannot be derived from an evolved type or a subtype.
  • ora-04062 : %s of string has been changed
  • ora-01636 : rollback segment 'string' is already online
  • ora-40103 : invalid case-id column: string
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-09719 : osncui: invalid handle.
  • ora-32593 : database supplemental logging attributes in flux
  • ora-16104 : invalid Logical Standby option requested
  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-06306 : IPA: Message write length error
  • ora-08235 : smsget: listener not on this node
  • ora-28535 : invalid Heterogeneous Services context
  • ora-31456 : error executing a procedure in the DBMS_CDC_UTILITY package
  • ora-22150 : variable-length array has not been initialized
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-37086 : %s is not a valueset
  • ora-01353 : existing Logminer session
  • ora-12504 : TNS:listener was not given the SID in CONNECT_DATA
  • ora-01285 : error reading file string
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.