PRVG-1101 PRVF-4664 PRVF-4657
2023-09-14 08:59:39 时间
PRVG-1101 : SCAN name "scan" failed to resolve
SCAN Name IP Address Status Comment
------------ ------------------------ ------------------------ ----------
scan 172.16.15.100 failed NIS Entry
ERROR:
PRVF-4657 : Name resolution setup check for "scan" (IP address: 172.16.15.100) failed
ERROR:
PRVF-4664 : Found inconsistent name resolution entries for SCAN name "scan"
Verification of SCAN VIP and Listener setup failed
[grid@opendb-401~]$ less /disk/grid/oraInventory/logs/installActions2013-10-11_11-06-08AM.log
INFO:TCP connectivity to SCAN Listeners exists on all cluster nodes
INFO:Checking name resolution setup for "rac-cluster-scan"...
INFO:ERROR:
INFO:PRVG-1101 : SCAN name "rac-cluster-scan" failed to resolve
INFO:ERROR:
INFO:PRVF-4657 : Name resolution setup check for "rac-cluster-scan" (IPaddress: 172.17.202.5) failed
INFO:ERROR:
INFO:PRVF-4664 : Found inconsistent name resolution entries for SCAN name"rac-cluster-scan"
INFO:Verification of SCAN VIP and Listener setup failed
到这里，就完成了grid的安装。
Applies to: Oracle Server - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
Purpose runInstaller (OUI) reports INS-20802 while running Oracle Cluster Verification Utility post check after successful 11gR2 Grid Infrastructure clusterware (CRS) installation or upgrade:
Installation log - $ORACLE_BASE/oraInventory/logs/installActions{$TIMESTAMP}.log INFO: PRVG-1101 : SCAN name "cluscan.us.oracle.com" failed to resolve
INFO: ERROR:
INFO: PRVF-4664 : Found inconsistent name resolution entries for SCAN name "cluscan.us.oracle.com"
INFO: ERROR:
INFO: PRVF-4657 : Name resolution setup check for "scanclunm" (IP address: 10.4.0.202) failed
OR
PRCS-1016 : Failed to resolve Single Client Access Name cluscan.us.oracle.com
If "$GRID_HOME/bin/cluvfy comp scan" is executed, similar message will be reported. Details Cause 1. SCAN name is expected to be resolved by local hosts file SCAN name is resolved by local hosts file (/etc/hosts or %SystemRoot%\system32\drivers\etc\hosts) instead of DNS or GNS Solution: Oracle strongly recommend to use DNS or GNS for SCAN name resolution as hosts file support only one IP for SCAN If the intention is to use hosts file for SCAN name resolution, and ping command returns correct SCAN VIP, you can ignore the error and move forward. If the intention is to use DNS or GNS for SCAN name resolution, comment out entries in local hosts file for SCAN name on all nodes, and re-run "$GRID_HOME/bin/cluvfy comp scan" to confirm. Cause 2. nslookup fails to find record for SCAN name:
Solution: Engage System Administrator(SA) to check resolver configuration (/etc/resolv.conf on Linux/UNIX), correct any misconfiguration on all nodes and re-run "$GRID_HOME/bin/cluvfy comp scan" to confirm.
Cause 3. SCAN name is canonical name(CNAME record) in DNS
nslookup cluscan.us.oracle.com
..
cluscan.us.oracle.com canonical name = cluscan.a3.oracle.com
Name: cluscan.a3.oracle.com
Address: 10.4.0.201
Name: cluscan.a3.oracle.com
Address: 10.4.0.202
Name: cluscan.a3.oracle.com
Address: 10.4.0.203
Solution: Engage SA to update SCAN record in DNS to A type instead of CNAME type.
Cause 4. DNS is configured properly in DNS but other naming resolution(nis, ldap..) is being used and doesnt have proper SCAN info
Solution: Engage SA to check name resolution switch configuration (/etc/nsswitch.conf on Linux, Solaris and hp-ux or /etc/netsvc.conf on AIX) and correct any misconfiguration on all nodes. Example hosts in nsswitch.conf: hosts: files dns nis Once its corrected, execute "$GRID_HOME/bin/cluvfy comp scan" to confirm
Cause 5. Persistent cache for nscd has incorrect information.
Solution: Engage SA to restart nscd and clear persistent cache on all nodes. Example on Linux # /sbin/service nscd restart
# /usr/sbin/nscd --invalidate=hosts Once its corrected, execute "$GRID_HOME/bin/cluvfy comp scan" to confirm. ------------------------------------------------------------------------------------------------------------ Whats the expected output when executing nslookup
Name: cluscan.us.oracle.com
Address: 10.4.0.203
ping -c 1 cluscan.us.oracle.com
PING cluscan.us.oracle.com (10.4.0.201) 56(84) bytes of data.
64 bytes from cluscan.us.oracle.com (10.4.0.201): icmp_seq=1 ttl=64 time=0.258 ms
--- cluscan.us.oracle.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms
ping -c 1 cluscan.us.oracle.com
PING cluscan.us.oracle.com (10.4.0.202) 56(84) bytes of data.
64 bytes from cluscan.us.oracle.com (10.4.0.202): icmp_seq=1 ttl=64 time=0.258 ms
--- cluscan.us.oracle.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms
ping -c 1 cluscan.us.oracle.com
PING cluscan.us.oracle.com (10.4.0.203) 56(84) bytes of data.
64 bytes from cluscan.us.oracle.com (10.4.0.203): icmp_seq=1 ttl=64 time=0.258 ms
--- cluscan.us.oracle.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms From above you can see:
1. nslookup is returning proper SCAN name and IPs
2. ping to SCAN name is Round Robin resolved to different IP each time by DNS
If you see different behaviour than above, please engage SA to investigate.
------------------------------------------------------------------------------------------------------------ Ping command reference Linux: /bin/ping -c 1 cluscan.us.oracle.com
Solaris: /usr/sbin/ping -s cluscan.us.oracle.com 1500 1
hp-ux: /usr/sbin/ping cluscan.us.oracle.com -n 1
AIX: /usr/sbin/ping -c 1 cluscan.us.oracle.com
Windows: ping -n 1 cluscan.us.oracle.com ------------------------------------------------------------------------------------------------------------
References BUG:8901977 - CLUVFY PRVF-4664 : FOUND INCONSISTENT NAME RESOLUTION ENTRIES FOR SCAN NAME
NOTE:887522.1 - 11gR2 Grid Infrastructure Single Client Access Name (SCAN) Explained
WARNING: POSSIBLE DNS SPOOFING DETECTED! 在 win10 系统中，首次提交项目代码到公司内部 GitLab 远程仓库，出现 WARNING: POSSIBLE DNS SPOOFING DETECTED! 错误，如上图 因为我们的远程仓库是没问题的，在Ubuntu系统里日常代码提交都正常，根据错误描述提示，分析应该是 known_hosts 文件中的内容 [git.sg-ai.com]:2289 改变导致.
ORA-00600 qosdExpStatRead expcnt mismatch Oracle 12.2.0.1最近出现了ORA--0600错误，其详细信息如下: ORA-00600: 内部错误代码, 参数: [qosdExpStatRead: expcnt mismatch], [], [], [], [], [], [], [], [], [], [], []ORA-06512: 在 SYS.
提示是不能获取本地节点名。 PRVF意思应是安装前的检查，没有查出缩写，我猜是Pre-Requisite VeriFication的缩写。
[grid@opendb-401~]$ less /disk/grid/oraInventory/logs/installActions2013-10-11_11-06-08AM.log
INFO:TCP connectivity to SCAN Listeners exists on all cluster nodes
INFO:Checking name resolution setup for "rac-cluster-scan"...
INFO:ERROR:
INFO:PRVG-1101 : SCAN name "rac-cluster-scan" failed to resolve
INFO:ERROR:
INFO:PRVF-4657 : Name resolution setup check for "rac-cluster-scan" (IPaddress: 172.17.202.5) failed
INFO:ERROR:
INFO:PRVF-4664 : Found inconsistent name resolution entries for SCAN name"rac-cluster-scan"
INFO:Verification of SCAN VIP and Listener setup failed
到这里，就完成了grid的安装。
Applies to: Oracle Server - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
Purpose runInstaller (OUI) reports INS-20802 while running Oracle Cluster Verification Utility post check after successful 11gR2 Grid Infrastructure clusterware (CRS) installation or upgrade:
Installation log - $ORACLE_BASE/oraInventory/logs/installActions{$TIMESTAMP}.log INFO: PRVG-1101 : SCAN name "cluscan.us.oracle.com" failed to resolve
INFO: ERROR:
INFO: PRVF-4664 : Found inconsistent name resolution entries for SCAN name "cluscan.us.oracle.com"
INFO: ERROR:
INFO: PRVF-4657 : Name resolution setup check for "scanclunm" (IP address: 10.4.0.202) failed
OR
PRCS-1016 : Failed to resolve Single Client Access Name cluscan.us.oracle.com
If "$GRID_HOME/bin/cluvfy comp scan" is executed, similar message will be reported. Details Cause 1. SCAN name is expected to be resolved by local hosts file SCAN name is resolved by local hosts file (/etc/hosts or %SystemRoot%\system32\drivers\etc\hosts) instead of DNS or GNS Solution: Oracle strongly recommend to use DNS or GNS for SCAN name resolution as hosts file support only one IP for SCAN If the intention is to use hosts file for SCAN name resolution, and ping command returns correct SCAN VIP, you can ignore the error and move forward. If the intention is to use DNS or GNS for SCAN name resolution, comment out entries in local hosts file for SCAN name on all nodes, and re-run "$GRID_HOME/bin/cluvfy comp scan" to confirm. Cause 2. nslookup fails to find record for SCAN name:
Solution: Engage System Administrator(SA) to check resolver configuration (/etc/resolv.conf on Linux/UNIX), correct any misconfiguration on all nodes and re-run "$GRID_HOME/bin/cluvfy comp scan" to confirm.
Cause 3. SCAN name is canonical name(CNAME record) in DNS
nslookup cluscan.us.oracle.com
..
cluscan.us.oracle.com canonical name = cluscan.a3.oracle.com
Name: cluscan.a3.oracle.com
Address: 10.4.0.201
Name: cluscan.a3.oracle.com
Address: 10.4.0.202
Name: cluscan.a3.oracle.com
Address: 10.4.0.203
Solution: Engage SA to update SCAN record in DNS to A type instead of CNAME type.
Cause 4. DNS is configured properly in DNS but other naming resolution(nis, ldap..) is being used and doesnt have proper SCAN info
Solution: Engage SA to check name resolution switch configuration (/etc/nsswitch.conf on Linux, Solaris and hp-ux or /etc/netsvc.conf on AIX) and correct any misconfiguration on all nodes. Example hosts in nsswitch.conf: hosts: files dns nis Once its corrected, execute "$GRID_HOME/bin/cluvfy comp scan" to confirm
Cause 5. Persistent cache for nscd has incorrect information.
Solution: Engage SA to restart nscd and clear persistent cache on all nodes. Example on Linux # /sbin/service nscd restart
# /usr/sbin/nscd --invalidate=hosts Once its corrected, execute "$GRID_HOME/bin/cluvfy comp scan" to confirm. ------------------------------------------------------------------------------------------------------------ Whats the expected output when executing nslookup
Name: cluscan.us.oracle.com
Address: 10.4.0.203
ping -c 1 cluscan.us.oracle.com
PING cluscan.us.oracle.com (10.4.0.201) 56(84) bytes of data.
64 bytes from cluscan.us.oracle.com (10.4.0.201): icmp_seq=1 ttl=64 time=0.258 ms
--- cluscan.us.oracle.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms
ping -c 1 cluscan.us.oracle.com
PING cluscan.us.oracle.com (10.4.0.202) 56(84) bytes of data.
64 bytes from cluscan.us.oracle.com (10.4.0.202): icmp_seq=1 ttl=64 time=0.258 ms
--- cluscan.us.oracle.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms
ping -c 1 cluscan.us.oracle.com
PING cluscan.us.oracle.com (10.4.0.203) 56(84) bytes of data.
64 bytes from cluscan.us.oracle.com (10.4.0.203): icmp_seq=1 ttl=64 time=0.258 ms
--- cluscan.us.oracle.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms From above you can see:
1. nslookup is returning proper SCAN name and IPs
2. ping to SCAN name is Round Robin resolved to different IP each time by DNS
If you see different behaviour than above, please engage SA to investigate.
------------------------------------------------------------------------------------------------------------ Ping command reference Linux: /bin/ping -c 1 cluscan.us.oracle.com
Solaris: /usr/sbin/ping -s cluscan.us.oracle.com 1500 1
hp-ux: /usr/sbin/ping cluscan.us.oracle.com -n 1
AIX: /usr/sbin/ping -c 1 cluscan.us.oracle.com
Windows: ping -n 1 cluscan.us.oracle.com ------------------------------------------------------------------------------------------------------------
References BUG:8901977 - CLUVFY PRVF-4664 : FOUND INCONSISTENT NAME RESOLUTION ENTRIES FOR SCAN NAME
NOTE:887522.1 - 11gR2 Grid Infrastructure Single Client Access Name (SCAN) Explained
WARNING: POSSIBLE DNS SPOOFING DETECTED! 在 win10 系统中，首次提交项目代码到公司内部 GitLab 远程仓库，出现 WARNING: POSSIBLE DNS SPOOFING DETECTED! 错误，如上图 因为我们的远程仓库是没问题的，在Ubuntu系统里日常代码提交都正常，根据错误描述提示，分析应该是 known_hosts 文件中的内容 [git.sg-ai.com]:2289 改变导致.
ORA-00600 qosdExpStatRead expcnt mismatch Oracle 12.2.0.1最近出现了ORA--0600错误，其详细信息如下: ORA-00600: 内部错误代码, 参数: [qosdExpStatRead: expcnt mismatch], [], [], [], [], [], [], [], [], [], [], []ORA-06512: 在 SYS.
提示是不能获取本地节点名。 PRVF意思应是安装前的检查，没有查出缩写，我猜是Pre-Requisite VeriFication的缩写。