Question & Answer
Question
What is Card Application - Utilities?
This card shows the same data you would see in LIST UTILITIES SHOW DETAILS, and more, except it is for the monitored database only. In contrast, when using CLP, the LIST UTILITIES command shows in-flight utilities for all databases in the instance.
In addition to the usual utilities shown by LIST UTILITIES SHOW DETAILS, this card shows in-flight and recent REORG operations. Note that it does NOT show recent runs of utilities such as LOAD or RUNSTATS, only REORG.
Answer
Historical data about utilities is available only if Utility event monitor has been enabled on.
Actions
View Details
Columns
DB2 reports different monitoring elements for REORG than it does for other utilities. So the table below has an extra column to explain what each column shows for REORG as opposed to other utilities.
|
Column Name |
Shown by Default |
Description (other utilities) |
Description (REORG) |
|
Database member |
n |
member |
member |
|
Type |
Y |
Possible values are:
RUNSTATS |
REORG |
|
State |
Y |
Possible values are:
|
Possible values are:
From reorg_status |
|
Start time |
Y |
Start time of the utility |
Start time of the REORG From reorg_start |
|
Estimated percent complete |
Y |
This is calculated as (completed work / total work) * 100.0. |
For REORG, this shows the estimated percent complete of the current phase of the REORG. This is calculated as (reorg_current_counter / reorg_max_counter) * 100.0 |
|
Description |
n |
This field can be null, or can tell a little more about the utility in question. For example what kind of BACKUP or what phase a REBALANCE operation is in. |
null |
|
Throttling priority |
n |
Priority if utility supports throttling, otherwise null. |
null |
|
Phase start time |
n |
Start time of the current phase of this utility. |
Start time of the current phase of this REORG (from reorg_phase_start) |
|
Phase |
n |
For some utilities this field tells what phase of operation the utility is in. For example, LOAD can show DELETE, LOAD or REDO here. |
null |
|
ID |
n |
Included in case you want to match up this data with what is shown in other sources, such as LIST UTILITIES or db2pd. |
null REORG is not shown in LIST UTILTIES |
|
Invocation type |
n |
Possible values are:
|
null |
|
Completed work |
n |
Used in the calculation of “Estimated Percent Complete” |
null |
|
Total work |
n |
Used in the calculation of “Estimated Percent Complete” |
null |
|
Units |
n |
Possible values are:
|
null |
|
Data partition identifier |
n |
null |
Only relevant for range partitioned tables |
|
Index schema |
n |
null |
For index REORG |
|
Index name |
n |
null |
For index REORG TBD: I suspect these only apply for global indexes on range partitioned tables |
|
Current progress list attributes |
n |
||
|
Current progress list sequence number |
n |
||
|
Progress sequence number |
n |
||
|
Reorganization completion flag |
n |
null |
Possible values are:
|
|
Table reorganization end time |
n |
null There is no equivalent for ordinary utilities since they are no longer displayed once they have completed |
Time at which this REORG completed. This is null while a REORG is in flight. It is important that this is shown so the user can distinguish active versus historical records in the grid. |
|
Table reorganization phase |
n |
||
|
Rows compressed |
n |
null |
Relevant only for REORG involving compression |
|
Rows rejected |
n |
null |
Relevant only for REORG |
|
Table reorganization attributes |
n |
||
|
Table schema |
n |
null |
Schema of table being REORG’ed |
|
Table name |
n |
null |
Name of table being REORG’ed |
Was this topic helpful?
Document Information
Modified date:
31 December 2019
UID
ibm11166170