{"id":12292,"date":"2019-03-08T17:00:02","date_gmt":"2019-03-08T16:00:02","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/"},"modified":"2019-03-08T17:00:02","modified_gmt":"2019-03-08T16:00:02","slug":"how-to-patch-your-oda-lite-to-18-3-0-0-0","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/","title":{"rendered":"How to patch your ODA lite to 18.3.0.0.0"},"content":{"rendered":"

Even you don’t need 18c, or you’re not ready for this release, this patch will also update your 11gR2, 12cR1 and 12cR2 databases to the latest PSU available on ODA, it means for example the patchset from last July if you’re using 12cR1. Here is how to apply this latest patch for your ODA lite. In this example, the patch was applied on an X6-2S ODA running on previous release: 12.2.1.4.0.<\/p>\n

1) Download the patch<\/strong><\/p>\n

The patch number is 28864490. As usual, this patch will update the following components: dcs (odacli), operating system, bios\/firmwares, storage (on lite it means data disks firmwares), ilom, GI, dbhomes and databases.
\nDownload and copy the patch to a temporary folder on the server, for example \/opt\/patch. You’ll have to be root to apply the patch.<\/p>\n

2) Check the actual versions and free space on disk<\/strong><\/p>\n

First check the current version:<\/p>\n

odacli describe-component\n\nSystem Version\n---------------\n12.2.1.4.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       12.2.1.4.0            up-to-date\nGI                                        12.2.0.1.180417       up-to-date\nDB                                        12.1.0.2.180417       up-to-date\nDCSAGENT                                  18.2.1.0.0            up-to-date\nILOM                                      3.2.9.23.r116695      up-to-date\nBIOS                                      38070200              up-to-date\nOS                                        6.9                   up-to-date\nFIRMWARECONTROLLER {\n[ c2 ]                                    4.650.00-7176         up-to-date\n[ c0,c1 ]                                 KPYAGR3Q              up-to-date\n}\nFIRMWAREDISK                              0R3Q                  up-to-date<\/pre>\n
For the moment, the “available version” column doesn’t know that a newer patch has been released.<\/p>\n
Check that folders \/, \/u01 and \/opt have enough free GB to process (>=20GB). This 18c patch is quite big, so don’t forget that you can extend the \/u01 and \/opt logical volumes online quite easily, for example if you need to increase the \/opt:<\/p>\n
lvextend -L +30G \/dev\/VolGroupSys\/LogVolOpt\nresize2fs \/dev\/VolGroupSys\/LogVolOpt\n<\/pre>\n
If you never changed the logical volume configuration, about 200GB are available on local disks on this kind of ODA.<\/p>\n
3) Prepare the patch files<\/strong><\/p>\n
You need to unzip and register the 3 unzipped files (they are zip files, too).<\/p>\n
cd \/opt\/patch\nunzip p28864490_183000_Linux-x86-64_1of3.zip\nunzip p28864490_183000_Linux-x86-64_2of3.zip\nunzip p28864490_183000_Linux-x86-64_3of3.zip\nodacli update-repository -f \/opt\/patch\/oda-sm-18.3.0.0.0-181205-server1of3.zip\nodacli update-repository -f \/opt\/patch\/oda-sm-18.3.0.0.0-181205-server2of3.zip\nodacli update-repository -f \/opt\/patch\/oda-sm-18.3.0.0.0-181205-server3of3.zip\n<\/pre>\n
Updating the repository, as other tasks through odacli, will generate a job. Check if the 3 latest jobs are OK:<\/p>\n
odacli list-jobs | head -n 3;  odacli list-jobs | tail -n 4\nID                                       Description               Created                             Status\n---------------------------------------- ------------------------- ----------------------------------- ----------\nadd82ae5-3295-49ad-811d-c8c57ebb0cb1     Repository Update         March 7, 2019 1:11:13 PM CET        Success\na057e961-2584-467f-9fc3-d8951dcae213     Repository Update         March 7, 2019 1:11:49 PM CET        Success\n0483dbf8-7562-424e-b7bb-3786558d62b1     Repository Update         March 7, 2019 1:15:31 PM CET        Success\n<\/pre>\n
4) Run the prepatch report<\/strong><\/p>\n
It’s strongly advised to run the prepatch report before patching:<\/p>\n
odacli create-prepatchreport -s -v 18.3.0.0.0\nodacli describe-prepatchreport -i 9112e726-62f1-4e85-9d9c-aec46e8e8210\nPatch pre-check report\n------------------------------------------------------------------------\n                 Job ID:  9112e726-62f1-4e85-9d9c-aec46e8e8210\n            Description:  Patch pre-checks for [OS, ILOM, GI]\n                 Status:  SUCCESS\n                Created:  March 7, 2019 1:41:23 PM CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbi02\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__OS__\nValidate supported versions     Success   Validated minimum supported versions\nValidate patching tag           Success   Validated patching tag: 18.3.0.0.0\nIs patch location available     Success   Patch location is available\nVerify OS patch                 Success   Verified OS patch\n\n__ILOM__\nValidate supported versions     Success   Validated minimum supported versions\nValidate patching tag           Success   Validated patching tag: 18.3.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
Success on all the pre-checked elements is not a patching guarantee: as for each patch you’ll need to manually remove extra rpms and unsupported configurations, like public yum repository (all the package updates have to be done through ODA patches only).<\/p>\n
5) Update the dcs-agent<\/strong><\/p>\n
It seems that it’s no more mandatory to update the dcs-agent before patching the server, it will probably be updated in the same time, but if you want it’s still working:<\/p>\n
\/opt\/oracle\/dcs\/bin\/odacli update-dcsagent -v 18.3.0.0.0\n\nodacli update-dcsagent -v 18.3.0.0.0\n{\n  \"jobId\" : \"5cd58876-3db5-48d5-880e-2ce934545d2f\",\n  \"status\" : \"Created\",\n  \"message\" : \"Dcs agent will be restarted after the update. Please wait for 2-3 mins before executing the other commands\",\n  \"reports\" : [ ],\n  \"createTimestamp\" : \"March 07, 2019 13:35:12 PM CET\",\n  \"resourceList\" : [ ],\n  \"description\" : \"DcsAgent patching\",\n  \"updatedTime\" : \"March 07, 2019 13:35:12 PM CET\"\n}\nodacli list-jobs | head -n 3;  odacli list-jobs | tail -n 2\n\nID                                       Description                         Created                             Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\n5cd58876-3db5-48d5-880e-2ce934545d2f     DcsAgent patching                   March 7, 2019 1:35:12 PM CET        Success\n<\/pre>\n
6) Update the server<\/strong><\/p>\n
Updating the server is the biggest and longest part of the patch, make sure that everything is OK before patching.<\/p>\n
odacli update-server -v 18.3.0.0.0\nodacli describe-job -i \"3a568fb1-8517-405f-9a60-0a1ee285e1ff\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  3a568fb1-8517-405f-9a60-0a1ee285e1ff\n            Description:  Server Patching\n                 Status:  Running\n                Created:  March 7, 2019 4:48:32 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nPatch location validation                March 7, 2019 4:48:32 PM CET        March 7, 2019 4:48:32 PM CET        Success\ndcs-controller upgrade                   March 7, 2019 4:48:32 PM CET        March 7, 2019 4:48:32 PM CET        Success\nPatch location validation                March 7, 2019 4:48:32 PM CET        March 7, 2019 4:48:32 PM CET        Success\ndcs-cli upgrade                          March 7, 2019 4:48:33 PM CET        March 7, 2019 4:48:33 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:33 PM CET        March 7, 2019 4:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:38 PM CET        Success\nUpdating YumPluginVersionLock rpm        March 7, 2019 4:48:38 PM CET        March 7, 2019 4:48:39 PM CET        Success\nApplying OS Patches                      March 7, 2019 4:48:39 PM CET        March 7, 2019 4:51:31 PM CET        Success\nCreating repositories using yum          March 7, 2019 4:51:31 PM CET        March 7, 2019 4:51:32 PM CET        Success\nApplying HMP Patches                     March 7, 2019 4:51:32 PM CET        March 7, 2019 4:51:32 PM CET        Success\nPatch location validation                March 7, 2019 4:51:32 PM CET        March 7, 2019 4:51:32 PM CET        Success\noda-hw-mgmt upgrade                      March 7, 2019 4:51:33 PM CET        March 7, 2019 4:51:33 PM CET        Success\nApplying Firmware Disk Patches           March 7, 2019 4:51:33 PM CET        March 7, 2019 4:51:51 PM CET        Success\nApplying Firmware Expander Patches       March 7, 2019 4:51:51 PM CET        March 7, 2019 4:52:03 PM CET        Success\nApplying Firmware Controller Patches     March 7, 2019 4:52:03 PM CET        March 7, 2019 4:52:16 PM CET        Success\nChecking Ilom patch Version              March 7, 2019 4:52:17 PM CET        March 7, 2019 4:52:19 PM CET        Success\nPatch location validation                March 7, 2019 4:52:19 PM CET        March 7, 2019 4:52:20 PM CET        Success\nSave password in Wallet                  March 7, 2019 4:52:21 PM CET        March 7, 2019 4:52:21 PM CET        Success\nApply Ilom patch                         March 7, 2019 4:52:21 PM CET        March 7, 2019 4:52:22 PM CET        Success\nCopying Flash Bios to Temp location      March 7, 2019 4:52:22 PM CET        March 7, 2019 4:52:22 PM CET        Success\nStarting the clusterware                 March 7, 2019 4:52:22 PM CET        March 7, 2019 4:52:22 PM CET        Success\nCreating GI home directories             March 7, 2019 4:52:22 PM CET        March 7, 2019 4:52:22 PM CET        Success\nCloning Gi home                          March 7, 2019 4:52:22 PM CET        March 7, 2019 4:54:55 PM CET        Success\nConfiguring GI                           March 7, 2019 4:54:55 PM CET        March 7, 2019 4:55:54 PM CET        Success\nRunning GI upgrade root scripts          March 7, 2019 4:55:54 PM CET        March 7, 2019 5:08:19 PM CET        Failure<\/pre>\n
Bad news, GI upgrade failed in my case. Hopefully it’s possible to relaunch the patching and it will skip the already patched components. But another attempt failed 2 steps before (Cloning the Gi home: for sure GI home is already deployed on disk).<\/p>\n
Actually if you already patched your ODA with the previous release, there is a bug with this previous patch:<\/p>\n
ODA GI Patching from 12.2 to 18.3 Failed, CLSRSC-697: Failed to get the value of environment variable ‘TZ’ from the environment file (Doc ID 2502972.1)<\/strong><\/em><\/p>\n
An XML file incorrectly describing the previous Grid Infrastructure home needs to be deleted before applying this newest patch:<\/p>\n
cat '\/u01\/app\/grid\/crsdata\/@global\/crsconfig\/ckptGridHA_global.xml' | grep 12\n         <PROPERTY NAME=\"VERSION\" TYPE=\"STRING\" VAL=\"12.2.0.1.0\"\/>\n         <PROPERTY NAME=\"OLD_CRS_HOME\" TYPE=\"STRING\" VAL=\"\/u01\/app\/12.1.0.2\/grid\"\/>\n         <PROPERTY NAME=\"OLD_CRS_VERSION\" TYPE=\"STRING\" VAL=\"12.1.0.2.0\"\/>\n         <PROPERTY NAME=\"MANUAL_BACKUP_FILE_NAME\" TYPE=\"STRING\" VAL=\"+DATA:\/dbi02-c\/OCRBACKUP\/dbi02-c_backup12.1.0.2.0.ocr.261.987245221\"\/>\nrm '\/u01\/app\/grid\/crsdata\/@global\/crsconfig\/ckptGridHA_global.xml'<\/pre>\n
Before running the patch again, cloned GI home needs to be deleted and its reference in the oraInventory needs to be removed:<\/p>\n
vi \/u01\/app\/oraInventory\/ContentsXML\/inventory.xml\nDelete this line ==>  <HOME NAME=\"OraGrid180\" LOC=\"\/u01\/app\/18.0.0.0\/grid\" TYPE=\"O\" IDX=\"7\" CRS=\"true\"\/> \n\nrm -rf \/u01\/app\/18.0.0.0\n<\/pre>\n
Now the patching will work:<\/p>\n
odacli update-server -v 18.3.0.0.0\nodacli describe-job -i \"3a568fb1-8517-405f-9a60-0a1ee285e1ff\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  3a568fb1-8517-405f-9a60-0a1ee285e1ff\n            Description:  Server Patching\n                 Status:  Success\n                Created:  March 7, 2019 5:48:32 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nPatch location validation                March 7, 2019 5:48:32 PM CET        March 7, 2019 5:48:32 PM CET        Success\ndcs-controller upgrade                   March 7, 2019 5:48:32 PM CET        March 7, 2019 5:48:32 PM CET        Success\nPatch location validation                March 7, 2019 5:48:32 PM CET        March 7, 2019 5:48:32 PM CET        Success\ndcs-cli upgrade                          March 7, 2019 5:48:33 PM CET        March 7, 2019 5:48:33 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:33 PM CET        March 7, 2019 5:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:38 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:38 PM CET        Success\nUpdating YumPluginVersionLock rpm        March 7, 2019 5:48:38 PM CET        March 7, 2019 5:48:39 PM CET        Success\nApplying OS Patches                      March 7, 2019 5:48:39 PM CET        March 7, 2019 5:51:31 PM CET        Success\nCreating repositories using yum          March 7, 2019 5:51:31 PM CET        March 7, 2019 5:51:32 PM CET        Success\nApplying HMP Patches                     March 7, 2019 5:51:32 PM CET        March 7, 2019 5:51:32 PM CET        Success\nPatch location validation                March 7, 2019 5:51:32 PM CET        March 7, 2019 5:51:32 PM CET        Success\noda-hw-mgmt upgrade                      March 7, 2019 5:51:33 PM CET        March 7, 2019 5:51:33 PM CET        Success\nApplying Firmware Disk Patches           March 7, 2019 5:51:33 PM CET        March 7, 2019 5:51:51 PM CET        Success\nApplying Firmware Expander Patches       March 7, 2019 5:51:51 PM CET        March 7, 2019 5:52:03 PM CET        Success\nApplying Firmware Controller Patches     March 7, 2019 5:52:03 PM CET        March 7, 2019 5:52:16 PM CET        Success\nChecking Ilom patch Version              March 7, 2019 5:52:17 PM CET        March 7, 2019 5:52:19 PM CET        Success\nPatch location validation                March 7, 2019 5:52:19 PM CET        March 7, 2019 5:52:20 PM CET        Success\nSave password in Wallet                  March 7, 2019 5:52:21 PM CET        March 7, 2019 5:52:21 PM CET        Success\nApply Ilom patch                         March 7, 2019 5:52:21 PM CET        March 7, 2019 5:52:22 PM CET        Success\nCopying Flash Bios to Temp location      March 7, 2019 5:52:22 PM CET        March 7, 2019 5:52:22 PM CET        Success\nStarting the clusterware                 March 7, 2019 5:52:22 PM CET        March 7, 2019 5:52:22 PM CET        Success\nCreating GI home directories             March 7, 2019 5:52:22 PM CET        March 7, 2019 5:52:22 PM CET        Success\nCloning Gi home                          March 7, 2019 5:52:22 PM CET        March 7, 2019 5:54:55 PM CET        Success\nConfiguring GI                           March 7, 2019 5:54:55 PM CET        March 7, 2019 5:55:54 PM CET        Success\nRunning GI upgrade root scripts          March 7, 2019 5:55:54 PM CET        March 7, 2019 6:08:19 PM CET        Success\nResetting DG compatibility               March 7, 2019 6:08:19 PM CET        March 7, 2019 6:08:29 PM CET        Success\nRunning GI config assistants             March 7, 2019 6:08:29 PM CET        March 7, 2019 6:11:50 PM CET        Success\nrestart oakd                             March 7, 2019 6:11:53 PM CET        March 7, 2019 6:12:03 PM CET        Success\nUpdating GiHome version                  March 7, 2019 6:12:03 PM CET        March 7, 2019 6:12:09 PM CET        Success\nSetting AUDIT SYSLOG LEVEL               March 7, 2019 6:12:30 PM CET        March 7, 2019 6:14:55 PM CET        Success\nUpdate System version                    March 7, 2019 6:14:55 PM CET        March 7, 2019 6:14:55 PM CET        Success\npreRebootNode Actions                    March 7, 2019 6:14:55 PM CET        March 7, 2019 6:15:37 PM CET        Success\nReboot Ilom                              March 7, 2019 6:15:37 PM CET        March 7, 2019 6:15:37 PM CET        Success\n\n<\/pre>\n
Once this part of the patch is successfully applied, let the server reboot automatically 5 minutes after and then check again the 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                                        12.1.0.2.180417       12.1.0.2.180717\nDCSAGENT                                  18.3.0.0.0            up-to-date\nILOM                                      4.0.4.22.r126940      up-to-date\nBIOS                                      38110100              up-to-date\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER {\n[ c2 ]                                    4.650.00-7176         up-to-date\n[ c0,c1 ]                                 KPYAGR3Q              kpyair3q\n}\nFIRMWAREDISK                              0R3Q                  up-to-date\n<\/pre>\n
7) Patch the storage<\/strong><\/p>\n
You now need to patch the storage, understand firmware of data disks:<\/p>\n
odacli update-storage -v 18.3.0.0.0\n{\n  \"jobId\" : \"38a779cf-ac6c-4514-a838-f5cd1bec637c\",\n  \"status\" : \"Created\",\n  \"message\" : \"Success of Storage Update may trigger reboot of node after 4-5 minutes. Please wait till node restart\",\n  \"reports\" : [ ],\n  \"createTimestamp\" : \"March 07, 2019 17:28:34 PM CET\",\n  \"resourceList\" : [ ],\n  \"description\" : \"Storage Firmware Patching\",\n  \"updatedTime\" : \"March 07, 2019 17:28:35 PM CET\"\n}\n\nodacli describe-job -i \"38a779cf-ac6c-4514-a838-f5cd1bec637c\"\nJob details\n----------------------------------------------------------------\n                     ID:  38a779cf-ac6c-4514-a838-f5cd1bec637c\n            Description:  Storage Firmware Patching\n                 Status:  Success\n                Created:  March 7, 2019 5:28:34 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nApplying Firmware Disk Patches           March 7, 2019 5:28:35 PM CET        March 7, 2019 5:28:49 PM CET        Success\nApplying Firmware Controller Patches     March 7, 2019 5:28:49 PM CET        March 7, 2019 5:33:02 PM CET        Success\npreRebootNode Actions                    March 7, 2019 5:33:02 PM CET        March 7, 2019 5:33:02 PM CET        Success\nReboot Ilom                              March 7, 2019 5:33:02 PM CET        March 7, 2019 5:33:02 PM CET        Success\n\nodacli describe-component\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                                        12.1.0.2.180417       12.1.0.2.180717\nDCSAGENT                                  18.3.0.0.0            up-to-date\nILOM                                      4.0.4.22.r126940      up-to-date\nBIOS                                      38110100              up-to-date\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER {\n[ c2 ]                                    4.650.00-7176         up-to-date\n[ c0,c1 ]                                 KPYAIR3Q              up-to-date\n}\nFIRMWAREDISK                              0R3Q                  up-to-date\n\n<\/pre>\n
The server will also reboot after this update.<\/p>\n
8) Patch the dbhomes<\/strong><\/p>\n
You now need to patch the dbhomes separately. First of all, list them:<\/p>\n
odacli list-dbhomes\n\nID                                       Name                 DB Version        Home Location                                 Status\n---------------------------------------- -------------------- ----------------- ------------------------------------------- ----------\n2c28acde-f041-4283-b984-fe6b73dd724d     OraDB12102_home2     12.1.0.2.180417   \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_2     Configured\nebac9543-337b-4edd-8e00-d593abd52ca6     OraDB12102_home10    12.1.0.2.180417   \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_10    Configured\n0ab15f33-e1b7-4193-a110-fa4aee01cc21     OraDB12102_home21    12.1.0.2.180417   \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_21    Configured\n<\/pre>\n
Patch the dbhomes one by one. Target version is actually version of the patch. Remember that updating the ODA through a patch will never upgrade your database to a newer release. Only the PSU number will change (the fifth number which is actually a date).<\/p>\n
odacli update-dbhome -i 2c28acde-f041-4283-b984-fe6b73dd724d -v 18.3.0.0.0\n{\n  \"jobId\" : \"bc3e5564-7283-4497-ac70-9e41c834183d\",\n  \"status\" : \"Created\",\n  \"message\" : null,\n  \"reports\" : [ ],\n  \"createTimestamp\" : \"March 07, 2019 17:45:46 PM CET\",\n  \"resourceList\" : [ ],\n  \"description\" : \"DB Home Patching: Home Id is 2c28acde-f041-4283-b984-fe6b73dd724d\",\n  \"updatedTime\" : \"March 07, 2019 17:45:46 PM CET\"\n}\nodacli describe-job -i \"bc3e5564-7283-4497-ac70-9e41c834183d\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  bc3e5564-7283-4497-ac70-9e41c834183d\n            Description:  DB Home Patching: Home Id is 2c28acde-f041-4283-b984-fe6b73dd724d\n                 Status:  Success\n                Created:  March 7, 2019 5:45:46 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nclusterware patch verification           March 7, 2019 5:45:47 PM CET        March 7, 2019 5:45:52 PM CET        Success\nPatch location validation                March 7, 2019 5:45:52 PM CET        March 7, 2019 5:46:03 PM CET        Success\nOpatch updation                          March 7, 2019 5:48:05 PM CET        March 7, 2019 5:48:09 PM CET        Success\nPatch conflict check                     March 7, 2019 5:48:09 PM CET        March 7, 2019 5:49:45 PM CET        Success\ndb upgrade                               March 7, 2019 5:49:45 PM CET        March 7, 2019 5:55:04 PM CET        Success\nSqlPatch upgrade                         March 7, 2019 5:55:04 PM CET        March 7, 2019 5:55:48 PM CET        Success\nUpdate System version                    March 7, 2019 5:55:48 PM CET        March 7, 2019 5:55:48 PM CET        Success\nupdating the Database version            March 7, 2019 5:55:51 PM CET        March 7, 2019 5:55:54 PM CET        Success\n\n...\n\nodacli list-dbhomes\n\nID                                       Name                 DB Version        Home Location                                 Status\n---------------------------------------- -------------------- ----------------- ------------------------------------------ ----------\n2c28acde-f041-4283-b984-fe6b73dd724d     OraDB12102_home2     12.1.0.2.180717   \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_2     Configured\nebac9543-337b-4edd-8e00-d593abd52ca6     OraDB12102_home10    12.1.0.2.180717   \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_10    Configured\n0ab15f33-e1b7-4193-a110-fa4aee01cc21     OraDB12102_home21    12.1.0.2.180717   \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_21    Configured\n\n<\/pre>\n
9) Optional: deploy the latest db clone files<\/strong><\/p>\n
If you’ll never deploy a new dbhome this is not necessary. If you will, or simply if you don’t know if you’ll have to do that later, download and register the new db clone files in the repository to be able to create a new dbhome at the same patch level than the one already deployed. With this release, you can choose dbhome from various versions: 11gR2, 12cR1, 12cR2 and 18c. <\/p>\n
10) Control the final version of the components<\/strong><\/p>\n
Now the patching is done. \u00b12.5 hours were needed, if everything is running fine.<\/p>\n
oodacli 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                                        12.1.0.2.180717       up-to-date\nDCSAGENT                                  18.3.0.0.0            up-to-date\nILOM                                      4.0.4.22.r126940      up-to-date\nBIOS                                      38110100              up-to-date\nOS                                        6.10                  up-to-date\nFIRMWARECONTROLLER {\n[ c2 ]                                    4.650.00-7176         up-to-date\n[ c0,c1 ]                                 KPYAIR3Q              up-to-date\n}\nFIRMWAREDISK                              0R3Q                  up-to-date<\/pre>\n
11) Latest steps<\/strong><\/p>\n
Don’t forget to remove the patch files and the unzipped files too and check the remaining space on your local disks. Remember to keep your ODA clean and up-to-date.<\/p>\n","protected":false},"excerpt":{"rendered":"
Even you don’t need 18c, or you’re not ready for this release, this patch will also update your 11gR2, 12cR1 and 12cR2 databases to the latest PSU available on ODA, it means for example the patchset from last July if you’re using 12cR1. Here is how to apply this latest patch for your ODA lite. […]<\/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,198,199,59],"tags":[1585,61,79,1327,365,572,1586,1587,1588,867,1329],"type_dbi":[],"class_list":["post-12292","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","category-hardware-storage","category-oracle","tag-18-3-0-0-0","tag-18c","tag-oda","tag-odacli","tag-oracle-database-appliance","tag-patch","tag-update-dbhome","tag-update-server","tag-update-storage","tag-x6","tag-x7"],"acf":[],"yoast_head":"\nHow to patch your ODA lite to 18.3.0.0.0 - dbi Blog<\/title>\n<meta name=\"description\" content=\"How to patch your ODA lite (X6-2 and X7-2) to latest 18c release\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to patch your ODA lite to 18.3.0.0.0\" \/>\n<meta property=\"og:description\" content=\"How to patch your ODA lite (X6-2 and X7-2) to latest 18c release\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-03-08T16:00:02+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=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"How to patch your ODA lite to 18.3.0.0.0\",\"datePublished\":\"2019-03-08T16:00:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\"},\"wordCount\":762,\"commentCount\":0,\"keywords\":[\"18.3.0.0.0\",\"18c\",\"ODA\",\"odacli\",\"Oracle database appliance\",\"patch\",\"update-dbhome\",\"update-server\",\"update-storage\",\"X6\",\"X7\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\",\"Hardware & Storage\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\",\"name\":\"How to patch your ODA lite to 18.3.0.0.0 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2019-03-08T16:00:02+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"description\":\"How to patch your ODA lite (X6-2 and X7-2) to latest 18c release\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to patch your ODA lite to 18.3.0.0.0\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\",\"name\":\"J\u00e9r\u00f4me Dubar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"caption\":\"J\u00e9r\u00f4me Dubar\"},\"description\":\"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How to patch your ODA lite to 18.3.0.0.0 - dbi Blog","description":"How to patch your ODA lite (X6-2 and X7-2) to latest 18c release","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/","og_locale":"en_US","og_type":"article","og_title":"How to patch your ODA lite to 18.3.0.0.0","og_description":"How to patch your ODA lite (X6-2 and X7-2) to latest 18c release","og_url":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/","og_site_name":"dbi Blog","article_published_time":"2019-03-08T16:00:02+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"How to patch your ODA lite to 18.3.0.0.0","datePublished":"2019-03-08T16:00:02+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/"},"wordCount":762,"commentCount":0,"keywords":["18.3.0.0.0","18c","ODA","odacli","Oracle database appliance","patch","update-dbhome","update-server","update-storage","X6","X7"],"articleSection":["Database Administration & Monitoring","Database management","Hardware & Storage","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/","url":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/","name":"How to patch your ODA lite to 18.3.0.0.0 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2019-03-08T16:00:02+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"description":"How to patch your ODA lite (X6-2 and X7-2) to latest 18c release","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-lite-to-18-3-0-0-0\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to patch your ODA lite to 18.3.0.0.0"}]},{"@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\/12292","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=12292"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12292\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12292"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12292"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12292"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}