ODA: "libclntsh.so.12.1" active cause GI upgrade failed
(Doc ID 2067856.1)
Last updated on JULY 24, 2023
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
It's a general GI upgrade issue but we will need use ODA oakcli to cleanup/rerun the steps.
Symptoms
GI Upgrade is failing due to patch conflict
# oakcli update -patch 12.1.2.4.0 --gi
Please enter the 'SYSASM' password : (During deployment we set the SYSASM password to 'welcome1'):
Please re-enter the 'SYSASM' password:
INFO: Running pre-install scripts
....
SUCCESS: All nodes in /opt/oracle/oak/temp_clunodes.txt are pingable and alive.
INFO: 2015-09-23 19:51:18: Setting up the ssh for grid user
e
INFO: 2015-09-23 19:56:09: Patching the GI home on node oda_node2
...
INFO: 2015-09-23 19:57:53: ASM is running in flex mode
INFO: GI patching summary on node: oda_node1
ERROR: 2015-09-23 19:57:54: Conflict checks failed for the home /u01/app/12.1.0.2/grid
INFO: 2015-09-23 19:57:54: Did not consider the home /u01/app/12.1.0.2/grid for patching
INFO: GI patching summary on node: oda_node2
ERROR: 2015-09-23 19:57:54: Conflict checks failed for the home /u01
/u01/app/12.1.0.2/grid/cfgtoollogs/opatch/opatch*.log may have the ERROR:
UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
/u01/app/12.1.0.2/grid/lib/libclntsh.so.12.1 >>>>>>>>>>>>>>>>>>>>>>>> This library file is active and it is not allow to apply the patch
Log file location: /u01/app/12.1.0.2/grid/cfgtoollogs/opatch/opatch2015-09-29_16-28-17PM_1.log
OPatch failed with error code 73
ERROR:
UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
Changes
Customer is performing GI upgrade from 12.1.0.2.1 to 12.1.0.2.4
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! |