ITPub博客

首页 > Linux操作系统 > Linux操作系统 > Starting Instance ORA-27504/27300/27301/27302/27303: requested interfa-1534434.1

Starting Instance ORA-27504/27300/27301/27302/27303: requested interfa-1534434.1

原创 Linux操作系统 作者:rongshiyuan 时间:2013-08-11 20:36:44 0 删除 编辑

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

Symptoms
Changes
Cause
Solution



Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.1 [Release 10.1 to 11.2]
Information in this document applies to any platform.

Symptoms

There are two cluster_interconnect defined for a 11.2.0.1 (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:

SQL> startup
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:check if cable failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgxpcini1
ORA-27303: additional information: requested interface eth0 interface not running set _disable_interface_checking = TRUE to disable this check for single instance cluster. Check output from ifcon

 

Changes

One of the cluster_interconnect network is brought down for maintenance.

Cause

For database upto 11.2.0.1 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:

Interface type 1 eth0 10.0.0.0 configured from GPnP Profile for use as a cluster interconnect
Interface type 1 eth2 10.1.1.128 configured from GPnP Profile for use as a cluster interconnect
...
Starting up:
...
Cluster communication is configured to use the following interface(s) for this instance
 10.0.0.1
 10.1.1.111

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.

Solution

1. Remove the down interface eth0 from OCR:

oifcfg delif -global eth0

2. Shutdown instance 1

3. Restart both instances

Both instances should be able to start after above.

Note: this issue will not happen for 11.2.0.2+ 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/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2009-11-24

  • 博文量
    798
  • 访问量
    3198949