Anonymous said...Thanks for wonderful article.I noticed that scan ip addresses missing on both nodes except dns.After adding scan address on both nodes I was able to connect RAC remotely.
Anonymous said...Adding this line "sh /vagrant_script/configure_hosts_scan.sh" in root_setup.sh in scripts folder on all nodes will add scan ip address to /etc/hosts
Anonymous said...correction Adding this line "sh /vagrant_scripts/configure_hosts_scan.sh" in root_setup.sh in scripts folder on all nodes will add scan ip address to /etc/hosts
You really don't want to put the SCAN IP into the node1 and node2 "/etc/hosts" file. These hosts are resolved using the DNS, not the hosts file.
They are included in the DNS, as they are read by Dnsmasq. This configuration is done by design.
Mike N said...Tim,
First of all thank you for the great article. One observation regarding scan resolution. I had noticed that after first re-boot (vagrant halt/vagrant up) of node1 and node2, DNS resolution becomes broken. Here is nslookup output that I am getting:
$ nslookup ol7-19-scan
** server can't find ol7-19-scan: NXDOMAIN
Bike N said...Cont...
I found that on all servers /etc/resolv.conf gets updated from DNS server address 192.168.56.100 to 10.0.2.3.
There is a comment in resolv.conf file:
; generated by /usr/sbin/dhclient-script
Is that part of NetworkManager?
Mike N said...Cont...
I tried to disable NetworkManager, however after next reboot still got /etc/resolv.conf changed:
; generated by /usr/sbin/dhclient-script
For now changing the file manually... but would appreciate any suggestions or fix
The solution is add this.
To the /etc/NetworkManager/NetworkManager.conf file and restart NetworkManager.
I've amended the build now. Seems fine on restart.
Carl said...Hi Tim,
Excellent site. Thanks for all your hard work on another great article.
For comparison I'm also looking at the Oracle provided vagrant builds on github under oracle/vagrant-boxes/OracleRAC/
I can see that your builds include a DNS, do you know of anything else which is significantly different?
I don't really look at the Oracle Vagrant or Docker builds. I write these for fun and as a learning experience, so I'm not really looking at other people's stuff. I'm sure there are lots of differences, as everyone does stuff differently. :)
Olivier said...Hi Tim,
Thanks a lot very clear and perfectly working :)
If I want to have standard DATA/RECO/OCR+VOTING i guess i have to modify shell scripts and Grid Response file parameters ?
Yep. I keep meaning to alter the disks to be a bit more standard. I'm sure I'll get round to it some day. :)
It you have already modified your scripts for standard DiskGroups :)
Could you please add 2 optional nodes so that we can build a standby RAC ?
Many thanks !
It's not really practical for a "laptop build". Most people complain about the amount of resources for a regular RAC build, let alone adding a standby.
Olivier said...Tim, That would just be optional :)
Have 64gigs of mem and 16 threads.
I managed to add a second standby cluster but with dirty modifications :(
Olivier said...Anyway Tim,
I take it as a good exercise to learn vagrant :)
Clean customization in good progress on my side for the addition of Standby Cluster.
Thanks a lot for this very nice stuff !
to echo others - thanks again for your work on this.
I was trying to get two suites installed of RAC 19c.
I installed the first 100% OK.
Then I tried a second install.
I assumed, incorrectly it seems, that if I just changed all references I could find for servers and directories it would work.
It doesn't - says already provisioned
any ideas ?
Sorry. I don't understand what you are asking. "two suites"?
Anonymous said...Sorry I wasnt clear
one suite = one up and running a 2 node RAC system & 1 DNS server using the ol7_19 directory you provided.
I want to install another RAC system ( 2 node & 1 DNS ) with different host names without losing the first in virtualbox setup.
Oh. OK. Take a copy of the whole directory and call it something different. Make sure you remove the ".vagrant" directory before attempting to start it. Enter the new details in the shared config files. Remember to amend the values in both the vagrant YAML file and the env file for the build. I suspect you left the .vagrant directory intact, which was the problem. :)
Alberto Gonzalez said...Thanks so much for this awesome setup, it saved me a lot of hours!
Anonymous said...Seems like the link to this image referenced from this page is broken: src="/articles/rac/images/common_rac_images/virtual-rac.jpg"
It looks fine to me. Perhaps there was a "glitch in the matrix" when you requested the page.
My humble idea is port 1521 is forwarded for Adapter 1 but both local and remote listener listen for Adapter2 and Adapter2 is internal network
default: Adapter 1: nat
default: Adapter 2: intnet
default: 1521 (guest) => 1521 (host) (adapter 1)
default: 5500 (guest) => 5500 (host) (adapter 1)
default: 22 (guest) => 2200 (host) (adapter 1)
Anonymous said...Sorry. The first part of the message: Thank you for the great work. I run it on windows 10. Able to ssh from the host bet I cannot reach 1521 via sqldevelepor from the host.
Status : Failure -Test failed: G/Ç Hatası: An established connection was aborted by the software in your host machine, Authentication lapse 0 ms.
Listening Endpoints Summary...
So, is it intentional not to let the host machine reach to the database or did I do something wrong in the installation.
2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute eth0
3: eth1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet 192.168.56.101/24 brd 192.168.56.255 scope globa
I've created a new listener on 10.0.2.15 port 1521 and connected successfully
yet this is very dirty solution :)
The networks are private. If you want them available from your PC change the public IP address config from this.
config.vm.network "private_network", ip: var_public_ip, virtualbox__intnet: "public"
config.vm.network "private_network", ip: var_public_ip
This changes it from a private network to a default host-only network. That should then be accessible from your PC directly.
Anonymous said...Thank you.
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.