IC84324: OPTIMIZER MIGHT NOT CONSIDER A TABLESCAN OF A RANGE PARTITIONED TABLE ON THE INNER OF A NESTED LOOP JOIN

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• The query plan optimizer might not consider a table scan of a
  range partitioned table on the inner of a nested loop join even
  though it is not a full table scan when the pushed down join
  predicates could restrict the number of partitions that are
  being scanned.  You might encounter this problem at optimization
  class 7 and lower.
  

Local fix

• Compiling the query under optimization class 9 will enable the
  optimizer to consider the table scan option.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * OPTIMIZER MIGHT NOT CONSIDER A TABLESCAN OF A RANGE          *
  * PARTITIONED TABLE ON THE INNER OF A NESTED LOOP JOIN         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 Version 10 Fix Pack 1.                        *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 Version 10 Fix Pack 1.
  

Temporary fix

Comments

APAR Information

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

  IC80758

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

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RA10 PSN

     UP