Oracle Key Manager (OKM) - Issues Using OKM GUI Installers on a System Where Java 8 is Installed

Asset ID:	1-72-2137379.1
Update Date:	2017-09-13
Keywords:

Solution Type Problem Resolution Sure

Solution 2137379.1 : Oracle Key Manager (OKM) - Issues Using OKM GUI Installers on a System Where Java 8 is Installed

Applies to:

Oracle Key Manager - Version 2.0.0 and later
Information in this document applies to any platform.

Symptoms

Error messages might appear when launching one of the installers for the Oracle Key Manager GUI and CLIs on a system where Java 8 is installed. These particular error messages are not seen on systems where Java 5, 6, or 7 is installed. This article describes these error messages and provide workarounds to follow, should these error messages appear.

Cause

Java 8 is installed on the system platform where the OKM GUI is being installed.

Solution

Solaris 10 SPARC Systems

The following behavior has been seen on Solaris 10 SPARC systems.

Installer Reports Error About kms_config File

The installer on a Solaris 10 SPARC system might display an error about the kms_config file. The Oracle_Key_Manager_InstallLog.log file contains the following messages:

Modify Text File – Single File: kms_config
Status: ERROR
Additional Notes: ERROR – Unable to locate ASCII
text file to be manipulated. Deferring...

When you try to launch the Oracle Key Manager GUI, you see the following messages:

"$" ./Oracle_Key_Manager: line 18: /path/to/dir/kms_config:
No such file or directory
missing directory , not properly installed

These messages have been seen on a Solaris 10 SPARC system where Java 8 has been installed. Bug 23010108 describes this behavior in more detail.

To work around this behavior, contact Oracle Customer Support in order to obtain an OKM Solaris GUI installer which contains its own Java Virtual Machine (JVM). Then download and launch this installer as usual.

Another approach to work around this behavior can be used when the SPARC system also has Java 5, 6, or 7 installed. Launch the installer at a command prompt, specifying "LAX_VM" and the full path to the "java" file in the Java 5, 6, or 7 installation: For example:

$ sh OKMManager_solaris_3_0_2_without_JVM.bin LAX_VM \
> /usr/jdk/jdk1.7.0_05/bin/java

Solaris 10 SPARC and x86 Systems

The following behavior has been seen on Solaris 10 SPARC and x86 systems.

Installer Displays Not Supported Error

The installer on a Solaris 10 SPARC system might display an "Installer User Interface Mode Not Supported" error message and then fail. This error message has been seen on Solaris systems where a Java 8 Java Development Kit (JDK) has been installed instead of or in addition to a Java 8 Runtime Environment (JRE).

If your system is a SPARC system:
1. Contact Oracle Customer Support in order to obtain an OKM Solaris GUI installer which contains its own Java Virtual Machine (JVM). Then download and launch this installer as usual.

If your system is an x86 system:
1. If a Java 8 JRE is not already installed, first download and install a Java 8 JRE from the Oracle Java Download web site.
2. Launch the installer at a command prompt, specifying "LAX_VM" and the full path to the "java" file in the Java 8 JRE installation: For example:

$ sh OKMManager_solaris_3_0_2_without_JVM.bin LAX_VM \
> /usr/java/jre1.8.0_91/bin/java

Windows Systems

The following behavior has been seen on Windows systems.

Installer Displays Windows Error

The installer on a Windows system might display a "Windows error 2" error message and then fail. This error message has been seen on Windows systems where a Java 8 Java Development Kit (JDK) has been installed instead of or in addition to a Java 8 Runtime Environment (JRE).

To run the installer successfully, first bring up a DOS window. To do this, go to the Start menu on your Windows systems and enter "cmd" in the search field at the bottom of the Start menu.

In the DOS window, navigate to the location where you downloaded the Oracle Key Manager GUI installer. For example:

C:\User\myuser> cd \Users\myuser\Downloads

Then launch the installer at the command prompt, specifying "LAX_VM" and the full path to the "java.exe" file that you are using. For example (as one command line):

C:\User\myuser\Downloads> OKMManager_windows_3_0_2_without_JVM.exe LAX_VM "C:\Program Files\Java\jre1.8.0_77\bin\java.exe"

Uninstaller Displays Java Error

The uninstaller on a Windows system might display a Java error message similar to the following message and then fail:

Error: Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.8', but '1.7' is required.

You might see this error message if you had installed Java 8 after you installed the Oracle Key Manager and CLIs. For example, Java 7 was installed on your Windows system where you installed the OKM GUI and CLIs, and later you upgraded to Java 8.

To run the uninstaller successfully, first edit the Uninstall_Oracle_Key_Manager.lax file (which resides in the Uninstall_Oracle_Key_Manager folder under your GUI installation folder) and modify the lax.nl.current.vm entry to reference an older Java "javaw.exe" file that appears on your Windows system. For example:

#lax.nl.current.vm=C:\\windows\\system32\\javaw.exe
lax.nl.current.vm=C:\\Program Files\\java\\jre1.7.0_101\\bin\\javaw.exe

Then invoke the uninstaller from the Programs and Features console panel as usual.

Attachments

This solution has no attachment