Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the problem of error reporting PRVF-4007 in Oracle

2025-03-31 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to solve the problem of error reporting PRVF-4007 in Oracle". In daily operation, I believe many people have doubts about how to solve the problem of error reporting PRVF-4007 in Oracle. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for everyone to answer the doubt of "how to solve the problem of error reporting PRVF-4007 in Oracle"! Next, please follow the editor to study!

Problem: Oracle verifies runcluvfy before installing Grid Infrastructure. The Times error is as follows

PRVF-4007: User equivalence check failed for user "grid"

The cause of the problem:

After configuring ssh mutual trust, only check with the remote node, not with the local node (input yes for the first verification)

Solution:

Do a ssh check on the local node

Problem: Oracle verifies runcluvfy before installing Grid Infrastructure. The Times error is as follows

[grid@rac1 grid] $. / runcluvfy.sh stage-pre crsinst-n rac1,rac2-verbose > check0526.log

[grid@rac1 grid] $vi check0526.log

Checking user equivalence...

Check: User equivalence for user "grid"

Node Name Status

-

Rac2 passed

Rac1 failed

Result: PRVF-4007: User equivalence check failed for user "grid"

WARNING:

User equivalence is not set for nodes:

Rac1

Verification will proceed with nodes:

Rac2

Cause of the problem: after configuring ssh mutual trust, only check with the remote node, not with the local node

Solution: do a ssh check on the local node

[root@rac1 grid] # su-oracle

[oracle@rac1 ~] $ssh rac1

The authenticity of host 'rac1 (192.168.100.61)' can't be established.

RSA key fingerprint is 13:88:4c:1b:84:6b:29:1c:79:51:94:59:72:a2:42:e8.

Are you sure you want to continue connecting (yes/no)? Yes

Warning: Permanently added 'rac1192.168.100.61' (RSA) to the list of known hosts.

Last login: Sat May 26 02:36:41 2018 from rac2

[grid@rac1 ~] $ssh rac1

The authenticity of host 'rac1 (192.168.100.61)' can't be established.

RSA key fingerprint is 13:88:4c:1b:84:6b:29:1c:79:51:94:59:72:a2:42:e8.

Are you sure you want to continue connecting (yes/no)? Yes

Warning: Permanently added 'rac1192.168.100.61' (RSA) to the list of known hosts.

Last login: Sat May 26 02:39:44 2018 from rac2

The test is normal after ssh verification with the local.

[grid@rac1 grid] $. / runcluvfy.sh stage-pre crsinst-n rac1,rac2-verbose > check0526a.log

[grid@rac1 grid] $vi check0526a.log

Checking user equivalence...

Check: User equivalence for user "grid"

Node Name Status

-

Rac2 passed

Rac1 passed

Result: User equivalence check passed for user "grid"

At this point, the study on "how to solve the problem of PRVF-4007 reporting errors in Oracle" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report