oraclebase
commented
1 year ago Hi.
I've never tried this (I don't have a high enough spec PC), but I would expect to do the following.
There are two basic approaches. Add two extra nodes into the existing cluster definition, or just copy the existing definition and make a completely separate cluster. I think the second is the simpler, so that's what I'll describe here.
- Make a copy of the vagrant directory for a second node. So for example I might have these, with all the same config beneath them.
C:\git\oraclebase\vagrant\rac\ol8_19\ C:\git\oraclebase\vagrant\rac\ol8_19b\
-
Amend the VM names, IP addresses and shared disk locations in the "C:\git\oraclebase\vagrant\rac\ol8_19b\config\install.env" file, so they are different to the first RAC cluster.
-
Add the extra IP addresses into the DNS config for each cluster...
-
Build the first RAC cluster as normal.
-
Try to build the second RAC cluster and see what if anything breaks. From there it is a case of identifying issues and fixing them...
Once you've got the second cluster running OK, you can then destroy the database and use that setup to configure the RAC DG setup you want.
Like I said, I've never done this, so I don't know exactly what issues you will encounter...
Cheers
Tim...
Thank you Tim for the excellent work put into developing the ol8-19-rac article.
I was wondering what changes I would need to make if I wanted to spin up a second RAC cluster on the same machine to configure the cluster with a physical standby database. Possibly straight forward, likely not.
Thanks in advance.