PI96768: INCORRECT FILTER FACTOR FOR CURRENT DATE OR CURRENT TIMESTAMP SPECIAL REGISTERS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An incorrect filter factor can be produced for a predicate
  containing a CURRENT DATE/CURRENT TIMESTAMP special
  register and the query contains host variables and/or
  parameter markers.
  
  Additional symptoms and keywords:
  SQLPERFORMANCE SQLDATE SQLTIMESTAMP
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS users who experience                     *
  * an inefficient access path as a result of                    *
  * an incorrect filter factor being calculated                  *
  * for an EQUAL, RANGE or BETWEEN                               *
  * predicate containing CURRENT DATE, CURRENT                   *
  * TIMESTAMP.                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * An inefficient access path can result                        *
  * from an incorrect filter factor being                        *
  * calculated for an EQUAL, RANGE, or                           *
  * BETWEEN predicate containing CURRENT                         *
  * DATE or CURRENT TIMESTAMP.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  The incorrect filter factor is produced by an invalid value
  returned internally when the calculation is done for the
  CURRENT DATA or CURRENT TIMESTAMP special registers.  Db2 will
  now avoid using the incorrect values for the calculation.
  
  Additonal keywords:
  SQLACCESSPATH FILTERFACTOR SQLSPECIALREG
  

Problem conclusion

• The described problem is fixed by correcting the bad
  filterfactor on such predicates.
  

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:

  UI56157

Modules/Macros

• DSNXODFE DSNXODFB DSNXODFR DSNXORSP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI56157

     UP18/06/13 P F806

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.