In this Document
| Goal |
| Solution |
| Details |
| Announcement |
| Overview |
| Five easy steps to analyze a patch or group of patches using an OPatch inventory report |
| Two easy steps to resolve conflicts |
| How to monitor pending requests |
| Video Demonstration |
| Known Issues |
| Issue 1: PSUs ONLY - Additional patches added to the download table |
| Issue 2: OPatch inventory log files not finding all patches installed or showing as Invalid file selected. Supported file types are text/plain |
| Issue 3: PSUs ONLY - Conflict resolutions may not be found for large merged patches (patches containing more than one fix) |
| Issue 4: 11.2.0.2 and 11.2.0.3 ONLY - Incorrect conflicts between Grid Infrastructure PSU and Database Oracle Home inventory listing reported |
| Issue 5: WLS Conflict check does not detect conflict between 1 patch and an inventory |
| Community Discussion on this article |
| References |
APPLIES TO:
Oracle Fusion Middleware - Version 11.1.1.1.0 and laterOracle Database - Enterprise Edition - Version 9.2.0.8 and later
Generic Linux
Generic UNIX
GOAL
To explain and demonstrate the My Oracle Support Conflict Checker
SOLUTION
Details
Announcement
On July 21, 2014, a new My Oracle Support Conflict Checker tool became available from the My Oracle Support Patches & Updates 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.
NOTE: This tool does not check for entitlement. In most cases, the release of a conflicting patch will be the same as the release of the resolution, therefore, if you are not entitled to download the original patch, you will not be entitled to download a resolution (new or existing). Before running the MOS Conflict Checker, please verify your entitlement by trying to download the original patch.
Overview
1941934.1> My Oracle Support Patch Conflict Checker Overview [VIDEO]
Five easy steps to analyze a patch or group of patches using an OPatch inventory report
NOTE: The intent of this tool is to check for, and resolve conflicts for recommend patches coming from either the Recommended Patch Advisor, documentation or Support.
For example, do not perform an Advance Search and randomly select 50 patches for conflict analysis.
This will result in the tool automatically submitting a request to generate a massive merged patch of the conflicts.
For example, do not perform an Advance Search and randomly select 50 patches for conflict analysis.
This will result in the tool automatically submitting a request to generate a massive merged patch of the conflicts.
- Find the patch(es) by performing one of the following
- a Simple search for a patch or a group of patches
- a Saved search
- a Recent search
- an advance search (selectively)
- search using the Recommended Patch Advisor
- Review a document
- a Simple search for a patch or a group of patches
- Select the patch(es)
- Click Analyze with OPatch
- Search Results
- Detail Results
- Search Results
- Attach the inventory text file (generated by the command "opatch lsinv" found in $ORACLE_HOME/cfgtoollogs/opatch/lsinv) 2 3
- Click Analyze for Conflict
Two easy steps to resolve conflicts
- Click Request Patch or Request all
- Find all patches in the Download table (original non-conflicting patches plus resolutions) 3
How to monitor pending requests
- Click the Patches & Updates tab
- Click the Patch Requests tab in the Plans & Patch Requests region. Look for the Patch Request ID (PR-) of the pending request in the Associated Request column
1 All platforms must be the same or generic
2 This is optional. If the OPatch inventory file is not attached, the conflict checker will analyze all the selected patches for conflict with each other.
3 See video demonstration of the tool for further details to include how to generate the inventory text file and what to do if there is no resolution to a conflict
2 This is optional. If the OPatch inventory file is not attached, the conflict checker will analyze all the selected patches for conflict with each other.
3 See video demonstration of the tool for further details to include how to generate the inventory text file and what to do if there is no resolution to a conflict
Video Demonstration
Please run the following video demonstration of the tool provided in the below document
Known Issues
Issue 1: PSUs ONLY - Additional patches added to the download table
Resolved MOS 15.1 - 01-Feb-2015
Details: When conflict resolution is an overlay patch of a PSU sub-patch, the PSU sub-patch is also being added to the Download table
Workaround: Ignore the PSU sub-patch in the Download table
Fix: Enhancement has been filed requesting the additional patches be suppressed from the download table
BUG 18886721 - CONFLICT CHECKER ADDING UNNECESSARY PATCHES TO THE DOWNLOAD PATCH TABLE
Issue 2: OPatch inventory log files not finding all patches installed or showing as Invalid file selected. Supported file types are text/plain
Details: Only the lsinventory*.txt file from $ORACLE_HOME/cfgtoollogs/opatch/lsinv is supported for the inventory listing
Resolution: An Enhancement Request is being worked so that the opatch*.log file in $ORACLE_HOME/cfgtoollogs/opatch will be supported
Issue 3: PSUs ONLY - Conflict resolutions may not be found for large merged patches (patches containing more than one fix)
Bug 18947219 - FIX DETAILED IN 18261260 STILL CAUSES ARU RESOLVE CONFLICT ISSUES
Details: If a merged patch is installed or selected to be installed, conflict resolutions with a PSU may not be found. Additionally, if other patches conflict with the same PSU patch (or sub-patch), their resolutions may not be found
Workaround: See the following
Document 1913040.1 Patch conflict analysis may not find resolutions for large merged patches
Issue 4: 11.2.0.2 and 11.2.0.3 ONLY - Incorrect conflicts between Grid Infrastructure PSU and Database Oracle Home inventory listing reported
Bug 19365002 - ARU CC reporting conflict with a DB interim patch and GI PSU where there's none
Details: Conflicts are reported when analyzing the Grid Infrastructure Patch Set Update (PSU) against an inventory listing from the Database Oracle Home
Workaround: Perform the conflict analysis on the Database Oracle Home inventory using the Database PSU patch instead of the Grid Infrastructure patch
Issue 5: WLS Conflict check does not detect conflict between 1 patch and an inventory
Bug 23225728 - Show bug WLS conflict check does not detect conflict between 1 patch and an inventory
Bug 23225671 - Show bug WLS conflict check does not detect conflict between 2 patches
Bug 23225671 - Show bug WLS conflict check does not detect conflict between 2 patches
Details: Result "you can apply both patches together" while one expects "patches are incompatible due to different prerequisites".
Cause: The patches are on different base release. ARU conflict checker does not check release.
ER: BUG 19467881 - MOS CC should warn when the releases of selected patches are mismatched
Community Discussion on this article
The window below is a live discussion of this article (not a screenshot). We encourage you to join the discussion by clicking the "Reply" link below for the entry you would like to provide feedback on. If you have questions or implementation issues with the information in the article above, please share that below.
REFERENCES
NOTE:1913040.1 - Patch conflict analysis may not find resolutions for large merged patches
NOTE:1941934.1 - My Oracle Support Patch Conflict Checker Overview [VIDEO]
No comments:
Post a Comment