ODA OAK Stack: How to Change Oracle Database Appliance IP Addresses Post Deployment (Doc ID 1504734.1)

Last updated on JUNE 18, 2024

Applies to:

Oracle Database Appliance Software - Version 2.3.0.0 to 12.1.2.12 [Release 2.3 to 12.1]
Information in this document applies to any platform.

Goal

The purpose of this note is to illustrate how to change a public IP address, a Virtual IP Address (VIP), VIP hostname or other VIP attributes in Oracle Grid Infrastructure environment for the Oracle Database Appliance (ODA).

** Note: These steps do _not_ apply to any ODA version using the DCS Stack:
The DCS does not support altering the public IP after deployment at this time.

This lack of support for the DCS stack resulted in the following Enhancement request.

Bug 28937165 : ENABLE PUBLIC NETWORK CHANGES FOR DCS STACK ODA

While development has stated that this functionality is scheduled, it is not known which version this will be available.
Contact support for further information and reference this note.
We will update as soon as we become award of any changes allowing this functionality in the ODA DCS Stack

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

How to Change Oracle Database Appliance IP Addresses Post Deployment **

Case I. Changing public IP addresses only without changing interface, subnet or netmask

1. Shutdown Oracle Clusterware stack

2. Create a new copy of the current version configuration parameter file unless this is immediately after a deployment and you are on the first version

3. Use the OAK Configurator and load the previous working configuration file

4. Perform IP changes at the Host Level

5. Restart Oracle Clusterware stack

Case II. Changing the ILOM IP address and ILOM hostname

1. Save a copy of the current working version of the configuration parameter file that was generated during the last successful deployment.

2. Run Oracle Database Appliance Configurator from node 1 and load copy of the previous working version of configuration file.

3. Modify the ILOM Network details

Case III. Changing public network interface, subnet or netmask

Case IV. Changing VIPs associated with public network change

Planning for VIP changes

Gathering Current VIP Configuration

Stopping Resources

Modifying VIP and Its Associated Attributes

Restarting Resources

Case V. Change SCAN VIP associated with public network change

Case VI. Change of dom-0 ipaddress in ODA Virtualized Platform

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