My Oracle Support Banner

After Upgrade From 10.2.0.1 to 10.2.0.4 or Above, Clusterware Cannot Start on Both Nodes (Doc ID 1935738.1)

Last updated on FEBRUARY 18, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.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

After clusterware is upgraded from 10.2.0.1 to 10.2.0.4 or 10.2.0.5, clusterware will not come up on both nodes at once.

The crsd.log on the dysfunctional node reports "clssgsGroupJoin: CSS has not reached fatal mode.Registration is not yet safe. Retrying"

Note: There are other issues which can cause symptom of "clssgsGroupJoin: CSS has not reached fatal mode.Registration is not yet safe. Retrying".  The KEY symptoms here are the "clssgmAssignMemberNo(): grock(#CSS_CLSSOMON) memberNo(1) already assigned" and "clssgsGroupJoin: member in use group(1/#CSS_CLSSOMON)"  messages .

This same problem can happen on AIX platform after applying AIX Service Pack 1 (6100-09-01-1341).

Changes

 Upgrade from 10.2.0.1 or 10.2.0.2 to 10.2.0.4 or 10.2.0.5.

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

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