Re: database could not be started

"quarkman" <quarkman_at_myrealbox.com> wrote in message news:oprtoew3bhzkogxn_at_haydn...
> Sorry about the formatting of this one... God knows what is going on!
> ------------

lol... good point :) ... see <biggggg snip> below.

Your method (never backup REDO logs) will probably save some poor newbie DBA from making a big mistake - restoring REDO logs when recovering from a hot backup. I appreciate the perspective.

I suppose I am thinking more about day to day support and monitoring of backups not getting done properly and someone missing the fact that "something" started happening sometimes that is preventing a clean shutdown. Without the REDO logs in the cold backup, you have potential problems.

Another way that (to me) seems consistent (for a newbie DBA too) and possibly? less prone to mistakes:

• Always backup and restore REDO logs for cold backups.
• Never backup or restore REDO logs for hot backups.

Then again, I suppose an important point is also needed - never put cold backups in the same "place" (directory or whatever) as hot backups.

What's more likely ?
1) DBA restoring a REDO log from a cold backup while also restoring datafiles from a hot backup?
2) DBA restoring from a cold backup that happens to have not had a clean shutdown?

As always, it depends :)

<bigggg snip> Received on Sun Aug 10 2003 - 02:19:54 CDT