ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

STPR table not showing up under Detector SQL Table Activity Display

book

Article ID: 41664

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

 

Question: 

When user looks at the data for a given collection id in DETECTOR SQL Table Activity Display , he only sees data for the associated qualified table, but the display is missing information about I/O against SPTR, which used to be displayed. Is this an expected behavior and that they should not expect to see I/O against SPTR? If so, is the data for SPTR I/O stored somewhere else?

 

Here is an example of a before and after view:

 

Before, with extra information for unrelated qualifiers:

 

17.0 -------- DETECTOR SQL Table Activity Display ------- 04/11/16 16:22

COMMAND ===> Scroll ==> CSR 

LINE 1 OF 8

Total/Avg => T DB2 SSID ==> DB1O 

Program ==> CM00D965 Type ==> PKGE Statement ==> 0000322 

Ctoken ==> 194AB0E80477B266 Section ==> 00001 

Collid ==> P820 SQL Call Type ==> SELECT 

Version ==> @[email protected] 

 

Interval Date => 04/08/16 Interval Time => 07:00:00 Elapsed Time => 04:00 

-------------------------------------------------------------------------------

 

TABLE INDEX TB_SEQ_GP TB_IDX_GP IS_GETP IS_TBGETP CREATOR 

------------------ -------- --------- --------- --------- --------- -------- 

T_PROC_CD_CAT 0 766 CHAP820O 

T_PROC_CD_CAT 0 558 CHAP860O 

T_PROC_CD_CAT XPRCDCAT 348028 300 CHAP810O 

T_PROC_CD_CAT 0 395 CHAP810O 

T_PROC_CD_CAT XPRCDCAT 439300 504 CHAP820O 

T_PROC_CD_CAT XPRCDCAT 1176170 915 CHAP860O 

SPTR DSNSPT01 5149 1719 SYSIBM <=============

SPTR 0 1719 SYSIBM                       <=============

******************************* BOTTOM OF DATA ******************************** 

After, with no unrelated qualifiers or SPTR information: 

17.0 -------- DETECTOR SQL Table Activity Display ------- 04/11/16 16:20 

COMMAND ===> Scroll ==> CSR 

LINE 1 OF 2 

Total/Avg => T DB2 SSID ==> DB1O 

Program ==> CM00D965 Type ==> PKGE Statement ==> 0000322 

Ctoken ==> 194AB0E80477B266 Section ==> 00001 

Collid ==> P820 SQL Call Type ==> SELECT 

Version ==> @[email protected] 

 

Interval Date => 04/11/16 Interval Time => 07:00:00 Elapsed Time => 03:00 

------------------------------------------------------------------------------- 

 

TABLE INDEX TB_SEQ_GP TB_IDX_GP IS_GETP IS_TBGETP CREATOR 

------------------ -------- --------- --------- --------- --------- -------- 

T_PROC_CD_CAT XPRCDCAT 1249815 1722 CHAP820O

Answer: 

Regarding the concern about the STPR table not showing up under PSA, here is the explanation:

STPR table is internal to DB2 and DB2 accesses it and it is not accessed by the applications. So it’s okay to not see the I/O against that table since it is not attributed to the application.

 

 

 

 

 

 

 

Environment

Release:
Component: PSA