Tuning the Monitor database
Like all operational databases, the Monitor database requires regular maintenance and tuning. Some DB2® tools can help you to enhance the use and performance of the databases.
- Configuration Advisor
- DB2 Health Center: this tool assists database administrators (DBAs) by alerting them to potential problems and providing recommendations to resolve problems. DBAs can monitor an instance remotely using the DB2 Health Center, view alert details, and make recommendations.
- REORG command: this command eliminates overflow rows and reclaims space from deleted rows of tables and indexes. The REORG command is useful if there have been a large number of deletions, updates, or insertions.
- REORGCHK command: this command updates the statistics that are used by the DB2 optimizer tool. The REORGCHK command is useful when the statistical information of the database tables are not synchronized with database updates.
- RUNSTATS command: this command gathers statistics about
databases objects. These statistics can be used during data retrieval
to choose the path in accessing data. Therefore, DB2 then has the information it needs to choose
the most efficient access path. Databases performance will be poor
until an administrator runs the DBA RUNSTATS command against all of
the tables in all of the databases after some data has accumulated
in each of the databases. For example, you might run the following
command:
where the tablename must be fully qualified with the schema name. After running the RUNSTATS command, run the DB2 rebind command:RUNSTATS ON TABLE tablename WITH DISTRIBUTION AND DETAILED INDEXES ALL
The performance affects event-processing performance of the Monitor server and query performance of the dashboard, as well as performance of Data Movement Service.db2rbind database_alias -l logfile all
When monitor models are deployed, database indexes are created on the Monitor tables based on the model's sortable metrics, KPIs, and dimensions. In a production environment, actual user workload should be analyzed to determine if additional indexes are required or if existing indexes should be removed. Removing unneeded indexes allows event processing and data movement services to perform better because database index maintenance can slow down performance during instance inserts, updates, and deletes.
- For more information about DB2 maintenance utilities, see the IBM® DB2 documentation.
- For information on the utilities offered by other databases, see their documentation.
Backing up databases and recovering from deployment errors is also part of database maintenance.
