The SQL Activity Trace Index

The SQL Activity trace index provides a page index to the threads traced during the execution of an SQLACTIVITY command. An SQL Activity trace index is produced for each TRACE subcommand and is printed on a new page at the end of the trace output.

Each thread on the trace is listed in timestamp order followed by various OMEGAMON for Db2® PE identifiers.

If a thread satisfies the selection criteria for more than one TRACE subcommand, it is presented on each relevant trace, and is indexed accordingly.

SQL Activity Trace Index

The following example represents the trace index for location SYS1DSN2. From this page you can see the following:

This trace is the result of the first TRACE subcommand.
There are four threads.
There were no dates or times specified on the TRACE subcommand or on the GLOBAL command.
Both allied threads and DBATs are present. For allied threads, the requester location is the same as the local location (for example, the first entry shown in SQL Activity Trace Index). For DBATs, the requester location is different to the local location (for example, the second entry shown in SQL Activity Trace Index).

   LOCATION: SYS1DSN2                   IBM OMEGAMON FOR DB2 PERFORMANCE
                                    EXPERT (V5R5M0)                   PAGE: 0-2
      GROUP: DSN2                                  SQL ACTIVITY - TRACE                         REQUESTED FROM: NOT SPECIFIED
     MEMBER: SE21                                                                                           TO: NOT SPECIFIED
  SUBSYSTEM: SE21                                                                                  ACTUAL FROM: 01/30/15 06:45:39.34
DB2 VERSION: V10                                                                                            TO: 01/30/15 06:55:33.00
                                                            INDEX
     SQL TRACE #       1
                                                                           REQUESTER                         ACE     TRACE   STARTS
    TRACE START      CONNECT  CORRNAME CORRNMBR PRIMAUTH ORIGAUTH PLANNAME   SERVER             INSTANCE   ADDRESS     NO    PAGE NO
-------------------- -------- -------- -------- -------- -------- -------- ------------------ ------------ -------- -------- -------
01/30/15 06:42:18.13 TSO      WRL1     'BLANK'  WRL1     WRL1     DSNESPRR SYS1DSN2           AD7F37CCED27 05A493B8 1.7         2-69
01/30/15 06:45:39.34 TSO      WRL      'BLANK'  WRL      WRL      DSNESPRR PMO2DE21           AD7F37E1032D 05CDA8C8 1.4          2-1
01/30/15 06:49:32.14 TSO      WRL      'BLANK'  WRL      WRL      DSNESPRR PMO2DE21           AD7F38C0A3B0 05CDA8C8 1.5          2-7
01/30/15 06:55:44.54 TSO      WRL      'BLANK'  WRL      WRL      DSNESPRR PMO2DE21           AD7F3A23F5F9 05CDA8C8 1.6         2-38
SQL ACTIVITY TRACE COMPLETE

Field description

Here is a description of the field labels shown in the trace summary index:

TRACE START: The start time of the trace of the thread.
OMEGAMON for Db2 PE identifiers: The identifiers define the order of the SQL Activity data printed. If you specify no OMEGAMON for Db2 PE identifiers with ORDER, the default order of PRIMAUTH and PLANNAME is used.
SERVER: Reported in the same column as REQUESTER. All server locations involved are listed in alphabetical sequence below the requester location.
TRACE NO: The number of the thread, in the format x.yyyyy, where x is the number of the TRACE subcommand and yyyyy is the number of the thread reported as a result of that TRACE subcommand.
STARTS PAGE NO: The number of the page on which the beginning of the thread is reported. It is shown in the format x-yyyyy, where x is the location number and yyyyy is the page number within the location.
Note: If more than one summary level is selected, STARTS PAGE NO relates to the first summary printed for that thread.