Hi,
Tnanks for the answer.
For the time being, my purpose through this post is to "test" the Oracle Grid Infrastructure for Oracle 19c RAC.
Thanks for your post, I will read it.
I will come back to it here or through your page.
In the meantime I have errors from the check-step just posted below that I would like to solve.
Yes, there is a ssh_setup.sh script, I ran it before to run the Installer, and anyway the does the chech at a given momen.
I got no error with the ssh configuration.
In the meantime I went a little bit further.
I disabled the firewall and stopped the iptables, and I could go on with the installation (maybe not the best option).
But I got errors with the checks.
I post here only the ones I could not solve.
1) resolv.conf Integrity
2) DNS/NIS name service
Here the content:
---
1) resolv.conf Integrity
resolv.conf Integrity - This task checks consistency of the /etc/resolv.conf across nodes.
Check failed on nodes oel764-oraracn1, oel764-oraracn2
Verification result of failed node: oel764-oraracn2
Details:
- PRVF-5636: The DNS response time for an unreachable node exceeded "15000" ms on following nodes:
oel764-oraracn1, oel764-oraracn2
- Cause: The DNS response time for an unreachable node exceeded the value specified on nodes spcified.
- Action: Make sute that "option timeout", "option attempts" and "nameserver" entries in the /etc/resolv.con are proper.
On HPUX these entries will be "retrans". "retry" and "nameserver".
On Solaris these will be "option retrans", "option retry" and "nameserver".
Make sure that the DNS server responds back to name lookup request within the specified time when looking upt to an unknown host name.
Verification result of failed node: oel764-oraracn1
Details:
- PRVF-5636: The DNS response time for an unreachable node exceeded "15000" ms on following nodes:
oel764-oraracn2, oel764-oraracn1
- Cause: The DNS response time for an unreachable node exceeded the value specified on nodes spcified.
- Action: Make sute that "option timeout", "option attempts" and "nameserver" entries in the /etc/resolv.con are proper.
On HPUX these entries will be "retrans". "retry" and "nameserver".
On Solaris these will be "option retrans", "option retry" and "nameserver".
Make sure that the DNS server responds back to name lookup request within the specified time when looking upt to an unknown host name.
2) DNS/NIS name service
DNS/NIS name service - This test verifies that the Name Service lookups for teh Distributed Name Server (DNS)
and the Network Information Service (NIS) match the SCAN name entries.
Error:
- PRVG-11826: DNS resolved IP addresses "for SCAN name "oel764-orarac-scan" not found in the name service returned IP addesses "192.168.1.160"".
- Cause: The name resolution setup check for the indicated SCAN name failed because one or mroe of the indicated IP addresses otained from
DNS could not be found in the IP addresses obtained from the name service on the system as configured in "/etc/nsswitch.conf" configuration file.
- Action: Make sure all DNS resolved IP addresses are present in the IP addresses obtained from the name service on the system
as configurd in the "/etc/nsswitch.conf" configuration file by reconfiguring the "/etc/nsswitch.conf" for the indicated SCAN name.
Check the Name Service Cache Daemon (/usr/sbin/nscd) by clearing its cache and restartinig it.
- PRVG-11827: Name service returned IP addresses "192.168.1.160" for SCAN name "oel764-orarac-scan" not found in the DNS returned IP addresss.
Cause: The name resolution setup check for the indicated SCAN name failed because one or mroe of the indicated IP addresses otained from
DNS could not be found in the IP addresses obtained from the name service on the system as configured in "/etc/nsswitch.conf" configuration file.
- Action: Make sure all name service resolved IP addresses obtained obtained from the "/etc/nsswitch.conf" configuration file are present in the DNS
resolved IP addresses by reconfiguring "/etc/nsswitch.conf" configuration file for the indicated SCAN name.
Check the Name Service Cache Daemon (/usr/sbin/nscd) by clearing its cache and restartinig it.
---
It seems to be DNS server issue.
I understood from you that a DNS server is not a strict necessity.
Did I understand wrong maybe?
How can I solve these errors?
Any ideas about what the problem could be?
Kind regards