Tivoli Monitoring for Databases: Sybase Server Agent


Version 6.1.0

User’s Guide

SC32-9451-00
 Tivoli Monitoring for Databases: Sybase Server Agent
®


Version 6.1.0

User’s Guide

SC32-9451-00
 Note
Before using this information and the product it supports, read the information in Appendix E, “Notices,” on page 147.

First Edition (November 2005)

This edition applies to version 6.1 of IBM Tivoli Monitoring for Databases: Sybase Server Agent (product number
5724-B96) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v About workspaces . . . . . . . . . . . . 21
More information about workspaces . . . . . . 21
About this guide . . . . . . . . . . vii Predefined workspaces . . . . . . . . . . 21
Cache Usage workspace . . . . . . . . . 22
Who should read this guide . . . . . . . . . vii
Databases workspace . . . . . . . . . . 22
What this guide contains . . . . . . . . . . vii
Device Usage workspace . . . . . . . . . 23
Publications . . . . . . . . . . . . . . viii
Engine Summary workspace. . . . . . . . 24
Prerequisite publications . . . . . . . . . viii
Enterprise Database Summary workspace . . . 24
Related publications . . . . . . . . . . viii
Enterprise Errorlog Alerts workspace . . . . . 25
Accessing terminology online . . . . . . . ix
Enterprise Locking Summary workspace . . . 25
Accessing publications online . . . . . . . ix
Enterprise Processes Summary workspace . . . 26
Ordering publications . . . . . . . . . . ix
Enterprise Server Statistics workspace . . . . 26
Accessibility . . . . . . . . . . . . . . ix
Enterprise Server Summary workspace . . . . 26
Tivoli technical training . . . . . . . . . . . x
Enterprise Sybase Summary workspace . . . . 27
Support information . . . . . . . . . . . . x
Errorlog Alerts workspace . . . . . . . . 27
Conventions used in this guide . . . . . . . . x
Lock Information workspace . . . . . . . 28
Typeface conventions . . . . . . . . . . x
Lock Usage workspace . . . . . . . . . 28
Operating system-dependent variables and paths x
Log and Space Information workspace . . . . 29
Log Usage workspace . . . . . . . . . . 29
Chapter 1. Overview of the Monitoring Process Holding Lock workspace . . . . . . 30
Agent for Sybase Server . . . . . . . 1 Process SQL Text workspace . . . . . . . . 30
IBM Tivoli Monitoring overview . . . . . . . . 1 Processes workspace table view . . . . . . 31
Features of Monitoring Agent for Sybase Server . . 1 Server Configuration workspace . . . . . . 31
Components of Monitoring Agent for Sybase Server 2 Server Statistics Summary workspace . . . . . 32
User interface options . . . . . . . . . . . 2 Servers workspace . . . . . . . . . . . 32
SQL Text workspace . . . . . . . . . . 33
Chapter 2. Requirements and Sybase Server_ID workspace . . . . . . . 33
configuration for the monitoring agent . 5
Requirements for the monitoring agent . . . . . 5 Chapter 5. Attributes reference . . . . 35
Configuring on your local system from the Manage About attributes . . . . . . . . . . . . . 35
Tivoli Enterprise Monitoring Services window . . . 6 More information about attributes . . . . . . . 35
Configuring on your local system using the tacmd Attribute groups and attributes for the Monitoring
command line . . . . . . . . . . . . . . 7 Agent for Sybase Server . . . . . . . . . . 36
Deploying the monitoring agent remotely from the Cache Detail attributes . . . . . . . . . 36
Tivoli Enterprise Portal . . . . . . . . . . . 7 Cache Summary attributes . . . . . . . . 40
Deploying the monitoring agent using the tacmd Configuration attributes . . . . . . . . . 44
command line . . . . . . . . . . . . . . 8 Database Detail attributes . . . . . . . . 45
Granting permission on the Monitoring Agent for Database Summary attributes . . . . . . . 48
Sybase Server . . . . . . . . . . . . . . 9 Device Detail attributes . . . . . . . . . 49
Configuring the agent to your installed databases Engine Detail Attributes . . . . . . . . . 51
and verifying installation on UNIX . . . . . . 10 Engine Summary attributes . . . . . . . . 53
Configuring the UTF-8 character set . . . . . . 12 Lock Conflict Detail attributes . . . . . . . 54
Enabling unicode conversions . . . . . . . . 13 Lock Conflict Summary attributes . . . . . . 55
Lock Detail attributes . . . . . . . . . . 55
Chapter 3. How to use the Monitoring Lock Summary attributes . . . . . . . . . 57
Locks attributes . . . . . . . . . . . . 59
Agent for Sybase Server . . . . . . . 15
Log Detail attributes . . . . . . . . . . 61
View real-time data about Sybase Server. . . . . 15
Log Summary attributes . . . . . . . . . 62
Investigate an event . . . . . . . . . . . 16
Physical Device Detail attributes . . . . . . 62
Recover the operation of a resource . . . . . . 16
Problem Detail attributes . . . . . . . . . 65
Customize your monitoring environment . . . . 17
Problem Summary attributes . . . . . . . 66
Monitor with custom situations that meet your
Process Detail attributes . . . . . . . . . 67
requirements . . . . . . . . . . . . . . 18
Process Summary attributes . . . . . . . . 70
Collect and view historical data . . . . . . . 19
Remote Servers attributes . . . . . . . . . 71
Server Detail attributes . . . . . . . . . 72
Chapter 4. Workspaces reference . . . 21
© Copyright IBM Corp. 2005 iii
 Server Enterprise attributes . . . . . . . . 73 About Take Action commands . . . . . . . . 91
Server Summary attributes . . . . . . . . 74 More information about Take Action commands . . 91
SQL Detail attributes . . . . . . . . . . 75 Predefined Take Action commands . . . . . . 91
Statistics Detail attributes . . . . . . . . . 75
Statistics Summary attributes . . . . . . . 76 Chapter 8. Policies reference . . . . . 93
Task Detail attributes . . . . . . . . . . 78 About policies . . . . . . . . . . . . . 93
Text attributes . . . . . . . . . . . . 78 More information about policies . . . . . . . 93
Disk capacity planning for historical data . . . . 79 Predefined policies . . . . . . . . . . . . 93

Chapter 6. Situations reference . . . . 83 Appendix A. Workspaces workgroups

About situations . . . . . . . . . . . . . 83 mapped to tasks . . . . . . . . . . 95
More information about situations . . . . . . . 83
Predefined situations . . . . . . . . . . . 84
Sybase_Collection_Stat_Warning situation . . . 84 Appendix B. IBM Tivoli Enterprise
Sybase_DB_Error_Status situation . . . . . . 85 Console event mapping . . . . . . . 97
Sybase_DB_Freespace_Critical situation . . . . 85
Sybase_DB_Freespace_Warning situation . . . 85 Appendix C. Problem determination 117
Sybase_DB_Num_Errors_Warning situation . . . 85 Gathering product information for IBM Software
Sybase_Device_Free_Pct_Warning situation . . . 85 Support . . . . . . . . . . . . . . . 117
Sybase_ErrorLog_Size_Warning situation . . . 85 Built-in problem determination features . . . . 117
Sybase_IOERR_Startup_Warning situation . . . 85 Problem classification . . . . . . . . . . . 118
Sybase_IOError_Curintvl_Warning situation . . 85 Trace logging . . . . . . . . . . . . . 118
Sybase_Log_Freespace_Critical situation . . . . 85 Overview of log file management . . . . . 118
Sybase_Log_Freespace_Warning situation . . . 86 Examples of trace logging . . . . . . . . 119
Sybase_Log_Suspend_Warning situation . . . . 86 Principal trace log files . . . . . . . . . 119
Sybase_LogonPct_Warning situation . . . . . 86 Enabling detailed tracing in the collector trace
Sybase_Pct_CPU_Yields_Warning situation . . . 86 log . . . . . . . . . . . . . . . . 122
Sybase_Pct_Device_Lock_Warning situation . . 86 Setting RAS trace parameters . . . . . . . 124
Sybase_Pct_Engine_CPU_Critical situation . . . 86 Problems and workarounds . . . . . . . . 126
Sybase_Pct_Engine_CPU_Warning situation . . 86 Installation and configuration problem
Sybase_Pct_IO_Warning situation . . . . . . 86 determination . . . . . . . . . . . . 126
Sybase_Pct_MAX_Locks_Critical situation . . . 86 Agent problem determination . . . . . . . 134
Sybase_Pct_MAX_Locks_Warning situation . . . 87 Tivoli Enterprise Portal problem determination 136
Sybase_Pct_Task_Yields_Warning situation . . . 87 Problem determination for remote deployment 136
Sybase_Pct_Total_CPU_Critical situation . . . . 87 Workspace problem determination . . . . . 137
Sybase_Pct_Total_CPU_Warning situation . . . 87 Situation problem determination . . . . . . 137
Sybase_ProbAge_GT_17_Warning situation . . . 87 Problem determination for Sybase . . . . . 140
Sybase_ProbAge_LT_17_Warning situation . . . 87 Support information . . . . . . . . . . . 141
Sybase_Process_Blocked_Warning situation . . . 87 Searching knowledge bases . . . . . . . . 141
Sybase_Process_Infected_Warning situation . . . 87 Obtaining fixes . . . . . . . . . . . . 142
Sybase_Processes_Bad_Warning situation . . . 88 Receiving weekly support updates . . . . . 142
Sybase_Processes_Stop_Warning situation . . . 88 Contacting IBM Software Support . . . . . 143
Sybase_ProcessLockSleep_Warning situation . . 88
Sybase_ProcessOthSleep_Warning situation . . . 88 Appendix D. Accessibility . . . . . . 145
Sybase_Server_CPU_Critical situation . . . . 88
Navigating the interface using the keyboard . . . 145
Sybase_Server_CPU_Warning situation . . . . 88
Magnifying what is displayed on the screen . . . 145
Sybase_Server_Error_Warning situation . . . . 88
Sybase_Server_Status_Critical situation . . . . 88
Sybase_Server_Status_Inactive situation . . . . 89 Appendix E. Notices . . . . . . . . 147
Trademarks . . . . . . . . . . . . . . 149
Chapter 7. Take Action commands
reference . . . . . . . . . . . . . . 91 Index . . . . . . . . . . . . . . . 151

iv IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Tables
1. Requirements for the Monitoring Agent for 16. General problems and solutions for
Sybase Server . . . . . . . . . . . . 5 uninstallation . . . . . . . . . . . 133
2. Viewing real-time data about Sybase Server 15 17. General agent problems and solutions 134
3. Investigating an event . . . . . . . . . 16 18. Agent problems and solutions on the UNIX
4. Recovering the operation of a resource . . . 17 operating system . . . . . . . . . . 134
5. Customizing your monitoring environment 17 19. Tivoli Enterprise Portal problems and
6. Monitoring with custom situations . . . . . 19 solutions . . . . . . . . . . . . . 136
7. Collecting and viewing historical data . . . 20 20. Remote deployment problems and solutions 136
8. Capacity planning for historical data . . . . 80 21. Workspace problems and solutions . . . . 137
9. Workspace group choices mapping . . . . . 95 22. Specific situation problems and solutions 137
10. Overview of event slots to event classes 97 23. Problems with configuring situations that you
11. Information to gather before contacting IBM solve in the Situation Editor . . . . . . 138
Software Support . . . . . . . . . . 117 24. Problems with configuration of situations that
12. Trace log files for troubleshooting agents 120 you solve in the Workspace area . . . . . 139
13. Problems and solutions for installation and 25. Problems with configuration of situations that
configuration for agents that run on UNIX you solve in the Manage Tivoli Enterprise
systems . . . . . . . . . . . . . 127 Monitoring Services window . . . . . . 140
14. Problems and solutions for installation and 26. Sybase problems and solutions . . . . . . 141
configuration for agents that run on Windows
systems . . . . . . . . . . . . . 128
15. Problems and solutions for installation and
configuration of specific database agents:
Microsoft SQL Server, Sybase, and Oracle . . 130

© Copyright IBM Corp. 2005 v

vi IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
About this guide
The IBM Tivoli Monitoring for Databases: Sybase Server Agent User’s Guide provides
information about installing and using IBM® Tivoli® Monitoring for Databases:
Sybase Server Agent.

Use the configuration chapter in this guide with the IBM Tivoli Monitoring
Installation and Setup Guide to set up the software.

Use the information in this guide with the IBM Tivoli Monitoring User’s Guide to
monitor Sybase Server resources.

Who should read this guide

This guide is for system administrators who install and use Monitoring Agent for
Sybase Server to monitor and manage Sybase Server resources.

Readers should be familiar with the following topics:

v Tivoli Enterprise™ Portal interface
v IBM Tivoli Monitoring application software
v IBM Tivoli Enterprise Console® (optional)
v Sybase Server
v Microsoft® Windows® operating systems
v AIX® operating systems
v Solaris operating systems

What this guide contains

This guide contains the following chapters:
v Chapter 1, “Overview of the Monitoring Agent for Sybase Server,” on page 1
Provides an introduction to the Monitoring Agent for Sybase Server.
v Chapter 2, “Requirements and configuration for the monitoring agent,” on page
5
Provides requirements and configuration information specific to the Monitoring
Agent for Sybase Server.
v Chapter 3, “How to use the Monitoring Agent for Sybase Server,” on page 15
Provides a list of tasks to perform when using the monitoring agent, a list of
procedures for performing each task, and references for finding information
about the procedures. After completing installation and configuration and
becoming familiar with the information in Chapter 1 of this guide, use this
chapter to see how you can use the monitoring agent.
v Chapter 4, “Workspaces reference,” on page 21
Provides an overview of workspaces, references to additional information about
workspaces, and descriptions of predefined workspaces in this monitoring agent.
v Chapter 5, “Attributes reference,” on page 35
Provides an overview of attributes, references to additional information about
attributes, descriptions of the attribute groups and attributes, and disk space
requirements for historical data.

© Copyright IBM Corp. 2005 vii

 v Chapter 6, “Situations reference,” on page 83
Provides an overview of situations, references to additional information about
situations, and descriptions of the predefined situations in this monitoring agent.
v Chapter 7, “Take Action commands reference,” on page 91
Provides detailed information about the Take Action commands, references to
additional information about Take Action commands, and descriptions of the
Take Action commands provided in this monitoring agent.
v Chapter 8, “Policies reference,” on page 93
Provides an overview of policies, references for detailed information about
policies, and descriptions of the predefined policies included in this monitoring
agent.
v Appendix A, “Workspaces workgroups mapped to tasks,” on page 95
Provides additional information about the predefined workspaces provided with
this monitoring agent.
v Appendix B, “IBM Tivoli Enterprise Console event mapping,” on page 97
Provides an overview of the IBM Tivoli Enterprise Console event mapping
information for this monitoring agent.
v Appendix C, “Problem determination,” on page 117
Provides information about troubleshooting the various components of the
Monitoring Agent for Sybase Server, information about log files and messages,
and information about your options for obtaining software support.
v Appendix D, “Accessibility,” on page 145
Provides information about the accessibility features in the Monitoring Agent for
Sybase Server.
v Appendix E, “Notices,” on page 147
Provides IBM and Tivoli notices and trademark information as it applies to the
Monitoring Agent for Sybase Server.

Publications
This section lists publications relevant to using the Monitoring Agent for Sybase
Server and describes how to access these publications online and how to order
these publications.

Prerequisite publications
To use the information in this guide effectively, you must have some knowledge of
IBM Tivoli Monitoring products, which you can obtain from the following
documentation:
v IBM Tivoli Monitoring Installation and Setup Guide
v IBM Tivoli Monitoring Problem Determination Guide
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring
v Introducing IBM Tivoli Monitoring, Version 6.1.0
v IBM Tivoli Monitoring Administrator’s Guide
v IBM Tivoli Monitoring User’s Guide

Related publications
The following documents also provide useful information:
v IBM Tivoli Enterprise Console Adapters Guide
v IBM Tivoli Enterprise Console Event Integration Facility User’s Guide

viii IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 v IBM Tivoli Enterprise Console Reference Manual
v IBM Tivoli Enterprise Console Rule Builder’s Guide

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available at the following
Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

http://www.ibm.com/ibm/terminology

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

Ordering publications
You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755
v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli

publications.

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate most features of the graphical
user interface.

For additional information, see Appendix D, “Accessibility,” on page 145.

About this guide ix

Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education/

Support information
“Support information” on page 141 describes the following options for obtaining
support for IBM products:
v “Searching knowledge bases” on page 141
v “Obtaining fixes” on page 142
v “Contacting IBM Software Support” on page 143

Conventions used in this guide

This guide uses several conventions for special terms and actions, and operating
system-dependent commands and paths.

Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code examples
v File names, programming keywords, and other views that are difficult to
distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

Operating system-dependent variables and paths

The direction of the slash for directory paths might vary in this documentation. No
matter which type of slash you see in the documentation, use the following
guidelines for a slash:
v If using UNIX®, use a forward slash (/).
v If using Windows, use a backslash (\).

x IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
The names of environment variables are not always the same in Windows and
UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX.

For environment variables, use the following guidelines:

v If using UNIX, use $variable.
v If using Windows, use %variable%.

Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.

About this guide xi

xii IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 1. Overview of the Monitoring Agent for Sybase
Server
You can use the Monitoring Agent for Sybase Server to monitor Sybase Server and
to perform basic actions with Sybase Server resources. This chapter provides a
description of the features, components, and interface options for the Monitoring
Agent for Sybase Server.

IBM Tivoli Monitoring overview

IBM Tivoli Monitoring is the base software for the Monitoring Agent for Sybase
Server. IBM Tivoli Monitoring provides a way to monitor the availability and
performance of all the systems in your enterprise from one or several designated
workstations. It also provides useful historical data that you can use to track trends
and to troubleshoot system problems.

You can use IBM Tivoli Monitoring to do the following tasks:

v Monitor for alerts on the systems that you are managing by using predefined
situations or custom situations
v Establish your own performance thresholds
v Trace the causes leading to an alert
v Gather comprehensive data about system conditions
v Use policies to perform actions, schedule work, and automate manual tasks

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products.
Providing a consolidated view of your environment, the Tivoli Enterprise Portal
permits you to monitor and resolve performance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” on

page viii for complete information about IBM Tivoli Monitoring and the Tivoli
Enterprise Portal.

Features of Monitoring Agent for Sybase Server

The Monitoring Agent for Sybase Server offers a central point of management for
distributed databases. It provides a comprehensive means for gathering exactly the
information you need to detect problems early and prevent them. Because
information is standardized across all systems, you can monitor hundreds of
servers from a single workstation. You can collect and analyze specific information
easily.

The Monitoring Agent for Sybase Server is an intelligent, remote monitoring agent
that resides on managed systems. It helps you anticipate trouble and warns system
administrators when critical events occur on their systems. With the Monitoring
Agent for Sybase Server, database and system administrators can set required
threshold levels and flags to alert administrators when the system reaches these
thresholds.

Each Monitoring Agent for Sybase Server instance collects information about one
Sybase Server domain. The monitoring agent performs the following types of
monitoring functions:

© Copyright IBM Corp. 2005 1

 v Obtains data from a Sybase Server database and uses it to create various reports
whenever you choose. This data is useful for examining the performance of the
Sybase Server system.
v Evaluates situations to detect when Sybase Server attribute values exceed preset
thresholds you have defined, and makes this exception information available to
an IBM Tivoli Monitoring workstation.

Monitoring for exceptions requires you to create the Monitoring Agent for Sybase
Server situations that are meaningful to the Sybase Server transactions that you are
monitoring. Example situations and expert advice are provided on the IBM Tivoli
Monitoring workstation to make this task as easy as possible.

Components of Monitoring Agent for Sybase Server

After you install and set up the Monitoring Agent for Sybase Server, you have an
environment that contains the client, server, and monitoring agent implementation
for IBM Tivoli Monitoring that contain the following components:
v Tivoli Enterprise Portal client with a Java™™-based user interface for viewing
and monitoring your enterprise.
v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli
Enterprise Monitoring Server and enables retrieval, manipulation, and analysis
of data from the monitoring agents.
v Tivoli Enterprise Monitoring Server, which acts as a collection and control point
for alerts received from the monitoring agents, and collects their performance
and availability data.
v Monitoring Agent for Sybase Server monitoring agent installed on the systems
or subsystems that you want to monitor. This monitoring agent collects and
distributes data to a Tivoli Enterprise Portal Server.

For both of the IBM Tivoli Monitoring environments (IBM Tivoli Monitoring 5.x
and IBM Tivoli Monitoring 6.1), IBM Tivoli Enterprise Console is an optional
component, which acts as a central collection point for events from a variety of
sources, including those from other Tivoli software applications, Tivoli partner
applications, custom applications, network management platforms, and relational
database systems. You can view these events through the Tivoli Enterprise Portal
(using the event viewer), and you can forward events from IBM Tivoli Monitoring
situations to the IBM Tivoli Enterprise Console component.

User interface options

Installation of the base software and other integrated applications provides the
following interfaces that you can use to work with your resources and data:
Tivoli Enterprise Portal browser client interface
The browser interface is automatically installed with Tivoli Enterprise
Portal. To start Tivoli Enterprise Portal in your Internet browser, enter the
URL for a specific Tivoli Enterprise Portal browser client installed on your
Web server.
Tivoli Enterprise Portal desktop client interface
The desktop interface is a Java-based graphical user interface (GUI) on a
Windows or Linux® workstation.
IBM Tivoli Enterprise Console
Event management application

2 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Manage Tivoli Enterprise Monitoring Services window
The window for the Manage Tivoli Enterprise Monitoring Services utility is
used for configuring the agent and starting Tivoli services that are not
already designated to start automatically.

Chapter 1. Overview of the Monitoring Agent for Sybase Server 3

4 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 2. Requirements and configuration for the monitoring
agent
This chapter contains information about the following topics and procedures
relevant to the installation and configuration of the Monitoring Agent for Sybase
Server:
v “Requirements for the monitoring agent”
v “Configuring on your local system from the Manage Tivoli Enterprise
Monitoring Services window” on page 6
v “Deploying the monitoring agent using the tacmd command line” on page 8
v “Granting permission on the Monitoring Agent for Sybase Server” on page 9
v “Configuring the agent to your installed databases and verifying installation on
UNIX” on page 10
v “Configuring the UTF-8 character set” on page 12
v “Enabling unicode conversions” on page 13

Requirements for the monitoring agent

In addition to the requirements described in the IBM Tivoli Monitoring Installation
and Setup Guide, the Monitoring Agent for Sybase Server has the requirements
listed in Table 1.
Table 1. Requirements for the Monitoring Agent for Sybase Server
Operating system Windows UNIX
Operating system v Windows 2000 Advanced Server v AIX 5.1, 5.2, 5.3 (32-bit and
versions (32-bit) 64-bit)
v Windows 2000 Server (32-bit) v Solaris 8, 9 (32-bit and 64-bit),
v Windows 2003 Server EE Solaris 10 (64-bit)
(32-bit)
v Windows 2003 Server SE
(32-bit)
v Windows XP Professional
(32-bit)
Application v Sybase Server version 11.9.2 v Sybase Server version 11.9.2
versions (32-bit) (32-bit and 64 bit)
v Sybase Server version 12.5.1 v Sybase Server version 12.5.1
(32-bit) (32-bit and 64 bit)
v Sybase Server version 12.5.2 v Sybase Server version 12.5.2
(32-bit) (32-bit and 64 bit)
v Sybase Server version 12.5.3
(32-bit)
Memory v 32 MB RAM v AIX 20 MB
v 150 MB virtual memory, plus 5 v Solaris 50 MB
MB for each agent installed
Disk space v 55 MB disk space for the v AIX 150 MB
monitoring agent v Solaris 250 MB

© Copyright IBM Corp. 2005 5

 Table 1. Requirements for the Monitoring Agent for Sybase Server (continued)
Operating system Windows UNIX
Other v For remote administration, IBM For remote administration, IBM
requirements Tivoli Monitoring: Windows OS Tivoli Monitoring: UNIX OS
Agent must be installed and Agent must be installed and
running. running.
v Grant select permissions for
Sybase Server

v For Sybase Server version 11.9.2, add the UTF-8 charset

v The Monitoring Agent for Sybase Server uses the temporary
database to create its own stored procedures. If your temporary
database size is too small, you receive an error message indicating
that the temporary database is full.
v If you did not install the Sybase Open Client with your installation
of the Sybase Server, install the Sybase Open Client from the Sybase
Server media CD.

Configuring on your local system from the Manage Tivoli Enterprise

Monitoring Services window
Never attempt to start the monitoring agent until you have completed the
configuration steps appropriate to installation of the monitoring agent.

After completing the steps to install the Monitoring Agent for Sybase Server as
described in the IBM Tivoli Monitoring Installation and Setup Guide, ″Installing
monitoring agents,″ you configure the Monitoring Agent for Sybase Server.

To start the Monitoring Agent for Sybase Server use the itmcmd dbagent
command. This command is documented in the IBM Tivoli Monitoring Installation
and Setup Guide.

To configure the Monitoring Agent for Sybase Server, use the following settings:
Server Name
Name of the Sybase Database Server that is to be monitored
Login Sybase user id to be used to connect to the Sybase Database Server in the
Server Name field
Password
Password for the Sybase user id in the Login field
Database Version
Sybase version of the Database Server
Home Directory
Install directory for the Sybase Database Server to be monitored
Error Log File
Location and name of the Sybase Error Log

Note: Enter only ASCII characters in these fields.

6 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Configuring on your local system using the tacmd command line
See the IBM Tivoli Monitoring Installation and Setup Guide for the complete tacmd
addSystem command.

Note: For the addSystem command, all properties are mandatory.

Use the following parameters for the -p | --properties parameter to configure the
Monitoring Agent for Sybase Server:
DBSETTINGS.db_sid
Name of the Sybase Server instance that is to be monitored
INSTANCE
Name of the Sybase Server instance that is to be monitored
DBSETTINGS.db_hostname
Hostname that this monitor will be run on
DBSETTINGS.db_dir
UNIX only property. Database server instance’s directory path
DBSETTINGS.db_home
(Windows) Directory path of the database server instance. (UNIX)
Directory path of the ASE directory.
DBSETTINGS.SYBASE_OCS
Install directory for the Sybase database Open Client. For UNIX, an
example is /opt/sybase/OCS-12_5. For Windows, and example is
c:\sybase\ocs-12_5.

Note: For version 11, use the Sybase installation directory.

DBSETTINGS.db_login
Sybase Server user id to be used to connect to the Sybase Server
DBSETTINGS.db_password
Password for the Sybase Server user id
DBSETTINGS.db_ver
Sybase Server version
DBSETTINGS.db_errorlog
Sybase Errorlog File Path

Deploying the monitoring agent remotely from the Tivoli Enterprise

Portal
Use following settings for the Database Server Properties tab:
Database Server Instance Name
Name of the Sybase Server instance that is to be monitored
Database Server Home Directory Path
Install directory for the Sybase Server to be monitored
Database Server ASE Directory
(UNIX only) Directory in which ASE is installed. An example is
/opt/sybase/ASE-12_5.

Chapter 2. Requirements and configuration for the monitoring agent 7

 Database Server Open Client Directory
Install directory for the Sybase database Open Client. For UNIX, an
example is /opt/sybase/OCS-12_5. For Windows, and example is
c:\sybase\ocs-12_5.

Note: For version 11, use the Sybase installation directory.

Database Server User Id
Sybase Server user id to be used to connect to the Sybase Server in the
Database Server Instance Name field
Database Server Password
Sybase Server user id to be used to connect to the Sybase Server
Database Server Version
Sybase Server version
Database Hostname
Hostname that this monitor will be run on
Database Server Error Log File
Location and name of the Sybase Server Error Log

Use following settings for the Agent tab ″Run as″ information:
Use local system account
(Windows only) Select this setting.
Allow service to interact with desktop
(Windows only) Leave this check box clear.
User Name
(UNIX only and optional) If the default User ID and password are not to
be used (the ones selected when configuring the OS agent), they can be
overridden using this field.
Group Name
(UNIX only and optional) If the default User ID and password are not to
be used (the ones selected when configuring the OS agent), they can be
overridden using this field.

Deploying the monitoring agent using the tacmd command line

See the IBM Tivoli Monitoring Installation and Setup Guide for the complete tacmd
addSystem command.

Note: For the addSystem command, all properties are mandatory.

Use the -t |--type TYPE parameter to specify the Monitoring Agent for Sybase
Server that you are configuring: OY

Use the following parameters for the -p | --properties parameter to configure the
Monitoring Agent for Sybase Server:
DBSETTINGS.db_sid
Name of the Sybase Server instance that is to be monitored
INSTANCE
Name of the Sybase Server instance that is to be monitored
DBSETTINGS.db_hostname
Hostname that this monitor will be run on

8 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 DBSETTINGS.db_dir
UNIX only property. Database server instance’s directory path
DBSETTINGS.db_home
(Windows) Directory path of the database server instance. (UNIX)
Directory path of the ASE directory.
DBSETTINGS.SYBASE_OCS
Install directory for the Sybase database Open Client. For UNIX, an
example is /opt/sybase/OCS-12_5. For Windows, and example is
c:\sybase\ocs-12_5.

Note: For version 11, use the Sybase installation directory.

DBSETTINGS.db_login
Sybase Server user id to be used to connect to the Sybase Server
DBSETTINGS.db_password
Password for the Sybase Server user id
DBSETTINGS.db_ver
Sybase Server version
DBSETTINGS.db_errorlog
Sybase Errorlog File Path

For example:
tacmd addSystem -t OY -n myhostname:KUX -p INSTANCE=dbServer
DBSETTINGS.db_sid=dbServer DBSETTINGS.db_ver=12.5.3
DBSETTINGS.db_home="/opt/sybase/ASE-12_5" DBSETTINGS.db_dir="/opt/sybase"
DBSETTINGS.SYBASE_OCS="/opt/sybase/OCS-12_5"
DBSETTINGS.db_errorlog="/opt/sybase/ASE-12_5/install/dbServer.log"
DBSETTINGS.db_hostname=myhostname DBSETTINGS.db_login=sa
DBSETTINGS.db_password=sapassword

Granting permission on the Monitoring Agent for Sybase Server

Objective
To grant access to all views of the Monitoring Agent for Sybase Server.

Background information
This procedure includes creating a user ID and granting permission to the new
user ID.

Required authorization role

Database administrator

Before you begin

Before beginning this procedure, install and configure the agent at described in
IBM Tivoli Monitoring Installation and Setup Guide.

When you finish

When the permissions have been successfully granted, you can start the
monitoring agent. To start the Monitoring Agent for Sybase Server use the itmcmd
dbagent command. This command is documented in the IBM Tivoli Monitoring
Installation and Setup Guide.

Chapter 2. Requirements and configuration for the monitoring agent 9

 Procedure
Perform this procedure from the command line.
1. Open a command prompt.
2. For Windows, enter the following command:
cd %CANDLE_HOME%\tmaitm6\SQLLIB
Where:
%CANDLE_HOME%
Your Candle® home directory

For UNIX, enter the following command:

cd $INSTALLDIR/misc
Where:
$INSTALLDIR
Your Candle home directory
3. Use the isql command to log into the Sybase server as user ″sa″.
4. Enter the following command, which is case-sensitive, to configure the Candle
user:
1>sp_addlogin tivoli,password
2>go
Where:
tivoli Tivoli user ID, default
password
Password assigned to the Candle user

If the Tivoli user is not ″tivoli″, edit the koygrant.sql file and change ″tivoli″ to
the Tivoli user ID.
5. Enter the following case-sensitive command, which runs the koygrant.sql script
to change the grant permission tables in the master database:
isql -U sa -P password -S servername -i koygrant.sql

Where:
password
Password for user ″sa″
servername
Database server name

Configuring the agent to your installed databases and verifying

installation on UNIX
Objective
To configure the Monitoring Agent for Sybase Server to work with the specific
database servers located on each UNIX system and to verify that the Monitoring
Agent for Sybase Server is ready to use.

Background Information
During this procedure, you either use the itmcmd dbconfig command or the
itmcmd config command to locate the agent servers on the system that you want
to monitor. The search process is reliable when the servers are running when
itmcmd dbconfig or itmcmd config searches for them, but these commands cannot

10 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
always find non-running servers. Additionally, these commands can verify that the
installation and configuration are complete.

The itmcmd config command is documented in the IBM Tivoli Monitoring

Installation and Setup Guide.

The pertinent parameters that the itmcmd dbconfig command accepts are as
follows:

itmcmd dbconfig [-h install_dir] [-s server |-i ID| -ppassword] [product_code]
-h install_dir
The name of the top-level directory in which you installed the monitoring
agent.
-s server
The name of the server.
-i ID The user-defined ID for the server.
-p password
The user-defined password for the server.
product_code
The product code, which is oy.

Required authorization role

The user ID that was created using the koygrant.sql file.

Procedure
1. If you know the name of your server instance use the itmcmd config -A
command. This command is fully documented in the IBM Tivoli Monitoring
Installation and Setup Guide.
2. If you do not know the name of your server instance use the itmcmd dbconfig
command with the following steps.
a. At the first menu, select the following option: Confine automatic search to
running databases to search for your databases.
b. When the search is complete and the Database Options menu is displayed,
do the following as needed:
v If the initial search found all of your servers, configuration is complete,
go to Step 4.
v If you need to search for a database that the itmcmd dbconfig command
did not find because the database is not running, or because it is running
on another system, use itmcmd dbconfig as follows to search disk files:
1) Exit itmcmd dbconfig.
2) Open itmcmd dbconfig.
3) Select the following option: Also search for non-running databases.
4) Press Enter to display the Database Options menu.
5) Select the following option: Optional disk searches, manually add
servers....
Additional information: The menu that is displayed represents a
hierarchy of alternate search techniques listed in the order of the
amount of manual input they require. Use only the techniques that
you need to search for the files, because the process is slower and less
reliable than searching running servers. Searches through NFS file
systems can take some time.

Chapter 2. Requirements and configuration for the monitoring agent 11

 The list of UNIX users also shows the name of the file system on
which each user’s $HOME is located. The Manually add a server
option is a tool of last resort. You can use this tool to define any
server that is located on a file system that you cannot currently
access.
v If various searches found databases that you do not want monitored, or
that run on other UNIX machines, exclude these databases from
consideration by selecting the following option on the Database Options
menu: Exclude/Include a server from the configuration.
Additional information: Future searches ignore any server that you exclude,
but the excluded server can be manually included at any time.
v If you need to review the details of the servers, select the following
option: Display or Modify defined servers... on the Database Options
menu.
c. Verify the installation by selecting the following option: Verify Database
OMA installation on the Database Options menu.

Note: The Verify Database OMA Installation option does not inform you if
you enter the wrong user ID or password.
d. Exit itmcmd dbconfig.
Additional information: A message that names a file containing a log of your
itmcmd dbconfig activity is displayed. This log can help IBM Customer
Support diagnose configuration problems.

Configuring the UTF-8 character set

Objective
To configure the UTF-8 character set so that the Monitoring Agent for Sybase
Server can collect data from the Sybase Server to display on the Tivoli Enterprise
Portal, which uses the UTF-8 character set to display data.

Background Information
Monitoring Agent for Sybase Server must have the UTF-8 charset configured for
translation purposes.

Required authorization role

Sybase system administrator access

Before you begin

Determine which character sets you have configured using the Sybase Server isql
command to query the Sybase Server for all of the configured character sets. At the
isql prompt, enter the following query to list the configured character sets:
1> use master
2> go
1> select csid, id, name from syscharsets
2> go
csid id name
---- --- ------------------------------
0 0 ascii_8
0 1 iso_1
1 50 bin_iso_1

When you finish

Determine whether the UTF-8 character set is configured by running the isql
command described above in “Before you begin.”

12 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Procedure
1. Bring up a command window.
2. Go to the Sybase/charsets/utf8 directory.
3. Run the following command:
charset -Usa -Ppassword -Sservername binary.srt utf8
4. Restart the Monitoring Agent for Sybase Server so that it can use the UTF-8
charset.
Additional information: If the UTF-8 charset is not available, you receive the
following error message: Open Client Server Message Number: 2409 Character
set conversion is not available between client character set ’utf8’ and
server character set ’charset’.

Note: If your server uses the cp850 character set you receive the following
message that you can safely ignore: Message String: Character set
conversion is not available between client character set ’utf8’
and server character set ’cp850’.

Enabling unicode conversions

Objective
To collect data in the unicode format, the Monitoring Agent for Sybase Server must
be configured to do conversions between the configured code and the UTF8
codepage, which the agent uses. Perform this procedure to ensure that the UTF8
conversion occurs. This ensures that the code page specific data in the Monitoring
Agent for Sybase Server converts to UTF8 and displays correctly in the Tivoli
Enterprise Portal.

Background Information
Monitoring Agent for Sybase Server must have the UTF-8 charset configured for
translation purposes.

Required authorization role

Sybase system administrator access

Before you begin

Determine if unicode conversions are already enabled. Run the following
command from and isql command prompt::
1> sp_configure "enable unicode conversions"
2> go

If the Config Value and Run Value displayed are not 0, then no further steps are
required. If the values are 0, you need to perform the steps below.

When you finish

Determine whether the UTF-8 character set is configured by running the isql
command described above in “Before you begin.”

Procedure
At the isql prompt, run the following command to enable the unicode conversions:
1> sp_configure "enable unicode conversions", 2
2> go

If the Monitoring Agent for Sybase Server is running, it should be restarted.

Chapter 2. Requirements and configuration for the monitoring agent 13

14 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 3. How to use the Monitoring Agent for Sybase
Server
After you have installed and configured the Monitoring Agent for Sybase Server,
you can begin using this monitoring agent to monitor your resources.

This chapter provides information about how to use the Monitoring Agent for
Sybase Server to perform the following tasks:
v “View real-time data about Sybase Server”
v “Investigate an event” on page 16
v “Recover the operation of a resource” on page 16
v “Customize your monitoring environment” on page 17
v “Monitor with custom situations that meet your requirements” on page 18
v “Collect and view historical data” on page 19

For each of these tasks, there is a list of procedures that you perform to complete
the task. For the procedures, there is a cross-reference to where you can find
information about performing that procedure. Information about the procedures is
located in subsequent chapters and appendixes of this user’s guide and in the IBM
Tivoli Monitoring documentation.

View real-time data about Sybase Server

After the Monitoring Agent for Sybase Server has been installed, configured, and
started, the monitoring agent begins monitoring.

Table 2 contains a list of the procedures for viewing the real-time data about
Sybase Server that the monitoring agent collects. The table also contains a
cross-reference to where you can find information about each procedure.
Table 2. Viewing real-time data about Sybase Server
Procedure Where to find information
View the hierarchy of your monitored IBM Tivoli Monitoring User’s Guide:
resources from a system point of view ″Navigating through workspaces″ (in
(Navigator view organized by operating ″Monitoring: real-time and event-based″
platform, system type, monitoring agents, chapter)
and attribute groups).
View the indicators of real or potential
problems with the monitored resources
(Navigator view).
View changes in the status of the resources IBM Tivoli Monitoring User’s Guide: ″Using
that are being monitored (Enterprise workspaces″ (in ″Monitoring: real-time and
Message Log view). event-based″ chapter)
View the status of the agents in the Chapter 4, “Workspaces reference,” on page
managed enterprise that you are monitoring 21 in this guide
(Monitoring Agent Status view).

© Copyright IBM Corp. 2005 15

 Table 2. Viewing real-time data about Sybase Server (continued)
Procedure Where to find information
View the number of times an event has been IBM Tivoli Monitoring User’s Guide: ″Using
opened for a situation during the past 24 workspaces″ (in ″Monitoring: real-time and
hours (Open Situations Count view). event-based″ chapter)

Chapter 4, “Workspaces reference,” on page

21 in this guide

Chapter 6, “Situations reference,” on page 83

in this guide
Manipulate the views in a workspace. IBM Tivoli Monitoring User’s Guide: ″Using
views″ (in ″Monitoring: real-time and
event-based″ chapter)

Investigate an event
When the conditions of a situation have been met, an event indicator is displayed
in the Navigator. When an event occurs, you want to obtain information about that
event so you can correct the conditions and keep your enterprise running
smoothly. The situation must be associated with a Navigator Item in order to
appear.

Table 3 contains a list of the procedures for investigating an event and a

cross-reference to where you can find information about each procedure.
Table 3. Investigating an event
Procedure Where to find information
Determine which situation raised the event IBM Tivoli Monitoring User’s Guide: ″Opening
and identify the attributes that have values the situation event workspace″ (in
that are contributing to the alert. ″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)

Chapter 4, “Workspaces reference,” on page

Review available advice. 21 in this guide

Appendix A, “Workspaces workgroups

mapped to tasks,” on page 95 in this guide
Notify other users that you have taken IBM Tivoli Monitoring User’s Guide:
ownership of the problem related to an ″Acknowledging an situation event″ (in
event and are working on it. ″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)
Remove the event from the Navigator. IBM Tivoli Monitoring User’s Guide: ″Closing
the situation event workspace″ (in
″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)

Recover the operation of a resource

When you find out that a resource is not operating as desired, you can control it
manually or automatically using Take Action commands.

Table 4 on page 17 contains a list of the procedures for recovering the operation of
a resource and a cross-reference to where you can find information about each
procedure.

16 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Table 4. Recovering the operation of a resource
Procedure Where to find information
Take an action on a resource manually. IBM Tivoli Monitoring User’s Guide:
v ″Other views″ (in ″Custom workspaces″
chapter, ″Workspace views″ section)
v ″Take action – Reflex automation″ (in
Situations for event-based monitoring″
chapter, ″Event-based monitoring
overview″ section)

Chapter 7, “Take Action commands

reference,” on page 91 in this guide
Take an action on a system condition IBM Tivoli Monitoring User’s Guide:
automatically by setting up a situation to ″Situations for event-based monitoring″
run a Take Action command. chapter
v ″Customizing a situation″
v ″Creating a situation″
v ″Specify an action to take″
v ″Distribute the situation″

Chapter 7, “Take Action commands

reference,” on page 91 in this guide
Take multiple actions on system conditions IBM Tivoli Monitoring User’s Guide: ″Policies
automatically using a policy. for automation″ chapter
v ″Creating a policy″
v ″Maintaining policies″
Take actions across systems, monitoring v ″Workflows window″
agents, or computers using a policy.
Chapter 8, “Policies reference,” on page 93 in
this guide

Customize your monitoring environment

You can change how your monitoring environment looks by creating new
workspaces with one or more views in it.

Table 5 contains a list of the procedures for customizing your monitoring

environment and a cross-reference to where you can find information about each
procedure.
Table 5. Customizing your monitoring environment
Procedure Where to find information
Display data in tables or charts (views) in IBM Tivoli Monitoring User’s Guide:
Tivoli Enterprise Portal. v ″Custom workspaces″
v ″Table and chart views″
Display an overview of changes in the status IBM Tivoli Monitoring User’s Guide: ″Message
of the situations for your monitored log view″ (in ″Situation event views:
resources (Message Log View). message log, situation event console,
graphic, and Tivoli Enterprise Console″
chapter)

Chapter 3. How to use the Monitoring Agent for Sybase Server 17

 Table 5. Customizing your monitoring environment (continued)
Procedure Where to find information
Specify which attributes to retrieve for a IBM Tivoli Monitoring User’s Guide: ″Creating
table or chart so you can retrieve only the custom queries″ (in ″Table and chart views″
data you want by creating custom queries. chapter)

Chapter 5, “Attributes reference,” on page 35

in this guide
Build links from one workspace to another. IBM Tivoli Monitoring User’s Guide:
v ″Link from a workspace″ (in ″Custom
workspaces″ chapter)
v ″Link from a table or chart″ (in ″Table and
chart views″ chapter)
Identify which predefined situations started IBM Tivoli Monitoring User’s Guide: ″What
running automatically when you started the the enterprise workspace shows″ (in
Tivoli Enterprise Monitoring Server. ″Monitoring: real-time and event-based″
chapter, ″Using workspaces″ section)

Chapter 6, “Situations reference,” on page 83

in this guide
Determine whether to run situations as Chapter 6, “Situations reference,” on page 83
defined, modify the values in situations, or in this guide
create new situations to detect possible
problems.

Monitor with custom situations that meet your requirements

When your environment requires situations with values that are different from
those in existing situations, or when you need to monitor conditions not defined
by the existing situations, you can create custom situations to detect problems with
resources in two ways:
v Create an entirely new situation
v Create a situation by copying and editing a predefined situation

Note: When you create and run a situation, an IBM Tivoli Enterprise Console
event is created. For information on how to define event severities from
forwarded IBM Tivoli Monitoring situations and other event information,
see the IBM Tivoli Monitoring Administrator’s Guide.

You can specify the following information for a situation:

v Name
v Attribute group and attributes
v Qualification to evaluate multiple rows when a situation has a multiple-row
attribute group (display item)
v Formula
v Take Action commands
v Run at startup
v Sampling interval
v Persistence
v Severity
v Clearing conditions

18 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 v Expert Advice
v When a true situation closes
v Available Managed Systems

Table 6 contains a list of the procedures for monitoring your resources with custom
situations that meet your requirements and a cross-reference to where you can find
information about each procedure.
Table 6. Monitoring with custom situations
Procedure Where to find information
Create an entirely new situation. IBM Tivoli Monitoring User’s Guide: ″Creating
a new situation″ (in ″Situations for
event-based monitoring″ chapter, ″Creating a
situation″ section)

Chapter 5, “Attributes reference,” on page 35

in this guide
Create a situation by copying and editing a IBM Tivoli Monitoring User’s Guide:
predefined situation. ″Customizing a situation″ (in ″Situations for
event-based monitoring″ chapter)

Chapter 6, “Situations reference,” on page 83

in this guide

Chapter 5, “Attributes reference,” on page 35

in this guide
Run a situation on a managed system. IBM Tivoli Monitoring User’s Guide:
″Situations for event-based monitoring″
chapter
v ″Associate situations with navigator
items″
v ″Distribute the situation″ (in ″Customizing
a situation″ section)
v ″Start, stop, or delete a situation″

Collect and view historical data

When you collect historical data, you specify the following configuration
requirements:
v Attribute groups for which to collect data
v Collection interval
v Summarization and pruning of attribute groups
v Roll-off interval to a data warehouse, if any
v Where to store the collected data (at the agent or the Tivoli Enterprise
Monitoring Server)

Table 7 on page 20 contains a list of the procedures for collecting and viewing
historical data and a cross-reference to where you can find information about each
procedure.

Chapter 3. How to use the Monitoring Agent for Sybase Server 19

 Table 7. Collecting and viewing historical data
Procedure Where to find information
Configure and start collecting short-term IBM Tivoli Monitoring User’s Guide:
data (24 hours). ″Historical reporting″ (in ″Table and chart
views″ chapter)
Configure and start collecting longer-term
data (more than 24 hours). IBM Tivoli Monitoring Administrator’s Guide
View historical data in the Tivoli Enterprise
Portal. “Disk capacity planning for historical data”
on page 79
Create reports from historical data using
third-party reporting tools.
Filter out unwanted data to see specific
areas of interest.

20 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 4. Workspaces reference
This chapter contains an overview of workspaces, references for detailed
information about workspaces, and descriptions of the predefined workspaces
included in this monitoring agent.

About workspaces
A workspace is the working area of the Tivoli Enterprise Portal application
window. At the left of the workspace is a Navigator that you use to select the
workspace you want to see. As part of the application window, the right side of
the status bar shows the Tivoli Enterprise Portal server name and port number to
which the displayed information applies, and the ID of the current user.

As you select items in the Navigator, the workspace presents views pertinent to
your selection. Each workspace has at least one view. Some views have links to
workspaces. Every workspace has a set of properties associated with it.

This monitoring agent provides predefined workspaces. You cannot modify the
predefined workspaces, but you can create new workspaces by editing them and
saving the changes with a different name.

More information about workspaces

For more information about creating, customizing, and working with workspaces,
see the IBM Tivoli Monitoring User’s Guide.

For a list of the predefined workspaces for this monitoring agent and a description
of each workspace, refer to the Predefined workspaces section below and the
information in that section for each individual workspace.

For additional information about workspaces for this monitoring agent, see
Appendix A, “Workspaces workgroups mapped to tasks,” on page 95.

Predefined workspaces
The Monitoring Agent for Sybase Server provides the following predefined
workspaces, which are organized alphabetically:
v Cache Usage
v Databases
v Device Usage
v Engine Summary
v Enterprise Database Summary
v Enterprise Errorlog Alerts
v Enterprise Locking Summary
v Enterprise Processes Summary
v Enterprise Server Statistics
v Enterprise Server Summary
v Enterprise Sybase Summary
v Errorlog Alerts
© Copyright IBM Corp. 2005 21
 v Lock Information
v Lock Usage
v Log and Space Information
v Log Usage
v Process Holding Lock
v Process SQL Text
v Processes
v Server Configuration
v Server Statistics
v Servers
v SQL Text
v Sybase Server_ID

The remaining sections of this chapter contain descriptions of each of these

predefined workspaces. The workspaces are organized alphabetically.

Cache Usage workspace

The default Cache Usage workspace includes the following views:
v Cache Hit Percent bar chart
v Cache Usage bar chart
v Cache Summary table view
v Cache Usage table view

Cache Hit Percent bar chart

The Cache Hit Percent bar chart compares the numbers of cache hits and misses on
the server. This bar chart displays data provided by the Cache Summary attributes.

Cache Usage bar chart

The Cache Usage bar chart displays number of cache hits, misses, and searched. It
also shows the count for large I/O pages cached, denied, performed, and used as
well as counts for the Least Recently Used (LRU) and Most Recently Used (MRU)
buffers. This bar chart displays data provided by the Cache Summary attributes.

Cache Summary table view

The Cache Summary table view displays summary information about the caches
for a selected server. For example, it shows the number of cache searches resulting
in hits and misses and the various statistics for cached large I/O pages, LRU
buffers, and MRU buffers. This table view displays data provided by the Cache
Summary attributes.

Cache Usage table view

The Cache Usage table view displays detailed information about each named cache
for a selected server. For example, it shows the name of the cache and the number
of cache searches resulting in hits and misses and the various statistics for cached
large I/O pages, LRU buffers, and MRU buffers. This table view displays data
provided by the Cache Detail attributes.

Databases workspace
The Monitoring Agent for Sybase Server provides detailed and summary
information about databases, which also includes information about the number of
databases, the number of devices and log usage.

22 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 The predefined Databases workspace contains the following views:
v Percent Freespace bar chart
v Databases Summary bar chart
v Databases Summary table view
v Databases Detail table view

Percent Freespace bar chart

The Percent Freespace bar chart shows data and log free space available in
different data bases. This bar chart displays data provided by the Database Detail
attributes.

Database Summary bar chart

The Database Summary bar chart shows the total number of databases and totals
for databases that have error status, a DBO only status, read only status, single
user status, and free space accounting disabled. This bar chart displays data
provided by the Database Summary attributes.

Databases Summary table view

The Databases Summary table view displays summary information about
databases for a selected server. It shows which databases have an error status,
which have the lowest percentage of free space, and what database options are
being used. This table view displays data provided by the Database Summary
attributes.

Databases Detail table view

The Databases Detail table view displays detailed information about database
activity for a specific server. It shows the name and owner of each database and
the available space in the database. This table view displays data provided by the
Database Detail attributes. It also provides access to the Log and Space Information
workspace.

Device Usage workspace

The predefined Device Usage workspace contains the following views:
v Device Usage Per Second bar chart
v Percent Device Usage bar chart
v Device Usage table view

Device Usage Per Second bar chart

The Device Usage Per Second bar chart shows the number of locks, contentions,
reads, writes, and combined total of reads and writes being granted per second for
a device. This bar chart displays data provided by the Physical Device Detail
attributes.

Percent Device Usage bar chart

The Percent Device Usage bar chart shows the percentage of locks, contentions,
reads, writes, and combined total of reads and writes being granted per second for
a device. This bar chart displays data provided by the Physical Device Detail
attributes.

Device Usage table view

The Device Usage table view displays detailed information about each device
allocated for a selected server. For example, it shows the path name for the

Chapter 4. Workspaces reference 23

 physical device, the number of reads and writes, and the number of locks granted
and denied. This table view displays data provided by the Physical Device Detail
attributes.

Engine Summary workspace

The predefined Engine Summary workspace contains the following views:
v Engine Summary bar chart
v Engine Usage bar chart
v Engine Summary table view
v Engine Usage table view

Engine Summary bar chart

The Engine Summary bar chart for the sampling period shows the number of
completed and pending accesses to disk, the number of changes by the server from
one user task to another, and the number of TDS packets the engine sent and
received. This bar chart displays data provided by the Engine Summary attributes.

Engine Usage bar chart

The Engine Usage bar chart for the sampling period shows the number of TDS
bytes the engine sent and received, the number of changes by the server from one
user task to another, and the number of TDS packets the engine sent and received.
This bar chart displays data provided by the Engine Detail attributes.

Engine Summary table view

The Engine Summary table view displays summary information all server engines
in your environment. For example, it show the number of engines and the number
of bytes sent and received by each engine. This table view displays data provided
by the Engine Summary attributes.

Engine Usage table view

The Engine Usage table view displays detailed information about each engine of a
server. It provides such information as the name of the engine, the number of bytes
processed by the engine, and the number of transactions processed by the engine.
This table view displays data provided by the Engine Detail attributes.

Enterprise Database Summary workspace

The predefined Enterprise Database Summary workspace contains the following
views:
v Percent Freespace bar chart
v Databases Summary table view

Percent Freespace bar chart

The Percent Freespace bar chart shows the minimum percentage of available free
space in the data only and data log segments of a device allocated to the database.
This bar chart displays data provided by the Database Summary attributes.

Databases Summary table view

The Databases Summary table view displays summary information about
databases and devices on a selected server. It shows databases that have an error
status, the lowest percentage of free space in the databases on the server, and the
database options that are being used. This table view displays data provided by
the Database Summary attributes.

24 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Enterprise Errorlog Alerts workspace
The predefined Enterprise Errorlog Alerts workspace contains the following views:
v Total Errors bar chart
v Errorlog Size bar chart
v Alert Summary table view

Total Errors bar chart

The Total Errors bar chart shows how many error messages with a severity level of
17 or higher have been issued since startup. This bar chart displays data provided
by the Problem Summary attributes.

Errorlog Size bar chart

The Errorlog Size bar chart show the number of bytes in the error log file. This bar
chart displays data provided by the Problem Summary attributes.

Alert Summary table view

The Alert Summary table view displays summary information about the error
messages for the enterprise. It reports the following information:
v Number of errors since startup and during the current interval
v Date and time of the message with the highest severity level
v Highest severity level for errors during the current interval and since startup
v Size of the error log

This table view displays data provided by the Problem Summary attributes.

Enterprise Locking Summary workspace

The predefined Enterprise Locking Summary workspace contains the following
views:
v Locking Summary bar chart
v Processes Blocked bar chart
v Locking Summary table view

Locking Summary bar chart

The Locking Summary bar chart compares the total number of locks with the
number of lock conflicts. This bar chart displays data provided by the Lock Detail
attributes.

Processes Blocked bar chart

The Processes Blocked bar chart shows how many processes are blocked. This bar
chart displays data provided by the Process Summary attributes.

Locking Summary table view

The Locking Summary table view displays summary information about locks for
the Sybase Server server. It shows the following information:
v Server name and version
v Number of locks
v Number of blocked processes
v Percentage of blocked processes
v Status of the data collector

This table view displays data provided by the Server Summary attributes.

Chapter 4. Workspaces reference 25

 Enterprise Processes Summary workspace
The predefined Enterprise Processes Summary workspace contains the following
views:
v CPU Percent bar chart
v Processes Blocked bar chart
v Process Summary table view

CPU Percent bar chart

The CPU Percent bar chart compares the percentage of CPU being used by the
server with that being used by the applications. This bar chart displays data
provided by the Process Summary attributes.

Processes Blocked bar chart

The Processes Blocked bar chart displays the percentage of blocked processes. This
bar chart displays data provided by the Process Summary attributes.

Process Summary table view

The Process Summary table view displays summary information about processes
running on a selected server. It give totals for all processes and the number of
processes classified as blocked. This table view displays data provided by the
Process Summary and Server Summary attributes.

Enterprise Server Statistics workspace

The predefined Enterprise Server Statistics workspace contains the following views:
v Server Statistics bar chart
v Server Statistics table view

Server Statistics bar chart

The Server Statistics bar chart shows the number of physical reads and writes for
the current interval. This bar chart displays data provided by the Statistics
Summary attributes.

Server Statistics table view

The Server Statistics table view displays summary statistical information for a
selected server. For example, it shows the number of active connections and the
number of reads and writes per second. This table view displays data provided by
the Statistics Summary attributes.

Enterprise Server Summary workspace

The predefined Enterprise Server Summary workspace contains the following
views:
v CPU Percent bar chart
v Servers Summary table view
v Remote Servers Summary table view

CPU Percent bar chart

The CPU percent bar chart compares the percentage of CPU time being used by
the server with that being used by the operating system and applications. This bar
chart displays data provided by the Server Summary attributes.

Servers Summary table view

The Servers Summary table view displays summary information about a selected
server. For example, it shows the server name and status, server type and version,

26 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 and the percentage of CPU time the server is using on the host. This table view
displays data provided by the Server Summary attributes.

Remote Servers Summary table view

The Remote Servers Summary table view displays information on the remote
servers in your enterprise. For example, it shows the name, ID status, and
connection level for each remote server. This table view displays data provided by
the Remote Servers attributes.

Enterprise Sybase Summary workspace

The predefined Enterprise Sybase Summary workspace contains the following
views:
v CPU Percent bar chart
v Lock Analysis bar chart
v Errolog Alerts Summary bar chart

CPU Percent bar chart

The CPU Percent bar chart compares CPU usage among the Sybase Server server,
the operating system, and the applications on the server. This bar chart displays
data provided by the Server Summary attributes.

Lock Analysis bar chart

The Lock Analysis bar chart shows totals for locks, blocked processes and lock
conflicts. This bar chart displays data provided by the Lock Detail attributes.

Errorlog Alerts Summary bar chart

The Errorlog Alerts Summary bar chart shows number of error messages with a
severity of 17 or higher that have occurred since the server was started. This bar
chart displays data provided by the Problem Summary attributes.

Errorlog Alerts workspace

The Monitoring Agent for Sybase Server provides information about the server
error log. The workspaces in this group provide the following information:
v Size of the error log
v Number of error messages with a high severity level
v Highest severity level encountered since startup

The predefined Errorlog Alerts workspace contains the following views:

v Alert Summary bar chart
v Alert Summary table view
v Alert Detail table view

Alert Summary bar chart

The Alert Summary bar chart shows the totals for all error messages, error
messages received during the current interval, error messages with a severity level
of 17 or higher, and error messages with a severity level of less than 17. This chart
displays data provided by the Problem Summary attributes.

Alert Summary table view

The Alert Summary table view displays summary information about the error
messages for a selected server. For example, it shows the
v number of errors since startup
v date and time of the message with the highest severity level

Chapter 4. Workspaces reference 27

 v highest severity level for errors during the current interval and since startup
v number of error messages that occurred during the current interval

This table view displays data provided by the (Problem Summary) attributes.

Alert Detail table view

The Alert Detail table view displays detailed information about the error messages
for a selected server. For example, it shows the following information:
v ID and age of the error
v Text of the error message
v Severity level for the error message

This table view displays data provided by the Problem Detail attributes.

Lock Information workspace

The Monitoring Agent for Sybase Server provides detailed and summary
information about locks and conflicts:
v Number of locks on processes
v Number of lock conflicts
v Percent of locks that resulted in deadlocks
v Type of lock on a process

The predefined Lock Information workspace contains the following views:

v Lock Statistics table view
v Lock Conflict table view
v Lock Details table view

Lock Statistics table view

The Lock Statistics table view displays statistical information about the locks on a
selected server. It shows the number of lock requests, deadlocks, and shared and
exclusive lock promotions. This table view displays data provided by the Lock
Summary attributes. It also provides access to the Lock Usage workspace.

Lock Conflict table view

The Lock Conflict table view displays detailed information about the lock conflicts
on a selected server. It provides the type of lock, the ID of the process holding the
lock, and how long a process has been blocked. This table view displays data
provided by the Lock Conflict Detail attributes.

Lock Detail table view

The Lock Details table view displays detailed information about the locks on a
selected server. It shows the cursor associated with the lock, the type of lock, and
the ID of the process holding the lock. This table view displays data provided by
the Locks attributes. It also provides access to the Process Holding Lock
workspace.

Lock Usage workspace

The predefined Lock Usage workspace contains the following views:
v Locking Summary bar chart
v Lock Usage table view

28 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Locking Summary bar chart
The Locking Summary bar chart displays the totals for deadlocks, lock contentions,
lock promotes, exclusive lock promotes, shared lock promotes, and lock requests.
This bar chart displays data provided by the Lock Summary attributes.

Lock Usage table view

The Lock Usage table view displays detailed information about locks on a selected
server. For example, it shows the type of lock, the number of requests for resources
that have been granted and denied, and the number of deadlocked requests.

This table view displays data provided by the Lock Detail attributes.

Log and Space Information workspace

The predefined Log and Space Information workspace contains the following
views:
v Data and Log Size bar chart
v Device Size and Freespace bar chart
v Log and Space Information table view
v Devices table view

Data and Log Size bar chart

The Data and Log Size bar chart compares the following numbers:
v Megabytes allocated for the data only and data and log segments of the
database with the number of megabytes free space for data
v Megabytes allocated for the transaction log, which includes the allocations for
the log only and transaction only partitions, with the number of megabytes free
space in the transaction log

This bar chart displays data provided by the Database Detail attributes.

Device Size and Freespace bar chart

The Device Size and Freespace bar chart compares the size of the device with the
number of megabytes of free space on the device. This bar chart displays data
provided by the Device Detail attributes.

Log and Space Information table view

The Log and Space Information table view displays information about transaction
log and space usage on a selected database. It shows the size of the database and
transaction log, the number of devices defined for the database, and the settings
for the database options. This table view displays data provided by the Database
Detail attributes.

Devices table view

The Devices table view displays summary information about devices defined for a
selected database. It gives the physical and mirror names of the device and the size
and type of the device. This table view displays data provided by the Device
Detail attributes. It also provides access to the Device Usage workspace.

Log Usage workspace

The predefined Log Usage workspace contains the following views:
v Logging Summary bar chart
v Log Usage table view
v Logging Summary table view

Chapter 4. Workspaces reference 29

 v SQL Activity table view

Logging Summary bar chart

The Logging Summary Percent bar chart for the sampling period displays counts
for Private Log Cache (PLC) semaphore requests and the total number of pages for
private log caches and cache flushes, page allocations for the transaction log, and
transaction log writes to disk. This bar chart displays data provided by the Log
Summary attributes.

Log Usage table view

The Log Usage table view displays detailed data provided about each transaction
log activity for a selected server. For example, it shows the names of each
transaction log activity, the number of times each activity occurred, and log cache
activity per second. This table view displays data provided by the Log Detail
attributes.

Logging Summary table view

The Logging Summary table view displays data provided by summary information
about transaction log activity for a selected server. It contains such information as
the number of lock requests, the number of private log cache flushes, the number
of log semaphore requests, and the maximum size of the private log cache. This
table view displays data provided by the Log Summary attributes.

SQL Activity table view

The SQL Activity table view displays summary information about SQL activity on
a selected server. It includes the type of activity and the number of times the
activity occurred. This table view displays data provided by the Text attributes.

Process Holding Lock workspace

The predefined Process holding workspace contains the following views:
v Event console
v Process Holding Lock SQL Text table view

Process Holding Lock SQL Text table view

The Process Holding Lock SQL Text table view displays the process ID and
sequence number of the process holding the lock and the partial or complete SQL
statement. This table view displays data provided by the Text attributes.

Process SQL Text workspace

The predefined Process SQL Text workspace for processes contains the following
views:
v Event console
v Waiting Process SQL Text table view
v Blocking Process SQL Text table view

Waiting Process SQL Text table view

The Waiting Process SQL Text table view displays process ID, sequence number,
and SQL text for the waiting process. This table view displays data provided by
the Text attributes.

Blocking Process SQL Text table view

The Blocking Process SQL Text table view displays process ID, sequence number,
and SQL text for the blocking process. This table view displays data provided by
the Text attributes.

30 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Processes workspace table view
The Monitoring Agent for Sybase Server provides detailed and summary
information about processes:
v Number of blocked processes
v Percentage of CPU time used by processes
v Percentage of CPU time used by application processes

The predefined Processes workspace contains the following views:

v CPU Percent bar chart
v Process Summary bar chart
v Process Summary table view
v Processes Detail table view

CPU Percent bar chart

The CPU Percent bar chart compares the percentage of CPU being used by the
server with that being used by applications. This bar chart displays data provided
by the Process Summary attributes.

Process Summary bar chart

The Process Summary bar chart displays totals for all processes and blocked,
infected, bad, and stopped processes. It also shows the number of processes in
locksleep and other sleep. This bar chart displays data provided by the Process
Summary attributes.

Process Summary table view

The Process Summary table view displays summary information about processes
running on a selected server. It shows totals for all processes as well as the number
of processes classified as blocked, infected, bad, stopped, in sleep, in locksleep, and
other sleep. This table view displays data provided by the Process Summary
attributes.

Processes Detail table view

The Process Detail table view displays detailed information about each process
running on a selected server. For each process, it shows the usage and time, the
name of the transaction, and status. This table view displays data provided by the
Process Detail attributes. This table view also provides access to the SOL Text
workspace.

Server Configuration workspace

The predefined Server Configuration workspace contains the following views:
v Server Configuration table view
v Server Options table view
v Task Switches table view

Server Configuration table view

The Server Configuration table view displays information for each active
configuration parameter. Use this report to view such information as the name of
the configuration parameter, the configuration value, and the maximum and
minimum values for the configuration parameter. This table view displays data
provided by the Configuration attributes.

Chapter 4. Workspaces reference 31

 Server Options table view
The Server Options table view displays detailed information to help you monitor a
selected server. Use this report to view information about the number of current
locks and allowable locks such as the status of the server and the size of the data
and procedure caches. This table view displays data provided by the Server Detail
attributes.

Task Switches
For each server, the Task Switches table view displays information about task
context switches. This report applies only to Sybase Server System 11. This table
view shows the cause of a task context switch and frequency of task context
switch. This table view displays data provided by the Task Detail attributes.

Server Statistics Summary workspace

The Monitoring Agent for Sybase Server provides statistical information about the
servers in your environment. This information includes statistics about the
following:
v SQL activity
v Cache usage
v Transaction log entries

The predefined Server Statistics Summary workspace contains the following views:
v Statistics Summary bar charts (2)
v Statistics Summary table view
v Statistics Detail table view

Statistics Summary Bar Charts

For the current interval, the chart on the left displays the totals per second for
logons and physical reads and writes. The chart on the right displays totals for
active connections or logons, the maximum number of active connections allowed
for the server, the number of times the disk was accessed for reads and writes, the
number of I/O errors for the current interval, and the number of I/O errors that
have occurred since the server started. These bar charts display data provided by
the Statistics Summary attributes.

Statistics Summary table view

The Statistics Summary table view displays a summary of statistical information
for a selected server. For example, it contains statistics for disk I/O, I/O errors,
and disk usage. This table view displays data provided by the Statistics Summary
attributes.

Statistics Detail table view

The Statistics Detail table view displays detailed information about each statistic
for a selected server. For example, it provides the name of the statistic and the
average, current, minimum, and maximum values reported for the statistic. This
table view displays data provided by the Statistics Detail attributes.

Servers workspace
The Monitoring Agent for Sybase Server provides information about server status,
activity, configuration, engine usage, and task usage.

The predefined Servers workspace contains the following views:

v CPU Percent bar chart

32 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 v Cache Utilization bar chart
v Server Summary table view

CPU Percent bar chart

The CPU Percent bar chart compares the amount of CPU being used by the server
with that being used by the operating system and all the user processes. This bar
chart displays data provided by the Server Summary attributes.

Cache Utilization bar chart

The Cache Utilization bar chart compares the number of hits that occurred during
cache searches with the number of misses. This bar chart displays data provided
by the Cache Detail attributes.

Server Summary table view

The Server Summary table view displays summary information about a selected
server. For example, it shows the version of the server, the amount of time that has
passed since the server started, and the percentage of CPU time the server is using
on the host. This table view displays data provided by the Server Summary
attributes. It also provides access to the Server Configuration and Engine Summary
workspaces.

SQL Text workspace

The predefined SQL Text workspace contains the following views:
v Event console
v SQL Text table view

SQL Text table view

The SQL Text table displays identification information and the SQL text of each
active process. This table view displays data provided by the Text attributes.

Sybase Server_ID workspace

The predefined Sybase Server_ID workspace contains the following five bar charts
for the Sybase Server server instance:
v Cache Utilization bar chart
v CPU Percent bar chart
v Errolog Alerts Summary bar chart
v Processes Summary bar chart
v Statistics Summary bar chart

Cache Utilization bar chart

The Cache Utilization bar chart compares the number of cache hits with cache
misses. This bar chart displays data provided by the Server Detail attributes.

CPU Percent bar chart

The CPU Percent bar chart compares the percentage of CPU time being used by
the server with that being used by the operating system and applications. This bar
chart displays data provided by the Server Summary attributes.

Errorlog Alerts Summary bar chart

The Errorlog Alerts Summary bar chart shows the total number of error messages
along with the totals for the current interval, high severity errors, and other errors.
This bar chart displays data provided by the Problem Summary attributes.

Chapter 4. Workspaces reference 33

 Processes Summary bar chart
The Processes Summary bar chart shows the totals for blocked, infected, bad,
stopped, sleeping, and other processes. This bar chart displays data provided by
the Process Summary attributes.

Statistics Summary bar chart

The Statistics Summary bar chart compares the number of reads per second with
the number of writes. This bar chart displays data provided by the Statistics
Summary attributes.

34 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 5. Attributes reference
This chapter contains information about the following topics:
v Overview of attributes
v References for detailed information about attributes
v Descriptions of the attributes for each attribute group included in this
monitoring agent
v Disk space requirements for historical data

About attributes
Attributes are the application properties being measured and reported by the
Monitoring Agent for Sybase Server, such as the amount of memory usage or the
message ID.

Attributes are organized into groups according to their purpose. The attributes in a
group can be used in the following two ways:
v Chart or table views
Attributes are displayed in chart and table views. The chart and table views use
queries to specify which attribute values to request from a monitoring agent.
You use the Query editor to create a new query, modify an existing query, or
apply filters and set styles to define the content and appearance of a view based
on an existing query.
v Situations
You use attributes to create situations that monitor the state of your operating
system, database, or application. A situation describes a condition you want to
test. When you start a situation, the Tivoli Enterprise Portal compares the values
you have assigned to the situation attributes with the values collected by the
Monitoring Agent for Sybase Server and registers an event if the condition is
met. You are alerted to events by indicator icons that appear in the Navigator.

Some of the attributes in this chapter are listed twice, with the second attribute
having a ″(Unicode)″ designation after the attribute name. These Unicode attributes
were created to provide access to globalized data. Use the globalized attribute
names because this is where the monitoring agent is putting the data. If you were
using a previous Candle OMEGAMON® release of this monitoring agent, you
must run the Application Migration Tool to create globalized attributes for your
customized queries, situations, and policies. See the IBM Tivoli Monitoring
Installation and Setup Guide for more information.

More information about attributes

For more information about using attributes and attribute groups, see the IBM
Tivoli Monitoring User’s Guide.

For a list of the attributes groups, a list of the attributes in each attribute group,
and descriptions of the attributes for this monitoring agent, refer to the Attribute
groups and attributes section in this chapter.

© Copyright IBM Corp. 2005 35

Attribute groups and attributes for the Monitoring Agent for Sybase
Server
This monitoring agent contains the following attribute groups, which are listed
alphabetically:
v Cache Detail
v Cache Summary
v Configuration
v Database Detail
v Database Summary
v Device Detail
v Engine Detail
v Engine Summary
v Lock Conflict Detail
v Lock Conflict Summary
v Lock Detail
v Lock Summary
v Locks
v Log Detail
v Log Summary
v Physical Device Detail
v Problem Detail
v Problem Summary
v Process Detail
v Process Summary
v Remote Servers
v Server Detail
v Server Enterprise
v Server Summary
v SQL Detail
v Statistics Detail
v Statistics Summary
v Task Detail
v Text

The following sections contain descriptions of these attribute groups. Each group
contains an alphabetical list of attributes.

Cache Detail attributes

Use cache detail attributes to create situations that monitor detailed information
about named caches.

Cache Hit Count. The number of hits during data cache searches for the current
interval. The value format is an integer, for example, 15000. This value represents a
count of logical reads from the named cache. If cache searches always result in
data being found in cache, this value is 100% of the number of cache searches
performed. Consider increasing the amount of memory allocated to the named
cache if this value is low.

36 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Cache Hit per Transaction. The average number of hits during data cache searches
per transaction for the current interval. The value format is a decimal with two
decimal places allowed, for example, 10.00. This value represents the number of
logical reads per transaction from the named cache. Consider increasing the
amount of memory allocated to the named cache if this value is low.

Cache Hit Percent. The percentage of data cache searches that resulted in hits
during the current interval. The value format is a percentage with two decimal
places allowed, for example, 90.00. This value represents the ratio of logical reads
to the total number of reads for the named cache. If cache searches always result in
data being found in cache, this value is 100%. Consider increasing the amount of
memory allocated to the named cache if this value is low.

Cache Hit Rate. The average number of hits during data cache searches per second
for the current interval. The value format is a decimal with two decimal places
allowed, for example, 75.00. This value represents the number of logical reads per
second from the named cache. Consider increasing the amount of memory
allocated to the named cache if this value is low.

Cache Miss Count. The number of times in the interval that a page was not found
in cache. The value format is an integer, for example, 530.

Cache Miss per Transaction. The average number of misses during data cache
searches for the current interval. The value format is a decimal with two decimal
places allowed, for example, 2.00. This value represents the number of physical
reads per transaction from a database device. The server must perform a physical
read if the data is not found in the named cache. Consider increasing the amount
of memory allocated to the named cache if this value is high.

Cache Miss Percent. The percentage of data cache searches that resulted in misses
where the page was not found during the current interval. The value format is a
percentage with two decimal places allowed, for example, 10.00. This value
represents the ratio of physical reads to the total number of reads for the named
cache. If cache searches never result in data being found in cache, this value is
100%. Consider increasing the amount of memory allocated to the named cache if
this value is high.

Cache Miss Rate. The average number of misses during data cache searches for
the current interval. The value format is a decimal with two decimal places
allowed, for example, 8.00. This value represents the number of physical reads per
second from a database device. If cache searches always result in data being found
in cache, this value is zero. Consider increasing the amount of memory allocated to
the named cache if this value is high.

Cache Name. The server-assigned name for the data cache. The value format is
alphanumeric with a maximum 30 characters, for example, tempdb_cache. The
name is unique. Sybase Server System 11 allows you to use named caches to
improve cache performance.

Cache Name (Unicode). The server-assigned name for the data cache. This
attribute is globalized. The value format is alphanumeric with a maximum 90
bytes, for example, tempdb_cache. The name is unique. You can use Sybase Server
System 11 named caches to improve cache performance.

Cache Search Count. The number of cache searches during the current interval.
The value includes hits and misses. The value format is an integer, for example,

Chapter 5. Attributes reference 37

 240. If cache searches result in hits, the server finds the data in memory and avoids
reading data from database devices. Consider allocating more memory to the
named cache to increase the number of hits.

Cache Search per Transaction. The average number of data cache searches per
transaction during the current interval. The value format is a decimal with two
decimal places allowed, for example, 30.00. If cache searches result in hits, the
server finds the data in memory and avoids reading data from database devices.
Consider allocating more memory to the named cache to increase the number of
hits.

Cache Search Rate. The average number of data cache searches per second during
the current interval. The value format is a decimal with two decimal places
allowed, for example, 25.00. If cache searches result in hits, the server finds the
data in memory and avoids reading data from database devices. Consider
allocating more memory to the named cache to increase the number of hits.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Large IO Denied Count. The number of large I/O requests not performed by the
server during the current interval. The value format is an integer, for example,
10000. The server may deny large I/O requests when any page in a buffer is in
another pool, no buffers are available in the requested pool, and the first extent of
an allocation unit contains the allocation page in the 2K pool. If this value is high,
evaluate individual caches to determine the cause.

Large IO Denied per Transaction. The average number of large I/O requests per
transaction not performed by the server during the current interval. The value
format is a decimal with two decimal places allowed, for example, 2.00. The server
may deny large I/O requests when any page in a buffer is in another pool, no
buffers are available in the requested pool, and the first extent of an allocation unit
contains the allocation page in the 2K pool. If this value is high, evaluate
individual caches to determine the cause.

Large IO Denied Percent. The percentage of large I/O requests not performed by
the server during the current interval. The value format is a percentage with two
decimal places allowed, for example, 20.00. The server may deny large I/O
requests when any page in a buffer is in another pool, no buffers are available in
the requested pool, and the first extent of an allocation unit contains the allocation
page in the 2K pool. If this value is high, evaluate individual caches to determine
the cause.

Large IO Denied Rate. The average number of large I/O requests per second not
performed by the server during the current interval. The value format is a decimal
with two decimal places allowed, for example, 5.00. The server may deny large
I/O requests when any page in a buffer is in another pool, no buffers are available
in the requested pool, and the first extent of an allocation unit contains the
allocation page in the 2K pool. If this value is high, evaluate individual caches to
determine the cause.

Large IO Pages Cached Count. The number of large I/O pages cached during the
current interval. The value format is an integer, for example, 15000.

Large IO Pages Cached per Transaction. The average number of large I/O pages
per transaction cached during the current interval. The value format is a decimal

38 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
with two decimal places allowed, for example, 5.00. This data can be useful for
validating percentage values or in environments where the number of transactions
is well-defined.

Large IO Pages Cached Rate. The average number of large I/O pages per second
cached during the current interval. The value format is a decimal with two decimal
places allowed, for example, 30.00.

Large IO Pages Used Count. The number of large I/O pages used during the
current interval. The value format is an integer, for example, 50000.

Large IO Pages Used per Transaction. The average number of large I/O pages per
transaction used during the current interval. The value format is a decimal with
two decimal places allowed, for example, 100.00.

Large IO Pages Used Percent. The percentage of large I/O requests used by the
server during the current interval. The value format is a percentage with two
decimal places allowed, for example, 30.00. This data can be useful for monitoring
trends.

Large IO Pages Used Rate. The average number of large I/O pages per second
used during the current interval. The value format is a decimal with two decimal
places allowed, for example, 200.00.

Large IO Performed Count. The number of large I/O operations performed during
the current interval. The value format is an integer, for example, 15000. The server
may perform large I/O requests unless any page in a buffer is in another pool, no
buffers are available in the requested pool, and the first extent of an allocation unit
contains the allocation page in the 2K pool. If this value is low, evaluate individual
caches to determine the cause.

Large IO Performed per Transaction. The average number of large I/O requests
per transaction performed during the current interval. The value format is a
decimal with two decimal places allowed, for example, 10.00. The server may
perform large I/O requests unless any page in a buffer is in another pool, no
buffers are available in the requested pool, and the first extent of an allocation unit
contains the allocation page in the 2K pool. If this value is low, evaluate individual
caches to determine the cause.

Large IO Performed Percent. The percentage of large I/O requests performed by

the server during the current interval. The value format is a percentage with two
decimal places allowed, for example, 40.00. The server may perform large I/O
requests unless any page in a buffer is in another pool, no buffers are available in
the requested pool, and the first extent of an allocation unit contains the allocation
page in the 2K pool. If this value is low, evaluate individual caches to determine
the cause.

Large IO Performed Rate. The average number of large I/O requests per second
performed during the current interval. The value format is a decimal with two
decimal places allowed, for example, 20.00. The server may perform large I/O
requests unless any page in a buffer is in another pool, no buffers are available in
the requested pool, and the first extent of an allocation unit contains the allocation
page in the 2K pool. If this value is low, evaluate individual caches to determine
the cause.

Chapter 5. Attributes reference 39

 LRU Buffer Use Count. The number of LRU buffers used during the current
interval. The value format is an integer, for example, 15000.

LRU Buffer Use per Transaction. The average number of LRU buffers used per
transaction during the current interval. The value format is a decimal with two
decimal places allowed, for example, 300.00.

LRU Buffer Use Percent. The percentage of all buffers used during the current
interval that were LRU buffers. The value format is a percentage with two decimal
places allowed, for example, 45.00.

LRU Buffer Use Rate. The average number of LRU buffers used per second during
the current interval. The value format is a decimal with two decimal places
allowed, for example, 15.00.

MRU Buffer Use Count. The number of MRU buffers used during the current
interval. The value format is an integer, for example, 20000.

MRU Buffer Use per Transaction. The average number of MRU buffers per
transaction used during the current interval. The value format is a decimal with
two decimal places allowed, for example, 15.00.

MRU Buffer Use Percent. The percentage of all buffers used during the current
interval that were MRU buffers. The value format is a percentage with two decimal
places allowed, for example, 80.00.

MRU Buffer Use Rate. The average number of MRU buffers per second used
during the current interval. The value format is a decimal with two decimal places
allowed, for example, 15.00.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Cache Summary attributes

Use Cache Summary attributes to create situations that monitor summary
information about named caches.

Cache Hit Count. The number of hits during data cache searches for the current
interval. The value format is an integer, for example, 15000. This value represents a
count of logical reads from the named cache. If cache searches always result in
data being found in cache, this value is 100% of the total cache searches. Consider
increasing the amount of memory allocated to the named cache if this value is low.

Cache Hit per Transaction. The average number of hits during data cache searches
per transaction for the current interval. The value format is a decimal with two
decimal places allowed, for example, 10.00 This value represents the number of
logical reads per transaction from the named cache. Consider increasing the
amount of memory allocated to the named cache if this value is low.

Cache Hit Percent. The percentage of data cache searches that resulted in hits
during the current interval. The value format is a percentage with two decimal

40 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
places allowed, for example, 90.00. This value represents the ratio of logical reads
to the total number of reads for the named cache. If cache searches always result in
data being found in cache, this value is 100%. Consider increasing the amount of
memory allocated to the named cache if this value is low.

Cache Hit Rate. The average number of hits during data cache searches per second
for the current interval. The value format is a decimal with two decimal places
allowed, for example, 75.00. This value represents the number of logical reads per
second from the named cache. Consider increasing the amount of memory
allocated to the named cache if this value is low.

Cache Miss Count. Number of times in the interval that a page was not found in
the cache.

Cache Miss per Transaction. The average number of misses during data cache
searches for the current interval. The value format is a decimal with two decimal
places allowed, for example, 2.00. This value represents the number of physical
reads per transaction from a database device. The server must perform a physical
read if the data is not found in the named cache. Consider increasing the amount
of memory allocated to the named cache if this value is high.

Cache Miss Percent. The percentage of data cache searches that resulted in misses
during the current interval. The value format is a percentage with two decimal
places allowed, for example, 10.00. This value represents the ratio of physical reads
to the total number of reads for the named cache. If cache searches never result in
data being found in cache, this value is 100%. Consider increasing the amount of
memory allocated to the named cache if this value is high.

Cache Miss Rate. The average number of misses during data cache searches for
the current interval. The value format is a decimal with two decimal places
allowed, for example, 8.00. This value represents the number of physical reads per
second from a database device. Consider increasing the amount of memory
allocated to the named cache if this value is high.

Cache Search Count. The number of cache searches during the current interval.
The value includes hits and misses. The value format is an integer, for example,
240. If cache searches result in hits, the server finds the data in memory and avoids
reading data from database devices. Consider allocating more memory to the
named cache to increase the number of hits.

Cache Search per Transaction. The average number of data cache searches per
transaction during the current interval. The value format is a decimal with two
decimal places allowed, for example, 30.00. If cache searches result in hits, the
server finds the data in memory and avoids reading data from database devices.
Consider allocating more memory to the named cache to increase the number of
hits.

Cache Search Rate. The average number of data cache searches per second during
the current interval. The value format is a decimal with two decimal places
allowed, for example, 25.00. If cache searches result in hits, the server finds the
data in memory and avoids reading data from database devices. Consider
allocating more memory to the named cache to increase the number of hits.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Chapter 5. Attributes reference 41

 Large IO Denied Count. The number of large I/O requests not performed by the
server during the current interval. The value format is an integer, for example,
10000. The server may deny large I/O requests when any page in a buffer is in
another pool, no buffers are available in the requested pool, and the first extent of
an allocation unit contains the allocation page in the 2K pool. If this value is high,
evaluate individual caches to determine the cause.

Large IO Denied per Transaction. The average number of large I/O requests per
transaction not performed by the server during the current interval. The value
format is a decimal with two decimal places allowed, for example, 2.00. The server
may deny large I/O request when any page in a buffer is in another pool, no
buffers are available in the requested pool, and the first extent of an allocation unit
contains the allocation page in the 2K pool. If this value is high, evaluate
individual caches to determine the cause.

Large IO Denied Percent. The percentage of large I/O requests not performed by
the server during the current interval. The value format is a percentage with two
decimal places allowed, for example, 20.00. The server may deny large I/O request
when any page in a buffer is in another pool, no buffers are available in the
requested pool, and the first extent of an allocation unit contains the allocation
page in the 2K pool. If this value is high, evaluate individual caches to determine
the cause.

Large IO Denied Rate. The average number of large I/O requests per second not
performed by the server during the current interval. The value format is a decimal
with two decimal places allowed. The server may deny large I/O request when
any page in a buffer is in another pool, no buffers are available in the requested
pool, and the first extent of an allocation unit contains the allocation page in the
2K pool. If this value is high, evaluate individual caches to determine the cause.

Large IO Pages Cached Count. The number of large I/O pages cached during the
current interval. The value format is an integer, for example, 15000.

Large IO Pages Cached per Transaction. The average number of large I/O pages
per transaction cached during the current interval. The value format is a decimal
with two decimal places allowed, for example, 5.00. This data can be useful for
validating percentage values or in environments where the number of transactions
is well-defined.

Large IO Pages Cached Rate. The average number of large I/O pages per second
cached during the current interval. The value format is a decimal with two decimal
places allowed, for example, 30.00.

Large IO Pages Used Count. The number of large I/O pages used during the
current interval. The value format is an integer, for example, 50000.

Large IO Pages Used per Transaction. The average number of large I/O pages per
transaction used during the current interval. The value format is a decimal with
two decimal places allowed, for example, 100.00.

Large IO Pages Used Percent. The percentage of large I/O requests used by the
server during the current interval. The value format is a percentage with two
decimal places allowed, for example, 30.00. This data can be useful for monitoring
trends.

42 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Large IO Pages Used Rate. The average number of large I/O pages per second
used during the current interval. The value format is a decimal with two decimal
places allowed, for example, 200.00.

Large IO Performed Count. The number of large I/O requests performed during
the current interval. The value format is an integer, for example, 15000. The server
may perform large I/O requests unless any page in a buffer is in another pool, no
buffers are available in the requested pool, and the first extent of an allocation unit
the allocation page in the 2K pool. If this value is low, evaluate individual caches
to determine the cause.

Large IO Performed per Transaction. The average number of large I/O requests
per transaction performed during the current interval. The value format is a
decimal with two decimal places allowed, for example, 10.00. The server may
perform large I/O requests unless any page in a buffer is in another pool, no
buffers are available in the requested pool, and the first extent of an allocation unit
contains the allocation page in the 2K pool. If this value is low, evaluate individual
caches to determine the cause.

Large IO Performed Percent. The percentage of large I/O requests performed by

the server during the current interval. The value format is a percentage with two
decimal places allowed, for example, 40.00. The server may perform large I/O
requests unless any page in a buffer is in another pool, no buffers are available in
the requested pool, and the first extent of an allocation unit contains the allocation
page in the 2K pool. If this value is low, evaluate individual caches to determine
the cause.

Large IO Performed Rate. The average number of large I/O requests per second
performed during the current interval. The value format is a decimal with two
decimal places allowed, for example, 20.00. The server may perform large I/O
requests unless any page in a buffer is in another pool, no buffers are available in
the requested pool, and the first extent of an allocation unit contains the allocation
page in the 2K pool. If this value is low, evaluate individual caches to determine
the cause.

LRU Buffer Use Count. The number of least recently used (LRU) buffers used
during the current interval. The value format is an integer, for example, 15000.

LRU Buffer Use per Transaction. The average number of LRU buffers used per
transaction during the current interval. The value format is a decimal with two
decimal places allowed, for example, 300.00.

LRU Buffer Use Percent. The percentage of all buffers used during the current
interval that were LRU buffers. The value format is a percentage with two decimal
places allowed, for example, 45.00.

LRU Buffer Use Rate. The average number of LRU buffers used per second during
the current interval. The value format is a decimal with two decimal places
allowed, for example, 15.00.

MRU Buffer Use Count. The number of most recently used (MRU) buffers used
during the current interval. The value format is an integer, for example, 20000.

MRU Buffer Use per Transaction. The average number of MRU buffers per
transaction used during the current interval. The value format is a decimal with
two decimal places allowed, for example, 15.00.

Chapter 5. Attributes reference 43

 MRU Buffer Use Percent. The percentage of all buffers used during the current
interval that were MRU buffers. The value format is a percentage with two decimal
places allowed, for example, 80.00.

MRU Buffer Use Rate. The average number of MRU buffers per second used
during the current interval. The value format is a decimal with two decimal places
allowed, for example, 15.00.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Configuration attributes
Use the Configuration attributes to create situations that monitor the configuration
of a server.

Config Parameter. The name of the configuration parameter. The value format is
alphanumeric with a maximum 30 characters.
Example: Partition groups.

The sysconfigures and syscurconfigs system tables store the configuration

parameters. Use the parameter name to track the performance of a particular
configuration parameter.

Config Parameter (Unicode). The name of the configuration parameter. This

attribute is globalized. The value format is alphanumeric with a maximum 90
bytes.
Example: Partition groups.

The sysconfigures and syscurconfigs system tables store the configuration

parameters. Use the parameter name to track the performance of a particular
configuration parameter.

Config Value. The value for the configuration parameter. The value format is
alphanumeric with a maximum 12 characters.
Example: 1000

The value was initially specified in the sysconfigures system table. Monitor this
value to track its effect on performance, and to compare the initial setting to the
maximum, minimum, and run values.

Config Value (Unicode). The value for the configuration parameter. This attribute
is globalized. The value format is alphanumeric with a maximum 36 bytes.
Example: 1000

The value was initially specified in the sysconfigures system table. Monitor this
value to track its effect on performance, and to compare the initial setting to the
maximum, minimum, and run values.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

44 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Maximum Value. The maximum value that can be specified for the configuration
parameter. The value format is alphanumeric with a maximum 12 characters, for
example, 2147483647.

Minimum Value. The minimum value that can be specified for the configuration
parameter. The value format is alphanumeric with a maximum 12 characters, for
example, 1.

Parm Type. The type of configuration parameter. The following values are valid:
Dynamic
Configuration parameter is dynamic. Server restart is not required.
Static Configuration parameter is static. Server restart is required.

If the configuration parameter is dynamic, a server restart is not required.

Run Value. The value the server is using for the configuration parameter. The
value format is alphanumeric with a maximum 12 characters, for example, 1000.

Run Value (Unicode). The value the server is using for the configuration
parameter. This attribute is globalized. The value format is alphanumeric with a
maximum 36 bytes, for example, 1000.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Database Detail attributes

Use the Database Detail attributes to create situations that monitor detail
information about databases.

Abort Tran On Log Full. Indicates whether the Abort Tran On Log Full option is
enabled for the database. The following values are valid:
Dynamic
Abort Tran On Log Full option is disabled.
Static Abort Tran On Log Full option is enabled.

Data Freespace. The number of megabytes (MB) of free space in the database. The
value includes the megabytes of free data only and data and log space. The value
format is a decimal with two decimal places allowed, for example, 10.00. When the
transaction log is stored on a separate segment, the database uses a last-chance
threshold to manage free space. Set alerts for abnormal conditions if you are not
using a last-chance threshold to manage free space in the database.

Data Freespace Percent. The percentage of free space in the databases. The value
format is a percentage with two decimal places allowed, for example, 20.00. The
product calculates this percentage from the number of free blocks in the database
and the number of data blocks that are allocated for the database. Consider using
the alter database command to expand the database size.

Chapter 5. Attributes reference 45

 Data Size. The number of megabytes (MB) allocated for the data only and data
and log segments of the database. The value format is a decimal with two decimal
places allowed, for example, 50.00. The database size can range from 2 to 2048
megabytes.

Database Name. The name of the database. The value format is alphanumeric with
a maximum 30 characters. Each database name is unique. The server also assigns
each database its own identification number.

Database Name (Unicode). The name of the database. This attribute is globalized.
The value format is alphanumeric with a maximum 90 bytes. Each database name
is unique. The server also assigns each database its own identification number.

DB ID. The ID for the database. The value format is alphanumeric with a
maximum 12 characters, for example, 2156. This value is stored in the sysdatabases
table.

DB ID (Unicode). The ID for the database. This attribute is globalized. The value
format is alphanumeric with a maximum 36 bytes, for example, 2156. This value is
stored in the sysdatabases table.

DB Owner. The server-assigned user ID for the owner of the database. The value
format is alphanumeric with a maximum 8 characters, for example, DBO. Use the
create database command to establish this identifier.

DB Owner (Unicode). The server-assigned user ID for the owner of the database.
This attribute is globalized. The value format is alphanumeric with a maximum 64
bytes, for example, DBO. Use the create database command to establish this
identifier.

DBO Only Access. Indicates whether the database is set for owner access only.
The following values are valid:
No Database can be accessed by authorized users.
Yes Database can be accessed by owner only.

Dump Tran Date. The time stamp that indicates the date and time the dump
transaction command was last executed for the database. The format is
YY.MM.DD. The following values are valid:
YY Year
MM Month
DD Day

Error Status. Indicates whether the database has an error status. A database with
an error status has a status of suspect, crashed, or recovery. The following values
are valid:
No Database does not have an error status.
Yes Database has an error status.

Check the status bits in the sysdatabases table to determine the cause of the error.
Use the database consistency checker dbcc to verify the database integrity.

46 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Free Space Accounting Suppressed. Indicates whether the free space accounting
option is enabled for the database. The following values are valid:
No Free space accounting is enabled.
Yes Free space accounting is disabled.

The no-free-space-actg option turns off free space accounting on non-log segments
only. Information about free space is inaccurate when free space accounting is
turned off. Use the no-free-space-actg option and the checkpoint command to
speed recovery. No time is needed to count free space for non-log segments.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Log Freespace. The number of megabytes (MB) of free space in the transaction log
for the database. The value includes the number of megabytes of free space on the
log only and data and log partitions. The value format is a decimal with two
decimal places allowed, for example, 2.00. Various types of transactions, such as
mass updates and bulk copying, can involve extensive logging.

Log Freespace Percent. The percentage of free space in the transaction log for the
database. The value format is a percentage with two decimal places allowed, for
example, 20.00. Various types of transactions, such as mass updates and bulk
copying in can involve extensive logging.

Log Size. The number of megabytes (MB) allocated for the transaction log for the
database. The value includes the number of megabytes allocated for the transaction
log on the log only and data and log partitions. The value format is a decimal with
two decimal places allowed, for example, 5.00. The appropriate size for a
transaction log depends on how the database is used. Several factors, such as the
number of transactions, type of transactions, and number of users, effect sizing.
Evaluate the need to truncate the transaction log to prevent it from filling up.

No CKPT After Recovery. Indicates whether a record for the checkpoint is added
to the transaction log when the database is recovered. The following values are
valid:
No No CKPT After Recovery option is disabled.
Yes No CKPT After Recovery option is enabled.

Read Only Access. Indicates whether the database has a status of read-only. The
following values are valid:
No Database is a read and write database.
Yes Database has a status of read only.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Select Into Bulkcopy Enabled. Indicates whether the select into/bulkcopy option
is enabled for the database. The following values are valid:
No Select Into/Bulkcopy option is disabled.
Yes Select Into/Bulkcopy option is enabled.

Chapter 5. Attributes reference 47

 Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Single User Access. Indicates whether the database has a status of single-user. A
database with a status of single-user can only be accessed by one user at a time.
The following values are valid:
No Database can be accessed by multiple users.
Yes Database has a status of single user.

Total Devices. The number of devices allocated for the database. The value format
is an integer in the range 1-128, for example, 4.

Truncate Log on CKPT. Indicates whether the trunc log on CHKPT option is
enabled for the database. The following values are valid:
No Trunc Log On CHKPT option is disabled.
Yes Trunc Log On CHKPT option is enabled.

Database Summary attributes

Use the Database Summary attributes to create situations that monitor summary
information about server databases.

Current Interval. The number of seconds that have elapsed between the previous
sample and the current sample. The value format is an integer, for example, 90. A
sample contains the data that the Monitoring Agent for Sybase Server collects
about each server. New data becomes available if a new interval has occurred and
data has been refreshed.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Minimum Pct Data Freespace. The lowest percentage of free space in data only
and data and log segments on a device allocated to a database. The value format is
a percentage with two decimal places allowed, for example, 5.00. The amount of
space needed by the database depends on its anticipated activity. Set alerts for
abnormal conditions. Evaluate the possibility of adding more space to the
database.

Minimum Pct Log Freespace. The lowest percentage of free space in log only and
data and log segments on a device allocated for the database transaction log. The
value format is a percentage with two decimal places allowed, for example, 5.00.
The amount of space needed by the transaction log depends on the type and
quantity of the transactions and the frequency of backups. Set alerts for abnormal
conditions. Evaluate the possibility of expanding the log.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Total Databases. The number of databases for the server. The value format is an
integer, for example, 10.

48 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Total DBs DBO Only. The number of databases with a status of DBO only. A
database with a status of database owner can be accessed only by users with DBO
authority. The value format is an integer, for example, 5.

Total DBs in Error. The number of databases with an error status. A database with
an error status is a database with a status of suspect, crashed, or recovery. The
value format is an integer, for example, 2.

Total DBs No Free Space Accounting. The number of databases that have the free
space accounting option disabled. The value format is an integer, for example, 5.

Total DBs Read Only. The number of databases with a status of read only. The
value format is an integer, for example, 5.

Total DBs Single User. The number of databases with a status of single user. A
database with a status of single user can be accessed by only one user at a time.
The value format is an integer, for example, 2.

Device Detail attributes

Use the Device Detail attributes to create situations that monitor detail information
about devices.

Database Name. The name of the database. The value format is alphanumeric with
a maximum 30 characters. Each database name is unique. The server also assigns
each database its own identification number.

Database Name (Unicode). The name of the database. This attribute is globalized.
The value format is alphanumeric with a maximum 90 bytes. Each database name
is unique. The server also assigns each database its own identification number.

Device Free Space. The number of megabytes (MB) of free space on a device. The
value format is a decimal with two decimal places allowed, for example, 10.00.
Adequate space is required to support database and system administration
activities. Set alerts for abnormal conditions. Refer to this value when estimating
space needed for tables, indexes, logs, and system administration.

Device Free Space Percent. The percentage of free space on the device. The value
format is a percentage with two decimal places allowed, for example, 15.00.
Adequate space is required to support database and system administration
activities. Set alerts for abnormal conditions. Refer to this value when estimating
space needed for tables, indexes, logs, and system administration.

Device Name. The name of the device allocated for the database. The value format
is alphanumeric with a maximum 30 characters, for example, DATA_1. The logical
name of the device is stored in the name column of the sysdevices table. Use the
device name in storage-management commands.

Device Name (Unicode). The name of the device allocated for the database. This
attribute is globalized. The value format is alphanumeric with a maximum 90
bytes, for example, DATA_1. The logical name of the device is stored in the name
column of the sysdevices table. Use the device name in storage-management
commands.

Chapter 5. Attributes reference 49

 Device Size. The number of megabytes (MB) on the device. The value format is an
integer, for example, 20. The size relates to the number of 2K pages. Use this value
when analyzing the amount of free space.

Device Type. Indicates the type of device allocated for the database. The following
values are valid:
Data only
Device stores data for the database.
Log only
Device stores the transaction log for the database.
Data and log
Device stores data and the transaction log for the database.

The value indicates the type of data that is stored on the device. Databases are
frequently spread across several devices due to size, performance, and
recoverability issues.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Mirror Device Name. The name of the mirror device for the database. The value
format is alphanumeric with a maximum 64 characters, for example, dev/rsd2g.
The mirror device duplicates the contents of a primary device. Refer to the logical
and physical names of the device that is being mirrored.

Mirror Device Name (Unicode). The name of the mirror device for the database.
This attribute is globalized. The value format is alphanumeric with a maximum
192 bytes, for example, dev/rsd2g. The mirror device duplicates the contents of a
primary device. Refer to the logical and physical names of the device that is being
mirrored.

Physical Device Name. The name of the physical device allocated for the database.
The value format is alphanumeric with a maximum 64 characters, for example,
DATA_1. The physical name of the device is stored in the sysdevices table. Use the
physical name only with the Sybase Server disk init command.

Physical Device Name (Unicode). The name of the physical device allocated for
the database. This attribute is globalized. The value format is alphanumeric with a
maximum 192 bytes, for example, DATA_1. The physical name of the device is
stored in the sysdevices table. Use the physical name only with the Sybase Server
disk init command.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Server Version. The version of the server. The value format is the version in the
format version.release, for example, 11.9.

50 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Engine Detail Attributes
Use the Engine Detail attributes to create situations that monitor detail information
about server engines.

Completed Disk Io Count. The number of accesses to disk completed during the
sampling period. The value format is an integer, for example, 120.

CPU Available Percent. The percentage of time the server was not busy executing
tasks during the sampling period. The value format is a percentage with two
decimal places allowed, for example, 20.00. This data can be useful for monitoring
trends.

CPU Busy Percent. The percentage of time the server was busy executing tasks
during the sampling period. The value format is a percentage with two decimal
places allowed, for example, 80.00. This data can be useful for monitoring trends.

CPU Yields Count. The number of yields by the server engine to the operating
system. The value format is an integer, for example, 10.

CPU Yields Per Second. The average number of yields by the server engine to the
operating system per second during the sampling period. The value format is a
decimal with two decimal places allowed, for example, 10.00.

CPU Yields Per Transaction. The average number of yields by the server engine to
the operating system per transaction during the sampling period. The value format
is a decimal with two decimal places allowed, for example, 10.00. This data can be
useful for validating percentage values or in environments where the number of
transactions is well-defined.

CPU Yields Percent. The percentage of server engine yields represented by the
specified engine. The value format is a percentage with two decimal places
allowed, for example, 25.00. This data can be useful for monitoring trends.

Current Interval. The number of seconds in the sampling period. the value format
is an integer, for example, 120.

Engine Name. The name of the operating system process running on a CPU for a
server. The value format is alphanumeric with a maximum 10 characters, as in this
example: engine 0.

Engine Name (Unicode). The name of the operating system process running on a
CPU for a server. This attribute is globalized. The value format is alphanumeric
with a maximum 90 bytes, as in this example: engine 0.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, voyager.

Maximum Outstanding IO Count. The number of accesses to disk pending

processing during the sampling period. The value format is an integer, for
example, 20.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. a sample is the data the product collects about
the server.

Chapter 5. Attributes reference 51

 Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, Cfs_Svr5.

Task Switch Count. The number of changes by the server from one user task to
another during the sampling period. The value format is an integer, for example,
50.

Task Switch Per Transaction. The average number of task context switches per
transaction performed by the server during the sampling period. The value format
is a decimal with two decimal places allowed, for example, 30.00.

Task Switch Percent. The percentage of total CPU switches that this engine did
between threads (user tasks). The value format is a percentage with two decimal
places allowed, for example, 15.00.

Task Switch Per Second. The average number of task switches performed by the
server per second during the sampling period. The value format is a decimal with
two decimal places allowed, for example, 25.00.

TDS Bytes Received Count. The number of bytes the engine received during the
sampling period. The value format is an integer, for example, 1500.

Tds Bytes Received Per Second. The average number of bytes the engine received
per second during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 750.00.

TDS Bytes Received Per Transaction. The average number of bytes the engine
received per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 350.00. This data can be useful for
validating percentage values or in environments where the number of transactions
is well-defined.

TDS Bytes Received Percent. The percentage of tds bytes that were received by
the engine. The value format is a percentage with two decimal places allowed, for
example, 75.00. This data can be useful for monitoring trends.

TDS Bytes Sent Count. The number of bytes sent by the engine during the
sampling period. The value format is an integer, for example, 6000.

TDS Bytes Sent Per Second. The average number of bytes the engine sent per
second during the sampling period. The Value format is a decimal with two
decimal places allowed, for example, 150.00.

TDS Bytes Sent Per Transaction. The average number of bytes the engine sent per
transaction during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 250.00. this data can be useful for monitoring
trends.

TDS Bytes Sent Percent. The percentage of tds bytes that were sent by the engine.
The value format is a percentage with two decimal places allowed, for example,
40.00. This data can be useful for monitoring trends.

TDS Packets Received Count. The number of packets the engine received during
the sampling period. The value format is an integer, for example, 90.

52 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 TDS Packets Received Per Second. The average number of packets the engine
received per second during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 45.00.

TDS Packets Received Per Transaction. The average number of packets the engine
received per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 50.00. This data can be useful for
validating percentage values in environments where the number of transactions is
well-defined.

TDS Packets Received Percent. The percentage of tds packets that were received
by the engine. The value format is a percentage with two decimal places allowed,
for example, 30.00. This data can be useful for monitoring trends.

TDS Packets Sent Count. The number of packets sent by the engine during the
sampling period. The value format is an integer, for example, 60.

TDS Packets Sent Per Second. The average number of packets the engine sent per
second during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 40.00.

TDS Packets Sent Per Transaction. The average number of packets the engine sent
per transaction during the sampling period. The value format is a decimal with
two decimal places allowed, for example, 25.00. This data can be useful for
validating percentage values or in environments where the number of transactions
is well-defined.

TDS Packets Sent Percent. The percentage of tds packets that were sent by the
engine. The value format is a decimal with two decimal places allowed, for
example, 40.00. This data can be useful for monitoring trends.

Total Transactions. The number of transactions the server completed during the
sampling period. The value format is an integer, for example, 50.

Engine Summary attributes

Use the Engine Summary attributes to create situations that monitor summary
information about server engines.

Completed Disk IO Count. The number of accesses to disk completed during the
sampling period. The value format is an integer, for example, 120.

CPU Available Percent. The percentage of time the server was not busy executing
tasks during the sampling period. The value format is a percentage with two
decimal places allowed, for example, 20.00. This data can be useful for monitoring
trends.

CPU Busy Percent. The percentage of time the server was busy executing tasks
during the sampling period. The value format is a percentage with two decimal
places allowed, for example, 80.00. This data can be useful for monitoring trends.

CPU Yields Count. The number of yields by the server engine to the operating
system. The value format is an integer, for example, 10.

Current Interval. The number of seconds in the sampling period. The value format
is an integer, for example, 120.

Chapter 5. Attributes reference 53

 Engine Count. The number of engines enabled for the server. The value format is
an integer in the range 1-32, for example, 1. The number of engines should not
exceed the number of CPUs.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Maximum Outstanding IO Count. The number of accesses to disk pending

processing during the sampling period. The value format is an integer, for
example, 20.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Task Switch Count. The number of changes by the server from one user task to
another during the sampling period. The value format is an integer, for example,
50.

TDS Bytes Received Count. The number of bytes the engine received during the
sampling period. The value format is an integer, for example, 1500.

TDS Bytes Sent Count. The number of bytes sent by the engine during the
sampling period. The value format is an integer, for example, 6000.

TDS Packets Received Count. The number of packets the engine received during
the sampling period. The value format is an integer, for example, 90.

TDS Packets Sent Count. The number of packets sent by the engine during the
sampling period. The value format is an integer, for example, 60.

Total Transactions. The number of transactions the server completed during the
sampling period. The value format is an integer, for example, 50.

Lock Conflict Detail attributes

Use the Lock Conflict Detail attributes to create situations that monitor detail
information about a selected lock conflict.

Blocking Process ID. The identifier for the process that is blocking a request for a
lock. The value format is alphanumeric with a maximum 4 characters, for example,
12. Some blocking processes can become stranded. Investigate situations in which a
process is being blocked for an extended period of time. For more information on a
blocking process, query the sysprocesses and use the sp-lock system procedure.

Database ID. Identification number of the database.

Database Name. The name of the database. The value format is alphanumeric with
a maximum 30 characters, for example, KOY3. Each database name is unique. The
server also assigns each database its own identification number.

Database Name (Unicode). Name of the database. This attribute is globalized. The
value format is alphanumeric with a maximum of 90 bytes.

54 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Requestor Process ID. The ID of the blocked process that is requesting the lock.
The value format is alphanumeric with a maximum 16 characters, for example, 21.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 32 characters, for example, CFS_SVR5.

Server User ID (Unicode). Identification for the user of the server. This attribute is
globalized. The value format is alphanumeric with a maximum of 24 bytes.

Time Blocked. If the process is being blocked, the number of seconds that the
process has been blocked. The value format is an integer, for example, 30.

Lock Conflict Summary attributes

Use the Lock Conflict Summary attributes to create situations that monitor
summary information about lock conflict for a server.

Avg Time Blocked. Average time blocked in seconds. The value format is an
integer, for example, 30.

Database Max Blocks. Name of database that is blocking the largest number of
processes. The value format is alphanumeric with a maximum 32 characters, for
example, DB0999.

Database Max Locks. Name of database with the largest number of locks. The
value format is alphanumeric with a maximum 32 characters, for example, DB3365.

Max Time Blocked. Maximum time blocked in seconds. The value format is an
integer, for example, 70.

Percent Process Block. Percentage of the total processes in conflict. The value
format is an integer, for example, 10.

Table Max Locks. Name of table with the largest number of locks. The value
format is alphanumeric with a maximum 32 characters, for example, TB89375.

Total Locks. Number of locks in this server. The value format is an integer, for
example, 5.

Total Lock Conflicts. Number of processes involved in lock conflicts. The value
format is an integer, for example, 2.

Lock Detail attributes

Use the Lock Detail attributes to create situations that monitor detail information
about lock contention by lock type.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Chapter 5. Attributes reference 55

 Lock Contention Count. The number of requests waiting for locks on resources to
be released during the sampling period. The value format is an integer, for
example, 40.

Lock Contention per Second. The average number of lock requests per second
waiting for locks on resources to be released during the sampling period. The
value format is a decimal with two decimal places allowed, for example, 10.00.

Lock Contention per Transaction. The average number of requests per transaction
waiting for locks on resources to be released during the sampling period. The
value format is a decimal with two decimal places allowed, for example, 2.00.

Lock Contention Percent. The percentage of requests waiting for locks on

resources to be released during the sampling period. The value format is a
percentage with two decimal places allowed, for example, 20.00. This data can be
useful for monitoring trends.

Lock Deadlocked Count. The number of deadlocks during the current interval.
The value format is an integer, for example, 25.

Lock Deadlocked per Second. The average number of deadlocks per second
during the current interval. The value format is a decimal with two decimal places
allowed, for example, 1.00.

Lock Deadlocked per Transaction. The average number of deadlocks per

transaction during the current interval. The value format is a decimal with two
decimal places allowed, for example, 1.00. This data can be useful for validating
percentage values or in environments where the number of transactions is
well-defined.

Lock Deadlocked Percent. The percentage of lock requests that resulted in

deadlocks during the current interval. The value format is a percentage with two
decimal places allowed, for example, 15.00. This data can be useful for monitoring
trends.

Lock Granted Count. The number of processes that acquired locks on resources
during the sampling period. The value format is an integer, for example, 200.

Lock Granted per Second. The average number of processes per second that
acquired locks on resources during the sampling period. The value format is a
decimal with two decimal places allowed, for example, 25.00.

Lock Granted per Transaction. The average number of processes per transaction
that acquired locks on resources during the sampling period. The value format is a
decimal with two decimal places allowed, for example, 5.00. This data can be
useful for validating percentage values or in environments where the number of
transactions is well-defined.

Lock Granted Percent. The percentage of lock requests granted during the current
interval. The value format is a percentage with two decimal places allowed, for
example, 15.00.

Lock Total Count. The number of requests for the specified lock type during the
sampling period. The value format is an integer, for example, 150.

56 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Lock Total per Second. The average number of lock requests of the specified type
per second during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 25.00.

Lock Total per Transaction. The average number of lock requests of the specified
type per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 3.00. This data can be useful for
validating percentage values or in environments where the number of transactions
is well-defined.

Lock Total Percent. The percentage of lock requests represented by the specified
lock type. The value format is a percentage with two decimal places allowed, for
example, 15.00. This data can be useful for monitoring trends.

Lock Type. If the process is being blocked, indicates the type of lock on the
resource that is being requested. The following values are valid:
Excl intent lock
Exclusive intent lock
Excl page lock
Exclusive page lock
Excl tbl lock
Exclusive table lock
Shr -- intent lock
Shared intent lock
Shr -- page lock
Shared page lock
Shr -- tbl lock
Shared table lock
Unknown
Unknown type
Update -- page lock
Update page lock

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Lock Summary attributes

Use the Lock Summary attributes to create situations that monitor summary
information about lock contention for a server.

Deadlocks Count. The number of deadlocks for the server during the current
interval. The value format is an integer, for example, 5.

Deadlocks per Second. The average number of deadlocks per second during the
current interval. The value format is a decimal with two decimal places allowed,
for example, 10.00.

Chapter 5. Attributes reference 57

 Deadlocks per Transaction. The average number of deadlocks per transaction
during the sampling period. The value format is a decimal with two decimal
places allowed, for example, 3.00. This data can be useful for validating percentage
values or in environments where the number of transactions is well-defined.

Deadlocks Percent. The percentage of lock requests that resulted in deadlocks for
the server during the sampling period. The value format is a percentage with two
decimal places allowed. This data can be useful for monitoring trends.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Lock Contention Count. The number of requests waiting for locks on resources to
be released during the sampling period. The value format is an integer, for
example, 40.

Lock Contention per Second. The average number of lock requests per second
waiting for locks on resources to be released during the sampling period. The
value format is a decimal with two decimal places allowed, for example, 10.00.

Lock Contention per Transaction. The average number of requests per transaction
waiting for locks on resources to be released during the sampling period. The
value format is a decimal with two decimal places allowed, for example, 2.00.

Lock Contention Percent. The percentage of requests waiting for locks on

resources to be released during the sampling period. The value format is a
percentage with two decimal places allowed, for example, 20.00. This data can be
useful for monitoring trends.

Lock Promotes Count. The number of lock promotions during the sampling
period. The value includes the number of exclusive lock promotions and shared
lock promotions. The value format is an integer, for example, 20.

Lock Promotes Exclusive Count. The number of locks promoted from exclusive
page locks to exclusive table locks for the server during the sampling period. The
value format is an integer, for example, 5.

Lock Promotes Exclusive per Second. The average number of exclusive lock
promotions per second for the server during the sampling period. The value
format is a decimal with two decimal places allowed, for example, 2.00.

Lock Promotes Exclusive per Transaction. The average number of exclusive lock
promotions per transaction for the server during the sampling period. The value
format is a decimal with two decimal places allowed, for example, 5.00. This data
can be useful for validating percentage values or in environments where the
number of transactions is well-defined.

Lock Promotes Exclusive Percent. The percentage of exclusive page locks

promoted to exclusive table locks by the server during the sampling period. The
value format is a percentage with two decimal places allowed, for example, 5.00.
This data can be useful for monitoring trends.

Lock Promotes per Second. The average number of lock promotions per second
during the sampling period. The value includes the number of exclusive lock
promotions and shared lock promotions. The value format is a decimal with two
decimal places allowed, for example, 2.00.

58 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Lock Promotes per Transaction. The average number of lock promotions per
transaction during the sampling period. The value includes the number of
exclusive lock promotions and shared lock promotions. The value format is a
decimal with two decimal places allowed, for example, 3.00.

Lock Promotes Shared Count. The number of locks promoted from shared page
locks to shared table locks for the server during the sampling period. The value
format is an integer, for example, 40. This data can be useful for monitoring trends.

Lock Promotes Shared per Second. The average number of shared lock
promotions per second for the server during the sampling period. The value
format is a decimal with two decimal places allowed, for example, 20.00.

Lock Promotes Shared per Transaction. The average number of shared lock
promotions per transaction for the server during the sampling period. The value
format is a decimal with two decimal places allowed, for example, 15.00. This data
can be useful for validating percentage values or in environments where the
number of transactions is well-defined.

Lock Promotes Shared Percent. The percentage of shared page locks promoted to
shared table locks by the server during the sampling period. The value format is a
percentage with two decimal places allowed, for example, 25.00. This data can be
useful for monitoring trends.

Lock Request Count. The number of request for locks on resources during the
sampling period. The value format is an integer, for example, 20.

Lock Request per Second. The average number of requests for locks on resources
per second during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 10.00.

Lock Request per Transaction. The average number of requests for locks on
resources per transaction during the sampling period. The value format is a
decimal with two decimal places allowed, for example, 2.00. This data can be
useful for validating percentage values or in environments where the number of
transactions is well-defined.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Locks attributes
Use Locks attributes to create situations that monitor summary information about
locks and lock conflicts.

CClass. The name of the cursor associated with a lock. The value format is
alphanumeric with a maximum 30 characters, for example, fetch.

CClass (Unicode). The name of the cursor associated with a lock. This attribute is
globalized. The value format is alphanumeric with a maximum 90 bytes, for
example, fetch.

Chapter 5. Attributes reference 59

 Database ID. The ID for the database that is locked. The value format is
alphanumeric with a maximum 12 characters, for example, 2156. This value is
stored in the sysdatabases table.

Database Name. The name of the database that is locked. The value format is
alphanumeric with a maximum 30 characters, for example, KOY3. Each database
name is unique. The server also assigns each database its own identification
number.

Database Name (Unicode). The name of the database that is locked. This attribute
is globalized. The value format is alphanumeric with a maximum 36 bytes, for
example, KOY3. Each database name is unique. The server also assigns each
database its own identification number.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Page Number. If the type of lock on the resource is a page lock, the number of the
page that is locked. The value format is alphanumeric with a maximum 12
characters, for example, 761. The server applies different types of page locks. The
types are shared, exclusive, and update. Investigate situations in which a process is
being blocked for an extended period of time.

Process Holding Lock. The numeric identifier of the process holding a lock. The
value format is an integer, for example, 0056.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 32 characters, for example, CFS_SVR5.

Table Name. If the type of lock on the resource is a table lock, the name of the
table that is locked. The value format is alphanumeric with a maximum 16
characters, for example, Employee.

Table Name (Unicode). If the type of lock on the resource is a table lock, the name
of the table that is locked. This attribute is globalized. The value format is
alphanumeric with a maximum 48 bytes, for example, Employee.

Type. If the process is being blocked, indicates the type of lock on the resource that
is being requested. The following values are valid:
Blocking exclusive table
Blocking exclusive table lock
Blocking update extent
Blocking update extent lock
Exclusive extent
Exclusive extent lock
Excl intent lock
Exclusive intent lock
Excl page lock
Exclusive page lock

60 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Excl tbl lock
Exclusive table lock
Next extent
Next extent lock
Previous extent
Previous extent lock
Shr intent lock
Shared intent lock
Shr page lock
Shared page lock
Shr tbl lock
Shared table lock
Unknown
Unknown type
Update extent
Update extent lock
Update page lock
Update page lock

Log Detail attributes

Use Log Detail attributes to create situations that monitor detail information about
log activities.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Log Activity Count. The number of times the log cache activity occurred during
the sampling period. The value format is an integer, for example, 15.

Log Activity Name. The name of the log cache activity, such as cache flushes, locks
granted, locks waited, and so on. The value format is alphanumeric with a
maximum 32 characters, as in this example: locks waited.

Log Activity per Second. The average number of occurrences of the log cache
activity per second during the sampling period. The value format is a decimal with
two decimal places allowed, for example, 1.00.

Log Activity per Transaction. The average number of occurrences of the log cache
activity per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 1.00. This data can be useful for
validating percentage values or in environments where the number of transactions
is well-defined.

Log Activity Percent. The percentage of log cache activity represented by the
specified activity. The value format is a percentage with two decimal places
allowed, for example, 15.00. This data can be useful for monitoring trends.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Chapter 5. Attributes reference 61

 Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Log Summary attributes

Use the Log Summary attributes to create situations that monitor summary
information about the transaction log for a database.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Log Semaphore Requests Count. The number of requests waiting for locks on
resources to be released during the sampling period. The value format is an
integer, for example, 40.

Maximum Private Log Cache Size. The maximum size in kilobytes (KB) of any
private log cache. The value format is an integer, for example, 500.

PLC Semaphore Requests Count. The number of Private Log Cache (PLC
)semaphore requests during the sampling period. The value includes requests
granted and waited. The value format is an integer, for example, 100. This value
measures contention for the log semaphore of the current page in cache. Use this
value to monitor transaction log semaphore activity.

Private Log Cache Flushes Count. The number of private log cache flushes during
the sampling period. The value includes private log cache flushes for any reason.
The value format is an integer, for example, 15. The server reduces transaction log
contention by accumulating log entries in private areas of memory until the private
log cache is full. If necessary, increase the user log cache size to decrease the
number of private log cache flushes.

Private Log Cache Log Records Count. The number of pages for private log
caches during the sampling period. The value format is an integer, for example,
500.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format alphanumeric with a maximum
30 characters, for example, CFS_SVR5.

Transaction Log Allocates Count. The number of page allocations to the

transaction log during the sampling period. The value format is an integer, for
example, 55.

Transaction Log Writes Count. The number of transaction log writes to disk
during the sampling period. The value format is an integer, for example, 150. The
server writes a transaction log page to disk after the current page is full or the
transaction commits. Use this value to evaluate transaction log activity.

Physical Device Detail attributes

Use the Physical Device Detail attributes to create situations that monitor a server
physical device.

62 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Device Lock Contention Count. The number of requests waiting for locks on
resources to be released during the sampling period. The value format is an
integer, for example, 40.

Device Lock Contention per Second. The average number of lock requests per
second waiting for locks on resources to be released during the sampling period.
The value format is a decimal with two decimal places allowed, for example, 10.00.
If contention exists on a device, consider redistributing data on physical devices.

Device Lock Contention per Transaction. The average number of requests per
transaction waiting for locks on resources to be released during the sampling
period. The value format is a decimal with two decimal places allowed, for
example, 2.00. This data can be useful for validating percentage values or in
environments where the number of transactions is well-defined. If contention exists
on a device, consider redistributing data on physical devices.

Device Lock Contention Percent. The percentage of requests waiting for locks on
resources to be released during the sampling period. The value format is a
percentage with two decimal places allowed, for example, 20.00. This data can be
useful for monitoring trends. If contention exists on a device, consider
redistributing data on physical devices.

Device Lock Granted Count. The number of requests for locks on the device
granted during the sampling period. The value format is an integer, for example,
50.

Device Lock Granted per Second. The average number of requests for locks on
the device granted per second during the sampling period. The value format is a
decimal with two decimal places allowed, for example, 15.00.

Device Lock Granted per Transaction. The average number of requests for locks
on the device granted per transaction during the sampling period. The value
format is a decimal with two decimal places allowed, for example, 1.00. This data
can be useful for validating percentage values or in environments where the
number of transactions is well-defined. If contention exists on a device, consider
redistributing data on physical devices.

Device Lock Granted Percent. The percentage of requests for locks on the device
the server granted during the sampling period. The value format is a percentage
with two decimal places allowed, for example, 25.00. This data can be useful for
monitoring trends.

Device Name. The name of the device allocated for the database. The value format
is alphanumeric with a maximum 30 characters, for example, DATA_1. The logical
name of the device is stored in the name column of the sysdevices table. Use the
device name in storage-management commands.

Device Reads Count. The number of physical reads from the device during the
sampling period. The value format is an integer, for example, 25. This data
provides information about disk I/O distribution patterns over devices. Use this
information to evaluate disk I/O usage.

Device Reads per Second. The average number of physical reads from the device
per second during the sampling period. The value format is a decimal with two

Chapter 5. Attributes reference 63

 decimal places allowed, for example, 2.00. This data provides information about
disk I/O distribution patterns over devices. Use this information to evaluate disk
I/O usage.

Device Reads per Transaction. The average number of physical reads from the
device per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 10.00. This data provides
information about disk I/O distribution patterns over devices. Use this information
to evaluate disk I/O usage.

Device Reads Percent. The percentage of reads that occurred on the specified
device during the sampling period. The value format is a percentage with two
decimal places allowed, for example, 10.00. This data provides information about
disk I/O distribution patterns over devices. This information can be useful for
monitoring trends. Use this information to evaluate disk I/O usage.

Device Total Count. The number of devices. The value format is an integer, for
example, 4. This data provides information about disk I/O distribution patterns
over devices. Use this information to evaluate disk I/O usage.

Device Total per Second. The average amount of reads and writes on the device
per second during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 30.00. This data provides information about
disk I/O distribution patterns over devices. Use this information to evaluate disk
I/O usage.

Device Total per Transaction. The average amount of reads and writes on the
device per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 5.00. This data provides information
about disk I/O distribution patterns over devices. Use this information to evaluate
disk I/O usage.

Device Total Percent. The percentage of reads and writes that occurred on the
specified device during the sampling period. The value format is a percentage with
two decimal places allowed, for example, 30.00. This data provides information
about disk I/O distribution patterns over devices. This information can be useful
for monitoring trends. Use this information to evaluate disk I/O usage.

Device Writes Count. The number of physical writes to the device during the
sampling period. The value format is an integer, for example, 40. This data
provides information about disk I/O distribution patterns over devices. Use this
information to evaluate disk I/O usage.

Device Writes per Second. The average number of physical writes to the device
per second during the sampling period. The value format is a decimal with two
decimal places allowed, for example, 5.00. This data provides information about
disk I/O distribution patterns over devices. Use this information to evaluate disk
I/O usage.

Device Writes per Transaction. The average number of physical writes to the
device per transaction during the sampling period. The value format is a decimal
with two decimal places allowed, for example, 10.00. This data provides
information about disk I/O distribution patterns over devices. Use this information
to evaluate disk I/O usage.

64 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Device Writes Percent. The percentage of writes that occurred on the specified
device during the sampling period. The value format is a percentage with two
decimal places allowed, for example, 15.00. This data provides information about
disk I/O distribution patterns over devices. This information can be useful for
monitoring trends. Use this information to evaluate disk I/O usage.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Physical Name. The path name of the database physical device. The value format
is alphanumeric with a maximum 80 characters, for example, /dev/CORPDB_DEV.
The physical name of the device is stored in the sysdevices table. Use the physical
name only with the disk init command.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Problem Detail attributes

Error ID. The ID of the error message. The value format is an integer, for example,
2520. The unnumbered errors with text explanations are written to the server
message logs.

Error ID (Unicode). The ID of the error message. This attribute is globalized. The
value format is alphanumeric with a maximum of 36 bytes, for example, MES2520.
The unnumbered errors with text explanations are written to the server message
logs.

Use the Problem Detail attributes to create situations that monitor detail
information about a selected error.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Hub Timestamp. The time stamp that indicates the time when this data was
inserted at the hub.

Maximum Severity. The level of highest severity encountered since the server
started. The value format is an integer in the range 10-24, for example, 22. Errors
with a severity level of 17 or greater are fatal errors. Monitor this value to track
current messages.

Message Age. The number of minutes that have elapsed since the error occurred.
The value format is an integer, for example, 2. Monitor this value to track current
messages.

Message Issuer. The source of the error message. The value format is
alphanumeric with a maximum 8 characters, for example, JSMITH.

Message Issuer (Unicode). The source of the error message. This attribute is
globalized. The value format is alphanumeric with a maximum 24 bytes, for
example, JSMITH.

Chapter 5. Attributes reference 65

 Message Timestamp. The time stamp that indicates the date and time the error
occurred.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Severity Level. Indicates the severity level of the error. The following values are
valid:
10-16 User error
17-18 Software error or hardware error
19-24 System error

SQL State Code. The state value for the error message. The value format is an
integer, for example, 37.

Problem Summary attributes

Use the Problem Summary attributes to create situations that monitor summary
information about server errors.

Age of Last Error. The number of minutes that have elapsed since the last error
message occurred. The value format is an integer, for example, 2.

Current Interval. The number of seconds that have elapsed between the previous
sample and the current sample. The value format is an integer, for example, 90. A
sample contains the data that the Monitoring Agent for Sybase Server collects
about each server. New data becomes available if a new interval has occurred and
data has been refreshed.

Error Log Size. The number of bytes in the error log file. The value format is an
integer, for example, 50000.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Maximum Sev Current Interval. The error message of the highest severity level
encountered during the current interval. The value format is an integer in the
range 10-24, for example, 19.

Maximum Sev Level. The level of highest severity encountered since the server
started. The value format is an integer in the range 10-24, for example, 22.

Maximum Sev Timestamp. The time stamp that indicates the highest severity.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

66 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Total Error Messages. The number of error messages that have occurred since the
server was started. The value format is an integer, for example, 3.

Total Errors Current Interval. The number of error messages that occurred during
the current interval. The value format is an integer, for example, 1.

Total Errors High Sev. The number of error messages with a severity level of 17 or
higher that have occurred since the server was started. The value format is an
integer, for example, 2.

Total Errors Other. The number of error messages with a severity level of less than
17 that have occurred since the server was started. The value format is an integer,
for example, 3.

Process Detail attributes

Use the Process Detail attributes to create situations that monitor detail information
about a selected server process.

Blocking Process ID. The identifier for the process that is blocking a request for a
lock. The value format is alphanumeric with a maximum 8 characters, for example,
12. Some blocking processes can become stranded. Investigate situations in which a
process is being blocked for an extended period of time. For more information on a
blocking process, query the sysprocesses and use the sp-lock procedure.

Blocking Process ID (Unicode). The identifier for the process that is blocking a
request for a lock. This attribute is globalized. The value format is alphanumeric
with a maximum 24 bytes. Some blocking processes can become stranded.
Investigate situations in which a process is being blocked for an extended period of
time. For more information on a blocking process, query the sysprocesses and use
the sp-lock procedure.

Client Group ID. The group ID of the user executing the process. The value
format is alphanumeric with a maximum 8 characters, for example, ACCT_1.

Client Group ID (Unicode). The group ID of the user executing the process. This
attribute is globalized. The value format is alphanumeric with a maximum 24
bytes, for example, ACCT_1.

Client Host Name. The name of the host for the client. The value format is
alphanumeric with a maximum 16 characters, for example, Rocket.

Client Process ID. The ID the client assigned to the process. The value format is
alphanumeric with a maximum 16 characters, for example, amc_2236.

Client Process ID (Unicode). The ID the client assigned to the process. This
attribute is globalized. The value format is alphanumeric with a maximum 48
bytes, for example, amc_2236.

Client User ID. The ID of the user executing the process. The value format is
alphanumeric with a maximum 8 characters, for example, J_Kelly.

Client User ID (Unicode). The ID of the user executing the process. This attribute
is globalized. The value format is alphanumeric with a maximum 48 bytes, for
example, J_Kelly.

Chapter 5. Attributes reference 67

 Command. The name of the command being executed by the process. The value
format is alphanumeric with a maximum 16 characters, for example, CREATE VIEW.

Command (Unicode). The name of the command being executed by the process.
This attribute is globalized. The value format is alphanumeric with a maximum 48
bytes, for example, CREATE VIEW.

Current CPU Percent Used. The percentage of CPU time the process is using on
the operating system. The value format is a percentage with two decimal places
allowed, for example, 80.00. This dynamic information is from the sysprocesses
table. Set alerts for processes using an abnormal amount of CPU.

Database Name. The name of the database. The value format is alphanumeric with
a maximum 30 characters, for example, KOY3. Each database name is unique. The
server also assigns each database its own identification number.

Database Name (Unicode). The name of the database. This attribute is globalized.
The value format is alphanumeric with a maximum 90 bytes, for example, KOY3.
Each database name is unique. The server also assigns each database its own
identification number.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Login Name. The name of the process. The value format is alphanumeric with a
maximum 30 characters, for example, PROC.

Login Name (Unicode). The process name. This attribute is globalized. The value
format is alphanumeric with a maximum 90 bytes.

Network Packet Size. The number of bytes allocated for the network packet for
the process. The value format is an integer in the range 512-424288, for example,
1024. The default size is 512 bytes. The memory required for each connection is the
equivalent of three times the network packet size. If you increase the network
packet size, confirm that configuration settings for memory and user connections
provide sufficient memory for the server.

OS Process ID. The ID the operating system assigned to the process. The value
format is alphanumeric with a maximum 10 characters, for example, 35427. This
value is from the sysengines table.

Process ID. The ID of the process that is requesting or holding the lock on the
resource. The value format is alphanumeric with a maximum 4 characters, for
example, 42168.

Process Status. Indicates the status of the process. The following values are valid:
Alarm sleep
Process is waiting for an alarm.
Background
Process is a Sybase Server process.
Bad status
Process has errors.
Infected
Process is infected.

68 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Lock sleep
Process is waiting for a lock to be released.
Log suspend
Process is suspended by the log transaction.
Recv sleep
Process is waiting for a network read.
Runnable
Process is in the queue.
Running
Process is running.
Sleeping
Process is sleeping.
Stopped
Process is stopped.
Send sleep
Process is waiting on a network send.

Program Name. The name of the program (front-end module) for the process. The
value format is alphanumeric with a maximum 8 characters, for example, ISQL.

Program Name (Unicode). The name of the program (front-end module) for the
process. This attribute is globalized. The value format is alphanumeric with a
maximum 48 bytes, for example, ISQL.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 32 characters, for example, CFS_SVR5.

Server User Name. The server-assigned ID for the user executing the process. The
value format is alphanumeric with a maximum 8 characters, for example, S.

Server User Name (Unicode). The server-assigned ID for the user executing the
process. This attribute is globalized. The value format is alphanumeric with a
maximum 64 bytes, for example, S.

Time Blocked. If the process is being blocked, the number of seconds that the
process has been blocked. The value format is an integer, for example, 30.

Total CPU Time. The amount of CPU time, in seconds, the process has used on the
host since the process started. The value format is an integer, for example, 60. This
value is based on the statistics collected by the server. Use this value to check for
processes that use abnormal amounts of CPU time.

Total Disk IO. The number of accesses to hard drive since the process started. The
value includes accesses to hard drive for physical reads and physical writes. The
value format is an integer, for example, 10.

Total Memory Alloc. The number of kilobytes (KB) of memory allocated for the
process. The value format is an integer, for example, 500.

Chapter 5. Attributes reference 69

 Transaction Name. The name of the transaction for the process. The value format
is alphanumeric with a maximum 16 characters, as in this example:
Data_Base_Reorg.

Transaction Name (Unicode). The name of the transaction for the process. This
attribute is globalized. The value format is alphanumeric with a maximum 48
bytes, as in this example: Data_Base_Reorg.

Process Summary attributes

Use the Process Summary attributes to create situations that monitor summary
information about processes.

Current Interval. The number of seconds that have elapsed between the previous
sample and the current sample. The value format is an integer, for example, 90. A
sample the data that the Monitoring Agent for Sybase Server collects about each
server. New data becomes available if a new interval has occurred and data has
been refreshed.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Percent Processes Bad. The percentage of processes with a status of bad. The value
format is a percentage with two decimal places allowed, for example, 2.00. This
value is based on information from the sysprocesses table. Bad processes are often
associated with a process ID problem.

Percent Processes Blocked. The percentage of processes that are being blocked.
The value format is a percentage with two decimal places allowed, for example,
4.00. This value is based on information from the sysprocesses table. The value
includes all processes currently in a waiting state.

Percent Processes Infected. The percentage of processes with a status of infected.

The value format is a percentage with two decimal places allowed, for example,
2.00. This value is based on information from the sysprocesses table. An infected
process is associated with a serious error condition.

Percent Processes Lock Sleep. The percentage of processes with a status of

locksleep. The value format is a percentage with two decimal places allowe, for
example, 10.00. This value is based on information from the sysprocesses table. The
processes are waiting to obtain locks on resources.

Percent Processes Other Sleep. The percentage of processes with a status of alarm
sleep, recv sleep, or send sleep. The value format is a percentage with two decimal
places allowed, for example, 10.00.

Percent Processes Sleeping. The percentage of processes with a status of sleep.

The value includes processes with a status of alarm sleep, lock sleep, recv sleep, or
send sleep. The value format is a percentage with two decimal places allowed, for
example, 20.00. This value is based on information from the sysprocesses table.

Percent Processes Stopped. The percentage of processes with a status of stopped.

The value format is a percentage with two decimal places allowed, for example,
2.00. This value is based on information from the sysprocesses table.

70 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 32 characters, for example, CFS_SVR5.

Server CPU Percent Application. The percentage of CPU time the server
application processes are using on the host. The value format is a percentage with
two decimal places allowed, for example, 20.00. The value counts only the
processes that still exist, and can be misleading if a process burned a lot of CPU
but ended before the sample was taken. Furthermore, this number includes only
Sybase Server internal processes, excluding the portion of OS CPU reported.

Server CPU Percent System. The percentage of CPU time the server processes are
using on the host. It might be over-reported because APPCPUPCT is
under-reported. The value format is a percentage with two decimal places allowed,
for example, 25.00.

Total Log Suspend. The number of processes with a status of log suspend. A
process with a status of log suspend is a process that cannot complete until there is
free space in the transaction log. The value format is an integer, for example, 1.

Total Processes Other Sleep. The number of processes that are in a sleep state
other than locked. The value format is an integer, for example, 2.

Total Processes. The number of processes. The value includes background

processes, processes for applications, and user processes. The value format is an
integer, for example, 50.

Total Processes Bad. The number of processes with a status of bad. The value
format is an integer, for example, 1.

Total Processes Blocked. The number of processes that are being blocked. The
value format is an integer, for example, 2.

Total Processes Infected. The number of processes with a status of infected. A

process with a status of infected is a process that cannot be completed. The value
format is an integer, for example, 1.

Total Processes Locksleep. The number of processes with a status of locksleep. A

process with a status of locksleep is a process waiting for a lock on a resource to
be released. The value format is an integer, for example, 5.

Total Processes Stopped. The number of processes with a status of stopped. The
value format is an integer, for example, 1.

Remote Servers attributes

Use the Remote Servers attributes to create situations that monitor summary
information about remote servers.

Connection Level. The connection level for the remote server. The value format is
an integer, for example, 3.

Chapter 5. Attributes reference 71

 Current Interval. The number of seconds that have elapsed between the previous
sample and the current sample. The value format is an integer, for example, 0.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Network Name. The name of the network for the remote server. The value format
is alphanumeric with a maximum 16 characters, for example, REM_NET.

Remote Server ID. The ID of the remote server. The value format is alphanumeric
with a maximum 12 characters, for example, SERV_ID.

Remote Server Name. The name of the remote server. The value format is
alphanumeric with a maximum 12 characters, for example, REM_SVR5.

Remote Server Status. The value depends on the version of the server you are
using. For version 10.0, 10.2 and 11.0, the value is the status of the remote server.
For version 11.5 and 11.9, the value is the security option for the remote server.
Valid The following values are valid for Versions 10.0, 10.2, and 11.0:
Inactive
The remote server is inactive.
Active The remote server is active.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 32 characters, for example, CFS_SVR5.

Server Detail attributes

Use the Server Detail attributes to create situations that monitor detail information
about a selected server.

Current Locks. The number of current locks for the server. The value format is an
integer, for example, 73. This value is a configuration parameter.

Data CacheSize. The number of kilobytes (KB) allocated for the data cache
memory. The server uses the data cache to store data and index pages. The value
format is an integer, for example, 1000. The cache is sometimes referred to as the
buffer cache.

Error Log Size. The number of bytes in the error log file. The value format is an
integer, for example, 50000. The error log contains the fatal error and kernel error
messages issued by the server.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Max Locks Allowed. The greatest value for the statistic since the server was
started. The value format is an integer, for example, 2000. This value is a
configuration parameter.

72 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 OS Type. The operating system for the server. The value format is alphanumeric,
for example, AIX.

OS Version. The version of the operating system for the server. The value format
is the version in the format version.release, for example, 2.5.

Percent Max Locks. The percentage of locks on resources of the maximum number
of locks allowed by the server. The value format is a percentage with two decimal
places allowed, for example, 10.00. Setting a higher limit for the maximum number
of locks does not impair performance. If your operations exceed the number of
available locks, you can increase this limit.

Procedure Cache Percent. The percentage of cache memory the server uses for the
procedure cache. The valid format is a percentage with two decimal places
allowed, for example, 20.00.

Procedure Cache Size. The number of kilobytes (KB) allocated for the procedure
cache. The server uses the procedure cache to compile queries and store
procedures that are compiled. The value format is an integer, for example, 1000.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Server Status. Indicates the status of the server. The following values are valid:
Active The server is active.
Blank Server status is unknown.

Server Type. The type of server. The value format is alphanumeric, for example,
Server.

Server Version. The version of the server. The value format is the version in the
format version.release, for example, 10.0.

Startup Timestamp. The time stamp that indicates the date and time the server
was started.

Time Since Startup. The number of minutes that have elapsed since the server was
started. The value format is an integer, for example, 360.

Server Enterprise attributes

The Server Enterprise attributes provide the Sybase system with common
information for the enterprise view.

Host Name. The name of the host host computer for Sybase. The value format is
alphanumeric with a maximum of 32 characters.

Server. The name of the Sybase server. The value format is alphanumeric (for
example, TEST1) with a maximum of 64 characters.

Chapter 5. Attributes reference 73

 Server Summary attributes
Use the Server Summary attributes to create situations that monitor summary
information about servers. These attributes have information about Sybase system
identification, revision level, and status.

Collection Status. Indicates the status of the data collector on the remote node.
The data collector is the part of the product that collects information about the
server. The following values are valid:
Active Data collector is active.
Inactive
Data collector is inactive.

Current Interval. The number of seconds that have elapsed between the previous
sample and the current sample. The value format is an integer, for example, 90. A
sample contains the data that the Monitoring Agent for Sybase Server collects
about each server. New data becomes available if a new interval has occurred and
data has been refreshed.

Data Cache Size. The number of kilobytes (KB) allocated for the data cache
memory. The server uses the data cache to store data and index pages. The value
format is an integer, for example, 1000.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Percent Max Locks. The percentage of locks on resources of the maximum number
of locks allowed by the server. The value format is a percentage with two decimal
places allowed, for example, 10.00.

Procedure Cache Size. The number of kilobytes (KB) allocated for the procedure
cache. The server uses the procedure cache to compile queries and store
procedures that are compiled. The value format is an integer, for example, 1000.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Server CPU Percent. The percentage of CPU time the server process is using on
the host. The value format is a percentage with two decimal places allowed, for
example, 20.00.

Server Status. Indicates the status of the server. The following values are valid:
Active Server is active.
Inactive
Server is not active.
Blank Server status is unknown.

Server Type. The type of server. The value format is alphanumeric, for example,
Server.

74 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Server Version. The version of the server. The value format is the version in the
format version.release, for example, 10.0.

Time Since Startup. The number of minutes that have elapsed since the server was
started. The value format is an integer, for example, 360.

Total OS CPU Percent. The percentage of CPU time being used by the operating
system as well as all the user processes (for example, the percentage of CPU time
used by the UNIX operating system and the percentage of CPU time used by all
the user processes). The value format is a percentage with two decimal places
allowed, for example, 40.00.

SQL Detail attributes

Use the SQL Detail attributes to create situations that monitor detail information
about activity.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

SQL Activity Count. The number of times the activity occurred during the
sampling period. The value format is an integer, for example, 25.

SQL Activity Name. The name of the activity. The value format is alphanumeric
with a maximum 32 characters, for example, Insert Total.

SQL Activity per Second. The average number of times per second the activity
occurred for the server. The value format is a decimal with two decimal places
allowed, for example, 15.00.

SQL Activity per Transaction. The average number of times per transaction the
activity occurred for the server. The value format is a decimal with two decimal
places allowed, for example, 10.00.

SQL Activity Percent. The percentage of activity represented by the specified

activity. The value format is a percentage with two decimal places allowed, for
example, 20.00.

Statistics Detail attributes

Use the Statistics Detail attributes to create situations that monitor detail
information about server statistics.

Average Value per Second. The average value per second for the statistic since the
server was started. The value format is a decimal with two decimal places allowed,
for example, 5.00.

Current Value. The value for the statistic during the current interval. The value
format is an integer, for example, 40. This is a cumulative value for the statistic.

Chapter 5. Attributes reference 75

 Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Maximum Seen. The greatest value per second for the statistic since the server was
started. The value format is an integer, for example, 2000. This is a benchmark
value.

Minimum Seen. The smallest value per second for the statistic since the server
was started. The value format is an integer, for example, 10. This is a benchmark
value.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Statistic Name. The name of the statistic. The value format is alphanumeric with a
maximum 32 characters, for example, CPU_busy.

Statistic Name (Unicode). The name of the statistic. This attribute is globalized.
The value format is alphanumeric with a maximum 32 bytes, for example,
CPU_busy.

Total Since Startup. The total of all the values for the statistic since the server was
started. The value format is an integer, for example, 9000.

Statistics Summary attributes

Use the Statistics Summary attributes to create situations that monitor summary
information about server statistics.

Collection Status. Indicates the status of the data collector on the remote node.
The data collector is the part of the product that collects information about the
server. The following values are valid:
Active Data collector is active.
Inactive
Data collector is inactive.

Current Interval. The number of seconds that have elapsed between the previous
sample and the current sample. The value format is an integer, for example, 90.

A sample contains the data that the Monitoring Agent for Sybase Server collects
about each server. New data becomes available if a new interval has occurred and
data has been refreshed.

Current Logons. The number of active connections (logons). The value format is an
integer, for example, 50.

Database Max Blocks (Unicode). Name of the database that is blocking the largest
number of processes. This attribute is globalized. The value format is alphanumeric
with a maximum 96 bytes.

76 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Database Max Locks (Unicode). Name of the database with the largest number of
locks. This attribute is globalized. The value format is alphanumeric with a
maximum 96 bytes.

Disk IO Current Interval. The number of times the server accessed hard drive
during the current interval. The value includes access to hard drive for physical
reads and physical writes. The value format is an integer, for example, 50.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters; for example, Voyager.

IO Errors Current Interval. The number of errors that occurred when the server
accessed hard drive during the current interval. The value format is an integer, for
example, 5.

IO Errors Since Startup. The number of errors that have occurred when the server
accessed hard drive since startup. The value format is an integer, for example, 2.

Max User Connections Allowed. The maximum number of active connections

(logons) allowed for the server. The value format is an integer in the range
5-2147483647, for example, 100.

This is a configuration value for the server. To determine the number of

connections that can be configured for the server, use the select
@@max_connections command.

Percent IO Errors Current Interval. The percentage of the accesses to hard drive
that had errors occur during the current interval. The value format is a percentage
with two decimal places allowed, for example, 1.00.

Percent Max Logons Active. The percentage of active connections (logons) of the
maximum number of active connections allowed for the server. The value format is
a percentage with two decimal places allowed, for example, 50.00.

Physical Reads per Second. The average number of physical reads per second
during the current interval. The value format is a decimal with two decimal places
allowed, for example, 5.00.

Physical Writes per Second. The average number of physical writes per second
during the current interval. The value format is a decimal with two decimal places
allowed, for example, 5.00.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters, for example, CFS_SVR5.

Table Max Locks (Unicode). Name of the table with the largest number of locks.
This attribute is globalized. The value format is alphanumeric with a maximum 96
bytes.

Total Logons per Second. The average number of active connections (logons) per
second during the current interval. The value format is a decimal with two decimal
places allowed, for example, 15.00.

Chapter 5. Attributes reference 77

 Total OS CPU Percent Busy. The percentage of CPU seconds the server has used
during the current interval of all the CPU seconds used since the server was
started. The value format is a percentage with two decimal places allowed, for
example, 20.00.

Total OS IO Percent Busy. The percentage of I/O the server used during the
current interval of all the I/O used since the server was started. The value format
is a percentage with two decimal places allowed, for example, 25.00.

Task Detail attributes

Use the Task Detail attributes to create situations that monitor detail information
about task context switches for a selected server.

Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 30 characters,for example, CFS_SVR5.

Task Switch Cause. The type of task context switch. The value format is
alphanumeric with a maximum 32 characters, for example, Cache Search Miss.

Task Switch Count. The number of times the specified task context switch
occurred during the sampling period. The value format is an integer, for example,
50.

Task Switch per Second. The average number of times the specified task context
switch occurred per second during the sampling period. The value format is a
decimal with two decimal places allowed.

Task Switch per Transaction. The average number of times the specified task
context switch occurred per transaction during the sampling period. The value
format is a decimal with two decimal places allowed, for example, 30.00.

Task Switch Percent. The percentage of task context switches represented by the
specified task context switch. The value format is a percentage with two decimal
places allowed, for example, 15.00.

Text attributes
Use the Text attributes to create situations that monitor information about text
strings associated with a selected process.

Database Name. The name of the database. The value format is alphanumeric with
a maximum 30 characters, for example, KOY3.

Database Name (Unicode). The name of the database. This attribute is globalized.
The value format is alphanumeric with a maximum 90 bytes, for example, KOY3.
Each database name is unique. The server also assigns each database its own
identification number.

78 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Host Name. The name of the host computer running the server. The value format
is alphanumeric with a maximum 64 characters, for example, Voyager.

Process ID. The ID of the process that is requesting or holding the lock on the
resource. The value format is alphanumeric with a maximum 10 characters, for
example, 42168.

Sample Timestamp. The time stamp that indicates the date and time the product
collected the sample for the server. A sample is the data the product collects about
the server.

Server. The name of the server. The value format is alphanumeric with a
maximum 32 characters, for example, CFS_SVR5.

Sequence Num. SQL sequence number. The value format is an integer, for
example, 3.

Text. A complete or partial SQL statement. The value format is alphanumeric with
a maximum 60 characters.

Text (Unicode). A complete or partial SQL statement. This attribute is globalized.

The value format is alphanumeric with a maximum 180 bytes.

Disk capacity planning for historical data

Disk capacity planning for a monitoring agent is a prediction of the amount of disk
space to be consumed for each attribute group whose historical data is being
collected. Required disk storage is an important factor to consider when you are
defining data collection rules and your strategy for historical data collection.

Calculate expected disk space consumption by multiplying the number of bytes

per instance by the expected number of instances, and then multiplying that
product by the number of samples.Table 8 on page 80 provides the following
information required to calculate disk space for the Monitoring Agent for Sybase
Server:
v DB table name is the table name as it would appear in the warehouse database, if
the attribute group is configured to be written to the warehouse.
v Bytes per instance (agent) is an estimate of the record length for each row or
instance written to the agent disk for historical data collection. This estimate can
be used for agent disk space planning purposes.
v Bytes per instance (warehouse) is an estimate of the record length for detailed
records written to the warehouse database, if the attribute group is configured to
be written to the warehouse. Detailed records are those that have been uploaded
from the agent for long-term historical data collection. This estimate can be used
for warehouse disk space planning purposes.
v Bytes per summarized instance (warehouse) is an estimate of the record length for
aggregate records written to the warehouse database, if the attribute group is
configured to be written to the warehouse. Aggregate records are created by the
Summarization agent for attribute groups that have been configured for
summarization. This estimate can be used for warehouse disk space planning
purposes.
v Expected number of instances is a guideline that can be different for each attribute
group, because it is the number of instances of data that the agent will return for
a given attribute group, and depends upon the application environment that is

Chapter 5. Attributes reference 79

 being monitored. For example, if your attribute group is monitoring each
processor on your machine and you have a dual processor machine, the number
of instances is 2.
The IBM Tivoli Monitoring Installation and Setup Guide contains formulas that can
be used to estimate the amount of disk space used at the agent and in the
warehouse database for historical data collection of an attribute group.
Table 8. Capacity planning for historical data
Bytes per
Bytes per summarized
Attribute Bytes per instance instance Expected number of
Group DB table name instance (agent) (warehouse) (warehouse) instances
Cache Detail KOYCACD 754 809 2448 multiple rows
Cache KOYCACS 634 687 2326 single row
Summary
Configuration KOYSCFG 445 473 510 multiple rows
Database Detail KOYDBD 537 578 960 multiple rows
Database KOYDBS 260 286 620 single row
Summary
Device Detail KOYDEVD 1006 1038 1177 multiple rows
Engine Detail KOYENGD 658 709 2117 multiple rows
Engine KOYENGS 280 312 802 single row
Summary
Lock Conflict KOYLOCK 380 407 495 multiple rows
Detail
Lock Detail KOYLCKD 431 467 1272 multiple rows
Lock Summary KOYLCKS 478 519 1606 single row
Locks KOYLOCKS 478 507 544 multiple rows
Log Detail KOYLOGD 282 306 535 multiple rows
Log Summary KOYLOGS 226 252 562 single row
Physical Device KOYSDEVD 898 941 1938 multiple rows
Detail
Problem Detail KOYPROBD 788 818 855 multiple rows
Problem KOYPROBS 248 275 435 single row
Summary
Process Detail KOYPRCD 950 998 1230 multiple rows
Process KOYPRCS 382 417 1225 single row
Summary
Remote Servers KOYSRVR 256 281 318 multiple rows
Server Detail KOYSRVD 570 605 798 multiple rows
Server KOYSRVRE 888 942 1831 multiple rows
Enterprise
Server KOYSRVS 308 336 541 single row
Summary
SQL Detail KOYSQLD 282 306 535 multiple rows
Statistics Detail KOYSTATD 262 287 390 multiple rows
Statistics KOYSTATS 336 366 892 single row
Summary

80 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 8. Capacity planning for historical data (continued)
Bytes per
Bytes per summarized
Attribute Bytes per instance instance Expected number of
Group DB table name instance (agent) (warehouse) (warehouse) instances
Task Detail KOYTSKD 282 306 535 multiple rows
Text KOYSQL 568 593 630 multiple rows

For more information about historical data collection, see the IBM Tivoli Monitoring
Administrator’s Guide.

Chapter 5. Attributes reference 81

82 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 6. Situations reference
This chapter contains an overview of situations, references for detailed information
about situations, and descriptions of the predefined situations included in this
monitoring agent.

About situations
A situation is a logical expression involving one or more system conditions.
Situations are used to monitor the condition of systems in your network. You can
manage situations from the Tivoli Enterprise Portal by using the Situation editor.

The IBM Tivoli Monitoring agents that you use to monitor your system
environment are shipped with a set of predefined situations that you can use as-is
or you can create new situations to meet your requirements. Predefined situations
contain attributes that check for system conditions common to many enterprises.

Using predefined situations can improve the speed with which you can begin
using the Monitoring Agent for Sybase Server. You can examine and, if necessary,
change the conditions or values being monitored by a predefined situation to those
best suited to your enterprise.

Note: The predefined situations provided with this monitoring agent are not
read-only. Do not edit these situations and save over them. Software updates
will write over any of the changes that you make to these situations.
Instead, clone the situations that you want to change to suit your enterprise.

You can display predefined situations and create your own situations using the
Situation editor. The left frame of the Situation editor initially lists the situations
associated with the Navigator item that you selected. When you click a situation
name or create a new situation, the right frame opens with the following tabs:
Formula
Condition being tested
Distribution
List of managed systems (operating systems, subsystems, or applications)
to which the situation can be distributed.
Expert Advice
Comments and instructions to be read in the event workspace
Action
Command to be sent to the system
Until Duration of the situation

More information about situations

The IBM Tivoli Monitoring User’s Guide contains more information about predefined
and custom situations and how to use them to respond to alerts.

For a list of the predefined situations for this monitoring agent and a description
of each situation, refer to the Predefined situations section below and the
information in that section for each individual situation.

© Copyright IBM Corp. 2005 83

Predefined situations
This monitoring agent contains the following predefined situations:
v Sybase_Collection_Stat_Warning
v Sybase_DB_Error_Status
v Sybase_DB_Freespace_Critical
v Sybase_DB_Freespace_Warning
v Sybase_DB_Num_Errors_Warning
v Sybase_Device_Free_Pct_Warning
v Sybase_ErrorLog_Size_Warning
v Sybase_IOERR_Startup_Warning
v Sybase_IOError_Curintvl_Warning
v Sybase_Log_Freespace_Critical
v Sybase_Log_Freespace_Warning
v Sybase_Log_Suspend_Warning
v Sybase_LogonPct_Warning
v Sybase_Pct_CPU_Yields_Warning
v Sybase_Pct_Device_Lock_Warning
v Sybase_Pct_Engine_CPU_Critical
v Sybase_Pct_Engine_CPU_Warning
v Sybase_Pct_IO_Warning
v Sybase_Pct_MAX_Locks_Critical
v Sybase_Pct_MAX_Locks_Warning
v Sybase_Pct_Task_Yields_Warning
v Sybase_Pct_Total_CPU_Critical
v Sybase_Pct_Total_CPU_Warning
v Sybase_ProbAge_GT_17_Warning
v Sybase_ProbAge_LT_17_Warning
v Sybase_Process_Blocked_Warning
v Sybase_Process_Infected_Warning
v Sybase_Processes_Bad_Warning
v Sybase_Processes_Stop_Warning
v Sybase_ProcessLockSleep_Warning
v Sybase_ProcessOthSleep_Warning
v Sybase_Server_CPU_Critical
v Sybase_Server_CPU_Warning
v Sybase_Server_Error_Warning
v Sybase_Server_Status_Critical
v Sybase_Server_Status_Inactive

The remaining sections of this chapter contain descriptions of each of these

predefined situations in alphabetical order.

Sybase_Collection_Stat_Warning situation
Declares a warning condition when the collector is not active. This situation has
the following formula:

84 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Sybase_Server_Summary.Collection_Status NE Active

Sybase_DB_Error_Status situation
Declares a critical condition if the database has a serious error status. This situation
has the following formula:
Sybase_Database_Detail.Error_Status EQ ’Yes’

Sybase_DB_Freespace_Critical situation
Declares a critical condition if the remaining free space in the database is 10% or
less. This situation has the following formula:
Sybase_Database_Summary.Minimum_Pct_Data_Freespace LE 10

Sybase_DB_Freespace_Warning situation
Declares a warning condition if the remaining free space in the database is
between 10 to 20%. This situation has the following formula:
Sybase_Database_Summary.Minimum_Pct_Data_Freespace GT 10
AND
Sybase_Database_Summary.Minimum_Pct_Data_Freespace LE 20

Sybase_DB_Num_Errors_Warning situation
Declares a warning condition if a database has an error status. This situation has
the following formula:
Sybase_Database_Summary.Total_DBs_in_Error GT 0

Sybase_Device_Free_Pct_Warning situation
Declares a warning condition if the remaining free space in a device is 10% or less.
This situation has the following formula:
Sybase_Device_Detail.Device_Free_Space_Percent LE 10

Sybase_ErrorLog_Size_Warning situation
Declares a warning condition if the error log contains 1,000,000 or more bytes. This
situation has the following formula:
Sybase_Problem_Summary.Error_Log_Size GE 1000000

Sybase_IOERR_Startup_Warning situation
Declares a warning condition if ten or more I/O errors occurred since startup and
the percentage of I/O errors is 5% or more. This situation has the following
formula:
Sybase_Statistics_Summary.IO_Errors_Since_Startup GE 10
AND
Sybase_Statistics_Summary.Percent_IO_Errors_Current_Interval GE 5

Sybase_IOError_Curintvl_Warning situation
Declares a warning condition if the percentage of I/O errors during the current
interval is 80% or more. This situation has the following formula:
Sybase_Statistics_Summary.IO_Errors_Current_Interval GE 8000

Sybase_Log_Freespace_Critical situation
Declares a critical condition if log free space is 10% or less. This situation has the
following formula:
Sybase_Database_Summary.Minimum_Pct_Log_Freespace LE 10

Chapter 6. Situations reference 85

 Sybase_Log_Freespace_Warning situation
Declares a warning condition if log free space is between 10% and 20%. This
situation has the following formula:
Sybase_Database_Summary.Minimum_Pct_Log_Freespace GT 10
AND
Sybase_Database_Summary.Minimum_Pct_Log_Freespace LE 20

Sybase_Log_Suspend_Warning situation
Declares a warning condition if one or more processes is in log suspend. This
situation has the following formula:
Sybase_Process_Summary.Total_Log_Suspend GE 1

Sybase_LogonPct_Warning situation
Declares a warning condition if the maximum number of logons is 90% or more.
This situation has the following formula:
Sybase_Statistics_Summary.Percent_Max_Logons_Active GE 90

Sybase_Pct_CPU_Yields_Warning situation
Declares a warning condition if CPU yields are more than 75%. This situation has
the following formula:
Sybase_Process_Detail.Current_CPU_Percent_Used GT 75

Sybase_Pct_Device_Lock_Warning situation
Declares a warning condition if more than 20% of lock requests were waiting. This
situation has the following formula:
Sybase_Physical_Device_Detail.Device_Lock_Contention_Percent GE 20

Sybase_Pct_Engine_CPU_Critical situation
Declares a critical condition if the percentage of busy engine CPUs is greater than
90%. This situation has the following formula:
Sybase_Engine_Summary.CPU_Busy_Percent GT 90

Sybase_Pct_Engine_CPU_Warning situation
Declares a warning condition if the percentage of busy engine CPUs is between 75
to 90%. This situation has the following formula:
Sybase_Engine_Detail.CPU_Busy_Percent GT 75
AND
Sybase_Engine_Detail.CPU_Busy_Percent LT 90

Sybase_Pct_IO_Warning situation
Declares a warning condition if 80% or more of the time is spent on I/O
operations. This situation has the following formula:
Sybase_Statistics_Summary.Total_OS_IO_Percent_Busy GE 80

Sybase_Pct_MAX_Locks_Critical situation
Declares a critical condition if the percentage of allowable locks reaches 80% or
more. This situation has the following formula:
Sybase_Server_Summary.Percent_Max_Locks GE 80

86 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Sybase_Pct_MAX_Locks_Warning situation
Declares a warning condition if the percentage of allowable locks is between 60 to
80%. This situation has the following formula:
Sybase_Server_Summary.Percent_Max_Locks GE 60
AND
Sybase_Server_Summary.Percent_Max_Locks LT 80

Sybase_Pct_Task_Yields_Warning situation
Declares a warning condition if the percentage of task yields is greater than 75%.
This situation has the following formula:
Sybase_Task_Detail.Task_Switch_Percent GT 75

Sybase_Pct_Total_CPU_Critical situation
Declares a critical condition if more than 90% of the total CPU is busy. This
situation has the following formula:
Sybase_Engine_Summary.CPU_Busy_Percent GT 90

Sybase_Pct_Total_CPU_Warning situation
Declares a warning condition if the percentage of CPU busy falls between 75 to
90%. This situation has the following formula:
Sybase_Engine_Summary.CPU_Busy_Percent GT 75
AND
Sybase_Engine_Summary.CPU_Busy_Percent LE 90

Sybase_ProbAge_GT_17_Warning situation
Declares a warning condition if an error is 30 or more minutes old and has a
severity level of 17 or more. This situation has the following formula:
Sybase_Problem_Summary.Age_of_Last_Error GE 30
AND
Sybase_Problem_Summary.Maximum_Sev_Current_Interval GE 17

Sybase_ProbAge_LT_17_Warning situation
Declares a warning condition if an error is 30 or more minutes old and has a
severity level of less than 17. This situation has the following formula:
Sybase_Problem_Summary.Age_of_Last_Error GE 30
AND
Sybase_Problem_Summary.Maximum_Sev_Current_Interval LT 17

Sybase_Process_Blocked_Warning situation
Declares a warning condition if five or more processes are blocked, causing 25% or
more processes to be blocked. This situation has the following formula:
Sybase_Process_Summary.Percent_Processes_Blocked GE 25
AND
Sybase_Process_Summary.Total_Processes_Blocked GE 5

Sybase_Process_Infected_Warning situation
Declares a warning condition if one or more processes are infected. This situation
has the following formula:
Sybase_Process_Summary.Total_Processes_Infected GE 1

Chapter 6. Situations reference 87

 Sybase_Processes_Bad_Warning situation
Declares a warning condition if one or more processes are bad. This situation has
the following formula:
Sybase_Process_Summary.Total_Processes_Bad GE 1

Sybase_Processes_Stop_Warning situation
Declares a warning condition if one to five processes are stopped, causing 10 % of
processes to be stopped. This situation has the following formula:
Sybase_Process_Summary.Total_Processes_Stopped GE 5
AND
Sybase_Process_Summary.Percent_Processes_Stopped GE 10

Sybase_ProcessLockSleep_Warning situation
Declares a warning condition if five or more processes are in lock sleep, which
causes 10% or more processes to be in lock sleep. This situation has the following
formula:
Sybase_Process_Summary.Percent_Processes_Lock_Sleep GE 10
AND
Sybase_Process_Summary.Total_Processes_Lock_Sleep GE 5

Sybase_ProcessOthSleep_Warning situation
Declares a warning condition if two or more processes are in other sleep, causing
50% or more processes to be in other sleep. This situation has the following
formula:
Sybase_Process_Summary.Total_Processes_Other_Sleep GE 2
AND
Sybase_Process_Summary.Percent_Processes_Other_Sleep GE 50

Sybase_Server_CPU_Critical situation
Declares a critical condition if the server has been active for ten minutes or longer
and the CPU usage on the server is 80% or more. This situation has the following
formula:
Sybase_Server_Summary.Total_OS_CPU_Percent GE 80
AND
Sybase_Server_Summary.Time_Since_Startup GE 10

Sybase_Server_CPU_Warning situation
Declares a warning condition if the CPU usage on the server is between 60 to 80%.
This situation has the following formula:
Sybase_Server_Summary.Total_OS_CPU_Percent GE 60
AND
Sybase_Server_Summary.Total_OS_CPU_Percent LT 80
AND
Sybase_Server_Summary.Time_Since_Startup GE 10

Sybase_Server_Error_Warning situation
Declares a warning condition if server errors have occurred during the current
interval. This situation has the following formula:
Sybase_Problem_Summary.Total_Errors_High_Sev GT 0

Sybase_Server_Status_Critical situation
Declares a critical condition if the server status is not active. This situation has the
following formula:

88 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Sybase_Server_Summary.Server_Status NE Active

Sybase_Server_Status_Inactive situation
Declares a critical condition if the server status is inactive. This situation has the
following formula:
Sybase_Server_Summary.Server_Status EQ Inactive

Chapter 6. Situations reference 89

90 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 7. Take Action commands reference
This chapter contains an overview of Take Action commands and references for
detailed information about Take Action commands.

About Take Action commands

Take Action commands can be run from the desktop or included in a situation or a
policy.

When included in a situation, the command executes when the situation becomes
true. A Take Action command in a situation is also referred to as reflex automation.
When you enable a Take Action command in a situation, you automate a response
to system conditions. For example, you can use a Take Action command to send a
command to restart a process on the managed system or to send a text message to
a cell phone.

Advanced automation uses policies to perform actions, schedule work, and

automate manual tasks. A policy comprises a series of automated steps called
activities that are connected to create a workflow. After an activity is completed,
Tivoli Enterprise Portal receives return code feedback, and advanced automation
logic responds with subsequent activities prescribed by the feedback.

More information about Take Action commands

For more information about working with Take Action commands, see the IBM
Tivoli Monitoring User’s Guide.

Predefined Take Action commands

This monitoring agent does not have any Take Action commands.

© Copyright IBM Corp. 2005 91

92 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Chapter 8. Policies reference
This chapter contains an overview of policies and references for detailed
information about policies.

About policies
Policies are an advanced automation technique for implementing more complex
workflow strategies than you can create through simple automation.

A policy is a set of automated system processes that can perform actions, schedule
work for users, or automate manual tasks. You use the Workflow Editor to design
policies. You control the order in which the policy executes a series of automated
steps, which are also called activities. Policies are connected to create a workflow.
After an activity is completed, Tivoli Enterprise Portal receives return code
feedback and advanced automation logic responds with subsequent activities
prescribed by the feedback.

Note: For monitoring agents that provide predefined policies, predefined policies
are not read-only. Do not edit these policies and save over them. Software
updates will write over any of the changes that you make to these policies.
Instead, clone the policies that you want to change to suit your enterprise.

More information about policies

For more information about working with policies, see the IBM Tivoli Monitoring
User’s Guide.

For information about using the Workflow Editor, see the IBM Tivoli Monitoring
Administrator’s Guide or the Tivoli Enterprise Portal online help.

Predefined policies
This monitoring agent does not have any predefined policies.

© Copyright IBM Corp. 2005 93

94 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Appendix A. Workspaces workgroups mapped to tasks
In Tivoli Enterprise Portal, the Monitoring Agent for Sybase Server provides
workspaces that contain table views and chart views for viewing information
about each server you monitor. Each workspace displays information about server
activities and conditions.

Use Table 9 to determine which the Monitoring Agent for Sybase Server workspace
group to use in a specific situation.
Table 9. Workspace group choices mapping

Errorlog Alerts
Databases

Locking
Servers

Process
If you want to...
Analyze the performance of your U U U U
system
Identify problem areas and U U U
bottlenecks in your system
Get the information you need to tune U U U U
your system
Evaluate how your tuning decisions U U
affect the performance of your
system
Identify and anticipate times of peak U U U
usage
Monitor database activity U
Select optimum threshold values for U U U U U
situation monitoring

© Copyright IBM Corp. 2005 95

96 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Appendix B. IBM Tivoli Enterprise Console event mapping
Generic event mapping provides useful event class and attribute information for
situations that do not have specific event mapping defined. Each event class
corresponds to an attribute group in the monitoring agent. For a description of the
event slots for each event class, see Table 10. For more information about mapping
attribute groups to event classes, see the IBM Tivoli Monitoring Administrator’s
Guide.

BAROC files are found on the Tivoli Enterprise Monitoring Server in the
installation directory in TECLIB (that is, install_dir/cms/TECLIB for Windows
systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM
Tivoli Enterprise Console event synchronization provides a collection of
ready-to-use rule sets that you can deploy with minimal configuration. Be sure to
install IBM Tivoli Enterprise Console event synchronization to access the correct
Sentry.baroc, which is automatically included during base configuration of IBM
Tivoli Enterprise Console rules if you indicate that you want to use an existing
rulebase. See the IBM Tivoli Monitoring Installation and Setup Guide for details.

Each of the event classes is a child of KOY_Base. The KOY_Base event class can be
used for generic rules processing for any event from the Monitoring Agent for
Sybase Server.
Table 10. Overview of event slots to event classes
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Server_Summary Sybase_Server_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v server_type: STRING
v server_status: STRING
v collection_status: STRING
v data_cache_size: INTEGER
v procedure_cache_size: INTEGER
v percent_max_locks: REAL
v server_cpu_percent: REAL
v total_os_cpu_percent: REAL
v time_since_startup: INTEGER
v server_version: STRING
v current_interval: INTEGER
v sample_timestamp: STRING

© Copyright IBM Corp. 2005 97

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Server_Detail Sybase_Server_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v server_type: STRING
v server_version: STRING
v server_status: STRING
v current_locks: INTEGER
v max_locks_allowed: INTEGER
v percent_max_locks: REAL
v data_cache_size: INTEGER
v procedure_cache_size: INTEGER
v procedure_cache_percent: REAL
v startup_timestamp: STRING
v time_since_startup: INTEGER
v error_log_name: STRING
v error_log_size: INTEGER
v os_type: STRING
v os_version: STRING
v sample_timestamp: STRING
v error_log_name_u: STRING
ITM_Sybase_Database_Summary Sybase_Database_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v total_databases: INTEGER
v minimum_pct_data_freespace: REAL
v minimum_pct_log_freespace: REAL
v total_dbs_in_error: INTEGER
v total_dbs_read_only: INTEGER
v total_dbs_dbo_only: INTEGER
v total_dbs_single_user: INTEGER
v total_dbs_no_free_space_accounting:
INTEGER
v current_interval: INTEGER
v sample_timestamp: STRING

98 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Database_Detail Sybase_Database_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v db_id: STRING
v db_owner: STRING
v error_status: STRING
v dbo_only_access: STRING
v single_user_access: STRING
v read_only_access: STRING
v select_into_bulkcopy_enabled: STRING
v dump_tran_date: STRING
v free_space_accounting_suppresed:
STRING
v abort_tran_on_log_full: STRING
v truncate_log_on_ckpt: STRING
v no_ckpt_after_recovery: STRING
v data_size: REAL
v log_size: REAL
v data_freespace: REAL
v log_freespace: REAL
v data_freespace_percent: REAL
v log_freespace_percent: REAL
v total_devices: INTEGER
v sample_timestamp: STRING
v database_name_u: STRING
v db_owner_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 99

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Device_Detail Sybase_Device_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_version: STRING
v host_name: STRING
v database_name: STRING
v device_name: STRING
v device_size: INTEGER
v device_free_space: REAL
v device_free_space_percent: REAL
v device_type: STRING
v physical_device_name: STRING
v mirror_device_name: STRING
v sample_timestamp: STRING
v database_name_u: STRING
v device_name_u: STRING
v physical_device_name_u: STRING
v mirror_device_name_u: STRING
ITM_Sybase_Locks Sybase_Locks attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v type: STRING
v process_holding_lock: INTEGER
v database_name: STRING
v database_id: INTEGER
v table_name: STRING
v page_number: INTEGER
v cclass: STRING
v sample_timestamp: STRING
v database_name_u: STRING
v table_name_u: STRING
v cclass_u: STRING

100 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Lock_Conflict_Detail Sybase_Lock_Conflict_Detail attribute
group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v database_id: INTEGER
v server_user_id: STRING
v requestor_process_id: INTEGER
v blocking_process_id: INTEGER
v time_blocked: REAL
v sample_timestamp: STRING
v database_name_u: STRING
v server_user_id_u: STRING
ITM_Sybase_Text Sybase_Text attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v process_id: INTEGER
v text: STRING
v sequence_num: INTEGER
v sample_timestamp: STRING
v database_name_u: STRING
v text_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 101

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Process_Summary Sybase_Process_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v server_cpu_percent_system: REAL
v server_cpu_percent_application: REAL
v total_processes: INTEGER
v total_processes_blocked: INTEGER
v percent_processes_blocked: REAL
v total_processes_infected: INTEGER
v percent_processes_infected: REAL
v total_processes_bad: INTEGER
v percent_processes_bad: REAL
v total_processes_stopped: INTEGER
v percent_processes_stopped: REAL
v total_processes_lock_sleep: INTEGER
v percent_processes_lock_sleep: REAL
v total_processes_other_sleep: INTEGER
v percent_processes_other_sleep: REAL
v percent_processes_sleeping: REAL
v total_log_suspend: INTEGER
v current_interval: INTEGER
v sample_timestamp: STRING

102 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Process_Detail Sybase_Process_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v process_id: INTEGER
v database_name: STRING
v process_status: STRING
v total_cpu_time: REAL
v current_cpu_percent_used: REAL
v total_disk_io: INTEGER
v total_memory_alloc: INTEGER
v time_blocked: REAL
v blocking_process_id: STRING
v os_process_id: STRING
v server_user_name: STRING
v command: STRING
v client_host_name: STRING
v client_process_id: STRING
v transaction_name: STRING
v program_name: STRING
v client_user_id: STRING
v client_group_id: STRING
v network_packet_size: INTEGER
v login_name: STRING
v sample_timestamp: STRING
v database_name_u: STRING
v blocking_process_id_u: STRING
v server_user_name_u: STRING
v command_u: STRING
v transaction_name_u: STRING
v program_name_u: STRING
v client_user_id_u: STRING
v client_group_id_u: STRING
v login_name_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 103

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Problem_Summary Sybase_Problem_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v age_of_last_error: INTEGER
v maximum_sev_level: STRING
v maximum_sev_timestamp: STRING
v maximum_sev_current_interval: STRING
v total_error_messages: INTEGER
v total_errors_current_interval: INTEGER
v total_errors_high_sev: INTEGER
v total_errors_other: INTEGER
v error_log_size: INTEGER
v current_interval: INTEGER
v sample_timestamp: STRING
ITM_Sybase_Problem_Detail Sybase_Problem_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v message_timestamp: STRING
v message_age: INTEGER
v error_id: STRING
v severity_level: STRING
v maximum_severity: STRING
v sql_state_code: INTEGER
v message_issuer: STRING
v message_text: STRING
v sample_timestamp: STRING
v error_id_u: STRING
v message_issuer_u: STRING
v message_text_u: STRING

104 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Statistics_Summary Sybase_Statistics_Summary attribute group
v originnode: STRING
v hub_timestamp: SRING
v server: STRING
v host_name: STRING
v total_os_cpu_percent_busy: REAL
v total_os_io_percent_busy: REAL
v current_logons: INTEGER
v percent_max_logons_active: REAL
v total_logons_per_second: REAL
v max_user_connections_allowed:
INTEGER
v physical_reads_per_second: REAL
v physical_writes_per_second: REAL
v disk_io_current_interval: INTEGER
v io_errors_since_startup: INTEGER
v io_errors_current_interval: INTEGER
v percent_io_errors_current_interval: REAL
v current_interval: INTEGER
v sample_timestamp: STRING
ITM_Sybase_Statistics_Detail Sybase_Statistics_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v statistic_name: STRING
v current_value: INTEGER
v total_since_startup: INTEGER
v average_value_per_second: REAL
v maximum_seen: INTEGER
v minimum_seen: INTEGER
v sample_timestamp: STRING
ITM_Sybase_Remote_Servers Sybase_Remote_Servers attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v remote_server_id: STRING
v remote_server_status: STRING
v remote_server_name: STRING
v network_name: STRING
v connection_level: INTEGER
v current_interval: INTEGER
v sample_timestamp: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 105

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Configuration Sybase_Configuration attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v config_parameter: STRING
v parm_type: STRING
v config_value: STRING
v run_value: STRING
v minimum_value: STRING
v maximum_value: STRING
v sample_timestamp: STRING
v config_parameter_u: STRING
v config_value_u: STRING
v run_value_u: STRING

106 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Engine_Detail Sybase_Engine_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v engine_name: STRING
v current_interval: INTEGER
v total_transactions: INTEGER
v cpu_available_percent: REAL
v cpu_busy_percent: REAL
v cpu_yields_per_second: REAL
v cpu_yields_per_transaction: REAL
v cpu_yields_count: INTEGER
v cpu_yields_percent: REAL
v task_switch_per_second: REAL
v task_switch_per_transaction: REAL
v task_switch_count: INTEGER
v task_switch_percent: REAL
v maximum_outstanding_io_count:
INTEGER
v completed_disk_io_count: INTEGER
v tds_packets_received_per_second: REAL
v tds_packets_received_per_transaction:
REAL
v tds_packets_received_count: INTEGER
v tds_packets_received_percent: REAL
v tds_bytes_received_per_second: REAL
v tds_bytes_received_per_transaction:
REAL
v tds_bytes_received_count: INTEGER
v tds_bytes_received_percent: REAL
v tds_packets_sent_per_second: REAL
v tds_packets_sent_per_transaction: REAL
v tds_packets_sent_count: INTEGER
v tds_packets_sent_percent: REAL
v tds_bytes_sent_per_second: REAL
v tds_bytes_sent_per_transaction: REAL
v tds_bytes_sent_count: INTEGER
v tds_bytes_sent_percent: REAL
v sample_timestamp: STRING
v engine_name_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 107

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Engine_Summary Sybase_Engine_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v engine_count: STRING
v current_interval: INTEGER
v total_transactions: INTEGER
v cpu_available_percent: REAL
v cpu_busy_percent: REAL
v cpu_yields_count: INTEGER
v task_switch_count: INTEGER
v maximum_outstanding_io_count:
INTEGER
v completed_disk_io_count: INTEGER
v tds_packets_received_count: INTEGER
v tds_bytes_received_count: INTEGER
v tds_packets_sent_count: INTEGER
v tds_bytes_sent_count: INTEGER
v sample_timestamp: STRING
ITM_Sybase_Log_Summary Sybase_Log_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v maximum_private_log_cache_size:
INTEGER
v transaction_log_writes_count: INTEGER
v transaction_log_allocates_count:
INTEGER
v private_log_cache_log_records_count:
INTEGER
v private_log_cache_flushes_count:
INTEGER
v plc_semaphore_requests_count:
INTEGER
v log_semaphore_requests_count:
INTEGER
v sample_timestamp: STRING

108 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Log_Detail Sybase_Log_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v log_activity_name: STRING
v log_activity_per_second: REAL
v log_activity_per_transaction: REAL
v log_activity_count: INTEGER
v log_activity_percent: REAL
v sample_timestamp: STRING
ITM_Sybase_Physical_Device_Detail Sybase_Physical_Device_Detail attribute
group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v device_name: STRING
v physical_name: STRING
v device_reads_per_second: REAL
v device_reads_per_transaction: REAL
v device_reads_count: INTEGER
v device_reads_percent: REAL
v device_writes_per_second: REAL
v device_writes_per_transaction: REAL
v device_writes_count: INTEGER
v device_writes_percent: REAL
v device_total_per_second: REAL
v device_total_per_transaction: REAL
v device_total_count: INTEGER
v device_total_percent: REAL
v device_lock_granted_per_second: REAL
v device_lock_granted_per_transaction:
REAL
v device_lock_granted_count: INTEGER
v device_lock_granted_percent: REAL
v device_lock_contention_per_second:
REAL
v device_lock_contention_per_transaction:
REAL
v device_lock_contention_count: INTEGER
v device_lock_contention_percent: REAL
v sample_timestamp: STRING
v device_name_u: STRING
v physical_name_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 109

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Task_Detail Sybase_Task_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v task_switch_cause: STRING
v task_switch_per_second: REAL
v task_switch_per_transaction: REAL
v task_switch_count: INTEGER
v task_switch_percent: REAL
v sample_timestamp: STRING
ITM_Sybase_SQL_Detail Sybase_SQL_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v sql_activity_name: STRING
v sql_activity_per_second: REAL
v sql_activity_per_transaction: REAL
v sql_activity_count: INTEGER
v sql_activity_percent: REAL
v sample_timestamp: STRING

110 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Lock_Summary Sybase_Lock_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v lock_request_per_second: REAL
v lock_request_per_transaction: REAL
v lock_request_count: INTEGER
v lock_contention_per_second: REAL
v lock_contention_per_transaction: REAL
v lock_contention_count: INTEGER
v lock_contention_percent: REAL
v deadlocks_per_second: REAL
v deadlocks_per_transaction: REAL
v deadlocks_count: INTEGER
v deadlocks_percent: REAL
v lock_promotes_per_second: REAL
v lock_promotes_per_transaction: REAL
v lock_promotes_count: INTEGER
v lock_promotes_exclusive_per_second:
REAL
v lock_promotes_exclusive_per_transaction:
REAL
v lock_promotes_exclusive_count:
INTEGER
v lock_promotes_exclusive_percent: REAL
v lock_promotes_shared_per_second:
REAL
v lock_promotes_shared_per_transaction:
REAL
v lock_promotes_shared_count: INTEGER
v lock_promotes_shared_percent: REAL
v sample_timestamp: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 111

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Lock_Detail Sybase_Lock_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v lock_type: STRING
v lock_total_per_second: REAL
v lock_total_per_transaction: REAL
v lock_total_count: INTEGER
v lock_total_percent: REAL
v lock_granted_per_second: REAL
v lock_granted_per_transaction: REAL
v lock_granted_count: INTEGER
v lock_granted_percent: REAL
v lock_contention_per_second: REAL
v lock_contention_per_transaction: REAL
v lock_contention_count: INTEGER
v lock_contention_percent: REAL
v lock_deadlocked_per_second: REAL
v lock_deadlocked_per_transaction: REAL
v lock_deadlocked_count: INTEGER
v lock_deadlocked_percent: REAL
v sample_timestamp: STRING

112 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Cache_Summary Sybase_Cache_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v cache_search_rate: REAL
v cache_search_per_transaction: REAL
v cache_search_count: INTEGER
v cache_hit_rate: REAL
v cache_hit_per_transaction: REAL
v cache_hit_count: INTEGER
v cache_hit_percent: REAL
v cache_miss_rate: REAL
v cache_miss_per_transaction: REAL
v cache_miss_count: INTEGER
v cache_miss_percent: REAL
v lru_buffer_use_rate: REAL
v lru_buffer_use_per_transaction: REAL
v lru_buffer_use_count: INTEGER
v lru_buffer_use_percent: REAL
v mru_buffer_use_rate: REAL
v mru_buffer_use_per_transaction: REAL
v mru_buffer_use_count: INTEGER
v mru_buffer_use_percent: REAL
v large_io_performed_rate: REAL
v large_io_performed_per_transaction:
REAL
v large_io_performed_count: INTEGER
v large_io_performed_percent: REAL
v large_io_denied_rate: REAL
v large_io_denied_per_transaction: REAL
v large_io_denied_count: INTEGER
v large_io_denied_percent: REAL
v large_io_pages_cached_rate: REAL
v large_io_pages_cached_per_transaction:
REAL
v large_io_pages_cached_count: INTEGER
v large_io_pages_used_rate: REAL
v large_io_pages_used_per_transaction:
REAL
v large_io_pages_used_count: INTEGER
v large_io_pages_used_percent: REAL
v sample_timestamp: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 113

 Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Cache_Detail Sybase_Cache_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v cache_name: STRING
v cache_search_rate: REAL
v cache_search_per_transaction: REAL
v cache_search_count: INTEGER
v cache_hit_rate: REAL
v cache_hit_per_transaction: REAL
v cache_hit_count: INTEGER
v cache_hit_percent: REAL
v cache_miss_rate: REAL
v cache_miss_per_transaction: REAL
v cache_miss_count: INTEGER
v cache_miss_percent: REAL
v lru_buffer_use_rate: REAL
v lru_buffer_use_per_transaction: REAL
v lru_buffer_use_count: INTEGER
v lru_buffer_use_percent: REAL
v mru_buffer_use_rate: REAL
v mru_buffer_use_per_transaction: REAL
v mru_buffer_use_count: INTEGER
v mru_buffer_use_percent: REAL
v large_io_performed_rate: REAL
v large_io_performed_per_transaction:
REAL
v large_io_performed_count: INTEGER
v large_io_performed_percent: REAL
v large_io_denied_rate: REAL
v large_io_denied_per_transaction: REAL
v large_io_denied_count: INTEGER
v large_io_denied_percent: REAL
v large_io_pages_cached_rate: REAL
v large_io_pages_cached_per_transaction:
REAL
v large_io_pages_cached_count: INTEGER
v large_io_pages_used_rate: REAL
v large_io_pages_used_per_transaction:
REAL
v large_io_pages_used_count: INTEGER
v large_io_pages_used_percent: REAL
v sample_timestamp:STRING
v cache_name_u: STRING

114 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 10. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
ITM_Sybase_Server_Enterprise_View Sybase_Server_Enterprise_View attribute
group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v percent_max_locks: REAL
v server_cpu_percent: REAL
v total_os_cpu_percent: REAL
v time_since_startup: INTEGER
v server_version: STRING
v total_databases: INTEGER
v minimum_pct_data_freespace: REAL
v minimum_pct_log_freespace: REAL
v total_locks: INTEGER
v total_lock_conflicts: INTEGER
v database_max_locks: STRING
v database_max_blocks: STRING
v table_max_locks: STRING
v percent_process_block: REAL
v max_time_blocked: REAL
v avg_time_blocked: REAL
v server_cpu_percent_system: REAL
v server_cpu_percent_application: REAL
v total_processes: INTEGER
v total_processes_blocked: INTEGER
v age_of_last_error: INTEGER
v maximum_sev_level: STRING
v maximum_sev_timestamp: STRING
v total_errors_high_sev: INTEGER
v error_log_size: INTEGER
v current_logons: INTEGER
v percent_max_logons_active: REAL
v physical_reads_per_second: REAL
v physical_writes_per_second: REAL
v io_errors_current_interval: INTEGER
v server_status: STRING
v collection_status: STRING
v sample_timestamp: STRING
v database_max_locks_u: STRING
v database_max_blocks_u: STRING
v table_max_locks_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 115

116 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Appendix C. Problem determination
This appendix explains how to troubleshoot the IBM Tivoli Monitoring for
Databases: Sybase Server Agent. Troubleshooting, or problem determination, is the
process of determining why a certain product is malfunctioning.

Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in Chapter 2, “Requirements and configuration
for the monitoring agent,” on page 5.

This appendix provides agent-specific problem determination information. See the

IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information. Also see “Support information” on page 141 for other
problem-solving options.

Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing
with this product, gather the following information that relates to the problem:
Table 11. Information to gather before contacting IBM Software Support
Information type Description
Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectory
on the host computer. See “Trace logging” on page 118 for lists of all trace log files and
their locations. See the IBM Tivoli Monitoring User’s Guide for general information about
the IBM Tivoli Monitoring environment.
Sybase Server v Version number and patch level
information v Sample application data file (if monitoring a file)
Operating system Operating system version number and patch level
Messages Messages and other information displayed on the screen
Version numbers for Version number of the following members of the monitoring environment:
IBM Tivoli Monitoring v IBM Tivoli Monitoring. Also provide the patch level, if available.
v IBM Tivoli Monitoring for Databases: Sybase Server Agent
Screen captures Screen captures of incorrect output, if any.
(UNIX only) Core dump If the system stops on UNIX systems, collect core dump file from install_dir/bin directory,
files where install_dir is the directory path where you installed the monitoring agent.

Upload files for review to the following FTP site: ftp.emea.ibm.com. Log in as
anonymous and place your files in the directory that corresponds to the IBM Tivoli
Monitoring component that you use. See “Contacting IBM Software Support” on
page 143 for more information about working with IBM Software Support.

Built-in problem determination features

The primary troubleshooting feature in the IBM Tivoli Monitoring for Databases:
Sybase Server Agent is logging. Logging refers to the text messages and trace data
generated by the IBM Tivoli Monitoring for Databases: Sybase Server Agent.
Messages and trace data are sent to a file.

Trace data captures transient information about the current operating environment
when a component or application fails to operate as designed. IBM Software

© Copyright IBM Corp. 2005 117

 Support personnel use the captured trace information to determine the source of
an error or unexpected condition. See “Trace logging” for more information.

Problem classification
The following types of problems might occur with the IBM Tivoli Monitoring for
Databases: Sybase Server Agent:
v Installation and configuration
v General usage and operation
v Display of monitoring data
v Take Action commands

This appendix provides symptom descriptions and detailed workarounds for these
problems, as well as describing the logging capabilities of the monitoring agent.
See the IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.

Trace logging
Trace logs capture information about the operating environment when component
software fails to operate as intended. The principal log type is the RAS (Reliability,
Availability, and Serviceability) trace log. These logs are in the English language
only. The RAS trace log mechanism is available for all components of IBM Tivoli
Monitoring. Most logs are located in a logs subdirectory on the host computer. See
the following sections to learn how to configure and use trace logging:
v “Principal trace log files” on page 119
v “Examples: using trace logs” on page 121
v “Enabling detailed tracing in the collector trace log” on page 122
v “Setting RAS trace parameters” on page 124

Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as
″RAS1″.

IBM Software Support uses the information captured by trace logging to trace a
problem to its source or to determine why an error occurred. The default
configuration for trace logging, such as whether trace logging is enabled or
disabled and trace level, depends on the source of the trace logging. Trace logging
is always enabled.

Overview of log file management

Table 12 on page 120 provides the names, locations, and descriptions of RAS1 log
files. The log file names adhere to the following naming convention:
hostname_product_adaptiveservername_program_timestamp-nn.log

where:
v hostname is the host name of the machine on which the monitoring component is
running.
v product is the two-character product code. For Monitoring Agent for Sybase
Server, the product code is oy.
v adaptiveservername is the name of a database server instance that is being
monitored.

118 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 v program is the name of the program being run.
v timestamp is an 8-character hexadecimal timestamp representing the time at
which the program started.
v nn is a rolling log suffix. See “Examples of trace logging” for details of log
rolling.

Examples of trace logging

For example, if a Sybase Server database ″dbinst02″ is running on computer
″server01″, the RAS log file for the Monitoring Agent for Sybase Server might be
named as follows:
server01_oy_dbinst02_koyagent_437fc59-01.log

For long-running programs, the nn suffix is used to maintain a short history of log
files for that startup of the program. For example, the koyagent program might
have a series of log files as follows:
server01_oy_dbinst02_koyagent_437fc59-01.log
server01_oy_dbinst02_koyagent_437fc59-02.log
server01_oy_dbinst02_koyagent_437fc59-03.log

As the program runs, the first log (nn=01) is preserved because it contains program
startup information. The remaining logs ″roll." In other words, when the set of
numbered logs reach a maximum size, the remaining logs are overwritten in
sequence. Each time a program is started, a new timestamp is assigned to maintain
a short program history. For example, if the Monitoring Agent for Sybase Server is
started twice, it might have log files as follows:
server01_oy_dbinst02_koyagent_437fc59-01.log
server01_oy_dbinst02_koyagent_437fc59-02.log
server01_oy_dbinst02_koyagent_437fc59-03.log

server01_oy_dbinst02_koyagent_537fc59-01.log
server01_oy_dbinst02_koyagent_537fc59-02.log
server01_oy_dbinst02_koyagent_537fc59-03.log

Each program that is started has its own log file. For example, the Monitoring
Agent for Sybase Server would have agent logs in this format:
server01_oy_dbinst02_koyagent_437fc59-01.log

Other logs, such as logs for collector processes and Take Action commands, have a
similar syntax, as in the following example:
server01_oy_dbinst02_koysql_447fc59-01.log

where koyesql is the name of a program.

Note: When you communicate with IBM Software Support, you must capture and
send the RAS1 log that matches any problem occurrence that you report.

Principal trace log files

Table 12 on page 120 contains locations, file names, and descriptions of trace logs
that can help determine the source of problems with agents.

Appendix C. Problem determination 119

Table 12. Trace log files for troubleshooting agents
System where log File name and path Description
is located
On the computer The RAS1 log files are named Traces activity of the monitoring agent.
that hosts the hostname_oy_adaptiveservername_program_timestamp- Note: Other logs, such as logs for
monitoring agent nn.log and are located in the following path: collector processes and Take Action
v On Windows: install_dir\tmaitm6\logs commands (if available), have a
See “Definitions of similar syntax and are located in this
variables” on page v On UNIX: install_dir/logs
directory path.
121 for Note: File names for RAS1 logs include a hexadecimal
descriptions of the time stamp.
variables in the
file names in Also on UNIX, a log with a decimal time stamp is
column two. provided: hostname_oy_timestamp.log and
hostname_oy_timestamp.pidnnnnn in the
install_dir/logs path, where nnnnn is the process ID
number.
On Windows: The collector trace log file is named A collector trace log file is produced
hostname_oy_adaptiveservername_col.outThe file is by Monitoring Agent for Sybase
located in the install_dir\tmaitm6\logs path. Server.
v On Windows: New log files are
On UNIX: The collector trace log file is named
created each time the agent is
hostname_oy_adaptiveservername_col.log and is
started. One backup copy, renamed
located in the install_dir/logs path.
from *.out to *.ou1, is kept for
Note: A hostname_oy_adaptiveservername_col.out log
historical purposes. The log file is
file also exists and contains stderr and stdout
not pruned.
messages.
v On UNIX: New log files are created
each time the agent is started. One
backup copy, renamed from *.log to
*.lo1 is kept for historical purposes.
The log file is not pruned.
See “Enabling detailed tracing in the
collector trace log” on page 122 to
learn how to change the default
behavior of this type of logging.
On Windows: The "agt" trace log file is named Traces activity of the monitoring agent.
hostname_OY_adaptiveservername_agt.out. The file is v On Windows: New log files are
located in the install_dir\tmaitm6\logs path. created each time the agent is
started. One backup copy, renamed
On UNIX: The "agt" trace log file is named
from *.out to *.ou1, is kept for
hostname_oy_adaptiveservername_agt.log and is
historical purposes. The log file is
located in the install_dir/logs path. See “Definitions
not pruned.
of variables” on page 121.
v On UNIX:New log files are created
each time the agent is started. One
backup copy, renamed from *.log to
*.lg1 is kept for historical purposes.
The *SYB.LG0 file is located in the following path: A new version of this file is generated
v On Windows: install_dir\tmaitm6\logs every time the agent is restarted. IBM
Tivoli Monitoring generates one
v On UNIX: install_dir/logs
backup copy of the *SYB.LG0 file with
the tag .LG1. View *SYB.LG0 to learn
the following details regarding the
current monitoring session:
v Status of connectivity with the
monitoring server.
v Situations that were running.
v The success or failure status of Take
Action commands.
120 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 12. Trace log files for troubleshooting agents (continued)
System where log File name and path Description
is located
On the Tivoli On UNIX: The candle_installation.log file in the Provides details about products that
Enterprise install_dir/logs path. are installed.
Monitoring Server Note: Trace logging is enabled by
On Windows: The file in the install_dir\InstallITM default. A configuration step is not
See “Definitions of path. Unlike RAS1 log files, the name of the file required to enable this tracing.
variables” for displays a decimal time stamp. *
descriptions of the
The Warehouse_Configuration.log file is located in the Provides details about the
variables in the
following path on Windows: install_dir\InstallITM. configuration of data warehousing for
file names in
historical reporting.
column two.
The RAS1 log file is named hostname_ms_timestamp- Traces activity on the monitoring
nn.log and is located in the following path: server.
v On Windows: install_dir\logs
v On UNIX: install_dir/logs
Note: File names for RAS1 logs include a hexadecimal
time stamp

Also on UNIX, a log with a decimal time stamp is

provided: hostname_ms_timestamp.log and
hostname_ms_timestamp.pidnnnnn in the
install_dir/logs path, where nnnnn is the process ID
number.
On the Tivoli The RAS1 log file is named hostname_cq_timestamp- Traces activity on the portal server.
Enterprise Portal nn.log and is located in the following path:
Server v On Windows: install_dir\logs
See “Definitions of v On UNIX: install_dir/logs
variables” for Note: File names for RAS1 logs include a hexadecimal
descriptions of the time stamp
variables in the
file names in Also on UNIX, a log with a decimal time stamp is
column two. provided: hostname_cq_timestamp.log and
hostname_cq_timestamp.pidnnnnn in the install_dir/logs
path, where nnnnn is the process ID number.
The TEPS_ODBC.log file is located in the following path When you enable historical reporting,
on Windows: install_dir\InstallITM. this log file traces the status of the
warehouse proxy agent.
Definitions of variables for RAS1 logs:
v hostname is the host name of the machine on which the agent is running.
v install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can
represent a path on the computer that hosts the monitoring server, the monitoring agent, or the portal server.
v product is the two character product code. For Monitoring Agent for Sybase Server, the product code is oy.
v adaptiveservername refers to the name of the database server instance that you are monitoring.
v program is the name of the program being run.
v timestamp is an eight-character hexadecimal time stamp representing the time at which the program started.
v nn is a rolling log suffix. See “Examples of trace logging” on page 119 for details of log rolling.

See the IBM Tivoli Monitoring Installation and Setup Guide for more information on
the complete set of trace logs that are maintained on the monitoring server.

Examples: using trace logs

Typically IBM Software Support applies specialized knowledge to analyze trace
logs to determine the source of problems. However, you can open trace logs in a
text editor to learn some basic facts about your IBM Tivoli Monitoring
environment.

Appendix C. Problem determination 121

 Example one
This excerpt shows the typical .LG0 log for a failed connection between a
monitoring agent and a monitoring server with the host name server1a:
(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,
"location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect to
broker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK
(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable
to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>
Example two
The following excerpts from the trace log for the monitoring server show the
status of an agent, identified here as ″Remote node.″ The name of the
computer where the agent is running is SERVER5B:
(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:KOY is ON-LINE.
. . .
(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:KOY is OFF-LINE.

Key points regarding the preceding excerpt:

v The monitoring server appends the KOY product code to the server
name to form a unique name (SERVER5B:KOY) for this instance of
Monitoring Agent for Sybase Server. This unique name enables you to
distinguish multiple monitoring products that might be running on
SERVER5B.
v The log shows when the agent started (ON-LINE) and later stopped
(OFF-LINE) in the environment.
v For the sake of brevity an ellipsis (...) represents the series of trace log
entries that were generated while the agent was running.
v Between the ON-LINE and OFF-LINE log entries, the agent was
communicating with the monitoring server.
v The ON-LINE and OFF-LINE log entries are always available in the
trace log. All trace levels that are described in “Setting RAS trace
parameters” on page 124 provide these entries.

On Windows, you can use the following alternate method to view trace logs:
1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring >
Manage Tivoli Monitoring Service. The Manage Tivoli Enterprise Monitoring
Services window is displayed.
2. Right-click a component and select Advanced > View Trace Log in the pop-up
menu. The program displays the Select Log File window that lists the RAS1
logs for the monitoring agent.
3. Select a log file from the list and click OK. You can also use this viewer to
access remote logs.

Note: The viewer converts time stamps in the logs to a readable format.

Enabling detailed tracing in the collector trace log

Collector trace logs are generated by a database monitoring agent. You can use the
following options to modify collector trace logging.

Option one: modify the settings file

Perform the following steps to enable detailed logging for the collector trace log:
1. Open the koytrac.ctl file.
The file is located in the following path:

122 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 v On Windows: install_dir\tmaitm6
v On UNIX systems: install_dir/misc
where install_dir is the location of the IBM Tivoli Monitoring component.
2. Remove the two semicolons (;;) from the beginning of the line that contains
trace_all;.
3. Save the file.
4. Restart the monitoring agent for the database server instance that you want to
trace. Logging goes to a collector trace log file that is named in Table 12 on
page 120.
The log file is stored in the following path:
v On Windows: install_dir\tmaitm6\logs
v On UNIX systems: install_dir/logs
where install_dir is the path where you installed IBM Tivoli Monitoring.
5. When you complete an analysis of detailed trace logs, turn off detailed logging
as follows, because trace logs can consume a large amount hard disk space.
a. Open the koytrac.ctl file mentioned in Step 1.
b. Type two semicolons (;;) at the beginning of the line that contains trace_all;.
c. Save the file.
d. Restart the monitoring agent for the database server instance that you have
been tracing.

Option two: modify the environment variables

You can modify trace logging for the collector log by setting the following
environment variables:
COLL_WRAPLINES
By default, new collector log files are created each time you start the agent
or when the log file reaches the limit specified by the COLL_WRAPLINES
environment variable. COLL_WRAPLINES defines the number of lines in
the col.out file and is 30,000 lines by default (about 2 MB).
COLL_NUMOUTBAK
By default, the product creates one backup copy of the collector log file.
The file tag is changed from *.out to *.ou1. You can configure the product
to create up to nine backup files by defining COLL_NUMOUTBAK to be
an integer from one to nine.

Set the environment variables as follows:

v On UNIX: Use a text editor to enter a new integer value for the variables in the
hostname_oy_adaptiveservername_name.cfg file in the install_dir/config
directory. (If you want your changes to affect all monitoring agents that are
running on the computer, modify the oy.ini file.) Save your changes and restart
the agent.
v On Windows:
1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring
> Manage Tivoli Monitoring Service. The Manage Tivoli Enterprise
Monitoring Services window is displayed.
2. Right-click the row that contains the name of the monitoring agent whose
environment variables you want to set.
3. Select Advanced > Edit Variables in the pop-up menu.
4. If the agent is running, accept the prompt to stop the agent. A restart is
necessary so that the environment variable that you create takes effect.
Appendix C. Problem determination 123
 5. The list dialog is displayed. When only the default settings are in effect, there
are no variables displayed. The variables are listed after you override them.
6. Override the variable settings as follows:
a. Click Add.
b. Select the variable you want to modify in the Variable pulldown menu.
For example, select COLL_NUMOUTBAK.
c. Type a value in the Value field. For example, type the number 9, the
maximum number of backup files that can be generated.
d. Select OK two times.
e. Restart the agent.

Setting RAS trace parameters

Objective
Pinpoint a problem by setting detailed tracing of individual components of the
monitoring agent and modules.

Background Information
Monitoring Agent for Sybase Server uses RAS1 tracing and generates the logs
described in Table 12 on page 120. The default RAS1 trace level is ERROR.

RAS1 tracing has control parameters to manage to the size and number of RAS1
logs. Use the procedure described in this section to set the parameters.

Note: The KBB_RAS1_LOG parameter also provides for the specification of the
log file directory, log file name, and the inventory control file directory and
name. Do not modify these values or log information can be lost.

Before you begin

See “Overview of log file management” on page 118 to ensure that you understand
log rolling and can reference the correct log files when you managing log file
generation.

After you finish

Monitor the size of the logs directory. Default behavior can generate a total of 45 to
60 MB for each agent that is running on a computer. For example, each database
server instance that you monitor could generate 45 to 60 MB of log data. See the
″Procedure″ section to learn how to adjust file size and numbers of log files to
prevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlike
the RAS1 log files which are pruned automatically, other log types can grow
indefinitely, for example, the logs in Table 12 on page 120 that include a process ID
number (PID).

Consider using collector trace logs (described in Table 12 on page 120) as an

additional source of problem determination information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can
generate a large amount of trace logging. Use them only temporarily, while
you are troubleshooting problems. Otherwise, the logs can occupy excessive
amounts of hard disk space.

124 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Procedure
Specify RAS1 trace options in the install_dir\tmaitm6\KOYENV file on Windows or
the install_dir/config/oy.ini file on UNIX systems.

Note: On UNIX, the trace options that you set in the oy.ini file apply to all
database server instances that you are monitoring on the computer where
oy.ini is located. An additional trace options file,
hostname_oy_adaptiveservername.cfg, exists for each database server
instance. The hostname_oy_adaptiveservername.cfg file inherits its settings
from the oy.ini file. If you want to set trace options for a specific instance
only, modify options in the hostname_oy_adaptiveservername.cfg file.
Use one of the following methods to modify trace options:
v Manually edit the configuration file to set trace logging
1. Open the trace options file:
– On Windows, open the install_dir\tmaitm6\KOYENV file.
– On UNIX systems, open the /install_dir/config/oy.ini file.
2. Edit the line that begins with KBB_RAS1= to set trace logging preferences.
For example, if you want detailed trace logging, set the Maximum Tracing
option:
– On Windows,
KBB_RAS1=ERROR (UNIT:kdd ALL) (UNIT:koy ALL) (UNIT:kra ALL)
– On UNIX systems,
export KBB_RAS1=’ERROR (UNIT:kdd ALL) (UNIT:koy ALL) (UNIT:kra ALL)’
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation
of log files:
– Edit the following parameters to adjust the number of rolling log files and
their size.
- MAXFILES: the total number of files that are to be kept for all startups
of a given program. Once this value is exceeded, the oldest log files are
discarded. Default value is 9.
- LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file.
Default value is 5.
– IBM Software Support might guide you to modify the following
parameters:
- COUNT: the number of log files to keep in the rolling cycle of one
program startup. Default value is 3.
- PRESERVE: the number of files that are not to be reused in the rolling
cycle of one program startup. Default value is 1.

Note: The KBB_RAS1_LOG parameter also provides for the specification of

the log file directory, log file name, and the inventory control file
directory and name. Do not modify these values or log information
can be lost.
4. Restart the monitoring agent so that your changes take effect.
v (Windows only) Alternate method to edit trace logging parameters:
1. Open the Manage Tivoli Enterprise Monitoring Services window.
2. Right-click the icon of the monitoring agent whose logging you want to
modify.
3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring
Server Trace Parameters window is displayed.

Appendix C. Problem determination 125

 4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters
field or type a valid string.
The selections are as follows:
– No error tracing. KBB_RAS1=-none-
– General error tracing. KBB_RAS1=ERROR
– Intensive error tracing. KBB_RAS1=ERROR (UNIT:koy ALL)
– Maximum error tracing. KBB_RAS1=ERROR (UNIT:koy ALL) (UNIT:kra ALL)

Note: As this example shows, you can set multiple RAS tracing options in
a single statement.
5. Modify the value for ″Maximum Log Size Per File (MB)″ to change the log
file size (changes LIMIT value).
6. Modify the value for ″Maximum Number of Log Files Per Session″ to change
the number of logs files per startup of a program (changes COUNT value).
7. Modify the value for ″Maximum Number of Log Files Total″ to change the
number of logs files for all startups of a program (changes MAXFILES
value).
8. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log
information that can help you diagnose communications and connectivity
problems between the monitoring agent and the monitoring server.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can
generate a large amount of trace logging. Use them only temporarily,
while you are troubleshooting problems. Otherwise, the logs can
occupy excessive amounts of hard disk space.
9. Click OK. You see a message reporting a restart of the monitoring agent so
that your changes take effect.

Problems and workarounds

The following sections provide symptoms and workarounds for problems that
might occur with Monitoring Agent for Sybase Server:
v “Installation and configuration problem determination” on page 126
v “Agent problem determination” on page 134
v “Tivoli Enterprise Portal problem determination” on page 136
v “Workspace problem determination” on page 137
v “Problem determination for remote deployment” on page 136
v “Situation problem determination” on page 137
v “Problem determination for Sybase” on page 140

Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in Chapter 2, “Requirements and configuration
for the monitoring agent,” on page 5.
This appendix provides agent-specific problem determination information. See the
IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.

Installation and configuration problem determination

This section provides tables that show solutions for the following types of
installation, configuration, and uninstallation problems:
v Operating system problems

126 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 v Problems with database applications
Table 13. Problems and solutions for installation and configuration for agents that run on UNIX systems
Problem Solution
When you upgrade to IBM Tivoli Fixpacks for Candle, Version 350, are delivered as each monitoring agent is
Monitoring, you might need to apply upgraded to IBM Tivoli Monitoring.
fixpacks to Candle, Version 350, agents. Note: The IBM Tivoli Monitoring download image or CD provides
application fixpacks for the monitoring agents that are installed from that
CD (for example, the agents for operating systems such as Windows,
Linux, UNIX, and i5/OS). The upgrade software for other agents is located
on the download image or CDs for that specific monitoring agent, such as
the agents for database applications.

If you do not upgrade the monitoring agent to IBM Tivoli Monitoring, the
agent continues to work. However, you must upgrade to have all the
functionality that IBM Tivoli Monitoring offers.
Presentation files and customized The upgrade from version 350 to IBM Tivoli Monitoring handles export of
Omegamon DE screens for Candle the presentation files and the customized Omegamon DE screens.
monitoring agents need to be
upgraded to a new Linux on z/Series
system.
Non-ASCII characters entered into the Enter only ASCII characters into these fields.
configuration window for the
monitoring agent do not show up or
are not the correct characters.
During the command-line installation, You must exit and restart the installation process. You cannot return to the
you choose to install a component that list where you selected components to install. When you run the installer
is already installed, and you see the again, do not attempt to install any component that is already installed.
following warning:
WARNING - you are about to install
the SAME version of "component"

where component is the name of the

component that you are attempting to
install.
Note: This problem affects UNIX
command-line installations. If you
monitor only Windows environments,
you would see this problem if you
choose to install a product component
(for example, a monitoring server) on
UNIX.
While installing the agent from a CD, This error is caused by low disk space. Although the install.sh script
the following message is displayed indicates that it is ready to install the agent software, the script considers
and you are not able to continue the the size of all tar files, not the size of all the files that are contained within
installation: the tar file.Run the df -k command to check whether the file systems have
install.sh warning: unarchive of enough space to install agents.
"/cdrom/unix/filename.tar" may
have failed
Cannot locate the KDCB0_HOSTNAME Go to install_dir/config and edit the corresponding .ini file. Set the
setting. KDCB0_HOSTNAME parameter followed by the IP address. If you use multiple
network interface cards (NICs), give the Primary IP address of the network
interface.

Appendix C. Problem determination 127

Table 13. Problems and solutions for installation and configuration for agents that run on UNIX systems (continued)
Problem Solution
The Monitoring Agent for Sybase You can collect data to analyze this problem as follows:
Server repeatedly restarts. 1. Access the install_dir/config/oy.ini file, which is described in
“Setting RAS trace parameters” on page 124.
2. Add the following line: KBB_SIG1=trace –dumpoff
Agents in the monitoring environment Configure both the monitoring server and the Warehouse proxy server to
use different communication protocols. accept multiple protocols, as described in the IBM Tivoli Monitoring
For example, some agents have Installation and Setup Guide.
security enabled and others do not.
Creating a firewall partition file: The How it works: When the agents start, they search KDCPARTITION.TXT for
partition file enables an agent to the following matches:
connect to the monitoring server v An entry that matches the partition name OUTSIDE.
through a firewall.
v An entry that also includes a valid external address.
For more information, see the IBM Tivoli Monitoring Installation and Setup
Guide.
You successfully migrate a Candle Copy the attribute files for the upgraded Candle monitoring agent to
monitoring agent to IBM Tivoli install_dir\tmaitm6\attrlib on the computer where you have installed
Monitoring, Version 6.1.0. However, the Warehouse Proxy. The Warehouse Proxy must be able to access the
when you configure historical data short attribute names for tables and columns. That way, if the longer
collection, you see an error message versions of these names exceed the limits of the Warehouse database, the
that includes, Attribute name may be shorter names can be substituted.
invalid, or attribute file not
installed for warehouse agent.
The monitoring agent does not start in Check the agent configuration to ensure that all the values are correctly
a non-ASCII environment. represented. To view these parameters, go to the Manage Tivoli Enterprise
Monitoring Services window, select the agent template, and choose the
Configure using defaults. From the resulting window, select and edit the
database instance to view its parameters.

Table 14. Problems and solutions for installation and configuration for agents that run on Windows systems
Problem Solution
When you upgrade to IBM Tivoli Fixpacks for Candle, Version 350, are delivered as each monitoring agent is
Monitoring, you might need to upgraded to IBM Tivoli Monitoring.
apply fixpacks to Candle, Version Note: The IBM Tivoli Monitoring download image or CD provides application
350, agents. fixpacks for the monitoring agents that are installed from that CD (for example,
the agents for operating systems such as Windows, Linux, UNIX, and i5/OS).
The upgrade software for other agents is located on the download image or CDs
for that specific monitoring agent, such as the agents for database applications.

If you do not upgrade the monitoring agent to IBM Tivoli Monitoring, the agent
continues to work. However, you must upgrade to have all the functionality that
IBM Tivoli Monitoring offers.
Presentation files and customized The upgrade from version 350 to IBM Tivoli Monitoring handles export of the
Omegamon DE screens for presentation files and the customized Omegamon DE screens.
Candle monitoring agents need to
be upgraded to a new Linux on
z/Series system.

128 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 14. Problems and solutions for installation and configuration for agents that run on Windows
systems (continued)
Problem Solution
Diagnosing problems with When you have problems with browse settings, perform the following steps:
product browse settings. 1. Click on Start > Programs > IBM Tivoli Monitoring > Manage Tivoli
Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring
Services is displayed.
2. Right-click the Windows agent and select Browse Settings. A text window is
displayed.
3. Click Save As and save the information in the text file. If requested, you can
forward this file to IBM Software Support for analysis.
A message similar to ″Unable to If a message similar to ″Unable to find running CMS on CT_CMSLIST″ is
find running CMS on displayed in the Log file, the agent is not able to connect to the monitoring
CT_CMSLIST″ in the log file is server. Confirm the following points:
displayed. v Do multiple network interface cards (NICs) exist on the system?
v If multiple NICs exist on the system, find out which one is configured for the
monitoring server. Ensure that you specify the correct host name and port
settings for communication in the IBM Tivoli Monitoring environment.
You successfully migrate a Candle Copy the attribute files for the upgraded Candle monitoring agent to
monitoring agent to IBM Tivoli install_dir\tmaitm6\attrlib on the computer where you have installed the
Monitoring, Version 6.1.0. Warehouse Proxy. The Warehouse Proxy must be able to access the short
However, when you configure attribute names for tables and columns. That way, if the longer versions of these
historical data collection, you see names exceed the limits of the Warehouse database, the shorter names can be
an error message that includes, substituted.
Attribute name may be invalid,
or attribute file not installed
for warehouse agent.
The monitoring agent does not Check the agent configuration to ensure that all the values are correctly
start in a non-ASCII environment. represented. To view these parameters, go to the Manage Tivoli Enterprise
Monitoring Services window, select the agent template, and choose the
Configure using defaults. From the resulting window, select and edit the
database instance to view its parameters.

The following table shows problems and solutions for database agents Microsoft
SQL Server, Sybase, and Oracle. However, these points do not apply to IBM DB2.

Appendix C. Problem determination 129

Table 15. Problems and solutions for installation and configuration of specific database agents: Microsoft SQL Server,
Sybase, and Oracle
Problem Solution
The procedure for launching This problem happens when the trace options file is missing. You can
Monitoring Agent for Sybase Server: correct the problem as follows:
Trace Parameters window in“Setting 1. Create a text file with the following path name:
RAS trace parameters” on page 124
v On Windows systems: install_dir\tmaitm6\KOYENV
fails.
v On UNIX systems: /install_dir/config/oy.ini
2. Paste the following configuration setting in the file:
v On Windows:
KBB_RAS1=ERROR ^> C:\IBM\ITM\tmaitm6\logs\KOYRAS1.LOG

Note: If you installed the product in a directory path other than the
default, use that directory path instead of C:\IBM\ITM.
v On UNIX systems:
export KBB_RAS1=’ERROR’

Note: If you installed the product in a directory path other than the
default, use that directory path instead.
1. Save your changes.
2. Repeat the “Setting RAS trace parameters” on page 124 procedure. Now
the Tivoli Enterprise Monitoring Server: Trace Parameters window is
displayed.
Collector trace logs are not receiving Review the information in “Trace logging” on page 118 to ensure that you
error information. are consulting the correct log file. The file is located in the following path:
install_dir\tmaitm6, where install_dir is the location of IBM Tivoli
Monitoring.
After running the agent successfully, Consult the list of supported versions in the configuration chapter of the
you reinstall the agent software, and agent user’s guide for Sybase. Confirm that you are running a valid version
collection of monitoring data stops. of the target application. If you are monitoring a supported version of the
database application, gather log files and other information and contact
IBM Software Support, as described in “Gathering product information for
IBM Software Support” on page 117.
Alert summary report of Tivoli Ensure that the COLL_ERRORLOG setting defines a valid path. Confirm
Enterprise Portal shows no that the error log file is correct. If the error log file is correct, the problem
information. can occur because the logon account that you are using does not have
sufficient permissions in the IBM Tivoli Monitoring environment.
Error counts are displayed in the Alert Check the time stamp for the reports. If you have set up historical data
summary report in the Tivoli collection for Alert summary report, it is recommended that you set up
Enterprise Portal, however, error historical data collection for the Alert detail report, too.
messages are not displayed in the
Alert detail report.

130 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 15. Problems and solutions for installation and configuration of specific database agents: Microsoft SQL Server,
Sybase, and Oracle (continued)
Problem Solution
(Sybase and Oracle only) Problems with Specifically, you might see an error like the following in the collector trace
database connectivity occur because log:
the KOYGRANT script is not run. v In Sybase: The Sybase agent displays the following message:
YEM0155E (193633) Failed to open SYBASE Server connection \
YCD0130E (193633)
Unable to connect to SYBASE server:HDCHASDSTC0041,
id:tivoli, Retcode= 0
v In Oracle: The Oracle agent displays -942 error in the collector log file as
shown in this excerpt:
RPF0340T (5/19/05) Time = 2005/05/19 15:07:40 For cursor KSS5, \
rows collected for insert = 1
RPF0300T (5/19/05) Doing prep_l_fet for cursor KSS6
RSC0200I (5/19/05) SQLCODE for PREPARE = -942
RSC0205T (5/19/05) Stmt = SELECT max(bytes) MAXLOGBYTE FROM \
v$log
RSC0220W (5/19/05) ORACLE Message ORA-00942: table or view does \
not exist for PREPARE
CGN1521E (5/19/05) Interval collection failed for cursor KORSRVR

After installation, run the koygrant.sql script to obtain a connection ID, as

described in Chapter 2, “Requirements and configuration for the
monitoring agent,” on page 5.

To collect data, the agent must have the DBA select privilege on the Sybase
system tables.
After the agent starts the ’kddos When the tmp directory path is inaccessible two things happen:
isremote failed, no localization’ v The logs are stored in the install_dir/logs directory
message is displayed.
v The message kddos isremote failed, no localization is displayed as
shown in this excerpt:
$ ./CandleAgent start oy
CandleAgent : installer level 350 / 547.
CandleAgent : considering servers: name.
kddexec: kddos isremote failed, no localization
Collector and Agent started for name

You can safely ignore this message.

You see the following error message Run the itmcmd config -A oy command under install_dir/bin directory
when you execute itmcmd config. to configure the monitoring agent. It calls the kddfind.sh script internally.
Your kddos root permission is not The kddfind.sh script is located under install_dir/OS_dir/bin directory.
set. This will impede database The kddfind.sh script uses kddos and kddos64 internally. If you have not
self-discovery. Please exit and set root permissions or setuid, you get this error message whenever
have the superuser issue the itmcmd config starts. You must change the owner and setuid of kddos
following commands: (and kddos64) before executing itmcmd config -A oy, as in this example:
$su –root
cd /ct99r1e/slee/AIX5
# cd install_dir/$OSsubdir/bin
chown root */bin/kddos
# chown root kddos
chmod u+sx */bin/kddos
# chmod u+sx kddos
Press enter to continue, or type
"exit" to exit.
On HP-UX and SunOS, you have to make the same settings for kddos64, as
The full text of this message is in this example:
provided in the next row. # chown root kddos64
# chmod u+sx kddos64

Appendix C. Problem determination 131

Table 15. Problems and solutions for installation and configuration of specific database agents: Microsoft SQL Server,
Sybase, and Oracle (continued)
Problem Solution
Sample itmcmd config -A oy error message:
$ ./itmcmd config -A oy
Candle DB config: Welcome to CandleDBconfig 07/07/05 8:46
__________________________________________________________________

CandleDBconfig prepares the environment to run the Omegamon Monitoring Agent

(OMA) for distributed databases. CandleDBconfig:

1. Prepares a configuration file for each monitored server, so that the OMA
knows how to talk to the database.

2. Verifies that the installation is correct and operational.

CandleDBconfig finds running databases much more easily and reliably than
non-running databases. If you want to monitor databases that are not currently
running, you might wish to exit CandleDBConfig and start them.

Also, CandleDBconfig works best if you have more than 25 display lines. Both
X-Windows and NT Telnet allow you to expand the number of lines without
disconnecting from UNIX. You don’t have to issue any UNIX commands to take
advantage of the increased lines.

Your kddos root permission is not set. This will impede database self-
discovery. Please exit and have the super-user issue the following commands:

cd /ct99r1e/slee/AIX5
chown root */bin/kddos
chmod u+sx */bin/kddos
Press enter to continue, or type "exit" to exit.
Unique names for monitoring IBM Tivoli Monitoring might not be able to generate a unique name for
components: ORIGINNODE is monitoring components due to the truncation of names that the product
truncated and doesn’t show the automatically generates. IBM Tivoli Monitoring automatically creates a
product code. name for each monitoring component by concatenating the subsystem
name, host name, and product code separated by colons
(subsystem_name:hostname:OY).
Note: When you monitor a multinode systems, like databases, IBM Tivoli
Monitoring uses a database instance name as the subsystem name.

The length of the name that IBM Tivoli Monitoring generates is limited to
32 characters. Truncation can result in multiple components having the
same 32-character name. If this problem happens, shorten the
subsystem_name portion of the name as described in the steps in the
following rows:

132 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 15. Problems and solutions for installation and configuration of specific database agents: Microsoft SQL Server,
Sybase, and Oracle (continued)
Problem Solution

v On Windows:
Note: This procedure involves editing the Windows Registry. An error in editing the Registry may cause other
system errors. It is best practice to make a backup copy of the Registry prior to modifying the Registry. If you do
not feel comfortable editing the Registry, contact IBM Software Support.
1. Run the Registry editor, regedit. Select Start > Run. Type regedit in the field and click OK.
2. Locate the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KOY\610\instance_name

where instance_name is the Sybase Server instance name that is associated with the target agent.
3. Open the Environment key.
4. Select the CTIRA_SUBSYSTEM_ID string attribute. If you do not find CTIRA_SUBSYSTEM_ID, add it. step
6. Type a new name for an instance name( subsystem name) For the step 4 -6, if user can’t find
CTIRA_SUBSYSTEM_ID, add it.
5. Right-click and select Modify.
6. Type a new instance name (subsystem name). Keep in mind that the final concatenated name, including the
subsystem name, host name, and OY, cannot be longer than 32 characters.
Note: You must ensure that the resulting name is unique with respect to any existing monitoring component
that was previously registered with the Tivoli Enterprise Monitoring Server.
7. Exit from the Registry editor.
8. Restart the agent.
9. A second instance in the Tivoli Enterprise Portal navigation tree might be automatically added. If this
happens, clear the old, offline agent instance navigation item using the Managed System Status workspace of
the Enterprise navigation tree item.

v On UNIX:
1. Open the configuration file for the monitoring agent, which is located in the following path:
install_dir/config/hostname_oy_instancename.cfg
2. Find the line the begins with CTIRA_SUBSYSTEM_ID=.
3. Type a new name for instance name (subsystem_name) that is a unique, shorter name for the instance name
(subsystem_name). The final concatenated name including the subsystem name, new host name, and OY, cannot
be longer than 32 characters.
Note: You must ensure that the resulting name is unique with respect to any existing monitoring component
that was previously registered with the Tivoli Enterprise Monitoring Server.
4. Save the file.
5. Restart the agent.
If you cannot find the CTIRA_SUBSYSTEM_ID environment variable, you must add it to the configuration file
of the monitoring agent. Open hostname_oy_instancename.cfg and add CTIRA_SUBSYSTEM_ID with the new instance
name.

Table 16. General problems and solutions for uninstallation

Problem Solution
On Windows, uninstallation of Be sure that you follow the general uninstallation process described in the IBM
IBM Tivoli Monitoring fails to Tivoli Monitoring Installation and Setup Guide:
uninstall the entire environment. 1. Uninstall monitoring agents first, as in the following examples:
v Uninstall a single monitoring agent for a specific database.
—OR—
v Uninstall all instances of a monitoring product, such as IBM Tivoli
Monitoring for Databases.
2. Uninstall IBM Tivoli Monitoring.

Appendix C. Problem determination 133

Table 16. General problems and solutions for uninstallation (continued)
Problem Solution
The way to remove inactive When you want to remove a managed system from the navigation tree,
managed systems (systems whose right-click the item that you want to remove, and select Remove managed
status is OFFLINE) from the system.
Enterprise navigation tree in the
portal is not obvious.

Agent problem determination

This section lists problems that might occur with agents.

This appendix provides agent-specific problem determination information. See the

IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.
Table 17. General agent problems and solutions
Problem Solution
When you edit the configuration for an existing The original configuration settings might include
monitoring agent, the values displayed are not correct. non-ASCII characters. These values were stored incorrectly
and result in the incorrect display. Enter new values using
only ASCII characters.
A problem can arise when you run multiple agents on You must reconfigure the previously existing agents to
one computer and want them to communicate with restore their communication connection with TEMS1. For
multiple monitoring servers, as described in this example, you can right-click the row for a specific agent in
example: the Manage Tivoli Enterprise Monitoring Services, and
v Agents are running on computer and communicating select Reconfigure. See the IBM Tivoli Monitoring
with a Tivoli Enterprise Monitoring Server, called Installation and Setup Guide for more information on
TEMS1. reconfiguration.
v You install a new agent on the same computer and
you want this agent to communicate with a different
monitoring server, called TEMS2.
v When you configure the new agent to communicate
with TEMS2, all the existing agents are re-configured
to communicate with TEMS2.
The system experiences high CPU usage after you View the memory usage of the KOYCMA process. If CPU
install or configure Monitoring Agent for Sybase Server. usage seems to be excessive, recycle the monitoring agent.

Table 18. Agent problems and solutions on the UNIX operating system
Problem Solution
You see an unknown instance of The verification process for Monitoring Agent for Sybase Server creates a Sybase
the monitoring agent for Sybase server instance called koyagent. The system creates this instance to validate the
called koyagent in the Tivoli connection to the Tivoli Enterprise Monitoring Server. The Tivoli Enterprise
Enterprise Portal. Portal shows an entry for this Sybase server instance, even though that instance
only exists during the verification steps. To remove this instance from Tivoli
Enterprise Portal, follow the standard process for removing an instance on the
Tivoli Enterprise Portal.

134 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 18. Agent problems and solutions on the UNIX operating system (continued)
Problem Solution
Agent unable to connect: The This error message means that the agent is not able to connect to the computer
agent is started, but no reports where the Tivoli Enterprise Monitoring Server is running. The reason might be
are displayed on Tivoli any one of the following:
Enterprise Monitoring Server. Computer where the Tivoli Enterprise Monitoring Server is running is down
The log file includes the Ping the computer where the Tivoli Enterprise Monitoring Server is running
following error: and make sure that it is up and running.
Unable to find running CMS on Tivoli Enterprise Monitoring Server is not running
CMSLIST or Endpoint If the Tivoli Enterprise Monitoring Server is not running, recycle the Tivoli
unavailable Enterprise Monitoring Server and verify whether the agent is connecting.
Multiple NIC Cards on the computer where the Tivoli Enterprise Monitoring
Server is running.
If multiple NICs are installed on the computer where the Tivoli Enterprise
Monitoring Server is running, identify the Primary NIC and use the hostname
or IP address.
Verify that the Tivoli Enterprise Monitoring Server has been configured with
the Primary NIC’s IP address or hostname.
If you are using hostname, make sure that /etc/hosts has a valid entry for the
Primary NICs host name and its IP address.
On the Tivoli Enterprise Monitoring Server set the KDCB0_HOSTNAME
variable to the primary IP address of the computer. Use the same address to
configure the agent.
To connect to the Tivoli Enterprise Monitoring Server, configure the agent
with Primary NIC’s IP address or host name of the computer where the
Tivoli Enterprise Monitoring Server is running.
While configuring the agent, make sure that the port number that you are
connecting to is correct. If you are not using the default port number, make
sure that you are using the same port number used in Tivoli Enterprise
Monitoring Server. For more information, see the IBM Tivoli Monitoring
Installation and Setup Guide.
Agent is behind the Firewall
If you use a Firewall, identify whether you have any one of the following
scenarios:
v Hub monitoring server INSIDE, and agents OUTSIDE
v Hub and remote monitoring servers INSIDE, agents OUTSIDE
v Hub monitoring server INSIDE, remote monitoring server and agents
OUTSIDE
See Creating a firewall partition file for information about the
KDC_PARTITION file that enables communication across a firewall. For
additional information, see the IBM Tivoli Monitoring Installation and Setup
Guide.
Connecting to the monitoring server through a Virtual Private Network (VPN)
In some cases, the agent or a remote monitoring server needs to connect to
the hub monitoring server through a VPN. You must configure the
communication channel (pipe) to be ephemeral, as in the following example:
KDC_FAMILIES=ip.pipe port:port_number
ephemeral:y ip use:n sna use:n

Appendix C. Problem determination 135

 Tivoli Enterprise Portal problem determination
Table 19 lists problems that might occur with the Tivoli Enterprise Portal. This
appendix provides agent-specific problem determination information. See the IBM
Tivoli Monitoring Problem Determination Guide for general problem determination
information.
Table 19. Tivoli Enterprise Portal problems and solutions
Problem Solution
Historical data collection is The column, Sort By, Group By, and First/Last functions are not compatible with
unavailable because of the historical data collection feature. Use of these advanced functions will make a
incorrect queries in the Tivoli query ineligible for historical data collection.
Enterprise Portal.
Even if data collection has been started, you cannot use the time span feature if the
query for the chart or table includes any column functions or advanced query
options (Sort By, Group By, First / Last).

To ensure support of historical data collection, do not use the Sort By, Group By, or
First/Last functions in your queries.

See the IBM Tivoli Monitoring Administrator’s Guide the Tivoli Enterprise Portal
online Help for information on the Historical Data Collection function.
When you use a long process Truncation of process names in the portal display is the expected behavior. 64 bytes
name in the situation, the is the maximum name length.
process name is truncated.

Problem determination for remote deployment

Table 20 lists problems that might occur with remote deployment. This appendix
provides agent-specific problem determination information. See the IBM Tivoli
Monitoring Problem Determination Guide for general problem determination
information.

This section describes problems and solutions for remote deployment and removal
of agent software Agent Remote Deploy:
Table 20. Remote deployment problems and solutions
Problem Solution
While you are using the remote deployment feature Do not close or modify this window. It is part of the
to install Monitoring Agent for Sybase Server, an installation process and will be dismissed automatically.
empty command window is displayed on the target
computer. This problem occurs when the target of
remote deployment is a Windows computer. (See the
IBM Tivoli Monitoring Installation and Setup Guide for
more information on the remote deployment
feature.)
The removal of a monitoring agent fails when you This problem might happen when you attempt the remote
use the remote removal process in the Tivoli removal process immediately after you have restarted the
Enterprise Portal desktop or browser. Tivoli Enterprise Monitoring Server. You must allow time for
the monitoring agent to refresh its connection with the Tivoli
Enterprise Monitoring Server before you begin the remote
removal process.

136 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 Workspace problem determination
Table 21 shows problems that might occur with workspaces. This appendix
provides agent-specific problem determination information. See the IBM Tivoli
Monitoring Problem Determination Guide for general problem determination
information.
Table 21. Workspace problems and solutions
Problem Solution
You see the following message: KFWITM083W You see this message because some links do not have default
Default link is disabled for the selected workspaces. Right-click the link to access a list of workspaces to
object; please verify link and link anchor select.
definitions.
The name of the attribute does not display in a When a chart or graph view that includes the attribute is scaled
bar chart or graph view. to a small size, a blank space is displayed instead of a truncated
name. To see the name of the attribute, expand the view of the
chart until there is sufficient space to display all characters of the
attribute’s name.
You start collection of historical data but the data Managing options for historical data collection:
cannot be seen. v Basic historical data collection populates the Warehouse with
raw data. This type of data collection is turned off by default.
See Chapter 2, “Requirements and configuration for the
monitoring agent,” on page 5 for information on managing
this feature including how to set the interval at which data is
collected. By setting a more frequent interval for data
collection you reduce the load on the system incurred every
time data is uploaded.
v You use the Summarization and Pruning monitoring agent to
collect specific amounts and types of historical data. Be aware
that historical data is not displayed until the Summarization
and Pruning monitoring agent begins collecting the data. By
default, this agent begins collection at 2 AM daily. At that
point, data is visible in the workspace view. See the IBM Tivoli
Monitoring Administrator’s Guide to learn how to modify the
default collection settings.

Situation problem determination

This section provides information about both general situation problems and
problems with the configuration of situations. See the IBM Tivoli Monitoring
Problem Determination Guide for more information about problem determination for
situations.

General situation problems

Table 22 lists problems that might occur with specific situations.
Table 22. Specific situation problems and solutions
Problem Solution
You want to change the appearance of 1. Right-click an item in the Navigation tree.
situations when they are displayed in a
2. Select Situations in the pop-up menu. The Situation Editor window is
Workspace view.
displayed.
3. Select the situation that you want to modify.
4. Use the Status pull-down menu in the lower right of the window to
set the status and appearance of the Situation when it triggers.
Note: This status setting is not related to severity settings in IBM
Tivoli Enterprise Console.

Appendix C. Problem determination 137

Table 22. Specific situation problems and solutions (continued)
Problem Solution
Monitoring activity requires too much Check the RAS trace logging settings that are described in “Setting RAS
disk space. trace parameters” on page 124. For example, trace logs grow rapidly
when you apply the ALL logging option.
A formula that uses mathematical This formula is incorrect because situation predicates support only logical
operators appears to be incorrect. For operators. Your formulas cannot have mathematical operators.
example, if you were monitoring Sybase Note: The Situation Editor provides alternatives to math operators.
Server, a formula that calculates when Regarding the example, you can select % Processes Bad attribute and
Total Processes Bad falls under 10 avoid the need for math operators.
percent of Total Processes does not
work: LT #’KOYPRCS.NUMPROCESS’ / 10
If you are running a Version 350 Access the database detail. In the ″release″ section change the version
Monitoring Agent for Sybase Server and setting for the agent from 610 to 350. To enable Unicode and other
you choose to alter the views to include features, upgrade the monitoring agent to IBM Tivoli Monitoring, Version
a Version 610 UNICODE attribute, be 6.1.0.
aware that data for this attribute is not
displayed and you see a blank column
in this view.
Situations that you create display the For a situation to have the correct severity in TEC for those situations
severity UNKNOWN in IBM Tivoli which are not mapped, you need to ensure that an entry exists in the
Enterprise Console. tecserver.txt file for the situation and that SEVERITY is specified.

See the “Configuring Tivoli Enterprise Console integration” chapter in the

IBM Tivoli Monitoring Administrator’s Guide for more information.
You see the 'Unable to get attribute Ensure that the agent attribute files are installed on the Tivoli Enterprise
name' error in the Tivoli Enterprise Monitoring Server.
Monitoring Server log after creating a
situation. The following example shows a typical log entry when you have this
problem:
(4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer") \
Unable to get attribute name for tablename/column \
<UAG524400.UA4>. Ignored.

Problems with configuration of situations

Table 23 lists problems that might occur with situations.

This section provides information for problem determination for agents. Be sure to
consult the IBM Tivoli Monitoring Problem Determination Guide for more general
problem determination information.
Table 23. Problems with configuring situations that you solve in the Situation Editor
Problem Solution
Note: To get started with the solutions in this section, perform these steps:
1. Launch the Tivoli Enterprise Portal.
2. Click Edit > Situation Editor.
3. In the tree view, choose the agent whose situation you want to modify.
4. Choose the situation in the list. The Situation Editor view is displayed.
The situation for a specific agent is Open the Situation Editor. Access the All managed servers view. If the situation
not visible in the Tivoli Enterprise is absent, confirm that application support for Monitoring Agent for Sybase
Portal. Server has been added to the monitoring server. If not, add application support
to the server, as described in the IBM Tivoli Monitoring Installation and Setup
Guide.

138 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 23. Problems with configuring situations that you solve in the Situation Editor (continued)
Problem Solution
The monitoring interval is too Access the Situation Editor view for the situation that you want to modify.
long. Check the Sampling interval area in the Formula tab. Adjust the time interval
as needed.
The situation did not activate at Manually recycle the situation as follows:
startup. 1. Right-click the situation and choose Stop Situation.
2. Right-click the situation and choose Start Situation.
Note: You can permanently avoid this problem by placing a check mark in the
Run at Startup option of the Situation Editor view for a specific situation.
The situation is not displayed. Click the Action tab and check whether the situation has an automated
corrective action. This action can occur directly or through a policy. The
situation might be resolving so quickly that you do not see the event or the
update in the graphical user interface.
An Alert event has not occurred Check the logs, reports, and workspaces.
even though the predicate has been
properly specified.
A situation fires on an unexpected Confirm that you have distributed and started the situation on the correct
managed object. managed system.
The product did not distribute the Click the Distribution tab and check the distribution settings for the situation.
situation to a managed system.
The situation does not fire. In the Formula tab, analyze predicates as follows:
1. Click the fx icon in the upper-right corner of the Formula area. The Show
Incorrect predicates are present in
formula window is displayed.
the formula that defines the
situation. For example, the a. Confirm the following details in the Formula area at the top of the
managed object shows a state that window:
normally triggers a monitoring v The attributes that you intend to monitor are specified in the formula.
event, but the situation is not true v The situations that you intend to monitor are specified in the formula.
because the wrong attribute is v The logical operators in the formula match your monitoring goal.
specified in the formula. v The numerical values in the formula match your monitoring goal.
b. (Optional) Click the Show detailed formula check box in the lower left
of the window to see the original names of attributes in the application
or operating system that you are monitoring.
c. Click OK to dismiss the Show formula window.
2. (Optional) In the Formula area of the Formula tab, temporarily assign
numerical values that will immediately trigger a monitoring event. The
triggering of the event confirms that other predicates in the formula are
valid.
Note: After you complete this test, you must restore the numerical values
to valid levels so that you do not generate excessive monitoring data based
on your temporary settings.

Table 24. Problems with configuration of situations that you solve in the Workspace area
Problem Solution
Situation events are not displayed Associate the situation with a workspace.
in the Events Console view of the Note: The situation does not need to be displayed in the workspace. It is
workspace. sufficient that the situation be associated with any workspace.

Appendix C. Problem determination 139

Table 24. Problems with configuration of situations that you solve in the Workspace area (continued)
Problem Solution
You do not have access to a Note: You must have administrator privileges to perform these steps.
situation. 1. Select Edit > Administer Users to access the Administer Users window.
2. In the Users area, select the user whose privileges you want to modify.
3. In the Permissions tab, Applications tab, and Navigator Views tab, select
the permissions or privileges that correspond to the user’s role.
4. Click OK.
A managed system seems to be 1. Select Physical View and highlight the Enterprise Level of the navigator
offline. tree.
2. Select View > Workspace > Managed System Status to see a list of
managed systems and their status.
3. If a system is offline, check network connectivity and status of the specific
system or application.

Table 25. Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Services
window
Problem Solution
After an attempt to restart the For UNIX, NetWare, or Windows, log on to the applicable system and perform
agents in the Tivoli Enterprise the appropriate queries.
Portal, the agents are still not
running.
The Tivoli Enterprise Monitoring Check the system status and check the appropriate IBM Tivoli Monitoring logs.
Server is not running.
The managed objects you created Check the managed system distribution on both the situation and the managed
are firing on incorrect managed object settings sheets.
systems.
For agents that can have multiple sub-nodes, such as database agents:
The icon is incorrect. Check the icon assignments in the template.
The situation is not assigned to a Check the situation assignments in the template of the associated managed
state in the template. object.
You assigned the situation to an Check the State settings sheet for the template.
incorrect state in the template.

Problem determination for Sybase

Table 26 on page 141 lists problems that might occur on the system or application
that you are monitoring. See the IBM Tivoli Monitoring Problem Determination Guide
for general problem determination information.

140 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Table 26. Sybase problems and solutions
Problem Solution
(AIX only) SQL text information is not The default Adaptive Server setting for max SQL text monitored is zero
available to the IBM Tivoli Monitoring. (0). Do the following to change the setting to the recommended number
of bytes, 1024:
1. Run the following isql commands:
a. sp_configure "max SQL text monitored", 1024
b. go
2. Restart Sybase.
See the following Web document for more information:
http://manuals.sybase.com/onlinebooks/group-
as/asg1250e/monbook/@ebt-
link;pt=3138?target=%25N%14_3401_START_RESTART_N%25
UTF-8 is not available. Ensure that the UTF-8 character set is present and activated on the Sybase
server. See configuration details in Chapter 2, “Requirements and
configuration for the monitoring agent,” on page 5.

Support information
If you have a problem with your IBM software, you have the following options for
obtaining support for software products:
v “Searching knowledge bases”
v “Obtaining fixes” on page 142
v “Receiving weekly support updates” on page 142
v “Contacting IBM Software Support” on page 143

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Appendix C. Problem determination 141

 Searching the Internet
If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

The IBM Software Support Web site provides the latest information about known
product limitations and workarounds in the form of technotes for your product.
You can view this information at the following Web site:

http://www.ibm.com/software/support

To search for information on IBM products through the Internet (for example, on
Google), be sure to consider the following types of documentation:
v IBM technotes
v IBM downloads
v IBM Redbooks
v IBM developerWorks
v Forums and newsgroups

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the Software support Web site at
http://www.ibm.com/software/support.
2. Click the Download tab.
3. Select the operating system in the Operating system menu.
4. Type search terms in the Enter search terms field.
5. As appropriate, use other search options to further define your search.
6. Click Search.
7. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at
http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at
http://www.ibm.com/software/support.
2. Click My account in the upper right corner of the page.
3. Click Subscribe to IBM e-news. (If you have already subscribed and want to
modify your subscription preferences, click Modify subscriptions and follow
the instructions on screen.)
4. Follow the instructions on screen to provide the following data:
v Your personal contact information.
v Your areas of interest.
v The types of subscriptions and regional versions that you want to receive.
5. Review the subscription confirmation to confirm your settings.

142 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Contacting IBM Software Support
IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus, and Rational products, as well as DB2 and WebSphere products that run
on Windows, or UNIX operating systems), enroll in Passport Advantage in one
of the following ways:
Online
Go to the Passport Advantage Web site at
http://www.lotus.com/services/passport.nsf/
WebDocs/Passport_Advantage_Home and click How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/login.
v For customers with IBMLink, CATIA, Linux, OS/390, iSeries, pSeries, z/Series,
and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer software products (including, but not limited to, DB2 and
WebSphere products that run in z/Series, pSeries, and iSeries environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact”
2. “Describing problems and gathering information” on page 144
3. “Submitting problems” on page 144

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:

Appendix C. Problem determination 143

 Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you re-create the problem? If so, what steps were performed to re-create the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.
See “Gathering product information for IBM Software Support” on page 117 for
further tips for gathering information for IBM Software Support.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site at
http://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround that you can implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.

144 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Appendix D. Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features in this product enable users to do the following:
v Use assistive technologies, such as screen-reader software and digital speech
synthesizer, to hear what is displayed on the screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product.
v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the following

features to aid accessibility:
v All documentation is available in both HTML and convertible PDF formats to
give the maximum opportunity for users to apply screen-reader software.
v All images in the documentation are provided with alternative text so that users
with vision impairments can understand the contents of the images.

Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and are
documented by the operating system. Refer to the documentation provided by
your operating system for more information.

Magnifying what is displayed on the screen

You can enlarge information on the product windows using facilities provided by
the operating systems on which the product is run. For example, in a Microsoft
Windows environment, you can lower the resolution of the screen to enlarge the
font sizes of the text on the screen. Refer to the documentation provided by your
operating system for more information.

© Copyright IBM Corp. 2005 145

146 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Appendix E. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described 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:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

© Copyright IBM Corp. 2005 147

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating systems. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
system for which the sample programs are written. These examples have not been

148 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
 thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs. You may copy, modify, and
distribute these sample programs in any form without payment to IBM for the
purposes of developing, using, marketing, or distributing application programs
conforming to IBM’s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color
illustrations might not appear.

Trademarks
IBM, the IBM logo, AIX, Candle, CandleNet Portal, DB2, developerWorks, eServer,
Hummingbird®, iSeries, Lotus, MVS, OMEGAMON, Passport Advantage, pSeries,
Rational, Redbooks, S/390, Tivoli, the Tivoli logo, Tivoli Enterprise, Tivoli
Enterprise Console, WebSphere, and zSeriesare trademarks or registered
trademarks of International Business Machines Corporation in the United States,
other countries, or both.

Microsoft, and Windows are registered trademarks of Microsoft Corporation in the

United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, and service names may be trademarks or service marks
of others.

Appendix E. Notices 149

150 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
Index
A capacity planning for historical data 79
character set
accessibility ix, 145 configuring UTF-8 12
agent collecting data 19
problem determination 134 commands, Take Action 91
trace logs 119 components 2
agent installation problems 127 configuration 5
application version requirements 5 settings 6
attribute groups Configuration attribute group 44
Cache Detail 36 configuring
Cache Summary 40 unix 10
Configuration 44 Configuring UTF-8 character set 12
Database Detail 45 contacting support 143
Database Summary 48 conventions
Device Detail 49 operating system x
Engine Summary 53 typeface x
list of all 36 creating user ID 9
Lock Conflict Detail 54 customer support
Lock Conflict Summary 55 See support
Lock Detail 55 customizing
Lock Summary 57 monitoring environment 17
Locks 59 situations 18
Log Detail 61
Log Summary 62
more information 35
overview 35 D
Physical Device Detail 62 data
Problem Detail 65 collecting 19
problem summary 66 trace logs 118
process detail 67 viewing 19
process summary 70 data provider
remote servers 71 See agent
server detail 72 database agent installation problems 127
Server Enterprise 73 Database Detail attribute group 45
server summary 74 Database Summary attribute group 48
SQL detail 75 Databases workspace 22
statistics detail 75 detecting problems, modifying situation values 18
statistics summary 76 Device Detail attribute group 49
task detail 78 Device Usage workspace 23
text 78 directory names, notation x
Attribute Groups disk capacity planning for historical data 79
Engine Detail 51 disk space requirements 5
attributes
more information 35
overview 35 E
education
see Tivoli technical training x
B enabling unicode conversions 13
books Engine Detail Attribute Group 51
feedback viii Engine Summary attribute group 53
online viii Engine Summary workspace 24
ordering viii Enterprise Database Summary workspace 24
see publications ix Enterprise Errorlog Alerts workspace 25
built-in problem determination features 117 Enterprise Locking Summary workspace 25
Enterprise Processes Summary workspace 26
Enterprise Server Statistics workspace 26
C Enterprise Server Summary workspace 26
Enterprise Sybase Summary workspace 27
Cache Detail attribute group 36 environment
Cache Summary attribute group 40 customizing 17
Cache Usage workspace 22 features 1
calculate historical data disk space 79

© Copyright IBM Corp. 2005 151

environment (continued)
monitoring real-time 15
L
real-time monitoring 15 legal notices 147
environment variables, notation x Lock Conflict Detail attribute group 54
Errorlog Alerts workspace 27 Lock Conflict Summary attribute group 55
event Lock Detail attribute group 55
mapping 97 Lock Information workspace 28
events Lock Summary attribute group 57
investigating 16 Lock Usage workspace 28
workspaces 16 Locks attribute group 59
Log and Space Information workspace 29
Log Detail attribute group 61
Log Summary attribute group 62
F Log Usage workspace 29
features, Monitoring Agent for Sybase Server 1 logging
files agent trace logs 119, 120
agent trace 119 built-in features 117
installation trace 119 installation log files 119
other trace log 120 location and configuration of logs 118
trace logs 118 trace log files 118
fixes, obtaining 142

G M
manuals
gathering support information 117 feedback viii
granting permission 9 online viii
ordering viii
see publications ix
H memory requirements 5
historical data messages
calculate disk space 79 built-in features 117
disk capacity planning 79 modifying situation values to detect problems 18
historical data, collecting and viewing 19 Monitoring Agent for Sybase Server
components 2
features 1
purposes 15
I using 15
IBM Software Support workspace groups
See support determining which to use 95
IBM Tivoli Enterprise Console monitoring, viewing the real-time environment 15
event mapping 97
IBM Tivoli Monitoring for Databases: Sybase Server Agent
performance considerations 137
information centers for support 141
N
information, additional notation
attributes 35 environment variables x
policies 93 path names x
procedural 15 typeface x
situations 83
Take Action commands 91
workspaces 21 O
installation 5 online publications
log file 119 accessing ix
problems 127 for support 141
interface, user 2 operating systems 5
problem determination for Tivoli Enterprise Portal 136 operation of resource, recovering 16
Internet ordering publications ix
for product support 142 other requirements 6
investigating an event 16

P
K path names, for trace logs 118
knowledge bases for support 141 path names, notation x
performance considerations 137
permission, granting 9
Physical Device Detail attribute group 62

152 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
policies resource, recovering operation 16
list of all 93
more information 93
overview 93
predefined 93
S
Server Configuration workspace 31
Problem Detail attribute group 65
server detail attribute group 72
problem determination 117, 126
Server Enterprise attribute group 73
agents 134
Server Statistics Summary workspace 32
built-in features 117
server summary attribute group 74
describing problems 144
Servers workspace 32
determining business impact 143
situations 84
information centers for 141
general problem determination 138
installation 127
more information 83
installation logs 119
overview 83
knowledge bases for 141
predefined 84
remote deployment 136
specific problem determination 137
situations 137, 138
Sybase_Collection_Stat_Warning 84
submitting problems 144
Sybase_DB_Error_Status 85
Tivoli Enterprise Portal 136
Sybase_DB_Freespace_Critical 85
uninstallation 127
Sybase_DB_Freespace_Warning 85
uninstallation logs 119
Sybase_DB_Num_Errors_Warning 85
workspaces 137
Sybase_Device_Free_Pct_Warning 85
problem summary attribute group 66
Sybase_ErrorLog_Size_Warning 85
problems
Sybase_IOERR_Startup_Warning 85
detecting 18
Sybase_IOError_Curintvl_Warning 85
problems and workarounds 126
Sybase_Log_Freespace_Critical 85
problems with monitoring Sybase 140
Sybase_Log_Suspend_Warning 86
procedures 15
Sybase_LogonPct_Warning 86
process detail attribute group 67
Sybase_Pct_Device_Lock_Warning 86
Process Holding Lock workspace 30
Sybase_Pct_Engine_CPU_Critical 86
Process SQL Text workspace 30
Sybase_Pct_Engine_CPU_Warning 86
process summary attribute group 70
Sybase_Pct_IO_Warning 86
Processes workspace 31
Sybase_Pct_MAX_Locks_Critical 86
publications
Sybase_Pct_MAX_Locks_Warning 87
accessing online ix
Sybase_Pct_Task_Yields_Warning 87
feedback viii
Sybase_Pct_Total_CPU_Critical 87
for support 141
Sybase_Pct_Total_CPU_Warning 87
online viii
Sybase_ProbAge_GT_17_Warning 87
ordering viii, ix
Sybase_ProbAge_LT_17_Warning 87
purposes
Sybase_Process_Blocked_Warning 87
collecting data 19
Sybase_Process_Infected_Warning 87
customizing monitoring environment 17
Sybase_Processes_Bad_Warning 88
investigating events 16
Sybase_Processes_Stop_Warning 88
monitoring with custom situations 18
Sybase_ProcessLockSleep_Warning 88
problem determination 117
Sybase_ProcessOthSleep_Warning 88
recovering resource operation 16
Sybase_Server_CPU_Critical 88
viewing data 19
Sybase_Server_CPU_Warning 88
viewing real-time monitoring environment 15
Sybase_Server_Error_Warning 88
Sybase_Server_Status_Critical 88
Sybase_Server_Status_Inactive 89
Q values, modifying 18
queries, using attributes 35 situations, using attributes 35
SQL detail attribute group 75
SQL Text workspace 33
R statistics detail attribute group 75
statistics summary attribute group 76
real-time data, viewing 15
support
recovering the operation of a resource 16
about 141
remote deployment
contacting 143
problem determination 136
describing problems 144
remote servers attribute group 71
determining business impact of problems 143
requirements
gathering information for 117
application versions 5
information centers for 141
disk space 5
knowledge bases for 141
memory 5
obtaining fixes 142
operating system 5
on Internet 142
other 6
submitting problems 144

Index 153
support (continued)
weekly update option 142
U
Sybase problems 140 unicode
Sybase Server Locking workspace group 28 enabling conversions 13
Sybase Server Processes workspace group 31 uninstallation
Sybase Server_ID workspace 33 log file 119
Sybase Statistics Summary workspace group 32 problems 127
Sybase_Collection_Stat_Warning situation 84 unix
Sybase_DB_Error_Status situation 85 configuring 10
Sybase_DB_Freespace_Critical situation 85 UNIX operating systems 5
Sybase_DB_Freespace_Warning situation 85 user ID, creating 9
Sybase_DB_Num_Errors_Warning situation 85 user interfaces options 2
Sybase_Device_Free_Pct_Warning situation 85 UTF-8
Sybase_ErrorLog_Size_Warning situation 85 configuring character set 12
Sybase_IOERR_Startup_Warning situation 85
Sybase_IOError_Curintvl_Warning situation 85
Sybase_Log_Freespace_Critical situation 85 V
Sybase_Log_Suspend_Warning situation 86 values, modifying situations 18
Sybase_LogonPct_Warning situation 86 variables, notation for x
Sybase_Pct_Device_Lock_Warning situation 86 viewing data 19
Sybase_Pct_Engine_CPU_Critical situation 86 viewing real-time monitoring environment 15
Sybase_Pct_Engine_CPU_Warning situation 86 views
Sybase_Pct_IO_Warning situation 86 Cache Usage workspace 22
Sybase_Pct_MAX_Locks_Critical situation 86 Databases workspace 22
Sybase_Pct_MAX_Locks_Warning situation 87 Device Usage workspace 23
Sybase_Pct_Task_Yields_Warning situation 87 Engine Summary workspace 24
Sybase_Pct_Total_CPU_Critical situation 87 Enterprise Database Summary workspace 24
Sybase_Pct_Total_CPU_Warning situation 87 Enterprise Errorlog Alerts workspace 25
Sybase_ProbAge_GT_17_Warning situation 87 Enterprise Locking Summary workspace 25
Sybase_ProbAge_LT_17_Warning situation 87 Enterprise Processes Summary workspace 26
Sybase_Process_Blocked_Warning situation 87 Enterprise Server Statistics workspace 26
Sybase_Process_Infected_Warning situation 87 Enterprise Server Summary workspace 26
Sybase_Processes_Bad_Warning situation 88 Enterprise Sybase Summary workspace 27
Sybase_Processes_Stop_Warning situation 88 Errorlog Alerts workspace 27
Sybase_ProcessLockSleep_Warning situation 88 Lock Information workspace 28
Sybase_ProcessOthSleep_Warning situation 88 Lock Usage workspace 28
Sybase_Server_CPU_Critical situation 88 Log and Space Information workspace 29
Sybase_Server_CPU_Warning situation 88 Log Usage workspace 29
Sybase_Server_Error_Warning situation 88 Process Holding Lock workspace 30
Sybase_Server_Status_Critical situation 88 Process SQL Text workspace 30
Sybase_Server_Status_Inactive situation 89 Processes workspace 31
Server Configuration workspace 31
Server Statistics Summary workspace 32
T Servers workspace 32
Take Action commands 16 SQL Text workspace 33
list of all 91 Sybase Server_ID workspace 33
more information 91
overview 91
predefined 91 W
target application weekly update support option 142
problems 140 Windows agent installation problems 127
task detail attribute group 78 Windows operating systems 5
tasks for using 15 workarounds 126
text attribute group 78 agents 134
Tivoli Enterprise Portal remote deployment 136
accessing workspaces and table views 95 situations 137
problem determination 136 Tivoli Enterprise Portal 136
Tivoli software information center ix workspaces 137
Tivoli technical training x workspace groups
trace logs 118 overview 95
directories 118 Sybase Errorlog Alerts Workspace 27
trademarks 149 Sybase Server Databases 22
training, Tivoli technical x Sybase Server Locking Workspace 28
transport command 140 Sybase Server Process Workspace 31
troubleshooting 117 Sybase Servers 32
typeface conventions x Sybase Statistics Summary Workspace 32

154 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide
workspaces
accessing in Tivoli Enterprise Portal 95
Cache Usage 22
Databases 22
Device Usage 23
Engine Summary 24
Enterprise Database Summary 24
Enterprise Errorlog Alerts 25
Enterprise Locking Summary 25
Enterprise Processes Summary 26
Enterprise Server Statistics 26
Enterprise Server Summary 26
Enterprise Sybase Summary 27
Errorlog Alerts 27
event 16
list of all 21
Lock Information 28
Lock Usage 28
Log and Space Information 29
Log Usage 29
more information 21
overview 21
predefined 21
problem determination 137
Process Holding Lock 30
Process SQL Text 30
Processes 31
Server Configuration 31
Server Statistics Summary 32
Servers 32
SQL Text 33
Sybase Server_ID 33

Index 155
156 IBM Tivoli Monitoring for Databases: Sybase Server Agent: User’s Guide



Printed in USA

SC32-9451-00