DB2 - Problem description
|Problem IC62148||Status: Closed|
REORG MONITOR REPORTS INCORRECT MAX COUNT FOR BUILD PHASE WHEN INTRA_PARALLEL IS ON
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Reorg monitoring feature (available in DB2 version 9.1 Fixpack 8) reports the progress of index reorganization. For build phase the progress indicators are: the current record being processed (Cur Count) and the maximum number of records to process (Max Count). The Max Count for build phase is collected during the scan-sort phase. When the registry variable INTRA_PARALLEL is enabled, and the index has more than 200 nodes, the index creation will use parallel agents to perform scanning and sorting. During this parallel index creation the code sets Max Count variable too early and starts the build phase prematurely. The problem does not occur with serial index build which is the default index creation method. Users will observe incorrect Max Count value (e.g. that is less that Cur Count) and possibly incorrect Cur Count value, as well.
During the parallel index creation the code which sets the Max Count variable executes too early and starts the build phase prematurely (i.e., without waiting for all sort agents to return).
Setting the registry variable INDEXSORT to NO will bypass parallel index creation; however, it may have impact on reorg performance.
|available fix packs:|
The fix is to serialize the actions proparly such that the monitoring code will wait for all sort agents to finish before updating the Max Count counter and starting the build phase.
not known / see Local fix
Date - problem reported : Date - problem closed : Date - last modified :
22.07.2009 10.11.2009 10.11.2009
|Problem solved at the following versions (IBM BugInfos)|
|Problem solved according to the fixlist(s) of the following version(s)|