Opatch version was different across nodes which causes GI Patching was stuck in state [ROLLING PATCH] (Doc ID 2199275.1)

Last updated on DECEMBER 07, 2016

Applies to:

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

Symptoms

This is a 4 node cluster. CRS is up on Nodes 2 and 4. But on Nodes 1 and 3 the cluster upgrade state is [ROLLING PATCH]

CRS would not start on two nodes after GI patching of OCt 2016 PSU done in a rolling fashion using
/opt/oracrs/gridsw/grid12102/crs/install/rootcrs.sh -prepatch
/opt/oracrs/gridsw/grid12102/crs/install/rootcrs.sh -patch

[oracle@mysystem.mycompany.com ] $ dcli -g /opt/oracle/.dbs_group -l oracle '/opt/oracrs/gridsw/grid12102/bin/crsctl query crs softwarepatch'
Node-1: CRS-6751: unable to get the software patch version
Node-1: CRS-6753: Software patch query failed.
Node-2: Oracle Clusterware patch level on node Node-2 is [400595693].
Node-3: CRS-6751: unable to get the software patch version
Node-3: CRS-6753: Software patch query failed.
Node-4: Oracle Clusterware patch level on node Node-4 is [400595693].

Changes

Applied the current PSU (can occur on any patch / version.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms