|
Problem IT07030
|
Status: Closed |
DB2 MIGHT TRAP WHILE COMPILING A QUERY THAT IS ELIGIBLE FOR ZIGZAG JOIN PROCESSING |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In a rare scenario, DB2 might trap while compiling a query that
is eligible for zigzag join processing.
You will find the following in the stack trace if you encounter
this problem:
<StackTrace>
sqloEDUCodeTrapHandler
...
gsignal
abort
...
...
sqlno_zzjn_generate_fact_plan
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 Fix Pack 5 *
**************************************************************** |
| Local Fix: |
You can disable zigzag join by setting
DB2_REDUCED_OPTIMIZATION="ZZJN OFF". You can apply this against
an application or specific set of statements by using an
optimization profile that contains a REGISTRY request. You can
also disable zigzag join by setting the optimization level to 0
or 1. |
| Solution |
Problem first fixed in DB2 version 10.1 Fix Pack 5 |
| Workaround |
See Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.02.2015
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
