DB2 FOR LUW / DB2FORLUW / A50 - DB2

Compiling an SQL statement can return SQL0901N with Reason "Too 
many columns or record length exceeded." when all of the 
following conditions are met: 
 
(1) intra-partition parallelism is enabled (i.e. DBM 
configuration parameter INTRA_PARALLEL is set to YES). 
(2) DB2 chooses zigzag join in the query plan. 
(3) DB2 chooses to SMP-parallelize the zigzag join. 
(4) There is a dimension table, in which the join column data 
type is either INT or BIGINT. 
(5) The query needs to access a column whose data type is 
DECIMAL from the dimension table. 
 
For example, in the following query, if d1.key1 is int data type 
and d1.col1 is decimal data type, and if DB2 chooses zigzag join 
and SMP-parallelize the zigzag join, then DB2 can return the 
SQL0901 error when compiling this query. 
 
   select d1.col1 
   from fact f, dimension1 d1, dimension2 d2 
   where d1.c1 = 10 and d2.c1 = 30 
   and d1.key1 = f.key1 
   and d2.key2 = f.key2

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4                       * 
****************************************************************

Disable intra-partition parallelism. To disable intra-partition 
parallelism at application or statement level, set special 
register "current degree" to 1. For example: SET CURRENT DEGREE 
= '1'

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 Cancun Release 10.5.0.4

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.06.2014
09.09.2014
09.09.2014