This section introduces the summary report.
At normal completion of OMEGAMON for DB2® Performance Expert explain, the last pages of the output are a summary of the OMEGAMON for Db2 Performance Expert explain execution. This is called the Summary Report. Each command is prefixed with the report number.
For each SQLSTMT, QUERYNO, and QMFQUERY request, the access path is listed adjacent to the input request. For each PLAN or PACKAGE statement, the access path is listed for every SQL statement in the plan or package.
To the right of the access path information, the report page number (rrr-nnnn) is shown, unless LEVEL(SUMMARY) was specified. In this way the summary report can be used as a table of contents.
For details on how to specify EXPLAIN SUMMARY commands refer to the Report Command Reference.
Explain Report - Summary Report BlockThis is an example of a Summary report.
REPORT ON: 02/18/16 15:05:08 OMEGAMON XE DB2 PE (V5.4) PAGE : SUMMARY EXPLAIN SUMMARY REPORT USER AUTHID: XRK THE FOLLOWING 1 EXPLAIN REQUESTS WERE PROCESSED: PAGE NO 1: DA11 PACKAGE : KO2EX540 .DGO@TPG3 DETAIL REPORT REQUESTED DBRM/PACK STMT TYP DGO@TPG3 1011020 P MATCHING INDEX SCAN(2/4)-DATA PAGES 1-2 DGO@TPG3 1011021 P S TABLE SPACE SCAN-NO INDEX WILL BE USED 1-7 DGO@TPG3 1011021 P ADDITIONAL SORT FOR ORDER BY 1-10 DGO@TPG3 1011070 P L MATCHING INDEX SCAN(3/4)-DATA PAGES 1-12 DGO@TPG3 1011071 P MATCHING INDEX SCAN(1/4)-DATA PAGES 1-16 DGO@TPG3 1011071 P ADDITIONAL SORT FOR ORDER BY 1-20
- Standard sequential prefetch
- Prefetch through a page list Table space scan
- Nonmatching index scan
- A blank
- No prefetch or others
The numbers in brackets following MATCHING INDEX SCAN, for example (2/3), show how many columns match, namely 2, and how many columns the index has, namely 3.