|
Problem IT37326
|
Status: Closed |
TOTAL_LOG_USED MONITOR ELEMENT SHOW UNREASONABLY HIGH VALUE
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
This problem occurs when the LOGFILSIZ database configuration
parameter is set to 1053721 or higher.
User may notice a very high value of the TOTAL_LOG_USED
under monitor function mon_get_transaction_log(). The usage
value reported is much higher than the actual use, and over time
it gets worse.
The trigger for the incorrect tracking of log space usage is by
and ONLINE BACKUP operation, or ARCHIVE LOG command,
which truncates the current log file.
This is not just an incorrect reporting problem. It can also
cause
transactions to fail with SQL0964N error when there should be
sufficient log space to contain the workload.
Deactivate the database can resolve the incorrect tracking of
log space. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description above *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 11.1 Mod 4 Fix Pack 7 *
**************************************************************** |
| Local Fix: |
Deactivate the database can resolve the incorrect tracking of
log space.
Configuring LOGFILSIZ database configuration parameter to a
value smaller than 1053721 can avoid this problem. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description above *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 11.1 Mod 4 Fix Pack 7 *
**************************************************************** |
| Comment |
First fixed in DB2 Version 11.1 Mod 4 Fix Pack 7 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.06.2021
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) |
