The Getpages from Insight do not match the Getpages from Detector, for the same SQL statement . Why not?

book

Article ID: 17164

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

This document explains why the Getpages in Insight may not match the Getpages from Detector, for the same SQL statement. 



The Getpages from Insight do not match the Getpages from Detector, for the same SQL statement. Why not?

Environment

z/OS 1.11 and above.

Resolution

The Insight Detail & History screens, as well as the BTACTSMS report uses the GET-PAGE field. Whereas, the PKG-GET-PAGE field is a better match for Detector.

Also, what apparently is not counted (or rather aggregated into IFCIDs) are the package level details of getpages (or more generally per buffer pool stats) in child threads roll up records (when parallelism is involved), but thread level data are still available. That’s the source of the discrepancy between summaries of GET-PAGE and PKG-GET-PAGE fields.