VMware vRealize True Visibility Suite 1 · Management Pack for IBM DB2 1 The VMware vRealize® True...

Management Pack for IBM DB2

VMware vRealize True Visibility Suite 1.0

You can find the most up-to-date technical documentation on the VMware website at:

https://docs.vmware.com/

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

Copyright ©

2020 VMware, Inc. All rights reserved. Copyright and trademark information.


VMware, Inc. 2

https://docs.vmware.com/http://pubs.vmware.com/copyright-trademark.html

Contents

1 Management Pack for IBM DB2 4

2 System Requirements (IBM DB2) 5Configuring the Management Pack for Monitoring Metrics (IBM DB2) 5

Enabling SSL (IBM DB2) 7

Creating a Least-Privileged User (IBM DB2) 7

3 Installing the Management Pack (IBM DB2) 10

4 Configuring the Management Pack (IBM DB2) 13Creating a Credential (IBM DB2) 13

Creating an Adapter Instance (IBM DB2) 15

Enabling Virtual Machine IOPS Metrics (IBM DB2) 17

Validating Data Collection (IBM DB2) 18

5 Troubleshooting the Management Pack (IBM DB2) 20

6 Using the Management Pack (IBM DB2) 22Resource Kinds and Relationships (IBM DB2) 22

Inventory Tree (Traversal Spec) (IBM DB2) 23

Dashboards (IBM DB2) 24

DB2 Overview 24

DB2 on VM 25

DB2 IOPS 25

DB2 Top-N Queries 26

Views (IBM DB2) 27

Reports (IBM DB2) 28

Analysis Badges and Capacity Definitions (IBM DB2) 29

Alerts (IBM DB2) 30

Metrics (IBM DB2) 37

VMware, Inc. 3

Management Pack for IBM DB2 1The VMware vRealize® True Visibility™ Management Pack for IBM DB2 is an embedded adapter for vRealize Operations (vROps), collecting performance and capacity data from your IBM DB2 environment and providing predictive analytics and real-time information about problems in your infrastructure—all within the vRealize Operations user interface.

Notable Features

The Management Pack for IBM DB2 provides the following notable features:

n 4comprehensive DB2 monitoring dashboards:

n DB2 Overview

n DB2 on VM

n DB2 IOPS

n DB2 Top-N Queries

n 190+ collected metrics for DB2 resources

n Key performance metrics such as average system CPU time, logical data reads, physical data reads, average index write rate, number of current connections, and active applications

n 7 total views providing lists of metrics such as application performance; health, availability, and alert counts; and slowest queries

n 5 exportable reports providing a roll-up of DB2 application, buffer pool, health, overview, and tablespace metrics

n Relationship mapping between databases and VMware virtual infrastructure

n Detailed alerts and recommendations

Release Notes

Version Release Date Description

3.0.0 October 6, 2020 Initial General Availability release for VMware vRealize® True Visibility™

VMware, Inc. 4

System Requirements (IBM DB2) 2Before installing and configuring the Management Pack, ensure your system meets the following requirements:

vRealize Operations Requirements IBM DB2 Requirements

Version(s) vRealize Operations 7.x or 8.x

(Enterprise edition only)

IBM DB2 versions 9.5+

Important A few special configurations are required on your IBM DB2 database in order for the Management Pack to collect metrics. See: Configuring the Management Pack for Monitoring Metrics (IBM DB2).

Connection vROps hostname or IP address

IBM DB2 hostname (i.e., IP or DNS name of IBM DB2 System)

Important If your DB2 database system is set up to use SSL, you must add the DB2 SSL certificate prior to adding your adapter instance. See: Enabling SSL (IBM DB2) for details.

D efault port is 50000 (TCP)

Credentials vROps username/password with access to vRealize Suite API is required

IBM DB2 username/password

Important For least-privileged user requirements, see: Creating a Least-Privileged User (IBM DB2).

This chapter includes the following topics:

n Configuring the Management Pack for Monitoring Metrics (IBM DB2)

n Enabling SSL (IBM DB2)

n Creating a Least-Privileged User (IBM DB2)

Configuring the Management Pack for Monitoring Metrics (IBM DB2)

A few special configurations are required on the DB2 database side in order for the Management Pack to collect metrics correctly.

VMware, Inc. 5

Procedure

1 Enable DB2 configuration parameter HEALTH_MON (i.e., turn on health indicators for instance and database objects).

2 Enable switch for monitoring statements.

3 Set up permissions for Management Pack to query the lock waits administrative view.

4 Enable table monitoring (DFT_MON_TABLE) for the database you are monitoring.

5 To complete the above configurations, run the following commands by Command Line Processor (CLP) at the db2 prompt:

update dbm cfg using HEALTH_MON on

update dbm cfg using DFT_MON_STMT on

update dbm cfg using DFT_MON_LOCK on

update dbm cfg using DFT_MON_TABLE on

update dbm cfg using DFT_MON_BUFPOOL on

6 To check if your changes are effective, run the following command:

db2==> get dbm cfg

The following is the output:

.....

.....

.....

Monitor health of instance and databases (HEALTH_MON) = ON

Default database monitor switches

Buffer pool (DFT_MON_BUFPOOL) = ON

Lock (DFT_MON_LOCK) = ON

Sort (DFT_MON_SORT) = OFF

Statement (DFT_MON_STMT) = ON

Table (DFT_MON_TABLE) = ON

Timestamp (DFT_MON_TIMESTAMP) = ON

Unit of work (DFT_MON_UOW) = OFF

Monitor health of instance and databases (HEALTH_MON) = ON

.....

.....

.....


VMware, Inc. 6

What to do next

Enabling SSL (IBM DB2)

Enabling SSL (IBM DB2)

If your DB2 database system is set up to use SSL, you must add the DB2 SSL certificate prior to your adapter configuration.

Procedure

1 Copy certificate to the vROps host.

2 Log in to vROps host as ‘root’.

] cd /usr/java/default

] bin/keytool -import -keystore lib/security/cacerts -file /path/to/mydb2sslserver.arm

3 Create password when prompted (must be at least 6 characters).

4 Type 'yes' when asked to trust this certificate.

] service vmware-vcops restart collector

What to do next

Enabling Virtual Machine IOPS Metrics (IBM DB2)

Creating a Least-Privileged User (IBM DB2)

This topic outlines the process to create an IBM DB2 least-privileged user (LPU) on Linux/UNIX to use as the monitoring user for the management pack.

For the purposes of this management pack, we chose the SYSMON group as noted in this IBM Knowledge Center article because it has the least permissions of the four groups listed that provide access to snapshot monitoring data.

Procedure

1 Starting as the root user on Linux/UNIX, run the following command:

groupadd

useradd -g

passwd

Example:


VMware, Inc. 7

http://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.sql.rtn.doc/doc/r0022019.html

IMPORTANT:

groupadd sysmong

useradd -g sysmong db2lpu

passwd db2lpu

2 Switch to the instance master user (in the following example db2inst1 for instance 1):

su - db2inst1

3 Grant the necessary permissions by setting the OS group as the SYSMON_GROUP:

db2 update dbm cfg using SYSMON_GROUP

Example:

IMPORTANT:

db2 update dbm cfg using SYSMON_GROUP SYSMONG

4 Exit from the master user back to root:

exit

5 Reboot the server, then log in again as root. Copy the .bashrc from master user to in order to get the environment variables that make DB2 work:

Example (using same variables as before):

cp -f /home/db2inst1/.bashrc /home/db2lpu/

chown db2lpu:sysmong /home/db2lpu/.bashrc

6 Test permissions:

a Log in as .

b Connect to a database.

Example (connecting to sample below):

db2 connect to sample

7 Enter the DB2 shell:

db2

8 Run our queries from the DB2 shell to test that they all return successfully:

SELECT coalesce((sum(DATA_LOGICAL_READS) - sum(DATA_PHYSICAL_READS)) / nullif(cast(sum(DATA_LOGICAL_READS) as float), 0), 1) * 100 as buffer_pool_data_hit from SYSIBMADM.BP_HITRATIO group by db_name, snapshot_timestamp

SELECT COUNT(locks_waiting) as applications_waiting_on_locks from SYSIBMADM.SNAPAPPL WHERE LOCKS_WAITING > 0

SELECT LOG_UTILIZATION_PERCENT AS log_utilization from SYSIBMADM.LOG_UTILIZATION


VMware, Inc. 8

SELECT TOTAL_CONS, DEADLOCKS, LOCK_TIMEOUTS, APPLS_IN_DB2 FROM SYSIBMADM.SNAPDB

SELECT LOCAL_CONS, REM_CONS_IN FROM SYSIBMADM.SNAPDBM

9 Optional: To test if your user is in the SYSMON_GROUP without queries, you can use the following OS command:

db2pd

The following are some useful permission queries that may help with debugging:

SELECT AUTHORITY, D_USER, D_GROUP, D_PUBLIC, ROLE_USER, ROLE_GROUP, ROLE_PUBLIC, D_ROLE FROM TABLE (SYSPROC.AUTH_LIST_AUTHORITIES_FOR_AUTHID ('DB2LPU', 'U') ) AS T ORDER BY AUTHORITY

SELECT AUTHORITY, D_USER, D_GROUP, D_PUBLIC, ROLE_USER, ROLE_GROUP, ROLE_PUBLIC, D_ROLE >FROM TABLE (SYSPROC.AUTH_LIST_AUTHORITIES_FOR_AUTHID ('SYSMONG', 'G') ) AS T ORDER BY AUTHORITY

What to do next

Chapter 3 Installing the Management Pack (IBM DB2)


VMware, Inc. 9

Installing the Management Pack (IBM DB2) 3The Management Pack for IBM DB2 is installed using a .pak file.

1 Log in to vRealize Operations as an admin user.

2 From the top navigation bar, select Administration. In the left panel, the default Solutions

view will be selected. In the right panel, click the Add icon.

Note If you are using vROps 7.5, Solutions will have two subcategories: Configuration and Repository. Select Repository and scroll down to Other Management Packs and select Add a Management Pack to install a new management pack. Refer to the second screenshot below if needed.

vROps versions 7 and lower:

vROps version 7.5:

VMware, Inc. 10

3 The Add Solution window will appear. Browse to the location of the saved .pak file, then click Upload.


VMware, Inc. 11

4 Click Next when the upload has finished.

5 Read and accept the End User License Agreement (EULA), then click Next.

6 Click Finish when the installation process is complete.


VMware, Inc. 12

Configuring the Management Pack (IBM DB2) 4Configuring the Management Pack for IBM DB2 in vRealize Operations includes the following required tasks:

n Creating a Credential (IBM DB2)

n Creating an Adapter Instance (IBM DB2)

n Enabling Virtual Machine IOPS Metrics (IBM DB2)

Note In addition, you may want to perform the following optional task to further configure the Management Pack for your specific needs:

n Validating Data Collection (IBM DB2) (optional)



n Creating an Adapter Instance (IBM DB2)

n Enabling Virtual Machine IOPS Metrics (IBM DB2)

n Validating Data Collection (IBM DB2)

Creating a Credential (IBM DB2)

One of the required configuration tasks for the Management Pack is to create a set of credentials in vROps.

Prerequisites

n Chapter 3 Installing the Management Pack (IBM DB2)

VMware, Inc. 13

Procedure

1 From the top navigation bar, select Administration . In the left panel, expand the Management category and select Credentials.

2 Click the Add icon. In the Manage Credential window that appears, enter the following information:

Results

n Credential Name:A name for this set of Management Pack credentials

n Username: Username for your DB2 system


VMware, Inc. 14

n Password: Password for your DB2 system

n vRealize Username: vRealize Operations Username

n vRealize Password: Password associated with vRealize Operations Username

Note The vRealize user name and password must have access to vRealize Suite API.

What to do next

Creating an Adapter Instance (IBM DB2)


Before you can begin using the Management Pack, you must create an adapter instance to identify the host from which the Management Pack will retrieve data.

Prerequisites

n Chapter 3 Installing the Management Pack (IBM DB2)


Procedure

1 From the top navigation bar, select Administration. In the right panel, the Solutions view will be displayed.

2 Select DB2 Adapter from the Solutions list on the right.

3 Click the Configure icon. The Manage Solution window will appear.

Note Click the Add icon above the Instance Name list on the left to create multiple adapter instances.


VMware, Inc. 15

4 In the Manage Solution window, enter the following information:

a Instance Settings:

n Display Name: Enter a name for this particular instance of the management pack.

n Description: Optional field, but it can be helpful to describe multiple adapter instances of the management pack.

b Basic Settings:

n Database Name(s): Enter the name of your DB2 database

n Host: Enter the hostname (or IP address) of your DB2 database.

n Port: Enter the port to connect to; default port for the first database instance in DB2 is 50000.

n Credential: Select the credential you created when Creating a Credential (IBM DB2).


VMware, Inc. 16

c Advanced Settings:

n Collector: The collector you select determines which vRealize Operations Manager collector is used to manage the adapter processes. Default Collector/Group is automatically selected. Click the drop-down menu if you want to run the collection on a different node.

5 Click Test Connection to test the configured connection information.

6 Click Save Settings and Close to save your adapter instance.

What to do next

To validate data collection, see: Validating Data Collection (IBM DB2).

Enabling Virtual Machine IOPS Metrics (IBM DB2)

To enable Virtual Machine IOPs metrics that populate the DB2 IOPS Dashboard within the Management Pack, you must enable them via policy within vRealize Operations.

Prerequisites

n The VMware vSphere Management Pack must be installed.

n The IBM DB2 Management Pack must be installed.

Procedure

1 From the top navigation bar, select Administration, then click Policies.

2 Take note of the active policy listed in the Active tab, then click the Policy Library tab.

3 Select the active policy from the list.

Note If a custom policy from another Management Pack is not your current active policy, the default will be something like ‘vSphere Solution’s Default Policy ()’.

4 Click the Edit icon.

5 Select 2. Select Base Policies.

6 Select Blue Medora Default Policy for DB2 Adapter under Override settings from additional policies.

7 Click Apply, then Save.


VMware, Inc. 17

Results

What to do next

Creating a Credential (IBM DB2)

Validating Data Collection (IBM DB2)

After you add an adapter instance, you will most likely want to validate the data that it collects in vROps. Wait until one collection cycle is complete and the Collection Status for the adapter instance on the Solutions page shows as "Data Receiving".

Prerequisite


Procedure

1 From the top navigation bar, select Environment.

2 In the left panel, select All Objects , then expand the DB2 Adapter objects list.

3 Select a resource from the list, then click the All Metrics tab to select metrics and validate values against the data source.


VMware, Inc. 18

What to do next

To learn more about using the Management Pack, see: Chapter 6 Using the Management Pack (IBM DB2).


VMware, Inc. 19

Troubleshooting the Management Pack (IBM DB2) 5Once you have finished Chapter 3 Installing the Management Pack (IBM DB2) and Chapter 4 Configuring the Management Pack (IBM DB2), check the Collection State and Collection Status for the adapter instance on the Solutions page. If they show as Not Collecting or No Data Receiving, respectively, the following troubleshooting topics can help you diagnose and correct common problems with your adapter instance.

n Test Connection Errors

n Adapter and Collector Log Files

Test Connection Errors

When Creating an Adapter Instance (IBM DB2), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

Wrong Credentials

Error Message: Unable to establish a valid connection to target system. Connection authorization failure occurred. Reason: User ID or Password invalid.

Action: Ensure the correct IBM DB2 system and vRealize Operations User Name and Password was entered when adding your adapter instance.

Wrong Host

Error Message: Unable to establish a valid connection to target system. Required property is unknown host. Ensure the correct IBM DB2 Management IP or DNS name for you IBM DB2 System was entered.

Action: Ensure the correct hostname or IP address was entered when adding your adapter instance.

Wrong Port

Error Message: Unable to establish a valid connection to target system. Connection authorization failure occurred. Error opening socket server on port with message: Connection refused.

Action: Check your DB2 database system and ensure the connection port number matches the port number entered (if other than default of 50000) when adding your adapter instance.

VMware, Inc. 20

Wrong Database

Error Message: Connection authorization failure occurred. The application server rejected establishment of the connection. An attempt was made to access a database, , which was either not found or does not support transactions.

Action: Ensure the database name(s) provided match the DB2 system. Multiple databases should be separated by commas in the Manage Solution window.

Adapter and Collector Log Files

You can review adapter errors in the adapter and collector log files, which can be viewed in the vROps UI or in an external log viewer.

n Adapter log files are located in the $VCOPS_BASE/user/log/adapters/DB2Adapter/ folder.

n Collector log files are located in the $VCOPS_BASE/user/log/ folder.

To set the base log level for the collector in vROps:

1 Navigate to Administration > Logs .

2 Expand the MASTER folder, then select the COLLECTOR folder.

3 Click the Edit Properties icon.

4 In the Root logger level drop-down menu, select the desired option:

n The default logging level is warning.

n To troubleshoot issues, set the logging level to info.

n To view detailed messages, including micro steps, queries, and returned results, set the logging level to debug.

Note If you set the logging level to debug , log files can become large very quickly. Set the logging level to debug only for short periods of time.

For more information about viewing log files and modifying levels, refer to the vROps online help.


VMware, Inc. 21

Using the Management Pack (IBM DB2) 6The Management Pack for IBM DB2 includes the following out-of-the-box features, harnessing the power of the vRealize Operations user interface:

n Resource Kinds and Relationships (IBM DB2)

n Inventory Tree (Traversal Spec) (IBM DB2)

n Dashboards (IBM DB2)

n Views (IBM DB2)

n Reports (IBM DB2)

n Analysis Badges and Capacity Definitions (IBM DB2)

n Alerts (IBM DB2)

n Metrics (IBM DB2)


n Resource Kinds and Relationships (IBM DB2)

n Inventory Tree (Traversal Spec) (IBM DB2)

n Dashboards (IBM DB2)

n Views (IBM DB2)

n Reports (IBM DB2)

n Analysis Badges and Capacity Definitions (IBM DB2)

n Alerts (IBM DB2)

n Metrics (IBM DB2)

Resource Kinds and Relationships (IBM DB2)

The Management Pack for IBM DB2 creates Resource Kinds and Relationships (associations) for critical resources in your IBM DB2 environment.

VMware, Inc. 22

Resource Kinds

Performance, health, and availability data are collected for the following IBM DB2 resource kinds:

1 DB2 Database

2 DB2 HADR (High Availability Disaster Recovery)

3 DB2 Slow Query

Relationships

Relationships among discovered resources are also created by the Management Pack. The hierarchical structure of those relationships is depicted in the diagram below.

IBM DB2 Relationships Diagram

Inventory Tree (Traversal Spec) (IBM DB2)

The Inventory Tree (Traversal Spec) feature in vROps allows you to easily navigate your IBM DB2 environment. The hierarchical structure implicitly shows relationships among resources and enables quick drill-downs to root-cause issues.

To access your IBM DB2 Inventory Tree, select Environment from the top navigation bar, then select IBM DB2 from the left panel. Click on a resource from the Inventory Tree to populate details about the resource on the right.


VMware, Inc. 23

Example Inventory Tree - IBM DB2 Icon Legend

Database

HADR (High Availability Disaster Recovery)

Slow Query

Dashboards (IBM DB2)

Dashboards are the primary feature for monitoring and troubleshooting IBM DB2 from within vRealize Operations.

The following dashboards are included in the Management Pack for IBM DB2:

n DB2 Overview

n DB2 on VM

n DB2 IOPS

n DB2 Top-N Queries

DB2 Overview

TheDB2 Overviewdashboard displays heat maps depicting overall health of DB2 databases and HADRs.


VMware, Inc. 24

DB2 on VM

TheDB2 on VMdashboard allows the user to select a DB2 database to view key performance indicators (KPIs) for the database and related Virtual Machine.

DB2 IOPS


VMware, Inc. 25

The DB2 IOPS dashboard allows the user to select a DB2 database to view IO stats for the related database, Virtual Machine, and related Datastore.

Important To enable IOPs metrics for Virtual Machines, you must modify the active policy within vROps. For instructions, see: Enabling VM IOPS Metrics.

DB2 Top-N Queries

TheDB2 Top-N Queriesdashboard allows the user to select a DB2 database to view a ranking of the Top 10 slowest queries. The dashboard also allows you to select individual queries from the heat map slowest queries selector to view performance metrics for the selected query.


VMware, Inc. 26

Views (IBM DB2)

The Management Pack for IBM DB2 creates views that allow the user to view statistics of metrics for IBM DB2 resources. The views help give a broad picture of the entire system, as opposed to a more in depth view.

The following views are available in the Management Pack:

View Type Description

DB2 Application Performance List Provides a list of application performance metrics.

DB2 Buffer Pool Metrics List Provides a list of buffer pool metrics.

DB2 Health, Availability, & Alert Count List Provides a list of DB2 health, availability, and alert counts.

DB2 I/O Performance List Provides a list of I/O performance metrics.

DB2 KPIs List Provides a list of DB2 key performance metrics.

DB2 Slowest Queries List Provides a list of the slowest DB2 queries.

DB2 Tablespace Metrics List Provides a list of tablespace metrics.

To access the Management Pack views:

1 Navigate to Environment > All Objects > DB2 .

2 Double-click on the desired object (resource).


VMware, Inc. 27

3 Select the Details tab, then Views.

The available views for that resource are listed and can be selected.

Accessing Views

Reports (IBM DB2)

The Management Pack for IBM DB2 contains out-of-the-box report(s)—which contain one or more Views (IBM DB2)—that you can export and easily share with key stakeholders in either .pdf or .csv formats.

The following reports are available in the Management Pack:

Report Description

DB2 Application Provides a roll-up of DB2 application metrics.

DB2 Buffer Pool Provides a roll-up of DB2 buffer pool metrics.

DB2 Health Provides a roll-up of DB2 health metrics.

DB2 Overview Provides a roll-up of DB2 overview metrics.

DB2 Tablespace Provides a roll-up of DB2 tablespace metrics.

To access Management Pack reports:

1 Navigate to Environment > All Objects > DB2.

2 Double-click on the desired object (resource).

3 Select the Reports tab, then Report Templates.

The available report(s) for the selected resource are listed and can be selected.

To run a selected report, click the Run Template icon.


VMware, Inc. 28

Accessing Reports

Analysis Badges and Capacity Definitions (IBM DB2)

Using the predictive analytics capabilities of vRealize Operations Analysis Badges through capacity definitions, the Management Pack for IBM DB2 populates capacities as indicated in the table below.

Capacity Definitions List

Container Use in Workload

DB2 Database

vRealize Computed Database Capacity yes

vRealize Computed Application Capacity yes

Analysis Badge Example


VMware, Inc. 29

Alerts (IBM DB2)

The Management Pack for IBM DB2 creates alerts (and in some cases provides recommended actions) based on various symptoms it detects in your IBM DB2 Environment. See the table below for the list of alerts available in the Management Pack.

Alerts List


VMware, Inc. 30

Name Description Symptom Recommendation

Database Operational State

The state of the database can restrict activity or tasks that can be performed. The state can be one of the following: ACTIVE, QUIESCE PENDING, QUIESCED, or ROLLFORWARD. A change from Active to another state may generate an Attention alert.

Database Operational State

Refer to the DB2 Information Center for information on these states.

Shared Sort Memory Utilization

A sample event has been detected

Shared Sort Memory Utilization

Sorting is considered healthy if there is sufficient heap space in which to perform sorting and sorts do not overflow unnecessarily. This indicator tracks the utilization of the shared sort memory. The SHEAPTHRES_SHR database configuration parameter is a soft limit. If the allocation is close to the limit, an alert may be generated. The indicator is calculated using the formula: (db.sort_shrheap_allocated / SHEAPTHRES_SHR) * 100. The Maximum Shared Sort Memory Used snapshot monitor element maintains a shared sort memory high-water mark for the database. The value of this indicator, shown in the Additional Information, indicates the maximum amount of shared sort memory that has been in use at any one point in time since the database has been active. This value can be used to help determine an appropriate value for the shared sort memory threshold. This health indicator's threshold checking is not enabled by default in new installations where self tuning memory is expected to be used.

Percentage of Sorts That Overflowed


Percentage of Sorts That Overflowed

Sorting is considered healthy if there is sufficient heap space in which to perform sorting and sorts do not overflow unnecessarily. Sorts that overflow to disk can cause significant performance degradation. Some level of sort overflows however, may be unavoidable in such cases where the size of the sort exceeds physical memory or the maximum available memory for the database. If a high percentage of sorts spill, an alert may be generated. The indicator is calculated using the formula: (db.sort_overflows / db.total_sorts)*100. The system monitor data element db.sort_overflows is the total number of sorts that ran out of sort heap and may have required disk space for temporary storage. The data element db.total_sorts is the total number of sorts that have been executed. This health indicator's threshold checking is not enabled by default in new installations where self tuning memory is expected to be used.


VMware, Inc. 31


Long Term Shared Sort Memory Utilization


Long Term Shared Sort Memory Utilization

Sorting is considered healthy if there is sufficient heap space in which to perform sorting and sorts do not overflow unnecessarily. This indicator tracks an over-configured shared sort heap, whose memory could be better used somewhere else in DB2. An alert may be generated when the percentage usage is low. The indicator is calculated using the formula: (db.max_shr_sort_mem / SHEAPTHRES_SHR)*100. This health indicator's threshold checking is not enabled by default in new installations where self tuning memory is expected to be used.

Log Utilization A sample event has been detected

Log Utilization This indicator tracks the total amount of active log space used in bytes in the database. Log utilization is measured as the percentage of space consumed, where a high percentage may generate an alert. The indicator is calculated using the formula: (db.total_log_used / (db.total_log_used + db.total_log_available))*100. The values for the log-related database configuration parameters, shown in the additional information, display the current allocations for logs. The additional information also includes the application id for the application which has the oldest active transaction. This application can be forced to free up log space.

Log Filesystem Utilization


Log Filesystem Utilization

Log Filesystem Utilization tracks the fullness of the filesystem on which the transaction logs reside. DB2 may not be able to create a new log file if there is no room on the filesystem. Log utilization is measured as the percentage of space consumed. If the amount of free space in the filesystem is minimal (i.e. high percentage for utilization), an alert may be generated. The indicator is calculated using the formula: (fs.log_fs_used / fs.log_fs_total)*100 where fs is the filesystem on which the log resides. The values for the log-related database configuration parameters, shown in the additional information, display the current allocations for logs. The additional details also shows if log archiving is enabled. If Block on Log Disk Full, shown in the additional details, is set to yes and utilization is at 100%, you should resolve any alerts as soon as possible to limit the impact to applications which cannot commit transactions until the log file is successfully created.

Deadlock Rate A sample event has been detected

Deadlock Rate Deadlock rate tracks the rate at which deadlocks are occurring in the database and the degree to which applications are experiencing contention problems. Deadlocks may be caused by the following situations: o Lock escalations are occurring for the database o An application may be locking tables explicitly when system- generated row locks may be sufficient o An application may be using an inappropriate isolation level when binding o Catalog tables are locked for repeatable read o Applications are getting the same locks in different orders, resulting in deadlock. The indicator is calculated using the formula: (db.deadlocks - db.deadlocks) where 't' is the current snapshot and 't-1' is the last snapshot "5" "minutes" ago. A high rate of deadlocks results in a greater degree of contention which may generate an alert.


VMware, Inc. 32


Lock List Utilization


Lock List Utilization

This indicator tracks the amount of lock list memory that is being used. There is one lock list per database and it contains the locks held by all applications concurrently connected to the database. There is a set limit on lock list memory. Once the limit is reached, performance degrades because of the following situations: o Lock escalation converts row locks to table locks, thereby reducing concurrency on shared objects in the database. o More deadlocks between applications can occur since applications are waiting for a limited number of table locks. As a result, transactions are rolled back. An error is returned to the application when the maximum number of lock requests has reached the limit set for the database. The indicator is calculated using the formula: (db.lock_list_in_use / (LOCKLIST * 4096)) * 100. Utilization is measured as a percentage of memory consumed, where a high percentage represents an unhealthy condition. This health indicator's threshold checking is not enabled by default in new installations where the self tuning memory feature is expected to be used.

Lock Escalation Rate


Lock Escalation Rate

This indicator tracks the rate at which locks have been escalated from row locks to a table lock thereby impacting transaction concurrency. 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. The amount of lock list space available is determined by the MAXLOCKS and LOCKLIST database configuration parameters. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, the application uses the space in the lock list allocated for other applications. There is one lock list per database and it contains the locks held by all applications concurrently connected to the database. When the entire lock list is full an error occurs. The indicator is calculated using the formula: (db.lock_escals - db.lock_escals) where 't' is the current snapshot and 't-1' is the last snapshot "5" "minutes" ago. A high rate of deadlocks results in a greater degree of contention which may generate an alert. This health indicator's threshold checking is not enabled by default in new installations where the self tuning memory feature is expected to be used.

Percentage of Applications Waiting on Locks


Percentage of Applications Waiting on Locks

This indicator measures the percentage of all currently executing applications that are waiting on locks. A high percentage can indicate that applications are experiencing concurrency problems which can negatively affect performance. The indicator is calculated using the formula: (db.locks_waiting / db.appls_cur_cons) *100). This health indicator's threshold checking is not enabled by default in new installations where the self tuning memory feature is expected to be used.


VMware, Inc. 33


Package Cache Hit Ratio


Package Cache Hit Ratio

The hit ratio is a percentage indicating how well the package cache is helping to avoid reloading packages and sections for static SQL from the system catalogs as well as helping to avoid recompiling dynamic SQL statements. A high ratio indicates it is successful in avoiding these activities. The indicator is calculated using the formula: (1-(db.pkg_cache_inserts/db.pkg_cache_lookups))*100. This health indicator's threshold checking is not enabled by default in new installations where the self tuning memory feature is expected to be used.

Catalog Cache Hit Ratio


Catalog Cache Hit Ratio

The hit ratio is a percentage indicating how well the catalog cache is helping to avoid actual accesses to the catalog on disk. A high ratio indicates it is successful in avoiding actual disk I/O accesses. The indicator is calculated using the formula: (1-(db.cat_cache_inserts/db.cat_cache_lookups))*100.

Shared Workspace Hit Ratio


Shared Workspace Hit Ratio

he hit ratio is a percentage indicating how well the shared SQL workspace is helping to avoid having to initialize sections for SQL statements that are about to be executed. A high ratio indicates it is successful in avoiding this action. The indicator is calculated using the formula: (1-(db.shr_workspace_section_inserts/db.shr_workspace_section_lookups))*100.

Database Heap Utilization


Database Heap Utilization

This indicator tracks the consumption of the monitor heap memory, based on the memory pool with the ID SQLM_HEAP_DATABASE. The utilization is calculated using the formula (db.pool_cur_size / db.pool_max_size) * 100 for the Memory Pool Identifier SQLM_HEAP_DATABASE. Once this percentage reaches the maximum, 100%, queries and operations may fail because there is no heap available.

Reorganization Required


Reorganization Required

This health indicator tracks the need to reorganize tables or indexes within a database. Tables or all indexes defined on a table require reorganization to eliminate fragmented data. The reorganization is accomplished by compacting the information and reconstructing the rows or index data. This may result in a performance improvement and space in the table or indexes being freed. The tables considered by this health indicator can be limited using an SQL query. The scope in the additional information displays the subselect clause on system tables for this query. Refer to the DB2 Information Center for how to update this query. An attention alert might be generated to indicate that reorganization is required. Reorganization can be automated by setting the AUTO_REORG database configuration parameter to ON. If automatic reorganization is enabled, the attention alert indicates that one or more automatic reorganizations could not complete successfully. Refer to the collection details of this health indicator for the list of objects that need attention.


VMware, Inc. 34


HADR Operational status


HADR Operational status

This health indicator tracks the DB2 High Availability Disaster Recovery (HADR) operational state of the database. The state between primary and standby servers can be one of the following: CONNECTED, CONGESTED or DISCONNECTED. A change from CONNECTED to another state might generate an Attention alert. Refer to the DB2 Information Center for information on these states.

HADR Log Delay


HADR Log Delay

This health indicator tracks the current average delay (in minutes) between the data changes on the primary database and the replication of those changes on the standby database. The large delay value represents a possibility of a data loss in case of failover when a failure on primary occurs. Moreover, the large delay value may also mean longer downtime when takeover is required, since the standby is not yet a failover candidate, as the current primary is ahead of the standby.

Database Backup Required


Database Backup Required

This health indicator tracks the need for a backup on the database. Backups should be taken regularly as part of a recovery strategy to protect your data against the possibility of loss in the event of a hardware or software failure. This health indicator determines when a database backup is required based on the time elapsed and amount of data changed since the last backup. Refer to the DB2 Information Center for information about how to update these settings. An attention alert might be generated to indicate that a database backup is required. Database backups can be automated by setting the AUTO_DB_BACKUP database configuration parameter to ON. If automatic database backups are enabled

Nickname Status


Nickname Status

This health indicator checks all of the nicknames defined in a federated database to determine if there are any invalid nicknames. A nickname may be invalid if the data source object was dropped or changed or if the user mapping is incorrect. An attention alert might be generated if any nicknames defined in the federated database are invalid. Refer to the collection details of this health indicator for the list of objects that need attention.

Data Source Server Status


Data Source Server Status

This health indicator checks all of the data source servers defined in a federated database to determine if any are unavailable. A data source server may be unavailable if the data source server was stopped, no longer exists, or was incorrectly configured. An attention alert might be generated if any data source servers defined in the federated database are invalid. Refer to the collection details of this health indicator for the list of objects that need attention.


VMware, Inc. 35


Statistics Collection Required


Statistics Collection Required

This health indicator tracks the need to collect statistics for tables and their indexes within a database. Tables and all indexes defined on a table require statistics to improve query execution time. The tables considered by this health indicator can be limited using an SQL query. The scope in the additional information displays the subselect clause on system tables for this query. Refer to the DB2 Information Center on how to update this query. An attention alert may be generated to indicate that statistics collection is required. Statistics can be automatically collected by setting the AUTO_RUNSTATS database configuration parameter to ON. If automatic statistics collection is enabled, the attention alert indicates that one or more automatic statistics collection actions could not complete successfully. Refer to the collection details of this health indicator for the list of objects that need attention.

Database Automatic Storage Utilization


Database Automatic Storage Utilization

This health indicator tracks the consumption of storage for the defined database storage paths. When automatic storage table spaces are created, containers will be allocated automatically for these table spaces on the database storage paths. If there is no more space on any of the filesystems on which the database storage paths are defined, automatic storage table spaces will be unable to increase in size and may become full. This indicator is calculated using the formula: (db.auto_storage_used / db.auto_storage_total) * 100 where db.auto_storage_used and db.auto_storage_total are the sum of used and total space respectively across all physical filesystems identified in the list of database storage paths. Database automatic storage path utilization is measured as a percentage of the space consumed on the database storage path filesystems, where a high percentage indicates less than optimal function for this indicator. The calculation of time remaining to fullness in the additional information is a prediction of how much time is remaining until all free space is consumed.

Table Space Operational State


Table Space Operational State

The state of a table space can restrict activity or tasks that can be performed. A change from normal to another state might generate an Attention alert. For a complete list of possible table space states, refer to the DB2 Information Center.


VMware, Inc. 36


Table Space Utilization


Table Space Utilization

This health indicator tracks the consumption of storage for each DMS table space. The DMS table space is considered full when all containers are full. If automatic resize is enabled on the table space this alert condition may correct itself when the table space resizes. The indicator is calculated using the formula: (ts.used / ts.useable) * 100 where ts.used and ts.useable are the system monitor data elements Used Pages in Table Space and Useable Pages in Table Space, respectively. Table space utilization is measured as the percentage of space consumed, where a high percentage indicates less than optimal function for this indicator. The short term and long term growth rates, included in the additional information for this indicator, can be used to determine if current rate of growth is a short term aberration or consistent with longer term growth. The calculation of time remaining to fullness in the additional information is a prediction of how much time is remaining until all free space is consumed.

Table Space Automatic Resize Status


Table Space Automatic Resize Status

This health indicator identifies whether or not tablespace resize operations are succeeding for DMS tablespaces which have automatic resize enabled. When a DMS tablespace with automatic resize enabled fails to increase in size it is effectively full. This condition may be due to lack of free space on the filesystems on which the tablespace containers are defined, or a result of the tablespace automatic resize settings. For example, the defined maximum size may have been reached, or the increase amount may be set too high to be accommodated by the remaining free space. Refer to the additional information for details about the tablespace and the automatic resize settings.

Automatic Resize Table Space Utilization


Automatic Resize Table Space Utilization

This health indicator tracks the consumption of table space storage for each automatic resize DMS table space on which a maximum size has been defined. The DMS table space is considered full when the maximum size has been reached. The indicator is calculated using the formula: ((ts.used * ts.page_size) / ts.max_size) * 100 where ts.used, ts.page_size and ts.max_size are the system monitor data elements Used Pages in Table Space, Table Space Page Size and Maximum Table Space Size, respectively. Automatic resize DMS Table Space utilization is measured as a percentage of the maximum table space storage consumed. A high percentage indicates the table space is approaching fullness. The short term and long term growth rates, included in the additional information for this indicator, can be used to determine if current rate of growth is a shot term aberration or consistent with long term growth. The calculation of time remaining to fullness in the additional information is a prediction of how much time there is remaining until the maximum size has been reached.

Metrics (IBM DB2)


VMware, Inc. 37

The Management Pack for IBM DB2 collects the metrics listed in the table below, according to IBM DB2 resource kinds.

Download metrics list as .csv file

Resource Kind Resource Group Resource Attribute Attribute Type

DB2 Slow Query Top N Average Execution Time double

DB2 Slow Query Top N Average User CPU Time double

DB2 Slow Query Top N Average System CPU Time double

DB2 Slow Query Top N Rows Read double

DB2 Slow Query Top N Rows Written double

DB2 Slow Query Top N Number of Executions double

DB2 Slow Query Top N Query Statement string

DB2 HADR HADR Connect Status string

DB2 HADR HADR Connect Time string

DB2 HADR HADR Heartbeat double

DB2 HADR HADR Local Host string

DB2 HADR HADR Remote Host string

DB2 HADR HADR Remote Instance string

DB2 HADR HADR Remote Service double

DB2 HADR HADR Role string

DB2 HADR HADR State string

DB2 HADR HADR Sync Mode string

DB2 HADR HADR Timeout double

DB2 Database Tablespace Extent Size double

DB2 Database Tablespace Number of Containers double

DB2 Database Tablespace Page Size double

DB2 Database Tablespace Prefetch Size double

DB2 Database Tablespace Tablespace Free Pages double

DB2 Database Tablespace Tablespace State string

DB2 Database Tablespace Tablespace Total Pages double

DB2 Database Tablespace Tablespace Type string

DB2 Database Tablespace Tablespace Usable Pages double

DB2 Database Tablespace Tablespace Used Pages double

DB2 Database Tablespace Tablespace Utilization double

DB2 Database Tablespace Number of Ranges double

DB2 Database Tablespace Bufferpool Identifier double

DB2 Database Buffer Pool Performance Buffer Pool Hit Ratio double


VMware, Inc. 38

https://s3.amazonaws.com/docs.bluemedora.com/vROps/IBM-DB2/Content/Resources/Images/db2_metric_list.csv


DB2 Database Buffer Pool Performance Logical Data Reads double

DB2 Database Buffer Pool Performance Logical Index Reads double

DB2 Database Buffer Pool Performance Physical Data Reads double

DB2 Database Buffer Pool Performance Physical Index Reads double

DB2 Database Buffer Pool Performance Pool Asynchronous Data Reads double

DB2 Database Buffer Pool Performance Pool Asynchronous Index Reads double

DB2 Database Buffer Pool Performance Pool Asynchronous Data Writes double

DB2 Database Buffer Pool Performance Pool Asynchronous Index Writes double

DB2 Database Buffer Pool Performance Pool Asynchronous Read Time double

DB2 Database Buffer Pool Performance Pool Asynchronous Write Time double

DB2 Database Buffer Pool Performance Pool Data Writes double

DB2 Database Buffer Pool Performance Pool Index Writes double

DB2 Database Buffer Pool Performance Pool Read Time double

DB2 Database Buffer Pool Performance Pool Write Time double

DB2 Database Memory Pool Memory Pool Utilization double

DB2 Database Performance Current Database Size double

DB2 Database Performance Allocated Database Size double

DB2 Database Performance Logical Location of Database string

DB2 Database Performance Pool Asynchronous Writes double

DB2 Database Performance Buffer Pool Data Hit Ratio double

DB2 Database Performance Buffer Pool Hit Ratio double

DB2 Database Performance Buffer Pool Index Hit Ratio double

DB2 Database Performance Logical Data Reads double

DB2 Database Performance Logical Index Reads double

DB2 Database Performance Physical Data Reads double

DB2 Database Performance Physical Index Reads double

DB2 Database Performance Percentage of Applications Waiting on Locks double

DB2 Database Performance Number of Applications Waiting on Locks double

DB2 Database Performance Average Lock Wait Time double

DB2 Database Performance Commit SQL Statements double

DB2 Database Performance Connection Time string

DB2 Database Performance Physical Disk Location of Database string

DB2 Database Performance Number of Deadlocks double

DB2 Database Performance Dynamic SQL Statements double

DB2 Database Performance Failed SQL Statements double


VMware, Inc. 39


DB2 Database Performance Number of Exclusive Lock Escalations double

DB2 Database Performance Number of Internal Rollbacks double

DB2 Database Performance Number of Internal Deadlock Rollbacks double

DB2 Database Performance Last Reset double

DB2 Database Performance Number of Lock Escalations double

DB2 Database Performance Total Locklist Memory in Use double

DB2 Database Performance Number of Lock Timeouts double

DB2 Database Performance Total Lock Wait Time double

DB2 Database Performance Number of Locks Held double

DB2 Database Performance Number of Lock Waits double

DB2 Database Performance Pool Asynchronous Data Reads double

DB2 Database Performance Pool Asynchronous Data Writes double

DB2 Database Performance Pool Asynchronous Index Reads double

DB2 Database Performance Pool Asynchronous Index Writes double

DB2 Database Performance Pool Asynchronous Read Time double

DB2 Database Performance Pool Asynchronous Write Time double

DB2 Database Performance Pool Synchronous Data Reads double

DB2 Database Performance Pool Synchronous Data Writes double

DB2 Database Performance Pool Synchronous Index Reads double

DB2 Database Performance Pool Synchronous Index Writes double

DB2 Database Performance Pool Data Writes double

DB2 Database Performance Pool Index Writes double

DB2 Database Performance Pool Data Logical Reads double

DB2 Database Performance Pool Data Physical Reads double

DB2 Database Performance Pool Index Logical Reads double

DB2 Database Performance Pool Index Physical Reads double

DB2 Database Performance Pool Read Time double

DB2 Database Performance Pool Write Time double

DB2 Database Performance Rollback SQL Statements double

DB2 Database Performance Static SQL Statements double

DB2 Database Performance Number of Current Connections double

DB2 Database Performance Deadlock Rate double

DB2 Database Performance Commit SQL Statements Rate double

DB2 Database Performance Dynamic SQL Statements Rate double

DB2 Database Performance Exclusive Lock Escalation Rate double


VMware, Inc. 40


DB2 Database Performance Failed SQL Statements Rate double

DB2 Database Performance Internal Deadlock Rollbacks Rate double

DB2 Database Performance Lock Escalation Rate double

DB2 Database Performance Lock Timeouts Rate double

DB2 Database Performance Rollback SQL Statements Rate double

DB2 Database Performance Static SQL Statements Rate double

DB2 Database Performance Average Data Write Rate double

DB2 Database Performance Average Index Write Rate double

DB2 Database Performance Average Page Read Rate double

DB2 Database Performance Average Page Write Rate double

DB2 Database Performance Logical Data Read Rate double

DB2 Database Performance Logical Index Read Rate double

DB2 Database Performance Physical Data Read Rate double

DB2 Database Performance Physical Index Read Rate double

DB2 Database Performance Synchronous Data Read Rate double

DB2 Database Performance Synchronous Data Write Rate double

DB2 Database Performance Synchronous Index Read Rate double

DB2 Database Performance Synchronous Index Write Rate double

DB2 Database Log Log Space Utilization double

DB2 Database Log Total Log Used double

DB2 Database Log Log Reads double

DB2 Database Log Log Writes double

DB2 Database Application Connection Active Applications double

DB2 Database Application Connection Maximum Active Applications double

DB2 Database Application Connection Applications Connected double

DB2 Database Application Connection Total Connections double

DB2 Database Application Connection Active Local Connections double

DB2 Database Application Connection Active Remote Connections double

DB2 Database Application Connection Local Connections double

DB2 Database Application Connection Remote Connections double

DB2 Database Backup Time of Last Backup string

DB2 Database Backup Days Since Last Backup double

DB2 Database Cache Performance Catalogue Cache Inserts double

DB2 Database Cache Performance Catalogue Cache Lookups double

DB2 Database Cache Performance Catalogue Cache Overflows double


VMware, Inc. 41


DB2 Database Cache Performance Package Cache Inserts double

DB2 Database Cache Performance Package Cache Lookups double

DB2 Database Cache Performance Package Cache Max Used double

DB2 Database Cache Performance Package Cache Overflows double

DB2 Database Cache Performance Catalog Cache Hit Ratio double

DB2 Database Cache Performance Catalog Cache Heapfull double

DB2 Database Cache Performance Package Cache Hit Ratio double

DB2 Database IO Agents Buffer Pool Victim Page Cleaner Invokes double

DB2 Database IO Agents Buffer Pool Threshold Page Cleaner Invokes double

DB2 Database Memory Manager Total Locklist Memory in Use double

DB2 Database Non Buffered IO Performance

Average Direct Write Rate double


Average Direct Read Rate double


Direct Read Requests double


Direct Read Time double


Direct Reads double


Direct Write Requests double


Direct Write Time double


Direct Writes double


Average Data Read Rate double

DB2 Database Sort Heap Active Sorts double

DB2 Database Sort Heap Post Threshold Hash Joins double

DB2 Database Sort Heap Post Threshold Sorts double

DB2 Database Sort Heap Sort Heap Pages Allocated double

DB2 Database Sort Heap Sort Overflows double

DB2 Database Sort Heap Total Hash Joins double

DB2 Database Sort Heap Total Hash Loops double

DB2 Database Sort Heap Total Hash Join Overflows double

DB2 Database Sort Heap Total Hash Join Small Overflow double

DB2 Database Sort Heap Total Sort Time double


VMware, Inc. 42


DB2 Database Sort Heap Total Sorts double

DB2 Database Sort Heap Small Overflow Hash Joins to Total Hash Joins Ratio

double

DB2 Database Sort Heap Average Post Threshold Joins Rate double

DB2 Database Sort Heap Average Post Threshold Sorts Rate double

DB2 Database Sort Heap Piped Sorts Accepted double

DB2 Database Sort Heap Piped Sorts Requested double

DB2 Database Sort Heap Piped Sorts Rejected double

DB2 Database Sort Heap Average Active Sorts Rate double

DB2 Database Sort Heap Average Hash Join Overflow Rate double

DB2 Database Sort Heap Average Hash Join Rate double

DB2 Database Sort Heap Average Hash Join Small Overflow Rate double

DB2 Database Sort Heap Average Hash Join Small Overflow Ratio double

DB2 Database Sort Heap Average Hash Loops Rate double

DB2 Database Sort Heap Average Piped Sorts Rejected Rate double

DB2 Database Sort Heap Average Sorts Rate double

DB2 Database Summary Status string

DB2 Database Agents Connection Agent Created due to Empty Pool double

DB2 Database Agents Connection Agent Waiting Top double

DB2 Database Agents Connection Agents Registered double

DB2 Database Agents Connection Coordination Agents Top double

DB2 Database Agents Connection Idle Agents double

DB2 Database Agents Connection Pool Agents double

DB2 Database Agents Connection Agents Assignment Rate double

DB2 Database Agents Connection Agent Creation Rate double

DB2 Database Agents Connection Agent Creation to Assignment Ratio double

DB2 Database Instance Startup Time string

DB2 Database Instance Status string

DB2 Database Instance Registered Agents double

DB2 Database Instance Allocated Sort Heap Memory double

DB2 Database Instance Committed Private Memory double

DB2 Database Instance Sort Heap Threshold double

DB2 Database Instance Sort Heap Utilization double


VMware, Inc. 43

Management Pack for IBM DB2ContentsManagement Pack for IBM DB2System Requirements (IBM DB2)Configuring the Management Pack for Monitoring Metrics (IBM DB2)Enabling SSL (IBM DB2)Creating a Least-Privileged User (IBM DB2)

Installing the Management Pack (IBM DB2)Configuring the Management Pack (IBM DB2)Creating a Credential (IBM DB2)Creating an Adapter Instance (IBM DB2)Enabling Virtual Machine IOPS Metrics (IBM DB2)Validating Data Collection (IBM DB2)

Troubleshooting the Management Pack (IBM DB2)Using the Management Pack (IBM DB2)Resource Kinds and Relationships (IBM DB2)Inventory Tree (Traversal Spec) (IBM DB2)Dashboards (IBM DB2)DB2 OverviewDB2 on VMDB2 IOPSDB2 Top-N Queries

Views (IBM DB2)Reports (IBM DB2)Analysis Badges and Capacity Definitions (IBM DB2)Alerts (IBM DB2)Metrics (IBM DB2)

VMware vRealize True Visibility Suite 1 · Management Pack for IBM DB2 1 The VMware vRealize® True...

Documents

Transcript of VMware vRealize True Visibility Suite 1 · Management Pack for IBM DB2 1 The VMware vRealize® True...