11.2.0.4,ASM实例异常宕机,ORA-29740: evicted by instance number 2

2023-10-11 05:48

本文主要是介绍11.2.0.4,ASM实例异常宕机,ORA-29740: evicted by instance number 2,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

一、环境背景

oracle 11.2.0.4  + RAC + RedHat5.8

二、故障描述

ASM实例异常宕机,报错信息如下:

Sun Sep 14 20:27:13 2014
IPC Send timeout detected. Sender: ospid 15909 [oracle@wyjkdb01 (RBAL)]
Receiver: inst 2 binc 458423771 ospid 20030
IPC Send timeout to 2.0 inc 4 for msg type 8 from opid 18
Sun Sep 14 20:27:17 2014
Suppressed nested communications reconfiguration: instance_number 2
Detected an inconsistent instance membership by instance 2
Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_lmon_15889.trc (incident=316873):
ORA-29740: evicted by instance number 2, group incarnation 6
Incident details in: /u01/app/grid/diag/asm/+asm/+ASM1/incident/incdir_316873/+ASM1_lmon_15889_i316873.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_lmon_15889.trc:
ORA-29740: evicted by instance number 2, group incarnation 6
LMON (ospid: 15889): terminating the instance due to error 29740

Sun Sep 14 20:27:22 2014
System state dump requested by (instance=1, osid=15889 (LMON)), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_diag_15883_20140914202722.trc
Dumping diagnostic data in directory=[cdmp_20140914202719], requested by (instance=1, osid=15889 (LMON)), summary=[abnormal instance termination].
Instance terminated by LMON, pid = 15889
Sun Sep 14 20:27:24 2014
MEMORY_TARGET defaulting to 1128267776.
* instance_number obtained from CSS = 1, checking for the existence of node 0...
* node 0 does not exist. instance_number = 1

网络异常,被正常的ASM实例踢除集群

 

三、问题分析

正常ASM日志报错如下:

Sun Sep 14 20:27:13 2014
IPC Send timeout detected. Sender: ospid 20048 [oracle@wyjkdb02 (RBAL)]
Receiver: inst 1 binc 429906001 ospid 15891
Sun Sep 14 20:27:14 2014
IPC Send timeout detected. Sender: ospid 20030 [oracle@wyjkdb02 (LMD0)]
Receiver: inst 1 binc 429906001 ospid 15891
IPC Send timeout to 1.0 inc 4 for msg type 65521 from opid 10
Sun Sep 14 20:27:14 2014
Communications reconfiguration: instance_number 1
Sun Sep 14 20:27:16 2014
IPC Send timeout detected. Receiver ospid 20030 [
Errors in file /u01/app/grid/diag/asm/+asm/+ASM2/trace/+ASM2_lmd0_20030.trc:
IPC Send timeout to 1.0 inc 4 for msg type 16 from opid 18
Detected an inconsistent instance membership by instance 2
Evicting instance 1 from cluster
Waiting for instances to leave: 1
Dumping diagnostic data in directory=[cdmp_20140914202719], requested by (instance=1, osid=15889 (LMON)), summary=[abnormal instance termination].
Reconfiguration started (old inc 4, new inc 8)
List of instances:
2 (myinst: 2)
Global Resource Directory frozen
* dead instance detected - domain 1 invalid = TRUE
* dead instance detected - domain 2 invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Sun Sep 14 20:27:23 2014
LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Submitted all GCS remote-cache requests
Post SMON to start 1st pass IR
Fix write in gcs resources
Reconfiguration complete
Sun Sep 14 20:27:23 2014
NOTE: SMON starting instance recovery for group DATA domain 1 (mounted)
NOTE: F1X0 found on disk 0 au 2 fcn 0.218420
NOTE: starting recovery of thread=2 ckpt=15.764 group=1 (DATA)
NOTE: SMON waiting for thread 2 recovery enqueue
NOTE: SMON about to begin recovery lock claims for diskgroup 1 (DATA)
NOTE: SMON successfully validated lock domain 1
NOTE: advancing ckpt for group 1 (DATA) thread=2 ckpt=15.764
NOTE: SMON did instance recovery for group DATA domain 1
NOTE: SMON starting instance recovery for group OCR_VOTE domain 2 (mounted)

IPC超时,将ASM实例踢除集群

 

CRS日志信息:

2014-09-14 20:21:57.640:
[/u01/app/11.2.0/grid/bin/orarootagent.bin(18720)]CRS-5018:(:CLSN00037:) Removed unused HAIP route:169.254.95.0 / 255.255.255.0 / 0.0.0.0 /usb0

usb网口的网段是169.254.95

 

操作系统日志/var/log/messages

Sep 14 20:21:43 wyjkdb02 last message repeated 2 times
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: Withdrawing address record for 169.254.95.120 on usb0.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: Leaving mDNS multicast group on interface usb0.IPv4 with address 169.254.95.120.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: iface.c: interface_mdns_mcast_join() called but no local address available.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: Interface usb0.IPv4 no longer relevant for mDNS.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: Withdrawing address record for fe80::40f2:e9ff:feda:1101 on usb0.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: Leaving mDNS multicast group on interface usb0.IPv6 with address fe80::40f2:e9ff:feda:1101.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: iface.c: interface_mdns_mcast_join() called but no local address available.
Sep 14 20:21:55 wyjkdb02 avahi-daemon[14864]: Interface usb0.IPv6 no longer relevant for mDNS.
Sep 14 20:21:56 wyjkdb02 dhclient: DHCPREQUEST on usb0 to 255.255.255.255 port 67 (xid=0x175227ff)
Sep 14 20:21:56 wyjkdb02 dhclient: DHCPACK from 169.254.95.118 (xid=0x175227ff)

Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: New relevant interface usb0.IPv4 for mDNS.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Joining mDNS multicast group on interface usb0.IPv4 with address 169.254.95.120.
Sep 14 20:21:56 wyjkdb02 dhclient: bound to 169.254.95.120 -- renewal in 244 seconds.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Registering new address record for 169.254.95.120 on usb0.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Withdrawing address record for 169.254.95.120 on usb0.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Leaving mDNS multicast group on interface usb0.IPv4 with address 169.254.95.120.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: iface.c: interface_mdns_mcast_join() called but no local address available.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Interface usb0.IPv4 no longer relevant for mDNS.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: New relevant interface usb0.IPv4 for mDNS.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Joining mDNS multicast group on interface usb0.IPv4 with address 169.254.95.120.
Sep 14 20:21:56 wyjkdb02 avahi-daemon[14864]: Registering new address record for 169.254.95.120 on usb0.
Sep 14 20:21:57 wyjkdb02 avahi-daemon[14864]: New relevant interface usb0.IPv6 for mDNS.
Sep 14 20:21:57 wyjkdb02 avahi-daemon[14864]: Joining mDNS multicast group on interface usb0.IPv6 with address fe80::40f2:e9ff:feda:1101.
Sep 14 20:21:57 wyjkdb02 avahi-daemon[14864]: Registering new address record for fe80::40f2:e9ff:feda:1101 on usb0.
Sep 14 20:22:10 wyjkdb02 cimserver[13651]: Listening on HTTP port 15988.
Sep 14 20:22:10 wyjkdb02 cimserver[13651]: Listening on HTTPS port 15989.
Sep 14 20:22:10 wyjkdb02 cimserver[13651]: Listening on local connection socket.
Sep 14 20:22:10 wyjkdb02 cimserver[13651]: Started CIM Server version 2.11.0.
Sep 14 20:22:10 wyjkdb02 Director Agent: ADPT_NoControllers wyjkdb02 No controllers found in the system. Sev: 2.
Sep 14 20:22:10 wyjkdb02 Director Agent: ADPT_NoControllers wyjkdb02 No controllers found in the system. Sev: 2.
Sep 14 20:22:50 wyjkdb02 cimserver[13651]: CIM Server registration with External SLP Failed. Exception: connection timed out
Sep 14 20:26:00 wyjkdb02 dhclient: DHCPREQUEST on usb0 to 169.254.95.118 port 67 (xid=0x175227ff)
Sep 14 20:26:40 wyjkdb02 last message repeated 4 times
Sep 14 20:27:47 wyjkdb02 last message repeated 6 times
Sep 14 20:28:48 wyjkdb02 last message repeated 4 times
Sep 14 20:30:05 wyjkdb02 last message repeated 5 times
Sep 14 20:30:40 wyjkdb02 last message repeated 3 times

 

#ifconfig  -a
eth0      Link encap:Ethernet  HWaddr 90:E2:BA:62:61:E8 
          inet addr:10.0.3.6  Bcast:10.0.3.255  Mask:255.255.255.0
          inet6 addr: fe80::92e2:baff:fe62:61e8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5500577 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5004018 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4161309900 (3.8 GiB)  TX bytes:747587111 (712.9 MiB)
          Memory:c5300000-c5380000

eth0:1    Link encap:Ethernet  HWaddr 90:E2:BA:62:61:E8 
          inet addr:10.0.3.8  Bcast:10.0.3.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Memory:c5300000-c5380000

eth1      Link encap:Ethernet  HWaddr 90:E2:BA:62:61:E9 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:c5380000-c5400000

eth2      Link encap:Ethernet  HWaddr 40:F2:E9:DA:16:8A 
          inet addr:173.12.3.6  Bcast:173.12.3.255  Mask:255.255.255.0
          inet6 addr: fe80::42f2:e9ff:feda:168a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:53086008 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45032496 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:36212358508 (33.7 GiB)  TX bytes:23821830145 (22.1 GiB)
          Memory:c5580000-c55a0000

eth2:1    Link encap:Ethernet  HWaddr 40:F2:E9:DA:16:8A 
          inet addr:169.254.151.223
  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Memory:c5580000-c55a0000

eth3      Link encap:Ethernet  HWaddr 40:F2:E9:DA:16:8B 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:c55a0000-c55c0000

eth4      Link encap:Ethernet  HWaddr 40:F2:E9:DA:16:8C 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:c55c0000-c55e0000

eth5      Link encap:Ethernet  HWaddr 40:F2:E9:DA:16:8D 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:c55e0000-c5600000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:65323187 errors:0 dropped:0 overruns:0 frame:0
          TX packets:65323187 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8009448558 (7.4 GiB)  TX bytes:8009448558 (7.4 GiB)

sit0      Link encap:IPv6-in-IPv4 
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

usb0      Link encap:Ethernet  HWaddr 42:F2:E9:DA:16:89 
          inet addr:169.254.95.120  Bcast:169.254.95.255  Mask:255.255.255.0
          inet6 addr: fe80::40f2:e9ff:feda:1689/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:83931 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11563 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6779323 (6.4 MiB)  TX bytes:936612 (914.6 KiB)

 

usb0网口的IP为169.254.95.120

 

据悉,usb0口是系统工程师为了方便管理用(网络直连至服务器).但11.2.0.4.2以后,RAC采用HAIP做心跳冗余,默认是用网段169.254.X.X

到此便知,是由于usb0网口使RAC的HAIP混乱致使ASM实例被踢除集群。

 

 

四、解决方法

1. 禁用usb0自动获取IP,或手工分配IP地址

2. 重启集群服务

 

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

本文来自于我的技术博客 http://blog.csdn.net/robo23

转载请标注源文链接,否则追究法律责任!

 

这篇关于11.2.0.4,ASM实例异常宕机,ORA-29740: evicted by instance number 2的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/185974

相关文章

Java对异常的认识与异常的处理小结

《Java对异常的认识与异常的处理小结》Java程序在运行时可能出现的错误或非正常情况称为异常,下面给大家介绍Java对异常的认识与异常的处理,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参... 目录一、认识异常与异常类型。二、异常的处理三、总结 一、认识异常与异常类型。(1)简单定义-什么是

Python实例题之pygame开发打飞机游戏实例代码

《Python实例题之pygame开发打飞机游戏实例代码》对于python的学习者,能够写出一个飞机大战的程序代码,是不是感觉到非常的开心,:本文主要介绍Python实例题之pygame开发打飞机... 目录题目pygame-aircraft-game使用 Pygame 开发的打飞机游戏脚本代码解释初始化部

Python主动抛出异常的各种用法和场景分析

《Python主动抛出异常的各种用法和场景分析》在Python中,我们不仅可以捕获和处理异常,还可以主动抛出异常,也就是以类的方式自定义错误的类型和提示信息,这在编程中非常有用,下面我将详细解释主动抛... 目录一、为什么要主动抛出异常?二、基本语法:raise关键字基本示例三、raise的多种用法1. 抛

Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析

《Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析》InstantiationAwareBeanPostProcessor是Spring... 目录一、什么是InstantiationAwareBeanPostProcessor?二、核心方法解

java String.join()方法实例详解

《javaString.join()方法实例详解》String.join()是Java提供的一个实用方法,用于将多个字符串按照指定的分隔符连接成一个字符串,这一方法是Java8中引入的,极大地简化了... 目录bVARxMJava String.join() 方法详解1. 方法定义2. 基本用法2.1 拼接

Java空指针异常NullPointerException的原因与解决方案

《Java空指针异常NullPointerException的原因与解决方案》在Java开发中,NullPointerException(空指针异常)是最常见的运行时异常之一,通常发生在程序尝试访问或... 目录一、空指针异常产生的原因1. 变量未初始化2. 对象引用被显式置为null3. 方法返回null

Linux lvm实例之如何创建一个专用于MySQL数据存储的LVM卷组

《Linuxlvm实例之如何创建一个专用于MySQL数据存储的LVM卷组》:本文主要介绍使用Linux创建一个专用于MySQL数据存储的LVM卷组的实例,具有很好的参考价值,希望对大家有所帮助,... 目录在Centos 7上创建卷China编程组并配置mysql数据目录1. 检查现有磁盘2. 创建物理卷3. 创

redis在spring boot中异常退出的问题解决方案

《redis在springboot中异常退出的问题解决方案》:本文主要介绍redis在springboot中异常退出的问题解决方案,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴... 目录问题:解决 问题根源️ 解决方案1. 异步处理 + 提前ACK(关键步骤)2. 调整Redis消费者组

springboot项目redis缓存异常实战案例详解(提供解决方案)

《springboot项目redis缓存异常实战案例详解(提供解决方案)》redis基本上是高并发场景上会用到的一个高性能的key-value数据库,属于nosql类型,一般用作于缓存,一般是结合数据... 目录缓存异常实践案例缓存穿透问题缓存击穿问题(其中也解决了穿透问题)完整代码缓存异常实践案例Red

使用@Cacheable注解Redis时Redis宕机或其他原因连不上继续调用原方法的解决方案

《使用@Cacheable注解Redis时Redis宕机或其他原因连不上继续调用原方法的解决方案》在SpringBoot应用中,我们经常使用​​@Cacheable​​注解来缓存数据,以提高应用的性能... 目录@Cacheable注解Redis时,Redis宕机或其他原因连不上,继续调用原方法的解决方案1