PDT Decrease of number o Commits after R20 Migration
search cancel

PDT Decrease of number o Commits after R20 Migration

book

Article ID: 203688

calendar_today

Updated On:

Products

SYSVIEW Performance Management Option for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - SQL Performance Suite Detector for DB2 for z/OS

Issue/Introduction

After upgrading from R19 to R20   a substantial decrease of COMMITs in Detecttor Plan History Display on a daily report was observed as seen below:
20.0    >   ----------- DETECTOR Plan History Display ---------- 20/05/07 15:34
 Command ==>                                                     Scroll ==> PAGE
                                                                    LINE 1 OF 30
 Total/Avg ==> T            DB2 SSID  ==> D12A             Planname ==> DISTSERV
 
 -------------------------------------------------------------------------------
 
 S -View Programs, D -View Detail
 
     DATE      TIME      ITIME SQL        COMMIT     ABORT      INDB2_TIME
     --------  --------  ----- ---------- ---------- ---------- ------------
 _   20/04/21  19:59:33  08:00   12970222    3059560       2091 01:44:30.783
 _   20/04/22  03:59:33  08:00   15842509    4537262       3550 06:30:16.274
 _   20/04/22  11:59:33  08:00   14805089    3740978       2344 03:20:50.576
 _   20/04/22  19:59:33  08:00   12839339    3022087       2293 01:56:43.858
 _   20/04/23  03:59:33  08:00   15676463    4514387       3628 05:14:07.647
 _   20/04/23  11:59:33  08:00   13960226    3558108       2631 01:44:42.560
 _   20/04/23  19:59:33  08:00   13729605    3050001       2048 02:01:17.839
 _   20/04/24  03:59:33  08:00   16203656    4710264       3109 04:38:49.661
 _   20/04/24  11:59:33  08:00   14017311    3620192       2290 01:19:27.312
 _   20/04/24  19:59:33  08:00   15559230    2858163       2117 02:04:56.076
 _   20/04/25  03:59:33  08:00   10650865    3186677       2553 55:46.105161
 _   20/04/25  11:59:33  08:00   13769122    4161325       2214 30:25.353888
 _   20/04/25  19:59:33  08:00    2681498     757124       1641 09:05.523140
 _   20/04/26  03:59:33  02:12    4138030    1255625        493 10:24.044633
 _   20/04/26  06:34:01  00:00      12946        483          0 00:02.397055
 _   20/04/26  06:37:04  01:02    1016070      45461        263 03:48.298519
 _   20/04/26  07:45:48  00:41     599431      34820        237 01:57.984785
 _   20/04/26  08:29:30  00:03      99304       6159          7 00:35.509182
 _   20/04/26  08:45:47  00:26    1511029      90174        160 08:47.701212
 _   20/04/26  10:01:12  00:45     854256      49121        234 25:09.819399
 _   20/04/26  10:47:09  01:12     621886      33043        336 03:02.338106
 _   20/04/26  11:59:33  08:00    8614057     339231       1994 44:00.394605
 _   20/04/26  19:59:33  08:00    6388354     220857       2147 56:39.835534
 _   20/04/27  03:59:33  07:59   13005579     625711       2960 05:33:36.536<======
 _   20/04/27  11:59:33  08:00   11438005     420163       2667 01:42:45.580<======
 _   20/04/27  19:59:33  08:00   11130031     277085       2033 02:39:51.874<======
 _   20/04/28  03:59:33  08:00   13108407     653104       3693 05:16:34.176<======
 _   20/04/28  11:59:33  08:00   11889435     448097       2456 01:53:21.922<======
 _   20/04/28  19:59:33  08:00   12119251     309259       2314 02:05:22.094<======
 _   20/04/29  03:59:33  08:00   13406139     690409       3500 03:56:04.496<======
 ******************************* BOTTOM OF DATA ********************************

Environment

Release : 20.0

Component : CA Detector for DB2 for z/OS

Resolution

The he problem was resolved by bringing the maintenance up to date, recycling the started tasks and Rebinding all the plans and packages.