Windows: CLUVFY Fails with TCP Check PRVF-7617 Due to Case of Node Names

(Doc ID 1286394.1)

Last updated on NOVEMBER 02, 2015

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Microsoft Windows x64 (64-bit)
Cluster Verification Utility 11.2.0.1 and higher.

Symptoms

The TCP Connectivity check for CLUVFY Fails with PRVF-7617 when the case of the node names (specified with -n) does not match the case of the hostname as defined at the OS level:


# ./runcluvfy stage -pre crsinst -n node1,node2 -verbose

. . .

Check: TCP connectivity of subnet "10.10.10.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
NODE1:10.10.10.107 node2:10.10.10.111 failed

ERROR:
PRVF-7617 : Node connectivity between "NODE1 : 10.10.10.107" and "node2 : 10.10.10.111" failed
NODE1:10.10.10.107 node1:10.10.10.107 failed

ERROR:
PRVF-7617 : Node connectivity between "NODE1 : 10.10.10.107" and "node1 : 10.10.10.107" failed
Result: TCP connectivity check failed for subnet "10.10.10.0"
. . .


In this case the hostname at the OS level is define in all UPPER case and was specified in lower case when running CLUVFY.

Changes

None.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms