7.2.1 Understanding the chgiphost Command

The chgiphost command-line utility changes the hostname, domain name, or IP address of a middle-tier instance, Infrastructure, or Identity Management installation.

The utility is located at:

• On UNIX systems: ORACLE_HOME/chgip/scripts/chgiphost.sh
• On Windows systems: ORACLE_HOME\chgip\scripts\chgiphost.bat

Table 7-2 shows the options for the command.

Note that if you use chgiphost to change the hostname or domain name, it does not update the instance name. For example, assume that the original instance name, with the hostname and domain name appended, is:

If you change the hostname to myhost2, the instance name remains the same.

7.2.2 Changing the Hostname or Domain Name of a Middle-Tier Installation

This section describes how to change the hostname, domain name, or both, of a host that contains any of the middle-tier installation types.

The following sections describe the procedure:

• Before You Begin
• Task 1: Prepare Your Host
• Task 2: Change the Hostname
• Task 3: Run the chgiphost Command
• Task 4: Re-enable SSO Authentication
• Task 5: Update Host Information for Other Members of Cluster
• Task 6: Manually Update the Hostname in Files
• Task 7: Restart Your Environment

Before You Begin

Review the following items before you start:

• If the middle-tier instance is registered with Oracle Internet Directory, you must supply the cn=orcladmin password during the procedure.
• Consider changing the log level before running the chgiphost command so you can view more detailed information. See Section 7.2.5.1 for more information.
• If your old hostname is a string that is likely to appear in a configuration file, the chgiphost command may encounter problems when trying to update the configuration files. Refer to Section 7.2.5.2 for information on how to avoid this problem.
• Write down the old hostname and IP address before you begin. You will be prompted for these values.
• Oracle recommends that you perform a backup of your environment before you start this procedure. Refer to Part V, "Backup and Recovery" for more information.

Task 1: Prepare Your Host

Prepare your host for the change by stopping all processes:

1. Shut down each middle-tier instance on the host by running the following commands in each Oracle home:
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl stopall
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl stopall
2. To make sure Oracle Application Server processes will not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as /etc/init.d scripts.
3. Make sure that the Oracle Internet Directory that is used by the middle tier is started.

Task 2: Change the Hostname

Update your operating system with the new hostname, domain name, or both. Consult your operating system documentation for information on how to perform the following steps. You can also change the IP address, if desired.

1. Make the updates to your operating system to properly change the hostname, domain name, or both.
2. Restart the host, if necessary for your operating system.
3. Verify that you can ping the host from another host in your network. Be sure to ping using the new hostname to make sure everything is resolving properly.

Task 3: Run the chgiphost Command

Follow these steps for each middle-tier instance on your host. Be sure to complete the steps entirely for one middle-tier instance before you move on to the next.

1. Log in to the host as the user that installed the middle-tier instance.
2. Make sure the ORACLE_HOME environment variable is set to the middle-tier Oracle home. Do not use a trailing slash (UNIX) or backslash (Windows) when specifying the variable.
3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you must set depend on the type of your UNIX operating system.
4. Run the following commands in the middle-tier Oracle home:
   • On UNIX systems: cd ORACLE_HOME/chgip/scripts ./chgiphost.sh -mid
   • On Windows systems: cd ORACLE_HOME\chgip\scripts cmd /c chgiphost.bat -mid

   The chgiphost command prompts for information, as shown in Table 7-3. Note that the prompts may provide values in parentheses. You can enter a different value, or press the return key to accept the suggested value.

   Table 7-3 Prompts and Actions for chgiphost -mid

   Prompt	Action
   Enter fully qualified hostname (hostname.domainname) of destination	Enter the new fully qualified hostname. This may be a new hostname, domain name, or both.
   Enter fully qualified hostname (hostname.domainname) of source	Enter the original fully qualified hostname, domain name, or both.
   Enter valid IP Address of destination	If you changed the IP address of the host, enter the new IP address. Otherwise, enter the current IP address.
   Enter valid IP Address of source	If you changed the IP address of the host, enter the old IP address. Otherwise, enter the current IP address.
   OIDAdmin Password:	Enter the cn=orcladmin password for the Oracle Internet Directory in which this middle-tier instance is registered.

5. Verify that the tool ran successfully by checking for errors in the files in the following directory:
   • On UNIX systems: ORACLE_HOME/chgip/log
   • On Windows systems: ORACLE_HOME\chgip\log

Task 4: Re-enable SSO Authentication

If the middle-tier instance was enabled for SSO authentication, you must enable it again. Follow the steps in "Task 1: Enable SSO Authentication (Optional)" in Section 6.6.

Task 5: Update Host Information for Other Members of Cluster

If the middle-tier instance is a member of a topology cluster, you may need to update the topology information in the opmn.xml file for the other members of the cluster.

If the middle-tier instance is part of a dynamic discovery cluster, you do not need to make any changes to the opmn.xml file.

However, if the cluster is one of the following types, you must update the opmn.xml file:

• Static hubs as discovery servers: You must change the host name or domain name in the <discover> element. The following example shows an example of the element: <topology> <discover list="node1.com:6201,node2.com:6202"/> </topology>
• Cross-topology gateways: You must change the host name or domain name in the <gateway> element. The following example shows an example of the element: <topology> <gateway list="node1.com:6201&node2.com:6202&node3.com:6203"/> <discover list="*224.0.1.37:8205"/> </topology>
• Static node-to-node: You must change the host name or domain name in the <nodes> element. The following example shows an example of the element: <topology> <nodes list="node1-sun:6201,node2-sun:6202"/> </topology>

Task 6: Manually Update the Hostname in Files

In some circumstances, you need to manually update the hostname in files:

• If you edited a file and entered the hostname as part of a user-defined parameter such as the Oracle home path, the hostname is not automatically updated by running the chgiphost command. To update the hostname in such cases, you must edit the files manually. For example on UNIX, the plsql.conf file may contain an NFS path including the hostname, such as: /net/dsun1/private/....
• It is common that WebCenter applications use portlets that are running on the same host. For example, a WebCenter application running in OC4J instance OC4J_Apps can consume a portlet running in the OC4J instance OC4J_WebCenter.

  If you change the hostname, domain name, or both, of a WebCenter application, you must manually update the internal references to these portlets. WebCenter applications store the portlet producer connection information in the file connections.xml, located in the following directory:

  ORACLE_HOME/j2ee/OC4J_instance/applications/application_name/adf/META-INF

  Using a text editor, search for the hostname and replace all occurrences with the appropriate new value. The information will look like that marked in bold in the following example:

  <urlconnection name="PdkPortletProducer1_115996420445613411da8-010e-1000-8002-8c5707c5e057-urlconn" url="http://apphost1.mycompany.com:8890/jpdk/providers"/> . . . <wsconnection description="http://apphost1.mycompany.com:6688/richtextportlet/portlets/wsrp2?WSDL"> <soap addressUrl="http://apphost1.mycompany.com:6688/richtextportlet/portlets/WSRP_v2_PortletManagement_Service" xmlns="http://schemas.xmlsoap.org/wsdl/soap/" />

  Similarly, if you are using Oracle Content DB and your connection information has changed, you can update connections.xml as follows:

  <StringRefAddr addrType="jcr_oracle.ifs.jcr.configuration.serverUrl"> <Contents>https://ctdbhost1.mycompany.com:4444/content/ws</Contents></StringRefAddr>
• The chgiphost command also does not edit the hostname references in the documentation files. You must manually edit these files to update the hostname. Examples of such files are the index.html.* files in the ORACLE_HOME/Apache/Apache/htdocs directory.

Task 7: Restart Your Environment

Restart the middle-tier instances and restore your configuration to the way it was before you started the procedure:

1. Start each middle-tier instance on your host by running the following command in each Oracle home: (Unix) ORACLE_HOME/opmn/bin/opmnctl startall (Windows) ORACLE_HOME\opmn\bin\opmnctl startall
2. If you disabled any processes for automatically starting Oracle Application Server at the beginning of this procedure, enable them.

7.2.3 Changing the Hostname, Domain Name, or IP Address of a 10.1.4 or 10.1.2 Identity Management Installation

You may have a 10g Release 3 (10.1.3.2.0) middle-tier instance associated with a 10.1.4 or 10.1.2 Identity Management installation.

This section describes how to change the hostname, domain name, or IP address on a host that contains an Identity Management installation. This procedure applies to any Identity Management-only installation, including the following:

• Identity Management with only Oracle Internet Directory configured
• Identity Management with OracleAS Single Sign-On, Oracle Delegated Administration Services, Oracle Directory Integration and Provisioning configured
• Identity Management with Oracle Internet Directory, OracleAS Single Sign-On, Oracle Delegated Administration Services, Oracle Directory Integration and Provisioning configured

The following sections describe the procedure:

• Before You Begin
• Task 1: Shut Down Middle-Tier Instances
• Task 2: Prepare Your Host
• Task 3: Change the Hostname or IP Address
• Task 4: Run the chgiphost Command
• Task 5: Restart Your Environment
• Task 6: Update Your Environment
• Task 7: Update Oracle Internet Directory If LDAP-Based Replication Is Used

Before You Begin

Review the following items before you start the procedure:

• Consider changing the log level before running the chgiphost command so you can view more detailed information. See Section 7.2.5.1 for more information.
• If your old hostname is a string that is likely to appear in a configuration file, the chgiphost command may encounter problems when trying to update the configuration files. Refer to Section 7.2.5.2 for information on how to avoid this problem.
• Write down the old hostname and IP address before you begin. You will be prompted for these values.
• Oracle recommends that you perform a backup of your environment before you start this procedure. Refer to Part V, "Backup and Recovery" for more information.

Task 1: Shut Down Middle-Tier Instances

For each 10g Release 3 (10.1.3.2.0) middle-tier instance that uses Identity Management, stop the Application Server Control Console and the middle-tier instance using the following command:

• On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl stopall
• On Windows systems: ORACLE_HOME\opmn\bin\opmnctl stopall

Task 2: Prepare Your Host

Prepare your host for the hostname change by stopping all processes on the Release 2 (10.1.2) Identity Management instance:

1. Set the ORACLE_HOME environment variable.
2. Shut down the Identity Management installation, including the servers, such as Oracle Directory Server, Directory Integration and Provisioning Data server (if it is configured), and Replication Server, as well as Application Server Control Console. For example, on UNIX, use the following commands: ORACLE_HOME/bin/emctl stop iasconsole ORACLE_HOME/bin/oidctl server=odisrv instance=instance_number stop ORACLE_HOME/bin/oidctl connect=global_db_name server=oidrepld instance=instance_number stop ORACLE_HOME/bin/oidctl server=oidldapd instance=instance_number stop ORACLE_HOME/opmn/bin/opmnctl stopall
3. To make sure Oracle Application Server processes will not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as /etc/init.d scripts.

Task 3: Change the Hostname or IP Address

Update your operating system with the new hostname, domain name, or IP address. Consult your operating system documentation for information on how to perform the following steps:

1. Make the updates to your operating system to properly change hostname, domain name, or both.
2. Restart the host, if necessary for your operating system.
3. Verify that you can ping the host from another host in your network. Be sure to ping using the new hostname to make sure everything is resolving properly.

Task 4: Run the chgiphost Command

Perform these steps in the Identity Management instance:

1. Log in to the host as the user that installed Identity Management.
2. Set the ORACLE_HOME environment variable. Do not use a trailing slash (UNIX) or backslash (Windows) when specifying the ORACLE_HOME variable.
3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you must set depend on the type of your UNIX operating system.
4. Run the following commands in the Identity Management Oracle home:
   • On UNIX systems: cd ORACLE_HOME/chgip/scripts ./chgiphost.sh -idm
   • On Windows systems: cd ORACLE_HOME\chgip\scripts cmd /c chgiphost.bat -idm

   The chgiphost command prompts for information, as shown in Table 7-4. Note that the prompts may provide values in parentheses. You can enter a different value, or press the return key to accept the suggested value.

   Table 7-4 Prompts and Actions for chgiphost -idm

   Prompt	Action
   Enter fully qualified hostname (hostname.domainname) of destination	If you changed the hostname or domain name on your system, enter the new fully qualified hostname. Otherwise, enter the current fully qualified hostname.
   Enter fully qualified hostname (hostname.domainname) of source	If you changed the hostname or domain name on your system, enter the old fully qualified hostname. Otherwise, enter the current fully qualified hostname.
   Enter valid IP Address of destination	If you changed the IP address of the system, enter the new IP address. Otherwise, enter the current IP address
   Enter valid IP Address of source	If you changed the IP address of the system, enter the old IP address. Otherwise, enter the current IP address

5. Verify that the tool ran successfully by checking for errors in the files in the following directory: (UNIX) ORACLE_HOME/chgip/log (Windows) ORACLE_HOME\chgip\log

Task 5: Restart Your Environment

Restart the Identity Management installation and any other Infrastructure instances that you stopped during this procedure:

1. Restart the Identity Management instance, using the following commands:
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl stopall ORACLE_HOME/opmn/bin/opmnctl startall ORACLE_HOME/bin/emctl start iasconsole
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl stopall ORACLE_HOME\opmn\bin\opmnctl startall ORACLE_HOME\bin\emctl start iasconsole
2. If you disabled any processes for automatically starting Oracle Application Server at the beginning of this procedure, enable them.

Task 6: Update Your Environment

This task contains the steps to update your environment for the new hostname, domain name, or IP address. The steps you need to take depend on how your environment is configured. If you changed the hostname or IP address of the host containing:

• Oracle Internet Directory only: See "Configuration 1: Oracle Internet Directory Only". Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you change the host that contains Oracle Internet Directory. In this case, you must update the other Identity Management components and the middle tiers that use this Identity Management.
• Identity Management components other than Oracle Internet Directory: See "Configuration 2: OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning". Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you change the host that contains the other Identity Management components. In this case, you must update the middle tiers that use this Identity Management.
• Oracle Internet Directory and other Identity Management components: See "Configuration 3: Oracle Internet Directory, OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning". Oracle Internet Directory and the other Identity Management components are installed on the same host. In this case, you must update the middle tiers that use this Identity Management.

If your environment uses LDAP-based replication of Oracle Internet Directory and Oracle Internet Directory is on a different host than OracleAS Metadata Repository, you can change the hostname, domain name, or IP address of the host containing the Master (supplier) or Replica (consumer) Oracle Internet Directory. See "Task 7: Update Oracle Internet Directory If LDAP-Based Replication Is Used" for information.

Configuration 1: Oracle Internet Directory Only In this case, Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you changed the host that contains Oracle Internet Directory. Take the following steps:

1. In the OracleAS Single Sign-On installation, stop the Infrastructure processes and the Application Server Control Console:
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl stopall ORACLE_HOME/bin/emctl stop iasconsole
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl stopall ORACLE_HOME\bin\emctl stop iasconsole
2. Update the ias.properties file in every OracleAS Infrastructure instance that uses Oracle Internet Directory. This includes other Identity Management instances (OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning, if it is configured).

   In each Oracle home, update the following file:

   (UNIX) ORACLE_HOME/config/ias.properties (Windows) ORACLE_HOME\config\ias.properties

   In the file, update the OIDhost parameter in with the new hostname:

   OIDhost=newhost.us.oracle.com
3. Update the ldap.ora file in every OracleAS Infrastructure instance that uses Oracle Internet Directory. This includes other Identity Management instances (OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning, if it is configured).

   In each Oracle home, edit the following file:

   (UNIX) ORACLE_HOME/ldap/admin/ldap.ora (Windows) ORACLE_HOME\ldap\admin\ldap.ora

   In the file, update the DIRECTORY_SERVERS parameter with the new fully qualified hostname.

4. In the Oracle homes for the other Identity Management components, start OPMN and Application Server Control Console:
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl start ORACLE_HOME/bin/emctl start iasconsole
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl start ORACLE_HOME\bin\emctl start iasconsole
5. In the Oracle homes for the middle-tier instances, start OPMN and Application Server Control Console. To start Application Server Control Console, you start the default OC4J instance, because Application Server Control Console runs as an application with the default OC4J instance.
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl start ORACLE_HOME/opmn/bin/opmnctl startproc process-type=home
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl start ORACLE_HOME\opmn\bin\opmnctl startproc process-type=home
6. If any middle-tier instance was enabled for SSO authentication, you must enable it again. Follow the steps in "Task 1: Enable SSO Authentication (Optional)" in Section 6.6 for each middle-tier instance that uses this Oracle Internet Directory instance.
7. In the Oracle homes for the other Identity Management components and each middle tier, run the Change Identity Management Services wizard and supply the new Oracle Internet Directory information. For example, for the 10.1.3 middle tier, take the following steps:
   1. Using the Application Server Control Console, navigate to the OC4J Home page for the middle-tier instance.
   2. Click Administration.
   3. In the Task Name column of the table, expand Security if it is not already expanded. Then, in the Identity Management row, click the Go to Task icon.
   4. On the Identity Management page, click Change.
   5. Follow the steps in the wizard for supplying the new Identity Management information. See Section 6.6 for more information.
   6. When the operation completes, you need to restart the OC4J instance. Do not click Restart on the Confirmation page. Instead, navigate to the Cluster Topology page, select the OC4J instance, and click Restart.

   Note that although you may see the new Internet Directory host and port on the page, you still need to perform this step. For Release 2 (10.1.2), the Application Server Control Console displays the virtual hostname only because it read it from the updated ias.properties file.

8. If OracleAS Certificate Authority is installed, take the following steps:
   1. Stop OracleAS Certificate Authority, the OC4J oca process, and the Oracle HTTP Server on the host running OracleAS Certificate Authority. For example, on UNIX, execute the following commands: ORACLE_HOME/oca/bin/ocactl stop ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=oca ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
   2. Edit the following file and change the name of the host listed in the file: (UNIX) ORACLE_HOME/oca/conf/oca.conf (Windows) ORACLE_HOME\oca\conf\oca.conf
   3. Reassociate with OracleAS Single Sign-On and Oracle Internet Directory. For example, on UNIX: ORACLE_HOME/oca/bin/ocactl changesecurity -server_auth_port OcaSslPort
   4. Start Oracle HTTP Server, the OC4J oca process, and OracleAS Certificate Authority. For example, on UNIX: ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server ORACLE_HOME/opmn/bin/opmnctl startproc process-type=oca ORACLE_HOME/oca/bin/ocactl start

Configuration 2: OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning In this case, Oracle Internet Directory is installed on one host and the other Identity Management components are installed on another host and you changed the host that contains the other Identity Management components.

In each middle-tier installation, take the following steps:

1. Start OPMN and Application Server Control Console. To start Application Server Control Console, you start the default OC4J instance, because Application Server Control Console runs as an application with the default OC4J instance.
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl start ORACLE_HOME/opmn/bin/opmnctl startproc process-type=home
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl start ORACLE_HOME\opmn\bin\opmnctl startproc process-type=home
2. In the Oracle home for each middle tier, run the Change Identity Management Services wizard and supply the new Oracle Internet Directory information:
   1. Using the Application Server Control Console, navigate to the OC4J Home page for the middle-tier instance.
   2. Click Administration.
   3. In the Task Name column of the table, expand Security if it is not already expanded. Then, in the Identity Management row, click the Go to Task icon.
   4. On the Identity Management page, click Change.
   5. Follow the steps in the wizard for supplying the new Identity Management information. See Section 6.6 for more information.
   6. When the operation completes, you need to restart the OC4J instance. Do not click Restart on the Confirmation page. Instead, navigate to the Cluster Topology page, select the OC4J instance, and click Restart.

   Note that although you see the correct Internet Directory host and port on the page, you still need to perform this step.

3. Restart the affected components. Run the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall ORACLE_HOME/opmn/bin/opmnctl startall

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall ORACLE_HOME\opmn\bin\opmnctl startall

Configuration 3: Oracle Internet Directory, OracleAS Single Sign-On, Oracle Delegated Administration Services, and Oracle Directory Integration and Provisioning In this case, Oracle Internet Directory and the other Identity Management components are installed on the same host and this is the host you changed. Take the following steps:

In each middle-tier installation, take the following steps:

1. Start OPMN and Application Server Control Console. To start Application Server Control Console, you start the default OC4J instance, because Application Server Control Console runs as an application with the default OC4J instance.
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl start ORACLE_HOME/opmn/bin/opmnctl startproc process-type=home
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl start ORACLE_HOME\opmn\bin\opmnctl startproc process-type=home
2. If any middle-tier instance was enabled for SSO authentication, you must enable it again. Follow the steps in "Task 1: Enable SSO Authentication (Optional)" in Section 6.6 for each middle-tier instance.
3. In each middle-tier installation, run the Change Identity Management Services wizard:
   1. Using the Application Server Control Console, navigate to the OC4J Home page for the middle-tier instance.
   2. Click Administration.
   3. In the Task Name column of the table, expand Security if it is not already expanded. Then, in the Identity Management row, click the Go to Task icon.
   4. On the Identity Management page, click Change.
   5. Follow the steps in the wizard for supplying the new Identity Management information. See Section 6.6 for more information.
   6. When the operation completes, you need to restart the OC4J instance. Do not click Restart on the Confirmation page. Instead, navigate to the Cluster Topology page, select the OC4J instance, and click Restart.
4. Restart the affected components. Run the following commands in each Oracle home:

   • On UNIX systems:

     ORACLE_HOME/opmn/bin/opmnctl stopall ORACLE_HOME/opmn/bin/opmnctl startall

   • On Windows systems:

     ORACLE_HOME\opmn\bin\opmnctl stopall ORACLE_HOME\opmn\bin\opmnctl startall

Task 7: Update Oracle Internet Directory If LDAP-Based Replication Is Used

If your environment uses LDAP-based replication of Oracle Internet Directory and Oracle Internet Directory is on a different host than OracleAS Metadata Repository, you can change the hostname, domain name, or IP address of the host containing the Master (supplier) or Replica (consumer) Oracle Internet Directory:

• Configuration A: Host with Master Oracle Internet Directory Is Changed
• Configuration B: Host with Replica Oracle Internet Directory Is Changed

Configuration A: Host with Master Oracle Internet Directory Is Changed

If you change the hostname, domain name, or IP address of the host containing the Master Oracle Internet Directory, take the following steps:

1. Obtain the replica ID of the Master Oracle Internet Directory: ldapsearch -p master_port -h master_host -b "" -s base "objectclass=*" orclreplicaid
2. On both the Master and the Replica, update either orclreplicauri or orclreplicasecondaryuri or both, if they exist, in the replica entry of the Master Oracle Internet Directory. Take the following steps:
   1. Create a file named mod.ldif and enter the following lines in the file: dn: orclreplicaid=master_replicaID,cn=replication configuration changetype:modify replace: orclreplicauri orclreplicauri: ldap://new_master_host:new_master_port/

      In the example, master_replicaID is the ID obtained in Step a, new_master_host is the new hostname of the Master Oracle Internet Directory, and new_master_port is the port number for the Master Oracle Internet Directory.

   2. Run the following command on the Master: ldapmodify -p master_port -h master_host -f mod.ldif
   3. Run the following command on the Replica: ldapmodify -p replica_port -h replica_host -f mod.ldif
3. Restart the Replication server at the Replica: oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h replica_host -p replica_port -m false" stop oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h replica_host -p replica_port -m false" start

   In the example, replica_host is the hostname of the Replica Oracle Internet Directory and replica_port is the port of the Replica Oracle Internet Directory.

Configuration B: Host with Replica Oracle Internet Directory Is Changed

If you change the hostname, domain name, or IP address of the host containing the Replica Oracle Internet Directory, take the following steps:

1. Obtain the replica ID of the Replica Oracle Internet Directory: ldapsearch -p replica_port -h replica_host -b "" -s base "objectclass=*" orclreplicaid
2. On both the Master and the Replica, update either orclreplicauri or orclreplicasecondaryuri or both, if they exist, in the replica entry of the Replica Oracle Internet Directory. Take the following steps:
   1. Create a file named mod.ldif and enter the following lines in the file: dn: orclreplicaid=replica_replicaID,cn=replication configuration changetype:modify replace: orclreplicauri orclreplicauri: ldap://new_replica_host:new_replica_port/

      In the example, replica_replicaID is the ID obtained in Step a, new_replica_host is the new hostname of the Replica Oracle Internet Directory, and new_replica_port is the port number for the Replica Oracle Internet Directory.

   2. Run the following command on the Master: ldapmodify -p master_port -h master_host -f mod.ldif
   3. Run the following command on the Replica: ldapmodify -p replica_port -h replica_host -f mod.ldif
3. Restart the Replication server at the Replica: oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h new_replica_host -p new_replica_port -m false" stop oidctl server=oidrepld inst=inst_num connect=connect_string flags="-h new_replica_host -p new_replica_port -m false" start

   In the example, new_replica_host is the new hostname of the Replica Oracle Internet Directory and new_replica_port is the port of the Replica Oracle Internet Directory.

7.2.4 Changing the IP Address of a 10.1.4 or 10.1.2 Infrastructure Containing a Metadata Repository

This section describes how to change the IP address of a host that contains either of the following Infrastructure installation types:

• Metadata Repository only
• Identity Management and Metadata Repository

The following sections describe the procedure:

• Before You Begin
• Task 1: Shut Down Middle-Tier Instances
• Task 2: Prepare Your Host
• Task 3: Change the IP Address
• Task 4: Update the Infrastructure
• Task 5: Restart Your Environment

Before You Begin

Review the following items before you start the procedure:

• Write down the old IP address before you begin. You will be prompted for this during the procedure.
• Oracle recommends that you perform a backup of your environment before you start this procedure. Refer to Part V, "Backup and Recovery" for more information.

Task 1: Shut Down Middle-Tier Instances

Shut down all middle-tier instances that use the Infrastructure installation, even if they are on other hosts:

Task 2: Prepare Your Host

Prepare your host for the change by stopping all processes:

1. Set the ORACLE_HOME and ORACLE_SID environment variables.
2. Shut down the Infrastructure:
   1. Stop all Application Server Control Console and all processes:

      • On UNIX systems:

        ORACLE_HOME/bin/emctl stop iasconsole ORACLE_HOME/opmn/bin/opmnctl stopall

      • On Windows systems:

        ORACLE_HOME\bin\emctl stop iasconsole ORACLE_HOME\opmn\bin\opmnctl stopall
   2. Change directory to the bin subdirectory of Oracle home. Then, shut down the listener and database: lsnrctl stop sqlplus /nolog SQL> connect SYS as SYSDBA SQL> shutdown SQL> quit
3. Verify that all Oracle Application Server processes have stopped.
4. To make sure Oracle Application Server processes will not start automatically after a restart of the host, disable any automated startup scripts you may have set up, such as /etc/init.d scripts.

Task 3: Change the IP Address

Update your operating system with the new IP address, restart the host, and verify that the host is functioning properly on your network. Consult your operating system documentation for information on how to perform the following steps:

1. Make the updates to your operating system to properly change the IP address.
2. Restart the host, if required by your operating system.
3. Verify that you can ping the host from another host in your network. Be sure to ping using the new IP address to make sure everything is resolving properly.

Task 4: Update the Infrastructure

Update the Infrastructure on your host with the new IP address:

1. Log in to the host as the user that installed the Infrastructure.
2. Set the ORACLE_HOME and ORACLE_SID environment variables. Do not use a trailing slash (UNIX) or backslash (Windows) when specifying the ORACLE_HOME variable.
3. On UNIX systems, set the LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, LIB_PATH, or SHLIB_PATH environment variables to the proper values, as shown in Table 1-1. The actual environment variables and values that you must set depend on the type of your UNIX operating system.
4. Change directory to the bin subdirectory of Oracle home. Then, start the database and listener: sqlplus /nolog SQL> connect SYS as SYSDBA SQL> startup SQL> quit lsnrctl start
5. Start OPMN: (UNIX) ORACLE_HOME/opmn/bin/opmnctl start (Windows) ORACLE_HOME\opmn\bin\opmnctl start
6. Start Oracle Internet Directory: (UNIX) ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID process-type=OID (Windows) ORACLE_HOME\opmn\bin\opmnctl startproc ias-component=OID process-type=OID
7. Run the following commands in the Infrastructure Oracle home:
   • On UNIX systems: cd ORACLE_HOME/chgip/scripts ./chgiphost.sh -infra
   • On Windows systems: cd ORACLE_HOME\chgip\scripts cmd /c chgiphost.bat -infra

   The chgiphost command prompts for the old and new IP address.

8. Verify that the tool ran successfully by checking for errors in the files in the following directory: (UNIX) ORACLE_HOME/chgip/log (Windows) ORACLE_HOME\chgip\log

Task 5: Restart Your Environment

Start the remaining components of the Infrastructure and start any middle-tier instances that use it:

1. Start the Infrastructure:
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl startall ORACLE_HOME/bin/emctl start iasconsole
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl startall ORACLE_HOME\bin\emctl start iasconsole
2. If a middle-tier instance is on the same host as the Infrastructure, then you need to run the chgiphost command on the middle-tier instance before restarting the middle-tier instances.
3. Start the middle-tier instances:
   • On UNIX systems: ORACLE_HOME/opmn/bin/opmnctl startall
   • On Windows systems: ORACLE_HOME\opmn\bin\opmnctl startall
4. If you disabled any processes for automatically starting Oracle Application Server at the beginning of this procedure, enable them.

7.2.5 Special Topics for Changing a Hostname or Domain Name

This section contains the following special topics that apply to changing the hostname or domain name of an Oracle Application Server host:

• Setting the Log Level for chgiphost
• Customizing the chgiphost Command
• Changing a Hostname After Upgrading from Windows 2000 to Windows 2003
• Recovering from Errors When Changing a Hostname

7.3.1 Moving from Off-Network to On-Network (Static IP Address)

This procedure assumes you have installed Oracle Application Server on a host that is off the network, using a standard hostname (not localhost), and would like to move on the network and use a static IP address. The IP address may be the default loopback IP, or any standard IP address.

To move onto the network, you can simply connect the host to the network. No updates to Oracle Application Server are required.

7.3.2 Moving from Off-Network to On-Network (DHCP)

This procedure assumes you have installed on a host that is off the network, using a standard hostname (not localhost), and would like to move on the network and use DHCP. The IP address of the host can be any static IP address or loopback IP address, and should be configured to the hostname.

To move onto the network:

1. Connect the host to the network using DHCP.
2. Configure the hostname to the loopback IP address only.

7.3.3 Moving from On-Network to Off-Network (Static IP Address)

Follow this procedure if your host is on the network, using a static IP address, and you would like to move it off the network:

1. Configure the /etc/hosts file so the IP address and hostname can be resolved locally.
2. Take the host off the network.
3. There is no need to perform any steps to change the hostname or IP address.
4. If the instance was configured as part of a cluster, you must remove it from the cluster before you start the instance. For example, to remove an instance from a cluster if you used dynamic discovery, use the following commands:
   • On UNIX: ORACLE_HOME/opmn/bin/opmnctl config topology delete discover ORACLE_HOME/opmn/bin/opmnctl reload
   • On Windows: ORACLE_HOME\opmn\bin\opmnctl config topology delete discover ORACLE_HOME\opmn\bin\opmnctl reload

   How you remove it from the cluster depends on how the cluster was configured. See the chapter, "Configuring and Managing Clusters" in the Oracle Containers for J2EE Configuration and Administration Guide for more information.

7.3.4 Moving from On-Network to Off-Network (DHCP)

Follow this procedure if your host is on the network, using DHCP in loopback mode, and you would like to move it off the network:

1. Take the host off the network.
2. There is no need to perform any steps to change the hostname or IP address.
3. If the instance was configured as part of a cluster, you must remove it from the cluster before you start the instance. For example, to remove an instance from a cluster if you used dynamic discovery, use the following commands:
   • On UNIX: ORACLE_HOME/opmn/bin/opmnctl config topology delete discover ORACLE_HOME/opmn/bin/opmnctl reload
   • On Windows: ORACLE_HOME\opmn\bin\opmnctl config topology delete discover ORACLE_HOME\opmn\bin\opmnctl config reload

   How you remove it from the cluster depends on how the cluster was configured. See the chapter, "Configuring and Managing Clusters" in the Oracle Containers for J2EE Configuration and Administration Guide for more information.

7.4.1 Changing from a Static IP Address to DHCP

To change a host from a static IP address to DHCP:

1. Configure the host to have a hostname associated with the loopback IP address before you convert the host to DHCP.
2. Convert the host to DHCP. There is no need to update Oracle Application Server.

7.4.2 Changing from DHCP to a Static IP Address

To change a host from DHCP to a static IP address:

1. Configure the host to use a static IP address.
2. There is no need to update Oracle Application Server.