C

Usage

This element can be used to recreate the hierarchy of embedded and recursive routine calls.

Usage

This element can be used to recreate the hierarchy of embedded and recursive routine calls.

Usage

The catalog cache draws its storage dynamically from the database heap and even if the cache storage has not reached its limit, inserts into the catalog cache may fail due to a lack of space in the database heap. If the catalog cache heap full count is not zero, then this insert failure condition can be corrected by increasing the database heap size or reducing the catalog cache size.

Usage

    1 - (Catalog Cache Inserts / Catalog Cache Lookups)

See the cat_cache_lookups monitor element for more information about using this element.

Usage

To calculate the catalog cache hit ratio use the following formula:

 
  (1 - (cat_cache_inserts / cat_cache_lookups))

indicates how well the catalog cache is avoiding catalog accesses. If the ratio is high (more than 0.8), then the cache is performing well. A smaller ratio might suggest that the catalogcache_sz configuration parameter should be increased. You should expect a large ratio immediately following the first connection to the database.

The execution of Data Definition Language (DDL) SQL statements involving a table, view, or alias will evict the table descriptor information for that object from the catalog cache causing it to be re-inserted on the next reference. In addition, GRANT and REVOKE statements for database authorization and execute privilege of routines will evict the subject authorization information from the catalog cache. Therefore, the heavy use of DDL statements and GRANT/REVOKE statements may also increase the ratio.

Usage

Use this element with thecat_cache_size_top monitor element to determine whether the size of the catalog cache needs to be increased to avoid overflowing.

Catalog cache space is reclaimed by evicting table descriptor information for tables, views, or aliases, or authorization information that is not currently in use by any transaction.

If the value of the cat_cache_overflows monitor element is large, the catalog cache may be too small for the workload. Enlarging the catalog cache may improve its performance. If the workload includes transactions which compile a large number of SQL statements referencing many tables, views, aliases, user-defined functions, or stored procedures in a single unit of work, then compiling fewer SQL statements in a single transaction may improve the performance of the catalog cache. Or if the workload includes binding of packages containing many SQL statements referencing many tables, views, aliases, user-defined functions, or stored procedures, you can try splitting packages so that they include fewer SQL statements to improve performance.

Usage

This element indicates the maximum number of bytes the catalog cache required logically for the workload run against the database since it was activated.

The catalog cache is managed by logical size, which does not include memory management usage. The pool_watermark element in the database snapshot provides the physical high water mark value for memory used by the catalog cache. The logical size rather than physical size should be used for catalog cache monitoring and tuning efforts.

If the catalog cache overflowed, then this element contains the largest size reached by the catalog cache during the overflow. Check the cat_cache_overflows monitor element to determine if such a condition occurred.

   maximum catalog cache size / 4096

Usage

This value is an indicator of the amount of time DB2 has spent waiting while communicating with the cluster caching facility.

Usage

I

The initial value that was captured when the event monitor was activated.

U

Updated value

Usage

DBCFG

Changing a database configuration parameter

DBMCFG

Changing a database manager configuration parameter

DBCFGVALUES

Capturing database configuration parameter values at event monitor startup, if a database configuration parameter was changed while the event monitor was inactive

DBMCFGVALUES

Capturing database manager configuration parameter values at event monitor startup, if a database manager configuration parameter was changed while the event monitor was inactive

Usage

Usage

• AUTOMATIC
• COMPUTED
• NONE

Usage

Usage

• AUTOMATIC
• COMPUTED
• NONE

Usage

FCM channel auto-tuning is enabled by setting the fcm_num_channels configuration parameter to AUTOMATIC.

Usage

(ch_free/ch_total) * 100

If the percentage of free FCM channels falls below 20% and if the FCM channel auto-tuning is enabled, then DB2 database manager will adjust the FCM channel numbers.

If the percentage of free FCM channels falls below 20% and if the FCM channel auto-tuning is not enabled, then you need to tune the fcm_num_channels configuration parameter.

Usage

Use this monitor element in conjunction with the fcm_num_channels configuration parameter to determine the maximum connection entry utilization.

Usage

This internal monitor element is used by IBM Support only.

Usage

If the ch_auto_tuning monitor element indicates that FCM is being tuned automatically, then the value of the ch_total monitor element is adjusted based on the demand for FCM channels.

ch_total - ch_free

(ch_free/ch_total) * 100

If the percentage of free FCM channels falls below 20% and if the FCM channel auto-tuning is enabled, then DB2 database manager will adjust the FCM channel numbers.

If the percentage of free FCM channels falls below 20% and if the FCM channel auto-tuning is not enabled, then you need to tune the fcm_num_channels configuration parameter.

Usage

Use this element for problem determination and accounting purposes.

Usage

Use this element for problem determination and accounting purposes.

Usage

Use this monitor element to determine the amount of time spent waiting for requests from a client, as opposed to working on requests. A high client idle time may indicate performance issues that need to be addressed on the client rather than the server.

Usage

You can use this element to correlate monitor information such as CPU and I/O time to your client application.

In the case of a DRDA AS connection, this element will be set to 0.

Usage

This element can be used for problem determination for remote applications. Values for this field can be found in the header file sqlmon.h.

Usage

Usage

Usage

Use this element in application server or Transaction Processing monitor environments to identify the end-user for whom the transaction is being executed.

Usage

Use this element to identify the user's machine by node ID, terminal ID, or similar identifiers.

Usage

This monitor element stores the compilation environment description in a binary large object. To view this information in readable form, use the COMPILATION_ENV table function.

You can provide this element as input to the COMPILATION_ENV table function, or to the SET COMPILATION ENVIRONMENT SQL statement.

Usage

Usage

Use this element as an indicator of the length of time that applications are maintaining connections to a host database.

This element is composed of two subelements that report time spent as seconds and microseconds (one millionth of a second). The names of the subelements can be derived by adding "_s" and "_ms" to the name of this monitor element. To retrieve the total time spent for this monitor element, the values of the two subelements must be added together. For example, if the "_s" subelement value is 3 and the "_ms" subelement value is 20, then the total time spent for the monitor element is 3.00002 seconds.

Usage

Use this element as an indicator of the time it currently takes applications to connect to a particular host database.

This element is composed of two subelements that report time spent as seconds and microseconds (one millionth of a second). The names of the subelements can be derived by adding "_s" and "_ms" to the name of this monitor element. To retrieve the total time spent for this monitor element, the values of the two subelements must be added together. For example, if the "_s" subelement value is 3 and the "_ms" subelement value is 20, then the total time spent for the monitor element is 3.00002 seconds.

Usage

Use this element to know the highest concurrency of activities (including nested activities) reached on a member for a service subclass in the time interval collected.

Usage

This element may be useful in determining where to place thresholds on connection concurrency by showing where the current high watermark is. It is also useful for verifying that such a threshold is configured correctly and doing its job.

Usage

Use this element to know the highest number of concurrent activities reached on a member for any occurrence of this workload in the time interval collected.

Usage

Use this element to know the highest concurrency of workload occurrences reached on a member for a workload in the time interval collected.

Usage

Use this element to understand which CONCURRENTDBCOORDACTIVITIES database threshold, if any, was applied to the activity.

Usage

Use this element to understand if the activity was queued by the CONCURRENTDBCOORDACTIVITIES database threshold applied to the activity.

Usage

Use this element to understand the value of the CONCURRENTDBCOORDACTIVITIES database threshold applied to the activity, if any.

Usage

Use this element to determine if the activity violated the CONCURRENTDBCOORDACTIVITIES database threshold that was applied to the activity.

Usage

Use this element to understand which CONCURRENTDBCOORDACTIVITIES service subclass threshold, if any, was applied to the activity.

Usage

Use this element to understand if the activity was queued by the CONCURRENTDBCOORDACTIVITIES service subclass threshold applied to the activity.

Usage

Use this element to understand the value of the CONCURRENTDBCOORDACTIVITIES service subclass threshold applied to the activity, if any.

Usage

Use this element to determine if the activity violated the CONCURRENTDBCOORDACTIVITIES service subclass threshold that was applied to the activity.

Usage

Use this element to understand which CONCURRENTDBCOORDACTIVITIES service superclass threshold, if any, was applied to the activity.

Usage

Use this element to understand if the activity was queued by the CONCURRENTDBCOORDACTIVITIES service superclass threshold applied to the activity.

Usage

Use this element to understand the value of the CONCURRENTDBCOORDACTIVITIES service superclass threshold applied to the activity, if any.

Usage

Use this element to determine if the activity violated the CONCURRENTDBCOORDACTIVITIES service superclass threshold that was applied to the activity.

Usage

Use this element to understand which CONCURRENTDBCOORDACTIVITIES workload work action set threshold, if any, was applied to the activity.

Usage

Use this element to understand if the activity was queued by the CONCURRENTDBCOORDACTIVITIES workload work action set threshold applied to the activity.

Usage

Use this element to understand the value of the CONCURRENTDBCOORDACTIVITIES workload work action set threshold applied to the activity.

Usage

Use this element to determine if the activity violated the CONCURRENTDBCOORDACTIVITIES workload work action set threshold that was applied to the activity.

Usage

Use this element to understand which CONCURRENTDBCOORDACTIVITIES work action set threshold, if any, was applied to the activity.

Usage

Use this element to understand if the activity was queued by the CONCURRENTDBCOORDACTIVITIES_WORK_ACTION_SET threshold applied to the activity.

Usage

Use this element to understand the value of the CONCURRENTDBCOORDACTIVITIES_WORK threshold applied to the activity, if any.

Usage

Use this element to determine if the activity violated the CONCURRENTDBCOORDACTIVITIES_WORK_ACTION_SET threshold that was applied to the activity.

Usage

Usage

Two members can be active, but the communication connection between them remains inactive until there is some communication between the members.

Usage

You can use this element to help identify the package and the SQL statement that is executing.

Usage

Use this monitor element in conjunction with the elements container_id, container_name, container_type, container_total_pages, container_usable_pages, and container_accessible to describe the container. This is only applicable to a DMS table space.

Usage

This element returns the type of the container, which can be a directory path (for SMS only), file (for DMS) or a raw device (for DMS). This element can be used in conjunction with the elements container_id, container_name, container_total_pages, container_usable_pages, container_stripe_set, and container_accessible to describe the container.

The valid values for this monitor element are defined in the sqlutil.h file.

Usage

Use this element to understand if activities on the system are completing successfully. Activities may be aborted due to cancellation, errors or reactive thresholds.

Usage

This element can be used to determine the throughput of activities in the system or to aid in calculating average activity lifetime across multiple members.

Usage

Use this statistic to determine the arithmetic mean of the estimated costs of coordinator DML activities at nesting level 0 that are associated this service subclass, workload, or work class that completed or aborted since the last statistics reset.

This average can also be used to determine whether or not the histogram template used for the activity estimated cost histogram is appropriate. Compute the average activity estimated cost from the activity estimated cost histogram. Compare the computed average with this monitor element. If the computed average deviates from the true average reported by this monitor element, consider altering the histogram template for the activity estimated cost histogram, using a set of bin values that are more appropriate for your data.

Usage

Use this statistic to determine the arithmetic mean of execution time for coordinator activities associated with a service subclass, workload, or work class that completed or aborted.

This average can also be used to determine whether or not the histogram template used for the activity execution time histogram is appropriate. Compute the average activity execution time from the activity execution time histogram. Compare the computed average with this monitor element. If the computed average deviates from the true average reported by this monitor element, consider altering the histogram template for the activity execution time histogram, using a set of bin values that are more appropriate for your data.

Usage

Use this statistic to determine the arithmetic mean between arrivals of coordinator activities at nesting level 0 associated with this service subclass, workload, or work class.

The inter-arrival time can be used to determine arrival rate, which is the inverse of inter-arrival time. This average can also be used to determine whether or not the histogram template used for the activity inter-arrival time histogram is appropriate. Compute the average activity inter-arrival time from the activity inter-arrival time histogram. Compare the computed average with this monitor element. If the computed average deviates from the true average reported by this monitor element, consider altering the histogram template for the activity inter-arrival time histogram, using a set of bin values that are more appropriate for your data.

Usage

Use this statistic to determine the arithmetic mean of the lifetime for coordinator activities associated with a service subclass, workload, or work class that completed or aborted.

This statistic can also be used to determine whether or not the histogram template used for the activity lifetime histogram is appropriate. Compute the average activity lifetime from the activity lifetime histogram. Compare the computed average with this monitor element. If the computed average deviates from the true average reported by this monitor element, consider altering the histogram template for the activity lifetime histogram, using a set of bin values that are more appropriate for your data.

Usage

This element can be used to help determine whether or not thresholds on activity lifetime are being effective and can also help to determine how to configure such thresholds.

Usage

Use this statistic to determine the arithmetic mean of the queue time for coordinator activities associated with a service subclass, workload, or work class that completed or aborted.

This statistic can also be used to determine whether or not the histogram template used for the activity queue time histogram is appropriate. Compute the average activity queue time from the activity queue time histogram. Compare the computed average with this monitor element. If the computed average deviates from the true average reported by this monitor element, consider altering the histogram template for the activity queue time histogram, using a set of bin values that are more appropriate for your data.

Usage

This element can be used to help determine whether or not predictive thresholds and work actions that prevent execution are being effective and whether or not they are too restrictive.

Usage

You can use this element to link database system monitor information to other sources of diagnostic information, such as system traces.

Usage

If the peak number of coordinating agents represents too high a workload for this node, you can reduce this upper boundary by changing the max_coordagents configuration parameter.

Usage

This element allows the coordinator partition to be identified for activities or units of work that have records on partitions other than the coordinator.

Usage

Use this element to determine the highest DML activity estimated cost reached on a member for a service class, workload, or work class in the time interval collected.

Usage

• This measurement represents the aggregate for all processors on the system.
• On AIX, this metric is reported for the workload partition (WPAR) and the logical partition (LPAR) on which the DB2 server is running.
• You can use this monitor element along with the related processor timer elements to calculate processor utilization for a specific time interval on the host system. To calculate processor utilization as a percentage, perform the following steps:
  1. Use the ENV_GET_SYSTEM_RESOURCES function at the beginning to the time interval to retrieve the values for the following metrics:
     • cpu_user_t1 = cpu_user
     • cpu_system_t1 = cpu_system
     • cpu_idle_t1 = cpu_idle
     • cpu_wait_t1 = cpu_wait
  2. Repeat the preceding step to determine the timestamps for the same metrics at the end of the time interval for which you want to calculate processor utilization:
     • cpu_user_t2 = cpu_user
     • cpu_system_t2 = cpu_system
     • cpu_idle_t2 = cpu_idle
     • cpu_iowait_t2 = cpu_iowait
  3. Calculate processor utilization using the following formula:

           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1)
     100 × ----------------------------------------------------------
           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1) +
           (cpu_idlet2 - cpu_idlet1) + (cpu_iowaitt2 - cpu_iowaitt1)

Usage

• This measurement represents the aggregate for all processors on the system.
• On AIX, this metric is reported for the workload partition (WPAR) and the logical partition (LPAR) on which the DB2 server is running.
• You can use this monitor element along with the related processor timer elements to calculate processor utilization for a specific time interval on the host system. To calculate processor utilization as a percentage, perform the following steps:
  1. Use the ENV_GET_SYSTEM_RESOURCES function at the beginning to the time interval to retrieve the values for the following metrics:
     • cpu_user_t1 = cpu_user
     • cpu_system_t1 = cpu_system
     • cpu_idle_t1 = cpu_idle
     • cpu_wait_t1 = cpu_wait
  2. Repeat the preceding step to determine the timestamps for the same metrics at the end of the time interval for which you want to calculate processor utilization:
     • cpu_user_t2 = cpu_user
     • cpu_system_t2 = cpu_system
     • cpu_idle_t2 = cpu_idle
     • cpu_iowait_t2 = cpu_iowait
  3. Calculate processor utilization using the following formula:

           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1)
     100 × ----------------------------------------------------------
           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1) +
           (cpu_idlet2 - cpu_idlet1) + (cpu_iowaitt2 - cpu_iowaitt1)

Usage

• This measurement represents the aggregate for all processors on the system.
• On AIX, this metric is reported for the workload partition (WPAR) and the logical partition (LPAR) on which the DB2 server is running.
• You can use this monitor element along with the related processor timer elements to calculate processor utilization for a specific time interval on the host system. To calculate processor utilization as a percentage, perform the following steps:
  1. Use the ENV_GET_SYSTEM_RESOURCES function at the beginning to the time interval to retrieve the values for the following metrics:
     • cpu_user_t1 = cpu_user
     • cpu_system_t1 = cpu_system
     • cpu_idle_t1 = cpu_idle
     • cpu_wait_t1 = cpu_wait
  2. Repeat the preceding step to determine the timestamps for the same metrics at the end of the time interval for which you want to calculate processor utilization:
     • cpu_user_t2 = cpu_user
     • cpu_system_t2 = cpu_system
     • cpu_idle_t2 = cpu_idle
     • cpu_iowait_t2 = cpu_iowait
  3. Calculate processor utilization using the following formula:

           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1)
     100 × ----------------------------------------------------------
           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1) +
           (cpu_idlet2 - cpu_idlet1) + (cpu_iowaitt2 - cpu_iowaitt1)

Usage

Usage

• This measurement represents the aggregate for all processors on the system.
• On AIX, this metric is reported for the workload partition (WPAR) and the logical partition (LPAR) on which the DB2 server is running.
• You can use this monitor element along with the related processor timer elements to calculate processor utilization for a specific time interval on the host system. To calculate processor utilization as a percentage, perform the following steps:
  1. Use the ENV_GET_SYSTEM_RESOURCES function at the beginning to the time interval to retrieve the values for the following metrics:
     • cpu_user_t1 = cpu_user
     • cpu_system_t1 = cpu_system
     • cpu_idle_t1 = cpu_idle
     • cpu_wait_t1 = cpu_wait
  2. Repeat the preceding step to determine the timestamps for the same metrics at the end of the time interval for which you want to calculate processor utilization:
     • cpu_user_t2 = cpu_user
     • cpu_system_t2 = cpu_system
     • cpu_idle_t2 = cpu_idle
     • cpu_iowait_t2 = cpu_iowait
  3. Calculate processor utilization using the following formula:

           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1)
     100 × ----------------------------------------------------------
           (cpu_systemt2 - cpu_systemt1) + (cpu_usert2 - cpu_usert1) +
           (cpu_idlet2 - cpu_idlet1) + (cpu_iowaitt2 - cpu_iowaitt1)

Usage

When returned by the WLM_GET_WORKLOAD_STATS or the WLM_GET_SERVICE_SUBCLASS_STATS function, this monitor element represents the CPU utilization since the last reset of the statistics.

When returned by the MON_SAMPLE_SERVICE_CLASS_METRICS or the MON_SAMPLE_WORKLOAD_METRICS function, this monitor element represents the CPU utilization since the function was executed.

Usage

The dispatcher is effective at prioritizing a service class or workload when that service class or workload demands more CPU resources at a given instant than can be supplied. In such instances, the work executing in the service class or workload spends time queuing to access the CPU resources. It is when this occurs that the dispatcher can give more of the CPU resources to such a service class or workload by reducing how much of the CPU resources it gives to another. A high CPU velocity indicates that the dispatcher can have little effect on improving response times or throughput for this service class at its current level of CPU demand because this demand is already being met. A low CPU velocity indicates that the dispatcher can potentially have a significant effect on improving response times or throughput for this service class or workload at its current level of CPU demand.

Use this element to determine whether the work executing in a service class or workload is spending a relatively large proportion of its time queuing to use the CPU resources. If the CPU velocity for a service class is low and you want to increase it, you can adjust the WLM dispatcher control of the CPU resources by increasing the number of CPU shares or increasing the CPU limit assigned to the service class that is exhibiting a low CPU velocity.

Usage

Use this element to understand which CPUTIME threshold, if any, was applied to the activity.

Usage

Use this element to understand the value of the CPUTIME threshold applied to the activity, if any.

Usage

Use this element to determine if the activity violated the CPUTIME threshold that was applied to the activity.

Usage

Use this element to understand which CPUTIMEINSC threshold, if any, was applied to the activity.

Usage

Use this element to understand the value of the CPUTIMEINSC threshold applied to the activity, if any.

Usage

Use this element to determine if the activity violated the CPUTIMEINSC threshold that was applied to the activity.

Usage

Use this element to determine the amount of CREATE NICKNAME activity against this data source by this federated server instance or an application. CREATE NICKNAME processing results in multiple queries running against the data source catalogs; therefore, if the value of this element is high, you should determine the cause and perhaps restrict this activity.