home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT07731 Status: Geschlossen

DB2 MIGHT PRODUCE ABEND OR PRODUCE SQL0901N WHEN EXECUTING A RECURSIVE
QUERY WITH A JOIN ON EXPRESSIONS

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Under rare scenarios, DB2 might abend or produce SQL0901N when 
the following conditions are true: 
1) DB2 must be running on MPP configuration 
2) The query contains a recursive UNION ALL construct 
3) The recursive branch of the UNION ALL contains one or more 
join predicates 
4) Atleast one of the joins is of type: <expression> = <col>, 
where <expression> involves only columns from a single subselect 
eg. T1.C1 + T1.c2 + 1 = T2.c1
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* MPP                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher.            * 
****************************************************************
Local-Fix:
Manually rewrite the query to push the expression to the 
subselect and use the output column reference for join predicate
Lösung
Problem first fixed in DB2 version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.03.2015
26.07.2015
26.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList