DB2

Configuration

NeoLoad monitors the DB2 server using the JDBC protocol. To monitor a DB2 server, it is necessary to place the driver and license jars in the NeoLoad lib/jdbcDrivers folder. These files can be found in the DB2 Server installation at the following location:

Supported versions

NeoLoad supports most common DB2 Database server versions from 8.1 upwards.

Connection settings

The DB2 monitor allows monitoring a DB2 database server. The counters are sorted by category: connections, catalog cache, IO requests, command rates, tables memory, pool, joins, and so on.

This monitor executes SQL requests on the database to obtain status data and system variables. To carry out the monitoring, NeoLoad requires an account with authorization to connect to the database and to read and collect global status data and variables. The account must belong to the DB2ADMNS system group (on Windows) and sysmon_group (on Unix and Linux).

For NeoLoad to collect the indicators for the most resource-hungry requests (see Top Statements), the monitoring switches on the database server must be activated. These are the commands required to activate the switches:

The database server must be restarted for these changes to take effect.

NeoLoad monitors the DB2 server using the JDBC protocol:

Create a DB2 monitor

NeoLoad makes it possible to create a new monitor either using the monitored machine creation wizard, as described in Create and configure a monitored machine, or from an existing monitored machine, as described in Create and configure a monitor.

EN_monitorsdbdb2counters01

The Additional properties area makes it possible to set the number of SQL requests displayed in NeoLoad which use database resources the most—for all the indicators of the Top SQL Statements category.

Available counters

EN_monitorsdbdb2counters02