Oracle 11g RAC 节点异常重启问题分析

心跳长时间missing,导致2节点被驱逐 当发现一个集群其中一个节点宕机,比如+ASM2在集群里offline,immediate,要重新拉起来所要做的步骤 一、停干净当前宕机节点集群/oragrid/app/11.2.0/grid/bin/crsctl stop crs -f  二、ps -ef |grep d.bin ----查看集群是否停干净,grep d.bin是因为有很多集群资源都是这个结尾的,例如 ohasd.bin,mdns... 阅读详情
AI摘要

国庆巡检时发现Oracle 11g RAC数据库alert日志有异常重启信息。通过分析数据库告警日志、crs及ocssd日志、节点2系统日志,发现节点之间心跳通信异常致节点2重启。经查询,此为11.2.0.3版本的bug,当前生产环境版本11.2.0.4受影响,需打对应补丁修复。

一、背景

在国庆期间巡检的时候,发现数据库alert日志中出现了异常重启的信息,当即对该报错进行分析处理。

二、处理过程

(1)数据库告警日志分析

node1 alert:
Sat Oct 05 13:05:14 2024
Thread 1 advanced to log sequence 6981 (LGWR switch)
  Current log# 11 seq# 6981 mem# 0: +DATA/ybqddb/onlinelog/group_11.302.1144593261
Sat Oct 05 13:05:15 2024
Archived Log entry 12130 added for thread 1 sequence 6980 ID 0x8d497377 dest 1:
Sat Oct 05 14:50:48 2024
Reconfiguration started (old inc 27, new inc 29)
List of instances:
 1 (myinst: 1) 
 Global Resource Directory frozen
 * dead instance detected - domain 0 invalid = TRUE 
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Sat Oct 05 14:50:48 2024
Sat Oct 05 14:50:48 2024
 LMS 3: 1 GCS shadows cancelled, 1 closed, 0 Xw survived
 LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Sat Oct 05 14:50:48 2024
 LMS 1: 1 GCS shadows cancelled, 0 closed, 0 Xw survived
Sat Oct 05 14:50:48 2024
 LMS 2: 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
Sat Oct 05 14:50:48 2024
Instance recovery: looking for dead threads
Beginning instance recovery of 1 threads
 Submitted all GCS remote-cache requests
 Post SMON to start 1st pass IR
 Fix write in gcs resources
Reconfiguration complete
 parallel recovery started with 32 processes
Started redo scan
Completed redo scan
 read 76 KB redo, 16 data blocks need recovery
Started redo application at
 Thread 2: logseq 5168, block 86069
Sat Oct 05 14:50:53 2024
Setting Resource Manager plan SCHEDULER[0x32DE]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Recovery of Online Redo Log: Thread 2 Group 10 Seq 5168 Reading mem 0
  Mem# 0: +DATA/ybqddb/onlinelog/group_10.300.1144593255
Completed redo application of 0.01MB
Completed instance recovery at
 Thread 2: logseq 5168, block 86222, scn 245107035
 16 data blocks read, 16 data blocks written, 76 redo k-bytes read
Sat Oct 05 14:50:53 2024
minact-scn: master found reconf/inst-rec before recscn scan old-inc#:29 new-inc#:29
Thread 2 advanced to log sequence 5169 (thread recovery)
Redo thread 2 internally disabled at seq 5169 (SMON)
Sat Oct 05 14:50:54 2024
Archived Log entry 12131 added for thread 2 sequence 5168 ID 0x8d497377 dest 1:
Sat Oct 05 14:50:54 2024
ARC2: Archiving disabled thread 2 sequence 5169
Archived Log entry 12132 added for thread 2 sequence 5169 ID 0x8d497377 dest 1:
minact-scn: master continuing after IR
minact-scn: Master considers inst:2 dead
Sat Oct 05 14:51:49 2024
Decreasing number of real time LMS from 4 to 0
Sat Oct 05 14:52:11 2024
Reconfiguration started (old inc 29, new inc 31)
List of instances:
 1 2 (myinst: 1) 
 Global Resource Directory frozen
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Sat Oct 05 14:52:11 2024
 LMS 3: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Sat Oct 05 14:52:11 2024
 LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Sat Oct 05 14:52:11 2024
 LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Sat Oct 05 14:52:11 2024
 LMS 2: 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
Sat Oct 05 14:52:11 2024
minact-scn: Master returning as live inst:2 has inc# mismatch instinc:0 cur:31 errcnt:0
 Submitted all GCS remote-cache requests
 Fix write in gcs resources
Reconfiguration complete
Sat Oct 05 14:53:26 2024
Increasing number of real time LMS from 0 to 4
Sat Oct 05 17:05:20 2024
ALTER SYSTEM ARCHIVE LOG
Sat Oct 05 17:05:21 2024
Thread 1 advanced to log sequence 6982 (LGWR switch)
  Current log# 5 seq# 6982 mem# 0: +DATA/ybqddb/onlinelog/group_5.290.1144593225
Sat Oct 05 17:05:21 2024
Archived Log entry 12134 added for thread 1 sequence 6981 ID 0x8d497377 dest 1:
Sat Oct 05 21:05:22 2024
ALTER SYSTEM ARCHIVE LOG
Sat Oct 05 21:05:22 2024
Thread 1 advanced to log sequence 6983 (LGWR switch)
  Current log# 7 seq# 6983 mem# 0: +DATA/ybqddb/onlinelog/group_7.294.1144593235
Sat Oct 05 21:05:23 2024
Archived Log entry 12135 added for thread 1 sequence 6982 ID 0x8d497377 dest 1:
Sun Oct 06 01:08:47 2024
ALTER SYSTEM ARCHIVE LOG
Sun Oct 06 01:08:49 2024
Thread 1 advanced to log sequence 6984 (LGWR switch)
  Current log# 9 seq# 6984 mem# 0: +DATA/ybqddb/onlinelog/group_9.298.1144593249
Sun Oct 06 01:08:49 2024
Archived Log entry 12138 added for thread 1 sequence 6983 ID 0x8d497377 dest 1:
Sun Oct 06 05:05:18 2024
ALTER SYSTEM ARCHIVE LOG
Sun Oct 06 05:05:18 2024
Thread 1 advanced to log sequence 6985 (LGWR switch)
  Current log# 11 seq# 6985 mem# 0: +DATA/ybqddb/onlinelog/group_11.302.1144593261
Archived Log entry 12139 added for thread 2 sequence 5173 ID 0x8d497377 dest 1:
Sun Oct 06 05:05:19 2024

node2 alert:

Sat Oct 05 13:05:14 2024
Archived Log entry 12129 added for thread 2 sequence 5167 ID 0x8d497377 dest 1:
Sat Oct 05 14:50:47 2024
NOTE: ASMB terminating
Errors in file /u01/app/oracle/diag/rdbms/ybqddb/ybqddb2/trace/ybqddb2_asmb_15097.trc:
ORA-15064: communication failure with ASM instance
ORA-03113: end-of-file on communication channel
Process ID: 
Session ID: 2109 Serial number: 3
Errors in file /u01/app/oracle/diag/rdbms/ybqddb/ybqddb2/trace/ybqddb2_asmb_15097.trc:
ORA-15064: communication failure with ASM instance
ORA-03113: end-of-file on communication channel
Process ID: 
Session ID: 2109 Serial number: 3
ASMB (ospid: 15097): terminating the instance due to error 15064
Instance terminated by ASMB, pid = 15097
Sat Oct 05 14:51:59 2024
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = UNLIMITED
 
Total Shared Global Region in Large Pages = 0 KB (0%)
 
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB
 
从节点2日志可以看出,在14:50:47出现与asm实例通信失败报错,并于14:51:59该节点实例开始启动。

(2)查看crs及ocssd日志

node1 crs日志:

2024-07-26 03:02:59.119: 
[client(240419)]CRS-10051:CVU found following errors with Clusterware setup : PRVF-4657 : Name resolution setup check for "nxybj-scan" (IP address: 172.31.122.38) failedPRVF-4664 : Found inconsistent name resolution entries for SCAN name "nxybj-scan"

2024-10-05 14:50:31.281: 
[cssd(10595)]CRS-1612:Network communication with node nxybj2 (2) missing for 50% of timeout interval.  Removal of this node from cluster in 14.200 seconds
2024-10-05 14:50:38.282: 
[cssd(10595)]CRS-1611:Network communication with node nxybj2 (2) missing for 75% of timeout interval.  Removal of this node from cluster in 7.200 seconds
2024-10-05 14:50:43.283: 
[cssd(10595)]CRS-1610:Network communication with node nxybj2 (2) missing for 90% of timeout interval.  Removal of this node from cluster in 2.200 seconds
2024-10-05 14:50:45.484: 
[cssd(10595)]CRS-1607:Node nxybj2 is being evicted in cluster incarnation 587229053; details at (:CSSNM00007:) in /u01/app/11.2.0/grid/log/nxybj1/cssd/ocssd.log.
2024-10-05 14:50:47.994: 
[cssd(10595)]CRS-1625:Node nxybj2, number 2, was manually shut down
2024-10-05 14:50:47.999: 
[cssd(10595)]CRS-1601:CSSD Reconfiguration complete. Active nodes are nxybj1 .
2024-10-05 14:50:48.000: 
[crsd(14356)]CRS-5504:Node down event reported for node 'nxybj2'.
2024-10-05 14:50:51.248: 
[crsd(14356)]CRS-2773:Server 'nxybj2' has been removed from pool 'Generic'.
2024-10-05 14:50:51.249: 
[crsd(14356)]CRS-2773:Server 'nxybj2' has been removed from pool 'ora.orcl'.
2024-10-05 14:50:51.249: 
[crsd(14356)]CRS-2773:Server 'nxybj2' has been removed from pool 'ora.ybqddb'.
2024-10-05 14:50:51.249: 
[crsd(14356)]CRS-2773:Server 'nxybj2' has been removed from pool 'ora.ybzxddb'.
2024-10-05 14:51:13.084: 
[cssd(10595)]CRS-1601:CSSD Reconfiguration complete. Active nodes are nxybj1 nxybj2 .
2024-10-05 14:51:42.117: 
[crsd(14356)]CRS-2772:Server 'nxybj2' has been assigned to pool 'Generic'.
2024-10-05 14:51:42.118: 
[crsd(14356)]CRS-2772:Server 'nxybj2' has been assigned to pool 'ora.ybzxddb'.
2024-10-05 14:51:42.118: 
[crsd(14356)]CRS-2772:Server 'nxybj2' has been assigned to pool 'ora.ybqddb'.
2024-10-05 14:51:42.118: 
[crsd(14356)]CRS-2772:Server 'nxybj2' has been assigned to pool 'ora.orcl'.

node1 ocssd日志:
2024-10-05 14:50:28.553: [    CSSD][2946451200]clssnmSendingThread: sent 5 status msgs to all nodes
2024-10-05 14:50:31.281: [    CSSD][2948028160]clssnmPollingThread: node nxybj2 (2) at 50% heartbeat fatal, removal in 14.200 seconds
2024-10-05 14:50:31.281: [    CSSD][2948028160]clssnmPollingThread: node nxybj2 (2) is impending reconfig, flag 2229260, misstime 15800
2024-10-05 14:50:31.281: [    CSSD][2948028160]clssnmPollingThread: local diskTimeout set to 27000 ms, remote disk timeout set to 27000, impending reconfig status(1)
2024-10-05 14:50:31.282: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693547, LATS 2409222280, lastSeqNo 108691578, uniqueness 1708519428, timestamp 1728111030/2407806020
2024-10-05 14:50:31.282: [    CSSD][3164333824]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693549, LATS 2409222280, lastSeqNo 108693378, uniqueness 1708519428, timestamp 1728111030/2407806140
2024-10-05 14:50:31.691: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111031/2409222690
2024-10-05 14:50:31.781: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111031/2409222780
2024-10-05 14:50:31.784: [    CSSD][3169081088]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693551, LATS 2409222790, lastSeqNo 108691579, uniqueness 1708519428, timestamp 1728111031/2407807110
2024-10-05 14:50:31.811: [    CSSD][3167487744]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111031/2409222810
2024-10-05 14:50:32.193: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2409223200
2024-10-05 14:50:32.282: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693553, LATS 2409223280, lastSeqNo 108693547, uniqueness 1708519428, timestamp 1728111032/2407807530
2024-10-05 14:50:32.291: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2409223290
2024-10-05 14:50:32.321: [    CSSD][3167487744]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2409223320
2024-10-05 14:50:32.701: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2409223700
2024-10-05 14:50:32.783: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693556, LATS 2409223790, lastSeqNo 108693553, uniqueness 1708519428, timestamp 1728111032/2407808040
2024-10-05 14:50:32.793: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2409223790
2024-10-05 14:50:32.823: [    CSSD][3167487744]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2409223820
2024-10-05 14:50:33.203: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2409224200
2024-10-05 14:50:33.282: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693559, LATS 2409224280, lastSeqNo 108693556, uniqueness 1708519428, timestamp 1728111033/2407808540
2024-10-05 14:50:33.301: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2409224300
2024-10-05 14:50:33.331: [    CSSD][3167487744]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2409224330
2024-10-05 14:50:33.554: [    CSSD][2946451200]clssnmSendingThread: sending status msg to all nodes
2024-10-05 14:50:33.554: [    CSSD][2946451200]clssnmSendingThread: sent 5 status msgs to all nodes
2024-10-05 14:50:33.711: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2409224710
2024-10-05 14:50:33.784: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693562, LATS 2409224790, lastSeqNo 108693559, uniqueness 1708519428, timestamp 1728111033/2407809050
2024-10-05 14:50:33.803: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2409224800
2024-10-05 14:50:33.833: [    CSSD][3167487744]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2409224840
2024-10-05 14:50:34.213: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2409225210
2024-10-05 14:50:34.282: [    CSSD][3169081088]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693563, LATS 2409225280, lastSeqNo 108693551, uniqueness 1708519428, timestamp 1728111033/2407809130
2024-10-05 14:50:34.282: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693565, LATS 2409225280, lastSeqNo 108693562, uniqueness 1708519428, timestamp 1728111034/2407809550
2024-10-05 14:50:34.311: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2409225310
2024-10-05 14:50:34.341: [    CSSD][3167487744]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2409225340
2024-10-05 14:50:34.721: [    CSSD][3162732288]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2409225720
2024-10-05 14:50:34.784: [    CSSD][3164333824]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693567, LATS 2409225790, lastSeqNo 108693549, uniqueness 1708519428, timestamp 1728111034/2407809680
2024-10-05 14:50:34.784: [    CSSD][3159578368]clssnmvDHBValidateNcopy: node 2, nxybj2, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108693568, LATS 2409225790, lastSeqNo 108693565, uniqueness 1708519428, timestamp 1728111034/2407810050
2024-10-05 14:50:34.813: [    CSSD][3172316928]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2409225810
 

                                                                                                                            
node2 crs日志:
[ctssd(11996)]CRS-2409:The clock on host nxybj2 is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.
2024-10-03 05:57:32.243: 
[ctssd(11996)]CRS-2409:The clock on host nxybj2 is not synchronous with the mean cluster time. No action has been taken as the Cluster Time Synchronization Service is running in observer mode.
2024-10-05 14:50:31.036: 
[cssd(10538)]CRS-1612:Network communication with node nxybj1 (1) missing for 50% of timeout interval.  Removal of this node from cluster in 14.520 seconds
2024-10-05 14:50:39.038: 
[cssd(10538)]CRS-1611:Network communication with node nxybj1 (1) missing for 75% of timeout interval.  Removal of this node from cluster in 6.520 seconds
2024-10-05 14:50:43.039: 
[cssd(10538)]CRS-1610:Network communication with node nxybj1 (1) missing for 90% of timeout interval.  Removal of this node from cluster in 2.520 seconds
2024-10-05 14:50:45.560: 
[cssd(10538)]CRS-1609:This node is unable to communicate with other nodes in the cluster and is going down to preserve cluster integrity; details at (:CSSNM00008:) in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:50:45.560: 
[cssd(10538)]CRS-1656:The CSS daemon is terminating due to a fatal error; Details at (:CSSSC00012:) in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log
2024-10-05 14:50:45.560: 
[cssd(10538)]CRS-1608:This node was evicted by node 1, nxybj1; details at (:CSSNM00005:) in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:50:45.560: 
[cssd(10538)]CRS-1608:This node was evicted by node 1, nxybj1; details at (:CSSNM00005:) in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:50:45.577: 
[cssd(10538)]CRS-1652:Starting clean up of CRSD resources.
2024-10-05 14:50:46.038: 
[cssd(10538)]CRS-1608:This node was evicted by node 1, nxybj1; details at (:CSSNM00005:) in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:50:46.803: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(14456)]CRS-5016:Process "/u01/app/11.2.0/grid/opmn/bin/onsctli" spawned by agent "/u01/app/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/11.2.0/grid/log/nxybj2/agent/crsd/oraagent_grid/oraagent_grid.log"
2024-10-05 14:50:47.404: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(14456)]CRS-5016:Process "/u01/app/11.2.0/grid/bin/lsnrctl" spawned by agent "/u01/app/11.2.0/grid/bin/oraagent.bin" for action "check" failed: details at "(:CLSN00010:)" in "/u01/app/11.2.0/grid/log/nxybj2/agent/crsd/oraagent_grid/oraagent_grid.log"
2024-10-05 14:50:47.405: 
[cssd(10538)]CRS-1654:Clean up of CRSD resources finished successfully.
2024-10-05 14:50:47.406: 
[cssd(10538)]CRS-1655:CSSD on node nxybj2 detected a problem and started to shutdown.
2024-10-05 14:50:47.434: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(14698)]CRS-5822:Agent '/u01/app/11.2.0/grid/bin/oraagent_oracle' disconnected from server. Details at (:CRSAGF00117:) {0:7:28777} in /u01/app/11.2.0/grid/log/nxybj2/agent/crsd/oraagent_oracle/oraagent_oracle.log.
2024-10-05 14:50:47.436: 
[ohasd(10322)]CRS-2765:Resource 'ora.crsd' has failed on server 'nxybj2'.
2024-10-05 14:50:47.437: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(14456)]CRS-5822:Agent '/u01/app/11.2.0/grid/bin/oraagent_grid' disconnected from server. Details at (:CRSAGF00117:) {0:1:4} in /u01/app/11.2.0/grid/log/nxybj2/agent/crsd/oraagent_grid/oraagent_grid.log.
2024-10-05 14:50:47.437: 
[/u01/app/11.2.0/grid/bin/orarootagent.bin(14460)]CRS-5822:Agent '/u01/app/11.2.0/grid/bin/orarootagent_root' disconnected from server. Details at (:CRSAGF00117:) {0:3:2522} in /u01/app/11.2.0/grid/log/nxybj2/agent/crsd/orarootagent_root/orarootagent_root.log.
2024-10-05 14:50:47.691: 
[cssd(10538)]CRS-1660:The CSS daemon shutdown has completed
2024-10-05 14:50:47.846: 
[ohasd(10322)]CRS-2765:Resource 'ora.evmd' has failed on server 'nxybj2'.
2024-10-05 14:50:47.848: 
[ohasd(10322)]CRS-2765:Resource 'ora.ctssd' has failed on server 'nxybj2'.
2024-10-05 14:50:48.452: 
[crsd(345044)]CRS-0805:Cluster Ready Service aborted due to failure to communicate with Cluster Synchronization Service with error [3]. Details at (:CRSD00109:) in /u01/app/11.2.0/grid/log/nxybj2/crsd/crsd.log.
2024-10-05 14:50:48.598: 
[ohasd(10322)]CRS-2765:Resource 'ora.cssdmonitor' has failed on server 'nxybj2'.
2024-10-05 14:50:48.603: 
[ohasd(10322)]CRS-2765:Resource 'ora.crsd' has failed on server 'nxybj2'.
2024-10-05 14:50:48.861: 
[ctssd(348486)]CRS-2402:The Cluster Time Synchronization Service aborted on host nxybj2. Details at (:ctss_css_init1:) in /u01/app/11.2.0/grid/log/nxybj2/ctssd/octssd.log.
2024-10-05 14:50:49.102: 
[ohasd(10322)]CRS-2765:Resource 'ora.cssd' has failed on server 'nxybj2'.
2024-10-05 14:50:49.105: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(10448)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/u01/app/11.2.0/grid/log/nxybj2/agent/ohasd/oraagent_grid/oraagent_grid.log"
2024-10-05 14:50:49.271: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(10448)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/u01/app/11.2.0/grid/log/nxybj2/agent/ohasd/oraagent_grid/oraagent_grid.log"
2024-10-05 14:50:49.272: 
[ohasd(10322)]CRS-2765:Resource 'ora.asm' has failed on server 'nxybj2'.
2024-10-05 14:50:51.030: 
[cssd(349990)]CRS-1713:CSSD daemon is started in clustered mode
2024-10-05 14:50:52.863: 
[ohasd(10322)]CRS-2878:Failed to restart resource 'ora.ctssd'
2024-10-05 14:50:52.863: 
[ohasd(10322)]CRS-2769:Unable to failover resource 'ora.ctssd'.
2024-10-05 14:51:06.688: 
[cssd(349990)]CRS-1707:Lease acquisition for node nxybj2 number 2 completed
2024-10-05 14:51:07.344: 
[ohasd(10322)]CRS-2765:Resource 'ora.cluster_interconnect.haip' has failed on server 'nxybj2'.
2024-10-05 14:51:07.954: 
[cssd(349990)]CRS-1605:CSSD voting file is online: /dev/asmdisk/ocr02; details in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:51:07.961: 
[cssd(349990)]CRS-1605:CSSD voting file is online: /dev/asmdisk/ocr03; details in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:51:07.968: 
[cssd(349990)]CRS-1605:CSSD voting file is online: /dev/asmdisk/ocr01; details in /u01/app/11.2.0/grid/log/nxybj2/cssd/ocssd.log.
2024-10-05 14:51:13.083: 
[cssd(349990)]CRS-1601:CSSD Reconfiguration complete. Active nodes are nxybj1 nxybj2 .
2024-10-05 14:51:15.026: 
[ctssd(351425)]CRS-2403:The Cluster Time Synchronization Service on host nxybj2 is in observer mode.
2024-10-05 14:51:15.261: 
[ctssd(351425)]CRS-2407:The new Cluster Time Synchronization Service reference node is host nxybj1.
2024-10-05 14:51:15.261: 
[ctssd(351425)]CRS-2401:The Cluster Time Synchronization Service started on host nxybj2.
2024-10-05 14:51:17.018: 
[ohasd(10322)]CRS-2767:Resource state recovery not attempted for 'ora.diskmon' as its target state is OFFLINE
2024-10-05 14:51:17.018: 
[ohasd(10322)]CRS-2769:Unable to failover resource 'ora.diskmon'.
2024-10-05 14:51:22.920: 
[ohasd(10322)]CRS-2878:Failed to restart resource 'ora.cluster_interconnect.haip'
2024-10-05 14:51:22.920: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(10448)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/u01/app/11.2.0/grid/log/nxybj2/agent/ohasd/oraagent_grid/oraagent_grid.log"
2024-10-05 14:51:23.116: 
[/u01/app/11.2.0/grid/bin/oraagent.bin(10448)]CRS-5011:Check of resource "+ASM" failed: details at "(:CLSN00006:)" in "/u01/app/11.2.0/grid/log/nxybj2/agent/ohasd/oraagent_grid/oraagent_grid.log"
2024-10-05 14:51:30.099: 
[ohasd(10322)]CRS-2878:Failed to restart resource 'ora.asm'
2024-10-05 14:51:31.109: 
[ohasd(10322)]CRS-2878:Failed to restart resource 'ora.crsd'
2024-10-05 14:51:36.711: 
[crsd(353461)]CRS-1012:The OCR service started on node nxybj2.
2024-10-05 14:51:36.717: 
[evmd(348478)]CRS-1401:EVMD started on node nxybj2.
2024-10-05 14:51:37.724: 
[crsd(353461)]CRS-1201:CRSD started on node nxybj2.
2024-10-05 14:51:39.350: 

                                                                                                                    
node2 ocssd日志:
2024-10-05 14:50:31.036: [    CSSD][1568802560]clssnmPollingThread: node nxybj1 (1) at 50% heartbeat fatal, removal in 14.520 seconds
2024-10-05 14:50:31.036: [    CSSD][1568802560]clssnmPollingThread: node nxybj1 (1) is impending reconfig, flag 2491406, misstime 15480
2024-10-05 14:50:31.036: [    CSSD][1568802560]clssnmPollingThread: local diskTimeout set to 27000 ms, remote disk timeout set to 27000, impending reconfig status(1)
2024-10-05 14:50:31.037: [    CSSD][1584641792]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592072, LATS 2407806370, lastSeqNo 108585015, uniqueness 1708518327, timestamp 1728111030/2409221770
2024-10-05 14:50:31.037: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592073, LATS 2407806370, lastSeqNo 108589502, uniqueness 1708518327, timestamp 1728111030/2409221810
2024-10-05 14:50:31.687: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111031/2407807020
2024-10-05 14:50:31.777: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111031/2407807110
2024-10-05 14:50:31.817: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111031/2407807150
2024-10-05 14:50:32.037: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592076, LATS 2407807370, lastSeqNo 108592073, uniqueness 1708518327, timestamp 1728111031/2409222810
2024-10-05 14:50:32.197: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2407807530
2024-10-05 14:50:32.287: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2407807620
2024-10-05 14:50:32.327: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2407807660
2024-10-05 14:50:32.480: [    CSSD][1567225600]clssnmSendingThread: sending status msg to all nodes
2024-10-05 14:50:32.480: [    CSSD][1567225600]clssnmSendingThread: sent 5 status msgs to all nodes
2024-10-05 14:50:32.539: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592079, LATS 2407807880, lastSeqNo 108592076, uniqueness 1708518327, timestamp 1728111032/2409223320
2024-10-05 14:50:32.698: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2407808040
2024-10-05 14:50:32.789: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2407808130
2024-10-05 14:50:32.828: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111032/2407808170
2024-10-05 14:50:33.038: [    CSSD][1579894528]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592080, LATS 2407808370, lastSeqNo 108591299, uniqueness 1708518327, timestamp 1728111032/2409223700
2024-10-05 14:50:33.038: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592082, LATS 2407808370, lastSeqNo 108592079, uniqueness 1708518327, timestamp 1728111032/2409223820
2024-10-05 14:50:33.207: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2407808540
2024-10-05 14:50:33.297: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2407808630
2024-10-05 14:50:33.337: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2407808670
2024-10-05 14:50:33.540: [    CSSD][1584641792]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592084, LATS 2407808880, lastSeqNo 108592072, uniqueness 1708518327, timestamp 1728111033/2409224300
2024-10-05 14:50:33.546: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592085, LATS 2407808880, lastSeqNo 108592082, uniqueness 1708518327, timestamp 1728111033/2409224330
2024-10-05 14:50:33.709: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2407809050
2024-10-05 14:50:33.799: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2407809130
2024-10-05 14:50:33.838: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111033/2407809170
2024-10-05 14:50:34.038: [    CSSD][1579894528]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592086, LATS 2407809370, lastSeqNo 108592080, uniqueness 1708518327, timestamp 1728111033/2409224710
2024-10-05 14:50:34.038: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592088, LATS 2407809370, lastSeqNo 108592085, uniqueness 1708518327, timestamp 1728111033/2409224840
2024-10-05 14:50:34.217: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2407809550
2024-10-05 14:50:34.307: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2407809640
2024-10-05 14:50:34.347: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2407809680
2024-10-05 14:50:34.540: [    CSSD][1579894528]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592089, LATS 2407809880, lastSeqNo 108592086, uniqueness 1708518327, timestamp 1728111034/2409225210
2024-10-05 14:50:34.540: [    CSSD][1575139072]clssnmvDHBValidateNcopy: node 1, nxybj1, has a disk HB, but no network HB, DHB has rcfg 587229053, wrtcnt, 108592091, LATS 2407809880, lastSeqNo 108592088, uniqueness 1708518327, timestamp 1728111034/2409225340
2024-10-05 14:50:34.718: [    CSSD][1583048448]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2407810050
2024-10-05 14:50:34.809: [    CSSD][1587885824]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2407810150
2024-10-05 14:50:34.849: [    CSSD][1578292992]clssnmvDiskPing: Writing with status 0x3, timestamp 1728111034/2407810180                                                                                                 

通过crs日志可以看出,在14:50:31开始出现节点之间通信失败报错,随后节点2发生了重启。

(3) 查看节点2系统日志

节点2系统日志:
[root@nxybj2 log]# more messages-20241006
Sep 29 03:50:01 nxybj2 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="7519" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Sep 29 03:50:02 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Sep 30 03:28:02 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Oct  1 04:16:02 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Oct  2 03:24:02 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Oct  3 03:23:03 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Oct  4 03:27:02 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Oct  5 03:34:02 nxybj2 rhsmd: In order for Subscription Manager to provide your system with updates, your system must be registered with the Customer Portal. Please enter your Red Hat login to ensure your system is up-
to-date.
Oct  5 14:50:46 nxybj2 ntpd[394054]: Deleting interface #4 bond0:1, 172.31.122.37#123, interface stats: received=0, sent=0, dropped=0, active_time=6191372 secs
Oct  5 14:51:15 nxybj2 ntpd[394054]: Deleting interface #6 bond1:1, 169.254.209.169#123, interface stats: received=0, sent=0, dropped=0, active_time=6191401 secs
Oct  5 14:51:23 nxybj2 ntpd[394054]: Listen normally on 17 bond1:1 169.254.209.169 UDP 123
Oct  5 14:51:46 nxybj2 ntpd[394054]: Listen normally on 18 bond0:1 172.31.122.37 UDP 123

 系统日志无异常报错。

三、故障原因分析

根据日志信息可以看到,是由于节点之间心跳通信异常,导致节点2发生了重启,根据日志中的关键信息:

2024-10-05 14:50:45.484: 
[cssd(10595)]CRS-1607:Node nxybj2 is being evicted in cluster incarnation 587229053; details at (:CSSNM00007:) in /u01/app/11.2.0/grid/log/nxybj1/cssd/ocssd.log.
2024-10-05 14:50:47.994: 
[cssd(10595)]CRS-1625:Node nxybj2, number 2, was manually shut down

在mos上查询该报错,通过查询到的结果分析,该报错为bug:

受影响版本为:11.2.0.3,当前生成环境版本为:11.2.0.4,由此可以确定本次节点2重启是bug导致。

进一步查询,该bug在如下版本中进行了修复:

根据查询结果,要想修复此bug,就需要打对应版本的补丁。
 

oracle RAC一个节点频繁重启 故障现象:  2011年的一次问题,oracle 11gr2 rac + redhat linux ,2节点rac中的其中一个节点频繁重启; 原因分析: 主机日志 VIP发生了漂移,重启后又归位 node1 Nov 23 18:22:27 dtydb2 avahi-daemon[13096]: Withdrawing address record for 10.4.12 阅读详情

相关推荐

oracle rac节点重启的原因,由重启引起的Oracle RAC节点宕机分析及追根溯源

作者介绍裴征峰,现就职于北京海天起点,二线专家成员,南京办事处负责人,OCP 10g、OCP 11g、OCM11g。超八年Oracle服务经验,擅长数据库故障诊断和性能调优。目前主要从事客户的现场维护、重大问题的解决、数据库性能分析、二线服务质量保证等工作。1背景说明某省份的电信业务系统由于业务量较大,按地市划分部署在4套配置相同的RAC上,相同主机版本,相同的CRS和数据库版本。该系统已正常运行...

weixin_32767301的博客 1236

某RAC数据库一个节点“宕机”原因分析

某RAC数据库一个节点“宕机”原因分析 (RAC down机原因分析)

IT圈黎俊杰 7391

oracle19c集群重启,由重启引起的Oracle RAC节点宕机分析及追根溯源

原标题:由重启引起的Oracle RAC节点宕机分析及追根溯源作者介绍裴征峰,现就职于北京海天起点,二线专家成员,南京办事处负责人,OCP 10g、OCP 11g、OCM11g。超八年Oracle服务经验,擅长数据库故障诊断和性能调优。目前主要从事客户的现场维护、重大问题的解决、数据库性能分析、二线服务质量保证等工作。1背景说明某省份的电信业务系统由于业务量较大,按地市划分部署在4套配置相同的RA...

weixin_33945685的博客 1265

安装GRID遇到CRS-5016无法启动ora.ons故障解决办法

安装GRID之后,在执行root.sh的时候,发现无法启动ora.ons,其它资源都是正常的.root.sh报错如下: 检查报错日志,有如下核心报错信息: 其中关键点是无法获取localhost的地址.很自然的想到是不是/etc/hosts里面把localhost的解析给丢掉了. 重新在/etc/hosts里面添加 127.0.0.1 localhost 再执行root.sh即可 ...

Brent的专栏 1217

Oracle 11g RAC 节点通信故障排查与修复指南

本文详细介绍了Oracle 11g RAC集群发生节点通信故障时的系统性排查与修复方法。当出现节点异常重启时,核心问题往往源于心跳网络中断。文章提供了从快速诊断、日志分析到六层深度检查的完整指南,并给出了针对网络配置、内核参数及Oracle已知Bug等常见根因的实战解决方案,帮助DBA快速恢复集群稳定。

weixin_29246195的博客 272

Oracle-实例重启导致其他实例不可访问!

用户报障生产一套11G的RAC集群,每个节点有5个数据库实例,其中一个实例由于ORA-00600错误引发实例异常重启,在该实例重启之后,同服务器上的其他4个实例均出现无法访问的情况,应用反馈出现ORA-12537连接不上报错问题。

sinat_36757755的博客 1092

CRS-1610,CRS-1611,CRS-1612 heartbeat fatal,eviction in ..

由于一个节点的负荷很高,好像导致心跳线出现问题, hou249bbodb3111$ $vi alerthou249bbodb3111.log 查询CRS 的log发现 heartbeat fatal . 2...

cuixie2370的博客 798

Oracle 11g RAC数据库实例重启的两种方式

NORMALIMMEDIATELOCALLOCAL⚠️ 本文仅讨论Oracle数据库实例的重启,不涉及ASM实例的重启。

Sebastien23的博客 717

Start Of ONS Resource Fails With CRS-2672, CRS-5016, CRS-2674 and CRS-4000

(Doc ID 1633123.1)Applies to: Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterInformation in this document applies to any platform.SymptomsThe ONS resource shows state OFFLINE for on

DBA never sleep-DBA,永不眠 5429

人形机器人_双足行走动力学:基于OpenSim平台的股骨模型与建模

摘要 本文系统解析了股骨模型的生物力学特性、建模方法及应用场景,并探讨了基于OpenSim平台的股骨与42块肌肉Hill-type建模的技术流程。股骨作为人体核心承重骨骼,其几何结构、力学性能及多尺度建模方法在医学仿真、假体设计和仿生机器人领域具有重要价值。OpenSim通过逆向动力学、肌肉力优化及多物理场耦合,为临床步态分析、手术规划及仿生系统开发提供量化工具。同时对比了Hill-type模型与其他肌肉模型的优劣,并展望AI驱动建模、智能材料集成等前沿方向。未来研究将聚焦个性化仿真、实时计算优化及生物-机

一枚农夫,闲来有事聊聊天,交个朋友,让沉闷的生活畅想下 1579

深入解析:如何基于开源OpENer开发EtherNet/IP从站服务

通过OpENer开源库,开发者可以快速实现符合ODVA规范的EtherNet/IP从站设备,降低开发成本并提高系统灵活性。本文详细介绍了EtherNet/IP协议原理、OpENer库的特点与优缺点,以及二次开发的完整流程。通过遵循本文提供的指南,开发者可以成功构建出工业级的EtherNet/IP通信设备。

极地星辰 2996

11G RAC由于存储链路异常导致rac节点宕机以及触发MemberKillEscalation特性分析

同事转来某客户待上线RAC集群异常宕机,需要进行分析并找到宕机原因。分析过程发现这个RAC重启有些不一样,不只是共享存储链路异常导致集群异常,还涉及了11gR2 RAC集群的新特性MemberKillEscalation,记录一下。 对RAC集群其中一节点宕机的原因分析如下: 1.从RAC集群各个组件的日志分析可以发现,节点1在2017-05-16 12:29:02.255开始...

还不算晕的专栏 4821

立创·庐山派-K230-CanMV(嘉楠勘智)开发板通过ATK-ESP8266实现图像识别数据无线传输至原子云

本文详细介绍了如何使用立创·庐山派-K230-CanMV开发板,通过ATK-ESP8266 WIFI模块实现图像识别数据的无线传输至原子云平台。内容包括硬件连接、软件环境搭建、AT指令控制、原子云连接及数据上传的全过程,并提供了实用的调试技巧和常见问题解决方案,为物联网应用开发提供了完整实践指南。

potato的博客 741

ORACLE RAC环境下节点自动重启问题总结

文章参考:主要来源于网络资源分享,并结合自己的ORACLE RAC环境近段时间OS节点自动重启问题进行分析总结 首先我们对能够导致节点重启的CRS进程进行介绍。 1.ocssd...

小麦苗DBA宝典 1824

halcon 查找圆形

先找到大概位置进行拟合,然后再以拟合出的位置作为测量的大概位置进行找圆;

qq_59062726的博客 734

当我们谈论Unidbg时我们在谈什么

文章目录一、前言二、使用Unidbg的工作量是什么三、补环境补的是什么3.1 运行环境缺失3.2 上下文缺失四、Unidbg 不是所有情况下最优的解决方案五、Unidbg在大多数情况下是好的方案六、Unidbg和风控无关七、尾声 一、前言 这是一篇漫谈Unidbg的文章,我对Unidbg的使用和理解都还很浅,日后会更新或修改看法,欢迎大佬指点,也期待同侪讨论。 二、使用Unidbg的工作量是什么 我们常规使用Frida + IDA的动静态分析中,工作可能是这样的 找线索→Frida Hook验证→验证成功继

lilac的博客 5788

Oracle 11g RAC节点异常重启:如何预防和应对常见Bug

本文深入探讨了Oracle 11g RAC节点异常重启的根源,指出常见Bug是主要诱因。文章系统性地介绍了如何从被动响应转向主动防御,包括建立Bug情报库、严谨评估与应用补丁的最佳实践,以及构建涵盖网络、存储和进程的多维监控体系,从而有效预防和应对节点异常重启问题,保障核心业务连续性。

weixin_28331555的博客 388

重塑计算的五层蛋糕:解读黄仁勋CES2026演讲背后的AI新秩序与物理世界

2026年CES演讲揭示AI新纪元:从语言模型到物理智能 NVIDIA CEO黄仁勋在2026年CES演讲中描绘了计算产业的根本性变革。核心突破包括: 计算范式转移:从指令执行转向意图理解,智能体系统崛起 物理AI突破:发布Cosmos世界模型,通过合成数据训练AI理解物理定律 全新VeraRubin计算平台:6芯片协同设计,解决摩尔定律放缓与AI需求增长的矛盾 自动驾驶革命:推出具备推理能力的Alpamayo模型,实现L4级自动驾驶 演讲标志着AI正从数字世界迈向物理世界,NVIDIA通过全栈布局,正在重

老孙 | Ethan Sun 的博客:AI 智能体与 AI 原生软件的工程实践 1273

Oracle 11G RAC重启系统异常

Oracl 11g rac 集群重启异常

向着太阳奔跑 647

华为OD技术面八股_C++_05

汇总华为OD技术面C++方向技术面八股文,提供详细解答。

qq_45776114的博客 413

CoppeliaSim和Python进行无人机联合仿真

CopeeliaSim和Python进行无人机轨迹跟踪联合仿真。首先建立起CoppeliaSim和Python的连接,其次在Python中生成轨迹,CoppeliaSim仿真环境中的无人机进行跟踪,并绘制出轨迹曲线,有每一步详细的教学。

加斯顿工程师的博客 987

oracle节点故障,Oracle11gR2RAC节点crash故障分析

环境:AIX 7100Oracle 11gR2 RAC 详细版本:11.2.0.4 现象: 节点2 CRS HANG住了,CRSCTL命令完全没反应,直接干掉CRS进程主机重环境:AIX 7100Oracle 11gR2 RAC详细版本:11.2.0.4现象:节点2 CRS HANG住了,,CRSCTL命令完全没反应,直接干掉CRS进程主机重启后,但VIP没飘到节点1分析思路;1、DB下的aler...

weixin_35804997的博客 677

最新的sdio 4.0 spec 协议标准 带书签 高清完整PDF版

Part-E1-SDIO-Specification-Ver4.00-Final-120220.pdf:最新的sdio 4.0 spec 协议标准 带书签 高清完整PDF版,包括SDIO 接口的外设,SDIO 接口官方协议等。

oracle10g cssd日志,【案例】Oracle CSSD进程HANG导致RAC节点重启原因分析笔记

【案例】Oracle CSSD进程HANG导致RAC节点重启原因分析笔记时间:2016-11-04 19:20来源:Oracle研究中心作者:HTZ点击:次天萃荷净Oracle研究中心案例分析:运维DBA反映Oracle RAC数据库节点异常重启,通过分析RAC两节点日志得出是由CSSD进程HANG导致RAC节点重启。下面是模拟主机OCSSD.LOG进程HANG住导致主机重启1,...

weixin_33491377的博客 564

Statistics and Machine Learning Toolbox

Statistics and Machine Learning Toolbox(带书签),MATLAB统计学习工具

LinePhone3.2.7(android端最新版本) sip客户端

SIP客户端For android:LinePhone3.2.7(最新版本),官网地址:http://www.linphone.org/

Oracle 11g RAC客户端使用SCAN IP无法连接问题

Oracle 版本:11.2.0.1.0 客户端:Windows Server 2003/PLSQL Developer Oracle服务器端的ip设置如下: ##公网ip 192.168.135.201 WIN-2008SERVER1 192.168.135.202 WIN-2008SERVER2 ##虚拟ip 192.168.135.211 WIN-2008SER

专注于Java技术、软件架构设计、数据分析 7156

Devexpress16.2.6破解工具

Devexpress16.2.6破解工具Devexpress16.2.6破解工具Devexpress16.2.6破解工具Devexpress16.2.6破解工具

solaris平台11gR2 RAC节点异常重启案例分享

故障时间点,在/var/adm/messages中有panic, crash dump的相关信息,检查/var/crash目录下有生成dump,序号已经到了38(说明这是个老问题)。如果真的是网络方面的原因,节点2上应该也有告警,而节点1上也应该有渐进的心跳丢失提示,所以比较合理的解释是,节点1当时出现性能过载,或者个别高优先级的异常进程占据了CPU不释放,导致cluster心跳侦测线程无法获得调度执行,引发超时,包括其他写入日志文件的线程也均受到干扰无法完成执行。(MC)控制网络超时,默认是30秒;

力哥讲技术 425

Oracle 11g RAC环境下Private IP修改方法及异常处理

Oracle 11g RAC环境下Private IP修改方法及异常处理 一、 修改方法 1. 确认所有节点CRS服务以启动 # olsnodes -s -n –i host1 1 host1-vip Active host2 2 host2-vip Active 2. 修改Private IP配置信息 如果之前只有一个私有网卡,则直接删除时会报错,如:PRIF-31: Failed...

sqlora的专栏 1365
上一篇: MySQL InnoDB特性:Double Write
下一篇: Oracle RAC IPC Send timeout detected问题分析处理
听雪楼主.
博客等级 码龄10年 513粉丝 214原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值