--
"Carlos" <miotromailcarlos_at_netscape.net> 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
Ok, I don't blame you :)
Just a thought/suggestion (hope I am not repeating what someone else might
have already said - don't have time to read the whole thread)...
To have this "potential option" of recovery, I would also suggest creating a
LOT of redo groups so that Oracle doesn't "wrap around" and overlay the 1st
one too soon. You might actually get lucky most of the time and actually
have "the potential option" of recovering with no data loss.
If you are at least placing the REDO logs on separate disk drives, as large
as disk systems are these days, you should have plenty of room for a lot of
groups.
> 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 Sun Jul 27 2003 - 22:54:11 CDT
