AIX RAC9I 節點當機測試
SQL> select * from gv$instance;
INST_ID INSTANCE_NUMBER INSTANCE_NAME HOST_ VERSION STARTUP_T STATUS PAR THREAD# ARCHIVE LOG_SWITCH_
---------- --------------- ---------------- ----- ----------------- --------- ------------ --- ---------- ------- -----------
LOGINS SHU DATABASE_STATUS INSTANCE_ROLE ACTIVE_ST
---------- --- ----------------- ------------------ ---------
2 2 rac2 P61B 9.2.0.8.0 11-MAY-09 OPEN YES 2 STOPPED
ALLOWED NO ACTIVE PRIMARY_INSTANCE NORMAL
1 1 rac1 P61A 9.2.0.8.0 11-MAY-09 OPEN YES 1 STOPPED
ALLOWED NO ACTIVE PRIMARY_INSTANCE NORMAL
SQL> select inst_id,open_mode from gv$database;
INST_ID OPEN_MODE
---------- ----------
1 READ WRITE
2 READ WRITE
直接通過電源鍵關閉P61B
Mon May 11 21:22:01 2009
Reconfiguration started (old inc 5, new inc 6)
List of nodes:
0
Global Resource Directory frozen
one node partition
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Resources and enqueues cleaned out
Resources remastered 622
634 GCS shadows traversed, 0 cancelled, 38 closed
429 GCS resources traversed, 0 cancelled
3809 GCS resources on freelist, 4208 on array, 4208 allocated
set master node info
Submitted all remote-enqueue requests
Update rdomain variables
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
634 GCS shadows traversed, 0 replayed, 38 unopened
Submitted all GCS remote-cache requests
0 write requests issued in 596 GCS resources
1 PIs marked suspect, 0 flush PI msgs
Mon May 11 21:22:01 2009
Reconfiguration complete
Post SMON to start 1st pass IR
Mon May 11 21:22:01 2009
Instance recovery: looking for dead threads
Mon May 11 21:22:01 2009
Beginning instance recovery of 1 threads
Mon May 11 21:22:01 2009
Started redo scan
Mon May 11 21:22:01 2009
Completed redo scan
100 redo blocks read, 32 data blocks need recovery
Mon May 11 21:22:01 2009
Started recovery at
Thread 2: logseq 4, block 2, scn 0.148534
Mon May 11 21:22:01 2009
Recovery of Online Redo Log: Thread 2 Group 4 Seq 4 Reading mem 0
Mem# 0 errs 0: /dev/rtrac_redo2_21
Mon May 11 21:22:01 2009
Completed redo application
Mon May 11 21:22:01 2009
Ended recovery at
Thread 2: logseq 4, block 102, scn 0.168687
31 data blocks read, 34 data blocks written, 100 redo blocks read
Ending instance recovery of 1 threads
SMON: about to recover undo segment 11
SMON: mark undo segment 11 as available
SMON: about to recover undo segment 12
SMON: mark undo segment 12 as available
SMON: about to recover undo segment 13
SMON: mark undo segment 13 as available
SMON: about to recover undo segment 14
SMON: mark undo segment 14 as available
SMON: about to recover undo segment 15
SMON: mark undo segment 15 as available
SMON: about to recover undo segment 16
SMON: mark undo segment 16 as available
SMON: about to recover undo segment 17
SMON: mark undo segment 17 as available
SMON: about to recover undo segment 18
SMON: mark undo segment 18 as available
SMON: about to recover undo segment 19
SMON: mark undo segment 19 as available
SMON: about to recover undo segment 20
SMON: mark undo segment 20 as available
幾乎是立即就查覺到了P61B當機,馬上把P61B踢出
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/8242091/viewspace-594779/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- AIX RAC9I 心跳線斷掉測試AI
- AIX RAC9I 心跳線斷掉測試(續)AI
- AIX RAC9i 節點2啟動時遭遇到7445錯誤AI
- 網上有提供AIX的測試機AI
- 軟體測試:DOM節點
- DRM特性引起的RAC節點當機
- Postgrsql 從節點當機,主節點執行DML語句出現等待情況SQL
- 一次RAC節點當機的解決過程
- AIX6.1系統11203RAC節點down機AI
- oracle11gR2 RAC 環境測試修改節點VIP的測試操作記錄Oracle
- oracle 11.2.0.4 rac節點異常當機之ORA-07445Oracle
- asm例項自動dismount導致rac一個節點當機ASM
- RAC一個節點記憶體故障當機,無法訪問記憶體
- Oracle9204 RAC 節點2當機後5小時重新啟動找不到節點1上例項Oracle
- 11G RAC 一節點當機後修改監聽相關配置使通過當機節點VIP連線資料庫的客戶端可以連線資料庫客戶端
- Hadoop2.2.0多節點分散式安裝及測試Hadoop分散式
- Service使用referred和avileable固定會話到一個節點,當機後會切換到另一個節點會話
- redis測試點Redis
- DataNode工作機制 & 新增節點 &下線節點
- TiDB3.0.2版本某業務TiKV當機測試TiDB
- 【AIX】AIX中級試題AI
- 軟體穩定性測試的測試點
- 使用kubeadm搭建一單節點k8s測試叢集K8S
- Tungsten Fabric知識庫丨測試2000個vRouter節點部署VR
- AIX試題AI
- 當前測試工作使用工具列表
- 當前主流的單元測試工具
- ORACLE 11.2.0.4 rac for linux 鏈路宕導致的單節點異常當機OracleLinux
- RAC系統當中,job在哪個節點執行?
- 手機應用軟體測試的思路與要點
- APP測試設計測試用例的要點APP
- 功能測試點總結
- ios APP 測試思考點iOSAPP
- 記:僅配置單vip連線串,當vip對應的節點down機情況下程式無法連線上正常節點的故障
- 因為主機時間不同步導致的hbase zookeeper 節點當機奔潰 一例
- AIX下的壓縮測試及所有壓縮命令AI
- aix小試牛刀AI
- ADAMoracle預言機節點需衡量節點伺服器安全性Oracle伺服器