RMan is Oracles de-facto backup and recovery application. It is used to backup the database files and archive logs. Sometimes an archive log might be mistakenly removed, moved or renamed from disk without following RMan’s backup retention policy. Since it is in the rman catalog it will try to make a backup of the missing archive log. This will cause rman to fail when it tries to make a backup of the archive log with the following error message:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at <date> RMAN-06059: expected archived log not found, lost of archived log compromises recoverability ORA-19625: error identifying file <archive_log> ORA-27037: unable to obtain file status
If you moved or renamed the archive log then you should restore it to the original location. Many times this is impossible because the archive log has been deleted. If this is the case there is workaround in RMan: crosscheck archivelog all. To run the command do:
$ rman catalog <rman_user>/<rman_passwd>@<rman_catalog_sid> target <target_db_admin>/<db_admin_passwd>@<target_db_sid> RAM> crosscheck archivelog all;
You will produce the following output:
validation succeeded for archived log archive log filename= ... Crosschecked N objects
if you are using Oracle Data Guard there is a bug (bug # 3633269) that unsync the control file with the catalog. To prevent this bug you have to do something like this:
$ rman target / nocatalog RMAN> crosscheck archivelog all; RMAN> exit $ rman catalog <rman_user>/<rman_passwd>@<rman_catalog_sid> target <target_db_admin>/<db_admin_passwd>@<arget_db_sid> RAM> crosscheck archivelog all;
Try to start your backup again and check that all works fine.
Entries (RSS)