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

相关文章

PyQt6 键盘事件处理的实现及实例代码

《PyQt6键盘事件处理的实现及实例代码》本文主要介绍了PyQt6键盘事件处理的实现示例,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面随着小编来一起... 目录一、键盘事件处理详解1、核心事件处理器2、事件对象 QKeyEvent3、修饰键处理(1)、修饰键类

Python异常处理之避免try-except滥用的3个核心原则

《Python异常处理之避免try-except滥用的3个核心原则》在Python开发中,异常处理是保证程序健壮性的关键机制,本文结合真实案例与Python核心机制,提炼出避免异常滥用的三大原则,有需... 目录一、精准打击:只捕获可预见的异常类型1.1 通用异常捕获的陷阱1.2 精准捕获的实践方案1.3

Python函数的基本用法、返回值特性、全局变量修改及异常处理技巧

《Python函数的基本用法、返回值特性、全局变量修改及异常处理技巧》本文将通过实际代码示例,深入讲解Python函数的基本用法、返回值特性、全局变量修改以及异常处理技巧,感兴趣的朋友跟随小编一起看看... 目录一、python函数定义与调用1.1 基本函数定义1.2 函数调用二、函数返回值详解2.1 有返

SpringBoot+RustFS 实现文件切片极速上传的实例代码

《SpringBoot+RustFS实现文件切片极速上传的实例代码》本文介绍利用SpringBoot和RustFS构建高性能文件切片上传系统,实现大文件秒传、断点续传和分片上传等功能,具有一定的参考... 目录一、为什么选择 RustFS + SpringBoot?二、环境准备与部署2.1 安装 RustF

java.sql.SQLTransientConnectionException连接超时异常原因及解决方案

《java.sql.SQLTransientConnectionException连接超时异常原因及解决方案》:本文主要介绍java.sql.SQLTransientConnectionExcep... 目录一、引言二、异常信息分析三、可能的原因3.1 连接池配置不合理3.2 数据库负载过高3.3 连接泄漏

Python中 try / except / else / finally 异常处理方法详解

《Python中try/except/else/finally异常处理方法详解》:本文主要介绍Python中try/except/else/finally异常处理方法的相关资料,涵... 目录1. 基本结构2. 各部分的作用tryexceptelsefinally3. 执行流程总结4. 常见用法(1)多个e

Debian 13升级后网络转发等功能异常怎么办? 并非错误而是管理机制变更

《Debian13升级后网络转发等功能异常怎么办?并非错误而是管理机制变更》很多朋友反馈,更新到Debian13后网络转发等功能异常,这并非BUG而是Debian13Trixie调整... 日前 Debian 13 Trixie 发布后已经有众多网友升级到新版本,只不过升级后发现某些功能存在异常,例如网络转

C#文件复制异常:"未能找到文件"的解决方案与预防措施

《C#文件复制异常:未能找到文件的解决方案与预防措施》在C#开发中,文件操作是基础中的基础,但有时最基础的File.Copy()方法也会抛出令人困惑的异常,当targetFilePath设置为D:2... 目录一个看似简单的文件操作问题问题重现与错误分析错误代码示例错误信息根本原因分析全面解决方案1. 确保

Java利用@SneakyThrows注解提升异常处理效率详解

《Java利用@SneakyThrows注解提升异常处理效率详解》这篇文章将深度剖析@SneakyThrows的原理,用法,适用场景以及隐藏的陷阱,看看它如何让Java异常处理效率飙升50%,感兴趣的... 目录前言一、检查型异常的“诅咒”:为什么Java开发者讨厌它1.1 检查型异常的痛点1.2 为什么说

MySQL的配置文件详解及实例代码

《MySQL的配置文件详解及实例代码》MySQL的配置文件是服务器运行的重要组成部分,用于设置服务器操作的各种参数,下面:本文主要介绍MySQL配置文件的相关资料,文中通过代码介绍的非常详细,需要... 目录前言一、配置文件结构1.[mysqld]2.[client]3.[mysql]4.[mysqldum