F.1.2 Read the Release Notes

Oracle recommends reading the Oracle Developer Suite 10g (10.1.2.0.2) Release Notes for Windows and UNIX prior to installing. These document contain product-level and component-level release notes for Windows, Linux and Solaris platforms. This manual is available in the Oracle Developer Suite Documentation Library. To display the manual, see Section C.3.1, "Viewing the Release Notes from Disk". The manual is also available on Oracle Technology Network (http://www.oracle.com/technology/).

Your platform-specific documentation may include release notes for your platform. Platform-specific release notes are also available on Oracle Technology Network (http://www.oracle.com/technology/).

F.2Troubleshooting the Installation

If you encounter an error while installing Oracle Developer Suite, follow these steps:

Do not exit the installer. You can find the installation log files more easily if you leave the installer running.

Incorrect Information: If you think you have entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen, correct the information, then proceed with your installation.

Copy or Link Errors: If the installer reports an error while copying or linking files, do the following:

Note the error, then review the installation logs for causes. The installation logs are in your Oracle inventory directory in the subdirectory \logs (for Windows) or /logs (for Linux and Solaris) and have the following file names:

For Windows:

oracle_inventory\logs\installActionstimestamp.log

oracle_inventory\logs\oraInstalltimestamp.err

oracle_inventory\logs\oraInstalltimestamp.out

For Linux and Solaris:

oracle_inventory/logs/installActionstimestamp.log

oracle_inventory/logs/oraInstalltimestamp.err

oracle_inventory/logs/oraInstalltimestamp.out

The string timestamp is a value that the installer adds to the file name at the start of the installation. The form of timestamp is yyyy-mm-dd_hh-mm-ss[AM|PM] where:

yyyy is the current year, for example 2003

mm is the current month number, for example 07 for July

dd is the current day number, for example 15 for the fifteenth

hh, mm, and ss are the hour, minute, and second at which the installation started

[AM/PM] is either AM or PM, depending on when the installation started

The location of the oracle_inventory directory is specified during the first installation of an Oracle product on your computer. To learn more about the directory and how to find it, refer to Section 2.8, "Directories Used by the Installer".

F.3 Troubleshooting Oracle Developer Suite Configuration Assistants

Review the configuration assistant log files located in the DevSuiteHome/cfgtoollogs directory for a specific Oracle Developer Suite configuration assistant. Table F-2 also lists any other log file locations for a specific configuration assistant. Try to fix the issue that caused the error.

F.3.1 Determining Configuration Assistant Execution Status

Oracle Developer Suite configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information, if applicable. The configuration assistant's execution status will be identified by the result. The result codes are listed in Table F-1:

Table F-1 Configuration Assistant Result Codes

Status

Result Code

Configuration Assistant Succeeded

0

Configuration Assistant Failed

1

Configuration Assistant Cancelled

-1

This result code is written to the following log file: oraInventory/logs/installActionstimestamp.log

F.3.2 Fixing Configuration Assistant Failures

During installation, configuration assistants run when the Configuration Assistants screen appears. If a configuration assistant fails, try the following procedure to correct the problem:

Review the installation log files for this installation session.

Review the log files for each configuration assistant located in the DevSuiteHome/cfgtoollogs directory. Default log file locations are described in Table F-2.

Refer to the section describing the configuration assistants in Table F-2:

If the failing configuration assistant has any dependencies, then run the dependencies again. You must do this even if the dependency completed successfully.

If an optional configuration assistant fails, and it does not have any dependencies, run the remaining configuration assistants. Uncheck the cancelled optional configuration assistant, highlight and check the next listed configuration assistant, and click Retry.

Run the failing configuration assistant again. If you are using the installer, select the configuration assistant and click Retry.

Note:

If the description of a configuration assistant in Table F-2 includes an "Initial Tasks" section, you must perform these tasks before running the configuration assistant.

F.3.3 Handling Fatal Errors

Some configuration assistant failures are fatal errors. You cannot recover from a fatal error by correcting the problem and continuing. You must remove the current installation and reinstall Oracle Developer Suite. The following tasks describe the recovery procedure: