背景：安装RAC，安装GI集群管理软件时，在最后快结束时，总是报如上INS-错误
#官方文档：error 说明;字符串解析失败
INS-20802: string failed.
Cause: The plug-in failed in its perform method
Action: Refer to the logs or contact Oracle Support Services.
#MOS文档有解释说明
PRVF-4664 PRVF-4657: Found inconsistent name resolution entries for SCAN name (Doc ID 887471.1)
#解释说明
如果主机文件用于解析SCAN主机名，则安装结束时将收到Cluster Verification Utility故障
如果主机文件用于解析SCAN主机名，则安装结束时将收到Cluster Verification Utility故障
###################此报错可忽略#############################
如下：学习MOS文档，解释说明
#PURPOSE 目的
在安装GI、或升级GI时，报错提示INS-20802 while running Oracle Cluster Verification Utility ---
在安装日志中得到显示如下信息： $ORACLE_BASE/oraInventory/logs/installActions{$TIMESTAMP}.log
#执行$ GRID_HOME / bin / cluvfy comp scan ：报错信息类似
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
#原因1：SCAN有本地hosts主机名解析文件
解决：建议使用DNS/ GNS进行SCAN名称解析：因为主机名解析SCAN IP只能解析一个IP地址
#如果确定使用主机名解析一个SCAN IP，则可以忽略
#如果使用DNS/ GNS进行SCAN IP解析：则配置完成后，注释/etc/hosts主机名解析SCAN IP
#原因2：nslookup 无法找到SCAN名称的记录
#确认，重新配置主机名解析文件
#原因3：SCAN名称是DNS中的规范名称：cname记录
nslookup cluscan.us.oracle.com .. cluscan.us。oracle.com canonical name = cluscan.a3。oracle.com 名称：cluscan.a3.oracle.com 地址：10.4.0.201 名称：cluscan.a3.oracle.com 地址：10.4.0.202 名称：cluscan.a3.oracle.com 地址：10.4.0.203
#解决方案：SCAN 将DNS中的SCAN记录更新为A类型，而不是CNAME类型
#原因4： DNS配置正确，但是正在使用其它的命名（nls,ldap）解决方案，SA检查还是认定使用主机名解析SCAN ip
使SA检查名称解析开关配置（Linux，Solaris和/或Linux上的/etc/nsswitch.conf） AIX上的hp-ux或/etc/netsvc.conf）并更正所有节点上的错误配置。nsswitch.conf中的示例主机： hosts：files dns nis 一旦更正，执行“ $ GRID_HOME / bin / cluvfy comp scan ”确认 请注意，在AIX上，netsvc.conf可能有如下条目： hosts =本地，绑定
#原因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 it's corrected, execute "$GRID_HOME/bin/cluvfy comp scan" to confirm.
#正常
What's the expected output when executing nslookup nslookup cluscan.us.oracle.com .. Name: cluscan.us.oracle.com Address: 10.4.0.201 Name: cluscan.us.oracle.com Address: 10.4.0.202 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