You might think the SSH connectivity has been setup correctly by Oracle Universal Installer, but INS-06006 eventually appeared when you tried to test it or enter the next step. In this post, I try to list some possibilities for you to think over, and probably you can find another way out of INS-06006.
Possible Causes of INS-06006
The error usually from the network problems, please check the following questions:
- .bash_profile of grid are the same on both nodes? if yes, this could be the problem.
- The host name resolutions wrongly registered on DNS?
- The network design is correct?
- VIP or SCAN is bound into any NIC?
Why? They couldn’t be the same on both nodes. I think you probably copied the configurations from one node to another.
Because OUI could take the wrong node as another to build a wrong connectivity. Hence, please check your DNS or /etc/hosts entries again and make sure entries of hostnames are all in one kind of letter case, either lowercase or uppercase.
I know the letter cases does not matter on name resolution, but there’s a bug was reported by Oracle, which concerns about the letter case of hostname. For Linux platform, the lowercase would be better.
Did you put Public IP, VIP or SCAN IP in different subnets? Because Public IP, VIP and SCAN IP should be all in the same subnet, Private IP should go to a different subnet.
Don’t bind VIP or SCAN into any NIC. Oracle clusterware will bind them into network interfaces automatically and dynamically at startup-time. You can only bind public and private IP into NICs.
Establish SSH Equivalency Manually
If you still get INS-06006, you can try to establish the connectivity manually. For your reference, the following post may provide some helps.
How to Build SSH Equivalency between Two Servers to Work Around INS-06006
It contains steps to build and verify the connectivity, you can try it.
If you are still struggling in how to build a 12c RAC environment, please feel free to visit my posts:
How to Build 12c RAC (0/6) – An Overview