sosreport (or rpm -Va, by default part of a sosreport) may change /usr/java/latest symbolic link if it does not point to latest installed release
(Doc ID 1597124.1)
Last updated on AUGUST 20, 2018
Applies to:Linux OS - Version Oracle Linux 5.0 and later
This could only be reproduced with a specific set of circumstances. This included installing a "newer" java runtime package, such as jre-7u9-linux-i586.rpm, then installing an older JRE version with the --force option. The --force is required as RPM will not install an older version of the package without being forced to do so. Some applications may utilize a similar type of configuration, for example a SunRay desktop may require a 32 bit version of Java. This is suspected to behave similarly on all current versions of Linux, though it has not been verified on every version.
- install a version of java (the "newer" version for testing - 7u9 here)
- install (force) an older version of java (6u30 for testing)
-> An rpm -i of the package will fail, as expected, as only one version of
the package may reside in RPM:
As above, this has only been seen in a case where an older JRE version is installed, with a subsequent recreation of the /usr/java/latest symbolic link to point to the (older) version.
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