|
Problem IC82103
|
Status: Closed |
FILTERCLAUSE IN AUTO_REORG POLICY IS IGNORED IF POLICY ATTRIBUTES RECLAIMEXTENTSSIZEFORMDCTABLES IS SPECIFIED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
With AUTO_REORG automatic table maintance if you specify in the
policy the 'reclaimExtentsSizeForMDCTables' attribute together
with 'maxOfflineReorgTableSize' will cause any FilterClause to
be ignored.
This will cause potentially all tables to be evaluated for
automatic reorg, despite you may have tried to exclude some of
them with a FilterClause. You eventually may see tables getting
reorg'ed in db2diag.log which should not have been considered
due the FilterClause.
This issue happens only when the policy has the
'reclaimExtentsSizeForMDCTables' attribute specified together
with the 'maxOfflineReorgTableSize' attribute. Note: specifying
the 'reclaimExtentsSizeForMDCTables' or
'maxOfflineReorgTableSize' attribute alone will not cause a
problem. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 6. *
**************************************************************** |
| Local Fix: |
If possible remove the 'reclaimExtentsSizeForMDCTables'
attribute from the
policy. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 9.7 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.03.2012
18.06.2012
18.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
