DB2 - Problem description
Problem IC88658 | Status: Closed |
QUERY CONTAINING "NOT IN" PREDICATE WITH A PARAMETER MARKER MIGHT CAUSE DB2 TO ABEND | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Under rare scenarios, DB2 might abend if the following conditions are satisfied. 1. The query contains one or more NOT IN predicates. 2. The join column of the NOT IN predicate also has another equality predicate with either a parameter marker or a literal. 3. In case of join with literal, statement concentrator must also be switched ON. Such a query results in FODC and following error in db2diag.log: FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:550 RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR "Severe programming error" DIA8516C A severe internal processing error has occurred. The trap file produced will have the below stack: sqlnr_NotExists2OJ_cond_detail sqlnr_NotExists2OJ_action sqlnr_seq sqlnr_rcc sqlnr_startqtb_action sqlnr_seq | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 Fix Pack 3 * **************************************************************** | |
Local Fix: | |
db2set DB2_ANTIJOIN=NO -im | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 version 10.1 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.11.2012 23.10.2013 23.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |