DB2 - Problem description
Problem IT01347 | Status: Closed |
DB2 MIGHT TRAP WHILE COMPILING A SQL STATEMENT WITH A DISTINCT CLAUSE WHEN INTRA-PARTITION PARALLELISM IS ENABLED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The following is the typical stack trace produced if you encounter this error: sqlnn_erds sqlng_build_IU_CLOB_obj sqlng_process_sort_op sqlngProcessLolepop sqlng_build_thread sqlng_scan_derived_table sqlng_process_scan_op sqlngProcessLolepop The problem can occur under the following conditions: - the optimizer chooses an all-probes list prefetch zigzag join alternative - there is a distinct clause that includes the fact table chosen for the zigzag join - intra-partition parallelism is enabled | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users running DB2 10.5 before Fix Pack 3 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5 Fix Pack 3 or above. * **************************************************************** | |
Local Fix: | |
Disable INTRA_PARALLEL for the problematic statement by setting the CURRENT DEGREE special register to 1. | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.04.2014 22.09.2014 22.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |