Background: Install RAC, when installing GI cluster management software, at the end of the final, always reported as ins-error
#官方文档: Error description; string parsing failed
INS-20802: string failed.
Cause:the plug-in failed in its perform methodAction: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) #解释说明
If the host file is used to resolve the scan hostname, you will receive a cluster verification utility failure at the end of the installation
################## #此报错可忽略 #############################as follows: Learn MOS documentation, explain#PURPOSE Purposewhen installing GI, or upgrading GI, error message INS-20802 while running Oracle Cluster verification Utility---The following information is displayed in the installation log: $ORACLE _base/orainventory/logs/installactions{$TIMESTAMP}.log#执行
$ grid_home/bin/cluvfy Comp Scan : Error message similar
Info:prvg-1101:scan name "cluscan.us.oracle.com" failed to resolveinfo: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 "SC ANCLUNM "(IP address:10.4.0.202) failedorprcs-1016:failed to resolve single Client Access Name cluscan.us.oracle.com
#原因1: Scan has local hosts hostname resolution fileWorkaround: It is recommended to use dns/gns for Scan name resolution: Because the host name resolution scan IP can only resolve one IP address#如果确定使用主机名解析一个SCAN IP, you can ignore theScan IP Resolution #如果使用DNS/gns: After the configuration is complete, the comment/etc/hosts hostname resolves the scan IP#原因2: nslookup cannot find record for scan name#确认, reconfigure the host name resolution file #原因3: Scan name is the canonical name in DNS: CNAME record
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
#解决方案: Scan updates the scan record in DNS to type A, not the CNAME type
#原因4: DNS is configured correctly, but other named (NLS,LDAP) solutions are being used, SA check still determines that the scan IP is resolved using host name
Make the SA check the name resolution switch configuration (Linux,solaris and/or/etc/nsswitch.conf on Linux) for HP-UX or/etc/netsvc.conf on AIX, and correct the misconfiguration on all nodes. Example host in nsswitch.conf: Hosts:files DNS NIS once corrected, perform "$ grid_home/bin/cluvfy Comp Scan" Confirmation please note that on AIX, netsvc.conf may have the following entry: Host s = local, bound
#原因5: Persistent cache for NSCD have incorrect information.
Solution:engage SA to restart NSCD and clear persistent caches on all nodes. Example on linux#/sbin/service nscd restart#/usr/sbin/nscd--invalidate=hostsonce It ' s corrected, execute "$GRID _home/b In/cluvfy Comp Scan "to confirm.
#正常
What's the expected output when executing nslookupnslookup cluscan.us.oracle.com. Name:cluscan.us.oracle.comaddress:10.4.0.201name:cluscan.us.oracle.comaddress:10.4.0.202name:cluscan.us.oracle . comaddress:10.4.0.203ping-c 1 Cluscan.us.oracle.comPING cluscan.us.oracle.com (10.4.0.201) bytes of data.64 byt Es 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 0msrtt Min/avg/max/mdev = 0.258/0.258/0.258/0.000 msping-c 1 clusc An.us.oracle.comPING cluscan.us.oracle.com (10.4.0.202) (+) 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 0msrtt Min/avg/max/mdev = 0.258/0.258/0.258/0.000 msping-c 1 Cluscan.us.oracle.comPING cluscan.us. Oracle.com (10.4.0.203) (+) 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 R Eceived, 0% packet loss, time 0msrtt Min/avg/max/mdev = 0.258/0.258/0.258/0.000 Msfrom above you can see:1. nslookup Returning proper SCAN name and IPs 2. Ping to SCAN name are Round Robin resolved to different IPs each time by dnsif you see different behaviour than above, pleas E Engage SA to Investigate.------------------------------------------------------------------------------------------------------------ Ping Command Reference Linux:/bin/ping-c 1 cluscan.us.oracle.comSolaris:/usr/sbin/ping-s cluscan.us.oracl e.com 1hp-ux:/usr/sbin/ping cluscan.us.oracle.com-n 1AIX:/usr/sbin/ping-c 1 cluscan.us.oracle.comWi Ndows:ping-n 1 cluscan.us.oracle.com
INS-20802 Oracle Cluster Verification Utility failed explanatory notes