8i | 9i | 10g | 11g | 12c | 13c | 18c | 19c | Misc | PL/SQL | SQL | RAC | WebLogic | Linux

Home » Misc » Here

Comments for Oracle Database 19c RAC On Oracle Linux 7 Using VirtualBox and Vagrant


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

Tim... said...

Hi.

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.

Cheers

Tim...

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: 10.0.2.3
Address: 10.0.2.3#53
** 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:

more /etc/resolv.conf
options single-request-reopen
; generated by /usr/sbin/dhclient-script
nameserver 10.0.2.3

For now changing the file manually... but would appreciate any suggestions or fix

Tim... said...

Hi.

The solution is add this.

dns=none

To the /etc/NetworkManager/NetworkManager.conf file and restart NetworkManager.

I've amended the build now. Seems fine on restart.

Cheers

Tim...

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.