Nimsoft Monitor. informix Guide. v4.1 series

Transcription

1 Nimsoft Monitor informix Guide v4.1 series

2 Legal Notices Copyright 2012, Nimsoft Corporation 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 Corporation 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 Corporation 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 Corporation 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 Corporation 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 Corporation 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 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.

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: informix informix Requirements... 9 informix Installation notes for Windows Installation notes for Unix informix Configuration The Setup tab The Connections tab The Profiles tab The Templates tab The Status tab The Groups tab Informix - Defining a new checkpoint Informix - Editing a checkpoint Informix - Thresholds Informix - Schedules Checkpoints metrics Single counter description Glossary 45 Contents 5

6

7 Chapter 1: informix 4.1 This description applies to informix probe version 4.1x The Informix probe will run selected SQL's to extract vital information about your Informix databases. The information is presented to the database-administrator as alarms and/or as a report. The following information is extracted and monitored: Monitor connectivity to the database server Monitor the uptime (in days) of the database server Monitor the number of databases Monitor the logging status of the databases Monitor the number of active users Monitor databases for offline status Monitor if database is recovering Monitor if database is inconsistent Monitor if database mirror is offline Monitor if database mirror is recovering Monitor database free space (percent) Monitor database free space (MB) Monitor buffer cache hit ratio for reads Monitor buffer cache hit ratio for writes Monitor table extents Monitor table size (MB) Monitor number of attempts to exceed the maximum number of locks Monitor number of attempts to exceed the maximum number of threads Monitor number of failed attempts to allocate entries in the transaction table Monitor number of times threads had to wait for a latch Monitor number of times threads had to wait for a buffer Monitor number of times sessions had to wait for a lock Monitor number of times threads had to wait for critical section checkpoints Monitor number of times potential deadlocks are detected and prevented Monitor number of times distributed deadlock timeout is exceeded while user is waiting for lock Chapter 1: informix 4.1 7

8 informix Requirements Monitor number of foreground writes Monitor number of LRU writes Monitor number of chunk writes Monitor number of users waiting for locks Monitor users waiting for locks Monitor chunk I/O read statistics Monitor chunk I/O write statistics Monitor virtual cpu user time Monitor virtual cpu system time This section contains the following topics: Documentation Changes (see page 9) informix Requirements (see page 9) informix Installation notes for Windows (see page 10) Installation notes for Unix (see page 11) informix Configuration (see page 12) Informix - Defining a new checkpoint (see page 28) Informix - Editing a checkpoint (see page 34) Checkpoints metrics (see page 40) 8 informix Guide

9 informix Requirements Documentation Changes This table describes the version history for this document. Version Date What's New? 4.1x October 2011 Initial Release informix Requirements Software: Informix Connect 3.50, Informix Client SDK 3.50 (or higher) and Informix 9.x, 10.x, 11.5, 11.7 Platforms: Windows 32/64 bit, Linux 32/64 bit, Solaris 8 and higher on Sparc 32/64 bit, Solaris on Amd 64 and i386 Hardware: Windows NT/2000/XP/2003/2008 Chapter 1: informix 4.1 9

10 informix Installation notes for Windows informix Installation notes for Windows Informix Connect or the Client SDK (which contains Informix Connect as well) must be installed prior to installation of this probe. Please refer to the installation documentation for the Client SDK or Informix Connect for information on how to install the connectivity to Informix. Informix Connect or the Client SDK must be in the systems PATH environment variable. Run the setnet32 application for Informix to set up connectivity with the databases you wish to monitor. Please note that you must not check the 'Use my settings' checkbox in setnet32. The following keys must exist in the Windows Registry for the probe to be able to connect: HKEY_LOCAL_MACHINE\Software\Informix\Environment\INFORMIXSERVER HKEY_LOCAL_MACHINE\Software\Informix\Environment\INFORMIXDIR HKEY_LOCAL_MACHINE\Software\Informix\SqlHosts\[one entry for each database] They should be created by setnet32 if the 'Use my settings' checkbox is unchecked, otherwise they are created under HKEY_CURRENT_USER. The dbping utility which is also a part of Informix Connect and the Client SDK allows you to test connections set up with setnet32. Verify a database connection definition by running this utility to check for connectivity. Note that database definition names are case sensitive, so you should always check the definition in setnet32 or the Windows Registry prior to setting up a profile in the probe. Note: The user configured in the connection parameters or in the odbc DSN must have CONNECT privileges on the Informix database server. The target database selected for connection must be sysmaster for the predefined checkpoints to work 10 informix Guide

11 Installation notes for Unix Installation notes for Unix Informix Client SDK 3.5 must be installed in unix platform prior to installation of informix probe on that unix machine. Informix server can be connected Either ODBC DSN connection OR providing user, password, database,service, hostname information through informix GUI. Following Environment variables are required for successful informix connection with Informix Server. Set the INFORMIXDIR variable to the directory where you installed the informix Client SDK.eg. export INFORMIXDIR=/opt/IBM/informix. set LD_LIBRARY_PATH variable with informix client libraries path.eg. export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/informix/lib/cli:/opt/IBM/informi x/lib/esql. Set ODBCINI variable to odbc.ini file path. odbc.ini file keeps odbc dsn connection information for informix.eg. export ODBCINI=/opt/IBM/informix/etc/odbc.ini Following steps are required for creating odbc dsn connection. The service name for Informix database should be defined in /etc/services configuration file. One example is given below testinformix 6605/tcp Add a line in $INFORMIXDIR/etc/sqlhosts file for Informix databases server. Each line in Sqlhosts file contains server, protocol, hostname, service/port information for a Informix database server. One example is given below informix server onsoctcp Add new ODBC dsn entry in $INFORMIXDIR/etc/odbc.ini file. One example for "testdb" ODBC DSN is given below [testdb] Driver=/opt/IBM/informix/lib/cli/iclis09b.so Description= IBM INFORMIX ODBC DRIVER Server=informixserver Database=sysmaster LogonID=Informix pwd=redhat CLIENT_LOCALE=en_us DB_LOCALE=en_us TRANSLATIONDLL=/opt/IBM/informix/lib/esql/igo4a304.so Chapter 1: informix

12 informix Configuration informix Configuration The initial configuration of the Informix probe is done by using the configuration tool (GUI), setting up one or more database instance profiles. The probe may be running locally on the database server, or it may be configured to run as a remote client. The probe is configured by double-clicking the line representing the probe in the Infrastructure Manager. This brings up the configuration tool for the probe. The Setup tab This property-sheet will set the general run-time parameters regarding the Informix probe. Field Setup tab Description Generate status only Instructs the probe to only generate status, not to issue an alarm when a threshold is breached. Select the Status tab to see the status for the different checkpoints. 12 informix Guide

13 informix Configuration Field Alarm severity filter Status Auto-Update Log Size Log level QoS V2 Compatibility Description Sets a "filter" on which severity levels to be considered as alarms. The Informix probe is capable of checking many areas of the databases. Some events that are generated are vital and key to the performance and availability of the database. As a database administrator, you may want to pass the important events on to the operations centre or helpdesk, so the event can trigger pagers, etc. The Alarm severity filter will consider the events matching the selected severity level and higher as alarms, and pass these on whenever the Generate status only option is unchecked. If you e.g. set this to be major, then only messages with severity major and upward are considered as alarms. A checkbox lets you activate/deactivate the Status Auto-Update functionality described below: The "Status Auto-Update" parameter (number of seconds) specifies the automatic refresh interval of the Status Window on the Status tab. Setting this parameter to a value higher than 0 and then selecting a profile on the Status tab, the status will be automatically updated every x seconds. The checkpoints of the selected profile will be displayed until selecting another profile. Note that this parameter is a "dialog" value - it means it is not saved in the configuration file, but in the machine running the dialog (same as for example widows size). Set the size of the probe s log file to which probe-internal log messages are written. The default size is 100 KB. When this size is reached, the contents of the file are cleared. Sets the level of details written to the log file. Log as little as possible during normal operation, to minimize disk consumption. Select this checkbox to generate the suppression key in alarm messages and target in QoS messages as per the format defined in version 2 of Informix probe. By default, the suppression key in alarm message and target in QoS message is generated as per the format defined in version 4 of Informix probe. Chapter 1: informix

14 informix Configuration Field Message pool tab Description This tab contains a list of all alarm messages available. You select messages from this list when editing the properties for a checkpoint. Right-clicking in the list, allows you to add, edit, copy or delete messages. Informix, defining a message Select the Message pool tab, right-click in the list and select New. You must specify a message name in the pop-up dialog box. Note: While creating an alarm message, use the name of the checkpoint followed by a two-character index, as the message name. For example: 'dbspace_size_mb_xx' 14 informix Guide

15 informix Configuration Select the checkpoint for which you create the alarm message in the drop-down list, and all variables available for that check-point will be listed in the right part of the dialog. Type the message and pick the variables you need. Click the OK button when finished. The new message should now appear in the message pool. Chapter 1: informix

16 informix Configuration The Connections tab This list contains the various connections to instances that the Informix probe will monitor. You need to specify user name, password and service name you want to use to connect to the instance. The password information is encrypted and placed into the configuration file. A connection can be used by more than one profile. The list contains one predefined connection that you may modify to your preferences. You may add, edit delete and copy connections. Select the connection and choose Edit from the right pop-up menu, to open the connection property window for editing. 16 informix Guide

17 informix Configuration Field DSN Protocol Driver Service Server Name Host User ID and Password Database Timeout Description Select this check box to create a DSN connection. In a DSN connection, you do not need to specify the rest of the parameters except password. Select the protocol of the connection. Enter the name of the driver for the connection. Enter the connection service name. Enter the connection server name. Enter the name of the host on which this connection should run. In case of SQL Server authentication, provide the user name and password for the SQL server. In case of Windows authentication, provide the user name and password for the domain. Enter the name of the database for the connection Defines how long the probe will wait for answer before it aborts the connection process. Test button: Clicking this button will test if the connection can be made. If successful, it will return the instance name and its version number. If not, an error message will be returned. Chapter 1: informix

18 informix Configuration The Profiles tab The list contains a sample profile that you may modify to your preferences. Every profile will run as a separate thread, and multiple profiles can be used to monitor one instance. This way the probe can be configured to deploy available resources the best way and allows independent monitoring of several instances simultaneously. Icons in the profile list Green icon in the profile line means the profile is active and running. Yellow icon means the profile is active but suspended (the suspend / resume button in the profile properties dialog allows stopping / starting profile monitoring dynamic, without deactivating /activating the probe). Black icon shows the profile is inactive. 18 informix Guide

19 informix Configuration You may add, edit, delete and copy profiles. The suspend /resume commands allows stopping / starting profile monitoring dynamic, without deactivating /activating the probe. Selecting the profile and choose Edit from the right popup-menu, opens the profile property window for editing. The upper part of the window shows general profile properties and defaults. At the bottom, you will find a list of available checkpoints. Field Description Heartbeat Connection Description Short description of the profile. Defines the interval, at which all profile checkpoints schedules will be tested and trigger eventual checkpoint execution. This number should be common denominator to all used check interval values. The higher the value the lower is the profile overhead. Connection used in this profile. It has to be defined in "Connections" dialog before crating a profile. Chapter 1: informix

20 informix Configuration Field Check interval Clear message SQL timeout Message Profile timeout Message Timeout severity Suspended/Resumed (indicator) Alarm Source Profile checkpoints Alarm Source Description Default value for check interval in the profile. Will be used if nothing else is defined in the checkpoint and overwrites the default checkpoint list setting. Message name for clear alarm. Every checkpoint query run asynchronously. In case the query reaches the SQL timeout, the checkpoint processing will be terminated and the next checkpoint will be started. Alarm is issued. Message name used for SQL timeout alarm. Defines the maximum processing time for all checkpoints in the profile. If this timeout is reached, the interval processing is finished and the probe waits for next heartbeat to evaluate any checkpoint schedules. Alarm message is issued. Message name used for profile timeout alarm. Severity for timeout messages. This indicator is green when the profile is activated. The indicator changes to yellow when the profile is suspended and to black when deactivated. This option lets you override the source name of the alarm. At the bottom, you will find a list of available checkpoints. When defining a new profile, all checkpoints available (listed under the Checkpoints tab) will be listed here. Select the checkpoints you want for your new profile. The global and default checkpoint settings will be used, unless you modify the settings locally for your profile (see Note below this table). Possibility to change the source for issued alarms. If not used, default is assumed (robot IP). 20 informix Guide

21 informix Configuration Note on checkpoint types While defining a profile, you can use two different strategies to handle Checkpoints in a profile. You can decide to use checkpoint templates dynamic, which means that the checkpoints are defined globally (under the "Templates" tab) and represent the default settings. Every time you change the template value, it will reflect on all profiles using dynamic templates strategy. To have specific settings applicable just for one profile, right-click the checkpoint in the list and select Change to static. Chapter 1: informix

22 informix Configuration Now you can double-click the checkpoint to modify the properties, and the settings will be valid for this profile only. Note: If attempting to modify a template checkpoint in the Profile dialog without changing it to static as described above, you will get a warning like this: You can use both template" and "static" checkpoints in same profile. If a checkpoint is managed as static, the checkpoint name will appear in the list with a blue color, and it will be marked as static in the column Type. Conclusion: Static. To manage the properties for a checkpoint locally, "change" the checkpoint to static in your profile before modifying it. When modified, the new settings will be valid for this profile only. Template. To edit the properties for a checkpoint template, double-click the checkpoint in the profile list or Templates tab. When modified, the new settings will be valid for all profiles, unless overruled by static settings in the profile. Please see Single counter description for a description of different checkpoints. 22 informix Guide

23 informix Configuration The Templates tab The list contains the predefined set of checkpoints that you may use in your profiles. These checkpoints can be modified to your preferences. By default, most checkpoints are active with a reasonable default threshold value. The checkpoint properties can be used in a profile either dynamically, using the template values, or they can be added to the profile and managed statically in the profile. Chapter 1: informix

24 informix Configuration The Status tab The status is presented in a hierarchal fashion, with a profile name nodes and one or more checkpoint nodes (only active checkpoints are considered here). The highest status is propagated. Select the checkpoint in the navigation tree (to your left) to bring up the corresponding events. Changing the individual values for checkpoints: The properties for an individual checkpoint object can also be modified here. Select a profile and a monitored checkpoint in the left pane. Then double-click an object in the right pane. If the object belongs to a template object, you will be warned that a modification will make the checkpoint static for the selected profile. See the section Editing a checkpoint for a description of the checkpoint properties. 24 informix Guide

25 informix Configuration The Groups tab This tab allows user to create multiple groups which can be associated with profiles. To add a group, right click in the Group tab and select New option. Add New Group dialog appears. Chapter 1: informix

26 informix Configuration Enter a name for the group and click OK. New Group dialog appears. Enter a description for the new group in the Description text box. From the Group Checkpoints section, select the checkboxes for the check points that you wish to enable for the new group. Click the OK button. 26 informix Guide

27 informix Configuration The new group can now be selected from the Group drop-down in the Edit Profiles dialog. Chapter 1: informix

28 Informix - Defining a new checkpoint Informix - Defining a new checkpoint Select the Templates tab, right-click in the checkpoint-list and select "Create new". A dialog pops up, and you must give the new checkpoint a name: 28 informix Guide

29 Informix - Defining a new checkpoint The difference to regular edit checkpoint dialog is the additional "Query" tab. SQL query is the data source and therefore the central piece for every checkpoint. It is recommended to test the query first with SQL Server Management Studio (or other tool) before you start to create new checkpoint. The query has to return at least one numeric column, which will be used as checked value (all numeric formats are supported). If the query returns more than one row, the probe needs unique identification per row which will be used as part of suppression key and QoS definition. The row key can be created by concatenating several columns in the checkpoint definition. Additional columns can be retrieved to be used in generated messages. Tip: Use rtrim and ltrim functions to remove leading and trailing blanks from string variables! Use explicit column names for manipulated values; avoid generated names like Col0, Col1 etc. Queries are stored in separate files, not in the configuration file itself. Create the file, then use the "Read" button first, and then "Test" to test the query. Chapter 1: informix

30 Informix - Defining a new checkpoint On selecting the checkbox Interval modus, the variable "$interval_value.i" is added to the Message variables textbox. The "interval_value" variable can be configured using the Raw Configure dialog box. You have to run a successful test every time you want to make any change to the query itself, also the query test is necessary for the probe to have all information about retrieved columns to be able to define all checkpoints variables. Next step is to define checkpoints variables by hitting the "Edit" button in the "Message variables" line. This opens new window with a list of all available columns and their possible usage. You have to define their use and format. Numeric columns can be used as: Value candidate for checkpoint checking with standard formatting Value size candidate for checking, formatted as file size (B, KB, MB, GB or TB) Value int candidate for checking, formatted as integer number Information no checking, standard formatting (if available 2 digits after comma) Character columns: Row key candidate for row identification, string formatting. Information string formatting. 30 informix Guide

31 Informix - Defining a new checkpoint The next step is to choose which variable to be used for checking and to set the comparison operator. Then, if your query returns more than one line, you need to define unique row key. To see which variables you can use you need to type the sign "$" into the "Row identification" line, and a sub list with all suitable variables will appear. Chapter 1: informix

32 Informix - Defining a new checkpoint Last setting on this page is the "interval modus" checkbox. If you check interval modus, then the probe will always subtract the variable value at the beginning of an interval from the value at the end of the interval and use the result for checking and QoS. If you do not check the interval value checkbox, the value of variable, as it returned from the query will be used for checking and QoS. 32 informix Guide

33 Informix - Defining a new checkpoint You need to define the rest of the checkpoint processing settings, like: Check interval value Samples scheduling thresholds messages QoS definitions You can also create a "hint" text, but it is not mandatory. Chapter 1: informix

34 Informix - Editing a checkpoint Now you can save the definition and restart the probe to start using this new checkpoint. Informix - Editing a checkpoint The checkpoint properties may be used in a profile either dynamic, using the template values, or they can be added to the profile and managed static in the profile. Static. To edit the properties for a checkpoint locally for a profile, right-click the profile in the Checkpoints list in the profile dialog and change it to static. Then double-click the checkpoint to modify it. When modified, the new settings will be valid for this profile only. Template. To edit the properties for a checkpoint template, double-click the checkpoint in the profile list or Templates tab. When modified, the new settings will be valid for all profiles, unless overruled by static settings in the profile. The properties for checkpoints are described below: 34 informix Guide

35 Informix - Editing a checkpoint The upper part of the window contains general checkpoint settings. The lower part contains two lists with threshold and schedule settings. Field Description Description Active Condition Check interval Send Quality of Service QoS List Short description of the purpose of the checkpoint. Check this option to activate the checkpoint. Information, describing how the threshold values are evaluated. Interval value used for this checkpoint. Every checkpoint can have a different check interval value. Default is taken from the profile definition, if not defined than from the default checkpoint list. Activates QoS values being send into the QoS database. If not available in a checkpoint, checkbox is disabled. Clicking this button opens the QoS list, showing the current QoS definitions (default is one definition per checkpoint). Right-clicking in the list lets you add new QoS definitions and copy, edit or delete an existing QoS definition. definition The "Edit QoS" dialog offers available metrics (numerical variables which could be reported as QoS) and available object variables (if any - to be added to the QoS source). The name of the QoS has to start with the checkpoint name. QoS can be activated/deactivated as usual. Note that some of the checkpoints have no QoS possibilities - from these checkpoints the QoS dialog cannot be activated. Chapter 1: informix

36 Informix - Editing a checkpoint Field Samples Use excludes Description The probe will save the number of samples specified here and calculate an average value. This average value will be compared to the alarm threshold specified (see threshold description below the table). Setting "Samples = 1", no sampling is done. Setting "Samples = 3", the average of the 3 last samples will be used. Setting "Samples = 0" (in profile), number of samples will be taken from the template. If not set there, no sampling is done. Initially after start-up, the probe calculates the average value from the number of samples available. Example, Samples=3: In the first interval the first sample value is used In the second interval, the average of sample 1 and 2 will be used etc. NOTE: Many checkpoints calculate an "interval value", therefore in the first interval there is no value at all (no threshold checking). Checking this option gives you the possibility to add excludes to the "exclude list" to some of the checkpoints (as it does not make sense for all checkpoints). Using excludes, you can define objects that you do NOT want to monitor on the checkpoint. The excluded patterns are found if clicking the Excludes list button (see below) will be used for the checkpoint. 36 informix Guide

37 Informix - Editing a checkpoint Field Excludes list Scheduling Description Clicking this button opens the Excludes list. This list shows if excludes are defined for the checkpoint. The excludes found in the list will be used for the checkpoint if the Use excludes option (see above) is checked. Right-clicking in the list lets you add new excludes or edit, copy or delete existing excludes. When adding (or editing) an exclude pattern, a "match expression" dialog is opened, letting you edit or define the exclude pattern. Excludes are defined using regular expression patterns. A test button lets you test the exclude pattern defined. This test is possible only for running active profiles and checkpoints. The test uses the status list (on the status tab) as input: Note that if there already are active excludes, the excluded objects are excluded from the status list BEFORE the test. When clicking the test button, an exclude test list pops up, showing the result of the test: Red text lines show the objects which would be excluded using the tested pattern. The "object thresholds" are functioning as an "include list" - it means, if there are special thresholds defined for a special object, this object will always stay in, even if the exclude pattern would eliminate it normally. This is considered also in the test function. This field lets you select how to use the schedules settings, if any (see description below the table). Rules Selecting Rules means to run according the rules described in the Schedules settings. Exceptions Selecting Exceptions means to run except the rules described in the Schedules settings. Chapter 1: informix

38 Informix - Editing a checkpoint Field Clear message Clear severity Thresholds/Schedules Description Message name used for clear alarm message. Severity, used for message issued in normal state. See description below the table. Informix - Thresholds The list contains the predefined set of monitoring profiles that you may use in your profiles and that you can modify to your preferences. By default, most profiles are active with a reasonable default threshold value. The threshold values may be defined by modifying checkpoints in the respective profile. Every checkpoint has to have at least one threshold, but there can be additional thresholds defined. The threshold identification consists of an object name (if applicable), like tablespace name, userid etc. and a threshold ID, numbered from 0. Threshold values have to be descending or ascending, depending on condition used in a checkpoint, starting with the highest severity threshold condition. Field Threshold object name Threshold value Description Monitoring object name, if applicable or default. Some special checkpoints have a second threshold called count" (e.g. "locked_users"). Value used for threshold evaluation 38 informix Guide

39 Informix - Editing a checkpoint Field Current value Severity Message Message text Variables Description If invoked from the status report, it contains the last measured value. Alarm severity. Name of message used for threshold alarm. Text of the message, containing variables, which will be replaced in run time. If the message text is changed from a profile list, you will be forced to create new message. List of variables, available in the checkpoint. Informix - Schedules If the schedules list is empty, the checkpoint will be executed in interval matter, 24 hours a day. Additional to it there can be defined number of schedules per checkpoints, which can define additional rules to the check interval or exceptions of it. Rules and exceptions cannot be mixed in one checkpoint. In principle, a schedule is a definition of an execution period (or execution break if exceptions used) with specified days, time from/to and date from/to values. Additionally to it, if only date from and time from is defined, first execution can be defined. Run once will cause the checkpoint run only once a day in the defined period (unlike multiple times if interval used). Chapter 1: informix

40 Checkpoints metrics Checkpoints metrics There are five kinds of metrics used: Count absolute number of events in the interval. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the server". Count/sec absolute number of events in the interval per second. It is calculated as delta between count at the beginning of the interval and at the end, divided by length of the interval in seconds. In the first interval, counts are not checked because their interval value cannot be calculated. If there is a "total" value in the message, it means "since the start of the server". Gauge absolute number, describing the actual state of the system. If it describes size, it will be in KB or MB, depending on actual size. Ratio calculated percentage, using interval counts. In the first interval, it is calculated from total counts (as the interval count cannot be calculated). Status absolute value like ONLINE etc. Average calculated using interval counts. In the starting interval it is calculated from absolute counts. 40 informix Guide

41 Checkpoints metrics Single counter description active_users Checks for currently active Informix users buf_cachehit_ratio_read - ratio Calculated as (1 - (disk reads/buffer reads)) * 100 Monitors buffer cache hit ratio for reads buf_cachehit_ratio_write Calculated as (1 - (disk writes/buffer writes)) * 100 Monitors buffer cache hit ratio for writes buffer_wait Monitors the number of times the threads had to wait for buffer check_dbalive This checkpoint tries to connect to a server. In case the connection cannot be established, an alert is generated. This checkpoint cannot be deactivated! In case of Alert, check the server connectivity or if the server itself is running. checkpoint_wait Monitors the number of times the threads had to wait for critical section checkpoints chunk_io_read Monitors the read statistics for input/output in the chunk chunk_io_write Monitors the write statistics for input/output in the chunk chunk_writes Monitors the number of chunk writes database_count Monitors the number of database dbspace_count Monitors the count of database space dbspace_inconsistent Monitors the database inconsistencies dbspace_mirror_offline Monitors the database mirrors for offline status dbspace_mirror_recovering Chapter 1: informix

42 Checkpoints metrics Monitors the recovery status of the database mirrors dbspace_offline Monitors the database for offline status dbspace_recovering Monitors if the database is recovering dbspace_size_mb Monitors the free database space in Mbs dbspace_size_pct Monitors the free database space in percent deadlock_prevented Monitors the number of times potential deadlocks are detected and prevented deadlock_timeout Monitors the number of times a distributed deadlock timeout is exceeded while the user is waiting for a lock foreground_writes Monitors the number of foreground wrties latch_wait Monitors the number of times a thread had to wait for a latch lock_session Monitors the number of attempts to exceed the maximum number of locks lock_thread Monitors the number of failed attempts to allocate entries in the transaction table lock_user Monitors the number of attempts by a user to exceed the maximum number of threads lock_wait Monitors the number of times the sessions had to wait for a lock logging_status Monitors the logging status of the databases lru_writes Monitors the number of lru writes server_startup Monitors the uptime of the database server (in days) 42 informix Guide

43 Checkpoints metrics table_extents Monitors the extent of the tables table_size - count Measures the total table space size user_lock_wait Monitors users waiting for locks user_locks Lists user holding a lock. Helps to identify user, blocking other sessions (checkpoint locked_users). This checkpoint has two threshold values default and count. If the default threshold is set = 1, than the probe will issue for every locked user a message with details about the user locking situation. If set > 1, no message this types will be issued. The count threshold defines the number of locked users as a threshold for this checkpoint. virtual_cpu_system Monitors virtual cpu system time virtual_cpu_usercheck_dbalive status Monitors virtual cpu user time Chapter 1: informix

44

45 Glossary Glossary 45