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 : 23-06-2017

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

  • ora-10704 : Print out information about what enqueues are being obtained
  • ora-01987 : client os username is too long
  • ora-12468 : max write level does not equal max read level
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-13842 : no SELECT privilege on DBA_SQL_PROFILES
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-38956 : Target platform string not cross platform compliant
  • ora-00976 : LEVEL, PRIOR, or ROWNUM not allowed here
  • ora-01172 : recovery of thread string stuck at block string of file string
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-16511 : messaging error using ksrget
  • ora-12502 : TNS:listener received no CONNECT_DATA from client
  • ora-16757 : resource guard could not get property
  • ora-31029 : Cannot bind to unsaved resource
  • ora-12046 : cannot use trusted constraints for refreshing remote MV
  • ora-15113 : alias name 'string' refers to a directory
  • ora-19102 : XQuery string literal expected
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-19117 : invalid redefinition of predefined namespace prefix 'string'
  • ora-19695 : fixed table x$krbmsft has not been populated
  • ora-24372 : invalid object for describe
  • ora-19721 : Cannot find datafile with absolute file number string in tablespace string
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-02423 : schema name does not match schema authorization identifier
  • ora-33458 : (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.
  • ora-21709 : cannot refresh an object that has been modified
  • ora-24044 : source string and destination string object types do not match
  • ora-15202 : cannot create additional ASM internal change segment
  • ora-01879 : the hh25 field must be between 0 and 24
  • 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.