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-04-2017
ORA-16651

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

  • ora-07474 : snclrd: close error, unable to close sgadef.dbf file.
  • ora-06578 : output parameter cannot be a duplicate bind
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-15131 : block string of file string in diskgroup string could not be read
  • ora-10614 : Operation not allowed on this segment
  • ora-26697 : LCR contains extra column 'string'
  • ora-10902 : disable seghdr conversion for ro operation
  • ora-04067 : not executed, string does not exist
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-12030 : cannot create a fast refresh materialized view
  • ora-33557 : (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-06114 : NETTCP: SID lookup failure
  • ora-02462 : Duplicate INDEX option specified
  • ora-09757 : osnipn: port allocation failure.
  • ora-30072 : invalid time zone value
  • ora-19772 : change tracking file name exceeds limit of string characters
  • ora-14552 : cannot perform a DDL, commit or rollback inside a query or DML
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-19501 : read error on file "string", blockno string (blocksize=string)
  • ora-02403 : plan table does not have correct format
  • ora-21601 : attribute is not an object
  • ora-19265 : XQ0045 - invalid or unknown prefix string in function declaration
  • ora-16626 : failed to enable specified object
  • ora-19574 : output filename must be specified
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-25307 : Enqueue rate too high, flow control enabled
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-02852 : Invalid critical-section time out value
  • ora-19239 : XP0019 - step expression must return sequence of nodes
  • 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.