Historical Database Configuration Changes
You can get a chronological list of DB2 database configuration changes with the before and after value. This is a great way of keeping an audit trail of your configuration changes.
Historical DB2 Log Consumption
You can monitor your DB2 Active Log space hourly - this is very important to make sure you don't have a transaction holding the logs and causing a transaction log full condition. As well, you can get a high level statistical view of how many logs the database produces on a daily basis.
Database Workload Pattern
You can get a historical hourly database metrics such as "rows read" for every DB2 database in your organization. This can help you detect abnormal activity or sometimes even an occurrence of a new query that is doing a table-scan.
Historical Database Size
You can get a historical database size so that you can estimate your space requirement for the future, or simply see when the database had a sudden jump.
Database Backup History
You can get one consolidated report of the last backup all your databases or a report that shows you the historical view of database backups for a given database.
Database Load History
You can get a historical report of all the DB2 Loads that have been executed against your databases. This could help you identify why a tablespace is not accessible any more.
Historical Top 20 Tables
The system can show you a historical view of the top 20 tables so you can easily detect if a table is getting a tablescan.
Historical Top 20 Tablespaces
The system can show you a historical view of the top 20 tablespaces so you can easily detect if a tablespace is getting hit in an abnormal way, or growing faster than expected.
Historical Top 20 Dynamic SQL
The system can show you a historical view of the top 20 dynamic SQLs so you can easily pick if something out of the ordinary has taken place.
Historical Bufferpool Performance
The system can calculate a daily bufferpool hit ratio and graph it over time so that you can see when the bufferpool performance started to deteriorate.
Historical DB2DIAG.LOG Error Summary
You can get a high level statistical view of your db2diag.log, or a detailed view that would show you the actual error. The statistical view is useful in a sense that you can detect if in a particular day there was an abnormal number of incidents.
Tables Needing REORG
The system can show you which tables need reorg and as well show you which tables have been reorged.
What's coming down the pipe?
Historical Database Object Changes
You can get a historical report that shows you when a database object was changed - including when it was dropped. This can become very handy if someone accidentally dropped an index and as a result there is a performance problem (just as an example).
Historical Application Snapshot
You can get a historical picture of what the database connection was doing before you had to kill it. For instance, you can see the number of rows that connection was reading in say 15 minute intervals which could give a lot of hints as to the nature of the connection (such as a run-away query).
Database Object Last Used or Existed
You can get a historical report on the usage of a database object - so say if a table is missing, you can tell up to when it existed. Or you can check the last time a table was used (from the table snapshots) before you can safely drop it.