Again, if i list the backup (l#ist backup), the status of latest backup which executed successfully today becomes "EXPIRED".That would happen if a non-RMAN command (e.g. an OS level DEL or RM command) was used to delete the backup pieces. When running the CROSSCHECK, Oracle no longer finds them in the expected location and, therefore, marks them as EXPIRED.
Vidhya.V wrote:I've never tested trying to "unexpire" a backup piece once it is marked as 'expired', but it sounds reasonable. It would be easy enough for you test for yourself. If that is going to be your strategy, then you need to make sure you never do a 'delete expired'. That command will cause rman to remove the entries of the 'expired' backups from its repository. Then if you tried to 'unexpire' by restoring your backups and re-running 'crosscheck', the entries in the repository are no longer there to BE crosschecked. And since you are running the very obsolete 9i, you can't recatalog them. And since that strategy means never issuing a 'delete expired', your control file will continue to grow ad infinitum because you will NEVER be able to clean up old entries.
I will zip the backup copies for reclaiming more space. So, since files are not present there is it displaying as expired.
Once I unzip the files and try for a crosscheck, will it work??