Tivoli Manager for Sybase** Reference Guide. Version 1.1

Transcription

1 Tivoli Manager for Sybase** Reference Guide Version 1.1

2

3 Tivoli Manager for Sybase** Reference Guide (March 1999) Copyright Notice Copyright 1999 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli Enterprise Console (TEC) Tivoli Management Environment, Tivoli Manager for Sybase, TME 10, TME 10 Distributed Monitoring, and TME 10 Framework. Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation. Sybase, the Sybase logo, Adaptive Server, Adaptive Server Enterprise, Adaptive Server Monitor, SQL Server, and Transact-SQL are trademarks of Sybase, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notice References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli Systems or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York

4

5 Tivoli Manager for Sybase Reference Guide Preface...v Chapter 1 Introduction Using the Reference Guide How this Manual is Organized Using the Tivoli Desktop or Command Line Understanding the Monitor Output Chapter 2 The SybaseServer Monitoring Collection List of SybaseServer Monitoring Sources by GUI and CLI Names Backup Server Errors Bad Processes Blocked Processes Connections Available Connections In Use CPU By Process Currently Open Databases Database Status Dataserver Errors Dataserver Errors By Severity Device Mirror Status Engine CPU Busy Engine Status Free Form SQL Numeric Free Form SQL String Infected Processes Locks Available Locks In Use Tivoli Manager for Sybase Reference Guide iii

6 Long Running Transactions Memory Usage By Process Packet Errors Packets Received Packets Sent Percent Connections Used Percent Locks Available Percent Locks Used Percent Transaction Log Space Used By Server Physical IO By Process SLD Free Space SLD Free Space By Device SLD Space Used By Device SQL Server Status Stopped Processes User CPU Busy Chapter 3 The SybaseDatabase Monitoring Collection List of SybaseDatabase Monitoring Sources by GUI and CLI Names Database State Free Form SQL Numeric Free Form SQL String Free Segment Space By Segment Percent Free Segment Space Percent Transaction Log Space Used Transaction Log Free Space Used Segment Space By Segment iv Version 1.1

7 Preface Preface The Tivoli Manager for Sybase Reference Guide provides detailed information about monitors for the Sybase Adaptive Server. Use this manual in conjunction with the procedures in the Tivoli Manager for Sybase User s Guide. You will notice that both Tivoli and TME 10 are used in our product documentation. These terms are interchangeable. We will remove references to TME 10 in future product releases. Also in our product documentation, the term Adaptive Server is used, but the information also pertains to Sybase SQL Server for releases prior to Sybase Adaptive Server, Version Who Should Read This Guide This guide provides detailed information about the fields on the Tivoli desktop and the command line interface (CLI) for Tivoli Manager for Sybase monitors, their outputs, and usage notes. Readers of this guide should have knowledge of Windows NT, UNIX or similar operating systems, Tivoli Manager (or TME 10), and Sybase Adaptive Server (or SQL Server) database administration. Related Documents You must be familiar with the information in the related documents before you install and use Tivoli Manager for Sybase and its monitoring collections. Tivoli Manager for Sybase User s Guide, Version 1.1 Describes how to install and use the Tivoli Manager for Sybase software to manage Sybase Adaptive Server resources through the Tivoli Enterprise software. TME 10 Distributed Monitoring User s Guide Explains how to set up and use the Tivoli Distributed Monitoring application. You must be familiar with Tivoli Distributed Monitoring before you can install and use a monitoring collection. Tivoli Manager for Sybase Reference Guide v

8 Preface TME 10 Framework Reference Guide Describes command line interface (CLI) commands and the default and validation policies for Framework components. TME 10 Framework Planning and Installation Guide Provides information on Tivoli Management Region (TMR) server and client hardware requirements. TME 10 Framework User s Guide Contains more detailed information about profile management, including profile managers, profile databases, and profiles. TME 10 Enterprise Console User s Guide Contains information about setting up the Enterprise Console to receive distributed monitoring events. Also refer to the Sybase Adaptive Server documentation, particularly the following documents: System Administration Guide Describes how to administer security for the Sybase Adaptive Server Enterprise and provides information for specifying character conversion, international language, and sort-order settings. Transact-SQL User s Guide Describes Transact-SQL, Sybase s enhanced version of the relational database language, SQL. What This Guide Contains The Tivoli Manager for Sybase Reference Guide contains the following chapters: Chapter 1, Introduction Contains information on how to use this reference manual. Chapter 2, The SybaseServer Monitoring Collection Describes each of the monitoring sources in the SybaseServer monitoring collection. vi Version 1.1

9 Preface Chapter 3, The SybaseDatabase Monitoring Collection Describes each of the monitoring sources in the SybaseDatabase monitoring collection. Typeface Conventions This guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold <italics> Bold Italics Monospace Commands, keywords, file names, authorization roles, or other information that you must use literally appear in bold. Names of windows, dialogs, and other controls also appear in bold. Variables and values that you must provide appear in italics within greater and less brackets (< >). Words and phrases that are emphasized also appear in italics. New terms appear in bold italics when they are defined in the text. Code examples appear in a monospace font. Platform-specific Information See the Tivoli Manager for Sybase Release Notes for detailed and up-to-date information on supported platform versions, disk space, and memory requirements. Contacting Customer Support For support inside the United States, for this or any other Tivoli product, contact Tivoli Customer Support in one of the following ways: Send to support@tivoli.com Call TIVOLI8 Navigate our Web site at For support outside the United States, refer to your Customer Support Handbook for phone numbers in your country. The Customer Support Handbook is available online at Tivoli Manager for Sybase Reference Guide vii

10 Preface When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily. We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send to viii Version 1.1

11 1 Introduction 1Introduction This manual is a reference manual to use with the procedures described in the Tivoli Manager for Sybase User s Guide. It provides alphabetical listings and detailed descriptions of the following: SybaseServer monitors in Chapter 2, The SybaseServer Monitoring Collection, provide Sybase Adaptive Server, Sybase Backup Server, and Sybase Monitor Server availability and performance monitoring facilities. SybaseDatabase monitors in Chapter 3, The SybaseDatabase Monitoring Collection, provide database availability and performance monitoring facilities. A monitor captures and returns information about a resource or application in the Tivoli management environment, such as the status of a database or whether a server is available or not. Tivoli Manager for Sybase provides the ability to manage and monitor Sybase Adaptive Servers by providing extensions to the Tivoli Framework, Distributed Monitoring, and Enterprise Console. The monitoring collections enable you to manage distributed Sybase Adaptive Server computing resources effectively and to the granularity that you need. Tivoli Manager for Sybase Reference Guide 1 1

12 Using the Reference Guide Using the Reference Guide This section contains information on how to use this reference manual. It includes the following information: How this manual is organized How to use the graphic user interface (GUI) or command line interface (CLI) How this Manual is Organized The manual is organized alphabetically within each monitoring collection. Each monitor contains the following information: A brief description of the monitor. The required authorization role. The target endpoint. Descriptions of each GUI field on the Tivoli desktop. The CLI syntax, which includes definitions for each of the arguments, and an example. Suggested monitor threshold values for severity levels. For more information on triggering conditions and response levels, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, of the Tivoli Manager for Sybase User s Guide. Example output for each monitor. Usage notes that provide additional information about each monitor. A list of related monitors. 1 2 Version 1.1

13 Using the Reference Guide Using the Tivoli Desktop or Command Line You can work with monitors from both the Tivoli desktop (GUI) or the command line (CLI). You might choose to use the Tivoli desktop to take advantage of visual input prompting, such as drop-down lists of options, or the default options provided by components such as the Notify TEC... button. Use the command line when you want to create scripts, respond to distributed monitoring monitors, and rapidly enter commands. Introduction Specifying Path Names Depending on the platform on which you run Tivoli Manager for Sybase, you will use either forward (/) or backward slashes (\) in path names. Examples in this documentation use both forward and backward slashes. Using the Tivoli Desktop You can set up monitors from the Tivoli desktop, using the procedures described in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. You can run monitors using procedures described in Chapter 6, Using Tivoli Manager for Sybase of the same guide. Each monitor description in this manual includes a section called GUI Data Entry Fields. This section has an illustration of the dialog displayed when you select the monitor. Following the illustration is a detailed explanation of each field and button on the dialog. Using the Command Line To create a monitor, you can use the waddmon command. The documentation for this command does not provide information regarding specific sources or monitoring collections, such as SybaseServer or SybaseDatabase. Each monitor description in this manual includes a section called CLI Syntax that supplies the arguments for the waddmon command. Also included is a section called CLI Example, which provides an example of how you would actually enter the waddmon command and the monitoring arguments at the command line. Tivoli Manager for Sybase Reference Guide 1 3

14 Understanding the Monitor Output For more information on the waddmon command, refer to the TME 10 Framework Reference Manual or its UNIX manual page. Understanding the Monitor Output The Tivoli Manager for Sybase monitors can provide output information once they are run. Much of the output information for the monitor is generic; output that is specific to a monitor is described in the Output section of each monitor description. Generic output from a Tivoli Manager for Sybase monitor is organized into the following parts: Identification information The names of the profile, monitor, Sybase Adaptive Server, and host, plus the time and date when the monitor was run. Trigger value The value returned by the monitor against which responses can be set. Trigger information Extra information that might be useful, pertaining only to the trigger value and the entity that generated the trigger value. For example, the trigger value might be 50% free space in the device and the trigger information might be the name of that device. Row results (optional) The row results of the SQL command that was executed on the server. 1 4 Version 1.1

15 Understanding the Monitor Output The following is an example output from the SybaseServer monitor Percent Transaction Log Space Used by Server and a description of its generic output. Introduction Identification Information Distributed Monitoring server_test4 The name of the Distributed Monitoring profile. Percent Transaction Log Space Used By Server The name of the monitor. pip_1150ds@pip The name of the Sybase Adaptive Server and host. 12/02/98 06:02:23 The time and date at which the monitor was run. Tivoli Manager for Sybase Reference Guide 1 5

16 Understanding the Monitor Output Trigger Value Status The trigger value for this monitor, which indicates the success or failure of the monitor Normal is returned only when no severity levels have been breached and the monitor has been set to always return a value. E.EXEC indicates a problem; an error occurred while running the monitor. Warning, Severe, or Critical are returned when a severity threshold is broken, the appropriate severity level is returned. Trigger Information Previous The value returned by the preceding monitor probe. For example, if the monitor is run at 5:56 p.m., 6 p.m., and 6.02 p.m., this value is for 6 p.m. The first time this monitor is run in any monitoring session, there is no value for this field. Current The value returned by the most recent monitor probe. For example, if the monitor is run at 5:56 p.m., 6 p.m., and 6:02 p.m., this value is for 6:02 p.m. Effective This value does not apply to any of the Tivoli Manager for Sybase monitors. #SYBASE= The name of either the Sybase Adaptive Server (if the monitor is distributed to a database), or the Sybase directory, $SYBASE (if the monitor is distributed to a server). #DSQUERY The Sybase Adaptive Server identifier. #DATABASE The name of the database to which the monitor was distributed. The #DATABASE information will not appear in the output of a SybaseServer monitor. 1 6 Version 1.1

17 Understanding the Monitor Output #SERVER_OID= The Tivoli SybaseDataServer object ID for the Sybase Adaptive Server. This object ID is used internally by Tivoli, but you can also specify it in CLI commands and use it for tracing activities with this object. #HOST= The managed node identifier. #ENDPOINT_OID= The Tivoli object ID for the endpoint to which the monitor was distributed. This object ID is used internally by Tivoli, but you can also specify it in CLI commands and use it for tracing activities with this object. #INTERP= The platform that the monitor runs on. #MONITOR_NUMBER= An internal number that uniquely represents the monitor. See the sections called Monitor Number in each monitor description in both Chapter 2, The SybaseServer Monitoring Collection, and Chapter 3, The SybaseDatabase Monitoring Collection. #TRIGGER_INFO= Supplementary information for users beyond the result from the monitor. Introduction Row Results (optional) The row results of the SQL command that was executed on the server. Note: The monitor output from #SYBASE= to the end is truncated at 1000 characters, so you might not see all the row results returned. Tivoli Manager for Sybase Reference Guide 1 7

18 Understanding the Monitor Output 1 8 Version 1.1

19 2 2The SybaseServer Monitoring Collection The SybaseServer monitoring collection provides a range of monitoring sources to manage distributed Sybase Adaptive Server Enterprise computing resources effectively. Each monitoring source manages a different aspect of a Sybase Adaptive Server or its databases, a Sybase Backup Server, or a Sybase Monitor Server, such as locks, I/O, and network statistics. You can also use the Free Form SQL Numeric and Free Form SQL String user-defined monitors to create your own Sybase Adaptive Server monitoring sources. For server-level monitoring, you can distribute a profile containing SybaseServer monitors to a SybaseDataServer, SybaseBackupServer, or SybaseMonitorServer endpoint. For database-specific monitoring, there is a SybaseDatabase monitoring collection, described in Chapter 3, The SybaseDatabase Monitoring Collection. Using monitors from both collections enables you to achieve the required range and granularity of monitoring. The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 1

20 List of SybaseServer Monitoring Sources by GUI and CLI Names List of SybaseServer Monitoring Sources by GUI and CLI Names The following table lists the monitoring sources in the SybaseServer collection by their GUI and their CLI names. GUI Name Backup Server Errors Bad Processes Blocked Processes Connections Available Connections In Use CPU By Process Currently Open Databases Database Status Dataserver Errors Dataserver Errors By Severity Device Mirror Status Engine CPU Busy Engine Status Free Form SQL Numeric Free Form SQL String Infected Processes Locks Available Locks In Use Long Running Transactions Memory Usage By Process CLI Name BackupServerErrors BadProcesses BlockedProcesses ConnectionsAvailable ConnectionsInUse CPUByProcess CurrentlyOpenDatabases DatabaseStatus DataserverErrors DataserverErrorsBySeverity DeviceMirrorStatus EngineCPUBusy EngineStatus FreeFormSQLNumeric FreeFormSQLString InfectedProcesses LocksAvailable LocksInUse LongRunningTransactions MemoryUsageByProcess 2 2 Version 1.1

21 List of SybaseServer Monitoring Sources by GUI and CLI Names GUI Name Packet Errors Packets Received Packets Sent Percent Connections Used Percent Locks Available CLI Name PacketErrors PacketsReceived PacketsSent PercentConnectionsUsed PercentLocksAvailable Percent Locks Used Percent Transaction Log Space Used By Server Physical IO By Process SLD Free Space SLD Free Space By Device SLD Space Used By Device PercentLocksUsed PercentTransactionLogSpace- UsedByServer PhysicalIOByProcess SLDFreeSpace SLDFreeSpaceByDevice SLDSpaceUsedByDevice The SybaseServer Monitoring Collection SQL Server Status Stopped Processes User CPU Busy SQLServerStatus StoppedProcesses UserCPUBusy Tivoli Manager for Sybase Reference Guide 2 3

22 Backup Server Errors Backup Server Errors DESCRIPTION This monitor checks the Sybase Backup Server error log for messages and reports the severity of the last error in the log file that is within a specified functional area and a specified severity range. Since the Sybase Backup Server silently reports errors to its error log, using this monitor is a good way to be alerted when errors are logged there. The Sybase Backup Server error message numbers are of the form <major>.<minor>.<severity>.<state>. This monitor allows you to specify which <major> and <severity> numbers you wish to monitor. For details, see USAGE NOTES on page At the time of monitor startup, if the log file contains any existing error messages that match the specified <major> and <severity> levels, the monitor reports the last error in its output. However, the monitor returns a trigger value of zero. If the log file is truncated between invocations of the monitor, no error messages are reported. For more details, see OUTPUT on page MONITOR NUMBER 4 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseBackupServer GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Backup Server Errors monitor. Descriptions of the monitor arguments follow. 2 4 Version 1.1

23 Backup Server Errors The SybaseServer Monitoring Collection Major Number Specifies the functional areas to monitor. The range of major numbers is 1 to 7. You can enter as many major numbers as you wish to monitor; for example, entering 1 means the log will be searched for only errors with major number 1. If you enter 1 3 4, the log will be searched for errors with major number 1, 3, or 4. You can use a hyphen to specify a range of values; for example, 1-7 denotes major numbers 1 through 7, inclusive. Do not enter a space before or after the hyphen. Tivoli Manager for Sybase Reference Guide 2 5

24 Backup Server Errors Severity Spaces and hyphens can be combined; for example, denotes major numbers 1 through 4 and 7. No spaces should precede the first number or follow the last number. Specifies the severity areas to monitor. The range of severity numbers is 1 to 4. You can enter as many severity numbers as you wish to monitor; for example, entering 1 means the log will be searched for only errors with severity 1. If you enter 1 3, the log will be searched for errors with severity 1 or 3. You can use a hyphen to specify a range of values; for example, 1-3 denotes severity numbers 1 through 3, inclusive. Do not enter a space before or after the hyphen. Spaces and hyphens can be combined; for example, denotes major numbers 1, 2, and 4. No spaces should precede the first number or follow the last number. CLI SYNTAX BackupServerErrors a <major number> a <severity> where: a <major number> Specifies a functional area or range of functional areas. a <severity> Specifies a severity area or range of severity areas. 2 6 Version 1.1

25 Backup Server Errors When specifying the <major number> and <severity> arguments, enter a single number or multiple numbers separated by spaces, a consecutive range of numbers with a hyphen between the first and last numbers in the range, or a combination of both, as shown in the following examples: 1 Searches for value 1 only Searches for values 1, 3, and Searches for values 1, 2, 3, 4, 5, 6, and Searches for values 1, 2, 3, 4, and 7 CLI EXAMPLE waddmon SybaseServer BackupServerErrors -a a 1-4 -t 20 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/monitor_outputs/backup_errors.log <profile name> The SybaseServer Monitoring Collection SUGGESTED RESPONSE LEVELS Assuming the Backup Server Errors monitor has been set up with the major numbers 1 through 7 and the severity numbers 1 through 4, then the following suggested response levels will raise a critical response if the monitor finds an error in the log file with a severity of 2, 3, or 4. If the monitor finds an error in the log file with a severity of 1, it will raise a warning. For more information, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Tivoli Manager for Sybase Reference Guide 2 7

26 Backup Server Errors Severity Trigger When Default Action Critical Greater than 1 Send Sybase Sentry Notice. Severe Not applicable None Warning Equal to 1 Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes 2 8 Version 1.1

27 OUTPUT Backup Server Errors The following is an example output from the Backup Server Errors monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the severity level. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are the latest error messages (or as many as will fit within the 1000-character restriction on the output s length) taken from the log file. Only those error messages within the specified <major number> and <severity> values are given. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. There are two exceptions to the typical Backup Server Errors monitor output: Tivoli Manager for Sybase Reference Guide 2 9

28 Backup Server Errors The first time this monitor is run, it returns a trigger value of zero and includes the following message in its output:!!!running in startup-mode - No errors will be reported!!! 2 10 Version 1.1

29 Backup Server Errors If the monitor is run and the error log file has been truncated since the last time the monitor ran, it returns a trigger value of zero and includes the following message in its output:!!!log file size mismatch due to possible truncation!!! The SybaseServer Monitoring Collection USAGE NOTES The Backup Server Errors monitor searches the error log file for only those messages that have the <major number> and <severity> values specified as arguments to the monitor. All other messages are ignored. Consequently, if you specify a <major number> of 1 and a <severity> of 1, then all messages with the number 1.x.1.y, for example, will be considered by the monitor. However, a message with the number 2.x.1.y, for example, will be ignored by the monitor. Tivoli Manager for Sybase Reference Guide 2 11

30 Backup Server Errors Major Number The <major number> generally indicates the functional area of the Sybase Backup Server code where the error occurred, as follows: 1 System errors 2 Errors with open server events 3 Errors in remote procedure calls to the Sybase Backup Server 4 Errors with the I/O service layer 5 Errors with transfer of network data 6 Volume handling errors 7 Option parsing errors Note: Severity The <major numbers> 1 through 6 result from Sybase Backup Server internal errors, or a variety of system problems, whereas <major number> 7 is almost always due to problems in the options specified in a dump or load command. The value of <severity> indicates the type of condition associated with the error. Here is the list of severity levels: 1 Informational, no user action necessary. 2, 3 An unexpected condition has occurred, which is fatal to the execution of the Sybase Backup Server. The error might have occurred with any or all of the following: usage, environment, or internal logic. 4 An unexpected condition has occurred, which is fatal to the execution of the Sybase Backup Server. The Sybase Backup Server must exit immediately Version 1.1

31 Backup Server Errors Note: If you wish to allocate functional areas in which errors can occur (such as network data transfer errors, or I/O service layer errors) to different database administrators (dbas), then set up the Backup Server Errors monitor a number of times with different <major numbers> and different monitor responses. SEE ALSO The following SybaseServer monitor: SQL Server Status The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 13

32 Bad Processes Bad Processes DESCRIPTION This monitor reports processes with a current status of bad status. Such a status indicates that the process is not reporting a valid status. The monitor output gives the process ID (spid), and program name of the offending processes. If this situation occurs, the offending process should be investigated and the Adaptive Server error log checked. MONITOR NUMBER 5 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX BadProcesses CLI EXAMPLE waddmon SybaseServer BadProcesses -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/bad_processes.log <profilename> 2 14 Version 1.1

33 SUGGESTED RESPONSE LEVELS Bad Processes The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Greater than 0 Send Sybase Sentry Notice. Severe Not applicable None Warning Not applicable None Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes The SybaseServer Monitoring Collection OUTPUT The following is an example output from this monitor: Tivoli Manager for Sybase Reference Guide 2 15

34 Bad Processes The trigger value for this monitor is the number of processes found in a bad status. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which include the trigger value, process ID (spid), and program name repeated for each process in a bad status. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor is not applicable for Sybase Adaptive Servers, Version 11.5 or higher, since the bad status value for processes listed in the syprocesses table does not exist. If this monitor is pushed to a Sybase Adaptive Server, Version 11.5 or higher, it will return zero. SEE ALSO None 2 16 Version 1.1

35 Blocked Processes Blocked Processes DESCRIPTION This monitor reports processes with a current status of lock sleep that have been blocked for longer than the user-specified number of seconds. The monitor output gives the longest time for which such a process has been blocked. Processes with a lock sleep status are those that have requested a lock, but are waiting for a competing lock to be released by another process. For example, if the monitor is set up with 50 as the number of seconds that a process can be blocked before you are notified of the situation, then the monitor output will include a list of all processes blocked for 50 or more seconds. The monitor trigger value is the longest number of seconds that a process has been blocked (always 50 seconds or longer, in this case). This monitor can be used to determine which processes are delayed by lock contention rather than performance issues. Further information regarding blocked processes can be obtained by running the system-stored procedure sp_lock. The SybaseServer Monitoring Collection MONITOR NUMBER 6 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 17

36 Blocked Processes GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Blocked Processes monitor. A description of the monitor argument follows. Blocked For (seconds) Specifies the maximum number of seconds a process can be blocked before being reported by the monitor. The default is 50 seconds Version 1.1

37 CLI SYNTAX Blocked Processes BlockedProcesses a <blocked for (seconds)> where: a <blocked for (seconds)> Specifies the maximum number of seconds a process can be blocked before being reported by the monitor. CLI EXAMPLE waddmon SybaseServer BlockedProcesses -a 50 -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/blocked_processes.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels are based on the monitor being set up with the <blocked for (seconds)> argument set to 15 seconds. These suggested response levels set a critical response if a process is blocked for more than 30 seconds. The SybaseServer Monitoring Collection Severity Trigger When Default Action Critical Greater than 30 seconds Send Sybase Sentry Notice. Severe Greater than 20 seconds Send Sybase Sentry Notice. Warning Greater than 15 seconds Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Tivoli Manager for Sybase Reference Guide 2 19

38 Blocked Processes Suggested monitoring schedule: 10 minutes OUTPUT The following is an example output from the Blocked Processes monitor: The trigger value returned by the monitor is the number of seconds blocked for the process with the longest blocked time. The trigger information (#TRIGGER_INFO=) repeats the trigger value. Below #TRIGGER_INFO= are row results, which are the process ID (spid) and time blocked or all other processes that have been blocked for more than <blocked for (seconds)> (or as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page Version 1.1

39 Blocked Processes USAGE NOTES The Blocked Processes monitor takes as an argument a number of seconds that a process can be blocked before you wish to be notified. You can then set different severity levels based on the actual number of seconds that processes satisfying the notification argument are blocked. The real use of the argument to the monitor is to limit the output of the monitor so you can identify more readily those processes with a problem. Lock contention can seriously affect transaction throughput. You can minimize lock contention by keeping transactions as small as possible. To avoid lock contention, you can do the following: Stagger competing transactions, or alter the order in which they are run. Avoid transactions holding locks that need to wait for user interaction. When possible, avoid setting locks for transactions that include network traffic and are, therefore, dependent upon the speed of the network. Avoid hotspots within tables by creating a clustered index, or by partitioning the table. Decrease the number of rows on each page by adjusting the fillfactor or max_rows_per_page values of tables and indexes. The SybaseServer Monitoring Collection SEE ALSO The following SybaseServer monitors: Locks Available, Percent Locks Available, and Percent Locks in Use. Tivoli Manager for Sybase Reference Guide 2 21

40 Connections Available Connections Available DESCRIPTION This monitor reports the number of user connections currently available on the target server. The maximum number of allowable connections is controlled with the number of user connections configuration parameter. For example, if this parameter is set to 100 and currently there are 30 user connections, the trigger value will be 70. The monitor output gives the value of the number of user connections parameter. You can use this monitor to alert when you are running out of user connections, which can result in server access problems. Also, this monitor is useful for tracking client access patterns. If the monitor alerts you that connections are running out, consider either removing some of the existing connections or increasing the value of the number of user connections parameter. For important considerations when extending the number of user connections parameter, refer to the Sybase Adaptive Server Enterprise System Administration Guide. MONITOR NUMBER 9 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX ConnectionsAvailable 2 22 Version 1.1

41 CLI EXAMPLE Connections Available waddmon SybaseServer ConnectionsAvailable -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/connections_available.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels are based on the assumption that the number of user connections configuration parameter is set to 100; if this parameter is set higher or lower than 100, you should alter the Trigger When conditions below accordingly. Severity Trigger When Default Action The SybaseServer Monitoring Collection Critical Less than 10 Send Sybase Sentry Notice. Severe Less than 20 Send Sybase Sentry Notice. Warning Less than 30 Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 30 minutes Tivoli Manager for Sybase Reference Guide 2 23

42 Connections Available OUTPUT The following is an example output from the Connections Available monitor: The trigger value returned by the monitor is the number of user connections available. The trigger information (#TRIGGER_INFO=) is MAX= x, where x is the maximum number of connections allowed, based on the number of user connections configuration parameter. Below #TRIGGER_INFO= are row results, which are y, the number of connections currently used, and the number x from the trigger information, separated by a comma ( y,x ). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES You will probably only need to use either this monitor or one of the following monitors: Connections In Use or Percent Connections Used 2 24 Version 1.1

43 SEE ALSO Connections Available The following SybaseServer monitors: Connections In Use and Percent Connections Used The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 25

44 Connections In Use Connections In Use DESCRIPTION This monitor reports the current number of user connections to the target server. The maximum number of user connections allowed is specified by the number of user connections configuration parameter. Use this monitor to alert when you are running out of user connections, which can result in server access problems. This monitor is also useful for tracking client access patterns. If the monitor alerts you that connections are running out, consider either clearing some of the existing connections or increasing the value of the number of user connections configuration parameter. For important considerations when extending the number of user connections parameter, refer to the Sybase Adaptive Server Enterprise System Administration Guide. MONITOR NUMBER 10 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX ConnectionsInUse 2 26 Version 1.1

45 CLI EXAMPLE Connections In Use waddmon SybaseServer ConnectionsInUse -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/connections_in_use.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels are based on the assumption that the number of user connections configuration parameter is set to 100; if this parameter is set higher or lower than 100, alter the Trigger When conditions below accordingly. Severity Trigger When Default Action The SybaseServer Monitoring Collection Critical Greater than 90 Send Sybase Sentry Notice. Severe Greater than 80 Send Sybase Sentry Notice. Warning Greater than 70 Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 30 minutes Tivoli Manager for Sybase Reference Guide 2 27

46 Connections In Use OUTPUT The following is an example output from the Connections in Use monitor: The trigger value is the current number of user connections to the target server. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES You will probably only need to use either this monitor or one of the following monitors: Connections Available or Percent Connections Used 2 28 Version 1.1

47 SEE ALSO Connections In Use The following SybaseServer monitors: Connections Available and Percent Connections Used The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 29

48 CPU By Process CPU By Process DESCRIPTION This monitor reports the user process with the largest cumulative CPU time as measured by clock ticks on the target server. The output of this monitor identifies the server process ID and user s login name that are dominating the CPU usage. The CPU usage value is reset to zero when it reaches the value of the server configuration parameter cpu accounting flush interval (which is used to facilitate chargeback accounting). Consequently, the value reported by this monitor might not represent the amount of CPU used since the server was started. If you are not running the accounting options, then setting cpu accounting flush interval to the highest possible value will result in a more accurate report of CPU usage by this monitor. This monitor allows you to identify those processes and users who are dominating the CPU. MONITOR NUMBER 7 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX CPUByProcess 2 30 Version 1.1

49 CLI EXAMPLE waddmon SybaseServer CPUByProcess -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/cpu_by_process.log <profilename> CPU By Process SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 10 minutes OUTPUT The following is an example output from the CPU By Process monitor: The SybaseServer Monitoring Collection The trigger value reported by the monitor is the largest cumulative CPU time (in ticks). Tivoli Manager for Sybase Reference Guide 2 31

50 CPU By Process The trigger information (#TRIGGER_INFO=) is the ID of the process with the highest CPU usage. Below #TRIGGER_INFO= are row results, which give the CPU usage, and login name of the user who issued the command, for each process in ascending order, with the highest CPU usage first (for as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor reports CPU usage for each process. For information about CPU usage for each engine or user, use the Engine CPU Busy or User CPU Busy monitors. SEE ALSO The following SybaseServer monitors: Engine CPU Busy and User CPU Busy 2 32 Version 1.1

51 Currently Open Databases Currently Open Databases DESCRIPTION This monitor reports the number of currently open databases. Open databases are defined as being in the system table sysdatabases with the offline control bit not set. This monitor allows you to keep track of the number of open databases on different servers, or to check that the expected number of databases are indeed up and running. This monitor can also be used to indicate shortfalls in backup strategies; for example, if this monitor indicates that 10 databases are running, then any strategy you use should be capable of backing up at least those 10 databases. A large number of databases becomes a concern because not only does each database take up disk space, but it also takes up valuable system resources such as CPU and memory. MONITOR NUMBER 11 The SybaseServer Monitoring Collection AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX CurrentlyOpenDatabases Tivoli Manager for Sybase Reference Guide 2 33

52 Currently Open Databases CLI EXAMPLE waddmon SybaseServer CurrentlyOpenDatabases -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/currently_open_databases.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 30 minutes OUTPUT The following is an example output from the Currently Open Databases monitor: The trigger value returned by the monitor is the number of open databases. #TRIGGER_INFO=(none) means there is no trigger information Version 1.1

53 Currently Open Databases Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If a user drops a database and creates another database between the times this monitor is run, then the number of open databases reported will be the same as the previous time the monitor was run. SEE ALSO The SybaseServer monitor Database Status, and the SybaseDatabase monitor Database State The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 35

54 Database Status Database Status DESCRIPTION This monitor identifies databases that are found to be in a state specified by the user as an argument to the monitor. The system table sysdatabases is searched, and the trigger value returned by the monitor is the name of the first database that is found to be in the specified state. The trigger information lists the names of additional databases found to be in the user-specified state. Note: This monitor does not affect or change the status of the representative database icon on the Tivoli desktop. Use this monitor to ensure that changes made by users to the database settings (using sp_dboption) are acceptable, or use the monitor to keep track of the states that the server itself might put databases into. MONITOR NUMBER 12 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Database Status monitor. A description of the monitor argument follows Version 1.1

55 Database Status The SybaseServer Monitoring Collection Database State Specifies the database state to monitor. Tivoli Manager for Sybase Reference Guide 2 37

56 Database Status For a list of database states, click the Choice button to display the Database State dialog. Do one of the following: Select the state you want to monitor from the scrolling list and click the Set & Close button. Tivoli Manager for Sybase automatically translates the text into a internal numeric value representing this state (as in the following table) and places it in the Database State argument field on the Add Monitor to TME 10 Distributed Monitoring Profile dialog. OR Select a database state from the following table and type the number found in the column headed Internal Value into the Database State argument field on the Add Monitor to TME 10 Distributed Monitoring Profile dialog. OR When using a command line, once you have decided which state you want to monitor, consult the following table and include the corresponding internal value as an argument to the command Version 1.1

57 Database Status Database State User Settable? (using sp_dboption) Explanation Internal Value Select into/bulkcopy True Non-logged operations are permitted on the database. They can be highly optimized, but are not recoverable. 4 Trunc log on chkpt No chkpt on recovery True True The logs are truncated when a checkpoint activity occurs. It is recommended this state not be set for production databases where the logs might be needed for recovery, backup, or replication. A checkpoint will not occur after recovery of the database or the transaction log. Don t recover False The database was created with the for load option, or crashed while loading the database. Recovery will not proceed The SybaseServer Monitoring Collection Not recovered False The database is suspect and cannot be opened or used. Ddl in tran True A user can place Data Definition Language (DDL) commands, such as create table, inside an explicitly begun transaction. Read only True Inserts, updates, and deletes are not permitted on the database. Dbo use only True Only the database owner can access the database. Single user True Only one user can connect to the database Tivoli Manager for Sybase Reference Guide 2 39

58 Database Status Database State User Settable? (using sp_dboption) Explanation Internal Value Allow nulls by default True Null values are allowed in columns, whether or not null is specified in the create table or alter table definition Abort tran on log full True If the log fills while a long running transaction is in progress, then the transaction will be aborted and rolled back No free space accounting True The Sybase Adaptive Server does not attempt to calculate when space is running out, and no threshold actions are executed Auto identity True A column, SYB_IDENTITY_COL, is added to each table created. This column can be used to uniquely identify each record in the table Identity in non unique index True A column, IDENTITY, is automatically included in a table s index keys, so all indexes created on the table are unique. This state can drastically increase the size of indexes Offline False The database is offline and cannot be accessed by any users Offline until recovery False The database is offline until recovery completes Version 1.1

59 Database Status Database State User Settable? (using sp_dboption) Explanation Internal Value No separate log device False The database does not have a separate log device. It is strongly recommended that all databases have their logs separate from the data. In particular, separate logs help with recovery and log management CLI SYNTAX DatabaseStatus a <internal value> where: a <internal value> Specifies the internal value that represents the database status you want. The numbers from the Internal Value column in the previous table are available for the <internal value> argument. The SybaseServer Monitoring Collection CLI EXAMPLE waddmon SybaseServer DatabaseStatus -a t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/database_status.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Tivoli Manager for Sybase Reference Guide 2 41

60 Database Status The following suggested response levels cause a warning response if any databases are found to be in the user-specified state, whatever that state might be. Severity Trigger When Default Action Critical Not applicable None Severe Not applicable None Warning Not equal to Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes OUTPUT The following is an example output from the Database Status monitor: 2 42 Version 1.1

61 Database Status The trigger value returned by the monitor is the name of first database found with the user-defined status. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which list the names of any other databases with the specified status (or as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES When setting up this monitor, you can provide a database name as a threshold value. For example, you can set up the monitor so that when it returns a database name equal to the threshold value, master, then it triggers a critical response such as sending a Tivoli notice. However, when the monitor returns a database name of pubs2, it triggers only a warning response. Alternatively, no database name need be specified when setting up the monitor. In this case, when the monitor returns any database name, a response is triggered, such as sending a Tivoli notice. In this way, for example, you might use this monitor to trigger a critical response if any database falls into an offline state. This can be done by setting the monitor to trigger when Not equal to the trigger value (with a blank space between the quotes). Since the threshold value is a blank, the monitor will trigger whenever a database name is returned. To monitor multiple states, set up this monitor multiple times; for example, once to monitor if any databases fall into an offline state, and once to monitor if any database does not have a dedicated log. If you need to monitor a particular database for a number of different states, consider using the Database State monitor. See Database State on page 3-3. The SybaseServer Monitoring Collection SEE ALSO The following SybaseServer monitors: Database State Tivoli Manager for Sybase Reference Guide 2 43

62 Dataserver Errors Dataserver Errors DESCRIPTION This monitor allows you to select those Sybase Adaptive Server errors of particular interest, prioritize them into categories of your choice, and set up different responses for each category. This monitor checks the Sybase Adaptive Server error log for specific errors. All error messages written to the error log are categorized and the worst new error message is the monitor trigger. Individual errors are graded on classes of error categorization that are unique within the Tivoli Management Region (TMR). A Tivoli administrator can define any number of new categorization classes you then select the name of a class and provide the class name (which is case-sensitive) as an argument to this monitor. For details, see USAGE NOTES on page All installations have a DEFAULT class that categorizes the errors listed below such that each monitor response value is 1. All other errors will be ignored. Error Category Error Message Infected with 10 1 Infected with 11 1 Error Not enough user connections available to start a new process. Error Failed to open virtual socket for new connections. Error Unable to locate the base procedure header (Pss->phdr) that had been switched earlier. Error The offset of the row number at offset %d does not match the entry in the offset table of the following page: %S_PAGE Version 1.1

63 Dataserver Errors Error Category Error Message Error Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=%ld; page# point to this page=%ld; previous page# indicated in this page=%ld). Error Could not retrieve row from logical page %ld with RID because the entry in the offset table for that RID is less than or equal to zero. Attempt to retrieve row from page with RID failed because the requested RID has a higher number than the last RID on the page. %S_RID.%S_PAGE. Error Attempt to retrieve row from page with RID failed because the requested RID has a higher number than the last RID on the page. %S_RID.%S_PAGE. The SybaseServer Monitoring Collection Error Could not find virtual page for logical page %ld in database %S_DBID. Error Logical page %ld in database %S_DBID, cache %.*s, is already hashed. Error An attempt was made to fetch logical page %ld in database %.*s from cache %.*s. Page belongs to object with ID %ld, not to object %.*s. Tivoli Manager for Sybase Reference Guide 2 45

64 Dataserver Errors The first time the Dataserver Errors monitor is run, any existing errors satisfying the monitor criteria will be reported in the trigger information. However, the monitor output returns a value of zero. From then on, only those errors raised since the monitor was last run will be reported. If the log file is truncated between invocations of the monitor, then the first time the monitor is run after the truncation, it will return zero. MONITOR NUMBER 13 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer 2 46 Version 1.1

65 GUI DATA ENTRY FIELDS Dataserver Errors The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Dataserver Errors monitor. A description of the monitor argument follows. The SybaseServer Monitoring Collection Custom Category Name Specifies the name of the error categorization class to be used by the monitor. DEFAULT is the name of the default error categorization class that is provided with the monitor. For details on defining your own error categorization class, see USAGE NOTES on page Tivoli Manager for Sybase Reference Guide 2 47

66 Dataserver Errors CLI SYNTAX DataserverErrors a <custom category> where: a <custom category> Specifies the name of the custom error category. CLI EXAMPLE waddmon SybaseServer DataserverErrors -a DEFAULT -t 20 minutes -c critical -R == 1 -c severe -c warning -c normal -c always -f pip:/data/sybase/monitor_outputs/ds_errors.log <profile name> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Assuming that the default categorization class DEFAULT is passed to the monitor, then the following suggested response levels cause a critical response if any error listed in category 1 is raised. Severity Trigger When Default Action Critical Equal to 1 Send Sybase Sentry Notice. Severe Not applicable None Warning Not applicable None Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes 2 48 Version 1.1

67 OUTPUT Dataserver Errors The following is an example output from the Dataserver Errors monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the category number of the worst error found. Category 1 errors are always deemed the worst. If no errors are located in the error log, this monitor returns zero. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which include the error text of all the errors written to the log file since the monitor was last run (or as many as will fit within the 1000-character restriction on the output s length). The included errors are only those specified in the error categorization class input to the monitor. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. Tivoli Manager for Sybase Reference Guide 2 49

68 Dataserver Errors There are two exceptions to the typical Dataserver Errors monitor output: The first time this monitor is run, it returns a trigger value of zero and includes the following message in its output:!!!running in startup-mode - No errors will be reported!!! 2 50 Version 1.1

69 Dataserver Errors If the monitor is run and the error log file has been truncated since the last time the monitor ran, it returns a trigger value of zero and includes the following message in its output:!!!log file size mismatch due to possible truncation!!! The SybaseServer Monitoring Collection USAGE NOTES To monitor errors in a different way than that provided with the error category class DEFAULT, write your own error category classes using the SetErrorCategory utility. This utility allows you to define and manipulate error categorizations for use with this monitor. To define and manipulate your own category classes, go to the directory <tivoli installation>/bin/generic/sybasesentry and run one of the following scripts. All of the following scripts are interactive, prompting you for the required information. Tivoli Manager for Sybase Reference Guide 2 51

70 Dataserver Errors SetErrorCategory.sh -a Enables you to create a new category class. Using this script, you can create a class named class1, for example, and add pairs to this class in the following form: <error number>:<category number> For example: 1601:1 The special pair OTHERS:x can be added to a customized class. This means that all other errors not listed in the class will be given category number x. This allows all otherwise undefined errors to be collected into a single category. The name class1 can then be provided as the monitor argument. SetErrorCategory.sh -h Displays online help about the SetErrorCategory utility. SetErrorCategory.sh -r Resets category definitions to the default. SetErrorCategory.sh -l Lists the currently defined category classes. SetErrorCategory.sh -d Enables you to delete one or more category classes. SEE ALSO The following SybaseServer monitor: Dataserver Errors By Severity 2 52 Version 1.1

71 Dataserver Errors By Severity Dataserver Errors By Severity DESCRIPTION This monitor checks the Sybase Adaptive Server error log for error messages of specified severity levels. The Sybase Adaptive Server writes errors silently to the log file. Use this monitor to be notified when errors have occurred. On monitor start up, any error messages found in the error log that match the specified severity levels are reported. However, the monitor output returns a value of zero. If the log file is truncated between invocations of the monitor, then the first time the monitor is run after the truncation, it will return zero. Sybase Adaptive Server errors are each given a severity level, with a different meaning for each level. For details, see USAGE NOTES on page Because the severity level of the errors to monitor is passed as an argument to the monitor, you can set up the monitor so that only the most serious errors are monitored. MONITOR NUMBER 14 The SybaseServer Monitoring Collection AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Dataserver Errors monitor. A description of the monitor argument follows. Tivoli Manager for Sybase Reference Guide 2 53

72 Dataserver Errors By Severity Severity Specifies the severity levels of errors the monitor should search for in the log. The range of default numbers is 19 to 24, all of which indicate fatal errors. You can enter numbers, spaces, and hyphens (to specify ranges). For example, entering 24 means the log will be searched for only errors with severity level 24. If you enter , the log will be searched for errors with severity levels 19, 23, or 24. You can use a hyphen to specify a range of severity levels; for example, denotes severity levels 19 through 24, inclusive. Do not enter a space before or after the hyphen Version 1.1

73 Dataserver Errors By Severity Spaces and hyphens can be combined; for example, searches for errors with severity levels 1 through 4 and 13. No spaces should precede the first number, or follow the last number. CLI SYNTAX DataserverErrorsBySeverity a <severity> where: a <severity> Specifies a severity level or range of severity levels. When specifying the <severity> argument, enter a single number or multiple numbers separated by spaces, a consecutive range of numbers with a hyphen between the first and last numbers in the range, or a combination of both, as shown in the following examples: 24 Searches for severity level 24 only Searches for severity levels 19, 23, and Searches for severity levels 19, 20, 21, 22, 23, and Searches for severity levels 19, 20, 21, 22, and 24 The SybaseServer Monitoring Collection CLI EXAMPLE waddmon SybaseServer DataserverErrorsBySeverity -a t 20 minutes -c critical -R > 18 -p Root_pip-region -c severe -c warning -c normal -c always -f pip:/data/monitor_outputs/sybase/dserrors_bys.log <profile name> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Tivoli Manager for Sybase Reference Guide 2 55

74 Dataserver Errors By Severity Assuming the monitor was set up with the severity range to include level 17 and all those above, the following suggested response levels cause a critical response if a fatal error 19 or higher is encountered, and a severe response if an error of severity level 17 or 18 is encountered. Severity Trigger When Default Action Critical Greater than 18 Send Sybase Sentry Notice. Severe Greater than 16 Send Sybase Sentry Notice. Warning Not applicable None Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes 2 56 Version 1.1

75 OUTPUT Dataserver Errors By Severity The following is an example output from the Dataserver Errors By Severity monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the highest severity error message (within the range of severity levels specified to the monitor) written to the log file since the monitor last ran. If no such errors are found. the trigger value is zero. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which include all the error messages written to the log file since the monitor was last run (or as many as will fit within the 1000-character restriction on the output s length). The included error messages are only those within the range of severity levels specified to the monitor. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. Tivoli Manager for Sybase Reference Guide 2 57

76 Dataserver Errors By Severity There are two exceptions to the typical Dataserver Errors By Severity monitor output: The first time this monitor is run, it returns a trigger value of zero and includes the following message in its output:!!!running in startup-mode - No errors will be reported!!! 2 58 Version 1.1

77 Dataserver Errors By Severity If the monitor is run and the error log file has been truncated since the last time the monitor ran, it returns a trigger value of zero and includes the following message in its output:!!!log file size mismatch due to possible truncation!!! The SybaseServer Monitoring Collection USAGE NOTES The Dataserver Errors By Severity monitor searches the error log file for only those messages that have severity levels specified as arguments to the monitor. All other messages are ignored. The monitor reports those error messages in the specified range that have occurred since the monitor last ran. Messages that occurred before the monitor was last run are not reported again. For maximum integrity, when the Sybase Adaptive Server responds to error conditions, it displays messages from sysmessages, but takes action according to an internal table. A few corresponding messages differ in severity levels, so you might occasionally notice a difference in expected behavior if you are developing applications or procedures that refer to Sybase Adaptive Server messages and severity levels. Tivoli Manager for Sybase Reference Guide 2 59

78 Dataserver Errors By Severity The Dataserver Errors By Severity monitor s output indicates the severity level associated with the error, which provides information about the kind of problem the Sybase Adaptive Server has encountered. Here is the list of reported severity levels and their meanings: 1 through 15 Indicate problems caused by mistakes in what the user entered. 16 and higher Indicate software or hardware errors. 17 or 18 Indicate that you can continue with the work you are doing, although you might not be able to execute a particular command. 19 and higher Indicate fatal errors, meaning the process is no longer running. The process freezes its state before it stops, recording information about what has happened. The server then kills the process. Note: Fatal errors break the user s connection to the Sybase Adaptive Server. Depending upon the problem, users might or might not be able to reconnect and resume working. Some problems with fatal severity levels affect only one process and one user; others affect all the processes in the database. In some cases, you must restart the Sybase Adaptive Server. Such problems do not necessarily damage a database or its objects, but they can. They might result from earlier damage to a database or its objects. Other problems are caused by hardware malfunctions. SEE ALSO The following SybaseServer monitor: Dataserver Errors 2 60 Version 1.1

79 Device Mirror Status Device Mirror Status DESCRIPTION This monitor reports the mirror status of a device passed as an argument to the monitor. This monitor will return one of the trigger states listed in the following table. Use this monitor to keep track of your most important devices; let it notify you if mirroring becomes disabled or altered in some way, or even if the device has been dropped. A logical device name is input to the monitor and, if this device is mirrored, all reads or writes, or both, to this primary device are also executed on a secondary device. You can select from the trigger states in the following table. Trigger State Has No Such Device CLI Trigger State Explanation == HasNoSuchDevice The input device does not exist. The SybaseServer Monitoring Collection Has No Mirror Device == HasNoMirrorDevice The input device is not a mirrored device; mirroring was not set up for the device. Is Mirrored == IsMirrored Mirroring is enabled for the input device; mirroring was set up for the device and neither the primary nor secondary side are disabled. Primary Disabled == PrimaryDisabled Mirroring is disabled for the input device and only its secondary device is used. Tivoli Manager for Sybase Reference Guide 2 61

80 Device Mirror Status Trigger State CLI Trigger State Explanation Secondary Disabled Becomes No Such Device Becomes Not Mirrored Becomes Mirrored Primary Becomes Disabled == SecondaryDisabled Mirroring is disabled for the input device and only the primary (input) device is used. -> HasNoSuchDevice The monitor returns Has No Such Device, but when the monitor was run previously, the returned status was one other than Has No Such Device. -> HasNoMirrorDevice The monitor returns Has No Mirror Device, but when the monitor was run previously, the returned status was one other than Has No Mirror Device. -> IsMirrored The monitor returns Is Mirrored, but when the monitor was run previously, the returned status was one other than Is Mirrored. -> PrimaryDisabled The monitor returns Primary Disabled, but when the monitor was run previously, the returned status was one other then Primary Disabled Version 1.1

81 Device Mirror Status Trigger State CLI Trigger State Explanation Secondary Becomes Disabled -> SecondaryDisabled The monitor returns Secondary Disabled, but when the monitor was run previously, the returned status was one other than Secondary Disabled. MONITOR NUMBER 15 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 63

82 Device Mirror Status GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Device Mirror Status monitor. A description of the monitor argument follows. Logical Device Name Specifies the logical name of the device to monitor. The default is master for the master device Version 1.1

83 CLI SYNTAX Device Mirror Status DeviceMirrorStatus a <logical device name> where: a <logical device name> Specifies the device name. Note: For trigger states, see the CLI Trigger State column in the table on page CLI EXAMPLE waddmon SybaseServer DeviceMirrorStatus -a default -t 1 minutes -c critical -R == HasNoMirrorDevice -p Root_pip-region -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/device_mirror_status.log <profilename> The SybaseServer Monitoring Collection SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide Severity Trigger When Default Action Critical Has No Mirror Device Send Sybase Sentry Notice. Severe Primary Disabled Send Sybase Sentry Notice. Warning Secondary Disabled Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Tivoli Manager for Sybase Reference Guide 2 65

84 Device Mirror Status Suggested monitoring schedule: 15 minutes OUTPUT The following is an example output from the Device Mirror Status monitor: The trigger value returned by the monitor is one of the trigger states listed in the table on page #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value information. For a general description of the monitor output, see Understanding the Monitor Output on page Version 1.1

85 Device Mirror Status USAGE NOTES With regard to the five becomes trigger states (Becomes No Such Device, Becomes Not Mirrored, Becomes Mirrored, Primary Becomes Disabled, and Secondary Becomes Disabled) listed in the table on page 2-61, the first time the monitor is run none of these states can be returned because there was no previous mirror state to compare to the current mirror state. In addition, none of the becomes trigger states can be returned twice in succession; in other words, if one of these states is returned by the monitor, then it cannot possibly be returned the next time the monitor is run. The mirror status of the input device is determined in the following order: Has No Such Device Has No Mirror Device Primary Disabled Secondary Disabled Is Mirrored For example, if a device that does not exist on the Sybase Adaptive Server is input as an argument, the monitor returns Has No Such Device. The SybaseServer Monitoring Collection SEE ALSO The following SybaseServer monitors: SLD Free Space, SLD Free Space By Device, and SLD Space Used By Device Tivoli Manager for Sybase Reference Guide 2 67

86 Engine CPU Busy Engine CPU Busy DESCRIPTION This monitor reports the percentage of the server s time since startup that is used by the engine for CPU activity and passed as an argument to the monitor. If you specify that the monitor is to check all engines, the monitor returns the highest percentage of CPU activity it found along with the engine number, which is the engine causing the most activity. The Sybase Adaptive Server can be configured (with the max online engines parameter) to use more than one engine. Usually the maximum number of engines equals the number of CPUs in the server, minus one. This monitor allows you to track the activity of one engine, or examine the spread of activity across all engines. MONITOR NUMBER 16 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer 2 68 Version 1.1

87 GUI DATA ENTRY FIELDS Engine CPU Busy The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Engine CPU Busy monitor. A description of the monitor argument follows. The SybaseServer Monitoring Collection Engine Number Specifies the number of the engine to monitor. The default is ALL, for all engines. Tivoli Manager for Sybase Reference Guide 2 69

88 Engine CPU Busy CLI SYNTAX EngineCPUBusy a <engine number> where: a <engine number> Enter a valid engine number, or ALL for all engines. CLI EXAMPLE waddmon SybaseServer EngineCPUBusy -a all -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/engine_cpu_busy.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 25 minutes 2 70 Version 1.1

89 OUTPUT Engine CPU Busy The following is an example output from the Engine CPU Busy monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is one of the following: The percent CPU usage for the engine specified as an argument to the monitor OR The highest percent CPU usage out of all the engines if ALL is specified as an argument to the monitor The trigger information (#TRIGGER_INFO=) is ENGINE= x, where x is the number of the engine with the highest percentage of CPU usage. Tivoli Manager for Sybase Reference Guide 2 71

90 Engine CPU Busy Below #TRIGGER_INFO= are row results, which provide one or the other of the following extra information: If ALL is selected, the percentage CPU usage and engine number for all the engines are given. OR If ALL is not selected and one engine number is supplied as an argument to the monitor, the trigger value and the trigger information are repeated. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES When multiple CPUs are available, the Sybase Adaptive Server can be configured with the max online engines parameter to have multiple engines. The distribution of tasks between the engines and the choice of CPU used by an engine is handled by the Sybase Adaptive Server (transparently to the user) and is not configurable. This monitor gives an indication of how the Sybase Adaptive Server is balancing the work load between the engines. A consistently high percentage of CPU activity reported by the monitor might indicate the need for an additional engine to be brought on line. Increasing the number of engines should only be done if there are enough available CPUs to support them. For important considerations when determining the optimum number of engines, refer to the Sybase Adaptive Server Enterprise System Administration Guide. SEE ALSO The following SybaseServer monitors: CPU By Process and User CPU Busy 2 72 Version 1.1

91 Engine Status Engine Status DESCRIPTION The monitor reports the number of engines found in the state specified, as an argument to the monitor. Available states are as follows: online offline in create in destroy debug MONITOR NUMBER 18 AUTHORIZATION ROLE sybase_monitor The SybaseServer Monitoring Collection TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 73

92 Engine Status GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Engine Status monitor. A description of the monitor argument follows. State You can use this field to specify one of the available states as an argument to the monitor. Enter the engine state in the text field exactly as it is listed on page 2-73 (lower case with the same spacing). OR Click the Choice button next to the text field to display the State dialog. See the following example Version 1.1

93 Engine Status Select an entry from the scrolling list of available states, then click the Set & Close button. The SybaseServer Monitoring Collection CLI SYNTAX EngineStatus a <engine state> where: a <engine state> Specifies the state you want to check. Note: Enter the engine state on the command line exactly as it is listed on page 2-73 (lower case with the same spacing). CLI EXAMPLE waddmon SybaseServer EngineStatus -a offline -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/engine_status.log <profilename> Tivoli Manager for Sybase Reference Guide 2 75

94 Engine Status SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Assuming the argument offline was passed to the monitor, the following suggested response levels cause a critical response if one or more engines are found to be in an offline state. Severity Trigger When Default Action Critical Greater than 0 Send Sybase Sentry Notice. Severe Not applicable None Warning Not applicable None Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes 2 76 Version 1.1

95 OUTPUT Engine Status The following is an example output from the Engine Status monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the number of engines found in the state that was passed as an argument to the monitor. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If your Sybase Adaptive Server is configured to use more than one engine, Tivoli recommends that you use this monitor in conjunction with the SQL Server Status monitor. See SQL Server Status on page However, if your Sybase Adaptive Server is configured to use only one engine, Tivoli recommends that you run only the SQL Server Status monitor. Tivoli Manager for Sybase Reference Guide 2 77

96 Engine Status SEE ALSO The following SybaseServer monitor: SQL Server Status 2 78 Version 1.1

97 Free Form SQL Numeric Free Form SQL Numeric DESCRIPTION You can use this monitor to define a monitor that meets your site s specific needs. This monitor runs a user-defined TRANSACT-SQL select statement that returns a numeric value. You can define multiple monitors and run them concurrently using the Free Form SQL Numeric monitor. The only limitation on the number of monitors you can create is your system resources. MONITOR NUMBER 44 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer The SybaseServer Monitoring Collection GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free Form SQL Numeric monitor. Descriptions of the monitor arguments follow. Tivoli Manager for Sybase Reference Guide 2 79

98 Free Form SQL Numeric SQL Statement Specifies the selection and calculation criteria for the monitor in the TRANSACT-SQL syntax. Column number of return value Specifies the column number in the first row returned that contains the monitor value. This is zero-based. Default value (if no rows found) Specifies the default value to be returned if no rows are returned from the SQL select statement Positive or negative integers, or zero, are acceptable input values Version 1.1

99 Free Form SQL Numeric CLI SYNTAX FreeFormSQLNumeric a <SQL_selectstatement> a <column> a <default> where: a <SQL_selectstatement> Specifies the selection and calculation criteria in the TRANSACT-SQL syntax for the monitor. a <column> Specifies the column number in the first row returned that contains the monitor value. This is zero-based. a <default> Specifies the value to be returned if no rows are returned from the SQL statement. Positive or negative integers, or zero, are acceptable input values. CLI EXAMPLE The following example creates a monitor that checks the number of devices on the Sybase Adaptive Server to which the monitor is distributed. waddmon SybaseServer FreeFormSQLNumeric -a select count(*) from master.dbo.sysdevices -a 0 -a 0 -t 40 minutes -c critical -R > 200 -p Root_pip-region -n Sybase Sentry -c severe -c warning -c normal -c always -f pip:/database/sybase/logs/freeform_numeric.log "<profilename>" In this example, the number of devices in the system table sysdevices is returned as the trigger value of the monitor. If there are more than 200 devices in the table, a critical response is generated with a pop-up window sent to Root_pip-region and a notice sent to the Sybase Sentry group. If fewer than 200 devices are in the table, the monitor output will always be recorded in the log file defined. No severe, warning, or normal responses are set. The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 81

100 Free Form SQL Numeric In this example, the SQL query provided to the monitor always returns a value of zero, or upwards. Therefore, in this example, the default value of zero provided to the monitor is never used. SUGGESTED RESPONSE LEVELS No response levels are suggested because they are dependent upon the select statement used. Suggested monitoring schedule: None suggested. OUTPUT The following is an example output from the Free Form SQL Numeric monitor: The trigger value returned by the monitor is the specified column of the first row that is returned. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which give all of the output of the SQL select statement passed as an argument to the monitor (that is, all the rows and columns returned by the statement) Version 1.1

101 Free Form SQL Numeric For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES You can use the Free Form SQL Numeric monitor to define an SQL select statement (using the TRANSACT-SQL syntax) as the basis of a monitor. Do not terminate the SQL statement with a semicolon (;) or forward slash (/). The select statement can return multiple columns and multiple rows. The monitor value (the value against which the monitoring criteria is evaluated) must be a numeric value that is in one of the columns in the first row returned by the select statement. The Column number of return value defines which column in the first row contains the monitor value (zero-based). An SQL select statement might return no rows. By default, Tivoli Manager for Sybase treats this as an error. However, you can override this default behavior by providing a Default value (if no rows found) value; in which case, the monitor returns the value specified. The SQL select statement you provide to the monitor will (unless specified otherwise) be executed on the master database. For example, select count(*) from sysusers will use the table master.dbo.sysusers, whereas select count(*) from database1.dbo.sysusers will obviously use the table database1.dbo.sysusers. The SybaseServer Monitoring Collection SEE ALSO The SybaseSever monitors Free Form SQL String, and the SybaseDatabase monitors Free Form SQL Numeric and Free Form SQL String Tivoli Manager for Sybase Reference Guide 2 83

102 Free Form SQL String Free Form SQL String DESCRIPTION You can use this monitor to define a monitor that meets your site s specific needs. This monitor runs a user-defined TRANSACT-SQL select statement that returns a string value. You can define multiple monitors and run them concurrently using the Free Form SQL String monitor. The only limitation on the number of monitors you can create is your system resources. MONITOR NUMBER 45 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free Form SQL String monitor. Descriptions of the monitor arguments follow Version 1.1

103 Free Form SQL String The SybaseServer Monitoring Collection SQL Statement Specifies the selection and calculation criteria for the monitor in the TRANSACT-SQL syntax. Column number of return value Specifies the column number in the first row returned that contains the monitor value. This is zero-based. Default value (if no rows found) Specifies the default value to be returned if no rows are returned from the SQL select statement. Any text string is an acceptable input. Tivoli Manager for Sybase Reference Guide 2 85

104 Free Form SQL String CLI SYNTAX FreeFormSQLString a <SQL_selectstatement> a <column> a <default> where: a <SQL_selectstatement> Specifies the selection and calculation criteria in the TRANSACT-SQL syntax for the monitor. a <column> Specifies the column number (zero-based), which is to contain the trigger value for the monitor, within the first row returned. a <default> Specifies the value to be returned if no rows are returned from the SQL statement. Any text string is an acceptable input. CLI EXAMPLE The following example creates a monitor that checks that the master database has a database identifier (dbid) of 1. waddmon SybaseServer FreeFormSQLString -a select name, dbid from master.dbo.sysdatabases \ where dbid=1 -a 0 -a FATAL -t 15 minutes -c critical -R == FATAL -p Root_pip-region -n Sybase Sentry -c severe -R!= master -p Root_pip-region -n Sybase Sentry -c warning -c normal -c always -f pip:/data/sybase/logs/freeform_string_server.log <profilename> The value in the first column is the monitor value. The monitor is set to run every 15 minutes. It takes the value from the first column of the first row returned by the SQL query. In this example, the monitor returns the name of the database with the ID of Version 1.1

105 Free Form SQL String If the database name is master, there is no problem. The name is returned as the monitor value. If the name is not master, it triggers a severe response level and sends a pop-up window to the root administrators group. It also sends a notice to the Sybase-Sentry notice group. If no value is returned by the SQL query, the value is defaulted to FATAL. This triggers a critical response level and sends a pop-up window to the root administrators group. It also sends a notice to the Sybase-Sentry notice group. No warning response level is set. SUGGESTED RESPONSE LEVELS No response levels are suggested because they are dependent upon the select statement used. Suggested monitoring schedule: None suggested. The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 87

106 Free Form SQL String OUTPUT The following is an example output from the Free Form SQL String monitor: The trigger value returned by the monitor is the specified column of the first row returned. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which give all of the output of the SQL select statement passed as an argument to the monitor (that is, all the rows and columns returned by the statement). For a general description of the monitor output, see Understanding the Monitor Output on page Version 1.1

107 Free Form SQL String USAGE NOTES You can use the Free Form SQL String monitor to define an SQL select statement (using the TRANSACT-SQL syntax) as the basis of a monitor. Do not terminate the SQL statement with a semicolon (;) or forward slash (/). The select statement can return multiple columns and multiple rows. The monitor value (the value against which the monitoring criteria is evaluated) must be a string value that is in one of the columns in the first row returned by the select statement. The Column number of return value defines which column in the first row contains the monitor value (zero-based). An SQL select statement might return no rows. By default, Tivoli Manager for Sybase treats this as an error. However, you can override this default behavior by providing a Default value (if no rows found) value; in which case, the monitor returns the value specified. The SQL select statement you provide to the monitor will (unless specified otherwise) be executed on the master database. For example, select name from sysusers will use the table master.dbo.sysusers, whereas select name from database1.dbo.sysusers will obviously use the table database1.dbo.sysusers. The SybaseServer Monitoring Collection SEE ALSO The SybaseSever monitors Free Form SQL Numeric, and the SybaseDatabase monitors Free Form SQL Numeric and Free Form SQL String Tivoli Manager for Sybase Reference Guide 2 89

108 Infected Processes Infected Processes DESCRIPTION This monitor reports on those processes marked as infected in the system table sysprocesses. A process is marked as infected when the server detects a serious error condition, prints a stack trace, and terminates the process. On termination, the process disappears from the sysprocesses table and is not reported by the monitor. The monitor output identifies the infected process that was killed by the server. MONITOR NUMBER 19 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX InfectedProcesses CLI EXAMPLE waddmon SybaseServer InfectedProcesses -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/infected_processes.log <profilename> 2 90 Version 1.1

109 SUGGESTED RESPONSE LEVELS Infected Processes The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels cause a critical response if any process is found to be in an infected state. Severity Trigger When Default Action Critical Greater than 0 Send Sybase Sentry Notice. Severe Not applicable None Warning Not applicable None Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 91

110 Infected Processes OUTPUT The following is an example output from the Infected Processes monitor: The trigger value returned by the monitor is the number of processes found in an infected state. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value and give the process ID (spid) and associated program name for each process found to be in an infected state. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES Only rarely do processes become infected and usually this is only a transient state. The server quickly kills the process, removing it from the system table sysprocesses. On very rare occasions, a process is marked as infected and remains in the sysprocesses table long enough for this monitor to detect it Version 1.1

111 Infected Processes SEE ALSO None The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 93

112 Locks Available Locks Available DESCRIPTION This monitor allows you to track the use and availability of locks. The monitor reports the number of locks currently available on the target server. For example, if the server is configured with the parameter number of locks to have at most 5000 locks and, when the monitor is run, 3000 locks are currently in use, then this monitor will return the value If the system runs out of locks, the Sybase Adaptive Server displays a server-level error message and the users experience lock errors. When a lock is in use, it blocks access to a database object, thereby increasing the chances of contention for objects and deadlocks. This potentially decreases the performance of the server by reducing throughput of the server and lengthening response times. MONITOR NUMBER 21 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX LocksAvailable 2 94 Version 1.1

113 CLI EXAMPLE waddmon SybaseServer LocksAvailable -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/locks_available.log <profilename> Locks Available SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels are based on the assumption that the number of locks configuration parameter is set to Severity Trigger When Default Action Critical Less than 500 Send Sybase Sentry Notice. The SybaseServer Monitoring Collection Severe Less than 1000 Send Sybase Sentry Notice. Warning Less than 1500 Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 10 minutes Tivoli Manager for Sybase Reference Guide 2 95

114 Locks Available OUTPUT The following is an example output from the Locks Available monitor: The trigger value returned by the monitor is the number of locks available. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If the system is running out of locks, you might have to adjust the number of locks configuration parameter. This parameter sets the maximum number of locks allowed on the server. The value of this parameter must be carefully tuned to suit your needs. In setting this parameter value, you should remember that each lock takes up 32 bytes of RAM, so increasing this configuration parameter costs memory Version 1.1

115 Locks Available Locks block access to database objects, preventing other transactions from accessing the data. This is called lock contention. If you suspect this is a problem on your system, then you can use the system-stored procedures sp_sysmon and sp_lock to gain further details regarding the locks. Lock contention can be reduced by keeping transactions short, avoiding hot spots in tables, decreasing the number of rows on each page, and tuning the lock promotion thresholds. For most monitoring purposes, you only need to use either this monitor or one of the following: Locks In Use, Percent Locks Available, or Percent Locks Used. SEE ALSO The following SybaseServer monitors: Blocked Processes, Locks In Use, Percent Locks Available, and Percent Locks Used The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 97

116 Locks In Use Locks In Use DESCRIPTION This monitor allows you to track the use of locks and the number of active locks during server activity. The monitor reports the number of locks currently in use on the target server. If the system runs out of locks, the Sybase Adaptive Server will display a server-level error message and the users will experience lock errors. When a lock is in use, it blocks access to a database object, thereby increasing the chances of contention for objects and deadlocks. This potentially decreases the performance of the server by reducing throughput of the server and lengthening response times. MONITOR NUMBER 20 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX LocksInUse 2 98 Version 1.1

117 Locks In Use CLI EXAMPLE waddmon SybaseServer LocksInUse -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/locks_in_use.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels are based on the assumption that the number of locks configuration parameter is set to Severity Trigger When Default Action Critical Greater than 4500 Send Sybase Sentry Notice. The SybaseServer Monitoring Collection Severe Greater than 4000 Send Sybase Sentry Notice. Warning Greater than 3500 Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 10 minutes Tivoli Manager for Sybase Reference Guide 2 99

118 Locks In Use OUTPUT The following is an example output from the Locks in Use monitor: The trigger value returned by the monitor is the number of locks currently in use. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If the system is running out of locks, you might have to adjust the number of locks configuration parameter. This parameter sets the maximum number of locks allowed on the server. The value of this parameter must be carefully tuned to suit your needs. In setting this parameter value, you should remember that each lock takes up 32 bytes of RAM, so increasing this configuration parameter costs memory Version 1.1

119 Locks In Use Locks block access to database objects, preventing other transactions from accessing the data. This is called lock contention. If you suspect this is a problem on your system, then you can use the system-stored procedures sp_sysmon and sp_lock to gain further details regarding the locks. Lock contention can be reduced by keeping transactions short, avoiding hot spots in tables, decreasing the number of rows on each page, and tuning the lock promotion thresholds. For most monitoring purposes, you only need to use either this monitor or one of the following: Locks Available, Percent Locks Available, or Percent Locks Used. SEE ALSO The following SybaseServer monitors: Blocked Processes, Locks Available, Percent Locks Available, and Percent Locks Used The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 101

120 Long Running Transactions Long Running Transactions DESCRIPTION This monitor tracks processes that have been idle since the monitor was last run. A process is deemed idle if in the sysprocesses system table, the following have not changed: The kernel process ID The amount of CPU used The amount of memory allocated to the process The number of disk reads and writes You can exclude certain processes from consideration by providing their names as arguments to this monitor. See GUI DATA ENTRY FIELDS below or CLI SYNTAX on page This monitor returns the program name that is associated with the first idle process listed in sysprocesses. The monitor output also contains a list of all other processes found to be idle. See OUTPUT on page Use this monitor to track programs that become unexpectedly idle. In particular, you can use this monitor to detect users who are occupying connections to the server, but not actually using them. MONITOR NUMBER 22 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Version 1.1

121 GUI DATA ENTRY FIELDS Long Running Transactions The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Long Running Transactions monitor. A description of the monitor argument follows. The SybaseServer Monitoring Collection Exclude program_name(s) You can use this field to list the names of programs to be excluded by the monitor. Enter the program names in the text field exactly as they appear in the program_name column of the sysprocesses system table. For multiple program names, separate them by spaces. Tivoli Manager for Sybase Reference Guide 2 103

122 Long Running Transactions CLI SYNTAX For example, to exclude all ctisql connections, enter ctisql in the field. The SQL wildcard % is supported. For example, to exclude all ctisql connections and all programs with names starting with Tiv, enter ctisql Tiv% in the field. LongRunningTransactions a <exclude program_name(s)> where: a <exclude program_name(s)> Specifies a list of program_name values to be excluded from this check. Notes: Enter the program names on the command line exactly as they appear in the program_name column of the sysprocesses system table. For multiple program names, separate them by spaces. The SQL wildcard % is supported. To exclude all programs with names starting with Tiv, for example, enter Tiv% into the field. CLI EXAMPLE waddmon SybaseServer LongRunningTransactions -a ctisql Tiv% -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/long_running_transactions.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide Version 1.1

123 Long Running Transactions The following suggested response levels cause a warning response if any program is found to be idle since the monitor was last run. Note that the trigger value is a blank space. No quotation marks are required. Severity Trigger When Default Action Critical Not applicable None Severe Not applicable None Suggested monitoring schedule: 30 minutes OUTPUT Warning Not equal to Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None The following is an example output from the Long Running Transactions monitor: The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 105

124 Long Running Transactions The trigger value returned by this monitor is the program name associated with the first idle process listed in the sysprocesses system table. The trigger information (#TRIGGER_INFO=) is the kernel process ID (kpid) of the first idle process listed in the sysprocesses system table. Below #TRIGGER_INFO= are row results, which list the kpid, process ID (spid), name of the front-end module (program_name), cumulative CPU time in clicks (cpu), amount of memory allocated to the process (memusage), and number of disk reads and writes for the current command (physical_io) for each idle process. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES By setting the trigger value to be a particular program name, you can monitor if that program becomes unexpectedly idle. By setting the trigger value to be a blank space, and setting the trigger to be Not equal to, the monitor can alert you if any program (apart from those programs excluded by the argument to the monitor) is idle, regardless of its name. Note that the monitoring schedule is significant, since a process is considered idle if certain statistics have not changed since the monitor was last run. SEE ALSO None Version 1.1

125 Memory Usage By Process Memory Usage By Process DESCRIPTION This monitor checks the amount of memory in pages being used by each process running on the server, and returns the largest amount being used. The output also indicates the login name of the user who initiated the process, plus the process ID. Use this monitor to track memory usage by processes and to identify those process that are using excessive memory. When the CPU usage value of a process reaches the value of the server configuration parameter cpu accounting flush interval (which is used for chargeback accounting), the sysprocesses system table, including memusage values, is re-initialized. Consequently, the figures reported by this monitor might not be representative of memory usage since the server was started. If you are not running the accounting options, setting cpu accounting flush interval to the highest possible value will result in a more accurate memory usage report by the monitor. The SybaseServer Monitoring Collection MONITOR NUMBER 24 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX MemoryUsageByProcess Tivoli Manager for Sybase Reference Guide 2 107

126 Memory Usage By Process CLI EXAMPLE waddmon SybaseServer MemoryUsageByProcess -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/memory_usage_by_process.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 20 minutes OUTPUT The following is an example output from the Memory Usage By Process monitor: Version 1.1

127 Memory Usage By Process The trigger value returned by the monitor is the largest number of memory pages being used by a process on the server. The trigger information (#TRIGGER_INFO=) is SPID= x NAME= y, where x is the process ID of the process using the most memory, and y is the login name of the user who initiated the process. Below #TRIGGER_INFO= are row results, which list in descending order of memory usage, the memory usage in pages, process ID, and user login name for all processes in the sysprocesses system table (or as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES None SEE ALSO None The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 109

128 Packet Errors Packet Errors DESCRIPTION This monitor returns the number of network errors that have occurred while the Sybase Adaptive Server was sending and receiving packets since server startup. On the average network, occasional errors are to be expected; busier networks might experience regular errors. Use this monitor to detect increases in the error rate. When errors occur, the Sybase Adaptive Server will be temporarily blocked from reading or writing to the network. Therefore, a high error rate will slow the server s access to the network and users will see slower performance. MONITOR NUMBER 25 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX PacketErrors CLI EXAMPLE waddmon SybaseServer PacketErrors -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/packet_errors.log <profilename> Version 1.1

129 SUGGESTED RESPONSE LEVELS Packet Errors No response levels are suggested since the number of expected errors will vary from site to site. Suggested monitoring schedule: 15 minutes OUTPUT The following is an example output from the Packet Errors monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the number of network packet errors. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If an unsatisfactorily large number of packet errors are encountered, consult with the network administrator of your site. Tivoli Manager for Sybase Reference Guide 2 111

130 Packet Errors SEE ALSO The following SybaseServer monitors: Packets Received and Packets Sent Version 1.1

131 Packets Received Packets Received DESCRIPTION This monitor returns the total number of network packets read by the server since its startup. The result of this monitor indicates the amount of network traffic being generated by the server. Take these results in conjunction with the output of the Packets Sent monitor to gain a much clearer picture of the total network traffic related to the server. For details, see USAGE NOTES on page You can determine the total number of network packets read since the monitor was last run by comparing the total with the value returned by the monitor when it ran previously. The previous value is always included in the monitor s output. Large amounts of network traffic obviously slow down the response times experienced by users connected to the server. Among the many ways you can reduce the network traffic generated by users are the following: Alter the network packet size with the configuration parameter default network packet size, which reduces the number of packets being transferred Use stored procedures Carefully design applications and queries Circumspectly use cursors and perform backups (or other such network traffic generating tasks) at off-peak times The SybaseServer Monitoring Collection MONITOR NUMBER 26 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 113

132 Packets Received GUI DATA ENTRY FIELDS None CLI SYNTAX PacketsReceived CLI EXAMPLE waddmon SybaseServer PacketsReceived -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/packets_received.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 10 minutes Version 1.1

133 OUTPUT Packets Received The following is an example output from the Packets Received monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the total number of packets received. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor can be used in conjunction with the Packets Sent monitor to give an indication of the total network traffic caused by the Sybase Adaptive Server. The combined results of these two monitors gives the total number of network I/Os since server startup. See Packets Sent on page Tivoli Manager for Sybase Reference Guide 2 115

134 Packets Received By using the Previous value provided in these monitor outputs, you can determine the total network I/O that occurred during the last monitoring interval. You can then compare this figure to the number of packets per second that the network can handle. In this way, you can determine if the Sybase Adaptive Server is challenging the network bandwidth. By altering the network packet size with the configuration parameter default network packet size, you can reduce the actual number of packets being transferred. The number of packets sent is generally more important than their sizes; it is the processing time per packet that is the performance overhead. SEE ALSO The following SybaseServer monitors: Packet Errors and Packets Sent Version 1.1

135 Packets Sent Packets Sent DESCRIPTION This monitor returns the total number of network packets written by the Adaptive Server since server startup. The result of this monitor indicates the amount of network traffic being generated by the server. Take these results in conjunction with the output of the Packets Received monitor to gain a much clearer picture of the total network traffic related to the server. For details, see USAGE NOTES on page You can determine the total number of network packets written since the monitor was last run by comparing the total with the value returned by the monitor when it ran previously. The previous value is always included in the monitor s output. Large amounts of network traffic obviously slow down the response times experienced by users connected to the server. Among the many ways you can reduce the network traffic generated by users are the following: Alter the network packet size with the configuration parameter default network packet size, which reduces the number of packets being transferred Use stored procedures Carefully design applications and queries Circumspectly use cursors and perform backups (or other such network traffic generating tasks) at off-peak times The SybaseServer Monitoring Collection MONITOR NUMBER 27 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 117

136 Packets Sent GUI DATA ENTRY FIELDS None CLI SYNTAX PacketsSent CLI EXAMPLE waddmon SybaseServer PacketsSent -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/packets_sent.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 10 minutes Version 1.1

137 OUTPUT Packets Sent The following is an example output from the Packets Sent monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the total number of packets sent. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor can be used in conjunction with the Packets Received monitor to give an indication of the total network traffic caused by the Adaptive Server. The combined results of these two monitors gives the total number of network I/Os since server startup. See Packets Received on page Tivoli Manager for Sybase Reference Guide 2 119

138 Packets Sent By using the Previous value, provided in these monitor outputs, you can determine the total network I/O that occurred during the last monitoring interval. You can then compare this figure to the number of packets per second that the network can handle. In this way, you can determine if the Sybase Adaptive Server is challenging the network bandwidth. By altering the network packet size with the configuration parameter default network packet size, you can reduce the actual number of packets being transferred. The number of packets sent is generally more important than their size; it is the processing time per packet that is the performance overhead. SEE ALSO The following SybaseServer monitors: Packet Errors and Packets Received Version 1.1

139 Percent Connections Used Percent Connections Used DESCRIPTION This monitor returns the current number of user connections to the target server as a percentage of the allowable connections. It returns the percentage of connections that are used. You use the number of user connections configuration parameter to control the maximum number of allowable connections. The value of this parameter is included in this monitor s output. For example, if this parameter is set to 100 and there are currently 30 user connections, this monitor will return the value 30%. Use this monitor to alert you when the server is running out of user connections, which can result in server access problems. This monitor is also useful for tracking client access patterns. If the monitor alerts you that connections are running out, consider either clearing out some of the existing connections, or increasing the setting of the number of user connections parameter. For important considerations when extending the number of user connections parameter, refer to the Sybase Adaptive Server Enterprise System Administration Guide. The SybaseServer Monitoring Collection MONITOR NUMBER 28 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX PercentConnectionsUsed Tivoli Manager for Sybase Reference Guide 2 121

140 Percent Connections Used CLI EXAMPLE waddmon SybaseServer PercentConnectionsUsed -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/percent_connections_used.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Greater than 90% Send Sybase Sentry Notice. Severe Greater than 80% Send Sybase Sentry Notice. Warning Greater than 70% Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 30 minutes Version 1.1

141 OUTPUT Percent Connections Used The following is an example output from the Percent Connections Used monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the percent connections used. The trigger information (#TRIGGER_INFO=) is CURRENT= x MAX= y, where x is the number of connections currently in use, and y is the maximum number of connections allowed. Below #TRIGGER_INFO= are row results, which repeat the numbers x and y, separated by a comma ( x,y ). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES You will probably only need to use either this monitor or one of the following monitors: Connections Available or Connections In Use Tivoli Manager for Sybase Reference Guide 2 123

142 Percent Connections Used SEE ALSO The following SybaseServer monitors: Connections Available and Connections In Use Version 1.1

143 Percent Locks Available Percent Locks Available DESCRIPTION This monitor returns the number of locks currently available on the target server as a percentage of the maximum number of locks allowable. You use the number of locks configuration parameter to control the maximum number of locks allowable. The value of this parameter is included in this monitor s output. For example, if this parameter is set to 5000 and there are currently 3000 locks in use, this monitor will return the value 40%. That is, 40% of the locks are not in use and are available. This monitor allows you to track the use of locks and monitor the availability of locks. If the system runs out of locks, the Sybase Adaptive Server will display a server-level error message and users will experience lock errors. Each lock in use blocks access to a database object, thereby increasing the chances of contention for objects and deadlocks. This potentially decreases performance of the server by reducing throughput and lengthening response times. The SybaseServer Monitoring Collection MONITOR NUMBER 31 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX PercentLocksAvailable Tivoli Manager for Sybase Reference Guide 2 125

144 Percent Locks Available CLI EXAMPLE waddmon SybaseServer PercentLocksAvailable -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/percent_locks_available.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Less than 10% Send Sybase Sentry Notice. Severe Less than 20% Send Sybase Sentry Notice. Warning Less than 30% Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 10 minutes Version 1.1

145 OUTPUT Percent Locks Available The following is an example output from the Percent Locks Available monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the percent locks available. The trigger information (#TRIGGER_INFO=) is USED= x MAX= y, where x is the number of locks currently in use and y is the maximum number of locks allowed. Below #TRIGGER_INFO= are row results, which repeat the numbers x and y, separated by a comma ( x,y ). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. Tivoli Manager for Sybase Reference Guide 2 127

146 Percent Locks Available USAGE NOTES If the system is running out of locks, you might have to adjust the number of locks configuration parameter. This parameter sets the maximum number of locks allowed on the server. The value of this parameter must be carefully tuned to suit your needs. In setting this parameter value, you should remember that each lock takes up 32 bytes of RAM, so increasing this configuration parameter costs memory. Locks block access to database objects, preventing other transactions from accessing the data. This is called lock contention. If you suspect this is a problem on your system, then you can use the system-stored procedures sp_sysmon and sp_lock to gain further details regarding the locks. Lock contention can be reduced by keeping transactions short, avoiding hot spots in tables, decreasing the number of rows per page, and tuning the lock promotion thresholds. For most monitoring purposes, you only need to use either this monitor or one of the following: Locks Available, Locks In Use, or Percent Locks Used. SEE ALSO The following SybaseServer monitors: Blocked Processes, Locks Available, Locks In Use, and Percent Locks Used Version 1.1

147 Percent Locks Used Percent Locks Used DESCRIPTION This monitor returns the number of locks currently in use on the target server as a percentage of the maximum number of locks allowable. You use the number of locks configuration parameter to control the maximum number of locks allowable. The value of this parameter is included in this monitor s output. For example, if this parameter is set to 5000 and there are currently 3000 locks in use, this monitor will return the value 60%. That is, 60% of the locks are in use and are not available. This monitor allows you to track the use of locks and monitor the percentage of locks active during server activity. If the system runs out of locks, the Sybase Adaptive Server will display a server-level error message and users will experience lock errors. Each lock in use blocks access to a database object, thereby increasing the chances of contention for objects and deadlocks. This potentially decreases performance of the server by reducing throughput and slowing down response times. The SybaseServer Monitoring Collection MONITOR NUMBER 29 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX PercentLocksUsed Tivoli Manager for Sybase Reference Guide 2 129

148 Percent Locks Used CLI EXAMPLE waddmon SybaseServer PercentLocksUsed -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/percent_locks_used.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Greater than 90% Send Sybase Sentry Notice. Severe Greater than 80% Send Sybase Sentry Notice. Warning Greater than 70% Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 10 minutes Version 1.1

149 OUTPUT Percent Locks Used The following is an example output from the Percent Locks Used monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the percent locks used. The trigger information (#TRIGGER_INFO=) is USED= x MAX= y, where x is the number of locks currently in use, and y is the maximum number of locks allowed. Below #TRIGGER_INFO= are row results, which repeat the numbers x and y, separated by a comma ( x,y ). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. Tivoli Manager for Sybase Reference Guide 2 131

150 Percent Locks Used USAGE NOTES If the system is running out of locks, you might have to adjust the number of locks configuration parameter. This parameter sets the maximum number of locks allowed on the server. The value of this parameter must be carefully tuned to suit your needs. In setting this parameter value, you should remember that each lock takes up 32 bytes of RAM, so increasing this configuration parameter costs memory. Locks block access to database objects, preventing other transactions from accessing the data. This is called lock contention. If you suspect this is a problem on your system, then you can use the system-stored procedures sp_sysmon and sp_lock to gain further details regarding the locks. Lock contention can be reduced by keeping transactions short, avoiding hot spots in tables, decreasing the number of rows per page, and tuning the lock promotion thresholds. For most monitoring purposes, you only need to use either this monitor or one of the following: Locks Available, Locks In Use, or Percent Locks Available. SEE ALSO The following SybaseServer monitors: Blocked Processes, Locks Available, Locks In Use, and Percent Locks Available Version 1.1

151 Percent Transaction Log Space Used By Server Percent Transaction Log Space Used By Server DESCRIPTION This monitor evaluates each database managed by a Sybase Adaptive Server in turn, determining the total space available for the transaction log, then calculating the percentage of log space currently in use by the log. This monitor returns the name and the percent used for the database with the highest percentage used found, alerting you to the transaction log possibly nearest to running out of space. The rest of this monitor s output lists the percentage of transaction log space used for every other database on the server (or as many as will fit within the 1000-character restriction on the output s length). For example, if KB of disk space in a database is permitted to have log information (that is, sp_helpdb dbname lists this space as being log only or data and log) and the transaction log currently contains 4096 KB of information, then this monitor returns the value 40% (meaning the log is 40% used). You can use this monitor to alert you to transaction logs that are dangerously close to running out of space. Such an event would suspend the database s operations until the log is dumped. Additionally, you can use this monitor to help you determine the optimum log size, select the optimum thresholds for the log and schedule timing of transaction log dumps. The SybaseServer Monitoring Collection MONITOR NUMBER 41 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 133

152 Percent Transaction Log Space Used By Server GUI DATA ENTRY FIELDS None CLI SYNTAX TransactionLogSpaceUsed CLI EXAMPLE waddmon SybaseServer TransactionLogSpaceUsed -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs \ /transaction_log_space_used.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Greater than 85% Send Sybase Sentry Notice. Severe Greater than 75% Send Sybase Sentry Notice. Warning Greater than 65% Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes Version 1.1

153 OUTPUT Percent Transaction Log Space Used By Server The following is an example output from the Percent Transaction Log Space Used By Server monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the percent transaction log space used for the database with the fullest transaction log. The trigger information (#TRIGGER_INFO=) is the name and percent usage figure for the database with the greatest log space usage. Below #TRIGGER_INFO= are row results, which list the names and percent usage figures for all the other databases on the server. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. Tivoli Manager for Sybase Reference Guide 2 135

154 Percent Transaction Log Space Used By Server USAGE NOTES A high percentage returned by the monitor is not necessarily a cause for alarm. If the database is static, the remaining space might be adequate. However, a volatile database with only a small amount of room for log expansion might soon run out of space. When the transaction log usage is determined for a database, if the database is found to be in one of the following states, then it is not possible to connect to that database. Therefore, the transaction log percent usage returned by the monitor for that database will be zero. The states are as follows: database offline database offline until recovery completes database is being recovered database suspect database created with for load To be alerted of the log space used by a particular database, use one of the following SybaseDatabase monitors: Percent Transaction Log Space Used or Transaction Log Free Space. These monitors are applied to a particular database rather than to all databases on the server. SEE ALSO The following SybaseDatabase monitors: Percent Transaction Log Space Used and Transaction Log Free Space Version 1.1

155 Physical IO By Process Physical IO By Process DESCRIPTION This monitor examines the number of disk reads and writes for all the user processes on the server. For each process, it determines the amount of physical I/O so far performed by the current command. The monitor output returns the highest physical I/O found for a process. It does not report the total I/O executed by the process so far, only the I/O of the current command of that process. The monitor output gives the process ID (spid) and the login name of the user who initiated the process. Only users connected to the server are considered by this monitor system processes with a set user ID (suid) value of zero are ignored. The remaining processes and their I/O statistics are listed in the monitor s output. You can use this monitor to identify processes that consistently make a high number of disk reads and writes, indicating a large amount of data access and possibly a large number of insert, update, or delete activities. You can also use this monitor to get an indication of the general disk access patterns of the users on the server. The sysprocesses system table is re-initialized when the CPU usage value reaches the value of the server configuration parameter cpu accounting flush interval (which is used to facilitate chargeback accounting). Consequently, the value reported by this monitor might not represent physical I/O of the current command. If you are not running the accounting options, then setting cpu accounting flush interval to the highest possible value will result in a more accurate CPU usage report by this monitor. The SybaseServer Monitoring Collection MONITOR NUMBER 32 AUTHORIZATION ROLE sybase_monitor Tivoli Manager for Sybase Reference Guide 2 137

156 Physical IO By Process TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX PhysicalIOByProcess CLI EXAMPLE waddmon SybaseServer PhysicalIOByProcess -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/physical_io_by_process.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 10 minutes Version 1.1

157 OUTPUT Physical IO By Process The following is an example output from the Physical IO By Process monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the highest amount of I/O found for a process. The trigger information (#TRIGGER_INFO=) is SPID= x OWNER= y, where x is the ID of the process with the highest I/O, and y is the name of the user who initiated the process. Below #TRIGGER_INFO= are row results in ascending order of I/O, which include the amount of I/O, process ID, and name of the user for every user process (or as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. Tivoli Manager for Sybase Reference Guide 2 139

158 Physical IO By Process USAGE NOTES You might want to streamline processes that make a high number of I/Os. Examine their queries to ensure they are not reading more information than required. For example, you might need to add an index to a table, which would prevent table scans. Another way to increase performance might be to stagger update and insert activities to better balance the write load. If the I/O subsystem handles queued I/O efficiently, you can increase the maximum number of asynchronous disk I/O requests that can be outstanding at one time by increasing the configuration parameter max asyn i/os per server or max async i/os per engine, or both. Setting these configuration parameters too high can overload the disk subsystem with writes. If an engine issues an asynchronous I/O that would exceed max async i/os per server or max async i/os per engine, the I/O is delayed until enough outstanding I/Os have completed to fall below the limit that was exceeded. SEE ALSO None Version 1.1

159 SLD Free Space SLD Free Space DESCRIPTION This monitor checks the percentage of free space on all the devices at the target server. The monitor returns the name and percentage of free space for the device with the least space available. The rest of this monitor s output lists percentage of free space for all other devices at the server, along with their device sizes and amount used. Assuming the device size is constant between runs of the monitor, a decrease in the amount of free space on the device indicates that the size of a database has increased, or that another database was created on the device. Conversely, an increase in the amount of free space on a device indicates that a database has been dropped. You can use this monitor to track the use of all the devices at a server and to be warned when free device space is getting critically low. Such a warning might indicate the need for additional devices. MONITOR NUMBER 33 The SybaseServer Monitoring Collection AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX SLDFreeSpace Tivoli Manager for Sybase Reference Guide 2 141

160 SLD Free Space CLI EXAMPLE waddmon SybaseServer SLDFreeSpace -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/sld_free_space.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Less than 10% Send Sybase Sentry Notice. Severe Less than 20% Send Sybase Sentry Notice. Warning Less than 30% Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 30 minutes Version 1.1

161 OUTPUT SLD Free Space The following is an example output from the SLD Free Space monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is the percentage of free space on the device with the least free space available. The trigger information (#TRIGGER_INFO=) is USED= y SIZE= z NAME= my_device, where y is the space in kilobytes (KB) on the device allocated to databases (that is, used), z is the total size of that device (in KB), and my_device is the logical name of the device. Below #TRIGGER_INFO= are row results, which include x, the percentage of free space on the device, and repeat y, z, and my_device from the trigger information, separated by commas ( x,y,z,my_device ) for all devices at the server (or as many as will fit within the 1000-character restriction on the output s length). Tivoli Manager for Sybase Reference Guide 2 143

162 SLD Free Space For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor enables you to keep track of all devices at one time, the output giving a full breakdown of space used and free for every device. To use the monitor to report on all device usage at the server, set up the monitor as response level: always. However, if there is a crucial device that you want to monitor closely, then consider setting up an additional monitor: SLD Free Space By Device or SLD Space Used By Device. SEE ALSO The following SybaseServer monitors: SLD Free Space By Device and SLD Space Used By Device Version 1.1

163 SLD Free Space By Device SLD Free Space By Device DESCRIPTION This monitor returns the amount of free space (that is, the amount of space not allocated to databases), in kilobytes (KB), on a logical device at the target server. Also provided in the monitor s output is the size of the device and the spaced used on the device. If the specified device does not exist, then the monitor returns 0.0 as the amount of free space to allow for distribution of the monitor over multiple servers. Use this monitor to track usage of a particular device and to be alerted when a device is near its maximum capacity. If a device is reaching its capacity, then consider doing the following: use other existing devices, create new devices, or drop the near-full device and alter its size, then add it back again. For details, refer to the Sybase Adaptive Server Enterprise System Administration Guide. Assuming the device size is constant between runs of the monitor, a decrease in the amount of free space returned by the monitor indicates either that the size of a database has been increased on the device with alter, or that another database was created on the device. Conversely, an increase in the amount of free space on a device indicates that a database has been dropped. The SybaseServer Monitoring Collection MONITOR NUMBER 31 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 145

164 SLD Free Space By Device GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the SLD Free Space By Device monitor. A description of the monitor argument follows. SLD Name You can use this field to enter the logical device name of the device you wish to monitor The default is master, indicating the master device. CLI SYNTAX SLDFreeSpaceByDevice a <logical_device_name> a <logical_device_name> Specifies the logical device name Version 1.1

165 CLI EXAMPLE SLD Free Space By Device waddmon SybaseServer SLDFreeSpaceByDevice -a master -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/sld_free_space_by_device.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 15 minutes OUTPUT The following is an example output from the SLD Free Space By Device monitor: The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 147

166 SLD Free Space By Device The trigger value returned by the monitor is the amount of free space (in KB) of the input device. The trigger information (#TRIGGER_INFO=) is USED= x SIZE= y PHYNAME= z, where x is the space (in KB) on the device allocated to databases, y is the size of that device (in KB), and z is the physical name of the device. Below #TRIGGER_INFO= are row results, which repeat the numbers x and y, plus the physical name z from the trigger information, separated by commas ( x,y,z ). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If you simply want to monitor changes in the space used on a device, then you might set up the monitor to generate a critical response when the trigger value changes by 1024 KB used. This would ensure that if the device usage goes up or down by 1024 KB (1 MB) or more, then a critical response is generated. For one device, you probably only need to use either this monitor or the SLD Space Used By Device monitor. For a broader view of device usage, you can use SLD Free Space, which monitors all the devices at the server. SEE ALSO The following SybaseServer monitors: SLD Free Space and SLD Space Used By Device Version 1.1

167 SLD Space Used By Device SLD Space Used By Device DESCRIPTION This monitor returns the space, in kilobytes (KB), allocated to databases on a specified device on the target server. The monitor s output also includes the size of the device, which allows you to determine the available free space on the device. However, if free space on the device is of utmost concern, consider using the SLD Free Space By Device monitor. If the specified device does not exist, the monitor returns 0.0; this allows for distribution of the monitor across multiple servers. You can use this monitor to track usage of a device. Assuming the device size is constant between runs of the monitor, an increase in the amount of space used returned by the monitor indicates that either the size of a database has been increased on the device with alter, or another database was created on the device. Conversely, a reduction in the amount of space used on a device indicates that a database has been dropped. The SybaseServer Monitoring Collection MONITOR NUMBER 30 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer Tivoli Manager for Sybase Reference Guide 2 149

168 SLD Space Used By Device GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the SLD Space Used By Device monitor. A description of the monitor argument follows. SLD Name You can use this field to enter the logical device name of the device you wish to monitor The default is master, indicating the master device. CLI SYNTAX SLDSpaceUsedByDevice a <logical_device_name> a <logical_device_name> Specifies the logical device name Version 1.1

169 CLI EXAMPLE SLD Space Used By Device waddmon SybaseServer SLDSpaceUsedByDevice -a master -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/sld_space_used_by_device.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 15 minutes OUTPUT The following is an example output from the SLD Space Used By Device monitor: The SybaseServer Monitoring Collection The trigger value returned by the monitor is x, which is the amount of space (in KB) used on the input device. Tivoli Manager for Sybase Reference Guide 2 151

170 SLD Space Used By Device The trigger information (#TRIGGER_INFO=) is SIZE= y PHYNAME= name, where y is the total size of the device (in KB), and name is the physical name of the device. Below #TRIGGER_INFO= are row results, which repeat x from the trigger value, and y and name from the trigger information, separated by commas ( x,y,name ). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES To monitor changes in the space used on a device, set up the monitor to generate a critical response when the trigger value changes by 1024 KB used. This ensures that if the device usage increases or decreases by 1024 KB (1 MB) or more, a critical response is generated. For one device, you probably only need to use either this monitor or the SLD Free Space By Device monitor. For a broader view of device usage, you can use SLD Free Space, which monitors all the devices at the server. SEE ALSO The following SybaseServer monitors: SLD Free Space and SLD Free Space By Device Version 1.1

171 SQL Server Status SQL Server Status DESCRIPTION This monitor checks the availability of the target server (SybaseDataServer, SybaseBackupServer, or SybaseMonitorServer). The monitor checks the target server to see which state it is in, and returns one of the states listed in the following table. (The equivalent state names to use in the command line are also included in the table.) State CLI State Explanation Is Available == AVAILABLE Tivoli Manager for Sybase can connect to the server. Is Suspect == SUSPECT Tivoli Manager for Sybase cannot connect to the server, but the server is not shut down. Is Shutdown == SHUTDOWN The server was shut down by one of the following: The Sybase services manager (if server runs on NT) A user-issued shutdown TSQL statement The control panel (if server runs on NT) A third-party utility The SybaseServer Monitoring Collection Is Unavailable!= AVAILABLE The server is shut down or suspect. Becomes Available -> AVAILABLE Last time the monitor was run the server was suspect or shut down, but is now available. Tivoli Manager for Sybase Reference Guide 2 153

172 SQL Server Status State CLI State Explanation Becomes Suspect Becomes Shutdown Becomes Unavailable -> SUSPECT Last time the monitor was run the server was available or shut down, but is now suspect. -> SHUTDOWN Last time the monitor was run the server was suspect or available, but is now shut down. -< AVAILABLE Last time the monitor was run the server was available, but is now shut down or suspect. The states in this table map to the AVAILABLE, SHUTDOWN, and SUSPECT icon states for the servers described in Chapter 6, Using Tivoli Manager for Sybase, in the Tivoli Manager for Sybase User s Guide. This availability check tests Tivoli's ability to connect to the server. Therefore, it does not ensure the connection and availability to all users over all configured access paths. MONITOR NUMBER 35 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer, SybaseBackupServer, SybaseMonitorServer GUI DATA ENTRY FIELDS None Version 1.1

173 SQL Server Status CLI SYNTAX SQLServerStatus CLI EXAMPLE waddmon SybaseServer SQLServerStatus -t 15 minutes -c critical -R == SUSPECT -p Root_pip-region -c severe -c warning \ -R == SHUTDOWN -p Root_pip-region -c normal -c always -f pip:/data/sybase/monitor_logs/sql_server_status.log <profile name> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels cause a critical response when the server is in a suspect state, and cause a warning response the first time the monitor detects that the server has been shut down by an administrator. The SybaseServer Monitoring Collection Severity Trigger When Default Action Critical Is Suspect Send Sybase Sentry Notice. Severe Not applicable None Warning Becomes Shutdown Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 15 minutes Tivoli Manager for Sybase Reference Guide 2 155

174 SQL Server Status OUTPUT The following is an example output from the SQL Server Status monitor: The trigger value returned by the monitor is one of the states listed in the table on page #TRIGGER_INFO=(none) means there is no trigger information. No row results follow #TRIGGER_INFO=. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES With regard to the four becomes states listed in the table on page (Becomes Available, Becomes Suspect, Becomes Shutdown, and Becomes Unavailable), the first time the monitor is run none of these states can be returned because there was no previous monitor return value to compare to the current value Version 1.1

175 SQL Server Status In addition, none of the becomes states can be returned twice in succession; in other words, if one of these states is returned by the monitor, then it cannot be returned the next time the monitor is run. SEE ALSO The following SybaseServer monitors: Backup Server Errors, Dataserver Errors, and Dataserver Errors By Severity The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 157

176 Stopped Processes Stopped Processes DESCRIPTION This monitor returns the number of processes with a current status of stopped in the sysprocesses system table. A stopped status generally occurs when a client process is terminated while the server believes the process still exists. If a process remains in a stopped state for any length of time, the client and Adaptive Server should be investigated and, possibly, the kill command should be applied to the process ID (spid) of the stopped process. MONITOR NUMBER 36 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None CLI SYNTAX StoppedProcesses CLI EXAMPLE waddmon SybaseServer StoppedProcesses -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/stopped_processes.log <profilename> Version 1.1

177 SUGGESTED RESPONSE LEVELS Stopped Processes The following table shows suggested threshold values for severity levels. For details, refer to the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Not applicable None Severe Not applicable None Warning Greater than 0 Send Sybase Sentry Notice. Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 159

178 Stopped Processes OUTPUT The following is an example output from the Stopped Processes monitor: The trigger value returned by the monitor is the number of processes found to be stopped. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which are the trigger value, process ID (spid), and associated program name repeated for each stopped process (or as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES If a process is marked as stopped, the Sybase Adaptive Server upon detecting it, usually internally issues a kill command, which removes the process from the sysprocesses system table. Therefore, it is unusual for a process to remain in the stopped state for any length of time Version 1.1

179 Stopped Processes SEE ALSO None The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 161

180 User CPU Busy User CPU Busy DESCRIPTION This monitor analyzes the amount of CPU time used by each user connected to the server. For the user who used the most CPU time, the monitor returns the CPU time as a percentage of the server s time since startup (averaged across all the currently configured engines). The monitor s output also includes all the other CPU times with their associated user IDs. Consider the example of a user who has used one minute of CPU time, the server has been up for 50 minutes, and two engines are configured. The user actually had 100 minutes of CPU time available because there are two engines, with two CPUs. Therefore, since the user has used 1% of the available CPU time (one minute out of 100 minutes available), the monitor returns the value of one. This monitor allows you to track the percentage of CPU time each user is taking, enabling you to identify those who are dominating the CPU. If these users are affecting the system s performance, then the solution might be to reschedule their work to off-peak times. Only users connected to the server are considered by this monitor system processes with a set user ID (suid) value of zero are ignored. MONITOR NUMBER 42 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDataServer GUI DATA ENTRY FIELDS None Version 1.1

181 User CPU Busy CLI SYNTAX UserCPUBusy CLI EXAMPLE waddmon SybaseServer UserCPUBusy -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/user_cpu_busy.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be specified on an individual site basis. Suggested monitoring schedule: 30 minutes The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 163

182 User CPU Busy OUTPUT The following is an example output from the User CPU Busy monitor: The trigger value returned by the monitor is the percentage of CPU time. The trigger information (#TRIGGER_INFO=) is SUID= x, where x is the ID of the user who has used the most CPU time. Below #TRIGGER_INFO= are row results, which include the user ID and percentage of CPU time used by that user for each user connected to the server (or as many as will fit within the 1000-character restriction on the output s length). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor returns the percentage of CPU time used by the process since the server started, not since the process started Version 1.1

183 User CPU Busy If the process and server started at approximately the same time, the process had the opportunity to use the CPU for approximately the whole time the server was up, so the percentage returned by the monitor tells you what percent of the CPU time the process actually used. If the process started significantly after the server, obviously the process could not use the CPU before the process itself started, so the percent returned by the monitor for that process will be relatively small. To track the CPU usage of later starting processes, compare the current monitor output values for the process with previous output values, and track the rate of change. Alternatively, you can use the CPU By Process monitor to track these processes. SEE ALSO The following SybaseServer monitors: CPU By Process and Engine CPU Busy The SybaseServer Monitoring Collection Tivoli Manager for Sybase Reference Guide 2 165

184 User CPU Busy Version 1.1

185 3 3The SybaseDatabase Monitoring Collection The SybaseDatabase monitoring collection provides a range of monitoring sources for using Tivoli Manager for Sybase to manage distributed Sybase Adaptive Server computing resources effectively. Each monitoring source enables you to manage a different aspect of a Sybase Adaptive Server database, such as database status and transaction log space. You can also use the Free Form SQL Numeric and Free Form SQL String user-defined monitors to create your own Sybase Adaptive Server monitoring sources. For database-specific monitoring, you can distribute a profile containing SybaseDatabase monitors to a SybaseDatabase endpoint. For server-specific monitoring, use this collection in conjunction with the SybaseServer monitoring collection, described in Chapter 2, The SybaseServer Monitoring Collection. Using monitors from both collections enables you to achieve the required range and granularity of monitoring. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 1

186 List of SybaseDatabase Monitoring Sources by GUI and CLI Names List of SybaseDatabase Monitoring Sources by GUI and CLI Names The following table lists the SybaseDatabase monitoring sources by both their GUI and CLI names. DataBase State GUI Name Free Form SQL Numeric Free Form SQL String Free Segment Space by Segment Percent Free Segment Space Percent Transaction Log Space Used Transaction Log Free Space Used Segment Space by Segment CLI Name DataBaseState FreeFormSQLNumeric FreeFormSQLString FreeSegmentSpaceBySegment PercentFreeSegmentSpace PercentTransactionLogSpaceUsed TransactionLogFreeSpace UsedSegmentSpaceBySegment 3 2 Version 1.1

187 Database State Database State DESCRIPTION This monitor checks the status of the target database and reflects a summary of the database states on the desktop icons. The Database State monitor is designed for use on mission-critical databases that require frequent availability and status checking. The monitor returns one of the states listed in the following table. The CLI name of the state is used when setting up the monitor, using the command line rather than the Tivoli desktop. See CLI EXAMPLE on page 3-6. State Description CLI Name DataServer Is Unavailable The Sybase Adaptive Server in which the database is held is unavailable (that is, shut down or suspect). == DATABASE_ DS_UNAVAILABLE Is Suspect Database suspect; not recovered; cannot be opened or used; can be dropped only with dbcc or dbrepair. == DATABASE_ SUSPECT Is Offline Database is offline. == DATABASE_ OFFLINE Is Read Only Inserts, deletes, and updates are not permitted on the database. Users can set this with sp_dboption. == DATABASE_ READ_ONLY The SybaseDatabase Monitoring Collection Is Single User Only one user can connect to the database. Users can set this with sp_dboption. == DATABASE_ SINGLE_USER Tivoli Manager for Sybase Reference Guide 3 3

188 Database State State Description CLI Name Is DBO Use Only Is Normal Is Not Normal Becomes DataServer Unavailable Becomes Suspect Becomes Offline Only the database owner can access the database. Users can set this with sp_dboption. The database is not in any of the above states (not Is Single User, Is Suspect, Is Offline, Is Read Only, Is DBO Use Only, or Dataserver Is Unavailable). The database is not online and is in one of the following states: Is Suspect, Is Offline, Is Read Only, Is Single User, Is DBO Use Only, or Dataserver Is Unavailable The monitor returns DataServer Is Unavailable, but when it was previously run, it returned a different state. The monitor returns Is Suspect, but when it was previously run, it returned a different state. The monitor returns Is Offline, but when it was previously run, it returned a different state. == DATABASE_ DBO_USER_ONLY == DATABASE_ ONLINE!= DATABASE_ ONLINE -> DATABASE_ DS_UNAVAILABLE -> DATABASE_ SUSPECT -> DATABASE_ OFFLINE 3 4 Version 1.1

189 Database State State Description CLI Name Becomes Read Only Becomes Single User Becomes DBO Use Only Becomes Normal The monitor returns Is Read Only, but when it was previously run, it returned a different state. The monitor returns Is Single User, but when it was previously run, it returned a different state. The monitor returns Is DBO Use Only, but when it was previously run, it returned a different state. The monitor returns Is Normal, but when it was previously run, it returned a different state. -> DATABASE_ READ_ONLY -> DATABASE_ SINGLE_USER -> DATABASE_ DBO_USER_ONLY -> DATABASE_ ONLINE Becomes Not Normal Notes: The monitor returns Is Not Normal, but when it was previously run, it returned Is Normal. -< DATABASE_ ONLINE The state of the database is determined in the same order as the states in the previous table, with the highest priority first. Consequently, if a database is both read only and in single-user mode, the monitor returns Is Read Only. These states are identical to those described for the SybaseDatabase endpoint in Chapter 6, Using Tivoli Manager for Sybase, in the Tivoli Manager for Sybase User s Guide. The SybaseDatabase Monitoring Collection MONITOR NUMBER 49 Tivoli Manager for Sybase Reference Guide 3 5

190 Database State AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase GUI DATA ENTRY FIELDS None CLI SYNTAX DatabaseState CLI EXAMPLE waddmon SybaseDatabase DatabaseState -t 20 minutes -c critical -R == DATABASE_SUSPECT -p Root_pip-region -c severe -c warning -R == DATABASE_OFFLINE -p Root_pip-region -c normal -c always -f pip:/data/sybase/monitor_logs/database_state.log Availability SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. See the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. The following suggested response levels send a critical response if the target database is found to be suspect, and a warning if the database is found to be offline. 3 6 Version 1.1

191 Database State Severity Trigger When Default Action Critical Is Suspect Send Sybase Sentry Notice Severe Not applicable None Warning Is Offline Send Sybase Sentry Notice Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes OUTPUT The following is an example output from the Database State monitor: The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 7

192 Database State The trigger value returned by the monitor is one of the database states listed in the table on page 3-3. Note that the monitor will return the state name as listed in the CLI Name column of that table, not the State column. #TRIGGER_INFO=(none) means there is no trigger information. There are no row results below #TRIGGER_INFO= for this monitor. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor allows monitoring of the states of the SybaseDatabase icon on the Tivoli desktop. If additional states of the database require monitoring (such as DDL in tran), use the Database Status monitor, which allows further states of a database to be monitored. With regard to the eight becomes states listed in the table on page 3-3 (Becomes DataServer Unavailable, Becomes Suspect, Becomes Offline, Becomes Read Only, Becomes Single User, Becomes DBO Use Only, Becomes Normal, and Becomes Not Normal), the first time the monitor is run none of these states can be returned because there was no previous monitor value to compare against. In addition, none of the becomes states can be returned twice in succession; in other words, if one of these states is returned by the monitor, then it cannot be returned the next time the monitor is run. It is probably not necessary to set up this monitor to detect the DataServer Is Unavailable state if the SQL Server Status monitor is distributed to the Sybase Adaptive Server which holds the database you wish to monitor. SEE ALSO The following SybaseServer monitor: Database Status 3 8 Version 1.1

193 Free Form SQL Numeric Free Form SQL Numeric DESCRIPTION You can use this monitor to define a monitor that meets your site s specific needs. This monitor runs a user-defined TRANSACT-SQL select statement that returns a numeric value. You can define multiple monitors and run them concurrently using the Free Form SQL Numeric monitor. The only limitation on the number of monitors you can create is your system resources. MONITOR NUMBER 44 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free Form SQL Numeric monitor. Descriptions of the monitor arguments follow. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 9

194 Free Form SQL Numeric SQL Statement Specifies the selection and calculation criteria in the TRANSACT-SQL syntax for the monitor. Column number of return value Specifies the column number in the first row returned that contains the monitor value. This is zero-based. Default value (if no rows found) Specifies the default value to be returned if no rows are returned from the SQL select statement. Positive or negative integers, or zero, are acceptable input values Version 1.1

195 CLI SYNTAX Free Form SQL Numeric FreeFormSQLNumeric a <SQL_selectstatement> a <column> a <default> where: a <SQL_selectstatement> Specifies the selection and calculation criteria in the TRANSACT-SQL syntax for the monitor. a <column> Specifies the column number in the first row returned that contains the monitor value. This is zero-based. a <default> Specifies the value to be returned if no rows are returned from the SQL select statement. Positive or negative integers, or zero, are acceptable input values. CLI EXAMPLE The following example checks the number of users of the database to which the monitor is distributed. waddmon SybaseDatabase FreeFormSQLNumeric -a select count(*) from!target!.dbo.sysusers -a 0 -a -1 -t 30 minutes -c critical -R == -1 -p steven, Root_pip-region -n Sybase Sentry -c severe -c warning -R > 100 -f pip:/database/sybase/logs/freeform_numeric.log -c normal -c always "<profilename>" In this example, the first column on the first row returned by the SQL select query is the monitor value. The monitor is set to run every 30 minutes. When the monitor value is returned, if the number is 100 or less, there are no problems. When the number is more than 100, it triggers a warning response level and logs the monitor output to the file /database/sybase/logs/freeform_numeric.log. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 11

196 Free Form SQL Numeric If no value is returned by the SQL query, the monitor value defaults to -1. This triggers a critical response level and sends a pop-up window to the user steven and the root administrators group. It also sends a notice to the Sybase Sentry notice group. No severe, normal, or always response level is set. SUGGESTED RESPONSE LEVELS No response levels are suggested because they are dependent upon the select statement used. Suggested monitoring schedule: None suggested. OUTPUT The following is an example output from the Free Form SQL Numeric monitor: The trigger value returned by the monitor is the specified column of the first row returned. #TRIGGER_INFO=(none) means there is no trigger information Version 1.1

197 Free Form SQL Numeric Below #TRIGGER_INFO= are row results, which give all of the output of the SQL select statement passed as an argument to the monitor (that is, all the rows and columns returned by the statement). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES You can use the Free Form SQL Numeric monitor to define a SQL select statement (using the TRANSACT-SQL syntax) as the basis of a monitor. Do not terminate the SQL statement with a semicolon (;) or forward slash (/). The select statement can return multiple columns and multiple rows. The monitor value (the value against which the monitoring criteria is evaluated) must be a numeric value in one of the columns in the first row returned by the select statement. The Column number of return value defines which column in the first row contains the monitor value (zero-based). A SQL select statement might return no rows. By default, Tivoli Manager for Sybase treats this as an error. However, you can override this default behavior by providing a Default value (if no rows found) value; in which case, the monitor returns the value specified. The SQL select statement you provide to the monitor will be executed on the master database unless you specify otherwise. To qualify an object name based upon the target database name, use the reserved keyword!target!. The exclamation marks are required; see CLI EXAMPLE on page For example, select count(*) from sysusers uses the table master.dbo.sysusers, whereas select count(*) from!target!.dbo.sysusers uses the sysusers table in the target database (that is, the database to which the monitor is distributed). The SybaseDatabase Monitoring Collection SEE ALSO The SybaseDatabase monitor Free Form SQL String, and SybaseSever monitors Free Form SQL Numeric and Free Form SQL String Tivoli Manager for Sybase Reference Guide 3 13

198 Free Form SQL String Free Form SQL String DESCRIPTION You can use this monitor to define a monitor that meets your site s specific needs. This monitor runs a user-defined TRANSACT-SQL select statement that returns a string value. You can define multiple monitors and run them concurrently using the Free Form SQL String monitor. The only limitation on the number of monitors you can create is your system resources. MONITOR NUMBER 45 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free Form SQL String monitor. Descriptions of the monitor arguments follow Version 1.1

199 Free Form SQL String SQL Statement Specifies the selection and calculation criteria in the TRANSACT-SQL syntax for the monitor. Column number of return value Specifies the column number in the first row returned that contains the monitor value. This is zero-based. Default value (if no rows found) Specifies the default value to be returned if no rows are returned from the SQL select statement. Any text string is an acceptable input. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 15

200 Free Form SQL String CLI SYNTAX FreeFormSQLString a <SQL_selectstatement> a <column> a <default> where: a <SQL_selectstatement> Specifies the selection and calculation criteria in the TRANSACT-SQL syntax for the monitor. a <column> Specifies the column number (zero-based), which is to contain the trigger value for the monitor, within the first row returned. a <default> Specifies the value to be returned if no rows are returned from the SQL statement. Any text string is an acceptable input. CLI EXAMPLE The following example creates a monitor that checks whether the target database has a guest user or not. waddmon SybaseDatabase FreeFormSQLString -a select * from!target!.dbo.sysusers where name= guest -a 3 -a no_guest -t 30 minutes -c critical -c severe -c warning -R == guest -f pip:/data/sybase/logs/freeform_string.log -c normal -c always <profilename> In this example, the fourth column on the first row returned by the SQL select query is the monitor value. The monitor is set to run every 30 minutes. In this example, the monitor returns the name guest, if guest is a user of the database; otherwise, the monitor returns no_guest Version 1.1

201 Free Form SQL String If the monitor returns the name guest, it triggers a warning response level and logs the monitor output to the file /data/sybase/logs/freeform_string.log. No critical, severe, normal, or always response levels are set. In the rows result section of the monitor output, all the rows returned by the select statement will be printed (that is, all the columns of the sysusers table with a name equal to guest). SUGGESTED RESPONSE LEVELS No response levels are suggested because they are dependent upon the select statement used. Suggested monitoring schedule: None suggested. OUTPUT The following is an example output from the Free Form SQL String monitor: The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 17

202 Free Form SQL String The trigger value returned by the monitor is the specified column of the first row returned. #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which give all of the output of the SQL select statement passed as an argument to the monitor (that is, all the rows and columns returned by the statement). For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES You can use the Free Form SQL String monitor to define a SQL select statement (using the TRANSACT-SQL syntax) as the basis of a monitor. Do not terminate the SQL statement with a semicolon (;) or forward slash (/). The select statement can return multiple columns and multiple rows. The monitor value (the value against which the monitoring criteria is evaluated) must be a string value in one of the columns in the first row returned by the select statement. The Column number of return value defines which column in the first row contains the monitor value (zero-based). A SQL select statement might return no rows. By default, Tivoli Manager for Sybase treats this as an error. However, you can override this default behavior by providing a Default value (if no rows found) value; in which case, the monitor returns the value specified. The SQL select statement you provide to the monitor will be executed on the master database unless you specify otherwise. To qualify an object name based upon the target database name, use the reserved keyword!target!. The exclamation marks are required; see CLI EXAMPLE on page For example, select name from sysusers uses the table master.dbo.sysusers, whereas select name from!target!.dbo.sysusers uses the sysusers table in the target database (that is, the database to which the monitor is distributed) Version 1.1

203 SEE ALSO Free Form SQL String The SybaseDatabase monitor Free Form SQL Numeric, and the SybaseServer monitors Free Form SQL Numeric and Free Form SQL String The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 19

204 Free Segment Space By Segment Free Segment Space By Segment DESCRIPTION This monitor checks the space currently used by data and by indexes in a user-specified segment on the target database and returns the total unused space, in kilobytes (KB). Space allocated to data or indexes, but as yet not used, is included in the total of free space returned by the monitor. In other words, this monitor reports the space that is available for expansion on the specified segment. For example, if the segment size is KB, and 1024 KB is currently in use by indexes and 5120 KB is currently in use by data, then the monitor returns 4096 KB, regardless of whether any of this free space is part of an allocated extent. You can use this monitor to track the free space on a segment or to monitor its usage. If space is becoming low, consider extending the segment with the system-stored procedure sp_extendsegment, using the alter database option to automatically extend segments, or adding new segments. MONITOR NUMBER 46 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase 3 20 Version 1.1

205 GUI DATA ENTRY FIELDS Free Segment Space By Segment The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free Segment Space By Segment monitor. Descriptions of the monitor arguments follow. Segment Name The name of the segment to be checked by the monitor. The default value for this argument is default, which is the segment on which all objects (other than system tables and the transaction log) are placed, unless they are explicitly placed elsewhere. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 21

206 Free Segment Space By Segment CLI SYNTAX FreeSegmentSpaceBySegment a <segment name> where: a <segment name> Specifies the segment to check. CLI EXAMPLE waddmon SybaseDatabase FreeSegmentSpaceBySegment -a default -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/free_segment_space.log "<profilename>" SUGGESTED RESPONSE LEVELS No response levels are suggested because they are dependent upon the customer s environment. Suggested monitoring schedule: 30 minutes 3 22 Version 1.1

207 OUTPUT Free Segment Space By Segment The following is an example output from the Free Segment Space By Segment monitor: The trigger value returned by the monitor is the unused space on the segment, in KB. The trigger information (#TRIGGER_INFO=) includes SIZE= x DATA= y INDEX= z, where x is the size of the segment, y is the amount of data currently on the segment, and z is the amount of space currently being used by indexes on the segment, all in KB. Below #TRIGGER_INFO= are row results, which repeat the numbers x, y, and z. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 23

208 Free Segment Space By Segment USAGE NOTES You can set up this monitor to check either a user-defined segment or a system-defined segment. To monitor a system-defined segment, enter default, system, or logsegment as an argument to the monitor. This allows the monitor to be meaningfully distributed to any database. However, if a specific segment name is passed as an argument to the monitor, it has relevance only on a database with a segment of that name. If the monitor is distributed to a database with no segment of that name, then the monitor will always return zero. This monitor checks only one segment. If you need to check all segments of a database, consider using the Percent Free Segment Space monitor. When calculating the used space on a segment, the monitor uses the segment column of the sysindexes table to determine which objects are on the segment. So, if you enter a segment name that references the same device as another segment, the monitor considers only those objects assigned to the segment you entered. For example, suppose a default segment is mapped to device dev1 and a user-defined segment seg1 is also mapped to device dev1. If you input seg1 to the monitor, it will consider the space occupied by only those objects assigned to seg1. Any objects assigned to default will not be considered, regardless of whether they are on device dev1. In other words, if a segment shares devices with other segments, then that segment s free space reported by the monitor might not represent the free space on the devices associated with that segment. Objects might have been placed on the other segments sharing those devices, and those objects might be occupying space on a device associated with the first segment. If a segment does not share a device with another segment, then that segment s free space reported by the monitor represents the free space on the devices associated with the segment. SEE ALSO The following SybaseDatabase monitors: Percent Free Segment Space and Used Segment Space By Segment 3 24 Version 1.1

209 Percent Free Segment Space Percent Free Segment Space DESCRIPTION This monitor checks the space currently used by data and by indexes on all the segments defined for the target database. It then calculates the total unused space as a percentage of the segment s total size for each segment. The monitor returns the smallest percentage of free segment space found. When determining the total free space on a segment, the space allocated but not used is counted as free space. The rest of this monitor s output lists the percentage of free segment space for all the other segments. For example, if the segment size is KB, and 1024 KB is currently in use by indexes and 5120 KB is currently in use by data, then the segment has 40% free space (regardless of whether any of this space is allocated). The monitor will return a value of 40% if no lower percentage is found for another segment. You can use this monitor to track the free space on all the segments of a database. If space is becoming low on a segment, consider extending the segment with the system-stored procedure sp_extendsegment, using the alter database option to automatically extend segments, or adding new segments. MONITOR NUMBER 48 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase The SybaseDatabase Monitoring Collection GUI DATA ENTRY FIELDS None Tivoli Manager for Sybase Reference Guide 3 25

210 Percent Free Segment Space CLI SYNTAX PercentFreeSegmentSpace CLI EXAMPLE waddmon SybaseDatabase PercentFreeSegmentSpace -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/percent_free_segment_space.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. See the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Less than 10% Send Sybase Sentry Notice Severe Less than 20% Send Sybase Sentry Notice Warning Less than 30% Send Sybase Sentry Notice Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 30 minutes 3 26 Version 1.1

211 OUTPUT The following is an example output from this monitor: Percent Free Segment Space The trigger value returned by the monitor is the lowest percentage of free space found on a segment at the target database. The trigger information (#TRIGGER_INFO=) includes SEGMENT_NAME=segment SIZE= x USED= y, where segment is the name of the segment with the least free space, x is the size of the segment, in kilobytes (KB), and y is the amount of space (in KB) currently used by data and indexes. Allocated space that is unused is considered free space. Below #TRIGGER_INFO= are row results, which list the percent free space, segment name, size of the segment (in KB), and the space used by data and indexes (in KB) for every segment of the database (or as much as will fit within the 1000-character restriction on the output s length). The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 27

212 Percent Free Segment Space For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES This monitor checks the free space on all the segments of the database. If only one segment is of interest, consider using either the Used Segment Space By Segment or the Free Segment Space By Segment monitor. When calculating the used space on a segment, the monitor uses the segment column of the sysindexes table to determine which objects are on the segment. So, if you input a segment name that references the same device as another segment, the monitor considers only those objects assigned to the input segment. For example, suppose a default segment is mapped to device dev1 and a user-defined segment seg1 is also mapped to device dev1. If you input seg1 to the monitor, it will only consider the space occupied by those objects assigned to seg1. Any objects assigned to default will not be considered, regardless of whether they are on device dev1. In other words, if a segment shares devices with other segments, then that segment s free space reported by the monitor might not represent the free space on the devices associated with the segment. Objects might have been placed on the other segments sharing those devices, and those objects might be occupying space on a device associated with the first segment. If a segment does not share a device with another segment, then that segment s free space reported by the monitor represents the free space on the devices associated with the segment. SEE ALSO The following SybaseDatabase monitors: Free Segment Space By Segment and Used Segment Space By Segment 3 28 Version 1.1

213 Percent Transaction Log Space Used DESCRIPTION Percent Transaction Log Space Used This monitor determines the total space available for the transaction log of the target database, and reports the percentage currently used by that log. The monitor s output also includes the space used in the log and the log size. For example, if a database has KB of disk space available that is permitted to have log information (that is, sp_helpdb dbname lists this space as being log only or data and log) and the transaction log currently contains 4096 KB of information, then this monitor returns a value of 40% (meaning the log is 40% used). You can use this monitor to alert you to transaction logs that are dangerously close to running out of space. Such an event would suspend the database s operations until the log is dumped. Additionally, you can use this monitor to help you determine the optimum log size, select the optimum thresholds for the log, or schedule timing of transaction log dumps. MONITOR NUMBER 47 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase GUI DATA ENTRY FIELDS None The SybaseDatabase Monitoring Collection CLI SYNTAX PercentTransactionLogSpaceUsed Tivoli Manager for Sybase Reference Guide 3 29

214 Percent Transaction Log Space Used CLI EXAMPLE waddmon SybaseDatabase PercentTransactionLogSpaceUsed -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/percent_trans_log_used.log <profilename> SUGGESTED RESPONSE LEVELS The following table shows suggested threshold values for severity levels. See the Specifying Response Levels section in Chapter 5, Setting Up Monitoring Profiles, in the Tivoli Manager for Sybase User s Guide. Severity Trigger When Default Action Critical Greater than 85% Send Sybase Sentry Notice Severe Greater than 75% Send Sybase Sentry Notice Warning Greater than 65% Send Sybase Sentry Notice Normal Not applicable None Always Not applicable None Suggested monitoring schedule: 20 minutes 3 30 Version 1.1

215 OUTPUT Percent Transaction Log Space Used The following is an example output from the Percent Transaction Log Space Used monitor: The trigger value returned by the monitor is the percentage of log space used. The trigger information (#TRIGGER_INFO=) includes LOGRESERVED= x LOGSIZE= y, where x is the space currently used by the transaction log, and y is the total space available for this log. Below #TRIGGER_INFO= are row results, which repeat the numbers x and y. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 31

216 Percent Transaction Log Space Used USAGE NOTES A high usage figure returned by the monitor is not necessarily a cause for alarm. If the database is static, the space remaining for log expansion might be adequate. However, a volatile database with only a small amount of room for log expansion might soon run out of space. To monitor the transaction logs of all the databases on the server, consider using the Percent Transaction Log Space Used monitor defined in Chapter 2, The SybaseServer Monitoring Collection, which has the Sybase Adaptive Server as the target. SEE ALSO The SybaseDatabase monitor Transaction Log Space Used, and the SybaseServer monitor Percent Transaction Log Space Used 3 32 Version 1.1

217 Transaction Log Free Space Transaction Log Free Space DESCRIPTION This monitor determines the total space available for the transaction log of the target database, and reports the space, in kilobytes (KB), currently not used but available for that log. For example, if a database has KB of disk space available that is permitted to have log information (that is, sp_helpdb dbname lists this space as being log only or data and log) and the transaction log currently contains 4096 KB of information, then this monitor returns 6144 KB as the amount of log space free. You can use this monitor to alert you to transaction logs that are dangerously close to running out of space. Such an event would suspend the database s operations until the log is dumped. Additionally, you can use this monitor to help you determine the optimum log size, select the optimum thresholds for the log, or schedule timing of transaction log dumps. MONITOR NUMBER 50 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase GUI DATA ENTRY FIELDS None The SybaseDatabase Monitoring Collection CLI SYNTAX TransactionLogFreeSpace Tivoli Manager for Sybase Reference Guide 3 33

218 Transaction Log Free Space CLI EXAMPLE waddmon SybaseDatabase TransactionLogFreeSpace -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/transaction_log_free_space.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be set up on an individual site basis. Suggested monitoring schedule: 20 minutes OUTPUT The following is an example output from the Transaction Log Free Space monitor: The trigger value returned by the monitor is the space (in KB) available for log expansion Version 1.1

219 Transaction Log Free Space #TRIGGER_INFO=(none) means there is no trigger information. Below #TRIGGER_INFO= are row results, which repeat the trigger value. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. USAGE NOTES A low free-space figure returned by the monitor is not necessarily a cause for alarm. If the database is static, this space might be adequate. However, a volatile database with only a small amount of room for log expansion might soon run out of space. To monitor the transaction logs of all the databases on the server, consider using the SybaseServer monitor Percent Transaction Log Space Used. SEE ALSO The SybaseDatabase monitor Percent Transaction Log Space Used, and the SybaseServer monitor Percent Transaction Log Space Used The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 35

220 Used Segment Space By Segment Used Segment Space By Segment DESCRIPTION This monitor checks the space currently used by data and by indexes in a user-specified segment on the target database, and returns the total used space, in kilobytes (KB). The space allocated but not used is considered free space and not included in the total returned by the monitor. For example, if the segment size is KB, and 1024 KB is currently in use by indexes and 5120 KB is currently in use by data, then the monitor returns 6144 KB (regardless of whether the remaining 4096 KB is part of an allocated extent). You can use this monitor to track the space used on a specified segment of the database and the growth rate of data. If space is becoming low on a segment, consider either extending the segment with the system-stored procedure sp_extendsegment, using the alter database option to automatically extend segments, or adding new segments. MONITOR NUMBER 51 AUTHORIZATION ROLE sybase_monitor TARGET ENDPOINT SybaseDatabase GUI DATA ENTRY FIELDS The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Used Segment Space By Segment monitor. Descriptions of the monitor arguments follow Version 1.1

221 Used Segment Space By Segment Segment Name Specifies the name of the segment to be checked by the monitor. The default value for this field is default, which is the segment on which all objects (other than system tables and the transaction log) are placed, unless they are explicitly placed elsewhere. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 37

222 Used Segment Space By Segment CLI SYNTAX UsedSegmentSpaceBySegment a <segment name> where: a <segment name> Specifies the segment to check. CLI EXAMPLE waddmon SybaseDatabase UsedSegmentSpaceBySegment -a default -t 1 minutes -c critical -c severe -c warning -c normal -c always -f pip:/data/sybase/logs/used_segment_space.log <profilename> SUGGESTED RESPONSE LEVELS No response levels are suggested because they must be set up on an individual site basis. Suggested monitoring schedule: 30 minutes 3 38 Version 1.1

223 OUTPUT Used Segment Space By Segment The following is an example output from the Used Segment Space By Segment monitor: The trigger value returned by the monitor is the space used on the segment (in KB). The trigger information (#TRIGGER_INFO=) includes DATA= x INDEX= y, where x is the space currently used by data, and y is the space currently used by indexes (both in KB). Below #TRIGGER_INFO= are row results, which repeat the numbers x and y. For a general description of the monitor output, see Understanding the Monitor Output on page 1-4. The SybaseDatabase Monitoring Collection Tivoli Manager for Sybase Reference Guide 3 39