Version 10.1 includes
enhancements that make monitoring DB2® database
environments more comprehensive with higher granularity of control.
New event monitor tracks configuration and registry changes and DDL and utility executions
The change history event monitor captures changes to database
and database manager configuration and registry settings, execution
of DDL statements, and execution of utilities. You can use this data
to determine if the appearance of any problems with your database
coincides with any of these events.
All event monitors now support the WRITE TO TABLE target
In earlier releases, the event data of some event monitors
was written to unformatted event (UE) tables, which required post-processing
to be viewed. Now, all event monitors can write event data directly
to relational tables.
Event monitor tables can now be upgraded
You can now upgrade existing event monitor tables from
previous releases. In previous releases, to retain the data in your
existing event monitor tables when you upgraded your DB2 product,
you had to manually alter those tables to match the definitions of
event monitor tables in the new release.
Pruning data from unformatted event tables is now supported
The PRUNE_UE_TABLES option has been added to the EVMON_FORMAT_UE_TO_TABLES
procedure to delete data from an unformatted event (UE) table after
this data has been successfully exported to relational tables.
FP1: New logical data groups added to the statistics event monitor
Starting with Version 10 Fix Pack 1, two new logical data
groups are available for the statistics event monitor. These logical
data groups include metrics monitor elements that were formerly returned
only in XML documents.
FP2: Routines can be monitored
In DB2 Version 10.1
Fix Pack 2 and later fix packs, you can retrieve information about
routines by using table functions.