|
Problem IC65349
|
Status: Closed |
NO ERROR DURING LOAD WHEN PARTITIONING KEY OF EXCEPTION TABLE DOESN'T MATCH LOAD TABLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
A partitioning key on the exception table needs to match the
load table.
If for instance the load table has partitioning key
distribute by hash ( col1, col2, col3 )
and the exception table only has :
distribute by hash ( col1 )
Then db2 will currently allow this, leading to an incorrect
hashing of rows into the exception table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Load users with partitioned tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* Exception table created by load may return wrong results *
* ifthe exception table was created with a *
* differentpartitioning key. *
****************************************************************
* RECOMMENDATION: *
* Partitioning key for the exception table needs to be thesame *
* as the table that is loaded.The fix for this APAR will *
* return an error if this is notthe case. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
This problem was first fixed in V9.1 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65398 IC65399
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.12.2009
22.04.2010
22.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
