Re: Moving 2-node RAC to AWS

From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Fri, 19 Nov 2021 13:31:20 -0600
Message-ID: <CAJvnOJbJOT_VV9uxqzh9tT_CLO-CVZHMzLVgP0JXbhghOwtbWA_at_mail.gmail.com>



The question I always ask in this situation is why they are using RAC. If its for scaling, an EC2 instance can scale up very big, and there is a decent chance it can scale big enough for your load. Yes, I know there are exceptions and some places really need those 8 node x 60 core exadata clusters, but many people dont need anything near that big, but still use RAC for scaling. If its for HA, dataguard can come pretty close with about a 5 minute switchover. And when it comes down to it, you are paying the cloud service provider to keep your host up, so why do you want to RAC for HA?

On Fri, Nov 19, 2021 at 1:25 PM Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

>
> On 11/19/21 12:38, niall.litchfield_at_gmail.com wrote:
> > I'd love to know how those constraints are articulated. As you've
> > discovered RAC is not supported on EC2, and indeed isn't even
> > implementable without additional software
>
>
> It is also possible to use NFS3 for RAC. FlashGrid is not necessary.
> However, it would require 3 nodes, not 2. The 3rd node would have to be
> the NFS server.
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217
> https://dbwhisperer.wordpress.com
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Nov 19 2021 - 20:31:20 CET

Original text of this message