Re: oracle recovery scenarios
- From: Howard Latham <howard.latham@xxxxxxxxx>
- To: oracledbaquestions@xxxxxxxxx
- Date: Sun, 8 Feb 2009 13:00:23 +0000
The other problem about such a manual is that knowledge grows and new
methods are developed so I think logging a tar and googling (or Yahooing if
google deice every website is dangerous again)) are essential in a recovery
situation.
2009/2/8 Howard Latham <howard.latham@xxxxxxxxx>
>
> I've been asked to write a 'recovery manual'
> So if on holiday our developers can recover the database.
> If I could I would publish it!
> Anyway you can add corruption sub heading - with corrupt dbf , redo , temp
> as subs of that.
> My books growing isnt it!
> 2009/2/7 Dba DBA <oracledbaquestions@xxxxxxxxx>
>
> I don't do alot of recoveries, so when I need to do something, I
>> always end up googling it. So I want to write myself some notes for
>> some of the basic scenarios. Here is my list so far.
>> I keep notes of activities I don't use very often. So I don't have to
>> look them up again.
>>
>> all of these assume I can use RMAN
>>
>> 1. full recovery(with and without archivelog mode)
>> 2. point in time recovery
>> 3. flashback database
>> 4. lost a redo log(both online and offline, with multiple redo log
>> groups or without)
>> 5. lost a datafile
>> 6. restore control file
>> 7. restore spfile
>> 8. someone drops a table, so flash back table
>> --
>> //www.freelists.org/webpage/oracle-l
>>
>>
>>
>
>
> --
> Howard A. Latham
>
>
>
--
Howard A. Latham
Other related posts:
