home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT02442 Status: Closed

DB2PD -REORG MIGHT SHOW INCORRECT REORG END TIME FOR PARTITIONED TABLES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When reorg is run on one partition of a partitioned table (ON 
DATA 
PARTITION clause) the reorg end time is updated for all 
partitions, including those which were not reorganized. 
 
If reorg is run on all partitions, the reorg end time gets 
updated 
only when the last partition is finished (hence the end time is 
the 
same for all partitions). 
 
Reorg end time can be checked by db2pd tool using -reorg switch. 
 
Example: 
# reorg on all partitions 
$ db2  "reorg table my_partitioned" 
$ db2pd -reorg -db sample 
[...] 
Table Reorg Stats: 
Address            TableName          Start               End 
[...] Status 
0x0700000044147CA8 MY_PARTITIONED     01/22/2014 05:53:54 
01/22/2014 05:53:59  [...] Done 
0x0700000044148FA8 MY_PARTITIONED     01/22/2014 05:53:58 
01/22/2014 05:53:59  [...] Done 
0x07000000441469A8 MY_PARTITIONED     01/22/2014 05:53:54 
01/22/2014 05:53:59  [...] Done 
 
# reorg on one partition 
$ db2 "reorg table my_partitioned on data partition PART1" 
$ db2pd -reorg -db sample 
[...] 
Address            TableName          Start               End 
[...] Status 
0x0700000044147CA8 MY_PARTITIONED     01/22/2014 05:56:40 
01/22/2014 05:56:43  [...] Done 
0x0700000044148FA8 MY_PARTITIONED     01/22/2014 05:53:58 
01/22/2014 05:56:43  [...] Done 
0x07000000441469A8 MY_PARTITIONED     01/22/2014 05:53:54 
01/22/2014 05:56:43  [...] Done 
 
As we can see, end time was updated for all partitions despite 
the fact that reorg was run only on partition 1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher.            * 
****************************************************************
Local Fix:
Actual time of REORG end can be verified using LIST HISTORY 
command: 
$ db2 LIST HISTORY REORG CONTAINING "<SCHEMA>.<TABLE>" FOR 
<DB_NAME>
Solution
Problem first fixed in DB2 version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.06.2014
26.07.2015
26.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList