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 : 22-08-2017
ORA-16145

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

  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-16738 : redo tranport service for standby database "string" unexpectedly offline
  • ora-02189 : ON required
  • ora-16792 : configuration property value is inconsistent with database setting
  • ora-01529 : error closing file 'string'
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-30729 : maximum number of columns exceeded
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-02755 : osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf
  • ora-37016 : (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command.
  • ora-15152 : cluster in rolling upgrade
  • ora-13144 : target table string not found
  • ora-04099 : trigger 'string' is valid but not stored in compiled form
  • ora-12535 : TNS:operation timed out
  • ora-16754 : resource guard could not activate standby database
  • ora-26023 : index string.string partition string was made unusable due to:
  • ora-04051 : user string cannot use database link string.string
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-14026 : PARTITION and CLUSTER clauses are mutually exclusive
  • ora-16063 : remote archival is enabled by another instance
  • ora-08208 : ora_addr: cannot read from address file
  • ora-16618 : response document of size "string" bytes is too large
  • ora-23514 : invalid or incorrect number of arguments
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-26063 : Can not flashback to specified SCN value - Wrap: string Base: string.
  • ora-13711 : Some snapshots in the range [string, string] are missing key statistics.
  • ora-01655 : unable to extend cluster string.string by string in tablespace 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.