E Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle Web Tier.

It contains the following sections:

E.1 General Troubleshooting Tips

If you encounter an error during installation:

  • Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network (http://www.oracle.com/technology/documentation).

  • Verify that your computer meets the requirements specified in Section 2.1.

  • 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 occurred 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 Chapter 5.

    3. Correct the issue that caused the error.

    4. Restart the installation.

E.2 Troubleshooting Oracle Fusion Middleware Installation

This section contains solutions to common problems that you might encounter when installing Oracle Fusion Middleware. The following topics are covered:

E.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log directory on UNIX, and Oracle_Inventory_Location\logs directory on Windows. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the Web_Tier_ORACLE_HOME/oraInst.loc file. On Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

  • installdate-time-stamp.log

    This is the main log file.

  • installdate-time-stamp.out

    This log file contains the output and error streams during the installation.

  • installActionsdate-time-stamp.log

    This file is used by the installer GUI to keep track of internal information.

  • installProfiledate-time-stamp.log

    This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.

  • oraInstalldate-time-stamp.log

    This log file contains the output stream of the copy session.

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log and timedate-time-stamp.log files are created in the same directory:

  • timeTakendate-time-stamp.log

    This file contains information for the amount of time taken to move between screens (applicable for GUI installations only).

  • timedate-time-stamp.log

    This file contains time information for the copy session.

If you start the installer with the -printmemory parameter, the memorydate-time-stamp.log file is created. This file contains memory usage information for the copy session.

E.2.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:


% ./config.sh -log=log_filename

On Windows

G:\ config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the Web_Tier_ORACLE_HOME/common/bin directory on UNIX, and Web_Tier_ORACLE_HOME\common\bin on Windows.

E.3 Configuring Java Required Files (JRF)

Java Required Files (JRF) bits are included with an Oracle Web Tier installation because they are required by some Oracle Web Tier components. These bits should not be used to configure JRF in a WebLogic domain.

To configure JRF in a WebLogic domain, you should the JRF included with some other Oracle Fusion Middleware products, such as Oracle SOA Suite, WebCenter, or Application Developer. Configuring JRF from the Web Tier Oracle home directory is not supported.

E.4 Need More Help?

If this appendix does not solve the problem you encountered, try these other sources:

If you do not find a solution for your problem, open a service request.