Why patch Do Not Update the required higher file version in environment after successful patch application
(Doc ID 2715776.1)
Last updated on OCTOBER 05, 2020
Applies to:
Oracle Applications DBA - Version 12.2 to 12.2.9 [Release 12.2Cloud to 12.2]Information in this document applies to any platform.
Goal
Applied patch XXXXXX twice, once in with forceapply=yes but patch did not update the required higher file version which it has to deliver and update in the environment.
For example: For File axxxx.sql
File version in patch 120.36.12020000.4 while file version in instance after successful patching is 120.36.12020000.3
The patch lgi file shows,
Turning off the following actions as the file should not be present on-site:
Action Product Filename Directory
——————————————————————
copy fnd axxxx.sql admin/template ========>>> File
unknown fnd FNDXXX.fmb forms/US
copy fnd DigSXXXXa.jsp html/jsp/fnd
Why the patch did not update the existing file to higher version even after successful patch application in EBS?
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 |
| References |