Oracle Grid Infrastructure on Windows 2012 (R2): 'ping <hostname>' Resolving to VIP or SCAN IP Address Instead of Public IP Address
(Doc ID 1664001.1)
Last updated on FEBRUARY 18, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Microsoft Windows x64 (64-bit)
Symptoms
Following successful Oracle Grid Infrastructure (11.2.0.4) install on a RAC on Windows 2012 cluster, ping <hostname> of each node to itself resolves to the VIP IP address instead of the public IP address. When Grid Infrastructure is stopped, ping <hostname> of each node to itself resolves to the public IP address (as expected).
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| Community Discussions |
| References |