After a short delay, the latest Release Updates are out for Linux.
Are you wondering about the remaining platforms? Or do you want to refresh your knowledge of database patching? We recently aired two webinars that you’ll find interesting.
| Webinar | |||
|---|---|---|---|
| Database Patching for DBAs – Patch smarter, not harder | Slides | Q&A | Recording |
| Patch smarter, not harder – MS Windows Special Edition | Slides | Q&A | Recording |
If you’re still downloading patches from My Oracle Support, you must watch these webinars. Save yourself a lot of time and grab all the patches you need in one command.
If you have RAC databases and the applications are a little slow to drain or you just want more control, check out the DBA-controlled draining we recently introduced.
My Highlights
Here are a few of the topics that I find especially useful:
Next Webinar
It didn’t take long after the last one before we settled on the next webinar:
Statistics and Migrations – Well-Kept Secrets Revealed
Interested? Take a look at the abstract and sign up.
Happy patching!
Databases Are Fun 
Hi Daniel ,
thanks for the great video #27 on patching .
I’m trying to download the latest GI and patches for release 26 .
This is my config file:
cat download.cfg
global.global_log_dir=/…/auto/log_d2
global.keystore=/…/auto/keystore
global.folder=/…/auto/patch-repo
download2.target_version=26
download2.patch=RECOMMENDED,JDK,MRP
download2.platform=LINUX.X64
java -jar autoupgrade.jar -config download.cfg -patch -mode download
AutoUpgrade Patching 26.3.260401 launched with default internal options
Processing config file …
Loading AutoUpgrade Patching keystore
Enter wallet password:
AutoUpgrade Patching keystore is loaded
Connected to MOS – Searching for specified patches
There were conditions found preventing AutoUpgrade Patching from successfully running *Downloading files
Cannot find the DPBP patch
Is it problem with MOS or my config file ?
Best regards
Januš
LikeLike
OK, if I’m specific ( instead using keyword RECOMMENDED ) download works :
…
#download2.patch=RECOMMENDED,JDK,MRP
download2.patch=RU, OPATCH, AU, JDK, MRP
…
java -jar autoupgrade.jar -config download.cfg -patch -mode download
…
MRP download will be ignored as Oracle has not created it for 23.26.2 RU version for the job with prefix download2
——————————————————–
Downloading files to /…/auto/patch-repo
——————————————————–
DATABASE RELEASE UPDATE 23.26.2.0.0 File: p39099680_230000_Linux-x86-64.zip – VALIDATED
OPatch 12.2.0.1.51 for DB 23.0.0.0.0 (Apr 2026) File: p6880880_230000_Linux-x86-64.zip – VALIDATED
JDK BUNDLE PATCH 23.26.0.0.0 File: p38378853_230000_Linux-x86-64.zip – VALIDATED
autoupgrade.jar 26.3 (April 2026) File: autoupgrade.jar – VALIDATED
——————————————————–
Best regards
Januš
LikeLike
You found the workaround already. AutoUpgrade is “too” sensitive if the Data Pump bundle patch is not ready when you want to download. Typically, we have the Data Pump bundle patch ready when we release the Release Updates, but this time was a little special.
We’ve decided to make a change to AutoUpgrade, so it will display a warning if the Data Pump bundle patch is not ready. Instead of erroring out like today.
Regards,
Daniel
LikeLike
Thanks for confirming.
Is there any documentation how to handle error situations when upgrading using autoupgrade -mode deploy ? I had recently problem ( it is already solved ) and I was not sure what exactly shall I do ?
+—-+——-+———+———+——+———-+——-+——–+
|Job#|DB_NAME| STAGE|OPERATION|STATUS|START_TIME|UPDATED| MESSAGE|
+—-+——-+———+———+——+———-+——-+——–+
| 100| CLMMAB|DBUPGRADE| STOPPED| ERROR| 09:36:59| |UPG-1401|
+—-+——-+———+———+——+———-+——-+——–+
Is there any good place to discuss such runtime problems when using autougrade ? ( I created SR for that but I resolved the problem myself in the end )
regards
Januš
LikeLike
Hi Daniel, these are very good slides, thank you! I have some questions on the COMPATIBLE setting.
We upgraded to RU 23.26.1.0.0 in production a couple of months ago, have no issues so far and do not plan to roll back. Our COMPATIBLE setting is still on 23.6.0 there.
We want to use new features in the latest RU, and I tried to set compatible to ‘23.26.1’ in our dev and test environments. It seems to work: alter system set compatible=’23.26.1′ scope=spfile sid=’*’;srvctl stop database -d CDBDEV_ad1_frasrvctl start database -d CDBDEV_ad1_fraBut I could not find a list of supported values for the parameter in the docs.
Is the RU version always a valid value to use in COMPATIBLE?
Could I add
ALTER DATABASE SET DOWNGRADE COMPATIBILIY TO '23.26.1';before the alter system command to avoid the cluster restart in Prod? I read about it only after I had already done the change in test environments, so I can’t test it there anymore.BR Göran
LikeLike
Hi,
Thanks for the feedback. Much appreciated.
Most new features DO NOT require that you change the compatible setting. Far from actually and to my knowledge there are no new features that won’t work with the default COMPATIBLE setting of 23.6.0.
However, if I’m wrong and you truly need to raise it, be sure to keep it at the same setting in all your CDBs on the same release (as discussed in the webinar).
You can set COMPATIBLE to any numeric value that you want (as long as it goes upwards). There’s no pre-defined list of values that you must choose from.
The ALTER DATABASE command is new and added in 23ai/26ai and only allows minor changes to the COMPATIBLE parameter. It’s to be used within a release if you need to raise it to allow a new feature. But so far, I’m not aware of any such features. You can also keep using the ALTER SYSTEM command that you know already.
Regards,
Daniel
LikeLiked by 1 person