RMAN-00571: ========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ============= RMAN-00571: ========================================================== RMAN-03002: failure of backup command at 11/08/2006 09:03:03 RMAN-06059: expected archived log not found, lost of archived log compromises recoverability ORA-19625: error identifying file /data/oracle/xxx/xxx/xxx/1_217.dbf ORA-27037: unable to obtain file status Linux Error: 2: Datei oder Verzeichnis nicht gefunden Additional information: 3"The first archive log file in this folder is the file 1_280.dbf. What should I do to correct the filename RMAN wants to back up?
When backing up your archived redo logs, RMAN will still attempt to back up the missing ones. So you need to help RMAN out. This can be done by either instructing RMAN where to find the archived redo log, or by letting RMAN know that the archived redo log no longer exists.
If you have located the archived redo log (maybe it is in another log destination), you can tell RMAN where the log is by using the CATALOG command:
CATALOG ARCHIVELOG '/directory/filename';To help RMAN figure out which archived redo logs are missing, use the CHANGE command:
CHANGE ARCHIVELOG SEQUENCE BETWEEN 217 AND 279 UNAVAILABLE;The above command tells RMAN that archive logs between sequences 217 and 279 are no longer available for backup.
You can find more information about the CATALOG and CHANGE commands in the Oracle documentation.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading