Re: Restoring & recovering in NOARCHIVELOG

"Pete's" <empete2000_at_yahoo.com> wrote in message news:6724a51f.0307250439.55e887eb_at_posting.google.com...
> Your are right, but, in order to perform a roll forward, archiving
> must be turned on and you'll have to have all of the archives that

Nope, archiving doesn't definitely have to be turned on. See my other and Quarkman's post.

Tanel.

> were created throughout the day. The size of the redo log does not
> necessarily matter, however, you don't want to be switching logs every
> minute, once every 15min is good.
>
> HTH,
> Pete's
>
> miotromailcarlos_at_netscape.net (Carlos) wrote in message
news:<1de5ebe7.0307250226.22aa87e7_at_posting.google.com>...
> > Hi all.
> >
> > We are working with Oracle 8.1.6 on Win NT in a production environment
> > (don't blame me, It's heritage). The Database archiving mode is
> > NOARCHIVELOG (again don't blame me). We do whole database backups
> > daily al the end of the day (It's not a 24/7 DB). Due to requisites,
> > we must be able to restore the status that the DB had at the beginning
> > of the day (start) in order to reprocess (by external processes) all
> > the activity of the day if necessary (this is easily done by restoring
> > the last-night backup). But I'm wondering about recovering the DB if a
> > HW problem occurs. Here is where my question comes out: If we use redo
> > log files large enough to hold all the redo activities of a whole day
> > we could not only restore the 'last-night cold backup' in order to
> > reprocess, but recover the DB status to the instant before a HW
> > failure as well by using the redo log files to roll forward.
> > Am I right?
> >
> > Thanks in advance.
> >
> > Carlos.
Received on Fri Jul 25 2003 - 08:50:40 CDT