|
ManageEngine® Applications Manager IBM DB2 DB Servers | ||
Applications Manager supports monitoring of IBM DB2 8.x, 9 versions.
Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations. Click on the individual monitors listed, to view the following information.
| Parameters |
Description |
|---|---|
| Name |
Specifies the name of IBM DB2 server monitor. |
| Health |
Specifies the health (Clear, Warning, Critical) of the IBM DB2 server. |
| Type |
Specifies the type you are monitoring. |
| Version |
Specifies the version of the database server. |
| Port |
Specifies the port number at which the database server is running. |
| Instance Name | The name of the instance in which the database is present |
| Server Status | The current status of the database server itself |
| Started Time | The date and time that the database manager was started using the db2start comma |
| Host Name |
Specifies the host at which the database server is running. |
| Host OS |
Specifies the OS of the host where the database server is running. |
| Last Alarm |
Specifies the last alarm that was generated for the database server. |
| Last Polled at |
Specifies the time at which the last poll was performed. |
| Next Poll at |
Specifies the time at which the next poll is scheduled. |
| Availability |
Shows the current status of the server - available or not available. |
| Parameters |
Description |
|---|---|
| Connection Time |
Time taken to get connected to the IBM DB2 database server |
| Total Connections | The total number of local and remote connections that currently present in the database manager |
| Local Connections | The number of connections initiated from remote clients to the current instance of the database manager |
| Remote Connections | The number of local applications that are currently connected to the database within the database manager |
| Parameters |
Description |
|---|---|
| Active Agents |
The number of agents in the agent pool that are currently active and assigned to an application |
| Idle Agents |
The number of agents in the agent pool that are currently unassigned to any application |
| Number of Agents |
The number of agents registered in the current database manager instance |
| Agents Waiting | The number of agents waiting for a token so they can execute a transaction in the database manager |
| Parameters |
Description |
|---|---|
| Database Name |
The real name of the database for which information is collected |
| Health |
Specifies the health (Clear, Warning, Critical) of the database. |
| Database Alias |
The alias of the database provided when calling the snapshot function |
| Database Path |
The full path of the location where the database is stored on the monitored system |
| Database Status | The current status of the database |
| Connected Time | The date and time when the activate database was issued |
| Deadlock Rate | The total number of deadlocks that have occurred in the given polling interval |
| Percentage of Log Utilization | The total amount of active log space used in bytes in the database |
| Percentage of Sorts Overflowed |
The percentage of sorts that have over flowed |
| Parameters |
Description |
|---|---|
| Successful Queries |
The total number of successful SQL statements executed at the database in the given polling interval |
| Failed Queries |
The number of SQL statements that were attempted, but failed at the database in the given polling interval |
| Units of Work |
This represents the total number of sql commits, internal commits, sql roll backs and internal roll backs done by the database manager in the given polling interval |
| Parameters |
Description |
|---|---|
| Package Cache Hit Ratio |
The hit ratio is a percentage indicating how well the package cache is helping to avoid reloading packages and sections for static SQL from the system catalogs as well as helping to avoid recompiling dynamic SQL statements. |
| Catalog Cache Hit Ratio |
The hit ratio is a percentage indicating how well the catalog cache is helping to avoid actual accesses to the catalog on disk |
|
Parameters |
Description |
|---|---|
| Buffer Pool Hit Ratio |
The buffer pool hit ratio indicates the percentage of time that the database manager loaded the required page from buffer pool in order to service a page request |
| Index Page Hit Ratio |
The Index Page hit ratio indicates the percentage of time that the database manager accessed the index pages present in the buffer pools. |
| Data Page Hit Ratio |
The Data Page hit ratio indicates the percentage of time that the database manager accessed the data pages present in the buffer pools. |
| Direct Reads |
The number of read operations that do not use the buffer pool |
| Direct Writes |
The number of write operations that do not use the buffer pool |
|
Parameters |
Description |
|---|---|
|
Name |
Refers to the name of the Table space. |
| Allocated Bytes | calculated from (tablespace_total_pages)*(tablespace_page_size) and converted to MB |
|
Free Bytes |
calculated from (tablespace_free_pages)*(tablespace_page_size) and converted to MB |
|
% of Free Bytes |
calculated from (tablespace_free_pages) /(tablespace_total_pages)*100 |
Creating New Monitor - IBM DB2 Database Server
MS SQL DB Servers |
IBM Informix Database Servers |