Introduction
Patch 19.30 is now available for Oracle Database Appliance series. Let’s find out what’s new and how to apply this patch.
What’s new?
The real new feature is the possibility to rollback a server component patch done by an odacli update-servercomponents. Until now, in the rare cases you would need to do a rollback, you could only rely on ODABR. And guess what? This new rollback feature makes use of ODABR. So keep doing manual ODABR snapshots prior attempting to patch your ODA.
Regarding the odacli update-dcscomponents, it now has a dedicated job engine you can query with a new command odacli describe-admin-job to see the progress. This is useful because this job now lasts longer. It’s always good to know the involved steps and their status of such a process.
This version is 19.30, meaning that bare metal GI stack is still using 19c binaries. 23/26ai databases are still limited to DB Systems, meaning that bare metal databases are limited to 19c.
As you can guess, this patch is mainly a bundle patch for security and bug fixes. A bigger update is expected later this year.
Which ODA is compatible with this 19.30 release?
The latest ODAs X11-HA, X11-L and X11-S are supported, as well as X10, X9-2 and X8-2 series. X7-2 series and older ones are not supported anymore. If you own one from these older generations, you will not be able to patch it anymore. If you’re using X8-2 ODAs, available from late 2019 to mid 2022, the last patch is planned for August 2027.
I still recommend keeping your ODA 7 years, not less, not more. This blog post is still relevant today: https://www.dbi-services.com/blog/why-you-should-consider-keeping-your-oda-more-than-5-years/.
Is this patch a cumulative one?
The rule is now well established: you can apply a patch on top of the four previous ones. 19.30 can then be applied on top of 19.29, 19.28, 19.27 and 19.26. Patching once a year will prevent having to apply 2 or more patches, meaning a longer downtime.
What’s new since 19.29 is the additional monthly system patch. This is a special patch for system only, for those who cannot wait for the global patch to be released. First one was 19.29.0.1.0. 19.30 can be applied on top of it.
In my lab at dbi services, I will use an ODA X8-2M running 19.29 with one DB home, one database and one DB System. The DB System is already running a 26ai database. The given patching procedure should be the same if you come from 19.26 or later.
Is there also a patch for my databases?
Only databases version 19c are supported on bare metal. Patch for 19c is obviously 19.30. For a 26ai database running inside a DB System, you will patch from 23.26.0.0 to 23.26.1.0. This is how the new version numbering works now.
Download the patch and clone files
These files are mandatory:
38776074 => the patch itself
30403673 => the GI clone needed for deploying newer 19c GI version
30403662 => the DB clone for deploying newer version of 19c
These files are optional:
30403643 => ISO file for reimaging, not needed for patching
36524660 => System image for deploying a new 26ai DB System
36524627 => the GI clone needed for deploying/patching to newer 26ai GI version
36524642 => the DB clone for deploying/patching to newer 26ai version
32451228 => The newer system image for 19c DB Systems
38776071 => The patch for 26ai DB Systems
Be sure to choose the very latest 19.30 when downloading some files, patch number is the same for older versions of GI clones, DB clones and ISO files.
Prepare the patching
Before starting, please check these prerequisites:
- filesystems /, /opt, /u01 and /root have at least 20% of available free space
- unzip the downloaded patch files
- additional manually installed rpms must be removed
- revert profile scripts to default’s one (for grid and oracle users)
- make sure you’ve planned a sufficient downtime (4+ hours depending on the number of databases and DB Systems)
- do a sanity reboot before patching to kill zombie processes
- use ODABR to make snapshots of the important filesystems prior patching: this tool is now included in the software distribution
df -h / /u01 /opt/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolRoot 30G 13G 16G 46% /
/dev/mapper/VolGroupSys-LogVolU01 59G 23G 34G 40% /u01
/dev/mapper/VolGroupSys-LogVolOpt 69G 34G 33G 52% /opt
cd /opt/dbi
for a in `ls p*1930*.zip` ; do unzip -o $a ; rm -f $a ; done
reboot
...
pvs
PV VG Fmt Attr PSize PFree
/dev/md126p3 VolGroupSys lvm2 a-- 446.09g 260.09g
/opt/odabr/odabr backup --snap
INFO: 2026-02-26 11:29:54: Please check the logfile '/opt/odabr/out/log/odabr_24079.log' for more details
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
odabr - ODA node Backup Restore - Version: 2.0.2-05
Copyright 2013, 2025, Oracle and/or its affiliates.
--------------------------------------------------------
RACPack, Cloud Innovation and Solution Engineering Team
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
INFO: 2026-02-26 11:29:54: Checking superuser
INFO: 2026-02-26 11:29:54: Checking Bare Metal
INFO: 2026-02-26 11:29:54: Removing existing LVM snapshots
WARNING: 2026-02-26 11:29:54: LVM snapshot for 'opt' does not exist
WARNING: 2026-02-26 11:29:54: LVM snapshot for 'u01' does not exist
WARNING: 2026-02-26 11:29:54: LVM snapshot for 'root' does not exist
INFO: 2026-02-26 11:29:54: Checking current OS version...
INFO: 2026-02-26 11:29:54: Checking LVM restore backgroud process
INFO: 2026-02-26 11:29:54: Checking LVM size
INFO: 2026-02-26 11:29:54: Boot device backup
INFO: 2026-02-26 11:29:54: Getting EFI device
INFO: 2026-02-26 11:29:54: ...step1 - unmounting EFI
INFO: 2026-02-26 11:29:54: ...step2 - making efi device backup
SUCCESS: 2026-02-26 11:29:57: ...EFI device backup saved as '/opt/odabr/out/hbi/efi.img'
INFO: 2026-02-26 11:29:57: ...step3 - checking EFI device backup
INFO: 2026-02-26 11:29:57: Getting boot device
INFO: 2026-02-26 11:29:57: ...step1 - making boot device backup using tar
SUCCESS: 2026-02-26 11:30:03: ...boot content saved as '/opt/odabr/out/hbi/boot.tar.gz'
INFO: 2026-02-26 11:30:03: ...step2 - unmounting boot
INFO: 2026-02-26 11:30:04: ...step3 - making boot device backup using dd
SUCCESS: 2026-02-26 11:30:09: ...boot device backup saved as '/opt/odabr/out/hbi/boot.img'
INFO: 2026-02-26 11:30:09: ...step4 - mounting boot
INFO: 2026-02-26 11:30:09: ...step5 - mounting EFI
INFO: 2026-02-26 11:30:10: ...step6 - checking boot device backup
INFO: 2026-02-26 11:30:10: Making OCR physical backup
INFO: 2026-02-26 11:30:11: ...ocr backup saved as '/opt/odabr/out/hbi/ocrbackup_24079.bck'
SUCCESS: 2026-02-26 11:30:11: OCR physical backup created successfully
INFO: 2026-02-26 11:30:11: OCR export backup
INFO: 2026-02-26 11:30:12: ...ocr export saved as '/opt/odabr/out/hbi/ocrexport_24079.bck'
SUCCESS: 2026-02-26 11:30:12: OCR export backup created successfully
INFO: 2026-02-26 11:30:12: Saving clusterware patch level as '/opt/odabr/out/hbi/clusterware_patch_level.info'
SUCCESS: 2026-02-26 11:30:12: Clusterware patch level saved successfully
INFO: 2026-02-26 11:30:12: Making LVM snapshot backup
SUCCESS: 2026-02-26 11:30:13: ...snapshot backup for 'opt' created successfully
SUCCESS: 2026-02-26 11:30:14: ...snapshot backup for 'u01' created successfully
SUCCESS: 2026-02-26 11:30:14: ...snapshot backup for 'root' created successfully
SUCCESS: 2026-02-26 11:30:14: LVM snapshots backup done successfullyVersion precheck
Start to check the current version of the various components:
odacli describe-component
System Version
--------------
19.29.0.0.0
System Node Name
----------------
dbioda01
Local System Version
--------------------
19.29.0.0.0
Component Installed Version Available Version
---------------------------------------- -------------------- --------------------
OAK 19.29.0.0.0 up-to-date
GI 19.29.0.0.251021 up-to-date
DB {
OraDB19000_home9 19.29.0.0.251021 up-to-date
[CPROD19]
}
DCSCONTROLLER 19.29.0.0.0 up-to-date
DCSCLI 19.29.0.0.0 up-to-date
DCSAGENT 19.29.0.0.0 up-to-date
DCSADMIN 19.29.0.0.0 up-to-date
OS 8.10 up-to-date
ILOM 5.1.5.22.r165351 up-to-date
BIOS 52160100 up-to-date
LOCAL CONTROLLER FIRMWARE {
[c4] 8000D9AB up-to-date
}
SHARED CONTROLLER FIRMWARE {
[c0, c1] VDV1RL06 up-to-date
}
LOCAL DISK FIRMWARE {
[c2d0, c2d1] XC311132 up-to-date
}
HMP 2.4.10.1.600 up-to-dateList the DB homes, databases, DB Systems and VMs:
odacli list-dbhomes
ID Name DB Version DB Edition Home Location Status
---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------
57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb OraDB19000_home9 19.29.0.0.251021 EE /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9 CONFIGURED
odacli list-databases
ID DB Name DB Type DB Version CDB Class Edition Shape Storage Status DB Home ID
---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------
976a80f2-4653-469f-8cd4-ddc1a21aff51 CPROD19 SI 19.29.0.0.251021 true OLTP EE odb8 ASM CONFIGURED 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
odacli list-dbsystems
Name Shape GI version DB info Status Created Updated
-------------------- ---------- ------------------ ------------------------------ ---------------------- ------------------------ ------------------------
dbs-04-tst dbs2 23.26.0.0.0 23.26(CONFIGURED=1) CONFIGURED 2026-01-12 10:14:46 CET 2026-01-12 10:45:45 CET
odacli list-vms
No data found for resource VM.Update the DCS components
Updating DCS components is the first step, after registering the patch file:
odacli update-repository -f /opt/dbi/oda-sm-19.30.0.0.0-260210-server.zip
sleep 30 ; odacli describe-job -i e3ba068f-01db-45c3-949d-b79f43c8d6b7
Job details
----------------------------------------------------------------
ID: e3ba068f-01db-45c3-949d-b79f43c8d6b7
Description: Repository Update
Status: Success
Created: February 26, 2026 11:30:48 CET
Message: /opt/dbi/oda-sm-19.30.0.0.0-260210-server.zip
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Unzip bundle February 26, 2026 11:30:49 CET February 26, 2026 11:31:10 CET Success
odacli describe-component
System Version
--------------
19.29.0.0.0
System Node Name
----------------
dbioda01
Local System Version
--------------------
19.29.0.0.0
Component Installed Version Available Version
---------------------------------------- -------------------- --------------------
OAK 19.29.0.0.0 19.30.0.0.0
GI 19.29.0.0.251021 19.30.0.0.260120
DB {
OraDB19000_home9 19.29.0.0.251021 19.30.0.0.260120
[CPROD19]
}
DCSCONTROLLER 19.29.0.0.0 19.30.0.0.0
DCSCLI 19.29.0.0.0 19.30.0.0.0
DCSAGENT 19.29.0.0.0 19.30.0.0.0
DCSADMIN 19.29.0.0.0 19.30.0.0.0
OS 8.10 up-to-date
ILOM 5.1.5.22.r165351 5.1.5.29.r167438
BIOS 52160100 52170100
LOCAL CONTROLLER FIRMWARE {
[c4] 8000D9AB up-to-date
}
SHARED CONTROLLER FIRMWARE {
[c0, c1] VDV1RL06 up-to-date
}
LOCAL DISK FIRMWARE {
[c2d0, c2d1] XC311132 up-to-date
}
HMP 2.4.10.1.600 up-to-dateLet’s update the DCS components to 19.30:
odacli update-dcsadmin -v 19.30.0.0.0
sleep 90 ; odacli describe-job -i "c3c278ad-89e6-4c7d-b9fd-27833a187e43"
Job details
----------------------------------------------------------------
ID: c3c278ad-89e6-4c7d-b9fd-27833a187e43
Description: DcsAdmin patching to 19.30.0.0.0
Status: Success
Created: February 26, 2026 11:32:11 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Dcs-admin upgrade February 26, 2026 11:32:11 CET February 26, 2026 11:32:21 CET Success
Ping DCS Admin February 26, 2026 11:32:21 CET February 26, 2026 11:33:29 CET Success
sleep 30 ; odacli update-dcscomponents -v 19.30.0.0.0
sleep 300 ; odacli describe-admin-job -i 2aeda3f3-df4d-4f7c-a0ce-b57eeab0448b
Job details
----------------------------------------------------------------
ID: 2aeda3f3-df4d-4f7c-a0ce-b57eeab0448b
Description: Update-dcscomponents to 19.30.0.0.0
Status: Success
Created: February 26, 2026 11:34:51 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Pre-checks for update DCS components February 26, 2026 11:34:57 CET February 26, 2026 11:35:05 CET Success
Update DCS components February 26, 2026 11:35:05 CET February 26, 2026 11:35:05 CET Success
Stop DCS-Agent February 26, 2026 11:35:05 CET February 26, 2026 11:35:05 CET Success
Update MySql February 26, 2026 11:35:05 CET February 26, 2026 11:35:42 CET Success
Apply metadata schema changes February 26, 2026 11:35:42 CET February 26, 2026 11:35:42 CET Success
Modify MySQL Metadata February 26, 2026 11:35:42 CET February 26, 2026 11:35:43 CET Success
Update DCS-Agent February 26, 2026 11:35:43 CET February 26, 2026 11:35:57 CET Success
Update DCS-Cli February 26, 2026 11:35:57 CET February 26, 2026 11:35:59 CET Success
Update DCS-Controller February 26, 2026 11:35:59 CET February 26, 2026 11:36:22 CET Success
Update AHF RPM February 26, 2026 11:36:22 CET February 26, 2026 11:38:41 CET Success
Reset Keystore password February 26, 2026 11:38:41 CET February 26, 2026 11:39:02 CET Success
Update HAMI February 26, 2026 11:39:02 CET February 26, 2026 11:39:54 CET Success
Remove old library files February 26, 2026 11:39:54 CET February 26, 2026 11:39:54 CET Success
Post DCS update actions February 26, 2026 11:39:54 CET February 26, 2026 11:39:54 CET SuccessSystem patching
Let’s do the prepatching of the system:
odacli create-prepatchreport -sc -v 19.30.0.0.0
sleep 180 ; odacli describe-prepatchreport -i c06cd4d0-d30c-4063-a3c1-3b86db6625b0
Prepatch Report
------------------------------------------------------------------------
Job ID: c06cd4d0-d30c-4063-a3c1-3b86db6625b0
Description: Patch pre-checks for [OS, ILOM, ORACHKSERVER, SERVER] to 19.30.0.0.0
Status: SUCCESS
Created: February 26, 2026 11:40:17 AM CET
Result: All pre-checks succeeded
Node Name
---------------
dbioda01
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.30.0.0.0.
Is patch location available Success Patch location is available.
Verify All OS patches Success No dependencies found for RPMs being
removed, updated and installed. Check
/opt/oracle/dcs/log/jobfiles/
dnfdryrunout_2026-02-26_11-40-
34.0688_236.log file for more details
Validate command execution Success Validated command execution
__ILOM__
Validate ILOM server reachable Success Successfully connected with ILOM
server using public IP and USB
interconnect
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 19.30.0.0.0.
Is patch location available Success Patch location is available.
Checking Ilom patch Version Success Successfully verified the versions
Patch location validation Success Successfully validated location
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution
__SERVER__
Validate local patching Success Successfully validated server local
patching
Validate all KVM ACFS Success All KVM ACFS resources are running
resources are running
Validate DB System VM states Success All DB System VMs states are expected
Validate DB System AFD state Success All DB Systems are on required
versions
Validate command execution Success Validated command execution
OK let’s apply the system patch:
odacli update-servercomponents -v 19.30.0.0.0
...
The server will reboot at the end of the patching (it took 40 minutes on my X8-2M). Let’s then check the job:
odacli describe-job -i "8d5b4b63-3a92-46e4-b466-9fd46cdf8b3a"
Job details
----------------------------------------------------------------
ID: 8d5b4b63-3a92-46e4-b466-9fd46cdf8b3a
Description: Server Patching to 19.30.0.0.0
Status: Success
Created: February 26, 2026 11:42:47 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Validating GI user metadata February 26, 2026 11:42:53 CET February 26, 2026 11:42:54 CET Success
Modify BM udev rules February 26, 2026 11:42:54 CET February 26, 2026 11:43:05 CET Success
Validate ILOM server reachable February 26, 2026 11:42:54 CET February 26, 2026 11:42:54 CET Success
Stop oakd February 26, 2026 11:43:05 CET February 26, 2026 11:43:08 CET Success
Creating local repository February 26, 2026 11:43:09 CET February 26, 2026 11:43:11 CET Success
OSPatchBaseRepo
Updating versionlock plugin February 26, 2026 11:43:11 CET February 26, 2026 11:43:14 CET Success
Applying OS Patches February 26, 2026 11:43:14 CET February 26, 2026 11:50:26 CET Success
Applying HMP Patches February 26, 2026 11:50:27 CET February 26, 2026 11:50:30 CET Success
Creating local repository HMPPatchRepo February 26, 2026 11:50:27 CET February 26, 2026 11:50:27 CET Success
Oda-hw-mgmt upgrade February 26, 2026 11:50:31 CET February 26, 2026 11:51:02 CET Success
Patch location validation February 26, 2026 11:50:31 CET February 26, 2026 11:50:31 CET Success
Setting SELinux mode February 26, 2026 11:50:31 CET February 26, 2026 11:50:31 CET Success
Installing SQLcl software February 26, 2026 11:51:02 CET February 26, 2026 11:51:06 CET Success
OSS Patching February 26, 2026 11:51:02 CET February 26, 2026 11:51:02 CET Success
Applying Firmware local Disk Patches February 26, 2026 11:51:06 CET February 26, 2026 11:51:10 CET Success
Applying Firmware local Controller Patch February 26, 2026 11:51:10 CET February 26, 2026 11:51:14 CET Success
Applying Firmware shared Controller February 26, 2026 11:51:15 CET February 26, 2026 11:51:19 CET Success
Patch
Checking Ilom patch Version February 26, 2026 11:51:19 CET February 26, 2026 11:51:19 CET Success
Patch location validation February 26, 2026 11:51:19 CET February 26, 2026 11:51:19 CET Success
Disabling IPMI v2 February 26, 2026 11:51:20 CET February 26, 2026 11:51:21 CET Success
Save password in Wallet February 26, 2026 11:51:20 CET February 26, 2026 11:51:20 CET Success
Apply Ilom patch February 26, 2026 11:51:21 CET February 26, 2026 12:02:07 CET Success
Copying Flash Bios to Temp location February 26, 2026 12:02:07 CET February 26, 2026 12:02:07 CET Success
Start oakd February 26, 2026 12:02:08 CET February 26, 2026 12:02:24 CET Success
Add SYSNAME in Env February 26, 2026 12:02:25 CET February 26, 2026 12:02:25 CET Success
Cleanup JRE Home February 26, 2026 12:02:25 CET February 26, 2026 12:02:25 CET Success
Starting the clusterware February 26, 2026 12:02:25 CET February 26, 2026 12:03:59 CET Success
Update lvm.conf file February 26, 2026 12:04:00 CET February 26, 2026 12:04:00 CET Success
Generating and saving BOM February 26, 2026 12:04:01 CET February 26, 2026 12:04:34 CET Success
Update System full patch version February 26, 2026 12:04:01 CET February 26, 2026 12:04:01 CET Success
Update System rebootless patch version February 26, 2026 12:04:01 CET February 26, 2026 12:04:01 CET Success
PreRebootNode Actions February 26, 2026 12:04:34 CET February 26, 2026 12:07:10 CET Success
Reboot Node February 26, 2026 12:07:10 CET February 26, 2026 12:18:17 CET SuccessGI patching
Let’s register the patch file, and do the precheck for GI:
odacli update-repository -f /opt/dbi/odacli-dcs-19.30.0.0.0-260210-GI-19.30.0.0.zip
sleep 70 ; odacli describe-job -i "5699a201-8f50-499c-98a8-18b2e79ca356"
Job details
----------------------------------------------------------------
ID: 5699a201-8f50-499c-98a8-18b2e79ca356
Description: Repository Update
Status: Success
Created: February 26, 2026 12:32:04 CET
Message: /opt/dbi/odacli-dcs-19.30.0.0.0-260210-GI-19.30.0.0.zip
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Unzip bundle February 26, 2026 12:32:05 CET February 26, 2026 12:33:14 CET Success
odacli create-prepatchreport -gi -v 19.30.0.0.0
sleep 180 ; odacli describe-prepatchreport -i ac157412-cfe2-4b2e-ae04-e7082cd4014f
Prepatch Report
------------------------------------------------------------------------
Job ID: ac157412-cfe2-4b2e-ae04-e7082cd4014f
Description: Patch pre-checks for [RHPGI, GI] to 19.30.0.0.0
Status: SUCCESS
Created: February 26, 2026 12:34:00 PM CET
Result: All pre-checks succeeded
Node Name
---------------
dbioda01
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__RHPGI__
Validate available space Success Validated free space under /u01
Evaluate GI patching Success Successfully validated GI patching
Validate command execution Success Validated command execution
__GI__
Validate GI metadata Success Successfully validated GI metadata
Validate supported GI versions Success Successfully validated minimum version
Is clusterware running Success Clusterware is running
Validate patching tag Success Validated patching tag: 19.30.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate ASM is online Success ASM is online
Validate kernel log level Success Successfully validated the OS log
level
Validate Central Inventory Success oraInventory validation passed
Validate patching locks Success Validated patching locks
Validate clones location exist Success Validated clones location
Validate DB start dependencies Success DBs START dependency check passed
Validate DB stop dependencies Success DBs STOP dependency check passed
Validate space for clones Success Clones volume is already created
volume
Validate command execution Success Validated command executionLet’s apply the GI update now:
odacli update-gihome -v 19.30.0.0.0
sleep 500 ; odacli describe-job -i "857bb637-82ec-4de9-a820-5ab9b895e9f8"
Job details
----------------------------------------------------------------
ID: 857bb637-82ec-4de9-a820-5ab9b895e9f8
Description: Patch GI with RHP to 19.30.0.0.0
Status: Success
Created: February 26, 2026 12:38:29 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Patch GI with RHP to 19.30.0.0.0 February 26, 2026 12:38:44 CET February 26, 2026 12:46:00 CET Success
Registering image February 26, 2026 12:38:45 CET February 26, 2026 12:38:45 CET Success
Registering working copy February 26, 2026 12:38:45 CET February 26, 2026 12:38:46 CET Success
Starting the clusterware February 26, 2026 12:38:45 CET February 26, 2026 12:38:45 CET Success
Creating GI home directories February 26, 2026 12:38:46 CET February 26, 2026 12:38:46 CET Success
Extract GI clone February 26, 2026 12:38:46 CET February 26, 2026 12:38:46 CET Success
Provisioning Software Only GI with RHP February 26, 2026 12:38:46 CET February 26, 2026 12:38:46 CET Success
Registering image February 26, 2026 12:38:46 CET February 26, 2026 12:38:46 CET Success
Patch GI with RHP February 26, 2026 12:39:20 CET February 26, 2026 12:45:25 CET Success
Set CRS ping target February 26, 2026 12:45:25 CET February 26, 2026 12:45:25 CET Success
Updating .bashrc February 26, 2026 12:45:25 CET February 26, 2026 12:45:26 CET Success
Updating GI home metadata February 26, 2026 12:45:26 CET February 26, 2026 12:45:26 CET Success
Updating GI home version February 26, 2026 12:45:26 CET February 26, 2026 12:45:31 CET Success
Updating All DBHome version February 26, 2026 12:45:31 CET February 26, 2026 12:45:36 CET Success
Starting the clusterware February 26, 2026 12:45:56 CET February 26, 2026 12:45:56 CET Success
Validate ACFS resources are running February 26, 2026 12:45:56 CET February 26, 2026 12:45:57 CET Success
Validate GI availability February 26, 2026 12:45:56 CET February 26, 2026 12:45:56 CET Success
Validate DB System VMs states February 26, 2026 12:45:57 CET February 26, 2026 12:45:58 CET Success
Patch CPU Pools distribution February 26, 2026 12:45:58 CET February 26, 2026 12:45:58 CET Success
Patch DB System domain config February 26, 2026 12:45:58 CET February 26, 2026 12:45:58 CET Success
Patch KVM CRS type February 26, 2026 12:45:58 CET February 26, 2026 12:45:58 CET Success
Patch VM vDisks CRS dependencies February 26, 2026 12:45:58 CET February 26, 2026 12:45:58 CET Success
Save custom VNetworks to storage February 26, 2026 12:45:58 CET February 26, 2026 12:45:59 CET Success
Add network filters to DB Systems February 26, 2026 12:45:59 CET February 26, 2026 12:46:00 CET Success
Create network filters February 26, 2026 12:45:59 CET February 26, 2026 12:45:59 CET Success
Patch DB Systems custom scale metadata February 26, 2026 12:46:00 CET February 26, 2026 12:46:00 CET Success
Patch DB Systems vDisks CRS dependencies February 26, 2026 12:46:00 CET February 26, 2026 12:46:00 CET SuccessNo reboot is needed for this patch.
Check the versions
odacli describe-component
System Version
--------------
19.30.0.0.0
System Node Name
----------------
dbioda01
Local System Version
--------------------
19.30.0.0.0
Component Installed Version Available Version
---------------------------------------- -------------------- --------------------
OAK 19.30.0.0.0 up-to-date
GI 19.30.0.0.260120 up-to-date
DB {
OraDB19000_home9 19.29.0.0.251021 19.30.0.0.260120
[CPROD19]
}
DCSCONTROLLER 19.30.0.0.0 up-to-date
DCSCLI 19.30.0.0.0 up-to-date
DCSAGENT 19.30.0.0.0 up-to-date
DCSADMIN 19.30.0.0.0 up-to-date
OS 8.10 up-to-date
ILOM 5.1.5.29.r167438 up-to-date
BIOS 52170100 up-to-date
LOCAL CONTROLLER FIRMWARE {
[c4] 8000D9AB up-to-date
}
SHARED CONTROLLER FIRMWARE {
[c0, c1] VDV1RL06 up-to-date
}
LOCAL DISK FIRMWARE {
[c2d0, c2d1] XC311132 up-to-date
}
HMP 2.4.10.1.600 up-to-datePatching the storage
Patching the storage is only needed if describe-component tells you that you’re not up-to-date. On my X8-2M, it wasn’t needed. If your ODA need the storage patch, it’s easy:
odacli update-storage -v 19.30.0.0.0
odacli describe-job -i ...
The server will reboot once done.
Patching the DB homes
It’s now time to patch the DB home and the database on my ODA. Let’s first unzip and register the patch file in the repository:
odacli update-repository -f /opt/dbi/odacli-dcs-19.29.0.0.0-251117-DB-19.29.0.0.zip
sleep 60; odacli describe-job -i 5690c811-9030-427e-82f1-caeeba236329
Job details
----------------------------------------------------------------
ID: 5690c811-9030-427e-82f1-caeeba236329
Description: Repository Update
Status: Success
Created: February 26, 2026 12:54:57 CET
Message: /opt/dbi/odacli-dcs-19.30.0.0.0-260210-DB-19.30.0.0.zip
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Unzip bundle February 26, 2026 12:54:57 CET February 26, 2026 12:55:50 CET Success
odacli list-dbhomes
ID Name DB Version DB Edition Home Location Status
---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------
57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb OraDB19000_home9 19.29.0.0.251021 EE /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9 CONFIGURED
Let’s check if the patch can be applied:
odacli create-prepatchreport -d -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb -v 19.30.0.0.0
sleep 600; odacli describe-prepatchreport -i 3522c79c-7444-44d7-9422-9d1daab161d2
Prepatch Report
------------------------------------------------------------------------
Job ID: 3522c79c-7444-44d7-9422-9d1daab161d2
Description: Patch pre-checks for [DB, RHPDB, ORACHKDB] to 19.30.0.0.0: DbHome is OraDB19000_home9
Status: FAILED
Created: February 26, 2026 12:56:59 PM CET
Result: One or more pre-checks failed for [ORACHK, DB]
Node Name
---------------
dbioda01
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__DB__
Validate data corruption in Failed DCS-10315 - Patch described in My
patching Oracle Support Note KB867473 must be
applied.
Validate DB Home ID Success Validated DB Home ID:
57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
Validate patching tag Success Validated patching tag: 19.30.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate minimum agent version Success Validated minimum agent version
Is GI upgraded Success Validated GI is upgraded
Validate available space for Success Validated free space required under
db /u01
Validate there is usable Success Successfully validated Oracle Base
space under oracle base usable space
Validate glogin.sql file Success Successfully verified glogin.sql
won't break patching
Validate dbHomesOnACFS Success User has configured disk group for
configured Database homes on ACFS
Validate Oracle base Success Successfully validated Oracle Base
Is DB clone available Success Successfully validated clone file
exists
Validate command execution Success Validated command execution
__RHPDB__
Evaluate DBHome patching with Success Successfully validated updating
RHP dbhome with RHP. and local patching
is possible
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Failed DCS-10702 - ORAchk validation failed:
.
Validate command execution Success Validated command execution
Verify the Fast Recovery Area Failed AHF-2929: FRA space management
(FRA) has reclaimable space problem file types are present
without an RMAN backup completion
within the last 7 daysI need to fix 2 problems. The first one is a bug that appeared in 19.29, let’s download and unzip the patch. Be careful because this patch is available for multiple versions: you will need the one for the version you’re currently using (19.29 in my case).
su - oracle
unzip -d /home/oracle /opt/dbi/p38854064_1929000DBRU_Linux-x86-64.zip
Archive: /opt/dbi/p38854064_1929000DBRU_Linux-x86-64.zip
creating: /home/oracle/38854064/
creating: /home/oracle/38854064/files/
creating: /home/oracle/38854064/files/lib/
creating: /home/oracle/38854064/files/lib/libserver19.a/
inflating: /home/oracle/38854064/files/lib/libserver19.a/kjfc.o
inflating: /home/oracle/38854064/README.txt
creating: /home/oracle/38854064/etc/
creating: /home/oracle/38854064/etc/config/
inflating: /home/oracle/38854064/etc/config/inventory.xml
inflating: /home/oracle/38854064/etc/config/actions.xml
inflating: /home/oracle/PatchSearch.xmlLet’s stop the database and apply this patch:
. oraenv <<< CPROD19
srvctl stop database -db CPROD19_S1
cd 38854064
$ORACLE_HOME/OPatch/opatch apply
Oracle Interim Patch Installer version 12.2.0.1.47
Copyright (c) 2026, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9
Central Inventory : /u01/app/oraInventory
from : /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9/oraInst.loc
OPatch version : 12.2.0.1.47
OUI version : 12.2.0.7.0
Log file location : /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9/cfgtoollogs/opatch/opatch2026-02-26_14-29-22PM_1.log
Verifying environment and performing prerequisite checks...
OPatch continues with these patches: 38854064
Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying interim patch '38854064' to OH '/u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9'
Patching component oracle.rdbms, 19.0.0.0.0...
Patch 38854064 successfully applied.
Log file location: /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9/cfgtoollogs/opatch/opatch2026-02-26_14-29-22PM_1.log
OPatch succeeded.
srvctl start database -db CPROD19_S1Second problem is because my database doesn’t have a proper backup strategy, let’s then remove the useless archivelogs:
rman target /
delete force noprompt archivelog all;
exit;
exit
Now let’s retry the precheck:
odacli create-prepatchreport -d -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb -v 19.30.0.0.0
odacli describe-prepatchreport -i b932011d-cfcf-402d-901e-5c7eac888f1f
Prepatch Report
------------------------------------------------------------------------
Job ID: b932011d-cfcf-402d-901e-5c7eac888f1f
Description: Patch pre-checks for [DB, RHPDB, ORACHKDB] to 19.30.0.0.0: DbHome is OraDB19000_home9
Status: FAILED
Created: February 26, 2026 3:01:14 PM CET
Result: One or more pre-checks failed for [ORACHK, DB]
Node Name
---------------
dbioda01
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__DB__
Validate data corruption in Failed DCS-10315 - Patch described in My
patching Oracle Support Note KB867473 must be
applied.
Validate DB Home ID Success Validated DB Home ID:
57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
Validate patching tag Success Validated patching tag: 19.30.0.0.0.
Is system provisioned Success Verified system is provisioned
Validate minimum agent version Success Validated minimum agent version
Is GI upgraded Success Validated GI is upgraded
Validate available space for Success Validated free space required under
db /u01
Validate there is usable Success Successfully validated Oracle Base
space under oracle base usable space
Validate glogin.sql file Success Successfully verified glogin.sql
won't break patching
Validate dbHomesOnACFS Success User has configured disk group for
configured Database homes on ACFS
Validate Oracle base Success Successfully validated Oracle Base
Is DB clone available Success Successfully validated clone file
exists
Validate command execution Success Validated command execution
__RHPDB__
Evaluate DBHome patching with Success Successfully validated updating
RHP dbhome with RHP. and local patching
is possible
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Failed DCS-10702 - ORAchk validation failed:
.
Validate command execution Success Validated command execution
Verify the Fast Recovery Area Failed AHF-2929: FRA space management
(FRA) has reclaimable space problem file types are present
without an RMAN backup completion
within the last 7 daysThis view doesn’t look updated, and the ODA documentation tells us that updating the DB home will need to be forced, let’s do that:
odacli update-dbhome -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb -v 19.30.0.0.0 --force
sleep 600; odacli describe-job -i "bd511055-7a35-45b4-b9f2-3a003c7ecb31"
Job details
----------------------------------------------------------------
ID: bd511055-7a35-45b4-b9f2-3a003c7ecb31
Description: DB Home Patching to 19.30.0.0.0: Home ID is 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
Status: Success
Created: February 26, 2026 15:08:46 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Creating wallet for DB Client February 26, 2026 15:09:33 CET February 26, 2026 15:09:33 CET Success
Patch databases by RHP - [CPROD19] February 26, 2026 15:09:33 CET February 26, 2026 15:16:44 CET Success
Updating database metadata February 26, 2026 15:16:44 CET February 26, 2026 15:16:44 CET Success
Upgrade pwfile to 12.2 February 26, 2026 15:16:44 CET February 26, 2026 15:16:47 CET Success
Set log_archive_dest for Database February 26, 2026 15:16:47 CET February 26, 2026 15:16:50 CET Success
Populate PDB metadata February 26, 2026 15:16:51 CET February 26, 2026 15:16:52 CET Success
Generating and saving BOM February 26, 2026 15:16:52 CET February 26, 2026 15:17:33 CET Success
TDE parameter update February 26, 2026 15:18:06 CET February 26, 2026 15:18:06 CET SuccessEverything is now OK.
Let’s check the DB homes and databases:
odacli list-dbhomes
ID Name DB Version DB Edition Home Location Status
---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------
d3b5fa9c-ad85-46c3-b11a-cd264978b653 OraDB19000_home10 19.30.0.0.260120 EE /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_10 CONFIGURED
57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb OraDB19000_home9 19.29.0.0.251021 EE /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9 CONFIGURED
odacli list-databases
ID DB Name DB Type DB Version CDB Class Edition Shape Storage Status DB Home ID
---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------
976a80f2-4653-469f-8cd4-ddc1a21aff51 CPROD19 SI 19.30.0.0.260120 true OLTP EE odb8 ASM CONFIGURED d3b5fa9c-ad85-46c3-b11a-cd264978b653Let’s now remove the old DB home. Note that DB homes are not protected by ODABR, I would recommend doing a backup before removing an old DB home:
tar czf /backup/`hostname -s`_dbhome_9.tgz /u01/app/odaorahome/oracle/product/19.0.0.0/dbhome_9
odacli delete-dbhome -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
sleep 40 ; odacli describe-job -i 4589a4d7-6986-4e16-818c-78d585f44443
Job details
----------------------------------------------------------------
ID: 4589a4d7-6986-4e16-818c-78d585f44443
Description: Database Home OraDB19000_home9 Deletion with ID 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
Status: Success
Created: February 26, 2026 15:24:44 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Setting up SSH equivalence February 26, 2026 15:24:44 CET February 26, 2026 15:24:44 CET Success
Setting up SSH equivalence February 26, 2026 15:24:44 CET February 26, 2026 15:24:44 CET Success
Validate DB Home February 26, 2026 15:24:44 CET February 26, 2026 15:24:44 CET Success
57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb
for deletion
Deleting DB Home by RHP February 26, 2026 15:24:45 CET February 26, 2026 15:25:21 CET SuccessCleanse the old patches
Let’s remove the previous patch from the repository:
odacli cleanup-patchrepo -comp all -v 19.29.0.0.0
odacli describe-job -i "a9e29414-8f12-4b55-a6d4-9ad82e9a4c74"
Job details
----------------------------------------------------------------
ID: a9e29414-8f12-4b55-a6d4-9ad82e9a4c74
Description: Cleanup patchrepos
Status: Success
Created: February 26, 2026 15:29:46 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Cleanup Repository February 26, 2026 15:29:46 CET February 26, 2026 15:29:47 CET Success
Cleanup old ASR rpm February 26, 2026 15:29:47 CET February 26, 2026 15:29:47 CET Success
Old GI binaries are still using space in /u01, it’s better to remove them manually:
du -hs /u01/app/19.*
14G /u01/app/19.29.0.0
14G /u01/app/19.30.0.0
rm -rf /u01/app/19.29.0.0I would recommend doing a reboot to check if everything run fine. But let’s first check the components:
odacli describe-component
System Version
--------------
19.30.0.0.0
System Node Name
----------------
dbioda01
Local System Version
--------------------
19.30.0.0.0
Component Installed Version Available Version
---------------------------------------- -------------------- --------------------
OAK 19.30.0.0.0 up-to-date
GI 19.30.0.0.260120 up-to-date
DB {
OraDB19000_home10 19.30.0.0.260120 up-to-date
[CPROD19]
}
DCSCONTROLLER 19.30.0.0.0 up-to-date
DCSCLI 19.30.0.0.0 up-to-date
DCSAGENT 19.30.0.0.0 up-to-date
DCSADMIN 19.30.0.0.0 up-to-date
OS 8.10 up-to-date
ILOM 5.1.5.29.r167438 up-to-date
BIOS 52170100 up-to-date
LOCAL CONTROLLER FIRMWARE {
[c4] 8000D9AB up-to-date
}
SHARED CONTROLLER FIRMWARE {
[c0, c1] VDV1RL06 up-to-date
}
LOCAL DISK FIRMWARE {
[c2d0, c2d1] XC311132 up-to-date
}
HMP 2.4.10.1.600 up-to-date
reboot
...
ps -ef | grep pmon
grid 8292 1 0 15:37 ? 00:00:00 asm_pmon_+ASM1
grid 11539 1 0 15:37 ? 00:00:00 apx_pmon_+APX1
oracle 20494 1 0 15:38 ? 00:00:00 ora_pmon_CPROD19
root 23559 23363 0 15:39 pts/1 00:00:00 grep --color=auto pmonEverything is fine.
Post-patching tasks
Dont’ forget these post-patching tasks:
- remove the ODABR snapshots
- add your additional RPMs
- put back your profile scripts for grid and oracle users
- check if monitoring still works
/opt/odabr/odabr infosnap
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
odabr - ODA node Backup Restore - Version: 2.0.2-06
Copyright 2013, 2025, Oracle and/or its affiliates.
--------------------------------------------------------
RACPack, Cloud Innovation and Solution Engineering Team
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
LVM snap name status COW Size Data%
------------- ---------- ---------- ------
root_snap active 30.00 GiB 6.08%
opt_snap active 70.00 GiB 11.41%
u01_snap active 60.00 GiB 25.30%
/opt/odabr/odabr delsnap
INFO: 2026-02-26 15:39:47: Please check the logfile '/opt/odabr/out/log/odabr_23962.log' for more details
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
odabr - ODA node Backup Restore - Version: 2.0.2-06
Copyright 2013, 2025, Oracle and/or its affiliates.
--------------------------------------------------------
RACPack, Cloud Innovation and Solution Engineering Team
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│
INFO: 2026-02-26 15:39:47: Removing LVM snapshots
INFO: 2026-02-26 15:39:47: ...removing LVM snapshot for 'opt'
SUCCESS: 2026-02-26 15:39:48: ...snapshot for 'opt' removed successfully
INFO: 2026-02-26 15:39:48: ...removing LVM snapshot for 'u01'
SUCCESS: 2026-02-26 15:39:48: ...snapshot for 'u01' removed successfully
INFO: 2026-02-26 15:39:48: ...removing LVM snapshot for 'root'
SUCCESS: 2026-02-26 15:39:48: ...snapshot for 'root' removed successfully
SUCCESS: 2026-02-26 15:39:48: LVM snapshots removed successfullyPatching the DB System
If you use DB Systems on your ODA, meaning that some of your databases are running in dedicated VMs, you will need to apply the patch inside each DB System. If you’re using 26ai, you first need to register the new clones in the repository before connecting to your DB System:
odacli update-repository -f /opt/dbi/odacli-dcs-23.26.1.0.0-260211-GI-23.26.1.0.zip
sleep 30 ; odacli describe-job -i 8612ef6a-7df4-419d-8d05-176e11126f48
Job details
----------------------------------------------------------------
ID: 8612ef6a-7df4-419d-8d05-176e11126f48
Description: Repository Update
Status: Success
Created: February 26, 2026 15:44:00 CET
Message: /opt/dbi/odacli-dcs-23.26.1.0.0-260211-GI-23.26.1.0.zip
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Unzip bundle February 26, 2026 15:44:00 CET February 26, 2026 15:44:13 CET Success
odacli update-repository -f /opt/dbi/odacli-dcs-23.26.1.0.0-260211-DB-23.26.1.0.zip
sleep 30 ; odacli describe-job -i 9dd624f2-9048-4897-b63b-400b955c803c
Job details
----------------------------------------------------------------
ID: 9dd624f2-9048-4897-b63b-400b955c803c
Description: Repository Update
Status: Success
Created: February 26, 2026 15:45:12 CET
Message: /opt/dbi/odacli-dcs-23.26.1.0.0-260211-DB-23.26.1.0.zip
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Unzip bundle February 26, 2026 15:45:12 CET February 26, 2026 15:45:40 CET Success
odacli update-repository -f /opt/dbi/oda-sm-23.26.1.0.0-260211-server.zip
sleep 20 ; odacli describe-job -i 6a24023f-de2e-4481-b9c4-d8511d54be48
Job details
----------------------------------------------------------------
ID: 6a24023f-de2e-4481-b9c4-d8511d54be48
Description: Repository Update
Status: Success
Created: February 26, 2026 15:59:07 CET
Message: /opt/dbi/oda-sm-23.26.1.0.0-260211-server.zip
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Unzip bundle February 26, 2026 15:59:08 CET February 26, 2026 15:59:30 CET Success
odacli list-availablepatches
-------------------- ------------------------- ------------------------- ------------------------------
ODA Release Version Supported DB Versions Available DB Versions Supported Platforms
-------------------- ------------------------- ------------------------- ------------------------------
19.30.0.0.0 23.26.1.0.0 23.26.1.0.0 DB System
21.8.0.0.221018 Clone not available DB System
19.30.0.0.260120 19.30.0.0.260120 DB System, Bare MetalApplying the patch is done the same way you’ve done it on bare metal, but here you need to specify the 23.26.1.0.0 version:
ssh dbs-04-tst
odacli update-dcsadmin -v 23.26.1.0.0
sleep 60 ; odacli describe-job -i 4b83ab57-ccb1-4f9f-8c70-572b45ada49b
Job details
----------------------------------------------------------------
ID: 4b83ab57-ccb1-4f9f-8c70-572b45ada49b
Description: DcsAdmin patching to 23.26.1.0.0
Status: Success
Created: March 05, 2026 10:07:44 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Dcs-admin upgrade March 05, 2026 10:07:45 CET March 05, 2026 10:07:59 CET Success
Ping DCS Admin March 05, 2026 10:07:59 CET March 05, 2026 10:09:07 CET Success
sleep 30 ; odacli update-dcscomponents -v 23.26.1.0.0
{
"jobId" : "cb674b3e-d6eb-4351-be39-0f19b8c56f9d",
"status" : "Success",
"message" : "Update-dcscomponents is successful on all the node(s): DCS-Agent shutdown is successful. MySQL upgrade is successful. Metadata schema update is done. Script '/opt/oracle/dcs/log/jobfiles/cb674b3e-d6eb-4351-be39-0f19b8c56f9d/apply_metadata_change.sh' ran successfully. dcsagent RPM upgrade is successful. dcscli RPM upgrade is successful. dcscontroller RPM upgrade is successful. ahf RPM upgrade is successful. Successfully reset the Keystore password. HAMI RPM is already updated. Removed old Libs Successfully ran setupAgentAuth.sh ",
"reports" : null,
"createTimestamp" : "March 05, 2026 10:10:13 AM CET",
"description" : "Update-dcscomponents job completed and is not part of Agent job list",
"updatedTime" : "March 05, 2026 10:18:38 AM CET",
"jobType" : null,
"externalRequestId" : null,
"action" : null
}
odacli describe-admin-job -i cb674b3e-d6eb-4351-be39-0f19b8c56f9d
odacli: 'describe-admin-job' is not an odacli command.
usage: odacli [-h/--help]
<category> [-h/--help]
<operation> [-h/--help]
<command> [-h/--help]
<command> [<args>]
Note that there is no describe-admin-job feature on DB Systems.
odacli create-prepatchreport -sc -v 23.26.1.0.0
sleep 20 ; odacli describe-prepatchreport -i 1b104d06-bc0c-45b8-ab25-b5b6a102a857
Prepatch Report
------------------------------------------------------------------------
Job ID: 1b104d06-bc0c-45b8-ab25-b5b6a102a857
Description: Patch pre-checks for [OS, ORACHKSERVER, SERVER] to 23.26.1.0.0
Status: SUCCESS
Created: March 05, 2026 10:59:34 CET
Result: All pre-checks succeeded
Node Name
---------------
dbs-04-tst
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions Success Validated minimum supported versions.
Validate patching tag Success Validated patching tag: 23.26.1.0.0.
Is patch location available Success Patch location is available.
Verify All OS patches Success No dependencies found for RPMs being
removed, updated and installed. Check
/opt/oracle/dcs/log/jobfiles/
dnfdryrunout_2026-03-05_10-59-
50.0718_832.log file for more details
Validate there is usable Success Successfully validated
space under repo volume /opt/oracle/dcs/repo usable space
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Success Successfully ran Orachk
Validate command execution Success Validated command execution
__SERVER__
Validate local patching Success Successfully validated server local
patching
Validate all KVM ACFS Success All KVM ACFS resources are running
resources are running
Validate DB System VM states Success All DB System VMs states are expected
Enable support for Multi-DB Success No need to convert the DB System
Validate DB System AFD state Success AFD is not configured
Validate there is usable Success Successfully validated
space under repo volume /opt/oracle/dcs/repo usable space
Validate command execution Success Validated command execution
odacli update-servercomponents -v 23.26.1.0.0
The DB System will reboot.
odacli describe-job -i 2b4da73a-7f64-48e0-af76-a1d687a0169f
Job details
----------------------------------------------------------------
ID: 2b4da73a-7f64-48e0-af76-a1d687a0169f
Description: Server Patching to 23.26.1.0.0
Status: Success
Created: March 05, 2026 11:04:19 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Deactivate Unit[dnf-makecache.timer] March 05, 2026 11:04:21 CET March 05, 2026 11:04:21 CET Success
Validating GI user metadata March 05, 2026 11:04:21 CET March 05, 2026 11:04:21 CET Success
Deactivate Unit[kdump.service] March 05, 2026 11:04:22 CET March 05, 2026 11:04:23 CET Success
Modify DBVM udev rules March 05, 2026 11:04:23 CET March 05, 2026 11:04:34 CET Success
Creating local repository March 05, 2026 11:04:34 CET March 05, 2026 11:04:37 CET Success
OSPatchBaseRepo
Updating versionlock plugin March 05, 2026 11:04:37 CET March 05, 2026 11:04:41 CET Success
Applying OS Patches March 05, 2026 11:04:41 CET March 05, 2026 11:07:33 CET Success
Creating local repository HMPPatchRepo March 05, 2026 11:07:34 CET March 05, 2026 11:07:34 CET Success
Applying HMP Patches March 05, 2026 11:07:35 CET March 05, 2026 11:07:38 CET Success
Patch location validation March 05, 2026 11:07:39 CET March 05, 2026 11:07:39 CET Success
Setting SELinux mode March 05, 2026 11:07:39 CET March 05, 2026 11:07:39 CET Success
Oda-hw-mgmt upgrade March 05, 2026 11:07:40 CET March 05, 2026 11:08:08 CET Success
Installing SQLcl software March 05, 2026 11:08:08 CET March 05, 2026 11:08:13 CET Success
Cleanup JRE Home March 05, 2026 11:08:14 CET March 05, 2026 11:08:14 CET Success
Generating and saving BOM March 05, 2026 11:08:17 CET March 05, 2026 11:08:24 CET Success
Update System full patch version March 05, 2026 11:08:17 CET March 05, 2026 11:08:17 CET Success
Update System rebootless patch version March 05, 2026 11:08:17 CET March 05, 2026 11:08:17 CET Success
PreRebootNode Actions March 05, 2026 11:08:24 CET March 05, 2026 11:08:25 CET Success
Reboot Node March 05, 2026 11:08:25 CET March 05, 2026 11:09:59 CET Success
odacli create-prepatchreport -gi -v 23.26.1.0.0
sleep 240 ; odacli describe-prepatchreport -i dd5d216b-d1bc-44cf-bcf8-381da0729469
Prepatch Report
------------------------------------------------------------------------
Job ID: dd5d216b-d1bc-44cf-bcf8-381da0729469
Description: Patch pre-checks for [RHPGI, GI] to 23.26.1.0.0
Status: SUCCESS
Created: March 05, 2026 11:13:21 CET
Result: All pre-checks succeeded
Node Name
---------------
dbs-04-tst
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__RHPGI__
Validate available space Success Validated free space under /u01
Evaluate GI patching Success Successfully validated GI patching
Validate there is usable Success Successfully validated
space under repo volume /opt/oracle/dcs/repo usable space
Validate command execution Success Validated command execution
__GI__
Validate GI metadata Success Successfully validated GI metadata
Validate supported GI versions Success Successfully validated minimum version
Validate there is usable Success Successfully validated
space under repo volume /opt/oracle/dcs/repo usable space
Is clusterware running Success Clusterware is running
Validate patching tag Success Validated patching tag: 23.26.1.0.0.
Is system provisioned Success Verified system is provisioned
Validate BM versions Success Validated BM server components
versions
Validate kernel log level Success Successfully validated the OS log
level
Validate Central Inventory Success oraInventory validation passed
Validate patching locks Success Validated patching locks
Validate clones location exist Success Validated clones location
Validate command execution Success Validated command execution
odacli update-gihome -v 23.26.1.0.0
sleep 600 ; odacli describe-job -i c93f84fc-5cb2-41bb-9f23-f7ce22b9f5de
Job details
----------------------------------------------------------------
ID: c93f84fc-5cb2-41bb-9f23-f7ce22b9f5de
Description: Patch GI with RHP to 23.26.1.0.0
Status: Success
Created: March 05, 2026 11:22:47 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Patch GI with RHP to 23.26.1.0.0 March 05, 2026 11:22:59 CET March 05, 2026 11:27:54 CET Success
Starting the clusterware March 05, 2026 11:22:59 CET March 05, 2026 11:22:59 CET Success
Creating GI home directories March 05, 2026 11:23:01 CET March 05, 2026 11:23:01 CET Success
Extract GI clone March 05, 2026 11:23:01 CET March 05, 2026 11:23:01 CET Success
Provisioning Software Only GI with RHP March 05, 2026 11:23:01 CET March 05, 2026 11:23:01 CET Success
Registering image March 05, 2026 11:23:01 CET March 05, 2026 11:23:01 CET Success
Registering image March 05, 2026 11:23:01 CET March 05, 2026 11:23:01 CET Success
Registering working copy March 05, 2026 11:23:01 CET March 05, 2026 11:23:01 CET Success
Patch GI with RHP March 05, 2026 11:23:47 CET March 05, 2026 11:26:58 CET Success
Set CRS ping target March 05, 2026 11:26:58 CET March 05, 2026 11:26:59 CET Success
Updating .bashrc March 05, 2026 11:26:59 CET March 05, 2026 11:26:59 CET Success
Updating GI home metadata March 05, 2026 11:26:59 CET March 05, 2026 11:27:00 CET Success
Updating GI home version March 05, 2026 11:27:00 CET March 05, 2026 11:27:04 CET Success
Updating All DBHome version March 05, 2026 11:27:04 CET March 05, 2026 11:27:08 CET Success
Patch DB System on BM March 05, 2026 11:27:48 CET March 05, 2026 11:27:54 CET Success
Starting the clusterware March 05, 2026 11:27:48 CET March 05, 2026 11:27:48 CET Success
odacli list-dbhomes
ID Name DB Version DB Edition Home Location Status
---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------
9116603b-3b5e-4e92-aa63-baad8ae1d6a8 OraDB23000_home1 23.26.0.0.0 EE /u01/app/oracle/product/23.0.0.0/dbhome_1 CONFIGURED
odacli create-prepatchreport -d -i 9116603b-3b5e-4e92-aa63-baad8ae1d6a8 -v 23.26.1.0.0
sleep 600 ; odacli describe-prepatchreport -i bb16e390-3dcb-4ea0-b8c5-0c22f38ba271
odacli describe-prepatchreport -i bb16e390-3dcb-4ea0-b8c5-0c22f38ba271
Prepatch Report
------------------------------------------------------------------------
Job ID: bb16e390-3dcb-4ea0-b8c5-0c22f38ba271
Description: Patch pre-checks for [DB, RHPDB, ORACHKDB] to 23.26.1.0.0: DbHome is OraDB23000_home1
Status: FAILED
Created: March 05, 2026 11:59:29 CET
Result: One or more pre-checks failed for [ORACHK]
Node Name
---------------
dbs-04-tst
Pre-Check Status Comments
------------------------------ -------- --------------------------------------
__DB__
Validate DB Home ID Success Validated DB Home ID:
9116603b-3b5e-4e92-aa63-baad8ae1d6a8
Validate patching tag Success Validated patching tag: 23.26.1.0.0.
Is system provisioned Success Verified system is provisioned
Validate minimum agent version Success Validated minimum agent version
Is GI upgraded Success Validated GI is upgraded
Validate available space for Success Validated free space required under
db /u01
Validate there is usable Success Successfully validated Oracle Base
space under oracle base usable space
Validate glogin.sql file Success Successfully verified glogin.sql
won't break patching
Is DB clone available Success Successfully validated clone file
exists
Validate command execution Success Validated command execution
__RHPDB__
Evaluate DBHome patching with Success Successfully validated updating
RHP dbhome with RHP. and local patching
is possible
Validate command execution Success Validated command execution
__ORACHK__
Running orachk Failed DCS-10702 - ORAchk validation failed:
.
Validate command execution Success Validated command execution
Verify the Fast Recovery Area Failed AHF-2929: FRA space management
(FRA) has reclaimable space problem file types are present
without an RMAN backup completion
within the last 7 daysThe failure is similar to the one I had when patching the bare metal DB home, but I can ignore this and update the DB home with the force option:
odacli update-dbhome -i 9116603b-3b5e-4e92-aa63-baad8ae1d6a8 -v 23.26.1.0.0 -f
sleep 1200 ; odacli describe-job -i 4fc89556-2f7c-4e5b-a12f-55e32d7e748a
Job details
----------------------------------------------------------------
ID: 4fc89556-2f7c-4e5b-a12f-55e32d7e748a
Description: DB Home Patching to 23.26.1.0.0: Home ID is 9116603b-3b5e-4e92-aa63-baad8ae1d6a8
Status: Success
Created: March 05, 2026 13:36:42 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Creating wallet for DB Client March 05, 2026 13:37:21 CET March 05, 2026 13:37:21 CET Success
Patch databases by RHP - [CTEST26] March 05, 2026 13:37:21 CET March 05, 2026 13:54:26 CET Success
Updating database metadata March 05, 2026 13:54:26 CET March 05, 2026 13:54:27 CET Success
Upgrade pwfile to 12.2 March 05, 2026 13:54:27 CET March 05, 2026 13:54:32 CET Success
Set log_archive_dest for Database March 05, 2026 13:54:32 CET March 05, 2026 13:54:37 CET Success
Populate PDB metadata March 05, 2026 13:54:38 CET March 05, 2026 13:54:39 CET Success
Generating and saving BOM March 05, 2026 13:54:39 CET March 05, 2026 13:55:08 CET Success
TDE parameter update March 05, 2026 13:55:44 CET March 05, 2026 13:55:44 CET Success
odacli list-databases
ID DB Name DB Type DB Version CDB Class Edition Shape Storage Status DB Home ID
---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------
276bf458-db09-4c9a-9cd9-a821e5274fb0 CTEST26 SI 23.26.1.0.0 true OLTP EE odb2 ASM CONFIGURED 9c51039d-ccba-4508-b879-a81b8c18d46a
odacli delete-dbhome -i 9116603b-3b5e-4e92-aa63-baad8ae1d6a8
sleep 100 ; odacli describe-job -i 0994b96e-e174-4776-8699-f179c1d89af0
Job details
----------------------------------------------------------------
ID: 0994b96e-e174-4776-8699-f179c1d89af0
Description: Database Home OraDB23000_home1 Deletion with ID 9116603b-3b5e-4e92-aa63-baad8ae1d6a8
Status: Success
Created: March 05, 2026 13:58:36 CET
Message:
Task Name Start Time End Time Status
---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------
Setting up SSH equivalence March 05, 2026 13:58:36 CET March 05, 2026 13:58:36 CET Success
Setting up SSH equivalence March 05, 2026 13:58:36 CET March 05, 2026 13:58:37 CET Success
Validate DB Home March 05, 2026 13:58:36 CET March 05, 2026 13:58:36 CET Success
9116603b-3b5e-4e92-aa63-baad8ae1d6a8
for deletion
Deleting DB Home by RHP March 05, 2026 13:58:38 CET March 05, 2026 13:59:15 CET Success
odacli describe-component
System Version
--------------
23.26.1.0.0
System Node Name
----------------
dbs-04-tst
Local System Version
--------------------
23.26.1.0.0
Component Installed Version Available Version
---------------------------------------- -------------------- --------------------
OAK 23.26.1.0.0 up-to-date
GI 23.26.1.0.0 up-to-date
DB {
OraDB23000_home2 23.26.1.0.0 up-to-date
[CTEST26]
}
DCSCONTROLLER 23.26.1.0.0 up-to-date
DCSCLI 23.26.1.0.0 up-to-date
DCSAGENT 23.26.1.0.0 up-to-date
DCSADMIN 23.26.1.0.0 up-to-date
OS 8.10 up-to-date
Finally, let’s remove obsolete GI binaries:
du -hs /u01/app/23.26.*
3.9G /u01/app/23.26.0.0
3.6G /u01/app/23.26.1.0
rm -rf /u01/app/23.26.0.0/Don’t forget to apply this procedure to the other DB Systems.
Conclusion
Applying this patch is OK, as soon as everything is clean and under control. When patching, only use the force option when you’re sure that you know what you’re doing. As always, patching an ODA with DB Systems can take quite a big amount of time, mainly depending on the number of DB Systems.
![Thumbnail [60x60]](https://www.dbi-services.com/blog/wp-content/uploads/2022/08/JDU_web-min-scaled.jpg)
![Thumbnail [90x90]](https://www.dbi-services.com/blog/wp-content/uploads/2025/05/JDE_Web-1-scaled.jpg)
![Thumbnail [90x90]](https://www.dbi-services.com/blog/wp-content/uploads/2024/04/SIT_web.png)