Problem Description

After Oracle RAC is deployed, the CRS log reports an error.

Alarm Information

** 英文 error: **
PRVG-1101 : SCAN name "rac-scan" could not be resolved
PRVF-4657 : Name resolution settings check failed for "rac-scan" (IP address: 192.168.245.189)
PRVF-4664 : Found inconsistent name resolution entries for SCAN name "rac-scan"

** English error: **
PRVG-1101 : SCAN name "cluster-scan.oracle.com" failed to resolve
PRVF-4664 : Found inconsistent name resolution entries for SCAN name "cluster-scan.oracle.com"
PRVF-4657 : Name resolution setup check for "cluster-scan" (IP address: 10.x.x.202) failed

Process –

1. Use the local host to interpret the address and ensure that SCANIP can be pinged, then it can be used normally.
2. Use the DNS server to resolve the problem.

Root Cause

See solution.

Solution

Reason 1: SCAN name should be resolved by local hosts file
SCAN names are resolved by the local hosts file (/etc/hosts or %SystemRoot%\system32\drivers\etc\hosts) instead of DNS or GNS

Solution: Oracle recommends using DNS or GNS for SCAN name resolution because Node hosts file only supports one IP for SCAN. If you intend to use the hosts file for SCAN name resolution and the ping command returns the correct SCAN VIP, you can ignore the error and move forward.
If you intend to use DNS or GNS for SCAN name resolution, comment out the entry for the SCAN name on all nodes in the local node and re-run "$GRID_HOME/bin/cluvfy comp scan" to confirm.

Reason 2: nslookup cannot find the record for the SCAN name:
nslookup rac-scan.oracle.com
..
**Server cannot find server.com: NXDOMAIN

Solution: Have your System admin (SA) check the resolver configuration (/etc/resolv.conf on Linux/UNIX), correct any misconfiguration on all node and re-run " $GRID_HOME/bin/cluvfy comp scan " to confirm.

Reason 3: The SCAN name is the canonical name in DNS (CNAME record)
nslookup rac-scan.oracle.com
..
rac-scan Canonical Name = rac-scan.a3.oracle.com
Name: rac-scan.**a3.**oracle.com
Address: 192.168.245.189
Name: rac-scan.a3.oracle.com
Address: 192.168.245.190
Name: rac-scan.a3.oracle.com
Address: 192.168.245.191

Solution: Update the SCAN record in DNS to be of type A instead of CNAME using SA.

Reason 4: DNS is correctly configured in DNS, but other naming resolution is being used (nis, ldap..) and does not have the correct SCAN information

Solution: Use SA to check the name resolution switch configuration (Linux, Solaris, and /etc/nsswitch.conf) and correct any misconfigurations on all nodes. Example hosts in nsswitch.conf:
hosts:file dns nis
Once corrected, execute "$GRID_HOME/bin/cluvfy comp scan" to confirm

**Cause 5: nscd's persistent cache has incorrect information. **
Solution: Launch SA to restart nscd and clear the persistent cache node all nodes. Example on Linux

/sbin/service nscd restart

/usr/sbin/nscd –invalidate=hosts

Once corrected, execute " $GRID_HOME/bin/cluvfy comp scan " to confirm.

Suggestions and Summary

When using scripts to automatically deploy Oracle RAC, the local hosts file is used to resolve the VIP address. Refer to reason 1. If the user has set up a DNS server, refer to reasons 2-5.

Original Link

https://support.sangfor.com.cn/cases/list?product_id=33&type=1&category_id=15813&isOpen=true