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 : 27-06-2017
ORA-16651

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

  • ora-01925 : maximum of string enabled roles exceeded
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-14603 : [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
  • ora-01320 : Invalid Logminer dictionar attribute
  • ora-23380 : propagation mode "string" is not valid
  • ora-12712 : new character set must be a superset of old character set
  • ora-07410 : slpdtb: number too large for supplied buffer.
  • ora-21601 : attribute is not an object
  • ora-01942 : IDENTIFIED BY and EXTERNALLY cannot both be specified
  • ora-31470 : asynchronous change tables must contain the RSID$ column
  • ora-13907 : Threshold value is invalid.
  • ora-13202 : failed to create or insert into the SDO_INDEX_METADATA table
  • ora-12234 : TNS:Redirect to destination
  • ora-28104 : input value for string is not valid
  • ora-15028 : ASM file 'string' not dropped; currently being accessed
  • ora-13417 : null or invalid layerNumber parameter
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-32303 : mviews with user-defined types cannot reference multiple master sites
  • ora-32611 : incorrect use of MODEL CV operator
  • ora-12400 : invalid argument to facility error handling
  • ora-00097 : use of Oracle SQL feature not in SQL92 string Level
  • ora-29933 : object being disassociated has some user defined statistics stored
  • ora-19201 : Datatype not supported
  • ora-07218 : slkhst: could not perform host operation
  • ora-01135 : file string accessed for DML/query is offline
  • ora-24395 : cannot reinitialize non-existent pool
  • ora-38422 : invalid datatype for the attribute: string
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-26053 : Row was not loaded due to conversion error.
  • 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.