ORA-16651: requirements not met for enabling Fast-Start Failover

Cause : The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met: - The Data Guard configuration must be in MaxAvailability protection mode. - The LogXptMode property for both the primary database and the Fast-Start Failover target standby database must be SYNC. - The primary database and the Fast-Start Failover target standby database must both have flashback enabled. - No valid target standby database was specified in the primary database's FastStartFailoverTarget property prior to the attempt to enable Fast-Start Failover, and more than one standby database exists in the Data Guard configuration.

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

Retry the attempted command after correcting the issue: - Set the Data Guard configuration to MaxAvailability protection mode. - Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target standby database are SYNC. - Ensure that both the primary database and the Fast-Start Failover target standby database have flashback enabled. - Set the primary database's FastStartFailoverTarget property to the db_unique_name value of the desired target standby database add the desired target standby database's FastStartFailoverTarget property to the db_unique_name value of the primary database.

update : 25-05-2017
ORA-16651

ORA-16651 - requirements not met for enabling Fast-Start Failover
ORA-16651 - requirements not met for enabling Fast-Start Failover

  • ora-09836 : addCallback: could not add a port to the callback set.
  • ora-26507 : null master connection
  • ora-25231 : cannot dequeue because CONSUMER_NAME not specified
  • ora-16625 : cannot reach the database
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-23365 : site string does not exist
  • ora-15058 : disk 'string' belongs to an incompatible diskgroup
  • ora-22904 : invalid reference to a nested table column
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-19687 : SPFILE not found in backup set
  • ora-13485 : error occurred during compression or decompression: string
  • ora-02819 : Write failed
  • ora-29278 : SMTP transient error: string
  • ora-39024 : wrong schema specified for job
  • ora-39208 : Parameter string is invalid for string jobs.
  • ora-28558 : HS_FDS_CONNECT_STRING undefined for non-Oracle system
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-22627 : tc [string] must be that of object/varray/nested table
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-02183 : valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-30394 : source statement identical to the destination statement
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-00266 : name of archived log file needed
  • ora-15056 : additional error message
  • ora-32816 : foreign queue string is referenced by a subscriber or schedule
  • ora-39113 : Unable to determine database version
  • ora-07746 : slemrd: invalid error message file handle
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-28345 : cannot downgrade because there exists encrypted column
  • 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.