How to Use My Oracle Support Conflict Checker Tool

  • by

The checker provided by My Oracle Support (MOS) is for detecting any conflicts between your database configuration and the incoming patch. The URL is at:

https://support.oracle.com/epmos/faces/PatchConflictCheck

Of course, you must have a MOS account for accessing it.

My Oracle Support Conflict Checker tool

My Oracle Support Conflict Checker tool

1. Select Platform

My Oracle Support Conflict Checker tool - Select Platform

My Oracle Support Conflict Checker tool - Select Platform

2. Attach lsinventory Log

You should do a detail opatch lsinventory first in order to get the latest configuration of installed Oracle software.

[oracle@primary01 ~]$ $ORACLE_HOME/OPatch/opatch lsinventory -detail

The log file is usually in the following directory:

$ORACLE_HOME/cfgtoollogs/opatch/lsinv

Then you upload the log file and attach it. Please note that, I renamed the log file before uploading, as you can see in the screen shot. If you don't mind, you can keep the original filename unchanged.

My Oracle Support Conflict Checker tool - Attach lsinventory Log

My Oracle Support Conflict Checker tool - Attach lsinventory Log

3. Add Patches

You can search and select the target patches that you want to apply.

My Oracle Support Conflict Checker tool - Select Target Patches

My Oracle Support Conflict Checker tool - Select Target Patches

4. Analyze for Conflicts

Click on Analyze for Conflicts.

My Oracle Support Conflict Checker tool - Analyze for Conflicts

My Oracle Support Conflict Checker tool - Analyze for Conflicts

My Oracle Support Conflict Checker tool - Analysis in Progress

My Oracle Support Conflict Checker tool - Analysis in Progress

5. See Results

When the page returned, you can see the result.

My Oracle Support Conflict Checker tool - Analysis Results

My Oracle Support Conflict Checker tool - Analysis Results

Next, you may like to know more ways to check prerequisites and conflicts before applying patches.

Leave a Reply

Your email address will not be published. Required fields are marked *