CRS-6706: Oracle Clusterware Release patch level ('nnn') does not match  Software patch level ('mmm') (Doc ID 1639285.1)

To Bottom

---

In this Document Purpose Details Case1: Discrepancy found in the list of applied patches on different nodes: Case2: All nodes have same patches but different patch level: References APPLIES TO: Oracle Database - Enterprise Edition - Version 12.1.0.1 and later Information in this document applies to any platform. PURPOSE This note lists causes/solutions for the following issue: Oracle 12c Grid Infrastructure fails to start after patching: CRS-6706: Oracle Clusterware Release patch level ('xxxxxxxx') does not match Software patch level ('xxxxxxxxx'). Oracle Clusterware cannot be started This can be encountered - for example - in cases where the post patch application instruction  to run 'rootcrs.pl -postpatch' is not followed. DETAILS   Case1: Discrepancy found in the list of applied patches on different nodes: Node 1: <GI_HOME>/bin/kfod op=patches --------------- List of Patches =============== 15994107 16495244   ====>> this one doesn't exist on the other node 17027533 17303297 <GI_HOME>/bin/kfod op=patchlvl ------------------- Current Patch level =================== 1581137133 Node 2: <GI_HOME>/bin/kfod op=patches --------------- List of Patches =============== 15994107 17027533 17077442         ====>> this one doesn't exist on the other node 17303297 <GI_HOME>/bin/kfod op=patchlvl ------------------- Current Patch level =================== 3400658801 crsd.trc ====== 2015-06-23 15:06:00.260076 :  OCRMAS:1797244672: th_hub_verify_master_pubdata: Shutdown CacheLocal. Patch Levels don't match.  Local Patch Level [3467666221] != Cache Writer Patch Level [4137922036] 2015-06-23 15:06:00.260101 :  OCRAPI:1797244672: procr_ctx_set_invalid: ctx is in state [6]. 2015-06-23 15:06:00.260103 :  OCRAPI:1797244672: procr_ctx_set_invalid: ctx set to invalid 2015-06-23 15:06:00.260193 :  OCRAPI:1797244672: procr_ctx_set_invalid: Aborting... In 12c, GI home must have identical patches for the clusterware to start unless during rolling patching. After applied the same patches on all nodes, GI started fine. Case2: All nodes have same patches but different patch level: Node1 $ /data01/12.1.0/grid/bin/kfod op=patches --------------- List of Patches =============== 17303297 18365185 19121550 $ /data01/12.1.0/grid/bin/kfod op=patchlvl ------------------- Current Patch level =================== 2061097728 Node2 $ /data01/12.1.0/grid/bin/kfod op=patches --------------- List of Patches =============== 17303297 18365185 19121550 $ /data01/12.1.0/grid/bin/kfod op=patchlvl ------------------- Current Patch level =================== 2061097728                                   ====>> same patch level However opatch lsinventory shows the different patch level: Patch level status of Cluster nodes : Patching Level Nodes -------------- ----- 1216323972 node2                          ====>> different patch level 2061097728 node1 For 12.1.0.1 on-wards: Execute"<GI_HOME>/crs/install/rootcrs.sh -patch" as root  user on the problematic node and the patch level should be corrected. For Oracle Grid Infrastructure for a standalone server Log in as root # <GI_HOME>/crs/install/roothas.sh -unlock # <GI_HOME>/crs/install/roothas.sh -patch