|
Problem IT30826
|
Status: Closed |
AUTOMATIC REORG MAY NOT WORK IF MAXOFFLINEREORGTABLESIZE IS SPECIFIED IN REORG POLICY
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - 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 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply v11.5.6.0 to Db2 Server *
**************************************************************** |
| Local Fix: |
Do not use maxOfflineReorgTableSize attribute |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply v11.5.6.0 to Db2 Server *
**************************************************************** |
| Comment |
First fixed in v11.5.6.0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2019
23.08.2021
23.08.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
