Error "Following patches have conflicts" when installing the Oracle CPU
search cancel

Error "Following patches have conflicts" when installing the Oracle CPU

book

Article ID: 208519

calendar_today

Updated On:

Products

Data Loss Prevention Oracle Standard Edition 2 Data Loss Prevention

Issue/Introduction

Not able to install the Oracle CPU on Oracle. 

 

The error details will look similar to the following:

--------------------------------------------------------------------------------
[Jan 6, 2021 10:03:31 AM] [INFO]    The following warnings have occurred during OPatch execution:
[Jan 6, 2021 10:03:31 AM] [INFO]    1) OUI-67301:
                                    Following patches have conflicts: [   31465105   31654782 ]
                                    Use the MOS Patch Conflict Checker "https://support.oracle.com/epmos/faces/PatchConflictCheck" to resolve.
                                    See MOS documents 1941934.1 and 1299688.1 for additional information and resolution methods.
[Jan 6, 2021 10:03:31 AM] [INFO]    --------------------------------------------------------------------------------
[Jan 6, 2021 10:03:31 AM] [INFO]    Finishing UtilSession at Wed Jan 06 10:03:31 PST 2021
[Jan 6, 2021 10:03:31 AM] [INFO]    Log file location: D:\oracle\product\12.2.0.1\db_2\cfgtoollogs\opatch\opatch2021-01-06_10-03-24AM_1.log
[Jan 6, 2021 10:03:31 AM] [INFO]    Stack Description: java.lang.RuntimeException: Please rebuild the superset patch [31654782] to make sure it supersedes all the relevant patch(es) [31210848,31465105].
                

Environment

This applies to any version of Oracle when applying a CPU (Critical Patch Update) with Opatch.

Cause

Patches in conflict are shown inside the brackets of the "Following patches have conflicts: [  31465105   31654782 ]" message. The conflict needs to be resolved prior to installation of current CPU.

Resolution

  1. Stop all Oracle services
  2. Uninstall patch that conflicts. 
    1. opatch rollback -id 31465105
    2. The ID will need to match the one listed in brackets listed in log file.
    3. Repeat with any additional conflicting ID's listed. (This may show it's already removed. That is normal.)
  3. Install the current CPU.
  4. If necessary reinstall patch that was removed (ie. patch 31465105, or the latest OJVM patch )

 

Additional Information

Note that the DLP Oracle database template does not require the OJVM patch as we do not use that function.

Also see Oracle Critical Patch Update on Windows fails with error 74

Powered by Wolken Software