Duplicate VIP or SCAN VIP or SCAN Listener Found on More than 1 Node in a RAC Cluster
Last updated on FEBRUARY 06, 2018
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
Duplicate IP for host VIP or SCAN VIP or SCAN listener found on more than 1 node in the cluster after a failover or CRS restart. In other words, the IP for the host VIP or SCAN VIP is not unplumbed from the network of its original node, causing client connection problem when that particular VIP or SCAN VIP is used.
In this sample, it is 2 node RAC cluster,
16:21:51 CSSD on node racnode02 shutdown by user.
CRS could not start properly due to ASM issue until
17:48:27 CSSD Reconfiguration complete. Active nodes are racnode01 racnode02 .
17:57:03 CRSD started on node racnode02
18:27:29 CSSD on node racnode01 shutdown by user
18:28:40 CSSD Reconfiguration complete. Active nodes are racnode01 racnode02
18:29:03 CRSD started on node racnode01
After this, racnode02-vip shows ONLINE on node 2, but its IP is binded on both nodes, its IP was not unplumbed from node 1:
racnode01-vip is 10.10.15.19
racnode02-vip is 10.10.15.20
Node 1 racnode01 ifconfig output
Above sample show host VIP racnode02-vip 10.10.15.20 is plumbed on both nodes. This problem could also happen to SCAN VIP. The scenario leading to this situation could be different, but usually there is CRS restart involved. Also there could be duplicate listener or listener_scan<x> seen on different cluster nodes.
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