ODSEE Command Line Tools Can Fail If JAVA_HOME Is Set to an Unsupported JDK/JRE Release Level
(Doc ID 1359129.1)
Last updated on JUNE 13, 2020
Applies to:Oracle Directory Server Enterprise Edition - Version 6.3 SP1 and later
Information in this document applies to any platform.
On : ODSEE 6.x through 11x versions, When using command line administration tools such as the dsconf command to perform an administrative tasks. Errors, exceptions or silent failure with no response from the dsconf command line can take place in an administration command prompt or shell. It will fail regardless of switches provided or when attempting to use it with any of the documented sub-commands as well.
To reproduce the issue:
1. Install ODSEE 11x on Windows, Linux or Solaris
2. Attempt to use command lines to manage/configure DS with JAVA_HOME set to an older (1.5x) or too new JDK (or when the PATH environment variable points to another JDK version)
http://www.oracle.com/technetwork/middleware/downloads/odsee-11gr1certmatrix-161592.xls under the System Certification tab, Client Certification section.
If there are still issues, please open a service request.
Note: For some ODSEE 184.108.40.206.x versions on Windows, command line tools such as dsconf may fail with this access log output -
When attempting to use dsconf using the secure port (without -e switch) it
fails with this access log output -
One consideration is that on an ISW installation or when java based services run on the host alongside with the ODSEE and are administered in common, there can be problems. Consider creating unique environment shell scripts that you can source so that your JAVA_HOME and PATH can be set easily on demand. See KM Doc ID 1325656.1 for information on using Unix and Linux systems. A BAT file can be used to wrap the command, setting the environment as well on windows.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document