|
Hrrrmm
- well, we've never seen the problem you describe, and we've got a pretty big
RAC environment here (clusters from two to six nodes, and we combine dev
clusters to build bigger ones as we need). What the situation you describe
sounds like is what happens when there's interconnect failure. Each node
thinks independently that its been separated from the rest of the cluster and
(effectively) shoots itself in the head. This causes every instance to
hang. This is why the crafty RAC Jedi designs well their interconnect
architecture.
But
yes, if you're willing to take the "completely 2n capacity" cluster route and
have two databases, double the oracle licenses, two storage arrays, two fibre
channel networks, etc. , that is the highest availability/reliability
cluster you can have - although at the highest cost and
complexity.
Which
clustering solution is right for you? Cheap and inelegant? Expensive
and bullet-proof? Well, that's why we get paid the big bucks, right?
:)
Thanks,
Matt
--
|
Title: Message
- Re: clustering Ron Rogers
- RE: clustering Matthew Zito
- Re: clustering AK
- Re: clustering Indy Johal
- RE: clustering Matthew Zito
- Re: clustering Indy Johal
- RE: clustering Jesse, Rich
- Re: clustering Tanel Poder
- RE: clustering Jamadagni, Rajendra
- Re: clustering Hemant K Chitale
- RE: clustering Matthew Zito
- RE: clustering Balakrishnan, Ashok - VSCM
- RE: clustering Jamadagni, Rajendra
- RE: clustering Loughmiller, Greg
- RE: clustering Ron Yount
- Re: clustering Tanel Poder
- Re: clustering Hemant K Chitale
