My Oracle Support Banner

18c GI upgrade failed with error 'java.sql.SQLException: ORA-28001: the password has expired' (Doc ID 2583505.1)

Last updated on MAY 11, 2020

Applies to:

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

Symptoms

Upgrading GI from 12.2 to 18.7 failed while executing rootupgrade.sh on node1.

ORACLE_HOME= <18c_GRID_HOME>

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.

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: <18c_GRID_HOME>/crs/install/crsconfig_params
The log of current session can be found at:
<ORACLE_BASE>/crsdata/<NODENAME>/crsconfig/rootcrs_<NODENAME>_<TIMESTAMP>.log
2019/08/30 11:53:21 CLSRSC-595: Executing upgrade step 1 of 19: 'UpgradeTFA'.
2019/08/30 11:53:22 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
2019/08/30 11:54:49 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
2019/08/30 11:54:49 CLSRSC-595: Executing upgrade step 2 of 19: 'ValidateEnv'.
2019/08/30 11:54:57 CLSRSC-595: Executing upgrade step 3 of 19: 'GetOldConfig'.
2019/08/30 11:54:57 CLSRSC-464: Starting retrieval of the cluster configuration data
2019/08/30 11:55:12 CLSRSC-692: Checking whether CRS entities are ready for upgrade. This operation may take a few minutes.
2019/08/30 11:56:46 CLSRSC-693: CRS entities validation completed successfully.
2019/08/30 11:56:55 CLSRSC-515: Starting OCR manual backup.
2019/08/30 11:57:12 CLSRSC-516: OCR manual backup successful.
2019/08/30 11:57:22 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.
2019/08/30 11:57:22 CLSRSC-541:
To downgrade the cluster:
1. All nodes that have been upgraded must be downgraded.
2019/08/30 11:57:22 CLSRSC-542:
2. Before downgrading the last node, the Grid Infrastructure stack on all other cluster nodes must be down.
2019/08/30 11:57:22 CLSRSC-615:
3. The last node to downgrade cannot be a Leaf node.
2019/08/30 11:57:36 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.
2019/08/30 11:57:36 CLSRSC-595: Executing upgrade step 4 of 19: 'GenSiteGUIDs'.
2019/08/30 11:57:42 CLSRSC-595: Executing upgrade step 5 of 19: 'UpgPrechecks'.
2019/08/30 11:58:02 CLSRSC-595: Executing upgrade step 6 of 19: 'SaveParamFile'.
2019/08/30 11:58:17 CLSRSC-595: Executing upgrade step 7 of 19: 'SetupOSD'.
2019/08/30 11:58:17 CLSRSC-595: Executing upgrade step 8 of 19: 'PreUpgrade'.
CLSCH-2005 : Oracle Cluster Health Analysis Service (OCHAD) failed due to a Grid Infrastructure Management Repository error.

Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLException: ORA-28001: the password has expired

2019/08/30 11:58:31 CLSRSC-180: An error occurred while executing the command '<12c_GRID_HOME>/bin/chactl query model'
Died at <18c_GRID_HOME>/crs/install/orachm.pm line 1096.

 Executing the command 'chactl query model' manually from pre-18c (12.2 in this case) GRID_HOME would eventually fail as below

[root@NODENAME ~]# $GRID_HOME/bin/chactl query model
CLSCH-2005 : Oracle Cluster Health Analysis Service (OCHAD) failed due to a Grid Infrastructure Management Repository error.
Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLException: ORA-28001: the password has expired

 

Changes

 Upgrading to 18c

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


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