{"id":789,"date":"2020-08-24T19:48:41","date_gmt":"2020-08-24T22:48:41","guid":{"rendered":"https:\/\/www.fernandosimon.com\/blog\/?p=789"},"modified":"2020-08-24T19:48:41","modified_gmt":"2020-08-24T22:48:41","slug":"patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6","status":"publish","type":"post","link":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/","title":{"rendered":"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6"},"content":{"rendered":"

This is the second part of the ODA patch series, from 18.3 to 19.8. I separate in multiple parts and you can use this second as a direct guide to patch ODA from 18.8 to 19.6. Each part can be used alone since they cover all the needed steps. Parts of this post are similar to the upgrade from 18.3 to 18,8 that I described in my previous post<\/a>.<\/p>\n

The process of patch ODA is not complicated but requires attention over some steps. The 19.6 version was the first that was possible to patch from 18.8 version, and the version that allows upgrades to newer. If you want to go directly to 19.5 you need to reimage of the appliance. In this post, I will cover the process that I made recently to patch from 18.3 to 19.8 version.<\/p>\n

<\/p>\n

Patch Matrix<\/h2>\n

The matrix of what can be done can be found at this post from ODA blog<\/a>, and you can check below:<\/p>\n

\"\"<\/a>Another important detail is to check the MOS note ODA: Quick Reference Matrix for Linux Release and Kernel by ODA Hardware Type and Version (Doc ID 2680219.1)<\/a> and verify if your hardware is still compatible.<\/p>\n

Remember that in this process, the ODA will reboot several times, so, you need to inform your teams that databases will be unavailable during the process.<\/p>\n

Actual environment<\/h2>\n

The environment is ODA X5-2, running the version 18.3. This same environment I reimaged last year, and you can see the steps that I made in a previous post<\/a>. And it running bare metal (BM).<\/p>\n

The first thing to do is to check the actual hardware about errors. If you have, please fix it before the start. Another important detail is to verify if your disks have smartctl warnings. To do that, execute smartctl -q errorsonly -H -l xerror \/dev\/DISK<\/strong>; If you have \u201cSMART Health Status: WARNING: ascq=0x97 [asc=b, ascq=97]<\/em>\u201d report (or similar warning), please open an SR to replace the disks. Even the warning can lead to an error during the patch.<\/p>\n

I recommend you to save outside of ODA some config files from BOTH nodes (to have quick access in case you need):<\/p>\n

[root@odat1 ~]# mkdir \/nfs\/ODA_PATCH_18\/bkp_files_odat1\r\n[root@odat1 ~]# cp \/etc\/hosts \/nfs\/ODA_PATCH_18\/bkp_files_odat1\r\n[root@odat1 ~]# cp \/etc\/fstab \/nfs\/ODA_PATCH_18\/bkp_files_odat1\r\n[root@odat1 ~]# cp \/etc\/resolv.conf \/nfs\/ODA_PATCH_18\/bkp_files_odat1\r\n[root@odat1 ~]# cp \/etc\/sysconfig\/network-scripts\/* \/nfs\/ODA_PATCH_18\/bkp_files_odat1\/\r\ncp: omitting directory `\/etc\/sysconfig\/network-scripts\/backupifcfgFiles'\r\ncp: omitting directory `\/etc\/sysconfig\/network-scripts\/bkupIfcfgOrig'\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# cp \/u01\/app\/18.0.0.0\/grid\/network\/admin\/listener* \/nfs\/ODA_PATCH_18\/bkp_files_odat1\/\r\n[root@odat1 ~]#<\/pre>\n
Another detail before the start is to check the actual components and running versions. To do that we execute the odacli describe-component<\/em>. If we need we just need to update the components with odacli update-storage -v 19.6.0.0.0<\/em>. This will (if some firmware is applied) reboot the ODA.<\/p>\n
The Patch Process<\/h2>\n
The upgrade from 18.8 to 19.6 has two main parts. The first is to upgrade the Linux from OEL 6 to OEL 7. The second is update ODA binaries (DCS and GI) itself.<\/p>\n
The first part is critical and can occur that you need to roll back in case of failure (if you change some parts of Linux as an example \u2013 not recommended, but can occur). To be possible to restore, you need to go to MOS note ODA (Oracle Database Appliance): ODABR a System Backup\/Restore Utility (Doc ID 2466177.1)<\/span><\/a> and download the ODABR. This RPM allows the patch process to generate KVM snapshots (or clones) and roll back in case of need. You can do manual backups if needed (due lack free of pv space \u2013 will talk later).<\/p>\n
Unfortunately for NFS, it does not support xattr attributes changes and this kind of backup can be very tricky.<\/p>\n
The idea is just to have it installed at both nodes. And to do that we just use rpm -Uvh<\/strong> over the downloaded package.<\/p>\n
19.6<\/h2>\n
Update Repository<\/h3>\n
The first step is to upload the unzipped patch (patch number 31010832) files at the internal ODA repository. This process is done using the odacli update-repository<\/strong> and you pass the full path to unzip patch files (here my files are in NFS folder). This generates one jobId that you can follow until it ends. Since is a big patch maybe you receive faulire due lack of space at \/opt<\/strong> (DCS-10802:Insufficient disk space on file system: \/tmp. Expected free space (MB): 22,467, available space (MB): 15,365<\/em>).  If you have free pv space you can increase it:<\/p>\n
[root@odat1 ~]# lvextend -L +10G \/dev\/VolGroupSys\/LogVolOpt\r\n  Size of logical volume VolGroupSys\/LogVolOpt changed from 80.00 GiB (2560 extents) to 90.00 GiB (2880 extents).\r\n  Logical volume VolGroupSys\/LogVolOpt successfully resized.\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# resize2fs \/dev\/VolGroupSys\/LogVolOpt\r\nresize2fs 1.42.9 (28-Dec-2013)\r\nFilesystem at \/dev\/VolGroupSys\/LogVolOpt is mounted on \/opt; on-line resizing required\r\nold_desc_blocks = 5, new_desc_blocks = 6\r\nThe filesystem on \/dev\/VolGroupSys\/LogVolOpt is now 23592960 blocks long.\r\n\r\n[root@odat1 ~]#<\/pre>\n
Calling the upload of files:<\/p>\n
[root@odat1 19.6]# \/opt\/oracle\/dcs\/bin\/odacli update-repository -f \/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server1of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server2of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server3of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server4of4.zip\r\n{\r\n  \"jobId\" : \"e942a1a8-1305-4b79-aef0-eea8dad8cef0\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : \"\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server1of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server2of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server3of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server4of4.zip\",\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 25, 2020 16:33:03 PM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"Repository Update\",\r\n  \"updatedTime\" : \"July 25, 2020 16:33:03 PM CEST\"\r\n}\r\n[root@odat1 19.6]# \r\n[root@odat1 19.6]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"e942a1a8-1305-4b79-aef0-eea8dad8cef0\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  e942a1a8-1305-4b79-aef0-eea8dad8cef0\r\n            Description:  Repository Update\r\n                 Status:  Success\r\n                Created:  July 25, 2020 4:33:03 PM CEST\r\n                Message:  \/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server1of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server2of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server3of4.zip,\/nfs\/ODA_PATCH_18\/19.6\/oda-sm-19.6.0.0.0-200420-server4of4.zip\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nCheck AvailableSpace                     July 25, 2020 4:33:05 PM CEST       July 25, 2020 4:33:05 PM CEST       Success\r\nSetting up ssh equivalance               July 25, 2020 4:33:07 PM CEST       July 25, 2020 4:33:08 PM CEST       Success\r\nCopy BundleFile                          July 25, 2020 4:33:09 PM CEST       July 25, 2020 4:39:02 PM CEST       Success\r\nValidating CopiedFile                    July 25, 2020 4:39:02 PM CEST       July 25, 2020 4:39:49 PM CEST       Success\r\nUnzip bundle                             July 25, 2020 4:39:49 PM CEST       July 25, 2020 5:05:10 PM CEST       Success\r\nUnzip bundle                             July 25, 2020 5:05:10 PM CEST       July 25, 2020 5:08:18 PM CEST       Success\r\nDelete PatchBundles                      July 25, 2020 5:08:26 PM CEST       July 25, 2020 5:08:29 PM CEST       Success\r\nRemoving ssh keys                        July 25, 2020 5:08:29 PM CEST       July 25, 2020 5:22:23 PM CEST       Success\r\n\r\n[root@odat1 19.6]#<\/pre>\n
DCSAgent<\/h3>\n
The next step is to update the internal DCS agent for ODA 18.8. This is a simple step done using the odacli update-dcsagent<\/strong>. Check that the version 19.6.0.0 was specified as a parameter:<\/p>\n
[root@odat1 19.6]# \/opt\/oracle\/dcs\/bin\/odacli update-dcsagent -v 19.6.0.0.0\r\n{\r\n  \"jobId\" : \"45d46df3-fdd8-44bf-a0ad-872237db2f20\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : \"Dcs agent will be restarted after the update. Please wait for 2-3 mins before executing the other commands\",\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 25, 2020 17:23:54 PM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"DcsAgent patching\",\r\n  \"updatedTime\" : \"July 25, 2020 17:23:54 PM CEST\"\r\n}\r\n[root@odat1 19.6]#<\/pre>\n
And again, you can check the jobId and wait it finish:<\/p>\n
[root@odat1 19.6]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"45d46df3-fdd8-44bf-a0ad-872237db2f20\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  45d46df3-fdd8-44bf-a0ad-872237db2f20\r\n            Description:  DcsAgent patching\r\n                 Status:  Success\r\n                Created:  July 25, 2020 5:23:54 PM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\ndcs-agent upgrade  to version 19.6.0.0.0 July 25, 2020 5:23:56 PM CEST       July 25, 2020 5:25:52 PM CEST       Success\r\ndcs-agent upgrade  to version 19.6.0.0.0 July 25, 2020 5:25:52 PM CEST       July 25, 2020 5:27:36 PM CEST       Success\r\nUpdate System version                    July 25, 2020 5:27:40 PM CEST       July 25, 2020 5:27:40 PM CEST       Success\r\nUpdate System version                    July 25, 2020 5:27:40 PM CEST       July 25, 2020 5:27:40 PM CEST       Success\r\n\r\n[root@odat1 19.6]#<\/pre>\n
As in the previous post from 18.3 upgrade, don\u2019t worry because this update will restart the DCS and for a moment the odacli will not work and can report errors (again, don\u2019t worry, it returns):<\/p>\n
[root@odat1 19.6]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"45d46df3-fdd8-44bf-a0ad-872237db2f20\"\r\nDCS-10001:Internal error encountered: Fail to start hand shake to localhost:7070.\r\n[root@odat1 19.6]#<\/pre>\n
Create-prepatchreport \u2013 First Run<\/h3>\n
The next step is to check if is possible to upgrade the operating system. We do that using the odacli create-prepatchreport -v 19.6.0.0.0 -os<\/strong>. Check the \u201c-os\u201d. This is critical.<\/p>\n
[root@odat1 19.6]# \/opt\/oracle\/dcs\/bin\/odacli create-prepatchreport -v 19.6.0.0.0 -os\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  666f7269-7f9a-49b1-8742-2447e94fe54e\r\n            Description:  Patch pre-checks for [OS]\r\n                 Status:  Created\r\n                Created:  July 25, 2020 5:30:42 PM CEST\r\n                Message:  Use 'odacli describe-prepatchreport -i 666f7269-7f9a-49b1-8742-2447e94fe54e' to check details of results\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\n\r\n[root@odat1 19.6]#<\/pre>\n
And you can check the report:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-prepatchreport -i 666f7269-7f9a-49b1-8742-2447e94fe54e\r\n\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n                 Job ID:  666f7269-7f9a-49b1-8742-2447e94fe54e\r\n            Description:  Patch pre-checks for [OS]\r\n                 Status:  FAILED\r\n                Created:  July 25, 2020 5:30:42 PM CEST\r\n                 Result:  One or more pre-checks failed for [OS]\r\n\r\nNode Name\r\n---------------\r\nodat1\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nValidate if ODABR is installed  Success   Validated ODABR is installed\r\nValidate if ODABR snapshots     Success   No ODABR snaps found on the node.\r\nexist\r\nValidate LVM free space         Failed    Insufficient space to create LVM\r\n                                          snapshots on node: odat1. Expected\r\n                                          free space (GB): 190, available space\r\n                                          (GB): 164.\r\nSpace checks for OS upgrade     Success   Validated space checks.\r\nInstall OS upgrade software     Success   Extracted OS upgrade patches into\r\n                                          \/root\/oda-upgrade. Do not remove this\r\n                                          directory untill OS upgrade completes.\r\nVerify OS upgrade by running    Success   Results stored in:\r\npreupgrade checks                         '\/root\/preupgrade-results\/\r\n                                          preupg_results-200725175724.tar.gz' .\r\n                                          Read complete report file\r\n                                          '\/root\/preupgrade\/result.html' before\r\n                                          attempting OS upgrade.\r\nValidate custom rpms installed  Failed    Custom RPMs installed. Please check\r\n                                          files\r\n                                          \/root\/oda-upgrade\/\r\n                                          rpms-added-from-ThirdParty and\/or\r\n                                          \/root\/oda-upgrade\/\r\n                                          rpms-added-from-Oracle.\r\nScheduled jobs check            Failed    Scheduled jobs found. Disable\r\n                                          scheduled jobs before attempting OS\r\n                                          upgrade.\r\n\r\nNode Name\r\n---------------\r\nodat2\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nValidate if ODABR is installed  Success   Validated ODABR is installed\r\nValidate if ODABR snapshots     Success   No ODABR snaps found on the node.\r\nexist\r\nValidate LVM free space         Failed    Insufficient space to create LVM\r\n                                          snapshots on node: odat2. Expected\r\n                                          free space (GB): 190, available space\r\n                                          (GB): 164.\r\nSpace checks for OS upgrade     Success   Validated space checks.\r\nInstall OS upgrade software     Success   Extracted OS upgrade patches into\r\n                                          \/root\/oda-upgrade. Do not remove this\r\n                                          directory untill OS upgrade completes.\r\nVerify OS upgrade by running    Success   Results stored in:\r\npreupgrade checks                         '\/root\/preupgrade-results\/\r\n                                          preupg_results-200725185704.tar.gz' .\r\n                                          Read complete report file\r\n                                          '\/root\/preupgrade\/result.html' before\r\n                                          attempting OS upgrade.\r\nValidate custom rpms installed  Failed    Custom RPMs installed. Please check\r\n                                          files\r\n                                          \/root\/oda-upgrade\/\r\n                                          rpms-added-from-ThirdParty and\/or\r\n                                          \/root\/oda-upgrade\/\r\n                                          rpms-added-from-Oracle.\r\nScheduled jobs check            Failed    Scheduled jobs found. Disable\r\n                                          scheduled jobs before attempting OS\r\n                                          upgrade.\r\n\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
As you can see above FAILED.<\/strong><\/p>\n
Know issue \u2013 Lack of space<\/h4>\n
To ODABR be able to create the LVM snapshot you need at least 190GB of unused space (in each node). If you don\u2019t have this, you can create a manual snapshot and use the \u201c\u2013force\u201d during the call. But you need to run the patchreport at least one time.<\/p>\n
Validate LVM free space         Failed    Insufficient space to create LVM\r\n                                          snapshots on node: odat1. Expected\r\n                                          free space (GB): 190, available space\r\n                                          (GB): 164.<\/pre>\n
One way to clean space is to reduce the \/u01 at this moment. To do that, you need to stop all databases (suppose to already be stopped), stop TFA (fundamental), stop crs, has, and umount the mountpoint \/u01. Maybe the reboot (I recommend) is needed to release some file usage.<\/p>\n
To reduce, first  do e2fsck:<\/p>\n
[root@odat1 ~]# e2fsck -f \/dev\/mapper\/VolGroupSys-LogVolU01\r\ne2fsck 1.43-WIP (20-Jun-2013)\r\nPass 1: Checking inodes, blocks, and sizes\r\nPass 2: Checking directory structure\r\nPass 3: Checking directory connectivity\r\nPass 4: Checking reference counts\r\nPass 5: Checking group summary information\r\n\/dev\/mapper\/VolGroupSys-LogVolU01: 6682323\/11141120 files (0.7% non-contiguous), 30107055\/44564480 blocks\r\n[root@odat1 ~]#<\/pre>\n
After, you can reduce the filesystem with resize2fs:<\/p>\n
[root@odat1 ~]# resize2fs \/dev\/mapper\/VolGroupSys-LogVolU01 130G\r\nresize2fs 1.43-WIP (20-Jun-2013)\r\nResizing the filesystem on \/dev\/mapper\/VolGroupSys-LogVolU01 to 34078720 (4k) blocks.\r\nThe filesystem on \/dev\/mapper\/VolGroupSys-LogVolU01 is now 34078720 blocks long.\r\n\r\n[root@odat1 ~]#<\/pre>\n
And after reducing the logical volume:<\/p>\n
[root@odat1 ~]# lvreduce -L 130G \/dev\/mapper\/VolGroupSys-LogVolU01\r\n  WARNING: Reducing active logical volume to 130.00 GiB.\r\n  THIS MAY DESTROY YOUR DATA (filesystem etc.)\r\nDo you really want to reduce VolGroupSys\/LogVolU01? [y\/n]: y\r\n  Size of logical volume VolGroupSys\/LogVolU01 changed from 170.00 GiB (5440 extents) to 130.00 GiB (4160 extents).\r\n  Logical volume LogVolU01 successfully resized.\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# lvs\r\n  LV         VG          Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert\r\n  LogVolOpt  VolGroupSys -wi-ao----  80.00g\r\n  LogVolRoot VolGroupSys -wi-ao----  50.00g\r\n  LogVolSwap VolGroupSys -wi-ao----  24.00g\r\n  LogVolU01  VolGroupSys -wi-a----- 130.00g\r\n[root@odat1 ~]#<\/pre>\n
After that, you just mount the filesystem, enable crs and has, and reboot both nodes.<\/p>\n
Know issue \u2013 Packages<\/h4>\n
Can occur that you installed some external packages. The need to be removed before the upgrade. The patch report informs it:<\/p>\n
Validate custom rpms installed  Failed    Custom RPMs installed. Please check\r\n                                          files\r\n                                          \/root\/oda-upgrade\/\r\n                                          rpms-added-from-ThirdParty and\/or\r\n                                          \/root\/oda-upgrade\/\r\n                                          rpms-added-from-Oracle.<\/pre>\n
Can be removed with a simple \u201crpm -e\u201d. In my case was iotop ( I removed from both nodes):<\/p>\n
[root@odat1 ~]# cat \/root\/oda-upgrade\/rpms-added-from-Oracle\r\niotop\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# rpm -qa |grep iotop\r\niotop-0.3.2-9.el6.noarch\r\n[root@odat1 ~]# rpm -e iotop-0.3.2-9.el6.noarch\r\n[root@odat1 ~]# cat \/root\/oda-upgrade\/rpms-added-from-ThirdParty\r\ncat: \/root\/oda-upgrade\/rpms-added-from-ThirdParty: No such file or directory\r\n[root@odat1 ~]#<\/pre>\n
Know issues \u2013 ODA Schedules<\/h4>\n
The O.S. upgrade needs the schedules to be disabled before. First, we list the schedules with odacli list-schedules<\/strong>:<\/p>\n
[root@odat1 ~]# odacli list-schedules\r\n\r\nID                                       Name                      Description                                        CronExpression                 Disabled\r\n---------------------------------------- ------------------------- -------------------------------------------------- ------------------------------ --------\r\ne27ebb8c-e80e-4a42-b165-4582bc90c1d1     metastore maintenance     internal metastore maintenance                     0 0 0 1\/1 * ? *                true\r\na779445f-7a29-4d44-99ad-5a3dab0ddd7a     AgentState metastore cleanup internal agentstateentry metastore maintenance     0 0 0 1\/1 * ? *                false\r\n6603842a-a6fc-4f16-9aa1-127402a9c27e     bom maintenance           bom reports generation                             0 0 1 ? * SUN *                false\r\n3eccdca9-72ee-4743-840d-9808d7e0967a     Big File Upload Cleanup   clean up expired big file uploads.                 0 0 1 ? * SUN *                false\r\nf1507855-d881-444f-90a1-73d820746374     feature_tracking_job      Feature tracking job                               0 0 20 ? * WED *               false\r\n6576b40b-6560-4adb-ad27-259ccd1ec069     Log files Cleanup         Auto log file purge bases on policy                0 0 3 1\/1 * ? *                false\r\n[root@odat1 ~]#<\/pre>\n
After we disable all that is with column Disabled equal false:<\/p>\n
[root@odat1 ~]# odacli update-schedule -d -i a779445f-7a29-4d44-99ad-5a3dab0ddd7a\r\nUpdate job schedule success\r\n[root@odat1 ~]#  odacli update-schedule -d -i  6603842a-a6fc-4f16-9aa1-127402a9c27e\r\nUpdate job schedule success\r\n[root@odat1 ~]# odacli update-schedule -d -i  3eccdca9-72ee-4743-840d-9808d7e0967a\r\nUpdate job schedule success\r\n[root@odat1 ~]# odacli update-schedule -d -i  f1507855-d881-444f-90a1-73d820746374\r\nUpdate job schedule success\r\n[root@odat1 ~]# odacli update-schedule -d -i 6576b40b-6560-4adb-ad27-259ccd1ec069\r\nUpdate job schedule success\r\n[root@odat1 ~]# odacli list-schedules\r\n\r\nID                                       Name                      Description                                        CronExpression                 Disabled\r\n---------------------------------------- ------------------------- -------------------------------------------------- ------------------------------ --------\r\ne27ebb8c-e80e-4a42-b165-4582bc90c1d1     metastore maintenance     internal metastore maintenance                     0 0 0 1\/1 * ? *                true\r\na779445f-7a29-4d44-99ad-5a3dab0ddd7a     AgentState metastore cleanup internal agentstateentry metastore maintenance     0 0 0 1\/1 * ? *                true\r\n6603842a-a6fc-4f16-9aa1-127402a9c27e     bom maintenance           bom reports generation                             0 0 1 ? * SUN *                true\r\n3eccdca9-72ee-4743-840d-9808d7e0967a     Big File Upload Cleanup   clean up expired big file uploads.                 0 0 1 ? * SUN *                true\r\nf1507855-d881-444f-90a1-73d820746374     feature_tracking_job      Feature tracking job                               0 0 20 ? * WED *               true\r\n6576b40b-6560-4adb-ad27-259ccd1ec069     Log files Cleanup         Auto log file purge bases on policy                0 0 3 1\/1 * ? *                true\r\n[root@odat1 ~]#<\/pre>\n
If you reboot the ODA node again before the next execution of the patch report, you need to disable the schedule again.<\/p>\n
Create-prepatchreport \u2013 Success Run<\/h3>\n
After fixing the know issues, we can sun again the patchreport and see the success. We do that using the odacli create-prepatchreport -v 19.6.0.0.0 -os<\/strong>, and with odacli describe-prepatchreport:<\/strong><\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli create-prepatchreport -v 19.6.0.0.0 -os\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  5da9f187-af89-4821-b7dc-7451da21761d\r\n            Description:  Patch pre-checks for [OS]\r\n                 Status:  Created\r\n                Created:  July 25, 2020 10:56:19 PM CEST\r\n                Message:  Use 'odacli describe-prepatchreport -i 5da9f187-af89-4821-b7dc-7451da21761d' to check details of results\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\n\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-prepatchreport -i 5da9f187-af89-4821-b7dc-7451da21761d\r\n\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n                 Job ID:  5da9f187-af89-4821-b7dc-7451da21761d\r\n            Description:  Patch pre-checks for [OS]\r\n                 Status:  RUNNING\r\n                Created:  July 25, 2020 10:56:19 PM CEST\r\n                 Result:\r\n\r\nNode Name\r\n---------------\r\nodat1\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nValidate if ODABR is installed  Success   Validated ODABR is installed\r\nValidate if ODABR snapshots     Success   No ODABR snaps found on the node.\r\nexist\r\nValidate LVM free space         Success   LVM free space: 204(GB) on node:odat1\r\nSpace checks for OS upgrade     Success   Validated space checks.\r\nInstall OS upgrade software     Success   Extracted OS upgrade patches into\r\n                                          \/root\/oda-upgrade. Do not remove this\r\n                                          directory untill OS upgrade completes.\r\nVerify OS upgrade by running    Success   Results stored in:\r\npreupgrade checks                         '\/root\/preupgrade-results\/\r\n                                          preupg_results-200725233758.tar.gz' .\r\n                                          Read complete report file\r\n                                          '\/root\/preupgrade\/result.html' before\r\n                                          attempting OS upgrade.\r\nValidate custom rpms installed  Scheduled\r\nScheduled jobs check            Scheduled\r\n\r\nNode Name\r\n---------------\r\nodat2\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nValidate if ODABR is installed  Success   Validated ODABR is installed\r\nValidate if ODABR snapshots     Success   No ODABR snaps found on the node.\r\nexist\r\nValidate LVM free space         Success   LVM free space: 204(GB) on node:odat2\r\nSpace checks for OS upgrade     Success   Validated space checks.\r\nInstall OS upgrade software     Success   Extracted OS upgrade patches into\r\n                                          \/root\/oda-upgrade. Do not remove this\r\n                                          directory untill OS upgrade completes.\r\nVerify OS upgrade by running    Running\r\npreupgrade checks\r\nValidate custom rpms installed  Scheduled\r\nScheduled jobs check            Scheduled\r\n\r\n\r\n\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-prepatchreport -i 5da9f187-af89-4821-b7dc-7451da21761d\r\n\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n                 Job ID:  5da9f187-af89-4821-b7dc-7451da21761d\r\n            Description:  Patch pre-checks for [OS]\r\n                 Status:  SUCCESS\r\n                Created:  July 25, 2020 10:56:19 PM CEST\r\n                 Result:  All pre-checks succeeded\r\n\r\nNode Name\r\n---------------\r\nodat1\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nValidate if ODABR is installed  Success   Validated ODABR is installed\r\nValidate if ODABR snapshots     Success   No ODABR snaps found on the node.\r\nexist\r\nValidate LVM free space         Success   LVM free space: 204(GB) on node:odat1\r\nSpace checks for OS upgrade     Success   Validated space checks.\r\nInstall OS upgrade software     Success   Extracted OS upgrade patches into\r\n                                          \/root\/oda-upgrade. Do not remove this\r\n                                          directory untill OS upgrade completes.\r\nVerify OS upgrade by running    Success   Results stored in:\r\npreupgrade checks                         '\/root\/preupgrade-results\/\r\n                                          preupg_results-200725233758.tar.gz' .\r\n                                          Read complete report file\r\n                                          '\/root\/preupgrade\/result.html' before\r\n                                          attempting OS upgrade.\r\nValidate custom rpms installed  Success   No additional RPMs found installed on\r\n                                          node:odat1.\r\nScheduled jobs check            Success   Verified scheduled jobs\r\n\r\nNode Name\r\n---------------\r\nodat2\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nValidate if ODABR is installed  Success   Validated ODABR is installed\r\nValidate if ODABR snapshots     Success   No ODABR snaps found on the node.\r\nexist\r\nValidate LVM free space         Success   LVM free space: 204(GB) on node:odat2\r\nSpace checks for OS upgrade     Success   Validated space checks.\r\nInstall OS upgrade software     Success   Extracted OS upgrade patches into\r\n                                          \/root\/oda-upgrade. Do not remove this\r\n                                          directory untill OS upgrade completes.\r\nVerify OS upgrade by running    Success   Results stored in:\r\npreupgrade checks                         '\/root\/preupgrade-results\/\r\n                                          preupg_results-200726002222.tar.gz' .\r\n                                          Read complete report file\r\n                                          '\/root\/preupgrade\/result.html' before\r\n                                          attempting OS upgrade.\r\nValidate custom rpms installed  Success   No additional RPMs found installed on\r\n                                          node:odat2.\r\nScheduled jobs check            Success   Verified scheduled jobs\r\n\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
As you can see above, the report was OK, and no errors.<\/p>\n
ILOM<\/h3>\n
To continue the patch is required to call the upgrade from console because it does not generate a job. It calls the process of O.S. itself. Since it does not restart that ILOM (due to patch), we can do ssh to ILOM (do not use ipmcitool) and call  start \/SP\/console<\/strong> to start the process. This is done for BOTH nodes<\/strong>.<\/p>\n
Update-server<\/h3>\n
Inside of the ILOM console and logged at a node, we can call the odacli update-server -v 19.6.0.0.0 -c os –local<\/strong> one node per time (just call the second node if the firs finish with success):<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-server -v 19.6.0.0.0 -c os --local    \r\nVerifying OS upgrade\r\nCurrent OS base version: 6 is lessthan target OS base version: 7\r\nOS needs to upgrade to 7.7\r\n*** Created ODABR snapshot ***\r\n\r\n****************************************************************************\r\n*  Depending on the hardware platform, the upgrade operation, including    *\r\n*  node reboot, may take 30-60 minutes to complete. Individual steps in    *\r\n*  the operation may not show progress messages for a while. Do not abort  *\r\n*  upgrade using ctrl-c or by rebooting the system.                        *\r\n****************************************************************************\r\n\r\nrun: cmd= '[\/usr\/bin\/expect, \/root\/upgradeos.exp]'\r\noutput redirected to \/root\/odaUpgrade2020-07-26_00-45-44.0420.log\r\n\r\nRunning pre-upgrade checks.\r\n.........\r\nRunning assessment of the system\r\n.....................................................................\r\nThe assessment finished.\r\n...\r\nChecking actions and results\r\n.......................................................................................................................................\r\nThe tarball with results is stored in '\/root\/preupgrade-results\/preupg_results-200726005634.tar.gz' .\r\n\r\nThe latest assessment is stored in the '\/root\/preupgrade' directory.\r\n.\r\n2020-07-26--00:56:37 - Creating directory \/root\/preupgrade\/hooks\/oda\/postupgrade\r\n\r\n2020-07-26--00:56:38 - Done installing upgrade tools and running pre-upgrade checks.\r\n.......................\r\nRunning redhat-upgrade-tool\r\n\r\nRunning redhat-upgrade-tool\r\n\r\nRunning upgrade setups\r\n..................\r\nSetting up system for upgrade.\r\n.\r\nNow the system is ready for upgrade OS higher version\r\nReboot the node to finish the upgrade\r\n\r\nNow the system is ready for upgrade OS higher version\r\nReboot the node to finish the upgrade\r\n\r\nRunning redhat-upgrade-tool\r\nReturn code: 0\r\n****************************************************************************\r\n* OS upgrade is successful. The node will reboot now.                      *\r\n****************************************************************************\r\n\r\nYou have new mail in \/var\/spool\/mail\/root\r\n[root@odat1 ~]#\r\nBroadcast message from root@odat1\r\n        (unknown) at 0:58 ...\r\n\r\nThe system is going down for reboot NOW!<\/pre>\n
As you can see above, the node will reboot after one time and complete the process:<\/p>\n
[root@odat1 ~]#\r\nBroadcast message from root@odat1\r\n        (unknown) at 0:58 ...\r\n\r\nThe system is going down for reboot NOW!\r\n...\r\n...\r\n[  OK  ] Created slice system-rdma\\x2dload\\x2dmodules.slice.\r\n         Starting Load RDMA modules from \/etc\/rdma\/modules\/infiniband.conf...\r\n         Starting Load RDMA modules from \/etc\/rdma\/modules\/rdma.conf...\r\n         Starting Load RDMA modules from \/etc\/rdma\/modules\/roce.conf...\r\n[  OK  ] Started Load RDMA modules from \/etc\/rdma\/modules\/infiniband.conf.\r\n[FAILED[   59.313816] ] upgrade-preFailed to start Load RDMA modules from \/etc\/rdma\/modules\/rdma.conf.[8180]:\r\nMerge the copy with `\/sysroot\/bin'.\r\nSee 'systemctl status rdma-load-modules@rdma.service' for details.\r\n[   59.346424] upgrade-pre[8180]: Clean up duplicates in `\/sysroot\/usr\/bin'.\r\n[FAILED] Failed to start Load RDMA modules from \/etc\/rdma\/modules\/roce.conf.\r\n[   59.366246] upgrade-pre[8180]: Make a copy of `\/sysroot\/usr\/sbin'.See 'systemctl status rdma-load-modules@roce.service' for details.\r\n\r\n[   59.376653] upgrade-pre[8180]: Merge the copy with `\/sysroot\/sbin'.\r\n[   59.401286] upgrade-pre[8180]: Clean up duplicates in `\/sysroot\/usr\/sbin'.\r\n[   59.411810] upgrade-pre[8180]: Make a copy of `\/sysroot\/usr\/lib'.\r\n[  OK  ] Reached target RDMA Hardware.\r\n[   60.810484] upgrade-pre[8180]: Merge the copy with `\/sysroot\/lib'.\r\n...\r\n...\r\n[   92.501335] upgrade[9171]: [23\/779] (7%) installing tigervnc-icons-1.8.0-17.0.1.el7...\r\n[   92.539542] upgrade[9171]: [24\/779] (8%) installing vim-filesystem-7.4.629-6.el7...\r\n[   92.576682] upgrade[9171]: [25\/779] (8%) installing ipxe-roms-qemu-20180825-2.git133f4c.el7...\r\n[   92.650862] upgrade[9171]: [26\/779] (8%) installing ncurses-base-5.9-14.20130511.el7_4...\r\n[   92.727926] upgrade[9171]: [27\/779] (8%) installing nss-softokn-freebl-3.44.0-8.0.1.el7_7...\r\n[   92.815910] upgrade[9171]: [28\/779] (8%) installing glibc-common-2.17-292.0.1.el7...\r\n[  100.296337] upgrade[9171]: [29\/779] (8%) installing glibc-2.17-292.0.1.el7...\r\n...\r\n...\r\n[  562.308139] upgrade-post[57158]: Installing : perl-SNMP_Session-1.13-5.el7.noarch                      317\/325\r\n[  562.329945] upgrade-post[57158]: Installing : blktrace-1.0.5-9.el7.x86_64                              318\/325\r\n[  562.344964] upgrade-post[57158]: Installing : perl-Crypt-SSLeay-0.64-5.el7.x86_64                      319\/325\r\n[  562.359884] upgrade-post[57158]: Installing : perl-Perl4-CoreLibs-0.003-7.el7.noarch                   320\/325\r\n[  562.374875] upgrade-post[57158]: Installing : perl-Encode-Detect-1.01-13.el7.x86_64                    321\/325\r\n[  562.411242] upgrade-post[57158]: Installing : perl-File-Slurp-9999.19-6.el7.noarch                     322\/325\r\n...\r\n...\r\n[  649.278013] upgrade-post[57158]: Preparing...                          ########################################\r\n[  649.293346] upgrade-post[57158]: Updating \/ installing...\r\n[  649.396564] upgrade-post[57158]: oracle-hmp-hwmgmt-2.4.5.0.1-1.el7     ########################################\r\n[  649.415607] upgrade-post[57158]: Installing oracle-hmp-snmp-*.rpm\r\n[  649.499052] upgrade-post[57158]: Preparing...                          ########################################\r\n[  649.513352] upgrade-post[57158]: Updating \/ installing...\r\n[  649.539014] upgrade-post[57158]: oracle-hmp-snmp-2.4.5.0.1-1.el7       ########################################\r\n...\r\n...\r\n[  689.039337] upgrade-post[57158]: Installing oda-hw-mgmt-*.rpm\r\n[  689.049298] upgrade-post[57158]: Preparing...                          ########################################\r\n[  689.063309] upgrade-post[57158]: Pre Installation steps in progress ...\r\n[  689.072310] upgrade-post[57158]: Updating \/ installing...\r\n...\r\n...\r\n[  803.635767] upgrade-post[57158]: all upgrade scripts finished\r\n[  803.645130] upgrade-post[57158]: writing logs to disk and rebooting\r\n[  813.014640] reboot: Restarting system\r\n...\r\n...\r\n[  OK  ] Started LSB: Supports the direct execution of binary formats..\r\n[  OK  ] Started Xinetd A Powerful Replacement For Inetd.\r\n[  OK  ] Started Notify NFS peers of a restart.\r\n\r\nOracle Linux Server 7.7\r\nKernel 4.14.35-1902.11.3.1.el7uek.x86_64 on an x86_64\r\n\r\nodat1 login:<\/pre>\n
The same upgrade call is done at node 2:<\/p>\n
[root@odat2 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-server -v 19.6.0.0.0 -c os --local\r\nVerifying OS upgrade\r\nCurrent OS base version: 6 is lessthan target OS base version: 7\r\nOS needs to upgrade to 7.7\r\n*** Created ODABR snapshot ***\r\n\r\n****************************************************************************\r\n*  Depending on the hardware platform, the upgrade operation, including    *\r\n*  node reboot, may take 30-60 minutes to complete. Individual steps in    *\r\n*  the operation may not show progress messages for a while. Do not abort  *\r\n*  upgrade using ctrl-c or by rebooting the system.                        *\r\n****************************************************************************\r\n\r\nrun: cmd= '[\/usr\/bin\/expect, \/root\/upgradeos.exp]'\r\noutput redirected to \/root\/odaUpgrade2020-07-26_01-23-33.0734.log\r\n\r\nRunning pre-upgrade checks.\r\n.........\r\nRunning assessment of the system\r\n......................................................................\r\nThe assessment finished.\r\n..\r\nChecking actions and results\r\n.........................................................................................................................................\r\nThe tarball with results is stored in '\/root\/preupgrade-results\/preupg_results-200726013431.tar.gz' .\r\n\r\nThe latest assessment is stored in the '\/root\/preupgrade' directory.\r\n.\r\n2020-07-26--01:34:34 - Creating directory \/root\/preupgrade\/hooks\/oda\/postupgrade\r\n.\r\n2020-07-26--01:34:35 - Done installing upgrade tools and running pre-upgrade checks.\r\n...............\r\nRunning redhat-upgrade-tool\r\n.\r\nRunning redhat-upgrade-tool\r\n\r\nRunning upgrade setups\r\n...................\r\nSetting up system for upgrade.\r\n..\r\nNow the system is ready for upgrade OS higher version\r\nReboot the node to finish the upgrade\r\n\r\nNow the system is ready for upgrade OS higher version\r\nReboot the node to finish the upgrade\r\n\r\nRunning redhat-upgrade-tool\r\nReturn code: 0\r\n****************************************************************************\r\n* OS upgrade is successful. The node will reboot now.                      *\r\n****************************************************************************\r\n\r\nYou have new mail in \/var\/spool\/mail\/root\r\n[root@odat2 ~]#\r\nBroadcast message from root@odat2\r\n        (unknown) at 1:36 ...\r\n\r\nThe system is going down for reboot NOW!\r\n\r\n\r\n[  OK  ] Started LSB: Supports the direct execution of binary formats..\r\n[  OK  ] Started Notify NFS peers of a restart.\r\n[  OK  ] Started Xinetd A Powerful Replacement For Inetd.\r\n\r\nOracle Linux Server 7.7\r\nKernel 4.14.35-1902.11.3.1.el7uek.x86_64 on an x86_64\r\n\r\nodat2 login:<\/pre>\n
At \/root of each server, you can check the file \/root\/odaUpgradeXXXXXXX.log<\/em> with the verbose execution of the upgrade.<\/p>\n
At this moment just the O.S. was upgraded. The GI was not touched and (if want), you can start databases. But I recommend finishing the process.<\/p>\n
Post Upgrade<\/h3>\n
After upgrade finish in both nodes, we can check if everything was fine with command odacli update-server-postcheck<\/strong>.<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-server-postcheck -v 19.6.0.0.0\r\n\r\nUpgrade post-check report\r\n-------------------------\r\n\r\nNode Name\r\n---------------\r\nodat1\r\n\r\nComp  Pre-Check                      Status   Comments\r\n----- ------------------------------ -------- --------------------------------------\r\nOS    OS upgrade check               SUCCESS  OS has been upgraded to OL7\r\nGI    GI upgrade check               INFO     GI home needs to update to 19.6.0.0.200114\r\nGI    GI status check                SUCCESS  Clusterware is running on the node\r\nOS    ODABR snapshot                 WARNING  ODABR snapshot found. Run 'odabr delsnap' to delete.\r\nRPM   Extra RPM check                SUCCESS  No extra RPMs found when OS was at OL6\r\n\r\nNode Name\r\n---------------\r\nodat2\r\n\r\nComp  Pre-Check                      Status   Comments\r\n----- ------------------------------ -------- --------------------------------------\r\nOS    OS upgrade check               SUCCESS  OS has been upgraded to OL7\r\nGI    GI upgrade check               INFO     GI home needs to update to 19.6.0.0.200114\r\nGI    GI status check                SUCCESS  Clusterware is running on the node\r\nOS    ODABR snapshot                 WARNING  ODABR snapshot found. Run 'odabr delsnap' to delete.\r\nRPM   Extra RPM check                SUCCESS  No extra RPMs found when OS was at OL6\r\n\r\n[root@odat1 ~]#<\/pre>\n
Above we can see some warnings, the most important is the ODABR telling that snapshots can be deleted.<\/p>\n
To do that we just call first odabr infosnap to check the existence of snapshots:<\/p>\n
[root@odat1 ~]# \/opt\/odabr\/odabr infosnap\r\n\r\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\r\n odabr - ODA node Backup Restore - Version: 2.0.1-60\r\n Copyright Oracle, Inc. 2013, 2020\r\n --------------------------------------------------------\r\n Author: Ruggero Citton <ruggero.citton@oracle.com>\r\n RAC Pack, Cloud Innovation and Solution Engineering Team\r\n\u2502\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2502\r\n\r\n\r\nLVM snap name         Status                COW Size              Data%\r\n-------------         ----------            ----------            ------\r\nroot_snap             active                30.00 GiB             27.06%\r\nopt_snap              active                60.00 GiB             3.80%\r\nu01_snap              active                100.00 GiB            1.44%\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
And after delete them:<\/p>\n
[root@odat1 ~]# \/opt\/odabr\/odabr delsnap\r\nINFO: 2020-07-26 09:09:09: Please check the logfile '\/opt\/odabr\/out\/log\/odabr_24797.log' for more details\r\n\r\nINFO: 2020-07-26 09:09:09: Removing LVM snapshots\r\nINFO: 2020-07-26 09:09:09: ...removing LVM snapshot for 'opt'\r\nSUCCESS: 2020-07-26 09:09:09: ...snapshot for 'opt' removed successfully\r\nINFO: 2020-07-26 09:09:09: ...removing LVM snapshot for 'u01'\r\nSUCCESS: 2020-07-26 09:09:10: ...snapshot for 'u01' removed successfully\r\nINFO: 2020-07-26 09:09:10: ...removing LVM snapshot for 'root'\r\nSUCCESS: 2020-07-26 09:09:10: ...snapshot for 'root' removed successfully\r\nSUCCESS: 2020-07-26 09:09:10: Remove LVM snapshots done successfully\r\n[root@odat1 ~]#\r\n[root@odat1 ~]#<\/pre>\n
We do this in BOTH nodes.<\/p>\n
DCSAdmin<\/h3>\n
The next step will be to update the dcsadmin using the command odacli update-dcsadmin<\/strong>:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-dcsadmin -v 19.6.0.0.0\r\n{\r\n  \"jobId\" : \"b4fc6b76-c815-4dd5-a8b7-ddbbd1bd77ae\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : null,\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 26, 2020 09:10:19 AM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"DcsAdmin patching\",\r\n  \"updatedTime\" : \"July 26, 2020 09:10:19 AM CEST\"\r\n}\r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"b4fc6b76-c815-4dd5-a8b7-ddbbd1bd77ae\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  b4fc6b76-c815-4dd5-a8b7-ddbbd1bd77ae\r\n            Description:  DcsAdmin patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 9:10:19 AM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nPatch location validation                July 26, 2020 9:10:21 AM CEST       July 26, 2020 9:10:21 AM CEST       Success\r\nPatch location validation                July 26, 2020 9:10:21 AM CEST       July 26, 2020 9:10:21 AM CEST       Success\r\ndcsadmin upgrade                         July 26, 2020 9:10:23 AM CEST       July 26, 2020 9:10:23 AM CEST       Success\r\ndcsadmin upgrade                         July 26, 2020 9:10:23 AM CEST       July 26, 2020 9:10:23 AM CEST       Success\r\nUpdate System version                    July 26, 2020 9:10:24 AM CEST       July 26, 2020 9:10:24 AM CEST       Success\r\nUpdate System version                    July 26, 2020 9:10:24 AM CEST       July 26, 2020 9:10:24 AM CEST       Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
DCSComponents<\/h3>\n
The next is to update the dcscomponents with command odacli update-dcscomponents<\/strong>. And here one detail. The commands will generate one jobID, but will be invalid and you need to use the command \u201codacli list-jobs<\/strong>\u201d to see the jobs (will be just update SSH keys \u2013 two jobs):<\/p>\n
[root@odat1 ~]#  \/opt\/oracle\/dcs\/bin\/odacli update-dcscomponents -v 19.6.0.0.0\r\n{\r\n  \"jobId\" : \"235a6820-e390-42e1-a4e3-b058c8f9af96\",\r\n  \"status\" : \"Success\",\r\n  \"message\" : null,\r\n  \"reports\" : null,\r\n  \"createTimestamp\" : \"July 26, 2020 09:11:05 AM CEST\",\r\n  \"description\" : \"Job completed and is not part of Agent job list\",\r\n  \"updatedTime\" : \"July 26, 2020 09:11:06 AM CEST\"\r\n}\r\n[root@odat1 ~]# \r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"235a6820-e390-42e1-a4e3-b058c8f9af96\"\r\nDCS-10000:Resource Job with ID 235a6820-e390-42e1-a4e3-b058c8f9af96 is not found.\r\n[root@odat1 ~]# \r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli list-jobs\r\n\r\nID                                       Description                                                                 Created                             Status\r\n---------------------------------------- --------------------------------------------------------------------------- ----------------------------------- ----------\r\n\u2026\r\n666f7269-7f9a-49b1-8742-2447e94fe54e     Patch pre-checks for [OS]                                                   July 25, 2020 5:30:42 PM CEST       Failure\r\n5da9f187-af89-4821-b7dc-7451da21761d     Patch pre-checks for [OS]                                                   July 25, 2020 10:56:19 PM CEST      Success\r\nb4fc6b76-c815-4dd5-a8b7-ddbbd1bd77ae     DcsAdmin patching                                                           July 26, 2020 9:10:19 AM CEST       Success\r\nf3bb0811-cb83-4b9c-a498-b1050a9767ba     SSH keys update                                                             July 26, 2020 9:11:28 AM CEST       Success\r\n0031f81e-5bb8-47c9-8389-2ef266c90363     SSH key delete                                                              July 26, 2020 9:11:33 AM CEST       Success\r\nbde68cf5-f479-4e95-81b8-123639c8ef0f     SSH keys update                                                             July 26, 2020 9:12:02 AM CEST       Success\r\ne1a2a798-4c7e-4ae6-b70c-1eb150b47680     SSH key delete                                                              July 26, 2020 9:12:12 AM CEST       Failure\r\n\r\n[root@odat1 ~]#<\/pre>\n
But as you can see above, there is one failure related to SSH deletion, but this is a known issue documented here<\/a>.<\/p>\n
If you describe the job you can see failure:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"e1a2a798-4c7e-4ae6-b70c-1eb150b47680\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  e1a2a798-4c7e-4ae6-b70c-1eb150b47680\r\n            Description:  SSH key delete\r\n                 Status:  Failure\r\n                Created:  July 26, 2020 9:12:12 AM CEST\r\n                Message:  DCS-10110:Failed to complete the operation.\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\n\r\n[root@odat1 ~]#<\/pre>\n
To solve, you need to remove all the \u201c~root\/.ssh\/id_rsa*<\/strong>\u201d files from both nodes:<\/p>\n
[root@odat1 .ssh]# ssh odat2\r\nLast login: Sun Jul 26 09:17:52 2020 from odat1\r\n[root@odat2 ~]#\r\n[root@odat2 ~]# mv ~root\/.ssh\/id_rsa* \/tmp\r\n[root@odat2 ~]# ls -l ~root\/.ssh\/\r\ntotal 20\r\n-rw-r--r-- 1 root root 1222 Jul 26 09:12 authorized_keys\r\n-rw------- 1 root root 7089 Jul 26 09:12 known_hosts\r\n-rw------- 1 root root 6702 Jul 26 09:11 known_hosts.old\r\n[root@odat2 ~]# logout\r\nConnection to odat2 closed.\r\n[root@odat1 .ssh]#\r\n[root@odat1 .ssh]#  mv ~root\/.ssh\/id_rsa* \/tmp\r\n[root@odat1 .ssh]# ls -l ~root\/.ssh\/\r\ntotal 20\r\n-rw-r--r-- 1 root root 1222 Jul 26 09:12 authorized_keys\r\n-rw------- 1 root root 7948 Jul 26 09:12 known_hosts\r\n-rw------- 1 root root 7561 Jul 26 09:11 known_hosts.old\r\n[root@odat1 .ssh]# ssh odat2\r\nroot@odat2's password:\r\n\r\n[root@odat1 .ssh]# cd\r\n[root@odat1 ~]#<\/pre>\n
And I recommend removing the lock files from oraInventory too (from both nodes):<\/p>\n
[root@odat1 ~]# mv \/u01\/app\/oraInventory\/locks \/tmp\/grid-locks\r\n[root@odat1 ~]#\r\n\r\n[root@odat2 ~]# mv \/u01\/app\/oraInventory\/locks \/tmp\/grid-locks\r\n[root@odat2 ~]#<\/pre>\n
Create-prepatchreport<\/h3>\n
The next step is to verify if you can update it to 19.6 or no. The odacli will do a lot of tests for GI, and ILOM. To do that, we just need to call odacli create-prepatchreport<\/strong>, and after that use the odacli describe-prepatchreport<\/strong> to check the report:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli create-prepatchreport -s -v 19.6.0.0.0\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  de5d169c-bebf-4441-9fa8-4e30efc971de\r\n            Description:  Patch pre-checks for [ILOM, GI, ORACHKSERVER]\r\n                 Status:  Created\r\n                Created:  July 26, 2020 9:26:05 AM CEST\r\n                Message:  Use 'odacli describe-prepatchreport -i de5d169c-bebf-4441-9fa8-4e30efc971de' to check details of results\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\n\r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-prepatchreport -i de5d169c-bebf-4441-9fa8-4e30efc971de\r\n\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n                 Job ID:  de5d169c-bebf-4441-9fa8-4e30efc971de\r\n            Description:  Patch pre-checks for [ILOM, GI, ORACHKSERVER]\r\n                 Status:  FAILED\r\n                Created:  July 26, 2020 9:26:05 AM CEST\r\n                 Result:  One or more pre-checks failed for [ORACHK]\r\n\r\nNode Name\r\n---------------\r\nodat1\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__ILOM__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nChecking Ilom patch Version     Success   Successfully verified the versions\r\nPatch location validation       Success   Successfully validated location\r\n\r\n__GI__\r\nValidate supported GI versions  Success   Validated minimum supported versions.\r\nValidate available space        Success   Validated free space under \/u01\r\nVerify DB Home versions         Success   Verified DB Home versions\r\nValidate patching locks         Success   Validated patching locks\r\nValidate clones location exist  Success   Validated clones location\r\nValidate ODABR snapshots exist  Success   No ODABR snaps found on the node.\r\n\r\n__ORACHK__\r\nRunning orachk                  Failed    Failed to run Orachk: Failed to run\r\n                                          orachk.\r\n\r\nNode Name\r\n---------------\r\nodat2\r\n\r\nPre-Check                      Status   Comments\r\n------------------------------ -------- --------------------------------------\r\n__ILOM__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.6.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nChecking Ilom patch Version     Success   Successfully verified the versions\r\nPatch location validation       Success   Successfully validated location\r\n\r\n__GI__\r\nValidate supported GI versions  Success   Validated minimum supported versions.\r\nValidate available space        Success   Validated free space under \/u01\r\nVerify DB Home versions         Success   Verified DB Home versions\r\nValidate patching locks         Success   Validated patching locks\r\nValidate clones location exist  Success   Validated clones location\r\nValidate ODABR snapshots exist  Success   No ODABR snaps found on the node.\r\n\r\n__ORACHK__\r\nRunning orachk                  Failed    Failed to run Orachk: Failed to run\r\n                                          orachk.\r\n\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
As you can see above, the orachk fails. But as documented at release notes, this can be ignored<\/a>. From 19.6 to 19.7 I address this error, but since there is no database running this can be ignored. If you want to check what is the error, you can go at folder \/opt\/oracle\/dcs\/oracle.ahf\/orachk\/SERVER\/<jobId> \/orachk_odat1_<*>\/<\/em> and check the HTML result.<\/p>\n
Update-server<\/h3>\n
After the success of the report, we can call the odacli update-server. And here the magic occurs: GI, and ILOM are updated:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-server -v 19.6.0.0.0\r\n{\r\n  \"jobId\" : \"98623be2-f0ff-4ec6-be7b-79331eb32380\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : \"Success of server update will trigger reboot of the node after 4-5 minutes. Please wait until the node reboots.\",\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 26, 2020 09:30:44 AM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"Server Patching\",\r\n  \"updatedTime\" : \"July 26, 2020 09:30:44 AM CEST\"\r\n}\r\n[root@odat1 ~]#<\/pre>\n
As you imagine, a jobIB is generated and we can follow it until it finishes:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"98623be2-f0ff-4ec6-be7b-79331eb32380\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  98623be2-f0ff-4ec6-be7b-79331eb32380\r\n            Description:  Server Patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 9:30:44 AM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nPatch location validation                July 26, 2020 9:31:08 AM CEST       July 26, 2020 9:31:08 AM CEST       Success\r\nPatch location validation                July 26, 2020 9:31:08 AM CEST       July 26, 2020 9:31:08 AM CEST       Success\r\ndcs-controller upgrade                   July 26, 2020 9:31:10 AM CEST       July 26, 2020 9:31:10 AM CEST       Success\r\ndcs-controller upgrade                   July 26, 2020 9:31:10 AM CEST       July 26, 2020 9:31:10 AM CEST       Success\r\nCreating repositories using yum          July 26, 2020 9:31:12 AM CEST       July 26, 2020 9:31:14 AM CEST       Success\r\nApplying HMP Patches                     July 26, 2020 9:31:14 AM CEST       July 26, 2020 9:31:15 AM CEST       Success\r\nPatch location validation                July 26, 2020 9:31:17 AM CEST       July 26, 2020 9:31:17 AM CEST       Success\r\nPatch location validation                July 26, 2020 9:31:17 AM CEST       July 26, 2020 9:31:17 AM CEST       Success\r\noda-hw-mgmt upgrade                      July 26, 2020 9:31:19 AM CEST       July 26, 2020 9:31:19 AM CEST       Success\r\noda-hw-mgmt upgrade                      July 26, 2020 9:31:19 AM CEST       July 26, 2020 9:31:20 AM CEST       Success\r\nOSS Patching                             July 26, 2020 9:31:21 AM CEST       July 26, 2020 9:31:22 AM CEST       Success\r\nApplying Firmware Disk Patches           July 26, 2020 9:33:10 AM CEST       July 26, 2020 9:35:01 AM CEST       Success\r\nApplying Firmware Expander Patches       July 26, 2020 9:35:16 AM CEST       July 26, 2020 9:35:35 AM CEST       Success\r\nApplying Firmware Controller Patches     July 26, 2020 9:35:48 AM CEST       July 26, 2020 9:36:06 AM CEST       Success\r\nChecking Ilom patch Version              July 26, 2020 9:36:08 AM CEST       July 26, 2020 9:36:10 AM CEST       Success\r\nChecking Ilom patch Version              July 26, 2020 9:36:10 AM CEST       July 26, 2020 9:36:13 AM CEST       Success\r\nPatch location validation                July 26, 2020 9:36:13 AM CEST       July 26, 2020 9:36:14 AM CEST       Success\r\nPatch location validation                July 26, 2020 9:36:13 AM CEST       July 26, 2020 9:36:14 AM CEST       Success\r\nSave password in Wallet                  July 26, 2020 9:36:16 AM CEST       July 26, 2020 9:36:16 AM CEST       Success\r\nApply Ilom patch                         July 26, 2020 9:36:17 AM CEST       July 26, 2020 9:36:18 AM CEST       Success\r\nApply Ilom patch                         July 26, 2020 9:36:18 AM CEST       July 26, 2020 9:36:19 AM CEST       Success\r\nCopying Flash Bios to Temp location      July 26, 2020 9:36:19 AM CEST       July 26, 2020 9:36:19 AM CEST       Success\r\nCopying Flash Bios to Temp location      July 26, 2020 9:36:19 AM CEST       July 26, 2020 9:36:19 AM CEST       Success\r\nStarting the clusterware                 July 26, 2020 9:38:29 AM CEST       July 26, 2020 9:40:13 AM CEST       Success\r\nCreating GI home directories             July 26, 2020 9:40:17 AM CEST       July 26, 2020 9:40:17 AM CEST       Success\r\nCloning Gi home                          July 26, 2020 9:40:17 AM CEST       July 26, 2020 9:44:10 AM CEST       Success\r\nCloning Gi home                          July 26, 2020 9:44:10 AM CEST       July 26, 2020 9:48:05 AM CEST       Success\r\nConfiguring GI                           July 26, 2020 9:48:05 AM CEST       July 26, 2020 9:52:19 AM CEST       Success\r\nRunning GI upgrade root scripts          July 26, 2020 10:09:20 AM CEST      July 26, 2020 10:21:17 AM CEST      Success\r\nResetting DG compatibility               July 26, 2020 10:21:42 AM CEST      July 26, 2020 10:22:11 AM CEST      Success\r\nRunning GI config assistants             July 26, 2020 10:22:11 AM CEST      July 26, 2020 10:24:24 AM CEST      Success\r\nrestart oakd                             July 26, 2020 10:24:36 AM CEST      July 26, 2020 10:24:48 AM CEST      Success\r\nUpdating GiHome version                  July 26, 2020 10:24:49 AM CEST      July 26, 2020 10:24:57 AM CEST      Success\r\nUpdating GiHome version                  July 26, 2020 10:24:49 AM CEST      July 26, 2020 10:24:57 AM CEST      Success\r\nUpdate System version                    July 26, 2020 10:25:18 AM CEST      July 26, 2020 10:25:19 AM CEST      Success\r\nUpdate System version                    July 26, 2020 10:25:19 AM CEST      July 26, 2020 10:25:19 AM CEST      Success\r\npreRebootNode Actions                    July 26, 2020 10:25:20 AM CEST      July 26, 2020 10:26:17 AM CEST      Success\r\npreRebootNode Actions                    July 26, 2020 10:26:17 AM CEST      July 26, 2020 10:27:08 AM CEST      Success\r\nReboot Ilom                              July 26, 2020 10:27:08 AM CEST      July 26, 2020 10:27:08 AM CEST      Success\r\nReboot Ilom                              July 26, 2020 10:27:08 AM CEST      July 26, 2020 10:27:09 AM CEST      Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
In ODAX5-2 this process took almost 1 hour. And passed all the updates. If you follow the \/opt\/oracle\/dcs\/log\/dcs-agent.log<\/strong> you can see more detail. At this moment, the GI was upgraded to 19.6.<\/p>\n
After this jobID finishes, the ODA will reboot (between the end of the job and reboot can be around 10 minutes).<\/p>\n
Update-storage<\/h3>\n
The last step is to patch the storage with command odacli update-storage<\/strong>. This is needed because the previous step does not updates the firmware of the disks as an example.<\/p>\n
You can see from odacli describe-component<\/strong> that some part are not up to date:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-component\r\nSystem Version\r\n---------------\r\n19.6.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\nodat1\r\n\r\nLocal System Version\r\n---------------\r\n19.6.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.6.0.0.0            up-to-date\r\n\r\nGI                                        19.6.0.0.200114       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.9.0.0.200114\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200114\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200114\r\n}\r\n\r\nDCSAGENT                                  19.6.0.0.0            up-to-date\r\n\r\nILOM                                      4.0.4.52.r132805      up-to-date\r\n\r\nBIOS                                      30300200              up-to-date\r\n\r\nOS                                        7.7                   up-to-date\r\n\r\nFIRMWARECONTROLLER {\r\n[ c0 ]                                    4.650.00-7176         up-to-date\r\n[ c1,c2 ]                                 13.00.00.00           up-to-date\r\n}\r\n\r\nFIRMWAREEXPANDER                          001E                  up-to-date\r\n\r\nFIRMWAREDISK {\r\n[ c0d0,c0d1 ]                             A7E0                  up-to-date\r\n[ c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c1d6,     PD51                  up-to-date\r\nc1d7,c1d8,c1d9,c1d10,c1d11,c1d12,c1d13,\r\nc1d14,c1d15,c2d0,c2d1,c2d2,c2d3,c2d4,\r\nc2d5,c2d6,c2d7,c2d8,c2d9,c2d10,c2d11,\r\nc2d12,c2d13,c2d14,c2d15 ]\r\n[ c1d16,c1d17,c1d18,c1d19,c1d20,c1d21,    A29A                  up-to-date\r\nc1d22,c1d23,c2d16,c2d17,c2d18,c2d19,\r\nc2d20,c2d21,c2d22,c2d23 ]\r\n}\r\n\r\nHMP                                       2.4.5.0.1             up-to-date\r\n\r\nSystem node Name\r\n---------------\r\nodat2\r\n\r\nLocal System Version\r\n---------------\r\n19.6.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.6.0.0.0            up-to-date\r\n\r\nGI                                        19.6.0.0.200114       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.9.0.0.200114\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200114\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200114\r\n}\r\n\r\nDCSAGENT                                  19.6.0.0.0            up-to-date\r\n\r\nILOM                                      4.0.4.52.r132805      up-to-date\r\n\r\nBIOS                                      30300200              up-to-date\r\n\r\nOS                                        7.7                   up-to-date\r\n\r\nFIRMWARECONTROLLER {\r\n[ c0 ]                                    4.650.00-7176         up-to-date\r\n[ c1,c2 ]                                 13.00.00.00           up-to-date\r\n}\r\n\r\nFIRMWAREEXPANDER                          001E                  up-to-date\r\n\r\nFIRMWAREDISK {\r\n[ c0d0,c0d1 ]                             A7E0                  up-to-date\r\n[ c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c1d6,     PD51                  up-to-date\r\nc1d7,c1d8,c1d9,c1d10,c1d11,c1d12,c1d13,\r\nc1d14,c1d15,c2d0,c2d1,c2d2,c2d3,c2d4,\r\nc2d5,c2d6,c2d7,c2d8,c2d9,c2d10,c2d11,\r\nc2d12,c2d13,c2d14,c2d15 ]\r\n[ c1d16,c1d17,c1d18,c1d19,c1d20,c1d21,    A29A                  up-to-date\r\nc1d22,c1d23,c2d16,c2d17,c2d18,c2d19,\r\nc2d20,c2d21,c2d22,c2d23 ]\r\n}\r\n\r\nHMP                                       2.4.5.0.1             up-to-date\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
And we can update calling the odacli update-storage<\/strong>:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-storage -v 19.6.0.0.0\r\n{\r\n  \"jobId\" : \"081de564-2cc1-4cb9-b18e-b3d5c484c58d\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : \"Success of Storage Update may trigger reboot of node after 4-5 minutes. Please wait till node restart\",\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 26, 2020 10:42:51 AM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"Storage Firmware Patching\",\r\n  \"updatedTime\" : \"July 26, 2020 10:42:51 AM CEST\"\r\n}\r\n[root@odat1 ~]#\r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"081de564-2cc1-4cb9-b18e-b3d5c484c58d\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  081de564-2cc1-4cb9-b18e-b3d5c484c58d\r\n            Description:  Storage Firmware Patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 10:42:51 AM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nApplying Firmware Disk Patches           July 26, 2020 10:47:24 AM CEST      July 26, 2020 10:50:27 AM CEST      Success\r\nApplying Firmware Controller Patches     July 26, 2020 10:50:42 AM CEST      July 26, 2020 10:51:00 AM CEST      Success\r\npreRebootNode Actions                    July 26, 2020 10:51:01 AM CEST      July 26, 2020 10:51:01 AM CEST      Success\r\npreRebootNode Actions                    July 26, 2020 10:51:01 AM CEST      July 26, 2020 10:51:01 AM CEST      Success\r\nReboot Ilom                              July 26, 2020 10:51:01 AM CEST      July 26, 2020 10:51:01 AM CEST      Success\r\nReboot Ilom                              July 26, 2020 10:51:02 AM CEST      July 26, 2020 10:51:02 AM CEST      Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
After the job finish (and after around 10 minutes) the ODA will reboot automatically.<\/p>\n
And you can see that now that everything is up to date:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-component\r\nSystem Version\r\n---------------\r\n19.6.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\nodat1\r\n\r\nLocal System Version\r\n---------------\r\n19.6.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.6.0.0.0            up-to-date\r\n\r\nGI                                        19.6.0.0.200114       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.9.0.0.200114\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200114\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200114\r\n}\r\n\r\nDCSAGENT                                  19.6.0.0.0            up-to-date\r\n\r\nILOM                                      4.0.4.52.r132805      up-to-date\r\n\r\nBIOS                                      30300200              up-to-date\r\n\r\nOS                                        7.7                   up-to-date\r\n\r\nFIRMWARECONTROLLER {\r\n[ c0 ]                                    4.650.00-7176         up-to-date\r\n[ c1,c2 ]                                 13.00.00.00           up-to-date\r\n}\r\n\r\nFIRMWAREEXPANDER                          001E                  up-to-date\r\n\r\nFIRMWAREDISK {\r\n[ c0d0,c0d1 ]                             A7E0                  up-to-date\r\n[ c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c1d6,     PD51                  up-to-date\r\nc1d7,c1d8,c1d9,c1d10,c1d11,c1d12,c1d13,\r\nc1d14,c1d15,c2d0,c2d1,c2d2,c2d3,c2d4,\r\nc2d5,c2d6,c2d7,c2d8,c2d9,c2d10,c2d11,\r\nc2d12,c2d13,c2d14,c2d15 ]\r\n[ c1d16,c1d17,c1d18,c1d19,c1d20,c1d21,    A29A                  up-to-date\r\nc1d22,c1d23,c2d16,c2d17,c2d18,c2d19,\r\nc2d20,c2d21,c2d22,c2d23 ]\r\n}\r\n\r\nHMP                                       2.4.5.0.1             up-to-date\r\n\r\nSystem node Name\r\n---------------\r\nodat2\r\n\r\nLocal System Version\r\n---------------\r\n19.6.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.6.0.0.0            up-to-date\r\n\r\nGI                                        19.6.0.0.200114       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.9.0.0.200114\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200114\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200114\r\n}\r\n\r\nDCSAGENT                                  19.6.0.0.0            up-to-date\r\n\r\nILOM                                      4.0.4.52.r132805      up-to-date\r\n\r\nBIOS                                      30300200              up-to-date\r\n\r\nOS                                        7.7                   up-to-date\r\n\r\nFIRMWARECONTROLLER {\r\n[ c0 ]                                    4.650.00-7176         up-to-date\r\n[ c1,c2 ]                                 13.00.00.00           up-to-date\r\n}\r\n\r\nFIRMWAREEXPANDER                          001E                  up-to-date\r\n\r\nFIRMWAREDISK {\r\n[ c0d0,c0d1 ]                             A7E0                  up-to-date\r\n[ c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c1d6,     PD51                  up-to-date\r\nc1d7,c1d8,c1d9,c1d10,c1d11,c1d12,c1d13,\r\nc1d14,c1d15,c2d0,c2d1,c2d2,c2d3,c2d4,\r\nc2d5,c2d6,c2d7,c2d8,c2d9,c2d10,c2d11,\r\nc2d12,c2d13,c2d14,c2d15 ]\r\n[ c1d16,c1d17,c1d18,c1d19,c1d20,c1d21,    A29A                  up-to-date\r\nc1d22,c1d23,c2d16,c2d17,c2d18,c2d19,\r\nc2d20,c2d21,c2d22,c2d23 ]\r\n}\r\n\r\nHMP                                       2.4.5.0.1             up-to-date\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
 <\/strong><\/p>\n
Disclaimer<\/strong>: \u201cThe postings on this site are my own and don\u2019t necessarily represent my actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications were removed to allow reach the generic audience and to be useful for the community. Post protected by copyright.\u201d<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
This is the second part of the ODA patch series, from 18.3 to 19.8. I separate in multiple parts and you can use this second as a direct guide to patch ODA from 18.8 to 19.6. Each part can be used alone since they cover all the needed steps. Parts of this post are similar […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[29,77,78,5,14,12],"tags":[100,79,65,135,124],"class_list":["post-789","post","type-post","status-publish","format-standard","hentry","category-database","category-engineeredsystems","category-oda","category-oracle","category-update","category-upgrade","tag-engineered-systems","tag-oda","tag-oracle","tag-patch","tag-upgrade"],"yoast_head":"\nPatch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6 - Fernando Simon<\/title>\n<meta name=\"description\" content=\"How to upgrade ODA from 18.8 to 19.6 version. All patch steps: S.O, odabr, odacli, GI, and all errors and known issues covered in detail.\" \/>\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.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6 - Fernando Simon\" \/>\n<meta property=\"og:description\" content=\"How to upgrade ODA from 18.8 to 19.6 version. All patch steps: S.O, odabr, odacli, GI, and all errors and known issues covered in detail.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/\" \/>\n<meta property=\"og:site_name\" content=\"Fernando Simon\" \/>\n<meta property=\"article:published_time\" content=\"2020-08-24T22:48:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg\" \/>\n<meta name=\"author\" content=\"Simon\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Simon\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"38 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/\"},\"author\":{\"name\":\"Simon\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/#\\\/schema\\\/person\\\/386da956604bca0d5be5dd52210c1dd9\"},\"headline\":\"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6\",\"datePublished\":\"2020-08-24T22:48:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/\"},\"wordCount\":1780,\"commentCount\":7,\"image\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/08\\\/19cmatrix.jpg\",\"keywords\":[\"Engineered Systems\",\"ODA\",\"Oracle\",\"Patch\",\"Upgrade\"],\"articleSection\":[\"Database\",\"Engineered Systems\",\"ODA\",\"Oracle\",\"Update\",\"Upgrade\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/\",\"url\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/\",\"name\":\"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6 - Fernando Simon\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/08\\\/19cmatrix.jpg\",\"datePublished\":\"2020-08-24T22:48:41+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/#\\\/schema\\\/person\\\/386da956604bca0d5be5dd52210c1dd9\"},\"description\":\"How to upgrade ODA from 18.8 to 19.6 version. All patch steps: S.O, odabr, odacli, GI, and all errors and known issues covered in detail.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/08\\\/19cmatrix.jpg\",\"contentUrl\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/wp-content\\\/uploads\\\/2020\\\/08\\\/19cmatrix.jpg\",\"width\":963,\"height\":505},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/\",\"name\":\"Fernando Simon\",\"description\":\"Have you hugged your backup today?\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/#\\\/schema\\\/person\\\/386da956604bca0d5be5dd52210c1dd9\",\"name\":\"Simon\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g\",\"caption\":\"Simon\"},\"sameAs\":[\"http:\\\/\\\/www.fernandosimon.com\"],\"url\":\"https:\\\/\\\/www.fernandosimon.com\\\/blog\\\/author\\\/simon\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6 - Fernando Simon","description":"How to upgrade ODA from 18.8 to 19.6 version. All patch steps: S.O, odabr, odacli, GI, and all errors and known issues covered in detail.","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.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/","og_locale":"en_US","og_type":"article","og_title":"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6 - Fernando Simon","og_description":"How to upgrade ODA from 18.8 to 19.6 version. All patch steps: S.O, odabr, odacli, GI, and all errors and known issues covered in detail.","og_url":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/","og_site_name":"Fernando Simon","article_published_time":"2020-08-24T22:48:41+00:00","og_image":[{"url":"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg","type":"","width":"","height":""}],"author":"Simon","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Simon","Est. reading time":"38 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#article","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/"},"author":{"name":"Simon","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"headline":"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6","datePublished":"2020-08-24T22:48:41+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/"},"wordCount":1780,"commentCount":7,"image":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#primaryimage"},"thumbnailUrl":"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg","keywords":["Engineered Systems","ODA","Oracle","Patch","Upgrade"],"articleSection":["Database","Engineered Systems","ODA","Oracle","Update","Upgrade"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/","url":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/","name":"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6 - Fernando Simon","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#primaryimage"},"image":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#primaryimage"},"thumbnailUrl":"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg","datePublished":"2020-08-24T22:48:41+00:00","author":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"description":"How to upgrade ODA from 18.8 to 19.6 version. All patch steps: S.O, odabr, odacli, GI, and all errors and known issues covered in detail.","breadcrumb":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#primaryimage","url":"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg","contentUrl":"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg","width":963,"height":505},{"@type":"BreadcrumbList","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-2-18-8-to-19-6\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fernandosimon.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Patch ODA from 18.3 to 19.8. Part 2 \u2013 18.8 to 19.6"}]},{"@type":"WebSite","@id":"https:\/\/www.fernandosimon.com\/blog\/#website","url":"https:\/\/www.fernandosimon.com\/blog\/","name":"Fernando Simon","description":"Have you hugged your backup today?","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fernandosimon.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9","name":"Simon","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a3dbc48de62fffb1829befb4a588d789ec6dc5e05977afabb3407a5f37a16482?s=96&d=mm&r=g","caption":"Simon"},"sameAs":["http:\/\/www.fernandosimon.com"],"url":"https:\/\/www.fernandosimon.com\/blog\/author\/simon\/"}]}},"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5ofTp-cJ","jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/789","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/comments?post=789"}],"version-history":[{"count":0,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/789\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/media?parent=789"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/categories?post=789"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/tags?post=789"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}