Last updated on OCTOBER 27, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 220.127.116.11.0 [Release 10.1 to 11.2]
Information in this document applies to any platform.
This issue can occur for databases both in ARCHIVELOG and NOARCHIVELOG mode.
After an instance crash or SHUTDOWN ABORT a simple restart is all that is needed to allow instance recovery to take place and recover from the current online redolog.
If however the instance is MOUNTED and recovery is done manual you could find , depending on how the recovery is done , that Oracle requests an archivelog that does not yet exist.
The alert log shows the following:
Thu Feb 07 15:59:02 2013
Thu Feb 07 15:59:40 2013
ALTER DATABASE RECOVER database until CANCEL
Media Recovery Start
started logmerger process
Parallel Media Recovery started with 4 slaves
ORA-279 signalled during: ALTER DATABASE RECOVER database until CANCEL ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log +FRA/padev/archivelog/padev_806768403_1_18.arc
Thu Feb 07 15:59:45 2013
Errors with log +FRA/padev/archivelog/padev_806768403_1_18.arc
Errors in file /app/oracle/diag/rdbms/padev/PADEV1/trace/PADEV1_pr00_23841.trc:
ORA-00308: cannot open archived log '+FRA/padev/archivelog/padev_806768403_1_18.arc'
ORA-17503: ksfdopn:2 Failed to open file +FRA/padev/archivelog/padev_806768403_1_18.arc
ORA-15173: entry 'padev_806768403_1_18.arc' does not exist in directory 'archivelog'
ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
The requested archived redolog does not yet exist because it is the current online redolog that is yet to be archived.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms