search cancel

HIGH2KEY and LOW2KEY BLANK after PDA Auto-Catalog Update processing.


Article ID: 52261


Updated On:


RC Compare for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Rapid Reorg for DB2 for z/OS CA Distributed Database Management CA Database Analyzer for DB2 for Oracle Database Analyzer (IMS Tools) Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC Compress Data Compression (IMS Tools) Database Analyzer for IMS for z/OS Database Copier for IMS for z/OS Database Organizer for IMS for z/OS Mainframe Extended Terminal Manager (IMS Tools) High Performance Recovery for IMS for z/OS Database Organizer (IMS Tools) Mainframe Program Restart Manager for IMS for z/OS Secondary Index Builder for IMS for z/OS Secondary Index for IMS for z/OS



A PDA Extract Procedure is run to collect statistics on tablespaces only, without their associated indexes. It also, at the same time, updates the DB2 catalog to mimic what RUNSTATS does, in theory, with COLSTATS=I(ndex) defined.

SYSCOLUMNS is updated with blank values in HIGH2KEY and LOW2KEY.

This may cause the optimizer to make some unfortunate access path choices in some cases.


This problem is caused by using Database Analyzer in a way other than how it is designed to work.

There are two options to resolve this problem:

  1. Do not specify COLSTATS=I(ndex) for Extract Procedures where indexes are excluded from statistics collection.

    Turn the COLSTATS off with COLSTATS=N.

  2. Include indexes in object selection to use COLSTATS=I(ndex) column. The help for Column Statistics for Index states the following:

    "I" - Save statistics for columns used in indexes only. Extract should contain indexes in object selection.

Typically you would want your Tablespace/Table statistics to stay in sync with their corresponding Indexes statistics so that the DB2 optimizer is fed valid info.


Component: DBA