ORA-16145: archival for thread# string sequence# string in progress

Cause : The indicated archived log file is not available for recovery due to the fact that it is still being archived.

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

Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.

update : 24-06-2017
ORA-16145

ORA-16145 - archival for thread# string sequence# string in progress
ORA-16145 - archival for thread# string sequence# string in progress

  • ora-03276 : duplicate ALLOCATE EXTENT option specification
  • ora-01650 : unable to extend rollback segment string by string in tablespace string
  • ora-29347 : Tablespace name validation failed - failed to match tablespace 'string'
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-38785 : Media recovery must be enabled for guaranteed restore point.
  • ora-21560 : argument string is null, invalid, or out of range
  • ora-13359 : extent does not have an area
  • ora-31121 : The string operator can not be FALSE
  • ora-01783 : only one RECOVERABLE or UNRECOVERABLE clause may be specified
  • ora-29263 : HTTP protocol error
  • ora-16401 : archivelog rejected by RFS
  • ora-29295 : invalid mime header tag
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-07646 : sszfck: $CREATE failure
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-00711 : new tablespace name is invalid
  • ora-22990 : LOB locators cannot span transactions
  • ora-29341 : The transportable set is not self-contained
  • ora-01882 : timezone region string not found
  • ora-13024 : polygon has less than three segments
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-13828 : generated SQL profile name string already exists
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • ora-13211 : failed to tessellate the window object
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-07247 : skgfrfms, skgfrnms: read error, unable to read block from database file
  • ora-09814 : Unable to expand file name
  • ora-16247 : DDL skipped on internal schema
  • ora-16038 : log string sequence# string cannot be archived
  • 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.