Re: Some one tested RESETLOGS new functionality on 10g?
- From: Tim Gorman <tim@xxxxxxxxx>
- To: Oracle-L <Oracle-L@xxxxxxxxxxxxx>
- Date: Mon, 28 Feb 2005 20:57:55 -0700
The basic idea is that, starting in v7.3.3, Oracle started emitting the SCN
of the RESETLOGS action to the "alert.log" file. Also, it was stored to the
V$DATABASE view in the controlfile. A savvy DBA will save that information
somewhere or at least be aware that it is there.
So, armed with that RESETLOGS_CHANGE# value...
- restore a controlfile from before the RESETLOGS
- restore all/some datafiles from backup taken before RESETLOGS
- perform RECOVER DATABASE UNTIL SCN = <resetlogs-scn>
- shutdown
- restore the most current controlfile (from after the RESETLOGS)
- startup mount
- perform RECOVER DATABASE until desired point-in-time
The key to it all is saving the RESETLOGS_CHANGE#. Without it, no chance.
With it, your next stop is to log a severity 1 iTAR and validate what you
want to do with someone at Support...
So, now it seems like Oracle10g has taken the next step and started
performing the above steps automatically, using only the most current
controlfile. I bet this saves a few lives...
on 2/28/05 7:27 PM, Juan Carlos Reyes Pacheco at juancarlosreyesp@xxxxxxxxx
wrote:
> Plese Tim how could I recover this, I understand you could do this
> without a backup after the resetlogs, or I misunderstood something.
>
> archive log 123,124...200
>
> Recover full backup and apply up to 150
> RESETLOGS
> archive log 1,2,3,....100
>
> Then I need to recover again upt to 150 and then to 30
>
> How do you do?
> Thank you
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
