home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC62436 Status: Closed

DB2 MAY RETURN SQL101N WHEN COMPILING CERTAIN QUERIES WITH AN OUTER JOIN
AND A GROUP-BY SUBQUERY.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may return SQL101N when compiling queries that satisfy all 
of the following conditions: 
 
1. Query has LEFT or RIGHT OUTER JOIN subquery, called ojSubq 
2. Query has Group-By subquery, called gbSubq 
3. gbSubq inner joins with ojSubq. gbSubq join key(s) contain 
all its Group-By columns. Some ojSubq join key(s) is derived 
from its own Group-By subquery or Null Producing stream of its 
own outer join subquery. 
 
How to diagnose the issue: 
1. The query returns SQL101N even when STMTHEAP has been set to 
maximum value. Query goes into an infinite loop until the 
the STMTHEAP is exhausted. 
 
2. The failing trace stack includes the following 
routines:    ..... 
   0x0900000070E4750C 
sqlnr_reorder_IJ_qgm__FCP9sqlnq_qunCP9sqlnq_oprPP13sqlnq_deplist 
PiCP3loc + 0x346C 
   0x0900000070E18890 sqlnr_qrwprep_phase2__FP3locPi + 0xAB0 
   ..... 
 
3. db2trc output indicates that sqlnr_qrwpprep_phase2() calls 
sqlnr_reorder_IJ_qgm() in an infinite loop. 
 
This issue occurs only starting 9.5 Fixpak 4
Problem Summary:
DB2 MAY RETURN SQL101N WHEN COMPILING CERTAIN QUERIES WITH AN 
OUTER JOIN AND A GROUP-BY SUBQUERY.
Local Fix:
Manually change equality join predicate between gbSubq and 
ojSubq to a BETWEEN predicate. 
For example, change 
     WHERE gbSubq.colX = ojSubq.colY 
to 
     WHERE gbSubq.colX BETWEEN ojSubq.colY AND ojSubq.colY
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in version 9.7 Fixpak 1
Workaround
Manually change equality join predicate between gbSubq and 
 
ojSubq to a BETWEEN predicate. 
For example, change 
     WHERE gbSubq.colX = ojSubq.colY 
to 
     WHERE gbSubq.colX BETWEEN ojSubq.colY AND ojSubq.colY
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.08.2009
19.12.2009
19.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList