Welcome to Spotlight on IBM DB2 LUW (Linux, Unix, and Windows). The help topics in this book cover features available in the interface when Spotlight is connected to a version 9 database.
Spotlight is a powerful database monitoring and diagnostic tool. Its unique user interface provides you with an intuitive, visual representation of the activity on the DB2 databases and database partitions that you choose to monitor. Graphical flows and line and fill graphs illustrate the activity on and between database components. Icons display the value of key statistics. Using the Spotlight browser, you can switch your monitoring focus between the various databases and partitions. Additionally, you can view activity at the DB2 instance level for any of these systems.
The power of Spotlight lies in its ability to provide visual and audible warnings if the performance metrics exceed acceptable thresholds. The components and dataflows on the home page change color to show you the source of the problem.
A range of reports and graphs provide you with detailed information about a DB2 database, database partition, or the instance to which the database belongs. This information can be viewed on the screen or be printed.
You can set Spotlight options to warn you when a threshold is reached. You can define a number of thresholds so that warning messages are displayed well before the traffic levels into or out of databases become critical.
Spotlight uses a number of different techniques to warn you when your DB2 instance or a database is exceeding a threshold. For example, to issue a warning, you can configure Spotlight to change a color on the home page or drilldown, provide an audible signal, or perform an action, such as send an email message.
The Database Manager Summary drilldown displays global summary information about all active databases and partitions in the DB2 for LUW (Linux, Unix, and Windows) instance you are monitoring. In a single-partition environment, only the All Nodes data is presented.
Note: For detailed information about a particular database or database partition, use the Databases drilldown.
When you select a specific database or database partition from the list, a set of tabs appear in the lower half of the window. These tabs contain additional details and activity statistics about the specific database, allowing you to drill down for more information about a problem.
If monitor heap failure becomes a problem, use this formula, taken from the IBM System Monitor Guide and Reference, to adjust the MON_HEAP_SZ parameter.
( number of monitoring applications + 1 ) * ( number of databases * (800 + ( number of tables accessed * 20 ) + ( (number of applications connected + 1) * (200 + (number of tablespaces * 100) ) ) ) ) / 4096
You can click any column header at the top of the grid to sort the database list by the contents of that column. Sorting the list by the various status and interval measurement columns can help identify problem databases. You can also rearrange the order of the columns, and hide columns in the grid to put focus on the information you want to view.
The summary information that the Database Manager Summary drilldown displays is as follows:
The following tabs appear on the Database Manager Summary drilldown to provide additional information about a selected database or database partition:
Welcome to Spotlight on IBM DB2 LUW (Linux, Unix, and Windows). The help topics in this book cover features available in the interface when Spotlight is connected to a version 9 database.
Spotlight is a powerful database monitoring and diagnostic tool. Its unique user interface provides you with an intuitive, visual representation of the activity on the DB2 databases and database partitions that you choose to monitor. Graphical flows and line and fill graphs illustrate the activity on and between database components. Icons display the value of key statistics. Using the Spotlight browser, you can switch your monitoring focus between the various databases and partitions. Additionally, you can view activity at the DB2 instance level for any of these systems.
The power of Spotlight lies in its ability to provide visual and audible warnings if the performance metrics exceed acceptable thresholds. The components and dataflows on the home page change color to show you the source of the problem.
A range of reports and graphs provide you with detailed information about a DB2 database, database partition, or the instance to which the database belongs. This information can be viewed on the screen or be printed.
You can set Spotlight options to warn you when a threshold is reached. You can define a number of thresholds so that warning messages are displayed well before the traffic levels into or out of databases become critical.
Spotlight uses a number of different techniques to warn you when your DB2 instance or a database is exceeding a threshold. For example, to issue a warning, you can configure Spotlight to change a color on the home page or drilldown, provide an audible signal, or perform an action, such as send an email message.
The Agent Activity tab on the Database Manager Summary drilldown provides a summary of agent activity on each database and partition in the system.
The Agent Activity tab contains the following graphs, which keep track of agent activity over consecutive monitoring intervals:
High rates depicted on the graphs for the following activities might be indications of performance degradation and inefficient use of system resources.
In the Active Agents graph, comparing the number of agents from the agent pool to the number of agents created from the empty pool can help you determine if the agent pool is being used efficiently.
A high number of dynamically created agents from the empty pool can indicate two things:
The NUM_POOLAGENTS parameter should be increased.
The overall workload for this partition is too high and should be corrected by lowering the number of coordinating agents or reducing the workload.
A low number of dynamically created agents from the empty pool can indicate that NUM_POOLAGENTS is set too high. What this means is there are seldom used agents residing in the agent pool that are unnecessarily using system resources.
Both the local connections and remote connections statistics can help you gauge a need to adjust MAX_COORDAGENTS. If there are more connections than MAX_COORDAGENTS then applications that do not have a coordinating agent are inactive until there is a coordinating agent to service that connection. Because of this, the MAX_COORDAGENTS can be used to fine tune the load on the database server.
The idle agents graph can be used to fine tune the value of the NUM_POOLAGENTS parameter. Having idle agents available to service requests for agents can increase performance of the database server. In environments where there are many applications connected, it is generally recommended to increase the NUM_POOLAGENTS value to avoid the unnecessary overhead of creating and destroying agents.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center
