Re: database could not be started

"quarkman" <quarkman_at_myrealbox.com> schrieb im Newsbeitrag news:oprtnqk2wfzkogxn_at_haydn...
> On Sat, 9 Aug 2003 12:39:31 -0500, Burton Peltier
> <burttemp1REMOVE_THIS_at_bellsouth.net> wrote:
>
> > "Anton Buijs" <remove_aammbuijs_at_xs4all.nl> wrote in message
> > news:3f3510b5$0$49108$e4fe514c_at_news.xs4all.nl...
>
> >
> > This is the main reason where you would need the REDO logs. I thought
> > that
> > was what I said? After re-reading my post, it IS what I said.
> >
> > Just to be clear... I did not mean to imply and I know you do NOT
recover
> > REDO logs when recovering from a hot backup. The entire context of the
> > OP
> > was a problem with a cold backup. All of the comments in my post were
> > about
> > cold backups ONLY.
> >
> > Hot backups are different, of course.
>
>
> The temperature of your backups makes no difference. You should never
> backup online redo logs, period. Archivelog or noarchivelog, hot or cold.
>
> The subtler point is that's it's fine to do cold backups, even in
> archivelog mode. Indeed, cold backups with archivelog mode is quite
> possibily the nicest combination of options available to the dba. But
> herein lies the source of possible confusion: I'm in archivelog mode, I
> take cold backups... is it therefore OK for me to backup my online redo
> logs? No it isn't, because I risk data loss at the time of restore.
But if one were in archivelog mode, why not simply do a logswitch, wait until the archiving has finished and that's it?

Lots of Greetings!
Volker Received on Mon Aug 11 2003 - 09:46:03 CDT