Re: Cleaning up my RMAN catalog
- From: TESTAJ3@xxxxxxxxxxxxxx
- To: "janine" <janine@xxxxxxxxxx>, "oracle-l L" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 1 Jun 2010 17:33:09 -0400
Dump the controfile to trace, rip out any remants of rman backups and Rebuild
the controlfile.
Joe
Sent from the crackberry, so please excuse the typos and terseness.
----- Original Message -----
From: Janine Sisk [janine@xxxxxxxxxx]
Sent: 06/01/2010 02:00 PM MST
To: oracle-l L <oracle-l@xxxxxxxxxxxxx>
Subject: Cleaning up my RMAN catalog
You may recall my posts from last week, where I mentioned that I had deleted
all backups and copies but that "crosscheck archive all" is reporting errors on
a bunch of archive logs that were accidentally deleted:
RMAN-06025: no backup of archived log for thread 1 with sequence 1613 and
starting SCN of 256369082 found to restore
I still have this situation and am concerned that it's going to interfere with
restoring from these backups if I should ever need to do so.
In addition, I now have an obnoxiously large incremental backup that I really
don't need; the result of having dropped the user owning most of the data in
the database and reloading it.
I would like to just clear everything out, tell RMAN to forget that any of this
ever happened, and start over. I didn't set up a recovery catalog, as the docs
said that one wasn't needed unless you are using a physical standby, so I'm
using the simpler setup where the catalog is stored in the control file.
I already know that running "delete backup" and "delete copy" will get rid of
the backups and copies, but will leave the memory of those missing archive logs
intact.
Is there some way to completely reset things so that it looks like I've never
run a single backup of any kind? I have Googled and searched the Backup &
Recovery doc and all I can find is dropping the catalog database, which doesn't
apply in my case.
Thanks in advance!
janine
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
