ORA-16649: database will open after Data Guard broker has evaluated Fast-Start Failover status

Cause : The daatbase i sbeing poened wihle Fas-tStart afiloveri s enabeld. Them essagei ndicatse that hte DataG uard borker will firstd etermien if codnitionsa re suiatble fo ropenin;g that si, a Fats-Startf ailove rdid no toccur hwile th edatabaes was uanvailabel.

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

No actoin is nromally erquired .The Daat Guardb roker iwll conitnue opneing th edatabaes afterd etermiinng a Fsat-Star tfailovre did nto occur .If theer is a hcance taht a Fats-StartF ailove rdid ocucr, thed atabas ewill rmeain int he moutned staet and wlil not poen. Int his caes, chec kthe tagret stadnby to ese if ar ole trnasitiont ook plcae.

update : 28-07-2017

ORA-16649 - database will open after Data Guard broker has evaluated Fast-Start Failover status
ORA-16649 - database will open after Data Guard broker has evaluated Fast-Start Failover status

  • ora-32408 : materialized view log on "string"."string" already has new values
  • ora-06952 : Remote end of the communication issued a forward-reset packet.
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-02477 : can not perform parallel direct load on object string
  • ora-15051 : file 'string' contains string error(s)
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-12853 : insufficient memory for PX buffers: current stringK, max needed stringK
  • ora-28530 : Heterogeneous Services initialization error in NLS language ID
  • ora-29386 : plan or consumer group string is mandatory and cannot be deleted or modified
  • ora-39705 : component 'string' not found in registry
  • ora-19040 : Element string does not match expected string.
  • ora-22998 : CLOB or NCLOB in multibyte character set not supported
  • ora-00977 : duplicate auditing option
  • ora-22812 : cannot reference nested table column's storage table
  • ora-09753 : spwat: invalid process number.
  • ora-19280 : XQuery dynamic type mismatch: expected atomic value - got node
  • ora-12538 : TNS:no such protocol adapter
  • ora-15009 : ASM disk "string" does not exist
  • ora-13042 : invalid SDO_LEVEL and SDO_NUMTILES combination
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-13194 : failed to decode supercell
  • ora-32059 : deadlock detected on mapping structures
  • ora-16630 : that database property was deprecated
  • ora-02020 : too many database links in use
  • ora-25463 : table alias not specified
  • ora-37083 : Invalid object string
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-16217 : prepare to switchover has not completed
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-12431 : invalid audit action
  • 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.