When applying an Oracle patch using OPatch, it’s not uncommon to encounter the error message:
UtilSession failed: Prerequisite check “CheckMinimumOPatchVersion” failed.
This issue often appears during patching operations on Oracle Databases, Grid Infrastructure, or Middleware products. It indicates that the current OPatch utility version is outdated or incompatible with the patch you are trying to apply.
In this blog, we’ll cover:
- Why this error occurs
- How to verify your OPatch version
- How to download and update OPatch properly
- Best practices to avoid patching failures in the future
Understanding the Error
The OPatch utility is Oracle’s official patching tool used to apply interim patches (one-offs) and bundle patches like Release Updates (RU) or Patch Set Updates (PSU).
Before proceeding with patching, Oracle performs several prerequisite checks, one of which is CheckMinimumOPatchVersion.
When the current version of OPatch does not meet the minimum required version mentioned in the patch metadata, Oracle automatically halts the process to prevent compatibility issues.
Typical error message:
Invoking prereq "checkConflictAgainstOHWithDetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
Invoking prereq "CheckMinimumOPatchVersion"
UtilSession failed: Prerequisite check "CheckMinimumOPatchVersion" failed.
Log file location: /u01/app/oracle/product/19.0.0.0/OPatch/opatch2025-10-16_11-12-34AM.log
OPatch version check failed. Minimum required version is 12.2.0.1.39.This error simply means your OPatch version is too old for the patch you’re attempting to apply.
⚠️ Root Cause
The root cause is version incompatibility.
Each Oracle patch comes with a minimum OPatch requirement, defined by Oracle Support.
If your Oracle Home has an older OPatch release, it cannot interpret the metadata of the newer patch bundle.
Example:
- Your current OPatch version:
12.2.0.1.17 - Minimum required version (from README):
12.2.0.1.47
Result → ❌ Prerequisite check “CheckMinimumOPatchVersion” failed.
Step-by-Step Solution
Let’s fix it properly.
Step 1: Check Your Current OPatch Version
Login to your Oracle server and execute:
$ORACLE_HOME/OPatch/opatch version
Example output:
OPatch Version: 12.2.0.1.17
OPatch succeeded.If the version is lower than the one mentioned in the patch’s README file, you must upgrade.
Step 2: Identify the Minimum Required Version
In your patch directory, locate and open the README.txt file.
Search for the line:
You must use the OPatch utility version 12.2.0.1.46 or later to apply this patch.
This tells you the version needed to apply this patch safely.
Step 3: Download the Latest OPatch from My Oracle Support (MOS)
- Go to Link : My Oracle Support (MOS)
Choose your Oracle Database version and platform.
Download the latest available version (e.g., p6880880_190000_Linux-x86-64.zip for Oracle 19c).
💡 Tip: Always match your platform — Linux, Windows, Solaris, or AIX — and ensure it corresponds to your ORACLE_HOME version.
Step 4: Backup and Replace the Old OPatch
Before updating, take a backup of your existing OPatch directory:
cd $ORACLE_HOME
mv OPatch OPatch_old
Now, unzip the downloaded OPatch utility into your ORACLE_HOME:
unzip /u01/soft/p6880880_190000_Linux-x86-64.zip -d $ORACLE_HOME/
Verify the new version:
$ORACLE_HOME/OPatch/opatch version
Expected output:
OPatch Version: 12.2.0.1.47
OPatch succeeded.
Step 5: Retry the Patch Application
Now that OPatch is updated, retry your patch command:
cd /u01/patches/37960098
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
This time, the prerequisite check should pass successfully:
Oracle Interim Patch Installer version 12.2.0.1.47
Copyright (c) 2025, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : /u01/app/oracle/product/19.0.0/dbhome_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/19.0.0/dbhome_1/oraInst.loc
OPatch version : 12.2.0.1.47
OUI version : 12.2.0.7.0
Log file location : /u01/app/oracle/product/19.0.0/dbhome_1/cfgtoollogs/opatch/opatch2025-10-15_18-15-18PM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
Prereq "checkConflictAgainstOHWithDetail" passed.
OPatch succeeded.
✅ You’re done! Your patching session will continue normally.
Additional Verification Steps
Check OPatch Inventory
After applying patches, validate the inventory to confirm the update:
$ORACLE_HOME/OPatch/opatch lsinventory
This ensures your environment is clean, consistent, and up to date.
Pro Tips for DBAs
- Always keep your OPatch updated — Oracle releases new versions regularly.
- Maintain a central repository of the latest OPatch for all environments (PROD, DR, TEST).
- Update OPatch before applying RU/CPU patches or any one-offs.
- Monitor MOS notes for known issues related to OPatch version mismatches.
- Validate file ownership and permissions —
oracle:oinstallmust own OPatch files.
Conclusion
The “UtilSession failed: Prerequisite check ‘CheckMinimumOPatchVersion’ failed” error often occurs when the OPatch utility version in your Oracle home is outdated. By simply verifying the current OPatch version and updating it to the latest compatible release, you can quickly resolve the issue and proceed with your patch installation successfully.
Keeping OPatch up to date is not just about fixing errors—it ensures that your environment remains compliant with Oracle’s patching framework and supports the latest RU and OJVM updates.
For DBAs planning a full database patch cycle, you can refer to our step-by-step article on performing a complete patch upgrade for Oracle 19c here:
👉 Oracle 19c Release Update 19.28 RHEL Guide
Following both the OPatch update and full release update process will help ensure your Oracle environment runs securely, efficiently, and error-free.
