|
Oracle® Developer Suite Installation Guide
10g (9.0.4) for Windows, Linux, Solaris, and HP-UX Part No. B10579-02 |
|
|
|
|
Oracle® Developer Suite Installation Guide
10g (9.0.4) for Windows, Linux, Solaris, and HP-UX Part No. B10579-02 |
|
|
|
|
This appendix lists some methods for troubleshooting your Oracle Developer Suite installation. It includes the following topics:
Oracle recommends that you review the following before you attempt to fix problems in your Oracle Developer Suite installation:
First, review the Oracle Developer Suite hardware and software requirements and pre-installation tasks:
Ensure that your computer meets the hardware requirements specified in Section 2.1, "Hardware Requirements".
Ensure that your software operating environment is supported by Oracle Developer Suite 10g (9.0.4). For a list of supported operating environments, see Section 2.2, "Operating Environments Supported".
Ensure that your supported software operating environment meets the software requirements specified in Section 2.3, "Operating Environment Software Requirements".
Ensure that you have completed all the product-level pre-installation requirements specified at the beginning of Section 2.8, "Preinstallation Tasks".
Ensure that you have completed all the component-level pre-installation requirements for the components you are installing. These are listed in Section 2.8.7, "Completing Component-specific Preinstallation Tasks".
Oracle recommends reading the Oracle Developer Suite release notes prior to installing. Oracle provides these release notes:
Oracle Developer Suite 10g (9.0.4) Release Notes for Windows, Linux, Solaris, and HP-UX contains product-level and component-level release notes for Windows and for Linux, Solaris, and HP-UX 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://otn.oracle.com).
Oracle Developer Suite 10g (9.0.4) Release Notes for Windows, Linux, Solaris, and HP-UX is also updated regularly and posted on the Oracle Technology Network (http://otn.oracle.com).
Your platform-specific documentation may include release notes for your platform. Platform-specific release notes are also available on Oracle Technology Network (http://otn.oracle.com).
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, Solaris, and HP-UX) and have the following filenames:
For Windows:
oracle_inventory\logs\installActionstimestamp.log
oracle_inventory\logs\oraInstalltimestamp.err
oracle_inventory\logs\oraInstalltimestamp.out
For Linux, Solaris, and HP-UX:
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 filename 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.7, "Directories Used by the Installer".
Remove the failed installation by following the instructions in Chapter 4, "Deinstallation and Reinstallation".
Correct the problem that caused the error.
To troubleshoot an installation error that occurs when the configuration assistants are running:
Review the installation log files listed in Section E.2, "Troubleshooting the Installation".
Review the configuration assistant log files located in the oracle_home/cfgtoollogs directory for a specific Oracle Developer Suite configuration assistant. Table E-2 also lists any other log file locations for a specific configuration assistant. Try to fix the issue that caused the error.
If you see a "Fatal Error. Reinstall" message, try to find the cause of the problem by analyzing the log files. Refer to Section E.3.3, "Handling Fatal Errors" for further instructions.
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 E-1:
Table E-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
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 oracle_home/cfgtoollogs directory. Default log file locations are described in Table E-2.
Refer to the section describing the configuration assistants in Table E-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 E-2 includes an "Initial Tasks" section, you must perform these tasks before running the configuration assistant. |
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:
Deinstall the failed installation using the procedure described in Section 4.1, "Deinstallation".
Correct the cause of the fatal error.
Reinstall Oracle Developer Suite.
If the fatal error reoccurs, then you must remove all Oracle installations from your computer using the procedure in Section Section 4.1.1, "Deinstalling Using the Installer".
Table E-2 lists the configuration assistants that run during Oracle Developer Suite installation. Different installation types may use different configuration assistants.
|
Note: Some configuration assistants run in silent mode, which means that their UI is not visible while they are running. |
Table E-2 Oracle Developer Suite Configuration Assistant Descriptions
