ORA-16655: specified target standby database invalid

Cause : The attempted command was not allowed because Fast-Start Failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database.

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

Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, you may disable Fast-Start Failover. You may then retry the command while specifying the originally specified target standby database.

update : 29-04-2017
ORA-16655

ORA-16655 - specified target standby database invalid
ORA-16655 - specified target standby database invalid

  • ora-39301 : schema "string" does not exist or is in use
  • ora-21601 : attribute is not an object
  • ora-07671 : $IDTOASC failed translating an integrity category
  • ora-13139 : could not obtain column definition for string
  • ora-07500 : scglaa: $cantim unexpected return
  • ora-38488 : attribute set already assigned to the column storing expressions
  • ora-32578 : password for SYS already specified
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-16773 : error starting Redo Apply
  • ora-14044 : only one partition may be moved
  • ora-24068 : cannot start queue string, queue table string is being migrated
  • ora-31154 : invalid XML document
  • ora-06512 : at stringline string
  • ora-24080 : unschedule_propagation pending for QUEUE string and DESTINATION string
  • ora-13348 : polygon boundary is not closed
  • ora-23603 : STREAMS enqueue aborted due to low SGA
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-32581 : missing or invalid password
  • ora-32844 : exceeded maximum number of string values
  • ora-07243 : supplied buffer not big enough to hold entire line
  • ora-01182 : cannot create database file string - file is in use or recovery
  • ora-06954 : Illegal file name
  • ora-07709 : sksaprs: archiving to a remote host is not allowed
  • ora-27159 : failure setting process scheduling priority
  • ora-02827 : Invalid file number
  • ora-01337 : log file has a different compatibility version
  • ora-16256 : Failure to complete standby redo logfile archival after failover
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-01260 : warning: END BACKUP succeeded but some files found not to be in backup mode
  • 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.