Table PLAN_TABLE Data

This section of the Explain report lists the raw EXPLAIN data as found in the DB2® table PLAN_TABLE.

For details on how to specify EXPLAIN commands refer to the Report Command Reference.

Explain Report - PLAN_TABLE Report Block

This is an example of the PLAN_TABLE report block.

EXPLAIN TABLE: PMDEV52.PLAN_TABLE ---------------------------------------------
EXPLAIN_TIME      : 2016-02-15-18.50.11.670393
TIMESTAMP         : 2016-02-15-18:50:11.71

PROGNAME (Package): DGO@TPG3          , COLLID            : KO2EX520
VERSION           : THIS_IS_A_LONG_NA*, APPLNAME (Plan)   : N/P
QUERYNO           : 1011071           , SECTNOI           : 4
QBLOCKNO          : 1                 , PARENT_QBLOCKNO   : 0
PLANNO            : 1                 , PARENT_PLANNO     : 0
MIXOPSEQ          : 0                 , QBLOCK_TYPE       : SELECT

TNAME (Table)     : SYSPACKAGE        , CREATOR (Table)   : SYSIBM
TABNO (Table)     : 1                 , CORRELATION_NAME  : N/P
TABLE_TYPE        : T - Table         , CTEREF            : 0
TABLE_ENCODE      : U - Unicode       , TABLE_MCCSID      : 1208
TABLE_SCCSID      : 367               , TABLE_DCCSID      : 1200
TSLOCKMODE        : N - No lock *     , GROUP_MEMBER      : N/P

ACCESSTYPE        : I - Index scan    , PRIMARY_ACCESSTYPE: BLANK
ACCESSNAME (Index): DSNKKX01          , ACCESSCREATOR     : SYSIBM
MATCHCOLS         : 1                 , INDEXONLY         : NO
METHOD (Join)     : 0 - First table   , JOIN_DEGREE       : 0
JOIN_TYPE         : b - INNER or NO   , MERGN             : NO
MERGE_JOIN_COLS   : 0                 , MERGC             : NO
PREFETCH          : D - Dynamic       , PAGE_RANGE        : NO
WHEN_OPTIMIZE     : b - At bind time  , ACCESS_DEGREE     : 0
COLUMN_FN_EVAL    : BLANK             , ROUTINE_ID        : 0
HINT_USED         : N/P               , OPTHINT           : N/P
SCAN_DIRECTION    : N/A

SORTN_PGROUP_ID   : 0                 , SORTN_UNIQ   : NO , SORTC_UNIQ   : NO
SORTC_PGROUP_ID   : 0                 , SORTN_JOIN   : NO , SORTC_JOIN   : NO
ACCESS_PGROUP_ID  : 0                 , SORTN_ORDERBY: NO , SORTC_ORDERBY: NO
JOIN_PGROUP_ID    : 0                 , SORTN_GROUPBY: NO , SORTC_GROUPBY: NO

REMARKS           : N/P               , STMTTOKEN         : N/P
PARALLELISM_MODE  : BLANK             , BIND_EXPLAIN_ONLY : NO
EXPANSION_REASON  : N/A

VERSION           : THIS_IS_A_LONG_NAME_VERSION_IDENTIFIER
TSLOCKMODE        : N - No lock (UR isolation)

The report field labels are the full PLAN_TABLE column names. For a detailed description of the PLAN_TABLE columns, refer to the Db2 SQL Reference. If the report field value is a long name or a long value, it is marked with an asterisk (*) at the end of the report field value, and it is reported at the end of the block in its full length.

The plan table is searched by using the bind time of the package. There might be multiple occurrences of the package with different bind times. For example, the DB2 system catalog might contain the latest package that is created by the DB2 command BIND or REBIND. It might also contain a former package version that is activated by the DB2 command REBIND SWITCH.