|
Problem IC88658
|
Status: Geschlossen |
QUERY CONTAINING "NOT IN" PREDICATE WITH A PARAMETER MARKER MIGHT CAUSE DB2 TO ABEND |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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 |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
The problem is first fixed in DB2 version 10.1 Fix Pack 3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 28.11.2012
23.10.2013
23.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
