The Performance Warehouse data tables
The Performance Warehouse database contains the following Performance Warehouse data tables for table space STAT.
Table name | Table description |
---|---|
DB2PM_STAT_BUFFER | One row for each buffer pool that is active
at the start of:
|
DB2PM_STAT_DATASET | One row for each open data set that has an I/O event rate of at least one event per second during the reporting interval. |
DB2PM_STAT_DDF | For each delta record (file data) or interval record (save-file data), one row per remote location participating in distributed activity using the system-directed access method and one row for all remote locations using the application-directed access method. |
DB2PM_STAT_GBUFFER | One row per group buffer pool that is active at the start of the corresponding delta record for file data or of the interval record for save-file data. |
DB2PM_STAT_GENERAL | For file data: One row for each Statistics delta record,
containing data from IFCID 1 and 2. A delta record is a set of counters
describing the Db2® activity
between two consecutive Db2 Statistics
records pairs. For save-file data: One row for each Statistics interval record, containing data from IFCID 1 and 2. A Statistics interval record is a set of counters describing the Db2 activity within the interval specified by the user. |
Table name | Table description |
---|---|
DB2PMSACCT_BUFFER | One row per buffer pool used. |
DB2PMSACCT_DDF | One row per remote location participating in distributed activity. |
DB2PMSACCT_GBUFFER | One row per group buffer pool used. |
DB2PMSACCT_GENERAL | One row per Db2 Accounting record, which is written when a thread terminates, is reused, or becomes inactive. |
DB2PMSACCT_PROGRAM | One row per package and DBRM executed. |
DB2PMSACCT_RLF | One row per resource limit type encountered. |
For more information about these tables, refer to the part on the Performance Warehouse database in Reporting User's Guide.
The Performance Warehouse database described in the Reporting User's Guide contains more tables than the one described here. However, it must be created and managed manually using the sample CREATE and LOAD parts shipped with OMEGAMON for Db2 Performance Expert. The Performance Warehouse database described here is created automatically, managed by the OMEGAMON® Collector, and is accessible using the Performance Warehouse client.
The Accounting and Statistics tables are associated in a 1:n relationship as described in Reporting User's Guide.
The general table is the parent table for all other tables. Each row in the general table is associated with zero, one, or several rows in the other tables. For Accounting SAVE tables, use the columns LOCAL_LOCATION to CLIENT_TRANSACTION for joining related data. For Statistics tables, use the columns LOCAL_LOCATION, GROUP_NAME, SUBSYSTEM_ID, MEMBER_NAME, INTERVAL_TSTAMP, and BEGIN_REC_TSTAMP for joining related data.
The Accounting and Statistics tables in the Performance Warehouse database contain the following additional columns: STEPLOGID of type INTEGER and ROW_ID of type ROWID. These columns are populated by the OMEGAMON Collector and Db2 when performance data is loaded into the Performance Warehouse data tables. The value of STEPLOGID references the LOADLOG table and can be used to correlate the performance data and the LOAD step that loaded the data. Db2 generates the ROW_ID values automatically when rows are added to the Performance Warehouse data tables. They are used in the rules-of-thumb analysis to correlate general and detailed analysis results.