Lisa Koch wrote:
I was once Unix admin for a company that did Oracle front-end development. We ran Oracle in NOARCHIVELOG mode too. But we shut it down regularly for cold backups.
If you stop the Oracle "listeners" before your backup and start them again afterward, you can get perfectly useable backups. I have recovered from such backups many times without problems (we were always doing backups and restores during testing). Most backup software can run pre-backup and post-backup scripts, where you can stop and start Oracle processes. Just let your users know that the database is unavailable when the backup is scheduled (usually in the middle of the night). You will only be able to recover data for the time of the last backup, of course.
Congratulations on your lucky recovery! Maybe management will let you improve your chances for the next time by actually backing up your data ...
Cheers, Lisa
On Monday, July 28, 2003, at 05:42 PM, Rick Perron wrote:
We had backups running, that happened to copy the database. But, Oracle needs to be in ARCHIVE mode to safely backup a running database. Even after restoring from tape, Oracle refused to open the database because the datafiles were not in a consistent state. Which was to be expected, (it was running in NOARCHIVELOG mode after all).
Yes, there is a cost to insurance. I have had that conversation with my management. The decisions were made believing we had all the facts.
BUT, somehow we got lucky. Thanks to the fact that this database has lots
of idle time and the backups don't always kick off at the same time, we
had lots of different backups to try to restore from. We got really lucky
and found one that I could get Oracle to recover with the few online redo
logs that were available on tape. Not a supported restore scenario. But,
it worked.
Now we get to see if this close call changes anyone's opinions about buying insurance up front.
--- Send mail for the `bblisa' mailing list to [EMAIL PROTECTED]'. Mail administrative requests to [EMAIL PROTECTED]'.
