My Oracle Support Banner

rootupgrade.sh is failing during GI Upgrade From 12c to 19C on node1 (Doc ID 2741198.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

rootupgrade.sh fails on the 1st node during GI upgrade from 12c to 19c.

[root@rac1 grid]# ./rootupgrade.sh
Performing root user operation.

The following environment variables are set as:
ORACLE_OWNER= grid
ORACLE_HOME= /u01/app/19.0.0.0/grid

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]: y
Copying oraenv to /usr/local/bin ...
The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]: y
Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Relinking oracle with rac_on option
Using configuration parameter file: /u01/app/19.0.0.0/grid/crs/install/crsconfig_params
The log of current session can be found at:
/u01/app/oracle/crsdata/rac1/crsconfig/rootcrs_rac1_2021-01-01_11-53-52PM.log
2021/01/01 23:54:13 CLSRSC-595: Executing upgrade step 1 of 18: 'UpgradeTFA'.
2021/01/01 23:54:13 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
2021/01/01 23:54:13 CLSRSC-595: Executing upgrade step 2 of 18: 'ValidateEnv'.
2021/01/01 23:54:19 CLSRSC-595: Executing upgrade step 3 of 18: 'GetOldConfig'.
2021/01/01 23:54:19 CLSRSC-464: Starting retrieval of the cluster configuration data
2021/01/01 23:54:31 CLSRSC-692: Checking whether CRS entities are ready for upgrade. This operation may take a few minutes.
2021/01/01 23:54:56 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
2021/01/01 23:56:46 CLSRSC-693: CRS entities validation completed successfully.
2021/01/01 23:56:51 CLSRSC-515: Starting OCR manual backup.
2021/01/01 23:57:00 CLSRSC-516: OCR manual backup successful.
2021/01/02 00:00:03 CLSRSC-486:
At this stage of upgrade, the OCR has changed.
Any attempt to downgrade the cluster after this point will require a complete cluster outage to restore the OCR.
2021/01/02 00:00:03 CLSRSC-541:
To downgrade the cluster:
1. All nodes that have been upgraded must be downgraded.
2021/01/02 00:00:03 CLSRSC-542:
2. Before downgrading the last node, the Grid Infrastructure stack on all other cluster nodes must be down.
2021/01/02 00:00:12 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.
2021/01/02 00:00:12 CLSRSC-595: Executing upgrade step 4 of 18: 'GenSiteGUIDs'.
2021/01/02 00:00:13 CLSRSC-595: Executing upgrade step 5 of 18: 'UpgPrechecks'.
2021/01/02 00:00:18 CLSRSC-363: User ignored prerequisites during installation
2021/01/02 00:00:30 CLSRSC-595: Executing upgrade step 6 of 18: 'SetupOSD'.
2021/01/02 00:00:30 CLSRSC-595: Executing upgrade step 7 of 18: 'PreUpgrade'.
2021/01/02 00:03:38 CLSRSC-468: Setting Oracle Clusterware and ASM to rolling migration mode
2021/01/02 00:03:38 CLSRSC-482: Running command: '/u01/app/12.2.0/grid/bin/crsctl start rollingupgrade 19.0.0.0.0'
CRS-1136: Rejecting the rolling upgrade mode change because the cluster is being patched.
CRS-4000: Command Start failed, or completed with errors.
2021/01/02 00:03:39 CLSRSC-511: failed to set Oracle Clusterware and ASM to rolling migration mode
Died at /u01/app/19.0.0.0/grid/crs/install/oraasm.pm line 1486.

 



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.