As you view drilldowns, you can filter them based on criteria specified in the Criteria tab. This is available for the following drilldowns: Database Analysis, Tablespace Analysis, Buffer Pool Analysis, Client Application Analysis, and Diagnostic Log.
Filtering lets you narrow the scope of the list shown in a drilldown. You can use it to focus on objects with a certain level of activity, certain attributes, or a certain current state. For example, you might filter a drilldown to see databases with the greatest I/O, tablespaces with the most direct writes, buffer pools with the lowest hit ratio, or applications that are currently connected.
Criteria for a drilldown can include multiple filters. The more filters you create, the narrower the scope of the drilldown list. Only items that meet filter criteria are shown. All others are filtered out. If no objects meet filter criteria, "No Data" is shown in the drilldown.
Filtering applies to the current database and current session. It is not saved when the session ends.
Note: When filtering is in use, an asterisk is shown beside the name of a drilldown's list tab. For example, when filtering is in use for the Tablespace Analysis drilldown, Tablespaces* is shown at the top of the Tablespaces tab.
Follow the procedure below to specify filter criteria. Before you create or modify filters, review the columns shown in the drilldown. The columns you can select for a filter are the ones currently displayed. If you want to filter on columns that are not currently displayed, select those columns in the Column Organizer. To open this window, right click any column header and select Organize Columns... from the right-click menu.
Note: The first filter you create determines which values are shown in the Value list box for the next filter. For example, if your first filter specifies "Content = Large" and you select the Extent Size column for the next filter, the Value list box shows extent sizes for tablespaces with the Large content type. If you want to use an extent size that is not listed, enter it in the Value list box.
To specify filter criteria
Click the Criteria tab for a drilldown.
If you plan to use multiple filters in criteria, select an option from the Result Set will include list box as follows:
|
Any |
Select this option if the result set should include items that meet criteria for one or more filters. Items are included even if they do not meet criteria for all filters. |
|
All |
Select this option if the result set should include items that meet criteria for all filters. Items are included only if they meet criteria for all filters. |
Specify criteria for a filter as follows:
|
a. |
Column |
From this list box, select a column for the filter. Objects are checked against values in this column. The list includes all columns currently displayed in the drilldown. |
|
b. |
Operator |
From this list box, select a comparison operator for column values. The choices are = (equal to), <> (less than and greater than), > (greater than), and < (less than). Use the = (equal to)operator for a column that shows an attribute such as status, name, or ID. |
|
c . |
Value |
From this list box, select the column value for the filter. In most cases, the values shown are for entire objects. Values for partitions are not listed. If a value for an entire object is not shown, you can enter it manually. Objects are checked to see if their values are equal to, less than and/or greater than this value (depending on the operator selected). |
Click Add to add the filter to the Active Filters list.
Repeat steps 3 and 4 for each filter you want to create.
To remove a filter from the Active Filters list, select it in the list, then click Remove. To remove all filters from the list, click Remove All.
Tip: To change the value for an active filter, remove the filter from the Active Filters list. Then create a new filter with the same column but a different value.
When you finish specifying filter criteria, click the information tab for a drilldown. The tab lists objects that meet filter criteria.
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 Details tab on the Client Applications Analysis drilldown provides the following information about the selected application:
Identification details about the application
Application status
The amount of time the application has spent on various activities during the last monitoring interval
The Application Information section lists information describing the application:
|
|
|
The Application Details sections provides statistics about the application:
|
| ||
|
| ||
|
| ||
|
|
The Caching tab on the Client Application Analysis drilldown measures the impact of the database’s resource caches (memory areas) on the selected application. This tab graphically depicts memory utilization statistics for package cache, catalog cache, the SQL workarea , and buffer pools for the application.
In general, caches enhance the performance of a database when their respective hit rates are high. Usually the hit rate is the ratio of retrieval requests that were satisfied by data already in the cache to the number of all requests—those satisfied by the cache plus those that required a disk read. (This ratio is expressed as a percentage in the various graphs on this tab.)
If you discover a cache utilization issue for a specific database on the Databases drilldown, use the information on this Caching tab to help determine whether the selected application is contributing to the problem.
Use the following graphs to follow cache performance over consecutive monitoring intervals:
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
