ORA-00308: cannot open archived log 'string'

Cause : The system cannot access a required archived redo log file.

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

Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.

update : 17-08-2017
ORA-00308

ORA-00308 - cannot open archived log 'string'
ORA-00308 - cannot open archived log 'string'

  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-01692 : unable to extend lob segment string.string partition string by string in tablespace string
  • ora-13529 : Error occurred when flushing AWR table group
  • ora-16708 : the state supplied to resource guard is invalid
  • ora-39219 : directory object name is too long
  • ora-07234 : slemcw: fseek error.
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-14108 : illegal partition-extended table name syntax
  • ora-14521 : Default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-19249 : XP0029 - value does not match facet of the target type
  • ora-21709 : cannot refresh an object that has been modified
  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-39174 : Encryption password must be supplied.
  • ora-14191 : ALLOCATE STORAGE may not be specified for Composite Range partitioned object
  • ora-07270 : spalck: setitimer error, unable to set interval timer.
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-15061 : ASM operation not supported [string]
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-00406 : COMPATIBLE parameter needs to be string or greater
  • ora-08116 : can not acquire dml enough lock(S mode) for online index build
  • ora-16566 : unsupported document type
  • ora-13789 : invalid process action
  • ora-06444 : ssvpstev: Failed with unexpected error number.
  • ora-01987 : client os username is too long
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-01231 : cannot make read write - file string is offline
  • ora-00236 : snapshot operation disallowed: mounted control file is a backup
  • ora-07470 : snclget: cannot get cluster number.
  • ora-16093 : dependent archive log destination is not LGWR-enabled
  • 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.