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 : 17-08-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-01969 : You must specify RESETLOGS or NORESETLOGS
  • ora-12596 : TNS:internal inconsistency
  • ora-02336 : column attribute cannot be accessed
  • ora-02338 : missing or invalid column constraint specification
  • ora-16229 : PDML child string string string for parent string string string cannot be skipped.
  • ora-31498 : description and remove_description cannot both be specified
  • ora-13120 : invalid face_id [string]
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-19772 : change tracking file name exceeds limit of string characters
  • ora-28102 : policy does not exist
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-15081 : failed to submit an I/O operation to a disk
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-33468 : (ESDREAD13) Discarding compiled code for workspace object because number is no longer a surrogate of dimension workspace object.
  • ora-31439 : subscription is already active
  • ora-13215 : window object is out of range
  • ora-32335 : dimension must have at least one level
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-23539 : table "string"."string" currently being redefined
  • ora-16221 : history table synchronization error
  • ora-01653 : unable to extend table string.string by string in tablespace string
  • ora-29307 : datafile string error, string
  • ora-12872 : First slave parse gave different plan
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • ora-15103 : conflicting or duplicate REPAIR options
  • ora-16100 : not a valid Logical Standby database
  • ora-06144 : NETTCP: SID (database) is unavailable
  • ora-26665 : STREAMS process string already exists
  • 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.