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 : 20-08-2017

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

  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-25502 : concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-24129 : table name string does not start with string prefix
  • ora-27121 : unable to determine size of shared memory segment
  • ora-08460 : invalid environment clause in environment parameter
  • ora-02210 : no options specified for ALTER TABLE
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-32743 : command cannot be executed on remote instance
  • ora-14263 : new subpartition name must differ from that of any other subpartition of the object
  • ora-00826 : cannot set sga_target for an ASM instance
  • ora-04070 : invalid trigger name
  • ora-12636 : Packet send failed
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-01755 : Must specify an extent number or block number
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-02711 : osnpvalid: write to validation channel failed
  • ora-31428 : no publication contains all the specified columns
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-09774 : osnmui: cannot send break message
  • ora-01326 : compatability of 9.0 or greater required to build into the logstream
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-19608 : %s is not a backup piece
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-32301 : object-relational materialized views must be primary key based
  • 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.