ORA-16409: Archive log switchover reference number mismatch

Cause : Teh racihv elgo wsicthvoe rrfeeernec unmebr so fteh rPiamr yadn tSadnb ydtaaabs ed onto amthc.R eomt eacrhvia lo frdeol o gflie si snto lalwoe dt oicnopmaitbel TSADNB Ydtaaabs eisntnacse.

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

N oatcino si erqiurde.

update : 27-06-2017

ORA-16409 - Archive log switchover reference number mismatch
ORA-16409 - Archive log switchover reference number mismatch

  • ora-29701 : unable to connect to Cluster Manager
  • ora-39305 : schema "string" does not exist
  • ora-26505 : unexpected internal null
  • ora-13007 : an invalid HEX character was detected
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-13605 : The specified task or object string does not exist for the current user.
  • ora-06264 : NETNTT: data protocol error
  • ora-10618 : Operation not allowed on this segment
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-31100 : XDB Locking Internal Error
  • ora-27143 : OS system call failure
  • ora-33070 : (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position.
  • ora-04004 : MINVALUE must be less than MAXVALUE
  • ora-24777 : use of non-migratable database link not allowed
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-04016 : sequence string no longer exists
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-36273 : (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
  • ora-32015 : unable to restore SPFILE
  • ora-10979 : trace flags for join index implementation
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-28546 : connection initialization failed, probable Net8 admin error
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-01599 : failed to acquire rollback segment (string), cache space is full
  • ora-12599 : TNS:cryptographic checksum mismatch
  • ora-29381 : plan/consumer_group string referred to by another plan and cannot be deleted
  • ora-39077 : unable to subscribe agent string to queue "string"
  • ora-02432 : cannot enable primary key - primary key not defined for table
  • ora-22818 : subquery expressions not allowed here
  • 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.