Re: Restoring & recovering in NOARCHIVELOG

You will need to read a bit about database backups and recovery. First, a Production database should never run in NOARCHIVELOG mode! Just put it in ARCHIVELOG mode (with automatic archiving, of course). Then, if you still want to make daily offline backups, go as you do now, but include the archive logs also in your backup. That way, you'll be 100% sure to be able to recover up to the second before any HW failure. Relying on the changes still being in the redo logs is not recommended, secure and supported, even if I might work sometimes. Please read the backup and recovery manuals at tahiti.oracle.com.

Daniel

> 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 - 09:55:54 CDT