Are you interested in the news and updates in opatch 12.2.0.1.45 (Jan 2025)? This is the opatch version being released on January 21, 2025 together with the January Release Updates (RUs) and other patch bundles.
What’s new in opatch 12.2.0.1.45 (Jan 2025)?
When I refer to opatch, I mean the opatch tool for the Oracle Database installations. You can always download it via OPatch Download: Patch 6880880. You will use this opatch for Oracle Database 12.1.0.2, 12.2.0.1, 18c, 19c and 21c. In addition, the same changes and updates are present in opatch 11.2.0.3.49 for Oracle Database 11.2.0.4.
This is the list of new features and additions you will find:
- Delete inactive patches by default for 23c\21c
- Performance enhancements in conflict engine area
- Fallback mechanism if fuser fails to detect active files
- New option in util to query RU version
- OPatchAuto:
- New option to skip running rrpatch
- New option to enable rrpatch in same session
Opatch has also the JRE for January 2025 and several bug fixes as well.
I would consider the most interesting update the fix for Enhancement 37204249 (DELETEINACTIVE PATCHES TO BE CALLED BY DEFAULT FOR 23AI DURING PATCHING) which cleans up now automatically in Oracle Database 23ai. Different from the bug but mentioned in the feature description already, this will happen to 21c homes as well. Christian Pfundtner has confirmed it since one of his colleagues came across it as well.
For a full feature description of opatch util deleteinactivepatches read on here:
Certainly, our recommendation and best practice stays:
Always update to the most recent opatch version before you patch.
Further Links and Information
- OPatch Download: Patch 6880880
- Cleaning up older patch artifacts – and speeding up patching performance
–Mike
Hi Mike,
do you know if this will be backported to support 19c? We’re currently at the 23th RU (26-3) and accumulated a lot of inactive patches.
Best,
Andreas
Hi Andreas,
this is supposed to be all in opatch for 19c as well. It is essentially the same tool.
Cheers,
Mike
Heya Mike
The conflict checker tool seems to have an issue with opatch lsinfo output, it keeps saying there is an invalid section.
If the software owner is not allowed to execute fuser, then opatch will not apply any patches because the prerequisites are not met. This is a major change in default behaviour, is there a flag one can set to fallback to the earlier versions?
I was looking to get an earlier version of opatch, but it looks like it isn’t readily available. Did I miss this somewhere?
Many thanks and regards.
Regards
Hi Carmen,
can you drop me an email, please?
Thanks,
Mike
OPatch 12.2.0.1.45 seams to be wrong on solaris (java.text.ParseException: Unparseable date: “2020.Apr.21 14:47:51 MEST”) 🙁 ….
is it possible to download the older version 12.2.0.1.44 ? (is supported for the January PSU and mybe will work fine :))
Nope, as far as I know the previous version get removed.
Please check with Oracle Support and see whether they can give you access to the previous one, or whether the issue you encountered is fixed already.
Cheers,
Mike
Hello Mike, is it okay to implement on Linux86 64bit. Thanks.
Hi Mike,
I cannot easily find any info on the jre version included in OPatch unless I explode it and check the java version. Can you help me point to a documentation where Oracle documented the jre version in each OPatch please.
Thank you.
Hi Marie,
I can do just the same. But as a rule of thumb, it is always the 3 month old version. For instance, opatch will deliver a new opatch version tonight, and the jre is the one from January 2025.
Cheers,
Mike
I see. Thank you so much, Mike!