Oracle 11gR2 RAC節點crash故障分析

Oracle 11gR2 RAC節點crash故障分析

環境：AIX 7100
Oracle 11gR2 RAC
 詳細版本：11.2.0.4
 
現象：
 節點2 CRS HANG住了，CRSCTL命令完全沒反應，直接幹掉CRS進程主機重啟後，但VIP沒飄到節點1
 
分析思路；
 1、DB下的alert日誌及相關trace日誌。
 2. 查看所有節點的"errpt -a"的輸出。
 3. 查看發生問題時所有節點的GI日誌：
 <GRID_HOME>/log/<host>/alert*.log
 <GRID_HOME>/log/<host>/crsd/crsd.log
 <GRID_HOME>/log/<host>/cssd/ocssd.log
 <GRID_HOME>/log/<host>/agent/ohasd/oracssdmonitor_root/oracssdmonitor_root.log
 <GRID_HOME>/log/<host>/agent/ohasd/oracssdagent_root/oracssdagent_root.log
 /etc/oracle/lastgasp/*, or /var/opt/oracle/lastgasp/*(If have)
 註：如果是CRS發起的重啟主機會在/etc/oracle/lastgasp/目錄下的檔案中添加一條記錄。
 4.  查看發生問題時所有節點的LMON, LMS*,LMD0 trace files。
 5. 查看發生問題時所有節點OSW的所有輸出。

--------------------------------------分割線 --------------------------------------

在CentOS 6.4下安裝Oracle 11gR2(x64)

Oracle 11gR2 在VMWare虛擬機器中安裝步驟

Debian 下 安裝 Oracle 11g XE R2

--------------------------------------分割線 --------------------------------------
 
詳細分析過程如下：
 
節點1DB的alert日誌：
 Tue Mar 25 12:59:07 2014
 Thread 1 advanced to log sequence 245 (LGWR switch)
  Current log# 2 seq# 245 mem# 0: +SYSDG/dbracdb/onlinelog/group_2.264.840562709
  Current log# 2 seq# 245 mem# 1: +SYSDG/dbracdb/onlinelog/group_2.265.840562727
 Tue Mar 25 12:59:20 2014
 Archived Log entry 315 added for thread 1 sequence 244 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 13:14:54 2014
 IPC Send timeout detected. Sender: ospid 6160700 [oracle@dbrac1 (LMS0)]
 Receiver: inst 2 binc 291585594 ospid 11010320
 IPC Send timeout to 2.1 inc 50 for msg type 65518 from opid 12
 Tue Mar 25 13:14:59 2014
 Communications reconfiguration: instance_number 2
 Tue Mar 25 13:15:01 2014
 IPC Send timeout detected. Sender: ospid 12452050 [oracle@dbrac1 (LMS1)]
 Receiver: inst 2 binc 291585600 ospid 11534636
 IPC Send timeout to 2.2 inc 50 for msg type 65518 from opid 13
 Tue Mar 25 13:15:22 2014
 IPC Send timeout detected. Sender: ospid 10682630 [oracle@dbrac1 (TNS V1-V3)]
 Receiver: inst 2 binc 50 ospid 6095056
 Tue Mar 25 13:15:25 2014
 Detected an inconsistent instance membership by instance 1
 Evicting instance 2 from cluster
 Waiting for instances to leave: 2
 Tue Mar 25 13:15:26 2014
 Dumping diagnostic data in directory=[cdmp_20140325131526], requested by (instance=2, osid=8192018 (LMD0)), summary=[abnormal instance termination].
 Tue Mar 25 13:15:42 2014
 Reconfiguration started (old inc 50, new inc 54)
 List of instances:
 1 (myinst: 1)
 ...
 Tue Mar 25 13:15:52 2014
 Archived Log entry 316 added for thread 2 sequence 114 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 13:15:53 2014
 ARC3: Archiving disabled thread 2 sequence 115
 Archived Log entry 317 added for thread 2 sequence 115 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 13:16:37 2014
 Thread 1 advanced to log sequence 246 (LGWR switch)
  Current log# 3 seq# 246 mem# 0: +SYSDG/dbracdb/onlinelog/group_3.266.840562735
  Current log# 3 seq# 246 mem# 1: +SYSDG/dbracdb/onlinelog/group_3.267.840562747
 Tue Mar 25 13:16:46 2014
 Decreasing number of real time LMS from 2 to 0
 Tue Mar 25 13:16:51 2014
 Archived Log entry 318 added for thread 1 sequence 245 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 13:20:50 2014
 IPC Send timeout detected. Sender: ospid 9306248 [oracle@dbrac1 (PING)]
 Receiver: inst 2 binc 291585377 ospid 2687058
 Tue Mar 25 13:30:08 2014
 Thread 1 advanced to log sequence 247 (LGWR switch)
  Current log# 1 seq# 247 mem# 0: +SYSDG/dbracdb/onlinelog/group_1.262.840562653
  Current log# 1 seq# 247 mem# 1: +SYSDG/dbracdb/onlinelog/group_1.263.840562689
 Tue Mar 25 13:30:20 2014
 Archived Log entry 319 added for thread 1 sequence 246 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 13:45:23 2014
 Thread 1 advanced to log sequence 248 (LGWR switch)
  Current log# 2 seq# 248 mem# 0: +SYSDG/dbracdb/onlinelog/group_2.264.840562709
  Current log# 2 seq# 248 mem# 1: +SYSDG/dbracdb/onlinelog/group_2.265.840562727
 
 節點2DB的alert日誌：
 Tue Mar 25 12:07:15 2014
 Archived Log entry 309 added for thread 2 sequence 112 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 12:22:22 2014
 Dumping diagnostic data in directory=[cdmp_20140325122222], requested by (instance=1, osid=7012828), summary=[incident=384673].
 Tue Mar 25 12:45:21 2014
 Thread 2 advanced to log sequence 114 (LGWR switch)
  Current log# 6 seq# 114 mem# 0: +SYSDG/dbracdb/onlinelog/group_6.274.840563009
  Current log# 6 seq# 114 mem# 1: +SYSDG/dbracdb/onlinelog/group_6.275.840563017
 Tue Mar 25 12:45:22 2014
 Archived Log entry 313 added for thread 2 sequence 113 ID 0xffffffff82080958 dest 1:
 Tue Mar 25 13:14:57 2014
 IPC Send timeout detected. Receiver ospid 11010320
 Tue Mar 25 13:14:57 2014
 Errors in file /oraclelog/diag/rdbms/dbracdb/dbracdb2/trace/dbracdb2_lms0_11010320.trc:
 IPC Send timeout detected. Receiver ospid 11534636 [
 Tue Mar 25 13:15:01 2014
 Errors in file /oraclelog/diag/rdbms/dbracdb/dbracdb2/trace/dbracdb2_lms1_11534636.trc:
 Tue Mar 25 13:15:25 2014
 LMS0 (ospid: 11010320) has detected no messaging activity from instance 1
 LMS0 (ospid: 11010320) issues an IMR to resolve the situation
 Please check LMS0 trace file for more detail.
 Tue Mar 25 13:15:25 2014
 Suppressed nested communications reconfiguration: instance_number 1
 Detected an inconsistent instance membership by instance 1
 Tue Mar 25 13:15:25 2014
 Received an instance abort message from instance 1
 Please check instance 1 alert and LMON trace files for detail.
 LMD0 (ospid: 8192018): terminating the instance due to error 481
 Tue Mar 25 13:15:26 2014
 ORA-1092 : opitsk aborting process
 Tue Mar 25 13:15:29 2014
 System state dump requested by (instance=2, osid=8192018 (LMD0)), summary=[abnormal instance termination].
 System State dumped to trace file /oraclelog/diag/rdbms/dbracdb/dbracdb2/trace/dbracdb2_diag_9699724_20140325131529.trc
 Instance terminated by LMD0, pid = 8192018
 

節點1的OSW PRVTNET日誌：
 zzz ***Tue Mar 25 13:12:19 BEIST 2014
 trying to get source for 192.168.100.1
 source should be 192.168.100.1
 traceroute to 192.168.100.1 (192.168.100.1) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  dbrac1-priv (192.168.100.1)  1 ms  0 ms  0 ms
 trying to get source for 192.168.100.2
 source should be 192.168.100.1
 traceroute to 192.168.100.2 (192.168.100.2) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  dbrac2-priv (192.168.100.2)  1 ms  0 ms *
 zzz ***Warning. Traceroute response is spanning snapshot intervals.
 zzz ***Tue Mar 25 13:12:31 BEIST 2014
 trying to get source for 192.168.100.1
 source should be 192.168.100.1
 traceroute to 192.168.100.1 (192.168.100.1) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  dbrac1-priv (192.168.100.1)  1 ms  0 ms  0 ms
 trying to get source for 192.168.100.2
 source should be 192.168.100.1
 traceroute to 192.168.100.2 (192.168.100.2) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  * * *
 2  * * *
 3  * dbrac2-priv (192.168.100.2)  0 ms *
 zzz ***Warning. Traceroute response is spanning snapshot intervals.
 zzz ***Tue Mar 25 13:13:17 BEIST 2014
 trying to get source for 192.168.100.1
 source should be 192.168.100.1
 traceroute to 192.168.100.1 (192.168.100.1) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  dbrac1-priv (192.168.100.1)  1 ms  0 ms  0 ms
 trying to get source for 192.168.100.2
 source should be 192.168.100.1
 traceroute to 192.168.100.2 (192.168.100.2) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  * * *
 2  * * *
 3  dbrac2-priv (192.168.100.2)  0 ms * *
 zzz ***Warning. Traceroute response is spanning snapshot intervals.
 zzz ***Tue Mar 25 13:14:04 BEIST 2014
 trying to get source for 192.168.100.1
 source should be 192.168.100.1
 traceroute to 192.168.100.1 (192.168.100.1) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  dbrac1-priv (192.168.100.1)  1 ms  0 ms  0 ms
 trying to get source for 192.168.100.2
 source should be 192.168.100.1
 traceroute to 192.168.100.2 (192.168.100.2) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  * * * <===============================註：*代表traceroute不成功，3個*代表執行了3次網路互動
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  dbrac2-priv (192.168.100.2)  0 ms  0 ms *
 zzz ***Warning. Traceroute response is spanning snapshot intervals.
 zzz ***Tue Mar 25 13:16:01 BEIST 2014  <====================================This snapshot is taken after 2 mins, OSW gap happened.
 trying to get source for 192.168.100.1
 source should be 192.168.100.1
 traceroute to 192.168.100.1 (192.168.100.1) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  dbrac1-priv (192.168.100.1)  1 ms  0 ms  0 ms
 trying to get source for 192.168.100.2
 source should be 192.168.100.1
 traceroute to 192.168.100.2 (192.168.100.2) from 192.168.100.1 (192.168.100.1), 30 hops max
 outgoing MTU = 1500
 1  * dbrac2-priv (192.168.100.2)  0 ms  0 ms

更多詳情見請繼續閱讀下一頁的精彩內容：

1 2 下一頁