Moving 2-node RAC to AWS
From: Sandra Becker <sbecker6925_at_gmail.com>
Date: Thu, 18 Nov 2021 11:59:21 -0700
Message-ID: <CAJzM94A_TLxGhD7-TkOY7+YDzNJTw_4SXExQKkBs-PSPiRWLxA_at_mail.gmail.com>
Current OS: RHEL6
Oracle version: 11g (11.2.0.3 and 11.2.0.4)
Date: Thu, 18 Nov 2021 11:59:21 -0700
Message-ID: <CAJzM94A_TLxGhD7-TkOY7+YDzNJTw_4SXExQKkBs-PSPiRWLxA_at_mail.gmail.com>
Current OS: RHEL6
Oracle version: 11g (11.2.0.3 and 11.2.0.4)
We have started a project to move our 50 or so on-prem RAC databases to AWS EC2 servers. Some use ASM, others do not. (I think the motto of previous
DBAs was "consistency is for the weak.".) We cannot upgrade the databases (or the OS) due to a host of constraints put on us by the applications and stakeholders. Using FlashGrid also is out of the question since it would be an additional software cost.I'm looking for good documents to read/follow that would tell us how to set up ASM on the EC2 instances as well as the best method to move the RAC databases. Has anyone done this that can point me to good documentation? I also have some non-RAC databases to move. I was thinking of creating the standby on the EC2 then doing a switchover during a migration window to minimize downtime. Is this approach feasible? Would another approach be preferable?
Thank you for any suggestions,
-- Sandy B. -- http://www.freelists.org/webpage/oracle-lReceived on Thu Nov 18 2021 - 19:59:21 CET