Replacing the Oracle Transportation Management-installed JDK
(Doc ID 1300509.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Transportation Operational Planning - Version 6.1.0 and later
Oracle Trade Compliance - Version 6.1.1 and later
Oracle Transportation Sourcing - Version 6.1.0 and later
Oracle Transportation Management - Version 6.1.0 and later
Oracle Global Trade Management - Version 6.1.0 and later
Information in this document applies to any platform.
OTM is certified with a specific version of the JDK from a specific vendor. There will be times when it becomes necessary to upgrade the JDK outside of an explicit recommendation from OTM Support or Development, for example when a security patch is released by the JDK vendor. OTM will support such upgrades with the following provisions:
- The JDK vendor does not change (for this purpose the Sun and JRockit JDKs are considered to be from separate vendors)
- The JDK is not downgraded to a lower version than what OTM was shipped with
- The JDK is not upgraded to a new major version (e.g. from 1.5 to 1.6)
- In the very rare case where a JDK-specific bug is suspected that cannot be reproduced on the certified version of the JDK, the client may need to revert to a certified version and reproduce the issue before further work is done on the bug
Note: Switching JDKs can cause problems with the OTM code that OTM has no control over. All of these instructions must first be done on a test system followed by extensive system testing done by the client. If the instructions are followed, reverting to a previous, working version of the JDK will be quick and simple.
Note: Any SEV1 issues logged involving the changing of JDK versions will always be dealt with by first reverting JDK versions to the last working version, followed by the downgrade of the SR and replication of the issue in a test instance.
Note: A full JDK is required by OTM; a simple JRE will not suffice. The instructions below will verify that a full JDK has been installed.
Note: Unless explicitly stated otherwise, all JDKs of all WEB & APP servers in a single OTM instance must be upgraded at the same time. We will not support an instance where only some of the JDKs have been upgraded.
Note: For the OTM " error java.sql.SQLException: OALL8 is in an inconsistent state" when running OTM 6.2.x upgrade the the driver to 22.214.171.124.0
The file that should be updated is ojdbc6.jar Update the ojdbc6.jar file in the diretories:
This information applies to OTM Administrators with a high level of expertice.
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
|Reverting to a Previous JDK Version|