{"id":13978,"date":"2020-04-28T11:01:21","date_gmt":"2020-04-28T09:01:21","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/"},"modified":"2020-04-28T11:01:21","modified_gmt":"2020-04-28T09:01:21","slug":"patching-oda-from-18-3-to-18-8","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/","title":{"rendered":"Patching ODA from 18.3 to 18.8"},"content":{"rendered":"

Introduction<\/h2>\n

19c will soon be available for your ODAs. But you may not be ready. Here is how to patch your ODA from 18.3 to 18.8, the very latest 18c release. This patch has here been applied on X7-2M hardware.<\/p>\n

Download the patch files<\/h2>\n

Patch number is 30518425. This patch is composed of 2 zipfiles you will copy on your ODA.<\/p>\n

Check free space on disk<\/h2>\n

Applying a patch requires several GB, please check free space on \/, \/opt and \/u01 before starting. These filesystems should have about 20% free space. If needed, \/u01 and \/opt filesystems can be extended online, based on Linux VG\/LV. For example if you need an additional 20GB in \/opt:<\/p>\n

lvextend -L +20G \/dev\/mapper\/VolGroupSys-LogVolOpt\nresize2fs \/dev\/mapper\/VolGroupSys-LogVolOpt<\/pre>\n
Check processes<\/h2>\n
It’s also recommended to check what’s running on your ODA before patching, you’ll do the same check after patching is complete:<\/p>\n
ps -ef | grep pmon\noracle     863     1  0 Feb22 ?        00:00:06 ora_pmon_UBTMUR\noracle    8014     1  0  2019 ?        00:03:06 ora_pmon_TSTDEV\noracle    9901     1  0 Feb22 ?        00:00:11 ora_pmon_DEVUT2\ngrid     14044     1  0  2019 ?        00:22:39 asm_pmon_+ASM1\ngrid     17118     1  0  2019 ?        00:18:18 apx_pmon_+APX1\noracle   22087 19584  0 11:02 pts\/0    00:00:00 grep pmon\n\nps -ef | grep tnslsnr\ngrid     15667     1  0  2019 ?        01:43:48 \/u01\/app\/18.0.0.0\/grid\/bin\/tnslsnr ASMNET1LSNR_ASM -no_crs_notify -inherit\ngrid     15720     1  0  2019 ?        02:26:42 \/u01\/app\/18.0.0.0\/grid\/bin\/tnslsnr LISTENER -no_crs_notify -inherit\noracle   22269 19584  0 11:02 pts\/0    00:00:00 grep tnslsnr\ngrid     26884     1  0  2019 ?        00:01:24 \/u01\/app\/18.0.0.0\/grid\/bin\/tnslsnr LISTENER1523 -inherit\ngrid     94369     1  0  2019 ?        00:01:16 \/u01\/app\/18.0.0.0\/grid\/bin\/tnslsnr LISTENER1522 -inherit\n<\/pre>\n
Check current version in use<\/h2>\n
Start to check current version on all components:<\/p>\n
odacli describe-component\n\nSystem Version\n---------------\n18.3.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       18.3.0.0.0            up-to-date\nGI                                        18.3.0.0.180717       up-to-date\nDB {\n[ OraDB12201_home1 ]                      12.2.0.1.180717       up-to-date\n[ OraDB11204_home1 ]                      11.2.0.4.180717       up-to-date\n}\nDCSAGENT                                  18.3.0.0.0            up-to-date\nILOM                                      4.0.4.21.r126801      up-to-date\nBIOS                                      41040100              up-to-date\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER                        QDV1RE14              up-to-date\nFIRMWAREDISK                              0121                  0112\n<\/pre>\n
Some components version could be higher than those available at time of previous patch\/deployment. In this example, starting version is 18.3.0.0.0: this version as a straight path to 18.8.0.0.0.<\/p>\n
Duration of the patch may vary depending on the components to be patched. I strongly advise you to check the target version for each component in the documentation, for an ODA X7-2M here is the url<\/a>.<\/p>\n
For this ODA, and compared to currently deployed components versions, no OS update is embedded in the patch, meaning that it will shortened the patching time.<\/p>\n
Preparing the patch<\/h2>\n
Copy the patch files on disk in a temp directory. Then unzip the files and update the repository:<\/p>\n
cd \/u01\/tmp\nunzip p30518425_188000_Linux-x86-64_1of2.zip\nunzip p30518425_188000_Linux-x86-64_1of2.zip\nrm -rf p30518425_188000_Linux-x86-64_*\nodacli update-repository -f \/u01\/tmp\/oda-sm-18.8.0.0.0-200124-server1of2.zip\nodacli update-repository -f \/u01\/tmp\/oda-sm-18.8.0.0.0-200124-server2of2.zip\nodacli list-jobs | head -n 3;  odacli list-jobs | tail -n 3\nID                                       Description                      Created                             Status\n---------------------------------------- -------------------------------- ----------------------------------- ---------\n7127c3ca-8fb9-4ac9-810d-b7e1aa0e32c5     Repository Update                February 24, 2020 01:13:53 PM CET   Success\n5e294f03-3fa8-48ae-b193-219659bec4de     Repository Update                February 24, 2020 01:14:09 PM CET   Success\n<\/pre>\n
Patch the dcs components<\/h2>\n
Patching the dcs components is easy. Now it’s a 3-step process:<\/p>\n
\/opt\/oracle\/dcs\/bin\/odacli update-dcsagent -v 18.8.0.0.0\n\/opt\/oracle\/dcs\/bin\/odacli update-dcsadmin -v 18.8.0.0.0\n\/opt\/oracle\/dcs\/bin\/odacli update-dcscomponents -v 18.8.0.0.0\n{\n  \"jobId\" : \"f36c44b3-4eb8-4a43-a323-d28a9836de74\",\n  \"status\" : \"Success\",\n  \"message\" : null,\n  \"reports\" : null,\n  \"createTimestamp\" : \"February 24, 2020 14:04:01 PM CET\",\n  \"description\" : \"Job completed and is not part of Agent job list\",\n  \"updatedTime\" : \"February 24, 2020 14:04:01 PM CET\"\n}\nodacli list-jobs | tail -n 3\nb8d474ab-3b5e-4860-a9f4-3d73497d6d4c     DcsAgent patching                                                           February 24, 2020 1:58:54 PM CET    Success\n286b36a2-c1fc-48b9-8c99-197e24b6c8ba     DcsAdmin patching                                                           February 24, 2020 2:01:52 PM CET    Success\n<\/pre>\n
Note that the latest update is not a job in the list.<\/p>\n
Check proposed version to patch to<\/h2>\n
Now the describe-component should propose the real available versions bundled in the patch:<\/p>\n
odacli describe-component\nSystem Version\n---------------\n18.8.0.0.0\n \nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       18.3.0.0.0            18.8.0.0.0\nGI                                        18.3.0.0.180717       18.8.0.0.191015\nDB {\n[ OraDB12201_home1 ]                      12.2.0.1.180717       12.2.0.1.191015\n[ OraDB11204_home1 ]                      11.2.0.4.180717       11.2.0.4.191015\n}\nDCSAGENT                                  18.8.0.0.0            up-to-date\nILOM                                      4.0.4.21.r126801      4.0.4.47.r131913\nBIOS                                      41040100              41060600\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER                        QDV1RE14              qdv1rf30\nFIRMWAREDISK                              0121                  up-to-date\n<\/pre>\n
OS and firmwaredisk components don’t need to be patched.<\/p>\n
Pre-patching report<\/h2>\n
Let’s check if patching has the green light:<\/p>\n
odacli create-prepatchreport -s -v 18.8.0.0.0\nodacli describe-prepatchreport -i 12d61cda-1cef-40b9-ad7d-8e087007da23\n\n \nPatch pre-check report\n------------------------------------------------------------------------\n                 Job ID:  12d61cda-1cef-40b9-ad7d-8e087007da23\n            Description:  Patch pre-checks for [OS, ILOM, GI]\n                 Status:  SUCCESS\n                Created:  February 24, 2020 2:05:41 PM CET\n                 Result:  All pre-checks succeeded\n \n\n\u2003\nNode Name\n---------------\ndbiora07\n \nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__OS__\nValidate supported versions     Success   Validated minimum supported versions\nValidate patching tag           Success   Validated patching tag: 18.8.0.0.0\nIs patch location available     Success   Patch location is available\nVerify OS patch                 Success   There are no packages available for\n                                          an update\n \n__ILOM__\nValidate supported versions     Success   Validated minimum supported versions\nValidate patching tag           Success   Validated patching tag: 18.8.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\n \n__GI__\nValidate supported GI versions  Success   Validated minimum supported versions\nValidate available space        Success   Validated free space under \/u01\nVerify DB Home versions         Success   Verified DB Home versions\nValidate patching locks         Success   Validated patching locks\n<\/pre>\n
ODA is ready.<\/p>\n
Patching infrastructure and GI<\/h2>\n
First the Trace File Analyzer should be stopped, then the update-server could be run:<\/p>\n
\/etc\/init.d\/init.tfa stop\nodacli update-server -v 18.8.0.0.0\nodacli describe-job -i 4d6aab0e-18c4-4bbd-8c16-a39c8a14f992\n Job details\n----------------------------------------------------------------\n                     ID:  4d6aab0e-18c4-4bbd-8c16-a39c8a14f992\n            Description:  Server Patching\n                 Status:  Success\n                Created:  February 24, 2020 2:15:32 PM CET\n                Message:\n\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nPatch location validation                February 24, 2020 2:15:39 PM CET    February 24, 2020 2:15:39 PM CET    Success\ndcs-controller upgrade                   February 24, 2020 2:15:39 PM CET    February 24, 2020 2:15:42 PM CET    Success\nPatch location validation                February 24, 2020 2:15:42 PM CET    February 24, 2020 2:15:42 PM CET    Success\ndcs-cli upgrade                          February 24, 2020 2:15:42 PM CET    February 24, 2020 2:15:43 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:43 PM CET    February 24, 2020 2:15:53 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:53 PM CET    Success\nUpdating YumPluginVersionLock rpm        February 24, 2020 2:15:53 PM CET    February 24, 2020 2:15:54 PM CET    Success\nApplying OS Patches                      February 24, 2020 2:15:54 PM CET    February 24, 2020 2:26:44 PM CET    Success\nCreating repositories using yum          February 24, 2020 2:26:44 PM CET    February 24, 2020 2:26:45 PM CET    Success\nApplying HMP Patches                     February 24, 2020 2:26:45 PM CET    February 24, 2020 2:27:35 PM CET    Success\nPatch location validation                February 24, 2020 2:27:35 PM CET    February 24, 2020 2:27:35 PM CET    Success\noda-hw-mgmt upgrade                      February 24, 2020 2:27:35 PM CET    February 24, 2020 2:28:04 PM CET    Success\nOSS Patching                             February 24, 2020 2:28:04 PM CET    February 24, 2020 2:28:04 PM CET    Success\nApplying Firmware Disk Patches           February 24, 2020 2:28:05 PM CET    February 24, 2020 2:28:11 PM CET    Success\nApplying Firmware Expander Patches       February 24, 2020 2:28:11 PM CET    February 24, 2020 2:28:16 PM CET    Success\nApplying Firmware Controller Patches     February 24, 2020 2:28:16 PM CET    February 24, 2020 2:29:02 PM CET    Success\nChecking Ilom patch Version              February 24, 2020 2:29:03 PM CET    February 24, 2020 2:29:05 PM CET    Success\nPatch location validation                February 24, 2020 2:29:05 PM CET    February 24, 2020 2:29:06 PM CET    Success\nSave password in Wallet                  February 24, 2020 2:29:07 PM CET    February 24, 2020 2:29:07 PM CET    Success\nApply Ilom patch                         February 24, 2020 2:29:07 PM CET    February 24, 2020 2:42:35 PM CET    Success\nCopying Flash Bios to Temp location      February 24, 2020 2:42:35 PM CET    February 24, 2020 2:42:35 PM CET    Success\nStarting the clusterware                 February 24, 2020 2:42:35 PM CET    February 24, 2020 2:44:53 PM CET    Success\nclusterware patch verification           February 24, 2020 2:55:27 PM CET    February 24, 2020 2:55:47 PM CET    Success\nPatch location validation                February 24, 2020 2:55:47 PM CET    February 24, 2020 2:56:37 PM CET    Success\nOpatch updation                          February 24, 2020 2:57:32 PM CET    February 24, 2020 2:57:36 PM CET    Success\nPatch conflict check                     February 24, 2020 2:57:36 PM CET    February 24, 2020 2:58:27 PM CET    Success\nclusterware upgrade                      February 24, 2020 2:58:27 PM CET    February 24, 2020 3:21:18 PM CET    Success\nUpdating GiHome version                  February 24, 2020 3:21:18 PM CET    February 24, 2020 3:21:53 PM CET    Success\nUpdate System version                    February 24, 2020 3:22:26 PM CET    February 24, 2020 3:22:27 PM CET    Success\npreRebootNode Actions                    February 24, 2020 3:22:27 PM CET    February 24, 2020 3:23:14 PM CET    Success\nReboot Ilom                              February 24, 2020 3:23:14 PM CET    February 24, 2020 3:23:14 PM CET    Success\n<\/pre>\n
Server reboots 5 minutes after the patch ends. On my X7-2M this operation lasted 1h15.<\/p>\n
Let’s check the component’s versions:<\/p>\n
odacli describe-component\nSystem Version\n---------------\n18.8.0.0.0\n \nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       18.8.0.0.0            up-to-date\nGI                                        18.8.0.0.191015       up-to-date\nDB {\n[ OraDB12201_home1 ]                      12.2.0.1.180717       12.2.0.1.191015\n[ OraDB11204_home1 ]                      11.2.0.4.180717       11.2.0.4.191015\n}\nDCSAGENT                                  18.8.0.0.0            up-to-date\nILOM                                      4.0.4.21.r126801      4.0.4.47.r131913\nBIOS                                      41040100              41060600\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER                        QDV1RE14              qdv1rf30\nFIRMWAREDISK                              0121                  up-to-date\n<\/pre>\n
Neither ILOM nor BIOS have been updated. This is a bug.<\/p>\n
Solve the ILOM and BIOS not patched<\/h2>\n
An additional procedure is needed (provided by MOS), crsctl needs to be stopped then BIOS patched manually:<\/p>\n
\/u01\/app\/18.0.0.0\/grid\/bin\/crsctl stop crs\nipmiflash -v write ILOM-4_0_4_47_r131913-ORACLE_SERVER_X7-2.pkg force script config delaybios warning=0\n<\/pre>\n
Versions should now be fine:<\/p>\n
odacli describe-component\n\nSystem Version\n---------------\n18.8.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       18.8.0.0.0            up-to-date\nGI                                        18.8.0.0.191015       up-to-date\nDB {\n[ OraDB12201_home1 ]                      12.2.0.1.180717       12.2.0.1.191015\n[ OraDB11204_home1 ]                      11.2.0.4.180717       11.2.0.4.191015\n}\nDCSAGENT                                  18.8.0.0.0            up-to-date\nILOM                                      4.0.4.47.r131913      up-to-date\nBIOS                                      41060600              up-to-date\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER                        QDV1RE14              qdv1rf30\nFIRMWAREDISK                              0121                  up-to-date\n<\/pre>\n
Patching the storage<\/h2>\n
Patching of the storage is much faster than patching the “server”:<\/p>\n
odacli update-storage -v 18.8.0.0.0\n\nodacli describe-job -i a97deb0d-2e0b-42d9-8b56-33af68e23f15\n \nJob details\n----------------------------------------------------------------\n                     ID:  a97deb0d-2e0b-42d9-8b56-33af68e23f15\n            Description:  Storage Firmware Patching\n                 Status:  Success\n                Created:  February 24, 2020 3:33:10 PM CET\n                Message:\n \nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nApplying Firmware Disk Patches           February 24, 2020 3:33:11 PM CET    February 24, 2020 3:33:19 PM CET    Success\nApplying Firmware Controller Patches     February 24, 2020 3:33:19 PM CET    February 24, 2020 3:40:53 PM CET    Success\npreRebootNode Actions                    February 24, 2020 3:40:53 PM CET    February 24, 2020 3:40:54 PM CET    Success\nReboot Ilom                              February 24, 2020 3:40:54 PM CET    February 24, 2020 3:40:54 PM CET    Success\n<\/pre>\n
Another auto reboot is done after this step.<\/p>\n
Patching the dbhomes<\/h2>\n
Time for patching the dbhomes depends on the number of dbhomes and number of databases. In this example, 2 dbhomes are deployed:<\/p>\n
odacli list-dbhomes\n\n\nID                                       Name                 DB Version                               Home Location                                 Status                 \n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- -------                 ---\n8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98     OraDB12201_home1     12.2.0.1.180717                          \/u01\/app\/oracle\/product\/12.2.0.1\/dbhome_1     Configured\n8a494efd-e745-4fe9-ace7-2369a36924ff     OraDB11204_home1     11.2.0.4.180717                          \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured\n\nodacli update-dbhome -i 8a494efd-e745-4fe9-ace7-2369a36924ff -v 18.8.0.0.0 \nodacli describe-job -i 7c5589d7-564a-4d8b-b69a-1dc50\n\nJob details\n----------------------------------------------------------------\n                     ID:  7c5589d7-564a-4d8b-b69a-1dc50162a4c6\n            Description:  DB Home Patching: Home Id is 8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98\n                 Status:  Success\n                Created:  February 25, 2020 9:18:49 AM CET\n                Message:  WARNING::Failed to run the datapatch as db TSTY_RP7 is not running##WARNING::Failed to run the datapatch as db EXPY_RP7 is not registered with\nclusterware##WARNING::Failed to run datapatch on db DEVM12_RP7Failed to run Utlrp script##WARNING::Failed t\n \nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nValidating dbHome available space        February 25, 2020 9:18:59 AM CET    February 25, 2020 9:18:59 AM CET    Success\nclusterware patch verification           February 25, 2020 9:19:21 AM CET    February 25, 2020 9:19:31 AM CET    Success\nPatch location validation                February 25, 2020 9:19:31 AM CET    February 25, 2020 9:19:31 AM CET    Success\nOpatch updation                          February 25, 2020 9:19:31 AM CET    February 25, 2020 9:19:32 AM CET    Success\nPatch conflict check                     February 25, 2020 9:19:32 AM CET    February 25, 2020 9:19:32 AM CET    Success\ndb upgrade                               February 25, 2020 9:19:32 AM CET    February 25, 2020 9:19:32 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:19:32 AM CET    February 25, 2020 9:19:35 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:19:35 AM CET    February 25, 2020 9:20:18 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:20:18 AM CET    February 25, 2020 9:20:55 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:20:55 AM CET    February 25, 2020 9:20:55 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:20:55 AM CET    February 25, 2020 9:20:56 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:20:56 AM CET    February 25, 2020 9:21:33 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:21:33 AM CET    February 25, 2020 9:21:40 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:21:40 AM CET    February 25, 2020 9:21:46 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:21:46 AM CET    February 25, 2020 9:21:57 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:21:57 AM CET    February 25, 2020 9:22:32 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:22:32 AM CET    February 25, 2020 9:23:12 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:23:12 AM CET    February 25, 2020 9:23:53 AM CET    Success\nUpdate System version                    February 25, 2020 9:23:53 AM CET    February 25, 2020 9:23:53 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:03 AM CET    February 25, 2020 9:24:08 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:08 AM CET    February 25, 2020 9:24:14 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:14 AM CET    February 25, 2020 9:24:18 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:18 AM CET    February 25, 2020 9:24:23 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:23 AM CET    February 25, 2020 9:24:28 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:28 AM CET    February 25, 2020 9:24:33 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:33 AM CET    February 25, 2020 9:24:38 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:38 AM CET    February 25, 2020 9:24:45 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:45 AM CET    February 25, 2020 9:24:51 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:51 AM CET    February 25, 2020 9:24:56 AM CET    Success\nupdating the Database version            February 25, 2020 9:24:56 AM CET    February 25, 2020 9:25:02 AM CET    Success\nupdating the Database version            February 25, 2020 9:25:02 AM CET    February 25, 2020 9:25:08 AM CET    Success\n\nodacli update-dbhome -i 8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98 -v 18.8.0.0.0 \nodacli describe-job -i fbed248a-1d0d-4972-afd2-8b43ac8ad514\n\n Job details\n----------------------------------------------------------------\n                     ID:  fbed248a-1d0d-4972-afd2-8b43ac8ad514\n            Description:  DB Home Patching: Home Id is 8a494efd-e745-4fe9-ace7-2369a36924ff\n                 Status:  Success\n                Created:  February 25, 2020 9:39:54 AM CET\n                Message:  WARNING::Failed to run the datapatch as db CUR7_RP7 is not registered with clusterware##WARNING::Failed to run the datapatch as db SRS7_RP7 is not registered with clusterware##WARNING::Failed to run the datapatch as db CUX7_RP7 is not regi\n \nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nValidating dbHome available space        February 25, 2020 9:40:05 AM CET    February 25, 2020 9:40:05 AM CET    Success\nclusterware patch verification           February 25, 2020 9:40:07 AM CET    February 25, 2020 9:40:12 AM CET    Success\nPatch location validation                February 25, 2020 9:40:12 AM CET    February 25, 2020 9:40:17 AM CET    Success\nOpatch updation                          February 25, 2020 9:40:49 AM CET    February 25, 2020 9:40:51 AM CET    Success\nPatch conflict check                     February 25, 2020 9:40:51 AM CET    February 25, 2020 9:41:07 AM CET    Success\ndb upgrade                               February 25, 2020 9:41:07 AM CET    February 25, 2020 9:43:27 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:27 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:27 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:27 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:27 AM CET    February 25, 2020 9:43:28 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:28 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:28 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:28 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:28 AM CET    February 25, 2020 9:43:29 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:29 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:29 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:29 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:29 AM CET    February 25, 2020 9:43:30 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:30 AM CET    February 25, 2020 9:43:30 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:30 AM CET    February 25, 2020 9:43:30 AM CET    Success\nSqlPatch upgrade                         February 25, 2020 9:43:30 AM CET    February 25, 2020 9:43:33 AM CET    Success\nUpdate System version                    February 25, 2020 9:43:33 AM CET    February 25, 2020 9:43:33 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:35 AM CET    February 25, 2020 9:43:37 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:37 AM CET    February 25, 2020 9:43:39 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:39 AM CET    February 25, 2020 9:43:42 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:42 AM CET    February 25, 2020 9:43:45 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:45 AM CET    February 25, 2020 9:43:48 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:48 AM CET    February 25, 2020 9:43:50 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:50 AM CET    February 25, 2020 9:43:52 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:52 AM CET    February 25, 2020 9:43:54 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:54 AM CET    February 25, 2020 9:43:56 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:56 AM CET    February 25, 2020 9:43:58 AM CET    Success\nupdating the Database version            February 25, 2020 9:43:58 AM CET    February 25, 2020 9:44:01 AM CET    Success\nupdating the Database version            February 25, 2020 9:44:01 AM CET    February 25, 2020 9:44:04 AM CET    Success\nupdating the Database version            February 25, 2020 9:44:04 AM CET    February 25, 2020 9:44:06 AM CET    Success\nupdating the Database version            February 25, 2020 9:44:06 AM CET    February 25, 2020 9:44:08 AM CET    Success\nupdating the Database version            February 25, 2020 9:44:08 AM CET    February 25, 2020 9:44:10 AM CET    Success\n\nodacli list-dbhomes\nID                                       Name                 DB Version                               Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------\n8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98     OraDB12201_home1     12.2.0.1.191015                          \/u01\/app\/oracle\/product\/12.2.0.1\/dbhome_1     Configured\n8a494efd-e745-4fe9-ace7-2369a36924ff     OraDB11204_home1     11.2.0.4.191015                          \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured\n<\/pre>\n
The 2 dbhomes are updated. Failures on Sqlpatch upgrade should be analyzed, but remember that standby databases cannot be upgraded as their dictionary is not available.<\/p>\n
Let’s check on primary 12c (and later) databases if everything is OK:<\/p>\n
su \u2013 oracle\n. oraenv <<< DEVC12\nsqlplus \/ as sysdba\nset serverout on\nexec dbms_qopatch.get_sqlpatch_status;\n...\nPatch Id : 28163133\n        Action : APPLY\n        Action Time : 27-MAY-2019 16:02:11\n        Description : DATABASE JUL 2018 RELEASE UPDATE 12.2.0.1.180717\n        Logfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/28163133\/22313390\/28163133_apply_DEVC12_201\n9May27_16_02_00.log\n        Status : SUCCESS\n \nPatch Id : 30138470\n        Action : APPLY\n        Action Time : 24-FEB-2020 17:10:35\n        Description : DATABASE OCT 2019 RELEASE UPDATE 12.2.0.1.191015\n        Logfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/30138470\/23136382\/30138470_apply_DEVC12_202\n0Feb24_17_09_56.log\n        Status : SUCCESS\n\nPL\/SQL procedure successfully completed.\n exit\n<\/pre>\n
Let’s check if everything is also OK on 11g databases;<\/p>\n
su \u2013 oracle\n. oraenv <<< DEVC11\nsqlplus \/ as sysdba\nselect * from dba_registry_history;\nACTION_TIME\n---------------------------------------------------------------------------\nACTION                         NAMESPACE\n------------------------------ ------------------------------\nVERSION                                ID BUNDLE_SERIES\n------------------------------ ---------- ------------------------------\nCOMMENTS\n--------------------------------------------------------------------------------\n...\n17-MAY-19 11.18.48.769476 AM\nAPPLY                          SERVER\n11.2.0.4                           180717 PSU\nPSU 11.2.0.4.180717\n \n25-FEB-20 09.57.40.969359 AM\nAPPLY                          SERVER\n11.2.0.4                           191015 PSU\nPSU 11.2.0.4.191015\n Patch Id : 26635944\n        Action : APPLY\n        Action Time : 21-NOV-2017 15:53:49\n        Description : OJVM RELEASE UPDATE: 12.2.0.1.171017 (26635944)\n        Logfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/26635944\/21607957\/26635944_apply_G100652_CD\nBROOT_2017Nov21_15_53_12.log\n        Status : SUCCESS\n<\/pre>\n
Optional: update the dbclones<\/h2>\n
If you now create a new dbhome, it will be based on the previous dbclone. So you may need to provision a new dbclone to avoid that. If you need the latest dbclone for 18c, patch number is 27604558:<\/p>\n
cd \/u01\/tmp\nunzip p27604558_188000_Linux-x86-64.zip\nodacli update-repository -f \/u01\/tmp\/odacli-dcs-18.8.0.0.0-191226-DB-18.8.0.0.zip\n<\/pre>\n
Now you are able to create a new dbhome from this dbclone:<\/p>\n
odacli create-dbhome -v 18.8.0.0.191015\nodacli list-dbhomes\nID                                       Name                 DB Version                               Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------\n8a2f98f8-2010-4d26-a4b3-2bd5ad8f0b98     OraDB12201_home1     12.2.0.1.191015                          \/u01\/app\/oracle\/product\/12.2.0.1\/dbhome_1     Configured\n8a494efd-e745-4fe9-ace7-2369a36924ff     OraDB11204_home1     11.2.0.4.191015                          \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured\n395451e5-12b9-4851-b331-dd3e650e6d11     OraDB18000_home1     18.8.0.0.191015                          \/u01\/app\/oracle\/product\/18.0.0.0\/dbhome_1     Configured\n<\/pre>\n
Final checks<\/h2>\n
Let’s get the final versions:<\/p>\n
odacli describe-component\nSystem Version\n---------------\n18.8.0.0.0\n \nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       18.8.0.0.0            up-to-date\nGI                                        18.8.0.0.191015       up-to-date\nDB {\n[ OraDB12201_home1 ]                      12.2.0.1.191015       up-to-date\n[ OraDB11204_home1 ]                      11.2.0.4.191015       up-to-date\n[ OraDB18000_home1 ]                      18.8.0.0.191015       up-to-date\n}\nDCSAGENT                                  18.8.0.0.0            up-to-date\nILOM                                      4.0.4.47.r131913      up-to-date\nBIOS                                      41060600              up-to-date\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER                        QDV1RF30              up-to-date\nFIRMWAREDISK                              0121                  up-to-date\n<\/pre>\n
Looks good. Please also check the running processes and compare them to the initial status.<\/p>\n
Cleanse the old patches<\/h2>\n
It’s now possible to cleanse the old patches, they will never be used again. For this ODA, history was:<\/p>\n
Deploy = 12.2.1.2.0 => Patch 12.2.1.4.0 => Patch 18.3.0.0.0 => Patch 18.8.0.0.0<\/code><\/p>\n
Check the filesystems usage before and after cleansing:<\/p>\n
df -h \/opt\nFilesystem            Size  Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolOpt\n                       79G   61G   15G  81% \/opt\n\ndf -h \/u01\nFilesystem            Size  Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolU01\n                      197G  116G   71G  63% \/u01\n\nodacli cleanup-patchrepo -cl -comp db,gi -v 12.2.1.2.0\nodacli cleanup-patchrepo -cl -comp db,gi -v 12.2.1.4.0\nodacli cleanup-patchrepo -cl -comp db,gi -v 18.3.0.0.0\n\n\ndf -h \/opt\nFilesystem            Size  Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolOpt\n                       79G   39G   37G  51% \/opt\ndf -h \/u01\nFilesystem            Size  Used Avail Use% Mounted on\n\/dev\/mapper\/VolGroupSys-LogVolU01\n                      197G  116G   71G  63% \/u01\n<\/pre>\n
Conclusion<\/h2>\n
Your ODA is now in the latest 18c version. Future upgrade will be more serious, OS will jump to Linux 7 and Oracle stack to 19.6. Old X4-2 ODAs will be stuck to 18.8. And remember that 19.5 is not a production release.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction 19c will soon be available for your ODAs. But you may not be ready. Here is how to patch your ODA from 18.3 to 18.8, the very latest 18c release. This patch has here been applied on X7-2M hardware. Download the patch files Patch number is 30518425. This patch is composed of 2 zipfiles […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,199,42,59],"tags":[1916,1917,1476,79,1327,365,572,155,1587,1534,1535,1331,1332,1698,1699],"type_dbi":[],"class_list":["post-13978","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-hardware-storage","category-operating-systems","category-oracle","tag-18-8","tag-18-8-0-0-0","tag-appliance","tag-oda","tag-odacli","tag-oracle-database-appliance","tag-patch","tag-patching","tag-update-server","tag-x6-2m","tag-x6-2s","tag-x7-2m","tag-x7-2s","tag-x8-2m","tag-x8-2s"],"acf":[],"yoast_head":"\nPatching ODA from 18.3 to 18.8 - 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\/patching-oda-from-18-3-to-18-8\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Patching ODA from 18.3 to 18.8\" \/>\n<meta property=\"og:description\" content=\"Introduction 19c will soon be available for your ODAs. But you may not be ready. Here is how to patch your ODA from 18.3 to 18.8, the very latest 18c release. This patch has here been applied on X7-2M hardware. Download the patch files Patch number is 30518425. This patch is composed of 2 zipfiles […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-04-28T09:01:21+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=\"16 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\\\/patching-oda-from-18-3-to-18-8\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"Patching ODA from 18.3 to 18.8\",\"datePublished\":\"2020-04-28T09:01:21+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/\"},\"wordCount\":665,\"commentCount\":0,\"keywords\":[\"18.8\",\"18.8.0.0.0\",\"appliance\",\"ODA\",\"odacli\",\"Oracle database appliance\",\"patch\",\"Patching\",\"update-server\",\"x6-2m\",\"x6-2s\",\"X7-2M\",\"X7-2S\",\"x8-2m\",\"x8-2s\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Hardware & Storage\",\"Operating systems\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/\",\"name\":\"Patching ODA from 18.3 to 18.8 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2020-04-28T09:01:21+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-oda-from-18-3-to-18-8\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patching ODA from 18.3 to 18.8\"}]},{\"@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":"Patching ODA from 18.3 to 18.8 - 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\/patching-oda-from-18-3-to-18-8\/","og_locale":"en_US","og_type":"article","og_title":"Patching ODA from 18.3 to 18.8","og_description":"Introduction 19c will soon be available for your ODAs. But you may not be ready. Here is how to patch your ODA from 18.3 to 18.8, the very latest 18c release. This patch has here been applied on X7-2M hardware. Download the patch files Patch number is 30518425. This patch is composed of 2 zipfiles […]","og_url":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/","og_site_name":"dbi Blog","article_published_time":"2020-04-28T09:01:21+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"16 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"Patching ODA from 18.3 to 18.8","datePublished":"2020-04-28T09:01:21+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/"},"wordCount":665,"commentCount":0,"keywords":["18.8","18.8.0.0.0","appliance","ODA","odacli","Oracle database appliance","patch","Patching","update-server","x6-2m","x6-2s","X7-2M","X7-2S","x8-2m","x8-2s"],"articleSection":["Database Administration & Monitoring","Hardware & Storage","Operating systems","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/","url":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/","name":"Patching ODA from 18.3 to 18.8 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2020-04-28T09:01:21+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-from-18-3-to-18-8\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Patching ODA from 18.3 to 18.8"}]},{"@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\/13978","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=13978"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13978\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13978"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13978"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13978"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13978"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}