{"id":955,"date":"2025-01-09T16:19:49","date_gmt":"2025-01-09T15:19:49","guid":{"rendered":"https:\/\/anjo.pt\/keyword-oracle\/?p=955"},"modified":"2025-02-12T11:51:15","modified_gmt":"2025-02-12T10:51:15","slug":"warning-opatchauto-ignores-disabled-components-possible-licensing-issues","status":"publish","type":"post","link":"https:\/\/anjo.pt\/keyword-oracle\/2025\/01\/09\/warning-opatchauto-ignores-disabled-components-possible-licensing-issues\/","title":{"rendered":"Warning: OPatchauto ignores disabled components &#8211; possible licensing issues"},"content":{"rendered":"\n<p>Since many years at my customer I&#8217;m using &#8220;opatchauto&#8221; to perform a out-of-place patching of Oracle Restart (GI+RDBMS).<\/p>\n\n\n\n<p>My customer is concerned about database users using not licensed options, like partitioning. To avoid it, at the installation time the partitioning option is disabled using chopt, like described at <a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocumentDisplay?parent=SrDetailText&amp;sourceId=3-39309619481&amp;id=948061.1\" target=\"_blank\" rel=\"noreferrer noopener\">Doc ID 948061.1<\/a>. <\/p>\n\n\n\n<p><strong>Today <\/strong>during a check we noticed that Partitioning option was activated everywhere, which is not the client standard! We found out the origin of the problem was the out-of-place patching with &#8220;opatchauto&#8221;.<\/p>\n\n\n\n<p>The big advantage of using &#8220;opatchauto&#8221; is that it allows easily either a single-step or a two-step Out-of-Place patching. We just write in a properties file the name of the new Oracle Homes and it does:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clone current GI + RDBMS homes to new Homes (prepare clone)<\/li>\n\n\n\n<li>Patches the new homes (prepare clone)<\/li>\n\n\n\n<li>Stops GI and DBs (switch clone)<\/li>\n\n\n\n<li>Switches GI and DBs from current homes to new Homes (switch clone)<\/li>\n\n\n\n<li>Restart everything (switch clone)<\/li>\n\n\n\n<li>Runs Datapatch on DBs if not standby (switch clone)<\/li>\n<\/ul>\n\n\n\n<p>This allows to decrease the patching downtime without RAC to about 10 minutes, with the two-step (prepare clone + switch clone) operation.<\/p>\n\n\n\n<p>Here the steps to reproduce de bug:<\/p>\n\n\n\n<!--more-->\n\n\n\n<p> &#8211; install GI + RDBMS Oracle 19c (p.e 19.24) on server<\/p>\n\n\n\n<p>&#8211; on RDBMS ORACLE_HOME disable partitioning component as described on&nbsp;<a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocumentDisplay?parent=SrDetailText&amp;sourceId=3-39309619481&amp;id=948061.1\" target=\"_blank\" rel=\"noreferrer noopener\">Doc ID 948061.1<\/a>:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n$ chopt disable partitioning\nWriting to \/u00\/app\/oracle\/product\/19.24.0\/install\/disable_partitioning_2025-01-09_11-40-06AM.log...\n\/usr\/bin\/make -f \/u00\/app\/oracle\/product\/19.24.0\/rdbms\/lib\/ins_rdbms.mk part_off ORACLE_HOME=\/u00\/app\/oracle\/product\/19.24.0\n\/usr\/bin\/make -f \/u00\/app\/oracle\/product\/19.24.0\/rdbms\/lib\/ins_rdbms.mk ioracle ORACLE_HOME=\/u00\/app\/oracle\/product\/19.24.0\n<\/pre><\/div>\n\n\n<p>&#8211; Check &#8211; partition is disabled:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n$ ar -tv \/u00\/app\/oracle\/product\/19.24.0\/rdbms\/lib\/libknlopt.a | grep -E &#039;kkpoban|ksnkkpo&#039;\nrw-r--r-- 1000\/1001 5240 Apr 17 07:25 2019 ksnkkpo.o\n<\/pre><\/div>\n\n\n<p>&#8211; Perform out of place patching of DB from GI ORACLE_HOME (single-step example here):<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n$ cat \/staging\/clone.properties\n\/u00\/app\/grid\/19.24.0=\/u00\/app\/grid\/19.25.0\n\/u00\/app\/oracle\/product\/19.24.0=\/u00\/app\/oracle\/product\/19.25.0\n\n$ echo $ORACLE_HOME\n\/u00\/app\/grid\/19.24.0\n\n$ sudo ${ORACLE_HOME}\/OPatch\/opatchauto apply -phBaseDir \/staging\/RU_19c_OCT2024\/ -outofplace -silent \/staging\/clone.properties\n\nOPatchauto session is initiated at Thu Jan  9 12:30:25 2025\n\nSystem initialization log file is \/u00\/app\/grid\/19.24.0\/cfgtoollogs\/opatchautodb\/systemconfig2025-01-09_12-30-30PM.log.\n\nSession log file is \/u00\/app\/grid\/19.24.0\/cfgtoollogs\/opatchauto\/opatchauto2025-01-09_12-30-34PM.log\nThe id for this session is GAEM\n\nExecuting OPatch prereq operations to verify patch applicability on home \/u00\/app\/grid\/19.24.0\nPatch applicability verified successfully on home \/u00\/app\/grid\/19.24.0\n\n\nExecuting OPatch prereq operations to verify patch applicability on home \/u00\/app\/oracle\/product\/19.24.0\nPatch applicability verified successfully on home \/u00\/app\/oracle\/product\/19.24.0\n\n\nExecuting patch validation checks on home \/u00\/app\/grid\/19.24.0\nPatch validation checks successfully completed on home \/u00\/app\/grid\/19.24.0\n\n\nExecuting patch validation checks on home \/u00\/app\/oracle\/product\/19.24.0\nPatch validation checks successfully completed on home \/u00\/app\/oracle\/product\/19.24.0\n\n\nVerifying SQL patch applicability on home \/u00\/app\/oracle\/product\/19.24.0\nSkipping SQL patch step execution on standby database : C0201Z01_ENG1\nNo sqlpatch prereq operations are required on the local node for this home\nNo step execution required.........\n\nCopying the files from the existing oracle home \/u00\/app\/grid\/19.24.0 to a new location. Please wait...\n\nCopying the files from the existing oracle home \/u00\/app\/oracle\/product\/19.24.0 to a new location. Please wait...\nClone of oracle home \/u00\/app\/grid\/19.24.0 is \/u00\/app\/grid\/19.25.0 on host vm01\nCopying the files from the existing oracle home \/u00\/app\/grid\/19.24.0 to a new location is successful.\n\nClone of oracle home \/u00\/app\/oracle\/product\/19.24.0 is \/u00\/app\/oracle\/product\/19.25.0 on host vm01\nCopying the files from the existing oracle home \/u00\/app\/oracle\/product\/19.24.0 to a new location is successful.\n\n\nUnlocking CRS clone home for home \/u00\/app\/grid\/19.24.0.\nPrepatch operation log file location: \/u00\/app\/oracle\/crsdata\/vm01\/crsconfig\/hapatch_2025-01-09_12-49-31AM.log\nUnlocked CRS clone home successfully for home \/u00\/app\/grid\/19.24.0.\n\n\nCreating clone for oracle home \/u00\/app\/grid\/19.24.0.\nClone operation successful for oracle home \/u00\/app\/grid\/19.24.0.\n\n\nCreating clone for oracle home \/u00\/app\/oracle\/product\/19.24.0.\nClone operation successful for oracle home \/u00\/app\/oracle\/product\/19.24.0.\n\n\nPerforming post clone operation for oracle home \/u00\/app\/grid\/19.24.0.\nPerforming post clone operation was successful for oracle home \/u00\/app\/grid\/19.24.0.\n\n\nPerforming post clone operation for oracle home \/u00\/app\/oracle\/product\/19.24.0.\nPerforming post clone operation was successful for oracle home \/u00\/app\/oracle\/product\/19.24.0.\n\n\nStart applying binary patch on home \/u00\/app\/grid\/19.25.0\nBinary patch applied successfully on home \/u00\/app\/grid\/19.25.0\n\n\nStart applying binary patch on home \/u00\/app\/oracle\/product\/19.25.0\nBinary patch applied successfully on home \/u00\/app\/oracle\/product\/19.25.0\n\n\nRunning rootadd_rdbms.sh on home \/u00\/app\/grid\/19.25.0\nSuccessfully executed rootadd_rdbms.sh on home \/u00\/app\/grid\/19.25.0\n\n\nRunning rootadd_rdbms.sh on home \/u00\/app\/oracle\/product\/19.25.0\nSuccessfully executed rootadd_rdbms.sh on home \/u00\/app\/oracle\/product\/19.25.0\n\n\nUpdate nodelist in the inventory for oracle home \/u00\/app\/grid\/19.25.0.\nUpdate nodelist in the inventory is completed for oracle home \/u00\/app\/grid\/19.25.0.\n\n\nBringing down database service on home \/u00\/app\/oracle\/product\/19.25.0\nDatabase service successfully brought down on home \/u00\/app\/oracle\/product\/19.25.0\n\n\nPerforming postpatch operations on CRS - starting CRS service on home \/u00\/app\/grid\/19.25.0\nPostpatch operation log file location: \/u00\/app\/oracle\/crsdata\/vm01\/crsconfig\/hapatch_2025-01-09_01-27-10PM.log\nCRS service started successfully on home \/u00\/app\/grid\/19.25.0\n\n\nPreparing home \/u00\/app\/oracle\/product\/19.25.0 after database service restarted\nNo step execution required.........\n\n\nConfirm that all resources have been started from home \/u00\/app\/grid\/19.25.0.\nAll resources have been started successfully from home \/u00\/app\/grid\/19.25.0.\n\n\nModifying  the database(s) to use new location home \/u00\/app\/oracle\/product\/19.25.0.\nAll database(s) modified successfully to run from new location home \/u00\/app\/oracle\/product\/19.25.0.\n\n\nTrying to apply SQL patch on home \/u00\/app\/oracle\/product\/19.25.0\nSkipping SQL patch step execution on standby database : C0201Z01_ENG1\nNo SQL patch operations are required on local node for this home\n\n\nOPatchAuto successful.\n\n--------------------------------Summary--------------------------------\n\nPatching is completed successfully. Please find the summary as follows:\n\nHost:vm01\nSIHA Home:\/u00\/app\/grid\/19.24.0\nVersion:19.0.0.0.0\nSummary:\n\n==Following patches were SKIPPED:\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36758186\nLog: \/u00\/app\/grid\/19.24.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_12-33-55PM_1.log\nReason: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36758186 is not required to be applied to oracle home \/u00\/app\/grid\/19.24.0\n\n\n==Following patches were SUCCESSFULLY applied:\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36878697\nLog: \/u00\/app\/grid\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_12-51-54PM_1.log\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36912597\nLog: \/u00\/app\/grid\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_12-51-54PM_1.log\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36917397\nLog: \/u00\/app\/grid\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_12-51-54PM_1.log\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36917416\nLog: \/u00\/app\/grid\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_12-51-54PM_1.log\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36940756\nLog: \/u00\/app\/grid\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_12-51-54PM_1.log\n\n\nHost:vm01\nSIDB Home:\/u00\/app\/oracle\/product\/19.24.0\nVersion:19.0.0.0.0\nSummary:\n\n==Following patches were SKIPPED:\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36917397\nReason: This patch is not applicable to this specified target type - &quot;oracle_database&quot;\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36758186\nReason: This patch is not applicable to this specified target type - &quot;oracle_database&quot;\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36940756\nReason: This patch is not applicable to this specified target type - &quot;oracle_database&quot;\n\n\n==Following patches were SUCCESSFULLY applied:\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36878697\nLog: \/u00\/app\/oracle\/product\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_13-09-38PM_1.log\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36912597\nLog: \/u00\/app\/oracle\/product\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_13-09-38PM_1.log\n\nPatch: \/staging\/RU_19c_OCT2024\/36866740\/36916690\/36917416\nLog: \/u00\/app\/oracle\/product\/19.25.0\/cfgtoollogs\/opatchauto\/core\/opatch\/opatch2025-01-09_13-09-38PM_1.log\n\n\nPatching session reported following warning(s):\n_________________________________________________\n\n&#x5B;Note]: Please verify the database is running from the desired Oracle home, if not then manually execute\n $ORACLE_HOME\/bin\/srvctl modify database command to fix the problem\n\n\nOut of place patching clone home(s) summary\n____________________________________________\nHost : vm01\nActual Home : \/u00\/app\/grid\/19.24.0\nVersion:19.0.0.0.0\nClone Home Path : \/u00\/app\/grid\/19.25.0\n\nHost : vm01\nActual Home : \/u00\/app\/oracle\/product\/19.24.0\nVersion:19.0.0.0.0\nClone Home Path : \/u00\/app\/oracle\/product\/19.25.0\n\n\nOPatchauto session completed at Thu Jan  9 13:32:41 2025\nTime taken to complete the session 62 minutes, 16 seconds\n<\/pre><\/div>\n\n\n<p>&#8211; Check &#8211; partition component is enabled on the new Oracle Home:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\n$ ar -tv \/u00\/app\/oracle\/product\/19.25.0\/rdbms\/lib\/libknlopt.a | grep -E &#039;kkpoban|ksnkkpo&#039;\nrw-r--r-- 1000\/1001 5144 Oct 11 13:17 2024 kkpoban.o\n<\/pre><\/div>\n\n\n<p>This problematic is also true for the other components: Advanced Analytics, OLAP and Real Application Testing.<\/p>\n\n\n\n<p>And probably happens also when using Opatchauto with RAC (not tested), as described here at <a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocContentDisplay?id=2419319.1\">Doc ID 2419319.1<\/a>.<\/p>\n\n\n\n<p>I&#8217;ve open a Bug\/SR today on Oracle Support site and will let here know when I&#8217;ve more information.<\/p>\n\n\n\n<p>Update 12.02.2025 &#8211; this Bug was now created by Oracle: <br>Bug 37575498 &#8211; PARTITIONING OPTION GETS ENABLED AFTER OUT-OF-PLACE PATCHING<br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since many years at my customer I&#8217;m using &#8220;opatchauto&#8221; to perform a out-of-place patching of Oracle Restart (GI+RDBMS). My customer is concerned about database users using not licensed options, like partitioning. To avoid it, at the installation time the partitioning option is disabled using chopt, like described at Doc ID 948061.1. Today during a check [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,6,39,18,19],"tags":[],"class_list":{"0":"post-955","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-opatch","7":"category-oracle","8":"category-oracle-19c","9":"category-patchset-update","10":"category-psu","11":"czr-hentry"},"_links":{"self":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/955","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/comments?post=955"}],"version-history":[{"count":3,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/955\/revisions"}],"predecessor-version":[{"id":976,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/posts\/955\/revisions\/976"}],"wp:attachment":[{"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/media?parent=955"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/categories?post=955"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anjo.pt\/keyword-oracle\/wp-json\/wp\/v2\/tags?post=955"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}