8 Upgrading High Availability Configurations

This chapter describes considerations, restrictions, and recommended procedures for upgrading an Oracle Application Server environment that has been configured for high availability.

This chapter contains the following sections:

• Summary of High Availability Upgrade Options, Restrictions, and Prerequisites

• Upgrading an OracleAS Cold Failover Cluster Infrastructure

8.1 Summary of High Availability Upgrade Options, Restrictions, and Prerequisites

Oracle Application Server 10g (9.0.4) introduced high availability configurations that you could install as part of the Oracle Application Server installation procedure.

If you installed and configured the Oracle Application Server Cold Failover Cluster configuration during the 10g (9.0.4) installation procedure, you can upgrade the OracleAS Cold Failover Cluster configuration using the 10g (10.1.2) installation procedure and Oracle Universal Installer.

However, the upgrade of any other high availability options is not supported directly by the 10g (10.1.2) installation procedure.

See Also: Oracle Application Server High Availability Guide for more information about the Oracle Application Server High Availability Solutions available for 10g (10.1.2)

The procedures provided in this chapter assume that you used the Oracle Application Server 10g (9.0.4) installation guide to install and configure your OracleAS Cold Failover Cluster configuration and that you have met all of the prerequisites described in the 10g (9.0.4) installation guide.

This also assumes you are using the seed database that was installed automatically with the 10g (9.0.4) installation procedure.

For example, these procedures assume you have already installed and configured clusterware such as Sun Cluster, VERITAS Cluster Server, or Fujitsu-Siemens PrimeCluster. For the official list of certified clusterware, visit the Certify section of OracleMetaLink:

http://metalink.oracle.com

To check that the clusterware is running, use the command appropriate for your clusterware. For example, if you are running Sun Cluster, use the scstat command to get the status of the nodes in the cluster.

See Also: The Oracle Application Server 10g (9.0.4) installation guide for your platform, which is available as part of the platform-specific documentation library on the Oracle Technology Network: http://www.oracle.com/technology/documentation/appserver10g.html

8.2 Upgrading an OracleAS Cold Failover Cluster Infrastructure

To upgrade a 10g (9.0.4) OracleAS Cold Failover Cluster Infrastructure installation:

1. If vendor clusterware agents or packages are being utilized to automatically monitor and manage the OracleAS Cold Failover Cluster environment, these should be stopped before you perform the 10g (10.1.2) upgrade.

   In addition, to re-enable vendor cluster agents or packages after the upgrade has been completed, verify that certification has been provided by the appropriate vendor for the 10g (10.1.2) OracleAS Cold Failover Cluster environment.

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

3. Log in to the computer on which the 10g (9.0.4) OracleAS Cold Failover Cluster 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.

   
   

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 (10.1.2) installer, as directed in Step 5.

   
   

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

   SOURCE_ORACLE_HOME/bin/ldapbind -p Non-SSL_port
   
   

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

   SOURCE_ORACLE_HOME/bin/ldapbind -p SSL_port -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. Be sure to set the 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

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

   • TNS_ADMIN

   • ORACLE_HOME

   • ORACLE_SID

6. Mount the Oracle Application Server 10g (10.1.2) CD–ROM and start the installer.

   
   

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

   
   

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

8. 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 (10.1.2) Oracle home.

   
   

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

   
   

9. Review Section 5.10, "Completing the OracleAS Identity Management Upgrade" and perform any post-upgrade tasks that are required for your configuration.

10. The following step is required only if you meet both of these requirements:

    • You plan to use the Automatic Storage Management (ASM) feature of Oracle Database 10g for the OracleAS Metadata Repository.

    • Your computer does not have an existing Oracle Database 10g.

    If you meet these requirements, you need to configure the CSS daemon on the other node. The CSS daemon synchronizes ASM instances with the database instances that use the ASM instances for database file storage.

    To configure the CSS daemon:

    1. Stop all the processes in the Oracle Application Server Cold Failover Cluster (Infrastructure) home.

    2. Stop the CSS daemon. You can do this by running the following command as root.

       # /etc/init.d/init.cssd stop
       
       

    3. Fail over the IP and the disk to the other node.

    4. On the other node, run the following command as root:

       # $ORACLE_HOME/root.sh
       
       

       ORACLE_HOME is where you installed the Oracle Application Server Cold Failover Cluster (Infrastructure).

11. After you upgrade OracleAS Identity Management in a colocated Infrastructure, refer to the following sections for information about post-upgrade tasks you should consider performing to help you manage and maintain the upgraded database:

    • Section 6.1.4, "Relocating the Database Datafiles, Control Files, and Log Files"

    • Section 6.1.5, "Configuring Oracle Enterprise Manager 10g Database Control"

12. If you have installed or upgraded any 10g (10.1.2) middle tiers that use the OracleAS Metadata Repository for components such as OracleAS Portal, OracleAS Wireless, or Oracle Application Server Certificate Authority, then run the Metadata Repository Upgrade Assistant (MRUA) to upgrade the component schemas in the OracleAS Metadata Repository.

    Complete instructions for running MRUA, including prerequisites and post-upgrade tasks, are included in Chapter 6, "Upgrading the OracleAS Metadata Repository".

13. Complete the 10g (10.1.2) Oracle Application Server Cold Failover Cluster Post-Installation instructions described in "Post-Installation Steps for OracleAS Cold Failover Cluster" in the Oracle Application Server Installation Guide.

Table 8-1 Summary of the Oracle Universal Installer Screens During the OracleAS Cold Failover Cluster Infrastructure Upgrade

Screen	Description and Recommended Options to Select
Welcome	Welcomes you to Oracle Universal Installer and the Oracle Application Server 10g (10.1.2) installation procedure.
Specify File Locations	Enter a name and path for the new Oracle home. This new Oracle home will be the destination Oracle home for your Oracle Application Server 10g (10.1.2) upgrade. Notes: You must enter a directory in the file system that can be mounted from either node in the OracleAS Cold Failover Cluster configuration. You must enter a new Oracle home name and directory. Do not select an existing Oracle home from the drop down list. If you select an existing Oracle home, the installer will not display the next screen, Specify Hardware Cluster Installation Mode. Example: /mnt/app/oracle/OraInfra_10_1_2
Specify Hardware Cluster Installation Mode	This screen appears only if you have Oracle Cluster Ready Services installed. It is okay if you do not see this screen; Oracle Cluster Ready Services is not required for OracleAS Cold Failover Cluster. Select Local Installation because you are installing OracleAS Infrastructure on the shared storage. Click Next.
Select a Product to Install	Select OracleAS Infrastructure 10g. If multiple languages are used in the OracleAS Infrastructure you are upgrading, then click Product Languages.
Language Selection	The screen appears only if you clicked Product Languages on the Select a Product to Install screen. If multiple languages are used in the OracleAS Infrastructure you are upgrading, select those languages. If you are not sure which languages were installed, but want languages other than English, click the double arrow button (>>) to select all languages.
Select Installation Type	Select Identity Management and OracleAS Metadata Repository. Note: It is very important that you select the same installation type that is used in the Oracle home you are upgrading.
Upgrade Existing Infrastructure	This screen appears when Oracle Universal Installer detects an existing Oracle Application Server installation of the same type as the one you selected on the Select Installation Type screen. Select the option to upgrade an existing OracleAS Infrastructure, and then select the Oracle home you want to upgrade from the drop-down list. (If there is only one Infrastructure of the selected time on the computer, then the drop-down list is inactive.)
Specify Login for Oracle Internet Directory	Enter the Oracle Internet Directory superuser distinguished name (DN) in the Username field. The superuser DN cn=orcladmin is the default for this field; change this value if the Oracle Internet Directory superuser DN is not cn=orcladmin. Enter the password for the superuser DN in the Password field.
Specify Infrastructure Database Connection	Enter SYS in the Username field and the SYS user's password in the Password field.
Warning dialog box	This dialog box warns you that all the clients of the OracleAS Metadata Repository database must now be stopped. Oracle Universal Installer will automatically stop any clients within the current Oracle home.Foot 1  However, you must manually stop any database clients and OracleAS Metadata Repository clients that reside in another Oracle home. Clients of the OracleAS Metadata Repository include: OracleAS Identity Management components that use this OracleAS Metadata Repository. Middle tier instances that use this OracleAS Metadata Repository Within each middle tier that uses this OracleAS Metadata Repository, you must be sure to stop all components, including Oracle HTTP Server and OracleAS Web Cache. For more information, see the chapter "Starting and Stopping " in the Oracle Application Server Administrator's Guide.
Database Listener Warning Dialog Box	If a database listener is running on the host, a warning dialog box displays. Review the dialog box determine whether or not you need to stop the listener manually. For more information, see Section 5.3.3, "Stopping the Database Listener When Prompted During the OracleAS Identity Management Upgrade".
Specify Instance Name and ias_admin Password	Enter a name for the new Oracle Application Server 10g (10.1.2) instance and a password for the ias_admin Administrator account. You use the ias_admin password to log on to the Application Server Control Console to manage the Oracle Application Server instance. In general, the minimum length of the ias_admin password is five alphanumeric characters. At least one of the characters must be a number and the password cannot start with a number. For more information, see the section "The ias_admin User and Restrictions on its Password" in the Oracle Application Server Installation Guide.
Summary	Use this screen to confirm the choices you've made. Click Install to begin upgrading to the new 10g (10.1.2) Oracle home. A dialog box appears when the copying is complete. This dialog box prompts you to run a configuration script as the root user. Follow the instructions in the dialog box and click OK when script is finished.
The Configuration Assistants	After the initial software is installed, a set of configuration assistants automatically set up the components in the new 10g (10.1.2) Oracle home. Use this screen to follow the progress of each assistant and to identify any problems during this phase of the installation. Notes: The Database Upgrade Assistant (DBUA) can take a significant amount of time to upgrade the database. For more information how long it takes to upgrade your database, see Section 3.3, "Planning for System Downtime". While Database Upgrade Assistant is running, do not use the Stop button to interrupt the execution of Database Upgrade Assistant. If you press Stop, the underlying processes for Database Upgrade Assistant will continue to run. Also, Oracle Universal Installer will wait until those processes complete before returning control to the user.
End of Installation	When the installation and upgrade is complete, this screen provides important details about the 10g (10.1.2) Oracle home, such as the URL for the Application Server Control Console and the location of the setupinfo.txt file. After you review the information on this screen, you can exit Oracle Universal Installer and proceed to the post-upgrade tasks.

^Footnote 1 You can access a log of the automated shutdown procedure executed by Oracle Universal Installer in the following directory: ORACLE_HOME/cfgtoollogs/shutdownprocesses.log