真是怪事情,大俠們看看是怎么回事情,急死了!

tcpip8008

db2 診斷日至顯示：
2004-04-05-18.22.05.653965   Instance:hbbiinst   Node:004
PID:15531(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102128
data_protection  sqlpgrsp   Probe:50   Database:HBBIDB

Log Full -- active log held by appl. handle 566
End this application by COMMIT, ROLLBACK or FORCE APPLICATION.

2004-04-05-18.22.05.683442   Instance:hbbiinst   Node:004
PID:15531(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102128
data_protection  sqlpWriteLR   Probe:80   Database:HBBIDB
DIA3609C Log file was full.

ZRC=0xFFFFD509

2004-04-05-18.22.44.931941   Instance:hbbiinst   Node:004
PID:20544(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102206
data_protection  sqlpgrsp   Probe:50   Database:HBBIDB

Log Full -- active log held by appl. handle 566
End this application by COMMIT, ROLLBACK or FORCE APPLICATION.

2004-04-05-18.22.44.960785   Instance:hbbiinst   Node:004
PID:20544(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102206
data_protection  sqlpWriteLR   Probe:80   Database:HBBIDB
DIA3609C Log file was full.

ZRC=0xFFFFD509

2004-04-05-18.23.21.034610   Instance:hbbiinst   Node:004
PID:20327(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102246
data_protection  sqlpgrsp   Probe:50   Database:HBBIDB

Log Full -- active log held by appl. handle 566
End this application by COMMIT, ROLLBACK or FORCE APPLICATION.

2004-04-05-18.23.21.062584   Instance:hbbiinst   Node:004
PID:20327(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102246
data_protection  sqlpWriteLR   Probe:80   Database:HBBIDB
DIA3609C Log file was full.

ZRC=0xFFFFD509

2004-04-05-18.23.56.112550   Instance:hbbiinst   Node:004
PID:2359(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102322
data_protection  sqlpgrsp   Probe:50   Database:HBBIDB

Log Full -- active log held by appl. handle 566
End this application by COMMIT, ROLLBACK or FORCE APPLICATION.

2004-04-05-18.23.56.139780   Instance:hbbiinst   Node:004
PID:2359(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102322
data_protection  sqlpWriteLR   Probe:80   Database:HBBIDB
DIA3609C Log file was full.

ZRC=0xFFFFD509

2004-04-05-18.24.38.168765   Instance:hbbiinst   Node:004
PID:15531(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102357
data_protection  sqlpgrsp   Probe:50   Database:HBBIDB

Log Full -- active log held by appl. handle 566
End this application by COMMIT, ROLLBACK or FORCE APPLICATION.

2004-04-05-18.24.38.196543   Instance:hbbiinst   Node:004
PID:15531(db2agntp (DWDB) 4)   Appid:*N6.hbbiinst.040405102357
data_protection  sqlpWriteLR   Probe:80   Database:HBBIDB
DIA3609C Log file was full.

ZRC=0xFFFFD509

可是通過df -k 查勘的時候發(fā)現(xiàn)空間的利用率不倒60％ ，這是怎么回事情？有遇到過這種情況的兄弟么？

SandBeach_SunSh

不是你地日志FS空間不足，是db cfg中你地主要的active log數(shù)量設(shè)地太小了，或者你地logfile size太小了；一個事務(wù)就把他們?nèi)麧M啦！

trick

肯定有大INSERT,UPDATE,DELETE操作導(dǎo)致LOG不夠?qū)?/td>

hujingyu

更改數(shù)據(jù)庫的參數(shù)
db2 update db cfg for <db_name>; using logfilsiz 10000 logprimary 10 logsecond 100

dreamings

[quote]原帖由 "SandBeach_SunShine"]不是你地日志FS空間不足，是db cfg中你地主要的active log數(shù)量設(shè)地太小了，或者你地logfile size太小了；一個事務(wù)就把他們?nèi)麧M啦！[/quote 發(fā)表：


我想也是這樣，可以設(shè)大一點logfile的大�。海�