9 Upgrading High Availability Configurations

9.3.1 Overview of the Transformation Procedure

Table 9-3 provides a summary of the steps involved with transforming an Oracle Application Server 10g (9.0.4) OracleAS Active Failover Cluster environment into an Oracle Application Server 10g Release 2 (10.1.2.0.2) OracleAS Cluster (Identity Management) environment.

The remaining sections describe each of these overview steps in more detail.

9.3.2 Back Up the Entire Environment, Including the Middle-Tier and Infrastructure Installations

Before you transform your 10g (9.0.4) OracleAS Active Failover Cluster environment to a 10g Release 2 (10.1.2) OracleAS Cluster (Identity Management) environment, it is important that you back up all the Oracle home installations.

Executing a backup of the current environment prior to any changes such as an upgrade is critical in order to ensure the system can be restored back to its original state in case of any errors or problems during the actual upgrade procedures. Ideally a restore test of the backup to a test environment should also be performed to further ensure the backup copy is valid and working as expected. These steps should all be done before starting the actual upgrade and can help minimize downtime in case a restore is required.

9.3.3 Upgrade the Database That Hosts the OracleAS Metadata Repository

Before you can upgrade the OracleAS Metadata Repository, you must be sure the database that hosts the repository is upgraded to a version supported by 10g Release 2 (10.1.2).

When you installed the Oracle Application Server 10g (9.0.4) OracleAS Active Failover Cluster, Oracle Universal Installer automatically installed and configured an Oracle9i (9.0.1.5) database to host the OracleAS Metadata Repository.

To upgrade this database to Oracle9i Release 2 (9.2.0.6), you must install a new Oracle9i Release 2 (9.2.0.1) database in a new Oracle home, patch the database to Oracle9i Release 2 (9.2.0.6), and then run the Database Upgrade Assistant from the Oracle9i Release 2 (9.2.0.6) Oracle home.

The database upgrade procedure involves the following steps.

Step 1 Stop the Middle Tiers, the OracleAS Identity Management Services, and the 10g (9.0.4) Metadata Repository Database

For information on starting and stopping Oracle Application Server components, see "Starting and Stopping" in the Oracle Application Server Administrator's Guide.

Step 2 Install a New Oracle9i Release 2 (9.2.0.1) Oracle Home

Use the following procedure to install a Oracle9i Release 2 (9.2.0.1) in a new Oracle home on the same host as the 10g (9.0.4) OracleAS Metadata Repository database:

1. Log in to the computer on which 10g (9.0.4) OracleAS Metadata Repository database instance is installed, as the same operating system user that performed the 10g (9.0.4) installation.

   
   

   Note: You must be logged in as a member of the dba operating system group.

   
   

2. Set the required environment variables, as defined in the section "Environment Variables" in the "Requirements" chapter of the Oracle Application Server Installation Guide.

   In particular, be sure to set following variables so they do not reference any Oracle home directories:

   • PATH

   • CLASSPATH

   • LD_LIBRARY_PATH

   • SHLIB_PATH

   In addition, be sure the following environment variables are not set:

   • TNS_ADMIN

   • ORACLE_HOME

   • ORACLE_SID

3. Mount the CD-ROM and start the installer.

   
   

   See Also: Oracle Application Server Installation Guide for detailed instructions about starting Oracle Universal Installer on your platform

   
   

4. Refer to Table 9-4 for information on the options you should select on each screen.

5. After the End of Installation screen appears, exit Oracle Universal Installer and then verify that Oracle Internet Directory and Oracle Application Server Single Sign-On are functioning and accessible in the new 10g Release 2 (10.1.2) Oracle home.

   
   

   See Also: Oracle Application Server Administrator's Guide, Chapter 1, "Accessing the Single Sign-On Server"

   
   

Step 3 Apply the Oracle9i Release 2 (9.2.0.6) Patchset

Before you install the patchset, carefully review the patchset release notes.

Note that the Oracle UNIX Distributed Lock Manager (UDLM) 3.3.4.8 patch might be required before applying the patchset in an Oracle Real Application Clusters with Sun Clusterware environment.

Start Oracle Universal Installer and use the information in Table 9-5 to perform the patchset installation.

Step 4 Prepare to Upgrade the Database

Perform the following steps to prepare for the database upgrade:

1. Review Chapter 2, "Preparing to Upgrade," in Oracle9i Database Migration, which is available as part of the Oracle9i Database Release 2 Documentation Library on the Oracle Technology Network (OTN):

   http://www.oracle.com/technology/documentation/oracle9i.html
   
   

2. Read and perform the steps in the following subsections of the section, "Upgrade the Database Manually," in Oracle9i Database Migration:

   • "System Considerations and Requirements"

   • "Prepare the Database to Be Upgraded"

3. Copy configuration files from the Oracle9i (9.0.1.5) Oracle home to the destination Oracle home.

   Specifically, be sure to perform the following tasks on all nodes in which this cluster database has instances configured:

   • If your parameter files reside within the Oracle9i (9.0.1.5) Oracle home (as opposed to outside the Oracle home), then copy the parameter files to the new Oracle home.

     By default, Oracle looks for the parameter file in ORACLE_HOME/dbs on UNIX platforms. The parameter file can reside anywhere you wish, but it should not reside in the Oracle9i (9.0.1.5) Oracle home after you upgrade to the new database release.

   • If your initdb_name.ora file resides within the destination Oracle home, then move or copy the file to the new Oracle home.

     By default, initdb_name.ora should reside in ORACLE_HOME/admin/db_name/pfile directory.

   • If you have a password file that resides within the Oracle9i (9.0.1.5) Oracle home, then move or copy the password file to the new Oracle home.

     The name and location of the password file are operating system specific. On UNIX platforms, the default password file is ORACLE_HOME/dbs/orapwsid.

   • Copy the following file from the Oracle9i (9.0.1.5) Oracle home to the new destination Oracle home:

     ORACLE_HOME/network/admin/tnsnames.ora
     
     

4. Adjust the database initialization parameters in your parameter file for use with the newly upgraded database, as shown in Table 9-6.

   Table 9-6 Summary of Initialization Parameters to Modify Before Upgrading to Oracle9i Release 2 (9.2.0.6)

   Parameter	Value for the New Oracle9i Release 2 (9.2.0.6) Database
   SHARED_POOL_SIZE	At least 48 MB
   PGA_AGGREGATE_TARGET	At least 24 MB
   LARGE_POOL_SIZE	At least 8 MB
   COMPATIBLE	9.0.1.3
   USER_DUMP_DEST	Make sure this parameter points to the new Oracle9i Release 2 (9.2.0.6) Oracle home.
   BACKGROUND_DUMP_DEST	Make sure this parameter points to the new Oracle9i Release 2 (9.2.0.6) Oracle home.
   CORE_DUMP_DEST	Make sure this parameter points to the new Oracle9i Release 2 (9.2.0.6) Oracle home.

   
   

5. Temporarily adjust the database initialization parameters shown in Table 9-7 during the duration of the upgrade.

   After the upgrade, you must return these parameters to their pre-upgrade values.

   Table 9-7 Initialization Parameters to Modify During the Upgrade to the Oracle9i Release 2 (9.2.0.6) Database

   Parameter	Value for the Duration of the Oracle9i Release 2 (9.2.0.6) Upgrade
   REMOTE_LOGIN_PASSWORDFILE	NONE
   CLUSTER_DATABASE	FALSE; after the upgrade, you must set this parameter to TRUE.

   
   

6. Make sure that the following environment variables point to the destination Oracle home:

   • ORACLE_HOME

   • PATH

   • ORA_NLS33

   • LD_LIBRARY_PATH

7. Make sure the ORACLE_SID environment variable is set to the System Identifier (SID) of the 10g (9.0.4) Infrastructure database.

Step 5 Perform the Database Upgrade

Perform the manual upgrade procedure, using the following steps:

1. Read and perform the steps in the following "Upgrade the Database" subsection of the section, "Upgrade the Database Manually," in Oracle9i Database Migration.

2. Log in to the system using the account that owns the new Oracle9i Release 2 (9.2.0.1) Oracle home.At the system prompt, change directory to the following directory in the destination Oracle home that you just installed and patched:

   DESTINATION_ORACLE_HOME/rdbms/admin
   
   

3. Start SQL*Plus and connect to the destination database instance as a user with SYSDBA privileges.

4. Start up the database by issuing the following command:

   SQL> STARTUP MIGRATE
   
   

   You may need to use the PFILE option to specify the location of your initialization parameter file.

5. Set the system to spool results to a log file for later verification of success:

   SQL> SPOOL upgrade.log
   
   

6. Run u0900010.sql to perform the database upgrade operation, as follows:

   SQL> @u0900010.sql
   
   

   Make sure you follow these guidelines when you run the script:

   • You must use the version of the script installed in new Oracle home.

   • You must run the script in the new Oracle home.

   The u0909910.sql script creates and alters certain dictionary tables. It also runs the catalog.sql and catproc.sql scripts that come with the Oracle9i Release 2 (9.2.0.6) patchset. These scripts create the system catalog views and all the necessary packages for using PL/SQL.

7. Run the cmpdbmig.sql script to upgrade components that can be upgraded while connected with SYSDBA privileges:

   SQL> @cmpdbmig.sql
   
   

8. Turn off the spooling of script results to the log file:

   SQL> SPOOL OFF
   
   

   Then, check the contents of the upgrade.log file that was generated by the SPOOL command. Verify that the packages and procedures compiled successfully. Correct any problems you find in this file and rerun the appropriate upgrade scripts, if necessary. You can rerun the scripts as many times as necessary.

9. Shutdown and restart the instance to reinitialize the system parameters for normal operation:

   SQL> SHUTDOWN IMMEDIATE
   SQL> STARTUP
   
   

   The restart will also initialize the Jserver JAVA Virtual Machine and other components.

Step 6 Upgrade the Required Database Components

Use the following guidelines to upgrade the components that existed in the Oracle9i (9.0.1.5) database.

• Oracle Spatial

  Perform the following steps to upgrade Oracle Spatial:

  1. Connect to the database instance as a user with SYSDBA privileges.

  2. Unlock the MDSYS account and reset the password.

  3. Grant the required privileges to the MDSYS user by running the following script:

     SQL> @$ORACLE_HOME/md/admin/mdprivs.sql
     
     

  4. Connect as MDSYS.

  5. Perform the migration by running the following procedure:

     SQL> @$ORACLE_HOME/md/admin/c901u920.sql
     
     

• Oracle Intermedia

  Upgrade instructions for Oracle interMedia can be found in the following directory in the destination Oracle home:

  DESTINATION_ORACLE_HOME/ord/im/admin/README.txt
  
  

• Oracle Text

  Use the following procedure to upgrade the Oracle Text database component:

  1. Connect to the database instance as a user with SYSDBA privileges.

  2. If the instance is running, shut it down using the following command:

     SQL> SHUTDOWN IMMEDIATE
     
     

  3. Start up the instance in RESTRICT mode:

     SQL> STARTUP RESTRICT
     
     

     You may need to use the PFILE option to specify the location of your initialization parameter file.

  4. Set the system to spool results to a log file for later verification of success:

     SQL> SPOOL text_upgrade.log
     
     

  5. Unlock the CTXSYS account and reset the password.

  6. Run s0902000.sql to grant new, required database privileges to the user CTXSYS.

     SQL> @$ORACLE_HOME/ctx/admin/s0902000.sql
     
     

  7. Connect to the database instance as user CTXSYS.

  8. Run u0902000.sql to upgrade the CTXSYS schema:

     SQL> @$ORACLE_HOME/ctx/admin/u0902000.sql
     
     

  9. Turn off the spooling of script results to the log file:

     SQL> SPOOL OFF
     

Step 7 Database Post-Upgrade Tasks

You must perform the following post-upgrade tasks on the upgraded database before you can upgrade the OracleAS Identity Management components:

1. Run the initxml.sql and utlrp.sql scripts on the upgraded database.

   The following procedure is necessary to make sure that no invalid objects remain in the database after the upgrade to Oracle9i Release 2 (9.2.0.6):

   1. Log in to the system as the owner of the Oracle home directory of the new Oracle9i Release 2 (9.2.0.6)

   2. At the system prompt, change to the ORACLE_HOME/rdbms/admin directory.

   3. Start SQL*Plus and connect to the database instance as a user with SYSDBA privileges.

   4. Start up the database by issuing the following command:

      SQL> STARTUP
      
      

      You may need to use the PFILE option to specify the location of your initialization parameter file.

   5. Set the system to spool results to a log file for later verification of success:

      SQL> SPOOL initxml.log
      
      

   6. Run initxml.sql, as follows:

      SQL> @initxml.sql
      
      

   7. Run the utlrp.sql as follows:

      SQL> @utlrp.sql
      
      

   8. Turn off the spooling of script results to the log file:

      SQL> SPOOL OFF
      
      

   After going through all necessary steps, if you find invalid JAVA CLASS or UNDEFINED objects, you may recompile them individually.

2. Adjust the following initialization parameters back to their pre-upgrade settings:

   1. Set REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE in the parameter file.

   2. Set CLUSTER_DATABASE initialization parameter to TRUE.

3. Upgrade SRVM in the Oracle9i (9.0.1.5) Real Application Clusters environment to Oracle9i Release 2 (9.2.0.6):

   1. Set your ORACLE_HOME environment variable to your Oracle9i (9.0.1.5) Oracle home.

   2. Stop the GSD processes on all nodes.

      ps -ef |grep jre
      kill JRE_PID
      
      

   3. Backup the SRVM configuration information.

      ORACLE_HOME/bin/srvconfig -exp /tmp/srvconfig_9iR1
      
      

   4. Set your ORACLE_HOME environment variable to your Oracle9i Release 2 (9.2.0.6) Oracle home.

   5. Re-initialize and restore the SVRM configuration information.

      ORACLE_HOME/bin/srvconfig -imp /tmp/srvconfig_9iR1
      ORACLE_HOME/bin/srvconfig -init -f
      
      

   6. Start the Oracle9i Release 2 (9.2.0.6) GSD on all nodes.

      ORACLE_HOME/bin/gsdctl start
      
      

   7. Verify that srvctl works.

      ORACLE_HOME/bin/srvctl status database -d dbname
      
      

4. Apply patch 4015165 to the newly upgraded Oracle9i Release 2 (9.2.0.6) database.

   The patch is available from OracleMetaLink (http://metalink.oracle.com).

5. Configure the database listener on each node of the Real Application Clusters environment, as follows:

   1. Shutdown the database and the database listener:

   2. Copy the listener.ora file from the Oracle9i (9.0.1.5) Oracle home to the following directory in the destination Oracle home:

      DESTINATION_ORACLE_HOME/network/admin directory
      
      

   3. Edit the listener.ora file and replace all occurrences of the Oracle9i (9.0.1.5) Oracle home path with the destination Oracle home path.

   4. Start the listener and OracleAS Metadata Repository database from destination Oracle home.

6. Start OPMN and OPMN managed processes, and then start the Oracle Application Server Control console on all nodes:

   ORACLE_HOME/opmn/bin/opmnctl startall
   ORACLE_HOME/bin/emctl start iasconsole
   

9.3.4 Use Oracle Universal Installer to Upgrade OracleAS Identity Management

The following sections describe how to upgrade OracleAS Identity Management after you have upgraded the database to a supported version.

The instructions in these sections apply to the first OracleAS Identity Management installation that resides in the source Oracle home where the Oracle9i (9.0.1.5) database was installed:

• Overview of the OracleAS Identity Management Components

• OracleAS Identity Management Pre-Upgrade Tasks

• Using Oracle Universal Installer to Upgrade OracleAS Identity Management

• Performing Post-Upgrade Tasks for the First OracleAS Identity Management Oracle Home

9.3.5 Use Oracle Universal Installer to Install OracleAS Identity Management on the Other Cluster Nodes

After you have upgraded the OracleAS Metadata Repository database and the OracleAS Identity Management installation on Node 1, you can then install a new 10g Release 2 (10.1.2) OracleAS Identity Management Oracle home on each of the OracleAS Cluster (Identity Management) nodes.

These new installations will operate as members of the OracleAS Cluster (Identity Management) cluster and share the same OracleAS Metadata Repository as the OracleAS Identity Management installation on Node 1.

Refer to the following sections for more information:

• Installing OracleAS Identity Management on a Cluster Node

• Manually Copying the osso.conf Configuration File

• Reconfiguring the Server Load Balancer

ORACLE_HOME/Apache/Apache/conf/osso/osso.conf

9.3.6 Upgrade the Middle Tiers

Refer to Chapter 4, "Upgrading the Middle Tier" for complete instructions on upgrading your Oracle Application Server middle-tier installations.

9.3.7 Upgrade the Component Schemas in the OracleAS Metadata Repository

After you have upgraded the database that hosts the OracleAS Metadata Repository, upgraded and installed the OracleAS Identity Management installations, and upgraded the middle-tier installations, you can then use the Metadata Repository Upgrade Assistant (MRUA) to upgrade the component schemas in the repository.

Refer to Section 7.4, "Task 4: Run the Metadata Repository Upgrade Assistant (MRUA)" for complete instructions on running MRUA.

In addition, refer to the following known problems and workarounds when upgrading the OracleAS Metadata Repository in an OracleAS Cluster (Identity Management) environment:

• Manually Creating the B2B Tablespaces Before Running MRUA

• Oracle Ultra Search Component Schema Not Upgraded Successfully

9.3.8 Optionally Decommission and Deinstall the Source Oracle Homes

Refer to the instructions in the following sections for more information on decommissioning and deinstalling your source Oracle homes:

• Section 4.9, "Task 8: Decommission the Middle-Tier Source Oracle Home"

• Section 5.8, "Task 7: Decommission the OracleAS Identity Management Source Oracle Home"

9.4.1 About Rack-Mounted Identity Management and OracleAS Cluster (Identity Management)

Following the release of Oracle Application Server 10g (9.0.4), a procedure was released for deploying multiple Identity Management instances against one Infrastructure Metadata Repository. This procedure was released in the form of a whitepaper titled Highly Available Identity Management example - Rack Mounted Identity Management and it was made available to customers on the Oracle Technology Network (OTN) at:

http://www.oracle.com/technology/products/ias/hi_av/index.html

Note that the link to the whitepaper on OTN might actually be shown as Highly Available Identity Management Deployment Example - Multi-box Identity Management.

With the release of Oracle Application Server 10g Release 2 (10.1.2), an "out-of-the-box" Multiple Identity Management solution is now available. This configuration is known as OracleAS Cluster (Identity Management).

The following sections provide step-by-step instructions for customers who wish to upgrade their 10g (9.0.4) Multiple Identity Management deployment to an OracleAS 10.1.2 Clusters (Identity Management) deployment.

The testing and steps provided in this document are based upon an OracleAS Identity Management implementation deployed on RedHat Linux 3.0. The steps provided in this document, however, apply to any Unix platform.

9.4.2 OracleAS Cluster (Identity Management) Upgrade Requirements

The following sections describe the requirements you must meet in order to transform your highly available environment from 10g (9.0.4) Rack-Mounted Identity MAnagement to OracleAS Cluster (Identity Management):

• OracleAS Identity Management Configuration Requirements

• Requirements for Colocated Versus Distributed OracleAS Identity Management

• OracleAS Metadata Repository Storage Requirements

• OracleAS Cluster (Identity Management) Backup Requirements

9.4.3 Overview of the OracleAS Cluster (Identity Management) Transformation Process

The General steps for transforming an OracleAS 10g (9.0.4) Identity Management implementation to an OracleAS 10g (10.1.2.0.2) Clusters (Identity Management) implementation are shown in Table 9-12.

9.4.4 Upgrading the Database That Hosts the OracleAS Metadata Repository

Before you can upgrade to OracleAS Cluster (Identity Management), you must upgrade the database that hosts the OracleAS Metadata Repository to a supported database.

For detailed instructions on upgrading the database that hosts the OracleAS Metadata Repository, see Section 7.1, "Task 1: Upgrade the Database That Hosts the OracleAS Metadata Repository".

9.4.5 Upgrading the Middle Tiers

After you upgrade the database that hosts the OracleAS Metadata Repository, you should upgrade any middle-tier installations that use the Rack-Mounted Identity Management Infrastructure.

Refer to Chapter 4, "Upgrading the Middle Tier" for more information.

9.4.6 Upgrading the First OracleAS Identity Management Instance

After the database that hosts the OracleAS Metadata Repository has been upgraded to a supported version, and after the middle tiers have been upgraded to 10g Release 2 (10.1.2), you can now upgrade the first OracleAS Identity Management Oracle home in the Rack-Mounted Identity Management configuration.

When you upgrade the first OracleAS Identity Management Oracle home, you also upgrade the OracleAS Identity Management schemas in the OracleAS Metadata Repository.

Note that in an OracleAS Cluster (Identity Management), the Identity Management instances are clustered together in a Distributed Configuration Management (DCM) Cluster. This ensures synchronization between the configurations of the different Identity Management components on all of the Identity Management instances.

To upgrade the first OracleAS Identity Management Oracle home, use the following steps.

1. Make sure that the other OracleAS Identity Management Instances in the Rack-Mounted Identity Management environment are down.

   Only the OracleAS Identity Management instance that you are upgrading first should be up and running. If necessary, shut down the other OracleAS Identity Management instances.

2. Configure the Load Balancer to direct traffic only to the OracleAS Identity Management instance you are about to upgrade

   All Requests should be directed only to the OracleAS Identity Management instance you are about to upgrade. The other OracleAS Identity Management instances in the Rack-Mounted Identity Management environment should be shut down.

3. Use the Oracle Application Server 10g Release 2 (10.1.2) installation procedure to upgrade the OracleAS Identity Management instance.

   Refer to Section 5.5.2, "Upgrading OracleAS Identity Management in a Non-Colocated 10g (9.0.4) Infrastructure" for complete instructions on upgrading the first OracleAS Identity Management Oracle home.

4. Perform any post-upgrade procedures that apply to your OracleAS Identity Management environment.

   Refer to Section 5.6, "Task 5: Complete the OracleAS Identity Management Upgrade" for more information.

5. Make sure that the Oracle HTTP Server listener is configured correctly.

   Edit the following Oracle HTTP Server configuration file and make sure that the ServerName directive is set to the virtual host (for example, imhost.domain.com) and not to the physical host:

   ORACLE_HOME/Apache/Apache/conf/httpd.conf
   
   

6. Configure OracleAS Single Sign-On to accept authentication requests.

   Run the following command to verify that OracleAS Single Sign-On is configured correctly:

   ORACLE_HOME/sso/bin/ssocfg.sh http imhost.domain.com 7777
   
   

   In this example, imhost.domain.com is the address configured at the load balancer for HTTP requests. The default HTTP Listener port is 7777, but this port may differ for your specific installation.

7. Re-register the instance with OracleAS Single Sign-On:

   Run the following command:

   ORACLE_HOME/sso/bin/ssoreg.sh
       -oracle_home_path orcl_home_path
       -site_name instance_name_you_specified_during_upgrade
       -config_mod_osso TRUE
       -mod_osso_url effective_URL_of_the_partner_application
       -u userid 
   
   

   In this example:

   • The effective_URL_of_the_partner_application is in this URL format:

     http://virtual_servername:port
     
     

   • Replace userid with the Oracle owner.

   Note that at this point in the procedure, the upgraded OracleAS Identity Management Oracle home should be a fully working 10g Release 2 (10.1.2) OracleAS Identity Management instance running against the Real Application Clusters database. The load balancer is still pointing to only this new, upgraded instance.

8. Create a Distributed Configuration Management (DCM) cluster that the other OracleAS Identity Management instances can join:

   1. Enter the DCM command-line shell:

      ORACLE_HOME/dcm/bin/dcmctl shell
      
      

   2. Create a new Cluster:

      DCM> createcluster -cl IMcluster
      
      

      In this example, IMCluster is the name you assign to the cluster.

   3. Join the DCM cluster as the first instance:

      DCM> joincluster -cl IMcluster
      
      

      At this point the instance will be stopped.

   4. Restart the instance:

      opmnctl startall
      
      

      A new cluster has now been created with the upgraded IM instance as its sole member.

9.4.7 Using Metadata Repository Upgrade Assistant to Upgrade the Component Schemas in the OracleAS Metadata Repository

1. Make sure that the OracleAS Identity Management instance (including Oracle Internet Directory) that you upgraded in Section 9.4.6, "Upgrading the First OracleAS Identity Management Instance" is up and running.

   If it is not running, start the Identity Management instance (including Oracle Internet Directory) as follows:

   ORACLE_HOME/opmn/bin/opmnctl startall
   
   

2. Upgrade the Metadata Repository in the newly upgraded database as described in Section 7.4, "Task 4: Run the Metadata Repository Upgrade Assistant (MRUA)", with the following exception:

   On the MRUA command line, enter the address of the load balancer in place of the oid_host and oid_ssl_port arguments.

   Note that the values you enter for the -oid_host argument and -oid_ssl_port arguments must match the value of the corresponding properties defined in following configuration file in the Identity Management Oracle home:

   IDENTITY_MANAGEMENT_HOME/config/ias.properties
   
   

   For example:

   OIDhost=sys42.acme.com
   OIDsslport=636
   
   

3. When MRUA finishes processing, verify that the schemas have been upgraded, as described in Section 7.4.9, "Using a SQL Query to Verify the Success of the OracleAS Metadata Repository Upgrade"

4. Complete the OracleAS Metadata Repository upgrade using the instructions in the following sections:

   • Section 7.5.1, "Completing the OracleAS Portal Schema Upgrade Process"

   • Section 7.5.2, "Completing the OracleAS Wireless Schema Upgrade Process".

9.4.8 Installing Subsequent OracleAS Cluster (Identity Management) Instances

After you upgrade the first OracleAS Identity Management instance in the cluster, and after you upgrade the OracleAS Metadata Repository, you can then install the additional OracleAS Identity Management instances in the OracleAS Cluster (Identity Management):

1. Make sure that the Oracle Internet Directory is up and running on the first OracleAS Identity Management instance.

2. Make sure that the OracleAS Metadata Repository database and listener are up and running.

3. Make sure that the Load Balancer is configured to direct traffic only to the first Identity Management instance.

4. Install the new 10g Release 2 (10.1.2) OracleAS Identity Management Oracle home by following the instructions in the section "Installing OracleAS Cluster (Identity Management) on Subsequent Nodes," in the Oracle Application Server Installation Guide.

5. Reconfigure Load Balancer and test the installation.

   After a successful installation of the subsequent OracleAS Identity Management Oracle home, configure the Load Balancer to route requests to the new instance.

6. Repeat this procedure for any additional and subsequent OracleAS Identity Management installations that will be part of the cluster.

9.4.9 About Upgrading a Distributed OracleAS Cluster (Identity Management) Environment

In a distributed OracleAS Cluster (Identity Management) environment, the Oracle Internet Directory is installed in a separate Oracle home from the other OracleAS Identity Management components.

The procedure for upgrading a distributed OracleAS Identity Management components is the same as that for upgrading colocated OracleAS Identity Management installations, with the following exception:

1. Upgrade the Internet Directory (OID) Oracle Home as described in Steps 1-5 of Section 9.4.6, "Upgrading the First OracleAS Identity Management Instance".

2. Create the Distributed Configuration Management cluster, as described in step 8 of Section 9.4.6, "Upgrading the First OracleAS Identity Management Instance".

3. Verify that the OID has been upgraded and works successfully.

4. Upgrade the OracleAS Single Sign-On and Oracle Delegated Administration Services Oracle Home, as described in Section 9.4.8, "Installing Subsequent OracleAS Cluster (Identity Management) Instances".

5. Re-associate OracleAS Single Sign-On as described in Step 7 of Section 9.4.6, "Upgrading the First OracleAS Identity Management Instance".