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 : 25-04-2017
ORA-16660

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

  • ora-13787 : missing SQL profile for statement object "string" for tuning task "string"
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-30489 : Cannot have more than one rollup/cube expression list
  • ora-19335 : Invalid format type object
  • ora-14155 : missing PARTITION or SUBPARTITION keyword
  • ora-30959 : The indexed column is not stored in CLOB.
  • ora-01487 : packed decimal number too large for supplied buffer
  • ora-02364 : error writing to file: string
  • ora-12737 : Instant Client Light: unsupported server character set string
  • ora-25003 : cannot change NEW values for this column type in trigger
  • ora-22805 : cannot insert NULL object into object tables or nested tables
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-12734 : Instant Client Light: unsupported client national character set string
  • ora-28350 : cannot encrypt the specified column recorded in CDC synchronized change table
  • ora-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • ora-01900 : LOGFILE keyword expected
  • ora-07266 : sppst: invalid process number passed to sppst.
  • ora-27091 : unable to queue I/O
  • ora-16727 : resource guard cannot close database
  • ora-29905 : method string does not exist in type string.string
  • ora-38104 : Columns referenced in the ON Clause cannot be updated: string
  • ora-07269 : spdcr: detached process died after exec.
  • ora-25507 : resource manager has not been continuously on
  • ora-09205 : sfqio: error reading or writing to disk
  • ora-16954 : SQL parse error.
  • ora-01411 : cannot store the length of column in the indicator
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-25440 : invalid table alias: string
  • ora-16751 : resource guard encountered errors in switchover to primary database
  • 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.