This content has been marked as final. Show 8 replies
Thanks for the quick response. I could delete based on a date but how come 'delete obsolete' does not delete records older than "recovery window". Is it possible that my last 60 days of backups are not valid for some reason and it needs to keep the older ones? If the old stuff is not in the catalog then when I do 'list backup' where is it showing the older records from?
We take nightly hotbackup on this database.
Apologize for too many questions.... trying to get an understanding of what's happening.
I have several short notes which may help :
But 2008 is so far out I would just clean it up and watch it for clues at this point.
See if you can determine what those older backups are ?
Were they backups taken with a KEEP UNTIL TIME clause (meaning that they cannot be obsoleted until the keep time has elapsed) or KEEP FOREVER ?
Are those backups of a particular tablespace which happens to be excluded from subsequent backups (thus requiring that oracle keep those backups as not obsolete as they would be required to restore that tablespace) ?
Hemant K Chitale
Could not get a whole lot of help from support but figured out that since we delete the backup files from the disk after nightly backup to tape, When I run a crosscheck backup command, it cannot find enough backups to satisy the recovery window of 60 days. Thus when I run 'delete obsolete' command, it doesn't delete older records. I cleaned up the catalog using 'delete noprompt backupset completed before 'SYSDATE - 100'.
Thank you all for the responses.