Do You Have a Novell Client Installed on the machine ?
Printable View
Do You Have a Novell Client Installed on the machine ?
Another variant of this problem is when Oracle says it can't find the msvrct42.dll file. I've had to copy this file directly in to the directory.
In case it is not this problem, is there anything in the inventory log?
Also, there may be a compatilbility problem with OUI and your computer. You can try downloading a newer version of OUI from Oracle's ftp site. I had to do that with 6.0 and 8.1.6 on a Dell NT workstation.
There is no Novell Client installed on this server.
Can you provide the path to the Oui on the oracle website so that I can download it. Additional explanation as to why this might be the problem would be appreciated.
Try the following Notes on the metalink which deal with similar problems
http://metalink.oracle.com/metalink/...atabase_id=NOT
http://metalink.oracle.com/metalink/...T&p_id=73123.1
http://metalink.oracle.com/metalink/...atabase_id=NOT
I don't have access to metalink at this time. What are these articles in reference to?
Problem Description:
====================
You are installing Oracle 8.1.5. When the installer begins to copy files to
your drive, the installer program disappears from the screen with no errors.
Problem Explanation:
====================
You may be encountering JAVA specific errors. These errors are documented in
C:\TEMP\ORAINSTALL\ORAINSTALL.ERR.
Search Words:
=============
OUI, JRE, JAVA
START
Solution Description:
=====================
There is a conflict between two OUI installations, or two JAVA version present
on the system.
Clean up the system settings, so the OUI can start completely anew again.
Solution Description:
=====================
1) Remove the INST_LOC:
On NT from the registry in the key HKEY_LOCAL_MACHINE/Software/Oracle
On UNIX from the /var/opt/oracle directory
2) Unset any CLASSPATH setting specified in the environment prior to
launching OUI.
3) Remove any PATH settings to other JAVA versions prior to launching
OUI.
Restart the OUI from the CD.
Solution Explanation:
=====================
A conflict with another JAVA product, or incorrect settings from a previous
installation can confuse the Universal Installer and make it lock up
completely.
Problem:
--------
Universal Installer fails to install.
The program either hangs or terminates after the initial splash screen.
Solution:
---------
There are two distinct possibilities here, causing the Universal Installer to
fail:
1) The Installer is detecting a 'lock', and is therefore quitting the
installation.
If during the previous installation, the Installer was interrupted in the
middle of an installation, a file called 'writer.lock' will still exist in
the 'lock' directory.
This is in fact a signal for the Universal Installer to abort this run,
since a previous run is still busy.
In this case, remove the "WRITER.LOCK" file from the lock directory in the
Universal Installer inventory.
The location of the inventory directory is specified:
- On Windows NT in the "INST_LOC" registry variable in HKLM/Software/Oracle
- On UNIX in the file "oraInst.loc", located in "/var/opt/oracle" (or /etc,
depending on the UNIX flavour)
See also [NOTE:71919.1] about debugging the Universal Installer.
2) There is a lock up with other JAVA programs:
If there are other JAVA products installed, with potential other JRE
versions on the system, it is possible that the system environment settings
are interfering with the JAVA version of the Universal Installer.
Solution here:
1) Open a new command window
2) Remove the CLASSPATH setting from the environment
3) Remove the INST_LOC from the registry on Windows NT, or remove the
"oraInst.loc" file on UNIX.
4) Restart the Universal Installer from the distribution media.
5) During this run, the Universal Installer will be installed again on the
system.
See also [NOTE:1075227.6]: Universal Installer disappears from the screen
PURPOSE
This document gives an overview of the debugging possibilities when something
unexpected happens during an installation, using the new Oracle Universal
Installer.
RELATED DOCUMENTS
Universal Installer Concepts Guide
Debugging the Universal Installer:
==================================
A couple of files can be consulted to check and debug the Oracle Universal
Installer.
First, find the location of the Installer software:
- On NT, the location of the Universal Installer Repository can be found in the
registry, in the following key:
HKEY_LOCAL_MACHINE
Software
Oracle
inst_loc REG_SZ full_directory_specification
The value of this variable points to the Installer software inventory, a
series of files that contain the information about all the installed
components on the machine.
If nothing is specified on NT, the first time installation will copy the
Oracle Universal Installer in the directory \Program Files\Oracle\Inventory
The registry variable can be preset, to force the Installer to install itself
in another directory.
- On UNIX platforms, the location of the Oracle Inventory is located in the
file "oraInst.loc". This file either resides in the "/var/opt/oracle"
directory, or in the "/etc" directory.
- On the same level as the Oracle Inventory, a few new directories are also
created:
* An OUI directory, containing the actual installer.
* A JRE directory, containing the patched Oracle JRE version, which the
Installer uses.
* An OSP directory, if the Software Packager is installed as well.
During the installation, some log files are created, and appended with the
information about the actions of the Installer:
- A file named "install.platform" will be created in the root of the Inventory
directory. This file contains the platform ID of the machine where the
Installer is running.
The ID written in this file is unique and must reflect the machine the
Installer is working on.
The Installer will check this file, if it already exists, and see if the
requested installation does indeed contain a procedure for this platform.
- Whenever a new install session is started, a file ("writer.lock") will be
written in the Inventory directory "Oracle/Inventory/locks". When the
Installer detects a file already there, it assumes that someone else is
in the middle of an installation and will not continue.
If the Installer does give an error and stops, remove the lock file, and
then retry the installation.
- All actions performed during the installation, are stored in a file called
"installActions.log", which is created in the "Oracle/Inventory/logs"
directory.
A new installer session will rename the current "installActions.log" file
and add the date and hour of the last installation to the log file. This
prevents overwrites of the Installer log files.
- JAVA specific information about the behavior is written to the
"oraInstall.err" and "oraInstall.out" files, in the $TEMP directory of the
system. All JAVA specific errors or warnings encountered during the
installation will be written to those files.
- If a silent installation is being done, a file called "silentInstall.log"
will be created in the $TEMP directory if an error occurs during the
installation.
If no such file is present, the installation was succesful and no errors
or warnings were encountered.
Languages used by the Installer:
================================
By default, the JRE will query the Operating System it runs on, and detect
which language is set there. The Universal Installer will then use this
language to display the information during the installation.
If you do not want the JRE and OUI to take the language specified at the
OS level, change the value of the NLS_ENABLED variable in the "oraparam.ini"
file. This file is located in the OUI directory, which resides at the same
level as the software inventory specified by the INST_LOC variable.
In this file, change:
[Oracle]
...
NLS_ENABLED=TRUE
...
into:
[Oracle]
...
NLS_ENABLED=FALSE
...
JAVA debugging:
===============
The Oracle Universal Installer gets the information and location of the JAVA
environment from a special configuration file, called "oraparam.ini". This file
is located in the OUI directory, at the same level as the software inventory.
Two variables in that file are important for the behavior of the JAVA runtime:
[Oracle]
JRE_LOCATION=C:\Program Files\Oracle\jre\1.1.7
JRE_MEMORY_OPTIONS=-ms16m -mx32m
The JRE_LOCATION points to the directory in which the JRE runtime is
installed.
The second parameter is specifying some variables which will influence
the behavior of the JRE. Additional JRE debugging parameters can be
specified here on this line. The installer will then pick up the extra
parameters as well and use them to start the Universal Installer.
I discovered that the orant directory was still in the environment variables path. I removed it and re-launched the installer. The same problem occurs.
What should I look for in my InstallActions.log that would give me some indication of what went wrong?