CRS-0215: Could not start resource 'ora.rac3.LISTENER_RAC3.lsnr'

时间：2014-08-26 17:20:06 阅读：422 评论：0 收藏：0 [点我收藏+]

标签：crs-0215 rac-vip 增加节点问题 oracle rac

问题：

NETCA to CreateListener Fails with CRS-0215 and the Created Listener Does Not Start

做添加节点的实验创建NETCA时报错crs-0215

查看metalink相关文章发现是因为vip的问题，果然看了一下节点3的vip在其他节点上

[root@rac3 bin]# ./crs_stat -t

Name Type Target State Host

------------------------------------------------------------

ora....B1.inst application ONLINE ONLINE rac1

ora....B2.inst application ONLINE ONLINE rac2

ora.RACDB.db application ONLINE ONLINE rac2

ora....SM1.asm application ONLINE ONLINE rac1

ora....C1.lsnr application ONLINE ONLINE rac1

ora.rac1.gsd application ONLINE ONLINE rac1

ora.rac1.ons application ONLINE ONLINE rac1

ora.rac1.vip application ONLINE ONLINE rac1

ora....SM2.asm application ONLINE ONLINE rac2

ora....C2.lsnr application ONLINE ONLINE rac2

ora.rac2.gsd application ONLINE ONLINE rac2

ora.rac2.ons application ONLINE ONLINE rac2

ora.rac2.vip application ONLINE ONLINE rac2

ora....C3.lsnr application ONLINE OFFLINE

ora.rac3.gsd application ONLINE ONLINE rac3

ora.rac3.ons application ONLINE ONLINE rac3

ora.rac3.vip application ONLINE ONLINE rac1

这是我重启一下nodeapps 发现

[root@rac3 bin]# ./srvctl stop nodeapps -n rac3

[root@rac3 bin]# ./srvctl start nodeapps -n rac3

rac3:ora.rac3.vip:checkIf: Default gateway is notdefined (host=rac3)

rac3:ora.rac3.vip:Interface eth0 checked failed(host=rac3)

rac3:ora.rac3.vip:Invalid parameters, or failed tobring up VIP (host=rac3)

rac3:ora.rac3.vip:checkIf: Default gateway is notdefined (host=rac3)

rac3:ora.rac3.vip:Interface eth0 checked failed(host=rac3)

rac3:ora.rac3.vip:Invalid parameters, or failed tobring up VIP (host=rac3)

CRS-0215: Could not start resource ‘ora.rac3.LISTENER_RAC3.lsnr‘.

在crsd.log日志中发现在节点rac3启动 rac3-vip失败，而在其他节点启动了

2014-08-26 16:07:11.548: [ CRSRES][2751167376]0startRunnable: settingCLI values

2014-08-26 16:07:11.571: [ CRSRES][2751167376]0Attempting to start`ora.rac3.gsd` on member `rac3`

2014-08-26 16:07:12.608: [ CRSRES][2751167376]0Start of `ora.rac3.gsd`on member `rac3` succeeded.

2014-08-26 16:07:12.924: [ CRSRES][2751167376]0startRunnable: settingCLI values

2014-08-26 16:07:12.942: [ CRSRES][2751167376]0Attempting to start`ora.rac3.vip` on member `rac3`

2014-08-26 16:07:19.968: [ CRSAPP][2751167376]0StartResource error forora.rac3.vip error code = 1

2014-08-26 16:07:23.470: [ CRSRES][2751167376]0Start of `ora.rac3.vip` on member `rac3` failed.

2014-08-26 16:07:23.880: [ CRSRES][2751167376]0Attempting to start`ora.rac3.vip` on member `rac1`

2014-08-26 16:07:37.049: [ CRSRES][2751167376]0Start of `ora.rac3.vip`on member `rac1` succeeded.

2014-08-26 16:07:37.328: [ CRSRES][2751167376]0startRunnable: settingCLI values

2014-08-26 16:07:37.353: [ CRSRES][2751167376]0Attempting to start`ora.rac3.ons` on member `rac3`

2014-08-26 16:07:39.397: [ CRSRES][2751167376]0Start of `ora.rac3.ons`on member `rac3` succeeded.

2014-08-26 16:07:39.858: [ CRSRES][2751167376]0StopResource: setting CLIvalues

2014-08-26 16:07:39.922: [ CRSRES][2751167376]0Attempting to stop`ora.rac3.vip` on member `rac1`

2014-08-26 16:07:40.127: [ CRSRES][2751167376]0Stop of `ora.rac3.vip` onmember `rac1` succeeded.

2014-08-26 16:07:40.138: [ CRSRES][2751167376]0startRunnable: settingCLI values

2014-08-26 16:07:40.138: [ CRSRES][2751167376]0Attempting to start`ora.rac3.vip` on member `rac3`

2014-08-26 16:07:47.157: [ CRSAPP][2751167376]0StartResource error forora.rac3.vip error code = 1

2014-08-26 16:07:50.315: [ CRSRES][2751167376]0Start of `ora.rac3.vip` on member `rac3` failed.

2014-08-26 16:07:50.665: [ CRSRES][2751167376]0rac1 : CRS-1019: Resourceora.rac3.LISTENER_RAC3.lsnr (application) cannot run on rac1

rac2 : CRS-1019: Resource ora.rac3.LISTENER_RAC3.lsnr(application) cannot run on rac2

2014-08-26 16:07:50.897: [ CRSRES][2751167376]0Attempting to start`ora.rac3.vip` on member `rac1`

2014-08-26 16:08:03.033: [ CRSRES][2751167376]0Start of `ora.rac3.vip`on member `rac1` succeeded.

发现ora.rac3.vip在节点rac3上尝试了两次重启都失败了最后在 rac1上重启了，导致crs-1019

metalink上描述：

Using NETCA to Create Listener Fails withCRS-0215 and the Created Listener Does Not Start (文档 ID859835.1)

Thisis because the vip of NODE B is not correctly configured, as the listeneris depend on the VIP.

The problem of the vip is that the nameregistered for public interface in the OCR is changed on the operating systemlevel.

From "oifcfg getif" that theregistered public interface is named "Public" command output asfollow :

Public 10.200.0.0 global public
Private - Heartbeat 192.168.1.0 global cluster_interconnect

From ipconofig/ifconfig for node"B" the public interface is named "Public 1" ipconfig command as follow:

Ethernet adapter Public 1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDISVBD Client)
Physical Address. . . . . . . . . : 00-10-18-4F-29-3C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.200.0.159(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.200.0.222
DNS Servers . . . . . . . . . . . : 10.200.0.211
NetBIOS over Tcpip. . . . . . . . : Enabled

This means that the vip for node B is online onnode A hence you will still not able to start/create the listener on node B.

SOLUTION

Consultyour system administrator to correct the public interface name on the OS levelfrom "Public 1" to " Public"

Then you you should restart nodeapps on thatnode B as follow

srvctl stop nodeapps -n node1
srvctl start nodeapps -n node1

Then you should see the vip online on node B, hence youshould be able to create the listener.

出现这个问题是由于vip的问题。

最后做了排查配置都对，所以上面的解决办法不行。

我就关掉了虚拟机换了两块网卡

重启后发现恢复正常了！！！