DB2 Version 9.7 for Linux, UNIX, and Windows
DB2 Version 9.7 for Linux, UNIX, and Windows
The health monitor captures information about the database manager, database, table space, and table space containers. The health monitor calculates health indicators based on data retrieved from database system monitor elements, the operating system, and DB2® database.
The health monitor can only evaluate health indicators on a database and its objects when the database is active. You can keep the database active either by starting it with the ACTIVATE DATABASE command or by maintaining a permanent connection to the database.
The health monitor retains a maximum of 10 history records for each health indicator. This history is stored in the instance_path\hmonCache directory and is removed when the health monitor is stopped. The health monitor automatically prunes obsolete history records when the maximum number of records is reached.
Health monitor data is accessible through health snapshots. Each health snapshot reports the status for each health indicator based on its most recent refresh interval. The snapshots are useful for detecting existing database health problems and predicting potential poor health of the database environment. You can capture a health snapshot from the CLP, by using APIs in a C or C++ application, or by using the graphical administration tools.
Health monitoring requires an instance attachment. If an attachment to an instance was not established using the ATTACH TO command, then a default instance attachment to the local instance is created.
In partitioned database environments, snapshots can be taken at any partition of the instance, or globally using a single instance connection. A global snapshot aggregates the data collected at each partition and returns a single set of values.
The health monitor is supported on all editions of the DB2 database.
To start or stop the health monitor from the Health Center, right-click an instance in the Health Center navigational view and select Start Health Monitor or Stop Health Monitor.
On Windows, the service for the DB2 instance needs to run under an account with SYSADM authority. You can use the -u option on the db2icrt command, or use the Services folder on Windows and edit the Log On properties to use an account with administrator privilege.
The health monitor process runs as a DB2 fenced mode process. These processes appear as DB2FMP on Windows. On other platforms, the health monitor process appears as DB2ACD.
The DB2 Administration server must be running on the system where the health monitor resides for notifications to be sent and alert actions to be run. If remote scripts, tasks, or contact lists are used, the DB2 Administration server on the remote system must also be started.
The tools catalog database is required only for creating tasks. If you do not use alert task actions for any health indicator, the tools catalog database is not required by the health monitor.
If you fall back to DB2 UDB Version 8.1 from a later version of the DB2 database system, any registry changes that were made are lost. The registry reverts to the version 8.1 HealthRules.reg file that contains the settings that existed before you upgraded and started using the settings in the newer registry file.