JRIMETA.DAT and how java class files can be overwritten by lower versions contained in a patch
(Doc ID 1304331.1)
Last updated on SEPTEMBER 28, 2021
Applies to:
Oracle Application Object Library - Version 11.5.10.0 to 12.1.3 [Release 11.5 to 12.1]Oracle E-Business Suite Technology Stack - Version 11.5.10.0 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Goal
Prevent java class files from being overwritten by lower versions when applying patches.
For example before the patch installation:
- OAWebBeanMetaData.class's version is 115.41,
and after applying RUP7:
- OAWebBeanMetaData.class's version is 115.10
Thus during the patch application via adpatch, the .class file was overwritten by an older version.
- OAWebBeanMetaData.class's version is 115.41,
and after applying RUP7:
- OAWebBeanMetaData.class's version is 115.10
Thus during the patch application via adpatch, the .class file was overwritten by an older version.
Solution
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
Goal |
Solution |