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 : 23-04-2017
ORA-16636

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-00105 : too many dispatcher configurations
  • ora-12438 : repeated policy option: string
  • ora-29655 : USING clause is incompatible with its supertype
  • ora-01761 : DML operation does not map to a unique table in the join
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-16529 : bad sender id
  • ora-09800 : Process sensitivity label retrieval failed.
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-03008 : parameter COMPATIBLE >= string needed for string
  • ora-19999 : skip_row procedure was called
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-02846 : Unkillable server
  • ora-23372 : type string in table string is unsupported
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-03212 : Temporary Segment cannot be created in locally-managed tablespace
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • ora-30048 : Internal event for IMU auto-tuning
  • ora-12538 : TNS:no such protocol adapter
  • ora-07476 : slsget: cannot get mapped memory statistics.
  • ora-29825 : invalid name for indextype
  • ora-09819 : Number exceeds maximum legal value
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-07242 : slembfn: translation error, unable to translate error file name.
  • ora-38492 : invalid ALTER INDEX parameters clause "string"
  • ora-15055 : unable to connect to ASM instance
  • ora-34019 : (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.
  • ora-30110 : syntax error at '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.