LI76075: CANNOT SET EXCLUDE XML COLUMNS CLAUSE IN STATISTICS PROFILE

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

• When running runstats
  on the command line with the Exclude XML Columns clause, it
  works
  perfectly.  However, when the stats profile is set with that
  clause,
  the stats profile ignores it and stores a runstats command for
  ALL
  columns and ALL indexes.
  
  ex:
  
  RUNSTATS ON TABLE sahana12.test2 with distribution on key
  columns and detailed indexes all excluding xml columns set
  profile
  DB20000I  The RUNSTATS command completed successfully.
  
  select substr(statistics_profile, 1, 150) as statistics_profile
  from syscat.tables where tabname='TEST2'
  
  STATISTICS_PROFILE
  ----------------------------------------------------------------
  ------------------------------------
  
  RUNSTATS ON TABLE "SAHANA12"."TEST2" ON ALL COLUMNS WITH
  DISTRIBUTION ON KEY COLUMNS AND DETAILED INDEXES ALL
  
    1 record(s) selected.
  
  
  In the above we see that external statiscs_profile does not
  contain clause 'EXCLUDING XML COLUMN'.
  This problem is only with external statistics_profile storage,
  however when the command is executed runstats does not collect
  statistics on xml columns when 'excluding xml column' option is
  specified.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 9.1 FP11 or Subsequent Fix Pack               *
  ****************************************************************
  

Problem conclusion

• Problem First Fixed in DB2 Version 9.1 Fix Pack 11
  

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:

  LI76423 IC78336

Fix information

• Fixed component name

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R910 PSN

     UP