Oracle® Database Installation Guide 10g Release 1 (10.1.0.2.0) for Windows Part Number B10130-01 |
|
|
View PDF |
This appendix contains information about troubleshooting. It includes information about the following topics:
Before performing any of the troubleshooting steps in this appendix, ensure that the system meets the requirements and that you have completed all of the preinstallation tasks specified in Chapter 2, " Oracle Database Preinstallation Requirements".
Read the release notes for the product on your platform before installing it. The release notes are available on the Oracle Database installation media. The latest version of the release notes is also available on the OTN Web site
http://otn.oracle.com/documentation/
If you encounter an error during installation:
Do not exit Oracle Universal Installer.
If you clicked Next after you entered incorrect information about one of the installation screens, click Back to return to the screen and correct the information.
If you encounter an error while Oracle Universal Installer is copying or linking files, see the "Reviewing the Log of an Installation Session" section.
If you encounter an error while a configuration assistant is running, see the "Troubleshooting Configuration Assistants" section.
If you cannot resolve the problem, remove the failed installation by following the steps listed in the "Cleaning Up After a Failed Installation" section.
During an installation, Oracle Universal Installer records all of the actions that it performs in a log file. If you encounter problems during the installation, review the log file for information about possible causes of the problem.
Log files are located in the SYSTEM
_
DRIVE
:\Program Files\Oracle\Inventory\logs
directory. Log filenames take the form installActions
date_time
.log
(for example, installActions2003-05-14_09-00-56-am.log
).
Note: Do not delete or manually alter theInventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system. |
To troubleshoot an installation error that occurs when a configuration assistant is running:
Review the installation log files listed in the "Reviewing the Log of an Installation Session" section.
Review the specific configuration assistant log file located in the ORACLE_BASE
\
ORACLE_HOME
\cfgtoollogs
directory. Try to fix the issue that caused the error.
If you see the Fatal Error. Reinstall message, look for the cause of the problem by reviewing the log files. Refer to the "Fatal Errors" section for further instructions.
Oracle configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the installActions
date_time
.log
file.
The execution status codes are listed in the following table:
Status | Result Code |
---|---|
Configuration assistant succeeded | 0 |
Configuration assistant failed | 1 |
Configuration assistant cancelled | -1 |
If you receive a fatal error while a configuration assistant is running, you must remove the current installation and reinstall the Oracle software, as follows:
Remove the failed installation as described in the "Cleaning Up After a Failed Installation" section.
Correct the cause of the fatal error.
Reinstall the Oracle software.
To determine whether a silent installation succeeds or fails, see the installActions
date_time
.log
file.
If necessary, see the previous section for information about determining the location of the Inventory
directory.
A silent installation fails if:
You do not specify a response file
You specify an incorrect or incomplete response file
Oracle Universal Installer encounters an error, such as insufficient disk space
Oracle Universal Installer or configuration assistant validates the response file at runtime. If the validation fails, the silent installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file.