Monitoring Agent for Db2 metrics

The metrics for Monitoring Agent for Db resource types collect data for monitoring with IBM Cloud Pak for Multicloud Management. Every Monitoring Agent for Db2 resource type defines a set of dimensions and metrics. The descriptions provide such information as data type, dimension key, and metric unit.

Resource db2Database

Shows monitoring metrics for set of databases present on DB2 server Instance. The following section lists the metrics, dimensions and components of Resource db2Database.

Metrics

The following metrics are available for the resource.

Active Sorts

• The number of sorts in the database with the allocated sort heap. Use this value with the Sort Heap Allocated attribute to determine the average sort heap space that is used by each sort. If the SORTHEAP configuration parameter is substantially larger than the average sort heap used, you can reduce the value of this parameter.
• The type is int.
• The unit is sorts.

Agents Top

• The maximum number of agents (at one time) associated with applications that are connected to the monitored database. Use this attribute to indicate how well the intra-query parallelism was realized. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Appls Cur Cons

• The number of applications that are currently connected to the monitored database. Use this attribute to understand the level of activity within a database and the amount of system resource that is being used.
• The type is int.
• The unit is applications.

Avg Lock Wait Time

• The average elapsed time (in milliseconds) that was spent waiting for a lock. If the average lock wait time is high, identify the applications that hold many locks, or have lock escalations, with a focus on tuning your applications to improve concurrency, if appropriate. If the average lock waiting time is high due to escalations, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low.
• The type is int.
• The unit is milliseconds.

Avg Pool Read Time

• The average elapsed time for a read request. This value is derived by dividing the value of the Pool Read Time attribute by the value of the Pool Total Reads attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Avg Pool Write Time

• The average elapsed time for a write request. This value is derived by dividing the value of the Pool Write Time attribute by the value of the Pool Total Writes attribute. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Avg Sort Time

• The average derived by dividing value of the Total Sort Time attribute by the value of the Total Sorts attribute. The average is expressed as elapsed time. at the database or application level, this attribute can indicate whether sorting is a performance issue. Elapsed times are affected by system load. The more processes you have running, the higher this elapsed time value is.
• The type is int.
• The unit is Milliseconds.

Cat Cache Heap Full

• The number of times that an insert into the catalog cache failed because of a heap full condition in the database heap. The catalog cache draws its storage dynamically from the database heap. Even if the cache storage has not reached its limit, inserts into the catalog cache might fail due to a lack of space in the database heap. If the catalog cache heap full count is not zero, you can correct the insert failure condition by increasing the database heap size or by reducing the catalog cache size. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is failures.

Cat Cache Hit Ratio

• The percentage of catalog sections in the cache. This ratio indicates how well the catalog cache is avoiding catalog accesses. If the ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that you must increase the size of the catalog cache. You must expect a large ratio immediately after the first connection to the database.
• The type is double.
• The unit is percent.

Cat Cache Inserts

• The number of times that the system tried to insert table descriptor information into the catalog cache. Table descriptor information is inserted into the cache following a failed lookup to the catalog cache while processing a table, view, or alias reference in an SQL statement. The catalog cache inserts value includes attempts to insert table descriptor information that fail due to catalog cache overflow and heap full conditions. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is attempts.

Cat Cache Lookups

• The number of times that the catalog cache was referenced to obtain table descriptor information. This attribute includes both successful and unsuccessful accesses to the catalog cache. This attribute is used in calculating the catalog cache hit ratio. This ratio indicates how well the catalog cache is avoiding catalog accesses. If the ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that you must increase the size of the catalog cache. You must expect a large ratio immediately following the first connection to the database. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Cat Cache Overflows

• The number of times that an insert into the catalog cache failed because the catalog cache was full. If the catalog cache overflows value is large, the catalog cache might be too small for the workload. Increasing the size of the catalog cache might improve its performance. If the workload includes transactions that compile a large number of SQL statements referencing many tables, views, and aliases in a single unit of work, compiling fewer SQL statements in a single transaction might improve the performance of the catalog cache. Or if the workload includes the binding of packages containing many SQL statements referencing many tables, views or aliases, you might want to split the packages so that they include fewer SQL statements to improve performance. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is failures.

Commit SQL Stmts

• The total number of SQL COMMIT statements that have been attempted. A small rate of change in this counter during the monitor period might indicate that applications are not doing frequent commits. The lack of frequent commits can lead to problems with logging and data concurrency. You can also use this attribute to calculate the total number of units of work by calculating the sum of the following values:
  • Commit statements attempted
  • Internal commits
  • Rollback statements attempted
  • Internal rollbacks
  The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Connections Top

• The highest number of simultaneous connections to the database since the database was activated. You can calculate the current number of connections at the time the snapshot was taken by adding the Remote Connections to Database Manager and Local Connections attributes. Use this attribute to evaluate the setting of the MAXAPPLS configuration parameter. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Coord Agents Top

• The maximum number of coordinating agents working at one time. The MAXCAGENTS configuration parameter determines the number of coordinating agents that can be executing concurrently. If the peak number of coordinating agents results in a workload that is too high for this node, you can reduce the MAXCAGENTS configuration parameter. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

CPU Used

• The percentage usage of CPU by the database.
• The type is int.
• The unit is milliseconds.

Database Application Locks Held

• The number of locks that the applications currently hold. If the monitor information is at the database level, this number represents the total number of locks the database applications currently hold. If the information is at the application level, this number represents the total number of locks the application agents currently hold.
• The type is int.
• The unit is locks.

DDL SQL Stmts

• The number of SQL Data Definition Language (DDL) statements that ran. Use this attribute to determine the level of database activity at the application or database level. DDL statements are expensive to run because of their impact on the system catalog tables. As a result, if the value of this attribute is high, you must determine the cause and possibly restrict the identified activity from being performed. You can also use this attribute to determine the percentage of DDL activity using the following formula: divide the number of DDL SQL statements by the total number of statements. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Deadlocks

• The total number of deadlocks that have occurred. This attribute can indicate that applications are experiencing contention problems. To resolve the problem, determine in which applications (or application processes) the deadlock are occurring. You can then modify the application to enable it to run concurrently. Some applications, however, might not be capable of running concurrently.
• The type is int.
• The unit is deadlocks.

Direct Read Reqs

• The number of requests to perform a direct read of one or more sectors of data. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Direct Read Time

• The elapsed time (in milliseconds) required to perform the direct reads. Use the following formula to calculate the average direct read time per sector: direct read time / direct reads from database A high average time might indicate an I/O conflict. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Direct Reads

• The number of read operations that occurred without using the buffer pool. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database/direct read requests. When you use the system monitors to track I/O, this attribute helps to distinguish a database I/O from a non-database I/O on the device.
• The type is int.
• The unit is reads.

Direct Write Reqs

• The number of requests to perform a direct write of one or more sectors of data. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Direct Write Time

• The elapsed time (in milliseconds) required to perform the direct writes. Use the following formula to calculate the average direct write time per sector: direct write time / direct writes to database A high average time might indicate an I/O conflict. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Direct Writes

• The number of write operations that occurred without using the buffer pool. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database/direct write requests. When you use the system monitors to track I/O, this attribute helps to distinguish a database I/O from a non-database I/O on the device.
• The type is int.
• The unit is writes.

Dynamic SQL Stmts

• The number of dynamic SQL statements that were attempted. Use this attribute to calculate the total number of successful SQL statements at the database or application level by performing the following operations:
  1. Add the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Failed SQL Stmts

• The number of SQL statements that were attempted, but failed. This count includes all SQL statements that received a negative SQLCODE. Use this attribute to calculate the total number of successful SQL statements at the database or application level by performing the following operations:
  1. Add the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This attribute can also help you to determine the reasons for poor performance; failed statements indicate time wasted by the database manager, which results in lower throughput for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is failures.

Files Closed

• The total number of database files closed. The database manager opens files for reading and writing into and out of the buffer pool. The maximum number of database files open by an application at any time is controlled by the MAXFILOP configuration parameter. If the maximum is reached, one file is closed before the new file is opened. Note that the actual number of files opened might not equal the number of files closed. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Hash Join Overflows

• The number of times that hash join data exceeded the available sort heap space. At the database level, if the percentage of Hash Join Small Overflows is greater than 10% of this value, you must consider increasing the sort heap size. You can use values at the application level to evaluate hash join performance for individual applications. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Hash Join Small Overflows

• The number of times that hash join data exceeded the available sort heap space by less than 10%. If this value and the value of the Hash Join Overflows attribute are high, consider increasing the sort heap threshold. If this value is greater than 10% of Hash Join Overflows, consider increasing the sort heap size. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Int Deadlock Rollbacks

• The total number of forced rollbacks initiated by the database manager due to a deadlock. The database manager initiates a rollback for the current unit of work in an application that is experiencing a deadlock. This attribute shows the number of deadlocks that have been broken. It can indicate the possibility of concurrency problems. It is also important because internal rollbacks due to deadlocks can cause performance degradation. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Int Rollbacks

• The total number of rollbacks initiated internally by the database manager. An internal rollback occurs when any of the following operations cannot complete successfully:
  • A reorganization
  • An import
  • A bind or pre-compile
  • An application that ends as a result of a deadlock situation or lock timeout situation
  • An application that ends without executing an explicit COMMIT or ROLLBACK statement (on Windows systems).
  Use this attribute to calculate the total number of units of work by calculating the sum of the following values: commit statements attempted, internal commits, rollback statements attempted, and internal rollbacks. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Lock Escals

• The number of times the lock escalations occurred for several row locks to a table lock. A lock is escalated when the total number of locks that are held by an application reaches the maximum amount of lock list space available to the application, or the lock list space that the applications use approaches the total lock list space. This data item includes the count of all lock escalations, including exclusive lock escalations. When an application reaches the maximum number of locks that are permitted and no locks are available to escalate, the application uses the space in the lock list that is allocated for other applications. When the entire lock list is full, an error occurs. The value format is an integer.
• The type is int.
• The unit is escalations.

Lock List in Use

• The total amount of lock list memory (in bytes) that is currently in use. This attribute can be used with the locklist configuration parameter to calculate the lock list utilization. If the lock list utilization is high, you might want to consider increasing the size of that parameter. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Lock Timeouts

• The number of times when a request to lock an object timed out instead of being granted. Use this attribute to adjust the setting for the LOCKTIMEOUT database configuration parameter. The high lock timeouts indicate that an application might be holding locks for long duration. In such a case, analyze some other attributes related to locks and deadlocks to determine whether the application problem exists. If the value for the LOCKTIMEOUT parameter is set too high, applications might wait for longer duration to acquire a lock.
• The type is int.
• The unit is timeouts.

Lock Wait Time

• The total elapsed time (in milliseconds) that was spent waiting for a lock. At the database level, this is the total amount of elapsed time of all applications that were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction waited for a lock to be granted. Use this attribute with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at the database or the application connection level. If the average wait time for a lock is high, identify the applications with many locks or lock escalations for improving concurrency of applications. If the average wait time for a lock is high due to escalations, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low.
• The type is int.
• The unit is milliseconds.

Lock Waits

• The total number of times when the applications or connections waited for locks. At the database level, the lock waiting value is the total number of times that applications waited for locks within the database. At the application-connection level, the lock waiting value is the total number of times that this connection requested a lock but waited because another connection was already holding a lock on the data. Use this attribute to calculate the average wait time for a lock. If the average lock wait time is high, you must look for applications that hold many locks, or have lock escalations, with a focus on tuning your applications to improve concurrency.
• The type is int.
• The unit is waits.

Locks Waiting

• The number of agents that are currently waiting on a lock.
• The type is int.
• The unit is agents.

Log Reads

• The number of log pages read from disk by the logger. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Log Writes

• The number of log pages written to disk by the logger. Use this attribute with an operating system monitor to quantify the amount of I/O on a device that is attributable to database activity. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Longest Lock Wait Time

• The longest time for which an application waited for a lock.
• The type is int.
• The unit is milliseconds.

Maximum Connection

• The maximum number of applications that can connect to the monitored database.
• The type is int.
• The unit is applications.

Memory Used Pct

• The percentage usage of system memory by the database.
• The type is double.
• The unit is percent.

Num Assoc Agents

• The current number of subagents associated with all applications that are connected to the monitored database. Use this attribute to evaluate the settings for the agent configuration parameters. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is subagents.

Pkg Cache Hit Ratio

• The percentage of package sections that were found in the cache. This ratio tells you whether the package cache is being used effectively. If the hit ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that the package cache must be increased.
• The type is double.
• The unit is percent.

Pkg Cache Inserts

• The total number of times that a requested section was not available for use and had to be loaded into the package cache. This count includes any implicit prepares performed by the system. By using the Package Cache Lookups attribute, you can calculate the package cache hit ratio using the following formula: 1 - (Package Cache Inserts / Package Cache Lookups) See the Package Cache Lookups attribute for information about using this attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Pkg Cache Lookups

• The number of times that an application looked for a section or package in the package cache. At a database level, it indicates the overall number of references since the database was started, or monitor data was reset. Note that this counter includes the cases where the section is already loaded in the cache and when the section has to be loaded into the cache. To calculate the package cache hit ratio use the following formula: 1 - (Package Cache Inserts / Package Cache Lookups) The package cache hit ratio tells you whether the package cache is being used effectively. If the hit ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that the package cache must be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Pool Async Data Read Reqs

• The number of asynchronous read requests. To calculate the average number of data pages read per asynchronous request, use the following formula: buffer pool asynchronous data reads / buffer pool asynchronous read requests This average can help to determine the amount of asynchronous I/O in each interaction with the prefetcher. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Pool Async Data Reads

• The number of pages read asynchronously into the buffer pool. Use this attribute with the Buffer Pool Data Physical Reads attribute to calculate the number of physical reads that were performed synchronously (that is, physical data page reads that were performed by database manager agents). Use the following formula: buffer pool data physical reads - buffer pool synchronous data reads By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Pool Async Data Writes

• The number of times a buffer pool data page was physically written to disk by an asynchronous page cleaner or by a prefetcher. A prefetcher might have written dirty pages to disk to make space for the pages being prefetched. Use this attribute with the Buffer Pool Data Writes attribute to calculate the number of physical write requests that were performed synchronously (that is, physical data page writes that were performed by database manager agents). Use the following formula: buffer pool data writes - buffer pool asynchronous data writes By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Pool Async Index Reads

• The number of index pages read asynchronously into the buffer pool by a prefetcher. Asynchronous reads are performed by database manager prefetchers. Use this attribute with the Buffer Pool Index Physical Reads attribute to calculate the number of physical reads that were performed synchronously (that is, physical index page reads that were performed by database manager agents). Use the following formula: buffer pool index physical reads - buffer pool asynchronous index reads By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Pool Async Index Writes

• The number of times a buffer pool index page was physically written to disk by an asynchronous page cleaner or a prefetcher. A prefetcher might have written dirty pages to disk to make space for the pages being prefetched. Use this attribute with the Buffer Pool Index Writes attribute to calculate the number of physical index write requests that were performed synchronously. That is, physical index page writes that were performed by database manager agents. Use the following formula: buffer pool index writes - buffer pool asynchronous index writes By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Pool Async Read Time

• The total elapsed time spent reading by database manager prefetchers. Use this attribute to calculate the elapsed time for synchronous reading, using the following formula: total buffer pool physical read time - buffer pool synchronous read time You can also use this attribute to calculate the average asynchronous read time using the following formula: buffer pool asynchronous read time / buffer pool asynchronous data reads These calculations can be used to understand the I/O work being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Pool Async Write Time

• The total elapsed time spent writing data or index pages from the buffer pool to disk by database manager page cleaners. Calculate the elapsed time spent writing pages synchronously by subtracting the value of the Pool Async Write Time attribute from the value of the Pool Physical Write Time attribute. You can also use this attribute to calculate the average asynchronous read time by performing the following operations:
  1. Add the Pool Async Data Writes and the Pool Async Index Writes.
  2. Divide the Pool Async Write Time by the sum from step 1.
  These calculations can be used to understand the I/O work being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Pool Data from Estore

• Number of buffer pool data pages copied from extended storage. Required pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Pool Data L Reads

• The number of logical read requests for data pages that have gone through the buffer pool. This count includes accesses to the following data:
  • Data that is already 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.
  By using the Pool Data Physical Reads attribute, you can calculate the data page hit ratio for the buffer pool as follows: 1 - (buffer pool data physical reads / buffer pool data logical reads) By using the Pool Data Physical Reads, Pool Index Physical Reads, and Pool Index Logical Reads attributes, you can calculate the overall buffer pool hit ratio as follows: 1 - ((buffer pool data physical reads + buffer pool index physical reads) / (buffer pool data logical reads + buffer pool index logical reads)) Increasing buffer pool size generally improves the hit ratio until you reach a point of diminishing returns. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Pool Data P Reads

• The number of read requests that required I/O to get data pages into the buffer pool. See Pool Data Logical Reads and Pool Async Data Reads attributes for information about how to use this attribute. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Pool Data to Estore

• Number of buffer pool data pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Pool Data Writes

• The number of times a buffer pool data page was physically written to disk. A buffer pool data page is written to disk for the following reasons:
  • To free a page in the buffer pool so another page can be read
  • To flush the buffer pool.
  If a buffer pool data page is written to disk for a high percentage of Buffer Pool Data Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Pool Drty Pg Steal Clns

• Buffer Pool Victim Page Cleaners Triggered is the number of times a page cleaner was invoked because a synchronous write was needed during the victim buffer replacement for the database. Use this attribute, in combination with others, to evaluate the number of page cleaners that are defined. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is invocations.

Pool Drty Pg Thrsh Clns

• The number of times a page cleaner was invoked because a buffer pool had reached the dirty page threshold criterion for the database. When the number of dirty pages in the pool exceeds this value, the cleaners are triggered. If this value is set too low, pages might be written out too early, requiring them to be read back in. If set too high, too many pages might accumulate, requiring users to write out pages synchronously. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is invocations.

Pool Hit Ratio

• The buffer pool hit ratio (as a percentage). The sum of the Pool Data Logical Reads and Pool Index Logical Reads attributes is divided by the value of the Pool Total Reads attribute to derive the pool hit ratio. Use this attribute to determine whether buffer pool assignment is efficient. If the pool hit ratio is low, increasing the number of buffer pool pages might improve performance.
• The type is double.
• The unit is percent.

Pool Index from Estore

• Number of buffer pool index pages copied from extended storage. Required index pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Pool Index L Reads

• The number of logical read requests for index pages that have gone through the buffer pool. This count includes accesses to the following index pages:
  • Pages that are already in the buffer pool when the database manager needs to process the page.
  • Pages that are read into the buffer pool before the database manager can process the page.
  By using the Buffer Pool Index Physical Reads attribute, you can calculate the index page hit ratio for the buffer pool as follows: 1 - (buffer pool index physical reads / buffer pool index logical reads) To calculate the overall buffer pool hit ratio, see the Buffer Pool Data Logical Reads attribute. If the hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool. See the Pool Index Logical Reads attribute for information about how to use this element. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Pool Index to Estore

• Number of buffer pool index pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Pool Index Writes

• The number of times a buffer pool index page was physically written to the disk. If this number is high, increase the number of buffer pool pages for the database to improve the performance.
• The type is int.
• The unit is writes.

Pool LSN Gap Clns

• The number of times a page cleaner was invoked because the logging space used had reached a predefined criterion for the database. Use this attribute to evaluate whether you have enough space for logging, and whether you need more log files or larger log files. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is invocations.

Pool Read Time

• The total amount of elapsed time spent processing read requests that caused data or index pages to be physically read from buffer pool to disk. Use this attribute with the Buffer Pool Data Physical Reads and Buffer Pool Index Physical Reads attributes to calculate the average page-read time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Pool Sync Data Reads

• The number of physical data page reads that were performed by database manager agents. This value is derived by subtracting the value of the Pool Async Data Reads attribute from the Pool Data Physical Reads attribute. By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Pool Sync Index Reads

• The number of index pages read synchronously (that is, physical index page reads that were performed by database manager agents) into the buffer pool. This value is derived by subtracting the value of the Pool Async Index Reads attribute from Pool Index Physical Reads attribute. By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Pool Total Reads

• The total number of read requests that required I/O to get data pages and index pages into the buffer pool. This attribute is the total of the Pool Data Physical Reads and Pool Index Physical Reads attributes. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Pool Total Writes

• The total number of write requests. This attribute is the total of the Pool Data Writes and Pool Index Writes attributes. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal.
• The type is int.
• The unit is writes.

Pool Write Time

• The total amount of time spent physically writing data or index pages from the buffer pool to disk. Use this attribute with the Buffer Pool Data Writes and Buffer Pool Index Writes attributes to calculate the average page-write time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Rollback SQL Stmts

• The total number of SQL ROLLBACK statements that have been attempted. A rollback can result from an application request, a deadlock, or an error situation. This attribute counts only the number of rollback statements issued from applications. At the application level, this attribute can help you determine the level of database activity for the application and the amount of conflict with other applications. At the database level, it can help you determine the amount of activity in the database and the amount of conflict between applications on the database. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Rows Deleted

• The number of row deletions attempted. Use this attribute to gain insight into the current level of activity within the database manager. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deletes.

Rows Inserted

• The number of row insertions attempted. Use this attribute to gain insight into the current level of activity within the database manager. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Rows Selected

• The number of rows that have been selected and returned to the application. Use this attribute to gain insight into the current level of activity within the database manager. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is selects.

Rows Updated

• The number of row updates attempted. Use this attribute to gain insight into the current level of activity within the database manager. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is updates.

Sec Log Used Top

• The maximum amount of secondary log space (in bytes) that has been used. Use this attribute with the Secondary Logs Allocated and Total Log Used Top attributes to show the current dependency on secondary logs. If this value is high, you might need larger log files, more primary log files, or more frequent COMMIT statements within your application. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Sec Logs Allocated

• The total number of secondary log files that are currently being used for the database. Use this attribute with the Secondary Log Used Top and Total Log Used Top attributes to show the current dependency on secondary logs. If this value is consistently high, you might need larger log files, more primary log files, or more frequent COMMIT statements within your application. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Select SQL Stmts

• The number of SQL SELECT statements that ran. Use this attribute to determine the level of database activity at the application or database level. You can also use the following formula to determine the ratio of SELECT statements to the total statements by performing the following operations:
  • Add the number of static SQL statements attempted and dynamic SQL statements attempted
  • Divide the resulting total by the number of select SQL statements that ran
  The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is selects.

Sort Heap Allocated

• The total number of allocated pages of sort heap space for all sorts at the level chosen (database manager or database) and at the time the snapshot was taken. Memory estimates do not include sort heap space. If excessive sorting occurs, add the extra memory (used for the sort heap) to the base memory requirements for running the database manager. Generally, the larger the sort heap, the more efficient the sort. Appropriate use of indexes can reduce the amount of sorting required. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Sort Overflows

• The total number of sorts that ran out of sort heap space and might have required disk space for temporary storage. at the database or application level, use this attribute with the Total Sorts attribute to calculate the percentage of sorts that required overflow to disk. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Sort Overflows Percent

• The percentage of sorts that ran out of sort heap space and might have required disk space for temporary storage. This percentage is calculated by dividing the value of the Sort Overflows attribute by the value of the Total Sorts attribute. at the database or application level, use this attribute to evaluate the percentage of sorts that required overflow to disk. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter.
• The type is double.
• The unit is percent.

SQL Stmts Failed Percent

• The percentage of SQL statements that failed to run successfully. This value is derived by dividing the value of the Failed SQL Statements attribute by the value of the Total SQL Statements attribute. Use this attribute to determine whether an application has some design issues.
• The type is double.
• The unit is percent.

SQL Stmts Rollback Percent

• The percentage of SQL statements that resulted in a rollback. This value is derived by dividing the value of the Rollback SQL Statements attribute by the value of the Total SQL Statements attribute. Use this attribute to determine whether an application has some design issues.
• The type is double.
• The unit is percent.

Static SQL Stmts

• The number of static SQL statements that were attempted. Use this attribute to calculate the total number of successful SQL statements at the database or application level by performing the following operations:
  1. Add the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Total Cons

• The number of connections to the database since the first connect, activate, or last reset (coordinator agents). Use this attribute with the Database Activation Timestamp and the Start Database Manager Timestamp attributes to calculate the frequency at which applications have connected to the database. The first connect to a database (such as an initial buffer pool allocation) causes extra overhead. If the frequency of connects is low, it might be beneficial to activate the database explicitly using the ACTIVATE DATABASE command before connecting any other application. As a result, subsequent connects are processed at a higher rate. The following value is valid: When you reset this attribute, the value of the attribute is set to the number of applications that are currently connected, instead of zero. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Total Hash Joins

• The total number of hash joins that ran. At the database or application level, use this value with the Hash Join Overflows attribute and the Hash Join Small Overflows attribute to determine if a significant percentage of hash joins would benefit from modest increases in the sort heap size. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Total Hash Loops

• The total number of times that a single partition of a hash join was larger than the available sort heap space. This attribute might indicate inefficient execution of hash joins (the sort heap size is too small or the sort heap threshold is too small). Use this value with the other hash join variables to tune the sort heap size (SORTHEAP) and sort heap threshold (SHEAPTHRES) configuration parameters. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Total Log Used Pct

• The percentage of used log space in the database.
• The type is double.
• The unit is percent.

Total Log Used Top

• The maximum amount of total log space (in bytes) that has been used. Use this attribute to evaluate the amount of primary log space that is allocated. Comparing the value of this attribute with the amount of primary log space that is allocated can help you to evaluate the configuration parameter settings. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Total Sec Cons

• The number of connections made by a subagent to the database at the node. Use this attribute with the Connects Since Database Activation, Database Activation Timestamp, and the Start Database Manager Timestamp attributes to calculate the frequency at which applications have connected to the database. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Total Sort Time

• The total elapsed time (in milliseconds) for all sorts that ran. at the database or application level, use this attribute with the Total Sorts attribute to calculate the average sort time, which can indicate whether sorting is a performance issue. Elapsed times are affected by system load. The more processes you have running, the higher this elapsed time value is. The following value is valid:.
• The type is int.
• The unit is milliseconds.

Total Sorts

• The total number of sorts that ran. at the database or application level, use this value with the Sort Overflows attribute to calculate the percentage of sorts that need more heap space. You can also use it with the Total Sort Time attribute to calculate the average sort time. If the number of sort overflows is small with respect to the total sorts, increasing the sort heap size might have little impact on performance, unless this buffer size is increased substantially. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Total SQL Stmts

• The total number of dynamic and static SQL statements. This value is derived by adding the values of the Dynamic SQL Statements and the Static SQL Statements attributes. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Transaction Per Min

• The total number of database transactions that occurred per minute.
• The type is int.
• The unit is transactions/minute.

UID SQL Stmts

• The number of SQL UPDATE, INSERT, and DELETE statements that ran. Use this attribute to determine the level of database activity at the application or database level. You can also use the following formula to determine the ratio of UPDATE, INSERT, and DELETE statements to the total number of statements:
  1. Add the number of static SQL statements attempted and the dynamic SQL statements attempted.
  2. Divide the number of UPDATE/INSERT/DELETE SQL statements that ran by the sum derived in step 1.
  The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

X Lock Escals

• The number of times that locks have been escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application. The amount of lock list space available is determined by the LOCKLIST and MAXLOCKS configuration parameters. Other applications cannot access data held by an exclusive lock. Because exclusive locks can affect the concurrency of your data, it is important to track them. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, it uses space in the lock list allocated for other applications. When the entire lock list is full, an error occurs. See the Lock Escals attribute for possible causes and resolutions to excessive exclusive lock escalations. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Dimensions

The following dimensions are available for the resource.

Catalog Node Name

• The network name of the catalog node. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Database Status

• The status of the database.
• The type is string.

DB Conn Timestamp

• The date and time when the first database connection was made. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

DB Location

• The location of the database in relation to the application. Determine the relative location of the database server with respect to the application taking the snapshot. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 characters. Use this attribute to identify the specific database to which the data applies.
• The type is string.

DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:.
• The type is string.

DB Path

• The full path of the location where the database is stored on the monitored system. The value format is a simple text string with a maximum of 768 characters. Use this attribute with the Database Name attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Input DB Alias

• The alias of the database provided when calling the snapshot function. The value format is a simple text string with a maximum of 60 characters. Use this attribute to help you identify the specific database to which the monitor data applies. It contains blanks unless you requested monitor information related to a specific database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Instance Hostname

• The format is instanceid:hostname for all operating systems.
• The type is string.

Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Last Backup

• The date and time that the latest database backup was completed. Use this attribute to help you identify a database that has not been backed up recently, or to identify which database backup file is the most recent. If the database has never been backed up, this timestamp is initialized to zero. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Node Name

• The format is instanceid:hostname:UD for all operating systems.
• The type is string.

Server Platform

• The operating system upon which the database management system is running. Use this attribute during troubleshooting for remote applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Component: application

Information about application activities. The following section lists the metrics and dimensions of Component application.

Metrics

The following metrics are available for the component.

Application01 Agent Process Agent User CPU Time

• The total CPU time (in seconds) that the database manager agent process spent in system calls. This counter includes time spent on both SQL and non-SQL statements, and any unfenced user-defined functions (UDFs) or stored procedures issued by the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is seconds.

Application01 Agent Sys CPU Time

• The total system CPU time (in seconds) that the database manager agent process spent executing database manager code. This element includes CPU time for both SQL and non-SQL statements, and CPU time for any unfenced user-defined functions (UDFs). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is seconds.

Application01 Agents Stolen

• The number of times that agents are stolen from an application. When another application requires a new subagent and has no subagents in its associated agent pool, it steals subagents from the agent pools of other applications. If the number of agents stolen from this application is high compared to normal operating levels, the number of pool agents might be too low. When the agent pool size is too small, one application might fill the pool with associated subagents. When another application requires a new subagent and has no subagents in its associated agent pool, it steals subagents from the agent pools of other applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Application01 Appl Section Inserts

• The number of inserts of SQL sections by an application from its SQL work area. The working copy of any executable section is stored in a unique SQL work area. The returned value is a count of how many times a copy was not available and had to be inserted. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application01 Appl Section Lookups

• The number of lookups of SQL sections by an application from its SQL work area. This counter indicates how many times the SQL work area for an application was accessed. The total is a cumulative figure of all lookups on all SQL work heaps for agents working on this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application01 Appl Work Load

• The ratio of the maximum number of subagents associated with this application to the number of agents that are stolen from the application by DB2 to work on a different application. Use the returned value to evaluate the load that this application places on the system. An agent working for an application is associated with that application. After the agent completes the work for the application, it is placed in the agent pool as an idle agent, but it remains associated with the application. When the application requires an agent again, DB2 searches the agent pool for an agent already associated with the application and assigns work to the associated agent. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ratio.

Application01 Associated Agents Top

• The maximum number of associated agents. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Application01 Avg Sect Read per Direct Read

• The average number of sectors that are read by a direct read for the database. The value is derived through this formula: direct reads / direct read reqs Direct reads do not use the buffer pool, and so result in poor performance because the data is physically read from disk each time. If you are using system monitors to track input and output for the device, this value helps you distinguish database input and output from non-database input and output. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sectors.

Application01 Avg Sect Written per Direct Write

• The average number of sectors that are written in a direct write by this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sectors.

Application01 Deadlocks for Interval

• The total number of deadlocks that occurred for the application during the monitoring interval. Use the returned value to determine if the application is experiencing contention problems. Modify the application to better enable it to run concurrently. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deadlocks.

Application01 DL SQL Percent for Interval

• The percentage of total SQL statements that are SQL DDL statements issued by the application during the monitoring interval. Due to the high activity in the system catalog tables, try to keep DDL statement activity to a minimum. If the returned value is high compared to normal operating levels, determine the activity causing it to be high and restrict it from being performed. Examples of DDL statements are CREATE TABLE, CREATE VIEW, ALTER TABLE, and DROP INDEX. You can also use the returned value to refine the package cache hit ratio for this application. DDL statements can also affect the package cache by invalidating sections that are stored there and causing additional system overhead due to section recompilation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application01 Lock Escalation for Interval

• The total number of lock escalations for the application during the monitoring interval. Exclusive lock escalations are included in this number. Use the returned value to help you evaluate the settings of the LOCKLIST and MAXLOCKS configuration parameters. Lock escalations can result in a decrease in concurrency among the applications connected to a database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Application01 Lock List in Use Percent

• The percentage of space used in the lock list by a connected application. The value format is a percentage. When an application reaches the maximum number of allowed locks and no additional locks are escalated, the application uses space in the lock list that is allocated for other applications. When an application holds too much of the lock list, other applications can experience lock escalations. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application01 Lock Wait Time for Interval

• The total elapsed time, in seconds, that the application waited for a lock to be granted during the monitoring interval. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application01 Open Curs

• The number of local and remote cursors that are currently open for this application, including the number of local and remote blocking cursors currently open for this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application01 Open Curs Blk

• The number of local and remote blocking cursors that are currently open for this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application01 Pkg Cache Hit Percent

• The application package cache hit ratio (as a percentage) for the last monitoring interval. The package cache hit ratio is the ratio of the difference between the package cache lookups and the package cache inserts to all package cache lookups. This percentage tells you whether the package cache is being used efficiently by this application. If the hit ratio is high (greater than 80%), the package cache is performing well. A smaller percentage can indicate that the package cache must be increased. However, it is not always worthwhile to increase the size of the package cache for an application that runs only once a day. The size of the package cache is set by the pckcachesz configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application01 Pool Hit Ratio Pct for Interval

• The overall buffer pool hit ratio (as a percentage) for the database during the monitoring interval. This hit ratio includes both index and data page activity. The overall buffer pool hit ratio indicates the percentage of page requests for which the database manager did not need to load a page from disk to service. (That is, the page was already in the buffer pool. ) The greater the buffer pool hit ratio, the lower the frequency of disk input and output. If the hit ratio is low compared to normal operating levels, increasing the number of buffer pool pages can improve performance. A ratio of zero indicates that pages needed to be read for every request. For a large database, increasing the buffer pool size can have a minimal effect on the buffer pool hit ratio. Such a database can have so large a number of data pages that the statistical chance of a hit is not increased by an increase of the buffer pools. However, even though the data might be too large to fit in the buffer pool, the entire index can fit. In this case, you can refine buffer pool sizes until the overall buffer pool hit ratio stops increasing, and then refine the buffer pool until the buffer pool index hit ratio no longer increases. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application01 Pool Index Hit Ratio Percent for Interval

• The application buffer pool index page hit ratio (as a percentage) during the monitoring interval. The index page hit ratio for the buffer pool indicates the percentage of index page requests for which the database manager did not need to load an index page from disk to service. That is, the index page was already in the buffer pool. The higher the returned value, the lower the frequency of disk input and output, and the faster the performance. If the hit ratio is low compared to normal operating levels, increasing the number of buffer pool pages can improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application01 Prefetch Wait Time

• The time an application spent waiting for an I/O server (prefetcher) to finish loading pages into the buffer pool. The value format is an integer. This attribute can be used to experiment with changing the number of I/O servers and the I/O server sizes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application01 SQL Reqs Since Commit

• The number of SQL requests that were submitted by the application since the last commit. Use the returned value to monitor the progress of a transaction. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application01 Stmts Sorts

• The total number of times that a set of data was sorted to process the OPEN operation of the current SQL statement. Use the returned value to help identify the need for an index, because indexes can reduce the need for sorting a set of data. Identify the SQL statement for which this returned value is providing sort information. Then, analyze this SQL statement to determine index candidates by looking at columns that are being sorted. For example, a column used in an ORDER BY clause can be an index candidate. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application01 Total Pool IO Time

• The total time (in seconds) that an application spent performing buffer pool input and output operations (reading or writing pages). The returned value is an indication of how much time the application performs input and output operations using the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application01 Total Sorts for Interval

• The total number of sorts that are issued by the application during the monitoring interval. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application01 UID SQL Percent for Interval

• The percentage of total SQL statements that are SQL UPDATE, INSERT, and DELETE statements issued by the application during the monitoring interval. Use the returned value to determine if the application performs frequent updates. If the returned value is low compared to normal operating levels, the application is query-based; otherwise, it is update-based. Knowing what type of applications you have (query-based or update-based) can aid you in refining the database configuration parameters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application01 UOW Log Space Used

• The log space used in the most recent UOW (unit of work). Values that are greater than or equal to 9223372036854775807 are indicated with the text Value Exceeds Maximum in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Dimensions

The following dimensions are available for the component.

Application01 Appl ID

• The application ID. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 Appl Name

• The name of the application running at the client as it is known to the database manager or DB2 Connect. The value format is a text string, with a maximum of 60 characters. For example: *Local. db2inst1. 990212202018 . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 characters. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 Prev UOW Stop Timestamp

• The date and time that the unit of work completed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application01 Section Number

• The internal section number in the package for the SQL statement currently processing or most recently processed. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application01 Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Application01 Stmt Start Timestamp

• The date and time that the most recent SQL statement operation started. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application01 Stmt Stop Timestamp

• The date and time that the most recent SQL statement operation stopped. If the statement is still running, this field is 0 (zero). Use this attribute with the Statement Start attribute to calculate the elapsed execution time for the statement operation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application01 UOW Comp Status

• The completion status of the previous UOW (unit of work). The value format is a text string with a maximum of 32 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application01 UOW Start Timestamp

• The date and time that the unit of work first required database resources. This resource requirement occurs at the first SQL statement execution for the unit of work. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application01 UOW Stop Timestamp

• The date and time that the most recent unit of work completed, which occurs when database changes are committed or rolled back. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Component: applicationActivities

Information about application activities. The following section lists the metrics and dimensions of Component applicationActivities.

Metrics

The following metrics are available for the component.

Application Acc Curs Blk

• The number of times that a request for an I/O block was accepted. The value format is an integer. Use this attribute with the Rejected Block Cursor Requests attribute to calculate the percentage of blocking requests that are accepted or rejected. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is accepteds.

Application Appl Idle Time

• The number of seconds since an application issued a request to the server. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application application Static SQL Stmts

• The number of static SQL statements that were attempted. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Avg Lock Wait Time

• The average elapsed time (in milliseconds) that was spent waiting for a lock. The value format is an integer. If the average lock wait time is high, you must look for applications that hold many locks, or have lock escalations, with a focus on tuning your applications to improve concurrency, if appropriate. If escalations are the reason for a high average lock wait time, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Avg Pool Read Time

• The average elapsed time for a read request. The value format is an integer.
• The type is int.
• The unit is milliseconds.

Application Avg Pool Write Time

• The average elapsed time for a write request. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Avg Sort Time

• The average time that was elapsed to complete a sort operation. At the database or application level, the value for this attribute can indicate the performance issues with sorting. This attribute value is affected by the system load. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is value.

Application Binds Precompiles

• The number of binds and precompiles attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is operations.

Application Cat Cache Heap Full

• The number of times that an insert into the catalog cache failed because of a heap full condition in the database heap. The value format is an integer. The catalog cache draws its storage dynamically from the database heap. Even if the cache storage has not reached its limit, inserts into the catalog cache might fail due to a lack of space in the database heap. If the catalog cache heap full count is not zero, you can correct the insert failure condition by increasing the database heap size or by reducing the catalog cache size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is failures.

Application Cat Cache Hit Ratio

• The percentage of catalog sections that are found in the cache. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Cat Cache Inserts

• The number of times that the system tried to insert table descriptor information into the catalog cache. The value format is an integer. Table descriptor information is inserted into the cache following a failed lookup to the catalog cache while processing a table, view, or alias reference in an SQL statement. The catalog cache inserts value includes attempts to insert table descriptor information that fail due to catalog cache overflow and heap full conditions. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Cat Cache Lookups

• The number of times that the catalog cache was referenced to obtain table descriptor information. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Cat Cache Overflows

• The number of times that an insert into the catalog cache failed because the catalog cache was full. The value format is an integer. If the catalog cache overflows value is large, the catalog cache might be too small for the workload. Increasing the size of the catalog cache might improve its performance. If the workload includes transactions that compile a large number of SQL statements referencing many tables, views, and aliases in a single unit of work, compiling fewer SQL statements in a single transaction might improve the performance of the catalog cache. Or if the workload includes the binding of packages containing many SQL statements referencing many tables, views or aliases, you might want to split the packages so that they include fewer SQL statements to improve performance.
• The type is int.
• The unit is overflows.

Application Commit SQL Stmts

• The total number of SQL COMMIT statements that have been attempted. The value format is an integer. A small rate of change in this counter during the monitor period might indicate that applications are not doing frequent commits. The lack of frequent commits can lead to problems with logging and data concurrency. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application DDL SQL Stmts

• The number of SQL Data Definition Language (DDL) statements that were issued. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Deadlocks

• The total number of deadlocks that have occurred. The value format is an integer. This attribute can indicate that applications are experiencing contention problems. To resolve the problem, determine in which applications (or application processes) the deadlocks are occurring. You can then modify the application to enable it to run concurrently. Some applications, however, might not be capable of running concurrently. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deadlocks.

Application Degree Parallelism

• The degree of parallelism requested when the query was bound. The value format is an integer. Use with the Agents Top attribute to determine if the query achieved maximum level of parallelism. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is degree.

Application Direct Read Reqs

• The number of requests to perform a direct read of one or more sectors of data. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Direct Read Time

• The elapsed time (in milliseconds) required to perform the direct reads. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Direct Reads

• The number of read operations that do not use the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Application Direct Write Reqs

• The number of requests to perform a direct write of one or more sectors of data. The value format is an integer.:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Direct Write Time

• The elapsed time (in milliseconds) required to perform the direct writes. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Direct Writes

• The number of write operations that do not use the buffer pool. The value format is an integer.:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Dynamic SQL Stmts

• The number of dynamic SQL statements that were attempted. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Failed SQL Stmts

• The number of SQL statements that were attempted, but failed. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Failed SQL Stmts Percent

• The percentage of SQL statements that failed to run successfully. The value format is an integer. This value is derived by dividing the value of the Failed SQL Statements attribute by the value of the Total SQL Statements attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Group00 Acc Curs Blk

• The number of times that a request for an I/O block was accepted. Use this attribute with the Rejected Block Cursor Requests attribute to calculate the percentage of blocking requests that are accepted or rejected. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is accepteds.

Application Group00 Agent Sys CPU Time

• The total system CPU time (in seconds) that the database manager agent process spent executing database manager code. This element includes CPU time for both SQL and non-SQL statements, and CPU time for any unfenced user-defined functions (UDFs). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.
• The unit is seconds.

Application Group00 Appl Idle Time

• The number of seconds since an application issued a request to the server. This amount includes applications that have not ended a transaction (for example, have not issued a commit or rollback). Use this information to force users who have been idle for a specified number of seconds. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application Group00 Avg Lock Waittime

• The average elapsed time (in milliseconds) that was spent waiting for a lock. If the average lock wait time is high, you must look for applications that hold many locks, or have lock escalations, to focus on tuning your applications to improve concurrency. If escalations cause a high average lock wait time, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Avg Pool Read Time

• The average elapsed time for a read request. This value is derived by dividing the value of the Pool Read Time attribute by the value of the Pool Total Reads attribute. This average can indicate the presence of an I/O wait, which might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Avg Pool Write Time

• The average elapsed time for a write request. This value is derived by dividing the value of the Pool Write Time attribute by the value of the Pool Total Writes attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Avg Sort Time

• The average derived by dividing value of the Total Sort Time attribute by the value of the Total Sorts attribute. The average is expressed as elapsed time. at the database or application level, this attribute can indicate whether sorting is a performance issue. System load affects elapsed time. As you increase the running processes, this elapsed time value becomes higher. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Binds Precompiles

• The number of attempted binds and precompiles. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group00 Cat Cache Heap Full

• The number of times that a heap full condition in the database heap caused an insert into the catalog cache to fail. The catalog cache draws its storage dynamically from the database heap. Even if the cache storage has not reached its limit, inserts into the catalog cache can fail if space is lacking in the database heap. If the catalog cache heap full count is not zero, you can correct the insert failure condition by increasing the database heap size or by reducing the catalog cache size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Application Group00 Cat Cache Hit Ratio

• The percentage of catalog sections found in the cache. This attribute indicates how well the catalog cache is avoiding catalog accesses. If the value is high (more than 0. 8), the cache is performing well. A smaller value might indicate that you must increase the size of the catalog cache. You must expect a large value immediately following the first connection to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group00 Cat Cache Inserts

• The number of times that the system tried to insert table descriptor information into the catalog cache. Table descriptor information is inserted into the cache following a failed lookup to the catalog cache while processing a table, view, or alias reference in an SQL statement. The catalog cache inserts value includes attempts to insert table descriptor information that fail if the catalog cache overflows and the heap is full. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Group00 Cat Cache Lookups

• The number of times that the catalog cache was referenced to obtain table descriptor information. This attribute includes both successful and unsuccessful accesses to the catalog cache. To calculate the catalog cache hit ratio use the following formula: (1 - (cat_cache_inserts / cat_cache_lookups)) This ratio indicates how well the catalog cache is avoiding catalog accesses. If the ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that you must increase the size of the catalog cache. You must expect a large ratio immediately following the first connection to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Group00 Cat Cache Overflows

• The number of times that an insert into the catalog cache failed because the catalog cache was full. If the catalog cache overflows value is large, the catalog cache might be too small for the workload. Increasing the size of the catalog cache might improve its performance. If the workload includes transactions that compile a large number of SQL statements referencing many tables, views, and aliases in a single unit of work, compiling fewer SQL statements in a single transaction might improve the performance of the catalog cache. Or if the workload includes the binding of packages containing many SQL statements referencing many tables, views or aliases, you might want to split the packages so that they include fewer SQL statements to improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Application Group00 Commit SQL Stmts

• The total number of SQL COMMIT statements that have been attempted. A small rate of change in this counter during the monitor period might indicate that applications are not doing frequent commits. The lack of frequent commits can lead to problems with logging and data concurrency. You can also use this attribute to calculate the total number of units of work by calculating the sum of the following values:
  • Commit statements attempted
  • Internal commits
  • Rollback statements attempted
  • Internal rollbacks
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application Group00 Database Manager Agent User CPU Time

• The total CPU time (in microseconds) that the database manager agent process used. This counter includes time spent on both SQL and non-SQL statements, and any fenced user-defined functions (UDFs) or stored procedures issued by the application. System CPU represents the time spent in system calls. User CPU represents time spent executing database manager code. The value format is a text string with a maximum of 10 characters. Use this attribute with the other CPU-time related attributes to help you identify applications or queries that consume large amounts of CPU time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.
• The unit is microseconds.

Application Group00 DDL SQL Stmts

• The number of SQL Data Definition Language (DDL) statements that ran. Use this attribute to determine the level of database activity at the application or database level. DDL statements are expensive to run because of their impact on the system catalog tables. As a result, if the value of this attribute is high, you must determine the cause and possibly restrict the identified activity from being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 Deadlocks

• The total number of deadlocks that have occurred. This attribute can indicate that applications are experiencing contention problems. To resolve the problem, determine in which applications (or application processes) the deadlock are occurring. You can then modify the application to enable it to run concurrently. Some applications, however, might not be capable of running concurrently. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deadlocks.

Application Group00 Degree Parallelism

• The degree of parallelism requested when the query was bound. Use with the Agents Top attribute to determine if the query achieved maximum level of parallelism. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is degree.

Application Group00 Direct Read Reqs

• The number of requests to perform a direct read of one or more sectors of data. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Direct Read Time

• The elapsed time (in milliseconds) required to perform the direct reads. Use the following formula to calculate the average direct read time per sector: direct read time / direct reads from database A high average time might indicate an I/O conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Direct Reads

• The number of read operations that do not use the buffer pool. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests When using system monitors to track I/O, this data attribute helps to distinguish database I/O from non-database I/O on the device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Application Group00 Direct Write Reqs

• The number of requests to perform a direct write of one or more sectors of data. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Direct Write Time

• The elapsed time (in milliseconds) required to perform the direct writes. Use the following formula to calculate the average direct write time per sector: direct write time / direct writes to database A high average time might indicate an I/O conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Direct Writes

• The number of write operations that do not use the buffer pool. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests When using system monitors to track I/O, this data attribute helps to distinguish database I/O from non-database I/O on the device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Group00 Dynamic SQL Stmts

• The number of dynamic SQL statements that were attempted. Use this attribute to calculate the total number of successful SQL statements at the database or application level:
  1. Sum the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 Failed SQL Stmts

• The number of SQL statements that were attempted, but failed. This count includes all SQL statements that received a negative SQLCODE. Use this attribute to calculate the total number of successful SQL statements at the database or application level:
  1. Sum the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This attribute can also help you to determine the reasons for poor performance; failed statements indicate time wasted by the database manager, which results in lower throughput for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 Failed SQL Stmts Pct

• The percentage of SQL statements that failed to run. This value is derived by dividing the value of the Failed SQL Statements attribute by the value of the Total SQL Statements attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group00 Hash Join Overflows

• The number of times that hash join data exceeded the available sort heap space. At the database level, if the percentage of Hash Join Small Overflows is greater than 10% of this value, you must consider increasing the sort heap size. You can use values at the application level to evaluate hash join performance for individual applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group00 Hash Join Small Overflows

• The number of times that hash join data exceeded the available sort heap space by less than 10%. If this value and the value of the Hash Join Overflows attribute are high, you must consider increasing the sort heap threshold. If this value is greater than 10% of Hash Join Overflows, you must consider increasing the sort heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group00 Int Auto Rebinds

• The number of automatic rebinds (or recompiles) that have been attempted. Automatic rebinds are the internal binds the system performs when the validity of a package is removed. Use this attribute to determine the level of database activity at the application or database level. Because internal automatic rebinds can have a significant impact on performance, they must be minimized where possible. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rebinds.

Application Group00 Int Commits

• The total number of commits initiated internally by the database manager. An internal commit might occur during one of the following operations:
  • A reorganization
  • An import
  • A bind or pre-compile
  • An application that ends without executing an explicit SQL COMMIT statement (on UNIX and Linux systems).
  Use this attribute to calculate the total number of units of work by calculating the sum of the following values: commit statements attempted, internal commits, rollback statements attempted, and internal rollbacks. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application Group00 Int Deadlock rollbacks

• The total number of forced rollbacks initiated by the database manager due to a deadlock. The database manager initiates a rollback for the current unit of work in an application that is experiencing a deadlock. This attribute shows the number of deadlocks that were broken. It can indicate the possibility of concurrency problems. It is also important because internal rollbacks due to deadlocks can cause performance degradation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Group00 Int Rollbacks

• The total number of rollbacks initiated internally by the database manager. An internal rollback occurs when any of the following operations cannot be completed successfully:
  • A reorganization
  • An import
  • A bind or pre-compile
  • An application that ends as a result of a deadlock situation or lock timeout situation
  • An application that ends without executing an explicit COMMIT or ROLLBACK statement (on Windows systems).
  Use this attribute to calculate the total number of units of work by calculating the sum of the following values: commit statements attempted, internal commits, rollback statements attempted, and internal rollbacks. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Group00 Int Rows Deleted

• The number of rows deleted from the database as a result of internal activity. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints or triggers that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Int Rows Inserted

• The number of rows inserted into the database as a result of internal activity caused by triggers. This attribute can help to gain insight into the internal activity within the database manager. If this activity is high, you must evaluate the design to determine if you can alter it to reduce this activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Int Rows Updated

• The number of rows updated from the database as a result of internal activity. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Lock Escals

• The number of times that locks have been escalated from several row locks to a table lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application, or the lock list space consumed by all applications is approaching the total lock list space. This data item includes a count of all lock escalations, including exclusive lock escalations. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, the application uses space in the lock list that is allocated for other applications. When the entire lock list is full, an error occurs. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Application Group00 Lock Timeouts

• The number of times that a request to lock an object time out instead of being granted. This attribute can help you adjust the setting for the LOCKTIMEOUT database configuration parameter. If the number of lock timeouts becomes excessive when compared to normal operating levels, an application might be holding locks for long durations. In this case, this attribute might indicate that you must analyze some of the other attributes related to locks and deadlocks to determine if an application problem exists. You can have too few lock timeouts if the LOCKTIMEOUT database configuration parameter is set too high. In this case, applications might wait excessively to obtain a lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timeouts.

Application Group00 Lock Wait Time

• The total elapsed time (in milliseconds) that was spent waiting for a lock. At the database level, this is the total amount of elapsed time that all applications were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction has waited for a lock to be granted. This attribute might be used with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Lock Waits

• The total number of times that applications or connections waited for locks. At the database level, the lock waits value is the total number of times that applications waited for locks within this database. At the application-connection level, the lock waits value is the total number of times that this connection requested a lock but waited because another connection was already holding a lock on the data. Use this attribute with the Lock Wait Time attribute to calculate, at the database level, the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. If the average lock wait time is high, look for applications that hold many locks, or have lock escalations, with a focus on tuning your applications to improve concurrency, if appropriate. If escalations are the reason for a high average lock wait time, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is waits.

Application Group00 Locks Held

• The number of locks currently held. If the monitor information is at the database level, this number represents the total number of locks currently held by all applications in the database. If the information is at the application level, this number represents the total number of locks currently held by all agents for the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is locks.

Application Group00 Open Local Curs

• The number of local cursors currently open for this application, including those cursors counted by Open Local Cursors with Blocking attribute. Use this attribute with the Open Local Cursors with Blocking attribute to calculate the percentage of local cursors that are blocking cursors. If the percentage is low, you might be able to improve performance by improving the row blocking in the application. For cursors used by remote applications, see the Open Remote Cursors attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group00 Open Local Curs Blk

• The number of local blocking cursors currently open for this application. Use this attribute with the Open Local Cursors attribute to calculate the percentage of local cursors that are blocking cursors. Rejected Block Cursor Requests and Accepted Block Cursor Requests attributes provide additional information that might help you tune your configuration parameters to improve row blocking in your application. For blocking cursors used by remote applications, see the Open Remote Cursors with Blocking attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group00 Open Rem Curs

• The number of remote cursors currently open for this application, including the cursors counted by the Open Remote Cursors with Blocking attribute. Use this attribute with the Open Remote Cursors with Blocking attribute to calculate the percentage of remote cursors that are blocking cursors. If the percentage is low, you might be able to improve performance by improving the row blocking in the application. For the number of open cursors used by applications connected to a local database, see the Open Local Cursors attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group00 Open Rem Curs Blk

• The number of remote blocking cursors currently open for this application. Use this attribute with the Open Remote Cursors attribute to calculate the percentage of remote cursors that are blocking cursors. If the percentage is low, you might be able to use the following steps to improve performance by improving the row blocking in the application:
  1. Check the pre-compile options for record blocking for treatment of ambiguous cursors.
  2. Redefine cursors to allow for blocking.
  Rejected Block Cursor Requests and Accepted Block Cursor Requests attributes provide additional information that might help you tune your configuration parameters to improve row blocking in your application. For the number of open blocking cursors that are used by applications connected to a local database, see the Open Local Cursors with Blocking attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group00 Pkg Cache Hit Ratio

• The percentage of package sections that were found in the cache. This attribute tells you whether the package cache is being used effectively. If the hit ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that the package cache must be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group00 Pkg Cache Inserts

• The total number of times that a requested section was not available for use and had to be loaded into the package cache. This count includes any implicit prepares performed by the system. By using the Package Cache Lookups attribute, you can calculate the package cache hit ratio using the following formula: 1 - (Package Cache Inserts / Package Cache Lookups). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group00 Pkg Cache Lookups

• The number of times that an application looked for a section or package in the package cache. At a database level, it indicates the overall number of references since the database was started, or monitor data was reset. Note that this counter includes the cases where the section is already loaded in the cache and when the section has to be loaded into the cache. To calculate the package cache hit ratio use the following formula: 1 - (Package Cache Inserts / Package Cache Lookups) The package cache hit ratio tells you whether the package cache is being used effectively. If the hit ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that the package cache must be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Group00 Pool Data from Estore

• Number of buffer pool data pages copied from extended storage. Required pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group00 Pool Data L Reads

• The number of logical read requests for data pages that have gone through the buffer pool. This count includes accesses to the following types of data:
  • Data that is already 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
  By using the Pool Data Physical Reads attribute, you can calculate the data page hit ratio for the buffer pool as in the following formula: 1 - (buffer pool data physical reads / buffer pool data logical reads) By using the Pool Data Physical Reads, Pool Index Physical Reads, and Pool Index Logical Reads attributes, you can calculate the overall buffer pool hit ratio as in the following example: 1 - ((buffer pool data physical reads + buffer pool index physical reads) / (buffer pool data logical reads + buffer pool index logical reads)) Increasing buffer pool size generally improves the hit ratio until you reach a point of diminishing returns. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Pool Data P Reads

• The number of read requests that required I/O to get data pages into the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Pool Data to Estore

• Number of buffer pool data pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group00 Pool Data Writes

• The number of times a buffer pool data page was physically written to disk. A buffer pool data page is written to disk for the following reasons:
  • To free a page in the buffer pool so that another page can be read
  • To flush the buffer pool
  If a buffer pool data page is written to disk for a high percentage of Buffer Pool Data Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Group00 Pool Hit Ratio

• The buffer pool hit ratio (as a percentage). The sum of the Pool Data Logical Reads and Pool Index Logical Reads attributes is divided by the value of the Pool Total Reads attribute to derive the ratio. Use this attribute to determine whether buffer pool assignment is efficient. If the pool hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group00 Pool Index from Estore

• Number of buffer pool index pages copied from extended storage. Required index pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group00 Pool Index L Reads

• The number of logical read requests for index pages that have gone through the buffer pool. This count includes accesses to index pages that are already in the buffer pool when the database manager needs to process the page or read into the buffer pool before the database manager can process the page. By using the Pool Index Physical Reads attribute, you can calculate the index page hit ratio for the buffer pool using the following formula: 1 - (buffer pool index physical reads / buffer pool index logical reads) To calculate the overall buffer pool hit ratio, see the Pool Data Logical Reads attribute. If the hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Pool Index to Estore

• Number of buffer pool index pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group00 Pool Index Writes

• The number of times a buffer pool index page was physically written to disk. If a buffer pool index page is written to disk for a high percentage of the Pool Index Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. If all applications are updating the database, increasing the size of the buffer pool might have minimal impact on performance; most pages contain updated data that must be written to disk. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Group00 Pool Read Time

• The total amount of elapsed time spent processing read requests that caused data or index pages to be physically read from disk to buffer pool. Use this attribute with the Buffer Pool Data Physical Reads and Buffer Pool Index Physical Reads attributes to calculate the average page-read time. This average is important because it might indicate the presence of an I/O wait, which can indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Pool Total Reads

• The total number of read requests that required I/O to get data pages and index pages into the buffer pool. This attribute is the total of the Pool Data Physical Reads and Pool Index Physical Reads attributes. Use this attribute to determine how busy the DB2 server is in terms of I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Pool Total Writes

• The total number of write requests. This attribute is the total of the Pool Data Writes and Pool Index Writes attributes. Use this attribute to determine how busy the DB2 server is in terms of write I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group00 Pool Write Time

• The total amount of time spent physically writing data or index pages from the buffer pool to disk. Use this attribute with the Buffer Pool Data Writes and Buffer Pool Index Writes attributes to calculate the average page-write time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Prefetch Wait Time

• The time an application spent waiting for an I/O server or prefetcher to finish loading pages into the buffer pool. This attribute can be used to experiment with changing the number of I/O servers and the I/O server sizes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Query Card Estimate

• An estimate of the number of rows that are returned by a query. You can compare this estimate by the SQL compiler with the actual runtime values. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Query Cost Estimate

• Estimated cost, in timerons, for a query, as determined by the SQL compiler. This attribute allows correlation of actual runtime values with the compile-time estimates. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timerons.

Application Group00 Rej Curs Blk

• The number of times that a request for an I/O block at the server was rejected and the request was converted to non-blocked I/O. If there are many cursors blocking data, the communication heap might become full. When this heap is full, I/O blocks are not allocated for blocking cursors; however, an error condition does not alert you to this condition. If cursors are unable to block data, performance can be affected adversely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rejections.

Application Group00 Rollback SQL Stmts

• The total number of SQL ROLLBACK statements that have been attempted. A rollback can result from an application request, a deadlock, or an error situation. This attribute counts only the number of rollback statements issued from applications. At the application level, this attribute can help you determine the level of database activity for the application and the amount of conflict with other applications. At the database level, it can help you determine the amount of activity in the database and the amount of conflict between applications on the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Group00 Rows Deleted

• The number of row deletions attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Rows Inserted

• The number of row insertions attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Rows Read

• The number of rows read from the table. This attribute helps to identify tables with heavy usage for which you might want to create additional indexes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Rows Selected

• The number of rows that have been selected and returned to the application. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Rows Updated

• The number of row updates attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Rows Written

• The number of rows changed (inserted, deleted, or updated) in the table. A high value for table-level information indicates heavy usage of the table. If so, you might want to use the Run Statistics (RUNSTATS) utility to maintain efficiency of the packages used for this table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group00 Select SQL Stmts

• The number of SQL SELECT statements that ran. Use this attribute to determine the level of database activity at the application or database level. You can also use the following steps to determine the ratio of SELECT statements to the total statements:
  1. Sum the number of attempted static SQL statements and the number of attempted dynamic SQL statements.
  2. Divide the sum by the number of select SQL statements that ran.
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 Sort Overflows

• The total number of sorts that ran out of sort heap space and might have required disk space for temporary storage. at the database or application level, use this element with the Total Sorts attribute, this attribute can help to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Group00 Sort Overflows Pct

• The percentage of sorts that ran out of sort heap space and might have required disk space for temporary storage. This percentage is calculated by dividing the value of the Sort Overflows attribute by the value of the Total Sorts attribute. at the database or application level, use this attribute to evaluate the percentage of sorts that required overflow to disk. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group00 Static SQL Stmts

• The number of static SQL statements that were attempted. Use this attribute to calculate the total number of successful SQL statements at the database or application level using the following steps:
  1. Sum the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 Total Hash Joins

• The total number of hash joins that ran. At the database or application level, use this value with the Hash Join Overflows attribute and the Hash Join Small Overflows attribute to determine if a significant percentage of hash joins would benefit from modest increases in the sort heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Application Group00 Total Hash Loops

• The total number of times that a single partition of a hash join was larger than the available sort heap space. Values for this attribute indicate inefficient execution of hash joins. This might indicate that the sort heap size is too small or the sort heap threshold is too small. Use this value with the other hash join variables to tune the sort heap size (sortheap) and sort heap threshold (sheapthres) configuration parameters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group00 Total Sort Time

• The total elapsed time (in milliseconds) for all sorts that ran. at the database or application level, use this element with the Total Sorts attribute to calculate the average sort time. This average can indicate whether sorting is a performance concern. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group00 Total Sorts

• The total number of sorts that ran. at the database or application level, use this value with the Sort Overflows attribute to calculate the percentage of sorts that need more heap space. You can also use it with the Total Sort Time attribute to calculate the average sort time. If the number of sort overflows is small with respect to the total sorts, increasing the sort heap size might have little impact on performance, unless this buffer size is increased substantially. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Group00 Total SQL Stmt

• The total number of dynamic and static SQL statements. This value is derived by adding the values of the Dynamic SQL Statements and the Static SQL Statements attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 UID SQL Stmts

• The number of SQL UPDATE, INSERT, and DELETE statements that ran. Use this attribute to determine the level of database activity at the application or database level. You can also use the following steps to determine the ratio of UPDATE, INSERT, and DELETE statements to the total number of statements:
  1. Sum the number of attempted static SQL statements and the number of attempted dynamic SQL statements.
  2. Divide the number of UPDATE/INSERT/DELETE SQL statements that ran by the sum derived in step 1.
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group00 UOW Lock Wait Time

• The total amount of elapsed time this unit of work has spent waiting for locks. This attribute can help you to determine the severity of the resource contention problem. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application Group00 UOW Log Space Used

• The amount of log space (in bytes) used in the current unit of work of the monitored application. Use this attribute to understand the logging requirements at the unit-of-work level. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Application Group00 X Lock Escals

• The number of times that locks have been escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application. The amount of lock list space available is determined by the LOCKLIST and MAXLOCKS configuration parameters. Other applications cannot access data held by an exclusive lock. Because exclusive locks can affect the concurrency of your data, it is important to track them. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, it uses space in the lock list allocated for other applications. When the entire lock list is full, an error occurs. Use this attribute with the Previous UOW Stop Time attribute to calculate the total elapsed time between COMMIT/ROLLBACK points, and with the UOW Start Time attribute to calculate the elapsed time of the latest unit of work. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Application Hash Join Overflows

• The number of times that hash join data exceeded the available sort heap space. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Hash Join Small Overflows

• The number of times that hash join data exceeded the available sort heap space by less than 10%. The value format is an integer. If this value and the value of the Hash Join Overflows attribute are high, you must consider increasing the sort heap threshold. If this value is greater than 10% of Hash Join Overflows, you must consider increasing the sort heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Int Auto Rebinds

• The number of automatic rebinds (or recompiles) that have been attempted. The value format is an integer. Automatic rebinds are the internal binds the system performs when a package has been invalidated. Use this attribute to determine the level of database activity at the application or database level. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rebinds.

Application Int Deadlock Rollbacks

• The total number of forced rollbacks initiated by the database manager due to a deadlock. The value format is an integer. The database manager initiates a rollback for the current unit of work in an application that is experiencing a deadlock. This attribute shows the number of deadlocks that have been broken. It can indicate the possibility of concurrency problems. It is also important because internal rollbacks due to deadlocks can cause performance degradation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Int Rollbacks

• The total number of rollbacks initiated internally by the database manager. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Int Rows Deleted

• The number of rows deleted from the database as a result of internal activity. The value format is an integer. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints or triggers that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Int Rows Inserted

• The number of rows inserted into the database as a result of internal activity caused by triggers. The value format is an integer. This attribute can help to gain insight into the internal activity within the database manager. If this activity is high, you must evaluate the design to determine if you can alter it to reduce this activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Int Rows Updated

• The number of rows updated from the database as a result of internal activity. The value format is an integer. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Internal Commits

• The total number of commits initiated internally by the database manager. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application Lock Escals

• The number of times that locks have been escalated from several row locks to a table lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application, or the lock list space consumed by all applications is approaching the total lock list space. This data item includes a count of all lock escalations, including exclusive lock escalations. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, the application uses space in the lock list that is allocated for other applications. When the entire lock list is full, an error occurs. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Lock Timeouts

• The number of times that a request to lock an object time out instead of being granted. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timeouts.

Application Lock Wait Time

• The total elapsed time (in milliseconds) that was spent waiting for a lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Lock Waits

• The total number of times the database applications waited for locks. The value format is an integer. At the database level, the lock waits value is the total number of times that applications waited for locks within this database. At the application-connection level, the lock waits value is the total number of times that this connection requested a lock but waited because another connection was already holding a lock on the data.
• The type is int.
• The unit is occurences.

Application Locks Held

• The number of locks that are currently held. The value format is an integer.
• The type is int.
• The unit is locks.

Application Open Local Curs

• The number of local cursors currently open for this application, including those cursors counted by Open Local Cursors with Blocking attribute. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Open Local Curs Blk

• The number of local blocking cursors currently open for this application. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Open Rem Curs

• The number of remote cursors currently open for this application, including the cursors counted by the Open Remote Cursors with Blocking attribute. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Open Rem Curs Blk

• The number of remote blocking cursors currently open for this application. The value format is an integer. Use this attribute with the Open Remote Cursors attribute to calculate the percentage of remote cursors that are blocking cursors. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Pkg Cache Hit Ratio

• The percentage of package sections that were found in the cache. The value format is an integer.
• The type is double.
• The unit is percent.

Application Pkg Cache Inserts

• The total number of times that a requested section was not available for use and had to be loaded into the package cache. The value format is an integer. This count includes any implicit prepares performed by the system. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Pkg Cache Lookups

• The number of times that an application looked for a section or package in the package cache. The value format is an integer. At a database level, it indicates the overall number of references since the database was started, or monitor data was reset. Note that this counter includes the cases where the section is already loaded in the cache and when the section has to be loaded into the cache. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Pool Data from Estore

• Number of buffer pool data pages copied from extended storage. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Data L Reads

• The number of logical read requests for data pages that have gone through the buffer pool. The value format is an integer. This count includes accesses to data that is already in the buffer pool when the database manager needs to process the page or read into the buffer pool before the database manager can process the page. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Data P Reads

• The number of read requests that required I/O to get data pages into the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Data to Estore

• Number of buffer pool data pages copied to extended storage. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Data Writes

• The number of times a buffer pool data page was physically written to disk. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Pool Hit Ratio

• The buffer pool hit ratio (as a percentage). The value format is an integer. The sum of the Pool Data Logical Reads and Pool Index Logical Reads attributes is divided by the value of the Pool Total Reads attribute to derive the percentage. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Pool Index from Estore

• Number of buffer pool index pages copied from extended storage. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Index L Reads

• The number of logical read requests for index pages that have gone through the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Index to Estore

• Number of buffer pool index pages copied to extended storage. The value format is an integer. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Index Writes

• The number of times a buffer pool index page was physically written to disk. The value format is an integer. If a buffer pool index page is written to disk for a high percentage of the Pool Index Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. If all applications are updating the database, increasing the size of the buffer pool might have minimal impact on performance; most pages contain updated data that must be written to disk. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Pool Read Time

• The total amount of elapsed time spent processing read requests that caused data or index pages to be physically read from disk to buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Pool Total Reads

• The total number of read requests that required I/O to get data pages and index pages into the buffer pool. The value format is an integer. This attribute is the total of the Pool Data Physical Reads and Pool Index Physical Reads attributes. Use this attribute to determine how busy the DB2 server is in terms of I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text.
• The type is int.
• The unit is requests.

Application Pool Total Writes

• The total number of write requests. The value format is an integer. This attribute is the total of the Pool Data Writes and Pool Index Writes attributes. Use this attribute to determine how busy the DB2 server is in terms of write I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text.
• The type is int.
• The unit is requests.

Application Pool Write Time

• The total amount of time spent physically writing data or index pages from the buffer pool to disk. The value format is an integer. Use this attribute with the Buffer Pool Data Writes and Buffer Pool Index Writes attributes to calculate the average page-write time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Query Card Estimate

• An estimate of the number of rows that are returned by a query. The value format is an integer. You can compare this estimate by the SQL compiler with the actual runtime values. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Query Cost Estimate

• Estimated cost, in timerons, for a query, as determined by the SQL compiler. The value format is an integer. This attribute allows correlation of actual runtime values with the compile-time estimates. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timerons.

Application Rej Curs Blk

• The number of times that a request for an I/O block at the server was rejected and the request was converted to non-blocked I/O. If there are many cursors blocking data, the communication heap might become full. The value format is an integer. When this heap is full, I/O blocks are not allocated for blocking cursors; however, an error condition does not alert you to this condition. If cursors are unable to block data, performance can be affected adversely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Rollback SQL Stmts

• The total number of SQL ROLLBACK statements that have been attempted. The value format is an integer. A rollback can result from an application request, a deadlock, or an error situation. This attribute counts only the number of rollback statements issued from applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Rows Deleted

• The number of row deletions attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deletes.

Application Rows Inserted

• The number of row insertions attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Rows Read

• The number of rows read from the table. The value format is an integer. This attribute helps to identify tables with heavy usage for which you might want to create additional indexes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Application Rows Selected

• The number of rows that have been selected and returned to the application. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is selects.

Application Rows Updated

• The number of row updates attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is updates.

Application Rows Written

• The number of rows changed (inserted, deleted, or updated) in the table. The value format is an integer. A high value for table-level information indicates heavy usage of the table. If so, you might want to use the Run Statistics (RUNSTATS) utility to maintain efficiency of the packages used for this table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is changes.

Application Select SQL Stmts

• The number of SQL SELECT statements that were issued. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is selects.

Application Sort Overflows

• The total number of sorts that ran out of sort heap space and might have required disk space for temporary storage. The value format is an integer. at the database or application level, use this element with the Total Sorts attribute. This attribute can help to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Sort Overflows Percent

• The percentage of sorts that ran out of sort heap space and might have required disk space for temporary storage. The value format is an integer. This percentage is calculated by dividing the value of the Sort Overflows attribute by the value of the Total Sorts attribute. at the database or application level, use this attribute to evaluate the percentage of sorts that required overflow to disk. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Total Hash Joins

• The total number of hash joins that ran. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Application Total Hash Loops

• The total number of times that a single partition of a hash join was larger than the available sort heap space. The value format is an integer. Values for this attribute indicate inefficient execution of hash joins. This might indicate that the sort heap size is too small or the sort heap threshold is too small. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Total Sort Time

• The total elapsed time (in milliseconds) for all sorts that ran. The value format is an integer. at the database or application level, use this element with the Total Sorts attribute to calculate the average sort time. This average can indicate whether sorting is a performance concern. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Total Sorts

• The total number of sorts that have been issued. The value format is an integer. at the database or application level, use this value with the Sort Overflows attribute to calculate the percentage of sorts that need more heap space. You can also use it with the Total Sort Time attribute to calculate the average sort time. If the number of sort overflows is small with respect to the total sorts, increasing the sort heap size might have little impact on performance, unless this buffer size is increased substantially. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Total SQL Stmt

• The total number of dynamic and static SQL statements. This value is derived by adding the values of the Dynamic SQL Statements and the Static SQL Statements attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application UID SQL Stmts

• The number of SQL UPDATE, INSERT, and DELETE statements that were issued. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application UOW Lock Wait Time

• The time the UOW (unit of work) waited on locks (in seconds). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application X Lock Escals

• The number of times that locks have been escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. The value format is an integer. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application. The amount of lock list space available is determined by the LOCKLIST and MAXLOCKS configuration parameters. Other applications cannot access data held by an exclusive lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Lock Conflict00 Lock Wait Time

• The total elapsed time (in milliseconds) that a lock was waited for. At the database level, this is the total amount of elapsed time that all applications were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction has waited for a lock to be granted. This attribute might be used with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Lock Conflict00 Lock Wait Time (Superseded)

• The total elapsed time (in milliseconds) that a lock was waited for. At the database level, this is the total amount of elapsed time that all applications were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction has waited for a lock to be granted. This attribute might be used with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is milliseconds.

Lock Conflict00 Locks Held

• The number of locks currently held. If the monitor information is at the database level, this is the total number of locks currently held by all applications in the database. If it is at the application level, this is the total number of locks currently held by all agents for the application. Usage of this attribute depends on the level of information being returned from the database system monitor. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is locks.

Lock Conflict00 Locks Held (Superseded)

• The number of locks currently held. If the monitor information is at the database level, this is the total number of locks currently held by all applications in the database. If it is at the application level, this is the total number of locks currently held by all agents for the application. Usage of this attribute depends on the level of information being returned from the database system monitor. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is locks.

Dimensions

The following dimensions are available for the component.

Application Agent ID

• The application handle, which is a system-wide unique ID for the application. The value format is an integer. On multi-node systems, where a database is partitioned, this ID is the same on every node where the application might make a secondary connection. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Agent ID Holding Lock

• The application handle of the agent holding a lock for which this application is waiting. The value format is an integer. The lock monitor group must be turned on to obtain this information. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Appl Conn Timestamp

• The date and time that an application started a connection request. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application Appl ID

• The identifier generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database. The value format is a text string, with a maximum of 32 characters.
• The type is string.

Application Appl ID Holding Lock

• The application ID of the application that is holding a lock on the object that this application is waiting to obtain (Unicode). The value format is a text string with a maximum of 96 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Appl Name

• The name of the application that is connected to the database. The value format is a text string, with a maximum of 60 bytes. For example: *Local. db2inst1. 990212202018 .
• The type is string.

Application Appl Status

• The status of the application being monitored. This attribute can help you diagnose potential application problems. The value format is a text string with a maximum of 64 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Auth ID

• The authorization ID of the user who invoked the application that is being monitored. On a DB2 Connect gateway node, this ID is the user authorization ID on the host. The value format is a text string with a maximum of 60 bytes. Use this attribute to determine who invoked the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Client PID

• The process ID of the client application that made the connection to the database. The value format is an integer. Use this attribute to correlate monitor information such as CPU and I/O time to your client application. If a DRDA AS connection is used, this element is set to 0. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Client Platform

• The operating system on which the client application is running. Use this attribute to analyze problems for remote applications. The value format is a text string with a maximum of 20 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Client Prdid

• The product and version identifier for the software on the client. The value format is a text string with a maximum of 20 characters. For example: SQL06010 . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Client Protocol

• The communication protocol that the client application is using to communicate with the server. The value format is a text string with a maximum of 12 characters. Use this attribute for troubleshooting of remote applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Conn Complete Timestamp

• The date and time that a connection request was granted. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application Corr Token

• The DRDA AS correlation token. The value format is a text string with a maximum of 96 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Country Code

• The country code of the client application. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Creator

• The authorization ID of the user that precompiled the application (Unicode). The value format is a text string with a maximum of 60 bytes. Use this attribute to help identify the SQL statement that is processing, with the CREATOR column of the package section information in the catalogs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Cursor Name

• The name of the cursor corresponding to this SQL statement. The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies.
• The type is string.

Application DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range.
• The type is string.

Application Execution ID

• The ID that the user specified when logging in to the operating system. This ID is distinct from the Authorization ID, which the user specifies when connecting to the database. The value format is a text string with a maximum of 60 bytes. Use this attribute to determine the operating system user ID of the individual running the monitored application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Agent ID

• The application handle, which is a system-wide unique ID for the application. On multi-node systems, where a database is partitioned, this ID is the same on every node where the application might make a secondary connection. Use the application handle to identify an active application (application handle is synonymous with agent ID) uniquely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group00 Agent ID Holding Lock

• The application handle of the agent holding a lock for which this application is waiting. The lock monitor group must be turned on to obtain this information. This attribute can help you to determine which applications are in contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group00 Appl Conn Time

• The string date and time that an application started a connection request. The value format is CYYMMDDHHMMSSmmm. Use this attribute to determine when the application started its connection request to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Appl ID

• The identifier generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database. The identifier is unique across the network. The application ID is displayed in various formats that depend on the communication protocol between the client and the server system on which the database manager or DDCS is running. Each of the formats consists of three parts that are separated by periods. Use this ID (known on both the client and server) to correlate the client and server parts of the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Appl ID Holding Lock

• The application ID of the application that is holding a lock on the object that this application is waiting to obtain. The value format is a text string with a maximum of 32 characters. This attribute can help you determine which applications are in contention for resources. You can use it to identify the application handle (agent ID) and table ID that are holding the lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Appl Name

• The name of the application running at the client as it is known to the database manager or DB2 Connect. The value format is a text string, with a maximum of 20 characters. For example: *Local. db2inst1. 990212202018 . Use this attribute with the Application ID attribute to relate data items with your application. In a client/server environment, this name is passed from the client to the server to establish the database connection. For DRDA-AS connections, this name is the DRDA external name. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Appl Status

• The status of the monitored application. This attribute can help you diagnose potential application problems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Auth ID

• The authorization ID of the user who invoked the monitored application. On a DB2 Connect gateway node, this ID is the user authorization ID on the host. The value format is a text string with a maximum of 20 characters. Use this attribute to determine who invoked the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Client PID

• The process ID of the client application that made the connection to the database. Use this attribute to correlate monitor information such as CPU and I/O time to your client application. If a DRDA AS connection is used, this element is set to 0. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group00 Client Platform

• The operating system on which the client application is running. Use this attribute to analyze problems for remote applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Client Prdid

• The product and version identifier for the software on the client. The value format is a text string with a maximum of 20 characters, for example: SQL06010. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Client Protocol

• The communication protocol that the client application is using to communicate with the server. Use this attribute for troubleshooting of remote applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Conn Complete Time

• The string date and time that a connection request was granted. The value format is CYYMMDDHHMMSSmmm. Use this attribute to determine when a connection request to the database was granted. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Corr Token

• The DRDA AS correlation token. The value format is a text string with a maximum of 32 characters. Use the DRDA correlation token to correlate the processing between the application server and the application requester. It is an identifier dumped into logs when errors arise. As a result, you can use it to identify the conversation that is in error. In some cases, it is the LUWID of the conversation. If communications are not using DRDA, this element returns the appl_id attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Country Code

• The country code of the client application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group00 Creator

• The authorization ID of the user that pre-compiled the application. The value format is a text string with a maximum of 20 characters. Use this attribute to help identify the SQL statement that is processing, with the CREATOR column of the package section information in the catalogs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Cursor Name

• The name of the cursor corresponding to this SQL statement. The value format is a text string with a maximum of 20 characters. Use this attribute to identify the SQL statement that is processing. This name is used on an OPEN, FETCH, CLOSE, and PREPARE of an SQL SELECT statement. If a cursor is not used, this field is blank. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 20 characters. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Execution ID

• The ID that the user specified when logging in to the operating system. This ID is distinct from the Authorization ID, which the user specifies when connecting to the database. The value format is a text string with a maximum of 20 characters. Use this attribute to determine the operating system user ID of the individual running the monitored application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Instance Name

• The name of the monitored Db2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Lock Mode

• The type of lock being held. Use the lock mode to determine the source of contention for resources. This attribute indicates one of the following lock types, depending on the type of monitoring information that is being examined:
  • The type of lock another application holds on the object that this application is waiting to lock (for application-monitoring and deadlock-monitoring levels)
  • The type of lock held on the object by this application (for object-lock levels)
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Lock Object Type

• The type of object against which the application holds a lock (for object-lock-level information), or the type of object for which the application is waiting to obtain a lock (for application-level and deadlock-level information). Use this attribute to help you determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Lock Wait Start Time

• The string date and time that the application started waiting to obtain a lock on the object that is currently locked by another application. The value format is CYYMMDDHHMMSSmmm. This attribute can help you to determine the severity of resource contention. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Package Name

• The name of the package that contains the SQL statement currently executing. The value format is a text string with a maximum of 20 characters. Use this attribute to help you identify the application program and the SQL statement that is executing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Prev UOW Stop Time

• The string date and time that the unit of work completed. The value format is CYYMMDDHHMMSSmmm. Use this attribute with the UOW Stop Time attribute to calculate the total elapsed time between COMMIT/ROLLBACK points, and with the UOW Start Time attribute to calculate the time spent in the application between units of work. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Row Number

• Row Number. This is available for thresholds, but not in the UI.
• The type is int.

Application Group00 Section Number

• The internal section number in the package for the SQL statement currently processing or most recently processed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group00 Snapshot Time

• The string date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. The timestamp value is formatted as a date and time string. The internal timestamp value that is stored in the database is in the format cYYMMDDhhmmss000. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Stmt Operation

• The statement operation currently being processed or most recently processed (if none is currently running). Use this attribute to determine the operation that is executing or recently finished. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Stmt Start

• The string date and time that the most recent SQL statement operation started. The value format is CYYMMDDHHMMSSmmm. Use this attribute with the Statement Stop attribute to calculate the elapsed execution time for the statement operation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Stmt Stop

• The string date and time that the most recent SQL statement operation stopped. If the statement is still running, this field is 0 (zero). Use this attribute with the Statement Start attribute to calculate the elapsed execution time for the statement operation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Stmt Text

• The text of the dynamic SQL statement. For application snapshots, the statement text helps you identify what the application was executing when the snapshot was taken, or most recently processed if no statement was being processed at the time the snapshot was taken. For dynamic SQL statements, this attribute identifies the SQL text associated with a package. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Stmt Type

• The type of SQL statement processed. Use this attribute to determine the type of statement that is executing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Table Name

• The name of the table the application is waiting to lock. The value format is a text string with a maximum of 20 characters. Use this attribute with the Table Schema attribute to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Table Schema

• The schema of the table the application is waiting to lock. The value format is a text string with a maximum of 20 characters. Along with the Table Name attribute, this attribute can help to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 Tablespace Name

• the name of the tablespace that the application is waiting to lock. The value format is a text string with a maximum of 20 characters. This attribute can help you to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 UOW Comp Status

• The completion status of the previous UOW (unit of work). Use this attribute to determine if the unit of work ended due to a deadlock or an abnormal termination. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 UOW Start Time

• The string date and time that the unit of work first required database resources. This resource requirement occurs at the first SQL statement execution for the unit of work. The value format is CYYMMDDHHMMsss. Use this attribute with the UOW Stop Time attribute to calculate the total elapsed time of the unit of work and with the Previous Unit of Work Completion Timestamp attribute to calculate the time spent in the application between units of work. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group00 UOW Stop Time

• The string date and time that the most recent unit of work completed, which occurs when database changes are committed or rolled back. The value format is CYYMMDDHHMMsss. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Application Lock Mode

• The type of lock being held. Use the lock mode to determine the source of contention for resources. The value format is a text string with a maximum of 32 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Lock Object Type

• The type of object against which the application holds a lock (for object-lock-level information), or the type of object for which the application is waiting to obtain a lock (for application-level and deadlock-level information). The value format is a text string with a maximum of 16 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Lock Wait Start Time

• The date and time that the application started waiting to obtain a lock on the object that is currently locked by another application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application Node Name

• The format is instanceid:hostname:UD for all operating systems.
• The type is string.

Application Package Name

• The name of the package that contains the SQL statement currently executing. The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Application Stmt Operation

• The statement operation currently being processed or most recently processed (if none is currently running). The value format is a text string with a maximum of 20 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Stmt Text

• The text of the dynamic SQL statement. For application snapshots, the statement text helps you identify what the application was executing when the snapshot was taken, or most recently processed if no statement was being processed at the time the snapshot was taken. For dynamic SQL statements, this attribute identifies the SQL text associated with a package. The value format is a text string with a maximum of 2000 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Stmt Type

• The type of SQL statement processed. The value format is a text string with a maximum of 32 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Table Name

• The name of the table the application is waiting to lock. The value format is a text string with a maximum of 60 bytes. Use this attribute with the Table Schema attribute to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Table Schema

• The schema of the table the application is waiting to lock. The value format is a text string with a maximum of 60 bytes. Along with the Table Name attribute, this attribute can help to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Tablespace Name

• The name of the tablespace that the application is waiting to lock. The value format is a text string with a maximum of 60 bytes. This attribute can help you to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Agent ID

• The application handle, which is a system-wide unique ID for the application. On multi-node systems, where a database is partitioned, this ID is the same on every node where the application might make a secondary connection. Use the application handle to identify an active application (application handle is synonymous with agent ID) uniquely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Lock Conflict00 Agent ID Holding Lock

• The application handle of the agent holding a lock for which this application is waiting. The lock monitor group must be turned on to obtain this information. This attribute can help you to determine which applications are in contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Lock Conflict00 Appl ID

• The identifier generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database. The identifier is unique across the network. The application ID is displayed in various formats, which depend on the communication protocol between the client and the server system on which the database manager or DDCS are running. Each of the formats consists of three parts separated by periods. Use this ID (known on both the client and server) to correlate the client and server parts of the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Appl ID (Unicode)

• The identifier generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database (Unicode). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Appl ID Holding Lock

• The application ID of the application that is holding a lock on the object that this application is waiting to obtain. The value format is a text string with a maximum of 32 characters. Use this attribute to determine which applications are in contention for resources. Specifically, it can help you to identify the application handle (agent ID) and table ID that are holding the lock. For example: Local. db2inst1. 990212202018. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Appl ID Holding Lock (Unicode)

• The application ID of the application that is holding a lock on the object that this application is waiting to obtain (Unicode). The value format is a text string with a maximum of 96 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Appl Name

• The name of the application running at the client as it is known to the database manager or DB2 Connect. The value format is a text string, with a maximum of 20 characters. For example: *Local. db2inst1. 990212202018 . Use this attribute with the Application ID attribute to relate data items with your application. In a client/server environment, this name is passed from the client to the server to establish the database connection. For DRDA-AS connections, this name is the DRDA external name. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Appl Name (Unicode)

• The name of the application running at the client as it is known to the database manager or DB2 Connect (Unicode). The value format is a text string, with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Appl Status

• The status of the application being monitored. The only valid status in LOCK WAITING. The following values are valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Auth ID

• The authorization ID of the user who invoked the application that is being monitored. On a DB2 Connect gateway node, this ID is the user authorization ID on the host. The value format is a text string with a maximum of 20 characters. Use this attribute to determine who invoked the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Auth ID (Unicode)

• The authorization ID of the user who invoked the application that is being monitored (Unicode). On a DB2 Connect gateway node, this is the user authorization ID on the host. The value format is a text string with a maximum of 20 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Client DB Alias

• The alias defined within the database manager where the database connection request originated. The value format is a text string with a maximum of 20 characters. Use to identify the actual database that the application is accessing. The mapping between this name and Database Name can be done by using the database directories at the client node and the database manager server node. Because different database aliases can have different authentication types, this attribute can also help you determine the authentication type. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Client DB Alias (Unicode)

• The alias defined within the database manager where the database connection request originated (Unicode). The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Codepage ID

• The codepage or CCSID at the node where the application started. For snapshot monitor data, this is the code page at the node where the monitored application started. Use this attribute to analyze problems for remote applications. By using this information, you can ensure that data conversion is supported between the application code page and the database code page (or for DRDA host databases, the host CCSID). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Lock Conflict00 DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Lock Escalation

• An indicator of whether a lock request was made as part of a lock escalation.
  • No
  • Yes
  Use this attribute to better understand the cause of deadlocks. If deadlocks occur that involve applications doing lock escalation, you might want to increase the amount of lock memory or change the percentage of locks that any one application can request. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Lock Mode

• The type of lock being held. Use the lock mode to determine the source of contention for resources. This attribute indicates one of the following, depending on the type of monitor information being examined:
  • The type of lock another application holds on the object that this application is waiting to lock (for application-monitoring and deadlock-monitoring levels)
  • The type of lock held on the object by this application (for object-lock levels).
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Lock Object Type

• The type of object against which the application holds a lock (for object-lock-level information), or the type of object for which the application is waiting to obtain a lock (for application-level and deadlock-level information). Use this attribute to help you determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Lock Wait Start Time

• The string date and time that the application started waiting to obtain a lock on the object that is currently locked by another application. The value format is CYYMMDDHHMMSSmmm. Use this attribute to help you determine the severity of resource contention. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Lock Wait Start Timestamp

• The date and time that the application started waiting to obtain a lock on the object that is currently locked by another application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Lock Conflict00 Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Row Number

• Row Number. This is available for thresholds, but not in the UI.
• The type is int.

Lock Conflict00 Snapshot Time

• The string date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. The timestamp value is formatted as a date and time string. The internal timestamp value that is stored in the database is in the format cYYMMDDhhmmss000. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Snapshot Timestamp

• The string date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. The timestamp value is formatted as a date and time string. The internal timestamp value that is stored in the database is in the format cYYMMDDhhmmss000. This is available for thresholds, but not in the UI.
• The type is timestamp.

Lock Conflict00 Status Change Time

• The string date and time the application entered its current status. The value format is CYYMMDDHHMMSSmmm. Use this attribute to determine how long an application has been in its current status. If the application status remains unchanged for a long period of time, the application might have a problem. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Status Change Timestamp

• The date and time the application entered its current status. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Lock Conflict00 Table Name

• The name of the table against which the application is holding locks. The value format is a text string with a maximum of 20 characters. Use this attribute with the Table Schema attribute to help you determine the source of resource contention. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Table Name (Unicode)

• The name of the table against which the application is holding locks (Unicode). The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Table Schema

• The schema of the table that is holding a lock. The value format is a text string with a maximum of 20 characters. Along with the Table Name attribute, use this attribute to help you determine the source of resource contention. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Table Schema (Unicode)

• The schema of the table against which the application is holding a lock (Unicode). The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Tablespace Name

• The name of the tablespace against which the application is holding a lock. The value format is a text string with a maximum of 20 characters. Use this attribute to help you determine the source of resource contention. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Lock Conflict00 Tablespace Name (Unicode)

• The name of the tablespace against which the application currently holds a lock (Unicode). The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Component: applyProgram

The Apply Program attributes provide status information about the Apply Program processes that are configured to run on a database manager server. To collect Apply Program attributes, the Apply Program must be configured successfully. The DB2 agent must be located on the control server to collect Apply Program attributes. The control server is often the same as the target database server in an Apply subscription set. The following section lists the metrics and dimensions of Component applyProgram.

Metrics

The following metrics are available for the component.

Apply Program Total Apply Sub Fail

• The number of subscriptions with the same apply ID that the Apply Program failed to replicate. This number includes only active subscriptions that failed with a status that is equal to -1. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is subscriptions.

Apply Program Total Apply Sub Fail (Superseded)

• The number of subscriptions with the same apply ID that the Apply Program failed to replicate. This number includes only active subscriptions that failed with a status that is equal to -1. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is subscriptions.

Apply Program Total Apply Sub Lag

• The total number of Apply Program subscriptions that have not completed within their scheduled replication interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is subscriptions.

Apply Program Total Apply Sub Lag (Superseded)

• The total number of Apply Program subscriptions that have not completed within their scheduled replication interval. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is subscriptions.

Dimensions

The following dimensions are available for the component.

Apply Program Apply ID

• The subscriber user ID that started the Apply Program. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Apply Qualifier

• Uniquely identifies which Apply Program processes this subscription set. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Apply Status

• Indicates the state of the Apply subscription process for every distinct apply ID in the Apply Program subscription sets. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Apply Program DB Name

• The database name on the Apply control server where the subscription set table is stored. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Snapshot Timestamp

• The date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Component: applyProgramSubscription

The Apply Subscription attributes provide information about Apply Program subscription sets that are configured to run on a database manager server. To collect Apply Program attributes successfully, the Apply Program must be configured. The DB2 agent must be located on the control server to collect Apply Program attributes. The control server is often the same as the target database server in an Apply subscription set. The following section lists the metrics and dimensions of Component applyProgramSubscription.

Metrics

The following metrics are available for the component.

Apply Program Subscription Apply Num Reqs Refresh

• Indicates the number of subscriptions the Apply Program failed to replicate because refresh copying was disabled. While attempting to perform a full refresh, the Apply Program encountered a DISABLE_REFRESH column in the register table, which was set to On . You can either turn off the DISABLE_REFRESH column or bypass the Apply Program and perform a manual refresh. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is subscriptions.

Apply Program Subscription Apply Num Reqs Refresh (Superseded)

• Indicates the number of subscriptions the Apply Program failed to replicate because refresh copying was disabled. While attempting to perform a full refresh, the Apply Program encountered a DISABLE_REFRESH column in the register table, which was set to On . You can either turn off the DISABLE_REFRESH column or bypass the Apply Program and perform a manual refresh. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is subscriptions.

Apply Program Subscription Apply Sub Lag Time

• The difference (in number of minutes) between how much time has elapsed since the last run of the Apply Program and the expected sleep interval between executions of the Apply Program for the target table. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is minutes.

Apply Program Subscription Apply Sub Lag Time (Superseded)

• The difference (in number of minutes) between how much time has elapsed since the last run of the Apply Program and the expected sleep interval between executions of the Apply Program for the target table. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is minutes.

Dimensions

The following dimensions are available for the component.

Apply Program Subscription Apply ID

• Subscriber user ID that started the Apply Program. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Subscription Apply Sub Status

• The Apply Program subscription status. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Apply Program Subscription DB Name Target

• Database name. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Subscription Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Subscription Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Subscription Snapshot Timestamp

• The date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Apply Program Subscription Target Owner

• The name of the target owner for this member. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Apply Program Subscription Target Table

• The name of the target table or view for this member. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Component: bufferPool

Information about buffer pool activities. The following section lists the metrics and dimensions of Component bufferPool.

Metrics

The following metrics are available for the component.

Buffer Pool Application Direct Read Reqs

• The number of requests to perform a direct read of one or more sectors of data. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Async Write Ratio

• The ratio of buffer pool asynchronous data writes to the total number of pool writes for the database.
• The type is int.
• The unit is ratio.

Buffer Pool Avg Data Page Read per Async Req

• The average number of pages read for each asynchronous request. This value is derived by dividing the value of the Pool Async Data Reads attribute by the value of the Pool Async Data Read Reqs attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Avg Direct Read Time

• The average elapsed time for a direct read request. This value is calculated by dividing the value of the Direct Read Time attribute by the value of the the Direct Reads attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Buffer Pool Avg Direct Write Time

• The average elapsed time for a direct write request. This value is calculated by dividing the value of the Direct Write Time attribute by the value of the Direct Writes attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is result.

Buffer Pool Avg Pool Read Time

• The average elapsed time for a read request. This value is derived by dividing the value of the Pool Read Time attribute by the value of the Pool Total Reads attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Buffer Pool Avg Pool Write Time

• The average elapsed time for a write request. This value is derived by dividing the value of the Pool Write Time attribute by the value of the Pool Total Writes attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Avg Sync Read Time

• The average elapsed time used to perform a synchronous read. This value is derived by dividing the value of the Pool Sync Read Time attribute by the value of the Pool Sync Read attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Avg Sync Write Time

• The average elapsed time used to perform a synchronous write. This value is derived by dividing the value of the Pool Sync Write Time attribute by the value of the Pool Sync Write attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Direct Read Time

• The elapsed time (in milliseconds) required to perform the direct reads. Use the following formula to calculate the average direct read time per sector: direct read time / direct reads from database A high average time might indicate an I/O conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Direct Reads

• The number of read operations that do not use the buffer pool. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests When using system monitors to track I/O, this data attribute helps to distinguish database I/O from non-database I/O on the device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Buffer Pool Direct Write Reqs

• The number of requests to perform a direct write of one or more sectors of data. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Direct Write Time

• The elapsed time (in milliseconds) required to perform the direct writes. Use the following formula to calculate the average direct write time per sector: direct write time / direct writes to database A high average time might indicate an I/O conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Direct Writes

• The number of write operations that do not use the buffer pool. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests When using system monitors to track I/O, this data attribute helps to distinguish database I/O from non-database I/O on the device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Files Closed

• The total number of database files closed. The database manager opens files for reading and writing into and out of the buffer pool. The maximum number of database files open by an application at any time is controlled by the MAXFILOP configuration parameter. If the maximum is reached, one file is closed before the new file is opened. Note that the actual number of files opened might not equal the number of files closed. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Buffer Pool Logical Read Per Min

• The number of logical read operations that are performed on the buffer pool per minute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads/minute.

Buffer Pool Pool Async Data Read Reqs

• The number of asynchronous read requests. To calculate the average number of data pages read per asynchronous request, use the following formula: buffer pool asynchronous data reads / buffer pool asynchronous read requests This average can help to determine the amount of asynchronous I/O in each interaction with the prefetcher. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Async Data Reads

• The number of pages read asynchronously into the buffer pool. Use this attribute with the Buffer Pool Data Physical Reads attribute to calculate the number of physical reads that were performed synchronously (that is, physical data page reads that were performed by database manager agents). Use the following formula: buffer pool data physical reads - buffer pool synchronous data reads By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Pool Async Data Writes

• The number of times a buffer pool data page was physically written to disk by an asynchronous page cleaner or by a prefetcher. A prefetcher might have written dirty pages to disk to make space for the pages being prefetched. Use this attribute with the Buffer Pool Data Writes attribute to calculate the number of physical write requests that were performed synchronously (that is, physical data page writes that were performed by database manager agents). Use the following formula: buffer pool data writes - buffer pool asynchronous data writes By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Pool Async Index Reads

• The number of index pages read asynchronously into the buffer pool by a prefetcher. Asynchronous reads are performed by database manager prefetchers. Use this attribute with the Buffer Pool Index Physical Reads attribute to calculate the number of physical reads that were performed synchronously (that is, physical index page reads that were performed by database manager agents). Use the following formula: buffer pool index physical reads - buffer pool asynchronous index reads By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Buffer Pool Pool Async Index Writes

• The number of times a buffer pool index page was physically written to disk by an asynchronous page cleaner or a prefetcher. A prefetcher might have written dirty pages to disk to make space for the pages being prefetched. Use this attribute with the Buffer Pool Index Writes attribute to calculate the number of physical index write requests that were performed synchronously. That is, physical index page writes that were performed by database manager agents. Use the following formula: buffer pool index writes - buffer pool asynchronous index writes By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Pool Async Read Time

• The total elapsed time spent reading by database manager prefetchers. Use this attribute to calculate the elapsed time for synchronous reading, using the following formula: total buffer pool physical read time - buffer pool synchronous read time You can also use this attribute to calculate the average asynchronous read time using the following formula: buffer pool asynchronous read time / buffer pool asynchronous data reads These calculations can be used to understand the I/O work being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Pool Async Write Time

• The total elapsed time spent writing data or index pages from the buffer pool to disk by database manager page cleaners. Calculate the elapsed time spent writing pages synchronously by subtracting the value of the Pool Async Write Time attribute from the value of the Pool Physical Write Time attribute. You can also use this attribute to calculate the average asynchronous read time:
  1. Sum the value of the Pool Async Data Writes attribute and the value of the Pool Async Index Writes attribute.
  2. Divide the value of the Pool Async Write Time attribute by the sum from step 1.
  These calculations can be used to understand the I/O work being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Pool Data from Estore

• Number of buffer pool data pages copied from extended storage. Required pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Pool Data L Reads

• The number of logical read requests for data pages that have gone through the buffer pool. This count includes accesses to the following data:
  • Data that is already 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.
  By using the Pool Data Physical Reads attribute, you can calculate the data page hit ratio for the buffer pool as follows: 1 - (buffer pool data physical reads / buffer pool data logical reads) By using the Pool Data Physical Reads, Pool Index Physical Reads, and Pool Index Logical Reads attributes, you can calculate the overall buffer pool hit ratio as follows: 1 - ((buffer pool data physical reads + buffer pool index physical reads) / (buffer pool data logical reads + buffer pool index logical reads)) Increasing buffer pool size generally improves the hit ratio until you reach a point of diminishing returns. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Buffer Pool Pool Data P Reads

• The number of read requests that required I/O to get data pages into the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Data to Estore

• Number of buffer pool data pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Pool Data Writes

• The number of times a buffer pool data page was physically written to disk. A buffer pool data page is written to disk for the following reasons:
  • To free a page in the buffer pool so another page can be read
  • To flush the buffer pool.
  If a buffer pool data page is written to disk for a high percentage of Buffer Pool Data Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Pool Hit Ratio

• The buffer pool hit ratio (as a percentage). The sum of the Pool Data Logical Reads and Pool Index Logical Reads attributes is divided by the value of the Pool Total Reads attribute to derive the pool hit ratio. This attribute can determine whether buffer pool assignment is efficient. If the pool hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Buffer Pool Pool Index from Estore

• Number of buffer pool index pages copied from extended storage. Required index pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Pool Index L Reads

• The number of logical read requests for index pages that have gone through the buffer pool. This count includes accesses to the following index pages:
  • Pages that are already in the buffer pool when the database manager needs to process the page.
  • Pages that are read into the buffer pool before the database manager can process the page.
  By using the Buffer Pool Index Physical Reads attribute, you can calculate the index page hit ratio for the buffer pool as follows: 1 - (buffer pool index physical reads / buffer pool index logical reads) If the hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool. see the Pool Index Logical Reads attribute for information about how to use this element. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Index to Estore

• Number of buffer pool index pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Pool Index Writes

• The number of times a buffer pool index page was physically written to disk. If a buffer pool index page is written to disk for a high percentage of Buffer Pool Index Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. If all applications are updating the database, increasing the size of the buffer pool might have minimal impact on performance; most pages contain updated data that must be written to disk. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Pool Read Time

• The total amount of elapsed time spent processing read requests that caused data or index pages to be physically read from buffer pool to disk. Use this attribute with the Buffer Pool Data Physical Reads and Buffer Pool Index Physical Reads attributes to calculate the average page-read time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Pool Sync Data Reads

• The number of physical data page reads that were performed by database manager agents. This value is derived by subtracting the value of the Pool Async Data Reads attribute from the Pool Data Physical Reads attribute. By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Buffer Pool Pool Sync Data Writes

• The total number of physical write requests that were performed synchronously (that is, physical data page writes that were performed by database manager agents). This value is derived by subtracting the value of the Pool Async Data Writes attribute from the value of the Pool Data Writes attribute. By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Sync Index Reads

• The number of index pages read synchronously (that is, physical index page reads that were performed by database manager agents) into the buffer pool. This value is derived by subtracting the value of the Pool Async Index Reads attribute from Pool Index Physical Reads attribute. By comparing the ratio of asynchronous to synchronous reads, you can gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Buffer Pool Pool Sync Index Writes

• The number of physical index write requests that were performed synchronously (that is, physical index page writes that were performed by database manager agents). This value is derived by subtracting the value of the Pool Async Index Writes attribute from the value of the Pool Index Writes attribute. By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Sync Read

• The total number of synchronous reads. This value is derived by adding the values of the Pool Sync Data Reads and Pool Sync Index Reads attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Buffer Pool Pool Sync Read Time

• The elapsed time used to perform all synchronous reads. This value is derived by subtracting the value of the Pool Async Read Time attribute from the value of the Pool Read Time attribute. Use this attribute to understand the I/O work being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Pool Sync Write

• The total number of synchronous index writes. The value is derived by adding the values of the Pool Sync Data Writes attribute and Pool Sync Index Writes attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Pool Sync Write Time

• The total elapsed time used to perform all synchronous writes. This value is derived by subtracting the value of the Pool Async Write Time attribute from the value of the Pool Write Time attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Pool Total Reads

• The total number of read requests that required I/O to get data pages and index pages into the buffer pool. This attribute is the total of the Pool Data Physical Reads and Pool Index Physical Reads attributes. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Buffer Pool Pool Total Writes

• The total number of write requests. This attribute is the total of the Pool Data Writes and Pool Index Writes attributes. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Buffer Pool Pool Write Time

• The total amount of time spent physically writing data or index pages from the buffer pool to disk. Use this attribute with the Buffer Pool Data Writes and Buffer Pool Index Writes attributes to calculate the average page-write time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Buffer Pool Prefetch Ratio

• The percentage of asynchronous read operations that the prefetcher performed for sequential scans.
• The type is int.
• The unit is percent.

Dimensions

The following dimensions are available for the component.

Buffer Pool BP ID

• The internal identifier for the buffer pool. This attribute is for internal use only. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Buffer Pool BP Name

• The name of the buffer pool. A new database has a default buffer pool (named IBMDEFAULTBP). The size of the default buffer pool is determined by the platform. Depending on your needs you might choose to create several buffer pools, each of a different size, for a single database. The CREATE, ALTER, and DROP BUFFERPOOL statements allow you to create, change, or remove a buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Buffer Pool DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 characters. Use this attribute to identify the specific database to which the data applies.
• The type is string.

Buffer Pool DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:.
• The type is string.

Buffer Pool DB Path

• The full path of the location where the database is stored on the monitored system. Use this attribute with the Database Name attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Buffer Pool Input DB Alias

• The alias of the database provided when calling the snapshot function. The value format is a simple text string with a maximum of 60 characters. Use this attribute to help you identify the specific database to which the monitor data applies. It contains blanks unless you requested monitor information related to a specific database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Buffer Pool Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Buffer Pool Node Name

• The format is instanceid:hostname:UD for all operating systems. The format for version 6, release 1 of theDB2 agent on Windows systems is instanceid:hostname:UD; on UNIX and Linux systems, the format is instanceid:hostname.
• The type is string.

Buffer Pool Snapshot Timestamp

• The date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Component: customSQLExecution

Information about the results of customized SQL statement executions, including five string columns, five number columns, and two date and time columns. The following section lists the dimensions of Component customSQLExecution.

Dimensions

The following dimensions are available for the component.

Custom SQL DB Alias

• The alias name of the database on which the SQL Statement associated with the SQL ID is executed, which is a key attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL DB Alias Filter Name

• The Database alias filter name that can be defined as:
  • The character ( * ), is required if you want to execute the SQL statement associated with the SQL ID on all the databases of the DB2 server excluding all HADR standby databases.
  • A database alias, this is required if you want to execute the SQL statement associated with the SQL ID on a specific database.
  If the database filter alias name contains blank spaces at the beginning and at the end, the blank spaces at the end are trimmed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Fifth Number Column Name

• The name of the fifth number type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Fifth Number Value

• The fifth number value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Custom SQL Fifth String Column Name

• The name of the fifth string type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Fifth String Value

• The fifth string value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL First Date Column Name

• The name of the first date time type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL First Date Value

• The first date time value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Custom SQL First Number Column Name

• The name of the first number type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL First Number Value

• The first number value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Custom SQL First String Column Name

• The name of the first string type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL First String Value

• The first string value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Fourth Number Column Name

• The name of the fourth number type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Fourth Number Value

• The fourth number value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Custom SQL Fourth String Column Name

• The name of the fourth string type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Fourth String Value

• The fourth string value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Node

• The managed system name of the agent. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Second Date Column Name

• The name of the second date time type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Second Date Value

• The second date time value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Custom SQL Second Number Column Name

• The name of the second number type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Second Number Value

• The second number value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Custom SQL Second String Column Name

• The name of the second string type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Second String Value

• The second string value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL SQL ID

• The SQL ID that is defined in the definition file. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status DB Alias

• The alias name of the database on which the SQL Statement associated with the SQL ID is executed, which is a key attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status Last Execution Error Code

• The native error code returned by DB2 for the last SQL execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Custom SQL Status Last Execution Error Message

• The error message returned by DB2 for the last SQL execution, which has a maximum length of 256 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status Node Name

• The managed system name of the agent. For new installations of version 7. 1, the format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status SQL ID

• The SQL ID that is defined in the definition file. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status SQL State

• The SQL STATE returned by DB2 for the last SQL execution, which has a length of 10 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Status Status Last Execution Time

• The last date and time when the SQL is executed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Custom SQL Status Time Stamp

• The local time at the agent when the data was collected. This is available for thresholds, but not in the UI.
• The type is timestamp.

Custom SQL Third Number Column Name

• The name of the third number type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Third Number Value

• The third number value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Custom SQL Third String Column Name

• The name of the third string type column in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Third String Value

• The third string value in the result of the customized SQL statement execution. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Custom SQL Time Stamp

• The local time at the agent when the data was collected. This is available for thresholds, but not in the UI.
• The type is timestamp.

Component: databaseActivities

Information about database activities. The following section lists the metrics and dimensions of Component databaseActivities.

Metrics

The following metrics are available for the component.

Activities Active Hash Joins

• The total number of hash joins that are currently running and consuming memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Activities Active OLAP Funcs

• The total number of OLAP functions that are currently running and consuming sort heap memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is functions.

Activities Async Runstats

• The total number of successful asynchronous RUNSTATS activities that are performed by real-time statistics gathering for all the applications in the database. Values reported by all the database partitions are aggregated together. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is activities.

Activities Blocks Pending Cleanup

• The total number of MDC table blocks in the database that are pending asynchronous cleanup following a roll out delete. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is tableBlocks.

Activities Cat Cache Size Top

• The largest size that is reached by the catalog cache. This attribute indicates the maximum number of bytes the catalog cache required for the workload run against the database since it is activated. If the catalog cache overflows, the value is the largest size reached by the catalog cache during the overflow. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Data Temp Pool Hit Ratio

• The data page hit ratio for buffer pools that are located in temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Activities Database Activities Log Held By Dirty Pages

• The amount of log (in bytes) corresponding to the difference between the oldest dirty page in the database and the top of the active log. When the snapshot is taken, this value is calculated based on conditions at the time of that snapshot. Use this element to evaluate the effectiveness of page cleaning for older pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Database Activities Log to Redo for Recovery

• The amount of log (in bytes) that has to be redone for crash recovery. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Database Activities Num Log Buffer Full

• The number of times that agents have to wait for log data to write to disk while copying log records into the log buffer. This value is increased per agent per incident. For example, if two agents attempt to copy log data while the buffer is full, this value is increased by two. Use this attribute to determine if the LOGBUFSZ database configuration parameter needs to be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Activities Database Activities Num Log Data Found in Buffer

• The number of times that an agent reads log data from the buffer. Reading log data from the buffer is preferable to reading from the disk because the latter is slower. Use this attribute with the num log read io attribute to determine if the LOGBUFSZ database configuration parameter needs to be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Activities Database Activities Num Log Part Page IO

• The number of I/O requests that are issued by the logger for writing partial log data to the disk. Use this attribute with the log writes, log write time, and num log write io attributes to determine if the current disk is adequate for logging. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Activities Database Activities Num Log Read IO

• The number of I/O requests that are issued by the logger for reading log data from the disk. Use this attribute with the log reads and log read time attributes to determine if the current disk is adequate for logging. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Activities Database Activities Num Log Write IO

• The number of I/O requests that are issued by the logger for writing log data to the disk. Use this attribute with the log writes and log write time attributes to determine if the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Activities database Activities Total Log Available

• The amount of active log space in the database that is not being used by uncommitted transactions (in bytes). Use this element in conjunction with the total log used attribute to determine whether you need to adjust the following configuration parameters of the monitored DB2 instance to avoid running out of log space:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Database Activities Total Log Used Pct

• The percentage of the log space that is used in the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Activities Elapsed Exec Time MS

• At the DCS statement level, this is the elapsed time (in ms) spent processing an SQL request on a host database server. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Activities Elapsed Exec Time S

• At the DCS statement level, this is the elapsed time (in seconds) spent processing an SQL request on a host database server. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Activities Log Read Time NS

• The total elapsed time (in ns) that the logger spends reading log data from the disk. Use this attribute with the log reads, num log read io, and num log data found in buffer attributes to determine the following items:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is nanoseconds.

Activities Log Read Time S

• The total elapsed time (in seconds) that the logger spends reading log data from the disk. Use this attribute with the log reads, num log read io, and num log data found in buffer attributes to determine the following items:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Activities Log Write Time NS

• The total elapsed time (in ns) that the logger spends writing log data to the disk. Use this attribute with the log writes and num log write io attributes to determine whether the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is nanoseconds.

Activities Log Write Time S

• The total elapsed time (in seconds) that the logger spends writing log data to the disk. Use this attribute with the log writes and num log write io attributes to determine whether the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Activities Min Catalog Cache Size

• The minimum size of the catalog cache that is required by your workload. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Min Pkg Cache Size

• The minimum size of the package cache that is required by your workload. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Num Indoubt Trans

• The number of outstanding indoubt transactions in the database. Indoubt transactions hold log space for uncommitted transactions, which can cause the logs to become full. When the logs are full, further transactions can not be completed. The resolution of this problem involves a manual process of heuristically resolving the indoubt transactions. This attributes provides a count of the number of currently outstanding indoubt transactions that must be heuristically resolved. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is transactions.

Activities Num Threshold Violations

• The number of threshold violations that have taken place in this database since the database was last activated. Use this attribute to determine whether thresholds are effective for this particular application or whether the threshold violations are excessive. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is violations.

Activities OLAP Func Overflows

• The number of times that OLAP function data exceeded the available sort heap space. At the database level, use this attribute in conjunction with the total olapfuncs attribute 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, consider increasing the sort heap size. At the application level, use this attribute to evaluate OLAP function performance for individual applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Activities Pkg Cache Num Overflows

• The number of times that the package cache overflowed the bounds of its allocated memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Activities Pkg Cache Size Top

• The largest size that is reached by the package cache. If the package cache overflowed, this attribute value is the largest size that is reached by the package cache during the overflow. Check the pkg cache num overflows attribute to determine if such a condition occurred. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Pool No Victim Buffer

• The number of times an agent does not have a preselected victim buffer that is available. Use this attribute to help evaluate whether you have enough page cleaners for a given buffer pool when using proactive page cleaning. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Activities Pool Temp Data L Reads

• The number of data pages that have been requested from the buffer pool (logical) for temporary tablespaces. In conjunction with the pool temp data p reads attribute, the data page hit ratio for buffer pools located in temporary tablespaces can be calculated using the following formula: 1 - (pool temp data p reads / pool temp data l reads). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool Temp Data P Reads

• The number of data pages read in from the tablespace containers (physical) for temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool Temp Hit Ratio

• The data page and index page hit ratio for buffer pools that are located in temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Activities Pool Temp Index L Reads

• The number of index pages that have been requested from the buffer pool (logical) for temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool Temp Index P Reads

• The number of index pages read in from the tablespace containers (physical) for temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool Temp XDA L Reads

• The number of pages for XML storage object (XDA) Data that is requested from the buffer pool (logical) for temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool Temp XDA P Reads

• The number of pages for XML storage object (XDA) Data that is read in from the tablespace containers (physical) for temporary tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool XDA L Reads

• The number of data pages for XML storage objects (XDAs) that are requested from the buffer pool (logical) for regular and large tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool XDA P Reads

• The number of data pages for XML storage objects (XDAs) that are read in from the tablespace containers (physical) for regular and large tablespaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Activities Pool XDA Writes

• The number of times that a buffer pool data page for an XML storage object (XDA) is physically written to disk. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Activities Post Shr Threshold Hash Joins

• The total number of hash joins that were throttled back by the sort memory throttling algorithm. A throttled hash join is a hash join that was granted less memory than requested by the sort memory manager. A hash join is throttled back when the memory allocation from the shared sort heap is close to the limit that is set by the sheapthres_shr database configuration parameter. This throttling significantly reduces the number of overflows over sheapthres_shr limit in a system that is not properly configured. The data reported in this element only reflects hash joins using memory allocated from the shared sort heap. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Activities Post Shr Threshold Sorts

• The total number of sorts that were throttled back by the sort memory throttling algorithm. A throttled sort is a sort that was granted less memory than requested by the sort memory manager. A sort is throttled back when the memory allocation for sorts is close to the limit that is set by the sheapthres_shr database configuration parameter. This throttling significantly reduces the number of overflows over sheapthres_shr limit in a system that is not properly configured. The data reported by this attribute only reflects sorts using memory allocated from the shared sort heap. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Activities Priv Workspace Num Overflows

• The number of times that the private workspaces overflowed the bounds of its allocated memory. Use this attribute with the priv workspace size top attribute to determine whether the size of the private workspace needs to be increased to avoid overflowing. Overflows of the private workspace might cause performance degradation and out of memory errors from the other heaps allocated out of agent private memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Activities Priv Workspace Section Inserts

• The number of inserts of SQL sections by applications into the private workspace. The working copy of executable sections are stored in the private workspace. This attribute indicates the number of times when a copy was not available and had to be inserted. At the database level, it is the cumulative total of all inserts for every application across all private workspaces in the database. At the application level, it is the cumulative total of all inserts for all sections in the private workspace for this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Activities Priv Workspace Section Lookups

• Indicates how many times the private workspace was accessed in order to locate a specific section for an application. At the database level, it is the cumulative total of all lookups for every application across all private workspaces in the database. At the application level, it is the cumulative total of all lookups for all sections in the private workspace for this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is accesses.

Activities Priv Workspace Size Top

• The largest size reached by the private workspace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Rows Read

• The number of rows that are read from the table. Use this attribute to identify tables with heavy usage, and for which you might want to create additional indexes. This attribute is not the number of rows that are returned to the calling application; it is the number of rows that must be read in order to return the result set. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Activities Shr Workspace Num Overflows

• The number of times that shared workspaces overflowed the bounds of their allocated memory. Use this attribute with the shr workspace size top attribute to determine whether the size of the shared workspaces need to be increased to avoid overflowing. Overflows of shared workspaces might cause performance degradation and out of memory errors from the other heaps that are allocated out of application shared memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Activities Shr Workspace Section Inserts

• The number of inserts of SQL sections by applications into shared workspaces. The working copy of executable sections are stored in shared workspaces. This attribute indicates the number of times when a copy was not available and had to be inserted. At the database level, it is the cumulative total of all inserts for every application across all shared workspaces in the database. At the application level, it is the cumulative total of all inserts for all sections in the shared workspace for this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Activities Shr Workspace Section Lookups

• Indicates how many times shared workspaces were accessed in order to locate a specific section for an application. At the database level, it is the cumulative total of all lookups for every application across all shared workspaces in the database. At the application level, it is the cumulative total of all lookups for all sections in the shared workspace for this application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Activities Shr Workspace Size Top

• The largest size reached by shared workspaces. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Sort Shrheap Top

• The high watermark (in 4KB pages) of the database-wide shared sort memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is 4kilobytePages.

Activities Stats Cache Size

• The current size of the statistics cache, which is used in a catalog partition to cache statistics information generated by real-time statistics gathering. Use this attribute to determine the size of the current statistics cache. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Activities Stats Fabricate Time

• The total time (in milliseconds) spent on statistics fabrications by real-time statistics gathering. Statistics fabrication is the statistics collection activity needed to generate statistics during query compilation. If this attribute value is collected at the database level, it represents the total time spent on real-time statistics gathering activities for all the applications running on the database. If this attribute value is collected at the statement level, it represents the time spent on the latest real-time statistics gathering activities for the statement. The times reported by all the database partitions are aggregated together. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Activities Stats Fabrications

• The total number of statistics fabrications that are performed by real-time statistics during query compilation for all the database applications. Instead of obtaining statistics by scanning data stored in a table or an index, statistics are fabricated based on metadata maintained by the index and data manager. Values reported by all the database partitions are aggregated together. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is fabrications.

Activities Sync Runstats

• The total number of synchronous RUNSTATS activities triggered by real-time statistics gathering for all the applications in the database. This value includes both successful and unsuccessful synchronous RUNSTATS commands. Values reported by all the database partitions are aggregated together. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is activities.

Activities Sync Runstats Time

• The total time spent on synchronous RUNSTATS activities triggered by real-time statistics gathering, in milliseconds. The synchronous RUNSTATS activities occur during query compilation. At the database level, this attribute value represents the total time spent on synchronous RUNSTATS activities for all the applications running on the database, triggered by real-time statistics gathering. At the statement level, this attribute value represents the time spent on the latest synchronous RUNSTATS activities for a particular statement, triggered by real-time statistics gathering. Values reported by all the database partitions are aggregated together. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Activities Total OLAP Funcs

• The total number of OLAP functions that run. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is functions.

Activities Unread Prefetch Pages

• The number of pages that the prefetcher read in but are never used. If the value is high, prefetchers are causing unnecessary I/O by reading pages into the buffer pool that will not be used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Dimensions

The following dimensions are available for the component.

Activities Appl ID Oldest Xact

• The application ID of the application that has the oldest transaction. Use this attribute to which application has the oldest active transaction. This application can be forced to free up log space. If the application take a large amount of log space, examine the application to determine if it can be modified to commit more frequently. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Activities Catalog Partition

• The number of the catalog node. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Activities Catalog Partition Name

• The network name of the catalog node. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Activities DB Name

• The real name of the host database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Activities DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Activities Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Activities Last Reset

• Indicates the most recent date and time when the monitor counters are reset for the application issuing the GET SNAPSHOT command. Use this attribute to determine the scope of information returned by the database system monitor. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Activities Node Name

• The format is instanceid:hostname:UD for all operating systems. The format for version 6, release 1 of the DB2 agent Windows systems is instanceid:hostname:UD; on UNIX and Linux systems, the format is instanceid:hostname. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Activities Num DB Storage Paths

• The number of automatic storage paths that are associated with this database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Activities Smallest Log Avail Node

• Indicates the node with the least amount (in bytes) of available log space. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Activities Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Activities Sort Shrheap Allocated

• The total amount of shared sort memory allocated in the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Component: databaseEfficiency

Information about the efficiency of the database and identify any problem areas for corrective action. All values are integers that are calculated from the first application connection, unless otherwise noted. The following section lists the metrics and dimensions of Component databaseEfficiency.

Metrics

The following metrics are available for the component.

Efficiency Appls in DB2

• The number of applications currently executing in the database. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is applications.

Efficiency Avg Appls

• The value of the average number of active applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is applications.

Efficiency Avg Lock Escal per Conn for Interval

• The average lock escalations per connection for this database during the monitoring interval. The value format is an integer. A lock is escalated when the total number of locks that an application holds reaches the maximum amount of lock list space available to the application, or the lock list space consumed by all applications is approaching the total lock list space. When an application reaches the maximum permitted number of locks and no additional locks can be escalated, the application uses space in the lock list that is allocated for other applications. When the entire lock list is full, an error occurs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Efficiency Avg Locks Held

• The average number of locks held by each currently connected application in the database. The value is derived through this formula: locks held / appls cur cons If the returned value is high compared to normal operating levels, it can indicate that one or more applications is using an excessive number of locks. Refine such applications to improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is locks.

Efficiency Avg Pages per Cleaner for Interval

• The average number of pages written per page cleaner that are invoked for the database during the monitoring interval. Use the returned value to determine how many pages are handled by the page cleaners of this database. If this value increases over time, you can define more page cleaners. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages/cleaner.

Efficiency Avg Pool Async Data Reads

• The average number of buffer pool asynchronous data reads when compared to the total number of pool reads for the database. The value is derived through this formula: pool async data reads / (pool data p reads + pool index p reads) . Use the returned value to gain insight into how well the prefetchers are working and to refine the num_ioservers configuration parameter. If the returned value is low compared to normal operating levels, there might not be enough input and output servers to prefetch data into the buffer, causing the database manager agents to spend extra time on physical reads. Increase the number of input and output servers by increasing the value of the num_ioservers configuration parameter. If too many servers are allocated, system performance is not reduced because the extra input and output servers are not used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Efficiency Avg Pool Async Data Writes

• The average number of buffer pool asynchronous data writes (data and index) when compared to the total number of pool writes for the database. The value is derived through this formula: pool async data writes / (pool data writes + pool index writes) . Use the returned value to gain insight into how well the page cleaners are working and to refine the num_iocleaners configuration parameter. If the returned value is low compared to normal operating levels, increase the number of input and output cleaners by increasing the value of the num_iocleaners parameter. If the returned value is high compared to normal operating levels, you can save system resources by decreasing the number of input and output cleaners (by decreasing the value of the num_iocleaners parameter). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Efficiency Avg Pool Writes per Read

• The ratio of total pool writes to pool reads for the database. The value is derived through this formula: (pool data writes + pool index writes) / (pool data p reads + pool index p reads) . If the returned value is greater than 1, you can improve performance by increasing the available buffer pool space. A returned value greater than 1 indicates that at least one write to disk had to occur (either to free a page in the buffer pool, or to flush the buffer pool) before a page can be read into the buffer pool. You can increase the available buffer pool space by freeing the space more often or by increasing the total space for the buffer pool. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes/reads.

Efficiency Commit Stmts per Sec

• The total number of commits initiated internally by the database per second. Use the returned value to determine rates of database activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits/second.

Efficiency Cur Cons Percent

• The percentage of applications currently connected. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Database Efficiency Appl Section Inserts

• The number of inserts of SQL sections by an application from its SQL work area. The working copy of any executable section is stored in a unique SQL work area. This value represents the number of times when a copy was not available and therefore was inserted. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Efficiency Database Efficiency Appl Section Lookups

• The number of lookups of SQL sections by an application from its SQL work area. This counter indicates how many times the SQL work area was accessed by agents for an application. It is a cumulative total of all lookups on all SQL work heaps for agents working on this application. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Efficiency Database Efficiency Avg Data Page Read per Async Req

• The average number of pages read for each asynchronous request. This value is derived by dividing the value of the Pool Async Data Reads attribute by the value of the Pool Async Data Read Reqs attribute. Use this attribute to determine whether good enough data pages were read per asynchronous request. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Efficiency Database Efficiency Avg Direct Read Time

• The average time in milliseconds that is used to perform direct reads to the database. The value is derived through this formula: direct read time / direct reads The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Avg Direct Write Time

• The average time in milliseconds for performing direct writes to the database. A high average time can indicate the existence of an input and output conflict. The value is derived through this formula: direct write time / direct write The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Avg Pool I/O Time

• The average time (in milliseconds) for performing buffer pool input and output operations (reading or writing) to the database. A high average time can indicate the existence of an input and output conflict. In this case, you might need to move data to a different device. The returned value includes the time applied to asynchronous input and output operations (which are performed by prefetchers and page cleaners). The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Avg Sect Read per Direct Read

• The average number of sectors that are read by a direct read for the database. The value is derived through this formula: direct reads / direct read reqs . Direct reads do not use the buffer pool, and so result in poor performance because the data is physically read from disk each time. If you are using system monitors to track input and output for the device, this value helps you distinguish database input and output from non-database input and output. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sectors.

Efficiency Database Efficiency Avg Sect Written per Direct Write

• The average number of sectors that are written by a direct write to the database. The value is derived through this formula: direct writes / direct write reqs . Direct writes do not use the buffer pool, which results in poor performance because the data is physically written from disk each time. If you are using system monitors to track input and output for the device, this value helps you distinguish database input and output from non-database input and output. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sectors.

Efficiency Database Efficiency Avg Sync I/O Time

• The average time (in milliseconds) to perform synchronous input and output operations for the database. Use the returned value to analyze the input and output work being performed for the database. Synchronous input and output operations for a database are performed by database manager agents. Asynchronous input and output operations are performed by prefetchers (reads) and page cleaners (writes). In general, asynchronous input and output helps your applications run faster. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Avg Sync Read Time

• The average elapsed time used to perform a synchronous read. This value is derived by dividing the value of the Pool Sync Read Time attribute by the value of the Pool Sync Read attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Avg Sync Write Time

• The average elapsed time used to perform a synchronous write. This value is derived by dividing the value of the Pool Sync Write Time attribute by the value of the Pool Sync Write attribute. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Binds Precompiles

• The number of binds and precompiles attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is binds.

Efficiency Database Efficiency Current Primary Log Used Percent

• The percentage of primary log space that is currently in use. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Database Efficiency Current Secondary Log Used Percent

• The percentage of secondary log space that is currently in use. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Database Efficiency DDL SQL Percent for Interval

• The percentage of total SQL statements that were SQL DDL statements during the monitoring interval. Due to the high activity in the system catalog tables, try to keep DDL statement activity to a minimum. If the returned value is high compared to normal operating levels, determine the activity causing it to be high and restrict it from being performed. Examples of DDL statements are CREATE TABLE, CREATE VIEW, ALTER TABLE, and DROP INDEX. You can also use the returned value to refine the package cache hit ratio for this application. DDL statements can also affect the package cache by invalidating sections that are stored there and causing additional system overhead due to section recompilation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Database Efficiency Deadlocks for Interval

• The number of deadlocks detected in the database during the monitoring interval. Use the returned value to determine whether applications are experiencing conflict problems in the database. You can resolve the problem by determining in which applications the deadlocks are occurring. You can then try to modify the applications to better enable them to run concurrently. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deadlocks.

Efficiency Database Efficiency Internal Commits

• The total number of commits initiated internally by the database. Use the returned value to gain insight into internal activity within the database. The returned value is also used in calculating "Commit statements per second. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Efficiency Database Efficiency Lock Escalation for Interval

• The total number of lock escalations for applications connected to this database during the monitoring interval. Exclusive lock escalations are included in this number. Use the returned value to help you evaluate the settings of the LOCKLIST and MAXLOCKS configuration parameters. Lock escalations can result in a decrease inconcurrency between applications connected to a database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Efficiency Database Efficiency Lock List in Use Percent

• The percentage of space used in the locklist of this database. Use the returned value to determine how much of the locklist space is free for new locks to be requested. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Database Efficiency Pool I/O per Sec

• The rate (per second) of buffer pool input and output operations for the database. Buffer pool input and output includes all physical data and index pages that go through the buffer pool when read or written. Use the returned value to determine how efficient your data storage device is. A low value indicates the presence of an input and output wait, in which case you must move data to a different device. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is operations/second.

Efficiency Database Efficiency Pool Sync Data Writes

• The total number of physical write requests that were performed synchronously (that is, physical data page writes that were performed by database manager agents). This value is derived by subtracting the value of the Pool Async Data Writes attribute from the value of the Pool Data Writes attribute. By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Efficiency Database Efficiency Pool Sync Index Reads

• The number of pool index physical reads minus the pool async index reads. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Efficiency Database Efficiency Pool Sync Index Writes

• The number of physical index write requests that were performed synchronously (that is, physical index page writes that were performed by database manager agents). This value is derived by subtracting the value of the Pool Async Index Writes attribute from the value of the Pool Index Writes attribute. By comparing the ratio of asynchronous to synchronous writes, you can gain insight into how well the buffer pool page cleaners are performing. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Efficiency Database Efficiency Pool Sync Read

• The total number of synchronous reads. This value is derived by adding the values of the Pool Sync Data Reads and Pool Sync Index Reads attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Efficiency Database Efficiency Pool Sync Read Time

• The elapsed time used to perform all synchronous reads. This value is derived by subtracting the value of the Pool Async Read Time attribute from the value of the Pool Read Time attribute. Use this attribute to understand the I/O work being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Pool Sync Write

• The total number of synchronous index writes. The value is derived by adding the values of the Pool Sync Data Writes attribute and Pool Sync Index Writes attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Efficiency Database Efficiency Pool Sync Write Time

• The total elapsed time used to perform all synchronous writes. This value is derived by subtracting the value of the Pool Async Write Time attribute from the value of the Pool Write Time attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Prefetch Wait Time

• The time an application spent waiting for an I/O server (prefetcher) to finish loading pages into the buffer pool. This attribute can be used to experiment with changing the number of I/O servers and the I/O server sizes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency Primary Log Used Percent

• The percentage of total log space used by the primary log. Use the returned value to help you evaluate the allocated amount of primary log space and refine the log buffer size, log file size, and primary log configuration parameters. The returned value is valid only if circular logging is used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Database Efficiency Total Log Used

• The total log space used in bytes. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Efficiency Database Efficiency Total Sync I/O

• The total synchronous input and output. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Efficiency Database Efficiency Total Sync I/O Time

• The total time in milliseconds applied to processing requests for synchronous reads or writes for the database. The returned value is the sum of the returned values from the average pool write time (ms) and average pool read time (ms). This time is the amount of time that database agents spend doing synchronous reads and writes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Database Efficiency UID SQL Percent for Interval

• The percentage of total SQL statements that were SQL UPDATE, INSERT, and DELETE statements during the monitoring interval. Use the returned value to determine the level of database data change activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Days Since Last Backup

• The numbers of days since the last database backup was completed. The value format is an integer. The value for no backup completed is 2147483647. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is days.

Efficiency DB Capture Error

• The number of errors encountered by the Capture program within the last five minutes. Use the returned value to determine whether the Capture program encountered an error that prevented it from running. If any errors are detected, the Capture program came down at the time the error occurred. The Capture program might or might not still be down. The Capture program is the most critical replication component in the replication system. If the Capture program is not active, there are no new change records to apply to the target systems. If your data concurrency requirements are high and you want to ensure that the Capture program runs continuously, use this monitor to determine when the Capture program encounters an error that prevents it from running. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is errors.

Efficiency DB Capture Prun

• The number of rows in the unit-of-work table. Use the returned value to help you determine whether you need to prune the unit -of-work (UOW) table or the change data (CD) table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Efficiency DB Heap Top

• This data attribute (now maintained for DB2 version compatibility) measures memory usage, but not exclusively usage by the database heap. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Efficiency Deadlock Rollbacks Percent

• The percentage of the total number of rollbacks that deadlock caused. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Estore Read/Write Ratio for Interval

• The ratio as a percentage of data and index pages copied from extended storage to pages copied to extended storage during the monitoring interval. When a page is transferred from extended storage to the buffer pool, you save a system input and output call. However, you still incur the cost of attaching to the extended memory segment, copying the page, and detaching from the segment. Use the returned value to determine if you would benefit from using extended storage. The higher the ratio, the more likely you are to benefit. In general, extended storage is particularly useful if input and output activity is very high on your system. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is reads/writes.

Efficiency Event Monitors

• The number of event monitors defined in the database. Use the returned value to determine how many event monitors are defined for the database. When you define an event monitor, its definition is stored in the database system catalog table. You can create any number of event monitors. However, the maximum number of event monitors that can be active for a database at any given time is 32. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is monitors.

Efficiency Failed SQL Stmts Percent for Interval

• The percentage of total Structured Query Language statements that failed during the monitoring interval. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Internal Auto Rebinds

• The number of automatic rebinds or recompiles that were attempted in the database. Use the returned value to determine the level of database activity. Automatic rebinds are the internal binds that the system performs when a package is invalidated. They can have a significant impact on performance and must be minimized where possible. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rebinds.

Efficiency Internal Deadlock Rollbacks Percent

• The percentage of the total number of internal rollbacks due to deadlocks. Use the returned value to distinguish those rollbacks caused by internal deadlocks from rollbacks caused by other situations (for example, incomplete imports). The returned value is the percentage of internal rollbacks due to internal deadlocks since the first database connection or the last reset of the database monitor counters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Efficiency Internal Deadlock Rollbacks Percent for Interval

• The percentage of rollbacks that were due to deadlock during the monitoring interval. Use the returned value to distinguish those rollbacks caused by internal deadlocks from rollbacks caused by other situations (for example, incomplete imports). The returned value is the percentage of internal rollbacks due to internal deadlocks since the first database connection or the last reset of the database monitor counters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Internal Rows Deleted

• The number of rows deleted from the database as a result of internal activity. Use the returned value to gain insight into internal activity within the database. If this activity is high compared to normal operating levels, you can evaluate your table design to determine if the referential constraints or triggers that you defined on your database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Efficiency Internal Rows Inserted

• The number of rows inserted into a database as a result of internal activity caused by triggers. Use the returned value to gain insight into internal activity within the database. If this activity is high compared to normal operating levels, you can evaluate your design to determine if you can alter it to reduce this activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Efficiency Internal Rows Updated

• The number of rows updated in the database as a result of internal activity. Use the returned value to gain insight into internal activity within the database. If this activity is high compared to normal operating levels, you can evaluate your table design to determine if the referential constraints that you defined are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Efficiency Invalid Packages

• The number of all packages that are currently marked not valid in the database. Use the returned value as an indication of the current number of packages that are not valid. A package is marked not valid if it depends on an object (for example, a table) and that object is dropped. The number of packages that are not valid can indicate how many automatic rebinds are necessary in the database. Such packages automatically rebound the next time they are accessed, unless a trigger was dropped or the dropped object was not recreated. Use of automatic rebinds can significantly lower performance, and must be minimized if possible. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is packages.

Efficiency Invalid System Packages

• The number of system packages that are currently marked not valid in the database. Use the returned value as an indication of the current number of nonvalid packages owned by the system. A package is marked not valid if it depends on an object (for example, a table) and that object is dropped. The number of packages that are not valid can indicate how many automatic rebinds are necessary in the database. The package is automatically rebound the next time it is accessed, unless it was marked not valid because a trigger was dropped or because the dropped object was not recreated. Use of automatic rebinds can significantly lower performance, and must be minimized where possible. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is packages.

Efficiency Invalid Triggers

• The number of triggers that are marked not valid in the database. Use the returned value to determine the number of triggers that must be revalidated. A trigger is marked not valid if an object on which the trigger depends is dropped. To revalidate such a trigger, retrieve its definition from the database system catalog and submit a new CREATE TRIGGER statement. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is triggers.

Efficiency lock Timeouts for Interval

• The number of times that a request to lock an object were timed out instead of being granted during the monitoring interval. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timeouts.

Efficiency Lock Waits for Interval

• The number of times that applications had to wait for locks in the database during the monitoring interval. Use the returned value as an indication of how much time is applied to waiting for locks during a particular monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is waits.

Efficiency Lock Waits Percent

• The percentage of currently connected applications that are waiting for a lock in the database. The value is derived through this formula: 100 * locks waiting / appls cur cons If the returned value is high compared to normal operating levels, the applications can have concurrency problems. You must identify applications that are holding locks or exclusive locks for long periods of time and determine whether they can release their locks more often.
• The type is double.
• The unit is percent.

Efficiency Log I/O for Interval

• The total amount of log input and output. This amount is the sum of the number of log pages read and the number of log pages written within the monitoring interval. Use the returned value to determine whether you must move the log to a different device. If this input and output is beyond the capabilities of the current device, you can determine if moving the log (by changing the newlogpath configuration parameter) improves performance. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Efficiency Page Cleans for Interval

• The number of times a page cleaner was invoked for the database (for any reason) during the monitoring interval. Use the returned value to determine how often pages are written to disk by the page cleaners of this database. If this value increases over time, you can define more page cleaners. The number of page cleaners is determined by the number of I/O cleaners configured. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cleans.

Efficiency Pages per Prefetch for Interval

• The number of data pages read per prefetch request for the database during the monitoring interval. Use the returned value to determine the amount of asynchronous input and output in each interaction with the prefetcher. An excessively low returned value when compared to normal operating levels indicates that you need more input and output servers. The more input and output servers that you have, the better your query performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages/prefetch.

Efficiency Pool Hit Ratio Index Percent for Interval

• The database index page hit ratio (as a percentage) for the buffer pool during the monitoring interval. The index page hit ratio for the buffer pool indicates the percentage of index page requests for which the database manager did not need to load an index page from disk to service. That is, the index page was already in the buffer pool. The higher the returned value, the lower the frequency of disk input and output, and the faster the performance. If the hit ratio is low compared to normal operating levels, increasing the number of buffer pool pages can improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Pool Hit Ratio Percent for Interval

• The overall buffer pool hit ratio as a percentage for the database during the monitoring interval. This hit ratio includes both index and data page activity. The overall buffer pool hit ratio indicates the percentage of page requests for which the database manager did not need to load a page from disk to service. (That is, the page was already in the buffer pool. ) The greater the buffer pool hit ratio, the lower the frequency of disk input and output. If the hit ratio is low compared to normal operating levels, increasing the number of buffer pool pages can improve performance. A ratio of zero indicates that pages needed to be read for every request. For a large database, increasing the buffer pool size can have a minimal effect on the buffer pool hit ratio. Such a database can have so large a number of data pages that the statistical chance of a hit is not increased by an increase of the buffer pools. However, even though the data might be too large to fit in the buffer pool, the entire index can fit. In this case, you can refine buffer pool sizes until the overall buffer pool hit ratio stops increasing, and then refine the buffer pool until the buffer pool index hit ratio no longer increases. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Primary Log Used Top

• The maximum bytes of primary logs used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Efficiency Rollback Rate for Interval

• The rate, in rollbacks per second, at which unit-of-work rollbacks were attempted during the monitoring interval. Unit-of-work rollbacks include SQL ROLLBACK statements that are issued from applications and INTERNAL ROLLBACKS that the database manager initiates. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Secondary Log Used Percent

• The percentage of maximum log space used by the secondary log. Use the returned value to show the current dependency on secondary logs. Secondary logs are used when you have circular logging (log retention off) and the primary log files are full.
• The type is double.
• The unit is percent.

Efficiency Select SQL Percent for Interval

• The percentage of total SQL statements that were SQL SELECT statements during the monitoring interval. Use the returned value to determine the level of application activity and throughput for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Sort Overflows Percent for Interval

• The percentage of application sorts that overflowed during the monitoring interval. An overflow occurs when a sort has run out of space in the sort heap and requires disk space for temporary storage. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency SQL Stmts Rate for Interval

• The rate, in issued SQL statements per second, at which SQL statements that run during the monitoring interval. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Efficiency Total Direct I/O Time

• The total time in milliseconds applied to direct reads and writes for the database. The returned value indicates the amount of time that the database performs direct reads and writes. A high returned value compared to normal operating levels can indicate the presence of an input and output conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Total Pool Phys I/O

• The total time in milliseconds applied to physical I/O for the database. A high returned value (as compared to the total number of physical buffer pool input and output operations) can indicate the presence of an input and output wait, which in turn can indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Total Pool Phys Read

• The total time in milliseconds applied to processing read requests that caused data or index pages to be physically read from disk to the buffer pool for the database. The value is derived through this formula: pool data p reads + pool index p reads . The returned value is used to calculate the average pool read time. This average can indicate the presence of an input and output wait, which in turn can indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Total Pool Phys Write

• The total time in milliseconds for buffer pool physical writes (including asynchronous writes). The value is derived through this formula: pool data writes + pool index writes . The returned value is used to calculate the average pool write time. This average can indicate the presence of an input and output wait, which in turn can indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Efficiency Triggers

• The number of triggers defined in the database. Use this attribute to track the use of triggers in the database. There are benefits to using triggers, including faster application development, easier maintenance, and global enforcement of business rules. For more information, see the DB2 administration documentation for the version of DB2 that you are using. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is triggers.

Efficiency User Indexes

• The number of indexes created by users in the database. Indexes created by SYSIBM are not counted. Use this to track the use of indexes in the database. The use of indexes can improve performance; for example, faster sorting of data. However, indexes can also have adverse effects on performance; for example, each INSERT or DELETE operation performed on a table requires additional updating of each index on that table. For a discussion of this topic, see the DB2 administration documentation for the version of DB2 that you are using. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is indexes.

Efficiency Views

• The number of views in the database. Use this attribute to track the use of views in the database. Views can be created to limit access to sensitive data, while allowing more general access to other data. This provides flexibility in the way your programs and end-user queries can look at the table data. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is views.

Dimensions

The following dimensions are available for the component.

Efficiency Appl Control Heap Size

• The maximum size (in 4-KB pages) for the application control heap in the database during the monitoring interval. The heap is required to share information among agents working on behalf of the same application at a node in a massively parallel processing (MPP) or a symmetric multiprocessor (SMP) system. If complex applications are being run or the MPP configuration has a large number of nodes, you must increase the size of this heap. In a partitioned database environment, this heap is used to store copies of the executing section of SQL statements for agents and subagents. However, symmetric multiprocessor agents (SMP), subagents, and agents in all other environments use appl heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Appl Heap Size

• The size (in 4-KB pages) of the application heap that is available for each individual agent in the database during the monitoring interval. Increase the value of the parameter if your application receives an error indicating that there is not enough storage in the application heap. The heap is allocated when an agent or subagent is initialized for an application. The amount allocated is the minimum amount needed to process the request given to the agent or subagent. When the agent or subagent requires more heap space to process larger SQL statements, the database manager allocates memory as needed, up to the maximum specified by the parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Buff Page

• Use the returned value (in units of 4-KB pages) to analyze the input and output work being performed for the database. Synchronous input and output operations for a database are performed by database manager agents. Asynchronous input and output operations are performed by prefetchers (reads) and page cleaners (writes). In general, asynchronous input and output helps your applications run faster. In the currently supported releases of DB2, multiple buffer pools might be defined in a single database. For instance, buffer pools can be defined and associated with a particular tablespace. Each buffer pool created can be given its own individual size. The buffpage attribute serves only as a default value for buffer pools created within a particular database. Therefore, the value of the buffpage attribute is much less critical to performance in current releases of DB2, because most buffer pools are given an individual size when created. The buffpage attribute must not be used to evaluate or tune the performance of DB2 unless it is used as the default value when creating buffer pools in a database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Catalog Cache Size

• The value in units of 4-KB pages of the catalog cache size. This value is the maximum amount of space that the catalog cache can use from the database heap (dbheap). The catalog cache is referenced whenever a table, view, or alias name is processed during the compilation of an SQL statement. It is dynamically allocated from dbheap, as required, until the catalog cache size is reached. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Change Pages Threshold

• The value in percentage units of the changed pages threshold. This value sets a limit on how much buffer pool space can be occupied by changed pages before the asynchronous page cleaners are started, if they are not currently active. Asynchronous page cleaners write changed pages from the buffer pool to disk before the space in the buffer pool is required by a database agent. This means that the agents do not need to wait for a changed page to be written out before being able to read a page, and application transactions run faster. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Database Efficiency Log Primary

• The number of primary log files. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Database Efficiency New Log Path

• The current value of the newlogpath configuration parameter. You use the newlogpath configuration parameter to specify a new location for the log files. The specified path does not become the current log path until both of the following conditions are met:
  • The database is in a consistent state.
  • All users are disconnected from the database.
  When the first new connection is made to the database, the database manager moves the logs to this location. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Efficiency Database Efficiency Restore Pending

• The RESTORE PENDING status in the database during the last monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Database Heap

• The value in units of 4-KB pages of the database heap. This value is the maximum amount of memory allowed for a database heap. There is one database heap for each database. It is used on behalf of all applications connected to the database. Refining dbheap has minimal impact on performance. The main function of this parameter is to prevent the database manager from allocating an excessive amount of space for a particular database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency DB Capture Lag

• The time difference in minutes between the current timestamp and the last timestamp recorded by the Capture program. This time difference is the Capture lag. Use the returned value to determine whether the Capture program is keeping up with the DB2 database log. The Capture program uses an interface to the DB2 database log or journal to detect and save changes to the data in the tables registered for replication. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 characters.
• The type is string.

Efficiency DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:.
• The type is string.

Efficiency DB Tablespaces

• The number of Database Managed Space tablespaces in the database. Use this attribute to track database growth over a period of time. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Efficiency Lock List

• The value in units of 4-KB pages of the maximum storage for lock lists. This value is the amount of storage that is allocated to the lock list. There is one lock list for each database, and it contains the locks held by all applications concurrently connected to the database. Too small a value can lead to excessive lock waits. Too high a value compared to normal operating levels can deprive the system of resources or memory. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Log Buffer Size

• This value specifies the amount of the database heap to use as a buffer for log records before writing these records to disk. It is important that the log buffer can hold the amount of log space used by an average transaction. Otherwise, logging performance decreases and slows the overall system. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Max Active Applications

• The value of the maximum number of active applications. This value is the maximum number of concurrent applications that can be connected (both local and remote) to a database. Because each application that attaches to a database causes some private memory to be allocated, allowing a large number of concurrent applications potentially uses more memory. Increasing the value of this parameter without lowering the maxlocks parameter or increasing the locklist parameter can cause you to reach the database limit on locks (locklist) rather than the application limit. The result can be pervasive lock escalation problems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Max Locks

• The value of the maximum percentage of lock list before escalation. This value specifies the percentage of the lock list that an application can hold before the database manager performs lock escalation. Lock escalation can increase contention, which reduces system throughput and increases user response time. The values for the maxlocks and maxappls parameters must satisfy (MAXLOKS x MAXAPPLS) >100, and each lock uses 32 bytes. Rebind application packages after changing this parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Min Commit

• The value of the number of commits to group. By using this parameter you can delay the writing of log records to disk until a minimum number of commits have been performed. This delay can help reduce the overhead associated with writing log records and can improve performance. The default value for mincommit is 1, which can be too low for your environment. By sampling the number of transactions per-second throughout the day, you can determine the peak per second rate and adjust the value of the mincommit parameter to accommodate all or most transactions. This adjustment minimizes the number of log writes under the heaviest conditions. As you increase the value of the mincommit parameter, you might also need to increase the log buffer size (LOGBUFSZ parameter) to avoid filling the log buffer. Filling the log buffer also forces the writing of log records to disk. If you change the value of the mincommit parameter, you must change the value for the logbufsz configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Node Name

• The format is instanceid:hostname:UD for all operating systems.
• The type is string.

Efficiency Num IO Servers

• The current value of the number of input and output servers. This value specifies the number of input and output servers for a database. Input and output servers are used on behalf of the database agents to perform asynchronous input and output operations for utilities such as backup and restore, and to perform prefetch input and output (in which case, they are called prefetchers) operations. Prefetchers read pages from disk into the buffer pool in anticipation of their use. In most situations, these pages are read just before they are needed. However, prefetchers can cause unnecessary input and output operations by reading pages into the buffer pool that might not be used. For example, an application starts reading through a table, and prefetchers read consecutive pages into the buffer pool before the pages are required by the application. Then the application fills the application buffer and stops reading. Meanwhile, the prefetchers already have performed the input and output operations for additional pages and the buffer pool is partially taken up with those pages. To exploit all the input and output devices in the system, a good value for num_ioservers to use is one or two more than the number of physical devices on which the database is established. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Number of I/O Cleaners

• The current value of the number of asynchronous page cleaners. This parameter specifies the number of asynchronous page cleaners for a database. Page cleaners monitor the buffer pool and asynchronously write out changed pages to disk to free space in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Package Cache Size

• The current value in units of 4-KB pages of the package cache size. This value controls the amount of application heap memory to be used for caching static and dynamic SQL statements of a package. You must experiment with the size of the package cache to find the optimal number for this attribute. For example, you can use a smaller package cache size if there is no increase in the number of package cache inserts when you decrease the size of the cache. Decreasing the package cache size frees up system resources for other work. However, increasing the package cache size can improve overall system performance if it results in a decrease of package cache inserts. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Sequential Detect

• The current value of the sequential detection flag, which determines if the database manager must perform sequential detection. The database manager can monitor input and output operations. If sequential page reading is occurring, the database manager can activate input and output prefetching. This type of sequential prefetch is known as sequential detection. If this configuration parameter is set to no , prefetching takes place only if the database manager determines that it is useful (for example, in table sorts). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Efficiency Sort Heap

• The current value in units of 4-KB pages of the sort heap size. This value is the maximum amount of memory that can be allocated as sort heap for each sort within a database. The sort heap is the memory block where data is sorted. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency System Tablespaces

• The number of SMS tablespaces in the database. Use the returned value to evaluate the use of SMS tablespaces and their effects on performance. Table data that is read from disk is available in the database buffer pool. Sometimes a data page is freed from the buffer pool before it is used. For SMS tablespaces, when the database manager requests that data page from the file system, the data page might still be in the cache of the file system. Having the page in the cache saves an input and output operation that would otherwise have been required. (For more information, see the DB2 administration documentation for the version of DB2 that you are using. ) If you have many SMS tablespaces, you can increase the size of the file system cache to take advantage of this extra buffering. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Tables

• The number of tables in the database. Use this attribute to track database growth due to an increased number of tables over a period of time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Tablespaces

• The number of tablespaces in the database. Use this attribute to track database growth over a period of time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Efficiency Tablespaces Long Data

• The number of tablespaces that store LONG data in the database. Use this attribute to track database growth over a period of time. LONG data can take up a large amount of space in a database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Component: dcsDatabase

The DCS Database attributes provide Direct Connection Service (DCS) database information for the monitored database gateway. You can use this information to monitor DCS database specific attributes, such as DCS connection response times and communication errors. The following section lists the metrics and dimensions of Component dcsDatabase.

Metrics

The following metrics are available for the component.

DCS GW Comm Errors for Interval

• The number of times during the monitoring interval that a communication error (SQL30081) occurred while a DCS application tried to connect to a host database, or while it was processing an SQL statement. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is errors.

DCS GW Comm Errors for Interval (Superseded)

• The number of times during the monitoring interval that a communication error (SQL30081) occurred while a DCS application tried to connect to a host database, or while it was processing an SQL statement. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is errors.

DCS GW Cons Wait Host

• The current number of connections to host databases that the DB2 Connect gateway is handling, and that are waiting for a reply from the host. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

DCS GW Cons Wait Host (Superseded)

• The current number of connections to host databases that the DB2 Connect gateway is handling, and that are waiting for a reply from the host. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is connections.

DCS GW Cur Cons

• The current number of connections to host databases that the DB2 Connect gateway is handling. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

DCS GW Cur Cons (Superseded)

• The current number of connections to host databases that the DB2 Connect gateway is handling. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is connections.

DCS Host Throughput for Interval

• The host throughput in bytes per second for the monitoring interval. This number represents bytes sent plus the number of bytes received divided by the cumulative host response time. The value format is an integer. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes/second.

DCS Host Throughput for Interval (Superseded)

• The host throughput in bytes per second for the monitoring interval. This number represents bytes sent plus the number of bytes received divided by the cumulative host response time. The value format is an integer. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is bytes/second.

DCS Host Time per Stmt for Interval

• The host response time (in seconds) over the last interval, including any network time over the last interval, divided by the number of statements attempted over the last interval. The value format is an integer. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

DCS Host Time per Stmt for Interval (Superseded)

• The host response time (in seconds) over the last interval, including any network time over the last interval, divided by the number of statements attempted over the last interval. The value format is an integer. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is seconds.

DCS Network Time per Stmt

• The total host response time minus the total statement execution time divided by the total number of attempted statements. The value format is an integer. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds/attempts.

DCS Network Time per Stmt (Superseded)

• The total host response time minus the total statement execution time divided by the total number of attempted statements. The value format is an integer. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is result.

DCS Recent Con Rsp Time

• The elapsed time (in seconds) between the start of connection processing and actual establishment of a connection for the most recent DCS application that connected to this database. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is seconds.

DCS Recent Con Rsp Time (Superseded)

• The elapsed time (in seconds) between the start of connection processing and actual establishment of a connection for the most recent DCS application that connected to this database. This is available for thresholds, but not in the UI.
• The type is double.
• The unit is seconds.

DCS Time per Stmt

• The statement execution time (in seconds) divided by the number of attempted statements. The value format is an integer. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds/attempts.

DCS Time per Stmt (Superseded)

• The statement execution time (in seconds) divided by the number of attempted statements. The value format is an integer. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is seconds.

Dimensions

The following dimensions are available for the component.

DCS DB Name

• The real name of the host database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

DCS DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

DCS Instance Name

• The name of the monitored DB2 instance (Unicode). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

DCS Node Name

• The format is instanceid:hostname:UD for all operating systems. The format for version 6, release 1 of the DB2 Connect agent on Windows systems is instanceid:hostname:UD; on UNIX and Linux systems, the format is instanceid:hostname. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

DCS Snapshot Timestamp

• The date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Component: diagnosticLog

Information about log record from a given facility. The following section lists the dimensions of Component diagnosticLog.

Dimensions

The following dimensions are available for the component.

Diagnostic Component Name

• The name of the component that created the message. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic DB Name

• The real name of the database for which information is collected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Facility

• A facility is a logical grouping which records relate to. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Function Name

• The name of the function that generated the message. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Function String

• A string provides information about the function that generated the message, including product name, component name, function name, and probe number. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Impact

• This attribute qualifies the impact of this message from a user's perspective. This clarifies the impact of the message on the business process DB2 is part of. The following values are valid: NONE, UNLIKELY, POTENTIAL, IMMEDIATE, and CRITICAL. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Level

• The severity level of the record. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Message

• The short description text for this record. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Message Number

• The numeric message number. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Diagnostic Message Type

• The type of the message. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic MSGID

• The unique message identifier of the message. The msgid is the combination of the message type, message number, and level. For example, ADM7513W. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Partition Num

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Diagnostic PID

• The identifier of the operating system process that created this message. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Diagnostic Process Name

• The name of the operating system process that created this message. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic Record Type

• The type of the record. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Diagnostic TID

• The numerical identifier of the thread that created this message. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Diagnostic Timestamp

• The date and time when the message was created. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Diagnostic Timezone Displacement

• The difference between UTC (Coordinated Universal Time, formerly known as GMT) and local time at the application server. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Component: events

Detailed information about predefined and triggered events. The following section lists the dimensions of Component events.

Dimensions

The following dimensions are available for the component.

Event Category

• The category of the event. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Event DB Name

• The real name of the database for which information is collected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies.
• The type is string.

Event Description

• The description of the event.
• The type is string.

Event Error Code

• The error code returned by the DB2 instance.
• The type is int.

Event Error Message

• The error message returned by the DB2 instance.
• The type is string.

Event Host Name

• The hostname of the machine where the DB2 database is hosted. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Event Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Event Level

• The level of the event. This can be either Error, Warning, Info or Misc. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Event Node Name

• The managed system name of the agent. For new installations of version 7, release 1, the format is instanceid:hostname:UD for all operating systems.
• The type is string.

Event SQL State

• The SQL state returned by the DB2 instance.
• The type is string.

Event Subcategory

• The subcategory of the event. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Event Suggestion

• The suggestion, detailing how best to proceed once the event has been triggered.
• The type is string.

Event Time Stamp

• The local time on the agent when the event was triggered.
• The type is timestamp.

Component: highAvailabilityDisasterRecovery

Information about High Availability Disaster Recovery (HADR) configuration and status. The following section lists the metrics and dimensions of Component highAvailabilityDisasterRecovery.

Metrics

The following metrics are available for the component.

Disaster Recovery Application Current Connections

• The number of applications that are connected to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

HADR Disconnect Time Left

• Time left to close HADR connection in seconds. Derived from Heartbeat Timeout and Time Since Last Recv. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

HADR Log Delay

• Calculated HADR log delay in seconds. Derived from Primary Log Time and Standby Log Time.
• The type is int.
• The unit is seconds.

HADR Log Gap

• Shows the recent average of the gap between the value PRIMARY LOG POS and value STANDBY LOG POS. The gap is measured in number of kilobytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is kilobytes.

HADR State

• The current High Availability Disaster Recovery state of the database.
• The type is int.
• The unit is state.

HADR Syncmode

• The current High Availability Disaster Recovery synchronization mode of the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.
• The unit is state.

HADR Wait Time per Log Flush

• Average log HADR wait time in seconds. Derived as average of Log HADR Wait Time and Log HADR Waits Total. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Heartbeat Miss Rate

• The rate of missed heartbeats. It is derived from Heartbeat Expected and Heartbeat Missed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Overall HADR Status

• The comprehensive HADR connection status for all partner databases. The status returns 'Critical' when HADR state for primary database or principle standby is DISCONECTED. It is derived as 'Warning' if the HADR state for auxiliary/secondary standby is DISCONNECTED. Otherwise the peer DB status is 'Normal'.
• The type is int.
• The unit is status.

Standby Key Rotation Error

• Returns YES, if the standby database encountered a master key rotation error.
• The type is int.
• The unit is flag.

Standby Log Device Full

• Returns YES, if the standby log device is full.
• The type is int.
• The unit is flag.

Standby Receive Blocked

• Returns YES, if the standby database temporarily cannot receive logs.
• The type is int.
• The unit is flag.

Standby Receive Buffer Percent

• Indicates the percentage of standby log receiving buffer that is being used during log shipping. When spooling is enabled, standby can continue to receive logs even when receive buffer is full (that is 100% used). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Standby Receive Replay Gap

• The recent average in kilobytes, of the gap between the standby log receive position and the standby log replay position. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is kilobytes.

Standby Replay Not on Preferred

• Returns YES, if the current replay member on the standby is not the preferred replay member.
• The type is int.
• The unit is flag.

Standby Replay Only Window Active

• Indicates whether the DDL or maintenance-operation replay is in progress on the standby.
• The type is int.
• The unit is state.

Standby Spool Limit

• The maximum number of pages to spool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Standby Spool Percent

• The percentage of spool space used, relative to the configured spool limit. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Standby Tablespace Error

• Returns YES, if a table space of standby database is in an invalid error state and can no longer replay transactions affecting it.
• The type is int.
• The unit is flag.

Dimensions

The following dimensions are available for the component.

Assisted Member Active

• Returns YES, if the member on primary database that is being assisted is active during assisted remote catchup. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Connect Status

• The current HADR connection status of the monitored database.
• The type is int.

Disaster Recovery Connect Time

• Depending on the connection status, the value is the HADR connection time, HADR congestion time, or HADR disconnection time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Disaster Recovery Database Status

• The status of the monitored database.
• The type is int.

Disaster Recovery DB Alias

• The alias of the database for which information is collected. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery DB Location

• The location of the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery DB Name

• The name of the monitored database.
• The type is string.

Disaster Recovery DB Partition

• The mode of the database partition.
• The type is int.

Disaster Recovery Heartbeat

• The number of missed heartbeats on the HADR connection. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Instance Name

• The name of the monitored DB2 instance (Unicode).
• The type is string.

Disaster Recovery Local Host

• The name of the local HADR host. The value is displayed as a host name or an IP address. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Local Service

• The local HADR TCP service. The value is displayed as a service name or a port number. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Log Gap

• The average gap (in bytes) between the primary log sequence number (LSN) and the standby LSN. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Node Name

• The node name of the database.
• The type is string.

Disaster Recovery Peer Window

• The value determines whether the database goes into the disconnected peer state after a connection is lost and how long the database remains in that state. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Peer Window End

• The time until which a HADR primary database stays in the peer or disconnected peer state. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Disaster Recovery Primary Log File

• The name of the current log file on the primary HADR database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Primary Log LSN

• The current log position of the primary HADR database. The log sequence number (LSN) is a byte offset in the database log stream. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Primary Log Page

• The page number in the current log file, indicating the current log position on the primary HADR database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Remote Host

• The name of the remote HADR host. The value is displayed as a host name or an IP address. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Remote Instance

• The name of the remote HADR instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Remote Service

• The remote HADR TCP service. The value is displayed as a service name or a port number. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Role

• The current HADR role of the monitored database.
• The type is int.

Disaster Recovery Snapshot Timestamp

• The date and time of the database snapshot. This is available for thresholds, but not in the UI.
• The type is timestamp.

Disaster Recovery Standby Log File

• The name of the current log file on the standby HADR database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Disaster Recovery Standby Log LSN

• The current log position of the standby HADR database. The log sequence number (LSN) is a byte offset in the database log stream. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Standby Log Page

• The page number in the current log file, indicating the current log position on the standby HADR database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery State

• The current HADR state of the database.
• The type is int.

Disaster Recovery Syncmode

• The current HADR synchronization mode of the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Disaster Recovery Timeout

• The time after which if no communication is received from the partner, an HADR server determines that the connection between them fails. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

HADR Role

• The current High Availability Disaster Recovery role of the database.
• The type is int.

HADR Timeout

• Represents the time period in seconds lapsed, since an HADR database server has confirmed its connection to the partner database is failed, and there is no communication from the partner database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

HADR01 DB Name

• The name of database.
• The type is string.

HADR01 Instance Name

• The name of the monitored DB2 instance.
• The type is string.

HADR01 Node Name

• Name of origin node of DB2 agent.
• The type is string.

Peer Wait Limit

• Represents the value of registry variable DB2_HADR_PEER_WAIT_LIMIT that is used to limit the primary logging wait time in the peer state. The unit is in second. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Peer Window

• Represents a value (in seconds) of hadr_peer_window, a configurable parameter of database. This is the configured amount of time for which a HADR primary-standby database pair continues to behave as in a disconnected peer state when the primary database loses connection with the standby database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Primary Host

• The value of the configuration parameter hadr_local_host of the member on the primary host that is processing the log stream.
• The type is string.

Primary Instance

• The DB2 instance name on the primary host that is processing the log stream.
• The type is string.

Primary Log File

• The name of the current log file on the primary HADR database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Query Timestamp

• Date/Time of query execution.
• The type is timestamp.

Read on Standby Enabled

• Indicates whether the Reads on standby feature is enabled. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Row Number

• Row Number. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Standby Error Time

• Timestamp of the last error message logged by the standby database.
• The type is timestamp.

Standby Host

• The value of the configuration parameter hadr_local_host of the standby member that is processing the log stream.
• The type is string.

Standby Instance

• The DB2 instance name of the standby member that is processing the log stream.
• The type is string.

Standby Log File

• The name of the current log file on the standby HADR database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Standby Replay Log File

• The name of the log file corresponding to the standby replay log position on the currently active log stream. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Component: log

Information about database configuration parameters that are related to archive logs, the number of archive logs, and the size of archived log path. The following section lists the metrics and dimensions of Component log.

Metrics

The following metrics are available for the component.

Log Arch Meth1 Free Size

• The amount of free space (in MB) of the primary destination for archived logs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Arch Meth1 Total Size

• The capacity (in MB) of the primary destination for archived logs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Arch Meth2 Free Size

• The amount of free space (in MB) of the secondary destination for archived logs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Arch Meth2 Total Size

• The capacity (in MB) of the secondary destination for archived logs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Buffer Size (4KB)

• This value specifies the amount (in 4KB) of the database heap to use as a buffer for log records before writing these records to disk. It is important that the log buffer can hold the amount of log space used by an average transaction. Otherwise, logging performance decreases and slows the overall system. The valid format is integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is 4kilobyteBlocks.

Log Current Archive Log

• The file number of the log file the DB2 instance is currently archiving. If the DB2 instance is not archiving a log file, the value for this element is SQLM_LOGFILE_NUM_UNKNOWN. Use this attribute to determine if there is a problem archiving log files. Such problems include the following two problems:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is fileNumber.

Log Current Primary Log Used Percent

• The percentage of the primary log space that are currently used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Log Current Secondary Log Used Percent

• The percentage of the secondary log space that are currently used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Log Fail Log Path Free Size

• The amount of free space (in MB) that is available on the file system that is pointed to by the fail log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Fail Log Path Total size

• The capacity of the file system (in MB) that is pointed to by the fail log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log File Size (4KB)

• This value defines the size (in 4KB) of each primary and secondary log file. The size of these log files limits the number of log records that can be written to them before they become full and a new log file is required. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is 4kilobyteBlocks.

Log Held By Dirty Pages

• The amount of log (in bytes) corresponding to the difference between the oldest dirty page in the database and the top of the active log. When the snapshot is taken, this value is calculated based on conditions at the time of that snapshot. Use this element to evaluate the effectiveness of page cleaning for older pages in the buffer pool. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Log Mirror Log Path Free Size

• The amount of the free space (in MB) of the file system that is pointed by the mirror log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Num Arch Retry

• The number of times that the monitored DB2 instance is to try archiving a log file to the primary or the secondary archive directory before trying to archive log files to the failover directory. This parameter is only used if the failarchpath database configuration parameter is set. If the failarchpath database configuration parameter is not set, DB2 will continuously retry archiving to the primary or the secondary log path. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is attempts.

Log Path Free Size

• The amount of the free space (in MB) on the file system that is pointed to by the log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is megabytes.

Log Primary

• The number of primary log files. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Log Read Time

• The total elapsed time that the logger spends reading log data from the disk. Use this attribute with the log reads, num log read io, and num log data found in buffer attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Log Sec Log Used Percent

• The percentage of maximum log space used by the secondary log. Use the returned value to show the current dependency on secondary logs. Secondary logs are used when you have circular logging (log retention off) and the primary log files are full. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Log Second

• The number of secondary log files. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Log to Redo for Recovery

• The amount of log (in bytes) that will have to be redone for crash recovery. When the snapshot is taken, this value is calculated based on conditions at the time of that snapshot. Larger values indicate longer recovery times after a system crash. If the value seems excessive, check the log held by dirty pages attribute to see if page cleaning needs to be tuned. Also check if there are any long running transactions that need to be terminated. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Log Write Time

• The total elapsed time that the logger spends writing log data to the disk. Use this attribute with the log writes and num log write io attributes to determine whether the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Logging Log Reads

• The number of log pages that are read from disk by the logger. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Logging Log Writes

• The number of log pages written to disk by the logger. Use this attribute with an operating system monitor to quantify the amount of I/O on a device that is attributable to database activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Logging Num Log Buffer Full

• The number of times that agents have to wait for log data to write to disk while copying log records into the log buffer. This value is increased per agent per incident. For example, if two agents attempt to copy log data while the buffer is full, this value is increased by two. Use this attribute to determine if the LOGBUFSZ database configuration parameter needs to be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Logging Num Log Data Found in Buffer

• The number of times that an agent reads log data from the buffer. Reading log data from the buffer is preferable to reading from the disk because the latter is slower. Use this attribute with the num log read io attribute to determine if the LOGBUFSZ database configuration parameter needs to be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Logging Num Log Part Page IO

• The number of I/O requests that are issued by the logger for writing partial log data to the disk. Use this attribute with the log writes, log write time, and num log write io attributes to determine if the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Logging Num Log Read IO

• The number of I/O requests that are issued by the logger for reading log data from the disk. Use this attribute with the log reads and log read time attributes to determine if the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Logging Num Log Write IO

• The number of I/O requests that are issued by the logger for writing log data to the disk. Use this attribute with the log writes and log write time attributes to determine if the current disk is adequate for logging. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Logging Primary Log Used Percent

• The percentage of total log space used by the primary log. Use the returned value to help you evaluate the allocated amount of primary log space and refine the log buffer size, log file size, and primary log configuration parameters. The returned value is valid only if circular logging is used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Logging Sec Log Used Top

• The maximum amount of secondary log space (in bytes) that has been used. Use this attribute with the Secondary Logs Allocated and Total Log Used Top attributes to show the current dependency on secondary logs. If this value is high, you might need larger log files, more primary log files, or more frequent COMMIT statements within your application. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Logging Sec Logs Allocated

• The total number of secondary log files that are currently being used for the database. Use this attribute with the Secondary Log Used Top and Total Log Used Top attributes to show the current dependency on secondary logs. If this value is consistently high, you might need larger log files, more primary log files, or more frequent COMMIT statements within your application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Logging Total Log Available

• The amount of active log space in the database that is not being used by uncommitted transactions (in bytes). Use this element in conjunction with the total log used attribute to determine whether you need to adjust the following configuration parameters of the monitored DB2 instance to avoid running out of log space:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Logging Total Log Used

• The total log space used in bytes in the database. The value format is an integer. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Logging Total Log Used Pct

• The percentage of the log space that is in used the database. The value is calculated using the following formula:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Logging Total Log Used Top

• The maximum amount of total log space (in bytes) that has been used. The value format is an integer. Use this attribute to evaluate the amount of primary log space that is allocated. Comparing the value of this attribute with the amount of primary log space that is allocated can help you evaluate the configuration parameter settings. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Dimensions

The following dimensions are available for the component.

Log Arch Meth1

• The media type of the primary destination for archived logs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Arch Meth2

• The media type of the secondary destination for archived logs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Arch Retry Delay

• The archive retry delay on error configuration parameter of the monitored DB2 instance. This parameter specifies the number of seconds to wait after a failed archive attempt before trying to archive the log file again. Subsequent retries only takes affect if the value of the numarchretry database configuration parameter is at least 1. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Backup Pending

• This parameter indicates whether you need to do a full backup of the database before accessing it. This parameter is only on if the database configuration is changed so that the database moves from being nonrecoverable to recoverable (that is, initially both the logretain and userexit parameters were set to NO, and then either one or both of these parameters is set to YES, and the update to the database configuration is accepted). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Current Active Log

• The file number of the active log file that the monitored DB2 instance is currently writing. Use this attributes with the first active log and last active log attributes to determine the range of active log files. Knowing the range of active log files helps you determine the disk space required for log files. You can also use this attribute to determine which log files have data to help you identify log files needed for split mirror support. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Database Is Consistent

• This attribute indicates whether the database is in a consistent state. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log DB Alias

• The alias of the database for which information is collected. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log DB Name

• The real name of the database for which information is collected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If you do not specify a db partition filter, data is returned for either the current database partition (single partition environment) or the aggregated database partitions (multiple partition environment). If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Fail Log Path

• This attribute specifies a path to which the monitored DB2 instance will try to archive log files if the log files cannot be archived to either the primary or the secondary (if set) archive destinations because of a media problem affecting those destinations. This specified path must reference a disk. If there are log files in the directory that is specified by the fail log path attribute, any updates to the fail log path attribute will not take effect immediately. Instead, the update will take effect when all applications disconnect. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log First Active Log

• The file number of the first active log file. Use this attribute with the last active log and current active log attributes to determine the range of active log files. Knowing the range of active log files helps you determine the disk space required for log files. You can also use this attribute to determine which log files have data to help you identify log files needed for split mirror support. The following value is valid: First active log file. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Last Active Log

• The file number of the last active log file. Use this attribute with the first active log and current active log attributes to determine the range of active log files. Knowing the range of active log files helps you determine the disk space required for log files. You can also use this attribute to determine which log files have data to help you identify log files needed for split mirror support. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Mirror Log Path

• The string that is specified for the mirror log path. The string points to a full qualified path name. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Mirror Log Path Total Size

• The capacity (in MB) of the file system that is pointed by the mirror log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log New Log Path Free Size

• The amount of the free space (in MB) of the file system that is pointed by the new log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log New Log Path Total Size

• The capacity (in MB) of the file system that is pointed by the new log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Overflow Log Path

• The location for DB2 to find log files that are needed for a rollforward operation, and to store active log files that are retrieved from the archive. It also gives a location for finding and storing log files that are needed for using db2ReadLog API. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Overflow Log Path Free Size

• The amount of free space (in MB) of the file system that is specified by the overflow log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Overflow Log Path Total Size

• The capacity (in MB) of the file system that is specified by the overflow log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Path

• This value indicates the current path that is used for logging purposes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Path Total Size

• The capacity of the file system (in MB) that is pointed by the log path attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Record Backup ID

• The backup identifier or unique table identifier. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record DB Alias

• The alias of the database for which information is collected. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record DB Name

• The real name of the database for which information is collected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If you do not specify a db partition filter, data is returned for either the current database partition (single partition environment) or the aggregated database partitions (multiple partition environment). If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Device Type

• The type identifier of the device that is associated with a logged event. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record End Timestamp

• The date and time that a logged event ended. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Log Record Entry Status

• The identifier for the status of an entry in the history file. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record First Log

• The name of the earliest transaction log that is associated with an event. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Last Log

• The name of the latest transaction log that is associated with an event. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Location

• The full path of the location to store files, such as backup images or load input file, that are associated with logged events. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Object Type

• The identifier for the target object of an operation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Operation

• The operation identifier. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Operation Type

• The action identifier of an operation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Log Record Sequence Number

• The sequence number. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Record Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Log Record Start Timestamp

• The date and time that a logged event started. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Log Record Uniquely Identifies

• The number that uniquely identifies an entry in the history file. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Retain

• The value of the log retain enable configuration parameter. The attribute is deprecated in DB2 Version 9. 5, but is used in pre-Version 9. 5 data servers and clients. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Rollforward Pending

• This attribute indicates whether the monitored DB2 instance is the rollforward pending status. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Log Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Log User Exit

• The value of the user exit enable configuration parameter. The parameter is deprecated in DB2 Version 9. 5, but is used in pre-Version 9. 5 data servers and clients. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Logging New Log Path

• The current value of the newlogpath configuration parameter. You can use the newlogpath configuration parameter to specify a new location for the log files. The specified path does not become the current log path until both of the following conditions are met:
  • The database is in a consistent state.
  • All users are disconnected from the database.
  When the first new connection is made to the database, the database manager moves the logs to this location. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Logging Restore Pending

• This attribute indicates whether a RESTORE PENDING status exists in the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Component: slowSQLStatements

Information about slow SQL Statements. The following section lists the metrics and dimensions of Component slowSQLStatements.

Metrics

The following metrics are available for the component.

Slow SQL Lock wait

• The total number of times that applications or connections waited for locks while executing the SQL Statement.
• The type is int.
• The unit is waits.

Dimensions

The following dimensions are available for the component.

Slow SQL Active State

• The state of the SQL statement.
• The type is string.

Slow SQL DB Name

• The name of the monitored database.
• The type is string.

Slow SQL DB Partition

• The DB2 database partition node number. DB2 partition numbers range from 0 to 999. The 'Aggregated' and 'Current' values can be used within a query or situation filter. If no db partition filter is specified, then a row of data will be returned for each database partition. If a db partition filter is used with the 'Aggregated' value, then only aggregated partition data will be returned. Historical data collection will include both aggregated and individual partition attribute data.
• The type is int.

Slow SQL Duration

• The duration of executing the SQL statement.
• The type is string.

Slow SQL Executable ID

• The unique identifier for the SQL statement.
• The type is string.

Slow SQL Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Slow SQL Node Name

• The origin node of db2 agent.
• The type is string.

Slow SQL Statement Text

• The query for the SQL statement.
• The type is string.

Slow SQL Statement Type

• The type of the SQL statement, such as static or dynamic.
• The type is string.

Slow SQL Statments Row Number

• Row Number. This is available for thresholds, but not in the UI.
• The type is int.

Slow SQL Stmt Start Timestamp

• The start time of the SQL statement.
• The type is timestamp.

Component: table

The Table data set provides information to monitor table-specific attributes, such as row read and row write rates. The following section lists the metrics and dimensions of Component table.

Metrics

The following metrics are available for the component.

Table Data Object Size

• The disk space, in kilobytes, that is logically and physically allocated for the table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is kilobytes.

Table Index Object Size

• The disk space, in kilobytes, that is logically and physically allocated for the indexes defined on the table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is kilobytes.

Table LOB Object

• The disk space, in kilobytes, that is logically and physically allocated for large objects in a table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is kilobytes.

Table Rows Read Rate for Interval

• The rate (per second) at which rows were read from the table during the monitoring interval.
• The type is double.
• The unit is rows/second.

Table Rows Write Rate for Interval

• The rate (per second) at which rows were changed (inserted, deleted, or updated) in the table during the monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is rows/second.

Table XML Object

• The disk space, in kilobytes, that is logically and physically allocated for the XML data in a table.
• The type is int.
• The unit is kilobytes.

Dimensions

The following dimensions are available for the component.

Table DB Name

• The database name. Data collection performance can be improved with the use of an eventing threshold or a filter in the Attribute Details tab that uses this attribute. When you specify a filter that has a distinct database name or list of database names, the agent data collector filters the return data before the data is transmitted to the Performance Management console.
• The type is string.

Table DB Name U

• The database name. Data collection performance can be improved with the use of an eventing threshold or a filter in the Attribute Details tab that uses this attribute. When you specify a filter that has a distinct database name or list of database names, the agent data collector filters the return data before the data is transmitted to the Performance Management console.
• The type is string.

Table DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. When specifying a filter with a distinct database partition value or list of values, the monitoring agent returns data for the requested partitions. If you do not specify a db partition filter value or if you specify a db partition filter value that is not valid, the return data is for the current partition. If a db partition filter is set to Aggregated , only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data.
• The type is string.

Table Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Table Name

• The name of the table for which the information is collected. The value format is a text string with a maximum of 60 bytes. Data collection performance can be improved with the use of an eventing threshold or a filter in the Attribute Details tab that uses this attribute. When you specify a filter that has a distinct database name or list of database names, the agent data collector filters the return data before the data is transmitted to the Performance Management console.
• The type is string.

Table Node Name

• The format is instanceid:hostname:UD for all operating systems.
• The type is string.

Table Reorg Needed

• Indicates whether the table, its indexes, or both need to be reorganized, and is calculated using DB2 monitoring data that is generated when the DB2 RUNSTATS utility is run. The RUNSTATS utility collects statistics on tables and indexes, and can affect system performance as it is collecting the statistics. For this reason, RUNSTATS is not automatically run. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Table Schema

• The schema of the table for which the information is collected. The value format is a text string with a maximum of 60 bytes.
• The type is string.

Table Snapshot Timestamp

• The date and time when the database system monitor information was collected. Use this attribute to help relate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Table Tablespace

• The name of the primary tablespace for the table. If no other tablespace is specified, all parts of the table are stored in this table space.
• The type is string.

Component: tableSpace

The Tablespace attributes provide information to monitor page size and usage characteristics for a tablespace. The following section lists the metrics and dimensions of Component tableSpace.

Metrics

The following metrics are available for the component.

Tablespace Auto Resize Current Size

• Represents the current tablespace size in bytes associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Auto Resize Free Pages

• The total number of free pages that are associated with the database.
• The type is int.
• The unit is pages.

Tablespace Auto Resize Increase Size

• Represents the size in bytes of the increase of the tablespace associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Auto Resize Increase Size Pct

• Represents the size as a percentage to which an auto-resize tablespace increases before reaching its maximum size and more space is required. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Auto Resize Initial Size

• Represents the initial tablespace size in bytes associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Auto Resize Max Size

• Represents the maximum tablespace size in bytes associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Auto Resize Page Size

• Page size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Auto Resize Prefetch Size

• The maximum number of pages that the prefetcher can get from the disk.
• The type is int.
• The unit is pages.

Tablespace Auto Resize Total Pages

• The total number of available pages that are associated with the database.
• The type is int.
• The unit is pages.

Tablespace Auto Resize Usable Pages

• The total number of usable pages that are associated with the database.
• The type is int.
• The unit is pages.

Tablespace Auto Resize Used Pages

• The total number of used pages.
• The type is int.
• The unit is pages.

Tablespace Auto Resize Used/Disk Pct

• Represents the percentage of used tablespace size for the disk size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Auto Resize Used/Max Pct

• Represents the percentage of the maximum size that has been used. :.
• The type is double.
• The unit is percent.

Tablespace Auto Resize Used/Total Pct

• Represents the percentage of the allocated size that has been used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Auto Resize Utilization Pct

• The percentage of used pages for a tablespace.
• The type is double.
• The unit is percent.

Tablespace Avg Direct Read Time

• The time (in milliseconds) for performing the direct reads for the tablespace. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Direct Write Time

• The time (in milliseconds) for performing the direct writes for the tablespace. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Pool I/O Time

• The average time (in milliseconds) for performing buffer pool input and output operations (reading or writing) for the tablespace. A high average time can indicate the existence of an input and output conflict. In this case, you might need to move data to a different device. The returned value includes the time applied to asynchronous input and output operations (which are performed by prefetchers and page cleaners). The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Pool Read Time

• The average time (in milliseconds) for processing read requests that caused data or index pages to be physically read from disk to buffer pool for the tablespace. A high average time generally indicates the existence of an input and output conflict. In this case, you might need to move data to a different device. The returned value includes the time applied to asynchronous read operations that are performed by prefetchers. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Pool Write Time

• The average time (in milliseconds) for processing write requests that caused data or index pages to be physically written from buffer pool to disk for the tablespace. A high average time generally indicates the existence of an input and output conflict. In this case, you might need to move data to a different device. The returned value includes the time applied to asynchronous write operations that are performed by page cleaners. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Sector Written

• The average number of sectors that are written for this tablespace for each direct read. Direct writes do not use the buffer pool, and so result in poor performance because the data is physically written from disk each time. If you are using system monitors to track input and output for the device, this returned value helps you distinguish database input and output from non-database input and output. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sectors.

Tablespace Avg Sectors Read

• The average number of sectors that are read for this tablespace for each direct read. Direct reads do not use the buffer pool, and so result in poor performance because the data is physically read from disk each time. If you are using system monitors to track input and output for the device, this returned value helps you distinguish database input and output from non-database input and output. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sectors.

Tablespace Avg Sync Data Read Time

• The average time (in milliseconds) for synchronous data reads for the tablespace. Use the returned value to analyze the input and output work being performed for the tablespace. Synchronous read operations are performed by database manager agents. Asynchronous reads are performed by prefetchers, which read data pages from disk into the buffer pool in anticipation of their use. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Sync Data Write Time

• The average time (in milliseconds) for synchronous data writes for the tablespace. Use the returned value to analyze the input and output work being performed for the tablespace. Synchronous write operations are performed by database manager agents. Asynchronous writes are performed by page cleaners, which write out changed pages to disk and free up space in the buffer pool. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Avg Sync I/O Time

• The average time (in milliseconds) for synchronous input and output operations for the tablespace. Use the returned value to analyze the input and output work being performed for the tablespace. Synchronous input and output operations are performed by database manager agents. Asynchronous input and output operations are performed by prefetchers (reads) and page cleaners (writes). In general, asynchronous input and output helps your applications run faster. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Direct Read Reqs

• The number of requests to perform a direct read from disk of one or more sectors of data for the database. The returned value is used in calculating the returned value for the average number of sectors read per direct read for the tablespace. Direct reads are performed in units, the smallest being a 512-byte sector. They are used while the system is doing any of the following operations: reading LONG VARCHAR columns, reading LOB columns, or performing a backup. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Direct Read Time

• The time (in milliseconds) for performing the direct reads for the tablespace since the first connection. The returned value is used in calculations for the average direct read time (ms). A high average time can indicate an input and output conflict. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Direct Reads

• The number of requests to perform a direct read from disk of one or more sectors of data for the tablespace since the first connection. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Direct Write Reqs

• The number of requests to perform a direct write to disk of one or more sectors of data for the database. The returned value is used in calculating the returned value for the average number of sectors written per direct write. Direct writes are performed in units, the smallest being a 512-byte sector. They are used while the system is doing any of the following operations: writing LONG VARCHAR columns, writing LOB columns, performing a restore, or performing a load. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Direct Write Time

• The time (in milliseconds) for performing the direct writes for the tablespace since the first connection. The returned value is used in calculations for the average direct write time (ms). A high average time can indicate an input and output conflict. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Direct Writes

• The number of direct writes to disk for the tablespace since the first connection. The returned value is used in calculating the returned value for the average number of sectors written per direct write. Direct writes are performed in units, the smallest being a 512-byte sector. They are used while the system is doing any of the following operations: writing LONG VARCHAR columns, writing LOB columns, performing a restore, or performing a load. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Estore Read/Write Ratio

• The ratio (as a percentage) of pages (data plus index) copied from extended storage to pages copied to extended storage within the tablespace. When a page is transferred from extended storage to the buffer pool, you save a system input and output call. However, you still incur the cost of attaching to the extended memory segment, copying the page, and detaching from the segment. Use the returned value to determine if you would benefit from using extended storage. The higher the ratio, the more likely you are to benefit. In general, extended storage is particularly useful if input and output activity is very high on your system. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Files Closed

• The total number of closed files for the tablespace since the first database connection. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is files.

Tablespace Free Pages

• The number of free pages that are associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pending Free Pages

• Represents the number of pending free pages associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Async Data Read Reqs

• The number of asynchronous data read requests. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Async Data Reads

• The number of data pages read asynchronously into the buffer pool for the tablespace. Compare the returned value with number of synchronous reads to gain insight into how well the prefetchers are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Async Data Writes

• The number of times a buffer pool data page was physically written asynchronously to disk for the tablespace. Compare the returned value with the number of synchronous writes to gain insight into how well the page cleaners are working. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Pool Async Index Reads

• The number of index pages read asynchronously into the buffer pool by a prefetcher within the tablespace. By comparing the ratio of asynchronous to synchronous reads, you can determine how well the prefetchers are working. Asynchronous reads are performed by database manager prefetchers. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Async Index Writes

• The number of times a buffer pool index page was written asynchronously to disk for the tablespace. Subtract the returned value from the buffer pool index writes to calculate the number of synchronous index writes. By comparing the number of asynchronous index writes to synchronous index writes, you can gain insight into how well the buffer pool page cleaners are performing. This ratio can be helpful when you are refining the num_iocleaners configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Pool Async Read Time

• The total time (in milliseconds) that database manager prefetchers spent reading data into the buffer pool for the tablespace. Compare the returned value to the synchronous read time to understand where input and output time is being spent. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Pool Async Write Time

• The total time (in milliseconds) that database manager page cleaners spent writing data or index pages from the buffer pool to disk for the tablespace. Compare the returned value to the synchronous write time to understand where input and output time is being spent. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Pool Aysnc Index Read Reqs

• The number of asynchronous index read requests. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Data from Estore

• The number of buffer pool data pages copied from extended storage within the tablespace to the buffer pool. Required pages are copied from extended storage to the buffer pool if they are not in the buffer pool but are in extended storage. This copying can incur the cost of connecting to the shared memory segment but saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Data L Reads

• The number of logical read requests for data pages that went through the buffer pool for the tablespace since the connection occurred. The returned value includes requests for data that is already in the buffer pool or read from disk into the buffer pool to fulfill the request. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Data P Reads

• The number of read requests requiring input and output to get data pages into the buffer pool for the tablespace since the first connection. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Data Reads

• The number of read requests to get data pages into the buffer pool for the tablespace.:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Data to Estore

• The number of buffer pool data pages copied to extended storage for the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Data Writes

• The number of times that a buffer pool data page was physically written to disk for the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Pool Hit Percent

• The percent buffer pool hit ratio (data plus index). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Pool Hit Ratio for Interval

• The overall buffer pool hit ratio (as a percentage) for the database during the monitoring interval. This hit ratio includes both index and data page activity. The overall buffer pool hit ratio indicates the percentage of page requests for which the database manager did not need to load a page from disk to service. (That is, the page was already in the buffer pool. ) The greater the buffer pool hit ratio, the lower the frequency of disk input and output. If the hit ratio is low compared to normal operating levels, increasing the number of buffer pool pages can improve performance. A ratio of zero indicates that pages needed to be read for every request. For a large database, increasing the buffer pool size can have a minimal effect on the buffer pool hit ratio. Such a database can have so large a number of data pages that the statistical chance of a hit is not increased by an increase of the buffer pools. However, even though the data might be too large to fit in the buffer pool, the entire index can fit. In this case, you can refine buffer pool sizes until the overall buffer pool hit ratio stops increasing, and then refine the buffer pool until the buffer pool index hit ratio no longer increases. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Pool I/O per Sec

• The rate (per second) for buffer pool input and output for the tablespace. Buffer pool input and output includes all physical data and index pages that go through the buffer pool when read or written. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is poolIO/second.

Tablespace Pool Index from Estore

• The number of buffer pool index pages copied from extended storage for the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Index Hit Percent for Interval

• The percent buffer pool index hit ratio for the monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Pool Index L Reads

• The number of logical read requests for index pages that went through the buffer pool for the tablespace since the connection. The returned value includes requests for index pages that are already in the buffer pool or read from disk into the buffer pool to fulfill the request. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool for the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Pool Index to Estore

• The number of buffer pool index pages copied to extended storage within the tablespace. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. This copying is required to make space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Pool Index Writes

• The number of times that a buffer pool index page was physically written to disk for the tablespace since the first connection. If the returned value is high compared to the buffer pool index physical reads, you can improve performance by increasing the available buffer pool space. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Pool Read Time

• The time (in milliseconds) spent reading data from the buffer pool to disk for the tablespace since the first connection. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Pool Sync Index Reads

• The number of buffer pool synchronous index reads. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Tablespace Pool Sync Index Writes

• The number of buffer pool synchronous index writes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Pool Write Time

• The time (in milliseconds) spent writing data from the buffer pool to disk for the tablespace since the first connection. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Prefetch Percent for Interval

• The percentage of asynchronous read requests that were satisfied for a tablespace during the last monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Prefetch Reqs for Interval

• The number of prefetch requests for the tablespace during the monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Tablespace Prefetch Size

• Indicates the prefetch size. A valid value is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Tablespace Space Used DMS Table Percent

• The percentage of space used in the Database Managed Space (DMS) tablespace. Use the returned value to determine if the tablespace needs more space. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Space Used SMS Table

• The number of bytes allocated to the System Managed Space (SMS) tablespace. Use the returned value to determine whether the number of bytes used by the SMS tablespace is excessive in relation to the file system on which the tablespace is established. Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Tablespace Sync Read Time

• The time (in milliseconds) applied to synchronous reads for the tablespace. Compare the returned value to the buffer pool async read time to understand where input and output time for this tablespace is used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Sync Write Time

• The time (in milliseconds) spent synchronously writing data to disk from the buffer pool for the tablespace. Compare the returned value to the value returned by the buffer pool async write time to understand where input and output time for this tablespace is used. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Table Space Pool Sync Data Reads

• The number of buffer pool synchronous reads. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Tablespace Table Space Pool Sync Data Writes

• The number of buffer pool synchronous writes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Tablespace Total Direct I/O Time

• The total time (in milliseconds) for direct reads to and writes from the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Total I/O Percent

• The percentage total of I/O. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Tablespace Total Pool I/O Time

• The total pool I/O time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Total Pool P Read Time

• The time (in milliseconds) spent reading data and index pages from the buffer pool to the disk for the tablespace since the first connection. The value format is an integer. This attribute is the same as the pool read time attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Total Pool P Write Time

• The total pool physical write time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Total Sync I/O

• The total number of synchronous reads and writes for both data and index pages for the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is readsWrites.

Tablespace Total Sync I/O Time

• The total time (in milliseconds) for processing requests for synchronous reads or writes within the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Tablespace Used Pages

• The total number of used pages. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Dimensions

The following dimensions are available for the component.

Tablespace Auto Resize DB Name

• The name of the monitored database.
• The type is string.

Tablespace Auto Resize DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range,.
• The type is string.

Tablespace Auto Resize Enabled

• Indicates whether automatic resizing is enabled for the tablespace.
• The type is int.

Tablespace Auto Resize Host Name

• The hostname of the machine where the DB2 database is hosted. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Auto Resize Instance Name

• The name of the monitored DB2 instance (Unicode).
• The type is string.

Tablespace Auto Resize Last Resize Failed

• Indicates whether the last resize attempted succeeded. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Auto Resize Last Resize Time

• Represents the time at which the last tablespace resize was successfully executed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Auto Resize Node Name

• The node name of the database.
• The type is string.

Tablespace Auto Resize Rebalance Mode

• Represents whether a forward or reverse rebalance is taking place. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Auto Resize TBSP ID

• The identifier for the tablespace.
• The type is int.

Tablespace Auto Resize TBSP Name

• The name of the tablespace. The value format is a simple text string with a maximum of 96 characters.
• The type is string.

Tablespace Auto Resize Time Stamp

• The local time at the agent when the data was collected. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Tablespace Auto Resize Type

• Tablespace Type of DB2 The automatic storage status of a tablespace.
• The type is string.

Tablespace Auto Resize Using Auto Storage

• The status of automatic storage for a tablespace in a database.
• The type is int.

Tablespace Auto Storage state

• The status of automatic storage for a tablespace in a database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Container Name

• Indicates the location of the container. Value format is a simple text string with a maximum of 768 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Content Type

• The type of content in a tablespace, such as permanent data, system temporary data, and user temporary data. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace DB Name

• Represents the real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. Value format is a simple text string with a maximum of 96 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. When specifying a filter with a distinct database partition value or list of values, the monitoring agent returns data for the requested partitions. If you do not specify a db partition filter value or if you specify a db partition filter value that is not valid, the return data is for the current partition. If a db partition filter is set to Aggregated , only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Extent Size

• Indicates the extent size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace ID

• Represents the identifier for the tablespace. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Instance Name

• The name of the monitored DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Name

• The tablespace name of DB2. The Value format is a simple text string with a maximum of 96 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Node Name

• The format is instanceid:hostname:UD for all operating systems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Num Containers

• Indicates the number of containers used. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Object ID

• Represents the identifier for the object. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Page Size

• Indicates the page size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Status

• The status of the tablespace. DB2 sets this value, which corresponds to the DB2 tablespace_state element in the DB2 tablespace_nodeinfo Snapshot logical data group. This element contains a hexadecimal value that indicates the current tablespace state. The externally visible state of a tablespace is composed of the hexadecimal sum of certain state values. For example, if the state is quiesced: EXCLUSIVE and Load pending , the value is 0x0004 + 0x0008, which is 0x000c. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Status Name

• The comma-delimited tablespace state name that corresponds to the tablespace status (TBSP STATUS) attribute. The following table shows the text that is used, depending upon the bit setting of tbsp status:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Total Pages

• The total number of available pages that are associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Type

• Represents the tablespace type of DB2. Value format is a simple text string with a maximum of 32 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Tablespace Usable Pages

• Represents the number of usable pages associated with the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Tablespace Version

• Indicates the version number of DB2. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Resource db2Instance

Shows performance data and overall status of the DB2 Server Instances. The following section lists the metrics, dimensions and components of Resource db2Instance.

Metrics

The following metrics are available for the resource.

Agents Created Empty Pool

• The number of agents created because the agent pool was empty. It includes the number of agents started at DB2 start up. By using the Agents Assigned From Pool attribute, you can calculate the ratio of the Agents Created Empty Pool attribute to the Agents From Pool attribute. See the Agents From Pool attribute for information about using this attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Agents Created Empty Pool Ratio

• The percentage of agents that are created because the pool is empty. This ratio is calculated by dividing the value of the Agents Created Empty Pool attribute by the value of the Agents From Pool attribute. Use this attribute to evaluate how often an agent must be created because the pool is empty. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Agents from Pool

• The number of agents assigned from the pool. Use this attribute with Agents Created Empty Pool attribute to determine how often an agent must be created because the pool is empty. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Agents Registered

• The number of agents that the database manager registered. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Agents Registered Top

• The maximum number of agents that the database manager has ever registered, at the same time, since it was started (coordinator agents and subagents). Use this attribute to evaluate the setting of the MAXAGENTS configuration parameter. The number of agents registered at the time the snapshot was taken is recorded by the Agents Registered attribute. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Agents Stolen

• The number of times that agents are stolen from an application. Agents are stolen when an idle agent associated with an application is reassigned to work on a different application. Use this attribute with the Maximum Number of Associated Agents attribute to evaluate the load that this application places on the system. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Agents Waiting on Token

• The number of agents waiting for a token so they can run a transaction in the database manager. Use this attribute to evaluate your setting for the MAXCAGENTS configuration parameter. Each application has a dedicated coordinator agent to process database requests (transactions) within the database manager. Each agent must have a token to run a transaction. The maximum number of coordinator agents is limited by the MAXCAGENTS configuration parameter. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Agents Waiting on Token Pct

• The percentage of agents waiting on a token. The percentage is calculated by dividing the value of the Agents Waiting on Token attribute by the number of local applications that are currently connected to a database (Local Cons attribute). Use this attribute to assess the number of agents. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Agents Waiting Top

• The highest number of agents waiting on a token, at the same time, since the database manager was started. Use this attribute to evaluate the setting of the MAXCAGENTS configuration parameter. In contrast, the Agents Waiting on Token attribute records the number of agents waiting for a token at the time the snapshot was taken. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Appl Support Layer Heap Size

• The current value (in units of 4-KB pages) of the application support layer heap size. This value is the amount of memory that is allocated for the application support layer heap. This heap is used as a communication buffer between the local application and its associated agent. In addition, this value is used to determine the input and output block size when a blocking cursor is opened. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Buff Free

• The number of Fast Communication Manager (FCM) buffers that are free in the partitioned database server during the monitoring interval. Use the returned value to determine the current buffer pool utilization. Use this information to refine the configuration of the number of FCM buffers. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is buffers.

Buff Free Bottom

• The minimum number of free connection entries. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Buff Max Used Percent

• The percentage of maximum FCM buffers used during processing within the partitioned database server. If the percentage of maximum FCM buffers used is high compared to normal operating levels, you can increase the number of FCM buffers; if the percentage is low compared to normal operating levels, you can decrease the value. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Buff Used Percent

• The percentage of FCM buffers that are used within the partitioned database server during the monitoring interval. If the percentage of FCM buffers used is high compared to normal operating levels, you can adjust the number of FCM buffers.
• The type is double.
• The unit is percent.

CE Free

• The number of connection entries that are free in the partitioned database server during the monitoring interval. Use the returned value to help determine the current connection entry utilization. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

CE Free Bottom

• The minimum number of free connection entries. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

CE Max Used Percent

• The maximum percentage of FCM connection entries used during processing within the partitioned database server. If the percentage of maximum FCM connection entries used is high compared to normal operating levels, you can increase the number of FCM connections; if the percentage is low compared to normal operating levels, you can decrease the value. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

CE Used Percent

• The percentage of FCM connection entries used during processing within the partitioned database server. If the percentage of FCM connection entries used is high compared to normal operating levels, you can increase the number of FCM connections; if the percentage is low compared to normal operating levels, you can decrease the value.
• The type is double.
• The unit is percent.

Commited Private Memory

• The amount of private memory that the instance of the database manager currently has committed at the time of the snapshot. Use this attribute to assess the MIN_PRIV_MEM configuration parameter to ensure that enough private memory is available. This attribute is returned for all platforms, but tuning can be accomplished only on platforms where DB2 uses threads (such as OS/2 and Windows NT systems). Values that are greater than or equal to 9223372036854775807 are indicated with the Value Exceeds Maximum text in the portal. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is kilobytes.

Conn Local Database

• The number of local databases with current connections to the monitored DB2 instance. This value gives an indication of how many database information records to expect when gathering data at the database level. The applications can be running locally or remotely, and might or might not be executing a unit of work within the database manager. The following value is valid:.
• The type is int.
• The unit is databases.

Cons in Exec Percent

• The percentage of the maximum number of applications allowed that are connected to a database and processing a unit of work during the monitoring interval. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Coordinating Agents Top

• The maximum number of coordinating agents working at one time. The MAXCAGENTS configuration parameter determines the number of coordinating agents that can be executing concurrently. If the peak number of coordinating agents results in a workload that is too high for this node, you can reduce the MAXCAGENTS configuration parameter. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

CPU Used Pct

• The percentage of CPU that is used on the system by the DB2 instance. DB2 returns this value as SMALLINT.
• The type is int.
• The unit is percent.

DB2 Available

• The amount of time (in seconds) the instance has been available since a DB2START command was issued. The value format is an integer. The value is derived through this formula: snapshot time - db2start time The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

FCM Num Anchors

• The number of FCM message anchors for the DB2 instance during the monitoring interval. Agents use the message anchors to send messages among themselves. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is anchors.

FCM Num Buffers

• The number of buffers that are used for internal communications (messages) among the nodes and within the nodes in a DB2 instance during the monitoring interval. You might need to increase the value of this parameter if you have either of the following conditions: multiple logical nodes on a processor, or too many users, nodes, or complex applications that exceed the buffer limit. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is buffers.

FCM Num Connect

• The number of FCM connection entries for the DB2 instance during the monitoring interval. Agents use connection entries to pass data among themselves. Use the results from the fcm_num_rqb attribute to help you refine the fcm_num_connect attribute. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

FCM Num Rqb

• The number of FCM request blocks for the DB2 instance during the monitoring interval. Request blocks are the media through which information is passed between the FCM daemon and an agent. The requirement for request blocks varies according to the number of users on the system, the number of database partition servers in the system, and the complexity of queries that are run. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requestBlocks.

Gateway Cons Wait Client

• For host databases being handled by the DB2 Connect gateway, the current number of connections that are waiting for the client to send a request. Because this value can change frequently, take samples at regular intervals over an extended period to obtain a realistic view of gateway usage. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Gateway Cons Wait Host

• For host databases being handled by the DB2 Connect gateway, the current number of connections that are waiting for a reply from the host. Because this value can change frequently, take samples at regular intervals over an extended period to obtain a realistic view of gateway usage. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Gateway Current Connections

• The current number of connections to host databases being handled by the DB2 Connect gateway. Use this attribute to help you understand the level of activity at the DB2 Connect gateway and the associated use of system resources. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Gateway Total Connections

• The total number of connections attempted from the DB2 Connect gateway since the last db2start command or the last reset. Use this attribute to help you understand the level of activity at the DB2 Connect gateway and the associated use of system resources. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Idle Agents

• The number of agents in the agent pool that are currently unassigned to an application. Use this attribute to set the NUM_POOLAGENTS configuration parameter. By having idle agents available to satisfy requests for agents, you can improve performance. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is agents.

Local Connection Executing

• The number of local applications that are currently connected to a database within the database manager instance being monitored and are currently processing a unit of work. By using this number, you can determine the level of concurrent processing occurring in the database manager. This value changes frequently. As a result, you must sample the data at specific intervals over an extended period of time to get a realistic view of system usage. This number includes only applications that were initiated from the same instance as the database manager. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is applications.

Local Connections

• The number of local applications that are currently connected to a database within the database manager instance being monitored. By using this number, you can determine the level of concurrent processing occurring in the database manager. This value changes frequently. As a result, you must sample the data at specific intervals over an extended period of time to get a realistic view of system usage. This number includes only applications that were initiated from the same instance as the database manager. The applications are connected, but might or might not be executing a unit of work in the database. The following value is valid:.
• The type is int.
• The unit is connections.

MA Free Bottom

• The minimum number of free message anchors. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is anchors.

MA Max Used Percent

• The maximum number of message anchors used as a percentage. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Max Agent Overflows

• The number of attempts to create a new agent when the MAXAGENTS configuration parameter had already been reached. If requests to create new agents are received after reaching the MAXAGENTS configuration parameter, the workload for this node might be too high. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is attempts.

Piped Sort Hit Ratio Percent for Interval

• The piped sort hit ratio (as a percentage) for the last monitoring interval. The piped sort hit ratio is the ratio of piped sorts accepted to piped sorts requested.
• The type is double.
• The unit is percent.

Piped Sorts Accepted

• The number of piped sorts that have been accepted. When the number of accepted piped sorts is low compared to the number requested, you can improve sort performance by adjusting one or both of the following configuration parameters:
  • SORTHEAP
  • SHEAPTHRES
  If piped sorts are being rejected, consider decreasing your sort heap or increasing your sort heap threshold. Be aware of the possible implications of these options:
  • If you increase the sort heap threshold, more memory might remain allocated for sorting. This can cause the paging of memory to disk.
  • If you decrease the sort heap, an extra merge phase (which can slow down the sort) might be required.
  The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Piped Sorts Accepted Percent

• The percentage of piped sorts that have been accepted. The percentage is calculated by dividing the value of the Piped Sorts Accepted attribute by the value of the Piped Sorts Requested attribute. Use this attribute to determine whether the value of the Piped Sorts Accepted attribute is in an acceptable range. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Piped Sorts Rejected for Interval

• The total number of piped sorts that were rejected during the monitoring interval. In the return phase of sorting, if the sorted information can return directly through the sort heap, it is a piped sort. However, even if the optimizer requests a piped sort, this request is rejected at run time if the total amount of sort heap memory for all sorts on the database is close to exceeding the sheapthres value. If this returned value is high compared to the total number of sorts requested, consider decreasing your sort heap (using the sortheap configuration parameter) or increasing your sort heap threshold (using the sheapthres configuration parameter). However, be aware of the implications of these options. If you increase the sort heap threshold, more memory can remain allocated for sorting, causing the paging of memory to disk. If you decrease the sort heap, you can require an extra merge phase that can slow down the sort. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Piped Sorts Rejected Percent for Interval

• The percentage of piped sort requests that were rejected for the DB2 instance during the monitoring interval. In the sort return phase, if the sorted information can return directly through the sort heap, it is a piped sort. However, even if the optimizer requests a piped sort, this request is rejected at run time if the total amount of sort heap memory for all sorts on the database is close to exceeding the sheapthres value. If this returned value is high compared to normal operating levels, consider decreasing your sort heap (using the sortheap configuration parameter) or increasing your sort heap threshold (using the sheapthres configuration parameter). However, be aware of the implications of these options. If you increase the sort heap threshold, more memory can remain allocated for sorting, causing the paging of memory to disk. If you decrease the sort heap, you can require an extra merge phase that can slow down the sort. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Piped Sorts Requested

• The number of piped sorts that have been requested. Because piped sorts might reduce disk I/O, allowing more piped sorts can improve the performance of sort operations and possibly the performance of the overall system. A piped sort is not accepted if the sort heap threshold is exceeded by allocating the requested sort heap. See the Piped Sorts Accepted attribute for more information if piped sorts are being rejected. The SQL EXPLAIN output shows whether the optimizer requested a piped sort. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Post Threshold Hash Joins

• The total number of times that a hash join heap request was limited due to the concurrent use of shared or private sort heap space. If this value is large (for example, greater than 5% of Hash Join Overflows), you must consider increasing the sort heap threshold. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Post Threshold OLAP Funcs

• The number of OLAP functions that have requested a sort heap after the sort heap threshold has been exceeded. If the value of this attribute is high, increase the sort heap threshold (sheapthres). The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is functions.

Post Threshold Sorts

• The number of sorts that have requested heaps after reaching the sort heap threshold. By modifying the sort heap threshold and sort heap size configuration parameters, you can improve the performance of sort operations or the overall system. If the value of this attribute is high, you can do one of the following actions:
  • Increase the sort heap threshold (sheapthres).
  • Adjust applications to use fewer or smaller sorts by using SQL query changes.
  The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

RB Free

• The number of request blocks that are free in the partitioned database server during the monitoring interval. Use the returned value with the fcm_num_rqb attribute to determine the current request block utilization. You can use this information to refine the fcm_num_rqb attribute. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requestBlocks.

RB Free Bottom

• The minimum number of free request blocks. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requestBlocks.

RB Max Used Percent

• The percentage of maximum FCM request blocks used during processing within the partitioned database server. If the percentage of maximum FCM request blocks used is high compared to normal operating levels, you can adjust the fcm_num_rqb attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

RB Used Percent

• The percentage of FCM request blocks used within the partitioned database server during the monitoring interval. If the percentage of FCM request blocks used is high compared to normal operating levels, you can adjust the fcm_num_rqb attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Remote Connections

• The current number of connections initiated from remote clients to the instance of the database manager that is being monitored. This attribute shows the number of connections from remote clients to databases in this instance. This value changes frequently. As a result, you must sample the data at specific intervals over an extended period of time to get a realistic view of system usage. This number does not include applications that were initiated from the same instance as the database manager. The following value is valid:.
• The type is int.
• The unit is connections.

Remote Connections Executing

• The number of remote applications currently connected to a database and currently processing a unit of work within the database manager instance being monitored. By using this number, you can determine the level of concurrent processing occurring on the database manager. This value changes frequently. As a result, you must sample the data at specific intervals over an extended period of time to get a realistic view of system usage. This number does not include applications that were initiated from the same instance as the database manager. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is connections.

Sort Heap Allocated

• The total number of pages that are used for sorts at the selected level (database manager or database) when the snapshot was taken. Add the extra memory used for the sort heap to the base memory requirements for running the database manager when excessive sorting occurs. The large heap size and indexes can improve the sorting performance. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Sort Heap Used Percent

• The percentage of the allocated sort heap that the DB2 instance used during the monitoring interval.
• The type is double.
• The unit is percent.

Total Buffers Rcvd

• The total number of FCM buffers received by the database node where this monitor runs. The database node is specified in the DB2_node_number variable. Use the returned value to measure the level of traffic between the node where this monitor runs and another node. If the total number of FCM buffers received from the other node is high compared to normal operating levels, you can redistribute the database or move tables to reduce the internode traffic. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is buffers.

Total Buffers Sent

• The total number of FCM buffers that are sent from the database node where this monitor runs to the specified node. Use the returned value to measure the level of traffic between the current node where this monitor runs and the specified node. If the total number of FCM buffers sent to the other node is high compared to normal operating levels, you can redistribute the database or move tables to reduce the internode traffic. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is buffers.

Total Memory Allocated

• The total memory allocated to the DB2 instance.
• The type is int.
• The unit is MB.

Total Memory Used

• The total database memory used by instance.
• The type is int.
• The unit is MB.

Dimensions

The following dimensions are available for the resource.

Connection Status

• The status of the communication connection between the database partition that is specified by the DB2 Node Number variable and the database partition where this monitor runs. Two nodes can be active, but the connection between them remains inactive unless there is active communication between them. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If you do not specify a db partition filter, data is returned for either the current database partition (single partition environment) or the aggregated database partitions (multiple partition environment). If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range, the following values are also valid:.
• The type is string.

DB2 Instance Status

• The current status of the DB2 instance. Use this attribute to determine the state of your database manager instance.
• The type is string.

DB2 Server Type

• The type of database manager being monitored.
• The type is string.

DB2 Start Timestamp

• The date and time that the database manager was started using the DB2START command. Use this attribute with the snapshot time attribute to calculate the elapsed time from the start of the database manager until the snapshot was taken. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

DB2 Version

• The version of the server that is returning the data. For example: 6. 1 or 7. 1. The data structures used by the monitor might change between releases. As a result, check the version of the data stream to determine whether your applications can process the data.
• The type is string.

DBPG Node Status

• The list of failing local nodes. This is a list of integers, where each integer represents the failed local nodes. Depending on the actual partitions defined in the database partition group, it is not necessarily true that all the nodes defined in the parallel environment are examined. To ensure that all the nodes in the partitioned environment are examined, define a partition group that contains at least one database partition from each of the nodes in the partitioned environment. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Fully Qualified Domain Name

• Fully qualified hostname of the server being monitored.
• The type is string.

Instance Hostname

• The format is instanceid:hostname for all operating systems.
• The type is string.

Instance Name

• The name of the monitored DB2 instance.
• The type is string.

Last Reset Timestamp

• The date and time that the monitor counters were reset for the application requesting the snapshot. Use this attribute to help you determine the scope of information returned by the database system monitor. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Max Agents

• The current value of the maximum number of existing agents. This value is the maximum number of database manager agents available at any given time to accept application requests. This value limits the total number of applications that can connect to all databases in the DB2 instance at a given time. The value of the maxagents attribute must be the sum of the values of the maxappls attribute in each database that is allowed to be accessed concurrently. Increasing the value of the maxagents attribute can increase resource use because resources for each agent are allocated when the DB2 instance is started. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Max Conc Agents

• The maximum number of database manager coordinator agents that can concurrently run a database manager transaction in the DB2 instance during the monitoring interval. When this monitor is used with DB2 Universal database servers, the maxcagents value is the default. This value is the maximum number of database manager agents that can be concurrently executing a database manager transaction. Use the maxcagents attributes to control the load on the system during periods of high simultaneous application activity. A value of -1 indicates that the limit is equal to the maximum number of agents (the MAXAGENTS parameter). The maxcagents parameter does not limit the number of applications that can have connections to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Max Coord Agents

• The maximum number of database manager coordinating agents that can exist on a server in a partitioned or nonpartitioned database environment. One coordinating agent is acquired for each local or remote application that connects to a database or attaches to an instance. Requests that require an instance attachment include CREATE DATABASE, DROP DATABASE, and Database System Monitor commands. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Mon Heap Size

• The current value (in units of 4-KB pages) of the database system monitor heap size. This value is the amount of memory that is allocated for database system monitor data. A value of zero prevents the database manager from collecting database system monitor data. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Node Name

• The format is instanceid:hostname:UD for all operating systems.
• The type is string.

Priority of Agents

• The current value of the priority of agents. This value is the priority that the operating system scheduler gives to agent and other database manager instance processes and threads. This priority determines how the operating system gives CPU time to the DB2 processes and threads relative to the other processes and threads running on the system. A value of -1 indicates that no special action is taken and the operating system schedules the database manager in the normal way that it schedules all processes and threads. Any other value indicates that the database manager creates its processes and threads with a static priority set to this value. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Product Version

• The product and version that is running on the DB2 instance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Query Heap Size

• The maximum amount of memory that can be allocated for the query heap within the DB2 instance during the monitoring interval. Use a query heap to store each query in the private memory of the agent. Use the results from the aslheapsz attribute to refine the query heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Req IO Blk

• The current value (in byte units) of the client input and output block size. This value is the amount of memory that is allocated for the communication buffer between remote applications and their database agents on the database server. When a database client requests a connection to a remote database, this communication buffer is allocated on the client. On the database server, a communication buffer of 32767 bytes is initially allocated, until a connection is established and the server can determine the value of the rqrioblk attribute at the client. In addition to this communication buffer, this parameter is also used to determine the input and output block size at the database client when a blocking cursor is opened. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Snapshot Timestamp

• The date and time when the database system monitored information was collected. Use this attribute to help correlate data chronologically if you are saving the results in a file or database for ongoing analysis. This is available for thresholds, but not in the UI.
• The type is timestamp.

Sort Heap Thres

• The current value (in units of 4-KB pages) of the sort heap threshold. This value is the maximum amount of memory that the database manager allocates for piped sorts. Piped sorts perform better than non-piped sorts and are used more often. However, their use can affect the performance. The value of the sheapthres attribute must be at least two times the largest sort heap that is defined for any database within the instance. The following value is valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Component: applicationActivities

Information about application activities. The following section lists the metrics and dimensions of Component applicationActivities.

Metrics

The following metrics are available for the component.

Application Acc Curs Blk

• The number of times that a request for an I/O block was accepted. The value format is an integer. Use this attribute with the Rejected Block Cursor Requests attribute to calculate the percentage of blocking requests that are accepted or rejected. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is accepteds.

Application Appl Idle Time

• The number of seconds since an application issued a request to the server. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application application Static SQL Stmts

• The number of static SQL statements that were attempted. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Avg Lock Wait Time

• The average elapsed time (in milliseconds) that was spent waiting for a lock. The value format is an integer. If the average lock wait time is high, you must look for applications that hold many locks, or have lock escalations, with a focus on tuning your applications to improve concurrency, if appropriate. If escalations are the reason for a high average lock wait time, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Avg Pool Read Time

• The average elapsed time for a read request. The value format is an integer.
• The type is int.
• The unit is ?.

Application Avg Pool Write Time

• The average elapsed time for a write request. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Avg Sort Time

• The average time that was elapsed to complete a sort operation. At the database or application level, the value for this attribute can indicate the performance issues with sorting. This attribute value is affected by the system load. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is value.

Application Binds Precompiles

• The number of binds and precompiles attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is operations.

Application Cat Cache Heap Full

• The number of times that an insert into the catalog cache failed because of a heap full condition in the database heap. The value format is an integer. The catalog cache draws its storage dynamically from the database heap. Even if the cache storage has not reached its limit, inserts into the catalog cache might fail due to a lack of space in the database heap. If the catalog cache heap full count is not zero, you can correct the insert failure condition by increasing the database heap size or by reducing the catalog cache size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is failures.

Application Cat Cache Hit Ratio

• The percentage of catalog sections that are found in the cache. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Cat Cache Inserts

• The number of times that the system tried to insert table descriptor information into the catalog cache. The value format is an integer. Table descriptor information is inserted into the cache following a failed lookup to the catalog cache while processing a table, view, or alias reference in an SQL statement. The catalog cache inserts value includes attempts to insert table descriptor information that fail due to catalog cache overflow and heap full conditions. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Cat Cache Lookups

• The number of times that the catalog cache was referenced to obtain table descriptor information. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Cat Cache Overflows

• The number of times that an insert into the catalog cache failed because the catalog cache was full. The value format is an integer. If the catalog cache overflows value is large, the catalog cache might be too small for the workload. Increasing the size of the catalog cache might improve its performance. If the workload includes transactions that compile a large number of SQL statements referencing many tables, views, and aliases in a single unit of work, compiling fewer SQL statements in a single transaction might improve the performance of the catalog cache. Or if the workload includes the binding of packages containing many SQL statements referencing many tables, views or aliases, you might want to split the packages so that they include fewer SQL statements to improve performance.
• The type is int.
• The unit is overflows.

Application Commit SQL Stmts

• The total number of SQL COMMIT statements that have been attempted. The value format is an integer. A small rate of change in this counter during the monitor period might indicate that applications are not doing frequent commits. The lack of frequent commits can lead to problems with logging and data concurrency. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application DDL SQL Stmts

• The number of SQL Data Definition Language (DDL) statements that were issued. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Deadlocks

• The total number of deadlocks that have occurred. The value format is an integer. This attribute can indicate that applications are experiencing contention problems. To resolve the problem, determine in which applications (or application processes) the deadlocks are occurring. You can then modify the application to enable it to run concurrently. Some applications, however, might not be capable of running concurrently. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deadlocks.

Application Degree Parallelism

• The degree of parallelism requested when the query was bound. The value format is an integer. Use with the Agents Top attribute to determine if the query achieved maximum level of parallelism. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is degree.

Application Direct Read Reqs

• The number of requests to perform a direct read of one or more sectors of data. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Direct Read Time

• The elapsed time (in milliseconds) required to perform the direct reads. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Direct Reads

• The number of read operations that do not use the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Application Direct Write Reqs

• The number of requests to perform a direct write of one or more sectors of data. The value format is an integer.:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Direct Write Time

• The elapsed time (in milliseconds) required to perform the direct writes. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Direct Writes

• The number of write operations that do not use the buffer pool. The value format is an integer.:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Dynamic SQL Stmts

• The number of dynamic SQL statements that were attempted. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Failed SQL Stmts

• The number of SQL statements that were attempted, but failed. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Failed SQL Stmts Percent

• The percentage of SQL statements that failed to run successfully. The value format is an integer. This value is derived by dividing the value of the Failed SQL Statements attribute by the value of the Total SQL Statements attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Group Acc Curs Blk

• The number of times that a request for an I/O block was accepted. Use this attribute with the Rejected Block Cursor Requests attribute to calculate the percentage of blocking requests that are accepted or rejected. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is accepteds.

Application Group Agent Sys CPU Time

• The total system CPU time (in seconds) that the database manager agent process spent executing database manager code. This element includes CPU time for both SQL and non-SQL statements, and CPU time for any unfenced user-defined functions (UDFs). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.
• The unit is seconds.

Application Group Appl Idle Time

• The number of seconds since an application issued a request to the server. This amount includes applications that have not ended a transaction (for example, have not issued a commit or rollback). Use this information to force users who have been idle for a specified number of seconds. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application Group Avg Lock Waittime

• The average elapsed time (in milliseconds) that was spent waiting for a lock. If the average lock wait time is high, you must look for applications that hold many locks, or have lock escalations, to focus on tuning your applications to improve concurrency. If escalations cause a high average lock wait time, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group Avg Pool Read Time

• The average elapsed time for a read request. This value is derived by dividing the value of the Pool Read Time attribute by the value of the Pool Total Reads attribute. This average can indicate the presence of an I/O wait, which might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group Avg Pool Write Time

• The average elapsed time for a write request. This value is derived by dividing the value of the Pool Write Time attribute by the value of the Pool Total Writes attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group Avg Sort Time

• The average derived by dividing value of the Total Sort Time attribute by the value of the Total Sorts attribute. The average is expressed as elapsed time. at the database or application level, this attribute can indicate whether sorting is a performance issue. System load affects elapsed time. As you increase the running processes, this elapsed time value becomes higher. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group Binds Precompiles

• The number of attempted binds and precompiles. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group Cat Cache Heap Full

• The number of times that a heap full condition in the database heap caused an insert into the catalog cache to fail. The catalog cache draws its storage dynamically from the database heap. Even if the cache storage has not reached its limit, inserts into the catalog cache can fail if space is lacking in the database heap. If the catalog cache heap full count is not zero, you can correct the insert failure condition by increasing the database heap size or by reducing the catalog cache size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Application Group Cat Cache Hit Ratio

• The percentage of catalog sections found in the cache. This attribute indicates how well the catalog cache is avoiding catalog accesses. If the value is high (more than 0. 8), the cache is performing well. A smaller value might indicate that you must increase the size of the catalog cache. You must expect a large value immediately following the first connection to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group Cat Cache Inserts

• The number of times that the system tried to insert table descriptor information into the catalog cache. Table descriptor information is inserted into the cache following a failed lookup to the catalog cache while processing a table, view, or alias reference in an SQL statement. The catalog cache inserts value includes attempts to insert table descriptor information that fail if the catalog cache overflows and the heap is full. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Group Cat Cache Lookups

• The number of times that the catalog cache was referenced to obtain table descriptor information. This attribute includes both successful and unsuccessful accesses to the catalog cache. To calculate the catalog cache hit ratio use the following formula: (1 - (cat_cache_inserts / cat_cache_lookups)) This ratio indicates how well the catalog cache is avoiding catalog accesses. If the ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that you must increase the size of the catalog cache. You must expect a large ratio immediately following the first connection to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Group Cat Cache Overflows

• The number of times that an insert into the catalog cache failed because the catalog cache was full. If the catalog cache overflows value is large, the catalog cache might be too small for the workload. Increasing the size of the catalog cache might improve its performance. If the workload includes transactions that compile a large number of SQL statements referencing many tables, views, and aliases in a single unit of work, compiling fewer SQL statements in a single transaction might improve the performance of the catalog cache. Or if the workload includes the binding of packages containing many SQL statements referencing many tables, views or aliases, you might want to split the packages so that they include fewer SQL statements to improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is overflows.

Application Group Commit SQL Stmts

• The total number of SQL COMMIT statements that have been attempted. A small rate of change in this counter during the monitor period might indicate that applications are not doing frequent commits. The lack of frequent commits can lead to problems with logging and data concurrency. You can also use this attribute to calculate the total number of units of work by calculating the sum of the following values:
  • Commit statements attempted
  • Internal commits
  • Rollback statements attempted
  • Internal rollbacks
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application Group Database Manager Agent User CPU Time

• The total CPU time (in microseconds) that the database manager agent process used. This counter includes time spent on both SQL and non-SQL statements, and any fenced user-defined functions (UDFs) or stored procedures issued by the application. System CPU represents the time spent in system calls. User CPU represents time spent executing database manager code. The value format is a text string with a maximum of 10 characters. Use this attribute with the other CPU-time related attributes to help you identify applications or queries that consume large amounts of CPU time. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.
• The unit is microseconds.

Application Group DDL SQL Stmts

• The number of SQL Data Definition Language (DDL) statements that ran. Use this attribute to determine the level of database activity at the application or database level. DDL statements are expensive to run because of their impact on the system catalog tables. As a result, if the value of this attribute is high, you must determine the cause and possibly restrict the identified activity from being performed. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group Deadlocks

• The total number of deadlocks that have occurred. This attribute can indicate that applications are experiencing contention problems. To resolve the problem, determine in which applications (or application processes) the deadlock are occurring. You can then modify the application to enable it to run concurrently. Some applications, however, might not be capable of running concurrently. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deadlocks.

Application Group Degree Parallelism

• The degree of parallelism requested when the query was bound. Use with the Agents Top attribute to determine if the query achieved maximum level of parallelism. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is degree.

Application Group Direct Read Reqs

• The number of requests to perform a direct read of one or more sectors of data. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Direct Read Time

• The elapsed time (in milliseconds) required to perform the direct reads. Use the following formula to calculate the average direct read time per sector: direct read time / direct reads from database A high average time might indicate an I/O conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group Direct Reads

• The number of read operations that do not use the buffer pool. Use the following formula to calculate the average number of sectors that are read by a direct read: direct reads from database / direct read requests When using system monitors to track I/O, this data attribute helps to distinguish database I/O from non-database I/O on the device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Application Group Direct Write Reqs

• The number of requests to perform a direct write of one or more sectors of data. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Direct Write Time

• The elapsed time (in milliseconds) required to perform the direct writes. Use the following formula to calculate the average direct write time per sector: direct write time / direct writes to database A high average time might indicate an I/O conflict. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group Direct Writes

• The number of write operations that do not use the buffer pool. Use the following formula to calculate the average number of sectors that are written by a direct write: direct writes to database / direct write requests When using system monitors to track I/O, this data attribute helps to distinguish database I/O from non-database I/O on the device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Group Dynamic SQL Stmts

• The number of dynamic SQL statements that were attempted. Use this attribute to calculate the total number of successful SQL statements at the database or application level:
  1. Sum the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group Failed SQL Stmts

• The number of SQL statements that were attempted, but failed. This count includes all SQL statements that received a negative SQLCODE. Use this attribute to calculate the total number of successful SQL statements at the database or application level:
  1. Sum the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This attribute can also help you to determine the reasons for poor performance; failed statements indicate time wasted by the database manager, which results in lower throughput for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group Failed SQL Stmts Pct

• The percentage of SQL statements that failed to run. This value is derived by dividing the value of the Failed SQL Statements attribute by the value of the Total SQL Statements attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group Hash Join Overflows

• The number of times that hash join data exceeded the available sort heap space. At the database level, if the percentage of Hash Join Small Overflows is greater than 10% of this value, you must consider increasing the sort heap size. You can use values at the application level to evaluate hash join performance for individual applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group Hash Join Small Overflows

• The number of times that hash join data exceeded the available sort heap space by less than 10%. If this value and the value of the Hash Join Overflows attribute are high, you must consider increasing the sort heap threshold. If this value is greater than 10% of Hash Join Overflows, you must consider increasing the sort heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group Int Auto Rebinds

• The number of automatic rebinds (or recompiles) that have been attempted. Automatic rebinds are the internal binds the system performs when the validity of a package is removed. Use this attribute to determine the level of database activity at the application or database level. Because internal automatic rebinds can have a significant impact on performance, they must be minimized where possible. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rebinds.

Application Group Int Commits

• The total number of commits initiated internally by the database manager. An internal commit might occur during one of the following operations:
  • A reorganization
  • An import
  • A bind or pre-compile
  • An application that ends without executing an explicit SQL COMMIT statement (on UNIX and Linux systems).
  Use this attribute to calculate the total number of units of work by calculating the sum of the following values: commit statements attempted, internal commits, rollback statements attempted, and internal rollbacks. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application Group Int Deadlock rollbacks

• The total number of forced rollbacks initiated by the database manager due to a deadlock. The database manager initiates a rollback for the current unit of work in an application that is experiencing a deadlock. This attribute shows the number of deadlocks that were broken. It can indicate the possibility of concurrency problems. It is also important because internal rollbacks due to deadlocks can cause performance degradation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Group Int Rollbacks

• The total number of rollbacks initiated internally by the database manager. An internal rollback occurs when any of the following operations cannot be completed successfully:
  • A reorganization
  • An import
  • A bind or pre-compile
  • An application that ends as a result of a deadlock situation or lock timeout situation
  • An application that ends without executing an explicit COMMIT or ROLLBACK statement (on Windows systems).
  Use this attribute to calculate the total number of units of work by calculating the sum of the following values: commit statements attempted, internal commits, rollback statements attempted, and internal rollbacks. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Group Int Rows Deleted

• The number of rows deleted from the database as a result of internal activity. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints or triggers that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Int Rows Inserted

• The number of rows inserted into the database as a result of internal activity caused by triggers. This attribute can help to gain insight into the internal activity within the database manager. If this activity is high, you must evaluate the design to determine if you can alter it to reduce this activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Int Rows Updated

• The number of rows updated from the database as a result of internal activity. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Lock Escals

• The number of times that locks have been escalated from several row locks to a table lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application, or the lock list space consumed by all applications is approaching the total lock list space. This data item includes a count of all lock escalations, including exclusive lock escalations. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, the application uses space in the lock list that is allocated for other applications. When the entire lock list is full, an error occurs. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Application Group Lock Timeouts

• The number of times that a request to lock an object time out instead of being granted. This attribute can help you adjust the setting for the LOCKTIMEOUT database configuration parameter. If the number of lock timeouts becomes excessive when compared to normal operating levels, an application might be holding locks for long durations. In this case, this attribute might indicate that you must analyze some of the other attributes related to locks and deadlocks to determine if an application problem exists. You can have too few lock timeouts if the LOCKTIMEOUT database configuration parameter is set too high. In this case, applications might wait excessively to obtain a lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timeouts.

Application Group Lock Wait Time

• The total elapsed time (in milliseconds) that was spent waiting for a lock. At the database level, this is the total amount of elapsed time that all applications were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction has waited for a lock to be granted. This attribute might be used with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group Lock Waits

• The total number of times that applications or connections waited for locks. At the database level, the lock waits value is the total number of times that applications waited for locks within this database. At the application-connection level, the lock waits value is the total number of times that this connection requested a lock but waited because another connection was already holding a lock on the data. Use this attribute with the Lock Wait Time attribute to calculate, at the database level, the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. If the average lock wait time is high, look for applications that hold many locks, or have lock escalations, with a focus on tuning your applications to improve concurrency, if appropriate. If escalations are the reason for a high average lock wait time, the values of one or both of the LOCKLIST and MAXLOCKS configuration parameters might be too low. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is waits.

Application Group Locks Held

• The number of locks currently held. If the monitor information is at the database level, this number represents the total number of locks currently held by all applications in the database. If the information is at the application level, this number represents the total number of locks currently held by all agents for the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is locks.

Application Group Open Local Curs

• The number of local cursors currently open for this application, including those cursors counted by Open Local Cursors with Blocking attribute. Use this attribute with the Open Local Cursors with Blocking attribute to calculate the percentage of local cursors that are blocking cursors. If the percentage is low, you might be able to improve performance by improving the row blocking in the application. For cursors used by remote applications, see the Open Remote Cursors attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group Open Local Curs Blk

• The number of local blocking cursors currently open for this application. Use this attribute with the Open Local Cursors attribute to calculate the percentage of local cursors that are blocking cursors. Rejected Block Cursor Requests and Accepted Block Cursor Requests attributes provide additional information that might help you tune your configuration parameters to improve row blocking in your application. For blocking cursors used by remote applications, see the Open Remote Cursors with Blocking attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group Open Rem Curs

• The number of remote cursors currently open for this application, including the cursors counted by the Open Remote Cursors with Blocking attribute. Use this attribute with the Open Remote Cursors with Blocking attribute to calculate the percentage of remote cursors that are blocking cursors. If the percentage is low, you might be able to improve performance by improving the row blocking in the application. For the number of open cursors used by applications connected to a local database, see the Open Local Cursors attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group Open Rem Curs Blk

• The number of remote blocking cursors currently open for this application. Use this attribute with the Open Remote Cursors attribute to calculate the percentage of remote cursors that are blocking cursors. If the percentage is low, you might be able to use the following steps to improve performance by improving the row blocking in the application:
  1. Check the pre-compile options for record blocking for treatment of ambiguous cursors.
  2. Redefine cursors to allow for blocking.
  Rejected Block Cursor Requests and Accepted Block Cursor Requests attributes provide additional information that might help you tune your configuration parameters to improve row blocking in your application. For the number of open blocking cursors that are used by applications connected to a local database, see the Open Local Cursors with Blocking attribute. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Group Pkg Cache Hit Ratio

• The percentage of package sections that were found in the cache. This attribute tells you whether the package cache is being used effectively. If the hit ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that the package cache must be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group Pkg Cache Inserts

• The total number of times that a requested section was not available for use and had to be loaded into the package cache. This count includes any implicit prepares performed by the system. By using the Package Cache Lookups attribute, you can calculate the package cache hit ratio using the following formula: 1 - (Package Cache Inserts / Package Cache Lookups). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group Pkg Cache Lookups

• The number of times that an application looked for a section or package in the package cache. At a database level, it indicates the overall number of references since the database was started, or monitor data was reset. Note that this counter includes the cases where the section is already loaded in the cache and when the section has to be loaded into the cache. To calculate the package cache hit ratio use the following formula: 1 - (Package Cache Inserts / Package Cache Lookups) The package cache hit ratio tells you whether the package cache is being used effectively. If the hit ratio is high (more than 0. 8), the cache is performing well. A smaller ratio might indicate that the package cache must be increased. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Group Pool Data from Estore

• Number of buffer pool data pages copied from extended storage. Required pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group Pool Data L Reads

• The number of logical read requests for data pages that have gone through the buffer pool. This count includes accesses to the following types of data:
  • Data that is already 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
  By using the Pool Data Physical Reads attribute, you can calculate the data page hit ratio for the buffer pool as in the following formula: 1 - (buffer pool data physical reads / buffer pool data logical reads) By using the Pool Data Physical Reads, Pool Index Physical Reads, and Pool Index Logical Reads attributes, you can calculate the overall buffer pool hit ratio as in the following example: 1 - ((buffer pool data physical reads + buffer pool index physical reads) / (buffer pool data logical reads + buffer pool index logical reads)) Increasing buffer pool size generally improves the hit ratio until you reach a point of diminishing returns. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Pool Data P Reads

• The number of read requests that required I/O to get data pages into the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Pool Data to Estore

• Number of buffer pool data pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group Pool Data Writes

• The number of times a buffer pool data page was physically written to disk. A buffer pool data page is written to disk for the following reasons:
  • To free a page in the buffer pool so that another page can be read
  • To flush the buffer pool
  If a buffer pool data page is written to disk for a high percentage of Buffer Pool Data Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Group Pool Hit Ratio

• The buffer pool hit ratio (as a percentage). The sum of the Pool Data Logical Reads and Pool Index Logical Reads attributes is divided by the value of the Pool Total Reads attribute to derive the ratio. Use this attribute to determine whether buffer pool assignment is efficient. If the pool hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group Pool Index from Estore

• Number of buffer pool index pages copied from extended storage. Required index pages are copied from extended storage to the buffer pool. The copy process might incur the cost of connecting to the shared memory segment, but it saves the cost of a disk read. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group Pool Index L Reads

• The number of logical read requests for index pages that have gone through the buffer pool. This count includes accesses to index pages that are already in the buffer pool when the database manager needs to process the page or read into the buffer pool before the database manager can process the page. By using the Pool Index Physical Reads attribute, you can calculate the index page hit ratio for the buffer pool using the following formula: 1 - (buffer pool index physical reads / buffer pool index logical reads) To calculate the overall buffer pool hit ratio, see the Pool Data Logical Reads attribute. If the hit ratio is low, increasing the number of buffer pool pages might improve performance. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Pool Index to Estore

• Number of buffer pool index pages copied to extended storage. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Group Pool Index Writes

• The number of times a buffer pool index page was physically written to disk. If a buffer pool index page is written to disk for a high percentage of the Pool Index Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. If all applications are updating the database, increasing the size of the buffer pool might have minimal impact on performance; most pages contain updated data that must be written to disk. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Group Pool Read Time

• The total amount of elapsed time spent processing read requests that caused data or index pages to be physically read from disk to buffer pool. Use this attribute with the Buffer Pool Data Physical Reads and Buffer Pool Index Physical Reads attributes to calculate the average page-read time. This average is important because it might indicate the presence of an I/O wait, which can indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group Pool Total Reads

• The total number of read requests that required I/O to get data pages and index pages into the buffer pool. This attribute is the total of the Pool Data Physical Reads and Pool Index Physical Reads attributes. Use this attribute to determine how busy the DB2 server is in terms of I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Pool Total Writes

• The total number of write requests. This attribute is the total of the Pool Data Writes and Pool Index Writes attributes. Use this attribute to determine how busy the DB2 server is in terms of write I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Group Pool Write Time

• The total amount of time spent physically writing data or index pages from the buffer pool to disk. Use this attribute with the Buffer Pool Data Writes and Buffer Pool Index Writes attributes to calculate the average page-write time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group Prefetch Wait Time

• The time an application spent waiting for an I/O server or prefetcher to finish loading pages into the buffer pool. This attribute can be used to experiment with changing the number of I/O servers and the I/O server sizes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group Query Card Estimate

• An estimate of the number of rows that are returned by a query. You can compare this estimate by the SQL compiler with the actual runtime values. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Query Cost Estimate

• Estimated cost, in timerons, for a query, as determined by the SQL compiler. This attribute allows correlation of actual runtime values with the compile-time estimates. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timerons.

Application Group Rej Curs Blk

• The number of times that a request for an I/O block at the server was rejected and the request was converted to non-blocked I/O. If there are many cursors blocking data, the communication heap might become full. When this heap is full, I/O blocks are not allocated for blocking cursors; however, an error condition does not alert you to this condition. If cursors are unable to block data, performance can be affected adversely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rejections.

Application Group Rollback SQL Stmts

• The total number of SQL ROLLBACK statements that have been attempted. A rollback can result from an application request, a deadlock, or an error situation. This attribute counts only the number of rollback statements issued from applications. At the application level, this attribute can help you determine the level of database activity for the application and the amount of conflict with other applications. At the database level, it can help you determine the amount of activity in the database and the amount of conflict between applications on the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Group Rows Deleted

• The number of row deletions attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Rows Inserted

• The number of row insertions attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Rows Read

• The number of rows read from the table. This attribute helps to identify tables with heavy usage for which you might want to create additional indexes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Rows Selected

• The number of rows that have been selected and returned to the application. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Rows Updated

• The number of row updates attempted. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Rows Written

• The number of rows changed (inserted, deleted, or updated) in the table. A high value for table-level information indicates heavy usage of the table. If so, you might want to use the Run Statistics (RUNSTATS) utility to maintain efficiency of the packages used for this table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Group Select SQL Stmts

• The number of SQL SELECT statements that ran. Use this attribute to determine the level of database activity at the application or database level. You can also use the following steps to determine the ratio of SELECT statements to the total statements:
  1. Sum the number of attempted static SQL statements and the number of attempted dynamic SQL statements.
  2. Divide the sum by the number of select SQL statements that ran.
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group Sort Overflows

• The total number of sorts that ran out of sort heap space and might have required disk space for temporary storage. at the database or application level, use this element with the Total Sorts attribute, this attribute can help to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Group Sort Overflows Pct

• The percentage of sorts that ran out of sort heap space and might have required disk space for temporary storage. This percentage is calculated by dividing the value of the Sort Overflows attribute by the value of the Total Sorts attribute. at the database or application level, use this attribute to evaluate the percentage of sorts that required overflow to disk. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is percent.

Application Group Static SQL Stmts

• The number of static SQL statements that were attempted. Use this attribute to calculate the total number of successful SQL statements at the database or application level using the following steps:
  1. Sum the number of Dynamic SQL Statements Attempted and the Static SQL Statements Attempted.
  2. Subtract the number of Failed Statement Operations.
  The remainder equals the throughput (the number of successful SQL statements) during the current monitoring period. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group Total Hash Joins

• The total number of hash joins that ran. At the database or application level, use this value with the Hash Join Overflows attribute and the Hash Join Small Overflows attribute to determine if a significant percentage of hash joins would benefit from modest increases in the sort heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Application Group Total Hash Loops

• The total number of times that a single partition of a hash join was larger than the available sort heap space. Values for this attribute indicate inefficient execution of hash joins. This might indicate that the sort heap size is too small or the sort heap threshold is too small. Use this value with the other hash join variables to tune the sort heap size (sortheap) and sort heap threshold (sheapthres) configuration parameters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Group Total Sort Time

• The total elapsed time (in milliseconds) for all sorts that ran. at the database or application level, use this element with the Total Sorts attribute to calculate the average sort time. This average can indicate whether sorting is a performance concern. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Group Total Sorts

• The total number of sorts that ran. at the database or application level, use this value with the Sort Overflows attribute to calculate the percentage of sorts that need more heap space. You can also use it with the Total Sort Time attribute to calculate the average sort time. If the number of sort overflows is small with respect to the total sorts, increasing the sort heap size might have little impact on performance, unless this buffer size is increased substantially. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Group Total SQL Stmt

• The total number of dynamic and static SQL statements. This value is derived by adding the values of the Dynamic SQL Statements and the Static SQL Statements attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group UID SQL Stmts

• The number of SQL UPDATE, INSERT, and DELETE statements that ran. Use this attribute to determine the level of database activity at the application or database level. You can also use the following steps to determine the ratio of UPDATE, INSERT, and DELETE statements to the total number of statements:
  1. Sum the number of attempted static SQL statements and the number of attempted dynamic SQL statements.
  2. Divide the number of UPDATE/INSERT/DELETE SQL statements that ran by the sum derived in step 1.
  . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application Group UOW Lock Wait Time

• The total amount of elapsed time this unit of work has spent waiting for locks. This attribute can help you to determine the severity of the resource contention problem. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Group UOW Log Space Used

• The amount of log space (in bytes) used in the current unit of work of the monitored application. Use this attribute to understand the logging requirements at the unit-of-work level. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is bytes.

Application Group X Lock Escals

• The number of times that locks have been escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application. The amount of lock list space available is determined by the LOCKLIST and MAXLOCKS configuration parameters. Other applications cannot access data held by an exclusive lock. Because exclusive locks can affect the concurrency of your data, it is important to track them. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, it uses space in the lock list allocated for other applications. When the entire lock list is full, an error occurs. Use this attribute with the Previous UOW Stop Time attribute to calculate the total elapsed time between COMMIT/ROLLBACK points, and with the UOW Start Time attribute to calculate the elapsed time of the latest unit of work. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Application Hash Join Overflows

• The number of times that hash join data exceeded the available sort heap space. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Hash Join Small Overflows

• The number of times that hash join data exceeded the available sort heap space by less than 10%. The value format is an integer. If this value and the value of the Hash Join Overflows attribute are high, you must consider increasing the sort heap threshold. If this value is greater than 10% of Hash Join Overflows, you must consider increasing the sort heap size. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Int Auto Rebinds

• The number of automatic rebinds (or recompiles) that have been attempted. The value format is an integer. Automatic rebinds are the internal binds the system performs when a package has been invalidated. Use this attribute to determine the level of database activity at the application or database level. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rebinds.

Application Int Deadlock Rollbacks

• The total number of forced rollbacks initiated by the database manager due to a deadlock. The value format is an integer. The database manager initiates a rollback for the current unit of work in an application that is experiencing a deadlock. This attribute shows the number of deadlocks that have been broken. It can indicate the possibility of concurrency problems. It is also important because internal rollbacks due to deadlocks can cause performance degradation. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Int Rollbacks

• The total number of rollbacks initiated internally by the database manager. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Int Rows Deleted

• The number of rows deleted from the database as a result of internal activity. The value format is an integer. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints or triggers that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Int Rows Inserted

• The number of rows inserted into the database as a result of internal activity caused by triggers. The value format is an integer. This attribute can help to gain insight into the internal activity within the database manager. If this activity is high, you must evaluate the design to determine if you can alter it to reduce this activity. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Int Rows Updated

• The number of rows updated from the database as a result of internal activity. The value format is an integer. This attribute can help to gain insight into internal activity within the database manager. If this activity is high, you must evaluate the table design to determine if the referential constraints that you defined on the database are necessary. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Internal Commits

• The total number of commits initiated internally by the database manager. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is commits.

Application Lock Escals

• The number of times that locks have been escalated from several row locks to a table lock. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application, or the lock list space consumed by all applications is approaching the total lock list space. This data item includes a count of all lock escalations, including exclusive lock escalations. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, the application uses space in the lock list that is allocated for other applications. When the entire lock list is full, an error occurs. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Lock Timeouts

• The number of times that a request to lock an object time out instead of being granted. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timeouts.

Application Lock Wait Time

• The total elapsed time (in milliseconds) that was spent waiting for a lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Lock Waits

• The total number of times the database applications waited for locks. The value format is an integer. At the database level, the lock waits value is the total number of times that applications waited for locks within this database. At the application-connection level, the lock waits value is the total number of times that this connection requested a lock but waited because another connection was already holding a lock on the data.
• The type is int.
• The unit is occurences.

Application Locks Held

• The number of locks that are currently held. The value format is an integer.
• The type is int.
• The unit is locks.

Application Open Local Curs

• The number of local cursors currently open for this application, including those cursors counted by Open Local Cursors with Blocking attribute. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Open Local Curs Blk

• The number of local blocking cursors currently open for this application. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Open Rem Curs

• The number of remote cursors currently open for this application, including the cursors counted by the Open Remote Cursors with Blocking attribute. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Open Rem Curs Blk

• The number of remote blocking cursors currently open for this application. The value format is an integer. Use this attribute with the Open Remote Cursors attribute to calculate the percentage of remote cursors that are blocking cursors. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is cursors.

Application Pkg Cache Hit Ratio

• The percentage of package sections that were found in the cache. The value format is an integer.
• The type is double.
• The unit is percent.

Application Pkg Cache Inserts

• The total number of times that a requested section was not available for use and had to be loaded into the package cache. The value format is an integer. This count includes any implicit prepares performed by the system. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Pkg Cache Lookups

• The number of times that an application looked for a section or package in the package cache. The value format is an integer. At a database level, it indicates the overall number of references since the database was started, or monitor data was reset. Note that this counter includes the cases where the section is already loaded in the cache and when the section has to be loaded into the cache. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is lookups.

Application Pool Data from Estore

• Number of buffer pool data pages copied from extended storage. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Data L Reads

• The number of logical read requests for data pages that have gone through the buffer pool. The value format is an integer. This count includes accesses to data that is already in the buffer pool when the database manager needs to process the page or read into the buffer pool before the database manager can process the page. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Data P Reads

• The number of read requests that required I/O to get data pages into the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Data to Estore

• Number of buffer pool data pages copied to extended storage. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Data Writes

• The number of times a buffer pool data page was physically written to disk. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Pool Hit Ratio

• The buffer pool hit ratio (as a percentage). The value format is an integer. The sum of the Pool Data Logical Reads and Pool Index Logical Reads attributes is divided by the value of the Pool Total Reads attribute to derive the percentage. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Pool Index from Estore

• Number of buffer pool index pages copied from extended storage. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Index L Reads

• The number of logical read requests for index pages that have gone through the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Index P Reads

• The number of physical read requests to get index pages into the buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is requests.

Application Pool Index to Estore

• Number of buffer pool index pages copied to extended storage. The value format is an integer. Pages are copied from the buffer pool to extended storage when they are selected as victim pages. As a result of the copying process, there is sufficient space for new pages in the buffer pool. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is pages.

Application Pool Index Writes

• The number of times a buffer pool index page was physically written to disk. The value format is an integer. If a buffer pool index page is written to disk for a high percentage of the Pool Index Physical Reads, performance might improve by increasing the number of buffer pool pages available for the database. If all applications are updating the database, increasing the size of the buffer pool might have minimal impact on performance; most pages contain updated data that must be written to disk. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is writes.

Application Pool Read Time

• The total amount of elapsed time spent processing read requests that caused data or index pages to be physically read from disk to buffer pool. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Pool Total Reads

• The total number of read requests that required I/O to get data pages and index pages into the buffer pool. The value format is an integer. This attribute is the total of the Pool Data Physical Reads and Pool Index Physical Reads attributes. Use this attribute to determine how busy the DB2 server is in terms of I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text.
• The type is int.
• The unit is requests.

Application Pool Total Writes

• The total number of write requests. The value format is an integer. This attribute is the total of the Pool Data Writes and Pool Index Writes attributes. Use this attribute to determine how busy the DB2 server is in terms of write I/O activity. Values that are greater than or equal to 2147483647 are indicated in the portal with the Value Exceeds Maximum text, and values that are smaller than -2147483648 are indicated with the Value Exceeds Minimum text.
• The type is int.
• The unit is requests.

Application Pool Write Time

• The total amount of time spent physically writing data or index pages from the buffer pool to disk. The value format is an integer. Use this attribute with the Buffer Pool Data Writes and Buffer Pool Index Writes attributes to calculate the average page-write time. This average is important because it might indicate the presence of an I/O wait, which in turn might indicate that you must move data to a different device. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is ?.

Application Query Card Estimate

• An estimate of the number of rows that are returned by a query. The value format is an integer. You can compare this estimate by the SQL compiler with the actual runtime values. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rows.

Application Query Cost Estimate

• Estimated cost, in timerons, for a query, as determined by the SQL compiler. The value format is an integer. This attribute allows correlation of actual runtime values with the compile-time estimates. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is timerons.

Application Rej Curs Blk

• The number of times that a request for an I/O block at the server was rejected and the request was converted to non-blocked I/O. If there are many cursors blocking data, the communication heap might become full. The value format is an integer. When this heap is full, I/O blocks are not allocated for blocking cursors; however, an error condition does not alert you to this condition. If cursors are unable to block data, performance can be affected adversely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Rollback SQL Stmts

• The total number of SQL ROLLBACK statements that have been attempted. The value format is an integer. A rollback can result from an application request, a deadlock, or an error situation. This attribute counts only the number of rollback statements issued from applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is rollbacks.

Application Rows Deleted

• The number of row deletions attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is deletes.

Application Rows Inserted

• The number of row insertions attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is inserts.

Application Rows Read

• The number of rows read from the table. The value format is an integer. This attribute helps to identify tables with heavy usage for which you might want to create additional indexes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is reads.

Application Rows Selected

• The number of rows that have been selected and returned to the application. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is selects.

Application Rows Updated

• The number of row updates attempted. The value format is an integer. Use this attribute to gain insight into the current level of activity within the database manager. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is updates.

Application Rows Written

• The number of rows changed (inserted, deleted, or updated) in the table. The value format is an integer. A high value for table-level information indicates heavy usage of the table. If so, you might want to use the Run Statistics (RUNSTATS) utility to maintain efficiency of the packages used for this table. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is changes.

Application Select SQL Stmts

• The number of SQL SELECT statements that were issued. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is selects.

Application Sort Overflows

• The total number of sorts that ran out of sort heap space and might have required disk space for temporary storage. The value format is an integer. at the database or application level, use this element with the Total Sorts attribute. This attribute can help to determine the source of contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Sort Overflows Percent

• The percentage of sorts that ran out of sort heap space and might have required disk space for temporary storage. The value format is an integer. This percentage is calculated by dividing the value of the Sort Overflows attribute by the value of the Total Sorts attribute. at the database or application level, use this attribute to evaluate the percentage of sorts that required overflow to disk. If this percentage is high, you might want to adjust the database configuration by increasing the value of the SORTHEAP configuration parameter. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is double.
• The unit is percent.

Application Total Hash Joins

• The total number of hash joins that ran. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is joins.

Application Total Hash Loops

• The total number of times that a single partition of a hash join was larger than the available sort heap space. The value format is an integer. Values for this attribute indicate inefficient execution of hash joins. This might indicate that the sort heap size is too small or the sort heap threshold is too small. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is occurences.

Application Total Sort Time

• The total elapsed time (in milliseconds) for all sorts that ran. The value format is an integer. at the database or application level, use this element with the Total Sorts attribute to calculate the average sort time. This average can indicate whether sorting is a performance concern. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Application Total Sorts

• The total number of sorts that have been issued. The value format is an integer. at the database or application level, use this value with the Sort Overflows attribute to calculate the percentage of sorts that need more heap space. You can also use it with the Total Sort Time attribute to calculate the average sort time. If the number of sort overflows is small with respect to the total sorts, increasing the sort heap size might have little impact on performance, unless this buffer size is increased substantially. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is sorts.

Application Total SQL Stmt

• The total number of dynamic and static SQL statements. This value is derived by adding the values of the Dynamic SQL Statements and the Static SQL Statements attributes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application UID SQL Stmts

• The number of SQL UPDATE, INSERT, and DELETE statements that were issued. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is statements.

Application UOW Lock Wait Time

• The time the UOW (unit of work) waited on locks (in seconds). This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is seconds.

Application X Lock Escals

• The number of times that locks have been escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. The value format is an integer. A lock is escalated when the total number of locks held by an application reaches the maximum amount of lock list space available to the application. The amount of lock list space available is determined by the LOCKLIST and MAXLOCKS configuration parameters. Other applications cannot access data held by an exclusive lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is escalations.

Locking Conflict Lock Wait Time

• The total elapsed time (in milliseconds) that a lock was waited for. At the database level, this is the total amount of elapsed time that all applications were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction has waited for a lock to be granted. This attribute might be used with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is milliseconds.

Locking Conflict Lock Wait Time (Superseded)

• The total elapsed time (in milliseconds) that a lock was waited for. At the database level, this is the total amount of elapsed time that all applications were waiting for a lock within this database. At the application-connection and transaction levels, this is the total amount of elapsed time that this connection or transaction has waited for a lock to be granted. This attribute might be used with the Lock Waits attribute to calculate the average wait time for a lock. This calculation can be performed at either the database or the application-connection level. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is milliseconds.

Locking Conflict Locks Held

• The number of locks currently held. If the monitor information is at the database level, this is the total number of locks currently held by all applications in the database. If it is at the application level, this is the total number of locks currently held by all agents for the application. Usage of this attribute depends on the level of information being returned from the database system monitor. The following value is also valid:. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.
• The unit is locks.

Locking Conflict Locks Held (Superseded)

• The number of locks currently held. If the monitor information is at the database level, this is the total number of locks currently held by all applications in the database. If it is at the application level, this is the total number of locks currently held by all agents for the application. Usage of this attribute depends on the level of information being returned from the database system monitor. This is available for thresholds, but not in the UI.
• The type is int.
• The unit is locks.

Dimensions

The following dimensions are available for the component.

Application Agent ID

• The application handle, which is a system-wide unique ID for the application. The value format is an integer. On multi-node systems, where a database is partitioned, this ID is the same on every node where the application might make a secondary connection. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Agent ID Holding Lock

• The application handle of the agent holding a lock for which this application is waiting. The value format is an integer. The lock monitor group must be turned on to obtain this information. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Appl Conn Timestamp

• The date and time that an application started a connection request. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application Appl ID

• The identifier generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database. The value format is a text string, with a maximum of 32 characters.
• The type is string.

Application Appl ID Holding Lock

• The application ID of the application that is holding a lock on the object that this application is waiting to obtain (Unicode). The value format is a text string with a maximum of 96 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Appl Name

• The name of the application that is connected to the database. The value format is a text string, with a maximum of 60 bytes. For example: *Local. db2inst1. 990212202018 .
• The type is string.

Application Appl Status

• The status of the application being monitored. This attribute can help you diagnose potential application problems. The value format is a text string with a maximum of 64 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Auth ID

• The authorization ID of the user who invoked the application that is being monitored. On a DB2 Connect gateway node, this ID is the user authorization ID on the host. The value format is a text string with a maximum of 60 bytes. Use this attribute to determine who invoked the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Client PID

• The process ID of the client application that made the connection to the database. The value format is an integer. Use this attribute to correlate monitor information such as CPU and I/O time to your client application. If a DRDA AS connection is used, this element is set to 0. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Client Platform

• The operating system on which the client application is running. Use this attribute to analyze problems for remote applications. The value format is a text string with a maximum of 20 characters. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Client Prdid

• The product and version identifier for the software on the client. The value format is a text string with a maximum of 20 characters. For example: SQL06010 . This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Client Protocol

• The communication protocol that the client application is using to communicate with the server. The value format is a text string with a maximum of 12 characters. Use this attribute for troubleshooting of remote applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Conn Complete Timestamp

• The date and time that a connection request was granted. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is timestamp.

Application Corr Token

• The DRDA AS correlation token. The value format is a text string with a maximum of 96 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Country Code

• The country code of the client application. The value format is an integer. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Creator

• The authorization ID of the user that precompiled the application (Unicode). The value format is a text string with a maximum of 60 bytes. Use this attribute to help identify the SQL statement that is processing, with the CREATOR column of the package section information in the catalogs. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Cursor Name

• The name of the cursor corresponding to this SQL statement. The value format is a text string with a maximum of 60 bytes. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application DB Name

• The real name of the database for which information is collected or to which the application is connected. This name was given to the database when it was created. The value format is a simple text string with a maximum of 60 bytes. Use this attribute to identify the specific database to which the data applies.
• The type is string.

Application DB Partition

• The DB2 database partition node number, which can range from 0 to 999. The Aggregated and Current Partition values can be used within a query or situation filter. If a db partition filter is not specified, data is returned for the current database partition. If a db partition filter is set to Aggregated, only aggregated partition data is returned. Historical data collection includes both aggregated and individual partition attribute data. In addition to numeric partition numbers in the 0 to 999 range.
• The type is string.

Application Execution ID

• The ID that the user specified when logging in to the operating system. This ID is distinct from the Authorization ID, which the user specifies when connecting to the database. The value format is a text string with a maximum of 60 bytes. Use this attribute to determine the operating system user ID of the individual running the monitored application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Agent ID

• The application handle, which is a system-wide unique ID for the application. On multi-node systems, where a database is partitioned, this ID is the same on every node where the application might make a secondary connection. Use the application handle to identify an active application (application handle is synonymous with agent ID) uniquely. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group Agent ID Holding Lock

• The application handle of the agent holding a lock for which this application is waiting. The lock monitor group must be turned on to obtain this information. This attribute can help you to determine which applications are in contention for resources. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group Appl Conn Time

• The string date and time that an application started a connection request. The value format is CYYMMDDHHMMSSmmm. Use this attribute to determine when the application started its connection request to the database. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Appl ID

• The identifier generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database. The identifier is unique across the network. The application ID is displayed in various formats that depend on the communication protocol between the client and the server system on which the database manager or DDCS is running. Each of the formats consists of three parts that are separated by periods. Use this ID (known on both the client and server) to correlate the client and server parts of the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Appl ID Holding Lock

• The application ID of the application that is holding a lock on the object that this application is waiting to obtain. The value format is a text string with a maximum of 32 characters. This attribute can help you determine which applications are in contention for resources. You can use it to identify the application handle (agent ID) and table ID that are holding the lock. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Appl Name

• The name of the application running at the client as it is known to the database manager or DB2 Connect. The value format is a text string, with a maximum of 20 characters. For example: *Local. db2inst1. 990212202018 . Use this attribute with the Application ID attribute to relate data items with your application. In a client/server environment, this name is passed from the client to the server to establish the database connection. For DRDA-AS connections, this name is the DRDA external name. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Appl Status

• The status of the monitored application. This attribute can help you diagnose potential application problems. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Auth ID

• The authorization ID of the user who invoked the monitored application. On a DB2 Connect gateway node, this ID is the user authorization ID on the host. The value format is a text string with a maximum of 20 characters. Use this attribute to determine who invoked the application. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Client PID

• The process ID of the client application that made the connection to the database. Use this attribute to correlate monitor information such as CPU and I/O time to your client application. If a DRDA AS connection is used, this element is set to 0. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is int.

Application Group Client Platform

• The operating system on which the client application is running. Use this attribute to analyze problems for remote applications. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Client Prdid

• The product and version identifier for the software on the client. The value format is a text string with a maximum of 20 characters, for example: SQL06010. This is not available in the UI by default. It can be made available through dynamic configuration.
• The type is string.

Application Group Client Protocol