{"id":14656,"date":"2021-08-12T18:19:57","date_gmt":"2021-08-12T21:19:57","guid":{"rendered":"https:\/\/www.dbarj.com.br\/?p=14656"},"modified":"2021-08-12T18:39:19","modified_gmt":"2021-08-12T21:39:19","slug":"patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform","status":"publish","type":"post","link":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/","title":{"rendered":"Patching fails with &#8220;Linux x86-64 that is not one of the supported platform&#8221;"},"content":{"rendered":"<p>The <strong>19.12<\/strong> patch cycle was out last week for both Database and Grid Infrastructure. Since then, I&#8217;ve seen some customers complaining about an issue in the tomcat patch when trying to patch their environment with the latest opatch version:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">The oracle home \/u01\/app\/grid has a platform  Linux x86-64 that is not one of the supported platform for the given patch: [ Generic Platform]\r\nOPATCHAUTO-72009: Invalid ARU id for the platform.\r\nOPATCHAUTO-72009: ARU id value not recognized as a valid id for the platform.\r\nOPATCHAUTO-72009: Check system configuration.\r\nOPatchAuto failed.<\/pre>\n<p>In this post, I will try to simulate the issue and show how to fix it.<\/p>\n<p>So, first I downloaded both GI 19.12 and the latest opatch:<\/p>\n<ul>\n<li>Patch 32895426 &#8211; GI Release Update 19.12.0.0.210720<\/li>\n<li>https:\/\/updates.oracle.com\/download\/6880880.html<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>In GI 19.12 README, we have under <strong>&#8220;1.2.1.1 OPatch Utility Information&#8221;<\/strong>:<\/p>\n<div>\n<p><em>You must use the OPatch utility version <strong>12.2.0.1.25<\/strong> or later to apply this patch. Oracle recommends that you use the latest released OPatch version for 12.2 which is available for download from My Oracle Support patch\u00a0<a href=\"https:\/\/updates.oracle.com\/ARULink\/PatchDetails\/process_form?patch_num=6880880\" target=\"_blank\" rel=\"noopener\">6880880<\/a>\u00a0by selecting ARU link for the 12.2.0.1.0 OPatch release. It is recommended that you download the OPatch utility and the patch in a shared location to be able to access them from any node in the cluster for the patch application on each node.<\/em><\/p>\n<\/div>\n<p>So I&#8217;m using the required version:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"shell\">[root@node1 GI_19_12]# opatchauto version\r\nOracle OPatchAuto Version 12.2.1.25.0\r\nCopyright (c) 2016, Oracle Corporation.  All rights reserved.\r\n\r\n1. OPatchAuto version 12.2.1.25.0\r\n2. OpatchautoDB version 12.2.0.1.25<\/pre>\n<p>Let me start patching right away.<\/p>\n<p>PS: Note that I always recommend OOP (Out-of-Place) patching, as you reduce downtime and also the risk of issues. However, here I will use in-place to show what to do when you get stuck in the middle with one of your nodes down.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# opatchauto apply .\/32895426\/ -oh \/u01\/app\/grid\r\n\r\nOPatchauto session is initiated at Thu Aug 12 09:55:51 2021\r\n\r\nSystem initialization log file is \/u01\/app\/grid\/cfgtoollogs\/opatchautodb\/systemconfig2021-08-12_09-56-12AM.log.\r\n\r\nSession log file is \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/opatchauto2021-08-12_09-56-33AM.log\r\nThe id for this session is 1L1V\r\n\r\nExecuting OPatch prereq operations to verify patch applicability on home \/u01\/app\/grid\r\nPatch applicability verified successfully on home \/u01\/app\/grid\r\n\r\n\r\nExecuting patch validation checks on home \/u01\/app\/grid\r\nPatch validation checks successfully completed on home \/u01\/app\/grid\r\n\r\n\r\nPerforming prepatch operations on CRS - bringing down CRS service on home \/u01\/app\/grid\r\nPrepatch operation log file location: \/gihome\/crsdata\/node1\/crsconfig\/crs_prepatch_apply_inplace_node1_2021-08-12_09-57-47AM.log\r\nCRS service brought down successfully on home \/u01\/app\/grid\r\n\r\n\r\nStart applying binary patch on home \/u01\/app\/grid\r\nBinary patch applied successfully on home \/u01\/app\/grid\r\n\r\n\r\nPerforming postpatch operations on CRS - starting CRS service on home \/u01\/app\/grid\r\nPostpatch operation log file location: \/gihome\/crsdata\/node1\/crsconfig\/crs_postpatch_apply_inplace_node1_2021-08-12_10-15-48AM.log\r\nCRS service started successfully on home \/u01\/app\/grid\r\n\r\nOPatchAuto successful.\r\n\r\n--------------------------------Summary--------------------------------\r\n\r\nPatching is completed successfully. Please find the summary as follows:\r\n\r\nHost:node1\r\nCRS Home:\/u01\/app\/grid\r\nVersion:19.0.0.0.0\r\nSummary:\r\n\r\n==Following patches were SUCCESSFULLY applied:\r\n\r\nPatch: \/home\/oracle\/GI_19_12\/32895426\/32585572\r\nLog: \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2021-08-12_10-02-26AM_1.log\r\n\r\nPatch: \/home\/oracle\/GI_19_12\/32895426\/32904851\r\nLog: \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2021-08-12_10-02-26AM_1.log\r\n\r\nPatch: \/home\/oracle\/GI_19_12\/32895426\/32915586\r\nLog: \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2021-08-12_10-02-26AM_1.log\r\n\r\nPatch: \/home\/oracle\/GI_19_12\/32895426\/32916816\r\nLog: \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2021-08-12_10-02-26AM_1.log\r\n\r\nPatch: \/home\/oracle\/GI_19_12\/32895426\/32918050\r\nLog: \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2021-08-12_10-02-26AM_1.log\r\n\r\n\r\n\r\nOPatchauto session completed at Thu Aug 12 10:21:25 2021\r\nTime taken to complete the session 25 minutes, 34 seconds<\/pre>\n<p>So as you can see I haven&#8217;t had any issues. After researching a bit more, I found out this was an issue with &#8220;<strong>opatchauto resume<\/strong>&#8220;, not with &#8220;<strong>opatchauto apply<\/strong>&#8220;. And more specific to the opatch version &#8220;.25&#8221;, the one required by this GI.<\/p>\n<p>So let&#8217;s forcibly introduce an error and try again the &#8220;<strong>opatchauto resume<\/strong>&#8221; in a new environment to simulate this issue. Here what I did was removing the execution flag from the java binary that will be shipped to the GRID_HOME. So this way java will fail to execute after the node is patched:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# ls -la 32895426\/32904851\/files\/jdk\/bin\/java\r\n-rwxr-xr-x 1 oracle oinstall 8712 Jul 20 16:42 32895426\/32904851\/files\/jdk\/bin\/java\r\n[root@node1 GI_19_12]# chmod -x 32895426\/32904851\/files\/jdk\/bin\/java\r\n[root@node1 GI_19_12]# ls -la 32895426\/32904851\/files\/jdk\/bin\/java\r\n-rw-r--r-- 1 oracle oinstall 8712 Jul 20 16:42 32895426\/32904851\/files\/jdk\/bin\/java<\/pre>\n<p>Now if I try <strong>opatchauto apply:<\/strong><\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# opatchauto apply .\/32895426\/ -oh \/u01\/app\/grid\r\n\r\nOPatchauto session is initiated at Thu Aug 12 13:20:28 2021\r\n\r\nSystem initialization log file is \/u01\/app\/grid\/cfgtoollogs\/opatchautodb\/systemconfig2021-08-12_01-20-39PM.log.\r\n\r\nSession log file is \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/opatchauto2021-08-12_01-21-15PM.log\r\nThe id for this session is 7SDU\r\n\r\nExecuting OPatch prereq operations to verify patch applicability on home \/u01\/app\/grid\r\nPatch applicability verified successfully on home \/u01\/app\/grid\r\n\r\n\r\nExecuting patch validation checks on home \/u01\/app\/grid\r\nPatch validation checks successfully completed on home \/u01\/app\/grid\r\n\r\n\r\nPerforming prepatch operations on CRS - bringing down CRS service on home \/u01\/app\/grid\r\nPrepatch operation log file location: \/gihome\/crsdata\/node1\/crsconfig\/crs_prepatch_apply_inplace_node1_2021-08-12_01-22-38PM.log\r\nCRS service brought down successfully on home \/u01\/app\/grid\r\n\r\n\r\nStart applying binary patch on home \/u01\/app\/grid\r\nFailed while applying binary patches on home \/u01\/app\/grid\r\n\r\nExecution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures:\r\nPatch Target : node1-&gt;\/u01\/app\/grid Type[crs]\r\nDetails: [\r\n---------------------------Patching Failed---------------------------------\r\nCommand execution failed during patching in home: \/u01\/app\/grid, host: node1.\r\nCommand failed:  \/u01\/app\/grid\/OPatch\/opatchauto  apply .\/32895426\/ -oh \/u01\/app\/grid -target_type cluster -binary -invPtrLoc \/u01\/app\/grid\/oraInst.loc -jre \/u01\/app\/grid\/OPatch\/jre -persistresult \/u01\/app\/grid\/opatchautocfg\/db\/sessioninfo\/sessionresult_node1_crs_14.ser -analyzedresult \/u01\/app\/grid\/opatchautocfg\/db\/sessioninfo\/sessionresult_analyze_node1_crs_14.ser\r\nCommand failure output:\r\n==Following patches FAILED in apply:\r\n\r\nPatch: \/home\/oracle\/GI_19_12\/32895426\/32904851\r\nLog: \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2021-08-12_13-25-19PM_1.log\r\nReason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: ApplySession failed in system modification phase... 'ApplySession::apply failed: \/u01\/app\/grid\/bin\/patchgen: line 138: \/u01\/app\/grid\/jdk\/bin\/java: Permission denied\r\n'\r\n\r\nAfter fixing the cause of failure Run opatchauto resume\r\n\r\n]\r\nOPATCHAUTO-68061: The orchestration engine failed.\r\nOPATCHAUTO-68061: The orchestration engine failed with return code 1\r\nOPATCHAUTO-68061: Check the log for more details.\r\nOPatchAuto failed.\r\n\r\nOPatchauto session completed at Thu Aug 12 13:30:57 2021\r\nTime taken to complete the session 10 minutes, 30 seconds\r\n\r\n opatchauto failed with error code 42<\/pre>\n<p>It failed with &#8220;<strong>ApplySession::apply failed: \/u01\/app\/grid\/bin\/patchgen: line 138: \/u01\/app\/grid\/jdk\/bin\/java: Permission denied<\/strong>&#8221; as expected.<\/p>\n<p>Let&#8217;s try to fix back the java permission and retry:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# ls -la 32895426\/32904851\/files\/jdk\/bin\/java\r\n-rw-r--r-- 1 oracle oinstall 8712 Jul 20 16:42 32895426\/32904851\/files\/jdk\/bin\/java\r\n[root@node1 GI_19_12]# chmod +x 32895426\/32904851\/files\/jdk\/bin\/java\r\n[root@node1 GI_19_12]# ls -la 32895426\/32904851\/files\/jdk\/bin\/java\r\n-rwxr-xr-x 1 oracle oinstall 8712 Jul 20 16:42 32895426\/32904851\/files\/jdk\/bin\/java\r\n[root@node1 GI_19_12]#<\/pre>\n<p>I will also fix the java file that was already shipped to the GRID_HOME:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# ls -la $ORACLE_HOME\/jdk\/bin\/java\r\n-rw-r--r-- 1 oracle oinstall 8712 Jul 20 16:42 \/u01\/app\/grid\/jdk\/bin\/java\r\n[root@node1 GI_19_12]# chmod +x $ORACLE_HOME\/jdk\/bin\/java\r\n[root@node1 GI_19_12]# ls -la $ORACLE_HOME\/jdk\/bin\/java\r\n-rwxr-xr-x 1 oracle oinstall 8712 Jul 20 16:42 \/u01\/app\/grid\/jdk\/bin\/java\r\n[root@node1 GI_19_12]#<\/pre>\n<p>Retrying:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# opatchauto resume\r\n\r\nOPatchauto session is initiated at Thu Aug 12 13:32:34 2021\r\nSession log file is \/u01\/app\/grid\/cfgtoollogs\/opatchauto\/opatchauto2021-08-12_01-32-38PM.log\r\nResuming existing session with id 7SDU\r\nThe oracle home \/u01\/app\/grid has a platform  Linux x86-64 that is not one of the supported platform for the given patch: [ Generic Platform]\r\nOPATCHAUTO-72009: Invalid ARU id for the platform.\r\nOPATCHAUTO-72009: ARU id value not recognized as a valid id for the platform.\r\nOPATCHAUTO-72009: Check system configuration.\r\nOPatchAuto failed.\r\n\r\nOPatchauto session completed at Thu Aug 12 13:33:08 2021\r\nTime taken to complete the session 0 minute, 34 seconds\r\n\r\n opatchauto failed with error code 42\r\n<\/pre>\n<p>Now as you can see we are stuck in this failure where we can&#8217;t resume. There is a MOS Note for it:<\/p>\n<table id=\"kmPgTpl:r1:0:tl5\" border=\"0\" summary=\"\" width=\"100%\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr id=\"kmPgTpl:r1:0:rl12\">\n<td id=\"kmPgTpl:r1:0:cf49\" align=\"left\"><a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocContentDisplay?id=2783608.1\" target=\"_blank\" rel=\"noopener\"><span id=\"kmPgTpl:r1:0:ol22\" class=\"xq\"><label>OPatchauto fails with OPATCHAUTO-72009: Invalid ARU id for the platform (Doc ID 2783608.1)<\/label><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Basically, this is an issue introduced on opatchauto &#8220;.25&#8221; and will be fixed on the &#8220;.27&#8221;, that happens when trying to resume and when the Patch has a generic platform.<\/p>\n<p>The MOS note suggests 2 ways for solving it:<\/p>\n<ol>\n<li>Restore from backup older OPatch version .24 or .23 and invoke OPatchauto resume.<\/li>\n<li>If there is no backup older version of OPatch then we can apply the patch manually via OPatch apply against &lt;GI_HOME&gt; and when done we must run the below to run the post steps in order to lock &lt;GI_HOME&gt; and bring the CRS stack.<\/li>\n<\/ol>\n<p>&nbsp;<\/p>\n<p>As I don&#8217;t have a previous &#8220;.24&#8221; patch to try, the best option here would be to try the second method: applying this specific patch that failed (in my case it was the 32918050) manually.<\/p>\n<p>However, applying a patch manually in GI is not that simple. You may need to stop your CRS \/ unlock grid home \/ do it in multiple nodes \/ etc. There is even a MOS note for it. In step 5 of note below, you have all the details:<\/p>\n<table id=\"kmPgTpl:r1:0:tl5\" border=\"0\" summary=\"\" width=\"100%\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr id=\"kmPgTpl:r1:0:rl12\">\n<td id=\"kmPgTpl:r1:0:cf49\" align=\"left\"><a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocContentDisplay?id=2246888.1\" target=\"_blank\" rel=\"noopener\"><span id=\"kmPgTpl:r1:0:ol22\" class=\"p_AFHoverTarget xq\"><label>Supplemental Readme &#8211; Grid Infrastructure Release Update 12.2.0.1.x \/ 18c \/19c (Doc ID 2246888.1)<\/label><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>What I rather prefer to do is just restart the GI back and retry &#8220;<strong>opatchauto apply<\/strong>&#8221; instead of using the bugged &#8220;<strong>opatchauto resume<\/strong>&#8220;:<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"generic\">[root@node1 GI_19_12]# $ORACLE_HOME\/bin\/crsctl start crs\r\nCRS-4123: Oracle High Availability Services has been started.\r\n[root@node1 GI_19_12]# opatchauto apply .\/32895426\/ -oh \/u01\/app\/grid<\/pre>\n<p>And it succeeds. That is it. Here are my 50 cents with a third option to solve the stuck GI patch apply. Just keep in mind that If DB is involved, then also start the database using &#8220;<strong>srvctl start database<\/strong>&#8220;.<\/p>\n<b>Have you enjoyed? Please leave a comment or give a \ud83d\udc4d!<\/b>\n<div class='watch-action'><div class='watch-position align-left'><div class='action-like'><a class='lbg-style2 like-14656 jlk' href='javascript:void(0)' data-task='like' data-post_id='14656' data-nonce='de4404f630' rel='nofollow'><img class='wti-pixel' src='https:\/\/www.dbarj.com.br\/wp-content\/plugins\/wti-like-post\/images\/pixel.gif' title='Like' \/><span class='lc-14656 lc'>+4<\/span><\/a><\/div><\/div> <div class='status-14656 status align-left'><\/div><\/div><div class='wti-clear'><\/div>","protected":false},"excerpt":{"rendered":"<p>The 19.12 patch cycle was out last week for both Database and Grid Infrastructure. Since then, I&#8217;ve seen some customers complaining about an issue in the tomcat patch when trying to patch their environment with the latest opatch version: The oracle home \/u01\/app\/grid has a platform Linux x86-64 that is not one of the supported &hellip; <\/p>\n<p><a class=\"more-link btn\" href=\"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/\">Continue reading<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[],"class_list":["post-14656","post","type-post","status-publish","format-standard","hentry","category-database-en","item-wrap"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.4 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Patching fails with &quot;Linux x86-64 that is not one of the supported platform&quot; - DBA - Rodrigo Jorge - Oracle Tips and Guides<\/title>\n<meta name=\"description\" content=\"How to solve the &quot;Linux x86-64 that is not one of the supported platform&quot; when running &quot;opatchauto resume&quot;.\" \/>\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.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"DBA RJ\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/\"},\"author\":{\"name\":\"DBA RJ\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\"},\"headline\":\"Patching fails with &#8220;Linux x86-64 that is not one of the supported platform&#8221;\",\"datePublished\":\"2021-08-12T21:19:57+00:00\",\"dateModified\":\"2021-08-12T21:39:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/\"},\"wordCount\":676,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\"},\"articleSection\":[\"Oracle Database General\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/\",\"url\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/\",\"name\":\"Patching fails with \\\"Linux x86-64 that is not one of the supported platform\\\" - DBA - Rodrigo Jorge - Oracle Tips and Guides\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#website\"},\"datePublished\":\"2021-08-12T21:19:57+00:00\",\"dateModified\":\"2021-08-12T21:39:19+00:00\",\"description\":\"How to solve the \\\"Linux x86-64 that is not one of the supported platform\\\" when running \\\"opatchauto resume\\\".\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/2021\\\/08\\\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patching fails with \\\"Linux x86-64 that is not one of the supported platform\\\"\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/\",\"name\":\"DBA - Rodrigo Jorge - Oracle Tips and Guides\",\"description\":\"Blog about Databases, Security and High Availability\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/en\\\/#\\\/schema\\\/person\\\/28a44ca3a6633fe4156ad1ea209d40a9\",\"name\":\"DBA RJ\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\",\"url\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\",\"contentUrl\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\",\"width\":712,\"height\":712,\"caption\":\"DBA RJ\"},\"logo\":{\"@id\":\"https:\\\/\\\/www.dbarj.com.br\\\/wp-content\\\/uploads\\\/2019\\\/09\\\/RodrigoJorgePOUG19.png\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Patching fails with \"Linux x86-64 that is not one of the supported platform\" - DBA - Rodrigo Jorge - Oracle Tips and Guides","description":"How to solve the \"Linux x86-64 that is not one of the supported platform\" when running \"opatchauto resume\".","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.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/","twitter_misc":{"Written by":"DBA RJ","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/#article","isPartOf":{"@id":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/"},"author":{"name":"DBA RJ","@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9"},"headline":"Patching fails with &#8220;Linux x86-64 that is not one of the supported platform&#8221;","datePublished":"2021-08-12T21:19:57+00:00","dateModified":"2021-08-12T21:39:19+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/"},"wordCount":676,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9"},"articleSection":["Oracle Database General"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/","url":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/","name":"Patching fails with \"Linux x86-64 that is not one of the supported platform\" - DBA - Rodrigo Jorge - Oracle Tips and Guides","isPartOf":{"@id":"https:\/\/www.dbarj.com.br\/en\/#website"},"datePublished":"2021-08-12T21:19:57+00:00","dateModified":"2021-08-12T21:39:19+00:00","description":"How to solve the \"Linux x86-64 that is not one of the supported platform\" when running \"opatchauto resume\".","breadcrumb":{"@id":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbarj.com.br\/en\/2021\/08\/patching-fails-with-linux-x86-64-that-is-not-one-of-the-supported-platform\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbarj.com.br\/en\/"},{"@type":"ListItem","position":2,"name":"Patching fails with \"Linux x86-64 that is not one of the supported platform\""}]},{"@type":"WebSite","@id":"https:\/\/www.dbarj.com.br\/en\/#website","url":"https:\/\/www.dbarj.com.br\/en\/","name":"DBA - Rodrigo Jorge - Oracle Tips and Guides","description":"Blog about Databases, Security and High Availability","publisher":{"@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbarj.com.br\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.dbarj.com.br\/en\/#\/schema\/person\/28a44ca3a6633fe4156ad1ea209d40a9","name":"DBA RJ","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png","url":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png","contentUrl":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png","width":712,"height":712,"caption":"DBA RJ"},"logo":{"@id":"https:\/\/www.dbarj.com.br\/wp-content\/uploads\/2019\/09\/RodrigoJorgePOUG19.png"}}]}},"_links":{"self":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts\/14656","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/comments?post=14656"}],"version-history":[{"count":5,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts\/14656\/revisions"}],"predecessor-version":[{"id":14661,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/posts\/14656\/revisions\/14661"}],"wp:attachment":[{"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/media?parent=14656"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/categories?post=14656"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbarj.com.br\/en\/wp-json\/wp\/v2\/tags?post=14656"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}