My Oracle Support Banner

GI Upgrade To 12.2.0.1 Due to Incorrect Hub Size (Doc ID 2266682.1)

Last updated on AUGUST 04, 2018

Applies to:

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

Symptoms

Upgrading from 12.1.0.2 to 12.2.0.1 Clusterware fails on second node when running rootupgrade.sh with the following:

CRS-2883: Resource 'ora.cssdmonitor' failed during Clusterware stack start.
CRS-4406: Oracle High Availability Services synchronous start failed.
CRS-4000: Command Start failed, or completed with errors.
2017/05/04 14:36:52 CLSRSC-117: Failed to start Oracle Clusterware stack
Died at /app/oracle/product/grid/12.2.0.1/crs/install/crsupgrade.pm line 1076.
The command '/app/oracle/product/grid/12.2.0.1/perl/bin/perl -I/app/oracle/product/grid/12.2.0.1/perl/lib -I/app/oracle/product/grid/12.2.0.1/crs/install /app/oracle/product/grid/12.2.0.1/crs/install/rootcrs.pl -upgrade' execution faile

 

The Clusterware Alert Log ($GI_BASE/diag/crs/<hostname>/crs/trace) on Node 2 Shows:

2017-05-04 14:36:49.578 [OCSSD(108023)]CRS-1605: CSSD voting file is online: /dev/asmdisks/asmrac; details in /app/oracle/base/grid/diag/crs/<node 2>>/crs/trace/ocssd.trc.
2017-05-04 14:36:49.586 [OCSSD(108023)]CRS-1672: The number of voting files currently available 1 has fallen to the minimum number of voting files required 1.
2017-05-04 14:36:51.191 [OCSSD(108023)]CRS-1665: maximum number of cluster Hub nodes reached; the CSS daemon is terminating
2017-05-04 14:36:52.691 [OCSSD(108023)]CRS-1656: The CSS daemon is terminating due to a fatal error; Details at (:CSSSC00012:) in /app/oracle/base/grid/diag/crs/<node 2>>/crs/trace/ocssd.trc
2017-05-04 14:36:52.692 [OCSSD(108023)]CRS-1603: CSSD on node <node 2> has been shut down.

 The CSSD Trace ($GI_BASE/diag/crs/<hostname>/crs/trace) On Node 1 Shows:

2017-05-04 14:36:49.642 : CSSD:941950720: clssnmCompleteConnProtocol: node <node 1>, 2, uniqueness 1493923007, msg uniqueness 1493923007, endp 0x17a5e probendp 0x7f4f00000000 endp 0x17a5e
2017-05-04 14:36:50.090 : CSSD:941950720: clssnmSendShutdown: Sending shutdown to node <node 2>, number 2, with kill time 0 and reason clssnmKillReasonHubMax
2017-05-04 14:36:50.091 : CSSD:941950720: clssnmHandleJoin: node 2 (<node 2>)not allowed to join because the max number of hubs has been reached (0)
2017-05-04 14:36:51.090 : CSSD:941950720: clssnmSendShutdown: Sending shutdown to node <node 2>, number 2, with kill time 0 and reason clssnmKillReasonHubMax
2017-05-04 14:36:51.090 : CSSD:941950720: clssnmHandleJoin: node 2 (<node 2>)not allowed to join because the max number of hubs has been reached (0)                         <<<<<<<<<<<<<<<<<<<<<< Not allowed to join due to hub size

 The CSSD Trace ($GI_BASE/diag/crs/<hostname>/crs/trace) On Node 2 Shows:

2017-05-04 14:36:49.641 : CSSD:2707334912: clssnmConnComplete: node <node 1> softver 12.2.0.1.0
2017-05-04 14:36:49.641 : CSSD:2707334912: clssnmCompleteConnProtocol: Connect ack from node 1 (<node 1>) ninf endp 0x504, probendp (nil), endp 0x7f3b00000504
2017-05-04 14:36:49.641 : CSSD:2707334912: clssnmCompleteConnProtocol: Connection from known node 1, <node 1>, node unique 1493922523, msg unique 1493922523
2017-05-04 14:36:49.641 : CSSD:2707334912: clssnmCompleteConnProtocol: node <node 1>, 1, uniqueness 1493922523, msg uniqueness 1493922523, endp 0x504 probendp 0x7f3b00000000 endp 0x504
2017-05-04 14:36:50.091 : CSSD:2707334912: clssnmHandleShutdown: Received shutdown from node <node 1>, number 1, incarnation 389350761, time 0, with reason clssnmKillReasonHubMax

 

Changes

 Upgrade to 12.2.0.1 and above

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.