CRS-6706: Oracle Clusterware Release patch level ('mmmmm') does not match Software patch level ('nnnnn'). Oracle Clusterware cannot be started

Error:-

 [ora12c@Server1~]$ sudo /rdbms/app/12.1.0.2/grid/bin/crsctl start crs
CRS-6706: Oracle Clusterware Release patch level ('1009910258') does not match Software patch level ('93699375'). Oracle Clusterware cannot be started.
CRS-4000: Command Start failed, or completed with errors.
[ora12c@Server1 ~]$ sudo /rdbms/app/12.1.0.2/grid/bin/crsctl stop  crs -f
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Stop failed, or completed with errors.
Solution :- 

 This can be encountered in cases where the post patch application measures to run 'rootcrs.pl -postpatch' is not followed.

 In 12c, GI home must have identical patches for the clusterware to start cluster

 Login as root

 Run "<GI_HOME>/crs/install/rootcrs.sh -patch"  on the problematic node and the patch level should be get corrected.

 Above command will correct all issue related to patch level.

 Once it is completed you can apply patch on second node.

 Thats it :)

5 comments:

  1. Jason Brown15 March 2018 at 07:37

    This is amazing. You deserve a medal for posting this!!

    ReplyDelete
  2. Unknown23 April 2018 at 22:46

    Yes your are relay deserve a medal for posting this. While doing the DB patch my host got rebooted and the CRS is not starting with your command: /crs/install/rootcrs.sh -patch issue fixed and the CRS started and my DB also started your amazing

    ReplyDelete
  3. Unknown9 August 2018 at 17:33

    Thanx a lot. really you deserve a medal..

    ReplyDelete
  4. Vijay30 March 2019 at 08:47

    Thanks for posting. One thing to note is that this command won't work on 12.2+.
    You have to use other workarounds as suggested in MoS note 2348013.1

    ReplyDelete
  5. vijay27 July 2020 at 22:46

    thanks for this post... This really helped and saved my day...

    ReplyDelete

Subscribe to: Post Comments (Atom)