O

object_data_gbp_indep_pages_found_in_lbp - Group buffer pool independent data pages found in local buffer pool monitor element

The number of group buffer pool (GBP) independent data pages found in a local buffer pool (LBP) by an agent. Outside of a DB2® pureScale® environment, this value is null.

Table 1. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED
Table 2. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Activities event_activitymetrics ACTIVITY METRICS BASE
Package Cache pkgcache_metrics ACTIVITY METRICS BASE
Unit of Work uow_metrics REQUEST METRICS BASE

object_data_gbp_invalid_pages - GBP invalid data pages for a table monitor element

The number of times that a data page is requested from the group buffer pool (GBP) for a table. The page is requested because the version of the page in the local buffer pool (LBP) is invalid. Outside of a DB2 pureScale environment, this value is null.

Table 3. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested data page is found in the LBP, use the following formula, which uses the values of monitor elements:
(object_data_lbp_pages_found + object_xda_lbp_pages_found) / (object_data_l_reads + object_xda_l_reads)
To determine how often a requested data page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_data_gbp_l_reads + object_xda_gbp_l_reads - object_data_gbp_p_reads - object_xda_gbp_p_reads) /
(object_data_gbp_l_reads + object_xda_gbp_l_reads)

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_data_gbp_l_reads - GBP data logical reads for a table monitor element

The number of times that a group buffer pool (GBP) dependent data page is requested from the GBP for a table. The page is requested because a valid version of the page does not exist in the local buffer pool (LBP). Outside of a DB2 pureScale environment, this value is null.

Table 4. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested data page is found in the LBP, use the following formula, which uses the values of monitor elements:
(object_data_lbp_pages_found + object_xda_lbp_pages_found) / (object_data_l_reads + object_xda_l_reads)
To determine how often a requested data page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_data_gbp_l_reads + object_xda_gbp_l_reads - object_data_gbp_p_reads - object_xda_gbp_p_reads) /
(object_data_gbp_l_reads + object_xda_gbp_l_reads)

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_data_gbp_p_reads - GBP data physical reads for a table monitor element

The number of times that a group buffer pool (GBP) dependent data page is read into the local buffer pool (LBP) from disk for a table. The page is read from disk into the LBP because the page is not in the GBP. Outside of a DB2 pureScale environment, this value is null.

Table 5. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested data page is found in the LBP, use the following formula, which uses the values of monitor elements:
(object_data_lbp_pages_found + object_xda_lbp_pages_found) / (object_data_l_reads + object_xda_l_reads)
To determine how often a requested data page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_data_gbp_l_reads + object_xda_gbp_l_reads - object_data_gbp_p_reads - object_xda_gbp_p_reads) /
(object_data_gbp_l_reads + object_xda_gbp_l_reads)

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_data_lbp_pages_found - LBP data pages found for a table monitor element

The number of times that a data page for a table is present in the local buffer pool (LBP).

Table 6. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested data page is found in the LBP, use the following formula, which uses the values of monitor elements:
(object_data_lbp_pages_found + object_xda_lbp_pages_found) / (object_data_l_reads + object_xda_l_reads)
To determine how often a requested data page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_data_gbp_l_reads + object_xda_gbp_l_reads - object_data_gbp_p_reads - object_xda_gbp_p_reads) /
(object_data_gbp_l_reads + object_xda_gbp_l_reads)

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_data_l_reads - Buffer pool data logical reads for a table monitor element

The number of data pages that are logically read from the buffer pool for a table.

Table 7. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

This monitor element tracks the number of accesses to the following data:
  • Data that is in the buffer pool when the database manager needs to process the page
  • Data that is read into the buffer pool before the database manager can process the page
Calculate the data page hit ratio by using the following formula, which uses the values of monitor elements:
(1 - (object_data_p_reads + object_xda_p_reads) /
(object_data_l_reads + object_xda_l_reads))
If the hit ratio is low, increasing the number of buffer pool pages might improve performance.

object_data_p_reads - Buffer pool physical data reads for a table monitor element

The number of data pages that are physically read for a table.

Table 8. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

Calculate the data page hit ratio by using the following formula, which uses the values of monitor elements:
(1 - (object_data_p_reads + object_xda_p_reads) /
(object_data_l_reads + object_xda_l_reads))
If the hit ratio is low, increasing the number of buffer pool pages might improve performance.

object_index_gbp_indep_pages_found_in_lbp - Group buffer pool independent index pages found in local buffer pool monitor element

The number of Group Buffer Pool (GBP) independent index pages found in Local Buffer Pool (LBP) by agent. Outside of a DB2 pureScale environment, this value is null.

Table 9. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED
Table 10. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Activities event_activitymetrics ACTIVITY METRICS BASE
Package Cache pkgcache_metrics ACTIVITY METRICS BASE
Unit of Work uow_metrics REQUEST METRICS BASE

object_index_gbp_invalid_pages - GBP invalid index pages for an index monitor element

The number of times that an index page is requested from the group buffer pool (GBP) for an index. The page is requested because the version of the page in the local buffer pool (LBP) is invalid. Outside of a DB2 pureScale environment, this value is null.

Table 11. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested index page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_index_lbp_pages_found / object_index_l_reads
To determine how often a requested index page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_index_gbp_l_reads - object_index_gbp_p_reads) / object_index_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_index_gbp_l_reads - GBP index logical reads for an index monitor element

The number of times that a group buffer pool (GBP) dependent index page is requested from the GBP for an index. The page is requested because a valid version of the page does not exist in the local buffer pool (LBP). Outside of a DB2 pureScale environment, this value is null.

Table 12. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested index page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_index_lbp_pages_found / object_index_l_reads
To determine how often a requested index page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_index_gbp_l_reads - object_index_gbp_p_reads) / object_index_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_index_gbp_p_reads - GBP index physical reads for an index monitor element

The number of times that a group buffer pool (GBP) dependent index page is read into the local buffer pool (LBP) from disk for an index. The page is read from disk into the LBP because the page is not in the GBP. Outside of a DB2 pureScale environment, this value is null.

Table 13. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested index page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_index_lbp_pages_found / object_index_l_reads
To determine how often a requested index page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_index_gbp_l_reads - object_index_gbp_p_reads) / object_index_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_index_lbp_pages_found - LBP index pages found for an index monitor element

The number of times that an index page for an index is present in the local buffer pool (LBP).

Table 14. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested index page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_index_lbp_pages_found / object_index_l_reads
To determine how often a requested index page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_index_gbp_l_reads - object_index_gbp_p_reads) / object_index_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_index_l_reads - Buffer pool index logical reads for an index monitor element

The number of index pages that are logically read from the buffer pool for an index.

Table 15. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED

Usage

This monitor element tracks the number of accesses to the following pages:
  • Index pages that are in the buffer pool when the database manager needs to process the pages
  • Index pages that are read into the buffer pool before the database manager can process the pages
Calculate the index page hit ratio by using the following formula, which uses the values of monitor elements:
(1 - (object_index_p_reads / object_index_l_reads))
If the hit ratio is low, increasing the number of buffer pool pages might improve performance.

object_index_p_reads - Buffer pool index physical reads for an index

The number of index pages that are physically read for an index.

Table 16. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_INDEX table function - get index metrics DATA OBJECT METRICS EXTENDED
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list DATA OBJECT METRICS EXTENDED

Usage

Calculate the index page hit ratio by using the following formula, which uses the values of monitor elements:
(1 - (object_index_p_reads / object_index_l_reads))
If the hit ratio is low, increasing the number of buffer pool pages might improve performance.

object_name - Object name monitor element

A table name or an index name, depending on the value of the objtype monitor element.

Table 17. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_AUTO_MAINT_QUEUE table function - Get information about automatic maintenance jobs Always collected
MON_GET_AUTO_RUNSTATS_QUEUE table function - Retrieve information about objects queued for evaluation Always collected
MON_GET_RTS_RQST table function - Retrieve information about real-time statistics requests Always collected
MON_GET_USAGE_LIST_STATUS table function - Returns the status on a usage list Always collected
Table 18. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Change history utilphaseutilstart Always collected

Usage

For the change history event monitor, if the object_type element is INDEX, PARTIONGROUP, or TABLE, then this is the name of the index, partition group, or table.

object_requested - Requested object monitor element

The type of lock the requester is trying to acquire from the owner. Values can be LOCK for database locks, or TICKET for WLM tickets..

Table 19. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Locking lock_participants  

object_schema - Object schema monitor element

A table schema or an index schema, depending on the value of the objtype monitor element.

Table 20. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_AUTO_MAINT_QUEUE table function - Get information about automatic maintenance jobs Always collected
MON_GET_AUTO_RUNSTATS_QUEUE table function - Retrieve information about objects queued for evaluation Always collected
MON_GET_RTS_RQST table function - Retrieve information about real-time statistics requests Always collected
MON_GET_USAGE_LIST_STATUS table function - Returns the status on a usage list Always collected
Table 21. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Change history utilphaseutilstart Always collected

Usage

For the change history event monitor, if the object_type element is INDEX or TABLE, then this is the schema of the index or table, otherwise it is an empty string.

object_xda_gbp_indep_pages_found_in_lbp - Group buffer pool XDA independent pages found in local buffer pool monitor element

The number of group buffer pool (GBP) independent XML storage object (XDA) data pages found in a local buffer pool (LBP) by an agent. Outside of a DB2 pureScale environment, this value is null.

Table 22. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED
Table 23. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Activities event_activitymetrics ACTIVITY METRICS BASE
Package Cache pkgcache_metrics ACTIVITY METRICS BASE
Unit of Work uow_metrics REQUEST METRICS BASE

object_xda_gbp_invalid_pages - GBP invalid XDA data pages for a table monitor element

The number of times that a data page for an XML storage object (XDA) is requested from the group buffer pool (GBP) for a table. The page is requested because the version of the page in the local buffer pool (LBP) is invalid. Outside of a DB2 pureScale environment, this value is null.

Table 24. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested XDA page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_xda_lbp_pages_found / object_xda_l_reads
To determine how often a requested XDA page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_xda_gbp_l_reads - object_xda_gbp_p_reads) / object_xda_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_xda_gbp_l_reads - GBP XDA data logical read requests for a table monitor element

The number of times that a group buffer pool (GBP) dependent data page for an XML storage object (XDA) is requested from the GBP for a table. The page is requested because a valid version of the page does not exist in the local buffer pool (LBP). Outside of a DB2 pureScale environment, this value is null.

Table 25. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested XDA page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_xda_lbp_pages_found / object_xda_l_reads
To determine how often a requested XDA page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_xda_gbp_l_reads - object_xda_gbp_p_reads) / object_xda_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_xda_gbp_p_reads - GBP XDA data physical read requests for a table monitor element

The number of times that a group buffer pool (GBP) dependent data page for an XML storage object (XDA) is read into the local buffer pool (LBP) from disk for a table. The page is read from disk into the LBP because the page is not in the GBP. Outside of a DB2 pureScale environment, this value is null.

Table 26. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested XDA page is found in the LBP, use the following formula, which uses the values of monitor elements:

object_xda_lbp_pages_found / object_xda_l_reads
To determine how often a requested XDA page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_xda_gbp_l_reads - object_xda_gbp_p_reads) / object_xda_gbp_l_reads

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_xda_lbp_pages_found - LBP XDA data pages found for a table monitor element

The number of times that an XML storage object (XDA) data page for a table is present in the local buffer pool (LBP).

Table 27. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

To determine how often a requested data page is found in the LBP, use the following formula, which uses the values of monitor elements:
(object_data_lbp_pages_found + object_xda_lbp_pages_found) / (object_data_l_reads + object_xda_l_reads)
To determine how often a requested data page is found in the GBP, use the following formula, which also uses the values of monitor elements:
(object_data_gbp_l_reads + object_xda_gbp_l_reads - object_data_gbp_p_reads - object_xda_gbp_p_reads) /
(object_data_gbp_l_reads + object_xda_gbp_l_reads)

LBP and GBP hit rates are important factors in the overall performance of a cluster caching facility. Using these formulas can help you determine whether the LBP or GBP might be limiting the throughput of your database.

object_xda_l_reads - Buffer pool XDA data logical reads for a table monitor element

The number of data pages for XML storage objects (XDAs) that are logically read from the buffer pool for a table.

Table 28. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

This monitor element tracks the number of accesses to the following data:
  • Data that is in the buffer pool when the database manager needs to process the page.
  • Data that is read into the buffer pool before the database manager can process the page
Calculate the data page hit ratio by using the following formula, which uses the values of monitor elements:
(1 - (object_data_p_reads + object_xda_p_reads) /
(object_data_l_reads + object_xda_l_reads))
If the hit ratio is low, increasing the number of buffer pool pages might improve performance.

object_xda_p_reads - Buffer pool XDA data physical reads for a table monitor element

The number of data pages for XML storage objects (XDAs) that are physically read for a table.

Table 29. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - get table metrics DATA OBJECT METRICS EXTENDED
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS EXTENDED

Usage

Calculate the data page hit ratio by using the following formula, which uses the values of monitor elements:
(1 - (object_data_p_reads + object_xda_p_reads) /
(object_data_l_reads + object_xda_l_reads))
If the hit ratio is low, increasing the number of buffer pool pages might improve performance.

objtype - Object type monitor element

The type of object for which monitoring data is being reported. This monitor element is an alias of the object_type monitor element.

Table 30. Table Function Monitoring Information
Table Function Monitor Element Collection Level
ADMIN_GET_TAB_COMPRESS_INFO table function - estimate compression savings ACTIVITY METRICS BASE
ADMIN_GET_TAB_DICTIONARY_INFO table function - report properties of existing table dictionaries ACTIVITY METRICS BASE
MON_GET_AUTO_MAINT_QUEUE table function - Get information about automatic maintenance jobs ACTIVITY METRICS BASE
MON_GET_AUTO_RUNSTATS_QUEUE table function - Retrieve information about objects queued for evaluation ACTIVITY METRICS BASE
MON_GET_PAGE_ACCESS_INFO table function - Get buffer pool page waiting information ACTIVITY METRICS BASE
MON_GET_RTS_RQST table function - Retrieve information about real-time statistics requests ACTIVITY METRICS BASE
MON_GET_USAGE_LIST_STATUS table function - Returns the status on a usage list ACTIVITY METRICS BASE
PD_GET_DIAG_HIST table function - Return records from a given facility ACTIVITY METRICS BASE
Table 31. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Change history utilphase
utilstart		 Always collected

Usage Notes

  • When this element is returned by the ADMIN_GET_TAB_COMPRESS_INFO table function or the ADMIN_GET_TAB_DICTIONARY_INFO table function, the returned value for the object_type monitor element can be either 'XML' or 'DATA'.
  • When this element is returned by the MON_GET_RTS_RQST table function, the returned value for the object_type monitor element is 'TABLE'.
  • When this element is returned by the MON_GET_AUTO_MAINT_QUEUE table function, the returned value for the object_type monitor element can be 'DATABASE', 'TABLE', 'NICKNAME', or 'VIEW'.
  • When this element is returned by the MON_GET_AUTO_RUNSTATS_QUEUE table function, the returned value for the object_type monitor element can be 'TABLE', 'NICKNAME', or 'VIEW'.
  • When this element is returned by the change history event monitor, the returned value for the object_type monitor element can be 'DATABASE', 'INDEX', 'PARTITIONGROUP', 'TABLE' or 'TABLESPACE'.

olap_func_overflows - OLAP Function Overflows monitor element

The number of times that OLAP function data exceeded the available sort heap space.

Table 32. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Database dbase Basic
Application appl Basic
For snapshot monitoring, this counter can be reset.
Table 33. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Database event_db Always collected
Connection event_conn Always collected

Usage

At the database level, use this element in conjunction with total_olap_funcs to calculate the percentage of OLAP functions that overflowed to disk. If this percentage is high and the performance of applications using OLAP functions needs to be improved, then you should consider increasing the sort heap size.

At the application level, use this element to evaluate OLAP function performance for individual applications.

open_cursors - Number of Open Cursors monitor element

The number of cursors currently open for an application.

Table 34. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
DCS Application dcs_appl Statement
Usage
Use this element to assess how much memory is being allocated. The amount of memory allocated by the DB2 client, DB2 Connect, or the database agent on the target database is related to the number of cursors that are currently open. Knowing this information can help with capacity planning. For example, each open cursor that is doing blocking has a buffer size of RQRIOBLK. If deferred_prepare is enabled, then two buffers will be allocated.

This element does not include cursors that were closed by an early close. An early close occurs when the host database returns the last record to the client. The cursor is closed at the host and gateway, but is still open at the client. Early close cursors can be set using the DB2 Call Level Interface.

open_loc_curs - Open Local Cursors monitor element

The number of local cursors currently open for this application, including those cursors counted by open_loc_curs_blk.

Element identifier
open_loc_curs
Element type
gauge
Table 35. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Application appl Basic
Usage
You may use this element in conjunction with open_loc_curs_blk to calculate the percentage of local cursors that are blocking cursors. If the percentage is low, you may be able to improve performance by improving the row blocking in the application.

For cursors used by remote applications, see open_rem_curs.

open_loc_curs_blk - Open Local Cursors with Blocking monitor element

The number of local blocking cursors currently open for this application.

Element identifier
open_loc_curs_blk
Element type
gauge
Table 36. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Application appl Basic
Usage
You may use this element in conjunction with open_loc_curs to calculate the percentage of local cursors that are blocking cursors. If the percentage is low, you may be able to improve performance by improving the row blocking in the application:
  • Check the pre-compile options for record blocking for treatment of ambiguous cursors
  • Redefine cursors to allow for blocking (for example, if possible, specify FOR FETCH ONLY on your cursors).

rej_curs_blk and acc_curs_blk provide additional information that may help you tune your configuration parameters to improve row blocking in your application.

For blocking cursors used by remote applications, see open_rem_curs_blk.

open_rem_curs - Open Remote Cursors monitor element

The number of remote cursors currently open for this application, including those cursors counted by open_rem_curs_blk.

Element identifier
open_rem_curs
Element type
gauge
Table 37. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Application appl Basic
Usage
You may use this element in conjunction with open_rem_curs_blk to calculate the percentage of remote cursors that are blocking cursors. If the percentage is low, you may be able to improve performance by improving the row blocking in the application. See open_rem_curs_blk for more information.

For the number of open cursors used by applications connected to a local database, see open_loc_curs.

open_rem_curs_blk - Open Remote Cursors with Blocking monitor element

The number of remote blocking cursors currently open for this application.

Element identifier
open_rem_curs_blk
Element type
gauge
Table 38. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Application appl Basic
Usage
You can use this element in conjunction with open_rem_curs to calculate the percentage of remote cursors that are blocking cursors. If the percentage is low, you may be able to improve performance by improving the row blocking in the application:
  • Check the pre-compile options for record blocking for treatment of ambiguous cursors
  • Redefine cursors to allow for blocking (for example, if possible, specify FOR FETCH ONLY on your cursors).

rej_curs_blk and acc_curs_blk provide additional information that may help you tune your configuration parameters to improve row blocking in your application.

For the number of open blocking cursors used by applications connected to a local database see open_loc_curs_blk.

os_level - Operating system level monitor element

The modification level of the operating system running on this host. Reported for Linux® systems only.

Table 39. Table Function Monitoring Information
Table Function Monitor Element Collection Level
ENV_GET_SYSTEM_RESOURCES table function - Return system information Always collected

outbound_appl_id - Outbound Application ID monitor element

This identifier is generated when the application connects to the DRDA host database. It is used to connect the DB2 Connect gateway to the host, while the appl_id monitor element is used to connect a client to the DB2 Connect gateway.

Element identifier
outbound_appl_id
Element type
information
Table 43. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
DCS Application dcs_appl_info Basic

Usage

You may use this element in conjunction with appl_id to correlate the client and server parts of the application information.

This identifier is unique across the network.

This element will be blank when the gateway concentrator is on, or if the DCS application is not in a logical unit of work.
Format
Network.LU Name.Application instance
Example
CAIBMTOR.OSFDBM0.930131194520

outbound_bytes_received - Outbound Number of Bytes Received monitor element

The number of bytes received by the DB2 Connect gateway from the host, excluding communication protocol usage (for example, TCP/IP). For the data transmission level: Number of bytes received by the DB2 Connect gateway from the host during the processing of all the statements that used this number of data transmissions.

Table 44. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
DCS Database dcs_dbase Basic
DCS Application dcs_appl Basic
DCS Statement dcs_stmt Statement
Data Transmission stmt_transmissions Statement

For snapshot monitoring at the statement level, this counter cannot be reset. This counter can be reset at other levels.

Usage

Use this element to measure the throughput from the host databases to the DB2 Connect gateway.

outbound_bytes_received_bottom - Minimum Outbound Number of Bytes Received monitor element

The lowest number of bytes received per statement or chain by the DB2 Connect gateway from the host during the processing of all the statements or chains against this DCS database, or in this DCS application, that used this number of data transmissions.

Table 45. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Data Transmission stmt_transmissions Statement
Usage
Use this element in conjunction with "outbound number of bytes received" as yet another parameter that illustrates the throughput from the host database to the DB2 Connect gateway.

outbound_bytes_received_top - Maximum Outbound Number of Bytes Received monitor element

Maximum number of bytes received per statement or chain by the DB2 Connect gateway from the host during the processing of all the statements or chains against this DCS database, or in this DCS application, that used this number of data transmissions.

Table 46. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Data Transmission stmt_transmissions Statement
Usage
Use this element in conjunction with "outbound number of bytes received" as yet another parameter that illustrates the throughput from the host database to the DB2 Connect gateway.

outbound_bytes_sent - Outbound Number of Bytes Sent monitor element

The number of bytes sent by the DB2 Connect gateway to the host, excluding communication protocol usage (for example, TCP/IP). For the data transmission level: Number of bytes sent by the DB2 Connect gateway to the host during the processing of all the statements that used this number of data transmissions.

Table 47. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
DCS Database dcs_dbase Basic
DCS Application dcs_appl Basic
DCS Statement dcs_stmt Statement
Data Transmission stmt_transmissions Statement
For snapshot monitoring at the statement level, this counter cannot be reset. This counter can be reset at other levels.
Usage
Use this element to measure the throughput from the DB2 Connect gateway to the host database.

outbound_bytes_sent_bottom - Minimum Outbound Number of Bytes Sent monitor element

The lowest number of bytes sent per statement or chain by the DB2 Connect gateway to the host during the processing of all the statements or chains against this DCS database, or in this DCS application, that used this number of data transmissions.

Table 48. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Data Transmission stmt_transmissions Statement
Usage
Use this element in conjunction with "outbound number of bytes sent" as yet another parameter that illustrates the throughput from the DB2 Connect Gateway to the host database.

outbound_bytes_sent_top - Maximum Outbound Number of Bytes Sent monitor element

Maximum number of bytes sent per statement or chain by the DB2 Connect gateway to the host during the processing of all the statements or chains against this DCS database, or in this DCS application, that used this number of data transmissions.

Table 49. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Data Transmission stmt_transmissions Statement
Usage
Use this element in conjunction with "outbound number of bytes sent" as yet another parameter that illustrates the throughput from the DB2 Connect Gateway to the host database.

outbound_comm_address - Outbound Communication Address monitor element

This is the communication address of the target database. For example, it could be an IP address and port number for TCP/IP.

Element identifier
outbound_comm_address
Element type
information
Table 50. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Application appl_info Basic
DCS Application dcs_appl_info Basic
Usage
Use this element for problem determination on DCS applications.

outbound_comm_protocol - Outbound Communication Protocol monitor element

The communication protocol used between the DB2 Connect gateway and the host.

Table 51. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
DCS Application dcs_appl_info Basic

Usage

Use this element for problem determination on DCS applications. The valid value is:
  • SQLM_PROT_TCPIP

outbound_sequence_no - Outbound Sequence Number monitor element

This element will be blank when the gateway concentrator is on, or if the DCS application is not in a logical unit of work.

Table 52. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
DCS Application dcs_appl_info Basic

overflow_accesses - Accesses to overflowed records monitor element

The number of accesses (reads and writes) to overflowed rows of this table.

Table 53. Table Function Monitoring Information
Table Function Monitor Element Collection Level
MON_GET_TABLE table function - Get table metrics Always collected
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list DATA OBJECT METRICS BASE
Table 54. Snapshot Monitoring Information
Snapshot Level Logical Data Grouping Monitor Switch
Table table Basic
For snapshot monitoring, this counter can be reset.
Table 55. Event Monitoring Information
Event Type Logical Data Grouping Monitor Switch
Tables event_table Always collected

Usage

Overflowed rows indicate that data fragmentation has occurred. If this number is high, you may be able to improve table performance by reorganizing the table using the REORG utility, which cleans up this fragmentation.

A row overflows if it is updated and no longer fits in the data page where it was originally written. This usually happens as a result of an update of a VARCHAR or an ALTER TABLE statement.