DB2 pureScale 的新特性介绍 -- Group Crash Recovery
2010-06-16 00:00:00 来源:WEB开发网清单 6. M3 执行事务
export DB2NODE=2
connect to testdb,
update command options using c off,
insert into t1 values(5, 2),
commit,
insert into t1 values(30, 20),
接下来产生触发 Group Crash Recovery 的条件,比如断电,这里我们使用 killdbm。
清单 7. killdbm 命令
killdbm – killca
清单 8 来查询 Group Crash Recovery 后数据库表的结果。
清单 8. 查询结果
db2 => select * from t1
A B
----------- -----------
1 2
2 4
3 2
4 4
5 2
5 record(s) selected.
清单 9 显示了 db2diag 中关于 Group Crash Recovery 的信息。
清单 9. db2diag 的关于 Group Crash Recovery 的信息
2010-03-04-01.43.43.538263+480 I3980161E770 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:401
DATA #1 : <preformatted>
Group crash recovery started.
Recovery status for log stream 1
lowtranlsn: 000000000002E5C1
minbufflsn: 000000000002E5C4
headlsn: 000000000002E570
groupHeadLsn: 000000000002E570
groupMinBuffLSN: 000000000002E570
HeadExtentID: 0
GroupHeadExtentID: 0
nextLso: 4173825
nextLsn: 000000000002E56B
2010-03-04-01.43.43.547061+480 I3980932E771 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:400
DATA #1 : <preformatted>
Group crash recovery started.
Recovery status for log stream 0
lowtranlsn: 000000000002E5BD
minbufflsn: 000000000002E5C4
headlsn: 000000000002E570
groupHeadLsn: 000000000002E570
groupMinBuffLSN: 000000000002E570
HeadExtentID: 0
GroupHeadExtentID: 0
nextLso: 36781825
nextLsn: 0000000000000000
2010-03-04-01.43.43.555777+480 I3981704E770 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:402
DATA #1 : <preformatted>
Group crash recovery started.
Recovery status for log stream 2
lowtranlsn: 000000000002E5C4
minbufflsn: 000000000002E5C4
headlsn: 000000000002E570
groupHeadLsn: 000000000002E570
groupMinBuffLSN: 000000000002E570
HeadExtentID: 0
GroupHeadExtentID: 0
nextLso: 8347649
nextLsn: 0000000000000000
2010-03-04-01.43.43.608423+480 I3985671E797 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, data protection services,
sqlpSetRecoveryStartingPoint, probe:101
DATA #1 : <preformatted>
Set recovery starting point.
Recovery status for log stream 1
lowtranlsn: 000000000002E570
minbufflsn: 000000000002E570
headlsn: 000000000002E570
groupHeadLsn: 000000000002E570
groupMinBuffLSN: 0000000000000000
HeadExtentID: 0
GroupHeadExtentID: 0
nextLso: 4173825
nextLsn: 000000000002E570
2010-03-04-01.43.43.626339+480 I3986469E798 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, data protection services,
sqlpSetRecoveryStartingPoint, probe:100
DATA #1 : <preformatted>
Set recovery starting point.
Recovery status for log stream 0
lowtranlsn: 000000000002E570
minbufflsn: 000000000002E570
headlsn: 000000000002E570
groupHeadLsn: 000000000002E570
groupMinBuffLSN: 0000000000000000
HeadExtentID: 0
GroupHeadExtentID: 0
nextLso: 36781825
nextLsn: 000000000002E570
2010-03-04-01.43.43.635045+480 I3987268E797 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, data protection services,
sqlpSetRecoveryStartingPoint, probe:102
DATA #1 : <preformatted>
Set recovery starting point.
Recovery status for log stream 2
lowtranlsn: 000000000002E570
minbufflsn: 000000000002E570
headlsn: 000000000002E570
groupHeadLsn: 000000000002E570
groupMinBuffLSN: 0000000000000000
HeadExtentID: 0
GroupHeadExtentID: 0
nextLso: 8347649
nextLsn: 000000000002E570
2010-03-04-01.43.47.247910+480 E4053435E467 LEVEL: Info
PID : 17993 TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24
EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3110
MESSAGE : ADM1528I Group crash recovery has completed successfully.
2010-03-04-01.43.47.262001+480 I4053903E478 LEVEL: Info
PID : 17993
TID : 47441067895104 KTID : 18157
PROC : db2sysc 1
INSTANCE: wucuixia NODE : 001 DB : TESTDB
APPHDL : 1-55 APPID: *N1.DB2.100303174336
EDUID : 24 EDUNAME: db2agnti (TESTDB ) 1
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:3170
DATA #1 : <preformatted>
Crash recovery completed. Next LSN is 000000000002E5CB
结束语
本文简单的对 DB2 pureScale 的结构进行了描述,并重点介绍了新特性 Group Crash Recovery 新特性,并使用 DB2 V9.8 做了简单的实例说明。
- ››db2 对float类型取char后显示科学计数法
- ››DB2中出现SQL1032N错误现象时的解决办法
- ››DB2 锁升级示例
- ››db2诊断系列之---定位锁等待问题
- ››db2 命令选项解释
- ››DB2 最佳实践: 使用 DB2 pureXML 管理 XML 数据的...
- ››DB2 9.5 SQL Procedure Developer 认证考试 735 准...
- ››DB2 9.5 SQL Procedure Developer 认证考试 735 准...
- ››DB2 9.5 SQL Procedure Developer 认证考试 735 准...
- ››DB2 基础: 表空间和缓冲池
- ››DB2 XML 编程,第 1 部分: 理解 XML 数据模型
- ››DB2 pureScale 实战
更多精彩
赞助商链接