Re: Shutdown Immediate Command

raas.no_spam_at_interware.hu wrote:
> With shutdown abort, you lose the redundancy in having commited
> transactions both in (archive) logs and in the database files. Imagine
> some disks failing.

Ah, at last, a technical argument instead of a political/fear-based one. Your point is an important one, but this is why most people "multiplex' their redologs. In the very unlikely event that you lose a redo disk between the time you shutdown abort and start up, crash recovery will just use one of the other log group members. Note that your argument requires an exceedingly unlikely (but still possible) problem: a disk failure duing a brief time interval (between shutdwn and startup), with no multiplexed redologs. With multiple members per redolog group, there should be no problem using shutdown abort, even if a disk containing one of the log members is lost in the intervening moments.

Thank you for a logical response, though. Everyone else just says, "cuz Oracle sez."

--
Jeremiah


Sent via Deja.com
http://www.deja.com/