DB2 FOR LUW / DB2FORLUW / 910 - DB2

Compiling a query on DB2 v9.1 fix pack 8 may result in the DB2 
instance terminating abnormally with a stack similar to this 
example from Linux: 
 
  0000002A9AE8F0BE ossDumpStackTrace + 0x0186 
  0000002A9AE8CBD4 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00aa 
  0000002A97F4A8DF sqlo_trce + 0x03cf 
  0000002A96D94B78 sqloEDUCodeTrapHandler + 0x02b8 
  0000003130A0C5B0 address: 0x0000003130A0C5B0 ; dladdress: 
0x0000003130A00000 ; 
  0000002A965D4FB9 _Z21sqlnq_const_fold_treeP9sqlnq_pidRbP3loc + 
0x0171 
 
Another possible symptom of this problem is SQLCODE -901 with 
one of the two following reason codes: 
 
  SQL0901N  The SQL statement failed because of a non-severe 
system error. 
  Subsequent SQL statements can be processed.  (Reason "invalid 
qnc assigment".) 
  SQLSTATE=58004 
 
or 
 
  SQL0901N  The SQL statement failed because of a non-severe 
system error. 
  Subsequent SQL statements can be processed.  (Reason "column 
number out of range".) 
  SQLSTATE=58004 
 
To hit this problem, a query must have an outer join whose 
result is inner joined with a base table and there must be a 
join predicate, for example: 
 
  create view V as select * from T1 left outer join T2 ... 
  select * from V, T3 where V.C1=T3.C2 
 
The problem only occurs on v9.1 fix pack 8.

Users affected :  Users compiling a query in DB2 V9.1 fix pak 8 
 
Problem Description : Compiling a  query  in V9.1 fix pak 8 can 
crash the  DB2 instance. Please  see APAR description for the 
details 
 
Problem Summary : Compiling a query in V9.1 fix pak 8 can crash 
the DB2  instance

Upgrade to DB2 v9.1 fix pack 9 or reverse the order in the join 
predicate, for the example above: T3.C2=V.C1

DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

First Fixed in DB2 Version V9.1 fix pak 9

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC66230 IC66239 IC66487 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

04.02.2010
21.04.2010
30.09.2010

9.0.,
9.1.