My Oracle Support Banner

HOWTO: Remove/Disable HAIP on ODA (Doc ID 2612963.1)

Last updated on SEPTEMBER 24, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Linux x86-64
Currently several ODA HAIP configurations may have been disabled using the steps provided in EXADATA Note 2524069.1.

Goal

This document will explain a manual option to remove (disable) HAIP on ODA with the least amount of production impact.
If ACFS is in use, then only ACFS will be impacted on each node briefly and then there will be on a brief rolling outage node by node.
The preferred method, however, is to upgrade the ODA to 18.7 (or higher) which will disable HAIP during the patch steps.

Note

For Exadata use Note 2524069.1 - The Exadata steps are different because the ODA uses a bonded configuration while Exadata does not.
IF HAIP was disabled on the ODA using Note 2524069.1 steps for Exadata then you will want to complete the HAIP removal using this note steps.

 

Solution

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
Goal
Solution
 1. Backup gpnp profile
 2. Get the cluster_interconnect interfaces (only on node0)
 3. Backup existing ifcfg-<interface> files
 4. Create ifcfg-icbond0 and modify ifcfg-<interface> files
 6. Creating/replacing init.ora-s for APX instances
 7. Stop the clusterware on node2
 8. Set the new, bonded cluster_interconnect interface and remove p1p1/p1p2 interfaces from the configuration (only on node0)
 9. Remove HAIP dependency in ora.asm
 10. Removing ora.cluster_interconnect.haip resource
 11. Stop the clusterware on node1
 12. Restart the network
 13. Restart the Clusterware
 14. Restart dcs-agent to rediscover the interfaces automatically
 Post Clean-up Task
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.