Understanding how ConfigUpdates operates
The ConfigUpdates parameter is provided by PATROL for DB2 UDB under the DB2UDB_COLLECTORS and the DB2EEE_COLLECTORS application classes. It checks for any changes made to the PATROL for DB2 UDB configuration variables and parameters through PATROL Configuration Manager by monitoring for the /DB2Config/KMConfigUpdated variable.
When one or more rules or a rule sets are applied in a PATROL Configuration Manager, the ConfigUpdates parameter performs as follows:
- The ConfigUpdates parameter checks for changes to the PATROL configuration variables (every 55 minutes, by default) by monitoring for the /DB2Config/KMConfigUpdated variable.
- Upon detection of the KMConfigUpdated variable, the DB2 UDB KM takes the following actions.
- It sets the ConfigUpdates parameter to a value of 1.
- It process the following three related variables:
- indoubt
- TbsplIOMon
- perf_monitor
It forces a discovery.
- After completion of one polling cycle (by default, 55 minutes), the ConfigUpdates parameter returns to a value of 0.
Making configuration changes take effect
In general, a change to a configuration variable takes effect through normal discovery and collection processes (DB2UDB_COLLECTORS and DB2EEE_COLLECTORS). If you want to process changes sooner, force a discovery either by using the PATROL console or by setting the /DB2Config/KMConfigUpdated variable to a value of 1.
Halting data collection
You can also use the ConfigUpdates parameter to stop the collection of certain data. By setting the /DB2Config/KMConfigUpdated configuration variable, you can change the settings of the following parameters to OFFLINE status:
- InDoubtTrans (DB2DB_RECOVERY)
- TableSpaceIO (DB2DB_PERFORMANCE)
- AveElapsedTime (DB2DB_PERFORMANCE)
When these parameters are set to OFFLINE status, they stop collecting data.
Dependencies and poll times
For information about parameter poll times and dependencies, see help topics for the parameters affected by the variable. Also see PATROL for DB2 Universal Database Getting Started, Knowledge Module filesets,, Parameters, and Configuration variables.