ExaCS: Conflicts were detected while validating the patch
(Doc ID 2879690.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]Information in this document applies to any platform.
Goal
We can see conflicts while applying April 2022 Patch on DB Home.
Running check_patch_conflict job
[WARNING] [DBAAS-60051] Conflicts were detected while validating the patch.
CAUSE: Refer to log '/var/opt/oracle/log/dbHome/patch/patchAnalyzer_<timestamp>.out' on node Node1.
Completed check_patch_conflict job
-----------------
[root@Node1 patches]# cat /var/opt/oracle/log/dbHome/patch/patchAnalyzer_<timestamp>.out
{
"conflict" : true,
"missingPatches" : [ {
"missingPatchId" : "32327208",
"description" : ""
} ],
"conflictingPatches" : [ {
"candidatePatchId" : "33613833",
"description" : "",
"conflictingWithList" : [ {
"installedPatchId" : "32327208",
"description" : "",
"conflictingWith" : [ "/u02/app/oracle/product/12.2.0/dbhome_9/javavm/admin/fixTZb.sql", "/u02/app/oracle/product/12.2.0/dbhome_9/javavm/admin/fixTZa.sql", "/u02/app/oracle/product/12.2.0/dbhome_9/javavm/lib/tzdb.dat" ],
"conflictingType" : "Files"
} ]
} ]
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 |