Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Database Performance Analyzer (DPA) > Use newer DB2 polling tables

Use newer DB2 polling tables

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 949 Votes: 0 Revisions: 9


This article applies to DPA 9.0 and later and DB2 9.5 and later.

In DB2 version 10.5, IBM removed certain snapshot tables that were used by the "quick poll" job. In order to support DB2 10.5, it was necessary to rewrite the query to use newer snapshot tables. In doing so, we were able to make the query slightly more efficient. By default, DB2 10.5 will be monitored using the new, more efficient, snapshots.

If you are monitoring a database that is running version DB2 9.5 to 10.1, you can configure monitoring to use the new queries. Below are the steps needed to set up this configuration.

  1. Stop all DB2 Monitor(s) that you are planning to configure.

  2. Find the monitored database id by looking in the COND table:
    SELECT id, name
    ORDER BY name;

  3. Add the DB2_USE_NEW_QUICKPOLL_QUERY parameter for each monitored database you plan to configure by running the following in your Repository database (replace '?' with the database ID from step 2):
    insert into CONDPRM
    values (?, 'DB2_USE_NEW_QUICKPOLL_QUERY', 'true', 'use new quick poll');

  4. Convert the CONEV_MAP_X VID column to use a string rather than an int by running the following queries (replace 'X' with the database ID from step 2):
    delete from CONEV_MAP_X;
    insert into CONEV_MAP_X (VID, ID) select NAME, ID from CONEV_X;

  5. Refresh the parameter cache:
    • Go to the "Options" page
    • Click the "Support" tab
    • Click "Refresh Parameter Cache"

  6. Restart any DB2 Monitor(s) that you configured.
Last modified