{"id":43377,"date":"2026-03-06T16:10:54","date_gmt":"2026-03-06T15:10:54","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=43377"},"modified":"2026-03-10T10:26:54","modified_gmt":"2026-03-10T09:26:54","slug":"how-to-patch-your-oda-to-19-30","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/","title":{"rendered":"How to patch your ODA to 19.30?"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\" id=\"h-introduction\">Introduction<\/h2>\n\n\n\n<p>Patch 19.30 is now available for Oracle Database Appliance series. Let&#8217;s find out what&#8217;s new and how to apply this patch.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-what-s-new\">What&#8217;s new?<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<p>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&#8217;s always good to know the involved steps and their status of such a process.<\/p>\n\n\n\n<p>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.<\/p>\n\n\n\n<p>As you can guess, this patch is mainly a bundle patch for security and bug fixes. A bigger update is expected later this year.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-which-oda-is-compatible-with-this-19-30-release\">Which ODA is compatible with this 19.30 release?<\/h2>\n\n\n\n<p>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&#8217;re using X8-2 ODAs, available from late 2019 to mid 2022, the last patch is planned for August 2027.<\/p>\n\n\n\n<p>I still recommend keeping your ODA 7 years, not less, not more. This blog post is still relevant today: <a href=\"https:\/\/www.dbi-services.com\/blog\/why-you-should-consider-keeping-your-oda-more-than-5-years\/\">https:\/\/www.dbi-services.com\/blog\/why-you-should-consider-keeping-your-oda-more-than-5-<\/a><a href=\"https:\/\/www.dbi-services.com\/blog\/why-you-should-consider-keeping-your-oda-more-than-5-years\/\" target=\"_blank\" rel=\"noreferrer noopener\">years<\/a><a href=\"https:\/\/www.dbi-services.com\/blog\/why-you-should-consider-keeping-your-oda-more-than-5-years\/\">\/<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-is-this-patch-a-cumulative-one\">Is this patch a cumulative one?<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<p>What&#8217;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.<\/p>\n\n\n\n<p>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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-is-there-also-a-patch-for-my-databases\">Is there also a patch for my databases?<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-download-the-patch-and-clone-files\">Download the patch and clone files<\/h2>\n\n\n\n<p>These files are mandatory:<\/p>\n\n\n\n<p>38776074 =&gt; the patch itself<br>30403673 =&gt; the GI clone needed for deploying newer 19c GI version<br>30403662 =&gt; the DB clone for deploying newer version of 19c<\/p>\n\n\n\n<p>These files are optional:<\/p>\n\n\n\n<p>30403643 =&gt; ISO file for reimaging, not needed for patching<br>36524660 =&gt; System image for deploying a new 26ai DB System<br>36524627 =&gt; the GI clone needed for deploying\/patching to newer 26ai GI version<br>36524642 =&gt; the DB clone for deploying\/patching to newer 26ai version<br>32451228 =&gt; The newer system image for 19c DB Systems<br>38776071 =&gt; The patch for 26ai DB Systems<\/p>\n\n\n\n<p>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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-prepare-the-patching\">Prepare the patching<\/h2>\n\n\n\n<p>Before starting, please check these prerequisites:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>filesystems \/, \/opt, \/u01 and \/root have at least 20% of available free space<\/li>\n\n\n\n<li>unzip the downloaded patch files<\/li>\n\n\n\n<li>additional manually installed rpms must be removed<\/li>\n\n\n\n<li>revert profile scripts to default&#8217;s one (for grid and oracle users)<\/li>\n\n\n\n<li>make sure you&#8217;ve planned a sufficient downtime (4+ hours depending on the number of databases and DB Systems)<\/li>\n\n\n\n<li>do a sanity reboot before patching to kill zombie processes<\/li>\n\n\n\n<li>use ODABR to make snapshots of the important filesystems prior patching: this tool is now included in the software distribution<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>df -h \/ \/u01 \/opt\/\nFilesystem                          Size  Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolRoot   30G   13G   16G  46% \/\n\/dev\/mapper\/VolGroupSys-LogVolU01    59G   23G   34G  40% \/u01\n\/dev\/mapper\/VolGroupSys-LogVolOpt    69G   34G   33G  52% \/opt\n\ncd \/opt\/dbi\nfor a in `ls p*1930*.zip` ; do unzip -o $a ; rm -f $a ; done\n\nreboot\n...\n\npvs\n  PV           VG          Fmt  Attr PSize   PFree\n  \/dev\/md126p3 VolGroupSys lvm2 a--  446.09g 260.09g\n\n\/opt\/odabr\/odabr backup --snap\nINFO: 2026-02-26 11:29:54: Please check the logfile '\/opt\/odabr\/out\/log\/odabr_24079.log' for more details\n\n\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n odabr - ODA node Backup Restore - Version: 2.0.2-05\n Copyright 2013, 2025, Oracle and\/or its affiliates.\n --------------------------------------------------------\n RACPack, Cloud Innovation and Solution Engineering Team\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n\nINFO: 2026-02-26 11:29:54: Checking superuser\nINFO: 2026-02-26 11:29:54: Checking Bare Metal\n\nINFO: 2026-02-26 11:29:54: Removing existing LVM snapshots\nWARNING: 2026-02-26 11:29:54: LVM snapshot for 'opt' does not exist\nWARNING: 2026-02-26 11:29:54: LVM snapshot for 'u01' does not exist\nWARNING: 2026-02-26 11:29:54: LVM snapshot for 'root' does not exist\n\nINFO: 2026-02-26 11:29:54: Checking current OS version...\nINFO: 2026-02-26 11:29:54: Checking LVM restore backgroud process\nINFO: 2026-02-26 11:29:54: Checking LVM size\n\nINFO: 2026-02-26 11:29:54: Boot device backup\nINFO: 2026-02-26 11:29:54: Getting EFI device\nINFO: 2026-02-26 11:29:54: ...step1 - unmounting EFI\nINFO: 2026-02-26 11:29:54: ...step2 - making efi device backup\nSUCCESS: 2026-02-26 11:29:57: ...EFI device backup saved as '\/opt\/odabr\/out\/hbi\/efi.img'\nINFO: 2026-02-26 11:29:57: ...step3 - checking EFI device backup\nINFO: 2026-02-26 11:29:57: Getting boot device\nINFO: 2026-02-26 11:29:57: ...step1 - making boot device backup using tar\nSUCCESS: 2026-02-26 11:30:03: ...boot content saved as '\/opt\/odabr\/out\/hbi\/boot.tar.gz'\nINFO: 2026-02-26 11:30:03: ...step2 - unmounting boot\nINFO: 2026-02-26 11:30:04: ...step3 - making boot device backup using dd\nSUCCESS: 2026-02-26 11:30:09: ...boot device backup saved as '\/opt\/odabr\/out\/hbi\/boot.img'\nINFO: 2026-02-26 11:30:09: ...step4 - mounting boot\nINFO: 2026-02-26 11:30:09: ...step5 - mounting EFI\nINFO: 2026-02-26 11:30:10: ...step6 - checking boot device backup\n\nINFO: 2026-02-26 11:30:10: Making OCR physical backup\nINFO: 2026-02-26 11:30:11: ...ocr backup saved as '\/opt\/odabr\/out\/hbi\/ocrbackup_24079.bck'\nSUCCESS: 2026-02-26 11:30:11: OCR physical backup created successfully\nINFO: 2026-02-26 11:30:11: OCR export backup\nINFO: 2026-02-26 11:30:12: ...ocr export saved as '\/opt\/odabr\/out\/hbi\/ocrexport_24079.bck'\nSUCCESS: 2026-02-26 11:30:12: OCR export backup created successfully\nINFO: 2026-02-26 11:30:12: Saving clusterware patch level as '\/opt\/odabr\/out\/hbi\/clusterware_patch_level.info'\nSUCCESS: 2026-02-26 11:30:12: Clusterware patch level saved successfully\n\nINFO: 2026-02-26 11:30:12: Making LVM snapshot backup\nSUCCESS: 2026-02-26 11:30:13: ...snapshot backup for 'opt' created successfully\nSUCCESS: 2026-02-26 11:30:14: ...snapshot backup for 'u01' created successfully\nSUCCESS: 2026-02-26 11:30:14: ...snapshot backup for 'root' created successfully\nSUCCESS: 2026-02-26 11:30:14: LVM snapshots backup done successfully<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-version-precheck\">Version precheck<\/h2>\n\n\n\n<p>Start to check the current version of the various components:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-component\nSystem Version\n--------------\n19.29.0.0.0\n\nSystem Node Name\n----------------\ndbioda01\n\nLocal System Version\n--------------------\n19.29.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                      19.29.0.0.0          up-to-date\n\nGI                                       19.29.0.0.251021     up-to-date\n\nDB {\n     OraDB19000_home9                    19.29.0.0.251021     up-to-date\n     &#091;CPROD19]\n}\n\nDCSCONTROLLER                            19.29.0.0.0          up-to-date\n\nDCSCLI                                   19.29.0.0.0          up-to-date\n\nDCSAGENT                                 19.29.0.0.0          up-to-date\n\nDCSADMIN                                 19.29.0.0.0          up-to-date\n\nOS                                       8.10                 up-to-date\n\nILOM                                     5.1.5.22.r165351     up-to-date\n\nBIOS                                     52160100             up-to-date\n\nLOCAL CONTROLLER FIRMWARE {\n     &#091;c4]                                8000D9AB             up-to-date\n}\n\nSHARED CONTROLLER FIRMWARE {\n     &#091;c0, c1]                            VDV1RL06             up-to-date\n}\n\nLOCAL DISK FIRMWARE {\n     &#091;c2d0, c2d1]                        XC311132             up-to-date\n}\n\nHMP                                      2.4.10.1.600         up-to-date<\/code><\/pre>\n\n\n\n<p>List the DB homes, databases, DB Systems and VMs:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\n57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb     OraDB19000_home9     19.29.0.0.251021     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9     CONFIGURED\n\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID\n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n976a80f2-4653-469f-8cd4-ddc1a21aff51     CPROD19    SI       19.29.0.0.251021     true    OLTP     EE       odb8     ASM      CONFIGURED   57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\n\n\nodacli list-dbsystems\nName                  Shape       GI version          DB info                         Status                  Created                   Updated\n--------------------  ----------  ------------------  ------------------------------  ----------------------  ------------------------  ------------------------\ndbs-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\n\nodacli list-vms\nNo data found for resource VM.<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-update-the-dcs-components\">Update the DCS components<\/h2>\n\n\n\n<p>Updating DCS components is the first step, after registering the patch file:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/opt\/dbi\/oda-sm-19.30.0.0.0-260210-server.zip\nsleep 30 ; odacli describe-job -i e3ba068f-01db-45c3-949d-b79f43c8d6b7\nJob details\n----------------------------------------------------------------\n                     ID:  e3ba068f-01db-45c3-949d-b79f43c8d6b7\n            Description:  Repository Update\n                 Status:  Success\n                Created:  February 26, 2026 11:30:48 CET\n                Message:  \/opt\/dbi\/oda-sm-19.30.0.0.0-260210-server.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nUnzip bundle                             February 26, 2026 11:30:49 CET           February 26, 2026 11:31:10 CET           Success\n\n\nodacli describe-component\nSystem Version\n--------------\n19.29.0.0.0\n\nSystem Node Name\n----------------\ndbioda01\n\nLocal System Version\n--------------------\n19.29.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                      19.29.0.0.0          19.30.0.0.0\n\nGI                                       19.29.0.0.251021     19.30.0.0.260120\n\nDB {\n     OraDB19000_home9                    19.29.0.0.251021     19.30.0.0.260120\n     &#091;CPROD19]\n}\n\nDCSCONTROLLER                            19.29.0.0.0          19.30.0.0.0\n\nDCSCLI                                   19.29.0.0.0          19.30.0.0.0\n\nDCSAGENT                                 19.29.0.0.0          19.30.0.0.0\n\nDCSADMIN                                 19.29.0.0.0          19.30.0.0.0\n\nOS                                       8.10                 up-to-date\n\nILOM                                     5.1.5.22.r165351     5.1.5.29.r167438\n\nBIOS                                     52160100             52170100\n\nLOCAL CONTROLLER FIRMWARE {\n     &#091;c4]                                8000D9AB             up-to-date\n}\n\nSHARED CONTROLLER FIRMWARE {\n     &#091;c0, c1]                            VDV1RL06             up-to-date\n}\n\nLOCAL DISK FIRMWARE {\n     &#091;c2d0, c2d1]                        XC311132             up-to-date\n}\n\nHMP                                      2.4.10.1.600         up-to-date<\/code><\/pre>\n\n\n\n<p>Let&#8217;s update the DCS components to 19.30:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-dcsadmin -v 19.30.0.0.0\n\nsleep 90 ; odacli describe-job -i \"c3c278ad-89e6-4c7d-b9fd-27833a187e43\"\nJob details\n----------------------------------------------------------------\n                     ID:  c3c278ad-89e6-4c7d-b9fd-27833a187e43\n            Description:  DcsAdmin patching to 19.30.0.0.0\n                 Status:  Success\n                Created:  February 26, 2026 11:32:11 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nDcs-admin upgrade                        February 26, 2026 11:32:11 CET           February 26, 2026 11:32:21 CET           Success\nPing DCS Admin                           February 26, 2026 11:32:21 CET           February 26, 2026 11:33:29 CET           Success\n\n\nsleep 30 ;  odacli update-dcscomponents -v 19.30.0.0.0\nsleep 300 ; odacli describe-admin-job -i 2aeda3f3-df4d-4f7c-a0ce-b57eeab0448b\nJob details\n----------------------------------------------------------------\n                     ID:  2aeda3f3-df4d-4f7c-a0ce-b57eeab0448b\n            Description:  Update-dcscomponents to 19.30.0.0.0\n                 Status:  Success\n                Created:  February 26, 2026 11:34:51 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nPre-checks for update DCS components     February 26, 2026 11:34:57 CET           February 26, 2026 11:35:05 CET           Success\nUpdate DCS components                    February 26, 2026 11:35:05 CET           February 26, 2026 11:35:05 CET           Success\nStop DCS-Agent                           February 26, 2026 11:35:05 CET           February 26, 2026 11:35:05 CET           Success\nUpdate MySql                             February 26, 2026 11:35:05 CET           February 26, 2026 11:35:42 CET           Success\nApply metadata schema changes            February 26, 2026 11:35:42 CET           February 26, 2026 11:35:42 CET           Success\nModify MySQL Metadata                    February 26, 2026 11:35:42 CET           February 26, 2026 11:35:43 CET           Success\nUpdate DCS-Agent                         February 26, 2026 11:35:43 CET           February 26, 2026 11:35:57 CET           Success\nUpdate DCS-Cli                           February 26, 2026 11:35:57 CET           February 26, 2026 11:35:59 CET           Success\nUpdate DCS-Controller                    February 26, 2026 11:35:59 CET           February 26, 2026 11:36:22 CET           Success\nUpdate AHF RPM                           February 26, 2026 11:36:22 CET           February 26, 2026 11:38:41 CET           Success\nReset Keystore password                  February 26, 2026 11:38:41 CET           February 26, 2026 11:39:02 CET           Success\nUpdate HAMI                              February 26, 2026 11:39:02 CET           February 26, 2026 11:39:54 CET           Success\nRemove old library files                 February 26, 2026 11:39:54 CET           February 26, 2026 11:39:54 CET           Success\nPost DCS update actions                  February 26, 2026 11:39:54 CET           February 26, 2026 11:39:54 CET           Success<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-system-patching\">System patching<\/h2>\n\n\n\n<p>Let&#8217;s do the prepatching of the system:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli create-prepatchreport -sc -v 19.30.0.0.0\n\nsleep 180 ; odacli describe-prepatchreport -i c06cd4d0-d30c-4063-a3c1-3b86db6625b0\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  c06cd4d0-d30c-4063-a3c1-3b86db6625b0\n            Description:  Patch pre-checks for &#091;OS, ILOM, ORACHKSERVER, SERVER] to 19.30.0.0.0\n                 Status:  SUCCESS\n                Created:  February 26, 2026 11:40:17 AM CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbioda01\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__OS__\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 19.30.0.0.0.\nIs patch location available     Success   Patch location is available.\nVerify All OS patches           Success   No dependencies found for RPMs being\n                                          removed, updated and installed. Check\n                                          \/opt\/oracle\/dcs\/log\/jobfiles\/\n                                          dnfdryrunout_2026-02-26_11-40-\n                                          34.0688_236.log file for more details\nValidate command execution      Success   Validated command execution\n\n__ILOM__\nValidate ILOM server reachable  Success   Successfully connected with ILOM\n                                          server using public IP and USB\n                                          interconnect\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 19.30.0.0.0.\nIs patch location available     Success   Patch location is available.\nChecking Ilom patch Version     Success   Successfully verified the versions\nPatch location validation       Success   Successfully validated location\nValidate command execution      Success   Validated command execution\n\n__ORACHK__\nRunning orachk                  Success   Successfully ran Orachk\nValidate command execution      Success   Validated command execution\n\n__SERVER__\nValidate local patching         Success   Successfully validated server local\n                                          patching\nValidate all KVM ACFS           Success   All KVM ACFS resources are running\nresources are running\nValidate DB System VM states    Success   All DB System VMs states are expected\nValidate DB System AFD state    Success   All DB Systems are on required\n                                          versions\nValidate command execution      Success   Validated command execution\n<\/code><\/pre>\n\n\n\n<p>OK let&#8217;s apply the system patch:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-servercomponents -v 19.30.0.0.0\n...\n<\/code><\/pre>\n\n\n\n<p>The server will reboot at the end of the patching (it took 40 minutes on my X8-2M). Let&#8217;s then check the job:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-job -i \"8d5b4b63-3a92-46e4-b466-9fd46cdf8b3a\"\nJob details\n----------------------------------------------------------------\n                     ID:  8d5b4b63-3a92-46e4-b466-9fd46cdf8b3a\n            Description:  Server Patching to 19.30.0.0.0\n                 Status:  Success\n                Created:  February 26, 2026 11:42:47 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nValidating GI user metadata              February 26, 2026 11:42:53 CET           February 26, 2026 11:42:54 CET           Success\nModify BM udev rules                     February 26, 2026 11:42:54 CET           February 26, 2026 11:43:05 CET           Success\nValidate ILOM server reachable           February 26, 2026 11:42:54 CET           February 26, 2026 11:42:54 CET           Success\nStop oakd                                February 26, 2026 11:43:05 CET           February 26, 2026 11:43:08 CET           Success\nCreating local repository                February 26, 2026 11:43:09 CET           February 26, 2026 11:43:11 CET           Success\nOSPatchBaseRepo\nUpdating versionlock plugin              February 26, 2026 11:43:11 CET           February 26, 2026 11:43:14 CET           Success\nApplying OS Patches                      February 26, 2026 11:43:14 CET           February 26, 2026 11:50:26 CET           Success\nApplying HMP Patches                     February 26, 2026 11:50:27 CET           February 26, 2026 11:50:30 CET           Success\nCreating local repository HMPPatchRepo   February 26, 2026 11:50:27 CET           February 26, 2026 11:50:27 CET           Success\nOda-hw-mgmt upgrade                      February 26, 2026 11:50:31 CET           February 26, 2026 11:51:02 CET           Success\nPatch location validation                February 26, 2026 11:50:31 CET           February 26, 2026 11:50:31 CET           Success\nSetting SELinux mode                     February 26, 2026 11:50:31 CET           February 26, 2026 11:50:31 CET           Success\nInstalling SQLcl software                February 26, 2026 11:51:02 CET           February 26, 2026 11:51:06 CET           Success\nOSS Patching                             February 26, 2026 11:51:02 CET           February 26, 2026 11:51:02 CET           Success\nApplying Firmware local Disk Patches     February 26, 2026 11:51:06 CET           February 26, 2026 11:51:10 CET           Success\nApplying Firmware local Controller Patch February 26, 2026 11:51:10 CET           February 26, 2026 11:51:14 CET           Success\nApplying Firmware shared Controller      February 26, 2026 11:51:15 CET           February 26, 2026 11:51:19 CET           Success\nPatch\nChecking Ilom patch Version              February 26, 2026 11:51:19 CET           February 26, 2026 11:51:19 CET           Success\nPatch location validation                February 26, 2026 11:51:19 CET           February 26, 2026 11:51:19 CET           Success\nDisabling IPMI v2                        February 26, 2026 11:51:20 CET           February 26, 2026 11:51:21 CET           Success\nSave password in Wallet                  February 26, 2026 11:51:20 CET           February 26, 2026 11:51:20 CET           Success\nApply Ilom patch                         February 26, 2026 11:51:21 CET           February 26, 2026 12:02:07 CET           Success\nCopying Flash Bios to Temp location      February 26, 2026 12:02:07 CET           February 26, 2026 12:02:07 CET           Success\nStart oakd                               February 26, 2026 12:02:08 CET           February 26, 2026 12:02:24 CET           Success\nAdd SYSNAME in Env                       February 26, 2026 12:02:25 CET           February 26, 2026 12:02:25 CET           Success\nCleanup JRE Home                         February 26, 2026 12:02:25 CET           February 26, 2026 12:02:25 CET           Success\nStarting the clusterware                 February 26, 2026 12:02:25 CET           February 26, 2026 12:03:59 CET           Success\nUpdate lvm.conf file                     February 26, 2026 12:04:00 CET           February 26, 2026 12:04:00 CET           Success\nGenerating and saving BOM                February 26, 2026 12:04:01 CET           February 26, 2026 12:04:34 CET           Success\nUpdate System full patch version         February 26, 2026 12:04:01 CET           February 26, 2026 12:04:01 CET           Success\nUpdate System rebootless patch version   February 26, 2026 12:04:01 CET           February 26, 2026 12:04:01 CET           Success\nPreRebootNode Actions                    February 26, 2026 12:04:34 CET           February 26, 2026 12:07:10 CET           Success\nReboot Node                              February 26, 2026 12:07:10 CET           February 26, 2026 12:18:17 CET           Success<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-gi-patching\">GI patching<\/h2>\n\n\n\n<p>Let&#8217;s register the patch file, and do the precheck for GI:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/opt\/dbi\/odacli-dcs-19.30.0.0.0-260210-GI-19.30.0.0.zip\nsleep 70 ; odacli describe-job -i \"5699a201-8f50-499c-98a8-18b2e79ca356\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  5699a201-8f50-499c-98a8-18b2e79ca356\n            Description:  Repository Update\n                 Status:  Success\n                Created:  February 26, 2026 12:32:04 CET\n                Message:  \/opt\/dbi\/odacli-dcs-19.30.0.0.0-260210-GI-19.30.0.0.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nUnzip bundle                             February 26, 2026 12:32:05 CET           February 26, 2026 12:33:14 CET           Success\n\nodacli create-prepatchreport -gi -v 19.30.0.0.0\n\nsleep 180 ; odacli describe-prepatchreport -i ac157412-cfe2-4b2e-ae04-e7082cd4014f\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  ac157412-cfe2-4b2e-ae04-e7082cd4014f\n            Description:  Patch pre-checks for &#091;RHPGI, GI] to 19.30.0.0.0\n                 Status:  SUCCESS\n                Created:  February 26, 2026 12:34:00 PM CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbioda01\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__RHPGI__\nValidate available space        Success   Validated free space under \/u01\nEvaluate GI patching            Success   Successfully validated GI patching\nValidate command execution      Success   Validated command execution\n\n__GI__\nValidate GI metadata            Success   Successfully validated GI metadata\nValidate supported GI versions  Success   Successfully validated minimum version\nIs clusterware running          Success   Clusterware is running\nValidate patching tag           Success   Validated patching tag: 19.30.0.0.0.\nIs system provisioned           Success   Verified system is provisioned\nValidate ASM is online          Success   ASM is online\nValidate kernel log level       Success   Successfully validated the OS log\n                                          level\nValidate Central Inventory      Success   oraInventory validation passed\nValidate patching locks         Success   Validated patching locks\nValidate clones location exist  Success   Validated clones location\nValidate DB start dependencies  Success   DBs START dependency check passed\nValidate DB stop dependencies   Success   DBs STOP dependency check passed\nValidate space for clones       Success   Clones volume is already created\nvolume\nValidate command execution      Success   Validated command execution<\/code><\/pre>\n\n\n\n<p>Let&#8217;s apply the GI update now:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-gihome -v 19.30.0.0.0\nsleep 500 ;  odacli describe-job -i \"857bb637-82ec-4de9-a820-5ab9b895e9f8\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  857bb637-82ec-4de9-a820-5ab9b895e9f8\n            Description:  Patch GI with RHP to 19.30.0.0.0\n                 Status:  Success\n                Created:  February 26, 2026 12:38:29 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nPatch GI with RHP to 19.30.0.0.0         February 26, 2026 12:38:44 CET           February 26, 2026 12:46:00 CET           Success\nRegistering image                        February 26, 2026 12:38:45 CET           February 26, 2026 12:38:45 CET           Success\nRegistering working copy                 February 26, 2026 12:38:45 CET           February 26, 2026 12:38:46 CET           Success\nStarting the clusterware                 February 26, 2026 12:38:45 CET           February 26, 2026 12:38:45 CET           Success\nCreating GI home directories             February 26, 2026 12:38:46 CET           February 26, 2026 12:38:46 CET           Success\nExtract GI clone                         February 26, 2026 12:38:46 CET           February 26, 2026 12:38:46 CET           Success\nProvisioning Software Only GI with RHP   February 26, 2026 12:38:46 CET           February 26, 2026 12:38:46 CET           Success\nRegistering image                        February 26, 2026 12:38:46 CET           February 26, 2026 12:38:46 CET           Success\nPatch GI with RHP                        February 26, 2026 12:39:20 CET           February 26, 2026 12:45:25 CET           Success\nSet CRS ping target                      February 26, 2026 12:45:25 CET           February 26, 2026 12:45:25 CET           Success\nUpdating .bashrc                         February 26, 2026 12:45:25 CET           February 26, 2026 12:45:26 CET           Success\nUpdating GI home metadata                February 26, 2026 12:45:26 CET           February 26, 2026 12:45:26 CET           Success\nUpdating GI home version                 February 26, 2026 12:45:26 CET           February 26, 2026 12:45:31 CET           Success\nUpdating All DBHome version              February 26, 2026 12:45:31 CET           February 26, 2026 12:45:36 CET           Success\nStarting the clusterware                 February 26, 2026 12:45:56 CET           February 26, 2026 12:45:56 CET           Success\nValidate ACFS resources are running      February 26, 2026 12:45:56 CET           February 26, 2026 12:45:57 CET           Success\nValidate GI availability                 February 26, 2026 12:45:56 CET           February 26, 2026 12:45:56 CET           Success\nValidate DB System VMs states            February 26, 2026 12:45:57 CET           February 26, 2026 12:45:58 CET           Success\nPatch CPU Pools distribution             February 26, 2026 12:45:58 CET           February 26, 2026 12:45:58 CET           Success\nPatch DB System domain config            February 26, 2026 12:45:58 CET           February 26, 2026 12:45:58 CET           Success\nPatch KVM CRS type                       February 26, 2026 12:45:58 CET           February 26, 2026 12:45:58 CET           Success\nPatch VM vDisks CRS dependencies         February 26, 2026 12:45:58 CET           February 26, 2026 12:45:58 CET           Success\nSave custom VNetworks to storage         February 26, 2026 12:45:58 CET           February 26, 2026 12:45:59 CET           Success\nAdd network filters to DB Systems        February 26, 2026 12:45:59 CET           February 26, 2026 12:46:00 CET           Success\nCreate network filters                   February 26, 2026 12:45:59 CET           February 26, 2026 12:45:59 CET           Success\nPatch DB Systems custom scale metadata   February 26, 2026 12:46:00 CET           February 26, 2026 12:46:00 CET           Success\nPatch DB Systems vDisks CRS dependencies February 26, 2026 12:46:00 CET           February 26, 2026 12:46:00 CET           Success<\/code><\/pre>\n\n\n\n<p>No reboot is needed for this patch.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-check-the-versions\">Check the versions<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-component\nSystem Version\n--------------\n19.30.0.0.0\n\nSystem Node Name\n----------------\ndbioda01\n\nLocal System Version\n--------------------\n19.30.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                      19.30.0.0.0          up-to-date\n\nGI                                       19.30.0.0.260120     up-to-date\n\nDB {\n     OraDB19000_home9                    19.29.0.0.251021     19.30.0.0.260120\n     &#091;CPROD19]\n}\n\nDCSCONTROLLER                            19.30.0.0.0          up-to-date\n\nDCSCLI                                   19.30.0.0.0          up-to-date\n\nDCSAGENT                                 19.30.0.0.0          up-to-date\n\nDCSADMIN                                 19.30.0.0.0          up-to-date\n\nOS                                       8.10                 up-to-date\n\nILOM                                     5.1.5.29.r167438     up-to-date\n\nBIOS                                     52170100             up-to-date\n\nLOCAL CONTROLLER FIRMWARE {\n     &#091;c4]                                8000D9AB             up-to-date\n}\n\nSHARED CONTROLLER FIRMWARE {\n     &#091;c0, c1]                            VDV1RL06             up-to-date\n}\n\nLOCAL DISK FIRMWARE {\n     &#091;c2d0, c2d1]                        XC311132             up-to-date\n}\n\nHMP                                      2.4.10.1.600         up-to-date<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-patching-the-storage\">Patching the storage<\/h2>\n\n\n\n<p>Patching the storage is only needed if describe-component tells you that you&#8217;re not up-to-date. On my X8-2M, it wasn&#8217;t needed. If your ODA need the storage patch, it&#8217;s easy:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-storage -v 19.30.0.0.0\nodacli describe-job -i ...\n<\/code><\/pre>\n\n\n\n<p>The server will reboot once done.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-patching-the-db-homes\">Patching the DB homes<\/h2>\n\n\n\n<p>It&#8217;s now time to patch the DB home and the database on my ODA. Let&#8217;s first unzip and register the patch file in the repository:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/opt\/dbi\/odacli-dcs-19.30.0.0.0-260210-DB-19.30.0.0.zip \nsleep 60; odacli describe-job -i 5690c811-9030-427e-82f1-caeeba236329\n\nJob details\n----------------------------------------------------------------\n                     ID:  5690c811-9030-427e-82f1-caeeba236329\n            Description:  Repository Update\n                 Status:  Success\n                Created:  February 26, 2026 12:54:57 CET\n                Message:  \/opt\/dbi\/odacli-dcs-19.30.0.0.0-260210-DB-19.30.0.0.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nUnzip bundle                             February 26, 2026 12:54:57 CET           February 26, 2026 12:55:50 CET           Success\n\n\n\nodacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\n57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb     OraDB19000_home9     19.29.0.0.251021     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9     CONFIGURED\n<\/code><\/pre>\n\n\n\n<p>Let&#8217;s check if the patch can be applied:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli create-prepatchreport -d -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb -v 19.30.0.0.0\n\nsleep 600; odacli describe-prepatchreport -i 3522c79c-7444-44d7-9422-9d1daab161d2\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  3522c79c-7444-44d7-9422-9d1daab161d2\n            Description:  Patch pre-checks for &#091;DB, RHPDB, ORACHKDB] to 19.30.0.0.0: DbHome is OraDB19000_home9\n                 Status:  FAILED\n                Created:  February 26, 2026 12:56:59 PM CET\n                 Result:  One or more pre-checks failed for &#091;ORACHK, DB]\n\nNode Name\n---------------\ndbioda01\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__DB__\nValidate data corruption in     Failed    DCS-10315 - Patch described in My\npatching                                  Oracle Support Note KB867473 must be\n                                          applied.\nValidate DB Home ID             Success   Validated DB Home ID:\n                                          57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\nValidate patching tag           Success   Validated patching tag: 19.30.0.0.0.\nIs system provisioned           Success   Verified system is provisioned\nValidate minimum agent version  Success   Validated minimum agent version\nIs GI upgraded                  Success   Validated GI is upgraded\nValidate available space for    Success   Validated free space required under\ndb                                        \/u01\nValidate there is usable        Success   Successfully validated Oracle Base\nspace under oracle base                   usable space\nValidate glogin.sql file        Success   Successfully verified glogin.sql\n                                          won't break patching\nValidate dbHomesOnACFS          Success   User has configured disk group for\nconfigured                                Database homes on ACFS\nValidate Oracle base            Success   Successfully validated Oracle Base\nIs DB clone available           Success   Successfully validated clone file\n                                          exists\nValidate command execution      Success   Validated command execution\n\n__RHPDB__\nEvaluate DBHome patching with   Success   Successfully validated updating\nRHP                                       dbhome with RHP.  and local patching\n                                          is possible\nValidate command execution      Success   Validated command execution\n\n__ORACHK__\nRunning orachk                  Failed    DCS-10702 - ORAchk validation failed:\n                                          .\nValidate command execution      Success   Validated command execution\nVerify the Fast Recovery Area   Failed    AHF-2929: FRA space management\n(FRA) has reclaimable space               problem file types are present\n                                          without an RMAN backup completion\n                                          within the last 7 days<\/code><\/pre>\n\n\n\n<p>I need to fix 2 problems. The first one is a bug that appeared in 19.29, let&#8217;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&#8217;re currently using (19.29 in my case).<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>su - oracle\nunzip -d \/home\/oracle \/opt\/dbi\/p38854064_1929000DBRU_Linux-x86-64.zip\nArchive:  \/opt\/dbi\/p38854064_1929000DBRU_Linux-x86-64.zip\n   creating: \/home\/oracle\/38854064\/\n   creating: \/home\/oracle\/38854064\/files\/\n   creating: \/home\/oracle\/38854064\/files\/lib\/\n   creating: \/home\/oracle\/38854064\/files\/lib\/libserver19.a\/\n  inflating: \/home\/oracle\/38854064\/files\/lib\/libserver19.a\/kjfc.o\n  inflating: \/home\/oracle\/38854064\/README.txt\n   creating: \/home\/oracle\/38854064\/etc\/\n   creating: \/home\/oracle\/38854064\/etc\/config\/\n  inflating: \/home\/oracle\/38854064\/etc\/config\/inventory.xml\n  inflating: \/home\/oracle\/38854064\/etc\/config\/actions.xml\n  inflating: \/home\/oracle\/PatchSearch.xml<\/code><\/pre>\n\n\n\n<p>Let&#8217;s stop the database and apply this patch:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. oraenv &lt;&lt;&lt; CPROD19\nsrvctl stop database -db CPROD19_S1\n\ncd 38854064\n$ORACLE_HOME\/OPatch\/opatch apply\nOracle Interim Patch Installer version 12.2.0.1.47\nCopyright (c) 2026, Oracle Corporation.  All rights reserved.\n\n\nOracle Home       : \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9\nCentral Inventory : \/u01\/app\/oraInventory\n   from           : \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9\/oraInst.loc\nOPatch version    : 12.2.0.1.47\nOUI version       : 12.2.0.7.0\nLog file location : \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9\/cfgtoollogs\/opatch\/opatch2026-02-26_14-29-22PM_1.log\n\nVerifying environment and performing prerequisite checks...\nOPatch continues with these patches:   38854064\n\nDo you want to proceed? &#091;y|n]\ny\nUser Responded with: Y\nAll checks passed.\n\nPlease shutdown Oracle instances running out of this ORACLE_HOME on the local system.\n(Oracle Home = '\/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9')\n\n\nIs the local system ready for patching? &#091;y|n]\ny\nUser Responded with: Y\nBacking up files...\nApplying interim patch '38854064' to OH '\/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9'\n\nPatching component oracle.rdbms, 19.0.0.0.0...\nPatch 38854064 successfully applied.\nLog file location: \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9\/cfgtoollogs\/opatch\/opatch2026-02-26_14-29-22PM_1.log\n\nOPatch succeeded.\n\nsrvctl start database -db CPROD19_S1<\/code><\/pre>\n\n\n\n<p>Second problem is because my database doesn&#8217;t have a proper backup strategy, let&#8217;s then remove the useless archivelogs:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rman target \/\ndelete force noprompt archivelog all;\nexit;\nexit\n<\/code><\/pre>\n\n\n\n<p>Now let&#8217;s retry the precheck:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli create-prepatchreport -d -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb -v 19.30.0.0.0\n\nodacli describe-prepatchreport -i b932011d-cfcf-402d-901e-5c7eac888f1f\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  b932011d-cfcf-402d-901e-5c7eac888f1f\n            Description:  Patch pre-checks for &#091;DB, RHPDB, ORACHKDB] to 19.30.0.0.0: DbHome is OraDB19000_home9\n                 Status:  FAILED\n                Created:  February 26, 2026 3:01:14 PM CET\n                 Result:  One or more pre-checks failed for &#091;ORACHK, DB]\n\nNode Name\n---------------\ndbioda01\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__DB__\nValidate data corruption in     Failed    DCS-10315 - Patch described in My\npatching                                  Oracle Support Note KB867473 must be\n                                          applied.\nValidate DB Home ID             Success   Validated DB Home ID:\n                                          57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\nValidate patching tag           Success   Validated patching tag: 19.30.0.0.0.\nIs system provisioned           Success   Verified system is provisioned\nValidate minimum agent version  Success   Validated minimum agent version\nIs GI upgraded                  Success   Validated GI is upgraded\nValidate available space for    Success   Validated free space required under\ndb                                        \/u01\nValidate there is usable        Success   Successfully validated Oracle Base\nspace under oracle base                   usable space\nValidate glogin.sql file        Success   Successfully verified glogin.sql\n                                          won't break patching\nValidate dbHomesOnACFS          Success   User has configured disk group for\nconfigured                                Database homes on ACFS\nValidate Oracle base            Success   Successfully validated Oracle Base\nIs DB clone available           Success   Successfully validated clone file\n                                          exists\nValidate command execution      Success   Validated command execution\n\n__RHPDB__\nEvaluate DBHome patching with   Success   Successfully validated updating\nRHP                                       dbhome with RHP.  and local patching\n                                          is possible\nValidate command execution      Success   Validated command execution\n\n__ORACHK__\nRunning orachk                  Failed    DCS-10702 - ORAchk validation failed:\n                                          .\nValidate command execution      Success   Validated command execution\nVerify the Fast Recovery Area   Failed    AHF-2929: FRA space management\n(FRA) has reclaimable space               problem file types are present\n                                          without an RMAN backup completion\n                                          within the last 7 days<\/code><\/pre>\n\n\n\n<p>This view doesn&#8217;t look updated, and the ODA documentation tells us that updating the DB home will need to be forced, let&#8217;s do that:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-dbhome -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb -v 19.30.0.0.0 --force\n\nsleep 600;  odacli describe-job -i \"bd511055-7a35-45b4-b9f2-3a003c7ecb31\"\nJob details\n----------------------------------------------------------------\n                     ID:  bd511055-7a35-45b4-b9f2-3a003c7ecb31\n            Description:  DB Home Patching to 19.30.0.0.0: Home ID is 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\n                 Status:  Success\n                Created:  February 26, 2026 15:08:46 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nCreating wallet for DB Client            February 26, 2026 15:09:33 CET           February 26, 2026 15:09:33 CET           Success\nPatch databases by RHP - &#091;CPROD19]       February 26, 2026 15:09:33 CET           February 26, 2026 15:16:44 CET           Success\nUpdating database metadata               February 26, 2026 15:16:44 CET           February 26, 2026 15:16:44 CET           Success\nUpgrade pwfile to 12.2                   February 26, 2026 15:16:44 CET           February 26, 2026 15:16:47 CET           Success\nSet log_archive_dest for Database        February 26, 2026 15:16:47 CET           February 26, 2026 15:16:50 CET           Success\nPopulate PDB metadata                    February 26, 2026 15:16:51 CET           February 26, 2026 15:16:52 CET           Success\nGenerating and saving BOM                February 26, 2026 15:16:52 CET           February 26, 2026 15:17:33 CET           Success\nTDE parameter update                     February 26, 2026 15:18:06 CET           February 26, 2026 15:18:06 CET           Success<\/code><\/pre>\n\n\n\n<p>Everything is now OK.<\/p>\n\n\n\n<p>Let&#8217;s check the DB homes and databases:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\nd3b5fa9c-ad85-46c3-b11a-cd264978b653     OraDB19000_home10    19.30.0.0.260120     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_10    CONFIGURED\n57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb     OraDB19000_home9     19.29.0.0.251021     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9     CONFIGURED\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID\n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n976a80f2-4653-469f-8cd4-ddc1a21aff51     CPROD19    SI       19.30.0.0.260120     true    OLTP     EE       odb8     ASM      CONFIGURED   d3b5fa9c-ad85-46c3-b11a-cd264978b653<\/code><\/pre>\n\n\n\n<p>Let&#8217;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:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>tar czf \/backup\/`hostname -s`_dbhome_9.tgz \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_9\n\nodacli delete-dbhome -i 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\nsleep 40 ; odacli describe-job -i 4589a4d7-6986-4e16-818c-78d585f44443\nJob details\n----------------------------------------------------------------\n                     ID:  4589a4d7-6986-4e16-818c-78d585f44443\n            Description:  Database Home OraDB19000_home9 Deletion with ID 57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\n                 Status:  Success\n                Created:  February 26, 2026 15:24:44 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nSetting up SSH equivalence               February 26, 2026 15:24:44 CET           February 26, 2026 15:24:44 CET           Success\nSetting up SSH equivalence               February 26, 2026 15:24:44 CET           February 26, 2026 15:24:44 CET           Success\nValidate DB Home                         February 26, 2026 15:24:44 CET           February 26, 2026 15:24:44 CET           Success\n57c0dd7f-dcf4-4a38-9e79-4bf8c78e81bb\nfor deletion\nDeleting DB Home by RHP                  February 26, 2026 15:24:45 CET           February 26, 2026 15:25:21 CET           Success<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-cleanse-the-old-patches\">Cleanse the old patches<\/h2>\n\n\n\n<p>Let&#8217;s remove the previous patch from the repository:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli cleanup-patchrepo -comp all -v 19.29.0.0.0\n\nodacli describe-job -i \"a9e29414-8f12-4b55-a6d4-9ad82e9a4c74\"\nJob details\n----------------------------------------------------------------\n                     ID:  a9e29414-8f12-4b55-a6d4-9ad82e9a4c74\n            Description:  Cleanup patchrepos\n                 Status:  Success\n                Created:  February 26, 2026 15:29:46 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nCleanup Repository                       February 26, 2026 15:29:46 CET           February 26, 2026 15:29:47 CET           Success\nCleanup old ASR rpm                      February 26, 2026 15:29:47 CET           February 26, 2026 15:29:47 CET           Success\n<\/code><\/pre>\n\n\n\n<p>Old GI binaries are still using space in \/u01, it&#8217;s better to remove them manually:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>du -hs \/u01\/app\/19.*\n14G\t\/u01\/app\/19.29.0.0\n14G\t\/u01\/app\/19.30.0.0\n\nrm -rf \/u01\/app\/19.29.0.0<\/code><\/pre>\n\n\n\n<p>I would recommend doing a reboot to check if everything run fine. But let&#8217;s first check the components:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-component\nSystem Version\n--------------\n19.30.0.0.0\n\nSystem Node Name\n----------------\ndbioda01\n\nLocal System Version\n--------------------\n19.30.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                      19.30.0.0.0          up-to-date\n\nGI                                       19.30.0.0.260120     up-to-date\n\nDB {\n     OraDB19000_home10                   19.30.0.0.260120     up-to-date\n     &#091;CPROD19]\n}\n\nDCSCONTROLLER                            19.30.0.0.0          up-to-date\n\nDCSCLI                                   19.30.0.0.0          up-to-date\n\nDCSAGENT                                 19.30.0.0.0          up-to-date\n\nDCSADMIN                                 19.30.0.0.0          up-to-date\n\nOS                                       8.10                 up-to-date\n\nILOM                                     5.1.5.29.r167438     up-to-date\n\nBIOS                                     52170100             up-to-date\n\nLOCAL CONTROLLER FIRMWARE {\n     &#091;c4]                                8000D9AB             up-to-date\n}\n\nSHARED CONTROLLER FIRMWARE {\n     &#091;c0, c1]                            VDV1RL06             up-to-date\n}\n\nLOCAL DISK FIRMWARE {\n     &#091;c2d0, c2d1]                        XC311132             up-to-date\n}\n\nHMP                                      2.4.10.1.600         up-to-date\n\nreboot\n...\n\nps -ef | grep pmon\ngrid      8292     1  0 15:37 ?        00:00:00 asm_pmon_+ASM1\ngrid     11539     1  0 15:37 ?        00:00:00 apx_pmon_+APX1\noracle   20494     1  0 15:38 ?        00:00:00 ora_pmon_CPROD19\nroot     23559 23363  0 15:39 pts\/1    00:00:00 grep --color=auto pmon<\/code><\/pre>\n\n\n\n<p>Everything is fine.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-post-patching-tasks\">Post-patching tasks<\/h2>\n\n\n\n<p>Dont&#8217; forget these post-patching tasks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>remove the ODABR snapshots<\/li>\n\n\n\n<li>add your additional RPMs<\/li>\n\n\n\n<li>put back your profile scripts for grid and oracle users<\/li>\n\n\n\n<li>check if monitoring still works<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>\/opt\/odabr\/odabr infosnap\n\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n odabr - ODA node Backup Restore - Version: 2.0.2-06\n Copyright 2013, 2025, Oracle and\/or its affiliates.\n --------------------------------------------------------\n RACPack, Cloud Innovation and Solution Engineering Team\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n\n\nLVM snap name         status                COW Size              Data%\n-------------         ----------            ----------            ------\nroot_snap             active                30.00 GiB             6.08%\nopt_snap              active                70.00 GiB             11.41%\nu01_snap              active                60.00 GiB             25.30%\n\n\/opt\/odabr\/odabr delsnap\n\nINFO: 2026-02-26 15:39:47: Please check the logfile '\/opt\/odabr\/out\/log\/odabr_23962.log' for more details\n\n\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n odabr - ODA node Backup Restore - Version: 2.0.2-06\n Copyright 2013, 2025, Oracle and\/or its affiliates.\n --------------------------------------------------------\n RACPack, Cloud Innovation and Solution Engineering Team\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\n\nINFO: 2026-02-26 15:39:47: Removing LVM snapshots\nINFO: 2026-02-26 15:39:47: ...removing LVM snapshot for 'opt'\nSUCCESS: 2026-02-26 15:39:48: ...snapshot for 'opt' removed successfully\nINFO: 2026-02-26 15:39:48: ...removing LVM snapshot for 'u01'\nSUCCESS: 2026-02-26 15:39:48: ...snapshot for 'u01' removed successfully\nINFO: 2026-02-26 15:39:48: ...removing LVM snapshot for 'root'\nSUCCESS: 2026-02-26 15:39:48: ...snapshot for 'root' removed successfully\nSUCCESS: 2026-02-26 15:39:48: LVM snapshots removed successfully<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-patching-the-db-system\">Patching the DB System<\/h2>\n\n\n\n<p>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&#8217;re using 26ai, you first need to register the new clones in the repository before connecting to your DB System:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/opt\/dbi\/odacli-dcs-23.26.1.0.0-260211-GI-23.26.1.0.zip\nsleep 30 ; odacli describe-job -i 8612ef6a-7df4-419d-8d05-176e11126f48\n\nJob details\n----------------------------------------------------------------\n                     ID:  8612ef6a-7df4-419d-8d05-176e11126f48\n            Description:  Repository Update\n                 Status:  Success\n                Created:  February 26, 2026 15:44:00 CET\n                Message:  \/opt\/dbi\/odacli-dcs-23.26.1.0.0-260211-GI-23.26.1.0.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nUnzip bundle                             February 26, 2026 15:44:00 CET           February 26, 2026 15:44:13 CET           Success\n\n\nodacli update-repository -f \/opt\/dbi\/odacli-dcs-23.26.1.0.0-260211-DB-23.26.1.0.zip\nsleep 30 ; odacli describe-job -i 9dd624f2-9048-4897-b63b-400b955c803c\n\nJob details\n----------------------------------------------------------------\n                     ID:  9dd624f2-9048-4897-b63b-400b955c803c\n            Description:  Repository Update\n                 Status:  Success\n                Created:  February 26, 2026 15:45:12 CET\n                Message:  \/opt\/dbi\/odacli-dcs-23.26.1.0.0-260211-DB-23.26.1.0.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nUnzip bundle                             February 26, 2026 15:45:12 CET           February 26, 2026 15:45:40 CET           Success\n\nodacli update-repository -f \/opt\/dbi\/oda-sm-23.26.1.0.0-260211-server.zip\nsleep 20 ; odacli describe-job -i 6a24023f-de2e-4481-b9c4-d8511d54be48\n\nJob details\n----------------------------------------------------------------\n                     ID:  6a24023f-de2e-4481-b9c4-d8511d54be48\n            Description:  Repository Update\n                 Status:  Success\n                Created:  February 26, 2026 15:59:07 CET\n                Message:  \/opt\/dbi\/oda-sm-23.26.1.0.0-260211-server.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nUnzip bundle                             February 26, 2026 15:59:08 CET           February 26, 2026 15:59:30 CET           Success\n\nodacli list-availablepatches\n-------------------- ------------------------- ------------------------- ------------------------------\nODA Release Version  Supported DB Versions     Available DB Versions     Supported Platforms\n-------------------- ------------------------- ------------------------- ------------------------------\n19.30.0.0.0          23.26.1.0.0               23.26.1.0.0               DB System\n                     21.8.0.0.221018           Clone not available       DB System\n                     19.30.0.0.260120          19.30.0.0.260120          DB System, Bare Metal<\/code><\/pre>\n\n\n\n<p>Applying the patch is done the same way you&#8217;ve done it on bare metal, but here you need to specify the 23.26.1.0.0 version:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh dbs-04-tst\n\nodacli update-dcsadmin -v 23.26.1.0.0\n\nsleep 60 ; odacli describe-job -i 4b83ab57-ccb1-4f9f-8c70-572b45ada49b\n\nJob details\n----------------------------------------------------------------\n                     ID:  4b83ab57-ccb1-4f9f-8c70-572b45ada49b\n            Description:  DcsAdmin patching to 23.26.1.0.0\n                 Status:  Success\n                Created:  March 05, 2026 10:07:44 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nDcs-admin upgrade                        March 05, 2026 10:07:45 CET              March 05, 2026 10:07:59 CET              Success\nPing DCS Admin                           March 05, 2026 10:07:59 CET              March 05, 2026 10:09:07 CET              Success\n\nsleep 30 ;  odacli update-dcscomponents -v 23.26.1.0.0\n{\n  \"jobId\" : \"cb674b3e-d6eb-4351-be39-0f19b8c56f9d\",\n  \"status\" : \"Success\",\n  \"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 \",\n  \"reports\" : null,\n  \"createTimestamp\" : \"March 05, 2026 10:10:13 AM CET\",\n  \"description\" : \"Update-dcscomponents job completed and is not part of Agent job list\",\n  \"updatedTime\" : \"March 05, 2026 10:18:38 AM CET\",\n  \"jobType\" : null,\n  \"externalRequestId\" : null,\n  \"action\" : null\n}\n\nodacli describe-admin-job -i cb674b3e-d6eb-4351-be39-0f19b8c56f9d\nodacli: 'describe-admin-job' is not an odacli command.\nusage: odacli\t&#091;-h\/--help]\n\t\t&lt;category&gt; &#091;-h\/--help]\n\t\t&lt;operation&gt; &#091;-h\/--help]\n\t\t&lt;command&gt; &#091;-h\/--help]\n\t\t&lt;command&gt; &#091;&lt;args&gt;]\n<\/code><\/pre>\n\n\n\n<p>Note that there is no describe-admin-job feature on DB Systems.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli create-prepatchreport -sc -v 23.26.1.0.0\n\nsleep 20 ; odacli describe-prepatchreport -i 1b104d06-bc0c-45b8-ab25-b5b6a102a857\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  1b104d06-bc0c-45b8-ab25-b5b6a102a857\n            Description:  Patch pre-checks for &#091;OS, ORACHKSERVER, SERVER] to 23.26.1.0.0\n                 Status:  SUCCESS\n                Created:  March 05, 2026 10:59:34 CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbs-04-tst\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__OS__\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 23.26.1.0.0.\nIs patch location available     Success   Patch location is available.\nVerify All OS patches           Success   No dependencies found for RPMs being\n                                          removed, updated and installed. Check\n                                          \/opt\/oracle\/dcs\/log\/jobfiles\/\n                                          dnfdryrunout_2026-03-05_10-59-\n                                          50.0718_832.log file for more details\nValidate there is usable        Success   Successfully validated\nspace under repo volume                   \/opt\/oracle\/dcs\/repo usable space\nValidate command execution      Success   Validated command execution\n\n__ORACHK__\nRunning orachk                  Success   Successfully ran Orachk\nValidate command execution      Success   Validated command execution\n\n__SERVER__\nValidate local patching         Success   Successfully validated server local\n                                          patching\nValidate all KVM ACFS           Success   All KVM ACFS resources are running\nresources are running\nValidate DB System VM states    Success   All DB System VMs states are expected\nEnable support for Multi-DB     Success   No need to convert the DB System\nValidate DB System AFD state    Success   AFD is not configured\nValidate there is usable        Success   Successfully validated\nspace under repo volume                   \/opt\/oracle\/dcs\/repo usable space\nValidate command execution      Success   Validated command execution\n\n\nodacli update-servercomponents -v 23.26.1.0.0\n<\/code><\/pre>\n\n\n\n<p>The DB System will reboot.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-job -i 2b4da73a-7f64-48e0-af76-a1d687a0169f\n\nJob details\n----------------------------------------------------------------\n                     ID:  2b4da73a-7f64-48e0-af76-a1d687a0169f\n            Description:  Server Patching to 23.26.1.0.0\n                 Status:  Success\n                Created:  March 05, 2026 11:04:19 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nDeactivate Unit&#091;dnf-makecache.timer]     March 05, 2026 11:04:21 CET              March 05, 2026 11:04:21 CET              Success\nValidating GI user metadata              March 05, 2026 11:04:21 CET              March 05, 2026 11:04:21 CET              Success\nDeactivate Unit&#091;kdump.service]           March 05, 2026 11:04:22 CET              March 05, 2026 11:04:23 CET              Success\nModify DBVM udev rules                   March 05, 2026 11:04:23 CET              March 05, 2026 11:04:34 CET              Success\nCreating local repository                March 05, 2026 11:04:34 CET              March 05, 2026 11:04:37 CET              Success\nOSPatchBaseRepo\nUpdating versionlock plugin              March 05, 2026 11:04:37 CET              March 05, 2026 11:04:41 CET              Success\nApplying OS Patches                      March 05, 2026 11:04:41 CET              March 05, 2026 11:07:33 CET              Success\nCreating local repository HMPPatchRepo   March 05, 2026 11:07:34 CET              March 05, 2026 11:07:34 CET              Success\nApplying HMP Patches                     March 05, 2026 11:07:35 CET              March 05, 2026 11:07:38 CET              Success\nPatch location validation                March 05, 2026 11:07:39 CET              March 05, 2026 11:07:39 CET              Success\nSetting SELinux mode                     March 05, 2026 11:07:39 CET              March 05, 2026 11:07:39 CET              Success\nOda-hw-mgmt upgrade                      March 05, 2026 11:07:40 CET              March 05, 2026 11:08:08 CET              Success\nInstalling SQLcl software                March 05, 2026 11:08:08 CET              March 05, 2026 11:08:13 CET              Success\nCleanup JRE Home                         March 05, 2026 11:08:14 CET              March 05, 2026 11:08:14 CET              Success\nGenerating and saving BOM                March 05, 2026 11:08:17 CET              March 05, 2026 11:08:24 CET              Success\nUpdate System full patch version         March 05, 2026 11:08:17 CET              March 05, 2026 11:08:17 CET              Success\nUpdate System rebootless patch version   March 05, 2026 11:08:17 CET              March 05, 2026 11:08:17 CET              Success\nPreRebootNode Actions                    March 05, 2026 11:08:24 CET              March 05, 2026 11:08:25 CET              Success\nReboot Node                              March 05, 2026 11:08:25 CET              March 05, 2026 11:09:59 CET              Success\n\nodacli create-prepatchreport -gi -v 23.26.1.0.0\n\nsleep 240 ; odacli describe-prepatchreport -i dd5d216b-d1bc-44cf-bcf8-381da0729469\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  dd5d216b-d1bc-44cf-bcf8-381da0729469\n            Description:  Patch pre-checks for &#091;RHPGI, GI] to 23.26.1.0.0\n                 Status:  SUCCESS\n                Created:  March 05, 2026 11:13:21 CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbs-04-tst\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__RHPGI__\nValidate available space        Success   Validated free space under \/u01\nEvaluate GI patching            Success   Successfully validated GI patching\nValidate there is usable        Success   Successfully validated\nspace under repo volume                   \/opt\/oracle\/dcs\/repo usable space\nValidate command execution      Success   Validated command execution\n\n__GI__\nValidate GI metadata            Success   Successfully validated GI metadata\nValidate supported GI versions  Success   Successfully validated minimum version\nValidate there is usable        Success   Successfully validated\nspace under repo volume                   \/opt\/oracle\/dcs\/repo usable space\nIs clusterware running          Success   Clusterware is running\nValidate patching tag           Success   Validated patching tag: 23.26.1.0.0.\nIs system provisioned           Success   Verified system is provisioned\nValidate BM versions            Success   Validated BM server components\n                                          versions\nValidate kernel log level       Success   Successfully validated the OS log\n                                          level\nValidate Central Inventory      Success   oraInventory validation passed\nValidate patching locks         Success   Validated patching locks\nValidate clones location exist  Success   Validated clones location\nValidate command execution      Success   Validated command execution\n\n\nodacli update-gihome -v 23.26.1.0.0\n\nsleep 600 ; odacli describe-job -i c93f84fc-5cb2-41bb-9f23-f7ce22b9f5de\n\nJob details\n----------------------------------------------------------------\n                     ID:  c93f84fc-5cb2-41bb-9f23-f7ce22b9f5de\n            Description:  Patch GI with RHP to 23.26.1.0.0\n                 Status:  Success\n                Created:  March 05, 2026 11:22:47 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nPatch GI with RHP to 23.26.1.0.0         March 05, 2026 11:22:59 CET              March 05, 2026 11:27:54 CET              Success\nStarting the clusterware                 March 05, 2026 11:22:59 CET              March 05, 2026 11:22:59 CET              Success\nCreating GI home directories             March 05, 2026 11:23:01 CET              March 05, 2026 11:23:01 CET              Success\nExtract GI clone                         March 05, 2026 11:23:01 CET              March 05, 2026 11:23:01 CET              Success\nProvisioning Software Only GI with RHP   March 05, 2026 11:23:01 CET              March 05, 2026 11:23:01 CET              Success\nRegistering image                        March 05, 2026 11:23:01 CET              March 05, 2026 11:23:01 CET              Success\nRegistering image                        March 05, 2026 11:23:01 CET              March 05, 2026 11:23:01 CET              Success\nRegistering working copy                 March 05, 2026 11:23:01 CET              March 05, 2026 11:23:01 CET              Success\nPatch GI with RHP                        March 05, 2026 11:23:47 CET              March 05, 2026 11:26:58 CET              Success\nSet CRS ping target                      March 05, 2026 11:26:58 CET              March 05, 2026 11:26:59 CET              Success\nUpdating .bashrc                         March 05, 2026 11:26:59 CET              March 05, 2026 11:26:59 CET              Success\nUpdating GI home metadata                March 05, 2026 11:26:59 CET              March 05, 2026 11:27:00 CET              Success\nUpdating GI home version                 March 05, 2026 11:27:00 CET              March 05, 2026 11:27:04 CET              Success\nUpdating All DBHome version              March 05, 2026 11:27:04 CET              March 05, 2026 11:27:08 CET              Success\nPatch DB System on BM                    March 05, 2026 11:27:48 CET              March 05, 2026 11:27:54 CET              Success\nStarting the clusterware                 March 05, 2026 11:27:48 CET              March 05, 2026 11:27:48 CET              Success\n\n\nodacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\n9116603b-3b5e-4e92-aa63-baad8ae1d6a8     OraDB23000_home1     23.26.0.0.0          EE         \/u01\/app\/oracle\/product\/23.0.0.0\/dbhome_1                CONFIGURED\n\nodacli create-prepatchreport -d -i 9116603b-3b5e-4e92-aa63-baad8ae1d6a8 -v 23.26.1.0.0\n\nsleep 600 ;  odacli describe-prepatchreport -i bb16e390-3dcb-4ea0-b8c5-0c22f38ba271\n\nodacli describe-prepatchreport -i bb16e390-3dcb-4ea0-b8c5-0c22f38ba271\n\nPrepatch Report\n------------------------------------------------------------------------\n                 Job ID:  bb16e390-3dcb-4ea0-b8c5-0c22f38ba271\n            Description:  Patch pre-checks for &#091;DB, RHPDB, ORACHKDB] to 23.26.1.0.0: DbHome is OraDB23000_home1\n                 Status:  FAILED\n                Created:  March 05, 2026 11:59:29 CET\n                 Result:  One or more pre-checks failed for &#091;ORACHK]\n\nNode Name\n---------------\ndbs-04-tst\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__DB__\nValidate DB Home ID             Success   Validated DB Home ID:\n                                          9116603b-3b5e-4e92-aa63-baad8ae1d6a8\nValidate patching tag           Success   Validated patching tag: 23.26.1.0.0.\nIs system provisioned           Success   Verified system is provisioned\nValidate minimum agent version  Success   Validated minimum agent version\nIs GI upgraded                  Success   Validated GI is upgraded\nValidate available space for    Success   Validated free space required under\ndb                                        \/u01\nValidate there is usable        Success   Successfully validated Oracle Base\nspace under oracle base                   usable space\nValidate glogin.sql file        Success   Successfully verified glogin.sql\n                                          won't break patching\nIs DB clone available           Success   Successfully validated clone file\n                                          exists\nValidate command execution      Success   Validated command execution\n\n__RHPDB__\nEvaluate DBHome patching with   Success   Successfully validated updating\nRHP                                       dbhome with RHP.  and local patching\n                                          is possible\nValidate command execution      Success   Validated command execution\n\n__ORACHK__\nRunning orachk                  Failed    DCS-10702 - ORAchk validation failed:\n                                          .\nValidate command execution      Success   Validated command execution\nVerify the Fast Recovery Area   Failed    AHF-2929: FRA space management\n(FRA) has reclaimable space               problem file types are present\n                                          without an RMAN backup completion\n                                          within the last 7 days<\/code><\/pre>\n\n\n\n<p>The 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:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-dbhome -i 9116603b-3b5e-4e92-aa63-baad8ae1d6a8 -v 23.26.1.0.0 -f\n\nsleep 1200 ; odacli describe-job -i 4fc89556-2f7c-4e5b-a12f-55e32d7e748a\n\nJob details\n----------------------------------------------------------------\n                     ID:  4fc89556-2f7c-4e5b-a12f-55e32d7e748a\n            Description:  DB Home Patching to 23.26.1.0.0: Home ID is 9116603b-3b5e-4e92-aa63-baad8ae1d6a8\n                 Status:  Success\n                Created:  March 05, 2026 13:36:42 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nCreating wallet for DB Client            March 05, 2026 13:37:21 CET              March 05, 2026 13:37:21 CET              Success\nPatch databases by RHP - &#091;CTEST26]       March 05, 2026 13:37:21 CET              March 05, 2026 13:54:26 CET              Success\nUpdating database metadata               March 05, 2026 13:54:26 CET              March 05, 2026 13:54:27 CET              Success\nUpgrade pwfile to 12.2                   March 05, 2026 13:54:27 CET              March 05, 2026 13:54:32 CET              Success\nSet log_archive_dest for Database        March 05, 2026 13:54:32 CET              March 05, 2026 13:54:37 CET              Success\nPopulate PDB metadata                    March 05, 2026 13:54:38 CET              March 05, 2026 13:54:39 CET              Success\nGenerating and saving BOM                March 05, 2026 13:54:39 CET              March 05, 2026 13:55:08 CET              Success\nTDE parameter update                     March 05, 2026 13:55:44 CET              March 05, 2026 13:55:44 CET              Success\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID\n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n276bf458-db09-4c9a-9cd9-a821e5274fb0     CTEST26    SI       23.26.1.0.0          true    OLTP     EE       odb2     ASM      CONFIGURED   9c51039d-ccba-4508-b879-a81b8c18d46a\n\nodacli delete-dbhome -i 9116603b-3b5e-4e92-aa63-baad8ae1d6a8\nsleep 100 ; odacli describe-job -i 0994b96e-e174-4776-8699-f179c1d89af0\n\nJob details\n----------------------------------------------------------------\n                     ID:  0994b96e-e174-4776-8699-f179c1d89af0\n            Description:  Database Home OraDB23000_home1 Deletion with ID 9116603b-3b5e-4e92-aa63-baad8ae1d6a8\n                 Status:  Success\n                Created:  March 05, 2026 13:58:36 CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------------\nSetting up SSH equivalence               March 05, 2026 13:58:36 CET              March 05, 2026 13:58:36 CET              Success\nSetting up SSH equivalence               March 05, 2026 13:58:36 CET              March 05, 2026 13:58:37 CET              Success\nValidate DB Home                         March 05, 2026 13:58:36 CET              March 05, 2026 13:58:36 CET              Success\n9116603b-3b5e-4e92-aa63-baad8ae1d6a8\nfor deletion\nDeleting DB Home by RHP                  March 05, 2026 13:58:38 CET              March 05, 2026 13:59:15 CET              Success\n\nodacli describe-component\nSystem Version\n--------------\n23.26.1.0.0\n\nSystem Node Name\n----------------\ndbs-04-tst\n\nLocal System Version\n--------------------\n23.26.1.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                      23.26.1.0.0          up-to-date\n\nGI                                       23.26.1.0.0          up-to-date\n\nDB {\n     OraDB23000_home2                    23.26.1.0.0          up-to-date\n     &#091;CTEST26]\n}\n\nDCSCONTROLLER                            23.26.1.0.0          up-to-date\n\nDCSCLI                                   23.26.1.0.0          up-to-date\n\nDCSAGENT                                 23.26.1.0.0          up-to-date\n\nDCSADMIN                                 23.26.1.0.0          up-to-date\n\nOS                                       8.10                 up-to-date\n<\/code><\/pre>\n\n\n\n<p>Finally, let&#8217;s remove obsolete GI binaries:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>du -hs \/u01\/app\/23.26.*\n3.9G\t\/u01\/app\/23.26.0.0\n3.6G\t\/u01\/app\/23.26.1.0\n\nrm -rf \/u01\/app\/23.26.0.0\/<\/code><\/pre>\n\n\n\n<p>Don&#8217;t forget to apply this procedure to the other DB Systems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-conclusion\">Conclusion<\/h2>\n\n\n\n<p>Applying this patch is OK, as soon as everything is clean and under control. When patching, only use the force option when you&#8217;re sure that you know what you&#8217;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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction Patch 19.30 is now available for Oracle Database Appliance series. Let&#8217;s find out what&#8217;s new and how to apply this patch. What&#8217;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, [&hellip;]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[3804,2567,2568,1923,3081,3079,3663,1698,1699,2682,2429],"type_dbi":[],"class_list":["post-43377","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-26ai","tag-oda-2","tag-oracle-database-appliance-2","tag-update","tag-x10-ha","tag-x10-s","tag-x11-ha","tag-x8-2m","tag-x8-2s","tag-x9-2l","tag-x9-2s"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>How to patch your ODA to 19.30? - dbi Blog<\/title>\n<meta name=\"description\" content=\"This is how to apply patch 19.30 on your Oracle Database Appliance X11, X10-2, X9-2 and X8-2\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to patch your ODA to 19.30?\" \/>\n<meta property=\"og:description\" content=\"This is how to apply patch 19.30 on your Oracle Database Appliance X11, X10-2, X9-2 and X8-2\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-06T15:10:54+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-10T09:26:54+00:00\" \/>\n<meta name=\"author\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"How to patch your ODA to 19.30?\",\"datePublished\":\"2026-03-06T15:10:54+00:00\",\"dateModified\":\"2026-03-10T09:26:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\"},\"wordCount\":1324,\"commentCount\":0,\"keywords\":[\"26ai\",\"oda\",\"oracle database appliance\",\"update\",\"x10-ha\",\"x10-s\",\"X11-HA\",\"x8-2m\",\"x8-2s\",\"X9-2L\",\"X9-2S\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\",\"name\":\"How to patch your ODA to 19.30? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2026-03-06T15:10:54+00:00\",\"dateModified\":\"2026-03-10T09:26:54+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"description\":\"This is how to apply patch 19.30 on your Oracle Database Appliance X11, X10-2, X9-2 and X8-2\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to patch your ODA to 19.30?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\",\"name\":\"J\u00e9r\u00f4me Dubar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"caption\":\"J\u00e9r\u00f4me Dubar\"},\"description\":\"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How to patch your ODA to 19.30? - dbi Blog","description":"This is how to apply patch 19.30 on your Oracle Database Appliance X11, X10-2, X9-2 and X8-2","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/","og_locale":"en_US","og_type":"article","og_title":"How to patch your ODA to 19.30?","og_description":"This is how to apply patch 19.30 on your Oracle Database Appliance X11, X10-2, X9-2 and X8-2","og_url":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/","og_site_name":"dbi Blog","article_published_time":"2026-03-06T15:10:54+00:00","article_modified_time":"2026-03-10T09:26:54+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"How to patch your ODA to 19.30?","datePublished":"2026-03-06T15:10:54+00:00","dateModified":"2026-03-10T09:26:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/"},"wordCount":1324,"commentCount":0,"keywords":["26ai","oda","oracle database appliance","update","x10-ha","x10-s","X11-HA","x8-2m","x8-2s","X9-2L","X9-2S"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/","url":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/","name":"How to patch your ODA to 19.30? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-03-06T15:10:54+00:00","dateModified":"2026-03-10T09:26:54+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"description":"This is how to apply patch 19.30 on your Oracle Database Appliance X11, X10-2, X9-2 and X8-2","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-30\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to patch your ODA to 19.30?"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd","name":"J\u00e9r\u00f4me Dubar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","caption":"J\u00e9r\u00f4me Dubar"},"description":"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.","url":"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43377","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=43377"}],"version-history":[{"count":6,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43377\/revisions"}],"predecessor-version":[{"id":43424,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43377\/revisions\/43424"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=43377"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=43377"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=43377"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=43377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}