{"id":791,"date":"2020-09-07T17:03:16","date_gmt":"2020-09-07T20:03:16","guid":{"rendered":"https:\/\/www.fernandosimon.com\/blog\/?p=791"},"modified":"2020-09-07T17:03:16","modified_gmt":"2020-09-07T20:03:16","slug":"patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7","status":"publish","type":"post","link":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/","title":{"rendered":"Patch ODA from 18.3 to 19.8. Part 3 \u2013 19.6 to 19.7"},"content":{"rendered":"

This is the third part of the ODA patch series, from 18.3 to 19.8. I separate in multiple parts and you can use this part as a direct guide to patch ODA from 19.6 to 19.7. Each part can be used alone since they cover all the needed steps. Some steps of this post are similar to the upgrade from 18.8 to 19.6 that I described in the 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 19.6. 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<\/em>. This will (if some firmware is applied) reboot the ODA.<\/p>\n
Before starting the patch I recommend stopping all databases running at ODA. This will speed up the process. So, left just GI and ASM running.<\/p>\n
If you got any error in the next steps related to lack of space. You can check my previous posts of this series because there I describe how to increase the filesystem if needed. And I also show how to decrease the filesystem as well (like \/u01) to have raw space that can be allocated to other mountpoints.<\/p>\n
19.7<\/h2>\n
The upgrade from 19.6 to 19.7 is a simple process and follows a well know procedure. In this process, we do not upgrade Linux (like 18.8 to 19.6), just some new rpms and we upgrade the GI to 19.6. The patch to download is 31220620.<\/p>\n
Update repository<\/h3>\n
The first step is to upload the unzipped patch 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):<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-repository -f \/nfs\/ODA_PATCH_18\/19.7\/oda-sm-19.7.0.0.0-200520-server1of2.zip,\/nfs\/ODA_PATCH_18\/19.7\/oda-sm-19.7.0.0.0-200520-server2of2.zip\r\n{\r\n  \"jobId\" : \"ad0389f3-2e2b-4523-b054-de8e84a84949\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : \"\/nfs\/ODA_PATCH_18\/19.7\/oda-sm-19.7.0.0.0-200520-server1of2.zip,\/nfs\/ODA_PATCH_18\/19.7\/oda-sm-19.7.0.0.0-200520-server2of2.zip\",\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 26, 2020 11:21:27 AM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"Repository Update\",\r\n  \"updatedTime\" : \"July 26, 2020 11:21:27 AM CEST\"\r\n}\r\nYou have new mail in \/var\/spool\/mail\/root\r\n[root@odat1 ~]#<\/pre>\n
After that we can follow the job with odacli describe-job<\/em>:<\/strong><\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"ad0389f3-2e2b-4523-b054-de8e84a84949\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  ad0389f3-2e2b-4523-b054-de8e84a84949\r\n            Description:  Repository Update\r\n                 Status:  Success\r\n                Created:  July 26, 2020 11:21:27 AM CEST\r\n                Message:  \/nfs\/ODA_PATCH_18\/19.7\/oda-sm-19.7.0.0.0-200520-server1of2.zip,\/nfs\/ODA_PATCH_18\/19.7\/oda-sm-19.7.0.0.0-200520-server2of2.zip\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nCheck AvailableSpace                     July 26, 2020 11:21:28 AM CEST      July 26, 2020 11:21:28 AM CEST      Success\r\nSetting up ssh equivalance               July 26, 2020 11:21:29 AM CEST      July 26, 2020 11:21:29 AM CEST      Success\r\nCopy BundleFile                          July 26, 2020 11:21:30 AM CEST      July 26, 2020 11:25:50 AM CEST      Success\r\nValidating CopiedFile                    July 26, 2020 11:25:50 AM CEST      July 26, 2020 11:26:21 AM CEST      Success\r\nUnzip bundle                             July 26, 2020 11:26:22 AM CEST      July 26, 2020 11:43:55 AM CEST      Success\r\nUnzip bundle                             July 26, 2020 11:43:55 AM CEST      July 26, 2020 11:46:16 AM CEST      Success\r\nDelete PatchBundles                      July 26, 2020 11:46:22 AM CEST      July 26, 2020 11:46:45 AM CEST      Success\r\nRemoving ssh keys                        July 26, 2020 11:46:45 AM CEST      July 26, 2020 11:46:47 AM CEST      Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
DCSAgent<\/h3>\n
The next step is to update the internal DCS agent for ODA 19.7. Is a simple step executed using the odacli update-dcsagent<\/strong>. The parameter is the version 19.7.0.0:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-dcsagent -v 19.7.0.0.0\r\n{\r\n  \"jobId\" : \"1af29269-73cd-4eb6-8208-e5885376b274\",\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 26, 2020 11:51:01 AM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"DcsAgent patching\",\r\n  \"updatedTime\" : \"July 26, 2020 11:51:01 AM CEST\"\r\n}\r\n[root@odat1 ~]#<\/pre>\n
And as usual, we need to wait for the job to finish before continuing. We use the odacli describe-job<\/em> to check this:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"1af29269-73cd-4eb6-8208-e5885376b274\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  1af29269-73cd-4eb6-8208-e5885376b274\r\n            Description:  DcsAgent patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 11:51:01 AM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\ndcs-agent upgrade  to version 19.7.0.0.0 July 26, 2020 11:51:02 AM CEST      July 26, 2020 11:52:49 AM CEST      Success\r\ndcs-agent upgrade  to version 19.7.0.0.0 July 26, 2020 11:52:49 AM CEST      July 26, 2020 11:54:28 AM CEST      Success\r\nUpdate System version                    July 26, 2020 11:54:35 AM CEST      July 26, 2020 11:54:35 AM CEST      Success\r\nUpdate System version                    July 26, 2020 11:54:35 AM CEST      July 26, 2020 11:54:35 AM CEST      Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
You can receive some errors if you try to describe the jobID. This can occur because the process restarts the DCS. If you got this, just wait some minutes and try again (some common errors are: DCS-10001:Internal error encountered: Fail to get credential<\/em> or DCS-10001:Internal error encountered: Fail to start hand shake to localhost:7070<\/em>).<\/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.7.0.0.0\r\n{\r\n  \"jobId\" : \"edf88f79-529c-438e-8a4a-a412749c8a70\",\r\n  \"status\" : \"Created\",\r\n  \"message\" : null,\r\n  \"reports\" : [ ],\r\n  \"createTimestamp\" : \"July 26, 2020 11:56:45 AM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"DcsAdmin patching\",\r\n  \"updatedTime\" : \"July 26, 2020 11:56:45 AM CEST\"\r\n}\r\n[root@odat1 ~]#<\/pre>\n
And as usual, we can check the end of the job before continue:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"edf88f79-529c-438e-8a4a-a412749c8a70\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  edf88f79-529c-438e-8a4a-a412749c8a70\r\n            Description:  DcsAdmin patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 11:56:45 AM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nPatch location validation                July 26, 2020 11:56:47 AM CEST      July 26, 2020 11:56:47 AM CEST      Success\r\nPatch location validation                July 26, 2020 11:56:47 AM CEST      July 26, 2020 11:56:47 AM CEST      Success\r\ndcsadmin upgrade                         July 26, 2020 11:56:48 AM CEST      July 26, 2020 11:56:54 AM CEST      Success\r\ndcsadmin upgrade                         July 26, 2020 11:56:54 AM CEST      July 26, 2020 11:57:01 AM CEST      Success\r\nUpdate System version                    July 26, 2020 11:57:02 AM CEST      July 26, 2020 11:57:02 AM CEST      Success\r\nUpdate System version                    July 26, 2020 11:57:02 AM CEST      July 26, 2020 11:57:02 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>. As occurred with other versions, 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 updated SSH keys \u2013 two jobs):<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-dcscomponents -v 19.7.0.0.0\r\n{\r\n  \"jobId\" : \"e4f87d5e-9b79-4bcd-a74f-daa9ff672474\",\r\n  \"status\" : \"Success\",\r\n  \"message\" : null,\r\n  \"reports\" : null,\r\n  \"createTimestamp\" : \"July 26, 2020 11:57:28 AM CEST\",\r\n  \"description\" : \"Job completed and is not part of Agent job list\",\r\n  \"updatedTime\" : \"July 26, 2020 11:57:28 AM CEST\"\r\n}\r\n[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"e4f87d5e-9b79-4bcd-a74f-daa9ff672474\"\r\nDCS-10000:Resource Job with ID e4f87d5e-9b79-4bcd-a74f-daa9ff672474 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\n\u2026\r\nad0389f3-2e2b-4523-b054-de8e84a84949     Repository Update                                                           July 26, 2020 11:21:27 AM CEST      Success\r\n1af29269-73cd-4eb6-8208-e5885376b274     DcsAgent patching                                                           July 26, 2020 11:51:01 AM CEST      Success\r\nedf88f79-529c-438e-8a4a-a412749c8a70     DcsAdmin patching                                                           July 26, 2020 11:56:45 AM CEST      Success\r\nc8d8bcde-4015-468d-8332-d2569e5ffa6d     SSH keys update                                                             July 26, 2020 11:57:51 AM CEST      Success\r\na1c4cdc8-1b9e-4d25-8fac-cf85ae561e5e     SSH key delete                                                              July 26, 2020 11:57:56 AM CEST      Success\r\n7a9aff35-a04e-43ab-bc3b-7c3aee9a72d9     SSH keys update                                                             July 26, 2020 11:58:25 AM CEST      Success\r\nd0817c75-3fa3-4974-ade1-470a0c7993d8     SSH key delete                                                              July 26, 2020 12:00:00 PM CEST      Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
Create-prepatchreport<\/h3>\n
The next step is to verify if you can update it to 19.7. The odacli will do a lot of tests for the operational system, 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.7.0.0.0\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  d7d1c155-1312-41bf-afe6-c85570073d9b\r\n            Description:  Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER]\r\n                 Status:  Created\r\n                Created:  July 26, 2020 1:59:04 PM CEST\r\n                Message:  Use 'odacli describe-prepatchreport -i d7d1c155-1312-41bf-afe6-c85570073d9b' to check details of results\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\n\r\n[root@odat1 ~]#<\/pre>\n
And after some time we got the full result (30 minutes more or less):<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-prepatchreport -i d7d1c155-1312-41bf-afe6-c85570073d9b\r\n\r\nPatch pre-check report\r\n------------------------------------------------------------------------\r\n                 Job ID:  d7d1c155-1312-41bf-afe6-c85570073d9b\r\n            Description:  Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER]\r\n                 Status:  FAILED\r\n                Created:  July 26, 2020 1:59:04 PM 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__OS__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.7.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nVerify OS patch                 Success   Verified OS patch\r\n\r\n__ILOM__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.7.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nChecking Ilom patch Version     Success   Patch already applied\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\nIs clusterware running          Success   Clusterware is running\r\nValidate patching tag           Success   Validated patching tag: 19.7.0.0.0.\r\nIs system provisioned           Success   Verified system is provisioned\r\nValidate ASM in online          Success   ASM is online\r\nValidate minimum agent version  Success   GI patching enabled in current\r\n                                          DCSAGENT version\r\nValidate GI patch metadata      Success   Validated patching tag: 19.7.0.0.0.\r\nValidate clones location exist  Success   Validated clones location\r\nIs patch location available     Success   Patch location is available.\r\nPatch location validation       Success   Successfully validated location\r\nPatch verification              Success   Patches 30869156 not applied on GI\r\n                                          home \/u01\/app\/19.0.0.0\/grid on node\r\n                                          odat1\r\nValidate Opatch update          Success   Successfully updated the opatch in\r\n                                          GiHome \/u01\/app\/19.0.0.0\/grid on node\r\n                                          odat1\r\nPatch conflict check            Success   No patch conflicts found on GiHome\r\n                                          \/u01\/app\/19.0.0.0\/grid on node odat1\r\n\r\n__ORACHK__\r\nRunning orachk                  Failed    Orachk validation failed: .\r\nSoftware home                   Failed    Software home check failed\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.7.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nVerify OS patch                 Success   Verified OS patch\r\n\r\n__ILOM__\r\nValidate supported versions     Success   Validated minimum supported versions.\r\nValidate patching tag           Success   Validated patching tag: 19.7.0.0.0.\r\nIs patch location available     Success   Patch location is available.\r\nChecking Ilom patch Version     Success   Patch already applied\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\nIs clusterware running          Success   Clusterware is running\r\nValidate patching tag           Success   Validated patching tag: 19.7.0.0.0.\r\nIs system provisioned           Success   Verified system is provisioned\r\nValidate ASM in online          Success   ASM is online\r\nValidate minimum agent version  Success   GI patching enabled in current\r\n                                          DCSAGENT version\r\nValidate GI patch metadata      Success   Validated patching tag: 19.7.0.0.0.\r\nValidate clones location exist  Success   Validated clones location\r\nIs patch location available     Success   Patch location is available.\r\nPatch location validation       Success   Successfully validated location\r\nPatch verification              Success   Patches 30869156 not applied on GI\r\n                                          home \/u01\/app\/19.0.0.0\/grid on node\r\n                                          odat2\r\nValidate Opatch update          Success   Successfully updated the opatch in\r\n                                          GiHome \/u01\/app\/19.0.0.0\/grid on node\r\n                                          odat2\r\nPatch conflict check            Success   No patch conflicts found on GiHome\r\n                                          \/u01\/app\/19.0.0.0\/grid on node odat2\r\n\r\n__ORACHK__\r\nRunning orachk                  Failed    Orachk validation failed: .\r\nSoftware home                   Failed    Software home check failed\r\n\r\n\r\n\r\n[root@odat1 ~]#<\/pre>\n
As you can see FAILED. Some known issues can be checked before. One that I passed was the existence of \/u01\/app\/oraInventory\/locks. I needed to remove it from both nodes to have success in the report<\/strong>.<\/p>\n
The ORACHK is more tricky to check the source. To check we need go to folder \/opt\/oracle\/dcs\/oracle.ahf\/orachk\/SERVER\/<jobID#>\/orachk_<hostname><random#>\/<\/em><\/strong> and check the HTML file:<\/p>\n
[root@odat1 ~]# ls -l \/opt\/oracle\/dcs\/oracle.ahf\/orachk\/SERVER\/d7d1c155-1312-41bf-afe6-c85570073d9b\/orachk_odat1_072620_14087\/\r\ntotal 1024\r\ndrwxr-xr-x 2 root root   4096 Jul 26 14:12 log\r\n-rw------- 1 root root 993400 Jul 26 14:12 orachk_odat1_072620_14087.html\r\ndrwxr-xr-x 4 root root  24576 Jul 26 14:12 outfiles\r\ndrwxr-xr-x 2 root root   4096 Jul 26 14:12 reports\r\ndrwxr-xr-x 2 root root  12288 Jul 26 14:12 scripts\r\ndrwxr-xr-x 2 root root   4096 Jul 26 14:12 upload\r\n[root@odat1 ~]#<\/pre>\n
There we can see internally the ERROR. In this case that we got the \u201cOrachk validation failed<\/em>\u201d and \u201cSoftware home check failed<\/em>\u201d the error is related with a check made but CVU that try to check some files (that are listed in XML file) and was not found:<\/p>\n
Cluster Verification Utility (CVU 19.6.0.0.0 ) result\r\nStatus\tType\tMessage\tStatus On\tDetails\r\nFAIL\tOS Check\tSoftware home check failed\tAll Database Servers\t\r\nView\r\n\r\nStatus on odat1:\r\nFAIL => Software home check failed\r\n\r\n\r\nError Message:\r\nFile \"\/u01\/app\/19.0.0.0\/grid\/jdk\/jre\/lib\/amd64\/libjavafx_font_t2k.so\" could not be verified on node \"odat1\". OS error: \"No such file or directory\"\r\nError Message:\r\nFile \"\/u01\/app\/19.0.0.0\/grid\/jdk\/jre\/lib\/amd64\/libkcms.so\" could not be verified on node \"odat1\". OS error: \"No such file or directory\"\r\nError Message:\r\nFile \"\/u01\/app\/19.0.0.0\/grid\/rdbms\/lib\/ksms.o\" could not be verified on node \"odat1\". OS error: \"No such file or directory\"<\/pre>\n
This error occurs because the CVU uses the context of file \/u01\/app\/19.0.0.0\/grid\/cv\/cvdata\/ora_software_cfg.xml<\/em> to verify the files that need to be checked. But this file has more contents that need:<\/p>\n
[root@odat1 ~]# cat \/u01\/app\/19.0.0.0\/grid\/cv\/cvdata\/ora_software_cfg.xml |grep libkcms\r\n         <File Path=\"jdk\/jre\/lib\/amd64\/\" Name=\"libkcms.so\"\/>\r\n         <File Path=\"jdk\/jre\/lib\/amd64\/\" Name=\"libkcms.so\"\/>\r\n         <File Path=\"jdk\/jre\/lib\/amd64\/\" Name=\"libkcms.so\"\/>\r\n[root@odat1 ~]#<\/pre>\n
So, to fix, need to copy the file \/u01\/app\/19.0.0.0\/grid\/cv\/cvdata\/19\/ora_software_cfg.xml over \/u01\/app\/19.0.0.0\/grid\/cv\/cvdata\/ora_software_cfg.xml. <\/strong>This is described at Bug 31208297<\/a> since the new version is aligned with 19c (while the other is aligned with other versions).<\/p>\n
Another option is simply ignore the error and continue with the process. If you have doubts or other errors, please check the release notes from the version to check if they are listed there. Another option is open SR.<\/p>\n
Update-Server<\/h3>\n
After the create patchreport we can patch the server calling odacli update-server<\/em><\/strong>:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-server -v 19.7.0.0.0\r\n{\r\n  \"jobId\" : \"91abf816-b171-4e2f-a206-23013f53fb8e\",\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 16:04:06 PM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"Server Patching\",\r\n  \"updatedTime\" : \"July 26, 2020 16:04:06 PM CEST\"\r\n}\r\n[root@odat1 ~]#<\/pre>\n
This will create one jobIB that we can follow:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"91abf816-b171-4e2f-a206-23013f53fb8e\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  91abf816-b171-4e2f-a206-23013f53fb8e\r\n            Description:  Server Patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 4:04:06 PM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nPatch location validation                July 26, 2020 4:04:42 PM CEST       July 26, 2020 4:04:43 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:04:42 PM CEST       July 26, 2020 4:04:42 PM CEST       Success\r\ndcs-controller upgrade                   July 26, 2020 4:04:43 PM CEST       July 26, 2020 4:04:50 PM CEST       Success\r\ndcs-controller upgrade                   July 26, 2020 4:04:50 PM CEST       July 26, 2020 4:04:57 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:05:00 PM CEST       July 26, 2020 4:05:00 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:05:00 PM CEST       July 26, 2020 4:05:00 PM CEST       Success\r\ndcs-cli upgrade                          July 26, 2020 4:05:02 PM CEST       July 26, 2020 4:05:02 PM CEST       Success\r\ndcs-cli upgrade                          July 26, 2020 4:05:02 PM CEST       July 26, 2020 4:05:03 PM CEST       Success\r\nCreating repositories using yum          July 26, 2020 4:05:07 PM CEST       July 26, 2020 4:05:10 PM CEST       Success\r\nUpdating YumPluginVersionLock rpm        July 26, 2020 4:05:11 PM CEST       July 26, 2020 4:05:11 PM CEST       Success\r\nApplying OS Patches                      July 26, 2020 4:05:11 PM CEST       July 26, 2020 4:24:31 PM CEST       Success\r\nCreating repositories using yum          July 26, 2020 4:24:32 PM CEST       July 26, 2020 4:24:34 PM CEST       Success\r\nApplying HMP Patches                     July 26, 2020 4:24:34 PM CEST       July 26, 2020 4:24:35 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:24:36 PM CEST       July 26, 2020 4:24:36 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:24:36 PM CEST       July 26, 2020 4:24:36 PM CEST       Success\r\noda-hw-mgmt upgrade                      July 26, 2020 4:24:37 PM CEST       July 26, 2020 4:25:11 PM CEST       Success\r\noda-hw-mgmt upgrade                      July 26, 2020 4:25:11 PM CEST       July 26, 2020 4:25:47 PM CEST       Success\r\nOSS Patching                             July 26, 2020 4:25:47 PM CEST       July 26, 2020 4:25:49 PM CEST       Success\r\nApplying Firmware Disk Patches           July 26, 2020 4:26:57 PM CEST       July 26, 2020 4:27:59 PM CEST       Success\r\nApplying Firmware Expander Patches       July 26, 2020 4:28:13 PM CEST       July 26, 2020 4:28:30 PM CEST       Success\r\nApplying Firmware Controller Patches     July 26, 2020 4:28:44 PM CEST       July 26, 2020 4:28:59 PM CEST       Success\r\nChecking Ilom patch Version              July 26, 2020 4:29:01 PM CEST       July 26, 2020 4:29:03 PM CEST       Success\r\nChecking Ilom patch Version              July 26, 2020 4:29:03 PM CEST       July 26, 2020 4:29:06 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:29:06 PM CEST       July 26, 2020 4:29:07 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:29:06 PM CEST       July 26, 2020 4:29:07 PM CEST       Success\r\nSave password in Wallet                  July 26, 2020 4:29:09 PM CEST       July 26, 2020 4:29:09 PM CEST       Success\r\nApply Ilom patch                         July 26, 2020 4:29:09 PM CEST       July 26, 2020 4:29:11 PM CEST       Success\r\nApply Ilom patch                         July 26, 2020 4:29:11 PM CEST       July 26, 2020 4:29:12 PM CEST       Success\r\nCopying Flash Bios to Temp location      July 26, 2020 4:29:12 PM CEST       July 26, 2020 4:29:12 PM CEST       Success\r\nCopying Flash Bios to Temp location      July 26, 2020 4:29:12 PM CEST       July 26, 2020 4:29:12 PM CEST       Success\r\nStarting the clusterware                 July 26, 2020 4:31:30 PM CEST       July 26, 2020 4:33:32 PM CEST       Success\r\nclusterware patch verification           July 26, 2020 4:33:38 PM CEST       July 26, 2020 4:33:45 PM CEST       Success\r\nclusterware patch verification           July 26, 2020 4:33:38 PM CEST       July 26, 2020 4:33:45 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:33:45 PM CEST       July 26, 2020 4:33:53 PM CEST       Success\r\nPatch location validation                July 26, 2020 4:33:45 PM CEST       July 26, 2020 4:33:53 PM CEST       Success\r\nOpatch update                            July 26, 2020 4:34:37 PM CEST       July 26, 2020 4:34:41 PM CEST       Success\r\nOpatch update                            July 26, 2020 4:34:37 PM CEST       July 26, 2020 4:34:40 PM CEST       Success\r\nPatch conflict check                     July 26, 2020 4:34:42 PM CEST       July 26, 2020 4:36:18 PM CEST       Success\r\nPatch conflict check                     July 26, 2020 4:36:18 PM CEST       July 26, 2020 4:37:54 PM CEST       Success\r\nclusterware upgrade                      July 26, 2020 4:38:09 PM CEST       July 26, 2020 5:26:26 PM CEST       Success\r\nclusterware upgrade                      July 26, 2020 5:26:27 PM CEST       July 26, 2020 6:14:40 PM CEST       Success\r\nUpdating GiHome version                  July 26, 2020 6:14:40 PM CEST       July 26, 2020 6:15:03 PM CEST       Success\r\nUpdating GiHome version                  July 26, 2020 6:14:40 PM CEST       July 26, 2020 6:15:03 PM CEST       Success\r\nUpdate System version                    July 26, 2020 6:16:31 PM CEST       July 26, 2020 6:16:32 PM CEST       Success\r\nUpdate System version                    July 26, 2020 6:16:32 PM CEST       July 26, 2020 6:16:32 PM CEST       Success\r\npreRebootNode Actions                    July 26, 2020 6:16:32 PM CEST       July 26, 2020 6:17:15 PM CEST       Success\r\npreRebootNode Actions                    July 26, 2020 6:17:15 PM CEST       July 26, 2020 6:18:00 PM CEST       Success\r\nReboot Ilom                              July 26, 2020 6:18:01 PM CEST       July 26, 2020 6:18:01 PM CEST       Success\r\nReboot Ilom                              July 26, 2020 6:18:01 PM CEST       July 26, 2020 6:18:02 PM CEST       Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
In ODAX5-2 this process took around two hours. If you follow the \/opt\/oracle\/dcs\/log\/dcs-agent.log<\/strong> you can see more detail like and steps executed. Some example:<\/p>\n
...\r\n2020-07-26 16:54:07,687 DEBUG [clusterware upgrade : JobId=91abf816-b171-4e2f-a206-23013f53fb8e] [] c.o.d.a.u.AgentCommonUtils: dbGiHome version:19.0.0.0:\r\n2020-07-26 16:54:07,687 DEBUG [clusterware upgrade : JobId=91abf816-b171-4e2f-a206-23013f53fb8e] [] c.o.d.a.r.s.p.PatchingOperations: Is 18c Database:is18c\r\n2020-07-26 16:54:07,687 DEBUG [clusterware upgrade : JobId=91abf816-b171-4e2f-a206-23013f53fb8e] [] c.o.d.c.u.CommonsUtils:\r\nrun: cmd= '[\/u01\/app\/19.0.0.0\/grid\/OPatch\/opatchauto,\r\n apply,\r\n \/u01\/patching\/19.7.0.0.200414\/31145668,\r\n -oh,\r\n \/u01\/app\/19.0.0.0\/grid,\r\n -ocmrf,\r\n \/u01\/app\/19.0.0.0\/grid\/default-ocm.rsp]'\r\n2020-07-26 16:54:07,900 DEBUG [Thread-1116] [] c.o.d.c.u.CommonsUtils: Output : EMPTY CONTENT\r\n2020-07-26 16:54:07,900 DEBUG [Thread-1116] [] c.o.d.c.u.CommonsUtils: Output :\r\nOPatchauto session is initiated at Sun Jul 26 16:54:07 2020\r\n2020-07-26 16:54:13,077 DEBUG [Thread-1116] [] c.o.d.c.u.CommonsUtils: Output : EMPTY CONTENT\r\n2020-07-26 16:54:13,077 DEBUG [Thread-1116] [] c.o.d.c.u.CommonsUtils: Output :\r\nSystem initialization log file is \/u01\/app\/19.0.0.0\/grid\/cfgtoollogs\/opatchautodb\/systemconfig2020-07-26_04-54-12PM.log.\r\n2020-07-26 16:54:13,077 DEBUG [Thread-1116] [] c.o.d.c.u.CommonsUtils: Output : EMPTY CONTENT\r\n...<\/pre>\n
After you finish this jobIB, and around 10 minutes later, ODA nodes will reboot to boot the new version.<\/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 update all the firmawares.<\/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.7.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\nodat1\r\n\r\nLocal System Version\r\n---------------\r\n19.7.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.7.0.0.0            up-to-date\r\n\r\nGI                                        19.7.0.0.200414       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.10.0.0.200414\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200414\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200414\r\n}\r\n\r\nDCSAGENT                                  19.7.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.8                   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           16.00.08.00\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.7.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.7.0.0.0            up-to-date\r\n\r\nGI                                        19.7.0.0.200414       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.10.0.0.200414\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200414\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200414\r\n}\r\n\r\nDCSAGENT                                  19.7.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.8                   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           16.00.08.00\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
Look above that diskcontrolers are not with the last version of the firmware. So, we need to call odacli update-storage<\/em><\/strong> to patch everything:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli update-storage -v 19.7.0.0.0\r\n{\r\n  \"jobId\" : \"095e10f4-cefc-410d-af3f-b3c8f9cd0af9\",\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 18:35:00 PM CEST\",\r\n  \"resourceList\" : [ ],\r\n  \"description\" : \"Storage Firmware Patching\",\r\n  \"updatedTime\" : \"July 26, 2020 18:35:00 PM CEST\"\r\n}\r\n[root@odat1 ~]#<\/pre>\n
And we can follow the jobID:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-job -i \"095e10f4-cefc-410d-af3f-b3c8f9cd0af9\"\r\n\r\nJob details\r\n----------------------------------------------------------------\r\n                     ID:  095e10f4-cefc-410d-af3f-b3c8f9cd0af9\r\n            Description:  Storage Firmware Patching\r\n                 Status:  Success\r\n                Created:  July 26, 2020 6:35:00 PM CEST\r\n                Message:\r\n\r\nTask Name                                Start Time                          End Time                            Status\r\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\r\nApplying Firmware Disk Patches           July 26, 2020 6:39:37 PM CEST       July 26, 2020 6:42:40 PM CEST       Success\r\nApplying Firmware Controller Patches     July 26, 2020 6:49:16 PM CEST       July 26, 2020 6:55:47 PM CEST       Success\r\npreRebootNode Actions                    July 26, 2020 6:55:48 PM CEST       July 26, 2020 6:55:48 PM CEST       Success\r\npreRebootNode Actions                    July 26, 2020 6:55:48 PM CEST       July 26, 2020 6:55:48 PM CEST       Success\r\nReboot Ilom                              July 26, 2020 6:55:48 PM CEST       July 26, 2020 6:55:48 PM CEST       Success\r\nReboot Ilom                              July 26, 2020 6:55:48 PM CEST       July 26, 2020 6:55:49 PM CEST       Success\r\n\r\n[root@odat1 ~]#<\/pre>\n
After it finishes, the ODA nodes will reboot again. To reboot be effective maybe you need to wait 10 minutes or more.<\/p>\n
And after the reboot you can see that everything is up-to-date:<\/p>\n
[root@odat1 ~]# \/opt\/oracle\/dcs\/bin\/odacli describe-component\r\nSystem Version\r\n---------------\r\n19.7.0.0.0\r\n\r\nSystem node Name\r\n---------------\r\nodat1\r\n\r\nLocal System Version\r\n---------------\r\n19.7.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.7.0.0.0            up-to-date\r\n\r\nGI                                        19.7.0.0.200414       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.10.0.0.200414\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200414\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200414\r\n}\r\n\r\nDCSAGENT                                  19.7.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.8                   up-to-date\r\n\r\nFIRMWARECONTROLLER {\r\n[ c0 ]                                    4.650.00-7176         up-to-date\r\n[ c1,c2 ]                                 16.00.08.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.7.0.0.0\r\n\r\nComponent                                Installed Version    Available Version\r\n---------------------------------------- -------------------- --------------------\r\nOAK                                       19.7.0.0.0            up-to-date\r\n\r\nGI                                        19.7.0.0.200414       up-to-date\r\n\r\nDB {\r\n[ OraDB18000_home1 ]                      18.3.0.0.180717       18.10.0.0.200414\r\n[ OraDB12102_home1,OraDB12102_home2 ]     12.1.0.2.180717       12.1.0.2.200414\r\n[ OraDB11204_home1,OraDB11204_home2 ]     11.2.0.4.180717       11.2.0.4.200414\r\n}\r\n\r\nDCSAGENT                                  19.7.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.8                   up-to-date\r\n\r\nFIRMWARECONTROLLER {\r\n[ c0 ]                                    4.650.00-7176         up-to-date\r\n[ c1,c2 ]                                 16.00.08.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
After that, you can start all databases that you stopped before and continue to use ODA.<\/p>\n
 <\/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 third part of the ODA patch series, from 18.3 to 19.8. I separate in multiple parts and you can use this part as a direct guide to patch ODA from 19.6 to 19.7. Each part can be used alone since they cover all the needed steps. Some steps of this post are […]<\/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_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_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}},"categories":[29,77,78,5,14,12],"tags":[100,79,65,135,124],"class_list":["post-791","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 3 \u2013 19.6 to 19.7 - Fernando Simon<\/title>\n<meta name=\"description\" content=\"How to upgrade ODA from 19.6 to 19.7. All patch steps covered: 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-3-19-6-to-19-7\/\" \/>\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 3 \u2013 19.6 to 19.7 - Fernando Simon\" \/>\n<meta property=\"og:description\" content=\"How to upgrade ODA from 19.6 to 19.7. All patch steps covered: 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-3-19-6-to-19-7\/\" \/>\n<meta property=\"og:site_name\" content=\"Fernando Simon\" \/>\n<meta property=\"article:published_time\" content=\"2020-09-07T20:03:16+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=\"23 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-3-19-6-to-19-7\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/\"},\"author\":{\"name\":\"Simon\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\"},\"headline\":\"Patch ODA from 18.3 to 19.8. Part 3 \u2013 19.6 to 19.7\",\"datePublished\":\"2020-09-07T20:03:16+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/\"},\"wordCount\":1312,\"commentCount\":1,\"image\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#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-3-19-6-to-19-7\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/\",\"url\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/\",\"name\":\"Patch ODA from 18.3 to 19.8. Part 3 \u2013 19.6 to 19.7 - 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-3-19-6-to-19-7\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg\",\"datePublished\":\"2020-09-07T20:03:16+00:00\",\"author\":{\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9\"},\"description\":\"How to upgrade ODA from 19.6 to 19.7. All patch steps covered: 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-3-19-6-to-19-7\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#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-3-19-6-to-19-7\/#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 3 \u2013 19.6 to 19.7\"}]},{\"@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:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/image\/\",\"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 3 \u2013 19.6 to 19.7 - Fernando Simon","description":"How to upgrade ODA from 19.6 to 19.7. All patch steps covered: 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-3-19-6-to-19-7\/","og_locale":"en_US","og_type":"article","og_title":"Patch ODA from 18.3 to 19.8. Part 3 \u2013 19.6 to 19.7 - Fernando Simon","og_description":"How to upgrade ODA from 19.6 to 19.7. All patch steps covered: 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-3-19-6-to-19-7\/","og_site_name":"Fernando Simon","article_published_time":"2020-09-07T20:03:16+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":"23 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#article","isPartOf":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/"},"author":{"name":"Simon","@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"headline":"Patch ODA from 18.3 to 19.8. Part 3 \u2013 19.6 to 19.7","datePublished":"2020-09-07T20:03:16+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/"},"wordCount":1312,"commentCount":1,"image":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#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-3-19-6-to-19-7\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/","url":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/","name":"Patch ODA from 18.3 to 19.8. Part 3 \u2013 19.6 to 19.7 - 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-3-19-6-to-19-7\/#primaryimage"},"image":{"@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#primaryimage"},"thumbnailUrl":"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2020\/08\/19cmatrix.jpg","datePublished":"2020-09-07T20:03:16+00:00","author":{"@id":"https:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/386da956604bca0d5be5dd52210c1dd9"},"description":"How to upgrade ODA from 19.6 to 19.7. All patch steps covered: 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-3-19-6-to-19-7\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fernandosimon.com\/blog\/patch-oda-from-18-3-to-19-8-part-3-19-6-to-19-7\/#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-3-19-6-to-19-7\/#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 3 \u2013 19.6 to 19.7"}]},{"@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:\/\/www.fernandosimon.com\/blog\/#\/schema\/person\/image\/","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_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5ofTp-cL","_links":{"self":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/791","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=791"}],"version-history":[{"count":0,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/posts\/791\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/media?parent=791"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/categories?post=791"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fernandosimon.com\/blog\/wp-json\/wp\/v2\/tags?post=791"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}