{"id":48497,"date":"2026-11-13T15:50:26","date_gmt":"2026-11-13T14:50:26","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=48497"},"modified":"2026-11-13T15:50:35","modified_gmt":"2026-11-13T14:50:35","slug":"oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/","title":{"rendered":"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">If you planning to upgrade your Oracle RAC Clusterware from version 19.30 or higher to release 23.26.1 please be aware that this will not work as there is issue with <strong>de-supported qosmserver and OC4J resource come in 19.30 update.<\/strong> To avoid problem described below, install 23.26.4 which bypass this issue during upgrade.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Always upgrade to version which was released the same time or later then your Older release patched version. <\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example as 23.26.1 was releases earlier then 19.30 of Clusterware it will case you troubles during patching, so always get newest version for now its <strong>October 2026, Release Update 23.26.4 <\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Below I will describe how to rollback in case you face issue with your clusterware upgrade. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">during upgrade from 19.31 >23.26.1 rootupgrade.sh script will fail in step 6 with error <strong>CLSRSC-1009: failed to stop resource OC4J<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;root@rac001_lab:~]# \/u01\/app\/23.26.1\/grid\/rootupgrade.sh\n\nCheck \/u01\/app\/23.26.1\/grid\/install\/root_rac001_lab_2026-11-03_15-43-44-143253259.log for the output of root script\n\n&#91;root@rac001_lab:~]# cat \/u01\/app\/23.26.1\/grid\/install\/root_rac001_lab_2026-11-03_15-43-44-143253259.log\n\nPerforming root user operation.\n\nThe following environment variables are set as:\n\n    ORACLE_OWNER= oracle\n    ORACLE_HOME= \/u01\/app\/23.26.1\/grid\n\n    Copying dbhome to \/usr\/local\/bin ...\n    Copying oraenv to \/usr\/local\/bin ...\n    Copying coraenv to \/usr\/local\/bin ...\n\nEntries will be added to the \/etc\/oratab file as needed by\nDatabase Configuration Assistant when a database is created\n\nFinished running generic part of root script.\nNow product-specific root actions will be performed.\n\nRAC option enabled on: Linux\n\nExecuting command '\/u01\/app\/23.26.1\/grid\/perl\/bin\/perl -I\/u01\/app\/23.26.1\/grid\/perl\/lib -I\/u01\/app\/23.26.1\/grid\/crs\/install \/u01\/app\/23.26.1\/grid\/crs\/install\/rootcrs.pl -upgrade'\n\nUsing configuration parameter file: \/u01\/app\/23.26.1\/grid\/crs\/install\/crsconfig_params\n\nThe log of current session can be found at:\n\n\/u01\/app\/oracle\/crsdata\/rac001_lab\/crsconfig\/crsupgrade_rac001_lab_2026-11-03_03-43-44PM.log\n\n2026\/11\/03 15:43:50 CLSRSC-595: Executing upgrade step 1 of 16: 'UpgradeTFA'.\n\n2026\/11\/03 15:43:50 CLSRSC-4015: Performing install or upgrade action for Oracle Autonomous Health Framework (AHF).\n\n2026\/11\/03 15:43:50 CLSRSC-4012: Shutting down Oracle Autonomous Health Framework (AHF).\n\n2026\/11\/03 15:44:07 CLSRSC-4013: Successfully shut down Oracle Autonomous Health Framework (AHF).\n\n2026\/11\/03 15:44:07 CLSRSC-595: Executing upgrade step 2 of 16: 'ValidateEnv'.\n\n2026\/11\/03 15:44:07 CLSRSC-595: Executing upgrade step 3 of 16: 'GetOldConfig'.\n\n2026\/11\/03 15:44:07 CLSRSC-692: Checking whether CRS entities are ready for upgrade. This operation may take a few minutes.\n\n2026\/11\/03 15:44:08 CLSRSC-693: CRS entities validation completed successfully.\n\n2026\/11\/03 15:44:08 CLSRSC-464: Starting retrieval of the cluster configuration data\n\nCRS-4672: Successfully backed up the Voting File for Cluster Synchronization Service.\n\n2026\/11\/03 15:44:11 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.\n\n2026\/11\/03 15:44:11 CLSRSC-595: Executing upgrade step 4 of 16: 'UpgPrechecks'.\n\n2026\/11\/03 15:44:11 CLSRSC-595: Executing upgrade step 5 of 16: 'SetupOSD'.\n\n2026\/11\/03 15:44:11 CLSRSC-595: Executing upgrade step 6 of 16: 'PreUpgrade'.\n\n2026\/11\/03 15:44:12 CLSRSC-1009: failed to stop resource OC4J\n\nDied at \/u01\/app\/23.26.1\/grid\/crs\/install\/oragqosaserver.pm line 304.\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So if rootupgrade failed and exit in this stage, you need to first downgrade your CRS to &#8216;NORMAL&#8217; state as  it would be [ROLLING UPGRADE] mode , which prevent you from future operations, check your clusterware active version<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\noracle@rac001_lab:\/u01\/app\/19.31.0.0\/grid\/ &#91;+ASM1] crsctl query crs activeversion -f\n\nOracle Clusterware active version on the cluster is &#91;19.0.0.0.0]. The cluster upgrade state is &#91;ROLLING UPGRADE]. The cluster active patch level is &#91;3307946645].<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For RAC Clusterware there are diffrent scenarios for downgrage and rollback depends which stage issue happend.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this case its not so hard, however need downtime for whole cluster. downgrade with &#8211;online option did not work in my case<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">step 1.  Start CRS using the 19c Grid Infrastructure home if down on node<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/u01\/app\/19.31.0.0\/grid\/bin\/crsctl start crs\nCRS-4123: Oracle High Availability Services has been started.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">step 2. Stop ASM rolling migration on both ASM instances nodes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\noracle@rac001_lab:~\/sqlplus \"\/as sysasm\"\nSQL*Plus: Release 19.0.0.0.0 - Production on Wed Nov 4 11:05:16 2026\nVersion 19.31.0.0.0\n\nCopyright (c) 1982, 2026, Oracle. All rights reserved.\n\nConnected to:\nOracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production\nVersion 19.31.0.0.0\n\nSQL> ALTER SYSTEM STOP ROLLING MIGRATION;\n\nSystem altered.\n\n\nNode 2:\n\noracle@rac001_lab2:~\/sqlplus \"\/as sysasm\"\nSQL*Plus: Release 19.0.0.0.0 - Production on Wed Nov 4 11:05:16 2026\nVersion 19.31.0.0.0\n\nCopyright (c) 1982, 2026, Oracle. All rights reserved.\n\nConnected to:\nOracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production\nVersion 19.31.0.0.0\n\nSQL> ALTER SYSTEM STOP ROLLING MIGRATION;\n\nSystem altered.\n\n\n\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">step 3.Run downgrade on the impacted node:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\n\/u01\/app\/23.26.1\/grid\/crs\/install\/rootcrs.sh -downgrade\n\nUsing configuration parameter file: \/u01\/app\/23.26.1\/grid\/crs\/install\/crsconfig_params\n\nThe log of current session can be found at:\n\/u01\/app\/oracle\/crsdata\/rac001_lab\/crsconfig\/crsdowngrade_rac001_lab_2026-11-04_09-23-25AM.log\n\n2026\/11\/04 11:24:07 CLSRSC-4006: Removing Oracle Autonomous Health Framework (AHF).\n2026\/11\/04 11:24:39 CLSRSC-4007: Successfully removed Oracle Autonomous Health Framework (AHF).\n2026\/11\/04 11:24:42 CLSRSC-591: successfully downgraded Oracle Clusterware stack on this node\n2026\/11\/04 11:24:46 CLSRSC-592: Run 'crsctl start crs' from home \/u01\/app\/19.31.0.0\/grid on each node to complete downgrade.\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">step 4. Start crs from old crs home and check configuration<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Node 1\n\/u01\/app\/19.31.0.0\/grid\/bin\/crsctl start crs\nCRS-4123: Oracle High Availability Services has been started.\n\/u01\/app\/19.31.0.0\/grid\/bin\/crsctl query crs activeversion -f\nOracle Clusterware active version on the cluster is &#91;19.31.0.0]. The cluster upgrade state is &#91;NORMAL]. The cluster active patch level is &#91;3367946646].\nOracle Clusterware version on node &#91;rac001_lab] is &#91;19.31.0.0]\n\nNode 2\n\/u01\/app\/19.31.0.0\/grid\/bin\/crsctl start crs\nCRS-4123: Oracle High Availability Services has been started.\n\/u01\/app\/19.31.0.0\/grid\/bin\/crsctl query crs activeversion -f\nOracle Clusterware active version on the cluster is &#91;19.31.0.0]. The cluster upgrade state is &#91;NORMAL]. The cluster active patch level is &#91;3367946646].\nOracle Clusterware version on node &#91;rac001_lab2] is &#91;19.31.0.0]\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now you get back to NORMAL State from before broken upgrade.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To not repeat my mistake, download and install newer version of Clusterware release update in my case issue didn&#8217;t happens on 23.26.4 upgrade.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you planning to upgrade your Oracle RAC Clusterware from version 19.30 or higher to release 23.26.1 please be aware that this will not work as there is issue with de-supported qosmserver and OC4J resource come in 19.30 update. To avoid problem described below, install 23.26.4 which bypass this issue during upgrade. Always upgrade to&hellip;&nbsp;<\/p>\n","protected":false},"author":148,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4133,59],"tags":[37,2248,6415,535,219],"class_list":["post-48497","post","type-post","status-publish","format-standard","hentry","category-database","category-oracle","tag-asm","tag-clusterware","tag-oracle-26ai","tag-rac","tag-upgrade"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue - dbi services | 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\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue\" \/>\n<meta property=\"og:description\" content=\"If you planning to upgrade your Oracle RAC Clusterware from version 19.30 or higher to release 23.26.1 please be aware that this will not work as there is issue with de-supported qosmserver and OC4J resource come in 19.30 update. To avoid problem described below, install 23.26.4 which bypass this issue during upgrade. Always upgrade to&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services | Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-13T14:50:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-13T14:50:35+00:00\" \/>\n<meta name=\"author\" content=\"Tomek Sikorski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tomek Sikorski\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 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\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/\"},\"author\":{\"name\":\"Tomek Sikorski\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/f75651c760df53ab8f0616d05d634a8c\"},\"headline\":\"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue\",\"datePublished\":\"2026-11-13T14:50:26+00:00\",\"dateModified\":\"2026-11-13T14:50:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/\"},\"wordCount\":287,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#organization\"},\"keywords\":[\"ASM\",\"Clusterware\",\"Oracle 26ai\",\"RAC\",\"Upgrade\"],\"articleSection\":[\"Database\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/\",\"name\":\"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue - dbi services | Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2026-11-13T14:50:26+00:00\",\"dateModified\":\"2026-11-13T14:50:35+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#organization\"},\"alternateName\":\"dbi Blog\",\"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\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#organization\",\"name\":\"dbi services\",\"alternateName\":\"dbi\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialised in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/f75651c760df53ab8f0616d05d634a8c\",\"name\":\"Tomek Sikorski\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2024\\\/04\\\/SIT_web.png\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2024\\\/04\\\/SIT_web.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2024\\\/04\\\/SIT_web.png\",\"caption\":\"Tomek Sikorski\"},\"description\":\"Tomek Sikorski, member of the Oracle Team Zurich, has more than 15 years of experience specializing in Oracle Platform solutions on Exadata, ExaCC, ODA, and PCA. His expertise spans full-stack Linux, network, and storage implementations, public and private cloud automation on Oracle OCI and AWS, database upgrades and migration via Oracle ZDM, high-availability Real Application Clusters, ASM storage management, and Data Guard. He also supports virtualization on PCA\\\/OLVM\\\/KVM and works with Ansible, bash, PL\\\/SQL, Git, and CI\\\/CD platforms including Jenkins. Prior to dbi services, he was Technical Architect at Accenture AG, and previously worked at Leonteq AG, UBS, IBM, and Cr\u00e9dit Agricole. His industry experience covers mainly banking and insurance.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/tomek-sikorski\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue - dbi services | 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\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/","og_locale":"en_US","og_type":"article","og_title":"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue","og_description":"If you planning to upgrade your Oracle RAC Clusterware from version 19.30 or higher to release 23.26.1 please be aware that this will not work as there is issue with de-supported qosmserver and OC4J resource come in 19.30 update. To avoid problem described below, install 23.26.4 which bypass this issue during upgrade. Always upgrade to&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/","og_site_name":"dbi services | Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2026-11-13T14:50:26+00:00","article_modified_time":"2026-11-13T14:50:35+00:00","author":"Tomek Sikorski","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Tomek Sikorski","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/"},"author":{"name":"Tomek Sikorski","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/f75651c760df53ab8f0616d05d634a8c"},"headline":"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue","datePublished":"2026-11-13T14:50:26+00:00","dateModified":"2026-11-13T14:50:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/"},"wordCount":287,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/blog\/#organization"},"keywords":["ASM","Clusterware","Oracle 26ai","RAC","Upgrade"],"articleSection":["Database","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/","url":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/","name":"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue - dbi services | Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-11-13T14:50:26+00:00","dateModified":"2026-11-13T14:50:35+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oracle-rac-clusterware-upgrade-23-26-1-after-19-30-oc4j-issue\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Oracle RAC Clusterware upgrade 23.26.1 after 19.30 OC4J issue"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/blog\/#organization"},"alternateName":"dbi Blog","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":"Organization","@id":"https:\/\/www.dbi-services.com\/blog\/#organization","name":"dbi services","alternateName":"dbi","url":"https:\/\/www.dbi-services.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialised in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/f75651c760df53ab8f0616d05d634a8c","name":"Tomek Sikorski","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2024\/04\/SIT_web.png","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2024\/04\/SIT_web.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2024\/04\/SIT_web.png","caption":"Tomek Sikorski"},"description":"Tomek Sikorski, member of the Oracle Team Zurich, has more than 15 years of experience specializing in Oracle Platform solutions on Exadata, ExaCC, ODA, and PCA. His expertise spans full-stack Linux, network, and storage implementations, public and private cloud automation on Oracle OCI and AWS, database upgrades and migration via Oracle ZDM, high-availability Real Application Clusters, ASM storage management, and Data Guard. He also supports virtualization on PCA\/OLVM\/KVM and works with Ansible, bash, PL\/SQL, Git, and CI\/CD platforms including Jenkins. Prior to dbi services, he was Technical Architect at Accenture AG, and previously worked at Leonteq AG, UBS, IBM, and Cr\u00e9dit Agricole. His industry experience covers mainly banking and insurance.","url":"https:\/\/www.dbi-services.com\/blog\/author\/tomek-sikorski\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/48497","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\/148"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=48497"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/48497\/revisions"}],"predecessor-version":[{"id":48523,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/48497\/revisions\/48523"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=48497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=48497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=48497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}