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 : 24-05-2017

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

  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-23494 : too many rows for destination "string"
  • ora-16520 : unable to allocate resource id
  • ora-02076 : sequence not co-located with updated table or long column
  • ora-00200 : control file could not be created
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-36910 : (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy.
  • ora-19577 : file string is MISSING
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-13843 : no SQL profile with name like "string" exists for category like "string"
  • ora-02235 : this table logs changes to another table already
  • ora-26514 : object 'string.string' not found
  • ora-13108 : spatial table string not found
  • ora-28339 : missing or invalid encryption algorithm
  • ora-37151 : MDX parser initialization error
  • ora-13303 : failure to retrieve a geometry object from a table
  • ora-00089 : invalid instance number in ORADEBUG command
  • ora-16191 : Primary log shipping client not logged on standby
  • ora-06953 : Not enough virtual memory
  • ora-16056 : backup control file archival requires proper syntax
  • ora-00277 : illegal option to the UNTIL recovery flag string
  • ora-23352 : duplicate destination for deferred transaction
  • ora-27488 : unable to set string because string was/were already set
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-13909 : Invalid combination of threshold value and operator.
  • ora-28539 : gateway does not support result sets
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "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.