This is my first blog here regarding db2 database monitoring.I am going to start from the basic level ,therefore starts and learners can easily understand.<\/p>\n
I will try to make more interesting and I hope users will like to read more on db2 .<\/p>\n
\u00a01.<What this unit is about ><\/h3>\n
This unit introduces the monitoring tools provided for DB2 databases. We will compare the newer monitoring infrastructure implemented in DB2 9.7 to the older snapshot monitoring. We will describe monitoring using db2pd commands and also show how to monitor using the monitoring SQL functions and views.<\/p>\n
2.<What you should be able to do><\/h3>\n
After completing this unit, you should be able to:–(Unit objectives)<\/p>\n
\u2022Compare the infrastructure used to support SNAPSHOT monitoring with the monitoring infrastructure introduced in DB2 9.7 \n\u2022Configure a database to collect the activity and object metrics returned by the Monitoring Table functions \n\u2022Use the db2pd to perform performance analysis or problem determination for a DB2 database \n\u2022Utilize the DB2 provided table functions and views with SQL in reporting and monitoring of the database system, data objects, and the package cache to help you quickly identify issues that might be causing problems \n\u2022Configure the DB2 Database configuration options that control the collection of request, activity and object level metrics on the entire database.<\/p>\n
\u00a0<Why should you monitor a DB2 database?> \n<\/span><\/strong><\/h3>\n
<\/p>\n
\u2022Forecast hardware requirements based on database usage patterns.<\/p>\n
\u2022Analyze the performance of individual applications or SQL queries.<\/p>\n
\u2022Track the usage of indexes and tables.<\/p>\n
\u2022Pinpoint the cause of poor system performance.<\/p>\n
\u2022Assess the impact of optimization activities, for example:<\/p>\n
Notes:<\/strong> \nThe term database monitoring refers to the tasks associated with examining the operational status of your database. \nDatabase monitoring is a vital activity for the maintenance of the performance and health of your database management system.<\/p>\n
To facilitate monitoring, DB2 collects information from the database manager, its databases, and any connected applications. With this information you can perform the following types of tasks, and more:<\/p>\n
\u2022Forecast hardware requirements based on database usage patterns.<\/span> \n\u2022Analyze the performance of individual applications or SQL queries.<\/span> \n\u2022Track the usage of indexes and tables.<\/span> \n\u2022Pinpoint the cause of poor system performance.<\/span> \n\u2022Assess the impact of optimization activities (for example, altering database manager configuration parameters, adding indexes, or modifying SQL queries).<\/span><\/p>\n
<\/p>\n
3.<Interfaces for database monitoring ><\/h3>\n
There are two ways to monitor operations in your database. You can view information that shows the state of various aspects of the database at a specific point in time. Or, you can set up event monitors to capture historical information as specific types of database events take place.<\/p>\n
<\/p>\n
4.<Monitor elements><\/h3>\n
Monitor elements are data structures used to store information about a particular aspect of the database system status. For example, the monitor element direct_reads reflects the number of read operations that take place that are performed directly from disk, rather than from any buffer pool.<\/p>\n
<\/p>\n
<\/p>\n
Notes:<\/strong> \nDB2 9.7 introduced a new monitoring infrastructure that you can access through new table functions and new event monitors. This infrastructure is a superior alternative to the existing system monitor, event monitors, snapshot commands, and snapshot SQL interfaces.<\/p>\n
The new monitoring infrastructure is independent from the snapshot based statistics used in prior releases and does not use the DB2 instance level switches to control detailed data collection.<\/p>\n
The GET SNAPSHOT command reports returned large amounts of information which could take extra effort to locate the specific data needed. For example, the table snapshot lists every table accessed and the table space snapshot lists every defined table space.<\/p>\n
Using the snapshot based SQL functions and views allowed the snapshot statistics to be selectively accessed, but the internal processing would still incur the overhead associated with producing a complete set of statistics.<\/p>\n
The system overhead associated with some of the snapshot switches that control collection of detailed statistics lead some users to only turn on the detailed data when needed for a specific problem or tuning effort.<\/p>\n
The new monitoring infrastructure was designed to provide detailed system and application statistics with a reduced overhead for collecting the monitor data. The plan is to provide a set of views and functions based on the new monitoring facility that will eventually completely replace snapshot based monitoring.<\/p>\n
<\/p>\n
To be continued in the next unit ….\u00a0 \ud83d\ude42<\/p>\n
![](\"https:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/949.png\")
<\/p>\n![](\"https:\/\/dbtut.com\/wp-content\/uploads\/2018\/09\/589.png\")
<\/p>\n