Hi all,
When performing a spot health check in a client environment, got this:
[oracle@dbserver1 ~]$ crsctl query crs releaseversion Oracle High Availability Services release version on the local node is [12.1.0.2.0] [oracle@dbserver1 ~]$ crsctl query crs activeversion -f Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [26717470].
By checking over the applied patched on the 3 nodes, it’s matching:
+ASM1@dbserver1 > kfod op=patches List of Patches =============== 20243804 20415006 20594149 20788771 20950328 21125181 21359749 21436941 21527488 21694919 21949015 22806133 23144544 24007012 24340679 24732088 24846605 25397136 25869760 26392164 26392192 26609798 26717470 +ASM2@dbserver2 > kfod op=patches List of Patches =============== 20243804 20415006 20594149 20788771 20950328 21125181 21359749 21436941 21527488 21694919 21949015 22806133 23144544 24007012 24340679 24732088 24846605 25397136 25869760 26392164 26392192 26609798 26717470 +ASM3@dbserver3 > kfod op=patches List of Patches =============== 20243804 20415006 20594149 20788771 20950328 21125181 21359749 21436941 21527488 21694919 21949015 22806133 23144544 24007012 24340679 24732088 24846605 25397136 25869760 26392164 26392192 26609798 26717470
So, it’s most likely some patch completed wrongly. Here is the quick fix:
$GI_HOME/bin/clscfg -patch $GI_HOME/bin/crsctl stop rollingpatch
Once done, issue fixed!
I hope it helps!