{"id":43282,"date":"2026-03-04T11:09:14","date_gmt":"2026-03-04T10:09:14","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=43282"},"modified":"2026-03-04T11:09:17","modified_gmt":"2026-03-04T10:09:17","slug":"grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/","title":{"rendered":"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward"},"content":{"rendered":"\n<p>This is third part of 26ai migration blog. We will upgrade here 2 node Clusterware with ASM in 19c. We will use newest 23.26.1 GoldImages from oracle support. This tutorial showing main steps how to perform upgrade, its not procedure to upgrade your production environment, please checkout official documentation from oracle and do proper planning and prechecks before you do it.<\/p>\n\n\n\n<p><a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/oracle-database\/26\/cwlin\/oracle-grid-infrastructure-installation-checklist.html\">https:\/\/docs.oracle.com\/en\/database\/oracle\/oracle-database\/26\/cwlin\/oracle-grid-infrastructure-installation-checklist.html<\/a><\/p>\n\n\n\n<p>This is third from 3 Articles:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.dbi-services.com\/blog\/database-upgrade-to-ai-database-26ai-23-26-1-for-linux-x86-64-upgrade-from-19c-in-3-steps-using-gold-images\/\" id=\"42890\">Database upgrade to AI Database 26ai (23.26.1) for Linux x86-64 upgrade from 19C in 3 steps using gold images.<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.dbi-services.com\/blog\/oracle-grid-infrastructure-26ai-asm-upgrade-from-19c-one-node\/\">Oracle GridInfrastructure 26ai\/ ASM upgrade from 19c one node.<\/a><\/li>\n\n\n\n<li><strong>Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward<\/strong><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-step-1-downloading-software-and-preparation\">Step 1. Downloading software and preparation<\/h2>\n\n\n\n<p>Download Base Gold image from Oracle support software from latest Oracle AI Database 26ai Grid Infrastructure (23.26.1) for Linux x86-64 (we upgrading on Oracle LInux 9)<\/p>\n\n\n\n<p><a href=\"https:\/\/www.oracle.com\/database\/technologies\/oracle26ai-linux-downloads.html\">https:\/\/www.oracle.com\/database\/technologies\/oracle26ai-linux-downloads.html<\/a><\/p>\n\n\n\n<p>or<\/p>\n\n\n\n<p>If you have access to new support web site, use this document to get always newest updated version (Recommended), there is new update every 3 months. <\/p>\n\n\n\n<p><a href=\"https:\/\/support.oracle.com\/ic\/builder\/rt\/customer_portal\/live\/webApps\/customer-portal\/?kmExternalId=KB153394\">Oracle AI Database 26ai Proactive Patch Information KB153394<\/a><\/p>\n\n\n\n<p>Download latest GoldImage release update, at the time writing this newest ones was Jan 2026. <a href=\"https:\/\/support.oracle.com\/support\/?patchId=38753741\" target=\"_blank\" rel=\"noreferrer noopener\">38753741<\/a><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"186\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1024x186.png\" alt=\"\" class=\"wp-image-42916\" srcset=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1024x186.png 1024w, https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-300x54.png 300w, https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-768x139.png 768w, https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1536x279.png 1536w, https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-2048x372.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Meanwhile downloading you can read documentation \ud83d\ude42 <\/p>\n\n\n\n<p><a href=\"https:\/\/updates.oracle.com\/Orion\/Services\/download?type=readme&amp;aru=28449739\">https:\/\/updates.oracle.com\/Orion\/Services\/download?type=readme&amp;aru=28449739<\/a><\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<ul class=\"wp-block-list\">\n<li>In this tutorial we will not use Oracle Fleet Patching and Provisioning (Oracle FPP)<\/li>\n\n\n\n<li>we will use traditional gridSetup.sh in silent mode and root scripts to switch has\/crs to new home.<\/li>\n<\/ul>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-step-2-update-your-linux-and-install-oracle-preinstall-rpm\">Step 2. Update your linux and install oracle preinstall rpm. <\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>yum update\n\nyum install oracle-ai-database-preinstall-26ai\n\nreboot <\/code><\/pre>\n\n\n\n<p>In my case LINUX was not updates since a while so i have more then 100 rpms to update including kernel so i also rebooted my linux box.<\/p>\n\n\n\n<p>Install&nbsp;&nbsp;&nbsp; 7 Packages<br><br>Upgrade&nbsp; 102 Packages<br><br>Remove&nbsp;&nbsp;&nbsp;&nbsp; 7 Packages<br><br>Total download size: 1.3 G<\/p>\n\n\n\n<p><strong>oracle-ai-database-preinstall-26ai<\/strong> this rpm is installing all dependencies need for oracle 26ai , in case you installed earlier versions there is not much to do , but better have it installed, as future updates may add some dependencies, if you not using Oracle Linux , please check documentation which exactly rpms are needed. <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unpack our downloaded database gold image software.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir -p \/u03\/app\/grid26\/\nunzip \/u02\/inst\/26ai\/p38753741_230000_Linux-x86-64.zip -d \/u03\/app\/grid26\/\ncd \/u03\/app\/grid26\/\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-step-3-setup-new-home-and-prechecks\">Step 3. Setup  new home and prechecks<\/h2>\n\n\n\n<div class=\"wp-block-group is-vertical is-layout-flex wp-container-core-group-is-layout-8cf370e7 wp-block-group-is-layout-flex\">\n<pre class=\"wp-block-code\"><code>oracle@racnode1 grid26]$ .\/gridSetup.sh -silent -setupHome -OSDBA oinstall -OSASM dba -ORACLE_BASE \/u01\/app\/oracle -executePrereqs \nLaunching Oracle Grid Infrastructure Setup Wizard...\n\n*********************************************\nSwap Size: This is a prerequisite condition to test whether sufficient total swap space is available on the system.\nSeverity: IGNORABLE\nOverall status: VERIFICATION_FAILED\nError message: PRVF-7573 : Sufficient swap size is not available on node \"racnode1\" &#091;Required = 8.4861GB (8898344.0KB) ; Found = 2GB (2097148.0KB)]\nCause: The swap size found does not meet the minimum requirement.\nAction: Increase swap size to at least meet the minimum swap space requirement.\n-----------------------------------------------\n&#091;WARNING] &#091;INS-13014] Target environment does not meet some optional requirements.\n CAUSE: Some of the optional prerequisites are not met. See logs for details. \/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-20_06-12-50PM\/gridSetupActions2026-02-20_06-12-50PM.log.\n ACTION: Identify the list of failed prerequisite checks from the log: \/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-20_06-12-50PM\/gridSetupActions2026-02-20_06-12-50PM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.\n<\/code><\/pre>\n<\/div>\n\n\n\n<p>Prechecks for &#8216;setuphome&#8217; showing only issue with swap space(this we ignoring on our test machine)<\/p>\n\n\n\n<p>All other prechecks we will do before Grid upgrade and run cluracvry from new grid home already, so we first only install grid software on both nodes.<\/p>\n\n\n\n<p>In this process we will do rolling upgrades on each node, so your database stay online always at least on one node.<\/p>\n\n\n\n<p><strong>Make sure your databases\/pdbs services and failover options are properly configured and applications using then.<\/strong><\/p>\n\n\n\n<p>Now lets setup new grid home<\/p>\n\n\n\n<p>\/gridSetup.sh -silent -setupHome -OSDBA oinstall -OSASM dba -ORACLE_BASE \/u01\/app\/oracle<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\n&#091;oracle@racnode1 grid26]$ .\/gridSetup.sh -silent -setupHome -OSDBA oinstall -OSASM dba -ORACLE_BASE \/u01\/app\/oracle \nLaunching Oracle Grid Infrastructure Setup Wizard...\n\n*********************************************\nSwap Size: This is a prerequisite condition to test whether sufficient total swap space is available on the system.\nSeverity: IGNORABLE\nOverall status: VERIFICATION_FAILED\nError message: PRVF-7573 : Sufficient swap size is not available on node \"racnode1\" &#091;Required = 8.4861GB (8898344.0KB) ; Found = 2GB (2097148.0KB)]\nCause:  The swap size found does not meet the minimum requirement.\nAction:  Increase swap size to at least meet the minimum swap space requirement.\n-----------------------------------------------\n\nThe response file for this session can be found at:\n \/u03\/app\/grid26\/install\/response\/grid_2026-02-20_06-14-20PM.rsp\n\nYou can find the log of this install session at:\n \/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-20_06-14-20PM\/gridSetupActions2026-02-20_06-14-20PM.log\n\nAs a root user, run the following script(s):\n\t1. \/u03\/app\/grid26\/root.sh\n\nRun \/u03\/app\/grid26\/root.sh on the following nodes:\n&#091;racnode1]\n\n\nSuccessfully Setup Software.\n<\/code><\/pre>\n\n\n\n<p>now as root user execute \/u03\/app\/grid26\/root.sh<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;root@racnode1 ~]# \/u03\/app\/grid26\/root.sh\nCheck \/u03\/app\/grid26\/install\/root_racnode1_2026-02-20_18-23-51-043070049.log for the output of root script\n&#091;root@racnode1 ~]# cat \/u03\/app\/grid26\/install\/root_racnode1_2026-02-20_18-23-51-043070049.log\nPerforming root user operation.\n\nThe following environment variables are set as:\n    ORACLE_OWNER= oracle\n    ORACLE_HOME=  \/u03\/app\/grid26\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\nFinished running generic part of root script.\nNow product-specific root actions will be performed.\n\nTo configure Grid Infrastructure for a Cluster or Grid Infrastructure for a Stand-Alone Server execute the following command as oracle user:\n\/u03\/app\/grid26\/gridSetup.sh\nThis command launches the Grid Infrastructure Setup Wizard. The wizard also supports silent operation, and the parameters can be passed through the response file that is available in the installation media.\n<\/code><\/pre>\n\n\n\n<p><strong>do the same steps on rac node 2<\/strong><\/p>\n\n\n\n<p>Now we have grid 26ai  software setup on both nodes, we can start prechecks before we perform upgrade. we will do 2 separate prechecks<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/u03\/app\/grid26\/bin\/cluvfyrac.sh stage -pre crsinst -n racnode1\nand\n\/u03\/app\/grid26\/gridSetup.sh -silent -upgrade -executePrereqs<\/code><\/pre>\n\n\n\n<p>outputs of this prechecks are quite long lists You should change most checks marked as &#8216;PASSED&#8217; if they are &#8216;FAILED&#8217; you should look into it and try to fix(not all FAILS means  that you unable to do upgrade), in my case I would ignore SWAP space size (as this is test VM swap space size can be small)<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;oracle@racnode1 grid26]$ \/u03\/app\/grid26\/bin\/cluvfyrac.sh stage -pre crsinst -n racnode1\nThis software is \"401\" days old. It is a best practice to update the CRS home by downloading and applying the latest release update. Refer to MOS note 756671.1 for more details.\n\nPerforming following verification checks ...\n\n  Physical Memory ...PASSED\n  Available Physical Memory ...PASSED\n  Swap Size ...FAILED (PRVF-7573)\n  Free Space: racnode1:\/usr,racnode1:\/var,racnode1:\/etc,racnode1:\/sbin,racnode1:\/tmp ...PASSED\n  Free Space: racnode1:\/u01\/grid ...PASSED\n  User Existence: oracle ...\n    Users With Same UID: 54321 ...PASSED\n  User Existence: oracle ...PASSED\n...\n...<\/code><\/pre>\n\n\n\n<p>In my case there were 2 main fails which make whole upgrade impossible if not fix earlier, diskgroups RDBMS compatibility parameter and ASM disks group ownership:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>*********************************************\nDisk group RDBMS compatibility setting: Check for disk group RDBMS compatibility setting\nSeverity: FATAL\nOverall status: VERIFICATION_FAILED\nError message: PRVE-3180 : RDBMS compatibility for ASM disk group \"DATA\" is set to \"10.1.0.0.0\", which is less than the minimum supported value \"19.0.0.0.0\".\nCause:  A query showed that the ASM disk group attribute \"compatible.rdbms\"\n         for the indicated disk group was set to a value less than the\n         minimum supported value.\nAction:  Ensure that the RDBMS compatibility of the indicated disk group is\n         set to a value greater than or equal to the indicated minimum\n         supported value by running the command ''asmcmd setattr -G\n         &lt;diskgroup&gt; compatible.rdbms &lt;value&gt;''.\n-----------------------------------------------\nError message: PRVE-3180 : RDBMS compatibility for ASM disk group \"DATA\" is set to \"10.1.0.0.0\", which is less than the minimum supported value \"19.0.0.0.0\".\nCause:  A query showed that the ASM disk group attribute \"compatible.rdbms\"\n         for the indicated disk group was set to a value less than the\n         minimum supported value.\nAction:  Ensure that the RDBMS compatibility of the indicated disk group is\n         set to a value greater than or equal to the indicated minimum\n         supported value by running the command ''asmcmd setattr -G\n         &lt;diskgroup&gt; compatible.rdbms &lt;value&gt;''.\n*********************************************\nDevice Checks for ASM: This is a prerequisite check to verify that the specified devices meet the requirements for ASM.\nSeverity: FATAL\nOverall status: VERIFICATION_FAILED\n-----------------------------------------------\n-----------------------------------------------\nError message: PRVF-9992 : Group of device \"\/dev\/asm-disk4\" did not match the expected group. &#091;Expected = \"oinstall\"; Found = \"dba\"] on nodes: &#091;racnode2, racnode1]\nCause:  Group of the device listed was different than required group.\nAction:  Change the group of the device listed or specify a different device.\nError message: PRVF-9992 : Group of device \"\/dev\/asm-disk5\" did not match the expected group. &#091;Expected = \"oinstall\"; Found = \"dba\"] on nodes: &#091;racnode2, racnode1]\nCause:  Group of the device listed was different than required group.\nAction:  Change the group of the device listed or specify a different device.\nError message: PRVF-9992 : Group of device \"\/dev\/asm-disk1\" did not match the expected group. &#091;Expected = \"oinstall\"; Found = \"dba\"] on nodes: &#091;racnode2, racnode1]\nCause:  Group of the device listed was different than required group.\nAction:  Change the group of the device listed or specify a different device.\nError message: PRVF-9992 : Group of device \"\/dev\/asm-disk2\" did not match the expected group. &#091;Expected = \"oinstall\"; Found = \"dba\"] on nodes: &#091;racnode2, racnode1]\nCause:  Group of the device listed was different than required group.\nAction:  Change the group of the device listed or specify a different device.\n*********************************************\nAccess Control List check: This check verifies that the ownership and permissions are correct and consistent for the devices across nodes.\nSeverity: CRITICAL\nOverall status: VERIFICATION_FAILED\n-----------------------------------------------\n-----------------------------------------------\n\n<\/code><\/pre>\n\n\n\n<p>quick fix:<\/p>\n\n\n\n<p>1. Diskgroups RDBMS compatibility parameter set to minimum 19<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;oracle@racnode1 ~]$ <strong>asmcmd setattr -G DATA compatible.rdbms 19.0.0.0.0<\/strong>\n<\/code><\/pre>\n\n\n\n<p>2. ASM disks: group change for oinstall<\/p>\n\n\n\n<p>my asm disks are udev disks, so group ownership i can change in \/etc\/udev\/rules.d\/99-oracle-asmdevices.rules:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>vi \/etc\/udev\/rules.d\/99-oracle-asmdevices.rules\n\nKERNEL==\"vdc1\", SYMLINK+=\"asm-disk1\", OWNER=\"oracle\", GROUP=\"<strong>oinstall<\/strong>\", MODE=\"0660\"\nKERNEL==\"vdd1\", SYMLINK+=\"asm-disk2\", OWNER=\"oracle\", GROUP=\"<strong>oinstall<\/strong>\", MODE=\"0660\"\n...\n\n<\/code><\/pre>\n\n\n\n<p>and we reboot the server. (please stop your database before using srvctl stop database instance on the node you work)<\/p>\n\n\n\n<p>after server startup up , start instance and repeat step 2 also on RAC node 2, now we good to go with main upgrade:<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-step-4-upgrade\">STEP 4. UPGRADE:<\/h2>\n\n\n\n<p>execute on node 1 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;oracle@racnode1 grid26]$ \/u03\/app\/grid26\/gridSetup.sh -silent -ignorePrereqFailure -upgrade\nLaunching Oracle Grid Infrastructure Setup Wizard...\n\n&#091;WARNING] &#091;INS-13013] Target environment does not meet some mandatory requirements.\n   CAUSE: Some of the mandatory prerequisites are not met. See logs for details. \/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-24_04-23-48PM\/gridSetupActions2026-02-24_04-23-48PM.log.\n   ACTION: Identify the list of failed prerequisite checks from the log: \/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-24_04-23-48PM\/gridSetupActions2026-02-24_04-23-48PM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.\nThe response file for this session can be found at:\n \/u03\/app\/grid26\/install\/response\/grid_2026-02-24_04-23-48PM.rsp\n\n\nAs a root user, run the following script(s):\n\t1. \/u03\/app\/grid26\/rootupgrade.sh\n\nRun \/u03\/app\/grid26\/rootupgrade.sh on the following nodes:\n&#091;racnode1, racnode2]\n\nRun the script on the node racnode1 first. After successful completion, you can run the script in parallel on all the other nodes, except a node you designate as the last node. When all the nodes except the last node are done successfully, run the script on the last node.\n\nSuccessfully Setup Software with warning(s).\nRun the 'gridSetup.sh -executeConfigTools' command to complete the configuration.\n<\/code><\/pre>\n\n\n\n<p>I use ignorePrereqFailure parameter as I would like to oracle ignore issue with swap space and some permissions checks.<\/p>\n\n\n\n<p>now we execute as root: u03\/app\/grid26\/rootupgrade.sh<\/p>\n\n\n\n<p>This is main upgrade process which will switch all stack Grid processes to new home and start also ASM in 26ai version.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\n&#091;root@racnode1 ~]# \/u03\/app\/grid26\/rootupgrade.sh\nCheck \/u03\/app\/grid26\/install\/root_racnode1_2026-02-24_16-32-24-369106275.log for the output of root script\n\n\n&#091;root@racnode1 ~]# cat \/u03\/app\/grid26\/install\/root_racnode1_2026-02-24_16-32-24-369106275.log\nPerforming root user operation.\n\nThe following environment variables are set as:\n    ORACLE_OWNER= oracle\n    ORACLE_HOME=  \/u03\/app\/grid26\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\nFinished running generic part of root script.\nNow product-specific root actions will be performed.\nRAC option is not linked in\nRelinking oracle with rac_on option\nExecuting command '\/u03\/app\/grid26\/perl\/bin\/perl -I\/u03\/app\/grid26\/perl\/lib -I\/u03\/app\/grid26\/crs\/install \/u03\/app\/grid26\/crs\/install\/rootcrs.pl  -upgrade'\nUsing configuration parameter file: \/u03\/app\/grid26\/crs\/install\/crsconfig_params\nThe log of current session can be found at:\n  \/u01\/app\/oracle\/crsdata\/racnode1\/crsconfig\/crsupgrade_racnode1_2026-02-24_04-32-46PM.log\n2026\/02\/24 16:32:55 CLSRSC-595: Executing upgrade step 1 of 16: 'UpgradeTFA'.\n2026\/02\/24 16:32:55 CLSRSC-4015: Performing install or upgrade action for Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:32:55 CLSRSC-4012: Shutting down Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:33:09 CLSRSC-4013: Successfully shut down Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:33:09 CLSRSC-595: Executing upgrade step 2 of 16: 'ValidateEnv'.\n2026\/02\/24 16:33:09 CLSRSC-363: User ignored prerequisites during installation\n2026\/02\/24 16:33:10 CLSRSC-595: Executing upgrade step 3 of 16: 'GetOldConfig'.\n2026\/02\/24 16:33:10 CLSRSC-692: Checking whether CRS entities are ready for upgrade. This operation may take a few minutes.\n2026\/02\/24 16:34:23 CLSRSC-4003: Successfully patched Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:34:50 CLSRSC-693: CRS entities validation completed successfully.\n2026\/02\/24 16:34:50 CLSRSC-464: Starting retrieval of the cluster configuration data\nNAME=ora.qosmserver\nTYPE=ora.qosmserver.type\nTARGET=ONLINE\nSTATE=ONLINE on racnode2\n\nCRS-4672: Successfully backed up the Voting File for Cluster Synchronization Service.\n2026\/02\/24 16:34:59 CLSRSC-515: Starting OCR manual backup.\n2026\/02\/24 16:35:03 CLSRSC-516: OCR manual backup successful.\n2026\/02\/24 16:35:07 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.\n2026\/02\/24 16:35:07 CLSRSC-595: Executing upgrade step 4 of 16: 'UpgPrechecks'.\n2026\/02\/24 16:35:14 CLSRSC-595: Executing upgrade step 5 of 16: 'SetupOSD'.\n2026\/02\/24 16:35:14 CLSRSC-595: Executing upgrade step 6 of 16: 'PreUpgrade'.\n2026\/02\/24 16:35:17 CLSRSC-486:\n At this stage of upgrade, the OCR has changed.\n Any attempt to downgrade the cluster after this point will require a complete cluster outage to restore the OCR.\n2026\/02\/24 16:35:17 CLSRSC-541:\n To downgrade the cluster:\n 1. All nodes that have been upgraded must be downgraded.\n2026\/02\/24 16:35:17 CLSRSC-542:\n 2. Before downgrading the last node, the Grid Infrastructure stack on all other cluster nodes must be down.\n2026\/02\/24 16:35:18 CLSRSC-468: Setting Oracle Clusterware and ASM to rolling migration mode\n2026\/02\/24 16:35:18 CLSRSC-482: Running command: '\/u01\/grid\/bin\/crsctl start rollingupgrade 23.0.0.0.0'\nCRS-1131: The cluster was successfully set to rolling upgrade mode.\n2026\/02\/24 16:35:22 CLSRSC-482: Running command: '\/u03\/app\/grid26\/bin\/asmca -silent -upgradeNodeASM -nonRolling false -oldCRSHome \/u01\/grid -oldCRSVersion 19.0.0.0.0 -firstNode true -startRolling false '\n2026\/02\/24 16:35:24 CLSRSC-469: Successfully set Oracle Clusterware and ASM to rolling migration mode\n2026\/02\/24 16:35:25 CLSRSC-466: Starting shutdown of the current Oracle Grid Infrastructure stack\n2026\/02\/24 16:36:16 CLSRSC-467: Shutdown of the current Oracle Grid Infrastructure stack has successfully completed.\n2026\/02\/24 16:36:18 CLSRSC-595: Executing upgrade step 7 of 16: 'CheckCRSConfig'.\n2026\/02\/24 16:36:18 CLSRSC-595: Executing upgrade step 8 of 16: 'UpgradeOLR'.\n2026\/02\/24 16:36:22 CLSRSC-595: Executing upgrade step 9 of 16: 'ConfigCHMOS'.\n2026\/02\/24 16:36:22 CLSRSC-595: Executing upgrade step 10 of 16: 'createOHASD'.\n2026\/02\/24 16:36:22 CLSRSC-595: Executing upgrade step 11 of 16: 'ConfigOHASD'.\n2026\/02\/24 16:36:22 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'\n2026\/02\/24 16:36:31 CLSRSC-595: Executing upgrade step 12 of 16: 'InstallACFS'.\n2026\/02\/24 16:36:48 CLSRSC-595: Executing upgrade step 13 of 16: 'RemoveKA'.\n2026\/02\/24 16:36:48 CLSRSC-595: Executing upgrade step 14 of 16: 'UpgradeCluster'.\n2026\/02\/24 16:37:31 CLSRSC-343: Successfully started Oracle Clusterware stack\nclscfg: EXISTING configuration version 19 detected.\nSuccessfully taken the backup of node specific configuration in OCR.\nSuccessfully accumulated necessary OCR keys.\nCreating OCR keys for user 'root', privgrp 'root'..\nOperation successful.\n2026\/02\/24 16:37:41 CLSRSC-595: Executing upgrade step 15 of 16: 'UpgradeNode'.\n2026\/02\/24 16:37:42 CLSRSC-474: Initiating upgrade of resource types\n2026\/02\/24 16:37:47 CLSRSC-475: Upgrade of resource types successfully initiated.\n2026\/02\/24 16:37:48 CLSRSC-595: Executing upgrade step 16 of 16: 'PostUpgrade'.\n2026\/02\/24 16:37:54 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded\n\n<\/code><\/pre>\n\n\n\n<p><br>we can check that our crs is running already from new home on node1<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;root@racnode1 ~]# systemctl status oracle-ohasd.service\n\u25cf oracle-ohasd.service - Oracle High Availability Services\n     Loaded: loaded (\/etc\/systemd\/system\/oracle-ohasd.service; enabled; preset: disabled)\n    Drop-In: \/etc\/systemd\/system\/oracle-ohasd.service.d\n             \u2514\u250000_oracle-ohasd.conf\n     Active: active (running) since Tue 2026-02-24 16:36:24 CET; 8min ago\n   Main PID: 86773 (init.ohasd)\n      Tasks: 651 (limit: 52416)\n     Memory: 5.5G (peak: 6.4G)\n        CPU: 2min 53.156s\n     CGroup: \/oracle.slice\/oracle-ohasd.service\n             \u251c\u2500 86773 \/bin\/sh \/etc\/oracle\/scls_scr\/racnode1\/root\/init.ohasd run \"&gt;\/dev\/null\" \"2&gt;&amp;1\" \"&lt;\/dev\/null\"\n             \u251c\u2500 91877 \/u03\/app\/grid26\/bin\/ohasd.bin reboot _ORA_BLOCKING_STACK_LOCALE=AMERICAN_AMERICA.AL32UTF8\n             \u251c\u2500 92028 \/u03\/app\/grid26\/bin\/orarootagent.bin\n             \u251c\u2500 92166 \/u03\/app\/grid26\/bin\/oraagent.bin\n             \u251c\u2500 92188 \/u03\/app\/grid26\/bin\/mdnsd.bin\n             \u251c\u2500 92190 \/u03\/app\/grid26\/bin\/evmd.bin\n             \u251c\u2500 92236 \/u03\/app\/grid26\/bin\/gpnpd.bin\n             \u251c\u2500 92288 \/u03\/app\/grid26\/bin\/gipcd.bin\n             \u251c\u2500 92308 \/u03\/app\/grid26\/bin\/evmlogger.bin\n             \u251c\u2500 92357 \/u03\/app\/grid26\/bin\/cssdmonitor\n             \u251c\u2500 92360 \/u03\/app\/grid26\/bin\/osysmond.bin\n             \u251c\u2500 92409 \/u03\/app\/grid26\/python\/bin\/python \/u03\/app\/grid26\/pylib\/chmdiag.zip start -f \"-n racnode1\"\n             \u251c\u2500 92415 \/u03\/app\/grid26\/bin\/cssdagent\n             \u251c\u2500 92450 \/u03\/app\/grid26\/bin\/onmd.bin\n             \u251c\u2500 92452 \/u03\/app\/grid26\/bin\/ocssd.bin\n             \u251c\u2500 92505 \/u03\/app\/grid26\/bin\/crfelsnr -n racnode1\n             \u251c\u2500 92569 \/u03\/app\/grid26\/bin\/crsd.bin reboot\n             \u251c\u2500 92725 \/u03\/app\/grid26\/bin\/orarootagent.bin\n\n\n\n<\/code><\/pre>\n\n\n\n<p>normally you do whole upgrade in ONLINE mode rolling forward to each node, keep you database instance running, check if your db is properly up and running on upgraded node, then continue to the next one.<br>now we can continue on second node, exactly execute the same script:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;root@racnode2 ~]# \/u03\/app\/grid26\/rootupgrade.sh\nCheck \/u03\/app\/grid26\/install\/root_racnode2_2026-02-24_16-47-22-723209560.log for the output of root script\n\n&#091;root@racnode2 ~]# cat \/u03\/app\/grid26\/install\/root_racnode2_2026-02-24_16-47-22-723209560.log\nPerforming root user operation.\n\nThe following environment variables are set as:\n    ORACLE_OWNER= oracle\n    ORACLE_HOME=  \/u03\/app\/grid26\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\nFinished running generic part of root script.\nNow product-specific root actions will be performed.\nRAC option is not linked in\nRelinking oracle with rac_on option\nExecuting command '\/u03\/app\/grid26\/perl\/bin\/perl -I\/u03\/app\/grid26\/perl\/lib -I\/u03\/app\/grid26\/crs\/install \/u03\/app\/grid26\/crs\/install\/rootcrs.pl  -upgrade'\nUsing configuration parameter file: \/u03\/app\/grid26\/crs\/install\/crsconfig_params\nThe log of current session can be found at:\n  \/u01\/app\/oracle\/crsdata\/racnode2\/crsconfig\/crsupgrade_racnode2_2026-02-24_04-47-45PM.log\n2026\/02\/24 16:47:51 CLSRSC-595: Executing upgrade step 1 of 16: 'UpgradeTFA'.\n2026\/02\/24 16:47:51 CLSRSC-4015: Performing install or upgrade action for Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:47:51 CLSRSC-4012: Shutting down Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:48:05 CLSRSC-4013: Successfully shut down Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:48:05 CLSRSC-595: Executing upgrade step 2 of 16: 'ValidateEnv'.\n2026\/02\/24 16:48:05 CLSRSC-363: User ignored prerequisites during installation\n2026\/02\/24 16:48:06 CLSRSC-595: Executing upgrade step 3 of 16: 'GetOldConfig'.\n2026\/02\/24 16:48:06 CLSRSC-464: Starting retrieval of the cluster configuration data\n2026\/02\/24 16:48:10 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.\n2026\/02\/24 16:48:10 CLSRSC-595: Executing upgrade step 4 of 16: 'UpgPrechecks'.\n2026\/02\/24 16:48:11 CLSRSC-595: Executing upgrade step 5 of 16: 'SetupOSD'.\n2026\/02\/24 16:48:11 CLSRSC-595: Executing upgrade step 6 of 16: 'PreUpgrade'.\n2026\/02\/24 16:48:14 CLSRSC-466: Starting shutdown of the current Oracle Grid Infrastructure stack\n2026\/02\/24 16:48:55 CLSRSC-467: Shutdown of the current Oracle Grid Infrastructure stack has successfully completed.\n2026\/02\/24 16:48:55 CLSRSC-595: Executing upgrade step 7 of 16: 'CheckCRSConfig'.\n2026\/02\/24 16:48:56 CLSRSC-595: Executing upgrade step 8 of 16: 'UpgradeOLR'.\n2026\/02\/24 16:49:04 CLSRSC-595: Executing upgrade step 9 of 16: 'ConfigCHMOS'.\n2026\/02\/24 16:49:04 CLSRSC-595: Executing upgrade step 10 of 16: 'createOHASD'.\n2026\/02\/24 16:49:05 CLSRSC-595: Executing upgrade step 11 of 16: 'ConfigOHASD'.\n2026\/02\/24 16:49:05 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'\n2026\/02\/24 16:49:18 CLSRSC-595: Executing upgrade step 12 of 16: 'InstallACFS'.\n2026\/02\/24 16:49:46 CLSRSC-595: Executing upgrade step 13 of 16: 'RemoveKA'.\n2026\/02\/24 16:49:46 CLSRSC-595: Executing upgrade step 14 of 16: 'UpgradeCluster'.\n2026\/02\/24 16:49:59 CLSRSC-4003: Successfully patched Oracle Autonomous Health Framework (AHF).\n2026\/02\/24 16:50:34 CLSRSC-343: Successfully started Oracle Clusterware stack\nclscfg: EXISTING configuration version 23 detected.\nSuccessfully taken the backup of node specific configuration in OCR.\nSuccessfully accumulated necessary OCR keys.\nCreating OCR keys for user 'root', privgrp 'root'..\nOperation successful.\n2026\/02\/24 16:50:42 CLSRSC-595: Executing upgrade step 15 of 16: 'UpgradeNode'.\nStart upgrade invoked..\n2026\/02\/24 16:50:45 CLSRSC-478: Setting Oracle Clusterware active version on the last node to be upgraded\n2026\/02\/24 16:50:45 CLSRSC-482: Running command: '\/u03\/app\/grid26\/bin\/crsctl set crs activeversion'\nStarted to upgrade the active version of Oracle Clusterware. This operation may take a few minutes.\nStarted to upgrade CSS.\nStarted to upgrade Oracle ASM.\nStarted to upgrade CRS.\nCRS was successfully upgraded.\nStarted to upgrade Oracle ACFS.\nOracle ACFS was successfully upgraded.\nSuccessfully upgraded the active version of Oracle Clusterware.\nOracle Clusterware active version was successfully set to 23.0.0.0.0.\n2026\/02\/24 16:51:55 CLSRSC-479: Successfully set Oracle Clusterware active version\n2026\/02\/24 16:51:58 CLSRSC-476: Finishing upgrade of resource types\n2026\/02\/24 16:52:01 CLSRSC-477: Successfully completed upgrade of resource types\n2026\/02\/24 16:52:19 CLSRSC-595: Executing upgrade step 16 of 16: 'PostUpgrade'.\nSuccessfully updated XAG resources.\n2026\/02\/24 16:52:28 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded\n\n\n<\/code><\/pre>\n\n\n\n<p>DONE, our 2 node Grid Cluster has been upgraded on both nodes, at this stage both nodes should have up and running all processes.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-step-5-verifying-our-configuration\">Step 5. Verifying our configuration<\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;oracle@racnode1 grid26]$ .\/gridSetup.sh -executeConfigTools\nERROR: Unable to verify the graphical display setup. This application requires X display. Make sure that xdpyinfo exist under PATH variable.\nLaunching Oracle Grid Infrastructure Setup Wizard...\n\nYou can find the logs of this session at:\n\/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-24_05-10-20PM\n\n&#091; Start ] CVU - 2026-02-24 17:10:35.22\nCommand: \/bin\/sh -c \/u03\/app\/grid26\/bin\/cluvfy  stage -post crsinst -collect cluster -gi_upgrade -n all\n\nInitializing ...\n\nPerforming following verification checks ...\n\n  Node Connectivity ...\n    Hosts File ...PASSED\n    Check that maximum (MTU) size packet goes through subnet ...PASSED\n    subnet mask consistency for subnet \"192.168.100.0\" ...PASSED\n    subnet mask consistency for subnet \"192.168.101.0\" ...PASSED\n  Node Connectivity ...PASSED\n  Multicast or broadcast check ...\n    Checking subnet \"192.168.101.0\" for multicast communication with multicast\n    group \"224.0.0.251\"\n\n    Subnet        Network Type              Multicast Enabled\n    ------------  ------------------------  ------------------------\n    192.168.101.0  PRIVATE                   TRUE\n  Multicast or broadcast check ...PASSED\n  Time zone consistency ...PASSED\n  Path existence, ownership, permissions and attributes ...\n    Path \"\/var\" ...PASSED\n    Path \"\/var\/lib\/oracle\" ...PASSED\n    Path \"\/u01\/app\/oraInventory\/ContentsXML\/inventory.xml\" ...PASSED\n    Path \"\/dev\/asm\" ...PASSED\n    Path \"\/dev\/shm\" ...PASSED\n    Path \"\/etc\/init.d\/ohasd\" ...PASSED\n    Path \"\/etc\/init.d\/init.ohasd\" ...PASSED\n    Path \"\/etc\/init.d\/init.tfa\" ...PASSED\n    Path \"\/etc\/oracle\/maps\" ...PASSED\n    Path \"\/etc\/oraInst.loc\" ...PASSED\n    Path \"\/etc\/tmpfiles.d\/oracleGI.conf\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/incident\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/metadata\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/incpkg\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/alert\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/metadata_pv\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/stage\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/sweep\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/lck\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/log\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/cdump\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/trace\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/metadata_dgif\" ...PASSED\n    Path \"\/u03\/app\/grid26\/gpnp\/wallets\/peer\/cwallet.sso\" ...PASSED\n    Path \"\/u03\/app\/grid26\/gpnp\/wallets\/root\/cwallet.sso\" ...PASSED\n    Path \"\/u03\/app\/grid26\/gpnp\/profiles\/peer\/profile.xml\" ...PASSED\n  Path existence, ownership, permissions and attributes ...PASSED\n  Cluster Manager Integrity ...PASSED\n  User Mask ...PASSED\n  Cluster Integrity ...PASSED\n  OCR Integrity ...PASSED\n  CRS Integrity ...\n    Clusterware Version Consistency ...PASSED\n  CRS Integrity ...PASSED\n  Node Application Existence ...PASSED\n  Single Client Access Name (SCAN) ...\n    DNS\/NIS name service 'rac-scan' ...\n      Name Service Switch Configuration File Integrity ...PASSED\n    DNS\/NIS name service 'rac-scan' ...PASSED\n  Single Client Access Name (SCAN) ...PASSED\n  OLR Integrity ...PASSED\n  Voting Disk ...PASSED\n  ASM Integrity ...PASSED\n  ASM Network ...PASSED\n  ASM disk group free space ...PASSED\n  User Not In Group \"root\": oracle ...PASSED\n  Clock Synchronization ...\n    Network Time Protocol (NTP) ...\n      Daemon 'ntpd' ...FAILED (PRVG-1024, PRVF-7590)\n      Daemon 'chronyd' ...FAILED (PRVG-1024, PRVF-7590)\n    Network Time Protocol (NTP) ...FAILED (PRVG-1024, PRVF-7590)\n  Clock Synchronization ...FAILED (PRVG-1024, PRVF-7590)\n  VIP Subnet configuration check ...PASSED\n  Oracle Net Services configuration ...PASSED\n  Network configuration consistency checks ...PASSED\n  Package: psmisc-22.6-19 ...PASSED\n  File system mount options for path GI_HOME ...PASSED\n  File system mount option hidepid for proc filesystem ...PASSED\n  Cleanup of communication socket files ...PASSED\n  Domain Sockets ...PASSED\n\nPost-check for cluster services setup was unsuccessful.\nChecks did not pass for the following nodes:\n\tracnode2,racnode1\n\n\nFailures were encountered during execution of CVU verification request \"stage -post crsinst\".\n\nClock Synchronization ...FAILED\n  Network Time Protocol (NTP) ...FAILED\n    Daemon 'ntpd' ...FAILED\n    PRVG-1024 : The NTP daemon or Service was not running on any of the cluster\n    nodes.\n\n    racnode2: PRVF-7590 : \"ntpd\" is not running on node \"racnode2\"\n    racnode2: Liveness check failed for \"ntpd\"\n\n    racnode1: PRVF-7590 : \"ntpd\" is not running on node \"racnode1\"\n    racnode1: Liveness check failed for \"ntpd\"\n\n    Daemon 'chronyd' ...FAILED\n    PRVG-1024 : The NTP daemon or Service was not running on any of the cluster\n    nodes.\n\n    racnode2: PRVF-7590 : \"chronyd\" is not running on node \"racnode2\"\n    racnode2: Liveness check failed for \"chronyd\"\n\n    racnode1: PRVF-7590 : \"chronyd\" is not running on node \"racnode1\"\n    racnode1: Liveness check failed for \"chronyd\"\n\n\nCVU operation performed:      stage -post crsinst\nDate:                         Feb 24, 2026, 5:10:35 PM\nCVU version:                  23.26.1.0.0 (010926x8664)\nClusterware version:          23.0.0.0.0\nCVU home:                     \/u03\/app\/grid26\nGrid home:                    \/u03\/app\/grid26\nUser:                         oracle\nOperating system:             Linux5.15.0-317.197.5.1.el9uek.x86_64\nConfiguration failed.\n&#091;FATAL] &#091;INS-20801] Configuration Assistant 'Oracle Cluster Verification Utility' failed.\n   ACTION: Refer to the logs or the extra details from below for additional information.\n*ADDITIONAL INFORMATION:*\n\nCommand: \/bin\/sh -c \/u03\/app\/grid26\/bin\/cluvfy stage -post crsinst -collect cluster -gi_upgrade -n all\n...\n...\n\nExit code: 1\n&#091; Exit Code ] 1\n&#091; End ] CVU - 2026-02-24 17:11:16.693\n\n&#091;WARNING] &#091;INS-43080] Some of the configuration assistants failed, were cancelled or skipped.\n   ACTION: Refer to the logs or contact Oracle Support Services.\n<\/code><\/pre>\n\n\n\n<p>UPS&#8230;  my verification failed due to ntp \/chronyd daemon missing, <\/p>\n\n\n\n<p>quick fix:<\/p>\n\n\n\n<p><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;root@racnode1 ~]# yum install chrony\nLast metadata expiration check: 3:25:13 ago on Tue 24 Feb 2026 01:50:02 PM CET.\nDependencies resolved.\n===============================================================================================================================================================================================\n Package                                  Architecture                             Version                                           Repository                                           Size\n===============================================================================================================================================================================================\nInstalling:\n chrony                                   x86_64                                   4.6.1-2.0.1.el9                                   ol9_baseos_latest                                   362 k\n\nTransaction Summary\n===============================================================================================================================================================================================\nInstall  1 Package\n\nTotal download size: 362 k\nInstalled size: 668 k\nIs this ok &#091;y\/N]: y\nDownloading Packages:\nchrony-4.6.1-2.0.1.el9.x86_64.rpm                                                                                                                              782 kB\/s | 362 kB     00:00\n-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\nTotal                                                                                                                                                          773 kB\/s | 362 kB     00:00\nRunning transaction check\nTransaction check succeeded.\nRunning transaction test\nTransaction test succeeded.\nRunning transaction\n  Preparing        :                                                                                                                                                                       1\/1\n  Running scriptlet: chrony-4.6.1-2.0.1.el9.x86_64                                                                                                                                         1\/1\n  Installing       : chrony-4.6.1-2.0.1.el9.x86_64                                                                                                                                         1\/1\n  Running scriptlet: chrony-4.6.1-2.0.1.el9.x86_64                                                                                                                                         1\/1\nCreated symlink \/etc\/systemd\/system\/multi-user.target.wants\/chronyd.service \u2192 \/usr\/lib\/systemd\/system\/chronyd.service.\n\n  Verifying        : chrony-4.6.1-2.0.1.el9.x86_64                                                                                                                                         1\/1\n\nInstalled:\n  chrony-4.6.1-2.0.1.el9.x86_64\n\nComplete!\n\n&#091;root@racnode2 ~]# systemctl start chronyd\n&#091;root@racnode2 ~]# systemctl enable chronyd\n&#091;root@racnode2 ~]# systemctl status chronyd\n\u25cf chronyd.service - NTP client\/server\n     Loaded: loaded (\/usr\/lib\/systemd\/system\/chronyd.service; enabled; preset: enabled)\n     Active: active (running) since Tue 2026-02-24 17:20:35 CET; 26s ago\n       Docs: man:chronyd(8)\n             man:chrony.conf(5)\n   Main PID: 158712 (chronyd)\n      Tasks: 1 (limit: 52408)\n     Memory: 3.1M (peak: 3.8M)\n        CPU: 22ms\n     CGroup: \/system.slice\/chronyd.service\n             \u2514\u2500158712 \/usr\/sbin\/chronyd -F 2\n\nFeb 24 17:20:35 racnode2 systemd&#091;1]: Starting NTP client\/server...\nFeb 24 17:20:35 racnode2 chronyd&#091;158712]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG)\nFeb 24 17:20:35 racnode2 chronyd&#091;158712]: Loaded 0 symmetric keys\nFeb 24 17:20:35 racnode2 chronyd&#091;158712]: Using right\/UTC timezone to obtain leap second data\nFeb 24 17:20:35 racnode2 chronyd&#091;158712]: Loaded seccomp filter (level 2)\nFeb 24 17:20:35 racnode2 systemd&#091;1]: Started NTP client\/server.\n<\/code><\/pre>\n\n\n\n<p>install also chronyd on second node, now we can run our postchecks again<\/p>\n\n\n\n<p><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#091;oracle@racnode1 grid26]$ .\/gridSetup.sh -executeConfigTools\nERROR: Unable to verify the graphical display setup. This application requires X display. Make sure that xdpyinfo exist under PATH variable.\nLaunching Oracle Grid Infrastructure Setup Wizard...\n\nYou can find the logs of this session at:\n\/u01\/app\/oraInventory\/logs\/GridSetupActions2026-02-24_05-22-12PM\n\n&#091; Start ] CVU - 2026-02-24 17:22:24.108\nCommand: \/bin\/sh -c \/u03\/app\/grid26\/bin\/cluvfy  stage -post crsinst -collect cluster -gi_upgrade -n all\n\nPerforming following verification checks ...\n\n  Node Connectivity ...\n    Hosts File ...PASSED\n    Check that maximum (MTU) size packet goes through subnet ...PASSED\n    subnet mask consistency for subnet \"192.168.100.0\" ...PASSED\n    subnet mask consistency for subnet \"192.168.101.0\" ...PASSED\n  Node Connectivity ...PASSED\n  Multicast or broadcast check ...\n    Checking subnet \"192.168.101.0\" for multicast communication with multicast\n    group \"224.0.0.251\"\n\n    Subnet        Network Type              Multicast Enabled\n    ------------  ------------------------  ------------------------\n    192.168.101.0  PRIVATE                   TRUE\n  Multicast or broadcast check ...PASSED\n  Time zone consistency ...PASSED\n  Path existence, ownership, permissions and attributes ...\n    Path \"\/var\" ...PASSED\n    Path \"\/var\/lib\/oracle\" ...PASSED\n    Path \"\/u01\/app\/oraInventory\/ContentsXML\/inventory.xml\" ...PASSED\n    Path \"\/dev\/asm\" ...PASSED\n    Path \"\/dev\/shm\" ...PASSED\n    Path \"\/etc\/init.d\/ohasd\" ...PASSED\n    Path \"\/etc\/init.d\/init.ohasd\" ...PASSED\n    Path \"\/etc\/init.d\/init.tfa\" ...PASSED\n    Path \"\/etc\/oracle\/maps\" ...PASSED\n    Path \"\/etc\/oraInst.loc\" ...PASSED\n    Path \"\/etc\/tmpfiles.d\/oracleGI.conf\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/incident\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/metadata\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/incpkg\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/alert\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/metadata_pv\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/stage\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/sweep\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/lck\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/log\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/cdump\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/trace\" ...PASSED\n    Path \"\/u01\/app\/oracle\/diag\/crs\/racnode1\/crs\/metadata_dgif\" ...PASSED\n    Path \"\/u03\/app\/grid26\/gpnp\/wallets\/peer\/cwallet.sso\" ...PASSED\n    Path \"\/u03\/app\/grid26\/gpnp\/wallets\/root\/cwallet.sso\" ...PASSED\n    Path \"\/u03\/app\/grid26\/gpnp\/profiles\/peer\/profile.xml\" ...PASSED\n  Path existence, ownership, permissions and attributes ...PASSED\n  Cluster Manager Integrity ...PASSED\n  User Mask ...PASSED\n  Cluster Integrity ...PASSED\n  OCR Integrity ...PASSED\n  CRS Integrity ...\n    Clusterware Version Consistency ...PASSED\n  CRS Integrity ...PASSED\n  Node Application Existence ...PASSED\n  Single Client Access Name (SCAN) ...\n    DNS\/NIS name service 'rac-scan' ...\n      Name Service Switch Configuration File Integrity ...PASSED\n    DNS\/NIS name service 'rac-scan' ...PASSED\n  Single Client Access Name (SCAN) ...PASSED\n  OLR Integrity ...PASSED\n  Voting Disk ...PASSED\n  ASM Integrity ...PASSED\n  ASM Network ...PASSED\n  ASM disk group free space ...PASSED\n  User Not In Group \"root\": oracle ...PASSED\n  Clock Synchronization ...\n    Network Time Protocol (NTP) ...\n      Daemon 'chronyd' ...PASSED\n      NTP daemon or service using UDP port 123 ...PASSED\n      chrony daemon is synchronized with at least one external time source ...PASSED\n    Network Time Protocol (NTP) ...PASSED\n  Clock Synchronization ...PASSED\n  VIP Subnet configuration check ...PASSED\n  Oracle Net Services configuration ...PASSED\n  Network configuration consistency checks ...PASSED\n  Package: psmisc-22.6-19 ...PASSED\n  File system mount options for path GI_HOME ...PASSED\n  File system mount option hidepid for proc filesystem ...PASSED\n  Cleanup of communication socket files ...PASSED\n  Domain Sockets ...PASSED\n\nPost-check for cluster services setup was successful.\n\nCVU operation performed:      stage -post crsinst\nDate:                         Feb 24, 2026, 5:22:24 PM\nCVU version:                  23.26.1.0.0 (010926x8664)\nClusterware version:          23.0.0.0.0\nCVU home:                     \/u03\/app\/grid26\nGrid home:                    \/u03\/app\/grid26\nUser:                         oracle\nOperating system:             Linux5.15.0-317.197.5.1.el9uek.x86_64\nSuccessfully Configured Software.\n&#091; Exit Code ] 0\n&#091; End ] CVU - 2026-02-24 17:23:01.076\n<\/code><\/pre>\n\n\n\n<p>Now all is up OK verification post check return successfull verification.<\/p>\n\n\n\n<p><br>At this stage we have upgraded our grid home to newest version 26ai ,ASM, OCR and grid processes on 2 node Cluster, This was rolling forward method so it can be done online as , one instance is always up and running on remaining node.<\/p>\n\n\n\n<p>Next step is to upgrade Oracle databases to 26ai home, I will explain this in next blog, generally process is very similar to one node upgrade <a href=\"https:\/\/www.dbi-services.com\/blog\/database-upgrade-to-ai-database-26ai-23-26-1-for-linux-x86-64-upgrade-from-19c-in-3-steps-using-gold-images\/\" id=\"42890\">Database upgrade to AI Database 26ai (23.26.1) for Linux x86-64 upgrade from 19C in 3 steps using gold images.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is third part of 26ai migration blog. We will upgrade here 2 node Clusterware with ASM in 19c. We will use newest 23.26.1 GoldImages from oracle support. This tutorial showing main steps how to perform upgrade, its not procedure to upgrade your production environment, please checkout official documentation from oracle and do proper planning [&hellip;]<\/p>\n","protected":false},"author":148,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[3804,37,258,96,535],"type_dbi":[],"class_list":["post-43282","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-26ai","tag-asm","tag-grid","tag-oracle","tag-rac"],"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>Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward - 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\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward\" \/>\n<meta property=\"og:description\" content=\"This is third part of 26ai migration blog. We will upgrade here 2 node Clusterware with ASM in 19c. We will use newest 23.26.1 GoldImages from oracle support. This tutorial showing main steps how to perform upgrade, its not procedure to upgrade your production environment, please checkout official documentation from oracle and do proper planning [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-04T10:09:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-04T10:09:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-scaled.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"464\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Tomek Sikorski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\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=\"5 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\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\"},\"author\":{\"name\":\"Tomek Sikorski\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c93fd4cb6011723833052cc4e889d01c\"},\"headline\":\"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward\",\"datePublished\":\"2026-03-04T10:09:14+00:00\",\"dateModified\":\"2026-03-04T10:09:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\"},\"wordCount\":943,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1024x186.png\",\"keywords\":[\"26ai\",\"ASM\",\"Grid\",\"Oracle\",\"RAC\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\",\"name\":\"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1024x186.png\",\"datePublished\":\"2026-03-04T10:09:14+00:00\",\"dateModified\":\"2026-03-04T10:09:17+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c93fd4cb6011723833052cc4e889d01c\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-scaled.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-scaled.png\",\"width\":2560,\"height\":464},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward\"}]},{\"@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\/c93fd4cb6011723833052cc4e889d01c\",\"name\":\"Tomek Sikorski\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/57f886b1e968e2d1f8af9b4aada9aa4f1c6a0fcb6e285cfd9273b2fe20745322?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/57f886b1e968e2d1f8af9b4aada9aa4f1c6a0fcb6e285cfd9273b2fe20745322?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/57f886b1e968e2d1f8af9b4aada9aa4f1c6a0fcb6e285cfd9273b2fe20745322?s=96&d=mm&r=g\",\"caption\":\"Tomek Sikorski\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/tomeksikorski\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward - 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\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/","og_locale":"en_US","og_type":"article","og_title":"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward","og_description":"This is third part of 26ai migration blog. We will upgrade here 2 node Clusterware with ASM in 19c. We will use newest 23.26.1 GoldImages from oracle support. This tutorial showing main steps how to perform upgrade, its not procedure to upgrade your production environment, please checkout official documentation from oracle and do proper planning [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/","og_site_name":"dbi Blog","article_published_time":"2026-03-04T10:09:14+00:00","article_modified_time":"2026-03-04T10:09:17+00:00","og_image":[{"width":2560,"height":464,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-scaled.png","type":"image\/png"}],"author":"Tomek Sikorski","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tomek Sikorski","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/"},"author":{"name":"Tomek Sikorski","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c93fd4cb6011723833052cc4e889d01c"},"headline":"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward","datePublished":"2026-03-04T10:09:14+00:00","dateModified":"2026-03-04T10:09:17+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/"},"wordCount":943,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1024x186.png","keywords":["26ai","ASM","Grid","Oracle","RAC"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/","url":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/","name":"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-1024x186.png","datePublished":"2026-03-04T10:09:14+00:00","dateModified":"2026-03-04T10:09:17+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c93fd4cb6011723833052cc4e889d01c"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-scaled.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/02\/image-1-scaled.png","width":2560,"height":464},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/grid-clusterware-26ai-2-node-rac-upgrade-from-19c-rolling-forward\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Grid Clusterware 26ai 2 node RAC upgrade from 19c rolling forward"}]},{"@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\/c93fd4cb6011723833052cc4e889d01c","name":"Tomek Sikorski","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/57f886b1e968e2d1f8af9b4aada9aa4f1c6a0fcb6e285cfd9273b2fe20745322?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/57f886b1e968e2d1f8af9b4aada9aa4f1c6a0fcb6e285cfd9273b2fe20745322?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/57f886b1e968e2d1f8af9b4aada9aa4f1c6a0fcb6e285cfd9273b2fe20745322?s=96&d=mm&r=g","caption":"Tomek Sikorski"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/tomeksikorski\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43282","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=43282"}],"version-history":[{"count":23,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43282\/revisions"}],"predecessor-version":[{"id":43324,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43282\/revisions\/43324"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=43282"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=43282"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=43282"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=43282"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}