Database Patch Conflict Resolution (Doc ID 1321267.1)

Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Database Patch Conflict Resolution (Doc ID 1321267.1)

In this Document
Goal
Ask Questions, Get Help, And Share Your Experiences With This Article
Solution
THE EASY WAY: Using My Oracle Support to find resolutions to conflicts
My Oracle Support Conflict Checker
OCM Configurations
THE HARD WAY: Patch Set Update (PSU)
Verify if a PSU is installed
Verify it is an actual conflict
Verify if the conflicting patch is an overlay patch
If it is an overlay patch
Is the PSU a Composite Patch
Determine if the PSU is packaged as a Composite Patch
Non-Composite Patch
Check My Oracle Support under the Patches and Updates tab for a solution to your conflict:
Check for available replacement patch
Composite Patch
Examples of output from OPatch when installing a PSU
Examples of output from OPatch when installing an interim patch
Determine the version of the Composite sub-patch associated to the conflict
Check My Oracle Support under the Patches and Updates tab for a solution to your conflict:
Check for available replacement patch
THE HARD WAY: Critical Patch Update/Security Patch Update (CPU/SPU)
CPU/SPU conflicting with an already install PSU
CPU/SPU conflicting with a non-psu or non-security patch
All other conflicts
Provide the following information via a Support Request

References
APPLIES TO:
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

GOAL
The goal of this documented is to assist customers in finding resolutions to patch conflicts and if no resolutions is available, provide Oracle Support the information required to resolve the conflict.

Ask Questions, Get Help, And Share Your Experiences With This Article
Would you like to explore this topic further with other Oracle Customers, Oracle Employees, and Industry Experts?

Click here to join the discussion where you can ask questions, get help from others, and share your experiences with this specific article.
Discover discussions about other articles and helpful subjects by clicking here to access the main My Oracle Support Community page for Database Install/Upgrade.

SOLUTION
THE EASY WAY: Using My Oracle Support to find resolutions to conflicts
My Oracle Support Conflict Checker
A new My Oracle Support Conflict Checker tool is now available from the Patch Search results page. This tool enables you to upload an OPatch inventory and check the patches that you want to apply to your environment for conflicts.

If no conflicts are found, you can download the patches. If conflicts are found, the tool finds an existing resolution to download. If no resolution is found, you can request a solution and monitor your request in the Plans region.

For more information and a demonstration video, see

Note 1091294.1 "How to use the My Oracle Support Conflict Checker Tool".

OCM Configurations
If your installation has a current configuration uploaded to My Oracle Support, you can utilize Patch Plans to verify and resolve conflicts. Should a resolution not exist for the conflict, it will also provide you a link to request a resolution without ever having to create an Support Request.

For videos on Patch Plans, please review the following:

Document 603505.1 My Oracle Support Speed Training - Links to Recorded Training
Support Tools and Processes tab
Why use Configuration Manager in MOS
Configuration Manager
Installing the Collector
MOS Configuration Manager
Patch Recommendations and Patch Plans
THE HARD WAY: Patch Set Update (PSU)
Verify if a PSU is installed
If it is unknown if a PSU is already installed, see the following document for verification steps:

861152.1> Do Patchset Updates (PSU's) Change the Oracle Release Version/Fifth Digit?

Verify it is an actual conflict
Definition: Overlay Patch

When a patch conflilcts with the PSU, an Overlay patch is created with the same version of the PSU. For example, the PSU is 11.1.0.7.8, the overlay patch will be 11.1.0.7.8. The overlay patch will be installed after the PSU and "overlays" the PSU with a merge of the conficting fixes of the PSU and original patch.

Verify if the conflicting patch is an overlay patch
Run the following

% opatch lsinv

Check inventory listing to see if the conflicting patch is an overlay patch. For example:
Patch 11840910 : applied on Fri Oct 12 11:22:09 EDT 2012
Unique Patch ID: 14478518
Created on 13 Jan 2012, 05:48:59 hrs PST8PDT
Bugs fixed:
11840910
This patch overlays patches:
13343438
This patch needs patches:
13343438
as prerequisites

If it is an overlay patch
Verify if it needed to be using the following note to confirm the base version (i.e. 11.1.0.7.0) can not be installed

Document 1357613.1 Can a patch be applied if it is available on base/release version, even though PSU/CPU/SPU is installed

Is the PSU a Composite Patch
A new patckaging model was introducted in April 2012 for certain releases of the PSU called the Composite Patching model. If you are not familiar with the Composite Patch model, please review the following:

1376691.1> Composite Patches for Oracle Products

The 1st step is to determine if the PSU associated to your conflict has been built on the Composite Patching packaging model

Determine if the PSU is packaged as a Composite Patch
See Section 2 of the following document for a table containing which releases are Composite Patches

<Document 1376691.1> Composite Patches for Oracle Products [Video]

Non-Composite Patch
Check My Oracle Support under the Patches and Updates tab for a solution to your conflict:
Enter the patch number in Patch ID and search for the platform matching your configuration. If a patch exists which is the same release as the PSU you are installing (egg. 11.1.0.7.8) then download and install that patch (after installing the PSU) to resolve the conflict.

Check for available replacement patch
Review the following document for possible replacement patch

Document 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution

If no resolution, go to Provide the following information via a Support Request

Composite Patch
Examples of output from OPatch when installing a PSU
Checking for conflicts before installing a PSU
% opatch prereq CheckConflictAgainstOHWithDetail -ph ./13343438

Following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches :
12646784, 13696216, 11840910

Following patches will be rolled back from Oracle Home on application of the patches in the given list :
12646784, 11840910

Conflicts/Supersets for each patch are:

Patch : 13696216

Conflict with 12646784
Conflict details:
<$ORACLE_HOME>/lib/libserver11.a:/atb.o

Conflict with 11840910
Conflict details:
<$ORACLE_HOME>/lib/libserver11.a:/kta.o

Installing a PSU
% opatch apply

Composite Patch 13696216 conflicts with installed patch(es) 12646784, 11840910

Conflict Description:
Here are the specific sub-patches of composite patch 13696216 that conflict with 12646784, 11840910

Sub-Patch 13343438 conflicts with 11840910

Sub-Patch 13696216 conflicts with 12646784

Conflict Remedy:
Refer to My Oracle Support Note 1299688.1 for instructions on resolving patch conflicts.

Notice the output from the apply does not agree with the output of the CheckConflictAgainstOHWithDetail.

apply states:

Sub-Patch 13343438 conflicts with 11840910

Sub-Patch 13696216 conflicts with 12646784
CheckConflictAgainstOHWithDetail states:

11840910 and 12646784 both conflict with 13696216
This is a known issue and will be resolved in a future release of OPatch. The correct information is the output from the apply.

So before proceeding you need to utilize Scenario 1 in the following note to determine which sub-patch is associated to the conflict:

Document 1626610.1 "opatch prereq CheckConflictAgainstOHWithDetail -ph ./" does not show correct Composite sub-patch

Installing a PSU when the PSU conflicts with multiple sub-patches
Composite Patch 13923374 conflicts with installed patch(es) 13632140

Conflict Description:
Here are the specific sub-patches of composite patch 13923374 that conflict with 13632140

Sub-Patch 13343438 conflicts with 13632140

Sub-Patch 13696216 conflicts with 13632140

Sub-Patch 13923374 conflicts with 13632140
In the case where the PSU conflicts with multiple sub-patches, use the latest sub-patch (largest patch number) during the Conflict Resolution process. In the example above, use 13923374.

Examples of output from OPatch when installing an interim patch
Checking for conflicts with a PSU before installing an interim patch
Following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches :
13343438, 11840910

Following patches will be rolled back from Oracle Home on application of the patches in the given list :
13343438

Conflicts/Supersets for each patch are:

Patch : 11840910

Conflict with 13343438
Conflict details:
<$ORACLE_HOME>/lib/libserver11.a:/kta.o
Installing an interim patch that conflicts with a PSU
Patch 11840910 conflicts with the composite patch 13696216 (specifically, sub-patch(es) 13343438). Please refer to the following to resolve the conflict(s): Patch conflict resolution (Doc ID 1299688.1)
or
Patch 12646784 conflicts with the composite patch 13696216 (specifically, sub-patch(es) 13696216). Please refer to the following to resolve the conflict(s): Patch conflict resolution (Doc ID 1299688.1)

Installing an interim patch that conflicts with multiple sub-patches of a PSU
Patch 13632140 conflicts with the composite patch 13923374 (specifically, sub-patch(es) 13923374,13696216,13343438).

In the case where the interim patch conflicts with multiple sub-patches, use the latest sub-patch (largest patch number) during the Conflict Resolution process. In the example above, use 13923374.

Determine the version of the Composite sub-patch associated to the conflict
Look up the Composite sub-patch number in the following document

Document 753736.1 Quick Reference to Patchset Patch Numbers

Check My Oracle Support under the Patches and Updates tab for a solution to your conflict:
Under Search, enter the non-PSU patch number (11840910) in Patch ID and search for the platform matching your configuration. If a patch exists which is the same release as the PSU sub-patch associated to the conflict (i.e. 11.2.0.3.1) then to resolve the conflict, download and install that patch after installing the PSU.
Check for available replacement patch
Review the following document for possible replacement patch

Document 1061295.1 Patch Set Updates - One-off Patch Conflict Resolution

If no resolution, go to Provide the following information via a Support Request

THE HARD WAY: Critical Patch Update/Security Patch Update (CPU/SPU)
CPU/SPU conflicting with an already install PSU
Run the following to determine if the PSU is installed

% $ORACLE_HOME/OPatch/opatch lsinventory

Review the output looking for any version of the PSU installed
This is not supported as documented in the current Patch Set Update and Critical Patch Update Availability Document. If a PSU is installed, you must do one of the following:

Install the current PSU instead of the CPU/SPU

Rollback the PSU and install the CPU/SPU. This is not recommnded as by rolling back the PSU, you wll be removing many fixes installed in the ORACLE_HOME
CPU/SPU conflicting with a non-psu or non-security patch
Go to Provide the following information via a Support Request
All other conflicts

Provide the following information via a Support Request
Ensure that you have the latest version of OPatch. If you do not have the latest version, then follow the instructions outlined in the My Oracle Support

224346.1> OPatch - Where Can I Find the Latest Version of OPatch?

Run the following

UNIX:
% $ORACLE_HOME/OPatch/opatch lsinventory

Windows:
%ORACLE_HOME%\OPatch\opatch lsinventory

• upload the current log file in

UNIX:
$ORACLE_HOME/cfgtoollogs/opatch (not the opatch_history.txt file)

Windows:
%ORACLE_HOME%\cfgtoollogs\opatch

Upload the OPatch log showing the conflict

Post the result of the following in the SR

UNIX:
% uname -a
% file $ORACLE_HOME/bin/sqlplus

REFERENCES
NOTE:1626610.1 - "opatch prereq CheckConflictAgainstOHWithDetail -ph ./" shows incorrect results for Composite Patch
NOTE:563656.1 - Different types of Patch Conflicts - Superset/Subset/Duplicate/Bug/File
NOTE:861152.1 - Do Patchset Updates (PSU's) Change the Oracle Release Version/Fifth Digit?