I am getting following error while i am installing oracle 9.2.0.1.0 client on my PC. Oracle Universal Installer. Error in writing to directory. Error in writing to directory temp oracle universal installer needs you to have permission in this area to install. Please make sure temp is set to a valid writable directory. PS: This is a generic error which can come for any installation setup. You can use the tips mentioned here for your issue.
This appendix is organized into the following troubleshooting sections:
Debugging Mechanisms in Oracle Universal Installer
During the installation, Oracle Universal Installer writes a text file that contains information on:
- Variable settings
- Action calls
- Queries
- Exception information
The log of installation actions is written to a file named
installActions<date>.log,
located in the <oraInventory>logs
directory. The oraInstall<timestamp>.err
and oraInstall<timestamp>.out
files are also created and stored in the same logs directory. The .log,
.err,
and .out
file for a particular session will be named with the same timestamp.The installation log is used for debugging purposes only. All actions, queries, everything that happens during the installation, and all modifications to the target host are logged in the file.
A sample file is shown below:
Text files are also written in the
temp
directory:If a problem occurs during the installation, you should look for Java exceptions in these files.
Oracle Universal Installer Errors
Refer to the release notes for information on any Oracle Universal Installer limitations for a particular version.
The most common Oracle Universal Installer errors are listed below:
- Out of 'temp' spaceMake sure you have enough space in the default
TEMP
orTMP
directory otherwise the installation will not succeed. The amount of space required depends on the product being installed.Note:On UNIX and Windows, Oracle Universal Installer looks for%TEMP%
then%TMP%.
If neither is set, Oracle Universal Installer will default to/tmp
on UNIX andc:temp
on Windows. - Incomplete stage and missing files in file groupsMake sure you have a good staging area. You may have incorrectly copied the staging area from the CD to the hard disk.
- Exceptions from action libraries:
- NT Services, if a service is already started
- File permissions
- UNCAUGHT_RUNTIME exception when user tries to install the product on his machineThis is a blanket error catch that catches any run-time errors like NullPointers from libraries. Check if the
tempOraInstallorainsrall.err
has any stack trace. The user will have to call support to debug the staging area.
Other Tips
The following tips may help you to troubleshoot:
- Make sure the correct version of the JRE is specified in the PATH.
- If Java cannot run applications from a Sun machine on an NCD X terminal (Oracle Universal Installer does not start), remove the following file:
- If you are deleting an Oracle home manually without using Oracle Universal Installer, the products remain registered with Oracle Universal Installer. You must then simulate a de-install so that all Oracle Universal Installer references are removed.
- If the installation is canceled:
- Products will not be registered with Oracle Universal Installer
- Some files may have been copied, depending on when you issued the cancellation.
X terminal emulators that were tested with Oracle Universal Installer are listed in the following sections.
Exceed
There is a known compatibility issue that Hummingbird has identified to be a problem with Exceed. You can fix it by going into XConfig/Screen Definition/Screen 0 and changing Window Manager from 'Default to Native' to 'Native.' Refer to Figure B-1 to see the proper setup.
Figure B-1 Setting Exceed's Window Manager to 'Native'
Another known issue where Exceed fails to recognize fonts is documented at the following site:
Reflection X
- Refection X 6.2+: Select Settings/Window Manager/ Default Local Window Manager/ Reflection Window Manager. You may also have to select 'X terminal desktop.'
- Reflection X 6.0: Select Connection/New XDMCP Connection/Connection Settings/Direct method/ type host destination and click Connect.
Tarantella
There is a known problem when using Tarantella to send DISPLAY to your Windows system, for instance, when using hosted UNIX systems. The bottoms of some Oracle Universal Installer screens may appear 'cut off,' with buttons not visible. The problem occurs only when you use an individual Tarantella terminal window so that Oracle Universal Installer window appears alone without a broader X-windowing environment.
To work around this problem, do one of the following:
- Use keyboard shortcuts to invoke commands:
- Use Alt-N for Next to move to the next screen.
- On the summary page, use Alt-I to start the installation.
- Use the Window Manager window in Tarantella, which displays the entire screen as if it were a UNIX monitor. Installer dialogs will appear properly in Window Manager.