DB2 - Problem description
Problem IT33252 | Status: Closed |
AUTOMATIC TABLE MAINTENANCE REORG RECLAIM EXTENTS OPERATIONS ON QUALIFYING ITC TABLES MAY NOT GET TRIGGERED AFTER A DB RESTART | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The Automatic Table Maintenance evaluation of INSERT TIME CLUSTERED (ITC) Tables uses a methodology of first performing a partial evaluation of the table by checking the number of ROWS DELETED for the table (via MON_GET_TABLE), and only when the number of rows deleted meets a specific threshold, then a full evaluation using ADMIN_GET_TAB_INFO() is performed. This methodology is meant to reduce the frequency of unnecessary executions of ADMIN_GET_TAB_INFO() for ITC tables, which can be expense operations on ITC tables in terms of CPU utilization and locking impact to other applications which are accessing the ITC table. If rows are deleted from an ITC table, and, prior to the next automatic maintenance evaluation period, the database is recycled/restarted, then it is possible that an ITC table which is eligible for reorg-reclaim-extents (because of the rows that had been deleted prior to the database restart) is not identified as eligible for reorg. Only after subsequent delete activity on this table might it be identified as eligible for reorg. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 Version 11.1 Mod 4 Fix Pack 6. * **************************************************************** | |
Local Fix: | |
- The ITC will eventually qualify for reorg after subsequent delete activity on the table and future Automatic Table Maintenance evaluations. - Or, you can manually perform a REORG ... RECLAIM EXTENTS operation on the table(s). | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.06.2020 16.03.2021 16.03.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |