It’s been several weeks that patch 19.19 is available on ODA. And I finally had the possibility to test it.<\/p>\n\n\n\n
This version brings latest PSUs to database and grid homes, with their bug fixes as usual. It also brings latest 21c and 19c DB Systems. You already know that 21c is an innovation release. 23c will be the next long-term release, but it’s not yet available. Oracle recently updated the support timeline accordingly, and 19c is now supported without any additional cost until the first quarter of 2026.<\/p>\n\n\n\n
Not a lot of new features for this version, but some nice additions. Among them, the error correlation between odacli and the subsequent tools directly from the command line. It was reserved for the BUI in the first versions:<\/p>\n\n\n\n
odacli describe-job -i 767bf32e-51fc-46e6-a314-85ce9c053da0 \r\nJob details\r\n----------------------------------------------------------------\r\n ID: 767bf32e-51fc-46e6-a314-85ce9c053da0\r\n Description: Database service creation with db name: DBTEST\r\n Status: Failure (To view Error Correlation report, run \"odacli describe-job -i 767bf32e-51fc-46e6-a314-85ce9c053da0 --ecr\" command)\r\n Created: July 26, 2023 4:22:42 PM CEST\r\n Message: DCS-10001:Internal error encountered: Insufficient disk space for dbShape odb1s.\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nDatabase Service creation July 26, 2023 4:22:42 PM CEST July 26, 2023 4:22:43 PM CEST Failure\r\nDatabase Service creation July 26, 2023 4:22:42 PM CEST July 26, 2023 4:22:43 PM CEST Failure\r\nValidating the required disk space July 26, 2023 4:22:42 PM CEST July 26, 2023 4:22:43 PM CEST Failure\r\n\nodacli describe-job -i 767bf32e-51fc-46e6-a314-85ce9c053da0 --ecr\n...<\/code><\/pre>\n\n\n\nWhich ODA is compatible with this 19.19 release?<\/h2>\n\n\n\n
The newest ODAs X9-2S\/L\/HA are supported, as well as X8, X7 and X6 series. X5-2HA is no longer supported starting from this release, and therefore becomes obsolete. I personally won’t regret it. On one hand, it brought high capacity storage for the ODA series, but on the other hand it was the less performant ODA of the familly with nearline SAS HDDs (7200 rpm) as a transition after 10K SAS HDDs and before SSDs\/NVMes.<\/p>\n\n\n\n
Is this patch a cumulative one?<\/h2>\n\n\n\n
This 19.19 can be applied on top of 19.15 or later. I just applied this new patch on an X6-2M running on 19.8 using 19.12 and 19.16 as intermediate versions.<\/p>\n\n\n\n
Is there also a patch for my databases?<\/h2>\n\n\n\n
Only databases version 19c are supported, and this is OK because this is the only one you should use now. You may use Data Preserving Reprovisioning if you come from a very old version (<=18.8) and want to keep your databases using 11g or 18c for example. I wrote a blog post on this feature several months ago<\/a>.<\/p>\n\n\n\nIf you absolutely need an older release, it should be possible to register an old DB clone belonging to an older patch without any problem. Several weeks ago, I successfully deployed a 12.2 DB home from 19.14 on a new X9-2S running 19.18, but an older 11gR2 didn’t work. If you really need 11gR2, you may configure an application VM on your ODA for that purpose, as <\/a>described<\/a> here<\/a>, but it comes without any guarantee of any kind.<\/p>\n\n\n\nDownload the patch and clone files<\/h2>\n\n\n\n
Download the patch and the corresponding clones to be able to apply the complete patch.<\/p>\n\n\n\n
35290009 => the patch itself
30403673 => the GI clone needed for deploying newer GI version (mandatory)
30403662 => the DB clone for deploying new databases version of 19c<\/p>\n\n\n\n
You don’t need the ISO file for patching, but I would recommend downloading it (patch 30403643).<\/p>\n\n\n\n
Be sure to choose the very latest 19.19 when downloading the clones, download link from MOS will first propose older versions.<\/p>\n\n\n\n
Prepare the patching<\/h2>\n\n\n\n
Before starting, please check these prerequisites:<\/p>\n\n\n\n
\n- filesystems have 20% available free space (does not concern acfs volumes)<\/li>\n\n\n\n
- additional rpms manually installed must be removed<\/li>\n\n\n\n
- revert profile scripts to default’s one (for grid and oracle users)<\/li>\n\n\n\n
- make sure you’ve planned a generous downtime, 4 hours being the bare minimum for patching and troubleshooting. 1 day is never too much. If you need to apply intermediate patches, you will need 4 hours for each jump<\/li>\n\n\n\n
- you may need to remove old kernel version if you already patched multiple time your ODA, I described this in the next chapter<\/li>\n\n\n\n
- I recently included a sanity reboot before patching in my procedure: I strongly recommend it<\/li>\n<\/ul>\n\n\n\n
You should (must) use ODABR to make snapshots of the important filesystems prior patching. It’s fast and it doesn’t cost anything. I would also recommend doing a backup of most important files: tnsnames.ora and listener.ora, database list, network configuration files, aso.<\/p>\n\n\n\n
Clean-up old kernels<\/h2>\n\n\n\n
If you have already patched multiple times your ODA, you may need to clean-up old kernels. Basically, each time an OS patch is applied, a new kernel is installed and it may filled up your \/boot volume:<\/p>\n\n\n\n
df -h \/boot \r\nFilesystem Size Used Avail Use% Mounted on\r\n\/dev\/md126p2 477M 359M 93M 80% \/boot\nuname -a \r\nLinux chlaora01 4.14.35-2047.510.5.4.el7uek.x86_64 #2 SMP Thu Jan 20 09:10:35 PST 2022 x86_64 x86_64 x86_64 GNU\/Linux\n\nrpm -qa | grep kernel-uek-4\r\nkernel-uek-4.14.35-2047.510.5.4.el7uek.x86_64\r\nkernel-uek-4.14.35-2025.404.1.2.el7uek.x86_64\r\nkernel-uek-4.14.35-1902.301.1.el7uek.x86_64<\/code><\/pre>\n\n\n\nIn this example, current kernel is 4.14.35-2047. The 1902 and 2025 kernel headers are not needed anymore. Let’s manually remove the packages:<\/p>\n\n\n\n
rpm -e kernel-uek-4.14.35-1902.301.1.el7uek.x86_64\r\nrpm -e kernel-uek-4.14.35-2025.404.1.2.el7uek.x86_64\r\n\r\ndf -h \/boot\r\nFilesystem Size Used Avail Use% Mounted on\r\n\/dev\/md126p2 477M 153M 300M 34% \/boot<\/code><\/pre>\n\n\n\nFar better, isn’t it?<\/p>\n\n\n\n
Version precheck<\/h2>\n\n\n\n
Start to check current version on all components:<\/p>\n\n\n\n
odacli describe-component\r\nSystem Version\r\n---------------\r\n19.16.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\noda2\r\n\r\nLocal System Version\r\n---------------\r\n19.16.0.0.0\r\n\r\nComponent Installed Version Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK\r\n 19.16.0.0.0 up-to-date\r\nGI\r\n 19.16.0.0.220719 up-to-date\r\nDB {\r\n[OraDB19000_home1 [POSTDT1,PMDT1]]\r\n 19.8.0.0.200714 19.16.0.0.220719\r\n[OraDB11204_home1 [CORIDT2,CORIDV2,\r\nIASDT2,IASIT1,ACTEDT1,SMTEST,IASAT1,\r\nGAIATEST]] 11.2.0.4.200714 not-available\r\n[OraDB12102_home1 [HORUSDT1,ATALDT2,\r\nDELOSDT1,DELOSDT2,SOLISDT1,SOLISDT2]] 12.1.0.2.200114 12.1.0.2.220719\r\n}\r\nDCSCONTROLLER\r\n 19.16.0.0.0 up-to-date\r\nDCSCLI\r\n 19.16.0.0.0 up-to-date\r\nDCSAGENT\r\n 19.16.0.0.0 up-to-date\r\nDCSADMIN\r\n 19.16.0.0.0 up-to-date\r\nOS\r\n 7.9 up-to-date\r\nILOM\r\n 5.1.0.20.r145377 up-to-date\r\nBIOS\r\n 38360300 up-to-date\r\nLOCAL CONTROLLER FIRMWARE {\r\n[c2]\r\n 4.650.00-7176 up-to-date\r\n[c3]\r\n 000161AB up-to-date\r\n[c4]\r\n 800005DD up-to-date\r\n\u2003\r\n[c5]\r\n 800005DE up-to-date\r\n}\r\nSHARED CONTROLLER FIRMWARE\r\n KPYAJR3Q up-to-date\r\nLOCAL DISK FIRMWARE\r\n GXM10R3Q up-to-date\r\nHMP\r\n 2.4.8.9.601 up-to-date<\/code><\/pre>\n\n\n\nOnce the patch will be registered in the ODA repository, the “Available Version” column will be updated with versions provided within the patch.<\/p>\n\n\n\n
Prepararing the patch and backing up the system<\/h2>\n\n\n\n
Copy the patch files to your ODA in a temp directory. On ODA X9-2, system disks are now smaller, so don’t hesitate to put the file on a nfs share or in the FRA acfs volume if you have acfs configured for your databases. Then unzip the files:<\/p>\n\n\n\n
cd \/opt\/oren\nunzip p30403673_1916000_Linux-x86-64.zip\r\nunzip p34376263_1916000_Linux-x86-64.zip\nunzip p30403662_1919000_Linux-x86-64.zip\n\r\nrm p30403673_1916000_Linux-x86-64.zip p34376263_1916000_Linux-x86-64.zip p30403662_1919000_Linux-x86-64.zip<\/code><\/pre>\n\n\n\nIf not yet done, install the latest ODABR from MOS note 2466177.1:<\/p>\n\n\n\n
rpm -ivh odabr-2.0.1-72.noarch.rpm\n<\/code><\/pre>\n\n\n\nCheck free space in the physical volume and choose adequate snapshot size for each of the 3 filesystems. These settings were OK for me:<\/p>\n\n\n\n
pvs\r\n PV VG Fmt Attr PSize PFree\r\n \/dev\/sda2 VolGroupSys lvm2 a-- <439.44g <123.44g\r\n\n\/opt\/odabr\/odabr backup -snap -osize 55 -rsize 15 -usize 40\nINFO: 2023-07-26 14:14:48: Please check the logfile '\/opt\/odabr\/out\/log\/odabr_13988.log' for more details\r\n\r\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\r\n odabr - ODA node Backup Restore - Version: 2.0.1-72\r\n Copyright 2013, 2023, Oracle and\/or its affiliates.\r\n --------------------------------------------------------\r\n Author: Ruggero Citton <ruggero.citton@oracle.com>\r\n RAC Pack, Cloud Innovation and Solution Engineering Team\r\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\r\n\r\nINFO: 2023-07-26 14:14:48: Checking superuser\r\nINFO: 2023-07-26 14:14:48: Checking Bare Metal\r\n\r\nINFO: 2023-07-26 14:14:48: Removing existing LVM snapshots\r\nWARNING: 2023-07-26 14:14:48: LVM snapshot for 'opt' does not exist\r\nWARNING: 2023-07-26 14:14:48: LVM snapshot for 'u01' does not exist\r\n\u2003\r\nWARNING: 2023-07-26 14:14:48: LVM snapshot for 'root' does not exist\r\n\r\nINFO: 2023-07-26 14:14:48: Checking current OS version\r\nINFO: 2023-07-26 14:14:48: Checking LVM restore backgroud process\r\nINFO: 2023-07-26 14:14:48: Checking LVM size\r\n\r\nINFO: 2023-07-26 14:14:48: Boot device backup\r\nINFO: 2023-07-26 14:14:48: Getting EFI device\r\nWARNING: 2023-07-26 14:14:48: Failing checking efi device\r\nINFO: 2023-07-26 14:14:48: ...no EFI device found\r\nINFO: 2023-07-26 14:14:48: Getting boot device\r\nINFO: 2023-07-26 14:14:48: ...step1 - making boot device backup using tar\r\nSUCCESS: 2023-07-26 14:15:06: ...boot content saved as '\/opt\/odabr\/out\/hbi\/boot.tar.gz'\r\nINFO: 2023-07-26 14:15:06: ...step2 - unmounting boot\r\nINFO: 2023-07-26 14:15:06: ...step3 - making boot device backup using dd\r\nSUCCESS: 2023-07-26 14:15:09: ...boot device backup saved as '\/opt\/odabr\/out\/hbi\/boot.img'\r\nINFO: 2023-07-26 14:15:09: ...step4 - mounting boot\r\nINFO: 2023-07-26 14:15:09: ...step5 - checking boot device backup\r\n\r\nINFO: 2023-07-26 14:15:10: Making OCR physical backup\r\nINFO: 2023-07-26 14:15:15: ...ocr backup saved as '\/opt\/odabr\/out\/hbi\/ocrbackup_13988.bck'\r\nSUCCESS: 2023-07-26 14:15:15: OCR physical backup created successfully\r\nINFO: 2023-07-26 14:15:15: OCR export backup\r\nINFO: 2023-07-26 14:15:17: ...ocr export saved as '\/opt\/odabr\/out\/hbi\/ocrexport_13988.bck'\r\nSUCCESS: 2023-07-26 14:15:17: OCR export backup created successfully\r\n\r\nINFO: 2023-07-26 14:15:17: Making LVM snapshot backup\r\nSUCCESS: 2023-07-26 14:15:17: ...snapshot backup for 'opt' created successfully\r\nSUCCESS: 2023-07-26 14:15:18: ...snapshot backup for 'u01' created successfully\r\nSUCCESS: 2023-07-26 14:15:18: ...snapshot backup for 'root' created successfully\r\nSUCCESS: 2023-07-26 14:15:18: LVM snapshots backup done successfully\r\n\r\n\/opt\/odabr\/odabr infosnap\r\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\r\n odabr - ODA node Backup Restore - Version: 2.0.1-72\r\n Copyright 2013, 2023, Oracle and\/or its affiliates.\r\n --------------------------------------------------------\r\n Author: Ruggero Citton <ruggero.citton@oracle.com>\r\n RAC Pack, Cloud Innovation and Solution Engineering Team\r\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\r\n\r\nLVM snap name Status COW Size Data%\r\n------------- ---------- ---------- ------\r\nroot_snap active 15.00 GiB 0.01%\r\nopt_snap active 55.00 GiB 0.01%\r\nu01_snap active 40.00 GiB 0.02%\r\n<\/code><\/pre>\n\n\n\nIf you need to apply multiple patches, I would recommend erasing the snapshots after each patch successfully applied, and creating new ones once patch files are unzipped.<\/p>\n\n\n\n
Updating the DCS tools<\/h2>\n\n\n\nodacli update-repository -f \/opt\/oren\/oda-sm-19.19.0.0.0-230510-server.zip\n\nsleep 60 ; odacli describe-job -i \"e0c8d130-a162-4364-a942-e4d4e89f4bdf\"\r\nJob details\r\n----------------------------------------------------------------\r\n ID: e0c8d130-a162-4364-a942-e4d4e89f4bdf\r\n Description: Repository Update\r\n Status: Success\r\n Created: July 26, 2023 2:16:43 PM CEST\r\n Message: \/opt\/oren\/oda-sm-19.19.0.0.0-230510-server.zip\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nUnzip bundle July 26, 2023 2:16:44 PM CEST July 26, 2023 2:17:19 PM CEST Success\r\n\r\n\n\nodacli describe-component\r\nSystem Version\r\n---------------\r\n19.16.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\noda2\r\n\r\nLocal System Version\r\n---------------\r\n19.16.0.0.0\r\n\r\n\u2003\r\nComponent Installed Version Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK\r\n 19.16.0.0.0 19.19.0.0.0\r\nGI\r\n 19.16.0.0.220719 19.19.0.0.230418\r\nDB {\r\n[OraDB19000_home1 [POSTDT1,PMDT1]]\r\n 19.8.0.0.200714 19.19.0.0.230418\r\n[OraDB11204_home1 [CORIDT2,CORIDV2,\r\nIASDT2,IASIT1,ACTEDT1,SMTEST,IASAT1,\r\nGAIATEST]] 11.2.0.4.200714 not-available\r\n[OraDB12102_home1 [HORUSDT1,ATALDT2,\r\nDELOSDT1,DELOSDT2,SOLISDT1,SOLISDT2]] 12.1.0.2.200114 not-available\r\n}\r\nDCSCONTROLLER\r\n 19.16.0.0.0 19.19.0.0.0\r\nDCSCLI\r\n 19.16.0.0.0 19.19.0.0.0\r\nDCSAGENT\r\n 19.16.0.0.0 19.19.0.0.0\r\nDCSADMIN\r\n 19.16.0.0.0 19.19.0.0.0\r\nOS\r\n 7.9 up-to-date\r\nILOM\r\n 5.1.0.20.r145377 5.1.1.21.r149558\r\nBIOS\r\n 38360300 38370200\r\nLOCAL CONTROLLER FIRMWARE {\r\n[c2]\r\n 4.650.00-7176 up-to-date\r\n[c3]\r\n 000161AB up-to-date\r\n[c4]\r\n 800005DD up-to-date\r\n[c5]\r\n 800005DE up-to-date\r\n}\r\nSHARED CONTROLLER FIRMWARE\r\n KPYAJR3Q up-to-date\r\nLOCAL DISK FIRMWARE\r\n GXM10R3Q up-to-date\r\nHMP\r\n 2.4.8.9.601 2.4.8.9.605\r\n<\/code><\/pre>\n\n\n\nLet’s start with the DCS components update:<\/p>\n\n\n\n
odacli update-dcsadmin -v 19.19.0.0.0\r\nodacli describe-job -i \"21d32707-245b-4712-b683-41e1274fb420\"\r\nJob details\r\n----------------------------------------------------------------\r\n ID: 21d32707-245b-4712-b683-41e1274fb420\r\n Description: DcsAdmin patching\r\n Status: Success\r\n Created: July 26, 2023 2:21:12 PM CEST\r\n Message:\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nPatch location validation July 26, 2023 2:21:13 PM CEST July 26, 2023 2:21:13 PM CEST Success\r\nDcs-admin upgrade July 26, 2023 2:21:13 PM CEST July 26, 2023 2:21:19 PM CEST Success\r\n\r\n\r\nodacli update-dcscomponents -v 19.19.0.0.0\r\n{\r\n \"jobId\" : \"51b60358-de51-4c7f-b68c-a346e5e80099\",\r\n \"status\" : \"Success\",\r\n \"message\" : \"Update-dcscomponents is successful on all the node(s):DCS-Agent shutdown is successful. MySQL upgrade is successful. Metadata migration is done before. Metadata schema update is done. dcsagent RPM upgrade is successful. dcscli RPM upgrade is successful. dcscontroller RPM upgrade is successful. Successfully ran setupAgentAuth.sh zookeeper RPM upgrade is successful. \",\r\n \"reports\" : null,\r\n \"createTimestamp\" : \"July 26, 2023 14:22:33 PM CEST\",\r\n \"description\" : \"Update-dcscomponents job completed and is not part of Agent job list\",\r\n \"updatedTime\" : \"July 26, 2023 14:24:20 PM CEST\"\r\n}\r\n\r\nsleep 20 ; odacli update-dcsagent -v 19.19.0.0.0\r\nodacli describe-job -i \"2c03c606-405e-4763-b31a-34149d22f0f2\"\r\nJob details\r\n----------------------------------------------------------------\r\n ID: 2c03c606-405e-4763-b31a-34149d22f0f2\r\n Description: DcsAgent patching\r\n Status: Success\r\n Created: July 26, 2023 2:24:44 PM CEST\r\n Message:\r\n\u2003\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nDcs-agent upgrade to version July 26, 2023 2:24:44 PM CEST July 26, 2023 2:26:38 PM CEST Success\r\n19.19.0.0.0\r\nUpdate System version July 26, 2023 2:26:39 PM CEST July 26, 2023 2:26:39 PM CEST Success<\/code><\/pre>\n\n\n\nRegister the 19.19 GI clone in the ODA repository:<\/p>\n\n\n\n
odacli update-repository -f \/opt\/oren\/odacli-dcs-19.19.0.0.0-230510-GI-19.19.0.0.zip\r\nsleep 45; odacli describe-job -i \"1763af8a-1407-4ed4-af4f-462761a4eb1d\"\r\nJob details\r\n----------------------------------------------------------------\r\n ID: 1763af8a-1407-4ed4-af4f-462761a4eb1d\r\n Description: Repository Update\r\n Status: Success\r\n Created: July 26, 2023 2:29:06 PM CEST\r\n Message: \/opt\/oren\/odacli-dcs-19.19.0.0.0-230510-GI-19.19.0.0.zip\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nUnzip bundle July 26, 2023 2:29:07 PM CEST July 26, 2023 2:29:54 PM CEST Success\r\n<\/code><\/pre>\n\n\n\nSystem prepatching report<\/h2>\n\n\n\n
Let’s do the prepatching test:<\/p>\n\n\n\n
odacli create-prepatchreport -s -v 19.19.0.0.0\r\n\r\nsleep 360; odacli describe-prepatchreport -i e99c3848-0ccb-4085-a15d-398f7ec91d59\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n Job ID: e99c3848-0ccb-4085-a15d-398f7ec91d59\r\n Description: Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER, SERVER]\r\n Status: FAILED\r\n Created: July 26, 2023 2:30:58 PM CEST\r\n Result: One or more pre-checks failed for [ORACHK]\r\n\r\nNode Name\r\n---------------\r\noda2\r\n\r\nPre-Check Status Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions Success Validated minimum supported versions.\r\nValidate patching tag Success Validated patching tag: 19.19.0.0.0.\r\nIs patch location available Success Patch location is available.\r\nVerify OS patch Success Verified OS patch\r\nValidate command execution Success Validated command execution\r\n\r\n__ILOM__\r\nValidate ILOM server reachable Success Successfully connected with ILOM\r\n server using public IP and USB\r\n interconnect\r\nValidate supported versions Success Validated minimum supported versions.\r\nValidate patching tag Success Validated patching tag: 19.19.0.0.0.\r\nIs patch location available Success Patch location is available.\r\nChecking Ilom patch Version Success Successfully verified the versions\r\nPatch location validation Success Successfully validated location\r\nValidate command execution Success Validated command execution\r\n\r\n__GI__\r\nValidate GI metadata Success Successfully validated GI metadata\r\nValidate supported GI versions Success Successfully validated minimum version\r\nValidate available space Success Validated free space under \/u01\r\nIs clusterware running Success Clusterware is running\r\nValidate patching tag Success Validated patching tag: 19.19.0.0.0.\r\nIs system provisioned Success Verified system is provisioned\r\nValidate ASM in online Success ASM is online\r\nValidate kernel log level Success Successfully validated the OS log\r\n level\r\nValidate minimum agent version Success GI patching enabled in current\r\n DCSAGENT version\r\nValidate Central Inventory Success oraInventory validation passed\r\nValidate patching locks Success Validated patching locks\r\nValidate clones location exist Success Validated clones location\r\nValidate DB start dependencies Success DBs START dependency check passed\r\nValidate DB stop dependencies Success DBs STOP dependency check passed\r\nValidate space for clones Success Clones volume is already created\r\nvolume\r\nEvaluate GI patching Success Successfully validated GI patching\r\nValidate command execution Success Validated command execution\r\n\r\n__ORACHK__\r\nRunning orachk Failed failed to run ORAchk: Failed to run\r\n orachk\r\nValidate command execution Success Validated command execution\r\n\r\n\u2003\r\n__SERVER__\r\nValidate local patching Success Successfully validated server local\r\n patching\r\nValidate command execution Success Validated command execution<\/code><\/pre>\n\n\n\nEverything is OK apart from ORACHK. But this shouldn’t be a problem, it’s about patching the system now. If a failure is detected on the other checks, I definitly won’t recommend going further.<\/p>\n\n\n\n
Patching server and GI<\/h2>\n\n\n\n
Let’s start the update-server, force option is mandatory because of the failure of ORACHK:<\/p>\n\n\n\n
odacli update-server -f -v 19.19.0.0.0\nodacli describe-job -i 02430d8e-6dff-4bcc-91f8-c7f20fcb9ad2\nJob details\r\n----------------------------------------------------------------\r\n ID: 02430d8e-6dff-4bcc-91f8-c7f20fcb9ad2\r\n Description: Server Patching\r\n Status: Success\r\n Created: July 26, 2023 2:41:36 PM CEST\r\n Message: Successfully patched GI with RHP\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nValidating GI user metadata July 26, 2023 2:41:55 PM CEST July 26, 2023 2:41:55 PM CEST Success\r\nValidate ILOM server reachable July 26, 2023 2:41:55 PM CEST July 26, 2023 2:41:56 PM CEST Success\r\nValidate DCS Admin mTLS setup July 26, 2023 2:41:56 PM CEST July 26, 2023 2:41:56 PM CEST Success\r\nConfigure export clones resource July 26, 2023 2:41:57 PM CEST July 26, 2023 2:41:58 PM CEST Success\r\nCreating repositories using yum July 26, 2023 2:41:58 PM CEST July 26, 2023 2:42:02 PM CEST Success\r\nUpdating YumPluginVersionLock rpm July 26, 2023 2:42:02 PM CEST July 26, 2023 2:42:02 PM CEST Success\r\nApplying OS Patches July 26, 2023 2:42:02 PM CEST July 26, 2023 2:56:06 PM CEST Success\r\nCreating repositories using yum July 26, 2023 2:56:07 PM CEST July 26, 2023 2:56:07 PM CEST Success\r\nApplying HMP Patches July 26, 2023 2:56:07 PM CEST July 26, 2023 2:56:30 PM CEST Success\r\nPatch location validation July 26, 2023 2:56:30 PM CEST July 26, 2023 2:56:30 PM CEST Success\r\nOda-hw-mgmt upgrade July 26, 2023 2:56:31 PM CEST July 26, 2023 2:57:07 PM CEST Success\r\nOSS Patching July 26, 2023 2:57:07 PM CEST July 26, 2023 2:57:08 PM CEST Success\r\nApplying Firmware Disk Patches July 26, 2023 2:57:08 PM CEST July 26, 2023 2:57:20 PM CEST Success\r\nApplying Firmware Controller Patches July 26, 2023 2:57:20 PM CEST July 26, 2023 2:57:31 PM CEST Success\r\nChecking Ilom patch Version July 26, 2023 2:57:31 PM CEST July 26, 2023 2:57:32 PM CEST Success\r\nPatch location validation July 26, 2023 2:57:32 PM CEST July 26, 2023 2:57:32 PM CEST Success\r\nSave password in Wallet July 26, 2023 2:57:32 PM CEST July 26, 2023 2:57:33 PM CEST Success\r\nDisabling IPMI v2 July 26, 2023 2:57:33 PM CEST July 26, 2023 2:57:36 PM CEST Success\r\nApply Ilom patch July 26, 2023 2:57:36 PM CEST July 26, 2023 3:14:07 PM CEST Success\r\nCopying Flash Bios to Temp location July 26, 2023 3:14:07 PM CEST July 26, 2023 3:14:07 PM CEST Success\r\nStarting the clusterware July 26, 2023 3:14:07 PM CEST July 26, 2023 3:15:47 PM CEST Success\r\nRegistering image July 26, 2023 3:15:47 PM CEST July 26, 2023 3:15:47 PM CEST Success\r\nRegistering working copy July 26, 2023 3:15:47 PM CEST July 26, 2023 3:15:48 PM CEST Success\r\nRegistering image July 26, 2023 3:15:48 PM CEST July 26, 2023 3:15:48 PM CEST Success\r\nCreating GI home directories July 26, 2023 3:15:48 PM CEST July 26, 2023 3:15:48 PM CEST Success\r\nExtract GI clone July 26, 2023 3:15:48 PM CEST July 26, 2023 3:15:48 PM CEST Success\r\nProvisioning Software Only GI with RHP July 26, 2023 3:15:48 PM CEST July 26, 2023 3:15:48 PM CEST Success\r\nPatch GI with RHP July 26, 2023 3:15:48 PM CEST July 26, 2023 3:22:10 PM CEST Success\r\nUpdating .bashrc July 26, 2023 3:22:10 PM CEST July 26, 2023 3:22:10 PM CEST Success\r\nUpdating GIHome in the repository July 26, 2023 3:22:10 PM CEST July 26, 2023 3:22:10 PM CEST Success\r\nUpdating GIHome version July 26, 2023 3:22:10 PM CEST July 26, 2023 3:22:15 PM CEST Success\r\nValidate GI availability July 26, 2023 3:22:26 PM CEST July 26, 2023 3:22:27 PM CEST Success\r\nPatch KVM CRS type July 26, 2023 3:22:27 PM CEST July 26, 2023 3:22:27 PM CEST Success\r\nPatch VM vDisks CRS dependencies July 26, 2023 3:22:27 PM CEST July 26, 2023 3:22:27 PM CEST Success\r\nPatch DB System domain config July 26, 2023 3:22:27 PM CEST July 26, 2023 3:22:27 PM CEST Success\r\nUpdate System version July 26, 2023 3:23:09 PM CEST July 26, 2023 3:23:09 PM CEST Success\r\nCleanup JRE Home July 26, 2023 3:23:09 PM CEST July 26, 2023 3:23:10 PM CEST Success\r\nAdd SYSNAME in Env July 26, 2023 3:23:10 PM CEST July 26, 2023 3:23:10 PM CEST Success\r\nStarting the clusterware July 26, 2023 3:23:10 PM CEST July 26, 2023 3:24:48 PM CEST Success\r\nSetting ACL for disk groups July 26, 2023 3:24:48 PM CEST July 26, 2023 3:24:54 PM CEST Success\r\nEnable LKCE July 26, 2023 3:27:02 PM CEST July 26, 2023 3:31:01 PM CEST Success\r\nUpdate previous workarounds July 26, 2023 3:31:09 PM CEST July 26, 2023 3:31:09 PM CEST Success\r\nGenerating and saving BOM July 26, 2023 3:31:09 PM CEST July 26, 2023 3:33:54 PM CEST Success\r\nPreRebootNode Actions July 26, 2023 3:33:54 PM CEST July 26, 2023 3:34:39 PM CEST Success\r\nReboot Ilom July 26, 2023 3:34:39 PM CEST July 26, 2023 3:34:39 PM CEST Success<\/code><\/pre>\n\n\n\nServer reboots several minutes after the patch ends. On this X6-2M, server patching took 55 minutes.<\/p>\n\n\n\n
odacli describe-component\r\nSystem Version\r\n---------------\r\n19.19.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\noda2\r\n\r\nLocal System Version\r\n---------------\r\n19.19.0.0.0\r\n\r\nComponent Installed Version Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK\r\n 19.19.0.0.0 up-to-date\r\nGI\r\n 19.19.0.0.230418 up-to-date\r\nDB {\r\n[OraDB19000_home1 [POSTDT1,PMDT1]]\r\n 19.8.0.0.200714 19.19.0.0.230418\r\n\u2003\r\n[OraDB11204_home1 [CORIDT2,CORIDV2,\r\nIASDT2,IASIT1,ACTEDT1,SMTEST,IASAT1,\r\nGAIATEST]] 11.2.0.4.200714 not-available\r\n[OraDB12102_home1 [HORUSDT1,ATALDT2,\r\nDELOSDT1,DELOSDT2,SOLISDT1,SOLISDT2]] 12.1.0.2.200114 not-available\r\n}\r\nDCSCONTROLLER\r\n 19.19.0.0.0 up-to-date\r\nDCSCLI\r\n 19.19.0.0.0 up-to-date\r\nDCSAGENT\r\n 19.19.0.0.0 up-to-date\r\nDCSADMIN\r\n 19.19.0.0.0 up-to-date\r\nOS\r\n 7.9 up-to-date\r\nILOM\r\n 5.1.1.21.r149558 up-to-date\r\nBIOS\r\n 38370200 up-to-date\r\nLOCAL CONTROLLER FIRMWARE {\r\n[c2]\r\n 4.650.00-7176 up-to-date\r\n[c3]\r\n 000161AB up-to-date\r\n[c4]\r\n 800005DD up-to-date\r\n[c5]\r\n 800005DE up-to-date\r\n}\r\nSHARED CONTROLLER FIRMWARE\r\n KPYAJR3Q up-to-date\r\nLOCAL DISK FIRMWARE\r\n GXM10R3Q up-to-date\r\nHMP\r\n 2.4.8.9.605 up-to-date<\/code><\/pre>\n\n\n\nPatching the storage<\/h2>\n\n\n\n
Patching the storage is only needed if describe-component tells you that you’re not up-to-date. On my X6-2M it wasn’t needed, but on your ODA if you need to, it’s quite straight forward:<\/p>\n\n\n\n
odacli update-storage -v 19.19.0.0.0\r\nodacli describe-job -i ...<\/code><\/pre>\n\n\n\nThe server will also reboot when it’s done.<\/p>\n\n\n\n
Patching the DB homes<\/h2>\n\n\n\n
Time for patching the DB homes depends on the number of DB homes and number of databases you have. In this other example (X8-2M), I will apply the patch on my 19.12 DB home. For DB homes, you don’t need to use intermediate patches (and you will save time).<\/p>\n\n\n\n
odacli update-repository -f \/opt\/oren\/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip \r\nsleep 30; odacli describe-job -i e078e543-10c0-438b-8cf4-ec24de7926e9\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n ID: e078e543-10c0-438b-8cf4-ec24de7926e9\r\n Description: Repository Update\r\n Status: Success\r\n Created: August 11, 2023 9:50:42 AM CEST\r\n Message: \/opt\/oren\/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nUnzip bundle August 11, 2023 9:50:42 AM CEST August 11, 2023 9:51:21 AM CEST Success\r\n\r\n\r\nodacli list-dbhomes\r\nID Name DB Version DB Edition Home Location Status\r\n---------------------------------------- -------------------- ---------------------------------------- ---------- ------------------------------------------------------- ----------\r\n5d04a23f-f282-43fb-b95c-3a4d93d007e7 OraDB19000_home1 19.12.0.0.210720 EE \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_1 CONFIGURED\r\n689f3b27-e122-4f70-825f-6221361ff3db OraDB19000_home2 19.12.0.0.210720 EE \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_2 CONFIGURED\r\n \r\nLet's patch the first DB home here:\n\nodacli create-prepatchreport -d -i 5d04a23f-f282-43fb-b95c-3a4d93d007e7 -v 19.19.0.0.0\n\nsleep 600; odacli describe-prepatchreport -i 621e5e56-744b-4c82-85cb-6f86a0204810\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n Job ID: 621e5e56-744b-4c82-85cb-6f86a0204810\r\n Description: Patch pre-checks for [DB, ORACHKDB]: DbHome is OraDB19000_home1\r\n Status: SUCCESS\r\n Created: August 11, 2023 10:07:07 AM CEST\r\n Result: All pre-checks succeeded\r\n\r\nNode Name\r\n---------------\r\noda-prod-01\r\n\r\nPre-Check Status Comments\r\n------------------------------ -------- --------------------------------------\r\n__DB__\r\nValidate DB Home ID Success Validated DB Home ID:\r\n 5d04a23f-f282-43fb-b95c-3a4d93d007e7\r\nValidate patching tag Success Validated patching tag: 19.19.0.0.0.\r\nIs system provisioned Success Verified system is provisioned\r\nValidate minimum agent version Success Validated minimum agent version\r\nIs GI upgraded Success Validated GI is upgraded\r\nValidate available space for Success Validated free space required under\r\ndb \/u01\r\nValidate dbHomesOnACFS Success User has configured disk group for\r\nconfigured Database homes on ACFS\r\nValidate Oracle base Success Successfully validated Oracle Base\r\nIs DB clone available Success Successfully validated clone file\r\n exists\r\nEvaluate DBHome patching with Success Successfully validated updating\r\nRHP dbhome with RHP. and local patching\r\n is possible\r\nValidate command execution Success Validated command execution\r\n\r\n__ORACHK__\r\nRunning orachk Success Successfully ran Orachk\r\nValidate command execution Success Validated command execution<\/code><\/pre>\n\n\n\nSometimes ORACHK will warn you about different things, but your database may need some specific settings ORACHK won’t like, so you could also force the DB home update with -f. But only these warnings from ORACHK please.<\/p>\n\n\n\n
odacli update-dbhome -i 5d04a23f-f282-43fb-b95c-3a4d93d007e7 -v 19.19.0.0.0\r\n\r\nsleep 600; odacli describe-job -i cca4b034-aa11-4250-946f-b7d28c794fc0\r\nJob details\r\n----------------------------------------------------------------\r\n ID: cca4b034-aa11-4250-946f-b7d28c794fc0\r\n Description: DB Home Patching: Home Id is 5d04a23f-f282-43fb-b95c-3a4d93d007e7\r\n Status: Success\r\n Created: August 11, 2023 1:09:56 PM CEST\r\n Message:\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nCreating wallet for DB Client August 11, 2023 1:10:10 PM CEST August 11, 2023 1:10:10 PM CEST Success\r\nPatch databases by RHP - [REPFMW] August 11, 2023 1:10:10 PM CEST August 11, 2023 1:16:08 PM CEST Success\r\nUpdating database metadata August 11, 2023 1:16:08 PM CEST August 11, 2023 1:16:08 PM CEST Success\r\nSet log_archive_dest for Database August 11, 2023 1:16:08 PM CEST August 11, 2023 1:16:11 PM CEST Success\r\nPatch databases by RHP - [PAMIF] August 11, 2023 1:16:11 PM CEST August 11, 2023 1:21:48 PM CEST Success\r\nUpdating database metadata August 11, 2023 1:21:48 PM CEST August 11, 2023 1:21:48 PM CEST Success\r\nSet log_archive_dest for Database August 11, 2023 1:21:48 PM CEST August 11, 2023 1:21:51 PM CEST Success\r\nUpdate System version August 11, 2023 1:21:51 PM CEST August 11, 2023 1:21:51 PM CEST Success\r\nGenerating and saving BOM August 11, 2023 1:21:51 PM CEST August 11, 2023 1:22:49 PM CEST Success\r\nTDE parameter update August 11, 2023 1:22:49 PM CEST August 11, 2023 1:22:49 PM CEST Success\r\n\r\n\r\nodacli list-dbhomes\r\nID Name DB Version DB Edition Home Location Status\r\n---------------------------------------- -------------------- ---------------------------------------- ---------- ------------------------------------------------------- ----------\r\n5d04a23f-f282-43fb-b95c-3a4d93d007e7 OraDB19000_home1 19.12.0.0.210720 EE \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_1 CONFIGURED\n689f3b27-e122-4f70-825f-6221361ff3db OraDB19000_home2 19.12.0.0.210720 EE \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_2 CONFIGURED\r\n83bfc182-bae6-4d8b-9491-aa2f2758b808 OraDB19000_home3 19.19.0.0.230418 EE \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_3 CONFIGURED<\/code><\/pre>\n\n\n\nDon’t forget that the previous DB home will not be deleted: you should delete it after the patch of several days later.<\/p>\n\n\n\n
Final checks<\/h2>\n\n\n\n
I would recommend checking the final versions:<\/p>\n\n\n\n
odacli describe-component\n...<\/code><\/pre>\n\n\n\nCleanse the old patches<\/h2>\n\n\n\n
The old patches will never be used again, so don’t forget to remove them from the repository if your ODA has already been patched:<\/p>\n\n\n\n
odacli cleanup-patchrepo -cl -v 19.16.0.0.0\r\nodacli describe-job -i \"ada6139b-4406-4e86-b978-73f7d5133385\"\r\nJob details\r\n----------------------------------------------------------------\r\n ID: ada6139b-4406-4e86-b978-73f7d5133385\r\n Description: Cleanup patchrepos\r\n Status: Success\r\n Created: July 26, 2023 3:48:37 PM CEST\r\n Message:\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nCleanup Repository July 26, 2023 3:48:37 PM CEST July 26, 2023 3:48:37 PM CEST Success\r\nCleanup JRE Home July 26, 2023 3:48:37 PM CEST July 26, 2023 3:48:37 PM CEST Success\r\nCleanup old ASR rpm July 26, 2023 3:48:37 PM CEST July 26, 2023 3:48:37 PM CEST Success<\/code><\/pre>\n\n\n\nPost-patching tasks<\/h2>\n\n\n\n
Once everything is OK, don’t forget to:<\/p>\n\n\n\n
\n- add your additional rpms manually if needed<\/li>\n\n\n\n
- put back your profile scripts for grid and oracle users<\/li>\n\n\n\n
- remove the old DB homes if they are not needed anymore<\/li>\n<\/ul>\n\n\n\n
odacli delete-dbhome -i 5d04a23f-f282-43fb-b95c-3a4d93d007e7 \r\nsleep 60 ; odacli describe-job -i odacli describe-job -i 8c79189a-dff6-41fe-b9a5-144a2bac1db1\r\nJob details\r\n----------------------------------------------------------------\r\n ID: 8c79189a-dff6-41fe-b9a5-144a2bac1db1\r\n Description: Database Home OraDB19000_home1 Deletion with id 5d04a23f-f282-43fb-b95c-3a4d93d007e7\r\n Status: Success\r\n Created: August 11, 2023 2:36:33 PM CEST\r\n Message:\r\n\r\nTask Name Start Time End Time Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nValidate dbhome August 11, 2023 2:36:33 PM CEST August 11, 2023 2:36:33 PM CEST Success\r\n5d04a23f-f282-43fb-b95c-3a4d93d007e7\r\nfor deletion\r\nSetting up ssh equivalance August 11, 2023 2:36:33 PM CEST August 11, 2023 2:36:33 PM CEST Success\r\nSetting up ssh equivalance August 11, 2023 2:36:33 PM CEST August 11, 2023 2:36:33 PM CEST Success\r\nDeleting DbHome by RHP August 11, 2023 2:36:34 PM CEST August 11, 2023 2:37:09 PM CEST Success<\/code><\/pre>\n\n\n\nIf everything is fine, remove the snapshots done with ODABR:<\/p>\n\n\n\n
\/opt\/odabr\/odabr delsnap\r\nINFO: 2023-07-26 15:51:19: Please check the logfile '\/opt\/odabr\/out\/log\/odabr_71724.log' for more details\r\n\r\nINFO: 2023-07-26 15:51:19: Removing LVM snapshots\r\nINFO: 2023-07-26 15:51:19: ...removing LVM snapshot for 'opt'\r\nSUCCESS: 2023-07-26 15:51:20: ...snapshot for 'opt' removed successfully\r\nINFO: 2023-07-26 15:51:20: ...removing LVM snapshot for 'u01'\r\nSUCCESS: 2023-07-26 15:51:20: ...snapshot for 'u01' removed successfully\r\nINFO: 2023-07-26 15:51:20: ...removing LVM snapshot for 'root'\r\nSUCCESS: 2023-07-26 15:51:20: ...snapshot for 'root' removed successfully\r\nSUCCESS: 2023-07-26 15:51:20: Remove LVM snapshots done successfully\r\n<\/code><\/pre>\n\n\n\nPatching DB Systems<\/h2>\n\n\n\n
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. I haven’t tried on my X6-2M because it only runs bare metal databases, but you will need to list your DB Systems, connect to each one, and apply the server and database patches:<\/p>\n\n\n\n
odacli list-dbsystems\nssh ...\nodacli update-server -v 19.19.0.0.0\r\nodacli update-dbhome -i ... -v 19.19.0.0.0\n<\/code><\/pre>\n\n\n\nConclusion<\/h2>\n\n\n\n
This release is easy to apply coming from 19.16 and probably from newer versions. Next versions might bring major OS upgrade and 23c GI and DB homes.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction It’s been several weeks that patch 19.19 is available on ODA. And I finally had the possibility to test it. What’s new? This version brings latest PSUs to database and grid homes, with their bug fixes as usual. It also brings latest 21c and 19c DB Systems. You already know that 21c is an […]<\/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":[],"type_dbi":[],"class_list":["post-27211","post","type-post","status-publish","format-standard","hentry","category-oracle"],"acf":[],"yoast_head":"\n
How to apply patch 19.19 on your ODA? - dbi Blog<\/title>\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-apply-patch-19-19-on-your-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to apply patch 19.19 on your ODA?\" \/>\n<meta property=\"og:description\" content=\"Introduction It’s been several weeks that patch 19.19 is available on ODA. And I finally had the possibility to test it. What’s new? This version brings latest PSUs to database and grid homes, with their bug fixes as usual. It also brings latest 21c and 19c DB Systems. You already know that 21c is an […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-08-14T15:05:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-08-14T15:05:40+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-apply-patch-19-19-on-your-oda\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"How to apply patch 19.19 on your ODA?\",\"datePublished\":\"2023-08-14T15:05:38+00:00\",\"dateModified\":\"2023-08-14T15:05:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/\"},\"wordCount\":1309,\"commentCount\":1,\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/\",\"name\":\"How to apply patch 19.19 on your ODA? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2023-08-14T15:05:38+00:00\",\"dateModified\":\"2023-08-14T15:05:40+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to apply patch 19.19 on your ODA?\"}]},{\"@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 apply patch 19.19 on your ODA? - dbi Blog","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-apply-patch-19-19-on-your-oda\/","og_locale":"en_US","og_type":"article","og_title":"How to apply patch 19.19 on your ODA?","og_description":"Introduction It’s been several weeks that patch 19.19 is available on ODA. And I finally had the possibility to test it. What’s new? This version brings latest PSUs to database and grid homes, with their bug fixes as usual. It also brings latest 21c and 19c DB Systems. You already know that 21c is an […]","og_url":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/","og_site_name":"dbi Blog","article_published_time":"2023-08-14T15:05:38+00:00","article_modified_time":"2023-08-14T15:05:40+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-apply-patch-19-19-on-your-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"How to apply patch 19.19 on your ODA?","datePublished":"2023-08-14T15:05:38+00:00","dateModified":"2023-08-14T15:05:40+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/"},"wordCount":1309,"commentCount":1,"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/","name":"How to apply patch 19.19 on your ODA? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-08-14T15:05:38+00:00","dateModified":"2023-08-14T15:05:40+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-apply-patch-19-19-on-your-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to apply patch 19.19 on your ODA?"}]},{"@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\/27211","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=27211"}],"version-history":[{"count":7,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/27211\/revisions"}],"predecessor-version":[{"id":27220,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/27211\/revisions\/27220"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=27211"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=27211"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=27211"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=27211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}