High Aborts count

book

Article ID: 191929

calendar_today

Updated On:

Products

CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Management for DB2 for z/OS - Performance Suite CA Database Management for DB2 for z/OS - SQL Performance Suite CA Detector for DB2 for z/OS CA-Insight Performance Monitor for DB2 UDB for z/OS

Issue/Introduction

The number of aborts are high in DETECTOR Planname Summary Display. Should that be a concern for followup?

20.0    >   --------- DETECTOR Planname Summary Display -------- 05-28-20 10:37

Command ==>                                        Scroll ==> CSR               LINE 1 OF 9

DB2 SSID  ==> DB02                                                            

View Type ==> A * -Activity X -Exception E -Error O -Object                   

View By   ==> P * -Plan G -Prog S -SQL Q -DSQL F -Prof K -Key   Total/Avg ==> T            

Interval Date => 05-26-20   Interval Time =>10:00:00    Elapsed Time => 03:00

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

S -Programs, D -Detail, Q -Dynamic SQL, K -Keys, H -History, T -Active Threads                                                                            

  PLANNAME COMMIT   ABORT  SQL        TIMEPCT CPUPCT  INDB2_TIME   INDB2_CPU  

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

RCUUPL20       76     23    2616332  14.85% 47.94% 00:28.987268 00:24.767743

_ TCXO1       27487      0     156860  33.30%  29.74% 01:05.001286 00:15.364226

_ TCXB1       10469      0     307828  24.05%  14.05% 00:46.942274 00:07.262912

_ TCXPLN03     5151      0      53726  26.49%   6.17% 00:51.702995 00:03.192146

_ CBROAM       3527      0       9610   1.24%   1.95% 00:02.428359 00:01.010205

_ RQPAPL20        8      0        204    .02%    .05% 00:00.048008 00:00.028651

_ PSAAPL20       67      0        278    .01%    .05% 00:00.031997 00:00.027160

_ QMF1210         4      0        282    .00%    .01% 00:00.008110 00:00.006778

_ TCXPLN05        0      0          6    .00%    .00% 00:00.014463 00:00.001017

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

Environment

Release : 20.0

Component : CA Detector for DB2 for z/OS

Resolution

The abort counts show the number of DB2 abort processes initiated during the interval for all activity or with the plan display it shows the number of time an abort process was initiated during any execution of the plan in the interval. A DB2 abort process can occur for certain types of SQL errors,abends, or the thread executing the plan being terminated for some reason by an operator. Detector(PDT) does not really give detailed info on what caused the abort to occur, but does have the capability to report on SQL errors. If the abort is a result of an SQL error, then it should be reported in Detector. The abort counts can be incremented as part of normal application activity. If the counts are high, you can evaluate the SQL errors collected for the plans in question using the SQL error displays.There is no direct list of how and when the abort count is being updated from the plan activity displays.
Some valid reasons for aborts:

- APPLICATION PROGRAM ABEND
- APPLICATION ROLL BACK REQUEST
- APPLICATION DEADLOCKED (-911s)
- APPLICATION CANCELED BY OPERATOR
- THREAD ABEND CAUSED BY RESOURCE SHORTAGE
In general, any time a unit of recovery is rolled back.