The Utility Activity Trace
This topic introduces the Utility Activity trace.
Traces are presented in the order in which the threads complete. Start times might not be shown in ascending order if other threads finished prior to completion of a thread which started earlier.
The Utility Activity trace is generated with the following command:
UTILITY
TRACE
ORDER (PRIMAUTH-PLANNAME-INSTANCE)
Utility Activity Short Trace Example
Here is an example of a Utility Activity Short trace.
LOCATION: OMPDB51 IBM OMEGAMON FOR DB2 PERFORMANCE
EXPERT (V5R5M0) PAGE: 1-1
GROUP: N/P UTILITY ACTIVITY TRACE REQUESTED FROM: NOT SPECIFIED
MEMBER: N/P TO: NOT SPECIFIED
SUBSYSTEM: DB51 ACTUAL FROM: 06/07/15 09:14:49.15
DB2 VERSION: V11 PAGE DATE: 06/07/15
WORKLOAD(NONE)
IDENTIFIED BY PRIMAUTH/PLANNAME/INSTANCE
PRIMAUTH
PLANNAME ELAPSED TIME
INSTANCE START TIME CPU TIME ACTIVITY TYPE OBJECT(S)
---------------------- ----------- ------------ ----------------------- -----------------------------------------------------------
KOZS
DSNBIND
X'CB79D266C962' 09:15:02.92 0.000280 BIND
0.000000 BIND PLAN PLANNAME: DSNREXX
KOZS
DSNBIND
X'CB79D3411068' 09:18:51.94 0.027328 BIND
0.000000 RBND PACK LOCN: OMPDB51
COLL: UTRUN
PKID: UTILV110
VRID: N/P
CONS: X'195D036002523DD6'
LOCATION: OMPDB61 IBM OMEGAMON FOR DB2 PERFORMANCE
EXPERT (V5R5M0) PAGE: 2-1
GROUP: N/P UTILITY ACTIVITY TRACE REQUESTED FROM: NOT SPECIFIED
MEMBER: N/P TO: NOT SPECIFIED
SUBSYSTEM: DB61 ACTUAL FROM: 07/29/15 12:33:31.62
DB2 VERSION: V11 PAGE DATE: 07/29/15
WORKLOAD(NONE)
IDENTIFIED BY PRIMAUTH/PLANNAME/INSTANCE
PRIMAUTH
PLANNAME START TIME ELAPSED TIME UTILITY-ID JOB NAME SHRLEVEL
INSTANCE SUBTASKS CPU TIME ACTIVITY TYPE DATABASE.PAGESET STEP TOT. ZIIP
SORT: DF DB2 DATA INDEX OTHER SORT CPU SORT ZIIP
---------------------- ----------- ------------ ----------------------- -----------------------------------------------------------
KOZS
DSNUTIL
X'CBBB5FBF101E' 12:33:31.62 0.732401 UTILITY KOZS.KOZUNLUT KOZUNLUT CHANGE
0 1 0 0.008799 REORG DB2PE .TSPAFDF UNLD1 0.001200
Y N 0 1 0 0.002311 0.000900
UTILITY TRACE COMPLETE
Field description
The trace contains the
following fields:
- OMEGAMON for Db2® PE identifiers
- The OMEGAMON for Db2 PE identifiers specified in the ORDER option. They are printed whenever they change. The second and third identifiers are indented.
- PLANNAME
- The Db2 application plan name of the thread.
- ELAPSED TIME
- The time difference between START TIME and the timestamp of the ENDUTIL of the last bind or utility record of the originating task.
- JOB NAME
- User-defined job name.
- SHRLEVEL
- The SHRLEVEL value of the utility. Possible values are: NONE, REFERENCE, or CHANGE.
- START TIME
- The timestamp of the first bind or utility record encountered for that thread.
- CPU TIME
- The CPU time of the bind or utility event, including the CPU time of any parallel tasks.
- ACTIVITY TYPE
- The name of the activity type and event. The activity type can
only be BIND for bind events including remote bind activity, or UTILITY
for utility events. All events are indented.
For a detailed description, of Activity Type, see page Field description.
- OBJECT(S)
- The description depends on whether it is a utility event, a bind
event referring to a plan, a bind event referring to a package, or
a BIND CONNECT:
- In the case of a utility, it is the database name.object name for each object worked on by the utility. Each database name.object name is shown only once.
- In the case of a BIND PLAN, RBND PLAN, or FREE PLAN event, it is the plan name.
- In the case of a BIND PACK, RBND PACK, FREE PACK, BIND R-PACK,
RBND R-PACK, or FREE R-PACK event, the following information is shown:
- LOCN
- The location of the package.
- COLL
- The collection to which the package belongs.
- PKID
- The package ID.
- VRID
- The first 53 characters of the version name.
- CONS
- The consistency token for the package.
- In the case of a CONNECT, it is LOCN, the location of the package.
- TOT. ZIIP
- The total utility ZIIP time (if Accounting class 1 trace is activated).
- SORT
- The following fields provide information about sorting. They are
only written for utility events:
- DF
- Shows if DFSORT was invoked at least once (Y/N).
- DB2
- Shows if DB2SORT was invoked at least once (Y/N).
- DATA
- Shows the number of parallel data sorts.
- INDEX
- Shows the number of parallel index sorts.
- OTHER
- Shows the number of other sorts.
- SORT CPU
- Shows the SORT CPU time.
- SORT ZIIP
- Shows the SORT ZIIP time (if provided by the SORT program).