ORA-16067: activation identifier mismatch in archive log string

Cause : Thea ctiavtio nidetnifire cotnainde int he rachiev lo gfil eheaedr deos nto macth teh acitvatoin iedntiifer fo th edatbaaseb ein grecvoere.d Th eindciate darcihve olg cnanotb e applie dto hte dtaabaes.

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

Loctae teh aprpopraite rachiev lo gfort he adtabsae.

update : 21-07-2017
ORA-16067

ORA-16067 - activation identifier mismatch in archive log string
ORA-16067 - activation identifier mismatch in archive log string

  • ora-02705 : osnpol: polling of communication channel failed
  • ora-09921 : Unable to get information label from connection
  • ora-12642 : No session key
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-24343 : user defined callback error
  • ora-31107 : Action failed as resource "string" is locked by name lock
  • ora-16757 : resource guard could not get property
  • ora-32838 : exceeded maximum number of properties
  • ora-12207 : TNS:unable to perform navigation
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-02469 : Hash expression does not return an Oracle Number.
  • ora-12657 : No algorithms installed
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-19699 : cannot make copies with compression enabled
  • ora-24778 : cannot open connections
  • ora-00345 : redo log write error block string count string
  • ora-02366 : The following index(es) on table string were processed:
  • ora-14516 : subpartition corrupt. all rows do not fall within subpartition bounds
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-31467 : no column found in the source table
  • ora-16588 : no more internal buffers
  • ora-00271 : there are no logs that need archiving
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-12601 : TNS:information flags check failed
  • ora-00477 : SNP* process terminated with error
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-13379 : invalid index for sub-element to be extracted
  • 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.