GI upgrade failure: ohasd not starting as multiple init.ohasd were running
(Doc ID 2120502.1)
Last updated on NOVEMBER 15, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1.0 and laterOracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Trying to upgrade the clusterware to 12.1.0.2 from pre-12.1.0.2, rootupgrade.sh on first node fails:
rootcrs_<node_time>.log
---------
2016-02-18 22:47:59: Oracle CRS stack has been shut down
2016-02-18 22:47:59: Executing cmd: /u01/app/12.2.0/grid/bin/crsctl start crs -wait
ohasd.trc
----------
2016-02-18 22:48:09.906 : AGFW:3277776640: {0:0:2} Received handshake message from PE.
2016-02-18 22:48:09.906 : CRSPE:3265169152: {0:0:2} Sending initial CHECK for [ora.crf 1 1] to racnode1
....
2016-02-18 22:48:09.914 : CRSOCR:1615466656: OCR context init failure.
Error: PROCL-24: Error in the messaging layer Messaging error [gipcretAddressInUse] [20]
2016-02-18 22:48:09.914 : default:1615466656: Created alert : (:OHAS00106:) : OLR initialization failed, error: PROCL-24: Error in the messaging layer Messaging error [gipcretAddressInUse] [20]
2016-02-18 22:48:09.914 : default:1615466656: [PANIC] OHASD exiting; Could not init OLR
2016-02-18 22:48:09.915 : default:1615466656: Done.
Changes
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 |
| References |