UPDATE THIS.....This section describes the required configurations as well as the optional configurations available for the Solution Package for MySql Database IBM DB2 in the RTView Configuration Application. You must define the classpath to the MySQL JDBC IBM DB2 jar file files and you must also define data source connections for each connection that you want to monitor. 

Configuring Data Connection

Use the RTView Configuration Application to configure your data collection.

• Navigate to Solution Package Configuration > MySQL DatabaseIBM DB2 from the list.

Image RemovedImage Added

• On the CONNECTIONS tab, provide the correct full path to the directory containing the MySQL JDBC IBM DB2 jar files in the Classpath field.
• In the Connections region, click the  icon.

The Add Connection dialog displays.

Image RemovedImage Added

• Specify the connection information and click SAVE where:

Connection Name: Enter the desired name for the connection.

Database URL: Enter the complete URL for the database connection. For example: jdbc:db2://hostOrIP>:50001/databaseName

Username: The username is used when creating the connection to the database. This field is optional.

Password: This password is used when creating the connection to the database. This field is optional. By default, the password entered is hidden. Click the  icon to view the password text.

Select at least one: Select at least one of the following options for this connection:

Monitor Statistics: Enables monitoring of MySQL Statistics. If this is not selected the MySQL Statistics displays in the monitor will not contain data for this connection.

Monitor Tables: Enables monitoring of MySQL Tables. If this is not selected the MySQL Tables displays in the monitor will not contain data for this connection.

.

The newly created connection displays in the Connections section.

Image RemovedImage Added

• You can optionally modify the Poll Rates (query interval, in seconds) that will be used to collect the metric data for the Poll Rate (MysqlServerPropertiesForDisplay cacheDb2EnvSysResources, Db2SnapDbm, Db2SnapDb, Db2DbSummary, and Db2TimeSpent caches) and the  Poll Rate Large (MysqlAbortedDb2BufferPools, MysqlBytes, MysqlCRUD, MysqlUptime, MysqlThreads, MysqlQcache, MysqlQueries, MysqlSummaryTable, MysqlCreatedTemp, MysqlOpenedMetrics, MysqlTableLockMetrics, MysqlBinlogMetrics, MysqlConnection, MysqlSelectMetrics and MysqlTableStats Db2TableSpace, Db2PdLogMsgs, and Db2SnapSwitches caches) caches by clicking on the DATA COLLECTION tab and entering the desired polling rate for each cache.

Image RemovedImage Added

Configuring Historical Data Collection (Optional)

This section describes the additional optional MySQL Database Monitor configurations. You can specify the number of history rows to store in memory, the compaction rules, the duration before metrics are expired and deleted, and the different types of metrics that you want the Historian to store in the DATA STORAGE tab in the RTView Configuration Application.

Defining the Storage of In-Memory History

You can modify the maximum number of history rows to store in memory in the DATA STORAGE tab. The History Rows property defines the maximum number of rows to store for the MysqlAborted, MysqlBytes, MysqlCRUD, MysqlQueries, MysqlTableLockMetrics, MysqlBinlogMetrics and MysqlConnections the Db2SnapDb, Db2SnapDbm, Db2DbSummary, Db2TableSpace, Db2Availability, Db2ResponseTime, Db2EnvSysResources, and Db2TimeSpent caches. The default settings for History Rows is 50,000. To update the default setting:

• Navigate to the Solution Package Configuration > MySQL DatabaseIBM DB2 > DATA STORAGE tab.
• In the Size region, click the History Rows field and specify the desired number of rows.

Image RemovedImage Added

Defining Compaction Rules

Data compaction, essentially, is taking large quantities of data and condensing it using a defined rule so that you store a reasonably sized sample of data instead of all of your data, thus preventing you from potentially overloading your database. The available fields are:

Condense Interval -- The time interval at which the cache history is condensed for the Db2Availability cache. The default is 60 seconds.

Condense Interval Base -- The time interval at which the cache history is condensed for the following caches:

Db2SnapDb,

Db2SnapDbm,

Db2DbSummary,

Db2ResponseTime,

Db2EnvSysResources,

and Db2TimeSpent. The default is 300 seconds.

Condense Interval Large -- The time interval at which the cache history is condensed for the Db2TableSpace cache. The default is 300 seconds.

Condense Raw Time -- The time span of raw data kept in the cache history table for the Db2Availability cache. The default is

600 seconds.

Condense Raw Time Base -- The time span of raw data kept in the cache history table for the following caches:

Db2SnapDb,

Db2SnapDbm,

Db2DbSummary,

Db2ResponseTime,

Db2EnvSysResources,

and Db2TimeSpent. The default is 1200 seconds.

Condense Raw Time Large -- The time span of raw data kept in the cache history table for the Db2TableSpace cache. The default is 1200 seconds.

Compaction Rules -- This field defines the rules used to condense your historical data in the database for the following caches:

Db2SnapDb, Db2SnapDbm, Db2DbSummary, Db2ResponseTime, Db2EnvSysResources, and Db2TimeSpent. By default, the columns kept in history will be aggregated by averaging rows with the following rule 1h -;1d 5m;2w 15m, which means the data from 1 hour will not be aggregated (1h - rule), the data over a period of 1 day will be aggregated every 5 minutes (1d 5m rule), and the data over a period of 2 weeks old will be aggregated every 15 minutes (2w 15m rule).

Compaction Rules Large -- This field defines the rules used to condense your historical data in the database for the Db2TableSpace cache. By default, the columns kept in history will be aggregated by averaging rows with the following rule 1h -;1d 5m;2w 15m, which means the data from 1 hour will not be aggregated (1h - rule), the data over a period of 1 day will be aggregated every 5 minutes (1d 5m rule), and the data over a period of 2 weeks old will be aggregated every 15 minutes (2w 15m rule).

To define compaction rules:

• Navigate to the Solution Package Configuration > MySQL DatabaseIBM DB2 > DATA STORAGE tab.
• In the Compaction region, click the  Condense Interval, Condense Raw Time, and Compaction Rulesvarious fields and specify the desired settings.

Note: When you click in the Compaction Rules and Compaction Rules Large fieldfields, the Copy default text to clipboard link appears, which allows you copy the default text (that appears in the field) and paste it into the field. This allows you to easily edit the string rather than creating the string from scratch.

Image RemovedImage Added

Defining Expiration and Deletion Duration for

IBM DB2 Metrics

The data for each metric is stored in a specific cache and, when the data is not updated in a certain period of time, that data will either be marked as expired or, if it has been an extended period of time, it will be deleted from the cache altogether. By default, metric data will be set to expired when the data in the cache has not been updated within 45 seconds. Also, by default, if the data has not been updated in the cache within 3600 seconds, it will be removed from the cache  The following caches are impacted by settings in the Expire Time field: Db2SnapDb, Db2SnapDbm, Db2DbSummary, Db2Availability, Db2ResponseTime, Db2EnvSysResources, and Db2TimeSpent. The following caches are impacted by settings in the Expire Time Large field: Db2SnapSwitches, Db2BufferPools, Db2TableSpace, and Db2PdLogMsgs. The following caches are impacted by settings in the Expire Delete Time field: MysqlAborted, MysqlBytes, MysqlCRUD, MysqlQueries, MysqlTableLockMetrics, MysqlBinlogMetrics and MysqlConnectionDb2SnapDb, Db2SnapDbm, Db2DbSummary, Db2Availability, Db2ResponseTime, Db2EnvSysResources, and Db2TimeSpent. The following caches are impacted by settings in the Delete Time Large field: Db2SnapSwitches, Db2BufferPools, Db2TableSpace, and Db2PdLogMsgs. To modify these defaults:

• Navigate to the Solution Package Configuration > MySQL DatabaseIBM DB2 > DATA STORAGE tab.
• In the Duration region, click the various Expire Time field fields and specify the desired settings.

Image RemovedImage Added

Enabling/Disabling Storage of Historical Data

The History Storage region allows you to select which metrics you want the Historian to store in the history database. By default, all historical MySQL Database metrics are not the following historical IBM DB2 metrics are saved to the database. The following caches are impacted by these metrics:

• AbortsAvailability: MysqlAborted DB2Availability
• Bin LogsDB Summaries: MysqlBinlogMetrics DB2DbSummary
• BytesEnv Sys Resources: MysqlBytes DB2EnvSysResources
• ConnectionsResponse Time: MysqlConnection
• Created Temps: MysqlCreatedTemp
• Crud: MysqlCRUD
• Opened: MysqlOpenedMetrics
• QCache: MysqlQcache
• Queries: MysqlQueries
• Selects: MysqlSelectMetrics
• Summary: MysqlSummaryTable
• Table Locks: MysqlTableLockMetrics
• Threads: MysqlThreads
• Uptimes: MysqlUptime
• User Tables: MysqlTableStats

•  DB2Response Time
• Snap DB: DB2SnapDb
• Snap DBM: DB2SnapDbm
• Table Spaces: DB2TableSpace
• Time Spent: DB2TimeSpent

To disable the collection of this historical data, perform the following steps:

• Navigate to the Solution Package Configuration > MySQL DatabaseIBM DB2 > DATA STORAGE tab.
• In the History Storage region, deselect the toggles for the metrics that you do want to collect. Blue is enabled, gray is disabled.

Image RemovedImage Added

Defining a Prefix for All History Table Names for

IBM DB2 Database Metrics

The History Table Name Prefix field allows you to define a prefix that will be added to the database table names so that the Monitor can differentiate history data between data servers when you have multiple data servers with corresponding Historians using the same solution package(s) and database. In this case, each Historian needs to save to a different table, otherwise the corresponding data server will load metrics from both Historians on startup. Once you have defined the History Table Name Prefix, you will need to create the corresponding tables in your database as follows:

• Locate the .sql template for your database under rtvapm/mysqlmondb2mon/dbconfig and make a copy of template.
• Add the value you entered for the History Table Name Prefix to the beginning of all table names in the copied .sql template.
• Use the copied .sql template to create the tables in your database.

To add the prefix:

• Navigate to Solution Package Configuration > MySQL DatabaseIBM DB2 > DATA STORAGE tab.
• Click on the History Table Name Prefix field and enter the desired prefix name.

Image RemovedImage Added