DB2 - Problem description
Problem IT37382 | Status: Closed |
TOTAL_LOG_USED INCREASE GRADUALLY TO AN UNREAL VALUE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The issue that was reported was a very high value for TOTAL_LOG_USED from mon_get_transaction_log() reported. The customer is complaining about some inconsistency in the monitoring data for the transaction log. They collected data from MON_GET_TRANSACTION_LOG() and found TOTAL_LOG_USED to be in the range of 220 - 230gb. This is collected with (but also seen in database snapshot): select * from table( select * from ( values ( cast(current timestamp as varchar(26)) ) ) as v ( collection_timestamp ) ) as x, (select * from table( mon_get_transaction_log(-2) )) as t; | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5 FP 7 or later * **************************************************************** | |
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 * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5 FP 7 or later * **************************************************************** | |
Comment | |
Upgrade to 11.5 FP 7 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.06.2021 21.11.2021 21.11.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |