Changed DB_RECOVERY_FILE_DEST path, but RMAN still backs up to the old path?

Posted on

Question :

I just recently changed the DB_RECOVERY_FILE_DEST parameter to point to a new directory path. However, I noticed only some archivelogs and backup sets are going to this new directory path and some are still going to the old path. Why is that?

Furthermore, some of the old archivelogs aren’t getting deleted when they’re past the retention policy. Do these need to get manually removed? If so, is there an RMAN command to manually remove them?

Thanks in advance.

Answer :

Can you provide your backup scrpit?

After changing DB_RECOVERY_FILE_DEST to new location – Copy all archive log file which is generated in old and copy to new location. using OS level copy command.

Then catalog the new DB_RECOVERY_FILE_DEST

RMAN> catalog db_recovery_file_dest;  ( else) 
RMAN> catalog start with 'New location Path'; 
RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all; 

Leave a Reply

Your email address will not be published. Required fields are marked *