Resolving the problem of invalid hostname during ORACLE12C RAC construction

Tag: ORACLE12C RAC hostname is invalid

To build an Oracle 12c RAC cluster on the Windows 2012 64-bit Enterprise Edition, the Hosts file is as follows:
#add for RAC Config
11.14.72.83 Rac1
11.14.72.84 RAC1-VIP
192.168.0.1 Rac1-priv
11.14.72.85 RAC2
11.14.72.86 RAC2-VIP
192.168.0.2 Rac2-priv
11.14.72.87 Scanip

Two machines to ping each other is not a problem, the pre-check batch is also completely passed, but in the installation of the cluster piece grid is prompted to say that the other node hostname is invalid, that is, the installation of Rac1 on the RAC2 invalid, the installation of Rac1 on the RAC2 invalid.

Error:

650) this.width=650; "Src=" https://s4.51cto.com/wyfs02/M02/9A/BF/wKioL1laBybDMYMTAAOO4OPDbkU292.png-wh_500x0-wm_ 3-wmp_4-s_1368404463.png "title=" 222wuxiao.png "alt=" Wkiol1labybdmymtaaoo4opdbku292.png-wh_50 "/>

Discover Oracle's website:

The solution to this problem :

Odm:

RAC on windows:ins-40937 encountering During 11.2.0.3 Grid Infrastructure Install (document ID 1479496.1)

Cause

Invalid binding order of the network adapters on the node which returned the error.

One of the installation prerequisites for grids Infrastructure installations on Windows platforms are

To has your ' public ' network adapter listed first in your binding order and

Your ' Private ' network adapter listed second in your binding order on all cluster nodes.

Solution

Fix the network Adapter Binding order So, the public Network Adapter is listed first and

Your private network adapter is listed second as per documented installation prerequisites

The same applies to 12C

Check the NIC binding order found that both public and private bindings have inconsistent NIC order

650) this.width=650; "Src=" https://s2.51cto.com/wyfs02/M01/9A/BF/wKiom1laCHyDxbmOAADNYOPZIlo104.png-wh_500x0-wm_ 3-wmp_4-s_3238712072.png "title=" 11111.png "alt=" Wkiom1lachydxbmoaadnyopzilo104.png-wh_50 "/>

Two nodes must first bind public on # #, then bind private at

After the adjustment, reinstall the cluster pieces successfully passed.

In addition, it is necessary to ensure that

1. Ensure that the node VIP and public IP are within the same network segment

A similar problem occurs if the VIP and public IPs are not in the same network segment.

2, two nodes of the hosts or/etc/fstab to be exactly the same

And Ping Public1, vip1, pubic2,vip2 two nodes to be able to ping through

This article is from the "Hollows Jie Sun" blog, be sure to keep this source http://xjsunjie.blog.51cto.com/999372/1944133

Resolving the problem of invalid hostname during ORACLE12C RAC construction