Yesterday, i am facing an issue where all crs commands fail on a cluster with the following error :
“CRS-0184: Cannot communicate with the CRS daemon”
I doesn’t want to resintall a complete clusterware and loose all the clusterware configuration.
To solve the probleme, i use perl script defined in the $ORAGRID_HOME./crs/install/ directory.
I found that the file crsconfig_params containes the global configuration of my cluster.
This file will be generated at the first installation.
This file in used as input by some perl scripts and especially by the roothas.pl and rootcrs.pl.
This file will be generated at the first installation.
This file in used as input by some perl scripts and especially by the roothas.pl and rootcrs.pl.
so first, i try on each node of my cluster to reset the complete ocr/olr configuration files.
To that i execute the following commands :
$ORAGRID_HOME./crs/install/roothas.pl -deconfig -force and $ORAGRID_HOME./crs/install/rootcrs.pl -deconfig -force
This script remove all the configuration donne for the Oracle High Availability Services and also for the Cluster Ready Services.
The -force option is used to indicate to note use the clusterware services (cause not available)
The -deconfig option is used to remove content of the clusterware configuration files.
To recreate the cluster i use the following command that takes in input by default the crsconfig_params file :
$ORAGRID_HOME./crs/install/rootcrs.pl
The magic is done.
You can after restart your cluster using the following command :
$ORAGRID_HOME/bin/crsctl start crs
