"opatch prereq CheckConflictAgainstOHWithDetail -ph ./" shows incorrect results for Composite Patch
(Doc ID 1626610.1)
Last updated on DECEMBER 25, 2019
Applies to:Oracle Universal Installer - Version 22.214.171.124 and later
Oracle Database - Standard Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Scenario 1: Checking for conflicts prior to installing a Patch Set Update (PSU)
You have the following installed:
Running the OPatch command to check for conflicts with the 18.104.22.168.2 PSU (13696216), OPatch reports the 22.214.171.124.2 PSU is in conflict when it should be reporting which sub-patch of the PSU is in conflict
Where patch 14727310 is the 126.96.36.199.5 PSU.
As it is impossible that a newer version (i.e.188.8.131.52.7) of an interim patch conflicts with an earlier version (i.e.184.108.40.206.5) sub-patch, this is clearly not a correct output from OPatch.
OPatch should have reported no conflict.
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
|Scenario 1: Checking for conflicts prior to installing a Patch Set Update (PSU)|
|Scenario 2: Checking in interim patch for conflicts with an already installed Patch Set Update (PSU)|
|Fix: Install the current release of OPatch|
|Workarounds: run "opatch apply -report"|
|Scenario 1: Use -report to simulate the application of the PSU|
|Scenario 2: Use -report to simulate the application of the interim patch|