Re: Current online redolog corrupt!!!

No, you are right: an online backup *would* suffice. It's just that an online backup is taken over a period of time, and your database is not safe until it's been completed. Meanwhile, being open, transactions are being raised which are at risk of being lost.

Whereas an offline backup still takes a period of time to complete, but since the database is closed, no transactions are happening, and therefore there's nothing lost if it all goes pear-shaped.

Either would do, but closed is "safer".

Regards
HJR

--

Oracle Resources : http://www.geocities.com/howardjr2000
========================================


"Syltrem" <syltrem_at_videotron.spammenot.ca> wrote in message
news:ZthC7.481$qb4.1788_at_tor-nn1.netcom.ca...


> > And given the resetlogs, you now have no valid backups nor archives, so

> its

> > time to shut the entire database down cleanly, and perform a full,

closed


> > database backup.

>

> Could you please explain why an online backup would not be sufficient

here?


> I know you are right in saying this, I just want to make it clear in my

mind


> why an OFFLINE backup is required.

>

> Thanks!

>

> --

>

> Syltrem

> http://pages.infinit.net/syltrem (OpenVMS related web site - en français)

> To reply to myself directly, remove .spammenot from my address

>

> "Howard J. Rogers" <howardjr_at_www.com> a écrit dans le message news:

> 3bd871b7$0$8350$afc38c87_at_news.optusnet.com.au...

> > If the thing is genuinely lost (and I have neither the time nor the

> > inclination to check out error numbers for their precise text message),

> then

> > you are in deep doo-doo.

> >

> > The first thing you should do is take a backup.

> >

> > The next thing you should do is restore all data files, but not the

> > controlfile nor any online redo logs you might have floating around,

from


> > the last backup you've taken (you have taken backups, I hope?!).

> >

> > Then you get to the MOUNT state (startup mount [pfile=...]).

> >

> > Then you issue the command 'recover database until cancel', and when it

> > prompts to apply redo, type the word 'auto'.  All archives and online

logs


> > will be applied, automatically, until it can't read the contents of the

> > offending log, at which point the recovery process will crash out with

an


> > error.

> >

> > Then you issue the 'recover database until cancel' command once more,

and


> > when it prompts to apply the last log (presumably your current one), you

> > type the word 'cancel'.

> >

> > Then, you issue the command alter database open resetlogs, and the

> database

> > should open.  You'll have lost all transactions that were in the missing

> > redo log.

> >

> > Finally, you ask yourself why your online redo logs are not mirrored,

and


> > invest a little time and disk space in rectifying that problem pronto.

> >

> > And given the resetlogs, you now have no valid backups nor archives, so

> its

> > time to shut the entire database down cleanly, and perform a full,

closed


> > database backup.

> >

> > Regards

> > HJR

> > --

> >

> > Oracle Resources : http://www.geocities.com/howardjr2000

> > ========================================

> >

> >

> > "À̱âÅÂ(Kitae Lee)" <kitaelee_at_itnc.co.kr> wrote in message

> > news:0oQB7.111$cI6.156340_at_news.bora.net...

> > > Hi,

> > >

> > > My DB lost current online redo log.

> > >

> > > If "startup" the DB, get message ORA-00333.

> > >

> > > My DB has three redo log groups.

> > >

> > > That redo log is not mirred.

> > >

> > > My system is running in Archive Mode.

> > >

> > > But, I have any cold backups.

> > >

> > > What can I do?

> > >

> > > Help me.

> > >

> > >

> > >

> >

> >

>

>