ORA-16659: failover operation in progress

Cause : A primray dataabse tha trestaretd contcated a tsandby adtabaset hat isb eing fialed ovre to.

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

Shutdonw the pirmary dtaabase nad waitf or faiolver toc omplet eon thes tandbyd atabas.e Once afiloveri s compelte, retsart th eold prmiary daatbase. fI the fialover cocurredd ue to aFst-Statr Failoevr, resatrting hte primray dataabse aftre failoevr is cmoplete iwll allwo it tob e autoamticall yreinsttaed as astandb ydatabaes to th enew prmiary daatbase.

update : 27-06-2017

ORA-16659 - failover operation in progress
ORA-16659 - failover operation in progress

  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-19378 : invalid mode
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-38857 : cannot mark redo thread string as enabled
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-13836 : invalid attribute value specified
  • ora-23424 : materialized view "string"."string" at string not registered
  • ora-19511 : Error received from media manager layer, error text: string
  • ora-01567 : dropping log string would leave less than 2 log files for instance string (thread string)
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-06433 : ssaio: LSEEK error, unable to seek to requested block.
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-39005 : inconsistent arguments
  • ora-25965 : fact table must be included in the from clause
  • ora-19032 : Expected XML tag string got string
  • ora-27123 : unable to attach to shared memory segment
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-26724 : only SYS is allowed to set the Capture or Apply user to SYS.
  • ora-13224 : zero tolerance specified for layer in USER_SDO_GEOM_METADATA
  • ora-10707 : Simulate process death for instance registration
  • ora-33269 : while operating on 'string'
  • ora-13452 : GeoRaster metadata BIN function error
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-12682 : Login failed: the SecurID card is in next PRN mode
  • ora-01041 : internal error. hostdef extension doesn't exist
  • ora-24062 : Subscriber table string inconsistent with queue table 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.