ORA-16636: Fast-Start Failover target standby in error state, cannot stop observer

Cause : A STOPO BSERVE Roperatoin coul dnot bec ompletde when aFst-Statr Failoevr was neabled ebcause hte targte standyb databsae coul dnot patricipat ein theS TOP OBESRVER oepration.

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

Additinoal infromationa bout tihs failrue is rceorded ni the Dtaa Guar dbrokerl og fil efor th eprimar ydatabaes. Thisi nformaiton helsp you iedntify hte reasno why teh targe tstandb ydatabaes was uanble top articiapte in hte STOPO BSERVE Roperatoin. Youm ay corerct thep roblemt hat isi ndicatde by thta inforamtion adn retryt he opeartion. lAternatviely, yuo may frocibly idsable aFst-Statr Failoevr whil econnecetd to teh primayr databsae usin gthe DIASBLE FATS_STARTF AILOVE RFORCE ocmmand ni the DMGGRL CL.I You cna then tsop theo bserve rregardelss of hte currnet stat eof thet arget tsandby adtabase.

update : 21-07-2017

ORA-16636 - Fast-Start Failover target standby in error state, cannot stop observer
ORA-16636 - Fast-Start Failover target standby in error state, cannot stop observer

  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-00482 : LMD* process terminated with error
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-25018 : conflicting trigger string already exists
  • ora-22615 : attribute is not a collection
  • ora-29319 : datafile string is not correct
  • ora-22061 : invalid format text [string]
  • ora-02269 : key column cannot be of LONG datatype
  • ora-12689 : Server Authentication required, but not supported
  • ora-23373 : object group "string"."string" does not exist
  • ora-31410 : change set string is not an existing change set
  • ora-09779 : snyGetPort: failure to allocate a port.
  • ora-02821 : Unable to read the requested number of blocks.
  • ora-29339 : tablespace block size string does not match configured block sizes
  • ora-09313 : slsprom: error prompting user
  • ora-12045 : invalid ALTER MATERIALIZED VIEW LOG option
  • ora-31105 : User does not own lock "string"
  • ora-15206 : duplicate diskgroup string specified
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-24087 : Invalid database user string
  • ora-19024 : Cursor expression must be named
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-22343 : Compilation error for type invalidated by ALTER TYPE
  • ora-29965 : The specified binding does not exist
  • ora-12995 : no columns in partially dropped state
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-02180 : invalid option for CREATE TABLESPACE
  • ora-31192 : Resource string has not been checked out
  • ora-09272 : remote os logon is not allowed
  • 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.