Oracle® Application Server

Installing the Oracle Application Server 10g Release 2 (10.1.2.0.2) Middle Tier

The first step in upgrading a middle tier is to install a new Oracle Application Server 10g Release 2 (10.1.2.0.2) middle tier. This new Oracle home is referred to as the destination Oracle home. Your original 10g (9.0.4) installation is referred to as the source Oracle home.

When you install the 10g Release 2 (10.1.2.0.2) destination Oracle home, use the following checklist to be sure that you install the new Oracle Application Server:

• On the same computer as the Oracle Application Server 10g (9.0.4) middle tier

• Using the same operating system user that installed the 10g (9.0.4) middle tier

• In a separate Oracle home from the 10g (9.0.4) middle tier.

• Using an installation type that is compatible with 10g (9.0.4) middle tier.

  Table 3 shows the compatible 10g Release 2 (10.1.2.0.2) install types you can select for each of the 10g (9.0.4) install types.

• So that it uses the same OracleAS Metadata Repository and OracleAS Identity Management as the 10g (9.0.4) middle tier.

Performing the Middle Tier Upgrade

This section provides step-by step instructions for using the OracleAS Upgrade Assistant to perform a middle-tier upgrade:

1. Log in to the user account that was used to install the source Oracle home.

2. Start the OracleAS Upgrade Assistant with the command:

   DESTINATION_ORACLE_HOME\upgrade\iasua.bat
   
   

   The Welcome screen appears.

3. Review the introductory information and then click Next.

   The Oracle Homes screen appears. The Source Oracle Home drop-down menu contains the names of 10g (9.0.4) Oracle homes that are found in the inventory of Oracle products on the current computer and that were installed using an installation type that is compatible with the installation type of the destination Oracle home.

   The destination Oracle home is the 10g Release 2 (10.1.2.0.2) Oracle home in which the OracleAS Upgrade Assistant is running.

4. Select the source Oracle home that you want to upgrade from the drop-down list; then, click Next.

   The OracleAS Upgrade Assistant performs many of the required pre-upgrade tasks automatically before it begins the upgrade process.

   If you are upgrading a middle-tier instance that requires an OracleAS Infrastructure component, a dialog box prompts you to be sure that the required Infrastructure components are up and running.

5. Ensure that all requirements are fulfilled, and click Yes.

   The Examining Components dialog box appears. The OracleAS Upgrade Assistant examines each component in the source Oracle home to determine whether it needs to be upgraded. For each component, the dialog box indicate the status of the examination.

   • If one or more components fails the pre-upgrade examination, the OracleAS Upgrade Assistant displays an Examination Failure Warning dialog box, which identifies the component that failed. Click Help for more information about what to do next.

   • If all component examinations succeed, the Summary screen appears.

   
   

   Note: The Summary screen is the last screen before upgrade processing begins. Before you click Finish, verify that the choices on previous screens are correct and the upgrade items listed are ready to upgrade.

   
   

6. Scroll to view the components on the Summary screen; click the plus symbol (+) to expand a component's upgrade items. Review the components; then, click Finish.

   The Upgrading screen appears. For each component, the OracleAS Upgrade Assistant shows the status of the upgrade process.

   • If the upgrade completes successfully, then the Upgrade Succeeded screen appears. Click OK and continue to the next step in the procedure.

   • If the upgrade fails, the Upgrade Failed screen appears. See "Troubleshooting the Middle Tier Upgrade".

7. Start the destination middle tier by starting the Application Server Control and Oracle Process Manager and Notification Server (OPMN) services for the middle tier, as shown in Table 2.

8. Verify that the middle tier has been upgraded successfully:

   1. Using your Web browser, navigate to the Application Server Control Console.

      The URL for the Application Server Control uses the following format:

      http://hostname.domain:port/
      
      

      For example:

      http://host1.acme.com:18100/
      
      

      Note that after the middle-tier upgrade, you can use the 10g (9.0.4) Application Server Control Console port to access the upgraded 10g Release 2 (10.1.2.0.2) Application Server Control Console.

   2. If the middle tier is part of an OracleAS Farm, on the Farm page, click the name of the middle tier that you just upgraded.

   3. On the Application Server Home page, verify that the components of the middle tier instance are up and running.

   4. Verify the version of the middle tier instance in the General section of the Application Server Home page.

9. Depending up on which Oracle Application Server components you are using, there may be additional post-upgrade tasks you should consider.

   Review the component-specific instructions that apply to your environment in the section "Task 5: Complete the Middle Tier Upgrade" in the Oracle Application Server Upgrade and Compatibility Guide.

   In particular, refer to Table 4 for a list of tasks you should consider after you have upgraded a middle tier Oracle home.

   Table 4 Common Middle-Tier Post-UpgradeTasks

   Task	More Information
   Verify that the ports defined in the destination Oracle home match those defined in the source Oracle home.	"About Port Values and the portlist.ini File" in the Oracle Application Server Upgrade and Compatibility Guide
   Verify the values of the ias_admin password and OracleAS Web Cache Manager passwords in the destination Oracle home.	"About Administration Passwords After Upgrade" in the Oracle Application Server Upgrade and Compatibility Guide
   If you enabled SSL in the source Oracle home, verify that SSL is configured correctly in the destination Oracle home.	"Verifying the Secure Sockets Layer (SSL) Configuration After Upgrade" in the Oracle Application Server Upgrade and Compatibility Guide

   
   

Troubleshooting the Middle Tier Upgrade

If the upgrade fails while examining or upgrading your Oracle Application Server components, use the following procedure to troubleshoot the problem:

1. Review the list of common middle-tier troubleshooting items in Table 5.

2. Review the list of "General and Middle Tier Upgrade Problems and Solutions" in the Oracle Application Server Upgrade and Compatibility Guide.

3. Note the name of the component or components that OracleAS Upgrade Assistant was unable to examine or upgrade successfully.

4. Locate and open the OracleAS Upgrade Assistant log file using a text editor:

   DESTINATION_ORACLE_HOME\upgrade\log\iasua.log
   
   

5. Refer to "Upgrade and Compatibility Error Messages" in the Oracle Application Server Upgrade and Compatibility Guide for information about component-specific error messages in the log files.

6. If you are able to resolve the problem, start the OracleAS Upgrade Assistant again.

ORACLE_HOME/opmn/bin/opmcntl stopall

Performing the OracleAS Identity Management Upgrade

To upgrade OracleAS Identity Management in a colocated Infrastructure 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 the 10g (9.0.4) OracleAS Infrastructure instance is installed as the same operating system user that performed the 10g (9.0.4) installation.

   
   

   Note: The account you use 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.

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

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

   SOURCE_ORACLE_HOME\bin\ldapbind -p SSL_port -h -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 to set following variables so they do not reference any Oracle home directories:

   • PATH

   • CLASSPATH

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

   • TNS_ADMIN

   • ORACLE_HOME

   • ORACLE_SID

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

   
   

7. Refer to Table 6 for information on the options you should select on each screen.

8. After the End of Installation screen appears, exit Oracle Universal Installer.

9. Verify that Oracle Internet Directory and OracleAS Single Sign-On are functioning and accessible in the new 10g Release 2 (10.1.2.0.2) Oracle home:

   1. Use your Web browser to navigate to the admistrative Home page for the OracleAS Single Sign-On server and verify that the server is running:

      http://host:port/pls/orasso
      
      

      In this example, host is the computer where theOracleAS Single Sign-On server is located, port is the port number of the server, and orasso is the database access descriptor for the single sign-on schema.

      
      

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

      
      

   2. Navigate to the Application Server Control Console URL for the OracleAS Infrastructure Oracle home:

      http://hostname.domain:port/
      
      

      For example:

      http://host1.acme.com:18100/
      
      

      Note that unlike the middle-tier upgrade, after you upgrade the OracleAS Infrastructure, you must use the 10g Release 2 (10.1.2.0.2) Application Server Control Console port to access the Application Server Control Console. That port can be found in the following file located in the 10g Release 2 (10.1.2.0.2) destination Oracle home:

      DESTINATION_ORACLE_HOME\install\setupinfo.txt
      
      

   3. On the Farm page, click the name of the OracleAS Infrastructure instance that you just upgraded.

   4. On the Application Server Home page, verify that the components of the OracleAS Infrastructure are up and running.

      In particular, verify that the OID and Single Sign-On components in the System Components table are up and running.

   5. Verify the version of the instance in the General section of the Application Server Home page.

10. Depending up on which OracleAS Infrastructure components you are using, there may be additional post-upgrade tasks you should consider.

    Review the component-specific instructions that apply to your environment in the section "Completing the OracleAS Infrastructure Upgrade" in the Oracle Application Server Upgrade and Compatibility Guide.

Troubleshooting the OracleAS Identity Management Upgrade

If you encounter an error during the OracleAS Identity Management upgrade, consider the following troubleshooting steps:

• Refer to the "OracleAS Identity Management Upgrade Problems and Solutions" in the Oracle Application Server Upgrade and Compatibility Guide for common troubleshooting tips.

• If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

• If an error occurrs while the installer is copying or linking files:

  1. Note the error and review the installation log files.

  2. Remove the failed installation by following the steps in Appendix E, "Deinstallation and Reinstallation" of the Oracle Application Server Installation Guide.

  3. Correct the issue that caused the error.

  4. Restart the upgrade procedure.

• If a configuration assistant fails, check the log file for that configuration assistant. For a list of the configuration assistants and the location of their log files, see the section "Description of Oracle Application Server Configuration Assistants" in the Oracle Application Server Installation Guide. If you do not see log files from some configuration assistants in the following directory, then exit the installer:

  DESTINATION_ORACLE_HOME/cfgtoollogs
  
  

  When you exit the installer, Oracle Universal Installer copies the log files to cfgtoollogs directory.

• For all other issues, refer to Oracle Universal Installer log files:

  oraInventory_location\logs\installActionstimestamp.log
  oraInventory_location\logs\oraInstalltimestamp.err
  oraInventory_location\logs\oraInstalltimestamp.out
  DESTINATION_ORACLE_HOME/install/make.log
  
  

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

  \\HKEY_LOCAL_MACHINE\\Software\Oracle\
  

Configuring Oracle Enterprise Manager 10g Database Control

The Oracle Enterprise Manager 10g Database Control provides a Web-based console you can use to manage Oracle Database 10g. When your OracleAS Metadata Repository is installed in an Oracle Database 10g instance, you can use the Database Control to manage your OracleAS Metadata Repository database.

However, after you use Oracle Universal Installer to upgrade your OracleAS Metadata Repository database to Oracle Database 10g, the Database Control is not configured automatically. Instead, if you want to use the Database Control to manage your upgraded OracleAS Metadata Repository database, you must configure the Database Control manually using the Enterprise Manager Configuration Assistant (EMCA).

Stopping All Middle Tier Instances That Use the OracleAS Metadata Repository

Before you use MRUA, you must stop all processes associated with each middle tier that uses the OracleAS Metadata Repository.

Note that at this point in the upgrade process, as a prerequisite for running MRUA, all the middle tier instances should have been upgraded to 10g Release 2 (10.1.2.0.2).

To stop all the Oracle Application Server instances that use the OracleAS Metadata Repository:

1. Display the Farm page in the Application Server Control Console; the Farm page lists all the Oracle Application Server instances that are currently using the services of the OracleAS Infrastructure.

   
   

   See Also: "Introduction to Administration Tools" in the Oracle Application Server Administrator's Guide for more information about the Application Server Control Console Farm page

   
   

2. Click the name of each instance listed on the Farm page, and click Stop All on the Application Server Control Console Home page for each instance.

Verifying That the Oracle Internet Directory and Database Processes Are Running

Before you use MRUA, you must be sure that the following processes are up and running:

• The database that hosts the OracleAS Metadata Repository

• The database listener for the OracleAS Metadata Repository database

• The Oracle Internet Directory instance where the OracleAS Metadata Repository database is registered

Log in to the Application Server Control Console to verify that the necessary processes are running and that the required components are configured properly. For example, you can use the Application Server Control Console to verify that the Farm page displays correctly; if the Farm page displays correctly, then the Oracle Internet Directory is up and running.

Checking for Invalid Database Objects

Before you run MRUA, use the following procedure to make sure that none of the database objects that are required by Oracle Application Server are invalid:

1. Connect to the OracleAS Metadata Repository database.

   For example:

   1012_INFRASTRUCTURE_ORACLE_HOME\bin\sqlplus "connect / as sysdba"
   
   

2. When prompted, enter the SYS password.

3. Issue the following SQL command:

   SELECT owner, object_type, object_name
      FROM all_objects
      WHERE status='INVALID';
   
   

The query should not return any database objects that have an Oracle Application Server component schema (such as PORTAL, WIRELESS, and so on) in the 'owner' column.

If you find any invalid objects, run the utlrp.sql script from the SQL*Plus command line to recompile the invalid objects:

@?/rdbms/admin/utlrp.sql

Running the Metadata Repository Upgrade Assistant (MRUA)

After you have stopped the middle tiers and verified that the Oracle Internet Directory and database processes are running, you can use MRUA to upgrade the component schemas in the OracleAS Metadata Repository.

To run MRUA:

1. Mount the Metadata Repository Upgrade Assistant and Utilities CD–ROM.

   The MRUA and Utilities CD–ROM is part of the Oracle Application Server CD–ROM Pack that you receive when you order the Oracle Application Server software.

2. Start MRUA by entering the following command, with the following required arguments, which are described in Table 7:

   CD_DRIVE_LETTER:\mrua\mrua.bat
   -oracle_home 1012_infrastructure_oracle_home 
   -oid_host Oracle_Internet_Directory_host
   -oid_ssl_port Oracle_Internet_Directory_SSL_port
   

   Table 7 Summary of the Required MRUA Command Line Arguments

   Argument	Description
   -oracle_home	The destination 10g Release 2 (10.1.2.0.2) OracleAS Metadata Repository home directory.
   -oid_host	The name of the computer that hosts the Oracle Internet Directory where the OracleAS Metadata Repository is registered.
   -oid_ssl_port	The secure port for the Oracle Internet Directory. For the purposes of upgrading the OracleAS Metadata Repository, you must use a secure connection to the Oracle Internet Directory.

   
   
   
   

   Note: The value of 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: 1012_INFRASTRUCTURE_ORACLE_HOME\config\ias.properties 1012_INFRASTRUCTURE_ORACLE_HOME/config/ias.properties For example: OIDhost=sys42.acme.com OIDsslport=636

   
   

3. When you are prompted, enter the password for the database SYS user account.

   MRUA needs the SYS password so it can access and modify the component schemas in the database.

4. When you are prompted, enter the Oracle Internet Directory cn=orcladmin administrator password.

   MRUA needs the Oracle Internet Directory password to connect to the Oracle Internet Directory in which the OracleAS Metadata Repository is registered.

   After you provide the required passwords, MRUA checks to be sure the Oracle Internet Directory is running and does one of the following:

   • If Oracle Internet Directory is down or unavailable, MRUA displays an error message and exits.

   • If Oracle Internet Directory is up and running, MRUA connects to the directory service and obtains additional information required to upgrade the component schemas.

   • MRUA starts the upgrade process. As each step in the upgrade is executed, information messages appear on the screen to show the progress of the upgrade.

     Example 1 shows an example of a typical MRUA upgrade session.

5. Review the output of the MRUA command; if MRUA reports any errors, see Section B.10, "Error Messages Generated By the Metadata Repository Upgrade Assistant".

mrua.bat -oracle_home D:\oracle10g -oid_host dserv1.acme.com -oid_ssl_port 3130

Executing mrua.pl
Running on Windows

OracleAS Metadata Repository Upgrade Assistant 10.1.2.0.2

Enter the password for SYS:
Enter the password for cn=orcladmin:

Upgrading the OracleAS Metadata Repository to release 10.1.2.0.2

Calling upgrade plugin for MRUA
Component  upgraded successfully MRUA

Calling upgrade plugin for UDDI
Component  upgraded successfully UDDI

Calling upgrade plugin for WCS
Component  upgraded successfully WCS

Calling upgrade plugin for ULTRASEARCH
Component  upgraded successfully ULTRASEARCH

Calling upgrade plugin for WIRELESS
Component  upgraded successfully WIRELESS

Calling upgrade plugin for WORKFLOW
Component  upgraded successfully WORKFLOW

Calling upgrade plugin for PORTAL
Component  upgraded successfully PORTAL

Calling upgrade plugin for DISCOVERER
Component  upgraded successfully DISCOVERER

Calling upgrade plugin for B2B
Component  upgraded successfully B2B

Calling upgrade plugin for MRC
Component  upgraded successfully MRC

Calling upgrade plugin for ORABPEL
Component  upgraded successfully ORABPEL

Calling upgrade plugin for BAM
Component  upgraded successfully BAM

SUCCESS: All OracleAS plug-ins report successful upgrade

Finished mrua.pl

Example Execution Times for the Metadata Repository Upgrade Assistant

The time required to run MRUA will vary, depending upon your hardware and the amount of data in your OracleAS Metadata Repository. However, testing of MRUA has shown the following typical execution times on the following hardware and software platforms:

• 1 hour, 40 minutes on a Sun UltraSPARC 60, dual CPU, running Solaris 2.9

• 45 minutes on a 2.4GHz Pentium 4, running Windows 2000 Service Pack 4

Using a SQL Query to Verify the Success of the OracleAS Metadata Repository Upgrade

Besides the MRUA log files, you can optionally query the database to verify the success of the OracleAS Metadata Repository upgrade. Specifically, you can use a SQL command to view the status of each component schema that MRUA upgrades.

To see the current status of each component schema in the repository that is upgraded by MRUA:

1. Connect to the OracleAS Metadata Repository database.

   For example:

   1012_INFRASTRUCTURE_ORACLE_HOME\bin\sqlplus "connect / as sysdba"
   
   

2. When prompted, enter the SYS password.

3. Enter the following SQL command to verify the status of the component schemas:

   SELECT comp_id,version,status FROM APP_REGISTRY;
   
   

   Example 2 shows an example of the output displayed from the component schema SQL query.

   Example 2 Sample Output of the Component Schema SQL Query

   prompt> SELECT comp_id,version,status FROM APP_REGISTRY;
   
   COMP_ID                        VERSION                        STATUS
   ------------------------------ ------------------------------ -----------
   WORKFLOW                       10.1.2.0.2                     VALID
   SYNDICATION                    10.1.2.0.2                     VALID
   PORTAL                         10.1.2.0.2                     VALID
   SSO                            10.1.2.0.2                     VALID
   B2B                            10.1.2.0.2                     VALID
   MRC                            10.1.2.0.2                     VALID
   OCA                            10.1.2.0.2                     VALID
   OID                            10.1.2.0.2                     VALID
   DCM                            10.1.2.0.2                     VALID
   DISCOVERER                     10.1.2.0.2                     VALID
   WCS                            10.1.2.0.2                     VALID
   UDDI                           10.1.2.0.2                     VALID
   WIRELESS                       10.1.2.0.2                     VALID
   
   13 rows selected.
   

Troubleshooting the OracleAS Metadata Repository Upgrade

Use the following information to troubleshoot any errors that occur while running MRUA:

• Reviewing the MRUA Log Files

• Reviewing the OracleAS Portal Repository Upgrade Log Files

1012_INFRASTRUCTURE_ORACLE_HOME\upgrade\logs

mrua2004-09-16_12-36-36PM.log
mrua2004-09-16_12-36-36PM.err
mrua2004-09-16_12-36-36PM.out

mrua<timestamp>.log

mrua<timestamp>.err

mrua<timestamp>.out

ORACLE_HOME\upgrade\temp\portal

http://metalink.oracle.com/

>>> Running upg/common/popinv.pl
### Upgrade completed successfully
>>> Running tmp/popinv.sql
Portal SQL script started at Thu Apr 22 20:56:23 2004
Connected.
Updating patch inventory.
Upgrade Ended at Thu Apr 22 20:56:24 2004

Removing the 10g (9.0.4) Instances from the OracleAS Farm

If the middle tier instance you have upgraded is a member of an OracleAS Farm, be sure to remove the source instance from the farm before you deinstall the source Oracle home.

For example, after you upgrade an instance that was using an OracleAS Infrastructure, the source instance remains in the list of instances on the Application Server Control Console Farm page.

To remove the source instance from the farm and from the Farm page, use the following command in the source Oracle home:

SOURCE_ORACLE_HOME\dcm\bin\dcmctl leavefarm

Preserving Application Files and Log Files

If there are application files or log files in the source Oracle home that are being referenced or used by the destination Oracle home, you should move them to another location before you decommission the source Oracle home, and, in the destination Oracle home, change any references to the files to the new location.

Relocating the Database Datafiles, Control Files, and Log Files

After you used Oracle Universal Installer to upgrade a OracleAS Metadata Repository seed database, the datafiles for the OracleAS Metadata Repository database remain in the source Oracle home.

As a result, Oracle recommends that you relocate these files as a safeguard against inadvertently deleting them (for example, by deleting or deinstalling the entire source Oracle home directory tree). In addition, there may be performance benefits to moving the database files outside of the source Oracle home.

Deinstalling a 10g (9.0.4) Oracle Home

When you are certain that the upgrade was successful, you have all of the necessary backups, you have moved the database data files, control files, log files to a new location, and you have no plans to revert to the source Oracle home, you may elect to remove the files from the source Oracle home. Use the Oracle Universal Installer to deinstall the instance.