Skip Headers
Oracle® Fusion Middleware Upgrade Planning Guide
11g Release 1 (11.1.1.7.0)

Part Number E10125-09
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

B Troubleshooting Your Upgrade

This chapter contains the following sections, which describe how to resolve problems and issues that occur while you are using the Upgrade Assistant to upgrade to Oracle Fusion Middleware 11g:

B.1 General Troubleshooting Guidelines

If errors occur while you are running the Upgrade Assistant, use the following steps to troubleshoot the problem:

  1. Locate and open the Upgrade Assistant log file with a text editor:

    For the location of the log file, see Section B.3, "Examining the Log File".

  2. Locate any error messages that are identified by number; for example, UPGAST-00091.

  3. Look up the error in the Oracle Fusion Middleware Error Messages Reference.

    The description of the error in the Oracle Fusion Middleware Error Messages Reference should include a description of the cause of the error, as well as the action you should take to resolve the error.

  4. Based on whether or not you can locate an error message and the error message description, do the following:

    • If, by reviewing the log files and the Oracle Fusion Middleware Error Messages Reference, you are able to identify a solution to the upgrade failure, you can implement your solution and then re-start the Upgrade Assistant and perform the upgrade again.

      When you re-run the Upgrade Assistant, any components that were upgraded successfully during the previous run will not be affected. However, the Upgrade Assistant will attempt to upgrade any components that were not upgraded successfully during a previous run of the utility.

    • Contact Oracle Support for any errors that are not documented or that cannot be resolved by following documented actions. Note that some errors that occur will require the repository to be restored from backup, the problem to be resolved, and another upgrade to be run.

B.2 Resolving Common Upgrade Assistant Errors

If errors occur while you are running the Upgrade Assistant, you must correct the conditions that caused them before you try the upgrade again. The following sections provide some guidance in resolving Upgrade Assistant errors:

B.2.1 Source Oracle Home Not Listed by Upgrade Assistant

If the source Oracle home does not appear as expected in the drop-down list on the Oracle Homes, or if you receive an error ("No matching Oracle homes found") when starting the Upgrade Assistant, then consider the following issues and solutions.

Wrong Installation Type The source Oracle home will not appear if the installation type of the source middle tier is not compatible with the installation type of the destination middle tier instance.

Oracle Homes on Different Computers Another case in which the source middle tier will not appear as a selection is that the source middle tier instance is installed on a different computer from the destination middle tier instance. If this is the case, you must install the destination middle tier instance on the same computer as the source instance to be upgraded.

Oracle Home Not in the Oracle Inventory The Upgrade Assistant locates Oracle Application Server Oracle homes on your system by analyzing the contents of the Oracle inventory.

Every time you install an Oracle software product on a host computer, Oracle Universal Installer saves information about the software installation on your hard disk. The directories and files that contain this software configuration information are referred to as the Oracle Universal Installer inventory.In some cases, a particular installation may not appear in the inventory. It could be that the inventory directory was deleted or damaged, or it could be that multiple inventories are installed on the computer. On UNIX systems, you can resolve this issue by referring to Section B.7, "Starting the Upgrade Assistant on UNIX Systems When Using Multiple Oracle Universal Installer Inventory Locations".

Products In the Inventory Installed by Different Operating System Users

The Upgrade Assistant uses the Oracle Universal Installer inventory APIs to get a list of components in an Oracle home. If the user running the Upgrade Assistant does not have read access to an Oracle home, then the OUI API returns an empty list of components.

This can occur if you are running Upgrade Assistant from an operating system user account other than the account used to install the source or destination Oracle home. When running the Upgrade Assistant, be sure to use the same operating system user that was used to install the Oracle Application Server 10g environment.

Alternatively, you can set the permissions of the source and target Oracle homes so your current user account has write access to the directories and their contents while running the Upgrade Assistant.

B.2.2 Error Message States that No Components Can Be Upgraded

This error can appear when you are attempting to upgrade an Oracle Application Server 10g Release 3 (10.1.3.1.0) Basic Installation, which does not include an instance of Oracle HTTP Server. In this situation, there are no components that can be upgraded automatically by the Oracle Fusion Middleware Upgrade Assistant.

B.2.3 Troubleshooting Database Connection Problems When Upgrading Schemas

If you have trouble connecting to a database when using the Upgrade Assistant to upgrade a component schema, try connecting to the database using another tool, such as SQL*Plus. This will help you troubleshoot the problem by verifying that the database is up and running and available on the network.

B.3 Examining the Log File

The Upgrade Assistant generates a set of log files that you can use to troubleshoot, verify, or analyze the upgrade process.

The Upgrade Assistant log file is located in the following directory; its name contains the date and time of the Upgrade Assistant session:

For database schema upgrades of certain components, there can also be an output (.out) file that will contain the screen output of commands that were run in a shell process or as PL/SQL scripts.

You can locate these output files at the following location:

B.4 Investigating Examination Failures

To determine the cause of an examination failure:

  1. Note the name of the failed component in the OracleAS Upgrade Assistant dialog or command-line output.

  2. Open the following Upgrade Assistant log file.

    For the location of the log file, see Section B.3, "Examining the Log File".

  3. In the log file, search for the message Starting to examine component_name.

  4. Refer to the Oracle Fusion Middleware Error Messages Reference for information about specific error messages in the Upgrade log files.

B.5 Investigating Upgrade Failures

To determine the cause of an upgrade failure:

  1. Note the name of the failed component in the OracleAS Upgrade Assistant dialog or command-line output.

  2. Open the Upgrade log file:

    For the location of the log file, see Section B.3, "Examining the Log File".

  3. Search for the message Starting to upgrade component_name.

  4. Refer to the Oracle Fusion Middleware Error Messages Reference for information about specific error messages in the Upgrade log files.

B.6 Restarting the Upgrade Assistant

When you are upgrading a middle tier, you can restart the Upgrade Assistant after it has partially or completely processed an Oracle home. Follow these steps:

  1. Start the Upgrade Assistant in GUI or command-line mode.

    The OracleAS Upgrade Assistant displays a message, which explains whether or not the previous upgrade was successful.

  2. If the previous upgrade was not completed, close the dialog (GUI version) or enter Yes (command-line version) and continue with the upgrade.

B.7 Starting the Upgrade Assistant on UNIX Systems When Using Multiple Oracle Universal Installer Inventory Locations

On UNIX systems, the Oracle Universal Installer creates an inventory location file, /etc/oraInst.loc, when it installs Oracle products. This file contains the location (full path) of the Oracle Universal Installer directory, and the group name of the user who installed it.

The Upgrade Assistant locates valid source Oracle home locations with the information from this directory, the default inventory. Additional inventories files are sometimes created after installation so you can manage Oracle homes independently (thereby circumventing the Oracle Universal Installer features that track all Oracle homes in a single inventory).

If there are multiple inventory location files on the computer on which you are performing an upgrade, and you want to be able to select a non-default inventory location, you must start the Upgrade Assistant with the -invPtrloc argument, specifying the inventory location file(s) for the Oracle homes involved in the upgrade.

For example, if the Oracle Application Server 10g Oracle home and the Oracle Fusion Middleware 11g Oracle home are installed in different inventories, then you must specify both inventories on the Upgrade Assistant command line.

For complete information about the Oracle inventory, see "Oracle Universal Installer Inventory" in the Oracle Universal Installer and OPatch User's Guide.

The syntax for starting the Upgrade Assistant for multiple inventory locations is provided below.

Graphical User Interface (GUI) Version:

ua [[-invPtrLoc inventory_location_file]...]

For example:

ua -invPtrLoc /du03/oracle_inventory1/orainst.loc -invPtrLoc /etc/orainst.loc

Command-line Version:

ua -sourcehome SOURCE_ORACLE_HOME [[-invPtrLoc inventory_location_file]...] [-verbose] [-noprompt]

For example:

ua -sourcehome /du03/oracle/appserver1/ -invPtrLoc /du03/oracle_inventory1/orainst.loc -invptrLoc /etc/orainst.loc -verbose -noprompt