Warnings While Applying Patch: Entry in the Archive Does Not Have Expected Size
(Doc ID 841737.1)
Last updated on FEBRUARY 12, 2023
Applies to:
Oracle Applications DBA - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]Information in this document applies to any platform.
Symptoms
When attempting to apply a patch the following warning messages occurs:
ERROR
WARNING: Entry README_bc4jmt.txt in the archive /.../apps/apps_st/comn/java/classes
does not have expected size of 1261 bytes (may indicate
corrupt metadata or concurrent modification)
WARNING: Entry README_mdsrt.txt in the archive /.../apps/apps_st/comn/java/classes
does not have expected size of 1251 bytes (may indicate
corrupt metadata or concurrent modification)
WARNING: Entry oracle/adf/mds/internal/ElementData.class in the archive
/.../apps/apps_st/comn/java/classes does not have expected size of
12799 bytes (may indicate corrupt metadata or concurrent modification)
WARNING: Entry oracle/jbo/server/DBSerializer$AMRow.class in the archive
/.../apps/apps_st/comn/java/classes does not have expected size of
3395 bytes (may indicate corrupt metadata or concurrent modification)
WARNING: Entry README_bc4jmt.txt in the archive /.../apps/apps_st/comn/java/classes
does not have expected size of 1261 bytes (may indicate
corrupt metadata or concurrent modification)
WARNING: Entry README_mdsrt.txt in the archive /.../apps/apps_st/comn/java/classes
does not have expected size of 1251 bytes (may indicate
corrupt metadata or concurrent modification)
WARNING: Entry oracle/adf/mds/internal/ElementData.class in the archive
/.../apps/apps_st/comn/java/classes does not have expected size of
12799 bytes (may indicate corrupt metadata or concurrent modification)
WARNING: Entry oracle/jbo/server/DBSerializer$AMRow.class in the archive
/.../apps/apps_st/comn/java/classes does not have expected size of
3395 bytes (may indicate corrupt metadata or concurrent modification)
-- Expected Behaviour
Expect to apply the patch without any warnings.
-- What is working
That patch application is working fine, but the warning messages.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |