JR26652: UNDER CERTAIN STRICT CONDITIONS A QUERY INVOLVING AN OUTERJOIN MAY RESULT IN A CRASH.

DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
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

APAR status

• Closed as program error.

Error description

• With the registry variable DB2COMPOPT is set a query involving
  all of:
  
  - one or more outer joins with at least one NULL producing
    operand consisting of a nested sub-select statement
  - outer join clause that contains a simple equality predicate
    referencing multiple columns
  - the outer join row preserving operand is a sub-select that
    contains GROUP BY, UNION, INTERSECT, EXCEPT or a nested
    table modification operand (UPDATE, INSERT, DELETE)
  
  may result in a crash whilst it is being compiled.
  

Local fix

• Unset the DB2COMPOPT registry variable and consult with DB2
  support about possible side effects from un-setting it.
  

Problem summary

• Users affected: Systems using the DB2COMPOPT variable.
  Problem Description: Under certain strict conditions
  including having DB2COMPOPT set, one or more outer joins
  with a null producing operand, outer join clause that
  contains multiple column simple equality predicates and the
  outer join row preserving operand being a sub select, the
  compilation of a query involving an outer join may result in a
  crash.
  Problem Summary: Unser certain strict conditions a query
  involving an outer join may crash.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.1, FixPak 4
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR27555

Fix information

• Fixed component name

  DB2 UDB EXE WIN

• Fixed component ID

  5724E4901

Applicable component levels

• R910 PSY

     UP

• R820 PSN

     UP