Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Redo + Archive + Data Layout...
Daniel Morgan wrote:
>>
Hardware mirroring protects against hardware failure; software multiplexing protects against software corruptions and user errors.
If I rm control*, hardware mirroring will not save me, because the rm will be replicated on the mirror. Or if CKPT is updating the controlfile, throws a wobbly, and introduces corruption, that corruption will be mirrored.
Only by making CKPT write to two separate and independent multiplexed versions of your controlfiles can you protect against that sort of error.
Of course, having two multiplexed copies means (maybe) you don't need to bother with the hardware mirroring in the first place. And if money and resources were tight, I'd go for multiplexing over mirroring every time.
But there's one thing hardware mirroring can do for you that Oracle multiplexing doesn't do: splitting mirrors for the taking of backups.
It's also true that in a world of 9 possible archive destinations, 2 control files is not sufficient protection. So why not Oracle-multiplex 3, 4 or more times? Because doing so causes CKPT to write to more files (and LGWR, and other processes), and you've therefore increased Oracle's workload. Having 2 files managed by Oracle, and then mirrored by the hardware, gives you the larger number of files you may require for resilience and peace of mind, without increasing the workload for Oracle unacceptably.
So, if I had the choice, I'd multiplex and then mirror. Best of both worlds.
Regards
HJR
-- -------------------------------------------- See my brand new website, soon to be full of new articles: www.dizwell.com. Nothing much there yet, but give it time!! --------------------------------------------Received on Tue Oct 21 2003 - 05:04:34 CDT