If you’ve installed and configured RAC environment, you should face “User equivalenece check” error during pre-requisite check

There’re three common reasons for getting this error:

– You didn’t configure ssh between nodes. Make sure you can ssh to all nodes which are used at runcluvfy.sh script

– UID are different on any of node

– runcluvfy.sh script can’t find necessary executable to perform the connectivity or equivalence check

In my case, I configured ssh on both nodes and all parameters of an oracle user were same. So in this case, I decided to debug runcluvfy.sh script. To debug this script, you need to set some environment variables:

export CV_HOME=/home/oracle/cv   (Export Cluster Verify debugging home page)

export SRVM_TRACE=true

./runcluvfy.sh stage -post hwos -n node1,node2 -verbose

Then I checked the log file under /home/oracle/cv/pid/cv/log/log_file.log and got the following output:

[Worker 0] [8:57:44:666] [UnixSystem.checkRemoteExecutionSetup:1833] checkRemoteExecutionSetup:: Error checking user equivalence us
ing Secured Shell ‘/usr/local/bin/ssh’; Wed Aug 14 08:57:44 GMT+04:00 2013

[Thread-7] [8:57:44:850] [StreamReader.run:65] ERROR>remshd: Login incorrect.; Wed Aug 14 08:57:44 GMT+04:00 2013

[Thread-5] [8:58:15:773] [StreamReader.run:65] ERROR>rcmd_af: connect: node1: Connection refused; Wed Aug 14 08:5
8:15 GMT+04:00 2013

Hey, wait. I don’t have /usr/local/bin/ssh file! I do have ssh executable but it’s under the different directory. And why the script didn’t use “which ssh” command and get the exact path of the ssh executable?

Anyway, I created a symbolic link to the original ssh file and run the script again. It worked!

Some days ago I was requested to deploy 9i database to 10g Grid Control. According to compatibility matrix (check metalink note – Oracle Enterprise Manager Grid Control Certification Checker (Doc ID 412431.1)) you can install 10g agent on 9i database and deploy it

So I downloaded 10.2.0.2 agent from this link and installed it on 9i machine

Before getting the installation screen, I got the following error :

Unable to convert from “UTF-8” to “ISO8859-1” for NLS!

After struggling a little bit, I set the DISPLAY environment variable and was able to get the installation screen. Installation went smooth and agent deployed successfully. However, when trying to reach to that database over OEM Grid Control, I got “peer not authenticated” error:

I checked OEM and agent logs and didn’t get much information about this error. The output from OEM log was as follows:

2013-08-13 11:19:13,950 [EMUI_11_19_13_/console/database/config] ERROR perf.sitemap logStackTrace.2401 – oracle.sysman.emSDK.emd.comm.CommException: peer not authenticated
at oracle.sysman.emSDK.emd.comm.EMDClient.getResponseForRequest(EMDClient.java:1680)
at oracle.sysman.emSDK.emd.comm.EMDClient.getTarget(EMDClient.java:1214)
at oracle.sysman.db.conf.DBConfigObject.getTargetInstance(DBConfigObject.java:463)
at oracle.sysman.db.conf.DBConfigObject.initPropertiesFromRepository(DBConfigObject.java:634)
at oracle.sysman.db.conf.DBConfigObject.initialize(DBConfigObject.java:434)
at oracle.sysman.db.conf.DBConfigUI.initialize(DBConfigUI.java:271)

Then I tried to compare targets.xml file on both 9i and on 10g machine where agent was working properly and found that the main two lines were missing from 9i targets.xml file:

<Property NAME=”UserName” VALUE=”emuser”/>
<Property NAME=”password” VALUE=”bae2342769a2fac163dfdf256813e716″ ENCRYPTED=”TRUE”/>

I added both lines to the 9i targets.xml file, created “emuser” and changed VALUE parameter of the password field and set ENCRYPTED to “FALSE”

Then I performed the following steps in order to delete all files that should be uploaded and start the agent again in non-secure mode :

$AGENT_HOME/bin/emctl stop agent

rm -rf $AGENT_HOME/sysman/emd/recv

rm -rf $AGENT_HOME/sysman/emd/collection

rm -rf $AGENT_HOME/sysman/emd/state

rm -rf $AGENT_HOME/sysman/emd/upload

rm -rf  $AGENT_HOME/sysman/emd/lastupld.xml

$AGENT_HOME/bin/emctl clearstaete agent

$AGENT_HOME/bin/emctl start agent

After some minutes I was able to manage the database from OEM and the error disappeared.