My Oracle Support Banner

GI upgrade failure: ohasd not starting as multiple init.ohasd were running (Doc ID 2120502.1)

Last updated on FEBRUARY 11, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle 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.


Trying to upgrade the clusterware to from pre-, on first node fails:

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


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.





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

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