Recovery failing with ORA-00328, ORA-00334 [ID 1327154.1]

rongshiyuan發表於2013-06-26
AI
Recovery failing with ORA-00328, ORA-00334 [ID 1327154.1]
 

In this Document
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.2.0.2 - Release: 9.2 to 11.2
Information in this document applies to any platform.

Symptoms

Recovery is failing with errors like these:


SQL> recover database using backup controlfile until cancel;

ORA-00279: change 3761213609795 generated at 05/16/2011 06:54:19 needed for thread 1
ORA-00289: suggestion : /usr/oracle/p003/archive/arch/_677042908_1_237409.log
ORA-00280: change 3761213609795 for thread 1 is in sequence #237409

Specify log: {=suggested | filename | AUTO | CANCEL}

ORA-00328: archived log ends at change 3760559938982, need later change 3761213609795
ORA-00334: archived log: '/usr/oracle/p003/archive/arch/_677042908_1_237409.log'

Cause

- database was restored to a new host (most likely but not required)
- database was opened read/write and NOT with RESETLOGS, so likely a COLD backup including the online redologs has been restored.
- database shutdowned and mounted afterwards, then recovery was started.

The database cannot be opened read/write then recovered. When the restored database is opened read/write it sends the database off into a different "direction" from the source (SCNs from the source archivelog files will not match the SCN requested by the recover command). When you try to apply an archivelog from the source you will see ORA-00328 / ORA-00334.

Look in the alert log for the restored database to see if it was opened after the restore.

Solution

It is STRONGLY recommend to NEVER EVER restore the online redolog files, not even for a COLD-backup. This would have prevented the initial startup to succeed, and the archived redologs would NOT have been overwritten with new and different SCN's.

Re-restore the datafiles, move any archivelog files created from the restored database after it was opened, mount, start the recovery.

References

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-764822/，如需轉載，請註明出處，否則將追究法律責任。

相關文章