|
Problem IC75709
|
Status: Closed |
DATABASE MARKED BAD DUE TO AN UNEXPECTED LOG FILE FULL ERROR WHEN DB2AGENT IS TRYING TO FLUSH LOG RECORDS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Under certain workload conditions, when the SOFTMAX is set to
too large, i.e SOFTMAX=600 and LOGPRIMARY=6 resulting in
minbufflsn moving up too slow, in some condition before db2agent
is trying to write log record, it incorrectly calculates the
required log space which will not trigger loggr to create new
log files. When db2agent writes log records, it may find there
are no log files which can be reused or renamed for new log
records. Then db2 will be panic due to logging cannot be
continued.
Similar entries may be wriiten to db2diag.log:
2011-03-07-11.56.36.793874+540 I4060823A439 LEVEL: Severe
PID : 7209444 TID : 6974 PROC : db2sysc
0
INSTANCE: inst1 NODE : 000
EDUID : 6974 EDUNAME: db2loggw (DB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgwlp,
probe:1472
RETCODE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.
2011-03-07-11.56.36.830900+540 I4063828A512 LEVEL: Severe
PID : 7209444 TID : 28672 PROC : db2sysc
0
INSTANCE: inst1 NODE : 000 DB : DB1
APPHDL : 0-6849 APPID:
10.107.30.21.46633.110306192323
AUTHID : authid1
EDUID : 28672 EDUNAME: db2agent (DB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpWriteToLog,
probe:3770
RETCODE : ZRC=0x870F0151=-2029059759=SQLO_WP_TERM
"The waitpost area has been terminated"
2011-03-07-11.56.36.831108+540 I4064341A509 LEVEL: Error
PID : 7209444 TID : 28672 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : GACP
APPHDL : 0-6849 APPID:
10.107.30.21.46633.110306192323
AUTHID : GACDBMGR
EDUID : 28672 EDUNAME: db2agent (GACP) 0
FUNCTION: DB2 UDB, data protection services, sqlpWriteLR,
probe:13130
MESSAGE : ZRC=0x870F0151=-2029059759=SQLO_WP_TERM
"The waitpost area has been terminated" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* see problem description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 v97 fix pack 5 or newer *
**************************************************************** |
| Local Fix: |
decrease SOFTMAX to a proper value |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem First Fixed in DB2 Version 9.7 Fix Pack 5 |
| Workaround |
decrease SOFTMAX to a proper value |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.04.2011
16.11.2011
13.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
