Consequences of Applying a Partially Archived Redo Log
(Doc ID 1499960.1)
Last updated on OCTOBER 01, 2024
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Steps performed:
1) Shutdown db and took snapshot of all datafiles to new host. Online redo logs and controlfiles were not copied across.
2) Restarted source db
3) Transferred all archivelogs from archive destination to new host
4) Recreated controlfile at new host
5) Started recovery until time using backup controlfile
Symptoms
When we tried to recover database to a point in time, it does not apply all the archive logs required to meet the time and finished with 'Media Recovery Complete'.
Command used:
1) First recovery attempt using the archivelog <archivelog name>.ARC that was originally transferred to the new host on Oct 07th. Incomplete recovery believes that it has applied all logs required, stopping at scn 7643306070118 time 10/07/2012 11:05:24. This is 2 days earlier than the required point in time:
ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL TIME '2012-10-09:09:31:00' USING BACKUP CONTROLFILE ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /<log directory>/<archivelog name>.ARC
Tue Oct 16 09:18:42 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 7643306070118 time 10/07/2012 11:05:24
Media Recovery Complete (<db name>)
2) Second recovery attempt, this time giving it the version from the source database. We can see that the real archivelog log <archivelog name>.ARC actually ends with SCN 7643267785414, not scn 7643306070118:
Tue Oct 16 12:24:11 2012
ORA-279 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ...
Tue Oct 16 12:24:26 2012
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /<log directory>/logs/<archivelog name>.ARC
Tue Oct 16 12:24:26 2012
Errors with log /<log directory>/logs/<archivelog name>.ARC
Errors in file /<Oracle base>/diag/rdbms/<dbname>/<instance name>/trace/<dbname>_pr00_25176.trc:
ORA-00328: archived log ends at change 7643267785414, need later change 7643306070118
ORA-00334: archived log: '/<log directory>/logs/<archivelog name>.ARC'
ORA-328 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
ALTER DATABASE RECOVER CANCEL
Media Recovery Canceled
Completed: ALTER DATABASE RECOVER CANCEL
4) third recovery attempt, giving it sequence 60915:
Tue Oct 16 09:50:36 2012
ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL TIME '2012-10-09:09:31:00' USING BACKUP CONTROLFILE ...
Tue Oct 16 09:56:49 2012
ALTER DATABASE RECOVER LOGFILE '/<log directory>/logs/<archivelog name>.ARC'
Media Recovery Log /<log directory>/logs/<archivelog name>.ARC
Tue Oct 16 09:56:49 2012
Errors with log /<log directory>/logs/<archivelog name>.ARC
Errors in file /<Oracle base>/diag/rdbms/<dbname>/<instance name>/trace/_pr00_12307.trc:
ORA-00310: archived log contains sequence 60915; sequence 60914 required
ORA-00334: archived log: '/<log directory>/logs/<archivelog name>.ARC'
ORA-310 signalled during: ALTER DATABASE RECOVER LOGFILE '/<log directory>/logs/<archivelog name>.ARC' ...
ALTER DATABASE RECOVER CANCEL
Media Recovery Canceled
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |