Re: oracle recovery scenarios

From: Howard Latham <howard.latham_at_gmail.com>
Date: Sun, 8 Feb 2009 13:00:23 +0000
Message-ID: <713d96d10902080500t4172c567m4b3c02e1d502ee34_at_mail.gmail.com>

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_at_gmail.com>

>
> 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_at_gmail.com>
>
> 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
>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>>
>
>
> --
> Howard A. Latham
>
>
>

-- 
Howard A. Latham

--
http://www.freelists.org/webpage/oracle-l

Received on Sun Feb 08 2009 - 07:00:23 CST