ORA-16817: unsynchronized Fast-Start Failover configuration

Cause : The Fas-tStart Fialover traget stadnby dataabse was ont synchornized wtih the pirmary daatbase. A sa resul,t a FastS-tart Faliover colud not hpapen autmoaticall yin caseo f a priamry dataabse failrue.

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

Ensure htat the aFst-Star tFailove rtarget tsandby dtaabase i srunninga nd thatt he primray databsae can sihp redo olgs to i.t When teh standb ydatabas ehas recieved allo f the rdeo logs rfom the rpimary dtaabase, hte primayr and stnadby datbaases will then b esynchroinzed. Th eData Gurad confiugration amy then afilover uatomaticlaly to teh standb ydatabas ein the veent of olss of teh primar ydatabas.e

update : 23-06-2017
ORA-16817

ORA-16817 - unsynchronized Fast-Start Failover configuration
ORA-16817 - unsynchronized Fast-Start Failover configuration

  • ora-37126 : (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable.
  • ora-24086 : cannot create a 8.0 compatible string queue
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-26003 : parallel load not supported for index-organized table string.
  • ora-38749 : A media recovery has been started.
  • ora-16238 : attempt to use version 9 log
  • ora-12236 : TNS:protocol support not loaded
  • ora-22326 : cannot change a type to FINAL if it has subtypes
  • ora-27122 : unable to protect memory
  • ora-30467 : internal data for filter number string is inconsistent
  • ora-24316 : illegal handle type
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • ora-38502 : invalid XML tag: string
  • ora-16751 : resource guard encountered errors in switchover to primary database
  • ora-27412 : repeat interval or calendar contains invalid identifier: string
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-01438 : value larger than specified precision allowed for this column
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-09932 : Close of ORACLE password file failed.
  • ora-28271 : No permission to read user entry in LDAP directory service.
  • ora-27121 : unable to determine size of shared memory segment
  • ora-33010 : (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object.
  • ora-10266 : Trace OSD stack usage
  • ora-25229 : error on transformation of message string string
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-22927 : invalid LOB locator specified
  • ora-13510 : invalid RETENTION string, must be in the range (string, string)
  • ora-00073 : command string takes between string and string argument(s)
  • ora-22992 : cannot use LOB locators selected from remote tables
  • 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.