DB2 - Problem description
Problem IC65399 | Status: Closed |
NO ERROR DURING LOAD WHEN PARTITIONING KEY OF EXCEPTION TABLE DOESN'T MATCH LOAD TABLE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 | |
Solution | |
This problem was first fixed in V9.7 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.01.2010 22.04.2010 22.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.9 | |
9.7.0.2 |