|
Problem IT30821
|
Status: Closed |
AUTOMATIC REORG MAY NOT WORK IF MAXOFFLINEREORGTABLESIZE IS SPECIFIED IN REORG POLICY
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Automatic reorg may not work due to error:
TABLE EXCEEDS OFFLINE REORG SIZE CRITERIA
This error is a consequence of erroneous reorg evaluation being
done by heath monitor.
It may happen when maxOfflineReorgTableSize is specified
in the reorg policy regardless of table size chosen.
Example auto reorg policy causing the issue:
TYPE IN ('S', 'T') AND TABNAME
!='LOCKEVENTS_LOCKEVMON' |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Fixed in Db2 11.1 or later *
**************************************************************** |
| Local Fix: |
Do not use maxOfflineReorgTableSize attribute |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Fixed in Db2 11.1 or later *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.11.2019
14.01.2021
14.01.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
