DB2 Local connection setup

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: $|?\"[]+=&*();!^<>:/

• Enter the full path (do not use the short path format) to the JRE directory on the PATROL Agent host. The Java version must be 8 or later.
  For example:
  • Windows: C:\Program Files (x86)\Java\jre8
  • Unix\LINUX: /usr/java8_64
• Alternatively, you can also use the $JAVA_HOME environment variable in this field. If you use the $JAVA_HOME variable, the Java location depends on the $JAVA_HOME you declare in you PATROL agent host.
• If this field is left blank, the KM looks for the Java executable in the Patrol3\openjdk and Patrol3\jre64 locations.

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.

Select the monitoring collection level for the IBM DB2 system.

• Availability - Select this option to check the availability of instances, connections, and databases.
• Full data monitoring - Select this option to collect all the monitored groups.
• Custom data monitoring - Select this option to collect only the monitored groups selected from the custom data module types.

Select monitor types for monitoring.

• Applications - This group is responsible for collecting applications instances and parameters and displaying them under each partition of a database.
• Buffer Pools - This group is responsible for collecting buffer pools instances and parameters and displaying them under each database’s partition.
• Capacity - This group is responsible for collecting capacity parameters and displaying them under each partition of a database. 
• HADR - This group is responsible for collecting HADR parameters and displaying them under each partition of HADR standby and primary databases.
• Instance Attributes - This group is responsible for collecting instance attributes and displaying them under the partitions container node of the instance.
• Instance Partition Attributes - This group is responsible for collecting instance's partition's attributes and displaying them under each instance’s partition’s node.
• Locks - This group is responsible for collecting lock parameters and displaying them under each partition of a database.
• Logs - This group is responsible for collecting log parameters and displaying them under each partition of a database.
• Performance - This group is responsible for collecting performance parameters and displaying them under each partition of a database.
• Recovery - This group is responsible for collecting recovery parameters and displaying them under each partition of a database.
• SQL - This group is responsible for collecting SQL parameters.
• Tablespaces - This group is responsible for collecting table spaces instances and parameters and displaying them under each partition of a database.

Select the IBM DB2 monitor type for monitoring:

• DB2 Instance
• DB2 Diag Log
• DB2 Databases Container
• DB2 Database
• DB2 HADR Database
• DB2 Buffer Pool Container
• DB2 Buffer Pool
• DB2 Database Lock
• DB2 Database Capacity
• DB2 Partitions Container
• DB2 Partitions
• DB2 DB Partition
• DB2 Applications Container
• DB2 Application
• DB2 Application's Agent 
• DB2 Table Spaces Container
• DB2 Tablespace
• DB2 Database Log
• DB2 Database Sql
• DB2 Database Recovery
• DB2 Database Performance
• DB2 Instance Partition Parameters
• DB2 Instance Parameters
• DB2 Database Hadr
• Custom SQL Queries
• SQL Query

Based on the monitor types selected in the above field, select the filtering option:

• None
• Include
• Exclude

Select the attribute state for monitoring:

• PRUNE
• INFORMATION
• WARN
• ALARM

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:

Patrol3/log/PSO_<DB type>^<environment name>-<Agent host>-<Agent port>.kmlog

For example: Patrol3/log/PSO_Local^DB2Env-IL-hhomndf-W1-3181.kmlog

The Java debug file of the environment is located under:

Patrol3/pso/logs/java/<DB type>^<environment>_<Agent port>_JavaCollector.log

For example: Patrol3/pso/logs/java/Local^DB2Env_3181_JavaCollector.log.0

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.

Patrol3/log/PSO_Local_main-<Agent host>-<Agent port>.kmlog