Rootupgrade From 11.2.0.4 To 12.2.0.1 Failed While Executing Upgrade Step 8 of 19: 'PreUpgrade' : CLSRSC-349: The Oracle Clusterware stack failed to stop
(Doc ID 2426995.1)
Last updated on JANUARY 29, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.2.0.1 [Release 11.2 to 12.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
rootupgrade from 11.2.0.4 to 12.2.0.1 failed on node-2 while executing the step-8 of 19 Preupgrade while stopping the Clusterware stack.
[root@Node-2 ~]# /u01/app/12.2.0.1/grid/rootupgrade.sh
Performing root user operation.
The following environment variables are set as:
ORACLE_OWNER= grid
ORACLE_HOME= /u01/app/12.2.0.1/grid
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
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/12.2.0.1/grid/crs/install/crsconfig_params
The log of current session can be found at:
/u01/app/grid/crsdata/<nodename>/crsconfig/rootcrs_<nodename>_2018-07-17_01-09-40AM.log
Changes
GI upgrade from 11.2.0.4 to 12.2.0.1
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 |
| Changes |
| Cause |
| Solution |