DB2 Local connection setup
After you have installed the PATROL for IBM DB2, you must configure a monitoring policy. You can use the information in this topic to configure a DB2 local connection setup with the TrueSight console.
This topic includes the following information:
Before you begin
You must download and install the PATROL for IBM DB2.
To configure the monitor type
In the Add Monitoring Configuration panel, select the following parameters for the DB2 local connection setup monitor type:
|Monitoring Solution||IBM DB2|
|Monitoring Profile||IBM DB2|
|Monitor Type||DB2 Local connection setup|
To add an environment configuration
Click Add and enter the Environment Configuration details.
Enter a unique environment name for monitoring the DB2 databases. A container will be created with the environment name. This environment will hold all the DB2 instances.
The name should not contain blank spaces or any of the following special characters:
|Local IBM DB2 details|
|IBM DB2 installation home|
Enter the path to the installation base directory or the environment variable that contains installation base directory. Files are installed to the following directories under the installation base directory as depicted in the following example:
Starting the 9.6.21 version of PATROL for IBM DB2, if you enter environment variable, ensure that the variable name begins with DB2PATH for example, DB2PATH, DB2PATH3. Also, ensure that the OS JVM user has access to the DB2PATH environment variable.
|IBM DB2 instance List||Specify the list of DB2 instances for monitoring. If the field is left blank, all the instances gets monitored.|
|Data encryption authentication|
Select this option to enable the IBM DB2 authenticated connection. The connection to IBM DB2 databases is established using data encrypt (DATA_ENCRYPT) security mechanism.
Use this option when the IBM DB2 databases are configured as data encrypt (DATA_ENCRYPT).
|IBM DB2 database credentials|
Enter the name of the user with permissions to connect and run SQL queries on all DB2 databases. The user should have minimum SYSMON authority with DATAACCESS privileges.
|The password of the DB2 user.|
|Java collector settings|
|JVM arguments||Enter the optional Java Virtual Machine (JVM) arguments for the DB2 Java collector.|
|Java OS credentials|
Enter the name of the OS JVM user (this user must exist where the PATROL Agent and DB2 KM are installed) with permission to run the Java process.
The password for the OS JVM user.
Note: If you use $PATROL_USER as user name, you must enter a dummy password. Otherwise, the policy does not save the $PATROL_USER value.
|Monitoring data details|
Select the monitoring collection level for the IBM DB2 system.
Select monitor types for monitoring.
Filter configuration by monitor types
Click Add and filter the monitor types for monitoring. For more information, see Using filter configuration by monitor types.
You can filter the monitor types at any instance level within the DB2 hierarchy.
|IBM DB2 instance name|
Enter IBM DB2 instance name. Use comma (,) only to separate the instance names. This field is regex enabled.
All the defined filters are applicable for the specified DB2 instances.
|IBM DB2 database name|
Enter IBM DB2 database name. Use comma (,) only to separate the database names. This field is regex enabled.
All the defined filters are applicable for the specified databases.
|Filters by monitor types list|
|Filtering monitor types|
Select the IBM DB2 monitor type for monitoring:
Based on the monitor types selected in the above field, select the filtering option:
|Filtering instances from the selected monitor type|
Based on the selection in the filtering options, specify the instances from the selected monitor type for monitoring. This field is regex enabled. Use comma (,) to define multiple instances for the specified monitor type.
Custom SQL queries configuration list
Click Add and configure the custom SQL queries section.
|IBM DB2 instance name|
Enter the IBM DB2 instance name. It supports regex for monitoring multiple instances. Use comma to separate entries. By default, .* is used which monitors all the instances.
|IBM DB2 database name|
Enter the IBM DB2 database name. It supports regex for monitoring multiple databases. Use comma to separate entries. By default, .* is used which monitors all the databases.
Custom SQL query configuation list
|SQL query name|
Enter the name of the SQL query. This is an user-defined field.
The name cannot include blank spaces or any of the following special characters:
Enter the SQL query that you want to execute in the database.
The SQL query must not contain the semicolon (;).
|Collection time (min)||Enter the SQL query collection time in minutes. The default collection cycle is 10 minutes.|
|Enable number of records annotation||Select this option to display the query result as an annotation on DB2 custom SQL query number of records metric.|
- All the defined Custom SQL query configuration lists are applicable on the instances and databases specified above.
If you configure multiple lists of DB2 instances and DB2 databases with same SQL query name and matches the same DB2 instance and DB2 database, the last entered list will be displayed. You will get an annotation about the same on Configuration status attribute.
IBM db2diag log search configuration list
Click Add and configure the db2diag log search configuration section.
You can define multiple search configurations for same instance. In case, if there are multiple search results, the DiagLogOK parameter value will set the value with high priority/severity and displays a detailed annotation for the search commands and their results.
|IBM DB2 Instance name|
Enter the IBM DB2 instance name. It supports regex for monitoring multiple instances. Use comma to separate instances.
The defined searches are applicable for the specified DB2 instance.
|IBM db2diag log search criteria list|
|DiagLogOK attribute states|
Select the attribute state for monitoring:
|IBM db2diag tool search command|
Specify a command that is supported by the IBM db2diag tool.
For example: -lastlines 100 -l Warning
Be cautious while using this feature, it might affect the performance of the environment monitoring in case if the IBM db2diag tool retrieves a huge chunk of data.
Click Add and configure the administration details.
Select this option to enable debugging operations for configured environment. This enables the PSL and Java logging of the specified environment.
The PSL debug file of the environment is located under:
For example: Patrol3/log/PSO_Local^DB2Env-IL-hhomndf-W1-3181.kmlog
The Java debug file of the environment is located under:
For example: Patrol3/pso/logs/java/Local^DB2Env_3181_JavaCollector.log.0
|Availability collection interval (min)||Enter the availability collection time in minutes for the DB2 JAVA collector. The default collection time is 1 minutes.|
|Data collection interval (min)||Enter the data collection time in minutes for the DB2 JAVA collector. The default collection time is 10 minutes.|
|IBM db2diag log collection interval (min)||Enter the IBM db2diag log collection time in minutes for the DB2 JAVA collector. The default collection time is 5 minutes.|
|Long running data collection queries threshold (sec)||Enter the threshold to monitor the data collection SQL queries that run longer than the number of seconds entered.|
|Long running data collection commands threshold (sec)||Enter the threshold to monitor the data collection CLP or OS commands that run longer than the number of seconds entered.|
Select this option to enable device mapping for all hosts in this environment. If enabled, all the monitors gets created within a device according to the discovered host name of the monitored system. If disabled, all the monitors gets discovered under the PATROL Agent host device.
|Disable monitoring for IBM DB2 remote databases||Select this option to disable the discovery of IBM DB2 remote databases.|
Disable monitoring configuration
Click Add and configure the disable monitoring details.
|Disable monitoring environment||Select this option to disable the KM from discovering and monitoring the configured environment.|
|IBM DB2 instance disable monitoring list|
|Instance name||Enter the IBM DB2 instance name that you want to disable from monitoring. The disable monitoring file location configuration will be applied to this IBM DB2 instance. Regex is not supported|
|Disable monitoring file location|
Enter the absolute location of the disable monitoring file. The disable monitoring file should be configured on the IBM DB2 host.
Once you remove the disable monitoring file from the monitoring system, monitoring will be enabled.
Global monitoring setting
|Logging||Select this option to enable main PSL debug logging for global configuration. The log file path:|
|Disable environments monitoring file location|
Enter the absolute location of the disable monitoring file. The disable monitoring file should be configured on the PATROL Agent host.
Once you remove the disable monitoring file from the monitoring system, the monitoring will be enabled.