9 Upgrading High Availability Configurations

9.2.1 Overview of the OracleAS Cold Failover Cluster Infrastructure Upgrade

This section provides an outline of the steps you must perform to upgrade your 10g (9.0.4) OracleAS Cold Failover Cluster environment to 10g Release 2 (10.1.2).

Note that this procedure assumes that your OracleAS Cold Failover Cluster consists of two nodes (Node 1 and Node 2) and a single shared disk that is used by both nodes. The procedure also assumes that you use Microsoft Cluster Administrator to manage the cluster environment.

Table Table 9-2 summarizes the major steps in the OracleAS Cold Failover Cluster upgrade process.

9.2.2 Backing Up the 10g (9.0.4) OracleAS Cold Failover Cluster Infrastructure

Before you upgrade the Infrastructure it is important that you perform a full backup of the entire OracleAS Cold Failover Cluster environment. You will use this backup to restore the 10g (9.0.4) Infrastructure later in the upgrade procedure.

To backup the OracleAS Cold Failover Cluster infrastructure:

1. Start the Microsoft Cluster Server (MSCS) Cluster Adminstrator.

   Windows 2000: Start > Programs > Administrative Tools > Cluster Administrator

   Windows 2003: Start > Administrative Tools > Cluster Administrator

2. Take the Oracle Application Server resources offline:

   1. In the left pane of Cluster Administrator, expand the Groups folder and select the name of the cluster group that contains your Oracle Application Server resources.

      For example, if you named the cluster group as904, then click as904.

   2. In the right pane, take each of the resources shown in Table 9-3 offline by right-clicking the resource and then selecting Take Offline from the context menu.

   Table 9-3 Oracle Application Server Services and Corresponding Cluster Administrator Resources

   Service	Format of Service Name	Format of Resource Name
   Application Server Control	OracleORACLE_HOMEASControl	OracleORACLE_HOMEASControl
   Oracle Process Manager and Notification Server (OPMN)	OracleORACLE_HOMEProcessManager	OracleORACLE_HOMEProcessManager
   OracleAS Metadata Repository database	OracleServiceSID	SID
   OracleAS Metadata Repository database listener	OracleORACLE_HOMETNSListenerFslvirtual_host_name	OracleORACLE_HOMETNSListenerFslvirtual_host_name

   
   

3. From the Services control panel, check to be sure that the services shown in Table 9-3 are stopped.

   Display the Services control panel as follows:

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

4. When you are sure all the required services and cluster groups are stopped, back up the Infrastructure by copying the entire Infrastructure directory structure on the shared disk to a new directory.

   For example, if the Oracle home for your OracleAS Infrastructure is F:\oracle\as904, then use the following command to backup the entire directory:

   copy F:\oracle\as904 G:\backup\as904
   

   
   

   Important Notes: Consider the following before starting the upgrade to 10g Release 2 (10.1.2): The admin and oradata directories associated with the OracleAS Metadata Repository database must be backed up before proceeding with the upgrade procedure. By default, the admin and oradata directories reside inside the Oracle home. However, if you have configured the installation so that these directories and their contents reside outside of the Oracle home, then be sure to back up the admin and oradata database directories as well. This backup of the Oracle Application Server Cold Failover Cluster Infrastructure directory structure is necessary because you will use these backup directories to restore the 10g (9.0.4) Infrastructure later in the OracleAS Cold Failover Cluster upgrade procedure.

   
   

5. Use the Windows Services control panel to start all the Infrastructure services shown in Table 9-3.

6. Start the database and listener as follows:

   ORACLE_HOME\bin\lsrnctl start
   ORACLE_HOME\bin\sqlplus "/ as sysdba"
   SQL> startup
   SQL> exit
   

9.2.3 Preparing to Upgrade to 10g Release 2 (10.1.2) From Node 1

Use the following procedure to perform the pre-installation steps on Node 1.

Step 1 Be Sure You Have Backed Up the Oracle Application Server Cold Failover Cluster Infrastructure Directories

You must back up the Infrastructure directories as directed in Section 9.2.2, "Backing Up the 10g (9.0.4) OracleAS Cold Failover Cluster Infrastructure" before you start the upgrade process.

Later in the upgrade procedure, you will be asked to restore the directories to their previous 10g (9.0.4) state. If a valid backup of the 10g (9.0.4) Infrastructure is not available, you will not be able to complete the upgrade to 10g Release 2 (10.1.2).

Step 2 From Cluster Administrator, Delete the Application Server Resources

1. In Cluster Administrator, open the application server group and delete each of the resources that you took offline in Section 9.2.2, "Backing Up the 10g (9.0.4) OracleAS Cold Failover Cluster Infrastructure".

   The resources include:

   • The OracleAS Metadata Repository database (for example, asdb)

   • The database listener

   • Oracle Process Manager and Notification Server (OPMN)

   • Application Server Control

   Use Table 9-3 to identify the name of each resource, since the resource name is the same as the resource name used in the Services control panel.

   To delete a resource, right-click the resource and select Delete from the context menu; then, click Yes in the confirmation prompt.

Step 3 Make Sure that All the Infrastructure Services are Up and Running

From the Services control panel, check to be sure that the services shown in Table 9-3 are up and running on Node 1.

Note that in this step, you are starting the Windows services from the Windows operating system. The components have already been removed from Cluster Administrator and are no longer being managed by Microsoft Cluster Server.

Step 4 Verify that a Password File Exists and that the remote_login_passwordfile Parameter is Set to EXCLUSIVE mode

If you are not already using a password file for the OracleAS Metadata Repository database, create one using the ORAPWD command.

For example, if your database data files reside in the Oracle home, and your Oracle home is F:\oracle\as904, you can create a password file in the ORACLE_HOME\database directory called pwdasdb.ora by entering the following command:

ORAPWD FILE=F:\oracle\as904\database\pwdasdb.ora PASSWORD=sys_password

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

To check the remote_login_passwordfile database parameter value:

1. Execute the following SQL command:

   prompt> sqlplus "sys/sys_password@database_SID as sysdba"
   
   

   In this example, replace sys_password with the password for the database SYS account and replace database_SID with the database system identifier (SID).

2. Execute the following command in the SQL plus prompt:

   SQL> show parameter remote_login_passwordfile
   
   

3. If the value is set to NONE, then update the init.ora file parameter as follows:

   remote_login_passwordfile=EXCLUSIVE
   
   

   The init.ora is located on your installation hard drive. For example, if ORACLE_HOME is set to F:\oracle\as904, then the init.ora file would be in the following location:

   F:\oracle\as904\admin\database_name\pfile\init.ora
   
   

   In the preceding example, replace database_name with the database system identifier (SID).

   You must restart the database after making this change to the init.ora file.

9.2.4 Upgrading to 10g Release 2 (10.1.2) From Node 1

To upgrade Oracle Application Server Cold Failover Cluster (Infrastructure), you use Oracle Universal Installer. During the installation procedure, you must select Identity Management and Metadata Repository from the Select Installation Type screen. Oracle Universal Installer then locates the existing installation and prompts you to upgrade the existing 10g (9.0.4) Infrastructure.

When you upgrade the 10g (9.0.4) Infrastructure, Oracle Universal Installer creates a new database for the 10g Release 2 (10.1.2) OracleAS Metadata Repository and a new Oracle Internet Directory instance in a new Oracle home on the shared disk.

The new Oracle home is referred to as the destination Oracle home. The existing 10g (9.0.4) Oracle home is referred to as the source Oracle home.

The Oracle Universal Installer then upgrades the content and data in the 10g (9.0.4) source Oracle home to the 10g Release 2 (10.1.2) destination Oracle home.

1. Stop all the middle tiers that are using the services of the OracleAS Identity Management installation.

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

   
   

   Note: The account you log in to install or upgrade the OracleAS Metadata Repository must be listed as a member of the Administrators group.

   
   

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

   For example, you can use the Services control panel to verify that the OracleAS Metadata Repository database service and the database listener service are started. Use Table 9-3 to locate the name of the database and listener services in the Services control panel.

4. Make sure the Oracle Internet Directory server is up and running.

   To verify that Oracle Internet Directory is running, enter one of the following commands.

   
   

   Note: You may have to temporarily set the ORACLE_HOME environment variable to the Oracle Internet Directory Oracle home before running the ldapbind command. After you verify that the Oracle Internet Directory is running, you must then make sure the ORACLE_HOME environment variable is not defined before you start the 10g Release 2 (10.1.2) installer, as described later in this procedure.

   
   

   If you are running Oracle Internet Directory on a non-secure port:

   SOURCE_ORACLE_HOME\bin\ldapbind -p Non-SSL_port -h oid_host_name
   
   

   If you are running Oracle Internet Directory on a secure port:

   SOURCE_ORACLE_HOME\bin\ldapbind -p SSL_port -h oid_host_name -U 1
   
   

   These commands should return a "bind successful" message.

   
   

   See Also: "Syntax for LDIF and Command-Line Tools" in the Oracle Internet Directory Administrator's Guide for more information about the ldapbind utility

   
   
   
   

   Note: Oracle Internet Directory 10g (9.0.4) allows you to start and stop the directory service using OPMN or the oidctl utility. Before upgrading an OracleAS Identity Management Oracle home that contains Oracle Internet Directory, start the Oracle Internet Directory instance using the opmnctl utility or the Application Server Control Console. Do not use the oidctl utility; otherwise, Oracle Universal Installer will not be able to start and stop Oracle Internet Directory automatically during the upgrade process. The correct use of opmnctl and oidctl is described in the Chapter "Oracle Internet Directory Process Control–Best Practices" in the Oracle Internet Directory Administrator's Guide.

   
   

5. 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 the following environment variables are not set:

   • TNS_ADMIN

   • ORACLE_HOME

   • ORACLE_SID

6. If the ORACLE_HOME environment variable was previously set, restart the host computer after unsetting the variable.

   The system restart is necessary to clear the ORACLE_HOME variable from the system registry. If you do not restart the computer after clearing the ORACLE_HOME variable, the installation might report an error and prevent you from finishing the installation.

7. 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

   
   

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

9. 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"

   
   

9.2.5 Cleaning Up the OracleAS Cold Failover Cluster Infrastructure on Node 1

Use the following steps to clean up the OracleAS Cold Failover Cluster Infrastructure on Node 1 and prepare to update Node 2.

Step 1 Stop the OracleAS Infrastructure Services on Node 1, and Set the Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop the 10g Release 2 (10.1.2) services:

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ClientCache

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>TNSListenerFsl<VirtualHostName>

   • OracleService<SID>

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the 10g Release 2 (10.1.2) services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 2 Restart Node 1

When you restart Node 1, the shared disk is moved to Node 2. If an error occurs while adding the database service to Oracle Fail Safe, then restart Node 2 and try adding the database to Oracle Fail Safe again.

9.2.6 Configuring the Windows Registry, Oracle Inventory, and Services on Node 2

After you upgrade the OracleAS Infrastructure on Node 1, the next step in the OracleAS Cold Failover Cluster upgrade procedure is to update Node 2 so that the required Windows registry settings, Oracle inventory entries, and Windows services are available for the OracleAS Cold Failover Cluster.

Step 1 Review Your Options for Updating Node 2

Review the following information to determine whether or not the two nodes of your cluster are symmetrical.

The two nodes of an OracleAS Cold Failover Cluster are symmetrical if they have an identical:

• Hardware configuration (for example, the same memory and CPU specifications)

• Software configuration (for example, the same operating system version and patch level)

• Oracle configuration (for example, the same Oracle products and Oracle homes are installed on both nodes

If the two nodes of your OracleAS Cold Failover Cluster are not symmetrical, then skip the remaining steps in this section and go directly to Section 9.2.7, "Special Instructions for Updating Node 2 When Using Asymmetrical Configurations".

Step 2 Export the Oracle Registry Settings From Node 1

1. From Node 1, select Run from the Windows Start menu, and enter regedit in the resulting text field.

2. Locate and select the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle entry in the Windows registry.

3. Select Export Registry File from the Registry menu.

4. In the resulting dialog box, make sure that the Selected Branch radio button is selected and that the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle branch is selected.

5. Enter a name for the exported registry file and click Save.

   For example, enter oracle_registry_entries.

Step 3 Remove the Database Instance from Node 1

On node 1, run the following command to remove the 10g Release 2 (10.1.2) OracleAS Metadata Repository database instance that you just upgraded:

F:\oracle\as1012\bin> oradim -delete -sid sid

Step 4 Import the Registry Settings into the Windows Registry on Node 2

1. Log in to Node 2.

2. Double-click the oracle_registry_entries.reg file you created when you exported the registry entries from Node 1.

3. When prompted to add the registry entries, click Yes.

Step 5 Create and Start the Required Windows Services for 10g Release 2 (10.1.2)

To create the Windows services on Node 2, you can use the SC tool (sc.exe), which is a services control management tool provided by Microsoft.

To use the SC tool to create the required services on Node 2:

1. Oracle Process Manager and Notification Server (OPMN):

   sc create Oracle<home name>ProcessManager
      binPath= "ORACLE_HOME\opmn\bin\opmn.exe -S"
   
   

   For example:

   sc create OracleINFRAProcessManager
      binPath= "C:\oracle\appserv1\opmn\bin\opmn.exe -S"
   
   

2. Oracle Enterprise Manager 10g Application Server Control:

   sc create Oracle<home name>ASControl
      binPath= "ORACLE_HOME\bin\nmesrvc.exe"
   
   

   For example:

   sc create OracleINFRAASControl
      binPath= "C:\oracle\appserv1\bin\nmesrvc.exe"
   
   

3. The OracleAS Metadata Repository database listener:

   sc create Oracle<home name>TNSListener
      binPath= "ORACLE_HOME\bin\TNSLSNR"
   
   

   For example:

   sc create OracleINFRATNSListener
      binPath= "C:\oracle\appserv1\bin\TNSLSNR"
   
   

4. The OracleAS Metadata Repository database:

   sc create OracleService<oracle_sid>
      binPath= "ORACLE_HOME\bin\oracle.exe oracle_sid"
   
   

   Note that oracle_sid should be in upper case. For example:

   sc create OracleServiceORCL
      binPath= "C:\oracle\appserv1\bin\ORACLE.EXE ORCL"
   

Step 6 Copy the Oracle Inventory from Node 1 to Node 2

The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

The Oracle inventory information is stored in Extensible Markup Language (XML) format in a single directory structure on the host. The inventory is usually located in the following directory on Windows systems:

C:\Program Files\Oracle\Inventory

You can always find the location of the inventory by selecting the following registry key in the Windows registry and viewing the value of the inst_loc string:

\\HKEY_LOCAL_MACHINE\\Software\Oracle\

To copy the Oracle Inventory to Node 2, select the entire directory (for example, C:\Program Files\Oracle\Inventory) and copy it to the same location on Node 2.

Step 7 Add Required Paths to the PATH Environment Variable

Use the System control panel to add the following to the beginning of the Windows PATH variable:

%ORACLE_HOME%\bin;%ORACLE_HOME%\jlib;

Step 8 Skip to Section 9.2.8, "Using MRUA to Upgrade the OracleAS Metadata Repository from Node 2"

Unless the nodes of the cluster are asymmetrical, skip Section 9.2.7 and go directly to Section 9.2.8.

9.2.7 Special Instructions for Updating Node 2 When Using Asymmetrical Configurations

If the two nodes in your OracleAS Cold Failover Cluster are not symmetrical, refer to the following procedures to update the configuration of Node 2.

Step 1 Remove the Database Instance from Node 1

On node 1, run the following command to remove the 10g Release 2 (10.1.2) OracleAS Metadata Repository database instance that you just upgraded:

F:\oracle\as1012\bin> oradim -delete -sid sid

Step 2 From Node 1, Delete the 10g Release 2 (10.1.2) Oracle Home and Restore the 10g (9.0.4) Oracle Home

1. On Node 1, delete the 10g Release 2 (10.1.2) destination Oracle home from the shard disk.

2. Delete the 10g (9.0.4) source Oracle home from the shared disk.

3. Restore the 10g (9.0.4) Infrastructure directories that you backed up in Section 9.2.2, "Backing Up the 10g (9.0.4) OracleAS Cold Failover Cluster Infrastructure".

   For example, copy the following backed up directories described in Step 1 to their original locations:

   copy G:\backup\as904 F:\oracle\as904
   

   
   

   Note: If the 10g (9.0.4) oradata and admin directories were stored outside of the Infrastructure Oracle home, be sure to restore them to their original directories.

   
   

Step 3 From Node 2, Start the 10g (9.0.4) Infrastructure Services

1. Log in to Node 2 as the same operating system user that performed the 10g (9.0.4) installation.

   
   

   Note: The account you log in to install or upgrade the OracleAS Metadata Repository must be listed as a member of the Administrators group.

   
   

2. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

3. Start the 10g (9.0.4) services:

   • OracleService<SID>

   • Oracle<OracleHomeName>TNSListenerFsl<VirtualHostName>

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>ClientCache

   • Oracle<OracleHomeName>ASControl

   To start a service, right-click the service and select Start from the pop-up menu.

Step 4 Verify that a Password File Exists and that the remote_login_passwordfile Parameter is Set to EXCLUSIVE mode

If you are not already using a password file for the OracleAS Metadata Repository database, create one using the ORAPWD command.

For example, if your database data files reside in the Oracle home, and your Oracle home is F:\oracle\as904, you can create a password file in the ORACLE_HOME\database directory called pwdasdb.ora by entering the following command:

ORAPWD FILE=F:\oracle\as904\database\pwdasdb.ora PASSWORD=sys_password

To check the remote_login_passwordfile database parameter value:

1. Execute the following SQL command:

   prompt> sqlplus "sys/sys_password@database_SID as sysdba"
   
   

   In this example, replace sys_password with the password for the database SYS account and replace database_SID with the database system identifier (SID).

2. Execute the following command in the SQL plus prompt:

   SQL> show parameter remote_login_passwordfile
   
   

3. If the value is set to NONE, then update the init.ora file parameter as follows:

   remote_login_passwordfile=EXCLUSIVE
   
   

   The init.ora is located on your installation hard drive. For example, if ORACLE_HOME is set to F:\oracle\as904, then the init.ora file would be in the following location:

   F:\oracle\as904\admin\database_name\pfile\init.ora
   
   

   In the preceding example, replace database_name with the database system identifier (SID).

   You must restart the database after making this change to the init.ora file.

Step 5 From Node 2, Upgrade the Infrastructure to 10g Release 2 (10.1.2)

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

2. Make sure the Oracle Internet Directory server is up and running.

   To verify that Oracle Internet Directory is running, enter one of the following commands.

   
   

   Note: You may have to temporarily set the ORACLE_HOME environment variable to the Oracle Internet Directory Oracle home before running the ldapbind command. After you verify that the Oracle Internet Directory is running, you must then make sure the ORACLE_HOME environment variable is not defined before you start the 10g Release 2 (10.1.2) installer, as directed later in this procedure.

   
   

   If you are running Oracle Internet Directory on a non-secure port:

   SOURCE_ORACLE_HOME\bin\ldapbind -p Non-SSL_port -h oid_host_name
   
   

   If you are running Oracle Internet Directory on a secure port:

   SOURCE_ORACLE_HOME\bin\ldapbind -p SSL_port -h oid_host_name -U 1
   
   

   These commands should return a "bind successful" message.

   
   

   See Also: "Syntax for LDIF and Command-Line Tools" in the Oracle Internet Directory Administrator's Guide for more information about the ldapbind utility

   
   
   
   

   Note: Oracle Internet Directory 10g (9.0.4) allows you to start and stop the directory service using OPMN or the oidctl utility. Before upgrading an OracleAS Identity Management Oracle home that contains Oracle Internet Directory, start the Oracle Internet Directory instance using the opmnctl utility or the Application Server Control Console. Do not use the oidctl utility; otherwise, Oracle Universal Installer will not be able to start and stop Oracle Internet Directory automatically during the upgrade process. The correct use of opmnctl and oidctl is described in the Chapter "Oracle Internet Directory Process Control–Best Practices" in the Oracle Internet Directory Administrator's Guide.

   
   

3. 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 the following environment variables are not set:

   • TNS_ADMIN

   • ORACLE_HOME

   • ORACLE_SID

4. If the ORACLE_HOME environment variable was previously set, restart the host computer after unsetting the variable.

   The system restart is necessary to clear the ORACLE_HOME variable from the system registry. If you do not restart the computer after clearing the ORACLE_HOME variable, the installation might report an error and prevent you from finishing the installation.

5. 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

   
   

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

   
   

   Note: Be sure to select and enter the same instance name, password, and other selected options you used in the previous upgrade that you performed from Node 1.

   
   

7. 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 6 Restart Node 2

After you have upgraded the Infrastructure and exited Oracle Universal Installer, perform the following procedure:

1. Restart Node 2.

2. From Cluster Administrator, move the application server group, including the shared disk, to Node 2.

9.2.8 Using MRUA to Upgrade the OracleAS Metadata Repository from Node 2

Log in to Node 2 and use the procedure in Section 6.4, "Using the Metadata Repository Upgrade Assistant (MRUA)" to upgrade the component schemas in the OracleAS Metadata Repository.

9.2.9 Creating a pfile for the Database

A pfile is a text file that contains the database initialization parameters. Oracle Fail Safe requires a "pfile" for your database. You enter the full path to the pfile in the Parameter File field when you add the database to the group.

To create a pfile:

1. Create a file called init<SID>.ora in the ORACLE_HOME\database directory.

2. Populate the file with the following lines:

   spfile=ORACLE_HOME\database\spfileSID.ora
   remote_login_passwordfile=EXCLUSIVE
   local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=Virtual_IP)(PORT=1521))"
   
   

   In this example:

   • Replace ORACLE_HOME with the full path of your Oracle home directory.

   • Replace SID with the SID of your database.

   • Replace Virtual_IP with the virtual IP for the virtual hostname.

9.2.10 Performing Required Post-Upgrade Procedures for the OracleAS Cold Failover Cluster

This section lists the post-upgrade procedures you must perform in order to finish upgrading a OracleAS Cold Failover Cluster on a Windows system.

1. From Node 2, use the Services control panel to set all the 10g (9.0.4) Infastructure services to Manual startup mode.

   These services will be removed later, when you decommission and deinstall the 10g (9.0.4) source Oracle homes.

2. Make sure the "Oracle Services for MSCS" is online.

3. Perform the following procedures, which are documented in the Oracle Application Server Installation Guide.

   In particular, refer to the following sections of that guide:

   • Section 12.11.1, "Edit the ORACLE_HOME\Apache\htdocs\index.html File"

   • Section 11.12.2, "Make OracleAS Metadata Repository Highly Available"

   • Section 11.12.3, "Add the Shared Disk as a Dependency for the Listener"

   • Section 11.12.4, "Add the Shared Disk as a Dependency for OPMN"

   • Section 11.12.5, "Make OPMN Highly Available"

   • Section 11.12.6, "Make Application Server Control Highly Available"

   • Section 11.12.7, "Check that the Correct Listener Is Active"

4. From Node 2, use the Services control panel to set all the upgraded Infastructure services to automatic startup mode.

   Use Table 9-3 to identify the name of each resource, since the resource name is the same as the resource name used in the Services control panel.

5. Use the procedure described in Section 7.1.7, "Configuring Oracle Enterprise Manager 10g Database Control" to configure the Oracle Enterprise Manager 10g Database Control.

9.2.11 Performing Typical OracleAS Identity Management Post-Upgrade Tasks

Besides the post-upgrade tasks specific to configuring an upgraded OracleAS Cold Failover Cluster environment, you must also perform the typical post-upgrade tasks required when upgrading any OracleAS Identity Management environment.

For more information, refer to the following:

• Section 5.6, "Task 5: Complete the OracleAS Identity Management Upgrade"

• Section 5.7, "Task 6: Validate the Identity Management Upgrade"

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

9.3.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.3.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.3.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-5.

9.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.6, "Upgrading the First OracleAS Identity Management Instance".

2. Create the Distributed Configuration Management cluster, as described in step 8 of Section 9.3.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.3.8, "Installing Subsequent OracleAS Cluster (Identity Management) Instances".

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