Thursday 23 July 2020

CRS-6706: Oracle Clusterware Release patch level ('2292884171') does not match Software patch level ('1844241963'). Oracle Clusterware

Cause:    

Post patch step failed and causing problem while starting crs

$GRID_HOME/crs/install/rootcrs.pl -postpatch

 

root@racnode01:# ./crsctl start crs

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

CRS-4000: Command Start failed, or completed with errors.

 

Solution:

1.Run the following command as the root user to complete the patching set up behind the scenes:

root@racnode01:# $GRID_HOME/bin/clscfg -localpatch

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

 

2.  Run the following command as the root user to lock the GI home:

root@racnode01:# cd ../crs/install/

root@racnode01:# ./rootcrs.sh -lock

Using configuration parameter file: /u01/app/18.3.0.0/grid/crs/install/crsconfig_params

The log of current session can be found at:

 /app/grid/crsdata/racnode01/crsconfig/crslock_ racnode01_2020-07-23_02-44-20AM.log

2020/07/23 02:44:22 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service'

root@racnode01:#

 

3. Start crs

root@racnode01:# cd ../../bin/

root@racnode01:# ./crsctl start crs

CRS-4123: Oracle High Availability Services has been started.

2 comments:

  1. This helped me my patching. I faced the similar issues post patching on ORACLE 19C.
    I did below steps

    1. /ora_grid/product/19.0.0.0/bin/clscfg -localpatch
    2./ora_grid/product/19.0.0.0/crs/install/rootcrs.sh -lock
    3./ora_grid/product/19.0.0.0/bin/crsctl start crs

    ReplyDelete
    Replies
    1. Good that it helped ,, thanks for comment

      Delete