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 : 25-09-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-02709 : osnpop: pipe creation failed
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-14251 : Specified subpartition does not exist
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • ora-29858 : error occurred in the execution of ODCIINDEXALTER routine
  • ora-30395 : dimension options require the COMPATIBLE parameter to be string or greater
  • ora-02271 : table does not have such constraint
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-19675 : file string was modified during proxy copy
  • ora-38711 : Corrupt flashback log block header: block string
  • ora-19262 : XQ0042 - namespace constructor not inside an element constructor
  • ora-08447 : syntax error in USAGE clause in mask options
  • ora-28347 : encryption properties mismatch
  • ora-13137 : failed to generate tablespace sequence number
  • ora-16250 : Failed to acquire starting scn of new log stream
  • ora-02724 : osnpbr: cannot send break message to orapop
  • ora-26698 : %s did not have a string rule set
  • ora-22303 : type "string"."string" not found
  • ora-29547 : Java system class not available: string
  • ora-00308 : cannot open archived log 'string'
  • ora-16412 : ONDEMAND archival requires active SQL apply operation
  • ora-13427 : invalid BLOB parameter for output
  • ora-30026 : Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
  • ora-13202 : failed to create or insert into the SDO_INDEX_METADATA table
  • ora-13251 : duplicate entry string in metadata table
  • ora-22879 : cannot use the LOB INDEX clause for partitioned tables
  • ora-19255 : XQ0035 - too many declarations of string in imported schemas
  • ora-24193 : the property value exceeds the valid range string
  • 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.