Nimsoft Monitor. db2mon Guide. v2.2 series

Transcription

1 Nimsoft Monitor db2mon Guide v2.2 series

2 Legal Notices Copyright 2012, CA. All rights reserved. Warranty The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft LLC disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft LLC shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft LLC and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control. Technology Licenses The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license. No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft LLC as governed by United States and international copyright laws. Restricted Rights Legend If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft LLC s standard commercial license terms, and non-dod Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR (c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR (June 1987) or DFAR (b)(2) (November 1995), as applicable in any technical data. Trademarks Nimsoft is a trademark of CA. Adobe, Acrobat, Acrobat Reader, and Acrobat Exchange are registered trademarks of Adobe Systems Incorporated. Intel and Pentium are U.S. registered trademarks of Intel Corporation. Java(TM) is a U.S. trademark of Sun Microsystems, Inc. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Netscape(TM) is a U.S. trademark of Netscape Communications Corporation. Oracle is a U.S. registered trademark of Oracle Corporation, Redwood City, California. UNIX is a registered trademark of the Open Group. ITIL is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries. All other trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

3 Contact Nimsoft For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products. At you can access the following: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads Nimsoft Support policies and guidelines Other helpful resources appropriate for your product Provide Feedback If you have comments or questions about Nimsoft product documentation, you can send a message to support@nimsoft.com.

4

5 Contents Chapter 1: db2mon Requirements... 8 Configuration... 9 Setup Snapshot_i Snapshot_db Snapshot_bp Snapshot_app tspace_stats The Menu bar Buttons in the Toolbar Context menu Real-time monitor displays Real-time monitor functions Show connections Show connection detail Find lock holder Add new application to configuration file Adding multiple DB2 instances for monitoring Contents 5

6

7 Chapter 1: db2mon 2.2 The db2mon probe is designed to monitor DB2 database managers (instances), databases, data sets and DB2 applications. The db2mon probe uses the DB2 monitoring APIs for snapshot and table space statistics. The DB2 monitoring API can be attached only locally, therefore the db2mon probe has to run on the same physical machine where the DB2 instance to be monitored is running. The db2mon probe has two parts: Alarm generation. Real-time monitor. This section contains the following topics: Documentation Changes (see page 8) Requirements (see page 8) Configuration (see page 9) The Menu bar (see page 16) Buttons in the Toolbar (see page 17) Context menu (see page 19) Real-time monitor displays (see page 22) Real-time monitor functions (see page 24) Adding multiple DB2 instances for monitoring (see page 26) Chapter 1: db2mon 2.2 7

8 Requirements Documentation Changes This table describes the version history for this document. Version Date What's New? 2.2 January 2010 Tablespace query, statistics fixed and QoS enabled. Related Documentation Documentation for other versions of the db2mon probe Getting Started with Nimsoft Probes Nimsoft Probes Reference Requirements DB2 Environment DB2 Version 5.2 or higher. DB2INSTANCE variable has to be filled. MON_HEAP_SZ instance configuration parameter >= 64. SYSADM user-id. Nimsoft Environment Robot version >= 2.0. db2mon authorization key for alarm generation. db2mon-rt authorization key for real-time monitor. Administration user-id. 8 db2mon Guide

9 Configuration Configuration More than 200 different parameters are being monitored, and each parameter can be separately configured for each monitored object (instance, database etc.). In case a parameter is not configured for an object, values are inherited from default definitions (under the db2mon node). Setup parameters are inherited hierarchically from higher-level objects. Two levels of alarm messages can be generated for each parameter. The severity levels are configurable. More Information Setup Snapshot_i Snapshot_db Snapshot_bp Snapshot_app tspace_stats Chapter 1: db2mon 2.2 9

10 Configuration Setup There are two ways to edit setup parameters: Right-click on the "setup" node, or left-mouse double-click a parameter. 10 db2mon Guide

11 Configuration Fig: Edit setup. The setup parameters: Instance: Auto-Discovery (discovery_i) Can be yes or no, it determines if the auto discovery function for instances, should be used. Auto discovered objects are automatically written into the configuration file with parameter discovery_i = yes. Snapshot (snapshot_i) Can be yes or no, it determines if the instance snapshot should be activated. Note (for UNIX systems): To find multiple instances, the probe needs to read the "node directory". Every "node directory" belongs to an instance, therefore the probe needs to be attached to one - default - instance. The default instance name is set in the environmental variable "DB2INSTANCE". DB2INSTANCE variable is filled in the script "db2profile". For this instance, all other instances on that server need to be catalogued in the "node directory" of this "default" instance, using the command "catalogue local node...", otherwise the Auto_Discovery feature for instances will not work. Database: Auto-Discovery (discovery_db) Can be yes or no. Determines if the auto discovery function for databases should be used. Auto discovered objects are automatically written into the configuration file with parameter discovery_db = yes. Snapshot (snapshot_db) Can be yes or no. Determines if the database snapshot should be activated. Table space: Auto-Discovery (discovery_ts) Can be yes or no. Determines if the auto discovery function for table spaces should be used. Auto discovered objects are automatically written into the configuration file with parameter discovery_ts = yes. Snapshot (snapshot_ts) Can be yes or no, it determines if the table space statistics monitoring should be activated. Application: Auto-Discovery (discovery_app) Chapter 1: db2mon

12 Configuration Can be yes or no. Determines if the auto discovery for running applications should be used. Auto discovered applications are automatically written into the configuration file with parameter auto_discovery = yes. Snapshot (snapshot_app) Can be yes or no. Determines if the application snapshot should be activated. Static SQL text (static_sql_text) Can be yes or no. Determines if the db2mon will access the DB2 catalogue to obtain text of monitored static SQL. Bufferpool: Auto-Discovery (discovery_bp) Can be yes or no. Determines if the auto discovery for active bufferpools should be used. Auto discovered bufferpools are automatically written into the configuration file with parameter auto_discovery = yes. Snapshot (snapshot_bp) General: QoS Can be yes or no. Determines if the bufferpool snapshot should be activated. Activates collecting of historical data into SLM database. Threshold sampling Activates sampling of snapshot data (not tablespace statistics!) for all checkpoints, which can be used as base for thresholds setting. After the data sampling was finished, this parameter will be automatically set to "inactive" (sampling_at_start=no), to avoid loss of colleted data in case of restart. If you activate threshold sampling you have set additional parameter: 12 db2mon Guide

13 Configuration Time in hours (sampling_time) Number of hours the interval data will be collected. The number of collected intervals should be close to 100 and it should be run in time, which represents typical workload for the database. Method (sampling_method) Can be "average", "top" or "percentile". Sets the method used to calculate the threshold value out of the collected data. Average: The probe calculates simple average value. Top: The probe takes the top value (biggest or smallest). Percentile: The probe calculates percentile value, to eliminate untypical peaks. Percentile value (sampling:pctle) Value for percentile calculation, must be between 90 and 99. E.g. percentile 95 means, that 95% of the collected values have to be below (above) the calculated value. Alarm increase (sampling_alarm) Value in %, used to increase the calculated value to get reasonable alarm threshold. Warning decrease (sampling_warning) Value in %, used to decrease the calculated value to get reasonable warning threshold. Other parameters: DB2 user (user, pw) User-id and password used to log on to the monitored instance, needs to have a SYSADM authorization. Each instance can use different user-id and password Nimsoft user Nimsoft administrator user-id and password, used to log on to the Hub, in order to receive DB2 alarm messages to the sub-console included in the DB2mon GUI. Snapshot Interval (in min.) Sets the snapshot-monitoring interval in seconds; default is 300 sec (5 minutes). Log Level Determines level of logging, can be between 0 and 5 into nimdb2.log data set, default is 0. Statistics Interval (in min.) Sets the statistics-monitoring interval in minutes; default is 60 min. Chapter 1: db2mon

14 Configuration Snapshot_i The container snapshot-i contains all available snapshot parameters for instance monitoring. Every line contains a checkbox for activation of that particular parameter monitoring, its alarm and warning values, evaluation operator (mostly < and > ), alarm and warning severity values (1-5) as well as a QoS activation field (tells, if that particular parameter and its values should be written into the Quality of Service database). A severity value of 1 means the corresponding warning/alarm will not be checked. Left-mouse double-clicking a parameter allows you to edit the parameter values. Snapshot_db The container snapshot-db contains all available snapshot parameter for database monitoring. Every line contains a checkbox for activation of that particular parameter monitoring, its alarm and warning values, evaluation operator (mostly < and > ), alarm and warning severity values (1-5) as well as a QoS activation field (tells, if that particular parameter and its values should be written into the Quality of Service database). A severity value of 1 means the corresponding warning/alarm will not be checked. Left-mouse double-clicking a parameter allows you to edit the parameter values. Snapshot_bp The container snapshot_bp contains all available snapshot parameters for bufferpool monitoring. Every line contains a checkbox for activation of that particular parameter monitoring, its alarm and warning values, evaluation operator (mostly < and > ), alarm and warning severity values (1-5) as well as a QoS activation field (tells, if that particular parameter and its values should be written into the Quality of Service database). A severity value of 1 means the corresponding warning/alarm will not be checked. Left-mouse double-clicking a parameter allows you to edit the parameter values. Snapshot_app The container snapshot_app contains all available snapshot parameters for application monitoring. Every line contains a checkbox for activation of that particular parameter monitoring, its alarm and warning values, evaluation operator (mostly < and > ), alarm and warning severity values (1-5) as well as a QoS activation field (tells, if that particular parameter and its values should be written into the Quality of Service database). A severity value of 1 means the corresponding warning/alarm will not be checked. Left-mouse double-clicking a parameter allows you to edit the parameter values. 14 db2mon Guide

15 Configuration tspace_stats The container tspace_stats contains all available table space statistics parameter for table space monitoring. Every line contains a checkbox for activation of that particular parameter monitoring, its alarm and warning values, evaluation operator (mostly < and > ), alarm and warning severity values (1-5) as well as a QoS activation field (tells if that particular parameter and its values should be written into the Quality of Service database). A severity value of 1 means the corresponding warning/alarm will not be checked. The values for status parameter are numeric values of a bit-mask, where every bit is a switch for a particular status. To see the meaning of these numbers, you have to edit the status parameter (double-click). In the edit mask you can see which status values are checked. Left-mouse double-clicking a parameter allows you to edit the parameter values. Chapter 1: db2mon

16 The Menu bar The Menu bar This section gives a short description of the different functions and tools found in the Menu Bar. File Close Edit Close the GUI session. Undo To clear all changes made since last save. Save To save all changes. List Unsaved Changes To list all changes made since last save. Options Show Reset Dialog To switch reset-dialog display off/on. Confirm Save cfg To switch confirmation during changes of configuration file off/on. List unsaved changes View To list all changes made since last save. Statusbar and Toolbar List Toggle function to show or hide the Status Bar and the Toolbar. To set format of the list-view to list. Detail To set format of the list-view to detail. Refresh To read the configuration file and refresh monitor data. 16 db2mon Guide

17 Buttons in the Toolbar Buttons in the Toolbar Chapter 1: db2mon

18 Buttons in the Toolbar Back, Forward To move the focus in the tree from node to node. Monitor mode / Setup mode toggle Setup mode hides all objects in the hierarchy tree, necessary only for configuration settings. Refresh To read the configuration file and refresh monitor data. Check-parameter filter To show only active (checked) monitoring parameters. List format To change the list format. Reset To show the "reset monitor" dialog. Fig: Reset monitor dialog. 18 db2mon Guide

19 Context menu Context menu The context menu is displayed by using the right-mouse button on tree node. Not all functions are available for all objects. Add To add an object instance, database, table space or application into the tree / configuration file hierarchy. Delete To delete an object from the tree / configuration file. Cancel Edit To cancel context menu. To edit objects properties. Show connections To show active connections. Show sampling report To show sampling data, created by threshold sampling function. Sampling report can be used to edit and save collected data as thresholds into the configuration file, both as default or object data. By editing the "Key" you can save the data to every object you need (be careful to pick up same object class, the probe could be delivering unexpected results!). Chapter 1: db2mon

20 Context menu 20 db2mon Guide

21 Context menu Show alarm console To show alarm console window with filter set for the desired object. Chapter 1: db2mon

22 Real-time monitor displays Real-time monitor displays The real time monitor data for applications are organized in lists, showing (so far applicable) three values: The interval value, calculated by db2mon. The total-value value for the lifetime of the object or since last reset. The top-value the highest/lowest interval value since start of monitoring or since last reset. All connections/parameters, causing an alarm/warning are marked by colored arrows, to make the display easier to read. The other objects (instance, database, buffer pool) are showing always Current interval value since start of this interval. Last interval value for last complete interval. Top interval the top value since start of db2mon. Cumulated value since DB2 start (if applicable). The values are sorted by alarm severity; inactive checkpoints are marked by grey arrow. Where applicable the probe shows the DB2 configuration parameter values (they cannot be changed here). 22 db2mon Guide

23 Real-time monitor displays Fig: Connection list. Chapter 1: db2mon

24 Real-time monitor functions Real-time monitor functions The real time monitor offers some special functions to make the monitoring easier. More Information Show connections Show connection detail Find lock holder Add new application to configuration file Show connections Beside of the node context menu, you can also click the "application" node to display all connections, or on one of the applications to display all connections using this application. The connections list on the right side is sorted by used CPU, but can be sorted by other columns on demand. Show connection detail Connection detail display can be reached, either by clicking the connection node in the tree, or the connection line in the connections list. 24 db2mon Guide

25 Real-time monitor functions Find lock holder A connection name, waiting for a lock, is displayed in red color. By double-clicking the line in the "Waiting for lock" list, real-time monitor switches to the connection, holding this lock and blocking the other connection. Fig: Waiting for lock display. Add new application to configuration file Adding new applications (in case you are not using discovery_app = yes, which is recommended) for snapshot-monitoring can be done by two different methods. Either you know the application name. Then you right-click the "application" node and put the name into displayed sub-window. Or, if you display all connections, you can right-click the cyan-colored application name and select add. The node will then be added into the configuration file. Chapter 1: db2mon

26 Adding multiple DB2 instances for monitoring Adding multiple DB2 instances for monitoring UNIX/Linux 1. In the starting shell (which is not neccessarily inst_init.sh - it depends on platform), you need to run the db2profile script for one of the instances. This instance then becomes the so called "default instance", it means that the probe will always first connect to this instance. You can check in the controller GUI with the "robot environment" button if all variables are properly set (DB2INSTANCE, PATH). 2. You have to register all other instances in the "node directory" on the default instance. The DB2 command is: db2> CATALOG LOCAL NODE node-name INSTANCE instance-name The probe will list the node catalog and "autodiscover" the instances here. Or, you can add the instances in the GUI if you do not want the "auto-discover" feauture (e.g. you do not want all instances to be discovered). But in any case, the instances have to be in the node directory. You can check by listing the node directory - connect to the default instance and run: db2> list node directory Windows On Windows, the DB2 installation maintains both the "default instance" and the node directory automaticaly. But it can be done the same way, with the difference, that the default instance is defined by a set of system variables. If the default instance name is DB2, there is no need to define the DB2INSTANCE variable. 26 db2mon Guide