DB2 - Problem description
Problem IT35925 | Status: Closed |
DISTRIBUTION KEY ORDER IS NOT INHERITED FROM THE AS-RESULT-TABLEWHEN COISBAR IS ENABLED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The distribution key order may be invalid when a table is created based on a SELECT and COISBAR is enabled for this table. For example: CREATE SCHEMA COISBAR ENABLE ROW MODIFICATION TRACKING; CREATE TABLE COISBAR.A (A INT, B INT) ORGANIZE BY COLUMN DISTRIBUTE BY (B); CREATE TABLE COISBAR.B AS (SELECT * FROM COISBAR.A) WITH DATA; SELECT TABNAME, COLNAME, PARTKEYSEQ FROM SYSCAT.COLUMNS WHERE TABNAME IN ('A','B') ORDER BY TABNAME, COLNO; TABNAME COLNAME PARTKEYSEQ ------ ------------- ---------- A SYSROWID 0 A CREATEXID 0 A DELETEXID 0 A A 0 A B 1 B SYSROWID 0 B CREATEXID 0 B DELETEXID 0 B A 1 B B 0 This is not what should be happening. The distribution key of table B should be inherited from table A. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.1 or higher * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.1 or higher * **************************************************************** | |
Comment | |
Upgrade to Db2 11.5.5.1 or higher | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.02.2021 09.04.2021 09.04.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |