Example: Identifying configuration changes and utility executions using the change history event monitor

You can use the change history event monitor to determine if there have been any recent configuration changes or the recent execution of utilities.

Scenario

In this example, the database administrator (DBA) notices a change in database performance over the last 24 hours. The DBA previously created a change history event monitor called HIST, that he has been using to understand changes in the behavior, performance, or stability of the databases and database management system.

The DBA issues the following query against the CHANGESUMMARY logical data group in order to summarize any change events or utility executions that occurred in the last 24 hours.

 SELECT EVENT_TIMESTAMP,
        EVENT_TYPE,
        UTILITY_TYPE,
        COORD_MEMBER,
        MEMBER
   FROM CHANGESUMMARY_HIST
   WHERE EVENT_TIMESTAMP > CURRENT TIMESTAMP - 24 HOURS
   ORDER BY BY EVENT_TIMESTAMP ASC

The query might return output similar to the following:

EVENT_TIMESTAMP            EVENT_TYPE     UTILITY_TYPE COORD_MEMBER MEMBER
-------------------------- -------------- ------------ ------------ ------
2010-10-31-17.29.04.545210 DBCFG                                  0      0
2010-10-31-18.29.04.545210 UTILSTART      LOAD                    0      0
2010-10-31-18.40.04.545210 UTILSTARTPROC  LOAD                    0      0
2010-10-31-18.50.04.545210 UTILSTOPPROC   LOAD                    0      0
2010-10-31-18.40.04.545210 UTILSTARTPROC  LOAD                    0      1
2010-10-31-18.50.04.545210 UTILSTOPPROC   LOAD                    0      1
2010-10-31-19.29.04.545210 UTILSTOP       LOAD                    0      0
2010-10-31-19.56.04.545210 UTILSTART      BACKUP                  0      0
2010-10-31-20.09.04.545210 UTILPHASESTART BACKUP                  0      0
2010-10-31-20.29.04.545210 UTILPHASESTOP  BACKUP                  0      0
2010-10-31-21.29.04.545210 UTILSTOP       BACKUP                  0      0

9 record(s) selected.

From this output, the DBA determines that there have been configuration changes and utility executions in the last 24 hours. He can now query the other change history event monitor logical data groups and obtain more information about the events returned in the CHANGESUMMARY logical data group. For example, for more information about the UTILSTART events, the DBA can query the UTILSTART logical data group to understand which objects are being acted on by the utilities and what options were used when the utilities were started.