|
Problem IC83469
|
Status: Closed |
INCORRECT RESULTS AFTER LOAD INTO TABLE WITH CONSTRAINTS FOLLOWED BY ATTACH OR DETACH |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
This APAR fixes the following two related problems:
1. The first problem occurs after loading into a table with
constraints and then attaching that table to a partitioned table
before using SET INTEGRITY on the standalone table to validate
the newly loaded data. All rows from the newly attached
partition should be visible after running SET INTEGRITY on the
partitioned table, however, the newly loaded rows are not
visible when using an index scan. To hit this problem there
must be one or more partitioned indexes on the range partitioned
table, and the source table to attach has a matching index for
each partitioned index on the target range partitioned table.
1b. Further, if a new partitioned index is created before
running SET INTEGRITY on the partitioned table, then the loaded
keys will, incorrectly not be included in the new index on the
newly attached partition. This is a problem regardless of
whether or not the partitioned indexes exist on the range
partitioned table prior to attach.
2. The second problem occurs after loading into a partitioned
table with constraints, not running SET INTEGRITY and then
detaching one of the partitions. All rows from the detach
partition (i.e. the newly created standalone table) should be
visible, however, the newly loaded rows are not visible when
using an index scan. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.1. *
**************************************************************** |
| Local Fix: |
To make the loaded data visible, the user can either:
- execute another load that loads data into the problem
partition
- OR execute the REORG INDEXES ALL command
In order to fix the corrupted index problem mentioned in 1b, the
user must execute the REORG INDEXES ALL command. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 version 10.1.0.1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.05.2012
13.09.2012
13.09.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
