{"id":11305,"date":"2018-05-31T14:57:46","date_gmt":"2018-05-31T12:57:46","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/"},"modified":"2018-05-31T14:57:46","modified_gmt":"2018-05-31T12:57:46","slug":"patching-oda-lite-to-12-2-1-3-0","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/","title":{"rendered":"Patching ODA lite to 12.2.1.3.0"},"content":{"rendered":"<p>Here is the latest patch for your ODA and it seems that Oracle documentation for this patch is not exactly the procedure you&#8217;ll have to follow to successfully patch your appliance. I recently updated X6-2M and X6-2L to this latest release and here is how to do that. In this example I was patching from 12.1.2.12.0, no intermediate patch was needed.<\/p>\n<p><strong>1) Download the patch<\/strong><\/p>\n<p>It seems odd but sometimes finding the corresponding patch is not so easy! With the patch number, it&#8217;s more convenient. For 12.2.1.3.0 with the dcs stack the number is 27648057. This patch will update all the components:\u00a0 dcs (odacli), operating system, bios\/firmwares, ilom, GI and dbhomes.<\/p>\n<p>Copy the patch in a temporary folder on the server, for example \/opt\/patch. You&#8217;ll need to be root to apply the patch.<\/p>\n<p><strong>2) Check the actual versions and free up space on disk<\/strong><\/p>\n<p>I recommend you to check the actual versions. It&#8217;s easy:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli describe-component\n\nSystem Version\n---------------\n12.1.2.12.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       12.1.2.12.0           up-to-date\nGI                                        12.1.0.2.170814       up-to-date\nDB {\n[ OraDB12102_home1 ]                      12.1.0.2.170814       up-to-date\n[ OraDB11204_home1 ]                      11.2.0.4.170814       up-to-date\n}\nILOM                                      3.2.7.26.a.r112632    up-to-date\nBIOS                                      39050100              up-to-date\nOS                                        6.8                   up-to-date\nFIRMWARECONTROLLER {\n[ c6 ]                                    4.650.00-7176         up-to-date\n[ c0,c1,c2,c3,c4,c5                       KPYABR3Q              up-to-date\n}\nFIRMWAREDISK                              0R3Q                  up-to-date<\/pre>\n<p>Don&#8217;t care about Available Version column, it&#8217;s only valid after you register a new patch. Your ODA doesn&#8217;t check the latest patch online.<\/p>\n<p>For free space check that folders \/, \/u01 and \/opt have enough free GB to process. At least 10GB I think.<\/p>\n<p><strong>3) Prepare the patch files<\/strong><\/p>\n<p>It&#8217;s slightly different than previous versions. Only the first zipfile has to be uncompressed and registered. The 2 other files can directly be registered without unzipping them.<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">cd \/opt\/patch\nunzip p27648057_122130_Linux-x86-64_1of3.zip\n\nodacli update-repository -f \/opt\/patch\/oda-sm-12.2.1.3.0-180504-server1of3.zip\nodacli update-repository -f \/opt\/patch\/p27648057_122130_Linux-x86-64_2of3.zip\nodacli update-repository -f \/opt\/patch\/p27648057_122130_Linux-x86-64_3of3.zip<\/pre>\n<p><strong>4) Update the dcs-agent<\/strong><\/p>\n<p>First you&#8217;ll have to update the dcs-agent:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli update-dcsagent -v 12.2.1.3.0\n{\n\"jobId\" : \"150b3486-cfb2-4b32-b751-0ed89ce3d7be\",\n\"status\" : \"Created\",\n\"message\" : \"Dcs agent will be restarted after the update. Please wait for 2-3 mins before executing the other commands\",\n\"reports\" : [ ],\n\"createTimestamp\" : \"May 22, 2018 10:31:50 AM CEST\",\n\"resourceList\" : [ ],\n\"description\" : \"DcsAgent patching\",\n\"updatedTime\" : \"May 22, 2018 10:31:50 AM CEST\"\n}<\/pre>\n<p>As for every kind of operation you do with odacli, you receive a jobId you can monitor:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli describe-job -i \"150b3486-cfb2-4b32-b751-0ed89ce3d7be\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  150b3486-cfb2-4b32-b751-0ed89ce3d7be\n            Description:  DcsAgent patching\n                 Status:  Success\n                Created:  May 22, 2018 10:31:50 AM CEST\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\ndcsagent rpm verification                May 22, 2018 10:31:50 AM CEST       May 22, 2018 10:31:50 AM CEST       Success\nPatch location validation                May 22, 2018 10:31:50 AM CEST       May 22, 2018 10:31:50 AM CEST       Success\ndcs-agent upgrade                        May 22, 2018 10:31:50 AM CEST       May 22, 2018 10:31:51 AM CEST       Success<\/pre>\n<p>This update takes only a minute.<\/p>\n<p>Check again the version and you will see a new component in 18c, quite weird:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli describe-component\nSystem Version\n---------------\n12.2.1.3.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       12.1.2.12.0           12.2.1.3.0\nGI                                        12.1.0.2.170814       12.2.0.1.180116\nDB {\n[ OraDB12102_home1 ]                      12.1.0.2.170814       12.1.0.2.180116\n[ OraDB11204_home1 ]                      11.2.0.4.170814       11.2.0.4.180116\n}\nDCSAGENT                                  18.1.3.0.0            up-to-date\nILOM                                      3.2.7.26.a.r112632    up-to-date\nBIOS                                      39050100              39090000\nOS                                        6.8                   6.9\nFIRMWARECONTROLLER {\n[ c6 ]                                    4.650.00-7176         up-to-date\n[ c0,c1,c2,c3,c4,c5 ]                     KPYABR3Q              kpyagr3q\n}\nFIRMWAREDISK                              0R3Q                  up-to-date<\/pre>\n<p><strong>5) Update the server<\/strong><\/p>\n<p>Updating the server will actually update not only the operating system but also the ILOM, the BIOS, the firmware of internal disks and the GI. For the OS, Oracle Linux will go from 6.8 to 6.9 and the update process will assume that no additional packages have been installed. If you installed additional packages, please remove them as they can prevent the patch to apply correctly. Even devel packages should be removed, the upgrade of normal packages linked to them will not work because of the dependencies. You can easily remove the install packages with rpm -e, for example:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">rpm -e openssl-devel-1.0.1e-48.el6_8.4.x86_64\nrpm -e krb5-devel-1.10.3-57.el6.x86_64\nrpm -e zlib-devel-1.2.3-29.el6.x86_64\nrpm -e keyutils-libs-devel-1.4-5.0.1.el6.x86_64\nrpm -e libcom_err-devel-1.42.8-1.0.2.el6.x86_64\nrpm -e libselinux-devel-2.0.94-7.el6.x86_64\nrpm -e libsepol-devel-2.0.41-4.el6.x86_64<\/pre>\n<p>Now you can safely run the patching:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli update-server -v 12.2.1.3.0<\/pre>\n<p>This update is the longest one (between 30 minutes and 1 hour), while you should see your server rebooting. As usual check the status of the job with describe-job:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli describe-job -i \"27d2195f-f16b-44d8-84e0-6af6e48ccad7\"<\/pre>\n<p>At the end of the process, describe-job will look like that:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">Task Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nPatch location validation                May 23, 2018 11:07:09 AM CEST       May 23, 2018 11:07:09 AM CEST       Success\ndcs-controller upgrade                   May 23, 2018 11:07:09 AM CEST       May 23, 2018 11:07:09 AM CEST       Success\nPatch location validation                May 23, 2018 11:07:09 AM CEST       May 23, 2018 11:07:09 AM CEST       Success\ndcs-cli upgrade                          May 23, 2018 11:07:09 AM CEST       May 23, 2018 11:07:09 AM CEST       Success\nCreating repositories using yum          May 23, 2018 11:07:09 AM CEST       May 23, 2018 11:07:10 AM CEST       Success\nApplying HMP Patches                     May 23, 2018 11:07:10 AM CEST       May 23, 2018 11:09:04 AM CEST       Success\nPatch location validation                May 23, 2018 11:09:04 AM CEST       May 23, 2018 11:09:04 AM CEST       Success\noda-hw-mgmt upgrade                      May 23, 2018 11:09:04 AM CEST       May 23, 2018 11:09:04 AM CEST       Success\nCreating repositories using yum          May 23, 2018 11:09:04 AM CEST       May 23, 2018 11:09:09 AM CEST       Success\nApplying OS Patches                      May 23, 2018 11:09:09 AM CEST       May 23, 2018 11:11:04 AM CEST       Success\nOSS Patching                             May 23, 2018 11:11:04 AM CEST       May 23, 2018 11:11:04 AM CEST       Success\nApplying Firmware Disk Patches           May 23, 2018 11:11:04 AM CEST       May 23, 2018 11:11:08 AM CEST       Success\nApplying Firmware Expander Patches       May 23, 2018 11:11:08 AM CEST       May 23, 2018 11:11:13 AM CEST       Success\nApplying Firmware Controller Patches     May 23, 2018 11:11:13 AM CEST       May 23, 2018 11:11:16 AM CEST       Success\nChecking Ilom patch Version              May 23, 2018 11:11:17 AM CEST       May 23, 2018 11:11:19 AM CEST       Success\nPatch location validation                May 23, 2018 11:11:19 AM CEST       May 23, 2018 11:11:20 AM CEST       Success\nApply Ilom patch                         May 23, 2018 11:11:21 AM CEST       May 23, 2018 11:11:22 AM CEST       Success\nCopying Flash Bios to Temp location      May 23, 2018 11:11:22 AM CEST       May 23, 2018 11:11:22 AM CEST       Success\nStarting the clusterware                 May 23, 2018 11:11:23 AM CEST       May 23, 2018 11:11:23 AM CEST       Success\nCreating GI home directories             May 23, 2018 11:11:23 AM CEST       May 23, 2018 11:11:23 AM CEST       Success\nCloning Gi home                          May 23, 2018 11:11:23 AM CEST       May 23, 2018 11:13:53 AM CEST       Success\nConfiguring GI                           May 23, 2018 11:13:53 AM CEST       May 23, 2018 11:14:06 AM CEST       Success\nRunning GI upgrade root scripts          May 23, 2018 11:14:06 AM CEST       May 23, 2018 11:29:04 AM CEST       Success\nResetting DG compatibility               May 23, 2018 11:29:04 AM CEST       May 23, 2018 11:29:09 AM CEST       Success\nRunning GI config assistants             May 23, 2018 11:29:09 AM CEST       May 23, 2018 11:30:10 AM CEST       Success\nrestart oakd                             May 23, 2018 11:30:13 AM CEST       May 23, 2018 11:30:23 AM CEST       Success\nUpdating GiHome version                  May 23, 2018 11:30:23 AM CEST       May 23, 2018 11:30:25 AM CEST       Success\npreRebootNode Actions                    May 23, 2018 11:30:39 AM CEST       May 23, 2018 11:31:25 AM CEST       Success\nReboot Ilom                              May 23, 2018 11:31:25 AM CEST       May 23, 2018 11:31:25 AM CEST       Success<\/pre>\n<p>Don&#8217;t forget that if there is a problem during the patching process (you forgot to remove an additional rpm for example), you can relaunch the patching and it will skip the already patched components. But you will loose a lot of time! Please control the components version after the reboot with describe-component.<\/p>\n<p><strong>6) Patch the dbhomes<\/strong><\/p>\n<p>You now need to patch the dbhomes separately. First of all list them:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli list-dbhomes\n\nID                                       Name                 DB Version                               Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------\n86b6a068-55a8-4171-9f94-48b86f135065     OraDB12102_home1     12.1.0.2.170814 (26680878, 26609798)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1     Configured\nc6e7d556-5785-41d8-a120-ed3ef756848a     OraDB11204_home1     11.2.0.4.170814 (26609929, 26609445)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured<\/pre>\n<p>And then patch the first one:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli update-dbhome -v 12.2.1.3 -i c6e7d556-5785-41d8-a120-ed3ef756848a<\/pre>\n<p>It will also apply the datapatch on all the primary databases connected to this home. If you don&#8217;t have any database linked to the dbhome patching is fast:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli describe-job -i \"9defa52d-2997-42ea-9bd3-aafdbf0a4dc5\"\nJob details\n----------------------------------------------------------------\n                     ID:  9defa52d-2997-42ea-9bd3-aafdbf0a4dc5\n            Description:  DB Home Patching: Home Id is c6e7d556-5785-41d8-a120-ed3ef756848a\n                 Status:  Success\n                Created:  May 23, 2018 11:43:55 AM CEST\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nclusterware patch verification           May 23, 2018 11:43:56 AM CEST       May 23, 2018 11:43:58 AM CEST       Success\nPatch location validation                May 23, 2018 11:43:58 AM CEST       May 23, 2018 11:43:59 AM CEST       Success\nOpatch updation                          May 23, 2018 11:44:19 AM CEST       May 23, 2018 11:44:20 AM CEST       Success\nPatch conflict check                     May 23, 2018 11:44:20 AM CEST       May 23, 2018 11:44:27 AM CEST       Success\ndb upgrade                               May 23, 2018 11:44:27 AM CEST       May 23, 2018 11:46:01 AM CEST       Success<\/pre>\n<p>About 2 minutes for an empty dbhome.<\/p>\n<p>And for a dbhome linked to databases:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli update-dbhome -v 12.2.1.3 -i 86b6a068-55a8-4171-9f94-48b86f135065\n{\n\"jobId\" : \"8083dc43-61fe-49da-8081-43b4e5257e95\",\n\"status\" : \"Created\",\n\"message\" : null,\n\"reports\" : [ ],\n\"createTimestamp\" : \"May 23, 2018 12:46:06 PM CEST\",\n\"resourceList\" : [ ],\n\"description\" : \"DB Home Patching: Home Id is 86b6a068-55a8-4171-9f94-48b86f135065\",\n\"updatedTime\" : \"May 23, 2018 12:46:06 PM CEST\"\n}\n\nodacli describe-job -i \"e871f741-7dd6-49c6-9b4a-af0d68e647e7\"\n\nJob details\n----------------------------------------------------------------\nID:  e871f741-7dd6-49c6-9b4a-af0d68e647e7\nDescription:  DB Home Patching: Home Id is 86b6a068-55a8-4171-9f94-48b86f135065\nStatus:  Success\nCreated:  May 23, 2018 1:37:00 PM CEST\nMessage:  WARNING::Failed to run datapatch on db DB01TST##WARNING::Failed to run datapatch on db DB03TST\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nclusterware patch verification           May 23, 2018 1:37:21 PM CEST        May 23, 2018 1:37:23 PM CEST        Success\nPatch location validation                May 23, 2018 1:37:23 PM CEST        May 23, 2018 1:37:23 PM CEST        Success\nOpatch updation                          May 23, 2018 1:37:23 PM CEST        May 23, 2018 1:37:23 PM CEST        Success\nPatch conflict check                     May 23, 2018 1:37:23 PM CEST        May 23, 2018 1:37:23 PM CEST        Success\ndb upgrade                               May 23, 2018 1:37:23 PM CEST        May 23, 2018 1:37:23 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:37:23 PM CEST        May 23, 2018 1:37:57 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:37:57 PM CEST        May 23, 2018 1:38:26 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:38:26 PM CEST        May 23, 2018 1:38:51 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:38:51 PM CEST        May 23, 2018 1:39:49 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:39:49 PM CEST        May 23, 2018 1:40:28 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:40:28 PM CEST        May 23, 2018 1:40:53 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:40:53 PM CEST        May 23, 2018 1:41:19 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:41:19 PM CEST        May 23, 2018 1:41:44 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:41:44 PM CEST        May 23, 2018 1:42:14 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:42:14 PM CEST        May 23, 2018 1:42:48 PM CEST        Success\nSqlPatch upgrade                         May 23, 2018 1:42:48 PM CEST        May 23, 2018 1:43:22 PM CEST        Success<\/pre>\n<p>It&#8217;s longer but less than 10 minutes for this example. You can see the number of databases here (one line SqlPatch upgrade for one database). The job is successful, but actually not so successful because 2 warnings are raised. And be careful because message field in the job details is limited: check the \/opt\/oracle\/dcs\/log\/dcs-agent.log for extended warning messages.<\/p>\n<p>Always check the DB Version after the update of all dbhomes, this is the new version of the binaries:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli list-dbhomes\n\nID                                       Name                 DB Version                               Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------\n86b6a068-55a8-4171-9f94-48b86f135065     OraDB12102_home1     12.1.0.2.180116 (26925218, 26925263)     \/u01\/app\/oracle\/product\/12.1.0.2\/dbhome_1     Configured\nc6e7d556-5785-41d8-a120-ed3ef756848a     OraDB11204_home1     11.2.0.4.180116 (26609929, 26925576)     \/u01\/app\/oracle\/product\/11.2.0.4\/dbhome_1     Configured<\/pre>\n<p>If update job is really successful, jump to step 8.<\/p>\n<p><strong>7) Update the databases where datapatch failed<\/strong><\/p>\n<p>For all the databases where datapatch cannot be applied, you&#8217;ll have to do it manually. I discovered that if your database is not in AMERICAN_AMERICA language and territory (FRENCH_FRANCE in my case) odacli will not be able to apply the datapatch on the database. Let&#8217;s check the status of the datapatch on the database, set the NLS_LANG environment to AMERICAN_AMERICA and apply the patch on these databases:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">su \u2013 oracle\n. oraenv &lt;&lt;&lt; DB01TST\ncd $ORACLE_HOME\/OPatch\nsqlplus \/ as sysdba\nSQL&gt; set serveroutput on\nSQL&gt; exec dbms_qopatch.get_sqlpatch_status;\n\nPatch Id : 26609798\nAction : APPLY\nAction Time : 24-SEP-2017 23:50:14\nDescription : DATABASE BUNDLE PATCH 12.1.0.2.170814\nLogfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/26609798\/21481992\/26609798_apply_G100316_CD\nBROOT_2017Sep24_23_48_22.log\nStatus : SUCCESS\n\nPatch Id : 26925263\nAction : APPLY\nAction Time : 29-MAY-2018 15:40:27\nDescription : DATABASE BUNDLE PATCH 12.1.0.2.180116\nLogfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/26925263\/21857460\/26925263_apply_DB01TST_20\n18May29_15_40_13.log\nStatus : FAILED\n\nPL\/SQL procedure successfully completed.\n\nexit\nexport NLS_LANG=AMERICAN_AMERICA.AL32UTF8\n.\/datapatch -verbose\nsqlplus \/ as sysdba\nSQL&gt; set serveroutput on\nSQL&gt; exec dbms_qopatch.get_sqlpatch_status;\n\nPatch Id : 26609798\nAction : APPLY\nAction Time : 24-SEP-2017 23:50:14\nDescription : DATABASE BUNDLE PATCH 12.1.0.2.170814\nLogfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/26609798\/21481992\/26609798_apply_G100316_CD\nBROOT_2017Sep24_23_48_22.log\nStatus : SUCCESS\n\nPatch Id : 26925263\nAction : APPLY\nAction Time : 29-MAY-2018 15:40:27\nDescription : DATABASE BUNDLE PATCH 12.1.0.2.180116\nLogfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/26925263\/21857460\/26925263_apply_DB01TST_20\n18May29_15_40_13.log\nStatus : FAILED\n\nPatch Id : 26925263\nAction : APPLY\nAction Time : 29-MAY-2018 15:53:43\nDescription : DATABASE BUNDLE PATCH 12.1.0.2.180116\nLogfile :\n\/u01\/app\/oracle\/cfgtoollogs\/sqlpatch\/26925263\/21857460\/26925263_apply_DB01TST_20\n18May29_15_53_01.log\nStatus : SUCCESS\n\nexit<\/pre>\n<p>Repeat this operation on all the faulty databases.<\/p>\n<p><strong>8) Patching the storage<\/strong><\/p>\n<p>Patching the storage is actually patching the NVMe disks. This is not always mandatory as your disks can already have the latest version. So, if needed, apply the patch:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli update-storage -v 12.2.1.3.0\n{\n\"jobId\" : \"4a221df4-8c85-4f34-aa7f-e014cdb751f7\",\n\"status\" : \"Created\",\n\"message\" : \"Success of Storage Update may trigger reboot of node after 4-5 minutes. Please wait till node restart\",\n\"reports\" : [ ],\n\"createTimestamp\" : \"May 29, 2018 13:27:41 PM CEST\",\n\"resourceList\" : [ ],\n\"description\" : \"Storage Firmware Patching\",\n\"updatedTime\" : \"May 29, 2018 13:27:41 PM CEST\"\n}\n\nodacli describe-job -i \"4a221df4-8c85-4f34-aa7f-e014cdb751f7\"\n\nJob details\n----------------------------------------------------------------\nID:  4a221df4-8c85-4f34-aa7f-e014cdb751f7\nDescription:  Storage Firmware Patching\nStatus:  Success\nCreated:  May 29, 2018 1:27:41 PM CEST\nMessage:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nApplying Firmware Disk Patches           May 29, 2018 1:27:41 PM CEST        May 29, 2018 1:27:45 PM CEST        Success\nApplying Firmware Expander Patches       May 29, 2018 1:27:45 PM CEST        May 29, 2018 1:27:52 PM CEST        Success\nApplying Firmware Controller Patches     May 29, 2018 1:27:52 PM CEST        May 29, 2018 1:28:51 PM CEST        Success\npreRebootNode Actions                    May 29, 2018 1:28:51 PM CEST        May 29, 2018 1:28:51 PM CEST        Success\nReboot Ilom                              May 29, 2018 1:28:51 PM CEST        May 29, 2018 1:28:51 PM CEST        Success<\/pre>\n<p>Beware of the reboot of the server few minutes after the patching is finished! And control the components version after the reboot.<\/p>\n<p><strong>9) Optional: deploy the latest db clone files<\/strong><\/p>\n<p>If you&#8217;ll never deploy a new dbhome this step is not necessary. If you will, or simply if you don&#8217;t know if you&#8217;ll have to do that later, download and register the new db clone files in the repository to be able to create a new dbhome at the same patch level, for example:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">cd \/opt\/patch\nunzip p23494992_122130_Linux-x86-64.zip\nArchive:  p23494992_122130_Linux-x86-64.zip\n extracting: odacli-dcs-12.2.1.3.0-180320-DB-12.1.0.2.zip\n  inflating: README.txt\n\nupdate-image --image-files odacli-dcs-12.2.1.3.0-180320-DB-12.1.0.2.zip\nUnpacking will take some time,  Please wait...\nUnzipping odacli-dcs-12.2.1.3.0-180320-DB-12.1.0.2.zip<\/pre>\n<p><strong>10) Control the version of the components<\/strong><\/p>\n<p>Now the patching is done. It took about 2 hours, not so bad for all these updates. Finally, do a last check of the components to see if everything is fine:<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">odacli describe-component\nSystem Version\n---------------\n12.2.1.3.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK                                       12.2.1.3.0            up-to-date\nGI                                        12.2.0.1.180116       up-to-date\nDB {\n[ OraDB12102_home1 ]                      12.1.0.2.180116       up-to-date\n[ OraDB11204_home1 ]                      11.2.0.4.180116       up-to-date\n}\nDCSAGENT                                  18.1.3.0.0            up-to-date\nILOM                                      4.0.0.24.r121140      up-to-date\nBIOS                                      39090000              up-to-date\nOS                                        6.9                   up-to-date\nFIRMWARECONTROLLER {\n[ c6 ]                                    4.650.00-7176         up-to-date\n[ c0,c1,c2,c3,c4,c5 ]                     KPYAGR3Q              up-to-date\n}\nFIRMWAREDISK                              0R3Q                  up-to-date<\/pre>\n<p>Everything should be up-to-date now, until the next patch \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Here is the latest patch for your ODA and it seems that Oracle documentation for this patch is not exactly the procedure you&#8217;ll have to follow to successfully patch your appliance. I recently updated X6-2M and X6-2L to this latest release and here is how to do that. In this example I was patching from [&hellip;]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[],"type_dbi":[],"class_list":["post-11305","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Patching ODA lite to 12.2.1.3.0 - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Patching ODA lite to 12.2.1.3.0\" \/>\n<meta property=\"og:description\" content=\"Here is the latest patch for your ODA and it seems that Oracle documentation for this patch is not exactly the procedure you&#8217;ll have to follow to successfully patch your appliance. I recently updated X6-2M and X6-2L to this latest release and here is how to do that. In this example I was patching from [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-05-31T12:57:46+00:00\" \/>\n<meta name=\"author\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"Patching ODA lite to 12.2.1.3.0\",\"datePublished\":\"2018-05-31T12:57:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\"},\"wordCount\":892,\"commentCount\":0,\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\",\"name\":\"Patching ODA lite to 12.2.1.3.0 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-05-31T12:57:46+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patching ODA lite to 12.2.1.3.0\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\",\"name\":\"J\u00e9r\u00f4me Dubar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"caption\":\"J\u00e9r\u00f4me Dubar\"},\"description\":\"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Patching ODA lite to 12.2.1.3.0 - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/","og_locale":"en_US","og_type":"article","og_title":"Patching ODA lite to 12.2.1.3.0","og_description":"Here is the latest patch for your ODA and it seems that Oracle documentation for this patch is not exactly the procedure you&#8217;ll have to follow to successfully patch your appliance. I recently updated X6-2M and X6-2L to this latest release and here is how to do that. In this example I was patching from [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/","og_site_name":"dbi Blog","article_published_time":"2018-05-31T12:57:46+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"Patching ODA lite to 12.2.1.3.0","datePublished":"2018-05-31T12:57:46+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/"},"wordCount":892,"commentCount":0,"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/","url":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/","name":"Patching ODA lite to 12.2.1.3.0 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-05-31T12:57:46+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/patching-oda-lite-to-12-2-1-3-0\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Patching ODA lite to 12.2.1.3.0"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd","name":"J\u00e9r\u00f4me Dubar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","caption":"J\u00e9r\u00f4me Dubar"},"description":"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.","url":"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11305","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11305"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11305\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11305"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}