資料庫日誌中Immediate Kill Session錯誤解決方法

paulyibinyi發表於2010-06-23

        環境:hp_unix  + oracle 10.2.0.3 rac

   客戶一套rac資料庫日誌中節點1日誌錯誤如下:

ALTER SYSTEM SET service_names='' SCOPE=MEMORY SID='ORCL1';
...
Immediate Kill Session#: 1606, Serial#: 23
Immediate Kill Session: sess: 0x447e141c0 OS pid: 21802
Immediate Kill Session#: 1607, Serial#: 25
Immediate Kill Session: sess: 0x446e27580 OS pid: 21751
Immediate Kill Session#: 1608, Serial#: 32
Immediate Kill Session: sess: 0x447e15670 OS pid: 21804
Immediate Kill Session#: 1610, Serial#: 56
Immediate Kill Session: sess: 0x447e16b20 OS pid: 20036
Immediate Kill Session#: 1611, Serial#: 21
Immediate Kill Session: sess: 0x446e29ee0 OS pid: 19893
...
ALTER SYSTEM SET service_names='ORCL' SCOPE=MEMORY SID='ORCL1';

從上面資訊可以看出,連線在節點1上的會話全部被kill掉,這個時候檢視作業系統日誌

Jun 17 07:25:18 sbka cmnetd[6358]: lan1 failed
Jun 17 07:25:18 sbka cmnetd[6358]: lan1 switching to lan2
Jun 17 07:25:18 sbka cmnetd[6358]: Subnet 17.16.6.0 switching from lan1 to lan2
Jun 17 07:25:18 sbka cmnetd[6358]: Subnet 17.16.6.0 switched from lan1 to lan2
Jun 17 07:25:18 sbka cmnetd[6358]: lan1 switched to lan2
Jun 17 07:25:18 sbka cmcld[6350]: Local switch has occurred since net_id 0x3 was not found on subnet 172.16.6.0.
Jun 17 07:25:58 sbka cmnetd[6358]: lan1 recovered
Jun 17 07:25:58 sbka cmnetd[6358]: Subnet 17.16.6.0 switching from lan2 to lan1
Jun 17 07:25:58 sbka cmnetd[6358]: Subnet 17.16.6.0 switched from lan2 to lan1
Jun 17 07:25:58 sbka cmnetd[6358]: lan2 switched to lan1

繫結在lan1公網的vip 地址發生漂移,導致節點1上的所有會話轉移到節點2上,應用連線正常

但這時資料庫日誌不應該報這些錯誤,透過查metalink ID為730315.1

要解決這個報錯資訊,以下兩種解決方法:

 第一.升級到10.2.0.5

 第二.修改service_name,不要和db_name名稱相同。

 

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7199859/viewspace-665998/,如需轉載,請註明出處,否則將追究法律責任。

相關文章