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 : 30-04-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-12690 : Server Authentication failed, login cancelled
  • ora-00449 : background process 'string' unexpectedly terminated with error string
  • ora-31030 : Unable to retrieve XML document
  • ora-16750 : resource guard encountered errors while activating logical primary database
  • ora-39019 : invalid operation type string
  • ora-00485 : DIAG process terminated with error string
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-28660 : Partitioned Index-Organized table may not be MOVEd as a whole
  • ora-31506 : duplicate subscription name string
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-12059 : prebuilt table "string"."string" does not exist
  • ora-01041 : internal error. hostdef extension doesn't exist
  • ora-27080 : too many files open
  • ora-01902 : SEGMENT keyword expected
  • ora-40003 : wordsize must be in the range string - string for BLAST-P
  • ora-16608 : one or more databases have warnings
  • ora-01599 : failed to acquire rollback segment (string), cache space is full
  • ora-06304 : IPA: Message receive error
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-01508 : cannot create database; error in file 'string' at line string
  • ora-30352 : inconsistent numeric precision or string length
  • ora-29804 : missing DATA keyword
  • ora-13856 : Service name must be specified
  • ora-06604 : LU6.2 Driver: Unable to allocate session with remote LU
  • ora-39772 : column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA
  • ora-16228 : Insufficient recovery for logical standby
  • ora-33456 : (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.
  • ora-01764 : new update value of join is not guaranteed to be unique
  • ora-16703 : cannot set property while the database is enabled
  • 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.