Re: Rule number 1 of an Oracle recovery process

In article <5SX89.11764$g9.38452_at_newsfeeds.bigpond.com>, you said (and I quote):
>
> Recovering the database is one of the most crucial aspects of the DBA role.
> Trying to work out what to do *when* the problem occurs is too late. At
> best, you're going to waste possible precious availability times. At worst,
> well at worst, close you're eyes and imagine the end of the world. Cause
> that's what it could feel like.

Yup. So, save the controlfile before you start! ;-)

IOW,
Murphy's law: no matter how well prepared you think you are, what can go wrong will.
Johnson's corollary: What cannot go wrong will make a darn good try of tripping you.

Me? Since I have no say whatsoever on how Oracle codes and handles recovery and its processes, I take the defensive approach: cover every possible option. It's never failed me when I needed it, takes less than 30 secs.

>
> There's nothing like seeing the message "Media Recovery Complete" a few
> minutes after detecting the problem ;)
>

You're not wrong...

-- 
Cheers
Nuno Souto
nsouto_at_optushome.com.au.nospam