In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-04 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/01 Report--
This article mainly shows you how to do "The specified nodes are not clusterable error appears when RAC is installed". The content is simple and easy to understand, and the organization is clear. I hope it can help you solve your doubts. Let Xiaobian lead you to study and learn this article "The specified nodes are not clusterable error appears when RAC is installed".
Error after installing RAC clusterware after adding nodes:
The specified nodes are not clusterable.
The following error was returned by the operating system: null
I have also installed several test rac environments before, and the problems encountered have also been encountered. Previously encountered this problem is the hosts file ghost, so this conditional reflex directly to check this file:
[root@node2 orcl]# more /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost
10.85.10.119 node1
10.85.10.121 node2
192.168.0.119 node1prv
192.168.0.121 node2prv
10.85.10.122 node1vip
10.85.10.123 node2vip
The first line of hosts of the two nodes: 127.0.0.1 localhost has been modified, and there is no problem.
Google's results are as follows, which helped me a lot..
Alert: The specified nodes are not clusterable. This could be due to one or more of the following reasons:
1. The user performing the install is not configured in an equivalent manner on all nodes.
2. ssh and scp are not configured properly on all nodes.
3. rsh and rcp are not configured properly on all nodes.
Reconstruction checks for user equivalence. I remember that I had tested it when I created it. I thought that the problem could not be here, but after running it again, I found that the problem was still here.
Node1:
[oracle@node1 ~]$ ssh node1 date
[oracle@node1 ~]$ ssh node2 date
[oracle@node1 ~]$ ssh node1prv date
[oracle@node1 ~]$ ssh node2prv date
Node2:
[oracle@node2 ~]$ ssh node1 date
[oracle@node2 ~]$ ssh node2 date
[oracle@node2 ~]$ ssh node1prv date
[oracle@node2 ~]$ ssh node2prv date
On node2, there are two nodes that have not yet run ssh and still need to enter passwords. Problem solved after running ssh. Still careless. There are 2 SSH missing. It's a little sad..
Here is how to establish user equivalence:
1. group add dba oinstall group on two nodes, create oracle user, primary group oinstall, additional groups are dba and disk
#groupadd oinstall
#groupadd dba
#useradd -g oinstall -G dba oracle
#passwd oracle
2. Establishment of equivalent users
At node1:
[root@node1 opt]# su - oracle
[oracle@node1 ~]$ mkdir ~/.ssh
[oracle@node1 ~]$ chmod 700 ~/.ssh
[oracle@node1 ~]$ ssh-keygen -t rsa
[oracle@node1 ~]$ ssh-keygen -t dsa
At node2:
[root@node2 opt]# su - oracle
[oracle@node2 ~]$ mkdir ~/.ssh
[oracle@node2 ~]$ chmod 700 ~/.ssh
[oracle@node2 ~]$ ssh-keygen -t rsa
[oracle@node2 ~]$ ssh-keygen -t dsa
Switch back to node1 and execute:
[oracle@node1 ~]$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
[oracle@node1 ~]$ cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
Tip: The following command will prompt you to enter the oracle password for node2. Follow the prompt to enter it. If it fails, you can try to execute the command again.
Order.
[oracle@node1 ~]$ scp ~/.ssh/authorized_keys node2:~/.ssh/authorized_keys
[oracle@node1 ~]$ ssh node2 cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
[oracle@node1 ~]$ ssh node2 cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
[oracle@node2 ~]$ scp ~/.ssh/authorized_keys node1:~/.ssh/authorized_keys
Make sure that both nodes have node information about each other.
The two machines execute each other to see if they still need to enter the password
[oracle@node1 ~]$ ssh node1 date
[oracle@node1 ~]$ ssh node2 date
[oracle@node1 ~]$ ssh node1prv date
[oracle@node1 ~]$ ssh node2prv date
Switch to node2 execution
[oracle@node2 ~]$ ssh node1 date
[oracle@node2 ~]$ ssh node2 date
[oracle@node2 ~]$ ssh node1prv date
[oracle@node2 ~]$ ssh node2prv date
After building equivalence, you need to enter a password for the first ssh node, and you don't need it for the second time. Therefore, after building equivalence, you must ssh all relevant nodes. If you don't, you will have a cup...
The above is "The specified nodes are not clusterable error when installing RAC" All the contents of this article, thank you for reading! I believe that everyone has a certain understanding, hope to share the content to help everyone, if you still want to learn more knowledge, welcome to pay attention to the industry information channel!
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.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.