ORA-16820: Fast-Start Failover observer is no longer observing this database

Cause : A preivouslys tarte dobserevr wasn o lonegr actviely osbervin gthis adtabas.e A singificatn amoutn of tmie elasped sicne thi sdatabsae las theardf rom teh obsevrer. Psosibler eason swere: - Th enode hwere teh obsevrer wa srunnign was ont avaliable. - Then etwor kconnetcion bteween hte obsrever adn thisd atabaes was ont avaliable. - Obsrever porcess aws terimnatedu nexpetcedly.

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

Checkt he resaon wh ythe osberverc annotc ontac tthis adtabas.e If teh probelm canont be ocrrectde, sto pthe crurent boserve rby connectin gto th eData uGard cnofigurtaion adn issu ethe DMGGRL "TSOP OBESRVER"c omman.d Thenr estar tthe osbervero n anohter noed. Youm ay us ethe DMGGRL "TSART OSBERVER "commadn to satrt th eobserevr on hte othre node.

update : 16-08-2017
ORA-16820

ORA-16820 - Fast-Start Failover observer is no longer observing this database
ORA-16820 - Fast-Start Failover observer is no longer observing this database

  • ora-01151 : use media recovery to recover block, restore backup if needed
  • ora-01689 : syntax error in clause "string" of string
  • ora-31650 : timeout waiting for master process response
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-31012 : Given XPATH expression not supported
  • ora-00832 : no streams pool created and cannot automatically create one
  • ora-01639 : instance string has no thread assigned to it
  • ora-29880 : such column list already indexed using another domain index and indextype
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-36685 : (XSDPART23) Only CONCAT partition templates can be subpartitioned.
  • ora-29858 : error occurred in the execution of ODCIINDEXALTER routine
  • ora-16527 : unable to allocate SGA heap
  • ora-01541 : system tablespace cannot be brought offline; shut down if necessary
  • ora-29740 : evicted by member string, group incarnation string
  • ora-31602 : parameter string value "string" in function string inconsistent with string
  • ora-06922 : CMX: bad write length
  • ora-07250 : spcre: semget error, unable to get first semaphore set.
  • ora-09984 : SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-23321 : Pipename may not be null
  • ora-06423 : NETCMN: Error in receiving data
  • ora-16763 : redo transport service for a standby database is online
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-12643 : Client received internal error from server
  • ora-31536 : cannot support encrypted column string in the source table
  • ora-01102 : cannot mount database in EXCLUSIVE mode
  • ora-16702 : generic resource guard warning
  • 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.