My Oracle Support Banner

VMS: IP Address and Host Name Change on OpenVMS Alpha and Itanium (Doc ID 742564.1)

Last updated on APRIL 14, 2022

Applies to:

Oracle Net Services - Version 9.2.0.2.0 to 10.2.0.2.0 [Release 9.2 to 10.2]
Oracle Database - Enterprise Edition - Version 9.2.0.2 to 10.2.0.2 [Release 9.2 to 10.2]
HP OpenVMS Itanium
HP OpenVMS Alpha
Oracle Net Services - Version: 9.2.0.2.0 to 10.2.0.2.0
HP OpenVMS ItaniumHP OpenVMS Alpha

Purpose

This note shall assist customers who  need to change the IP address and/or the host name of their server.

Scope

This article will NOT be of any help on how to change your network (DNS) and the OS network setup. It will merely mention the components that affect Oracle on OpenVMS.

Potential changes to the Enterprise Manager Grid Console and Grid Control Agent are outside the scope of this article.

This article has the following parts:

- generic introductory remarks
- IP address change
- node name change
- network checks applicable to both procedures

For information on versions before 9.2, please refer to

<Note.72283.1>  VMS Steps to Follow When Changing the IP Address of an OpenVMS Node Running Oracle
.<Note.70685.1> VMS How to Rename an OpenVMS Node that is Running Oracle V7 or V8

CRS related:
<Note.464539.1> VMS How to recreate the Cluster Registry on hp OpenVMS platforms in 10.2

Details

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
Purpose
Scope
Details
 General Remarks on this subject
 A) IP Address change
If you do not use IP addresses in your SQL*net setup, then changing the IP address at the DNS and OS network  level should be all you need to do.

SQL*Net allows you to use either an IP address or a node name when you specify the host or node parameters.  If you are not sure about your use of IP addresses, go through A) and the checks in C).


 A.1. Review the following Oracle files:Modify these files if necessary and change the IP address.

ORA_ROOT:[DBS]INIT<SID>.ora  and/or the SPFILE mentioned in it.
TNS_ADMIN TNSNAMES.ORA
TNS_ADMIN LISTENER.ORA

Use the following query to determine all parameters that need to be changed:

 
 A.2. Check your database link definitions:
Your database links may reference the IP address instead of a service name in the TNSNAMES.ORA file and may be stored in a database that resides on a node other than the OpenVMS node being renamed.

 

You can review your database links using the DBA_DB_LINKS view. Example:

 

The HOST column within the DBA_DB_LINKS view equates to the "using" clause when you created your database link. In this example, all the db links reference services in the TNSNAMES.ORA file. No changes to dblinks are needed in this example.


 A.3.  Additional verification:
Use the following command to search files under the ORA_ROOT directory structure for all occurrences of the IP address.
 

 B. Node Name changes
 B.1. Files that must be changed.
ORA_ROOT:[DBS]INIT<SID>.ORA or the SPFILE that is referenced in it.
ORA_DUMP <node name>_DBNAME_ALERT.LOG            (rename)
ORA_ROOT:[DBS]sid_<SID>.properties                                 (edit  the NODE parameter)
TNS_ADMIN TNSNAMES.ORA
TNS_ADMIN LISTENER.ORA


 
For 9.2 Gateways:

ORA_TG4RMS *STARTUP*.COM
ORA_TG4RDB *STARTUP*.COM

For 9.2 OEM Agent:

ORA_AGENT AGENT_START.COM
ORA_AGENT DBSNMPC.COM
ORA_AGENT DBSNMPJ.COM
TNS_ADMIN:ORATAB.ORA

Use the following query to determine all parameters that need to be changed:
 

Use the following command to search files under the ORA_ROOT directory structure for all occurrences of the node name.

 
 B.2. Files that might need to be changed.
These changes are only needed if the disk portion of the directory path includes the node name.

 

ORA_ROOT:[000000]ORAUSER.COM
ORA_ROOT:[DBS]INIT<SID>.ORA or the SPFILE it references for all parameters that specify a path
ORA_ROOT:[DBS]INIT_<SID>.PROPERTIES
ORA_NETWORK:BEQLSNR.COM
TNS_ADMIN:ORASRV_NETV2*.COM
TNS_ADMIN:ORASRV_BEQ*.COM
DISK:[<SWOWNER_SYS$LOGIN>.<NODENAME>]ORAINST.LOC
DISK:[<SWOWNER_SYS$LOGIN>.<NODENAME>]ORATAB.

For calls to and symbol definitions for orauser:

SYS$LOGIN:LOGIN.COM
SYS$STARTUP:SYLOGIN.COM


 B.3. Database Link definitions:
Your database links may reference the node name instead of a service from the TNSNAMES.ORA file. Your database links may be stored in a database that resides on a node other than the OpenVMS node being renamed.
 

You can review your database links using the DBA_DB_LINKS view.
 

The HOST column in the DBA_DB_LINKS view equates to the "using" clause when you create your database link. In this example, all the database links reference services in the TNSNAMES.ORA file and do not need to be changed.

 B.4. Datafile path names
Your physical file specification for your database files may reference the physical device name instead of an OpenVMS logical.
 

Check for other files  and parameters that might need to be changed:

 

For more information on renaming database files please see: 

<Note 115424.1> How to Rename or Move Datafiles and Logfiles


Perform the following query when logged in as internal:

 
This query shows all initialization parameters that use the node name.
Make sure you repeat the query for both UPPERCASE and lowercase Node name.

 B.5. Directory names that must be changedThe following directory contains important files and must either be renamed to the new node name or you have to create a new subdirectory with the new name and transfer the files.

DISK:[<SWOWNER_SYS$LOGIN>.<NODENAME>]

 
oratab. is created and used by DBCA and registers the databases in your installation.
ORAINST.LOC contains the location of your installations inventory.

For more information on the inventory see Tip6 and 7 in

<Note 391596.1> OUI tips for Oracle RDBMS 10.2.X on hp OpenVMS

 B.6.  Batch queue definitions
If you run CRS or the Grid Control Agent on the server, make sure your batch queue is correct.

 

 C. Verify your network setup
To verify the network setup for Oracle on OpenVMS, we suggest the  following checks:

 C.1. Is SCSnode correct?
 
Does it match C.2?


 C.2. Are the TCPIP logicals correct?
 

Does TCPIP$INET_HOST match C.1.?
 C.3. Does NSLOOKUP bring back the correct values?
Assume a Windows client:

 

From the OpenVMS server:

 

 C.4. Has your local hosts file be modified?
 

 C.5. Does your NIC card reflect the correct value(s)?
 

 C.6. Have your clients be modified to reflect the new node name and/or IP address?
Files to consider are

 
 C.7. Use of LDAP (OID)or Names

If you use Oracle Internet Directory, check your TNS_ADMIN:LDAP.ORA

If you use Oracle Names (available in 9.2 for backward compatibility), check the TNS_ADMIN:NAMES.ORA on the Names Server.


 C.8. Connection Manager and Firewalls
If you employ Firewalls and Connection Manager, make sure those environments know about the new IP address and/or node name.


References

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