|
Problem IT39320
|
Status: Closed |
STALE VALUE OF LOG_EXTRACTION_DISK_SPACE_USED_TOTAL WITH ADVANCED LOG SPACE MANAGEMENT ENABLED
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Starting from Db2 Version 11.5 Mod Pack 6, with Advanced Log
Space Management enabled, it is possible for
MON_GET_TRANSACTION_LOG table function to return a stale value
for LOG_EXTRACTION_DISK_SPACE_USED_TOTAL when first active log
file moves up after a long running transaction has
committed/rolled back.
For example, we have a long running transaction producing
extraction files:
db2 "select LOG_EXTRACTION_LAST_EXTRACTED_LOG as
LAST_EXTRACTED_LOG , CURRENT_ACTIVE_LOG , FIRST_ACTIVE_LOG ,
LAST_ACTIVE_LOG, LOG_EXTRACTION_DISK_SPACE_USED_TOTAL FROM
TABLE( MON_GET_TRANSACTION_LOG( -1 ) ) AS T"
LAST_EXTRACTED_LOG CURRENT_ACTIVE_LOG FIRST_ACTIVE_LOG
LAST_ACTIVE_LOG LOG_EXTRACTION_DISK_SPACE_USED_TOTAL
-------------------- -------------------- --------------------
-------------------- ------------------------------------
25 29 17
30 140560
1 record(s) selected.
$ ls
S0000021.LOG S0000030.LOG
X0000021_TID0000000000000177_0000.LOG
S0000022.LOG X0000017.META
X0000022.META
S0000023.LOG X0000017_TID000000000000015B_0000.LOG
X0000022_TID0000000000000177_0000.LOG
S0000024.LOG X0000018.META
X0000023.META
S0000025.LOG X0000019.META
X0000023_TID0000000000000177_0000.LOG
S0000026.LOG X0000019_TID0000000000000177_0000.LOG
X0000024.META
S0000027.LOG X0000020.META
X0000024_TID0000000000000177_0000.LOG
S0000028.LOG X0000020_TID0000000000000177_0000.LOG
X0000025.META
S0000029.LOG X0000021.META
X0000025_TID0000000000000177_0000.LOG
After the long running transaction has been committed/rolled
back and all corresponding extraction files have been removed,
LOG_EXTRACTION_DISK_SPACE_USED_TOTAL should reduce back to 0 but
it remains stale:
LAST_EXTRACTED_LOG CURRENT_ACTIVE_LOG FIRST_ACTIVE_LOG
LAST_ACTIVE_LOG LOG_EXTRACTION_DISK_SPACE_USED_TOTAL
-------------------- -------------------- --------------------
-------------------- ------------------------------------
25 29 29
38 19424
1 record(s) selected.
$ ls
S0000029.LOG S0000031.LOG S0000033.LOG S0000035.LOG
S0000037.LOG
S0000030.LOG S0000032.LOG S0000034.LOG S0000036.LOG
S0000038.LOG |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Advanced Log Space Management Enabled. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Advanced Log Space Management Enabled. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Comment |
Problem was first fixed in Db2 Version 11.5.8.0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.12.2021
27.05.2022
27.05.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
