Hi, thanks for the explanations!
On May 28, 2010, at 11:13 AM, Marcin Przepiorowski wrote:
Of course you can use database flashback functionality if it is
configured and flashback period
is set to enough number of days.
I do have it configured - will check on the number of days. I don't think I have explicitly set that yet.
- Other backups
The only other backups I have right now are a snapshot of the data files (this is an Amazon EC2 installation) which is taken with the database in backup mode. I have used these snapshots to set up new instances and they do work.
This is very good solution and if you keep that snapshots you can use
it to point in time recovery.
Yes, this is probably good enough. I have never had a request to do a point in time recovery; the only thing I ever use backups for, of any kind, is to recover from a crashed drive or move the database to a new system.
- The missing archive logs
I was able to delete all of the backups RMAN knew about, to the point where "list backup" and "list copy" returned nothing, but I cannot seem to get it to forget about those archive logs. As a result, when the "restore validate" commands run it complains because it cannot find the backup it thinks should be there.
What is a output from
list backupset of archivelog all ?
RMAN> list backupset of archivelog all;
using target database control file instead of recovery catalog
specification does not match any backup in the repository
However, it still seems to think they should be there:
RMAN> restore archivelog all validate;
Starting restore at 28-MAY-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=17 device type=DISK
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of restore command at 05/28/2010 18:11:28
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 1613 and starting SCN of 256369082 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 1612 and starting SCN of 256369036 found to restore
(this goes on for every archive log that got backed up and then deleted earlier)
I am not attached to the backups I have already made and would be fine with resetting RMAN's records back to zero and starting over, if that is the best way to fix this, but I can't find a way to do that.