Exadata: 12cR2: HAIP may get disabled after a clusterware reconfiguration or an addnode operation
(Doc ID 2316897.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 12.2]
Information in this document applies to any platform.
- Exadata environment with ACFS configured
- Grid infrastrucure was upgraded from 188.8.131.52 to 184.108.40.206
Customers may see the clusterware HAIP address getting disabled on the newly added node after an addnode operation or an existing node after a clusterware reconfiguration. This can affects the availability of the ACFS across all the DB Nodes in the cluster due to the pending membership reconfiguration.
ASM proxy instance on the DB Node where the HAIP is disabled will repeatedly terminate after being timed out when waiting to complete the Cluster membership rebuild.
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