Windows RAC : Connecting VIP times out after VIP is failbacked
(Doc ID 2759938.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]Oracle Database - Standard Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Microsoft Windows x64 (64-bit)
Symptoms
The client that belongs on different network segment with DB Server can not connect the vip after the vip is failed over.
This problem occurs only after the PUBLIC LAN is unplugged and plugged.
This problem does not occur when restarting the GI or OS, disabling or enabling the PUBLIC LAN.
You can confirm the VIP address on both nodes with "netsh interface ipv4 show ipaddresses" after the VIP failover occurs.
The problem is that even if the VIP failover to node2, the IP remains on node1.
＜Node1＞
Therefore, after the VIP fails back to node 1, the OS will not call GARP because the IP remains.
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 |
| Cause |
| Solution |