Opatch version was different across nodes which causes GI Patching was stuck in state [ROLLING PATCH]
(Doc ID 2199275.1)
Last updated on SEPTEMBER 23, 2021
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
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
[oracle@mysystem.####.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 .
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 .
Applied the current PSU (can occur on any patch / version.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!