|
Problem IT39754
|
Status: Closed |
LOCKING EVENT MONITOR "DROPPED RECORD" EVENT LEADS TO THE FLOOD OF DB2DIAG.LOG WARNING MESSAGES
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When a LOCKING event monitor is active, it is possible during a
period when MON_HEAP memory isn't available for a "dropped
record" probe to occur. When this occurs the probe keeps
reoccurring and flooding the db2diag.log
A sample probe is the following:
2021-12-21-07.25.47.184568-300 E410844623E619 LEVEL:
Warning
PID : 45331 TID : 140716403582720 PROC :
db2sysc 0
INSTANCE: xxxxxxxx NODE : 000 DB :
xxxxxxx
APPHDL : 0-143 APPID: *LOCAL.DB2.2X1205XXXX15
AUTHID : xxxxx HOSTNAME: xxxxxxxxxxxxxxxx
EDUID : 334 EDUNAME: db2fw12 (xxxxxx) 0
FUNCTION: DB2 UDB, database monitor,
sqmFastWriterManager::processDroppedRecords, probe:10
DATA #1 :
Event monitor has 161 dropped records
Start time: 12/15/2021 01:18:16.307628
End time: 12/19/2021 07:30:44.545009
The probes will stop when the database is deactivated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2v11.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* Locking Event Monitor ?dropped record? event does not get *
* cleaned up properly leading to the the following probe *
* flooding db2diag.log *
* 2021-12-21-07.25.47.184568-300 E410844623E619 LEVEL: *
* Warning *
* PID : 45331 TID : 140716403582720 PROC : *
* db2sysc 0 *
* INSTANCE: xxxxxxxx NODE : 000 DB : *
* xxxxxxx *
* APPHDL : 0-143 APPID: *
* *LOCAL.DB2.211205083315 *
* AUTHID : xxxxx HOSTNAME: xxxxxxxxxxxxxxxx *
* EDUID : 334 EDUNAME: db2fw12 (xxxxxx) 0 *
* FUNCTION: DB2 UDB, database monitor, *
* sqmFastWriterManager::processDroppedRecords, probe:10 *
* DATA #1 : *
* Event monitor has 161 dropped records *
* Start time: 12/15/2021 01:18:16.307628 *
* End time: 12/19/2021 07:30:44.545009 *
* The probes will stop when the database is deactivated. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.1.4.7 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Db2v11.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* Locking Event Monitor ?dropped record? event does not get *
* cleaned up properly leading to the the following probe *
* flooding db2diag.log *
* 2021-12-21-07.25.47.184568-300 E410844623E619 LEVEL: *
* Warning *
* PID : 45331 TID : 140716403582720 PROC : *
* db2sysc 0 *
* INSTANCE: xxxxxxxx NODE : 000 DB : *
* xxxxxxx *
* APPHDL : 0-143 APPID: *
* *LOCAL.DB2.211205083315 *
* AUTHID : xxxxx HOSTNAME: xxxxxxxxxxxxxxxx *
* EDUID : 334 EDUNAME: db2fw12 (xxxxxx) 0 *
* FUNCTION: DB2 UDB, database monitor, *
* sqmFastWriterManager::processDroppedRecords, probe:10 *
* DATA #1 : *
* Event monitor has 161 dropped records *
* Start time: 12/15/2021 01:18:16.307628 *
* End time: 12/19/2021 07:30:44.545009 *
* The probes will stop when the database is deactivated. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.1.4.7 *
**************************************************************** |
| Comment |
Upgrade to 11.1.4.7 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.01.2022
17.04.2022
17.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
