|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, and Linux x86 Part No. A97395-09 |
|
|
|
|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2) for AIX-Based Systems, hp HP-UX PA-RISC (64-bit), hp Tru64 UNIX, and Linux x86 Part No. A97395-09 |
|
|
|
|
This chapter describes how to change the IP address of UNIX host that has Oracle9iAS Release 2 (9.0.2.1.0) installed on it.
It describes how to change the static IP address. It does not describe how to configure DHCP or change the hostname.
It contains the following topics:
Changing the IP Address of a Host with One Oracle9iAS Installation
Changing the IP Address of a Host with Multiple Oracle9iAS Installations
The following table describes how to use this chapter:
| If you... | Do this... |
|---|---|
| Want to change the IP address of a host with one Oracle9iAS installation |
|
| Want to change the IP address of a host with more than one Oracle9iAS installation | You have two options:
Option 1 (Supported) The following procedure is fully supported by Oracle:
Option 2 (Beta support) The following procedure is under test and has been used successfully by beta sites: |
| Attempted to change the IP address of a pre-9.0.2.1.0 release and had problems | Refer to Section 4.5, "Recovering From a Failed IP Address Change". |
Please review this entire section before you start the IP address change procedure.
It contains the following topics:
The following table describes which Oracle9iAS Release 2 versions are supported for an IP address change. All Oracle9iAS installations on your host must be at a supported version level.
| Oracle9iAS Release 2 Version | Supported? |
|---|---|
| 9.0.2.0.0 and 9.0.2.0.1 | No. You must upgrade to 9.0.2.1.0 before you perform the IP address change.
If you have attempted an IP address change on 9.0.2.0.0 or 9.0.2.0.1 and have failed, refer to Recovering From a Failed IP Address Change for tips on how to recover. |
| 9.0.2.1.0 and all subsequent 9.0.2.x versions | Yes. |
To determine the version number of an installation:
Run Oracle Universal Installer:
ORACLE_HOME/bin/runInstaller
Click Installed Products and view the version number.
The following table describes which Oracle9iAS Release 2 install types are supported for an IP address change. You must make sure that all install types on your host are supported. If you have an install type that is not supported, you must deinstall it, perform the IP address change, and reinstall it.
| Oracle9iAS Release 2 Install Type | Supported? |
|---|---|
| J2EE and Web Cache
(May or may not be associated with an infrastructure; may or may not be clustered) |
Yes |
| Portal and Wireless | Yes |
| Business Intelligence and Forms | Yes |
| Unified Messaging | No |
| Infrastructure | Yes |
| OC4J Standalone
(This is the OC4J Standalone release that can be downloaded from OTN) |
No |
| Developer Kits | No |
Yes. If your host contains an installation that is part of a farm, and other members of the farm exist on other hosts, you must:
Make sure that all Oracle9iAS installations in the farm (even those on other hosts) are at a version that supports an IP address change (9.0.2.1.0)
Make sure that all members of the farm that exist on other hosts are up and running during the IP address change
This is because during the procedure you will run a command that updates all members of the farm with the new IP address information. So all members of the farm must be running and must be at a supported version level so they can register the new IP address.
More Information About Farms
A farm is a group of Oracle9iAS installations that use the same metadata repository. Often, the members of a farm are spread across different hosts. For example, all of these installations are in the same farm:
Host A: Infrastructure containing a metadata repository
Host B: J2EE and Web Cache installation that uses the metadata repository on Host A
Host C: Portal and Wireless installation that uses the metadata repository on Host A
In order to change the IP address on any of these hosts, you need to make sure the installations on the other two hosts are up and running.
You can determine if an installation is part of a farm by running the following command in the Oracle home of the installation:
ORACLE_HOME/dcm/bin/dcmctl listInstances
This will list all installations that are in the same farm.
This section contains the steps to change the IP address of a UNIX host with exactly one Oracle9iAS installation. Oracle recommends you review all steps before starting.
|
Note: Arrange for system downtime before you begin, since this procedure includes shutting down Oracle9iAS and rebooting the host. |
Verify the Oracle9iAS installation is at a supported version level (9.0.2.1.0).
Verify the Oracle9iAS installation is a supported install type.
Determine if the installation is part of a farm. If it is, and any members of the farm exist on other hosts:
Make sure they are running a supported version level (9.0.2.1.0).
Make sure they are up and running when you perform the IP address change procedure. This is because you will run a command that updates all members of the farm, so they all must be up and running.
Stop the following Oracle9iAS components:
Middle-tier installation: Stop all components, such as Oracle HTTP Server, all OC4J instances, Web Cache, Discoverer, Reports, and Forms, using your routine procedure.
Infrastructure installation: Stop all of the following components that you have: Oracle HTTP Server, all OC4J instances, and Web Cache. Do not stop Oracle Internet Directory or the metadata repository yet; you will stop those in step 7.
|
See Also: Oracle9i Application Server Administrator's Guide for instructions on stopping Oracle9iAS |
Stop the Enterprise Manager Web site:
ORACLE_HOME/bin/emctl stop
This command will prompt you for the ias_admin password.
Stop DCM and OPMN:
ORACLE_HOME/dcm/bin/dcmctl shutdown
If you have an infrastructure installation, stop Oracle Internet Directory and the metadata repository.
Make sure Oracle9iAS processes will not start automatically after a reboot by disabling any automated startup procedures you may have set up, such as /etc/init.d scripts.
Edit /etc/hosts and update it with the new IP address.
Make any other changes your operating system requires to properly change its IP address.
Reboot the host.
Verify that the new IP address is working.
Make sure DNS or the /etc/hosts file on other Oracle9iAS hosts in your network are updated with the new IP address.
Verify that you can ping the host from another host in your network. Be sure to ping using the hostname, not the new IP address, to verify that the host name is resolved properly. Especially make sure that other Oracle9iAS hosts that are in the same farm can ping the host.
Log in to the host as the user that installed Oracle9iAS.
If you have an infrastructure:
Make sure the ORACLE_SID environment variable is set (default is iasdb).
Make sure the ORACLE_HOME environment variable is set.
Start the metadata repository:
ORACLE_HOME/bin/lsnrctl start ORACLE_HOME/bin/sqlplus /nolog sql> connect sys/password_for_sys as sysdba sql> startup sql> quit
Start Oracle Internet Directory:
ORACLE_HOME/bin/oidmon start
Wait approximately 30 seconds.
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1 start
On HP-UX systems, modify the $ORACLE_HOME/bin/resetiASpasswd.sh file to include the following lines after the export LD_LIBRARY_PATH line:
SHLIB_PATH=$ORACLE_HOME/lib32:$SHLIB_PATH export SHLIB_PATH
Reset the Oracle9iAS password using the following command:
resetiASpasswd.sh "cn=orcladmin" orcladminpassword_given ORACLE_HOME
Re-register the mod_osso module using the following command:
ORACLE_HOME/jdk/bin/java -jar ORACLE_HOME/sso/lib/ossoreg.jar -site_name iASInstanceName.FQDN -success_url http://FQDN:ApachePortno/osso_login_success -cancel_url http://FQDN:ApachePortno -logout_url http://FQDN:ApachePortno/osso_logout_success -home_url http://FQDN:ApachePortno -config_mod_osso TRUE -oracle_home_path ORACLE_HOME -u root -apache_server_root ORACLE_HOME/Apache/Apache -config_file ORACLE_HOME/Apache/Apache/conf/osso/osso.conf -sso_server_version v1.2
where:
- ORACLE_HOME is the absolute path for the Oracle home
- iASInstanceName is the instance name specified during the installation
- FQDN is the fully qualified domain name, for example foo.bar.com
- ApachePortno is the Oracle HTTP Server port number
Run the following command to register the new IP address. You only need to run this command on the host whose IP address you are changing; it will automatically update any other members of the farm on other hosts. Make sure all members of the farm on other hosts are up when you run this:
ORACLE_HOME/dcm/bin/dcmctl resetHostInformation -v
Start Oracle9iAS.
Middle-tier installation: Start all components you have, such as Oracle HTTP Server, all OC4J instances, Web Cache, Discoverer, Reports, and Forms, using your routine procedure.
Infrastructure installation: Start all components you have, such as Oracle HTTP Server, all OC4J instances, and Web Cache, using your routine procedure.
|
See Also: Oracle9i Application Server Administrator's Guide for instructions on starting Oracle9iAS |
Verify that the following file contains the new IP address and that the old IP address is no longer present:
ORACLE_HOME/opmn/conf/ons.conf
You must verify this file in the Oracle home on the host whose IP address you are changing, as well as any Oracle homes on other hosts that are part of the farm.
If the IP address change has not propagated to all members of the farm, run the following command in the Oracle home of the host whose IP address you are changing and on all other members of the farm:
ORACLE_HOME/dcm/bin/dcmctl resetHostInformation -v
If there are still files that do not contain the new IP address, repeat this entire procedure.
Enable any automated startup procedures that you disabled in Step 8.
Perform this step if you configured a proxy plug-in for the host whose IP address you changed.
If you configured your proxy plug-in to route requests to the Oracle9iAS host using the hostname, restart your iPlanet or IIS server so that the new IP address will get resolved correctly.
If you configured your proxy plug-in to route requests to the Oracle9iAS host using the IP address, reconfigure your proxy plug-in to use the new IP address and restart your iPlanet or IIS server.
This section contains the steps to change the IP address of a UNIX host with more than one Oracle9iAS installation. Oracle recommends you review all steps before starting.
|
Note: Arrange for system downtime before you begin, since this procedure includes shutting down Oracle9iAS and rebooting the host. |
Verify all Oracle9iAS installations on the host are at a supported version level (9.0.2.1.0).
Verify all Oracle9iAS installations on the host are of a supported install type.
Determine if the host contains any installations that are part of a farm. If so, and any members of the farm exist on other hosts:
Make sure the hosts are running a supported version level (9.0.2.1.0).
Make sure the hosts are up and running when you perform the IP address change procedure. This is required because you will run a command that updates all members of the farm, so they all must be up and running.
Stop all Oracle9iAS installations:
Middle-tier installations: Stop all components, such as Oracle HTTP Server, all OC4J instances, Web Cache, Discoverer, Reports, and Forms, using your routine procedure.
Infrastructure installations: Stop all of the following components that you have: Oracle HTTP Server, all OC4J instances, and Web Cache. Do not stop Oracle Internet Directory or the metadata repository yet; you will stop those in step 7.
|
See Also: Oracle9i Application Server Administrator's Guide for instructions on stopping Oracle9iAS |
Stop the Enterprise Manager Web site by running the command in the primary Oracle home:
ORACLE_HOME/bin/emctl stop
This command will prompt you for the ias_admin password.
If you are not sure which is the primary Oracle home, it is listed in:
/var/opt/oracle/emtab
Stop DCM and OPMN by running the following command in each Oracle9iAS Oracle home:
ORACLE_HOME/dcm/bin/dcmctl shutdown
If you have an infrastructure installation, stop Oracle Internet Directory and the metadata repository.
Make sure Oracle9iAS processes will not start automatically after a reboot by disabling any automated startup procedures you may have set up, such as /etc/init.d scripts.
Edit /etc/hosts and update it with the new IP address.
Make any other changes your operating system requires to properly change its IP address.
Reboot the host.
Verify that the new IP address is working.
Make sure DNS or the /etc/hosts file on other Oracle9iAS hosts in your network are updated with the new IP address.
Verify that you can ping the host from another host in your network. Be sure to ping using the hostname, not the new IP address, to verify that the host name is resolved properly. Especially make sure that other Oracle9iAS hosts that are in the same farm can ping the host.
Log in to the host as the user that installed Oracle9iAS.
If you have an infrastructure on this host:
Make sure the ORACLE_SID environment variable is set (default is iasdb).
Make sure the ORACLE_HOME environment variable is set.
Start the metadata repository:
ORACLE_HOME/bin/lsnrctl start ORACLE_HOME/bin/sqlplus /nolog sql> connect sys/password_for_sys as sysdba sql> startup sql> quit
Start Oracle Internet Directory:
ORACLE_HOME/bin/oidmon start
Wait approximately 30 seconds.
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1 start
On HP-UX systems, modify the $ORACLE_HOME/bin/resetiASpasswd.sh file to include the following lines after the export LD_LIBRARY_PATH line:
SHLIB_PATH=$ORACLE_HOME/lib32:$SHLIB_PATH export SHLIB_PATH
Reset the Oracle9iAS password using the following command:
resetiASpasswd.sh "cn=orcladmin" orcladminpassword_given ORACLE_HOME
Re-register the mod_osso module using the following command in each Oracle home on the system:
ORACLE_HOME/jdk/bin/java -jar ORACLE_HOME/sso/lib/ossoreg.jar -site_name iASInstanceName.FQDN -success_url http://FQDN:ApachePortno/osso_login_success -cancel_url http://FQDN:ApachePortno -logout_url http://FQDN:ApachePortno/osso_logout_success -home_url http://FQDN:ApachePortno -config_mod_osso TRUE -oracle_home_path ORACLE_HOME -u root -apache_server_root ORACLE_HOME/Apache/Apache -config_file ORACLE_HOME/Apache/Apache/conf/osso/osso.conf -sso_server_version v1.2
where:
- ORACLE_HOME is the absolute path for the Oracle home
- iASInstanceName is the instance name specified during the installation
- FQDN is the fully qualified domain name, for example foo.bar.com
- ApachePortno is the Oracle HTTP Server port number
In this step you will register the new IP address. Before performing this step, make sure that any members of the farm that are on other hosts are up and running. You will run the commands in this step only on the host whose IP address you are changing, but the command will automatically go out and update members of the farm on other hosts, so they must be up.
Run the following command in each Oracle home on the host whose IP address you are changing:
ORACLE_HOME/dcm/bin/dcmctl resetHostInformation -v
Run the command in the following order:
Run it in the infrastructure Oracle home first (if you have one).
Run it in all middle-tier Oracle homes, in any order.
Run it in the infrastructure Oracle home again (if you have one).
Verify that the following file contains the new IP address and that the old IP address is no longer present:
ORACLE_HOME/opmn/conf/ons.conf
You must verify this file in each Oracle9iAS Oracle home on this host, as well as any installations on other hosts that are part of the farm.
If the IP address change has not propagated to all members of the farm, run the following command in the Oracle home of the host whose IP address you are changing and on all other members of the farm:
ORACLE_HOME/dcm/bin/dcmctl resetHostInformation -v
If there are still files that do not contain the new IP address, repeat this entire procedure.
Start Oracle9iAS.
Middle-tier installation: Start all components you have, such as Oracle HTTP Server, all OC4J instances, Web Cache, Discoverer, Reports, and Forms, using your routine procedure.
Infrastructure installations: Start all components you have, such as Oracle HTTP Server, all OC4J instances, and Web Cache, using your routine procedure.
|
See Also: Oracle9i Application Server Administrator's Guide for instructions on starting Oracle9iAS |
Enable any automated startup procedures that you disabled in Step 8.
Perform this step if you configured a proxy plug-in for the host whose IP address you changed.
If you configured your proxy plug-in to route requests to the Oracle9iAS host using the hostname, restart your iPlanet or IIS server so that the new IP address will get resolved correctly.
If you configured your proxy plug-in to route requests to the Oracle9iAS host using the IP address, reconfigure your proxy plug-in to use the new IP address and restart your iPlanet or IIS server.
If you attempted to change the IP address on an unsupported Oracle9iAS version (eg: 9.0.2.0.1) and failed, you can recover as follows:
Change the IP address back to the original IP address.
Make sure Oracle9iAS is working properly using the original IP address.
Upgrade to 9.0.2.1.0.
Go back to the beginning of this chapter and follow the steps for changing an IP address on 9.0.2.1.0.
If you cannot change the IP address back to the original because the network is no longer available, you can either reinstall Oracle9iAS or make the network available, whichever is the most cost-effective solution.
