Error Starting Instance ORA-27504 ORA-27300 ORA-27301 ORA-27302 ORA-27303: requested interface %s interface not running (文档 ID 1534434.1)
In this Document
There are two cluster_interconnect defined for a 188.8.131.52 (or earlier) RAC database: eth0 (10.0.0.x) and eth2(10.1.1.x). Due to network maintenance, eth0 is brought down, node 2 is restarted, after that instance 2 fails to startup with the following errors while instance 1 is still up and running:
One of the cluster_interconnect network is brought down for maintenance.
For database upto 184.108.40.206 release, even 2 private network defined for cluster_interconnect, there is no failover feature available at database layer. One interface down could lead to communication problem between the instances, causing 2nd instance could not start or could not join the cluster.
When eth0 is down, the message for 2nd instance startup: "ORA-27303: additional information: requested interface eth0 interface not running" is expected.
Setting _disable_interface_checking = TRUE will only allow instance to startup nomount, but not join the cluster, it will error out with ORA-29702 "error occurred in Cluster Group Service operation" while LMON trying to join the cluster. This is because when instance 1 was started, both interfaces were available, hence ports are opened on both interfaces. Alert log of instance 1 shows:
When instance 2 starts, ports will only be open on eth2, it will not be able to communicate with processes which have ports opened on eth0.
1. Remove the down interface eth0 from OCR:
2. Shutdown instance 1
3. Restart both instances
Both instances should be able to start after above.
Note: this issue will not happen for 220.127.116.11+ release due to HAIP feature. HAIP will failover automatically when 1 of the underlying interface is down. It is transparent to database instances and it will not affect communication between database instances.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/17252115/viewspace-768243/，如需转载，请注明出处，否则将追究法律责任。