oracle正版数据库验证失败怎么办,ORACLE RAC 等价性验证错误

Checking user equivalence...

Check: User equivalence for user "oracle"

Node Name                             Comment

------------------------------------  ------------------------

rac2                                  passed

rac1                                  failed

Result: User equivalence check failed for user "oracle".

WARNING:

User equivalence is not set for nodes:

rac1

Verification will proceed with nodes:

rac2

无语，节点1 ssh rac2 没问题

节点2 ssh rac1 也没问题。

无语啊。。

官方解释是

Cause

The first time ssh is run to any new hostname, it gives a warning that the key is not in the database.

The hostname database is on the full hostname that is entered. ie, the entry "abc002" is on a separate line from the entry "abc002.def.ghi.com".

Therefore, even though ssh equivalency is set up and has been run for abc002, the first time ssh is run to "abc002.def.ghi.com", it will prompt for the key.

Therefore ssh has to be run to both the hostname, and the fully qualified hostname, before OUI is run. (eg. to both "abc002" and "abc002.def.ghi.com" ).

Solution

1. Run ssh to both the hostname, and the fully qualified hostname, before OUI is run.

Eg. in the example cluster, you would run the following on each node before starting the install:

$ ssh abc001 date

$ ssh abc001.def.ghi.com date

$ ssh abc002 date

$ ssh abc002.def.ghi.com date

2. When prompted, confirm that YES, the key should be added to the database.

3. When the commands produce no other output/prompts than the date:

$ ssh abc001 date

Fri May 1 11:30:47 UTC 2009

$ ssh abc001.def.ghi.com date

Fri May 1 11:30:48 UTC 2009

$ ssh abc002 date

Fri May 1 11:30:50 UTC 2009

$ ssh abc002.def.ghi.com date

Fri May 1 11:32:50 UTC 2009

then retry the install.

但是我做了也没用，我SSH根本都是通的啊

LINUX 5.3 CLUSTERWARE 10.0.2.1 32bit