Re: Restoring & recovering in NOARCHIVELOG

Hi!

I wouldn't say that a production db should never be in noarchivelog. When we look at this from customer money point of view, then if one day of customer's data is less worth than additional disk storage and IO bandwidth for archivelogs - then production database can very well be in noarchivelog mode. I've had several such cases, especially when we are dealing with staging type of databases which can be recreated easily.

Tanel.

"Daniel Roy" <danielroy10junk_at_hotmail.com> wrote in message news:3722db.0307250655.5c526149_at_posting.google.com...
> 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
Received on Fri Jul 25 2003 - 11:30:46 CDT