Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Archive > 2017October06 - Cleanup > Configure Ignite to monitor DB2 10.5

Configure Ignite to monitor DB2 10.5

Please note: DPA/Ignite version 8.3 are End of Life and no longer supported.  This KB is for historical reference only.



This article provides steps that are required to allow Ignite 8.3 to monitor DB2 10.5. Due to the removal of some snapshot table functions in DB2 10.5, Ignite cannot currently monitor this DB2 version. Scripts have been created that allow monitoring by recreating those table functions that were removed. the table functions "wrap" other table functions that are still available in 10.5 to retrieve data.


  • All versions of DPA
  • Ignite 8.3 and earlier


1. Upgrade Ignite to  8.3.407 or higher.  Only required if Ignite is not at one of these versions. You can verify the version of Ignite in any of the following ways:

  • Check the version number on the Ignite login page.
  • The version is in the tab title in the browser that you are using to view Ignite.
  • Click Options in the upper right corner. When this page opens, you will see the version in the upper right of this page.


2. Contact support to obtain Hotfix AT83DB2. After receiving the hotfix, continue on to step 3.


3. Patch the Ignite Install. The patch is included as a zip file ( in the patch subdirectory of the hotfix bundle provided. Follow the instructions in the readme.txt (from the hotfix zip) to apply the patch.


4. Create New User and Schema. In each DB2 10.5 instance to be monitored, a new user and schema should be created. If Ignite already has a dedicated user/schema, these can be used. The scripts that grant privileges to this user and create the wrapper functions assume the user and schema names are "ignite". You can update the scripts if this is not the case.


5. Run Scripts on Monitored Instance. Run the following two scripts (from the hotfix zip) against all DB2 10.5 instances to be monitored:

  • ignite_db2_grants.sql
  • ignite_db2_functions.sql

The scripts assume the user and schema names are ignite. If this is not the case, update the scripts prior to execution.


6. Test Permissions. Run the script testscriptsforgrants.txt (from the hotfix zip).  If permissions have been configured properly, then all of these SQL statements must return a value without any errors.

 This needs a slight change as in 8.3.407 the navigation is different than in 9.0 and above. 


7. Configure Ignite for Single Database Monitoring. The wrapper functions created in the previous step only allow for single database monitoring. For this reason, Ignite should be configured, if not already, to monitor only a single database (i.e. not instance-wide).

In Ignite, make the following (7a and 7b) configuration changes via the Advanced Options page:

   a. Options link > Administration tab > Advanced Options button (Ignite must be started to access this page).


7a. Configure Single Database Monitoring for Instances Registered in the Future:

   a. Check Support Options box.

   b. Under the Repository Options section: 

       1. Edit the DB2_MONITOR_SINGLE_DB_DEFAULT option:

           a. Set the option's value to True and save (i.e. update).


7b. Configure Existing Registrations to Monitor Single Database:

   a. Go to Monitored Database Instance Options section.

   b. For each DB2 10.5 instance:

       1. Select the instance from the drop-down list.

       2. Edit the DB2_MONITOR_SINGLE_DB option:

           a. Set the option's value to 'True' and save (i.e. update).


8. Update EXPLAIN table to Allow for Plan Generation. One Explain table used by Ignite for generating explain plans was updated in DB 10.5. This update prevents Ignite from gathering plans. The following steps will create the EXPLAIN_OBJECT table to enable Ignite to collect plans from DB2 10.5:

  • For each DB2 10.5 database registered in Ignite:
    1. Make sure that Ignite is monitoring the DB2 10.5 database (i.e. that the Ignite monitor is started).
    2. In Ignite, attempt to run a live plan from Ignite (an error may occur, but ignore the errors for now). This ensures that all of the tables needed to collect plans have been created, although the EXPLAIN_OBJECT table will likely have the wrong structure.
    3. In the Ignite schema on the DB2 10.5 instance, run the ignite_db2_explain_object.sql script (from the hotfix).
    4. In Ignite, run a live plan again.  

Note: The Transaction Log Freespace alert does not work. A custom alert can be created as a workaround.



Last modified