RMAN Backup takes more time than
earlier.
RMAN Backup failed with error RMAN-06059:
expected archived log not found
ORA-19625: error identifying file
/u02/oradata/archive/1_prod_3241.arc.
we
did not delete archive log through RMAN. we delete archive log
directly using rm -rf command, so RMAN is unaware of those archive logs status.
if you are experiencing same problem that your backup failed because of missing
archive log then do following things.
Connect to RMAN as RMAN TARGET / and
then
crosscheck archivelog all;
delete expired archivelog all;
then connect to catalog database and resync
the catalog.
rman target / catalog
rman/rman_2005@RMANCAT
resync catalog;
one
more thing is that my RMAN backup took more time as it also looks for unavailable archive log as well, When an archive log
crosscheck is performed, RMAN checks each archive log in turn to make sure that
it exists on disk. Those that are missing are marked as unavailable. you can
skip the particular range of missing archivelog while taking the backup.
connect to catalog.
rman target / catalog
rman/rman_2005@RMANCAT
run
{
change archivelog from logseq = xxx
until logseq = yyy unavailable;
}
rman>resync catalog;
