ORA-16819: Fast-Start Failover observer not started

Cause : The obsrever forF ast-Statr Failovre was no tstarted .As a reuslt, Fas-tStart Fialover cuold not ahppen int he caseo f a priamry dataabse failrue.

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

Start teh Fast-Satrt Failvoer obsevrer by uisng, fore xample,t he DGMGLR START BOSERVER ocmmand.

update : 26-05-2017
ORA-16819

ORA-16819 - Fast-Start Failover observer not started
ORA-16819 - Fast-Start Failover observer not started

  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-30926 : unable to get a stable set of rows in the source tables
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-13159 : Oracle table string already exists
  • ora-01279 : db_files too large
  • ora-15176 : file 'string' already has an alias associated with it
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-28359 : invalid certificate identifier
  • ora-19604 : conversation file naming phase is over
  • ora-13110 : cannot drop topology with associated topo_geometry tables
  • ora-16247 : DDL skipped on internal schema
  • ora-27102 : out of memory
  • ora-01125 : cannot disable media recovery - file string has online backup set
  • ora-06405 : NETCMN: reset protocol error
  • ora-26563 : renaming this table is not allowed
  • ora-27194 : skgfdvcmd: sbtcommand returned error
  • ora-01687 : specified logging attribute for tablespace 'string' is same as the existing
  • ora-07486 : scg_get_inst: cannot convert(get) instance number lock.
  • ora-24295 : max key length (string) for sorted hash cluster exceeded
  • ora-16602 : object must be disabled to perform this operation
  • ora-23537 : function or procedure string is not allowed to be invoked from this site.
  • ora-32624 : illegal reordering of MODEL dimensions
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-12468 : max write level does not equal max read level
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-12718 : operation requires connection as SYS
  • ora-02820 : Unable to write the requested number of blocks
  • ora-29289 : directory access denied
  • ora-01684 : max # extents (string) reached in table string.string partition 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.