Way To Avoid PRV-4007 For “runcluvfy.sh”

I encountered a problem eg. Result: PRVF-4007 : User equivalence check failed for


[oracle@rac-2 grid]$ ./runcluvfy.sh stage -pre crsinst -n rac-1,rac-2 -fixup -verbose

Performing pre-checks for cluster services setup

Checking node reachability…

Check: Node reachability from node “rac-2”
Destination Node Reachable?
———————————— ————————
rac-2 yes
rac-1 yes
Result: Node reachability check passed from node “rac-2”

Checking user equivalence…

Check: User equivalence for user “oracle”
Node Name Comment
———————————— ————————
rac-2 failed
rac-1 failed
Result: PRVF-4007 : User equivalence check failed for user “oracle”

ERROR:
User equivalence unavailable on all the specified nodes
Verification cannot proceed

Pre-check for cluster services setup was unsuccessful on all the nodes.
[oracle@rac-2 grid]$

Here is a suggested method that may help you.

steps to avoid PRV-4007

you can take either of 1) and 2)
1) just del all previous user and create all new user in each node.If it is possible run telnet with each node and create group and users with same uid and gid.

I used step 1 and step 3 both to recover myself from this error.

2) if you have initially created a user one or two groups are not matching you can do it easily.but if your uid do not match for grid and oracle user,you may face some problem. But step 2 is the easiest way to handle this stuff.

first issue :


usermod -u 503 grid


Then


# /bin/find / -uid -print0 | /usr/bin/xargs -0 -r /bin/chown

if you do not issue the above command you may face error :


GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: IOR file '/tmp/gconfd-grid/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: No such file or directory)

key idea to issue the above command is:

The user needs to be logged off when making this type of change.
The usermod(8) just updates the /etc/group files. It is your responsibility to change the ownership of any files owned by that user, including their home directory, its files, and any files they may own anywhere in the file system.

Step 3)
ssh configuration for password less login

NB:-
you need to follow either of steps 1 and steps 2 and then steps 3.This steps 3 is mandatory.