t l tivoli monitoring sybase ase - ibm...
TRANSCRIPT
Tivoli® IBM Tivoli Monitoring for Databases: Sybase ASE
User’s Guide
5.1.2
GC32-9136-00
���
Tivoli® IBM Tivoli Monitoring for Databases: Sybase ASE
User’s Guide
5.1.2
GC32-9136-00
���
Note
Before using this information and the product it supports, read the information in Appendix G, “Notices,” on page 225.
First Edition (Oct. 2004)
This edition applies to version 5.1.2 of IBM Tivoli Monitoring for Databases: Sybase ASE and to all subsequent
releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v
Figures . . . . . . . . . . . . . . vii
About this guide . . . . . . . . . . . ix
Who should read this guide . . . . . . . . . ix
What this guide contains . . . . . . . . . . ix
Publications . . . . . . . . . . . . . . x
IBM Tivoli Monitoring for Databases: Sybase ASE
library . . . . . . . . . . . . . . . x
Prerequisite publications . . . . . . . . . x
Related publications . . . . . . . . . . . x
Accessing publications online . . . . . . . xi
Ordering publications . . . . . . . . . . xi
Accessibility . . . . . . . . . . . . . . xii
Tivoli technical training . . . . . . . . . . xii
Support information . . . . . . . . . . . xii
Conventions used in this guide . . . . . . . . xii
Typeface conventions . . . . . . . . . . xii
Operating system-dependent variables and
paths . . . . . . . . . . . . . . . xiii
Tivoli command syntax . . . . . . . . . xiii
Chapter 1. Overview of IBM Tivoli
Monitoring for Databases: Sybase ASE . 1
Features of IBM Tivoli Monitoring for Databases:
Sybase ASE . . . . . . . . . . . . . . . 1
IBM Tivoli Monitoring for Databases: Sybase ASE
functions . . . . . . . . . . . . . . . 2
IBM Tivoli Monitoring for Databases: Sybase ASE
environment . . . . . . . . . . . . . . 3
Objects that represent resources . . . . . . . 4
User interface options . . . . . . . . . . 4
Chapter 2. Resource models . . . . . . 5
About resource models . . . . . . . . . . . 5
Operational modes for thresholds . . . . . . . 9
Controlling statistical thresholding . . . . . . 14
Training modes . . . . . . . . . . . . 15
Chapter 3. How to use IBM Tivoli
Monitoring for Databases: Sybase ASE . 17
Begin monitoring with preconfigured resource
models . . . . . . . . . . . . . . . . 17
Examine the monitoring environment . . . . . 17
Recover the operation of a resource . . . . . . 18
Collect data and create reports . . . . . . . . 18
Modify resource model values to detect problems 18
Chapter 4. Procedures . . . . . . . . 21
Discovering resources to monitor . . . . . . . 21
Distributing resource models . . . . . . . . 23
Determining which resource models are monitoring
which managed resources . . . . . . . . . 25
Controlling monitoring . . . . . . . . . . 26
Specifying a task to run automatically . . . . . 27
Customizing cycle time . . . . . . . . . . 28
Customizing indications and events . . . . . . 29
Customizing parameters . . . . . . . . . . 31
Customizing thresholds . . . . . . . . . . 32
Re-training resource model thresholds . . . . . 34
Logging data for a resource model . . . . . . 35
Creating reports . . . . . . . . . . . . . 38
Appendix A. Resource model reference 41
Log Monitor . . . . . . . . . . . . . . 43
Sybase Availability . . . . . . . . . . . . 54
Locks RM . . . . . . . . . . . . . . . 60
Data Cache RM . . . . . . . . . . . . . 75
Space Usage RM . . . . . . . . . . . . . 81
Process Waits RM . . . . . . . . . . . . 102
State RM . . . . . . . . . . . . . . . 108
Traffic RM . . . . . . . . . . . . . . 118
Appendix B. Task reference . . . . . 131
Start Sybase Adaptive Server . . . . . . . . 134
Stop Sybase Adaptive Server . . . . . . . . 136
Start Sybase Backup Server . . . . . . . . . 138
Stop Sybase Backup Server . . . . . . . . . 140
Start Sybase Monitor Server . . . . . . . . 142
Stop Sybase Monitor Server . . . . . . . . 144
Check Sybase ASE Server Status . . . . . . . 146
Configure Event Server . . . . . . . . . . 148
Create Sybase ASE Server Object . . . . . . . 153
Discover . . . . . . . . . . . . . . . 157
Manage Tivoli Logs . . . . . . . . . . . 162
Modify Object Properties . . . . . . . . . 164
TBSM Synchronization . . . . . . . . . . 167
Appendix C. Event classes and rules
reference . . . . . . . . . . . . . 169
Event classes . . . . . . . . . . . . . 169
SybaseAvailability_IXB_ApplicationUnavailable 169
NumberOfDeadlocks_IXB . . . . . . . . 170
NumberOfLockWaits_IXB . . . . . . . . 170
LockWaitTime_IXB . . . . . . . . . . 170
NumberOfAvailableLocks_IXB . . . . . . . 171
LocksInUse_IXB . . . . . . . . . . . 171
CacheHitRatio_IXB . . . . . . . . . . 171
DBAllocatedSize_IXB . . . . . . . . . . 172
DBUsedSize_IXB . . . . . . . . . . . 172
DBIndexSize_IXB . . . . . . . . . . . 172
DBUnallocatedSizeInKB_IXB . . . . . . . 173
NumberTotalPages_IXB . . . . . . . . . 173
NumberFreePages_IXB . . . . . . . . . 173
NumberUsedPages_IXB . . . . . . . . . 174
PercentFreeSpace_IXB . . . . . . . . . 174
NumberWaitingProcesses_IXB . . . . . . . 174
NumberDatabasesOpen_IXB . . . . . . . 175
© Copyright IBM Corp. 2004 iii
EngineIdleTimeInSeconds_IXB . . . . . . . 175
NumberEngineConnections_IXB . . . . . . 175
NumberServerConnections_IXB . . . . . . 176
NumberServerConnectionsAvailable_IXB . . . 176
NumberPacketsSentPerSecond_IXB . . . . . 176
NumberPacketsReceivedPerSecond_IXB . . . 177
Rules for events . . . . . . . . . . . . 177
Appendix D. Data providers reference 179
LogMonitor provider . . . . . . . . . . . 179
LogMonitor configuration file . . . . . . . 182
LogMonitor configuration XML DTD . . . . 182
Log names . . . . . . . . . . . . . 188
Appendix E. Problem determination 191
Built-in problem determination features . . . . 191
Problem classification . . . . . . . . . . . 192
Trace logging . . . . . . . . . . . . . 192
Installation and uninstallation trace logs . . . 193
Data provider trace logs . . . . . . . . . 193
Resource model trace logs . . . . . . . . 195
Task trace logs . . . . . . . . . . . . 196
IBM Tivoli Enterprise Console trace logs . . . 196
Installation problem determination . . . . . . 197
Problems and workarounds . . . . . . . . 200
Discovery problem determination . . . . . 200
Resource model problem determination . . . 201
Tasks problem determination . . . . . . . 203
Event problem determination . . . . . . . 204
Support information . . . . . . . . . . . 206
Searching knowledge bases . . . . . . . . 206
Obtaining fixes . . . . . . . . . . . . 206
Contacting IBM Software Support . . . . . 207
Informational, warning, and error messages . . . 208
Message format . . . . . . . . . . . 209
IBM Tivoli Monitoring for Databases: Sybase
ASE Messages . . . . . . . . . . . . 210
IBM Tivoli Monitoring Component Services
messages . . . . . . . . . . . . . . 219
Appendix F. Accessibility . . . . . . 223
Navigating the interface using the keyboard . . . 223
Magnifying what is displayed on the screen . . . 223
Appendix G. Notices . . . . . . . . 225
Trademarks . . . . . . . . . . . . . . 226
Index . . . . . . . . . . . . . . . 229
iv IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Tables
1. Computation of thresholds example . . . . 13
2. IBM Tivoli Monitoring for Databases: Sybase
ASE resource models . . . . . . . . . 41
3. Ways to invoke tasks . . . . . . . . . 132
4. LogMonitor CIM class . . . . . . . . 179
5. LogMonitor properties . . . . . . . . 179
6. LogMonitor dependency set . . . . . . 180
7. LogMonitor parameters . . . . . . . . 180
8. ITMException ILT parameters . . . . . . 180
9. ITMException ILT exceptions for the
LogMonitor . . . . . . . . . . . . 181
10. LogMonitor Configuration XML DTD syntax
elements and attributes . . . . . . . . 182
11. Installation and uninstallation trace logs and
descriptions . . . . . . . . . . . . 193
12. Data provider trace logs . . . . . . . . 193
13. Resource model trace logs . . . . . . . 195
14. Task trace logs . . . . . . . . . . . 196
15. IBM Tivoli Enterprise Console trace logs 196
16. General problems and solutions for
installation . . . . . . . . . . . . 197
17. Installation problems and solutions for Tivoli
Data Warehouse . . . . . . . . . . 198
18. General problems and solutions for
uninstallation . . . . . . . . . . . 199
19. Discovery problems and solutions . . . . 200
20. General resource model problems and
solutions . . . . . . . . . . . . . 201
21. Specific resource model problems and
solutions . . . . . . . . . . . . . 203
22. Task problems and solutions . . . . . . 204
23. Event problems and solutions . . . . . . 204
© Copyright IBM Corp. 2004 v
vi IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Figures
1. Percent CPU utilization against I/O Read
Ops/Second . . . . . . . . . . . . 11
2. Distribution histogram for CPU utilization
over a one week period . . . . . . . . 12
3. CPU utilization over a one week period 12
4. Queries/minute over a one-week period 13
© Copyright IBM Corp. 2004 vii
viii IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
About this guide
The IBM Tivoli Monitoring for Databases: Sybase ASE User’s Guide provides
information about using IBM®® Tivoli®® Monitoring for Databases: Sybase ASE
after installation and setup. See IBM Tivoli Monitoring for Databases: Sybase ASE
Installation and Setup Guide for complete information about installing the software
and setting it up.
Who should read this guide
This guide is for system administrators who use IBM Tivoli Monitoring for
Databases: Sybase ASE to monitor and manage Sybase ASE resources.
Readers should be familiar with the following topics:
v Tivoli management software
v Tivoli application software
v UNIX-based operating systems
v Microsoft® Windows® operating systems
v Tivoli Data Warehouse (optional)
v IBM Tivoli Enterprise Console®
v IBM Tivoli Business Systems Manager (optional)
What this guide contains
This guide contains the following chapters:
v Chapter 1, “Overview of IBM Tivoli Monitoring for Databases: Sybase ASE,” on
page 1
Provides an introduction to IBM Tivoli Monitoring for Databases: Sybase ASE.
v Chapter 2, “Resource models,” on page 5
Provides conceptual information about resource models and thresholding.
v Chapter 3, “How to use IBM Tivoli Monitoring for Databases: Sybase ASE,” on
page 17
Provides a list of purposes to achieve when using the product, and a list of
procedures for achieving each purpose. After completing the tasks in the
Installation and Setup Guide and becoming familiar with the information in
Chapters 1 and 2 of this guide, this chapter provides information about how you
can use the product.
v Chapter 4, “Procedures,” on page 21
Provides procedural information about setting up, monitoring, and controlling
resources, including information about how to customize monitoring to match
the needs of your Sybase ASE monitoring environment.
v Appendix A, “Resource model reference,” on page 41
Provides detailed information about each resource model that you can use with
IBM Tivoli Monitoring for Databases: Sybase ASE, including the default settings.
v Appendix B, “Task reference,” on page 131
Provides detailed information about the tasks provided with IBM Tivoli
Monitoring for Databases: Sybase ASE.
v Appendix C, “Event classes and rules reference,” on page 169
© Copyright IBM Corp. 2004 ix
Describes the event classes and rules for IBM Tivoli Monitoring for Databases:
Sybase ASE.
v Appendix D, “Data providers reference,” on page 179
Provides a list of the MOF files for IBM Tivoli Monitoring for Databases: Sybase
ASE and the metrics for the LogMonitor data provider.
v Appendix E, “Problem determination,” on page 191
Provides information about troubleshooting the various components of IBM
Tivoli Monitoring for Databases: Sybase ASE, information about log files and
messages, and information about working with IBM Software Support.
v Appendix F, “Accessibility,” on page 223
Provides information about the accessibility features in IBM Tivoli Monitoring
for Databases: Sybase ASE.
v Appendix G, “Notices,” on page 225
Provides IBM and Tivoli notices and trademark information as it applies to IBM
Tivoli Monitoring for Databases: Sybase ASE.
Publications
This section lists publications in the IBM Tivoli Monitoring for Databases: Sybase
ASE library and any other related documents. It also describes how to access Tivoli
publications online, how to order Tivoli publications, and how to submit comments
on Tivoli publications.
IBM Tivoli Monitoring for Databases: Sybase ASE library
The IBM Tivoli Monitoring for Databases: Sybase ASE library contains the
following publications:
v IBM Tivoli Monitoring for Databases: Sybase ASE Installation and Setup Guide
Provides information about installing and setting up IBM Tivoli Monitoring for
Databases: Sybase ASE.
v IBM Tivoli Monitoring for Databases: Sybase ASE User’s Guide
Provides conceptual, procedural, and reference information about how to
monitor and manage resources with IBM Tivoli Monitoring for Databases:
Sybase ASE. This guide also provides troubleshooting information about the
various components of IBM Tivoli Monitoring for Databases: Sybase ASE, as
well as information about log files and informational, warning, and error
messages.
Prerequisite publications
To use the information in this book effectively, you must have some knowledge of
IBM Tivoli Monitoring, which you can get from the following books:
v IBM Tivoli Monitoring User’s Guide
Provides an overview of IBM Tivoli Monitoring, especially of resource models. It
also describes how to use the user interface.
v Tivoli Management Framework User’s Guide
Provides information about how to use the Tivoli graphical user interface (GUI)
Related publications
The following documents also provide useful information:
v Tivoli Enterprise™ Installation Guide
v Tivoli Management Framework Reference Manual
x IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
v IBM Tivoli Enterprise Console Adapters Guide
v IBM Tivoli Enterprise Console Event Integration Facility User’s Guide
v IBM Tivoli Enterprise Console Reference Manual
v IBM Tivoli Enterprise Console Rule Builder’s Guide
v IBM Tivoli Business Systems Manager product documentation
v IBM Tivoli Monitoring product documentation
v Installing and Configuring Tivoli Data Warehouse
v IBM Tivoli Monitoring Component Services, Version 5.1.3, Guide for Warehouse Pack,
Version 1.3.0.0, using Tivoli Data Warehouse 1.2
v Tivoli Data Warehouse product documentation
v IBM Tivoli Monitoring Resource Model Builder User’s Guide
The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available, in English only,
at http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm
Accessing publications online
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.
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 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
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, see the following Web site for a list of telephone numbers:
About this guide xi
http://www.ibm.com/software/tivoli/order-lit/
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 the Accessibility Appendix in the user’s guide for
this product.
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 206 describes the following options for obtaining
support for IBM products:
v “Searching knowledge bases” on page 206
v “Obtaining fixes” on page 206
v “Contacting IBM Software Support” on page 207
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 (for example, ″Use the word that to introduce a
restrictive clause.″)
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Code and other examples
xii IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
v File names, programming keywords, and other elements 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 publications in this library use the UNIX® convention for specifying
environment variables and for directory notation.
When using the Windows command line, replace $variable with %variable% for
environment variables and replace each forward slash (/) with a backslash (\) in
directory paths. The names of environment variables are not always the same in
Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in
UNIX.
Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.
Tivoli command syntax
The following special characters define Tivoli command syntax:
[ ] Identifies elements that are optional. Required elements do not have
brackets around them.
... Indicates that you can specify multiple values for the previous element.
Separate multiple values by a space, unless otherwise directed by
command information.
If the ellipsis for an element follows a closing bracket, use the syntax
within the brackets to specify multiple values. For example, to specify two
administrators for the option [–a admin]..., use –a admin1 –a admin2.
If the ellipsis for an element is within the brackets, use the syntax of the
last element to specify multiple values. For example, to specify two hosts
for the option [–h host...], use –h host1 host2.
| Indicates mutually exclusive information. You can use the element on
either the left or right of the vertical bar.
{ } Delimits a set of mutually exclusive elements when a command requires
one of them. Brackets ([ ]) are around elements that are optional.
In addition to the special characters, Tivoli command syntax uses the typeface
conventions described in “Typeface conventions” on page xii. The following
examples illustrate the typeface conventions used in Tivoli command syntax:
v wcrtpr [–a admin]... [–s region] [–m resource]... name
The name argument is the only required element for the wcrtpr command. The
brackets around the options indicate they are optional. The ellipsis after the –a
admin resource option means that you can specify multiple administrators
multiple times. The ellipsis after the –m resource option means that you can
specify multiple resources multiple times.v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}
The –f, –i, and object elements are mutually exclusive. Braces that surround
elements indicate that you are including a required element. If you specify the
object argument, you can specify more than one object.
About this guide xiii
xiv IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Chapter 1. Overview of IBM Tivoli Monitoring for Databases:
Sybase ASE
IBM Tivoli Monitoring for Databases: Sybase ASE provides you with the capability
to monitor Sybase ASE, and to perform basic actions with Sybase ASE.
This chapter provides a description of the features and functions of IBM Tivoli
Monitoring for Databases: Sybase ASE, and a description of the IBM Tivoli
Monitoring for Databases: Sybase ASE environment.
Features of IBM Tivoli Monitoring for Databases: Sybase ASE
The IBM Tivoli Monitoring component software identifies, notifies you of, and
corrects common problems with the application that it monitors. The software
includes the following features:
v Discovery of resources
v Monitoring
v Event management
v Operations management
v Data gathering and reporting
The discovery process searches your application environment and adds the
resources in that environment to the Tivoli monitoring environment to ensure that
you are managing all available resources. In a Tivoli environment, a resource is a
hardware, software, or data entity that is managed by Tivoli software. A managed
resource is a database object that represents a system or network resource and is
governed by policies.
The monitoring of resources occurs through resource models. The availability
resource model periodically checks the status of your application resources to
ensure that they are operational. You can configure this resource model to match
the monitoring needs of your application environment. You can also run a task to
check the availability of a resource. Log monitoring resource models monitor the
logs associated with the application to detect key errors and events affecting
availability or performance of the services. Other resource models collect
performance data for the application. These resource models contain thresholds
that cause events to be sent when these are not in the expected ranges. They also
log data that can be viewed in the IBM Tivoli Monitoring Web Health Console.
In addition to the resource models provided with IBM Tivoli Monitoring for
Databases: Sybase ASE, you can use the IBM Tivoli Monitoring resource models.
You can also configure resource models provided with other IBM Tivoli Monitoring
component software that you are using. “IBM Tivoli Monitoring for Databases:
Sybase ASE functions” on page 2 contains a description of each type of monitoring
for IBM Tivoli Monitoring for Databases: Sybase ASE.
When resource models detect that resources are not operating as desired, they
create events that they forward to the IBM Tivoli Enterprise Console server. You
can manage the events through IBM Tivoli Enterprise Console or through IBM
Tivoli Business Systems Manager if you have installed these applications.
© Copyright IBM Corp. 2004 1
Tasks enable you to manage your application resources on a daily basis, for
example, you can use tasks to start resources and stop resources manually or
automatically. When you run a task manually, you initiate the task. When you run
a task automatically, a resource model initiates the task.
When you enable data logging, the resource models gather data that you can view
in the IBM Tivoli Monitoring Web Health Console and Tivoli Data Warehouse.
Then, you can run reports on that data. Reports enable you to analyze the health
and performance of your Sybase ASE resources over a period of time. You can also
use reports to predict resource usage and diagnose potential problems before they
occur. With Tivoli Data Warehouse, you can create the following types of reports:
application availability, system resource consumption, and process resource
consumption. “IBM Tivoli Monitoring for Databases: Sybase ASE functions”
contains a description of each type of report for IBM Tivoli Monitoring for
Databases: Sybase ASE.
IBM Tivoli Monitoring for Databases: Sybase ASE functions
IBM Tivoli Monitoring for Databases: Sybase ASE provides the following functions:
Availability and resource monitoring
Monitor server and process availability. Monitor resource usage of
processes associated with Sybase ASE, including CPU and memory used.
Emit indications when processes become unavailable and when resource
usage is not within the range allowed by the threshold values.
Lock Monitoring
Monitor number of deadlocks. Emit indications when the number of
deadlocks is not within the range allowed by the threshold values. Monitor
lock waits and emit indications when the lock wait times is not within the
range allowed by the threshold values. Monitor available locks and locks
in use. Emit indications when available locks and locks in use are not
within the range allowed by the threshold values.
Cache Effectiveness monitoring
Monitor cache effectiveness as demonstrated by the ratio of cache hits as a
percentage of retrieval attempts. Emit indications when the percentage of
hits is not within the range allowed by the threshold values.
Space monitoring
Monitor space usage for each database. Identify the database size, how
much space has been allocated, how much space is being used, how much
space the indexes consume and how much space has not been allocated for
each database. Emit indications when any of the sizes are not within the
range allowed by the threshold values. Monitor space usage for all
segments is all databases. Identify the total segment size, how much space
is free and how much space is being used. Emit indications when any of
the sizes are not within the range allowed by the threshold values.
Log Monitoring
Monitor the Sybase ASE log file for for certain messages. Emit indications
for each message found in the log file.
Wait Monitoring
Monitor how many processes are waiting and generate an indication when
the number of waiting processes is not within the range allowed by the
threshold values.
2 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
State Monitoring
Monitor the number of databases open and emit indications when the
number is not within the range allowed by the threshold values. Monitor
the state, idle time and number of connections for each engine. Emit
indications when the idle time or the number of connections are not within
the range allowed by the threshold values.
Traffic Monitoring
Monitor packets sent and received. Emit indications when the number of
packets sent or received are not within the range allowed by the threshold
values. Monitor connections available and in use. Emit indications when
the number of connections available or in use are not within the range
allowed by the threshold values.
CPU Usage Report
Provides a resource usage report that shows the maximum CPU used per
day by the processes associated with the monitored product.
Server Availability Report
Provides an availability report that shows the percent of time the server
processes were available each day. All processes defined for monitoring by
Availability monitoring are reported.
Memory Usage Report
Provides a resource usage report that shows the maximum and average
memory used per day by the processes associated with the database server.
IBM Tivoli Monitoring for Databases: Sybase ASE environment
After you install and set up IBM Tivoli Monitoring for Databases: Sybase ASE as
described in the IBM Tivoli Monitoring for Databases: Sybase ASE Installation and
Setup Guide, you have an environment that contains the following components:
v Base software
– Tivoli Management Framework
– IBM Tivoli Monitoring
– IBM Tivoli Monitoring Component Services
– IBM Tivoli Monitoring for Databases: Sybase ASE
– Required patches or fix packsv Other optional applications that are integrated with IBM Tivoli Monitoring for
Databases: Sybase ASE
– IBM Tivoli Enterprise Console (one event server for each Tivoli management
region)
– IBM Tivoli Business Systems Manager
– IBM Tivoli Monitoring Web Health Console
– Tivoli Data Warehousev Basic monitoring components
– Authorization roles that enable product activities in the Tivoli environment
– Managed nodes and endpoints that are running
– A policy region that contains a profile manager
– A profile that contains resource models (See Appendix A, “Resource model
reference,” on page 41 for descriptions of the resource models.)
– Objects that represent the resources that the application manages
– Resource models that are running on managed resources (objects)
Chapter 1. Overview of IBM Tivoli Monitoring for Databases: Sybase ASE 3
– Task libraries that contain tasks (See Appendix B, “Task reference,” on page
131 for descriptions of the tasks.)
Objects that represent resources
Tivoli objects that represent Sybase ASE resources are registered in the Tivoli
management region and monitored by the IBM Tivoli Monitoring for Databases:
Sybase ASE resource models. You use tasks to take actions on these objects. The
following objects represent the resources you monitor with this software:
v SybaseASEServer_IXB
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 desktop
Traditional Tivoli graphical user interface (GUI)
Command-line interface (CLI)
UNIX command line or the bash shell on a Windows operating system,
from which you can perform system operations instead of using the Tivoli
desktop
IBM Tivoli Enterprise Console
Event management application
IBM Tivoli Business Systems Manager
Application for examining how resources affect a business function, and
for managing these resources.
IBM Tivoli Monitoring Web Health Console
Also referred to as the Web Health Console, a Web-based graphical
interface that enables you to view the health of resources on an endpoint
and to view real-time or historical data
Tivoli Data Warehouse
Centralized data store where historical data gathered by IBM Tivoli
Monitoring for Databases: Sybase ASE can be stored, aggregated, and
correlated so you can create reports
4 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Chapter 2. Resource models
Resource models are the key IBM Tivoli Monitoring component that provides the
monitoring function in IBM Tivoli Monitoring for Databases: Sybase ASE. This
chapter contains conceptual information about resource models and the parts of
resource models that you can customize to monitor your resources.
Some resource models have thresholds that are governed by parameters. This
chapter contains an extensive explanation of this type of thresholding.
The following additional information about resource models is also located in this
user’s guide:
v Chapter 4, “Procedures,” on page 21 contains procedural information about
customizing resource models as well as setting up and monitoring resources.
v Appendix A, “Resource model reference,” on page 41 contains detailed
information about the settings for each of the resource models included with
IBM Tivoli Monitoring for Databases: Sybase ASE.
The IBM Tivoli Monitoring User’s Guide also contains additional information about
resource models
About resource models
With IBM Tivoli Monitoring for Databases: Sybase ASE you can use preconfigured
resource models to monitor essential resources, and you can customize the
preconfigured resource models to monitor your resources. A resource model
accesses specific performance data from the system at runtime. (For example, the
Process resource model gathers data about processes running on the system.) The
resource models process the data they collect using an algorithm that determines
whether or not the system is performing according to expectations. This enables
you to detect bottlenecks and other potential problems and define automatic
recovery actions from critical situations affecting your resources. This ability frees
system administrators from manually scanning extensive performance data. This
monitoring software integrates with other Tivoli Availability solutions, including
IBM Tivoli Business Systems Manager and IBM Tivoli Enterprise Console.
You can either use the default values for a resource model to collect performance
data or customize a resource model to match specific requirements in your
environment. Distributing resource models using default values enables you to
begin monitoring immediately to obtain useful data concerning your enterprise. As
you become more familiar with the monitoring process and feedback, you might
choose to customize the resource model information.
In addition to customizing preconfigured resource models in IBM Tivoli
Monitoring for Databases: Sybase ASE, you can develop new resource models
using IBM Tivoli Monitoring Resource Model Builder. See the IBM Tivoli Monitoring
Resource Model Builder User’s Guide for information about how to develop a new
resource model.
You can customize a resource model by modifying the following elements of the
resource model configuration:
v Cycle time
© Copyright IBM Corp. 2004 5
v Thresholds
v Parameters
v Indications
– Occurrences
– Holes
– Sending events to IBM Tivoli Enterprise Console
– Severity of event
– Clearing events
– Tasksv Schedule
v Logging
The following information provides brief explanations of the resource model
elements that you can customize depending on the resource model:
Cycle time
When a resource model runs on an endpoint, it gathers data at regular
intervals, called cycles. The interval between cycles is the cycle time, which
is displayed in seconds. A resource model with a cycle time of 60 seconds
gathers data every 60 seconds. Each of the preconfigured resource models
has a default cycle time that you can modify. At each cycle, the resource
model collects data, analyzes it, generates the events, and triggers specified
tasks. See “Customizing cycle time” on page 28.
Thresholds
A threshold is a point that must be reached before a resource model
triggers an occurrence. Each threshold has a default numeric value that
you can change. Typically, this value represents a limit for a satisfactory
resource state. If the monitored resource exceeds this limit, an indication
occurs.
See “Operational modes for thresholds” on page 9 for a complete
explanation of thresholding. See “Customizing thresholds” on page 32 for
complete information about customizing thresholds.
Parameters
A parameter is a value that is used to control how a resource model
operates. Parameters can represent the instances that you want to monitor
or a limit you do not want a resource to exceed. While thresholds can only
be numeric values, parameters can be numeric or string values.
Some resource models have no parameters, others have one or more
parameters. Availability types of resource models do not have any
parameters. Data collection types of resource models have parameters that
allow you to customize how the thresholding works for a resource model.
The Log Monitor resource model and Parametric Event Log resource
model customize what is monitored.
See “Customizing parameters” on page 31 for information about modifying
parameters.
Indications
An indication occurs when the state of a given resource meets defined
criteria. By itself, an indication does not trigger any specific action.
Indications are aggregated to become an event.
6 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
An event is a notification of change in the status of a resource. An event is
triggered when an indication occurs and does not occur (referred to as a
hole) in a set pattern or a set number of times. When you define an event,
you also specify whether these indications must be consecutive, or whether
the sequence can be interrupted by one or more monitoring cycles that do
not register any indication (holes).
An event verifies the persistence of an indication by eliminating
unrepresentative peaks and troughs for the indication. For example, a
process that generates the Process High CPU indication in one cycle might
not threaten other processes if the high usage is not repeated. However, an
indication that persists over several cycles is more likely to be a problem.
Thus, an event defines the significant number of consecutive occurrences of
the indication.
The event notifies the system administrator about the state of a specific
resource. Events can trigger an action, and, if enabled, send a notification
to the IBM Tivoli Enterprise Console event server, IBM Tivoli Business
Systems Manager, or the IBM Tivoli Monitoring Web Health Console.
You can configure indications by specifying the following information:
v Occurrences
v Holes
v Sending events to IBM Tivoli Enterprise Console
v Severity of event
v Clearing events
v Tasks
See “Customizing indications and events” on page 29.
Occurrences and holes
Occurrences and holes record whether or not an indication occurs
during the cycle for a specific resource model. An occurrence is a
cycle during which an indication occurs for a given resource
model.
A hole is a cycle during which an indication does not occur for a
given resource model. A hole means none of the conditions that
generate an indication were met.
IBM Tivoli Enterprise Console server
When the settings for an indication include sending events to the
IBM Tivoli Enterprise Console server, you can view the events in
the IBM Tivoli Enterprise Console if you have compiled and
loaded the relevant Basic Recorder of Objects in C (BAROC) files on
the server. An event carries information including the event class,
event identity, severity, location (host where the event originated),
and description. This information can help to identify the problem.
IBM Tivoli Enterprise Console provides tools for the following
functions:
v Receiving events from various sources
v Processing events using rules
v Grouping events and delegating the groups selectively to
administrators
v Viewing events from multiple sources at a console
Chapter 2. Resource models 7
For information about viewing events, see the IBM Tivoli Enterprise
Console User’s Guide.
Clearing events can also be processed by the IBM Tivoli Enterprise
Console server. If the default procedure is used to enable the
monitoring of events, the IBM Tivoli Enterprise Console server
uses the clearing event to close the associated error event.
Severity
A severity value is assigned to an event when it is sent to the IBM
Tivoli Enterprise Console server or IBM Tivoli Business Systems
Manager because there is a problem. An event can have one of the
following degrees of severity: fatal, critical, warning, harmless, or
minor.
Clearing events
A clearing event is a resource model function that is enabled or
disabled when the resource model is developed. If enabled,
clearing events allow IBM Tivoli Monitoring software to close an
event when the circumstances that caused the event are no longer
present. Clearing events can be processed by the IBM Tivoli
Enterprise Console server and by IBM Tivoli Business Systems
Manager. Clearing events have a severity of harmless regardless of
the severity of the original event, but have the same event ID as
the original event.
For example, if a service stops, the IBM Tivoli Enterprise Console
server receives an event notifying it of this problem. Until the
service restarts, the problem is still present on the endpoint, but
IBM Tivoli Monitoring does not send any further event
notifications to the IBM Tivoli Enterprise Console server. If the
Clearing Event function is enabled, as soon as the service restarts,
a clearing event is sent to the IBM Tivoli Enterprise Console server,
thereby closing the original event. The Clearing Event itself does
not normally appear on the server, because its only function is to
clear the original error event.
When the clearing event function is enabled for a resource model,
events (carrying a specified event ID) are sent only the first time
the aggregation rule is satisfied.
Tasks For any indication, tasks can run automatically. These tasks take
positive steps to remedy the situation, or ensure that information
about the indication is distributed to the appropriate authorities or
entities.
You can associate one or more tasks with a specific indication.
These tasks are automatically triggered when the event occurs and,
typically, are used for restoring satisfactory system service level.
Each time an indication occurs, the system provides notification
that the indication occurred, triggers a task to restore satisfactory
conditions; and if the task is successful, provides notification that
the task was performed. Tasks are associated with the execution of
a CIM method or the execution of a program. Associate a task with
an indication when modifying an existing resource model using
this software. If you associate multiple tasks with an indication,
they can be called in any order, and all at once.
8 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Scheduling
IBM Tivoli Monitoring contains a scheduling feature that enables you to
determine a period within which monitoring takes place and specific
scheduling rules.
The monitoring period is determined by defining a “from” and a “to” date.
The scheduling rules enable you to define time periods on specific days of
the week during which monitoring takes place. Any number of rules can
be defined, allowing you to set up a complex pattern of resource
monitoring for a profile, covering the time periods important to you.
The scheduled times are always interpreted as local times, enabling you to
set up a single rule that monitors the same local time period in different
time zones. For example, if your region covers several time zones, but you
want to monitor morning activities in each time zone, a single rule
defining the monitoring period as between 08:00 and 13:00 is interpreted
locally in each of the time zones, so that you monitor the same relative
period.
All of the times for events or activities reported from endpoints or
gateways are also logged in the local time of the system where they
originated.
Logging
Resource models support data logging to collect and store monitoring data
in a local database.
You can log raw data or aggregated data. If you log raw data, you can also
log Tivoli Data Warehouse data. You can view raw, aggregated, and Tivoli
Data Warehouse data in the IBM Tivoli Monitoring Web Health Console.
You can only see Tivoli Data Warehouse data in the Tivoli Data Warehouse
application.
You can set the interval for aggregation and the amount of data stored in
the Endpoint DB. This governs the amount of disk space used on the
endpoint and limits the amount of data you can see in the IBM Tivoli
Monitoring Web Health Console.
See “Logging data for a resource model” on page 35.
Operational modes for thresholds
Many resource models can be viewed as a collection of rules of the following form:
if (metric >= value) then
SendEvent(name, properties);
These thresholding rules operate by comparing a metric associated with a specific
resource to a value (the threshold) that indicates that the resource is in an
unsatisfactory state, such as when a process is consuming an abnormal amount of
processor time. The default threshold values are chosen to bias against the
occurrence of false positives, so you might need to adapt the thresholds to the
deployment context.
Any threshold can be specified as a fixed threshold, a direct stipulation of the value
in the above form. This is the traditional methodology for specifying threshold
settings. Certain resource models present an additional methodology for specifying
thresholds, statistical thresholding, which uses historically gathered observational
data to compute threshold values.
Chapter 2. Resource models 9
To change the operational mode of thresholding, you must select the mode for
each individual threshold as described in “Customizing thresholds” on page 32. If
you want to use only statistical thresholding, you must modify all of the
″Threshold ... calculation method″ parameters in each of the resource models in a
profile.
Resource models that are enabled for statistical thresholding can be understood as
evaluating a rule of the following form:
if (metric >= percentile(p, observations, conditioning)) then
SendEvent(name, properties);
where:
p Percentile level
observations
Set of observations
conditioning
Set of temporal and metrical data used to inform the threshold
computation
Temporal conditioning imposes sensitivity to the current time of day, day of week, or
both. You can select temporal conditioning. Metrical conditioning is built into the
threshold by the resource model author when a correlation is expected between a
″driver″ metric and a ″driven″ metric. A ″driver″ metric is also known as an
″index″ metric. Where this type of thresholding is used, the value of the ″index″
metric is included in the ″current_index_value″ field on the indication. The rest of
this section describes the goals and detailed operational principles behind
statistical thresholding.
The primary goal of statistical thresholding is to learn ″typical behavior″ from the
observation of the resource in its deployment environment in order to minimize
the amount of tuning that you are required to do. In order to maximize the
applicability of these techniques, the threshold derivation model is based on
percentiles. The use of percentiles rather than other summary statistics allows the
same framework to apply to all metrics independently of the shape of their
distributions. For example, outlier identification based on ″more than so many
standard deviations above the average″ works best for metrics with normal
distributions, and clumsily on those with heavily skewed or multi-modal
distributions. In contrast, a percentile basis can be used to compute a threshold
setting from a specified proportion of observations, allowing a general policy to be
stated that declares typical as below the 90th percentile of observations taken in
the training period. Minimum training for this approach is 20 observations, which
generally gives reasonably good results, but more data are usually desirable.
Since typical behavior tends to be sensitive to the time of day, the day of week, or
both, statistically computed thresholds can be conditioned by the time, the day, or
both. This allows the 90th percentile at 14:00 to reflect a workload that is typically
heavier than one at 02:00, rather than requiring a threshold to be set for worst-case
behavior. This is especially useful when multiple workloads are being serviced by
a single computer under the assumption that each load follows a typical timeline.
Similarly, certain thresholds provided by the resource models incorporate a
relationship between a driver (input or index) metric and a driven (output) metric,
allowing a threshold to be conditioned by (the quartile range of) another metric.
10 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
For example, Figure 1 shows the range of the 10th and 90th percentiles of CPU
consumption as a function of the number of read operations per second.
For a workload that performs a typical amount of work for each block of data
read, this can be an early detector that something has gone awry. If the system is
currently experiencing heavy CPU consumption but few reads, then it is not
performing the work required of it at the expected cost. As this information is
correlated with other indications, both root cause and impact analysis can be
quickly and efficiently performed to ensure cost-effective incident triage.
This small bit of indirection, specification of the criteria by which a threshold
should be computed, rather than the threshold itself, is a powerful mechanism for
minimizing the amount of configuration that you are required to do when a single
profile is to be distributed to multiple machines of differing capabilities or
configurations. For example, a computer with a processor rating of 3GHz will
process a certain bit of computational work faster than a computer with a rating of
1GHz, leading to a lower CPU utilization on the faster machine than the slower.
Setting a threshold in a manner appropriate for the slower machine will miss
performance incidents on the faster computer, which leads to a duplication of
configuration effort. If both computers are currently providing acceptable service at
acceptable cost, then distributing a resource model to both computers that derives
its threshold settings automatically from observations allows a single configuration
to apply, reducing both configuration and maintenance costs.
The ability to condition a threshold by both the time of day and the value of
another metric gives a powerful mechanism for characterizing ″normal″ behavior
and detecting problems quickly and efficiently. As a specific example, Figure 2 on
page 12 shows a distribution of CPU Utilization readings from a simulated web
server over a one-week interval, taken at a sampling rate of one reading per
minute (for 10,080 readings).
Figure 1. Percent CPU utilization against I/O Read Ops/Second
Chapter 2. Resource models 11
Clearly, these data are not normally distributed, because three modes are apparent:
a light load (less than 20% utilization), a moderate load (between 30% and 50%
utilization), and a heavy load (more than 60% utilization). The average one-minute
utilization is 35%, with a standard deviation of 27%, reflecting the fact that
approximately 35% of the readings are below 10% utilization, 60% are below 40%
utilization, and 97% are below 80% utilization. Given these readings alone, settings
ranging from 80% to 100% can be justified for a HIGH CPU UTILIZATION
threshold. If unconditioned statistical thresholding was employed with a threshold
at the 97th percentile, the effective threshold value would be 80.6% at all times.
Figure 3 shows this same data plotted as a function of time, which reveals
additional structure.
In particular, a strong correlation between the time of day and the CPU utilization
is apparent, with a significant spike in the utilization occurring around 6 P.M. on
weekdays. Given this view of the data, a fixed threshold might be established at
around 70% to indicate that the typical behavior of this server is to consume less
Figure 2. Distribution histogram for CPU utilization over a one week period
Figure 3. CPU utilization over a one week period
12 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
than 70% of the available CPU. Alternatively, the deployment of time-of-day
conditioned statistical thresholding with a threshold at the 97th percentile would
give a tighter description of typical, with an effective threshold ranging from 6% to
99% depending on the time of day. The deployment of day-of-week conditioned
statistical thresholding would create effective thresholds of 82% on Monday
through Friday, 69% on Saturday, and 40% on Sunday, automatically.
Figure 4 shows another view of the activity on this simulated server: the number of
queries per minute serviced.
Although the strong correlation with time remains, the strong positive correlation
between queries per minute and one-minute CPU utilization (0.97) suggests
conditioning the threshold for HIGH CPU UTILIZATION by the current value for
queries per minute. Resource models that condition certain ″output″ (or cost)
metrics (like CPU Utilization) by certain ″input″ (or workload characterization)
metrics (like queries per second) incorporate best monitoring practices by stating
an expectation that the input metric and output metrics are correlated. Such
thresholds are always statistical in nature. Operationally, the threshold is computed
by classifying the input metric into the appropriate quartile (0..25, 25..50, 50..75, or
75..100) and computing the output metric percentile from the subset of the
observations that contain an input metric value in the appropriate quartile. That is,
if the input metric is drawn from the lowest quartile, the expectation is that the
monitored resource is ″behaving typically″ if and only if it consumes resources in a
way that was previously demonstrated by examples drawn from the lowest
quartile. In the case of the data in Figures 2 – 4, the thresholds would be computed
as shown in Table 1.
Table 1. Computation of thresholds example
Input Quartile Input Upper Range 97th percentile
1 326 queries/minute 0.05
2 991 queries/minute 0.40
3 1305 queries/minute 0.66
4 2000 queries/minute 0.80
Figure 4. Queries/minute over a one-week period
Chapter 2. Resource models 13
Violations of these thresholds detect changes in the operational characteristics of
the server, which might indicate that a previously sustainable workload is no
longer sustainable. This can happen after updates to applications, for example
when a performance defect is introduced, or after updates to servers such as when
a critical performance parameter is changed or a physical change has occurred in
the execution environment (excessive fragmentation, reduction in available
memory, and so on).
Controlling statistical thresholding
The statistical thresholding capability gathers observational data prior to
computing thresholds. The data collected are stored locally on the endpoint,
reflecting the goal that the thresholds reflect parochial environmental attributes. As
such, the capability is subject to certain data management and training policies.
Each threshold is subject to certain parameters that are global to the resource
model. Among these are the minimum data required before a threshold can be
computed statistically, the summary group size, the raw data retention policy, the
summary data retention policy, and the training policy. The raw and summary data
retention policies determine the maximum amount of data that can be stored for
the metrics for each resource instance, whereas, the training policy determines
what happens when these maxima are reached. Collected data is saved on the local
file system to allow it to be used when it is needed regardless of the operation of
the monitoring engine. Additional data is collected until the configured number of
summary groups is reached.
A key to understanding the role of each of these parameters is understanding the
manner in which observational data are collected, stored, and recalled during the
computation of statistical thresholds. The data are marked for both the time of the
observation and the resource instance, allowing thresholds to be both time
sensitive and adapted to individual instance characteristics. Raw observations are
gathered into raw data retention groups that are comprised of summary group size
observations and constrained to at least 20 observations. These raw data retention
groups are also reduced into summary groups for time and space efficiency.
Summary groups provide a time- efficient and space-efficient mechanism for
combining large numbers of raw observations into an active summary, as well as
providing for efficient temporal conditioning by allowing entire groups to be
included or excluded with small computational effort. Reflecting the concern of
thresholds with extrema detection, the summaries contain data indicating the
number of observation summaries, the time interval covered, and the 1st, 2nd, 5th,
10th, 25th, 50th, 75th, 90th, 98th, and 99th percentile values along with the
minimum and maximum values. Percentiles not explicitly represented in this list
are computed by interpolation.
Temporal conditioning is realized by including a summary group in the active
summary if and only if the time interval of that summary group is consistent with
the current time and the type of temporal conditioning specified. Thresholds can
be conditioned by the current clock time, the current day (name or type), or a
combination of these, resulting in six types of temporal conditioning:
No temporal conditioning
All summary groups
Time of day conditioning
Only summary groups with intervals containing the current time of day
Type of day conditioning
Weekend or weekday summary groups
14 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Day of week conditioning
Only summary groups with intervals containing the current day of week
Time of day and type of day conditioning
Only summary groups that contribute under both time of day and type of
day methods
Time of day and day of week
Only summary groups that contribute under both time of day and day of
week methods
You can independently specify the number of raw data retention groups and
summary groups to be retained on the endpoint. The number of raw observation
groups to retain can be as small as 1 or unlimited; the retention of these data is
enabled primarily for auditing and support purposes. The number of summary
groups to retain can also be as small as 1 or unlimited; however, care must be
taken to ensure that sufficient data are available for the computation of thresholds.
Additional data will allow for more predictive threshold values, but will result in
more data being stored. There is a strict limit to the amount of data stored. It is
defined by summary group size * number of summary groups. To limit the data
stored in memory, the persistant data is saved to disk and read from disk when
each summary period expires. The summary period is defined by cycle time of a
resource model * summary group size.
Training modes
Statistical thresholding requires a certain amount of observational history prior to
proper operation. Two paradigms are generally employed for gathering and
maintaining the relevant history:
Continuous training
Adds the latest observations to the training set indefinitely
Initialization training
Adds observations only until a certain number of observations have been
gathered
Each of these methods is appropriate in distinct situations. Continuous training is
most appropriate when a service is first being rolled into production and typical
behavior is expected to change significantly. Initialization training is most
appropriate when a service is well-established and typical behavior is expected to
remain within certain bounds.
Chapter 2. Resource models 15
16 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Chapter 3. How to use IBM Tivoli Monitoring for Databases:
Sybase ASE
This chapter provides information about how to use IBM Tivoli Monitoring for
Databases: Sybase ASE to achieve the following common purposes:
v “Begin monitoring with preconfigured resource models”
v “Examine the monitoring environment”
v “Recover the operation of a resource” on page 18
v “Collect data and create reports” on page 18
v “Modify resource model values to detect problems” on page 18
For each purpose, there is a list of procedures that you perform to achieve the
purpose. Each of the procedures contains a cross-reference (in parentheses) to
information about performing that procedure. Information about the procedures is
located in subsequent chapters and appendixes of this user’s guide and in the
publications for the following applications:
v Tivoli Management Framework
v IBM Tivoli Monitoring
v IBM Tivoli Enterprise Console
v IBM Tivoli Business Systems Manager
v Tivoli Data Warehouse
Begin monitoring with preconfigured resource models
For monitoring to occur, your environment must first recognize your application
resources and the resource models must be running. If you followed the
procedures in the IBM Tivoli Monitoring for Databases: Sybase ASE Installation and
Setup Guide to install all of the software, you are already monitoring your
application resources. Monitoring began after you installed the applications and
performed the following procedures:
v Add Sybase ASE resources to the Tivoli environment (“Discovering resources to
monitor” on page 21, “Discover” on page 157 in the ″Task reference appendix″)
v Establish the monitoring of resources (“Distributing resource models” on page
23)
You can perform these same procedures any time that you want add new resources
to monitor.
Examine the monitoring environment
After the product has been installed and monitoring has begun as described in
“Begin monitoring with preconfigured resource models,” you can look at your
monitoring environment to see the following:
v Status of resources that are in the environment (Check Status tasks in
Appendix B, “Task reference,” on page 131)
v Which resource models are monitoring the resources and which resources they
are monitoring (“Determining which resource models are monitoring which
managed resources” on page 25)
© Copyright IBM Corp. 2004 17
v View real-time data about Sybase ASE (IBM Tivoli Monitoring User’s Guide, ″Web
Health Console″ section)
v Status of the resource models (IBM Tivoli Monitoring User’s Guide, ″Web Health
Console″ section)
v View information about a resource that is not operating as desired (IBM Tivoli
Enterprise Console documentation, IBM Tivoli Business Systems Manager
documentation)
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 the Start and Stop tasks.
If you have one of the optional applications (IBM Tivoli Enterprise Console, IBM
Tivoli Business Systems Manager, or IBM Tivoli Monitoring Web Health Console),
you can first take a look at information about the event using one of these
interfaces. (See the documentation for these applications for information about
viewing event information.)
To control a resource manually, use the following procedures:
v Check the status of the resource. (Check Status tasks in the Appendix B, “Task
reference,” on page 131)
v Start or stop the resource (Start and Stop tasks in Appendix B, “Task reference,”
on page 131).
To control a resource automatically, set up the resource model to run a task as
described in the following procedure:
v Run a recovery task when a resource is not operating as desired. (“Specifying a
task to run automatically” on page 27)
Collect data and create reports
To collect data about resources and use that data to create reports, use the
following procedures:
v Enable data logging for a resource model (“Logging data for a resource model”
on page 35)
v Schedule when a resource model runs (IBM Tivoli Monitoring documentation)
v View real-time data about Sybase ASE (.IBM Tivoli Monitoring User’s Guide, ″Web
Health Console″ section)
v View historical data using Tivoli Data Warehouse (Tivoli Data Warehouse
documentation)
v Create reports using Tivoli Data Warehouse (Tivoli Data Warehouse
documentation and “Creating reports” on page 38)
For information about installing Tivoli Data Warehouse, see Installing and
Configuring Tivoli Data Warehouse.
Modify resource model values to detect problems
You can modify the preconfigured resource models to detect problems with
resources as needed in your monitoring environment by changing the values of the
following:
18 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
v Frequency with which the resource model gathers data (“Customizing cycle
time” on page 28)
v Thresholds (“Customizing thresholds” on page 32)
v Parameters (“Customizing parameters” on page 31)
v Number of monitoring cycles that must occur to trigger an event (“Customizing
indications and events” on page 29)
v Severity of an event generated by the indication (“Customizing indications and
events” on page 29)
v Specific time periods during which to monitor resources (IBM Tivoli Monitoring
documentation)
Chapter 3. How to use IBM Tivoli Monitoring for Databases: Sybase ASE 19
20 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Chapter 4. Procedures
This chapter contains information about the procedures that you can use for
working with IBM Tivoli Monitoring for Databases: Sybase ASE.
See Chapter 3, “How to use IBM Tivoli Monitoring for Databases: Sybase ASE,” on
page 17 for information regarding when to use these procedures.
Discovering resources to monitor
Objective
To identify Sybase ASE resources so the IBM Tivoli Monitoring for Databases:
Sybase ASE recognizes them, which allows IBM Tivoli Monitoring for Databases:
Sybase ASE to monitor the resources.
Background Information
Tivoli objects that represent Sybase ASE resources are registered in the Tivoli
management region and monitored by the IBM Tivoli Monitoring for Databases:
Sybase ASE resource models.
The Discover task creates objects for resources that exist. These resources must be
running at the time of discovery. With the Discover task, you provide information
about a resource and the task finds the resource and creates an object representing
that resource. You discover resources to monitor by running the Discover task. The
Discover task finds instances of the product that you want to monitor on specific
systems, provided that the instances are running at the time of discovery. When
more than one instance exists on a system, you must rerun the Discover task to
discover each instance. In a clustered environment, you must run the Discover task
for each installation of the target product on each system in the cluster.
Note: If the Tivoli environment traverses a firewall, you should install and
configure the Tivoli Firewall Security Toolbox (FST) in order to correctly
configure and monitor remote applications. Failing to utilize FST may result
in false discovery and intermittent connectivity issues. See the IBM Redbook
Tivoli Enterprise Management Across Firewalls (publication number SG24-5510)
for more information.
You can run the Discover task from the task library (Tivoli desktop), command
line, or policy region context menu.
The Discover task uses the following items that are created during the installation
of IBM Tivoli Monitoring for Databases: Sybase ASE:
v Task library
v Policy region
v Profile that contains the resource models for IBM Tivoli Monitoring for
Databases: Sybase ASE
v Profile manager that subscribes to the profile
Using the Discover task is the preferred method for creating objects because it
creates objects only for resources that exist. If the Discover task does not run for
some reason, you can use a ″Create ... Object″ task (where ... is the name of the
© Copyright IBM Corp. 2004 21
object type). Use the Discover task if possible, because the ″Create ... Object″ task
can create objects for resources that do not exist. The disadvantage of having
objects for non-existent applications is that resource models report that a resource
is down for an object that represents a non-existent resource. The task that checks
status also reports that a resource is down for an object that represents a
non-existent resource.
Required authorization role
SybaseMon_IXB_senior
Before you begin
Install IBM Tivoli Monitoring for Databases: Sybase ASE.
Set the authorization roles that you need as described in ″Setting authorization
roles″ in the IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup
Guide.
Ensure that the application that you want to monitor is running while you perform
this procedure. For the Discover task to work, the application must be installed and
running.
When you finish
Distribute the resource models using the following procedure: “Distributing
resource models” on page 23. (An alternative method is to use the option of the
Discover task that distributes monitoring when discovery happens.)
View the icons for the managed resources that you installed to verify that they
exist.
Procedure
Discover: You can perform these procedures from the command line or from the
Tivoli desktop.
Note: The Tivoli desktop procedure is easier to use than the command-line
procedure because the user interface window prompts for the required
information.
Command line: See Appendix B, “Task reference,” on page 131 for more
information about the command line syntax and an example.
Use the wruntask command as described in “Discover” on page 157.
Example:
wruntask -t "Discover" \
-l "Monitoring for Sybase ASE Utility Tasks" \
-h "@ManagedNode:MyManagedNode" \
-a "@Endpoint:example_ep @Endpoint:other_ep" \
-a "MyManagedNode" \
-a "60" \
-a "no" \
-a "no" \
-a "@EventServer" \
-a "5529" \
-a "SybaseASEServer_AP_SYBASE_IDENTIFIER" \
-a "server1" \
-a "SybaseASEServer_AP_SYBASE_INSTALL_PATH" \
-a "/opt/sybase/" \
-a "SybaseASEServer_AP_SYBASE_OS_USER" \
22 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
-a "sybase" \
-a "SybaseASEServer_AP_SYBASE_USER" \
-a "sa" \
-a "SybaseASEServer_AP_SYBASE_PASSWORD" \
-a "secret" \
-a "SybaseASEServer_AP_SYBASE_SERVER_NAME" \
-a "server1" \
-a "SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME" \
-a "server1_BS" \
-a "SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME" \
-a "server1_MS" \
-a "SybaseASEServer_AP_LogMonitorLogname" \
-a "/opt/sybase/ASE-12_5/install/server1.log" \
-m "600"
See the Tivoli Management Framework Reference Manual for details regarding the
wruntask command and see Appendix B, “Task reference,” on page 131 for more
information about the Discover task.
Tivoli desktop:
1. Right-click on the Monitoring for Sybase ASE policy region on the Tivoli
desktop and select Discover Application Configurations.
2. Complete the fields in the Discover window using the information in
Appendix B, “Task reference,” “Discover” on page 157.
3. Click Apply.
4. Click Set and Execute.
″Create ... Object″: You can perform this procedure manually from the command
line or from the Tivoli desktop.
Command line: See Appendix B, “Task reference,” on page 131 for command line
syntax and an example of the appropriate ″Create ... Object″ task (where ... is the
name of the object type).
Tivoli desktop:
1. Right-click on the Monitoring for Sybase ASE policy region on the Tivoli
desktop.
2. Click Create Sybase ASE Objects —> ″Create ... Object″ (where ... is the name
of the object type).
3. Complete the fields in the ″Create ... Object″ window using the information in
Appendix B, “Task reference,” on page 131.
4. Click Set and Execute.
Distributing resource models
Objective
To distribute resource models and begin monitoring instances of Sybase ASE.
Background Information
You distribute resource models by distributing a profile that includes the resource
models that you want to distribute. You distribute the profile to subscribers, which
are computers that represent instances of Sybase ASE that you want to monitor.
When you distribute resource models, you set up fixed thresholding for the
resource models, because this is the default setting. See “Customizing thresholds”
on page 32
Chapter 4. Procedures 23
on page 32 in the IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide for
information about the options for modifying thresholding and other settings for
resource models.
Required authorization role
admin
Before you begin
Discover the targets for distribution of monitors, using the Discover task described
in “Discover” on page 157.
When you finish
Check the resource models that you distributed to see the results of the
distribution.
(UNIX only) When you are monitoring an application on UNIX, the Availability
resource model will be in Error state when all of the following conditions are true:
v The monitoring engine is running on the system where resource models are
being distributed.
—AND—
v You distribute resource models, as described in this procedure.
—AND—
v You have never run DMXProcess (a resource model from IBM Tivoli Monitoring)
on the target computer.
To resolve this problem, stop and restart the engine for IBM Tivoli Monitoring. For
example, you can use the wdmcmd command to restart the engine on the
endpoint, as in the following example:
wdmcmd -restart -e endpoint_name
Procedure
You can perform this procedure from the command line or from the Tivoli desktop.
Command line: The wdmdistrib command updates subscriber databases and
configuration files. If no subscriber is specified, wdmdistrib updates all
subscribers. The syntax varies depending on the version of Tivoli management
region that you installed. For more information about the wdmdistrib command,
refer to the IBM Tivoli Monitoring User’s Guide.
Use the wdmdistrib command to distribute the profile to the subscribers of the
profile manager as follows:
1. Determine the target objects for distribution:
a. Run the following wlookup command:
wlookup -ar PAC_class
The available classes are as follows:
v SybaseASEServer_IXBb. Locate the objects for distribution using the label that the command returns.
2. Determine the profile:
a. Run the following wlookup command:
wlookup -ar Tmw2kProfile
b. Locate the label of the profile to be distributed.3. Distribute the profile:
24 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
a. Run the following wdmdistrib command:
wdmdistrib -p profile_name @PAC_class:PAC_object
Where:
-p profile_name
Name of the profile that is to be distributed. The profile name can
be fully qualified with the policy region name. If no region is
indicated, the local region is assumed. For example:MonitoringforSybaseASESybaseASE\ServerMonitorProfile.
PAC_class
The available classes are as follows:
v SybaseASEServer_IXB
PAC_object
Name of the objects that represent the managed resource instance to
which you are distributing the resource model. The available objects
are as follows:
v server1@SybaseASEServer_IXB@example_epb. See the IBM Tivoli Monitoring 5.1.2 User’s Guide for other options for the
wdmdistrib command.
Tivoli desktop:
1. Double-click the ″Monitoring for Sybase ASE″ policy region to access the policy
region view.
2. Open the ″Monitoring for Sybase ASE Sybase ASE Server Resource Models″
profile manager. The profile manager window displays the profile that it
contains and the profile manager that contains the available instances.
3. Drag the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile onto the ″Monitoring for Sybase ASE Sybase ASE
Server Instances″ profile manager to distribute resource models to all available
instances.
Determining which resource models are monitoring which managed
resources
Objective
To identify which resource models are running on an endpoint and which
managed resources the resource models are monitoring.
Background information
You can obtain a list of all resource models that have been distributed to a
specified endpoint and the status of those resource models.
Required authorization role
super, senior, admin, or user
Before you begin
See Appendix A, “Resource model reference,” on page 41 for detailed information
about each resource model.
When you finish
Not applicable.
Chapter 4. Procedures 25
Procedure
You can perform this procedure from the command line.
Use the wdmlseng command to determine which resource models are running on
an endpoint and which managed resources they are monitoring. For example:
wdmlseng -e endpoint [-verbose]
where:
endpoint
Tivoli endpoint label
verbose
Displays all indications for each resource model. The worst instance key (if
it exists) and the status (consolidation level) of each indication are also
displayed. The consolidation level indicates the completion status of the
generated occurrences that are required to trigger the particular event.
If a profile is specified, all indications are displayed for each resource
model of that profile.
If a resource model is also specified, all instances are displayed for each
indication of that resource model.
If an indication is also specified, all categories ( indication string property
value) and metrics (indication numeric property value) data are displayed
for each instance.
Refer to the IBM Tivoli Monitoring User’s Guide for more information.
Controlling monitoring
Objective
To control monitoring, profiles, and resource models in the following ways:
v Stop or restart monitoring
v Start, stop, or delete profiles
v Start or stop resource models
Background information
You can control what you are monitoring in several ways.
v If you want to stop monitoring, you can do any of the following:
– Stop all monitoring on an endpoint when you no longer wish to monitor any
of the resources on a particular endpoint.
– Stop an entire profile of resource models when you no longer want to
monitor your resources with any of the resource models in the profile, but
you want to keep the resource models to use at another time.
– Delete a profile of resource models if you want to stop the resource models
and not keep them to use in the future.
– Stop a single resource model when you no longer want to monitor a specific
resource on an endpoint.v If you want to start monitoring, you can do any of the following:
– Restart all monitoring on an endpoint.
– Start an entire profile of resource models.
– Start a single resource model on an endpoint.
26 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Required authorization role
super, senior, or admin
Before you begin
See Appendix A, “Resource model reference,” on page 41 for detailed information
about the resource model that you want to control.
When you finish
Not applicable.
Procedure
v To restart or to stop monitoring on one or more endpoints, use the wdmcmd
command, for example:
wdmcmd -restart -e endpoint
wdmcmd -stop -e endpoint
v To start or to stop profiles or resource models at endpoints or to delete profiles
at endpoints use the wdmeng command, for example:
wdmeng -e endpoint -p profile#region -start
wdmeng -e endpoint -p profile#region -stop
wdmeng -e endpoint -p profile#region -delete
See the IBM Tivoli Monitoring documentation for more information about the
wdmcmd and wdmeng commands.
Specifying a task to run automatically
Objective
To automatically run a task in response to an indication to recover the operation of
a managed resource.
Background information
You can select one or more tasks to run automatically when an indication is raised.
These tasks can access the IBM Tivoli Monitoring event name by accessing the
environment variables.
Required authorization role
admin
Before you begin
See Appendix A, “Resource model reference,” on page 41 for detailed information
about the resource model with which you want to associate tasks.
For information about each task that can be automatically invoked by the resource
model, see Appendix B, “Task reference,” on page 131.
When you finish
Modify any other resource model settings that you want to change. For the
changes to take effect, distribute the resource models as described in “Distributing
resource models” on page 23.
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Chapter 4. Procedures 27
Command line: Use the wdmeditprf command to customize a resource model for
a profile. See the IBM Tivoli Monitoring documentation for information about this
command.
See the IBM Tivoli Monitoring documentation for more information about the
wdm commands.
Tivoli desktop:
1. Open the IBM Tivoli Monitoring Profile window by following these steps:
a. Double-click the ″Monitoring for Sybase ASE″ icon to open the Policy
Region window.
b. Double-click the ″Monitoring for Sybase ASE Sybase ASE Server Resource
Models″ profile manager icon to open the Profile Manager window.
c. Double-click the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile icon to open the IBM Tivoli Monitoring
Profile window. 2. Click the row that contains the resource model with which you want to
associate a task.
3. Click Edit to open the Edit Resource Model window.
4. Click Indications to open the Indications and Actions window.
5. Click the indication to which you want to associate a task.
6. Click Tasks in the Action List area of the Indications and Actions window to
open the Tasks window.
7. Double-click the appropriate task library from the Libraries list to open the
Tasks list.
8. Double-click the appropriate tasks in the Tasks list one at a time.
Additional information: The selected tasks are displayed in the order in which
they will run in the field located under the Libraries and Tasks panels. You
can use the up and down arrows to change the order of the tasks.
If you have added your own tasks, select the Show by Identifier check box to
view the label for each task.
9. If a task requires more information, a Configure Task window opens. Specify
the appropriate parameters in the field in the Configure Task window and
click Change & Close.
10. When you have finished adding tasks to the indication, click Change & Close
in the Tasks window to add the task to the Action List in the Indications and
Actions window.
11. When you have completed changes to the indications and actions, click Apply
Changes & Close in the Indications and Actions window.
Customizing cycle time
Objective
To change the cycle time for a resource model so that the resource model gathers
data at an interval that meets the needs of your monitoring environment.
Cycle time is expressed as seconds.
Background information
See ″cycle time″ on page 6 for information about cycle time.
28 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Required authorization role
admin
Before you begin
See Appendix A, “Resource model reference,” on page 41 for the default cycle time
for each resource model.
When you finish
Modify any other resource model settings that you want to change. For the
changes to take effect, distribute the resource models as described in “Distributing
resource models” on page 23.
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Command line: Use the wdmeditprf command to customize a resource model for
a profile. See the IBM Tivoli Monitoring documentation for information about this
command.
See the IBM Tivoli Monitoring documentation for more information about the
wdm commands.
Tivoli desktop:
1. Open the IBM Tivoli Monitoring Profile window by following these steps:
a. Double-click the ″Monitoring for Sybase ASE″ icon to open the Policy
Region window.
b. Double-click the ″Monitoring for Sybase ASE Sybase ASE Server Resource
Models″ profile manager icon to open the Profile Manager window.
c. Double-click the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile icon to open the IBM Tivoli Monitoring Profile
window.2. Double-click the row that contains the resource model for which you want to
change the cycle time.
3. Click Edit to open the Edit Resource Model window.
4. Enter the number of seconds you want to pass between the intervals when the
resource model gathers data in the Cycle Time field.
5. Click Modify & Close to save your changes.
Customizing indications and events
Objective
To modify a resource model to tailor the required problem persistence to match
your environment, customize the event destinations, and modify the severity of the
event to reflect the importance of the monitored application and conditions in your
environment.
Background information
You can customize the following values for indications and events:
v Occurrences
v Holes
v Send TEC Events
This setting sends events to IBM Tivoli Enterprise Console and IBM Tivoli
Business Systems Manager.
Chapter 4. Procedures 29
v Severity of event
v Clearing events
v Tasks (automated recovery actions)
The procedure below for customizing indications includes modifying the values
above, except for tasks. See “Specifying a task to run automatically” on page 27 for
information about adding automated recovery actions.
See Chapter 2, “Resource models,” on page 5 for descriptions of these parts of a
resource model.
Required authorization role
admin
Before you begin
See Appendix A, “Resource model reference,” on page 41 for detailed information
about the indications for each resource model, including the default settings.
When you finish
Modify any other resource model settings that you want to change. For the
changes to take effect, distribute the resource models as described in “Distributing
resource models” on page 23.
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Command line: Use the wdmeditprf command to customize a resource model for
a profile. See the IBM Tivoli Monitoring documentation for information about this
command.
See the IBM Tivoli Monitoring documentation for more information about the
wdm commands.
Tivoli desktop:
1. Open the IBM Tivoli Monitoring Profile window by following these steps:
a. Double-click the ″Monitoring for Sybase ASE″ icon to open the Policy
Region window.
b. Double-click the ″Monitoring for Sybase ASE Sybase ASE Server Resource
Models″ profile manager icon to open the Profile Manager window.
c. Double-click the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile icon to open the IBM Tivoli Monitoring Profile
window.2. Double-click the row that contains the resource model that you want to
customize.
3. Click Edit to open the Edit Resource Model window.
4. Click Indications to open the Indications and Actions window.
5. Click the indication you want to customize.
6. Make the following changes as appropriate for your requirements:
Number of Occurrences
Enter the number of monitoring cycles during which an indication can
occur before an event is triggered. This value works in conjunction with
the Holes value.
30 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Number of Holes
Enter the number of monitoring cycles in a row that is allowed before
the occurrences count is reset to zero. This value works in conjunction
with the Occurrences value.
Send TEC Events
Select the check box to send any event triggered by an indication to
IBM Tivoli Enterprise Console.
Severity
Select the severity for the event generated by the indication: fatal,
critical, warning, harmless, or minor.
Clearing
Select Yes or No to specify whether clearing events are sent.
Yes The indication is sent as an event the first time it satisfies the
holes and occurrences. No more events are sent until the
conditions specified for the indication are no longer true when
a ’Clearing’ event is sent.
No A new event is sent for each cycle that the conditions specified
for the indication are true.7. Click Apply to apply the changes to the indication and continue with other
changes.
8. Click Apply Changes and Close to save your changes to the indication.
Customizing parameters
Objective
To change the parameters of a resource model so you can customize monitoring to
your environment and optimize the monitoring process.
Background information
Some resource models have one or more parameters. Each parameter can take the
form of a list of strings, a list of numeric values, a Boolean list of predetermined
values from which you can make any combination of selections, or a choice list of
mutually exclusive alternatives. Passwords and user IDs used to interface with the
managed resource are examples of parameters that you might need to change.
See “Operational modes for thresholds” on page 9 for complete information about
thresholding.
Required authorization role
admin
Before you begin
See Appendix A, “Resource model reference,” on page 41 for descriptions and
default settings for the parameters for each resource model.
When you finish
Modify any other resource model settings that you want to change. For the
changes to take effect, distribute the resource models as described in “Distributing
resource models” on page 23.
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Chapter 4. Procedures 31
Command line: Use the wdmeditprf command to customize a resource model for
a profile. See the IBM Tivoli Monitoring documentation for information about this
command.
See the IBM Tivoli Monitoring documentation for more information about the
wdm commands.
Tivoli desktop:
1. Open the IBM Tivoli Monitoring Profile window by following these steps:
a. Double-click the ″Monitoring for Sybase ASE″ icon to open the Policy
Region window.
b. Double-click the ″Monitoring for Sybase ASE Sybase ASE Server Resource
Models″ profile manager icon to open the Profile Manager window.
c. Double-click the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile icon to open the IBM Tivoli Monitoring Profile
window.2. Double-click the row that contains the resource model whose parameters you
want to change.
3. Click Edit to open the Edit Resource Model window.
4. Click Parameters.
5. Select the type of parameter from the Name drop-down list in the Parameters
panel.
Additional information: A description of the parameter is displayed below the
Value panel.
6. Perform one of the following steps depending on the type of parameter:
v Select an element from the Select an Element drop-down list in the Value
panel.
See “Operational modes for thresholds” on page 9 for complete information
about thresholding, and Appendix A, “Resource model reference,” on page
41 for information about the default values.
—or—
v Select a value and click Delete to delete the value.
Enter a value and click Add to add a different value.
See Appendix A, “Resource model reference,” on page 41 for information
about the default values.7. Click Apply Changes to save your changes to a parameter.
8. Click Apply Changes and Close to save your changes and the Parameters
window.
Customizing thresholds
Objective
To change the values of resource model thresholds to meet the needs of your
monitoring environment.
Background information
See ″thresholds″ on page 6 for information about thresholds and “Operational
modes for thresholds” on page 9 for complete information about thresholding.
Required authorization role
admin
32 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Before you begin
See Appendix A, “Resource model reference,” on page 41 for descriptions and
default values for the thresholds for each resource model and each parameter that
governs a threshold.
When you finish
Modify any other resource model settings that you want to change. For the
changes to take effect, distribute the resource models as described in “Distributing
resource models” on page 23.
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Command line: Use the wdmeditprf command to customize a resource model for
a profile. See the IBM Tivoli Monitoring documentation for information about this
command.
See the IBM Tivoli Monitoring documentation for more information about the
wdm commands.
Tivoli desktop:
1. Open the IBM Tivoli Monitoring Profile window by following these steps:
a. Double-click the ″Monitoring for Sybase ASE″ icon to open the Policy
Region window.
b. Double-click the ″Monitoring for Sybase ASE Sybase ASE Server Resource
Models″ profile manager icon to open the Profile Manager window.
c. Double-click the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile icon to open the IBM Tivoli Monitoring Profile
window.2. Double-click the row that contains the resource model with the threshold that
you want to change.
3. Click Edit to open the Edit Resource Model window.
4. To set the operational mode of the thresholds to statistical or fixed, perform the
following steps:
a. Click Parameters.
b. Select the ″Threshold ... calculation method″ from the Name drop-down list
in the Parameters panel.
Additional information: A description of the parameter is displayed below the
Value panel.
c. Select one of the following types of thresholding from the Select an
Element drop-down list in the Value panel:
Fixed Thresholding
This is the default type of thresholding. See “Operational modes for
thresholds” on page 9 for complete information about thresholding.
Statistical Thresholding
See “Operational modes for thresholds” on page 9 for more
information.d. Click Apply Changes to save your changes to a parameter.
e. Click Apply Changes and Close to save your changes and close the
Parameters window.5. If you changed a threshold from fixed to statistical, perform the following
steps:
Chapter 4. Procedures 33
a. In the Edit Resource Model window, double-click the name of the threshold
that you changed.
b. Type the desired value in the field next to the threshold name.
Additional information: The allowed range of values for the statistical
thresholds is 0 – 100. The values for fixed and statistical modes have
different meanings. Always reset the threshold value when you reset the
mode of operation to prevent the resource model from going into an
″Unable to start (142)″ state.
c. Click Apply.6. To change the training methodology for statistical thresholds, perform the
following steps:
a. Click Parameters.
b. Select the ″Training Methodology″ from the Name drop-down list in the
Parameters panel.
Additional information: A description of the parameter is displayed below the
Value panel.
c. Select one of the following types of training from the Select an Element
drop-down list in the Value panel:
Continuous Training
Continuous training simply replaces old data by new data at that
same threshold.
Initialization Training
Initialization training stops additional training when the Summary
Group Retention count parameter is reached.See “Operational modes for thresholds” on page 9 for complete information
about thresholding, and Appendix A, “Resource model reference,” on page
41 for information about the default values.
d. Click Apply Changes to save your changes to a parameter.
e. Click Apply Changes and Close to save your changes and the Parameters
window.7. To change the thresholds values for the resource model, perform the following
steps:
a. In the table that contains the Threshold Names and Threshold Values in the
Edit Resource Model window, click the name of the threshold that you want
to change to display a field containing the value of the threshold and a
description of the threshold.
b. In the field next to the threshold name, enter the desired threshold value.
Additional information: For information about the default values, refer to
Appendix A, “Resource model reference,” on page 41.
c. Click Apply next to the threshold value you entered.
d. Click Modify & Close to save your changes in to the thresholds.
Re-training resource model thresholds
Objective
When running statistical thresholding, clean up the data to re-set the state of
threshold to the initial state so that the resource model re-trains.
34 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Background information
Statistical thresholding uses historical data to determine the effective values for the
thresholds. There may be times when the previous history does not reflect current
conditions and you want to start over and have the statistical engine use only new
data. The threshold data is stored in $LCF_DATDIR/LCFNEW/AMG/stats_data
on the endpoint. This directory contains one directory for each object, each of
which contains a directory for each profile, each of which contains a directory for
each resource model that is collecting statistical data. Deleting data at any of these
levels causes that portion of the system to reinitialize its history.
Required authorization role
None required.
Before you begin
Stop the engine using the following command:
wdmcmd -stop -e ep
When you finish
Restart the engine using the following command:
wdmcmd -restart -e ep
Procedure
You can perform this procedure from the command line:
1. Log on to the endpoint system.
2. Clear the data as follows depending on the type of data you want to clear:
v To clear all of the data for a resource, delete the directory for the object and
all of its subdirectories:
cd $LCF_DATDIR/LCFNEW/AMG/stats_data
rm -rf object_directory
v To clear all of the data for a profile distributed to an object, delete the
directory for the profile and all of its subdirectories:
cd $LCF_DATDIR/LCFNEW/AMG/stats_data/object_directory
rm -rf profile_directory
v To clear the data for a resource model, delete the directory for the profile:
cd $LCF_DATDIR/LCFNEW/AMG/stats_data/object_directory/profile_directory
rm -rf resource_model_directory
Logging data for a resource model
Objective
To enable resource model data logging.
Background information
You can configure a resource model to write logged data in a local database so you
can view the data through the IBM Tivoli Monitoring Web Health Console or
Tivoli Data Warehouse. You can store the following types of data in the database:
Raw data
Data is written exactly as the resource model collects it. All of the
monitored values are collected and copied in the database.
Aggregated data
Data is collected and aggregated at fixed intervals that you define
Chapter 4. Procedures 35
(Aggregation Period). Only the aggregated values are written in the
database. The aggregated data are calculated on the basis of the following
options:
v Maximum
v Minimum
v Average
Tivoli Data Warehouse data
The resource models collect and log the generic resource metric and
attribute data hourly. In addition to maximum, minimum, and average, in
Tivoli Data Warehouse you have the Total option, which calculates
quantitative metrics such as MB and Qty instead of values and
percentages.
You can log raw data, Tivoli Data Warehouse data, or aggregated data. If you log
raw data, you can also log Tivoli Data Warehouse data. Raw data are stored for up
to 24 hours on the local database for the endpoint. Tivoli Data Warehouse data are
stored in Tivoli Data Warehouse until the data are scheduled to be pruned.
Appendix A, “Resource model reference,” on page 41 contains a list of logging
properties for each resource model.
Required authorization role
admin
Before you begin
See Appendix A, “Resource model reference,” on page 41 for detailed information
about the resource model for which you want to log data.
When you finish
v Modify any other resource model settings that you want to change. For the
changes to take effect, distribute the resource models as described in
“Distributing resource models” on page 23.
v Use the following application interfaces to look at the data logged by a resource
model:
– IBM Tivoli Monitoring Web Health Console
– Tivoli Data Warehouse
The IBM Tivoli Monitoring Web Health Console displays real-time or historical
data. You can view raw, aggregated, and Tivoli Data Warehouse data in the IBM
Tivoli Monitoring Web Health Console. To look at raw data, use the History
View of the IBM Tivoli Monitoring Web Health Console. You can also view the
current health of a resource model in the IBM Tivoli Monitoring Web Health
Console.
You can only see Tivoli Data Warehouse data in the Tivoli Data Warehouse
application. Use Tivoli Data Warehouse to view the results of aggregated data.
v Create reports using Tivoli Data Warehouse as described in “Creating reports”
on page 38.
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Command line: Use the wdmeditprf command to customize a resource model for
a profile. See the IBM Tivoli Monitoring documentation for information about this
command.
36 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
See the IBM Tivoli Monitoring documentation for more information about the
wdm commands.
Tivoli desktop:
1. Open the IBM Tivoli Monitoring Profile window by following these steps:
a. Double-click the Monitoring for Sybase ASE icon to open the Policy Region
window.
b. Double-click the Monitoring for Sybase ASE Sybase ASE Server Resource
Models profile manager icon to open the Profile Manager window.
c. Double-click the profile icon to open the IBM Tivoli Monitoring Profile
window.2. Click the row that contains the resource model that you want to log data.
3. Click Edit to open the Edit Resource Model window.
4. Click Logging to open the Logging window.
5. Select the Enable Data Logging check box in the Data Logging Settings panel
to enable logging.
6. Select the check boxes for the types of data you want to log as described in the
background information for this procedure:
Raw Data
This option is available only if Aggregated Data is not selected.
TEDW Data
If Tivoli Data Warehouse is installed, you can select the TEDW Data
check box to store the raw data for use in Tivoli Data Warehouse. This
option is not available if Aggregated Data is selected.
Aggregate Data
This option is available only if Raw Data or TEDW Data are not
selected.7. If you selected the Aggregate Data check box, perform the following steps to
specify the aggregation rule applied to the data before it is written to the
database:
a. Set Hours and Minutes of the Aggregation Period to the required values.
b. Select one or more of the check boxes for the following functions to perform
on the numerical data collected during the aggregation period before it is
written to the database:
Maximum
Calculates and logs the peak value in each aggregation period.
Minimum
Calculates and logs the lowest value in each aggregation period.
Average
Calculates and logs the average of all values in each aggregation
period. Average is the default setting.8. Set the Hours and Minutes of the Historical Period to specify how long you
want data to be stored so that the data can be viewed at the IBM Tivoli
Monitoring Web Health Console.
9. Click Apply Changes and Close to save your changes and close the Logging
window.
Chapter 4. Procedures 37
Creating reports
Objective
To create reports that assist you in analyzing the health and performance of your
Sybase ASE resources over a period of time, predicting resource usage, and
diagnosing potential problems before they occur.
Background information
Tivoli Data Warehouse enables you to access application reports (from Crystal
Reports). The IBM Tivoli Monitoring for Databases: Sybase ASE reports provide
information about the availability and performance of Sybase ASE over a period of
time.
The IBM Tivoli Monitoring Component Services warehouse pack provides six
predefined reports for IBM Tivoli Monitoring for Databases: Sybase ASE in the
IBM Tivoli Application Monitoring folder in Crystal ePortfolio:
v Application Availability Report
v Application Availability Hourly Report
v Process Consumption Report
v Process Consumption Hourly Report
v System Resources Report
v System Resources Hourly Report
Application Availability Report
Application Availability Report is a health report showing the availability
of an application. The purpose of the report is to show that the
applications were up and capable of meeting business needs. Alternatively,
it might show those applications that were unable to maintain 100%
availability, from 98.5% to 80% to 0%. This allows you to focus on those
computers that require extra attention to meet business needs. The report
has the following parameters:
Application Name
Used to specify the name of the application as it is represented in
the database. The DB2® wildcard % is supported, so applications
can be filtered using Sybase ASE Server.
Availability State
Used to select the availability metric.
Day, Week, or Month
Used to select the level of rollup: daily, weekly, or monthly.
Hostname
Used to select a specific host when more than one is in the
database. The DB2 wildcard % is supported, so hostnames can be
filtered using ″myHost%″.
Min, Max, or Average
Used to select the minimum, maximum, or average of the
availability metric.
Percent Available
Used to filter out computers based on a percentage available.
Intended to help filter out the machines that are 100% available.
Using ″99.99″ results in a report that shows machines that
experienced some downtime.
38 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Time Period
Used to select the number of days for the report to look back at
historical data. See IBM Tivoli Monitoring Component Services,
Version 5.1.3, Guide for Warehouse Pack, Version 1.3.0.0, using Tivoli
Data Warehouse 1.2 for an example.
Application Availability Hourly Report
Application Availability Hourly Report is a health report showing the
availability of an application. This report is similar to the previous report
but with hourly data for a specific day.
Process Consumption Report
Process Consumption Report is a summary report showing resource use by
the processes associated with an application. The purpose of the report is
to show the resources such as memory and handles consumed by each
process. The processes can be named explicitly, or you can use only the
application name so that the reports show all the processes for that
application. For reporting purposes all the processes have been rolled up
by process name under the respective application name to save space on
the charts. The data however is preserved with a process and PID
combined key so that data can be extracted with a custom report. The
report has the following parameters:
Application Name
Used to specify the name of the application as it is represented in
the database. The DB2 wildcard % is supported, so applications
can be filtered using ″myApp%″.
Metric Used to select the process metric.
Day, Week, or Month
Used to select the level of rollup: daily, weekly, or monthly.
Hostname
Used to select a specific host when more than one is in the
database. The DB2 wildcard % is supported, so hostnames can be
filtered using ″myHost%″.
Min, Max, or Average
Used to select the minimum, maximum, average, or total of the
metric.
Time Period
Used to select the number of days for the report to look back at
historical data.
Process Name
Used to select the processes. The DB2 wildcard % is supported. See
IBM Tivoli Monitoring Component Services, Version 5.1.3, Guide for
Warehouse Pack, Version 1.3.0.0, using Tivoli Data Warehouse 1.2 for an
example.
Process Consumption Hourly Report
Process Consumption Hourly Report is a summary report showing
resource use by the processes associated with an application. This report is
similar to the previous report but with an hourly data for a specific day.
System Resource Report
System Resource Report is a summary report showing resource use on a
system. The purpose of this report is to show the load on computers
hosting business applications. The report has the following parameters:
Chapter 4. Procedures 39
Hostname
Used to select a specific host when more than one is in the
database. The DB2 wildcard % is supported, so hostnames can be
filtered using ″myHost%″.
Metric Used to select the process metric.
Day, Week, or Month
Used to select the level of rollup: daily, weekly, or monthly.
Min, Max, or Average
Used to select the minimum, maximum, average or total of the
metric.
Time Period
Used to select the number of days for the report to look back at
historical data, for example, the Average userTime on all hosts by
month for the past year. This time period shows the usage trends
(the applications will typically run in user space) on the machine
for the last year. This time period also shows over and under
utilized systems, suggesting that some applications be moved from
one over utilized machine to one that is under utilized. See IBM
Tivoli Monitoring Component Services, Version 5.1.3, Guide for
Warehouse Pack, Version 1.3.0.0, using Tivoli Data Warehouse 1.2 for an
example.
System Resource Hourly Report
System Resource Hourly Report is a summary report showing resource use
on a system. This report is very similar to the previous report but shows
hourly data for a specific day.
Required authorization role
Not applicable
Before you begin
For information about installing Tivoli Data Warehouse, see Installing and
Configuring Tivoli Data Warehouse.
Enable IBM Tivoli Monitoring for Databases: Sybase ASE to collect data as
described in “Logging data for a resource model” on page 35.
When you finish
Use the detailed information in the reports to analyze how your application
resources are performing in regard to application availability, system resource
consumption, and process resource consumption.
Procedure
See the IBM Tivoli Monitoring Component Services, Version 5.1.3, Guide for Warehouse
Pack, Version 1.3.0.0, using Tivoli Data Warehouse 1.2 for complete information about
Tivoli Data Warehouse reports applicable to IBM Tivoli Monitoring for Databases:
Sybase ASE.
40 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix A. Resource model reference
This appendix contains detailed information about the IBM Tivoli Monitoring for
Databases: Sybase ASE resource models.
Resource models capture and return information about IBM Tivoli Monitoring for
Databases: Sybase ASE. The default values in the resource models represent the
best practices for monitoring. You can change many of the settings for a resource
model to customize it for your monitoring needs.
Table 2 lists the resource models included with IBM Tivoli Monitoring for
Databases: Sybase ASE.
Table 2. IBM Tivoli Monitoring for Databases: Sybase ASE resource models
Resource model Page Internal Name Description
Log Monitor 43 LogMonitor Monitors one or more of the log files for the
application.
Sybase Availability 54 SybaseAvailability_IXB Monitors the availability of the Sybase ASE server.
Locks RM 60 LocksRM_IXB Monitors the locks in the Sybase ASE server.
Data Cache RM 75 DataCacheRM_IXB Monitors the data cache in the Sybase ASE server.
Space Usage RM 81 SpaceUsageRM_IXB Monitors the space used by each database in the
Sybase ASE server.
Process Waits RM 102 WaitsRM_IXB Monitors the processes waiting in the Sybase ASE
server.
State RM 108 StateRM_IXB Monitors the state of the Sybase ASE server.
Traffic RM 118 TrafficRM_IXB Monitors the traffic of the Sybase ASE server.
In this appendix, a section for each resource model describes the configuration of
the resource model by covering the following information, including the settings
that you can change:
Description
Purpose of the resource model and information about the following
characteristics of the resource model:
v Internal name
Name of the resource model as you use it in the command line
v Category
Type of resource model
v Indications
List of indications for the resource model.
v Thresholds
List of thresholds for the resource model.
v Parameters
List of parameters for the resource model.
v Default cycle time
Number of seconds during which data are collected one time
© Copyright IBM Corp. 2004 41
Supported platforms
Operating systems environment in which the resource model runs
Target managed resource
Name of the managed resource to which this resource model is relevant
Indications and events
Information about all of the indications for the resource model in table
format and a section of more specific information about each indication:
v Event name
v Default severity
v Whether the resource model has Clearing events enabled
v Page where the indication is described in this guide
The table contains the following information for each indication:
Each section about a specific indication contains the following information:
v When the resource model sends the indication and why
v List of the attributes for the indication and notation regarding which
attributes are keys
v Table that describes the following default settings for the indication:
– Send events to IBM Tivoli Enterprise Console
– Send events to IBM Tivoli Business Systems Manager
– Occurrences
– Holes
Thresholds
List of the thresholds, if any, for the resource model in a table format with
a short description and default value for each threshold associated with the
resource model.
Parameters
List of parameters, if any, for the resource model with a short description
and default value for each threshold associated with the resource model.
The name in parentheses is the internal name.
Logging
A table shows the name of the managed resource, context, and properties
that the resource model logs with key properties noted.
Return codes
Information that the resource model returns such as status or availability.
CLI example
Example of the syntax for a resource model that illustrates the variable
options of the wdmeditprf command that are specific to the resource
model such as the name of the resource model, thresholds, parameters,
parameter values, and events.
The following chapters contain more information about resource models and
procedures for working with resource models:
v Chapter 4, “Procedures,” on page 21 provides procedural information about
setting up and monitoring resources, and about customizing resource models.
v Chapter 2, “Resource models,” on page 5 provides conceptual information about
resource models and thresholding.
42 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Log Monitor
Description
Provides generic log monitoring. The IBM Tivoli Monitoring Component Services
component of the IBM Tivoli Monitoring for Databases: Sybase ASE provides the
Log Monitor resource model, which you can use to monitor any application log.
The Log Monitor resource model is customized for IBM Tivoli Monitoring for
Databases: Sybase ASE. Though you can modify the resource model settings, do
not modify the customized parameter values. Do not delete this resource model. If
you do not want to use this resource model, you can disable it. If you delete it,
you lose all of the customized parameters. If you want to use this resource model
for monitoring a different application, create a new profile and add the
LogMonitor resource model with customized parameters.
The following list contains the key characteristics of this resource model:
Internal name
LogMonitor
Category
Application
Indications
v Severity 0 Log Event
v Severity 1 Log Event
v Severity 2 Log Event
v Severity 3 Log Event
v Severity 4 Log Event
v Maximum Log Bytes Exceeded
Thresholds
v Maximum Read Bytes Available
Parameters
v ApplicationName
v LogfileMonitorConfigFileName
v LogMonitorLogname
v LogMonitorMetrics
v LogMonitorSev0Formats
v LogMonitorSev1Formats
v LogMonitorSev2Formats
v LogMonitorSev3Formats
v LogMonitorSev4Formats
Default cycle time
60 seconds
Supported platforms
The Log Monitor resource model supports the following platforms: aix4-r1,
hpux10, linux-ix86, solaris2,w32-ix86, linux-ppc, linux-s390, os400
Appendix A. Resource model reference 43
Target managed resource
Endpoint or object
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
Severity 0 Log Event LogMonitor_Severity_0_Log_Event Fatal No 45
Severity 1 Log Event LogMonitor_Severity_1_Log_Event Critical No 46
Severity 2 Log Event LogMonitor_Severity_2_Log_Event Error No 47
Severity 3 Log Event LogMonitor_Severity_3_Log_Event Warning No 48
Severity 4 Log Event LogMonitor_Severity_4_Log_Event Harmless No 48
Maximum Log Bytes
Exceeded
LogMonitor_MaxLogBytesExceeded Warning No 44
Maximum Log Bytes Exceeded indication
Occurs when the number of bytes written into a monitored log during a single
monitoring cycle exceeds the specified threshold. This indicates that the cycle time
for the resource model might be too long. Data that cannot be read during a cycle
is read on the next monitoring cycle.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
@application_label@: Log bytes available for reading exceeds the threshold
(@MaxReadBytesThreshold@ bytes) for log, @LogName@
This indication has the following attributes:
application_class
Class of the registered object
application_label
Label for the registered object
application_oid
Object identifier of the registered object
application_version
Version of the managed resource; for example, 2000 or 2003
InstanceName
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter. (key attribute)
LogName
Name of the log to monitor (key attribute)
MaxReadBytesThreshold
Maximum number of bytes that are to be read from a log each time the log
is accessed
44 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
This indication has the following threshold: Maximum Read Bytes Available
Threshold
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events No
Occurrences 1
Holes 0
Severity 0 Log Event indication
Occurs when a log entry that matches the severity 0 regular expression formats is
found in a monitored log.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
@application_label@: @Text@
This indication has the following attributes:
application_class
Class of the registered object
application_label
Label for the registered object
application_oid
Object identifier of the registered object
application_version
Version of the managed resource; for example, 2000 or 2003
InstanceName
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter. (key attribute)
Offset
Offset, in bytes, where this entry was found in the log (key attribute)
Length
Length, in bytes, of the entry as it was found in the log
LogMatchSeverity
Numerical severity assigned to this log entry. This severity number is
associated with the regular expression log match format that was used to
match and retrieve this entry from the log.
LogName
Name of the log to monitor (key attribute)
Text Text of the log entry from the log
Appendix A. Resource model reference 45
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events No
Occurrences 1
Holes 0
Severity 1 Log Event indication
Occurs when a log entry that matches the severity 1 regular expression formats is
found in a monitored log.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
@application_label@: @Text@
This indication has the following attributes:
application_class
Class of the registered object
application_label
Label for the registered object
application_oid
Object identifier of the registered object
application_version
Version of the managed resource; for example, 2000 or 2003
InstanceName
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter. (key attribute)
Offset
Offset, in bytes, where this entry was found in the log (key attribute)
Length
Length, in bytes, of the entry as it was found in the log
LogMatchSeverity
Numerical severity assigned to this log entry. This severity number is
associated with the regular expression log match format that was used to
match and retrieve this entry from the log.
LogName
Name of the log to monitor (key attribute)
Text Text of the log entry from the log
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
46 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Setting Default value
Clearing events No
Occurrences 1
Holes 0
Severity 2 Log Event indication
Occurs when a log entry that matches the severity 2 regular expression formats is
found in a monitored log.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
@application_label@: @Text@
This indication has the following attributes:
application_class
Class of the registered object
application_label
Label for the registered object
application_oid
Object identifier of the registered object
application_version
Version of the managed resource; for example, 2000 or 2003
InstanceName
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter. (key attribute)
Offset
Offset, in bytes, where this entry was found in the log (key attribute)
Length
Length, in bytes, of the entry as it was found in the log
LogMatchSeverity
Numerical severity assigned to this log entry. This severity number is
associated with the regular expression log match format that was used to
match and retrieve this entry from the log.
LogName
Name of the log to monitor (key attribute)
Text Text of the log entry from the log
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events No
Occurrences 1
Holes 0
Appendix A. Resource model reference 47
Severity 3 Log Event indication
Occurs when a log entry that matches the severity 3 regular expression formats is
found in a monitored log.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
@application_label@: @Text@
This indication has the following attributes:
application_class
Class of the registered object
application_label
Label for the registered object
application_oid
Object identifier of the registered object
application_version
Version of the managed resource; for example, 2000 or 2003
InstanceName
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter. (key attribute)
Offset
Offset, in bytes, where this entry was found in the log (key attribute)
Length
Length, in bytes, of the entry as it was found in the log
LogMatchSeverity
Numerical severity assigned to this log entry. This severity number is
associated with the regular expression log match format that was used to
match and retrieve this entry from the log.
LogName
Name of the log to monitor (key attribute)
Text Text of the log entry from the log
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events No
Occurrences 1
Holes 0
Severity 4 Log Event indication
Occurs when a log entry that matches the severity 4 regular expression formats is
found in a monitored log.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
48 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
@application_label@: @Text@
This indication has the following attributes:
application_class
Class of the registered object
application_label
Label for the registered object
application_oid
Object identifier of the registered object
application_version
Version of the managed resource; for example, 2000 or 2003
InstanceName
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter. (key attribute)
Offset
Offset, in bytes, where this entry was found in the log (key attribute)
Length
Length, in bytes, of the entry as it was found in the log
LogMatchSeverity
Numerical severity assigned to this log entry. This severity number is
associated with the regular expression log match format that was used to
match and retrieve this entry from the log.
LogName
Name of the log to monitor (key attribute)
Text Text of the log entry from the log
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events No
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the Log
Monitor resource model:
Maximum Read Bytes Available Threshold (LogMonitorMaxReadBytes)
Maximum number of bytes that are to be read from a log each time the log
is accessed. The remaining data are read during the next monitoring cycle.
Default: 1MB (1048576)
Parameters
This resource model has default parameters and customized parameters.
Appendix A. Resource model reference 49
The following list shows the name (internal name), a short description, the default
value, and the customized value for each parameter that you can set for the Log
Monitor resource model:
Application Name (ApplicationName)
Enter the name of the application with the log to be monitored. This is an
arbitrary value that is included in all events and logged historical data. This
parameter is optional.
Customized parameter value for all objects: Sybase ASE
Log Metrics (LogMonitorMetrics)
Specify which event count metrics are to be logged for historical purposes.
This resource model tallies the number of events sent based on the severities
listed for each monitored log. This parameter allows you to enable or disable
logging of these tallies.
The following metrics are available:
v Severity 0 Event Count (numSeverity0EventCount): TRUE
v Severity 1 Event Count (numSeverity1EventCount): TRUE
v Severity 2 Event Count (numSeverity2EventCount): TRUE
v Severity 3 Event Count (numSeverity3EventCount): TRUE
v Severity 4 Event Count (numSeverity4EventCount): TRUE
Customized parameter value for monitoring SybaseASEServer_IXB: false
LogfileMonitor Configuration Filename (LogMonitorConfigFilename)
Enter the LogMonitor configuration filename. This file contains configuration
and pattern matching expressions specifying how to monitor the logs. The
filename is relative to $LCF_DATDIR. Changes to the Configuration Filename
or content are not active until the next time the resource model is stopped and
restarted. This parameter is required. If a LogMonitor configuration file is not
present at the specified location a default configuration file is created. This file
is XML based and has its own DTD. See Appendix D, “Data providers
reference,” on page 179.
Customized parameter value for monitoring SybaseASEServer_IXB:
Log Name (LogMonitorLogname)
Enter the name of each fully-qualified log that you want to monitor on a
separate line in the parameter. Wildcard characters, asterisks (*), and question
marks (?) are allowed in log names for the purpose of monitoring sets of
rolling logs. When a wildcard character is specified in a log name, only the
most recently updated log that matches the specified log name is monitored.
Wildcard characters are only allowed in the filename portion of the specified
log name. Wildcards are not allowed in the path portion of the log name.
Platform-specific log names can be identified by appending the log name with
a comma-separated list of platform names within parentheses. If a platform list
is not specified for a log name, the log will be monitored on all platforms. For
example:
c:\\temp\\my.log(w32-ix86)
/tmp/my.log(aix4-r1,solaris2,linux-ix86)
/tmp/XYZ/myapp*.log(aix4-r1,solaris2)
/tmp/abc/msg.log
Duplicate log names are filtered. This parameter is required unless log names
are already provided with the target application object.
50 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Customized parameter value for monitoring SybaseASEServer_IXB: ″The value
of the ″Sybase Adaptive Server log file name″ parameter specified on Discover
or Create object.″ object
Severity 0 Matching Formats (LogMonitorSev0Formats)
Enter regular expression formats for matching severity 0 log entries. These
regular expressions are used for matching log entries in addition to any regular
expressions specified in the configuration file for this resource model. This
parameter is optional.
Customized parameter value for monitoring SybaseASEServer_IXB: default
Severity 1 Matching Formats (LogMonitorSev1Formats)
Enter regular expression formats for matching severity 1 log entries. These
regular expressions will be used for matching log entries in addition to any
regular expressions specified in the configuration file for this resource model.
This parameter is optional.
Customized parameter value for monitoring SybaseASEServer_IXB:
v multi-line match=true match all mode=false expression=^.*Error: 605.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 624.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 625.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 806.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 813.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 1601.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 1605.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 2503.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 2620.*\n.*$
v multi-line match=true match all mode=false expression=^.*Error: 7733.*\n.*$
Severity 2 Matching Formats (LogMonitorSev2Formats)
Enter regular expression formats for matching severity 2 log entries. These
regular expressions are used for matching log entries in addition to any regular
expressions specified in the configuration file for this resource model. This
parameter is optional.
Customized parameter value for monitoring SybaseASEServer_IXB: default
Severity 3 Matching Formats (LogMonitorSev3Formats)
Enter regular expression formats for matching severity 3 log entries. These
regular expressions are used for matching log entries in addition to any regular
expressions specified in the configuration file for this resource model. This
parameter is optional.
Customized parameter value for monitoring SybaseASEServer_IXB: default
Severity 4 Matching Formats (LogMonitorSev4Formats)
Enter regular expression formats for matching severity 4 log entries. These
regular expressions will be used for matching log entries in addition to any
regular expressions specified in the configuration file for this resource model.
This parameter is optional.
Customized parameter value for monitoring SybaseASEServer_IXB: default
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Appendix A. Resource model reference 51
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
Value of the
ApplicationName parameter
—or—
″Unknown_Application″ if a
value is not set in the
ApplicationName parameter
LogMonitor v InstanceName*
v Severity0EventCount
v Severity1EventCount
v Severity2EventCount
v Severity3EventCount
v Severity4EventCount
An asterisk (*) denotes a key property.
The non-key properties are only logged if specified for logging in the resource
model parameter, LogMonitorMetrics. The following list describes the properties
that the resource model can log:
InstanceName*
Name of the instance to monitor. The default value is the contents of the
ApplicationName parameter.
Severity0EventCount
Number of severity 0 log entries found in the log during the current cycle
Severity1EventCount
Number of severity 1 log entries found in the log during the current cycle
Severity2EventCount
Number of severity 2 log entries found in the log during the current cycle
Severity3EventCount
Number of severity 3 log entries found in the log during the current cycle
Severity4EventCount
Number of severity 4 log entries found in the log during the current cycle
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
901 Unable to
start (101)
Required resource model parameters were not
specified. See log for more information.
Provide values for missing resource
model parameters. Then, redistribute
the resource model.
310 Failed (110) Error parsing configuration file. See the AMG log
for more information.
Edit the LogMonitor configuration
XML file on the endpoint and correct
any syntax or configuration errors.
See Appendix D, “Data providers
reference,” on page 179. Then, restart
the resource model.
311 Failed (111) Error parsing regular expression match format
string. See the AMG log for more information.
Modify regular expression format
strings in the resource model
parameters and or configuration
XML file to correct and syntax errors.
Then, restart the resource model.
52 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
312 Failed (112) Error processing the configuration file. See the
AMG log for more information.
v Correct any problems related to
access privileges for the
configuration file and location.
v Ensure that the configuration
filename provided does not refer
to a subdirectory.
Then, restart the resource model.
313 Failed (113) A non-numeric threshold value was supplied.
The threshold must be a positive integer.
Ensure that the threshold provided to
the resource model and data
provider is a positive integer. Then,
redistribute the resource model.
315 Failed (115) An invalid severity “id” was supplied in a
<severity> element in the configuration XML file.
The severity id must be a non-negative integer.
Ensure that the “id” attribute
supplied in each <severity> element
in the configuration XML file
contains a non-negative integer
representing severity. Then, restart
the resource model.
316 Failed (116) Error processing the mappingstring for the
specified CIM class being collected by the
resource model. See the AMG log for more
information.
Edit the MOF file containing the CIM
class being collected be the
LogMonitor resource model and
correct any syntax errors in the
mappingstring(s). Then, restart the
resource model.
318 Failed (118) Error retrieving the log names to monitor. See
the AMG log for more information.
Correct any problems identified in
the AMG log. Then, restart the
resource model.
320 Failed (120) Error loading data provider plug-in. See the
AMG log for more information.
v Ensure that the plug-in classname
is correctly identified in the
LogMonitor configuration XML
file.
v Ensure that the plug-in class (or
jar) is in the appropriate
subdirectory for inclusion in the
CLASSPATH. The best location is
$LCF_DATDIR/LCFNEW/ITM/PACS
CLI example
You can use this example to add the resource model to a profile named
″PROFILE″.
wdmeditprf -P PROFILE -add LogMonitor
Appendix A. Resource model reference 53
Sybase Availability
Description
Monitors the availability of the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
SybaseAvailability_IXB
Category
Monitoring for Sybase ASE
Indications
v Application Unavailable
Thresholds
v None
Parameters
v None
Default cycle time
60 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX®, Linux™ for X86 (for specific versions see the
″System and software requirements″ appendix in the IBM Tivoli Monitoring for
Databases: Sybase ASE Installation and Setup Guide).
Target managed resource
SybaseASEServer_IXB
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
Application Unavailable SybaseAvailability_\IXB_ApplicationUnavailable
Critical Yes 54
Application Unavailable indication
The Application is not running because one or more of the processes and/or
services required for the application to perform its intended function is not
running.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
54 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Critical Processes/Services for the application (application object class)
are not running.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
Application
Name of the application. (key attribute)
FailingApplicationComponents
List of required application elements which are not running.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Thresholds
The Sybase Availability resource model has no thresholds.
Parameters
The Sybase Availability resource model has no parameters.
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
Application Availability availabilityStateUp
Application Availability availabilityStateDown
Appendix A. Resource model reference 55
Managed resource Context Properties
Application Availability availabilityStateWarning
Application Availability Application.applicationName *
System SystemCapacity System.name *
System SystemCapacity Application.applicationName
System SystemCapacity idleTime
System SystemCapacity systemTime
System SystemCapacity userTime
System SystemCapacity packetInRate
System SystemCapacity packetOutRate
System SystemCapacity pageInputRate
System SystemCapacity pageOutputRate
Process ResourceConsumption Application.applicationName *
Process ResourceConsumption processName *
Process ResourceConsumption processId *
Process ResourceConsumption memoryUsed
Process ResourceConsumption percentProcessorTime
Process ResourceConsumption virtualSize
Process ResourceConsumption pageFaults
Process ResourceConsumption workingSetSize
Process ResourceConsumption threadCount
Process ResourceConsumption handleCount
Process ResourceConsumption readOperationRate
Process ResourceConsumption writeOperationRate
Process ResourceConsumption kernelModeTime
Process ResourceConsumption userModeTime
An asterisk (*) denotes a key property.
The following list describes the properties that the resource model logs:
availabilityStateUp
100 if the application is running correctly, 0 if the application is not
running.
availabilityStateDown
0 if the application is running correctly, 100 if the application is not
running.
availabilityStateWarning
0 if the application is running correctly, 100 if the application is in a
degraded state.
Application.applicationName
The name of the application.
System.name
An identifier for the system. It will reflect the operating system running.
(key attribute)
56 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Application.applicationName
The name of the application being monitored. This allows correlation
between the system and application measurments.
idleTime
The percent idle CPU time on the system.
systemTime
The percent of the CPU being used by the system.
userTime
The percent of the CPU being used by user processing.
packetInRate
The rate at which packets are arriving from the network (packets/sec).
This is logged on Windows systems.
packetOutRate
The rate at which packets are being sent to the network (packets/sec). This
is logged on Windows systems.
pageInputRate
The rate at which pages are loaded from disk (pages/sec).
pageOutputRate
The rate at which pages are swapped out to disk (pages/sec).
Application.applicationName
The name of the application being monitored. This process is part of the
application. This allows correlation between applications and process data.
(key attribute)
processName
The name of the process. (key attribute)
processId
The numeric process id (PID) for the process. (key attribute)
memoryUsed
The total memory used by the process. This is logged on Unix.
percentProcessorTime
The total percentage of the processor time used by the process.
virtualSize
The amount of virtual memory used by the process. This is logged on
Windows.
pageFaults
The number of page faults caused by this process. This is logged on
Windows.
workingSetSize
The working set size of the process. This is logged on Windows.
threadCount
The number of threads currently allocated by the process. This is logged
on Windows.
handleCount
The number of handles currently allocated by the process. This is logged
on Windows.
Appendix A. Resource model reference 57
readOperationRate
The read operations performed by this process (reads/sec). This is logged
on Windows.
writeOperationRate
The write operations performed by this process (reads/sec). This is logged
on Windows.
kernelModeTime
The amount of kernel processing performed on behalf of this process. This
is logged on Windows.
userModeTime
The amount of CPU time used by the process (not including kernel time).
This is logged on Windows.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
610 Retrying (10) No instances found. The resource model will
continue to run.
None. This can be normal.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add SybaseAvailability_IXB
58 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
To add the resource model, SybaseAvailability_IXB, to the profile, ″MyProfile″:
wdmeditprf -P MyProfile -add SybaseAvailability_IXB
To enable raw and Tivoli Data Warehouse data logging for the
SybaseAvailability_IXB resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit SybaseAvailability_IXB \-Log -LogEnable -RAW yes -TEDW yes
To allow the SybaseAvailability_IXB resource model to run in the profile,
″MyProfile″:
wdmeditprf -P MyProfile -edit SybaseAvailability_IXB \-enable
Appendix A. Resource model reference 59
Locks RM
Description
Monitors the locks in the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
LocksRM_IXB
Category
Monitoring for Sybase ASE
Indications
v NumberOfDeadlocks Threshold Violation
v NumberOfLockWaits Threshold Violation
v LockWaitTime Threshold Violation
v NumberOfAvailableLocks Threshold Violation
v LocksInUse Threshold Violation
Thresholds
v NumberOfDeadlocks_upperBound
v NumberOfDeadlocks_lowerBound
v NumberOfLockWaits_upperBound
v NumberOfLockWaits_lowerBound
v LockWaitTime_upperBound
v LockWaitTime_lowerBound
v NumberOfAvailableLocks_upperBound
v NumberOfAvailableLocks_lowerBound
v LocksInUse_upperBound
v LocksInUse_lowerBound
Parameters
v NumberOfDeadlocks_function
v NumberOfDeadlocks_relevant_time_interval
v NumberOfLockWaits_function
v NumberOfLockWaits_relevant_time_interval
v LockWaitTime_function
v LockWaitTime_relevant_time_interval
v NumberOfAvailableLocks_function
v NumberOfAvailableLocks_relevant_time_interval
v LocksInUse_function
v LocksInUse_relevant_time_interval
v stat_min_data_req
v stat_sum_group_size
v raw_retention_count
v sum_retention_count
v train_type
60 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Default cycle time
300 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX, Linux for X86 (for specific versions see the ″System
and software requirements″ appendix in the IBM Tivoli Monitoring for Databases:
Sybase ASE Installation and Setup Guide).
Target managed resource
SybaseASEServer_IXB
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
NumberOfDeadlocks
Threshold Violation
NumberOfDeadlocks_IXB Critical Yes 61
NumberOfLockWaits
Threshold Violation
NumberOfLockWaits_IXB Critical Yes 62
LockWaitTime Threshold
Violation
LockWaitTime_IXB Critical Yes 64
NumberOfAvailableLocks
Threshold Violation
NumberOfAvailableLocks_IXB Critical Yes 65
LocksInUse Threshold
Violation
LocksInUse_IXB Critical Yes 66
NumberOfDeadlocks Threshold Violation indication
This event indicates that the value for the NumberOfDeadlocks property violated
the limits defined by the NumberOfDeadlocks upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of deadlocks is not within the range allowed by the threshold
values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
Appendix A. Resource model reference 61
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberOfLockWaits Threshold Violation indication
This event indicates that the value for the NumLockWaits property violated the
limits defined by the NumberOfLockWaits upper and lower bounds.
62 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of locks in wait state is not within the range allowed by the
threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
Appendix A. Resource model reference 63
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
LockWaitTime Threshold Violation indication
This event indicates that the value for the LockWaitTime property violated the
limits defined by the LockWaitTime upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The lock wait time is not within the range allowed by the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
64 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberOfAvailableLocks Threshold Violation indication
This event indicates that the value for the AvailableLocks property violated the
limits defined by the NumberOfAvailableLocks upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of locks available is not within the range allowed by the
threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
Appendix A. Resource model reference 65
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
LocksInUse Threshold Violation indication
This event indicates that the value for the LocksInUse property violated the limits
defined by the LocksInUse upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of locks in use is not within the range allowed by the threshold
values.
This indication has the following attributes:
66 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Appendix A. Resource model reference 67
Setting Default value
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the
LocksRM_IXB resource model.:
NumberOfDeadlocks upper bound (NumberOfDeadlocks_upperBound)
The number of deadlocks since last cycle. This is the upper boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 10
NumberOfDeadlocks lower bound (NumberOfDeadlocks_lowerBound)
The number of deadlocks since last cycle. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
NumberOfLockWaits upper bound (NumberOfLockWaits_upperBound)
The number of locks in wait state. This is the upper boundary value for
this threshold. A value of 0 means this boundary will not be calculated. If
you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 10
NumberOfLockWaits lower bound (NumberOfLockWaits_lowerBound)
The number of locks in wait state. This is the lower boundary value for
this threshold. A value of 0 means this boundary will not be calculated. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
LockWaitTime upper bound (LockWaitTime_upperBound)
The wait time for a lock. Only the lock which has been waiting the longest
is reported. This is the upper boundary value for this threshold. A value of
68 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
0 means this boundary will not be calculated. If you want an upper
boundary of 0, then a very small value like 0.000001 must be used. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. If the threshold value entered is
outside of that range, then the resource model will be in an error state and
display a return code of 142.
Default: 10
LockWaitTime lower bound (LockWaitTime_lowerBound)
The wait time for a lock. Only the lock which has been waiting the longest
is reported. This is the lower boundary value for this threshold. A value of
0 means this boundary will not be calculated. If statistical thresholding is
enabled for this threshold, then the valid values for this threshold are
between 0 and 100. A value of 0 means that this boundary will not be
calculated. If you want a lower boundary of 0, then a very small value like
0.000001 must be used. If the threshold value entered is outside of that
range, then the resource model will be in an error state and display a
return code of 142.
Default: 0
NumberOfAvailableLocks upper bound
(NumberOfAvailableLocks_upperBound)
The number of available locks. This is the upper boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If you
want an upper boundary of 0, then a very small value like 0.000001 must
be used. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
NumberOfAvailableLocks lower bound
(NumberOfAvailableLocks_lowerBound)
The number of available locks. This is the lower boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 10
LocksInUse upper bound (LocksInUse_upperBound)
The number of locks in use. This is the upper boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If you
want an upper boundary of 0, then a very small value like 0.000001 must
be used. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 25
LocksInUse lower bound (LocksInUse_lowerBound)
The number of locks in use. This is the lower boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If
Appendix A. Resource model reference 69
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
Parameters
The following list shows the name (internal name), a short description, and the
default value for each parameter that you can set for the LocksRM_IXB resource
model:
Threshold NumberOfDeadlocks calculation method
(NumberOfDeadlocks_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberOfDeadlocks relevant time interval(s)
(NumberOfDeadlocks_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberOfLockWaits calculation method
(NumberOfLockWaits_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberOfLockWaits relevant time interval(s)
(NumberOfLockWaits_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold LockWaitTime calculation method (LockWaitTime_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold LockWaitTime relevant time interval(s)
(LockWaitTime_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberOfAvailableLocks calculation method
(NumberOfAvailableLocks_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberOfAvailableLocks relevant time interval(s)
(NumberOfAvailableLocks_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
70 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Threshold LocksInUse calculation method (LocksInUse_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold LocksInUse relevant time interval(s)
(LocksInUse_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Statistical Minimum Data Required (stat_min_data_req)
This parameter establishes the minimum number of relevant observations
required before threshold values are computed from observational data. An
observation is relevant if it is a member of a summary group that is active
when the threshold is computed. The default value is 20. The minumum value
is 20.
Summary Group Size (stat_sum_group_size)
This parameter establishes the number of raw observations to combine into
each summary group. Smaller values of this parameter give greater resolution
in time for thresholds sensitive to the time-of-day; larger values give greater
data compaction. If a number less than 20 is specified for this parameter, the
value will be considered equivalent to 20. The default value is 60.
Raw Group Retention Count (raw_retention_count)
This parameter establishes the number of raw observation groups to retain on
the endpoint for each metric instance. A raw observation group contains the
data used to compute a summary group and may be useful for tuning. Note
that this number may be different from the summary group retention count. A
value of zero stipulates retention of all data gathered. The default value is 24.
Summary Group Retention Count (sum_retention_count)
This parameter establishes the number of summary groups to retain on the
endpoint for each metric instance. Note that this setting may be different from
the raw group retention count. A value of zero stipulates retention of all data
summaries. Care should be taken to ensure enough summary groups are
retained to train the thresholds given the time sensitivity desired. The default
value is 170.
Training Methodology (train_type)
This parameter establishes the type of training desired for statistical thresholds.
’Initialization training’ stops additional training when the summary group
retention count threshold is reached, whereas ’Continuous training’ simply
replaces old data by new data at that same threshold. A value of zero for the
summary group retention count will have the same effect as continuous
training. The default value is ’Initialization training’.
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
SybaseASEServer Deadlocks NumberOfDeadlocks
Appendix A. Resource model reference 71
Managed resource Context Properties
SybaseASEServer Deadlocks instance *
SybaseASEServer LockWaits NumLockWaits
SybaseASEServer LockWaits instance *
SybaseASEServer LockWaitTimes DBName
SybaseASEServer LockWaitTimes LockWaitTime
SybaseASEServer LockWaitTimes instance *
SybaseASEServer AvailableLocks AvailableLocks
SybaseASEServer AvailableLocks instance *
SybaseASEServer LocksInUse LocksInUse
SybaseASEServer LocksInUse instance *
An asterisk (*) denotes a key property.
The following list describes the properties that the resource model logs:
NumberOfDeadlocks
Number of deadlocks that have occurred since last cycle.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
NumLockWaits
Number of locks in wait state.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
DBName
Database name.
LockWaitTime
Time a lock in wait state has been waiting. Only the lock which has been
waiting the longest is reported.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
AvailableLocks
Total number of locks available.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
LocksInUse
Total number of locks in use.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
72 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
610 Retrying (10) No instances found. The resource model will
continue to run.
One of the following:
v Unable to obtain data from Sybase
Adaptive Server. Ensure that the
Sybase Adaptive Server is
available and that the user id and
password specified are valid.
v None. This will happen if no
instances are present.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add LocksRM_IXB
To add the resource model, LocksRM_IXB, to the profile, ″MyProfile″:
wdmeditprf -P MyProfile -add LocksRM_IXB
To enable raw and Tivoli Data Warehouse data logging for the LocksRM_IXB
resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit LocksRM_IXB \-Log -LogEnable -RAW yes -TEDW yes
Appendix A. Resource model reference 73
To allow the LocksRM_IXB resource model to run in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit LocksRM_IXB \-enable
74 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Data Cache RM
Description
Monitors the data cache in the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
DataCacheRM_IXB
Category
Monitoring for Sybase ASE
Indications
v CacheHitRatio Threshold Violation
Thresholds
v CacheHitRatio_upperBound
v CacheHitRatio_lowerBound
Parameters
v CacheHitRatio_function
v CacheHitRatio_relevant_time_interval
v stat_min_data_req
v stat_sum_group_size
v raw_retention_count
v sum_retention_count
v train_type
Default cycle time
300 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX, Linux for X86 (for specific versions see the ″System
and software requirements″ appendix in the IBM Tivoli Monitoring for Databases:
Sybase ASE Installation and Setup Guide).
Target managed resource
SybaseASEServer_IXB
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
CacheHitRatio Threshold
Violation
CacheHitRatio_IXB Critical Yes 76
Appendix A. Resource model reference 75
CacheHitRatio Threshold Violation indication
This event indicates that the value for the HitRatio property violated the limits
defined by the CacheHitRatio upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The cache hit ratio is not within the range allowed by the threshold
values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
76 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the
DataCacheRM_IXB resource model.:
CacheHitRatio upper bound (CacheHitRatio_upperBound)
The ratio of cache hits as a percentage of retrieval attempts. Valid values
for this threshold are: 0.0 - 1.0. This is the upper boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If you
want an upper boundary of 0, then a very small value like 0.000001 must
be used. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
CacheHitRatio lower bound (CacheHitRatio_lowerBound)
The ratio of cache hits as a percentage of retrieval attempts. Valid values
for this threshold are: 0.0 - 1.0. This is the lower boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0.1
Parameters
The following list shows the name (internal name), a short description, and the
default value for each parameter that you can set for the DataCacheRM_IXB
resource model:
Threshold CacheHitRatio calculation method (CacheHitRatio_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Appendix A. Resource model reference 77
Threshold CacheHitRatio relevant time interval(s)
(CacheHitRatio_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Statistical Minimum Data Required (stat_min_data_req)
This parameter establishes the minimum number of relevant observations
required before threshold values are computed from observational data. An
observation is relevant if it is a member of a summary group that is active
when the threshold is computed. The default value is 20. The minumum value
is 20.
Summary Group Size (stat_sum_group_size)
This parameter establishes the number of raw observations to combine into
each summary group. Smaller values of this parameter give greater resolution
in time for thresholds sensitive to the time-of-day; larger values give greater
data compaction. If a number less than 20 is specified for this parameter, the
value will be considered equivalent to 20. The default value is 60.
Raw Group Retention Count (raw_retention_count)
This parameter establishes the number of raw observation groups to retain on
the endpoint for each metric instance. A raw observation group contains the
data used to compute a summary group and may be useful for tuning. Note
that this number may be different from the summary group retention count. A
value of zero stipulates retention of all data gathered. The default value is 24.
Summary Group Retention Count (sum_retention_count)
This parameter establishes the number of summary groups to retain on the
endpoint for each metric instance. Note that this setting may be different from
the raw group retention count. A value of zero stipulates retention of all data
summaries. Care should be taken to ensure enough summary groups are
retained to train the thresholds given the time sensitivity desired. The default
value is 170.
Training Methodology (train_type)
This parameter establishes the type of training desired for statistical thresholds.
’Initialization training’ stops additional training when the summary group
retention count threshold is reached, whereas ’Continuous training’ simply
replaces old data by new data at that same threshold. A value of zero for the
summary group retention count will have the same effect as continuous
training. The default value is ’Initialization training’.
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
SybaseASEServer DataCache CacheName *
SybaseASEServer DataCache HitRatio
An asterisk (*) denotes a key property.
78 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
The following list describes the properties that the resource model logs:
CacheName
Cache name. (key attribute)
HitRatio
Ratio of cache hits as a percentage of retrieval attempts for the cache.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
610 Retrying (10) No instances found. The resource model will
continue to run.
One of the following:
v Unable to obtain data from Sybase
Adaptive Server. Ensure that the
Sybase Adaptive Server is
available and that the user id and
password specified are valid.
v None. This will happen if no
instances are present.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add DataCacheRM_IXB
To add the resource model, DataCacheRM_IXB, to the profile, ″MyProfile″:
Appendix A. Resource model reference 79
wdmeditprf -P MyProfile -add DataCacheRM_IXB
To enable raw and Tivoli Data Warehouse data logging for the DataCacheRM_IXB
resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit DataCacheRM_IXB \-Log -LogEnable -RAW yes -TEDW yes
To allow the DataCacheRM_IXB resource model to run in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit DataCacheRM_IXB \-enable
80 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Space Usage RM
Description
Monitors the space used by each database in the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
SpaceUsageRM_IXB
Category
Monitoring for Sybase ASE
Indications
v DBAllocatedSizeInKB Threshold Violation
v DBUsedSizeInKB Threshold Violation
v DBIndexSizeInKB Threshold Violation
v DBUnallocatedSizeInKB Threshold Violation
v NumberTotalPages Threshold Violation
v NumberFreePages Threshold Violation
v NumberUsedPages Threshold Violation
v PercentFreeSpace Threshold Violation
Thresholds
v DBAllocatedSizeInKB_upperBound
v DBAllocatedSizeInKB_lowerBound
v DBUsedSizeInKB_upperBound
v DBUsedSizeInKB_lowerBound
v DBIndexSizeInKB_upperBound
v DBIndexSizeInKB_lowerBound
v DBUnallocatedSizeInKB_upperBound
v DBUnallocatedSizeInKB_lowerBound
v NumberTotalPages_upperBound
v NumberTotalPages_lowerBound
v NumberFreePages_upperBound
v NumberFreePages_lowerBound
v NumberUsedPages_upperBound
v NumberUsedPages_lowerBound
v PercentFreeSpace_upperBound
v PercentFreeSpace_lowerBound
Parameters
v DBAllocatedSizeInKB_function
v DBAllocatedSizeInKB_relevant_time_interval
v DBUsedSizeInKB_function
v DBUsedSizeInKB_relevant_time_interval
v DBIndexSizeInKB_function
v DBIndexSizeInKB_relevant_time_interval
v DBUnallocatedSizeInKB_function
Appendix A. Resource model reference 81
v DBUnallocatedSizeInKB_relevant_time_interval
v NumberTotalPages_function
v NumberTotalPages_relevant_time_interval
v NumberFreePages_function
v NumberFreePages_relevant_time_interval
v NumberUsedPages_function
v NumberUsedPages_relevant_time_interval
v PercentFreeSpace_function
v PercentFreeSpace_relevant_time_interval
v stat_min_data_req
v stat_sum_group_size
v raw_retention_count
v sum_retention_count
v train_type
Default cycle time
300 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX, Linux for X86 (for specific versions see the ″System
and software requirements″ appendix in the IBM Tivoli Monitoring for Databases:
Sybase ASE Installation and Setup Guide).
Target managed resource
SybaseASEServer_IXB
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
DBAllocatedSizeInKB
Threshold Violation
DBAllocatedSize_IXB Critical Yes 83
DBUsedSizeInKB Threshold
Violation
DBUsedSize_IXB Critical Yes 84
DBIndexSizeInKB Threshold
Violation
DBIndexSize_IXB Critical Yes 85
DBUnallocatedSizeInKB
Threshold Violation
DBUnallocatedSizeInKB_IXB Critical Yes 87
NumberTotalPages Threshold
Violation
NumberTotalPages_IXB Critical Yes 88
NumberFreePages Threshold
Violation
NumberFreePages_IXB Critical Yes 89
NumberUsedPages Threshold
Violation
NumberUsedPages_IXB Critical Yes 90
82 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Indication Generated event Default
severity
Clearing
events
Page
PercentFreeSpace Threshold
Violation
PercentFreeSpace_IXB Critical Yes 92
DBAllocatedSizeInKB Threshold Violation indication
This event indicates that the value for the AllocatedSizeInKB property violated the
limits defined by the DBAllocatedSizeInKB upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The allocated database size is not within the range allowed by the
threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Appendix A. Resource model reference 83
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
DBUsedSizeInKB Threshold Violation indication
This event indicates that the value for the UsedSizeInKB property violated the
limits defined by the DBUsedSizeInKB upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The size of the database being used is not within the range allowed by the
threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
84 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
DBIndexSizeInKB Threshold Violation indication
This event indicates that the value for the IndexSizeInKB property violated the
limits defined by the DBIndexSizeInKB upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The size of the index is not within the range allowed by the threshold
values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
Appendix A. Resource model reference 85
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
86 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
DBUnallocatedSizeInKB Threshold Violation indication
This event indicates that the value for the UnallocatedSizeInKB property violated
the limits defined by the DBUnallocatedSizeInKB upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The unallocated database size is not within the range allowed by the
threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
Appendix A. Resource model reference 87
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberTotalPages Threshold Violation indication
This event indicates that the value for the NumberOfTotalPages property violated
the limits defined by the NumberTotalPages upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The total number of pages for the segment is not within the range allowed
by the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
88 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberFreePages Threshold Violation indication
This event indicates that the value for the FreePages property violated the limits
defined by the NumberFreePages upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of free pages for the segment is not within the range allowed by
the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
Appendix A. Resource model reference 89
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberUsedPages Threshold Violation indication
This event indicates that the value for the UsedPages property violated the limits
defined by the NumberUsedPages upper and lower bounds.
90 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of used pages is not within the range allowed by the threshold
values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
Appendix A. Resource model reference 91
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
PercentFreeSpace Threshold Violation indication
This event indicates that the value for the PercentFreeSpace property violated the
limits defined by the PercentFreeSpace upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The percentage of free space for the segment is not within the range
allowed by the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
92 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the
SpaceUsageRM_IXB resource model.:
DBAllocatedSizeInKB upper bound (DBAllocatedSizeInKB_upperBound)
The size of the database which is allocated. This is the upper boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If you want an upper boundary of 0, then a very small value
like 0.000001 must be used. If statistical thresholding is enabled for this
threshold, then the valid values for this threshold are between 0 and 100. If
the threshold value entered is outside of that range, then the resource
model will be in an error state and display a return code of 142.
Default: 100
DBAllocatedSizeInKB lower bound (DBAllocatedSizeInKB_lowerBound)
The size of the database which is allocated. This is the lower boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. A value of 0 means
that this boundary will not be calculated. If you want a lower boundary of
0, then a very small value like 0.000001 must be used. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
Appendix A. Resource model reference 93
DBUsedSizeInKB upper bound (DBUsedSizeInKB_upperBound)
The size of the database which is used. This is the upper boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 102400
DBUsedSizeInKB lower bound (DBUsedSizeInKB_lowerBound)
The size of the database which is used. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
DBIndexSizeInKB upper bound (DBIndexSizeInKB_upperBound)
The size of the indexes in the database. This is the upper boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 51200
DBIndexSizeInKB lower bound (DBIndexSizeInKB_lowerBound)
The size of the indexes in the database. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
DBUnallocatedSizeInKB upper bound (DBUnallocatedSizeInKB_upperBound)
The size of the database which is unallocated. This is the upper boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If you want an upper boundary of 0, then a very small value
like 0.000001 must be used. If statistical thresholding is enabled for this
threshold, then the valid values for this threshold are between 0 and 100. If
the threshold value entered is outside of that range, then the resource
model will be in an error state and display a return code of 142.
Default: 10240
DBUnallocatedSizeInKB lower bound (DBUnallocatedSizeInKB_lowerBound)
The size of the database which is unallocated. This is the lower boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If statistical thresholding is enabled for this threshold, then the
94 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
valid values for this threshold are between 0 and 100. A value of 0 means
that this boundary will not be calculated. If you want a lower boundary of
0, then a very small value like 0.000001 must be used. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
NumberTotalPages upper bound (NumberTotalPages_upperBound)
The size of the segment. This is the upper boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If you
want an upper boundary of 0, then a very small value like 0.000001 must
be used. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 100000
NumberTotalPages lower bound (NumberTotalPages_lowerBound)
The size of the segment. This is the lower boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
NumberFreePages upper bound (NumberFreePages_upperBound)
The number of free pages for the segment. This is the upper boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If you want an upper boundary of 0, then a very small value
like 0.000001 must be used. If statistical thresholding is enabled for this
threshold, then the valid values for this threshold are between 0 and 100. If
the threshold value entered is outside of that range, then the resource
model will be in an error state and display a return code of 142.
Default: 0
NumberFreePages lower bound (NumberFreePages_lowerBound)
The number of free pages for the segment. This is the lower boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. A value of 0 means
that this boundary will not be calculated. If you want a lower boundary of
0, then a very small value like 0.000001 must be used. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 100
NumberUsedPages upper bound (NumberUsedPages_upperBound)
The number of used pages for the segment. This is the upper boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If you want an upper boundary of 0, then a very small value
like 0.000001 must be used. If statistical thresholding is enabled for this
threshold, then the valid values for this threshold are between 0 and 100. If
Appendix A. Resource model reference 95
the threshold value entered is outside of that range, then the resource
model will be in an error state and display a return code of 142.
Default: 100000
NumberUsedPages lower bound (NumberUsedPages_lowerBound)
The number of used pages for the segment. This is the lower boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. A value of 0 means
that this boundary will not be calculated. If you want a lower boundary of
0, then a very small value like 0.000001 must be used. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
PercentFreeSpace upper bound (PercentFreeSpace_upperBound)
The percentage of free space for the segment. Valid values for this
threshold are: 0.0 - 100.0. This is the upper boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If you
want an upper boundary of 0, then a very small value like 0.000001 must
be used. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
PercentFreeSpace lower bound (PercentFreeSpace_lowerBound)
The percentage of free space for the segment. Valid values for this
threshold are: 0.0 - 100.0. This is the lower boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 10
Parameters
The following list shows the name (internal name), a short description, and the
default value for each parameter that you can set for the SpaceUsageRM_IXB
resource model:
Threshold DBAllocatedSizeInKB calculation method
(DBAllocatedSizeInKB_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold DBAllocatedSizeInKB relevant time interval(s)
(DBAllocatedSizeInKB_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
96 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Threshold DBUsedSizeInKB calculation method (DBUsedSizeInKB_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold DBUsedSizeInKB relevant time interval(s)
(DBUsedSizeInKB_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold DBIndexSizeInKB calculation method (DBIndexSizeInKB_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold DBIndexSizeInKB relevant time interval(s)
(DBIndexSizeInKB_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold DBUnallocatedSizeInKB calculation method
(DBUnallocatedSizeInKB_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold DBUnallocatedSizeInKB relevant time interval(s)
(DBUnallocatedSizeInKB_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberTotalPages calculation method (NumberTotalPages_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberTotalPages relevant time interval(s)
(NumberTotalPages_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberFreePages calculation method (NumberFreePages_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberFreePages relevant time interval(s)
(NumberFreePages_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberUsedPages calculation method (NumberUsedPages_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Appendix A. Resource model reference 97
Threshold NumberUsedPages relevant time interval(s)
(NumberUsedPages_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold PercentFreeSpace calculation method (PercentFreeSpace_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold PercentFreeSpace relevant time interval(s)
(PercentFreeSpace_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Statistical Minimum Data Required (stat_min_data_req)
This parameter establishes the minimum number of relevant observations
required before threshold values are computed from observational data. An
observation is relevant if it is a member of a summary group that is active
when the threshold is computed. The default value is 20. The minumum value
is 20.
Summary Group Size (stat_sum_group_size)
This parameter establishes the number of raw observations to combine into
each summary group. Smaller values of this parameter give greater resolution
in time for thresholds sensitive to the time-of-day; larger values give greater
data compaction. If a number less than 20 is specified for this parameter, the
value will be considered equivalent to 20. The default value is 60.
Raw Group Retention Count (raw_retention_count)
This parameter establishes the number of raw observation groups to retain on
the endpoint for each metric instance. A raw observation group contains the
data used to compute a summary group and may be useful for tuning. Note
that this number may be different from the summary group retention count. A
value of zero stipulates retention of all data gathered. The default value is 24.
Summary Group Retention Count (sum_retention_count)
This parameter establishes the number of summary groups to retain on the
endpoint for each metric instance. Note that this setting may be different from
the raw group retention count. A value of zero stipulates retention of all data
summaries. Care should be taken to ensure enough summary groups are
retained to train the thresholds given the time sensitivity desired. The default
value is 170.
Training Methodology (train_type)
This parameter establishes the type of training desired for statistical thresholds.
’Initialization training’ stops additional training when the summary group
retention count threshold is reached, whereas ’Continuous training’ simply
replaces old data by new data at that same threshold. A value of zero for the
summary group retention count will have the same effect as continuous
training. The default value is ’Initialization training’.
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
98 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
SybaseASEServer DBUsage DBName *
SybaseASEServer DBUsage SizeInMB
SybaseASEServer DBUsage AllocatedSizeInKB
SybaseASEServer DBUsage UsedSizeInKB
SybaseASEServer DBUsage IndexSizeInKB
SybaseASEServer DBUsage UnallocatedSizeInKB
SybaseASEServer SegmentUsage DBName *
SybaseASEServer SegmentUsage SegName *
SybaseASEServer SegmentUsage NumberOfTotalPages
SybaseASEServer SegmentUsage FreePages
SybaseASEServer SegmentUsage UsedPages
SybaseASEServer SegmentUsage PercentFreeSpace
An asterisk (*) denotes a key property.
The following list describes the properties that the resource model logs:
DBName
Database name. (key attribute)
SizeInMB
Database size in megabytes.
AllocatedSizeInKB
Size of the database which is allocated in kilobytes.
UsedSizeInKB
Size of the database which is used in kilobytes.
IndexSizeInKB
Size of the indexes in the database in kilobytes.
UnallocatedSizeInKB
Size of the database which is unallocated in kilobytes.
DBName
Database name. (key attribute)
SegName
Segment name. (key attribute)
NumberOfTotalPages
Total segment size in number of pages.
FreePages
Number of free pages for the segment.
UsedPages
Number of used pages for the segment.
PercentFreeSpace
Percentage of free space for the segment.
Appendix A. Resource model reference 99
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
610 Retrying (10) No instances found. The resource model will
continue to run.
One of the following:
v Unable to obtain data from Sybase
Adaptive Server. Ensure that the
Sybase Adaptive Server is
available and that the user id and
password specified are valid.
v None. This will happen if no
instances are present.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add SpaceUsageRM_IXB
To add the resource model, SpaceUsageRM_IXB, to the profile, ″MyProfile″:
wdmeditprf -P MyProfile -add SpaceUsageRM_IXB
To enable raw and Tivoli Data Warehouse data logging for the SpaceUsageRM_IXB
resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit SpaceUsageRM_IXB \-Log -LogEnable -RAW yes -TEDW yes
100 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
To allow the SpaceUsageRM_IXB resource model to run in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit SpaceUsageRM_IXB \-enable
Appendix A. Resource model reference 101
Process Waits RM
Description
Monitors the processes waiting in the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
WaitsRM_IXB
Category
Monitoring for Sybase ASE
Indications
v NumberWaitingProcesses Threshold Violation
Thresholds
v NumberWaitingProcesses_upperBound
v NumberWaitingProcesses_lowerBound
Parameters
v NumberWaitingProcesses_function
v NumberWaitingProcesses_relevant_time_interval
v stat_min_data_req
v stat_sum_group_size
v raw_retention_count
v sum_retention_count
v train_type
Default cycle time
300 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX, Linux for X86 (for specific versions see the ″System
and software requirements″ appendix in the IBM Tivoli Monitoring for Databases:
Sybase ASE Installation and Setup Guide).
Target managed resource
SybaseASEServer_IXB
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
NumberWaitingProcesses
Threshold Violation
NumberWaitingProcesses_IXB Critical Yes 103
102 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
NumberWaitingProcesses Threshold Violation indication
This event indicates that the value for the NumWaitingProcesses property violated
the limits defined by the NumberWaitingProcesses upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of processes in waiting state is not within the range allowed by
the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
Appendix A. Resource model reference 103
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the
WaitsRM_IXB resource model.:
NumberWaitingProcesses upper bound (NumberWaitingProcesses_upperBound)
The number of processes in wait state. This is the upper boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 10
NumberWaitingProcesses lower bound (NumberWaitingProcesses_lowerBound)
The number of processes in wait state. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
Parameters
The following list shows the name (internal name), a short description, and the
default value for each parameter that you can set for the WaitsRM_IXB resource
model:
Threshold NumberWaitingProcesses calculation method
(NumberWaitingProcesses_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
104 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Threshold NumberWaitingProcesses relevant time interval(s)
(NumberWaitingProcesses_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Statistical Minimum Data Required (stat_min_data_req)
This parameter establishes the minimum number of relevant observations
required before threshold values are computed from observational data. An
observation is relevant if it is a member of a summary group that is active
when the threshold is computed. The default value is 20. The minumum value
is 20.
Summary Group Size (stat_sum_group_size)
This parameter establishes the number of raw observations to combine into
each summary group. Smaller values of this parameter give greater resolution
in time for thresholds sensitive to the time-of-day; larger values give greater
data compaction. If a number less than 20 is specified for this parameter, the
value will be considered equivalent to 20. The default value is 60.
Raw Group Retention Count (raw_retention_count)
This parameter establishes the number of raw observation groups to retain on
the endpoint for each metric instance. A raw observation group contains the
data used to compute a summary group and may be useful for tuning. Note
that this number may be different from the summary group retention count. A
value of zero stipulates retention of all data gathered. The default value is 24.
Summary Group Retention Count (sum_retention_count)
This parameter establishes the number of summary groups to retain on the
endpoint for each metric instance. Note that this setting may be different from
the raw group retention count. A value of zero stipulates retention of all data
summaries. Care should be taken to ensure enough summary groups are
retained to train the thresholds given the time sensitivity desired. The default
value is 170.
Training Methodology (train_type)
This parameter establishes the type of training desired for statistical thresholds.
’Initialization training’ stops additional training when the summary group
retention count threshold is reached, whereas ’Continuous training’ simply
replaces old data by new data at that same threshold. A value of zero for the
summary group retention count will have the same effect as continuous
training. The default value is ’Initialization training’.
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
SybaseASEServer Waits NumWaitingProcesses
SybaseASEServer Waits instance *
An asterisk (*) denotes a key property.
Appendix A. Resource model reference 105
The following list describes the properties that the resource model logs:
NumWaitingProcesses
Number of processes in waiting state.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
610 Retrying (10) No instances found. The resource model will
continue to run.
One of the following:
v Unable to obtain data from Sybase
Adaptive Server. Ensure that the
Sybase Adaptive Server is
available and that the user id and
password specified are valid.
v None. This will happen if no
instances are present.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add WaitsRM_IXB
106 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
To add the resource model, WaitsRM_IXB, to the profile, ″MyProfile″:
wdmeditprf -P MyProfile -add WaitsRM_IXB
To enable raw and Tivoli Data Warehouse data logging for the WaitsRM_IXB
resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit WaitsRM_IXB \-Log -LogEnable -RAW yes -TEDW yes
To allow the WaitsRM_IXB resource model to run in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit WaitsRM_IXB \-enable
Appendix A. Resource model reference 107
State RM
Description
Monitors the state of the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
StateRM_IXB
Category
Monitoring for Sybase ASE
Indications
v NumberDatabasesOpen Threshold Violation
v EngineIdleTimeInSeconds Threshold Violation
v NumberEngineConnections Threshold Violation
Thresholds
v NumberDatabasesOpen_upperBound
v NumberDatabasesOpen_lowerBound
v EngineIdleTimeInSeconds_upperBound
v EngineIdleTimeInSeconds_lowerBound
v NumberEngineConnections_upperBound
v NumberEngineConnections_lowerBound
Parameters
v NumberDatabasesOpen_function
v NumberDatabasesOpen_relevant_time_interval
v EngineIdleTimeInSeconds_function
v EngineIdleTimeInSeconds_relevant_time_interval
v NumberEngineConnections_function
v NumberEngineConnections_relevant_time_interval
v stat_min_data_req
v stat_sum_group_size
v raw_retention_count
v sum_retention_count
v train_type
Default cycle time
300 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX, Linux for X86 (for specific versions see the ″System
and software requirements″ appendix in the IBM Tivoli Monitoring for Databases:
Sybase ASE Installation and Setup Guide).
Target managed resource
SybaseASEServer_IXB
108 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
NumberDatabasesOpen
Threshold Violation
NumberDatabasesOpen_IXB Critical Yes 109
EngineIdleTimeInSeconds
Threshold Violation
EngineIdleTimeInSeconds_IXB Critical Yes 110
NumberEngineConnections
Threshold Violation
NumberEngineConnections_IXB Critical Yes 111
NumberDatabasesOpen Threshold Violation indication
This event indicates that the value for the NumDBsOpen property violated the
limits defined by the NumberDatabasesOpen upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of databases open is not within the range allowed by the
threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
Appendix A. Resource model reference 109
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
EngineIdleTimeInSeconds Threshold Violation indication
This event indicates that the value for the EngineIdleTimeInSeconds property
violated the limits defined by the EngineIdleTimeInSeconds upper and lower
bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The engine idle time is not within the range allowed by the threshold
values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
110 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberEngineConnections Threshold Violation indication
This event indicates that the value for the EngineConnections property violated the
limits defined by the NumberEngineConnections upper and lower bounds.
Appendix A. Resource model reference 111
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of connections to the engine is not within the range allowed by
the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
112 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the
StateRM_IXB resource model.:
NumberDatabasesOpen upper bound (NumberDatabasesOpen_upperBound)
The number of databases open. This is the upper boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If you
want an upper boundary of 0, then a very small value like 0.000001 must
be used. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 100
NumberDatabasesOpen lower bound (NumberDatabasesOpen_lowerBound)
The number of databases open. This is the lower boundary value for this
threshold. A value of 0 means this boundary will not be calculated. If
statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
EngineIdleTimeInSeconds upper bound
(EngineIdleTimeInSeconds_upperBound)
The engine idle time for the engine since last cycle. This is the upper
boundary value for this threshold. A value of 0 means this boundary will
not be calculated. If you want an upper boundary of 0, then a very small
value like 0.000001 must be used. If statistical thresholding is enabled for
this threshold, then the valid values for this threshold are between 0 and
100. If the threshold value entered is outside of that range, then the
resource model will be in an error state and display a return code of 142.
Default: 240
EngineIdleTimeInSeconds lower bound
(EngineIdleTimeInSeconds_lowerBound)
The engine idle time for the engine since last cycle. This is the lower
boundary value for this threshold. A value of 0 means this boundary will
not be calculated. If statistical thresholding is enabled for this threshold,
then the valid values for this threshold are between 0 and 100. A value of 0
means that this boundary will not be calculated. If you want a lower
Appendix A. Resource model reference 113
boundary of 0, then a very small value like 0.000001 must be used. If the
threshold value entered is outside of that range, then the resource model
will be in an error state and display a return code of 142.
Default: 20
NumberEngineConnections upper bound
(NumberEngineConnections_upperBound)
The number of connections to the engine. This is the upper boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If you want an upper boundary of 0, then a very small value
like 0.000001 must be used. If statistical thresholding is enabled for this
threshold, then the valid values for this threshold are between 0 and 100. If
the threshold value entered is outside of that range, then the resource
model will be in an error state and display a return code of 142.
Default: 100
NumberEngineConnections lower bound
(NumberEngineConnections_lowerBound)
The number of connections to the engine. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
Parameters
The following list shows the name (internal name), a short description, and the
default value for each parameter that you can set for the StateRM_IXB resource
model:
Threshold NumberDatabasesOpen calculation method
(NumberDatabasesOpen_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberDatabasesOpen relevant time interval(s)
(NumberDatabasesOpen_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold EngineIdleTimeInSeconds calculation method
(EngineIdleTimeInSeconds_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold EngineIdleTimeInSeconds relevant time interval(s)
(EngineIdleTimeInSeconds_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
114 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Threshold NumberEngineConnections calculation method
(NumberEngineConnections_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberEngineConnections relevant time interval(s)
(NumberEngineConnections_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Statistical Minimum Data Required (stat_min_data_req)
This parameter establishes the minimum number of relevant observations
required before threshold values are computed from observational data. An
observation is relevant if it is a member of a summary group that is active
when the threshold is computed. The default value is 20. The minumum value
is 20.
Summary Group Size (stat_sum_group_size)
This parameter establishes the number of raw observations to combine into
each summary group. Smaller values of this parameter give greater resolution
in time for thresholds sensitive to the time-of-day; larger values give greater
data compaction. If a number less than 20 is specified for this parameter, the
value will be considered equivalent to 20. The default value is 60.
Raw Group Retention Count (raw_retention_count)
This parameter establishes the number of raw observation groups to retain on
the endpoint for each metric instance. A raw observation group contains the
data used to compute a summary group and may be useful for tuning. Note
that this number may be different from the summary group retention count. A
value of zero stipulates retention of all data gathered. The default value is 24.
Summary Group Retention Count (sum_retention_count)
This parameter establishes the number of summary groups to retain on the
endpoint for each metric instance. Note that this setting may be different from
the raw group retention count. A value of zero stipulates retention of all data
summaries. Care should be taken to ensure enough summary groups are
retained to train the thresholds given the time sensitivity desired. The default
value is 170.
Training Methodology (train_type)
This parameter establishes the type of training desired for statistical thresholds.
’Initialization training’ stops additional training when the summary group
retention count threshold is reached, whereas ’Continuous training’ simply
replaces old data by new data at that same threshold. A value of zero for the
summary group retention count will have the same effect as continuous
training. The default value is ’Initialization training’.
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Appendix A. Resource model reference 115
Managed resource Context Properties
SybaseASEServer DBsOpen NumDBsOpen
SybaseASEServer DBsOpen instance *
SybaseASEServer EngineInfo EngineNumber *
SybaseASEServer EngineInfo EngineStatus
SybaseASEServer EngineInfo EngineIdleTimeInSeconds
SybaseASEServer EngineInfo EngineConnections
An asterisk (*) denotes a key property.
The following list describes the properties that the resource model logs:
NumDBsOpen
Number of databases open.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
EngineNumber
Engine number. (key attribute)
EngineStatus
Engine status.
EngineIdleTimeInSeconds
Engine idle time in seconds for the engine since last cycle.
EngineConnections
Number of engine connections for the engine.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
116 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
610 Retrying (10) No instances found. The resource model will
continue to run.
One of the following:
v Unable to obtain data from Sybase
Adaptive Server. Ensure that the
Sybase Adaptive Server is
available and that the user id and
password specified are valid.
v None. This will happen if no
instances are present.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add StateRM_IXB
To add the resource model, StateRM_IXB, to the profile, ″MyProfile″:
wdmeditprf -P MyProfile -add StateRM_IXB
To enable raw and Tivoli Data Warehouse data logging for the StateRM_IXB
resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit StateRM_IXB \-Log -LogEnable -RAW yes -TEDW yes
To allow the StateRM_IXB resource model to run in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit StateRM_IXB \-enable
Appendix A. Resource model reference 117
Traffic RM
Description
Monitors the traffic of the Sybase ASE server.
The following list contains the key characteristics of this resource model:
Internal name
TrafficRM_IXB
Category
Monitoring for Sybase ASE
Indications
v NumberServerConnections Threshold Violation
v NumberServerConnectionsAvailable Threshold Violation
v NumberPacketsSentPerSecond Threshold Violation
v NumberPacketsReceivedPerSecond Threshold Violation
Thresholds
v NumberServerConnections_upperBound
v NumberServerConnections_lowerBound
v NumberServerConnectionsAvailable_upperBound
v NumberServerConnectionsAvailable_lowerBound
v NumberPacketsSentPerSecond_upperBound
v NumberPacketsSentPerSecond_lowerBound
v NumberPacketsReceivedPerSecond_upperBound
v NumberPacketsReceivedPerSecond_lowerBound
Parameters
v NumberServerConnections_function
v NumberServerConnections_relevant_time_interval
v NumberServerConnectionsAvailable_function
v NumberServerConnectionsAvailable_relevant_time_interval
v NumberPacketsSentPerSecond_function
v NumberPacketsSentPerSecond_relevant_time_interval
v NumberPacketsReceivedPerSecond_function
v NumberPacketsReceivedPerSecond_relevant_time_interval
v stat_min_data_req
v stat_sum_group_size
v raw_retention_count
v sum_retention_count
v train_type
Default cycle time
300 seconds
Supported platforms
Windows, Solaris, HP-UX, AIX, Linux for X86 (for specific versions see the ″System
and software requirements″ appendix in the IBM Tivoli Monitoring for Databases:
Sybase ASE Installation and Setup Guide).
118 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Target managed resource
SybaseASEServer_IXB
Indications and events
The following table summarizes the indications for this resource model, the events
associated with the indications, the default severity of the events, whether the
resource model has clearing events, and where to find a detailed description of the
indication. The resource model generates an event based on the settings for the
indications. For information about customizing indications, refer to the
customization procedures in “Customizing indications and events” on page 29.
Indication Generated event Default
severity
Clearing
events
Page
NumberServerConnections
Threshold Violation
NumberServerConnections_IXB Critical Yes 119
NumberServerConnections \Available Threshold Violation
NumberServerConnectionsAvailable_\IXB
Critical Yes 120
NumberPacketsSent \PerSecond Threshold Violation
NumberPacketsSentPerSecond_\IXB
Critical Yes 122
NumberPacketsReceived \PerSecond Threshold Violation
NumberPacketsReceivedPerSecond_\IXB
Critical Yes 123
NumberServerConnections Threshold Violation indication
This event indicates that the value for the NumConnections property violated the
limits defined by the NumberServerConnections upper and lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of connections to the server is not within the range allowed by
the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
Appendix A. Resource model reference 119
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberServerConnectionsAvailable Threshold Violation
indication
This event indicates that the value for the NumConnectionsAvail property violated
the limits defined by the NumberServerConnectionsAvailable upper and lower
bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of available connections to the server is not within the range
allowed by the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
120 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Appendix A. Resource model reference 121
NumberPacketsSentPerSecond Threshold Violation indication
This event indicates that the value for the NumPacketsSentPerSecond property
violated the limits defined by the NumberPacketsSentPerSecond upper and lower
bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of packets sent per second is not within the range allowed by
the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
122 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
NumberPacketsReceivedPerSecond Threshold Violation
indication
This event indicates that the value for the NumPacketsReceivedPerSecond property
violated the limits defined by the NumberPacketsReceivedPerSecond upper and
lower bounds.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
The number of packets received per second is not within the range allowed
by the threshold values.
This indication has the following attributes:
application_instance
Name of the resource instance sending this indication.
application_class
Class of the resource instance sending this indication.
application_label
Label of the resource instance sending this indication.
application_version
Version of the resource instance sending this indication. This will always
be 1.0.
monitor_version
Version of the monitoring system for the resource instance sending this
indication.
application
Application name (key attribute).
threshold
Name of the threshold.
instance_name
Name of the specific instance which violated the threshold (key attribute).
Appendix A. Resource model reference 123
lower_bound
Lower bound of the acceptable range for this property. 0 indicates that
there is no lower bound.
upper_bound
Upper bound of the acceptable range for this property. 0 indicates that
there is no upper bound.
current_metric_value
Current value for the metric which violated a threshold.
calculation_method
This is the method by which this threshold violation was determined. If
the value is ″Fixed Thresholding″ then the current_metric_value is
compared against the lower and upper bound values to determine that a
threshold violation was encountered. If the value is ″Statistical
Thresholding″, then the value in the statistical_percentile slot is compared
against the lower and upper bounds to determine that a threshold
violation was encountered.
statistical_percentile
When ″Statistical Thresholding″ is enabled, this contains the percentile that
the current_metric_value combined with the current_index_value (if
applicable) is currently residing in. This value is compared against the
lower and upper bounds to determine that a threshold violation was
encountered. When statistical thresholding is not enabled, this value is set
to 0.
The following table describes the default settings for this indication.
Setting Default value
Send event to IBM Tivoli Enterprise Console Yes
Send event to IBM Tivoli Business Systems
Manager
Not applicable
Clearing events Yes
Occurrences 1
Holes 0
Thresholds
The following list shows the name, internal name (in parentheses), a short
description, and the default value for each threshold associated with the
TrafficRM_IXB resource model.:
NumberServerConnections upper bound
(NumberServerConnections_upperBound)
The number of connections to the server. This is the upper boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 100
124 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
NumberServerConnections lower bound
(NumberServerConnections_lowerBound)
The number of connections to the server. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Default: 0
NumberServerConnectionsAvailable upper bound
(NumberServerConnectionsAvailable_upperBound)
The number of connections available to the server. This is the upper
boundary value for this threshold. A value of 0 means this boundary will
not be calculated. If you want an upper boundary of 0, then a very small
value like 0.000001 must be used. If statistical thresholding is enabled for
this threshold, then the valid values for this threshold are between 0 and
100. If the threshold value entered is outside of that range, then the
resource model will be in an error state and display a return code of 142.
Default: 0
NumberServerConnectionsAvailable lower bound
(NumberServerConnectionsAvailable_lowerBound)
The number of connections available to the server. This is the lower
boundary value for this threshold. A value of 0 means this boundary will
not be calculated. If statistical thresholding is enabled for this threshold,
then the valid values for this threshold are between 0 and 100. A value of 0
means that this boundary will not be calculated. If you want a lower
boundary of 0, then a very small value like 0.000001 must be used. If the
threshold value entered is outside of that range, then the resource model
will be in an error state and display a return code of 142.
Default: 10
NumberPacketsSentPerSecond upper bound
(NumberPacketsSentPerSecond_upperBound)
The number of packets sent per second. This is the upper boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If you want an upper boundary of 0, then a very small value like 0.000001
must be used. If statistical thresholding is enabled for this threshold, then
the valid values for this threshold are between 0 and 100. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 10000
NumberPacketsSentPerSecond lower bound
(NumberPacketsSentPerSecond_lowerBound)
The number of packets sent per second. This is the lower boundary value
for this threshold. A value of 0 means this boundary will not be calculated.
If statistical thresholding is enabled for this threshold, then the valid values
for this threshold are between 0 and 100. A value of 0 means that this
boundary will not be calculated. If you want a lower boundary of 0, then a
very small value like 0.000001 must be used. If the threshold value entered
is outside of that range, then the resource model will be in an error state
and display a return code of 142.
Appendix A. Resource model reference 125
Default: 0
NumberPacketsReceivedPerSecond upper bound
(NumberPacketsReceivedPerSecond_upperBound)
The number of packets received per second. This is the upper boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If you want an upper boundary of 0, then a very small value
like 0.000001 must be used. If statistical thresholding is enabled for this
threshold, then the valid values for this threshold are between 0 and 100. If
the threshold value entered is outside of that range, then the resource
model will be in an error state and display a return code of 142.
Default: 10000
NumberPacketsReceivedPerSecond lower bound
(NumberPacketsReceivedPerSecond_lowerBound)
The number of packets received per second. This is the lower boundary
value for this threshold. A value of 0 means this boundary will not be
calculated. If statistical thresholding is enabled for this threshold, then the
valid values for this threshold are between 0 and 100. A value of 0 means
that this boundary will not be calculated. If you want a lower boundary of
0, then a very small value like 0.000001 must be used. If the threshold
value entered is outside of that range, then the resource model will be in
an error state and display a return code of 142.
Default: 0
Parameters
The following list shows the name (internal name), a short description, and the
default value for each parameter that you can set for the TrafficRM_IXB resource
model:
Threshold NumberServerConnections calculation method
(NumberServerConnections_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberServerConnections relevant time interval(s)
(NumberServerConnections_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberServerConnectionsAvailable calculation method
(NumberServerConnectionsAvailable_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberServerConnectionsAvailable relevant time interval(s)
(NumberServerConnectionsAvailable_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberPacketsSentPerSecond calculation method
(NumberPacketsSentPerSecond_function)
This is the method by which this threshold will be calculated. There are two
126 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberPacketsSentPerSecond relevant time interval(s)
(NumberPacketsSentPerSecond_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Threshold NumberPacketsReceivedPerSecond calculation method
(NumberPacketsReceivedPerSecond_function)
This is the method by which this threshold will be calculated. There are two
possible values: statistical thresholding and fixed thresholding. The default is
fixed thresholding. For a detailed description of these see page 9.
Threshold NumberPacketsReceivedPerSecond relevant time interval(s)
(NumberPacketsReceivedPerSecond_relevant_time_interval)
This parameter establishes the type of time sensitivity employed in computing
statistical thresholds. The default is no time sensitivity. For a detailed
explanation of these see page 14.
Statistical Minimum Data Required (stat_min_data_req)
This parameter establishes the minimum number of relevant observations
required before threshold values are computed from observational data. An
observation is relevant if it is a member of a summary group that is active
when the threshold is computed. The default value is 20. The minumum value
is 20.
Summary Group Size (stat_sum_group_size)
This parameter establishes the number of raw observations to combine into
each summary group. Smaller values of this parameter give greater resolution
in time for thresholds sensitive to the time-of-day; larger values give greater
data compaction. If a number less than 20 is specified for this parameter, the
value will be considered equivalent to 20. The default value is 60.
Raw Group Retention Count (raw_retention_count)
This parameter establishes the number of raw observation groups to retain on
the endpoint for each metric instance. A raw observation group contains the
data used to compute a summary group and may be useful for tuning. Note
that this number may be different from the summary group retention count. A
value of zero stipulates retention of all data gathered. The default value is 24.
Summary Group Retention Count (sum_retention_count)
This parameter establishes the number of summary groups to retain on the
endpoint for each metric instance. Note that this setting may be different from
the raw group retention count. A value of zero stipulates retention of all data
summaries. Care should be taken to ensure enough summary groups are
retained to train the thresholds given the time sensitivity desired. The default
value is 170.
Training Methodology (train_type)
This parameter establishes the type of training desired for statistical thresholds.
’Initialization training’ stops additional training when the summary group
retention count threshold is reached, whereas ’Continuous training’ simply
replaces old data by new data at that same threshold. A value of zero for the
summary group retention count will have the same effect as continuous
training. The default value is ’Initialization training’.
Appendix A. Resource model reference 127
Logging
You can log data for properties of the managed resources listed in the following
table. The table shows the context of each managed resource and the properties
that the resource model logs.
Note: If any one numeric metric within a context cannot be retrieved, the context
is not logged.
Managed resource Context Properties
SybaseASEServer Connections NumConnections
SybaseASEServer Connections instance *
SybaseASEServer ConnectionsAvailable NumConnectionsAvail
SybaseASEServer ConnectionsAvailable instance *
SybaseASEServer Packets NumPacketsSentPerSecond
SybaseASEServer Packets NumPacketsReceivedPerSecond
SybaseASEServer Packets instance *
An asterisk (*) denotes a key property.
The following list describes the properties that the resource model logs:
NumConnections
Number of connections.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
NumConnectionsAvail
Number of connections available.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
NumPacketsSentPerSecond
Number of packets sent per second.
NumPacketsReceivedPerSecond
Number of packets received per second.
instance
Key attribute for singleton data collection - the value will always be
″singleton″. (key attribute)
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the resource model takes for each return code.
Return
code
Displayed
code
Description Action
210 Failed (10) No instances found. This is not normal. There is
likely a problem with the application or
configuration of the monitor.
Check the application and the
monitoring settings.
128 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
220 Failed (20) The number of index values returned does not
match the number of metric instances collected.
This should not happen, index thresholding
requires that there be an index value for each
dependent value. The RM will be stopped.
Contact IBM Support.
341 Failed (141) Missing or invalid context variable. This happens
when the condition is recognised while collecting
and analyzing monitoring data.
Check the properties of the object.
610 Retrying (10) No instances found. The resource model will
continue to run.
One of the following:
v Unable to obtain data from Sybase
Adaptive Server. Ensure that the
Sybase Adaptive Server is
available and that the user id and
password specified are valid.
v None. This will happen if no
instances are present.
620 Retrying (20) Number of index values returned does not
match the number of metric instances collected.
This normally happens when there is no data
available for a metric because the resource does
not exist or is not being used. This is a normal,
transient condition. The resource model will
continue to run.
None. This can be normal.
941 Unable to
start (141)
Missing or invalid context variable. This happens
when the condition is recognised while
initializing data collection.
Check the properties of the object.
942 Unable to
start (142)
Invalid Statistical Threshold value. Values must
be between 0 and 100
Correct the Threshold values and
redistribute the Resource Model.
960 Unable to
start (160)
Resource Model distibuted to the wrong type of
object.
Distribute the RM to the correct
instance.
CLI example
You can use the following examples to modify the default values to meet your
needs, and you can omit any options for which you want to use the default values:
wdmeditprf -P MyProfile -add TrafficRM_IXB
To add the resource model, TrafficRM_IXB, to the profile, ″MyProfile″:
wdmeditprf -P MyProfile -add TrafficRM_IXB
To enable raw and Tivoli Data Warehouse data logging for the TrafficRM_IXB
resource model in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit TrafficRM_IXB \-Log -LogEnable -RAW yes -TEDW yes
To allow the TrafficRM_IXB resource model to run in the profile, ″MyProfile″:
wdmeditprf -P MyProfile -edit TrafficRM_IXB \-enable
Appendix A. Resource model reference 129
130 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix B. Task reference
A task is an action that can be routinely performed on selected managed resources
throughout the network. A task defines the executables to be run, the authorization
role required to execute the task, and the user or group name under which the task
executes.
IBM Tivoli Monitoring for Databases: Sybase ASE provides tasks in the following
task libraries:
Monitoring for Sybase ASE Utility Tasks task library
This task library contains the following tasks:
v Discover: Creates the objects that represent your resources.
v Create Sybase ASE Server Object: Registers the resource with the Tivoli
monitoring environment.
v TBSM Synchronization: Ensures that IBM Tivoli Business Systems
Manager and the Tivoli database have the same objects.
Monitoring for Sybase ASE Tasks task library
This task library contains the following tasks:
v Start Sybase Adaptive Server: Starts the Sybase Adaptive Server.
v Stop Sybase Adaptive Server: Issues the shutdown command to the
Sybase Adaptive Server.
v Start Sybase Backup Server: Starts the Sybase Backup Server.
v Stop Sybase Backup Server: Issues the shutdown command to the Sybase
Adaptive Server to shutdown the Sybase Backup Server. This task
requires that the Sybase Adaptive Server is available.
v Start Sybase Monitor Server: Starts the Sybase Monitor Server. In order
to start the Sybase Monitor Server, the Sybase Adaptive Server must
already be running. Make sure the Sybase Adaptive Server is started
before executing this task.
v Stop Sybase Monitor Server: Stops the Sybase Monitor Server.
v Check Sybase ASE Server Status: Checks to see whether the application
is in an operational state.
Other tasks
You can also run the following tasks:
v Configure Event Server: Configures the IBM Tivoli Enterprise Console
event server to receive and handle events.
v Modify Object Properties: Displays and modifies the properties of an
object.
v Manage Tivoli Logs: Lists, retrieves, or deletes trace logs.
You can invoke the tasks in various ways as noted in Table 3 on page 132.
© Copyright IBM Corp. 2004 131
Table 3. Ways to invoke tasks
Task name Page How to invoke the task
Task library Policy region Context
menu for the
managed
resource
CLI IBM Tivoli
Enterprise
Console
IBM Tivoli
Business
Systems
Manager
Configure Event
Server
148 yes yes no yes no no
Discover 157 yes yes yes yes no no
TBSM
Synchronization
167 yes no no yes no no
Check Sybase
ASE Server
Status
146 yes yes yes yes no yes
Create Sybase
ASE Server
Object
153 yes yes no yes no no
Modify Object
Properties
164 no no no yes no no
Manage Tivoli
Logs
162 no no yes yes no no
Start Sybase
Adaptive Server
134 yes no yes yes no yes
Stop Sybase
Adaptive Server
136 yes no yes yes no yes
Start Sybase
Backup Server
138 yes no yes yes no yes
Stop Sybase
Backup Server
140 yes no yes yes no yes
Start Sybase
Monitor Server
142 yes no yes yes no yes
Stop Sybase
Monitor Server
144 yes no yes yes no yes
See the Tivoli Management Framework documentation for more information about
tasks.
You can also set up the Start, Stop, and Check Status tasks to run when a resource
model sends an event indicating that a resource is not running as desired. See
“Specifying a task to run automatically” on page 27 for information about how to
set up resource models to run tasks automatically.
This appendix provides the following information for each IBM Tivoli Monitoring
for Databases: Sybase ASE task:
Description
Brief description of the task
Authorization roles
IBM Tivoli Monitoring for Databases: Sybase ASE and Tivoli authorization
roles required to run the task
132 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Target managed resource
Tivoli managed resource to which the task is distributed
Parameters
Description of the parameters that can be set for the task in the task
window or in the command-line interface
CLI example
Sample wruntask command that invokes the task
Return codes
Information that the task returns such as status or availability
Usage notes
Additional notes relevant to using the task
Appendix B. Task reference 133
Start Sybase Adaptive Server
Description
This task will start the Sybase Adaptive Server.
This task starts the following processes or services:
v Sybase Adaptive Server
Authorization roles
SybaseMon_IXB_senior, SybaseMon_IXB_super
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the wruntask
command
Description
Not applicable –t ″Start Sybase Adaptive Server″ Name of the task to run: Start Sybase
Adaptive Server
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task
is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the
SybaseASEServer_IXB
CLI example
The following example starts the following processes or services:
v Sybase Adaptive Server
wruntask -t "Start Sybase Adaptive Server" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
134 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
0 IXB8000I Task Complete. None.
— IXB8001E Task Failed. See the additional error messages to
determine the exact cause of the
error.
-1 IXB8002E The task cannot run on this platform. Run the task on a platform that
provides support for this task.
1 None. General Error executing task See other messages to determine
specific problem.
2 None. The application component is already running. It
will not be started.
None.
— IXB0003I Starting Sybase Adaptive Server. None.
— IXB0004E The Sybase Adaptive Server is already running. Stop the Sybase Adaptive Server.
— IXB0017E Error attempting to start Sybase Adaptive Server. Try to start the Sybase Adaptive
Server manually on the endpoint
system to see more specific errors.
Also check to make sure the
Operating system user id provided
has access to the Sybase installation
directory.
Usage notes
This task can be run from the Tivoli desktop task library, IBM Tivoli Monitoring,
and IBM Tivoli Business Systems Manager.
Appendix B. Task reference 135
Stop Sybase Adaptive Server
Description
This task will issue the shutdown command to the Sybase Adaptive Server.
This task stops the following processes or services:
v Sybase Adaptive Server
Authorization roles
SybaseMon_IXB_senior, SybaseMon_IXB_super
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the wruntask
command
Description
Not applicable –t ″Stop Sybase Adaptive Server″ Name of the task to run: Stop Sybase
Adaptive Server
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task
is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the
SybaseASEServer_IXB
CLI example
The following example stops the following processes or services:
v Sybase Adaptive Server
wruntask -t "Stop Sybase Adaptive Server" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
136 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
0 IXB8000I Task Complete. None.
— IXB8001E Task Failed. See the additional error messages to
determine the exact cause of the
error.
-1 IXB8002E The task cannot run on this platform. Run the task on a platform that
provides support for this task.
1 None. General Error executing task See other messages to determine
specific problem.
3 None. The application component is not running. It will
not be stopped.
None.
— IXB0007I Stopping Sybase Adaptive Server. None.
— IXB0008E Sybase Adaptive Server is not running. Start the Sybase Adaptive Server.
— IXB0016E Cannot connect to the Sybase Adaptive Server. Verify the user id and password
which are used to communicate with
the server are correct.
Usage notes
This task can be run from the Tivoli desktop task library, IBM Tivoli Monitoring,
and IBM Tivoli Business Systems Manager.
Appendix B. Task reference 137
Start Sybase Backup Server
Description
This task will start the Sybase Backup Server.
This task starts the following processes or services:
v Sybase Backup Server
Authorization roles
SybaseMon_IXB_senior, SybaseMon_IXB_super
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the wruntask
command
Description
Not applicable –t ″Start Sybase Backup Server″ Name of the task to run: Start Sybase
Backup Server
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task
is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the
SybaseASEServer_IXB
CLI example
The following example starts the following processes or services:
v Sybase Backup Server
wruntask -t "Start Sybase Backup Server" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
138 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
0 IXB8000I Task Complete. None.
— IXB8001E Task Failed. See the additional error messages to
determine the exact cause of the
error.
-1 IXB8002E The task cannot run on this platform. Run the task on a platform that
provides support for this task.
1 None. General Error executing task See other messages to determine
specific problem.
2 None. The application component is already running. It
will not be started.
None.
4 None. Warning. See other messages for specific reasons. None.
— IXB0001I Starting Sybase Backup Server. None.
— IXB0002E The Sybase Backup Server is already running. Stop the Sybase Backup Server.
— IXB0014W The Sybase Backup Server is undefined. Use the Discovery task or the Modify
Object Properties task to define the
Sybase Backup Server.
— IXB0018E Error attempting to start Sybase Backup Server. Try to start the Sybase Backup Server
manually on the endpoint system to
see more specific errors. Also check
to make sure the Operating system
user id provided has access to the
Sybase installation directory.
Usage notes
This task can be run from the Tivoli desktop task library, IBM Tivoli Monitoring,
and IBM Tivoli Business Systems Manager.
Appendix B. Task reference 139
Stop Sybase Backup Server
Description
This task will issue the shutdown command to the Sybase Adaptive Server to
shutdown the Sybase Backup Server. This task requires that the Sybase Adaptive
Server be available.
This task stops the following processes or services:
v Sybase Backup Server
Authorization roles
SybaseMon_IXB_senior, SybaseMon_IXB_super
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the wruntask
command
Description
Not applicable –t ″Stop Sybase Backup Server″ Name of the task to run: Stop Sybase
Backup Server
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task
is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the
SybaseASEServer_IXB
CLI example
The following example stops the following processes or services:
v Sybase Backup Server
wruntask -t "Stop Sybase Backup Server" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
140 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
0 IXB8000I Task Complete. None.
— IXB8001E Task Failed. See the additional error messages to
determine the exact cause of the
error.
-1 IXB8002E The task cannot run on this platform. Run the task on a platform that
provides support for this task.
1 None. General Error executing task See other messages to determine
specific problem.
3 None. The application component is not running. It will
not be stopped.
None.
4 None. Warning. See other messages for specific reasons. None.
5 None. There is a missing prerequisite component. The
application component cannot be started.
Start the appropriate component. See
other messages for specific details.
— IXB0005I Stopping Sybase Backup Server. None.
— IXB0006E Sybase Backup Server is not running. Start the Sybase Backup Server.
— IXB0009E The Sybase Adaptive Server needs to be started
first.
Start the Sybase Adaptive Server.
Usage notes
This task can be run from the Tivoli desktop task library, IBM Tivoli Monitoring,
and IBM Tivoli Business Systems Manager.
Appendix B. Task reference 141
Start Sybase Monitor Server
Description
This task will start the Sybase Monitor Server. In order to start the Sybase Monitor
Server, the Sybase Adaptive Server must already be running. Make sure the Sybase
Adaptive Server is started before executing this task.
This task starts the following processes or services:
v Sybase Monitor Server
Authorization roles
SybaseMon_IXB_senior, SybaseMon_IXB_super
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the wruntask
command
Description
Not applicable –t ″Start Sybase Monitor Server″ Name of the task to run: Start Sybase
Monitor Server
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task
is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the
SybaseASEServer_IXB
CLI example
The following example starts the following processes or services:
v Sybase Monitor Server
wruntask -t "Start Sybase Monitor Server" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
142 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
0 IXB8000I Task Complete. None.
— IXB8001E Task Failed. See the additional error messages to
determine the exact cause of the
error.
-1 IXB8002E The task cannot run on this platform. Run the task on a platform that
provides support for this task.
1 None. General Error executing task See other messages to determine
specific problem.
2 None. The application component is already running. It
will not be started.
None.
4 None. Warning. See other messages for specific reasons. None.
5 None. There is a missing prerequisite component. The
application component cannot be started.
Start the appropriate component. See
other messages for specific details.
— IXB0010I Starting Sybase Monitor Server. None.
— IXB0011E The Sybase Monitor Server is already running. Stop the Sybase Monitor Server.
— IXB0015W The Sybase Monitor Server is undefined. Use the Discovery task or the Modify
Object Properties task to define the
Sybase Monitor Server.
— IXB0019E Error attempting to start Sybase Monitor Server. Try to start the Sybase Monitor
Server manually on the endpoint
system to see more specific errors.
Also check to make sure the
Operating system user id provided
has access to the Sybase installation
directory.
Usage notes
This task can be run from the Tivoli desktop task library, IBM Tivoli Monitoring,
and IBM Tivoli Business Systems Manager.
Appendix B. Task reference 143
Stop Sybase Monitor Server
Description
This task will stop the Sybase Monitor Server.
This task stops the following processes or services:
v Sybase Monitor Server
Authorization roles
SybaseMon_IXB_senior, SybaseMon_IXB_super
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the wruntask
command
Description
Not applicable –t ″Stop Sybase Monitor Server″ Name of the task to run: Stop Sybase
Monitor Server
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task
is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the
SybaseASEServer_IXB
CLI example
The following example stops the following processes or services:
v Sybase Monitor Server
wruntask -t "Stop Sybase Monitor Server" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
144 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
0 IXB8000I Task Complete. None.
— IXB8001E Task Failed. See the additional error messages to
determine the exact cause of the
error.
-1 IXB8002E The task cannot run on this platform. Run the task on a platform that
provides support for this task.
1 None. General Error executing task See other messages to determine
specific problem.
3 None. The application component is not running. It will
not be stopped.
None.
4 None. Warning. See other messages for specific reasons. None.
— IXB0012I Stopping Sybase Monitor Server. None.
— IXB0013E Sybase Monitor Server is not running. Start the Sybase Monitor Server.
Usage notes
This task can be run from the Tivoli desktop task library, IBM Tivoli Monitoring,
and IBM Tivoli Business Systems Manager.
Appendix B. Task reference 145
Check Sybase ASE Server Status
Description
Checks to determine whether Sybase ASE Server is currently in an operational
state. You can use this task to verify your configuration. You can also obtain the
following information using this task:
v Whether the Tivoli configuration is valid as indicated by the task flowing from
the Tivoli desktop to the endpoint and back to the Tivoli desktop (Tivoli
management region).
v Status of Sybase ASE as indicated when the information that the Availability
resource model sends to IBM Tivoli Enterprise Console and IBM Tivoli Business
Systems Manager is correct.
Authorization roles
v SybaseMon_IXB_senior
v SybaseMon_IXB_super
v SybaseMon_IXB_admin
v SybaseMon_IXB_user
Target managed resource
SybaseASEServer_IXB
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable –t ″Check Sybase ASE Server Status″ Name of the task to run: Check Sybase ASE
Server Status
Not applicable –l ″Monitoring for Sybase ASE Utility
Tasks″
Name of the task library where the task is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_\IXB@example_ep″
@SybaseASEServer_IXB:followed by the name of
the instance
CLI example
The following example checks the status of Sybase ASE Server:
wruntask -t "Check Sybase ASE Server Status" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep"
146 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 IXB8900I Determining the status of object: object None.
0 IXB8901I The object is up. None.
0 IXB8902I The object is down. None.
0 IXB8903I Object object is in warning state. None.
1 IXB8904E Error determining the status of object: object If the problem persists, contact IBM
Software Support.
Usage notes
None.
Appendix B. Task reference 147
Configure Event Server
Description
Configures the IBM Tivoli Enterprise Console event server to include event classes
and rules so the IBM Tivoli Enterprise Console server is set up to accept IBM
Tivoli Monitoring for Databases: Sybase ASE events and run IBM Tivoli Monitoring
for Databases: Sybase ASE rules.
Authorization roles
senior
Target managed resource
Managed Node where IBM Tivoli Enterprise Console server is installed
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line
parameters for the
wruntask command
Description
Not applicable -t ″Configure Event
Server″
Name of the task to run: Configure Event Server
Not applicable -l ″IBM Tivoli
Monitoring Component
Services Tasks″
Name of the task library where this task is located
Event Server node to
configure
-h ″tec_managed_node ″ Managed node where the Event Server is installed:
Command line: If you run the task against a managed node that
is not an IBM Tivoli Enterprise Console server, the task starts to
run, then gives you an error. This is only possible from the
command line, where the target node is a free-form argument.
Tivoli desktop: Select the managed node that is filled in by
default as the managed node hosting the Event Server. Any
managed nodes that are not IBM Tivoli Enterprise Console servers
are not presented as options.
Not applicable -m ″timeout_in_seconds″ Amount of time in seconds that the task has to complete. If the
task does not complete in less than the specified amount of time,
an error is returned to whoever invoked the task saying that the
timeout has expired. However, the task continues to run in the
background until it completes. If a value of 0 is specified for the
timeout, the timeout is disabled and the system waits indefinitely
for the task to complete.
148 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Field name for the
Tivoli desktop
Command-line
parameters for the
wruntask command
Description
Rule Base
Configuration
(Required)
v Create New Rule
Base
v Create New Rule
Base From Existing
v Update Current
Rule Base
-a ″CREATE|CLONE|UPDATE″
Use the Tivoli desktop option or the parameter for the command
line that is in parentheses:
v Create New Rule Base (CREATE) creates a new rule base that
has not been initialized with an existing rule base. You must
specify the new rule base name and the path to the new rule
base in the fields or parameters for these names.
v Create New Rule Base From Existing (CLONE) creates a new
rule based on an existing rule base (also called cloning). If you
have not previously created a rule base, use ″Default.″ You
must specify the new rule base name and the path to the new
rule base in the fields or parameters for these names
v Update Current Rule Base (UPDATE) updates an existing rule
base.
Rule Bases -a ″″ The rule base names in this field depend on the rule base
configuration:
v If creating a new rule base not based on an existing rule base,
this field is not active. If no value is needed, specify ″″.
v If creating a new rule base from an existing rule base, this field
contains the names of existing rule bases.
v If updating a current rule base, this field contains the names of
rule bases that can be updated.
New Rule Base
Name
-a ″New_Rule_Base_ \Name″
Name of the rule base to be created.
Use a new name that is not currently in use. If you type the name
of an existing rule base, this task issues a message and does not
update the existing rule base.
If you are updating a rule base through the command line, use
the following command:
-a "Rule_Base_Name"
New Rule Base Path -a ″New_Rule_Base_Path″ Pathname on the event server managed node where the files
related to this rule base are stored
When you run the task on the Tivoli desktop, enter the full path
for the new rule base. The default path is $BINDIR/TME/TEC.
The task appends the name of the new rule base to this field
value to determine the complete path of the new rule base.
Event Forwarding:
Host Name
-a ″″ Not applicable to IBM Tivoli Monitoring for Databases: Sybase
ASE
Event Forwarding:
Port
-a ″″ Not applicable to IBM Tivoli Monitoring for Databases: Sybase
ASE
Forward to TBSM -a ″ON|OFF″ Forward events to IBM Tivoli Business Systems Manager. If the
value is set to ON, events are forwarded to IBM Tivoli Business
Systems Manager. If the value is OFF, events are not forwarded to
IBM Tivoli Business Systems Manager.
Appendix B. Task reference 149
Field name for the
Tivoli desktop
Command-line
parameters for the
wruntask command
Description
Rule Base Activation -a ″LOADONLY|RESTART|″″″
Use the Tivoli desktop option or the parameter for the command
line that is in parentheses:
v Do Not Activate (″″) creates or updates the rule base, but does
not upload the rule base to the event server. Use this option to
review rule base changes before you activate them.
v Load Rule Base Only (LOADONLY) creates or updates the
rule base and uploads it to the event server. The new rule base
is active when the event server is restarted.
v Load Rule Base and Restart Server (RESTART) creates or
updates the rule base, uploads it to the event server, and
restarts the event server.
Product to configure
(Required)
-a ″file_name″ Filename for the product you want to configure. For IBM Tivoli
Monitoring for Databases: Sybase ASE this is:
SybaseMon.pac
Note: You must supply an argument for each -a parameter. If you are not using
one of the properties, you must supply it as a null (″″) property.
CLI example
The following example configures the IBM Tivoli Enterprise Console event server
for IBM Tivoli Monitoring for Databases: Sybase ASE for the managed node named
Tec_Managed_Node in less than 15 minutes. It creates ″NewRule″ rule base by
making a copy of the existing default rule base and updating the copy with the
IBM Tivoli Monitoring for Databases: Sybase ASE event classes and rules. The path
for the new rule base is c:/Tivoli/bin/w32-ix86/TME/TEC. Events are not
forwarded to IBM Tivoli Business Systems Manager. After the rule base is created
and uploaded to the event server the event server restarts.
wruntask -t "Configure Event Server" \
-l "IBM Tivoli Monitoring Component Services Tasks" \
-h "@ManagedNode:Tec_Managed_Node" \
-m "900" \
-a "CLONE" \
-a "Default" \
-a "NewRule" \
-a "c:/Tivoli/bin/w32-ix86/TME/TEC" \
-a "" \
-a "" \
-a "OFF \
-a "RESTART" \
-a "SybaseMon.pac"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code. The only action the task takes is
to exit.
150 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return
code
Displayed
code
Description Action
1 AMG8154E The task needs to include the Tmw2k.baroc file
supplied by IBM Tivoli Monitoring, but this file
was missing. The likely cause is that IBM Tivoli
Monitoring was not installed.
Re-install IBM Tivoli Monitoring
1 AMG8039E The listed baroc file specified by IBM Tivoli
Monitoring for Databases: Sybase ASE for
inclusion in its rulebase was not found.
Re-install IBM Tivoli Monitoring for
Databases: Sybase ASE.
1 AMG8003E The listed rules file specified by IBM Tivoli
Monitoring for Databases: Sybase ASE for
inclusion in its rulebase was not found.
Re-install IBM Tivoli Monitoring for
Databases: Sybase ASE.
1 AMG8004E The listed script file specified by the IBM Tivoli
Monitoring for Databases: Sybase ASE to be
installed on the IBM Tivoli Enterprise Console
server was not found.
Re-install IBM Tivoli Monitoring for
Databases: Sybase ASE.
1 AMG8102E The new rulebase you asked to create with the
given name already exists.
Specify another rulebase name
1 AMG8006E The rulebase you asked to clone does not exist. Specify an existing rulebase.
1 AMG8005E The rulebase you asked to update does not exist. Specify an existing rulebase.
1 AMG8103E You specified an invalid option to the Configure
Event Server task. The valid options are
CREATE, CLONE, and UPDATE.
Specify a valid system.
1 AMG8104E The path you specified to locate the rule base in
is invalid. Components of the path may not
exist, or the directory permissions may not allow
the task to write there.
Specify a valid rulebase path.
1 AMG8008E The task was unable to create the rulebase
directory specified by the user.
None.
1 AMG8139E The directory specified to contain the new
rulebase already exists. This can cause IBM
Tivoli Enterprise Console errors if the directory
contents are not consistent with the new rulebase
being created.
Remove the directory or choose a
different location and run the task
again.
1 AMG8012E Compilation of the rulebase failed. There are
most likely syntax errors in the baroc files, or the
baroc files depend on prerequisite classes that
were not included.
None.
1 AMG8014E Creation of the new rulebase in the IBM Tivoli
Enterprise Console server failed.
None.
1 AMG8016E Copying the existing rulebase into new rulebase
failed.
None.
1 AMG8018E Importing the given class into the rulebase
failed. There are most likely syntax errors in the
baroc file, or the baroc file depends on
prerequisite classes that were not included.
None.
1 AMG8106E Importing the given ruleset into the rulebase
failed.
None.
1 AMG8021E Creation of specified event source in the IBM
Tivoli Enterprise Console server failed.
None.
1 AMG8024E Event source already exists and could not be
deleted.
None.
Appendix B. Task reference 151
Return
code
Displayed
code
Description Action
1 AMG8112E The IBM Tivoli Enterprise Console event
forwarding that you requested did not supply
the necessary hostname to which events should
be forwarded.
None.
1 AMG8026E Loading the new rulebase into the IBM Tivoli
Enterprise Console server failed.
None.
1 AMG8037E The rulebase directory that is needed does not
exist.
None.
1 AMG8033E The IBM Tivoli Enterprise Console server failed
to restart.
None.
1 AMG8035E The task was run on a node which is not the
IBM Tivoli Enterprise Console server.
None.
1 AMG8038E The arguments passed to the task are incorrect. None.
1 AMG8040I The task completed successfully. None.
Usage notes
Because the scope of the Discover task is a Tivoli management region, use
managed nodes and endpoints that are within the same Tivoli management region.
Configure the Event Server by adding the event classes and rules related to this
application. You can configure only one Tivoli Enterprise Console event server for
each Tivoli management region. When you have interconnected Tivoli management
regions, run the Configure Event Server task against each Tivoli management
region that contains a Tivoli Enterprise Console event server.
152 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Create Sybase ASE Server Object
Description
Creates an object of the identified object type in the Tivoli database.
Use this task only when Discovery does not work. This task does not check for the
existence of Sybase ASE or the correctness of any entered data, does not send an
event to IBM Tivoli Enterprise Console for IBM Tivoli Business Systems Manager,
does not allow you to automatically distribute the resource models, and does not
add the object to the instances profile manager.
Authorization roles
SybaseMon_IXB_senior
Target managed resource
Managed node on which the object is to be created
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable –t ″Create Sybase ASE Server Object″ Name of the task to run: Create Sybase ASE
Server Object
Not applicable –l ″Monitoring for Sybase ASE Utility
Tasks″
Name of the task library where the task is located
Object Host –h ″@ManagedNode:node_name″ Managed node on which the task will be run and
the object will be created
Not applicable –a ″ENDPOINT_NAME″ Tag identifying the next variable as the name of
the endpoint
Endpoint List –a ″@Endpoint:epName1″ The name of the endpoint
Sybase identifier -a ″AP_\SYBASE_IDENTIFIER″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This identifies the
Sybase ASE Server. Choose a unique value for
each Sybase ASE Server to be monitored. This
value can only contain alphanumeric values.
Appendix B. Task reference 153
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Sybase installation
path
-a ″AP_\SYBASE_INSTALL_PATH″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the installation
path of Sybase. This path should contain the
trailing delimitier, for example ’C:\sybase\’ or
’/opt/sybase/’
Operating system
user id
-a ″AP_\SYBASE_OS_USER″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the operating
system user id to be used to start and interact
with Sybase.
Sybase user id -a ″AP_\SYBASE_USER″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is a Sybase user ID
used to log into Sybase which has been granted
the mon_role.
Sybase password -a ″AP_\SYBASE_PASSWORD″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the password
for the user ID specified. This value must not be
NULL or an empty string.
Sybase Server name -a ″AP_\SYBASE_SERVER_NAME″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Adaptive Server name.
Sybase Backup
Server name
-a ″AP_\SYBASE_BACKUP_SERVER_NAME″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Backup Server name.
Sybase Monitor
Server name
-a ″_AP_\SYBASE_MONITOR_SERVER_NAME″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Monitor Server name.
154 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Sybase Adaptive
Server log file name
-a ″AP_\LogMonitorLogname″-a ″value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Adaptive Server log file name.
CLI example
The following example runs the ″Create ... Object″ task on the ″MyManagedNode″
managed node, searches the ″example_ep″ endpoint, and puts the objects that it
creates on the ″OtherManagedNode″ managed node. The task is set to run on each
endpoint for a maximum of 1 minute. The task is not set up to distribute the
profile or notify IBM Tivoli Business Systems Manager that a resource was
discovered. The events are to be sent to the default IBM Tivoli Enterprise Console
server for the policy region at port number 5529. The task has 10 minutes to
complete.
The following variables and their values (shown in parentheses) are set up:
v SybaseASEServer_AP_SYBASE_IDENTIFIER (server1)
v SybaseASEServer_AP_SYBASE_INSTALL_PATH (/opt/sybase/)
v SybaseASEServer_AP_SYBASE_OS_USER (sybase)
v SybaseASEServer_AP_SYBASE_USER (sa)
v SybaseASEServer_AP_SYBASE_PASSWORD (secret)
v SybaseASEServer_AP_SYBASE_SERVER_NAME (server1)
v SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME (server1_BS)
v SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME (server1_MS)
v SybaseASEServer_AP_LogMonitorLogname (/opt/sybase/ASE-12_5/install/server1.log)
wruntask –t "Create Sybase ASE Server Object" \
–l "Monitoring for Sybase ASE Utility Tasks" \
–h "@ManagedNode:MyManagedNode" \
–a "ENDPOINT_NAME" \
–a "example_ep" \
–a "SybaseASEServer_AP_SYBASE_IDENTIFIER" \
–a "server1" \
–a "SybaseASEServer_AP_SYBASE_INSTALL_PATH" \
–a "/opt/sybase/" \
–a "SybaseASEServer_AP_SYBASE_OS_USER" \
–a "sybase" \
–a "SybaseASEServer_AP_SYBASE_USER" \
–a "sa" \
–a "SybaseASEServer_AP_SYBASE_PASSWORD" \
–a "secret" \
–a "SybaseASEServer_AP_SYBASE_SERVER_NAME" \
–a "server1" \
–a "SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME" \
–a "server1_BS" \
–a "SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME" \
–a "server1_MS" \
–a "SybaseASEServer_AP_LogMonitorLogname" \
–a "/opt/sybase/ASE-12_5/install/server1.log" \
See the Parameters section for descriptions.
Appendix B. Task reference 155
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 IXB8500I Object object_name was created successfully. None.
-2 IXB8003E This task must be run against a managed node. Modify the task endpoint to be a
managed node.
1 IXB8503E The endpoint parameter was not specified for
this task.
Specify -a @Endpoint:epName1@Endpoint:epName2 on the
command.
1 IXB8504E The endpoint parameter was not specified for
this task.
Select an endpoint in the create
object dialog.
1 IXB8501E Error creating the object. See other messages for the specific
cause of the error.
1 IXB8505E The Create Object call failed with a return code
of return_code for object name object_name on
endpoint endpoint_name.
See other messages for the specific
cause of the error. You may also see
the additional text, the results from
the endpoint task.
1 IXB8506E Returned output from call:
output_from_endpoint_task
See the included text for indication of
the cause of the endpoint error.
1 IXB8507E Class init call failed. The dependency set might
not have been pushed to the endpoint.
Determine the cause for the failure.
You may re-push the dependencies
by calling objcall OID init followed
by objcall OID
post_discovery_depset_push.
1 IXB8502E Missing a required parameter. The following
parameters are required:
AP_SYBASE_IDENTIFIER
AP_SYBASE_INSTALL_PATH
AP_SYBASE_OS_USER
AP_SYBASE_USER
AP_SYBASE_PASSWORD
AP_SYBASE_SERVER_NAME
AP_SYBASE_BACKUP_SERVER_NAME
AP_SYBASE_MONITOR_SERVER_NAME
AP_LogMonitorLogname
Specify all of the required parameters
in the required order.
Usage notes
The object host managed node, gateway, and target endpoint must be in the same
Tivoli management region from which the task is being executed.
156 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Discover
Description
Creates the objects that represent the managed resources you want to monitor.
Authorization roles
SybaseMon_IXB_senior
Target managed resource
Managed node on which the object is created
The managed node varies depending on how the Discover task was invoked. If
you invoke from the task from the IBM Tivoli Monitoring for Databases: Sybase
ASE policy region icon context menu (right-click on the icon), then the managed
node is the Tivoli management region server. If you invoke the task from the IBM
Tivoli Monitoring for Databases: Sybase ASE Utility Tasks task library, you can
select which managed node to run the task on.
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
See the example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable -t ″Discover″ Name of the task to run: Discover
Not applicable -l ″Monitoring for Sybase ASE Utility
Tasks″
Name of the task library in which this task is
located
Not applicable -h ″managed_node_where_the_task_will_run″ Name of the managed node on which to run the
task
Endpoint List -a ″@Endpoint:epName1@Endpoint:epName2″
List of endpoints on which to search for resources
to monitor
Tivoli desktop: Select endpoints that run Sybase
ASE.
Command line: Include one or more endpoint
names separated by a space. Surround the entire
list with double quotation marks.
Object Host -a ″managed_node_name_on_which_the_task_
\is_to_create_the_objects″
Name of the managed node where the managed
resource objects representing the discovered
applications are to be created.
Endpoint task
timeout (seconds)
-a ″integer_value_in_seconds ″ Maximum number of seconds that the task runs
on each endpoint to search for application
configurations. The gateway timeout value should
be greater than or equal to this value.
Appendix B. Task reference 157
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Monitor on
discover?
-a ″yes|no″ The monitoring profile is not automatically
distributed to all discovered instances after the
Discover task runs. Application instances are
discovered; the corresponding object instances are
created; and the objects are added to the
subscription list of the monitoring profile. Then,
the profile is distributed or not:
v No: The profile is not distributed.
v Yes: The profiles are distributed to each
discovered instance.
Send notification to
TBSM?
-a ″yes|no″ Whether or not you want to notify IBM Tivoli
Business Systems Manager that a managed
resource was discovered
TEC Server Name -a ″TEC_Server_name″ Name of the IBM Tivoli Enterprise Console Server
to which to send the events.
The value must one of the following:
@EventServer, @EventServer#region_name, or for
non-TME TEC servers, host_name or IP address.
If this parameter is blank (-a ″″ in the command
line), the events are sent to the default IBM Tivoli
Enterprise Console server for the policy region.
For additional information see the IBM Tivoli
Enterprise Console Adapters Guide.
TEC Server Port -a ″port_number″ Port number for which the IBM Tivoli Enterprise
Console server was configured to listen for
events. The default is the IBM Tivoli Enterprise
Console default of 5529.
Sybase identifier -a ″SybaseASEServer_AP_\SYBASE_IDENTIFIER
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This identifies the
Sybase ASE Server. Choose a unique value for
each Sybase ASE Server to be monitored. This
value can only contain alphanumeric values.
Sybase installation
path
-a ″SybaseASEServer_AP_\SYBASE_INSTALL_PATH
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the installation
path of Sybase. This path should contain the
trailing delimitier, for example ’C:\sybase\’ or
’/opt/sybase/’
Operating system
user id
-a ″SybaseASEServer_AP_\SYBASE_OS_USER
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the operating
system user id to be used to start and interact
with Sybase.
158 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Sybase user id -a ″SybaseASEServer_AP_\SYBASE_USER
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is a Sybase user ID
used to log into Sybase which has been granted
the mon_role.
Sybase password -a ″SybaseASEServer_AP_\SYBASE_PASSWORD
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the password
for the user ID specified. This value must not be
NULL or an empty string.
Sybase Server name -a ″SybaseASEServer_AP_\SYBASE_SERVER_NAME
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Adaptive Server name.
Sybase Backup
Server name
-a ″SybaseASEServer_AP_\SYBASE_BACKUP_SERVER_NAME
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Backup Server name.
Sybase Monitor
Server name
-a ″SybaseASEServer_AP_\SYBASE_MONITOR_SERVER_NAME
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Monitor Server name.
Sybase Adaptive
Server log file name
-a ″SybaseASEServer_AP_\LogMonitorLogname
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Adaptive Server log file name.
Appendix B. Task reference 159
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable [-m ″integer_value″] Managed node timeout for the completion of this
task. If Discover runs against a large number of
endpoints, make this timeout longer than
normally needed for a task that runs against one
endpoint. This task runs in 2 phases. The first
phase runs on the managed node. During this
phase, another task is executed on each of the
selected endpoints. These are executed in groups,
but any of these endpoints can fail to complete
the task (for example, if the endpoint is not
running). This can cause each of the stages to take
the full default task timeout. If this happens, you
must make the timeout on the Discover task long
enough to allow each of the endpoint stages to
complete.
Note: Supply an argument for each -a parameter. If you are not using one of the
properties, you must supply it as a null (″″) property.
CLI example
The following example runs the Discover task on the ″vertical″ managed node,
searches the ″vertical″ and ″extreme″ endpoints, and puts the objects that it creates
on the vertical managed node. The task is set to run on each endpoint for a
maximum of 1 minute. The task is not set up to distribute the profile or notify IBM
Tivoli Business Systems Manager that a resource was discovered. The events are to
be sent to the default IBM Tivoli Enterprise Console server for the policy region at
port number 5529. The task has 10 minutes to complete.
The following variables and their values (shown in parentheses) are set up:
v SybaseASEServer_AP_SYBASE_IDENTIFIER (server1)
v SybaseASEServer_AP_SYBASE_INSTALL_PATH (/opt/sybase/)
v SybaseASEServer_AP_SYBASE_OS_USER (sybase)
v SybaseASEServer_AP_SYBASE_USER (sa)
v SybaseASEServer_AP_SYBASE_PASSWORD (secret)
v SybaseASEServer_AP_SYBASE_SERVER_NAME (server1)
v SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME (server1_BS)
v SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME (server1_MS)
v SybaseASEServer_AP_LogMonitorLogname (/opt/sybase/ASE-12_5/install/server1.log)
wruntask -t Discover \
–l "Monitoring for Sybase ASE Utility Tasks" \
–h "@ManagedNode:vertical" \
–a "@Endpoint:vertical @Endpoint:extreme" \
–a "vertical" \
–a "60" \
–a "no" \
–a "no" \
–a "@EventServer" \
–a "5529" \
–a "SybaseASEServer_AP_SYBASE_IDENTIFIER" \
–a "server1" \
–a "SybaseASEServer_AP_SYBASE_INSTALL_PATH" \
–a "/opt/sybase/" \
160 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
–a "SybaseASEServer_AP_SYBASE_OS_USER" \
–a "sybase" \
–a "SybaseASEServer_AP_SYBASE_USER" \
–a "sa" \
–a "SybaseASEServer_AP_SYBASE_PASSWORD" \
–a "secret" \
–a "SybaseASEServer_AP_SYBASE_SERVER_NAME" \
–a "server1" \
–a "SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME" \
–a "server1_BS" \
–a "SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME" \
–a "server1_MS" \
–a "SybaseASEServer_AP_LogMonitorLogname" \
–a "/opt/sybase/ASE-12_5/install/server1.log" \
–m "600"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 The task completed. Verify that the results indicated
match the expected results.
Usage notes
The object host managed node, gateway, and target endpoint must be in the same
Tivoli management region from which the task is being executed.
Appendix B. Task reference 161
Manage Tivoli Logs
Description
Lists, retrieves, or deletes trace logs for the object instance against which the task is
run.
This task only manages the trace logs in the IXB/logs directory for IBM Tivoli
Monitoring for Databases: Sybase ASE.
Authorization roles
v SybaseMon_IXB_senior
v SybaseMon_IXB_admin
v SybaseMon_IXB_user
Target managed resource
Managed node or endpoint
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable –t ″Manage Tivoli Logs″ Name of the task to run: Manage Tivoli Logs
Not applicable –l ″Monitoring for Sybase ASE Tasks″ Name of the task library where the task is located
Not applicable –h ″@SybaseASEServer_IXB:\server1@SybaseASEServer_IXB@example_ep″
Name of the instance of the node
Not applicable –a ″list|get|delete″ List action that lists, retrieves, or deletes trace logs
on the endpoint
Not applicable –a ″filename″ Name of the log file that you want to retrieve or
delete
CLI example
The following example retrieves the trace_discover.log file for the
server1@SybaseASEServer_IXB@example_ep object:
wruntask -t "Manage Tivoli Logs" \
-l "Monitoring for Sybase ASE Tasks" \
-h "@SybaseASEServer_IXB:server1@SybaseASEServer_IXB@example_ep" \
-a "get" \
-a "trace_discover.log"
See the Parameters section for descriptions.
162 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 The task completed. None
1 8201 Error deleting the file. Ensure that the specified file is not in
use or locked.
2 8202 The file specified in the ″get″ or ″delete″
operation does not exist.
Specify a different file.
3 8203 An incorrect option was passed to the task. Specify one of the following options:
get, list, and delete.
Usage notes
When invoked from the Tivoli desktop, the list action displays the log and trace
logs from the managed node where the object resides and from the endpoint.
When invoked from the command line, the list action displays the log and trace
logs only from the endpoint.
Appendix B. Task reference 163
Modify Object Properties
Description
Lists all properties of an object that represents a resource, and modifies existing
object properties that need to be changed, for example, a password value. You
cannot use this task to add new properties to the object; you can only modify
properties that already exist. Modify properties if an object property associated
with the application needs to be changed during the life of the application. For the
list feature of this task, property values that are encrypted are returned as six
asterisks.
Authorization roles
SybaseMon_IXB_senior
Target managed resource
Managed node that stores the object
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable -t ″Modify Object Properties″ Name of the task to run: Modify Object
Properties.
Not applicable -l ″Monitoring for Sybase ASE Internal
Utility Tasks″
Name of the task library that contains the task:
Monitoring for Sybase ASE Internal Utility Tasks
Not applicable -h ″@ManagedNode:managed node name″ Managed node on which to run the task
Not applicable -a ″Class_Name″ Type of object that the task is to modify
Not applicable -a ″Object_Name″ Name of the object to be modified
Not applicable -a ″list|set″ Action to take
Not applicable -a ″Context_Name″ Name of the AP_context variable for which you
are changing the value. Use this parameter only if
-a set was specified.
Not applicable -a ″Context_Value″ New value of the context variable. Use this
parameter only if -a set was specified.
CLI example
The following example lists the variables for the object:
164 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
wruntask -t "Modify Object Properties" \
-l "Monitoring for Sybase ASE Internal Utility Tasks" \
-h "@ManagedNode:managed node name" \
-a "class_name" \
-a "instance_name" \
-a "list"
The following example changes the value of the variable AP_Sample to NewVal:
wruntask -t "Modify Object Properties" \
-l "Monitoring for Sybase ASE Internal Utility Tasks" \
-h "@ManagedNode:managed_node_name" \
-a "class_name" \
-a "instance_name" \
-a "set" \
-a "AP_Sample" \
-a "NewVal"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 IXB8400I Property list is: None.
0 IXB8401I Successfully set property=value None.
1 IXB8402E Property property does not exist and cannot be
added.
This task was attempting to modify a
parameter that does not exist in the
object. This task can only be used to
modify existing parameters.
1 IXB8403E Error setting property=value See the additional error messages to
determine the exact cause of the
error.
7 IXB8404E This task requires that ″list″ or ″set″ be specified
as the third parameter.
The third parameter of the Modify
Object Properties task indicates
whether the task lists all of the
context of the object or modifies the
context of the object. It must be
specified on all invocations of this
task.
1 IXB8405E This task must be run against an application
object.
This task attempts to list or modify
properties of an application proxy
object. When running this task,
ensure that the target specified for
the task is the correct application
proxy object. Rerun the task
specifying the target to be the correct
application object.
1 IXB8406E ″set″ requires a property name and a new
property value.
Rerun the task specifying a
parameter name and value.
1 IXB8407E Read-only properties cannot be modified. The property that is being modified
is a read-only property. Read-only
properties cannot be modified.
Appendix B. Task reference 165
Return
code
Displayed
code
Description Action
1 IXB8408E An incorrect number of parameters were used.
The task needs at least the object type, object
label, and operation type as the first three
arguments.
Rerun the task using the correct
parameters.
1 IXB8409E Incorrect Object Type. Valid object types are:
object_classes.
An incorrect object type was used as
a parameter to the task. Use one of
the object types defined in this
product.
1 IXB84010E Unable to find object instance_name of type object
class.
An incorrect object label was used as
a parameter to the task. Check the
name of the object that you want to
modify and rerun the task.
Usage notes
This task modifies the value of the specified property of the object to the new
value. This is normally used to modify the object information to reflect changes in
the managed resource. For example a password in the application configuration
has changed, also change the password associated with the object in IBM Tivoli
Monitoring for Databases: Sybase ASE.
166 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
TBSM Synchronization
Description
Ensures that the IBM Tivoli Business Systems Manager objects match the Tivoli
desktop objects identically. This task searches for objects and sends a DISCOVER
event to IBM Tivoli Business Systems Manager for each object. The TBSM
Synchronization task also maintains a list of the objects that have been discovered
and alerts IBM Tivoli Business Systems Manager when they have been deleted by
sending a GONE event to IBM Tivoli Business Systems Manager for each object
that no longer exists.
Authorization roles
v SybaseMon_IXB_super
v SybaseMon_IXB_admin
v SybaseMon_IXB_user
Target managed resource
Managed node where the IBM Tivoli Enterprise Console server is installed.
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable –t ″TBSM Synchronization″ Name of the task to run: TBSM Synchronization
Not applicable –l ″Monitoring for Sybase ASE Utility
Tasks″
Name of the task library where the task is located
Not applicable –h ″managed_node_where_IBM_Tivoli\_Enterprise_Console_is_installed″
Managed node where the IBM Tivoli Enterprise
Console server is installed
CLI example
The following example executes the synchronization task on the my_TEC_server
managed node:
wruntask -t "TBSM Synchronization" \
-l "Monitoring for Sybase ASE Utility Tasks" \
-h "@ManagedNode:my_TEC_server"
where my_TEC_server is the name of the IBM Tivoli Enterprise Console server.
See the Parameters section for descriptions.
Appendix B. Task reference 167
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 IXB8000I Task complete. None
1 IXB8001E Task failed. See other messages for more details.
1 IXB8003E This task must be run against a managed node. Run the task against the managed
node where IBM Tivoli Enterprise
Console is installed.
0 IXB8300I Forwarding GONE event to IBM Tivoli Business
Systems Manager: $line
where $line is composed of the following:
Object OID;Version;Object Label.
For example:
1825982527.1.3330;1.0;\EnterpriseSingleSignOn_IQZ@zpmdlk
$line notifies you that the task sent a GONE
event to IBM Tivoli Business Systems Manager
for this object
Verify that the object has been
deleted on the IBM Tivoli Business
Systems Manager Console.
0 IXB8302I No objects were found to send to IBM Tivoli
Business Systems Manager.
Discover or create objects then run
the task again.
1 IXB8303E A TBSM notification event cannot be sent
because IBM Tivoli Business Systems Manager
Event Enablement has not been installed on the
IBM Tivoli Enterprise Console server.
Install the IBM Tivoli Business
Systems Manager Event Enablement
component on the IBM Tivoli
Enterprise Console event server.
0 IXB8304E A TBSM notification event cannot be sent
because IBM Tivoli Business Systems Manager
Event Enablement ihstttec command has failed
with an exit code of $IHSTTTEC_RC.
Verify that the IBM Tivoli Business
Systems Manager Event Enablement
is installed correctly and is
operational. You may need to run the
TBSM Synchronization task to
remove any discrepancy between the
IBM Tivoli Business Systems
Manager console and the Tivoli
Desktop.
Usage notes
None.
168 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix C. Event classes and rules reference
This appendix contains information about the IBM Tivoli Enterprise Console event
classes and rules that IBM Tivoli Monitoring for Databases: Sybase ASE provides.
The following topics are discussed in this appendix:
v “Event classes”
v “Rules for events” on page 177
Event classes
IBM Tivoli Monitoring for Databases: Sybase ASE provides the following set of
IBM Tivoli Enterprise Console event classes.
v SybaseAvailability_IXB_ApplicationUnavailable
v NumberOfDeadlocks_IXB
v NumberOfLockWaits_IXB
v LockWaitTime_IXB
v NumberOfAvailableLocks_IXB
v LocksInUse_IXB
v CacheHitRatio_IXB
v DBAllocatedSize_IXB
v DBUsedSize_IXB
v DBIndexSize_IXB
v DBUnallocatedSizeInKB_IXB
v NumberTotalPages_IXB
v NumberFreePages_IXB
v NumberUsedPages_IXB
v PercentFreeSpace_IXB
v NumberWaitingProcesses_IXB
v NumberDatabasesOpen_IXB
v EngineIdleTimeInSeconds_IXB
v NumberEngineConnections_IXB
v NumberServerConnections_IXB
v NumberServerConnectionsAvailable_IXB
v NumberPacketsSentPerSecond_IXB
v NumberPacketsReceivedPerSecond_IXB
SybaseAvailability_IXB_ApplicationUnavailable
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v Application
v FailingApplicationComponents
© Copyright IBM Corp. 2004 169
NumberOfDeadlocks_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberOfLockWaits_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
LockWaitTime_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
170 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
NumberOfAvailableLocks_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
LocksInUse_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
CacheHitRatio_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
Appendix C. Event classes and rules reference 171
DBAllocatedSize_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
DBUsedSize_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
DBIndexSize_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
172 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
DBUnallocatedSizeInKB_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberTotalPages_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberFreePages_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
Appendix C. Event classes and rules reference 173
NumberUsedPages_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
PercentFreeSpace_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberWaitingProcesses_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
174 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
NumberDatabasesOpen_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
EngineIdleTimeInSeconds_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberEngineConnections_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
Appendix C. Event classes and rules reference 175
NumberServerConnections_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberServerConnectionsAvailable_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
NumberPacketsSentPerSecond_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
176 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
NumberPacketsReceivedPerSecond_IXB
v application_instance
v application_class
v application_label
v application_version
v monitor_version
v application
v threshold
v instance_name
v lower_bound
v upper_bound
v current_metric_value
v calculation_method
v statistical_percentile
Rules for events
IBM Tivoli Monitoring for Databases: Sybase ASE supplies a set of rules that
provide correlation of related events. The rls files installed in
$BINDIR/../generic_unix/TME/SybaseMon contain the set of rules. These rule
sets use the classes defined in the baroc files contained in
$BINDIR/../generic_unix/TME/SybaseMon.
The IBM Tivoli Monitoring for Databases: Sybase ASE rules are defined in the
following files:
SybaseMon_tbsm_fwd.rls
Forwards the availability and discovery events for Sybase ASE to IBM Tivoli
Business Systems Manager. This allows IBM Tivoli Business Systems Manager
to maintain state information for instances of Sybase ASE.
SybaseMon.rls
Defines the rules that filter the event sent by the Discover task.
The rules and their functions are as follows:
sybasemon_ixb_forward_tbsm_notification
Forward the discovery event to IBM Tivoli Business Systems Manager.
sybasemon_ixb_SybaseASEServer_IXBAvailability_forward_tbsm_itm
Forward the Monitoring for Sybase ASE availability event for the Sybase ASE
Server to IBM Tivoli Business Systems Manager.
sybasemon_ixb_SybaseASEServer_IXBAvailability_forward_tbsm_itm_clearing
Forward the Monitoring for Sybase ASE availability clearing event for the
Sybase ASE Server to IBM Tivoli Business Systems Manager.
SybaseMon_IXB_drop_tbsm_notification_event
Drop the Monitoring for Sybase ASE IBM Tivoli Business Systems Manager
notification event.
Appendix C. Event classes and rules reference 177
178 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix D. Data providers reference
To create resource models, you need to use providers and their CIM classes,
properties, exceptions, and dependencies. A provider is the component of a
resource model that delivers the metrics of the monitored object.
The following MOF files contain customized data:
v IXB_NumDeadlocks_v1_mof.mof
v IXB_NumLockWaits_v1_mof.mof
v IXB_LockWaitTimes_v1_mof.mof
v IXB_AvailableLocks_v1_mof.mof
v IXB_LocksInUse_v1_mof.mof
v IXB_CacheHitRatio_v1_mof.mof
v IXB_DBSpaceUsage_v1_mof.mof
v IXB_SegmentSpaceUsage_v1_mof.mof
v IXB_NumWaits_v1_mof.mof
v IXB_NumDBsOpen_v1_mof.mof
v IXB_EngineInfo_v1_mof.mof
v IXB_NumConnections_v1_mof.mof
v IXB_NumConnectionsAvail_v1_mof.mof
v IXB_NumPacketsSentReceived_v1_mof.mof
MOF files that define data providers for IBM Tivoli Monitoring for Databases:
Sybase ASE and the source for the IBM Tivoli Monitoring for Databases: Sybase
ASE resource models are contained in the /WORKBENCH directory of the IBM
Tivoli Monitoring for Databases: Sybase ASE component software image.
The Log Monitor resource model is not used by IBM Tivoli Monitoring for
Databases: Sybase ASE. You can customize it to manage log files that you want to
monitor on the system.
LogMonitor provider
The following tables describe the CIM Class, properties, dependency set, and
parameters for the LogMonitor provider.
Table 4. LogMonitor CIM class
CIM class MOF file name Description
LogMonitor LogMonitor.mof Defines an interface for retrieving properties associated with
errors logged in application logs
Table 5. LogMonitor properties
Property Type Description
InstanceName string Name of the application or applications entity whose log is being
monitored. The default value is the content of the
ApplicationName parameter, which can be modified using the
LogMonitor Configuration XML file.
© Copyright IBM Corp. 2004 179
Table 5. LogMonitor properties (continued)
Property Type Description
LogName string Name of the application log being monitored
Offset uint64 Offset, in bytes, from the beginning of the log where the log
entry starts
Length uint32 Length of the matched log entry
Text string Text of the matched log entry
Severity string Severity, as an integer, of the matched log entry as defined in the
LogMonitor Configuration
Table 6. LogMonitor dependency set
itmcs_logmonitor_ilt This dependency set contains all of the files required to use the LogMonitor
provider. It is currently linked to the dependency set for the IBM Tivoli Monitoring
engine and is always pushed to any endpoint on which the IBM Tivoli Monitoring
engine is pushed.
Table 7. LogMonitor parameters
Parameter Required Type Default Description
LogMonitorConfigFilename Yes StringList None Use or reference descriptions from RM
parameters.
LogMonitorLogname Yes or No StringList None Use or reference descriptions from RM
parameters.
MAXREADBYTES_THRESHOLD Yes StringList None Use or reference descriptions from RM
threshold
LogMonitorSev0Formats No StringList None Use or reference descriptions from RM
parameters.
LogMonitorSev1Formats No StringList None Use or reference descriptions from RM
parameters.
LogMonitorSev2Formats No StringList None Use or reference descriptions from RM
parameters.
LogMonitorSev3Formats No StringList None Use or reference descriptions from RM
parameters.
LogMonitorSev4Formats No StringList None Use or reference descriptions from RM
parameters.
The following parameters are required to use the ITMException ILT with this ILT
for error reporting.
Table 8. ITMException ILT parameters
Parameter Required Type Default Description
COLLECTION_ID Yes StringList None An arbitrary unique ID string to
identify the instance of the running
resource model.
MONITOR_ID Yes StringList None ″LogMonitor″
CYCLE_TIME Yes StringList None The cycle time for the resource model.
The following table contains a list of exceptions (error codes & descriptions) that
can be returned by the ITMException ILT for the LogMonitor.
180 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 9. ITMException ILT exceptions for the LogMonitor
ENUM_ErrorCode
GET_ErrorCode Type Description
1000 Error An unrecognized error occurred while
processing the LogMonitor Configuration XML
file
1001 Error The LogMonitor Configuration XML file name
was not specified in the
LogMonitorConfigFilename parameter.
1002 Error An error occurred parsing the LogMonitor
Configuration XML file.
1003 Error An error occurred parsing a regular expression
format from either the LogMonitor
Configuration XML file or one of the format
parameters.
1004 Error An incorrect subexp attribute value was
specified in the LogMonitor Configuration
XML file.
1005 Error An incorrect severity id attribute was specified
in the LogMonitor Configuration XML file.
1100 Error An unrecognized error occurred while
accessing the log.
1101 Warning The specified log was not found or could not
be accessed.
1102 Warning The number of new bytes added to the log
since the last cycle exceeds the
MAXREADBYTES_THRESHOLD. Bytes are
read up to the threshold. Remaining bytes are
read during subsequent cycles.
1200 Error An unrecognized error occurred in the data
provider.
1201 Error An error occurred when instantiating a custom
plug-in class specified in the LogMonitor
Configuration XML file.
1202 Error An incorrect value was provided in the
MAXREADBYTES_THRESHOLD parameter.
1205 Error An error occurred when parsing the
mappingstring in the data provider CIM class
(MOF file).
1300 Error An unrecognized error occurred when
retrieving the names of logs to monitor.
1400 Error An unrecognized error occurred when
performing regular expression matching in the
log.
Note: The providers have the following requirements:
v For UNIX systems, locate a Perl interpreter in the /etc/Tivoli/bin file.
v For Windows systems, locate a Perl interpreter in the PATH.
Appendix D. Data providers reference 181
LogMonitor configuration file
Use the LogMonitor configuration file for advanced configuration of the
LogMonitor resource model. In most cases, this file is created for you and you are
not required to change it. However, it is important to specify the name and
location for the configuration file on the endpoint. On systems where multiple
instances of the LogMonitor resource model are running, it is important to name
the configuration files for each instance uniquely to avoid any configuration issues.
The name and location of the configuration file are specified in the
LogMonitorConfigFilename parameter of the LogMonitor resource model. The
name and location for the configuration file is arbitrary but must be a partial path
that is relative to the location of the $LCF_DATDIR. Because the configuration file
contains XML, it is normal to name the file with a .XML extension. For example:
Assume: $LCF_DATDIR=/opt/Tivoli/lcf/dat/1
If you want a LogMonitor configuration file to be named
/opt/Tivoli/lcf/dat/1/myApp/config11.xml
then, the value of the LogMonitorConfigFilename parameter is
myApp/config11.xml
LogMonitor configuration XML DTD
The syntax for the LogMonitor Configuration XML file is defined in the DTD file,
com.ibm.tivoli.monitoring.util.logmonitor.LogMonitorConfiguration.dtd, which is
embedded in the itmcs_logmonitor.jar. A copy of this DTD is also installed on the
Tivoli management region at
$BINDIR/../generic_unix/TME/ITMCS/LogMonitor/DTD/ \LogMonitorConfiguration.dtd.
Table 10 describes the elements and attributes that make up the DTD syntax for the
LogMonitor Configuration XML.
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes
Name Type Parent
Description and
usage
log_monitor_\
configuration
Element none Top level parent
element in the XML
document
version Element log_monitor_ \
configuration
Contains the version
for the XML
configuration
document
plugins Element log_monitor_\
configuration
Contains definitions
of Java™ classes that
override the default
plug-in classes used
by the LogMonitor
ILT
plugin Element plugins Contains the
definition of a Java
class that overrides
the default plug-in
class for the interface
specified by the
name attribute
182 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes (continued)
Name Type Parent
Description and
usage
name Attribute plugin Name of a specific
plug-in interface
whose default class is
being overridden.
The following values
are valid:
v ilogmonitor \logname
v ilogmonitorlog
v ilogmonitor \logmatcher
cim_property_ \mappings
Element log_monitor_\
configuration
Contains information
on how the
ILT/provider assigns
data to the CIM
properties defined in
the MOF file
property Element cim_property_ \
mappings
Contains information
on how the
ILT/provider assigns
data to a specific
CIM property
defined in the MOF
file. Mappings for
CIM properties,
Logname, Offset,
Length and Severity
are defined in the
ILT and cannot be
altered. There must
be a property
element for all other
CIM properties in the
MOF file.
name Attribute property The name of a
specific CIM
property whose data
source mapping is
being defined.
datasource Element property Identifies where the
ILT/provider obtains
data with which to
apply to specified
CIM properties. If
multiple datasource
elements are
included for a single
property the data are
concatenated into a
space delimited set
of strings.
Appendix D. Data providers reference 183
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes (continued)
Name Type Parent
Description and
usage
type Attribute datasource Identifies any of the
predefined data
source types from
which data will be
retrieved and
assigned to the CIM
property. The
following values are
valid:
v parameter
A resource model
parameter, whose
key is specified in
the key attribute,
is used as the data
source.
v context
An application
proxy object
context variable,
whose key is
specified in the
key attribute, is
used as the data
source.
v mappingstring
A CIM class
mappingstring
variable, whose
key is specified in
the key attribute,
is used as the data
source.
184 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes (continued)
Name Type Parent
Description and
usage
v logentry
A matching log
entry (or a portion
of the entry) is
used as the
datasource. If the
″subexp″ attribute
is specified in this
″logentry″ element,
then the
subexpression
matching the
specified subexp
attribute is used as
the data source. If
the ″subexp″
attribute is not
specified in this
element, then the
entire log entry is
used as the data
source.
v literalstring
The string
specified in the
″string″ attribute is
used as the data
source.
key Attribute datasource The key attribute
identifies the
keyword from the
data source whose
data value is to be
assigned to the CIM
property. When any
of the keyed data
source types are
specified you must
also specify a key
attribute.
Appendix D. Data providers reference 185
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes (continued)
Name Type Parent
Description and
usage
subexp Attribute datasource The optional
″subexp″ attribute
identifies a
subexpression from a
regular expression
logmatchformat that
will be assigned to
the CIM property. If
the subexp attribute
identifies a
non-existent
subexpression then
an empty string is
assigned to the CIM
property.
string Attribute datasource The ″string″ attribute
contains the literal
string that will be
assigned to the CIM
property.
log_elements Element datasource Reserved for future
use.
log_data Element log_elements Reserved for future
use
Tagname Attribute log_data Reserved for future
use
tagattr Attribute log_data Reserved for future
use
as_xml Attribute log_data Reserved for future
use
log_matching_ \expressions
Element log_monitor_ \configuration
Contains groups of
matching regular
expressions, which
are used by the
ILT/provider to
retrieve content from
the log
severities Element log_matching_ \expressions
Contains groups of
matching regular
expressions grouped
by severity
severity Element severities Contains matching
regular expressions
for a specific severity
186 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes (continued)
Name Type Parent
Description and
usage
id Attribute severity Identifies a severity
number from 0 – nn
with 0 being the
most critical severity.
Any log content
matching regular
expressions
contained within this
severity element are
applied against the
severity specified by
this id attribute. If a
log entry matches the
log_match_format
associated with
multiple severities,
the most critical
severity is reported.
log_match_formats Element severity Contains a collection
of log_match_format
elements for this
severity. A match
within the log is
defined by matching
″any″ or ″all″
log_match_format
elements as specified
in the matchtype
attribute.
matchtype Attribute log_match_formats Identifies whether
log file content must
match ″all″ or ″any″
of the
log_match_format
elements contained
within this
log_match_formats
element. The
following values are
valid:
v any
v all
If not specified, the
default value is ″all″.
Appendix D. Data providers reference 187
Table 10. LogMonitor Configuration XML DTD syntax elements and attributes (continued)
Name Type Parent
Description and
usage
log_match_format Element log_match_formats Contains a single
regular expression
used to match
against new content
in the log. The
expression syntax
supported by the
default
ilogmonitorlog \matcher plug-in is
Perl 5 regular
expressions.
multi_line_mode Attribute log_match_format Modifies the regular
expression parsing
behavior to
implement enhanced
line-anchor match
mode (also called the
multiline mode). This
is similar to the /m
option in Perl. Valid
values are ″true″ and
″false″, where the
default value is
″true″.
dot_matches_all \_mode
Attribute log_match_format Modifies the regular
expression parsing
behavior to
implement
″dot-matches-all″
match mode (also
called single-line
mode). This is similar
to the /s option in
Perl. Valid values are
″true″ and ″false″,
where the default
value is ″false″.
tagName Attribute LogMatchFormat Reserved for future
use
tagAttr Attribute LogMatchFormat Reserved for future
use
Log names
Log names are used to specify which logs to monitor. Log names are specified in
the LogMonitorLogname resource model parameter, the AP_LogMonitorLogname
context variable of the target application object, or both and must be fully
qualified. These log names can be provided in any of the following forms:
Fully qualified, no wildcards
In this case, the log name is a fully qualified name containing no wildcard
characters in the name. This form of log name identifies a single log as
specified by the name. This form supports the following logs:
188 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
v Single logs where the log grows infinitely
v Single logs where the log grows and is then pruned to zero-length upon
reaching a maximum size.
Fully qualified with wildcards
In this case, the log name is a fully qualified name that contains a wildcard
character (*) or (?) in the basename portion of the log name. The asterisk
(*) matches one or more characters, and the question mark (?) supports
exactly one character. Wildcard characters are not allowed in the path
portion of the log name. This form is used to support the monitoring of
indexed logs. For example:
v /tmp/logs/myAppnn.log
v /tmp/logs/myApptimestamp.log
Indexed logs represent a group of logs written into by the same
application. As one log becomes filled the application creates a new log
with a name that is indexed to indicate it is the most current log. The
LogMonitor resource model always monitors the most recently updated log
from a group of indexed logs.
Log name for specific platform
Often an application stores its logs in differing locations for different
platform types. This makes it important to be able to identify different
fully qualified log names for different platforms. You can do this by
appending a comma separated list of platform types in parentheses at the
end of a log name. You can specify different log names for each platform
in a single resource model, for example:.
/tmp/xyz/logs/some.log(aixv4-r1, solarix2)
Only AIX and Solaris systems monitor this log name.
c:/logdir/application*.log(w32-ix86)
Only Windows systems monitor the second log name.
/var/tmp/stuff.log
All systems monitor the third log name.
The Log Monitor resource model does not support circular rolling logs that are
trimmed at the beginning of the log to maintain a fixed size.
Appendix D. Data providers reference 189
190 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix E. Problem determination
This appendix explains how to troubleshoot IBM Tivoli Monitoring for Databases:
Sybase ASE. Troubleshooting, or problem determination, is the process of
determining why a certain product is malfunctioning.
If you have a problem that you are unable to solve using the information in this
appendix, contact IBM Software Support for further assistance.
Before contacting IBM Software Support about a problem you are experiencing
with this product, gather the following information that relates to the problem:
v Log files (See “Trace logging” on page 192.)
Collect all logs or all logs of a certain type, for example all task logs or all data
provider logs, from the failing systems:
– Tivoli management region:
- $DBDIR/IXB/logs/logname
- $DBDIR/IXB/ffdc/logname
- $DBDIR/AMW/logs/msg_profilename.log (for profile distribution issues)– Endpoint: $LCF_DATDIR/LCFNEW/IXB/logs/logname
v Sybase ASE version number and patch level
v Operating system version number and patch level
v Messages and other information displayed on the screen
v IBM Tivoli Monitoring for Databases: Sybase ASE version number and patch
level
v IBM Tivoli Monitoring version number and patch level
v IBM Tivoli Monitoring Component Services version number and patch level
v Tivoli Management Framework version number and patch level
See “Contacting IBM Software Support” on page 207 for more information about
working with IBM Software Support.
Built-in problem determination features
The primary troubleshooting feature in IBM Tivoli Monitoring for Databases:
Sybase ASE is logging. Logging refers to the text messages and trace data generated
by IBM Tivoli Monitoring for Databases: Sybase ASE and is always enabled for
every task. Messages and trace data are sent to an output destination, such as a
console screen or a file.
Typically, text messages relay information about the state and performance of a
system or application. Messages also alert the system administrator to exceptional
conditions when they occur. Consult the explanation and operator response
associated with the displayed messages to determine the cause of the failure. See
“Informational, warning, and error messages” on page 208 for message
information.
Trace data capture transient information about the current operating environment
when a component or application fails to operate as designed. IBM Software
© Copyright IBM Corp. 2004 191
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 IBM Tivoli Monitoring for
Databases: Sybase ASE:
v Installation and configuration
v General usage and operation
v Resource models
v Tasks
This appendix provides symptom descriptions and detailed workarounds for these
problems, as well as describing the logging capabilities of the product.
Trace logging
Trace logs capture information about the operating environment when component
code fails to operate as intended. These logs are in the English language only. IBM
Software Support uses the information captured by trace loggers to trace a problem
to its source or to determine why an error occurred. The default configuration for
tracing, such as whether tracing is enabled or disabled and trace level, depends on
the source of the tracing. Tracing is always enabled; however, you can choose how
many files to keep when it rolls.
The following sections provide details about the specific trace logs that are
collected:
v Installation trace logs
v Data provider trace logs
v Resource model trace logs
v Task trace logs
v IBM Tivoli Enterprise Console trace logs
The log files are located in the following directories:
v On the endpoint:
$LCF_DATDIR/LCFNEW/IXB/logs
$LCF_DATDIR/LCFNEW/IXB/ffdc
$LCF_DATDIR/LCFNEW/AMG/logs
$LCF_DATDIR/LCFNEW/AMW/logs (UNIX)
$LCF_DATDIR/LCFNEW/Tmw2k/Unix/data/dmxout.log (UNIX)
$LCF_DATDIR/LCFNEW/Tmw2k/Tmw2k.log (Windows)v On the managed node:
– $DBDIR/IXB/logs
– $DBDIR/IXB/ffdc
The trace logs are stored in a configurable number of files that roll each time the
component runs. For example, each time the component runs, trace information
from filename__1.log is copied into a new file, filename__n.log that is then named
192 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
filename__n+1.log. A new filename__1.log is created after the previous one has been
renamed, so the most recent log always has the number 1 at the end of the
filename.
Installation and uninstallation trace logs
Trace is always enabled by default. A configuration step is not required to enable
this tracing. Table 11 lists the location, names, and configuration options of the
installation and uninstallation trace logs that are in the Tivoli management region.
Table 11. Installation and uninstallation trace logs and descriptions
File location and name Configuration options
On the Tivoli management region managed node where
you are installing the product:
$DBDIR/IXB/logs \trace_SybaseMon_ \Install____N__pProcessIDNumber.log
These logs are never deleted and continue to wrap
forever. The most recent log has a value of 1 for N.
The ProcessIDNumber is an integer representing the
operating system process identifer of the process that
executes the install code.
On each managed node including the Tivoli management
region managed node where you are installing the
product:
$DBDIR/IXB/logs/ \trace_SybaseMon_ \Install_BIN____N__pProcessIDNumber.log
These logs are never deleted and continue to wrap
forever. The most recent log has a value of 1 for N.
The ProcessIDNumber is an integer representing the
operating system process identifer of the process that
executes the install code.
On each managed node including the Tivoli management
region managed node where you are uninstalling the
product:
$DBDIR/IXB/logs/ \trace_SybaseMon_ \Uninstall____N__pProcessIDNumber.log
These logs are never deleted and continue to wrap
forever. The most recent log has a value of 1 for N.
The ProcessIDNumber is an integer representing the
operating system process identifer of the process that
executes the uninstall code.
Data provider trace logs
Table 12 lists the location, names, and configuration options of the Data provider
trace logs.
Table 12. Data provider trace logs
Output location and file names What you can configure
$LCF_DATDIR/LCFNEW/AMG/logs/ \trc_itmcsN.log
1. Edit the following file:
$LCF_DATDIR/LCFNEW/AMG/logs/logging.properties
2. Set the following property to enable tracing:
AMS.ShellTrace.isLogging=true
3. Set the following property to change the number of
log files:
baseGroup.trcFile.maxFiles=N
where: N is the number of files to keep.
Appendix E. Problem determination 193
Table 12. Data provider trace logs (continued)
Output location and file names What you can configure
$LCF_DATDIR/LCFNEW/AMG/logs/ \trc_itmcsN.log
1. Edit the following file:
$LCF_DATDIR/LCFNEW/AMG/logs/logging.properties
2. Set the following properties to enable tracing:
AMS.LogMonitorConfigurationErrorHandlerTrace. \
isLogging=true
AMS.LogMonitorLogMatchFormatTrace.isLogging=true
AMS.LogMonitorILTBaseTrace.isLogging=true
AMS.LogMonitorLogTrace.isLogging=true
AMS.LogMonitorMatcherBaseTrace.isLogging=true
AMS.LogMonitorConfigurationTrace.isLogging=true
AMS.LogMonitorLogNameTrace.isLogging=true
3. Set the following property to change the number of
log files:
baseGroup.trcFile.maxFiles=N
where: N is the number of files to keep.
$LCF_DATDIR/LCFNEW/IXB/logs Controlling the rolling count:
1. Create and edit the following plain text file:
$LCF_DATDIR/LCFNEW/IXB/ \logs/logging.properties
2. Add the following line to the file, or edit the line to
contain this information:
itmcs.log.filecount=N
where: N is the number of files to keep.
Enabling data provider tracing for a specific object:
1. Obtain the OID for the object that you want to enable
logging for using the following command:
wlookup -ar PAC_class
2. Modify the trace enablement property with the
following command:
idlcall OID update_context
\"AP_SYBASE_ENABLE_UTILITY_LOGGING=true\"
Disabling data provider tracing for a specific object:
1. Obtain the OID for the object that you want to
disable logging for with the following command:
wlookup -ar PAC_class
2. Modify the trace enablement property with the
following command:
idlcall OID update_context
\"AP_SYBASE_ENABLE_UTILITY_LOGGING=false\"
194 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 12. Data provider trace logs (continued)
Output location and file names What you can configure
Using the statistical threshold mechanism in a resource
model:
$LCF_DATDIR/LCFNEW/ITM/PACS/itmcsLog.properties
v Set the following property to change the number of
log files:
itmcsFileHandler.maxFiles=N
where: N is the number of files to keep.
v Set the following property to increase the level of
logging:
itmcsLogger.trc.level=ERROR
Change ERROR to ALL.
Resource model trace logs
Table 13 lists the location, names, and configuration options of the resource model
trace logs.
Table 13. Resource model trace logs
Output location and file names What you can configure
These traces are always included in the IBM Tivoli
Monitoring traces at the following locations:
Windows operating systems
$LCF_DATDIR/LCFNEW/Tmw2k/Tmw2k.log
UNIX operating systems
$LCF_DATDIR/LCFNEW/AMW/logs/trace_ \dmxengine.log
Modify the trace level of the IBM Tivoli Monitoring
engine as follows:
The wdmtrceng command modifies the IBM Tivoli
Monitoring and resource model trace levels. You modify
the trace levels for the data providers (ILTs) in various
ways depending on the provider.
Use the following command to modify the trace level of
IBM Tivoli Monitoring and resource models:
wdmtrceng -e endpoint logfile_name \trace_level size
where:
-e endpoint
Label of the endpoint where the resource to be
managed resides
logfile_name
Name of the log file, which is usually left blank
to use the default
trace_level
0 – 3 with 3 being the most detailed
size Size of the log file, specified in bytes. Specify -1
to reset the size to the default value (5 MB for
Windows, 2.5MB for UNIX/Linux).
Example:
The following example sets tracing to the highest level
on the extreme endpoint, but leaves the file name and
the size set to the defaults:
wdmtrceng -e extreme "" 3 -1
Appendix E. Problem determination 195
Task trace logs
Tracing is always enabled for tasks. Table 14 lists the location, names and
configuration options of the task trace logs.
Table 14. Task trace logs
Output location What you can configure
On the endpoint:
$LCF_DATDIR/LCFNEW/IXB/logs
$LCF_DATDIR/LCFNEW/IXB/ffdc
1. Create and edit the following plain text file:
$LCF_DATDIR/LCFNEW/IXB/ \logs/logging.properties
2. Add the following line to the file, or edit the line to
contain this information:
itmcs.log.filecount=N
where: N is the number of files to keep.
On the managed node:
$DBDIR/IXB/logs
$DBDIR/IXB/ffdc
$DBDIR/IXB/cfg
1. Create and edit the following plain text file:
$DBDIR/IXB/logs/logging.properties
2. Add the following line to the file, or edit the line to
contain this information:
itmcs.log.filecount=N
where: N is the number of files to keep.
IBM Tivoli Enterprise Console trace logs
See IBM Tivoli Enterprise Console publications for additional information about
troubleshooting procedures for the IBM Tivoli Enterprise Console server and
collecting IBM Tivoli Enterprise Console Server trace logs.
The IBM Tivoli Monitoring for Databases: Sybase ASE provides script files that run
on the IBM Tivoli Enterprise Console server. These scripts are always enabled for
tracing. The associated trace logs reside on the IBM Tivoli Enterprise Console
server managed node.
Table 15 contains locations, file names, and descriptions of IBM Tivoli Enterprise
Console trace logs.
Table 15. IBM Tivoli Enterprise Console trace logs
Output location and file names Description
$DBDIR/IXB/logs/trace_tbsmfwd_itm____N__ \pProcessIDNumber.log
This log is produced when IBM Tivoli Monitoring for
Databases: Sybase ASE resource model events are being
forwarded to IBM Tivoli Business Systems Manager. You
can change the number of log files to keep as follows:
1. Create and edit the following plain text file:
$DBDIR/IXB/ \logs/logging.properties
2. Add the following line to the file, or edit the line to
contain this information:
itmcs.log.filecount=N
where: N is the number of files to keep. The most
recent log is 1.
196 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 15. IBM Tivoli Enterprise Console trace logs (continued)
Output location and file names Description
$DBDIR/IXB/logs/trace_tbsmfwd_notification____\N__pProcessIDNumber.log
This log is produced when IBM Tivoli Monitoring for
Databases: Sybase ASE managed resource discovery
events are being forwarded to IBM Tivoli Business
Systems Manager. You can change the number of log
files to keep as follows:
1. Create and edit the following plain text file:
$DBDIR/IXB/ \logs/logging.properties
2. Add the following line to the file, or edit the line to
contain this information:
itmcs.log.filecount=N
where: N is the number of files to keep. The most
recent log is 1.
Installation problem determination
Table 16 and Table 18 on page 199 contain problems related to installation and
uninstallation that might occur with IBM Tivoli Monitoring for Databases: Sybase
ASE. Table 17 on page 198 covers installation issues related to Tivoli Data
Warehouse.
Table 16. General problems and solutions for installation
Problem Solution
The installation fails and installation trace logs fail
to appear in the IBM Tivoli Monitoring for
Databases: Sybase ASE trace log directory on the
Tivoli management region.
The set of software that you used to install IBM Tivoli
Monitoring for Databases: Sybase ASE is probably not valid.
Obtain a new copy of the product software and perform the
installation again. You must follow the Passport Advantage®
Readme download instructions for IBM Tivoli Monitoring for
Databases: Sybase ASE.
The installation fails and installation trace logs are
available in the IBM Tivoli Monitoring for
Databases: Sybase ASE trace log directory on the
Tivoli management region.
Examine the IBM Tivoli Monitoring for Databases: Sybase
ASE installation trace log for the error. If possible, correct the
cause of the error. Optionally, uninstall IBM Tivoli Monitoring
for Databases: Sybase ASE, then reinstall.
To reinstall without uninstalling, remove the following file:
$DBDIR/.installed/SybaseMon.
See Table 11 on page 193 for more information about file
locations, names, and configuration options.
The IBM Tivoli Monitoring for Databases: Sybase
ASE successfully installs on the Tivoli management
region, but fails on another managed node.
Verify that there is connectivity between the Tivoli
management region and the managed nodes on which you
want to install the product.
Appendix E. Problem determination 197
Table 17. Installation problems and solutions for Tivoli Data Warehouse
Problem Solution
Installation of the prerequisite WEP AMX 5.1.2 Fix
Pack 1 fails with a prerequisite failure even though
AMX 5.1.1.600 is installed.
The installation of AMX WEP 5.1.1.600 failed to register the
warehouse pack version.
1. Run twg_configwep.bat -u user -p password -f list to
list the installed warehouse enablement packs and version
information.
Note: To ensure a successful installation, confirm the
version number (AMX 5.1.1.600) before you run the
installation of the AMX 5.1.2 Fixpack 1 WEP (version
5.1.1.660) that is a prerequisite for the IBM Tivoli
Monitoring Component Services warehouse enablement
pack.
2. Ensure that you access a user account that has DB2
administrator privileges on the computer that hosts Tivoli
Data Warehouse.
3. Access a command prompt.
4. Manually execute the following command before you
install the warehouse pack that has warehouse pack AMX
version 5.1.1.600 as a prerequisite:
twh_setwepver AMX 5.1.1 5.1.1.600
You need to run this command only once, however it is
harmless to run the command again. The command is
located in the following path:
install_dir/twh/tools/bin/twh_setwepver.bat
If the AMX version is 5.1.1.600 or higher, do not reset the
version information.
5. After AMX 5.1.1.660 is installed in the warehouse you can
proceed to install the IBM Tivoli Monitoring Component
Services warehouse enablement pack.
198 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 17. Installation problems and solutions for Tivoli Data Warehouse (continued)
Problem Solution
When you attempt to open the Crystal Reports for
the product, you might see an error message like the
following:
"Failed to open a rowset. File \
c838d26246160.rpt."
1. Install the Hot Fixes or Service Packs that address this
issue (Track ID ADAPT00319691). For Crystal Enterprise 9,
the updates for this issue are available at the following
locations:
ftp://ftp1.businessobjects.com/outgoing/EHF/ \
ce90servwin_en.zip
ftp://ftp1.businessobjects.com/outgoing/EHF/ \
ce90wcswin_en.zip
Note: Unless indicated otherwise, Weekly Hot Fix updates
from the FTP site have only been tested with English
versions of products.
2. Add the value -procreportoptions __ibmstoredproc to the
command line of the Page Server executable
(Pageserver.exe) as follows:
a. Click Start —> Programs —> Crystal Enterprise 9 —>
Crystal Configuration Manager.
b. In the Crystal Configuration Manager, right-click the
Crystal Page Server and stop the service.
c. Right-click the Crystal Page Server again, and select
Properties. The Crystal Page Server Properties box
appears.
d. In the Command box, add the value
-procreportoptions __ibmstoredproc (without
quotation marks) to the end of the command line.
e. Restart the Crystal Page Server.
Table 18. General problems and solutions for uninstallation
Problem Solution
If you uninstall IBM Tivoli Monitoring for
Databases: Sybase ASE after you uninstall IBM
Tivoli Monitoring Component Services, the IBM
Tivoli Monitoring for Databases: Sybase ASE
uninstall fails. You receive the following error
message:
Cannot uninstall. The following file is
missing:
$BINDIR/TME/APPLSVCS/ITMCSInstallUtils.sh
Restore the Tivoli management region to a backup taken
before IBM Tivoli Monitoring Component Services was
installed. Then, uninstall IBM Tivoli Monitoring for
Databases: Sybase ASE again.
The wuninst CLI returns a message stating that a
particular part of the product could not be removed.
Examine the IBM Tivoli Monitoring for Databases: Sybase
ASE uninstall trace log for the error. If possible, correct the
cause of the error, and uninstall the IBM Tivoli Monitoring for
Databases: Sybase ASE again.
You are unable to uninstall IBM Tivoli Monitoring
for Databases: Sybase ASE because wuninst returns
an error message indicating that the product is not
installed.
This problem can occur if the initial uninstall operation failed
and you need to run the uninstall CLI again. To uninstall the
product in this situation, run the following script on each
managed node from which you want to uninstall the product:
$BINDIR/../generic_unix/TME/ \SybaseMon.uninstall -rmfiles
Reinstall fails saying it is already installed Remove the following:
$DBDIR/.installed/SybaseMon_ALIDB
Appendix E. Problem determination 199
Problems and workarounds
The following sections provide symptoms and workarounds for problems that
might occur with IBM Tivoli Monitoring for Databases: Sybase ASE:
v “Discovery problem determination” on page 200
v “Resource model problem determination” on page 201
v “Tasks problem determination” on page 203
v “Event problem determination” on page 204
Discovery problem determination
Table 19 contains problems that might occur with the discovery task.
Table 19. Discovery problems and solutions
Problem Solution
IBM Tivoli Monitoring for Databases: Sybase ASE Discovery
does not discover and create the expected objects. For
example, you might see the following output from the task:
Task Name: Discover
Task Endpoint: myMN (ManagedNode)
Return Code: 0
------Standard Output------
IXB8050I Configuration: Sybase ASE Server matched \
on endpoint: myEP
IXB8060I Discovery task summary:
IXB8061I Number of matched configurations : 0
IXB8062I Number of non-matched configurations: 1
IXB8063I Number of objects created : 0
IXB8064I Number of object creation errors : 0
IXB8065I Number of endpoint object creation errors : 0
IXB8066I Number of duplicate objects : 0
The common reason for this failure is that the
Sybase ASE is not running in a normal state on the
endpoint. The Discover task uses the set of running
processes as part of the application signature. They
are used to determine whether the application is
installed and which aspects of the application are to
be monitored.
Verify that the application is running correctly and
rerun the Discover task.
If the objects are not created after rerunning the
Discover task, create objects using the appropriate
″Create ... Object″ task.
After the objects are discovered, they are not monitored. The Discovery task includes an argument to
distribute resource models automatically when
objects are created. If this argument is not specified
with the proper value, the resource models are not
automatically distributed when the object is created.
See “Discovering resources to monitor” on page 21
and “Discover” on page 157 for more information.
IBM Tivoli Monitoring for Databases: Sybase ASE Discover
task reports matching zero configuration and zero
non-matched conifgurations. For example, if you see the
following output from the task:
Task Name: Discover
Task Endpoint: myMN (ManagedNode)
Return Code: 0
------Standard Output------
IXB8050I Configuration: Sybase ASE Server matched \
on endpoint: myEP
IXB8060I Discovery task summary:
IXB8061I Number of matched configurations : 0
IXB8062I Number of non-matched configurations: 0
IXB8063I Number of objects created : 0
IXB8064I Number of object creation errors : 0
IXB8065I Number of endpoint object creation errors : 0
IXB8066I Number of duplicate objects : 0
Collect the logs and call IBM Software Support.
200 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Resource model problem determination
This section contains information about both general resource model problems and
problems for the specific resource models.
General resource model problems
Table 20 contains problems that might occur with resource models.
Table 20. General resource model problems and solutions
Problem Solution
A resource model fails to start. The state of the
resource model is ″Failed.″
The resource model encountered an error during a monitoring
cycle. Check the return code for the resource model in
Appendix A, “Resource model reference,” on page 41 for more
information about the error.
A resource model fails to start. The state of the
resource model is ″Unable to start.″
The resource model encountered an error during initialization.
Check the return code for the resource model in Appendix A,
“Resource model reference,” on page 41 for more information
about the error
A resource model fails to start. The state of the
resource model is ″Error.″
The resource model encountered an error during a monitoring
cycle. Check the return code for the resource model in
Appendix A, “Resource model reference,” on page 41 for more
information about the error. Also, check the resource model log
files.
A resource model fails to start. The state of the
resource model is ″Missed prereq.″
The resource model was unable to start because of a missing file
or environmental setup. Perform one of the following actions:
v Ensure that the JRE has been linked on the endpoint. Use the
DMLinkJRE task.
v A required data provider file is missing. If the product has an
Endpoint Init task, run the task to download the requisite files
to the system. Re-run the Discover task against the endpoint
to download the requisite files.
v The data provider experienced an error during monitoring.
Check the data provider logs for more information.
Resource models go into ″Retrying (10)″ state. Ensure that Sybase ASE is available. This can be done by looking
at the state of the Availability resource model, or by using the
Check Status task (see Appendix B, “Task reference,” on page
131). If the Sybase ASE is available, check the following:
v Ensure that the supplied Sybase ASE user ID and password
are valid. The supplied user or password can be viewed or
modified with the Modify Object Properties task (see
Appendix B, “Task reference,” on page 131).
v Ensure that Sybase ASE has been enabled for monitoring. See
″Enabling Sybase ASE for monitoring″ in IBM Tivoli Monitoring
for Databases: Sybase ASE: Installation and Setup Guide.
v Check the data provider log files.
Appendix E. Problem determination 201
Table 20. General resource model problems and solutions (continued)
Problem Solution
Resource models are in error or missed prereq
state after running the wdmlseng command.
These failures have the following possible causes:
v Product not installed on the endpoint gateway
v DependencyMgr problem
v Endpoint issues
Investigate the problem as follows:
Product not installed on the endpoint gateway
1. Run the following wlookup command to find the oid for the
class of the instance that is causing the problem:
wlookup -ar PAC_class
The available classes are as follows:
v SybaseASEServer_IXB
2. Run the following command using the oid for the class of the
instance found in Step 1:
idlcall "oid" post_discovery_depset_push
DependencyMgr problem
Call Customer Support for help with this problem after you
complete the following:
v Use the following commands to determine whether the
specified dependency manager (also called a dependency set)
is defined in the Tivoli management region configuration.
wlookup -r DependencyMgr IXB_prediscovery
wlookup -r DependencyMgr IXB_postdiscovery
v Use the following commands to show the dependency
manager definition:
wdepset -v oid
v Increase the gateway debug_level to 6 (which can generate
additional overhead on the gateway) using the following
command:
wgateway gatewayname set_debug_level 6
v Increase the endpoint logging level using the following
command:
wep endpoint set_config log_threshold=3
v Recreate the problem, and collect the gatelog, lcfd.log and
product specific logs. Send these logs to IBM Software
Support.
202 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 20. General resource model problems and solutions (continued)
Problem Solution
Endpoint issues
v See ″Product not installed on the endpoint gateway″
on page 202.
v Check disk space in the endpoint directory structure.
v Check permissions on the LCF file structure.
v Check to see if any security packages are running.
The following have been known to cause issues with
transferring dependencies:
– SEOS
– GSA
The Java engine is crashing and might be
producing javacore files.
Use the Java Runtime shipped with IBM Tivoli Monitoring. Java
programs can exercise different paths in Java runtimes. The most
reliable path is to use the version with which the application was
tested. They can also be very sensitive to patches on the
operating system. If replacing the JRE does not solve the
problem, check for operating system patches.
Non-key attributes in the events sent to IBM
Tivoli Enterprise Console do not reflect the
current values as displayed in the Web Health
Console.
Because the Web Health Console displays real-time data and
IBM Tivoli Enterprise Console provides a snapshot of the data at
the time the event was generated, it is possible for the
information in the events to be out of sync with the information
displayed on the Web Health Console.
Refer to the IBM Tivoli Monitoring Problem Determination Guide for more information
about problem determination for resource models.
Specific resource model problems
The following table contains problems that might occur with specific resource
models.
Table 21. Specific resource model problems and solutions
Problem Solution
The Availability resource model is in Error state
when Manage on Discovery is used and
DMXProcess has never been run on the endpoint.
This is normal for this resource model.
Stop and re-start the engine.
Tasks problem determination
Table 22 on page 204 lists general task problems that might occur.
Appendix E. Problem determination 203
Table 22. Task problems and solutions
Problem Solution
Sybase servers fail to start when running the
Start tasks on UNIX endpoints.
1. Verify that a valid Operating System user ID was specified
during Discovery. See the Appendix B, “Task reference,” on
page 131 for information about how to list the context
variables for the Sybase instance object.
2. Check the trace files prefixed with ″trace_startWrapper″’ in
the $LCF_DATDIR/LCFNEW/IXB/logs directory. The
standard output of the start command is in these trace files,
so this should give a clue regarding why the start failed. A
typical problem is supplying an operating system user ID
that does not have authority to the Sybase executables/files.
Sybase servers fail to stop v Ensure that the supplied Sybase ASE user ID and password
are valid. The supplied user or password can be modified
with the Modify Object Properties task (see Appendix B, “Task
reference,” on page 131).
v Ensure that Sybase ASE has been enabled for monitoring. See
″Enabling Sybase ASE for monitoring″ in IBM Tivoli
Monitoring for Databases: Sybase ASE: Installation and Setup
Guide.
Sybase servers fails to stop when running the
Stop tasks on Windows endpoints.
Sybase might not respond to shutdown requests on Windows;
therefore, attempts to stop it are unsuccessful. You can attempt
to stop the server manually on the endpoint. If that does not
work, consult the Sybase troubleshooting documentation.
Event problem determination
Table 23 contains problems that might occur with events.
Table 23. Event problems and solutions
Problem Solution
You do not see events for IBM Tivoli Monitoring
for Databases: Sybase ASE in IBM Tivoli
Enterprise Console.
From the IBM Tivoli Enterprise Console server, run the
wtdumprl command. If the output contains PARSING_FAILED
errors for the events sent by IBM Tivoli Monitoring for
Databases: Sybase ASE as in the example below this table, then
run the Configure Event Server task to update the current rule
base to include new event slots. See the IBM Tivoli Monitoring for
Databases: Sybase ASE Installation and Setup Guide for the
procedure to update the current rule base.
If this problem continues, contact IBM Software Support.
You do not see events for IBM Tivoli Monitoring
for Databases: Sybase ASE in IBM Tivoli
Enterprise Console when events were sent by the
IBM Tivoli Monitoring engine.
Run the following command to see if the profile was enabled to
send events to a valid IBM Tivoli Enterprise Console Server:
wdmdumpprf -P profile_name -x output_file_name
Check the output file to ensure that this profile is enabled to
send events.
You do not see events for IBM Tivoli Monitoring
for Databases: Sybase ASE in IBM Tivoli
Enterprise Console when events were sent by
IBM Tivoli Monitoring but were cached because
of network communication issues between the
endpoint and gateway.
Check the IBM Tivoli Monitoring cache directory on the
endpoint as follows:
v %LCF_DATDIR%/LCFNEW/Tmw2k/Tec/cache (Windows)
v $LCF_DATDIR/LCFNEW/Tmw2k/Unix/Tec/cache (UNIX)
If the cache directory contains recent events, verify connectivity
between the endpoint and the IBM Tivoli Enterprise Console
server.
204 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Table 23. Event problems and solutions (continued)
Problem Solution
The gateway does not have the IBM Tivoli
Enterprise Console code that contains the
send_event method.
Check the IBM Tivoli Enterprise Console documentation for this
requirement.
The IBM Tivoli Enterprise Console Server is
down when an event is sent, but there are no
cache files on the endpoint.
The gateway or endpoint might communicate, but the gateway
could not send the event. This should show a cache file on the
gateway at the following location: /etc/Tivoli/tec.
After uninstalling IBM Tivoli Monitoring for
Databases: Sybase ASE, the rulebase created
through the IBM Tivoli Monitoring for Databases:
Sybase ASE Configure Event Server task cannot
be compiled. You receive rule base compilation
errors such as the following:
v ECO3538E File
″rule_base_dirpath\SybaseMon_tbsm_ \notification.baroc″ does not exist or cannot be
read.
—or—
v ECO3056E ″’SybaseMon’″: rule set is not
defined in this rule base.
1. At a Tivoli command prompt on the IBM Tivoli Enterprise
Console server, issue the following command to remove the
IBM Tivoli Monitoring for Databases: Sybase ASE class
definitions from the rule base (rule_base_name) that no longer
compiles:
wrb -delrbclass SybaseMon_tbsm_ \notification -force rule_base_name
2. Issue the following commands to remove the IBM Tivoli
Monitoring for Databases: Sybase ASE rule definitions from
the rule base that no longer compiles:
wrb -delrbrule SybaseMon rule_base_name
wrb -delrbrule SybaseMon_tbsm_fwd rule_base_name
3. If the -delrbrule command fails stating that the rule pack
cannot be deleted because is it defined in a rule base target,
issue the following command for each rule base target
(rule_base_target) listed in the error message, then reissue the
above wrb -delrbrule commands that failed previously:
wrb -delrbtarget rule_base_target SybaseMonwrb -delrbtarget rule_base_target SybaseMon_tbsm_fwd
4. Recompile the rule base using the following command:
wrb -comprules rule_base_name
Example parsing failed error messages:
### EVENT ###
SybaseAvailability_IXB_ApplicationUnavailable;
modelname="SybaseMonAvailability_IXB";
profilename="ExampleProfile#admin-region";
event_key="Application=SybaseASEServer_IXB;";
eventid="83196390";
severity="CRITICAL"; application="SybaseASEServer_IXB";
application_class="SybaseASEServer_IXB";
application_label="server1@SybaseASEServer_IXB@example_ep";
application_oid="1825982527.1.5497"; application_version="1.0";
failingapplicationcomponents="SybaseASE";
monitor_version="5.1.2"; hostname="example_ep"; adapter_host="example_ep";
origin="9.27.137.143"; fqhostname="example_ep.raleigh.ibm.com";
date="09/23/2004 09:26:32"; msg="Critical Processes/Services for the
application (SybaseASEServer_IXB_IXB) are
not running.";END
### END EVENT ###
PARSING_FAILED
Appendix E. Problem determination 205
Support information
This section describes the following options for obtaining support for IBM
products:
v “Searching knowledge bases”
v “Obtaining fixes”
v “Contacting IBM Software Support” on page 207
Searching knowledge bases
If you have a problem with your IBM software, you want it resolved quickly. Begin
by searching the available knowledge bases to determine whether the resolution to
your problem is already documented.
Search the information center on your local system or network
IBM provides extensive documentation that can be installed on your local machine
or on an intranet server. You can use the search function of this information center
to query conceptual information, instructions for completing tasks, reference
information, and support documents.
Search 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. To search multiple Internet resources for your product, expand the
product folder in the navigation frame to the left and select Web search. From this
topic, you can search a variety of resources including:
v IBM technotes
v IBM downloads
v IBM Redbooks™
v IBM DeveloperWorks
v Forums and newsgroups
v Google
Obtaining fixes
A product fix might be available to resolve your problem. You can determine what
fixes are available for your IBM software product by checking the product support
Web site:
1. Go to the IBM Software Support Web site
(http://www.ibm.com/software/support).
2. Under Products A - Z, select your product name. This opens a product-specific
support site.
3. Under Self help, follow the link to All Updates, where you will find a list of
fixes, fix packs, and other service updates for your product. For tips on refining
your search, click Search tips.
4. Click the name of a fix to read the description and optionally download the fix.
To receive weekly e-mail notifications about fixes and other news about IBM
products, follow these steps:
1. From the support page for any IBM product, click My support in the
upper-right corner of the page.
2. If you have already registered, skip to the next step. If you have not registered,
click register in the upper-right corner of the support page to establish your
user ID and password.
206 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
3. Sign in to My support.
4. On the My support page, click Edit profiles in the left navigation pane, and
scroll to Select Mail Preferences. Select a product family and check the
appropriate boxes for the type of information you want.
5. Click Submit.
6. For e-mail notification for other products, repeat Steps 4 and 5.
For more information about types of fixes, see the Software Support Handbook
(http://techsupport.services.ibm.com/guides/handbook.html).
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 page
(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
(http://techsupport.services.ibm.com/guides/contacts.html) and click the
name of your geographic region.v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries®, 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 page (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 or, from other countries, go to
the contacts page of the IBM Software Support Handbook on the Web
(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.
Follow the steps in this topic to contact IBM Software Support:
1. Determine the business impact of your problem.
2. Describe your problem and gather background information.
3. Submit your problem to IBM Software Support.
Determine the business impact of your problem
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
you are reporting. Use the following criteria:
Appendix E. Problem determination 207
Severity 1 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 Significant business impact: The program is usable but is
severely limited.
Severity 3 Some business impact: The program is usable with less
significant features (not critical to operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on
operations, or a reasonable circumvention to the problem has
been implemented.
Describe your problem and gather background information
When explaining 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 the problem be recreated? If so, what steps led to the failure?
v Have any changes been made to the system? (For example, hardware, operating
system, networking software, and so on.)
v Are you currently using a workaround for this problem? If so, please be
prepared to explain it when you report the problem.
Submit your problem to IBM Software Support
You can submit your problem in one of two ways:
v Online: Go to the ″Submit and track problems″ page on the IBM Software
Support site (http://www.ibm.com/software/support/probsub.html). Enter
your information into the appropriate problem submission tool.
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 the problem be recreated? If so, what steps led to the failure?
v Have any changes been made to the system? (For example, hardware, operating
system, networking software, and so on.)
v Are you currently using a workaround for this problem? If so, please be
prepared to explain it when you report the problem.
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 for you to implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
IBM product support Web pages daily, so that other users who experience the
same problem can benefit from the same resolutions.
For more information about problem resolution, see Searching knowledge bases
and Obtaining fixes.
Informational, warning, and error messages
This appendix introduces message logging and explains how to gather information
from those logs.
208 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Message logging refers to the text and numeric messages created by the software.
These messages relay information about how the system or application is
performing and can alert you to exceptional conditions when they occur. Messages
are sent to an output destination, such as a file, database, or console screen.
If you receive a warning or error message, you can do one of the following:
v Follow the instructions listed in the Detail window of the message if this
information is included there.
v Consult the message details listed in this appendix to see what action you can
take to correct the problem.
v Consult the message log for message ID and text, time and date of the message,
as well as other data you can use to diagnose the problem.
Message format
IBM Tivoli Monitoring for Databases: Sybase ASE messages have the following
format:
Message ID and text
Explanation
Operator Response
The message ID has the following format:
CCC####severity
where:
CCC Prefix that indicates the component to which the message applies. The
component is one of the following:
IXB General IBM Tivoli Monitoring for Databases: Sybase ASE
messages
AMG IBM Tivoli Monitoring Component Services messages
AMW IBM Tivoli Monitoring messages
#### Number of the message
severity
Severity of the message. There are three levels of severity:
I Informational messages provide feedback about something that
happened in the product or system that might be important. These
messages can provide guidance when you are requesting a specific
action from the product. Informational messages are not
documented in this appendix.
W Warning messages call your attention to an exception condition.
The condition might not be an error but can cause problems if not
resolved.
E Error messages indicate that an action cannot be completed
because of a user or system error. These messages require user
response.
The Text of the message provides a general statement regarding the problem or
condition that occurred. The Explanation provides additional information about the
Appendix E. Problem determination 209
message and what might have caused the condition. The Operator Response
provides actions to take in response to the condition, particularly for error
messages (messages with the ″E″ suffix).
Note: Many message texts and explanations contain variables, such as the specific
name of a server or application. Those variables are represented in this
appendix as symbols, such as ″&1.″ Actual messages contain values for these
variables.
This appendix includes the messages for the following software:
v IBM Tivoli Monitoring for Databases: Sybase ASE
v IBM Tivoli Monitoring Component Services messages
IBM Tivoli Monitoring for Databases: Sybase ASE Messages
IXB0001I Starting Sybase Backup Server.
Explanation: Starting the Sybase Backup Server.
Operator Response: None.
IXB0002E The Sybase Backup Server is already
running.
Explanation: Could not start the Sybase Backup Server
because it was already running
Operator Response: Stop the Sybase Backup Server.
IXB0003I Starting Sybase Adaptive Server.
Explanation: Starting the Sybase Adaptive Server.
Operator Response: None.
IXB0004E The Sybase Adaptive Server is already
running.
Explanation: Could not start the Sybase Adaptive
Server because it was already running
Operator Response: Stop the Sybase Adaptive Server.
IXB0005I Stopping Sybase Backup Server.
Explanation: Stopping the Sybase Backup Server.
Operator Response: None.
IXB0006E Sybase Backup Server is not running.
Explanation: Could not stop the Sybase Backup Server
because it is not running
Operator Response: Start the Sybase Backup Server.
IXB0007I Stopping Sybase Adaptive Server.
Explanation: Stopping the Sybase Adaptive Server.
Operator Response: None.
IXB0008E Sybase Adaptive Server is not running.
Explanation: Could not stop the Sybase Adaptive
Server because it is not running
Operator Response: Start the Sybase Adaptive Server.
IXB0009E The Sybase Adaptive Server needs to be
started first.
Explanation: The Sybase Adaptive Server needs to be
started.
Operator Response: Start the Sybase Adaptive Server.
IXB0010I Starting Sybase Monitor Server.
Explanation: Starting the Sybase Monitor Server.
Operator Response: None.
IXB0011E The Sybase Monitor Server is already
running.
Explanation: Could not start the Sybase Monitor
Server because it was already running
Operator Response: Stop the Sybase Monitor Server.
IXB0012I Stopping Sybase Monitor Server.
Explanation: Stopping the Sybase Monitor Server.
Operator Response: None.
IXB0013E Sybase Monitor Server is not running.
Explanation: Could not stop the Sybase Monitor
Server because it is not running
Operator Response: Start the Sybase Monitor Server.
IXB0014W The Sybase Backup Server is undefined.
Explanation: Could not start the Sybase Backup Server
because it is undefined.
IXB0001I • IXB0014W
210 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Operator Response: Use the Discovery task or the
Modify Object Properties task to define the Sybase
Backup Server.
IXB0015W The Sybase Monitor Server is
undefined.
Explanation: Could not start the Sybase Monitor
Server because it is undefined.
Operator Response: Use the Discovery task or the
Modify Object Properties task to define the Sybase
Monitor Server.
IXB0016E Cannot connect to the Sybase Adaptive
Server.
Explanation: Could not connect to the Sybase
Adaptive Server.
Operator Response: Verify the user id and password
which are used to communicate with the server are
correct.
IXB0017E Error attempting to start Sybase
Adaptive Server.
Explanation: Attempted to start the Sybase Adaptive
Server but received an error.
Operator Response: Try to start the Sybase Adaptive
Server manually on the endpoint system to see more
specific errors. Also check to make sure the Operating
system user id provided has access to the Sybase
installation directory.
IXB0018E Error attempting to start Sybase Backup
Server.
Explanation: Attempted to start the Sybase Backup
Server but received an error.
Operator Response: Try to start the Sybase Backup
Server manually on the endpoint system to see more
specific errors. Also check to make sure the Operating
system user id provided has access to the Sybase
installation directory.
IXB0019E Error attempting to start Sybase Monitor
Server.
Explanation: Attempted to start the Sybase Monitor
Server but received an error.
Operator Response: Try to start the Sybase Monitor
Server manually on the endpoint system to see more
specific errors. Also check to make sure the Operating
system user id provided has access to the Sybase
installation directory.
IXB8000I Task complete.
Explanation: The task completed successfully.
Operator Response: None.
IXB8001E Task failed.
Explanation: A task failed.
Operator Response: See the additional error messages
to determine the exact cause of the error.
IXB8002E The task cannot run on this platform.
Explanation: A task was run on a platform that does
not support the task.
Operator Response: Run the task on a platform that
provides support for this task.
IXB8003E This task must be run against a
managed node.
Explanation: This task makes Tivoli Management
Framework calls such as ’idlcall’. In order to make
these calls, this task must be performed on a managed
node.
Operator Response: Rerun the task selecting a
managed node object as the target.
IXB8004I Component: &1 ( &2 ).
Explanation: The name of the component.
Operator Response: None.
IXB8005E File &1 was not found.
Explanation: A failure occurred when attempting to
use one of the right-click callback functions.
Operator Response: See the additional error messages
to determine the exact cause of the error.
IXB8006E There is no implementation for callback
request &1 .
Explanation: An internal error occurred. The specified
callback request requires an implementation script that
cannot be found.
Operator Response: Examine subsequent error
messages to determine the file name needed and its
location. If possible, replace the file from a backup
copy. If this problem occurred immediately after
product installation, contact IBM Software Support.
IXB0015W • IXB8006E
Appendix E. Problem determination 211
IXB8007E Searching in directory &1 .
Explanation: A failure occurred when attempting to
use one of the right-click callback functions.
Operator Response: See the additional error messages
to determine the exact cause of the error.
IXB8008I Cleaning up the endpoint on which the
object resides.
Explanation: A request was made to cleanup the
endpoint where this object resides. The results of this
request are displayed in this output window.
Operator Response: None.
IXB8009E An error occurred while running task ’
&1 ’ from library ’ &2 ’.
Explanation: An error occurred while running task %1
from task library %2. If Tivoli logging is enabled, the
log file associated with this callback is displayed.
Operator Response: Make sure that Tivoli logging is
enabled. Check the log file for wruntask errors. The
referenced error is near the end of the log file. If this is
not an environment problem, save the log file and
contact IBM Software Support.
IXB8010E An internal error occurred while
displaying output.
Explanation: An internal error occurred while using
the dispout function. The expected output could not be
displayed.
Operator Response: Ensure that Tivoli logging is
enabled. The log file associated with this call will be
displayed. Check for errors associated with the call to
dispout. The referenced error is near the end of the log.
Correct the errors if possible and rerun the request. If
the problem persists, contact IBM Software Support.
IXB8011I Attempting to call the start task.
Explanation: A start task has been executed.
Operator Response: None.
IXB8012I Attempting to call the stop task.
Explanation: A stop task has been executed.
Operator Response: None.
IXB8013E Unrecognized callback request: &1 .
Explanation: An internal error has occurred.
Operator Response: Contact IBM Software Support.
IXB8015E ’SybaseMondispout’ must be run within
a Tivoli callback context.
Explanation: The SybaseMondispout command is a
Tivoli internal command. It was invoked from an
incorrect context.
Operator Response: If this command is being issued
from Tivoli supplied code, contact IBM Software
Support.
IXB8016I SybaseMondispout [-p preface] [-f
file_name] [-c class_name]
Explanation: The SybaseMondispout command is a
Tivoli internal command. It was invoked with incorrect
syntax. The correct syntax is summarized in this usage
message.
Operator Response: If this command is being issued
from Tivoli supplied code, contact IBM Software
Support.
IXB8017E Exception: &1
Explanation: When creating an object, an internal
processing error occurred. This error is a Tivoli
exception. Detailed information about the exception is
provided in %1.
Operator Response: Correct the cause of the
exception, if possible, and rerun the command. If the
problem persists, contact IBM Software Support.
IXB8018E The SybaseMondispout utility could not
open the &1 file.
Explanation: The SybaseMondispout utility was called
with a request to print the contents of file %1, but the
file could not be opened.
Operator Response: Ensure Tivoli logging is enabled.
Check the log file associated with this callback request
to determine the log file name passed to the
SybaseMondispout Determine if there was an
environment error associated with the file. Try
rerunning the callback request. If the problem persists,
contact IBM Software Support.
IXB8019I SybaseMondisptlogs -f file_name -c
class_name
Explanation: The SybaseMondisptlogs command is a
Tivoli internal command. It was invoked with incorrect
syntax. The correct syntax is summarized in this usage
message.
Operator Response: If this command is being issued
from Tivoli supplied code, contact IBM Software
Support.
IXB8007E • IXB8019I
212 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
IXB8020I Displaying Tivoli log files.
Explanation: The callback function for displaying log
files is running.
Operator Response: None.
IXB8021I Log file created: " &1 " .
Explanation: This is an informational message; no
action is required.
Operator Response: None.
IXB8022I No logs available.
Explanation: A request was made to display the list of
log files. No log files were found.
Operator Response: None.
IXB8023E A file must be selected.
Explanation: You have requested to get or delete a log
file, but you did not specify the file name.
Operator Response: Specify a file name and rerun the
request.
IXB8024I Displaying log file " &1 " .
Explanation: A request was made to get a Tivoli log
file. The log file, or errors encountered when retrieving
it, are displayed following this message.
Operator Response: None.
IXB8025E An error occurred while deleting file "
&1 " .
Explanation: A request was made to delete the
specified log file. An error occurred during the delete
processing.
Operator Response: This message is followed by an
error log of the delete function. Examine the error log
to determine the cause of failure and try running the
task again.
IXB8026I File " &1 " deleted.
Explanation: The requested log file has been deleted.
Operator Response: None.
IXB8027I SybaseMonattr [-o owner -d
dialog_name -i dialog_instance] -g
gadget_path -t gadget_type -a
gadget_attribute {new_value | -f
file_name}
Explanation: The SybaseMonattr command is a Tivoli
internal command. It was invoked with incorrect
syntax. The correct syntax is summarized in this usage
message.
Operator Response: If this command is being issued
from Tivoli supplied code, contact IBM Software
Support.
IXB8028I SybaseMondispCreateDialog [-d
dialog_name -c class_name]
Explanation: The SybaseMondispCreateDialog
command is a Tivoli internal command. It was invoked
with incorrect syntax. The correct syntax is summarized
in this usage message.
Operator Response: If this command is being issued
from Tivoli supplied code, contact IBM Software
Support.
IXB8029I Calling &1 on Managed Node &2
Explanation: The SybaseMondispCreateDialog
command is a Tivoli internal command. It was invoked
with incorrect syntax. The correct syntax is summarized
in this usage message.
Operator Response: If this command is being issued
from Tivoli supplied code, contact IBM Software
Support.
IXB8030I Creating object of type: &1
Explanation:
Operator Response: None.
IXB8040I The attempt to send a IBM Tivoli
Enterprise Console event was
unsuccessful.
Explanation: An attempt to send a Tivoli Enterprise
Console notification event failed. The wpostemsg or
postemsg command provided as a prediscovery
prerequisite has failed. The event was not forwarded
and no further attempt will be made to send that Tivoli
Enterprise Console notification event. This failure may
result in a discrepancy between the Tivoli Business
System Manager console and the Tivoli Desktop, such
as the Tivoli Desktop showing more or less product
object icons than the Tivoli Business System Manager
console.
Operator Response: Verify that the required
prediscovery prerequisites have been installed correctly
and are operational. Also ensure that there is not a
network communications problem between the
managed node that executed the task and the TEC
server.
IXB8020I • IXB8040I
Appendix E. Problem determination 213
IXB8041I An error occurred while subscribing
oid= &1 to profile &2 .
Explanation: An attempt to subscribe the discovered
object to a monitor profile has failed.
Operator Response: Retry the operation using the
wsub command. If this fails, contact your Tivoli
Customer Service representative.
IXB8042I Configuration &1 requires a non-blank
value for variable &2 .
Explanation: The variable mentioned in the message
requires a non-blank value.
Operator Response: Ensure that a non-blank value is
entered for this variable.
IXB8043E An error occurred while creating the
object. The class does not exist.
Explanation: A required Tivoli Object class does not
exist. This is probably due to an error during the
installation of the component software or a
communication problem between an endpoint and a
managed node.
Operator Response: Rerun the discover task. If the
message persists, contact your Tivoli Customer Service
Representative.
IXB8044E Configuration name= &1 , label= &2 ,
EP= &3 , policy region= &4
Explanation: This message is accompanied by
additional messages. It provides additional data fields
that are more specific to the accompanied messages.
Operator Response: See the operator response of
additional messages for more information.
IXB8045E An error occurred while creating the
object.
Explanation: An attempt was made to create an object
in the Tivoli database to represent the discovered
application configuration. An error occurred during the
create operation due to a missing object class.
Operator Response: This is most likely caused by an
error that occurred during installation. Check the install
log file for error messages.
IXB8046I Object class, &1 , does not exist.
Explanation: An object class does not exists. This
message is accompanied by additional messages. Please
reference those messages.
Operator Response: Refer to the operator response
section in the accompanying messages. If the problem
persists, contact your Tivoli Customer Service
Representative.
IXB8047E This task requires more input
parameters than were specified.
Explanation: The discover process has detected that
required parameters are missing.
Operator Response: Refer to the Users Guide for the
list of required parameters for the discover process. If
Discover was invoked from the Tivoli Desktop please
contact Tivoli support.
IXB8048I Input arguments are: &1 .
Explanation: This is the list of input arguments that
were send to the discover process.
Operator Response: No action is necessary.
IXB8049E The destination endpoint list is empty.
Explanation: No endpoints are selected to run the
discover process.
Operator Response: Check that endpoints have been
selected for the discover process. If the request is from
the Tivoli Desktop, ensure that endpoints have been
selected. If the request is from the command line,
ensure that endpoints have been requested by
including them in the first parameter. Refer to the
User’s Guide for the syntax of the endpoint parameter.
IXB8050I Configuration: &1 matched on endpoint:
&2
Explanation: This message indicates that this
application configuration was able to match the
discover criteria on the endpoint.
Operator Response: No action is necessary.
IXB8051I Configuration: &1 did not match on
endpoint: &2
Explanation: This message indicates that this
application configuration was unable to match the
discover criteria on the endpoint.
Operator Response: If the result is in error, review the
filter criteria for correctness and ensure that all of the
required components of the application are running.
IXB8052I Application configuration &1 does not
specify any INTERPs that match
endpoint &1
Explanation: This message indicates that the
application configuration list of possible operating
system INTERPS does not match the actual INTERP
value of the endpoint.
IXB8041I • IXB8052I
214 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Operator Response: No action is necessary.
IXB8060I Discovery task summary:
Explanation: This message is the discover summary
results header line. Additional lines will follow this
message that will include additional information about
the discover request.
Operator Response: No action is necessary.
IXB8061I Number of matched configurations : &1
Explanation: This message is part of the discover
summary results. This indicates the number of
application configurations that have matched on the
endpoints selected.
Operator Response: No action is necessary.
IXB8062I Number of non-matched configurations:
&1
Explanation: This message is part of the discover
summary results. This indicates the number of
application configurations that did not match the
endpoints selected.
Operator Response: No action is necessary.
IXB8063I Number of objects created : &1
Explanation: This message is part of the discover
summary results. This indicates the number of
application objects that were created from matched
configurations. These objects may have been created
from the endpoint process.
Operator Response: No action is necessary.
IXB8064I Number of object creation errors : &1
Explanation: This is part of the discover summary
results. This indicates the number of application objects
that failed while attempting to create them.
Operator Response: No action is necessary.
IXB8065I Number of endpoint object creation
errors : &1
Explanation: This message is part of the discover
summary results. This indicates the number of
application objects that failed while attempting to
create them during the endpoint discover process.
Operator Response: If an object should have been
created, then rerun the discover task. Also check that
there is not a communication problem between the
endpoint and its gateway. If the problem persists,
contact Tivoli support.
IXB8066I Number of duplicate objects : &1
Explanation: This message is part of the discover
summary results. This indicates the number of
application objects that already existed. This will occur
if the discover process was rerun.
Operator Response: No response is necessary if the
objects already exist.
IXB8067E At least one selected endpoint failed to
execute the discover task.
Explanation: One or more managed Tivoli endpoints
failed to execute the discover task. This is likely caused
by a network communication problem or the endpoint
is down.
Operator Response: Reference additional output with
this message to determine which endpoint failed.
Check the status of the endpoint using the wep
command. If the endpoint is up, rerun this task. If the
problem persists, contact Tivoli support.
IXB8068E Possible errors on Tivoli endpoint &1 .
Refer to task log for details.
Explanation: The named Tivoli endpoint may not
have executed the discover task. This is could be
caused by a network communication problem or the
endpoint is down.
Operator Response: Check the status of the specified
endpoint using the wep command. If the endpoint is
up, rerun this task. Examine the discover task log for
Tivoli TME® messages pertaining to this endpoint. If
the problem persists, contact Tivoli support.
IXB8069E Discover did not execute on endpoint
&1
Explanation: The named Tivoli endpoint did not
execute the discover task. This is could be caused by a
network communication problem or the endpoint is
down.
Operator Response: Check the status of the specified
endpoint using the wep command. If the endpoint is
up, rerun this task. Examine the discover task log for
Tivoli TME messages pertaining to this endpoint. If the
problem persists, contact Tivoli support.
IXB8070E Discover did not complete on endpoint
&1
Explanation: The named Tivoli endpoint may not
have completed the discovery task. This is could be
caused by an insufficient endpoint task timeout value.
Operator Response: Check the status of the specified
endpoint using the ’wep’ command. If the endpoint is
’up’, rerun this task and specify a greater endpoint task
IXB8060I • IXB8070E
Appendix E. Problem determination 215
timeout value. If the problem persists, contact Tivoli
support.
IXB8071E The prediscovery dependency set push
operation failed on endpoint &1
Explanation: The discover task received an error while
attempting to perform a dependency set push operation
to the named endpoint. Discover is unable to continue
on that endpoint.
Operator Response: This is usually caused by an
incomplete or failed installation of a product. Rerun
this task. If the problem persists, contact Tivoli support.
IXB8072I Attempting to call the status task: &1
Explanation:
Operator Response: None.
IXB8100E Command failed, rc= &1
Explanation: An attempt to run the monitored
program failed with this return code.
Operator Response: Consult the appropriate
documentation for the monitored product.
IXB8201E File &1 does not exist.
Explanation: The specified file does not exist.
Operator Response: Rerun the task specifying a file
that does exist.
IXB8202E Error deleting file: &1 .
Explanation: The specified file does not exist.
Operator Response: Rerun the task specifying a file
that does exist.
IXB8203E An incorrect parameter was passed to
the command. Correct parameters are
’list’, ’delete’, and ’get’.
Explanation: An incorrect parameter was passed to
the command.
Operator Response: Rerun the task specifying the
correct command.
IXB8204I On system &1
Explanation:
Operator Response: None.
IXB8205I File list is:
Explanation:
Operator Response: None.
IXB8206E The command line version of this task
cannot be run against a managed node
object.
Explanation: The task is not supported against a
Managed Node object.
Operator Response: Rerun the task specifying a
different target.
IXB8207W The command line version of this task
is not supported against an endpoint
object. Duplicate logs may appear in the
file list.
Explanation: The correct type of object to run the task
against is an application object.
Operator Response: Rerun the task specifying a
different target.
IXB8300I Forwarding GONE event to Tivoli
Business Systems Manager: &1
Explanation: An attempt will be made to send a
GONE event to the Tivoli Business Systems Manager
for the objects listed.
Operator Response: Verify the object has been deleted
on the Tivoli Business Systems Manager Console.
IXB8301I Forwarding DISCOVER event to Tivoli
Business Systems Manager: &1
Explanation: An attempt will be made to send a
DISCOVER event to the Tivoli Business Systems
Manager for the objects listed.
Operator Response: Verify the object is displayed on
the Tivoli Business Systems Manager Console.
IXB8302I No objects were found to send to Tivoli
Business Systems Manager.
Explanation: No objects were found to send a
DISCOVER event to the Tivoli Business Systems
Manager.
Operator Response: Discover or create objects then
run the task again.
IXB8071E • IXB8302I
216 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
IXB8303E A Tivoli Business Systems Manager
notification event cannot be sent
because Tivoli Business Systems
Manager Event Enablement has not
been installed on the Tivoli Enterprise
Console server.
Explanation: An attempt to forward a Tivoli Business
Systems Manager notification event to Tivoli Business
Systems Manager failed because the prerequisite Tivoli
Business Systems Manager Event Enablement
component has not been installed on the Tivoli
Enterprise Console event server.
Operator Response: Install the Tivoli Business
Systems Manager Event Enablement component on the
Tivoli Enterprise Console event server.
IXB8304E A Tivoli Business Systems Manager
notification event cannot be sent
because Tivoli Business Systems
Manager Event Enablement ihstttec
command has failed with an exit code of
&1 .
Explanation: An attempt to forward a Tivoli Business
Systems Manager notification event to the Tivoli
Business Systems Manager failed because the ihstttec
command provided by the prerequisite Tivoli Business
Systems Manager Event Enablement component has
failed. The event was not forwarded and no further
attempt will be made to forward that Tivoli Business
Systems Manager notification event. This failure may
result in a discrepancy between the Tivoli Business
Systems Manager console and the Tivoli Desktop, such
as the Tivoli Desktop showing more or less product
object icons than the Tivoli Business Systems Manager
console.
Operator Response: Verify that the Tivoli Business
Systems Manager Event Enablement is installed
correctly and is operational. You may need to run the
Tivoli Business Systems Manager Synchronization task
to remove any discrepancy between the Tivoli Business
Systems Manager console and the Tivoli Desktop.
IXB8400I Property list is:
Explanation:
Operator Response: None.
IXB8401I Successfully set &1 = &2
Explanation:
Operator Response: None.
IXB8402E Property &1 does not exist and cannot
be added.
Explanation: This task was attempting to modify a
parameter that does not exist in the object. This task
can only be used to modify existing parameters.
Operator Response: Verify the name of the parameter
you are trying to modify by using the ’list’ option on
this command.
IXB8403E Error setting &1 = &2
Explanation: Failure attempting to change an object’s
properties.
Operator Response: See the additional error messages
to determine the exact cause of the error.
IXB8404E This task requires that ’list’ or ’set’ be
specified as the third parameter.
Explanation: The third parameter of the ’Modify
Object Properties’ task indicates whether the task is
going to list all of the context of the object, or modify
the context of the object. It must be specified on all
invocations of the task.
Operator Response: Rerun the task specifying either
’list’ or ’set’ as the third parameter to the task.
IXB8405E This task must be run against an
application object.
Explanation: This task attempts to list or modify
properties of an application proxy object. When the
task is run, ensure that the target specified for the task
is the correct application proxy object.
Operator Response: Rerun the task specifying the
target to be the correct application object.
IXB8406E ’set’ requires a property name and a
new property value to be passed in.
Explanation: When the ’set’ operation is specified for
this task, the parameter name and new value must be
passed in.
Operator Response: Rerun the task specifying a
parameter name and value.
IXB8407E Read only properties cannot be
modified.
Explanation: The property that is being modified is a
read only property. Read only properties cannot be
modified.
Operator Response: Rerun the task specifying a
differnt parameter.
IXB8303E • IXB8407E
Appendix E. Problem determination 217
IXB8408E An incorrect number of parameters were
passed to the task. The task needs at
least the object type, object label, and
operation type passed as the first three
arguments.
Explanation: The modify object task, which can only
be run from the wruntask CLI, requires an object type
be passed as the first argument, an object label as the
second argument, and the operation type (list, set) as
the third argument. If ’set’ is passed as the operation
type, then two additional arguments of the property
name and the new property value must be passed in.
Operator Response: Rerun the task passing in the
correct parameters.
IXB8409E Incorrect Object Type. Valid types are:
&1
Explanation: An incorrect object type was passed as a
parameter to the task.
Operator Response: Use one of the object types that is
listed in this message.
IXB8410E Unable to find object &1 of type &2
Explanation: An incorrect object label was passed as a
parameter to the task.
Operator Response: Check the name of the object you
want to modify and rerun the task.
IXB8500I Object &1 created successfully.
Explanation:
Operator Response: None.
IXB8501E Error creating object.
Explanation:
Operator Response:
IXB8502E Missing a required parameter. Required
parameters are: &1
Explanation: A required parameter was not passed in
for the object.
Operator Response: Determine which parameter was
missing and rerun the task specifying the parameter
name and value.
IXB8503E The endpoint parameter was not
specified for this task. Please specify -a
ENDPOINT_NAME -a <ENDPOINT
LABEL> on the command.
Explanation:
Operator Response:
IXB8504E The endpoint parameter was not
specified for this task. Please select an
endpoint in the create object dialog.
Explanation: A required parameter was not passed in
for the object.
Operator Response: An endpoint must be chosen
when using this task. Select an endpoint on the next
invocation.
IXB8505E The create object call failed with a
return code of &1 for object name &2 on
endpoint &3 .
Explanation: There was a failure attempting to create
the object.
Operator Response: Check the return codes against
Tivoli Management Framework guides to determine the
error. If the error persists, contact IBM Support.
IXB8506E Returned output from call: &1
Explanation: There was a failure attempting to create
the object.
Operator Response: None
IXB8507W The class object initialization failed.
The dependency set may not have been
pushed to the endpoint.
Explanation: The object was created successfully,
however the call to the init method on the object failed.
This means that the product may or may not have all
of its dependencies on the endpoint.
Operator Response: Contact IBM support.
IXB8600I Cleanup of the endpoint was successful.
Explanation:
Operator Response: None
IXB8601E Cleanup of the endpoint failed.
Explanation:
Operator Response:
IXB8900I Determining the status of object: &1
Explanation:
Operator Response: None.
IXB8901I The object is up.
Explanation:
Operator Response: None.
IXB8408E • IXB8901I
218 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
IXB8902I The object is down.
Explanation:
Operator Response: None.
IXB8903I Object: &1 is in warning state.
Explanation:
Operator Response: None.
IXB8904E Error determining the status of object:
&1
Explanation:
Operator Response:
IBM Tivoli Monitoring Component Services messages
AMG0001E itmcs_util_functions.sh not found.
Explanation: This file was not found.
AMG2112E An internal processing error occurred.
This error is a Tivoli exception. Detailed
information about the exception is
provided in "&1".
Explanation: No more information is available for this
message.
AMG2113E This command must be run within a
Tivoli callback context.
Explanation: No more information is available for this
message.
AMG2114E witmcsdispout utility could not open
file "&1".
Explanation: No more information is available for this
message.
AMG2120I witmcssetdslattr [-o owner -d
dialog_name -i dialog_instance] -g
gadget_path -t gadget_type -a
gadget_attribute new_value
Explanation: No more information is available for this
message.
AMG8002I Preparing rule base.
Explanation: No more information is available for this
message.
AMG8003E Cannot locate rules file "&1".
Explanation: This file cannot be located.
AMG8004E Cannot locate script file "&1".
Explanation: This file cannot be located.
AMG8005E Rule base "&1" does not exist.
Explanation: No more information is available for this
message.
AMG8006E Source rule base "&1" does not exist.
Explanation: No more information is available for this
message.
AMG8007I Created path "&1".
Explanation: No more information is available for this
message.
AMG8008E Error occurred creating path "&1".
Explanation: No more information is available for this
message.
AMG8009I Tivoli Distributed Monitoring classes
already installed.
Explanation: These classes have already been
installed.
AMG8010I IBM Tivoli Monitoring classes not
installed; adding them.
Explanation: No more information is available for this
message.
AMG8011I Rule base "&1" compiled successfully.
Explanation: No more information is available for this
message.
AMG8012E Rule base"&1" did not compile
successfully.
Explanation: No more information is available for this
message.
AMG8013I Rule base "&1" created in "&2".
Explanation: No more information is available for this
message.
IXB8902I • AMG8013I
Appendix E. Problem determination 219
AMG8014E Error occurred creating rule base "&1" in
"&2".
Explanation: No more information is available for this
message.
AMG8015I Rule base "&1" copied to "&2".
Explanation: No more information is available for this
message.
AMG8016E Error occurred copying rule base "&1" to
"&2".
Explanation: No more information is available for this
message.
AMG8017I Imported classes in file "&1" into rule
base "&2".
Explanation: No more information is available for this
message.
AMG8018E Error occurred importing classes in file
"&1" into rule base "&2".
Explanation: No more information is available for this
message.
AMG8019I Replacing rules in file "&1" in rule base
"&2".
Explanation: No more information is available for this
message.
AMG8020I Event source "&1" created as "&2".
Explanation: No more information is available for this
message.
AMG8021E Error occurred creating event source
"&1".
Explanation: No more information is available for this
message.
AMG8022I Event source "&1" already exists.
Explanation: No more information is available for this
message.
AMG8023I Event source "&1" deleted.
Explanation: No more information is available for this
message.
AMG8024E Error occurred deleting event source
"&1".
Explanation: No more information is available for this
message.
AMG8025I Rule base "&1" loaded.
Explanation: No more information is available for this
message.
AMG8026E Error occurred loading rule base "&1".
Explanation: No more information is available for this
message.
AMG8031I Event server stopped.
Explanation: No more information is available for this
message.
AMG8032I Event server started.
Explanation: No more information is available for this
message.
AMG8033E Event server did not start.
Explanation: No more information is available for this
message.
AMG8034E An error occurred stopping event server.
Explanation: No more information is available for this
message.
AMG8035E This task must be run on the event
server.
Explanation: Run this task from the event server.
AMG8036I Configuring the event server.
Explanation: No more information is available for this
message.
AMG8037E Rule base directory "&1" does not exist.
Explanation: No more information is available for this
message.
AMG8038E task_action clone_rulebase
rulebase_name rulebase_path
forward_host forward_port
forward_tbsm restart_action
Explanation: No more information is available for this
message.
AMG8014E • AMG8038E
220 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
AMG8039E Cannot locate baroc file "&1".
Explanation: No more information is available for this
message.
AMG8040I Task completed successfully.
Explanation: No more information is available for this
message.
AMG8102E Rule base "&1" already exists.
Explanation: No more information is available for this
message.
AMG8103E Task received invalid request: &1.
Explanation: No more information is available for this
message.
AMG8104E Rule base path "&1" is invalid.
Explanation: No more information is available for this
message.
AMG8105I Imported rules in file "&1" into rule
base "&2".
Explanation: No more information is available for this
message.
AMG8106E Error occurred importing rules in file
"&1" into rule base "&2".
Explanation: No more information is available for this
message.
AMG8107I Replacing event source "&1".
Explanation: No more information is available for this
message.
AMG8108I Installed rules script "&1".
Explanation: No more information is available for this
message.
AMG8109I Backup file "&1" not replaced.
Explanation: No more information is available for this
message.
AMG8110I Backup file "&1" created.
Explanation: No more information is available for this
message.
AMG8111I Updating file "&1".
Explanation: No more information is available for this
message.
AMG8112E Forwarding host required.
Explanation: No more information is available for this
message.
AMG8113I Creating file "&1".
Explanation: No more information is available for this
message.
AMG8114I Adding forwarding value "&1".
Explanation: No more information is available for this
message.
AMG8115I Updating forwarding value "&1".
Explanation: No more information is available for this
message.
AMG8116I Importing classes.
Explanation: No more information is available for this
message.
AMG8117I Importing rules.
Explanation: No more information is available for this
message.
AMG8118I Installing event sources.
Explanation: No more information is available for this
message.
AMG8119I Installing event processing scripts.
Explanation: No more information is available for this
message.
AMG8134I Configuring event forwarding.
Explanation: No more information is available for this
message.
AMG8135I Activating rule base.
Explanation: No more information is available for this
message.
AMG8039E • AMG8135I
Appendix E. Problem determination 221
AMG8136I Usage: witmcsdispout [-p text] [-f file]
Explanation: No more information is available for this
message.
AMG8137I Installing message catalogs.
Explanation: No more information is available for this
message.
AMG8138I Installing message catalog "&1".
Explanation: No more information is available for this
message.
AMG8139E The rulebase directory "&1" already
exists.
Explanation: Please remove it or choose a different
rulebase name and run the task again.
AMG8140E The specified configuration file "&1"
could not be found.
Explanation: No more information is available for this
message.
AMG8154E The Tmw2k.baroc file provided by IBM
Tivoli Monitoring can not be found.
Explanation: No more information is available for this
message.
AMG100200E %7$s: Could not source a valid auth
key from environment.
Explanation: No more information is available for this
message.
AMG100201E %7$s: Invalid key supplied / sourced.
Explanation: No more information is available for this
message.
AMG100202E %7$s: Could not source a valid OID
from environment.
Explanation: No more information is available for this
message.
AMG100203E %7$s: Could not source the
environment variable ’%8$s’ from the
environment.
Explanation: No more information is available for this
message.
AMG100204E ApplSvcs upcall `%7$s’ failed due to
authentication failure
Explanation: No more information is available for this
message.
AMG8136I • AMG100204E
222 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix F. 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. 2004 223
224 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Appendix G. 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. 2004 225
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.
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 platforms. 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
platform for which the sample programs are written. These examples have not
been 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, DB2, Tivoli, the Tivoli logo, and Tivoli Enterprise Console are
trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both.
BizTalk,, SharePoint, 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.
226 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
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 G. Notices 227
228 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Index
Aaccessibility xii, 223
Application Name parameter 50
Application Unavailable indication 54
attributesApplication Unavailable indication 55
CacheHitRatio Threshold Violation indication 76
DBAllocatedSizeInKB Threshold Violation indication 83
DBIndexSizeInKB Threshold Violation indication 85
DBUnallocatedSizeInKB Threshold Violation indication 87
DBUsedSizeInKB Threshold Violation indication 84
EngineIdleTimeInSeconds Threshold Violation
indication 110
LocksInUse Threshold Violation indication 66
LockWaitTime Threshold Violation indication 64
Maximum Log Bytes Exceeded indication 44
NumberDatabasesOpen Threshold Violation
indication 109
NumberEngineConnections Threshold Violation
indication 112
NumberFreePages Threshold Violation indication 89
NumberOfAvailableLocks Threshold Violation
indication 65
NumberOfDeadlocks Threshold Violation indication 61
NumberOfLockWaits Threshold Violation indication 63
NumberPacketsReceivedPerSecond Threshold Violation
indication 123
NumberPacketsSentPerSecond Threshold Violation
indication 122
NumberServerConnections Threshold Violation
indication 119
NumberServerConnectionsAvailable Threshold Violation
indication 120
NumberTotalPages Threshold Violation indication 88
NumberUsedPages Threshold Violation indication 91
NumberWaitingProcesses Threshold Violation
indication 103
PercentFreeSpace Threshold Violation indication 92
Severity 0 Log Event indication 45
Severity 1 Log Event indication 46
Severity 2 Log Event indication 47
Severity 3 Log Event indication 48
Severity 4 Log Event indication 49
Availability resource modelproblems 203
Bbooks
feedback x
online x
ordering x
see publications xi
built-in problem determination features 191
CCacheHitRatio Threshold Violation indication 76
CacheHitRatio_lowerBound threshold 77
CacheHitRatio_upperBound threshold 77
Check Sybase ASE Server Status taskdescription 146
return codes 147
CIM classes 179
cleaning up data 34
clearing eventsdescription 8
modifying sending 29
collecting data 18
commandsspecial characters xiii
syntax xiii
wdepset 202
wdmcmd -restart 27
wdmcmd -restart -e ep 35
wdmcmd -stop 27
wdmcmd -stop -e ep 35
wdmdistrib 24
wdmeng -delete -e endpoint 27
wdmeng -start 27
wdmeng -stop -e endpoint 27
wdmeng command 27
wdmlseng 26
wgateway 202
wlookup 202
wtdumprl 204
components, environment 3
configuration 5
indications 7
Log Monitor resource model configuration file 182
Configure Event Server taskdescription 148
return codes 150
controlling statistical thresholding 14
conventionstypeface xii
Create Sybase ASE Server Object taskdescription 153
Create SybaseASEServer_IXB Object taskreturn codes 156
creating reports 18, 38
customer supportsee Software Support 207
customizing logging 35
cycle timecustomizing for resource models 28
description 6
Ddata
cleaning up 34
collecting 18
creating reports 18
intervals 35
length of storage 35
logging, description 9
re-training resource model thresholds 34
Data Cache RM resource modeldescription 75
parameters 77
© Copyright IBM Corp. 2004 229
data providersdescription 179
Log Monitor 179
MOF files 179
trace logs 193
DataCacheRM resource modelCacheHitRatio Threshold Violation indication
attributes 76
indicationsCacheHitRatio Threshold Violation 76
DataCacheRM_IXB resource modelindications
list 75
logged data 78
return codes 79
thresholds 77
DBAllocatedSizeInKB Threshold Violation indication 83
DBAllocatedSizeInKB_lowerBound threshold 93
DBAllocatedSizeInKB_upperBound threshold 93
DBIndexSizeInKB Threshold Violation indication 85
DBIndexSizeInKB_lowerBound threshold 94
DBIndexSizeInKB_upperBound threshold 94
DBUnallocatedSizeInKB Threshold Violation indication 87
DBUnallocatedSizeInKB_lowerBound threshold 94
DBUnallocatedSizeInKB_upperBound threshold 94
DBUsedSizeInKB Threshold Violation indication 84
DBUsedSizeInKB_lowerBound threshold 94
DBUsedSizeInKB_upperBound threshold 94
deleting profiles 26
descriptive name threshold 68, 69, 77, 93, 94, 95, 96, 104, 113,
114, 124, 125, 126
detecting problems, modifying resource model values 18
determining which managed resources are monitored 25
determining which resource models are running 25, 38
directory names, notation xiii
Discover taskdescription 157
return codes 161
discovering resources 21
discoveryassigning 21
installation 200
monitoring 200
problems 200
distributing resource models 23
Eeducation
see Tivoli technical training xii
enabling data logging 35
endpointsdetermining which resource models are running 25, 38
EngineIdleTimeInSeconds Threshold Violation indication 110
EngineIdleTimeInSeconds_lowerBound threshold 113
EngineIdleTimeInSeconds_upperBound threshold 113
environmentcomponents 3
features 1
functions 2
monitoring 17
objects 4
environment variables, notation xiii
error codesCheck Sybase ASE Server Status task 147
Configure Event Server task 150
Create SybaseASEServer_IXB Object task 156
error codes (continued)DataCacheRM_IXB resource model 79
Discover task 161
LocksRM_IXB resource model 73
Log Monitor resource model 52
Manage Tivoli Logs task 163
Modify Object Properties task 165
SpaceUsageRM_IXB resource model 100
Start Sybase Adaptive Server task 134
Start Sybase Backup Server task 138
Start Sybase Monitor Server task 142
StateRM_IXB resource model 116
Stop Sybase Adaptive Server task 136
Stop Sybase Backup Server task 140
Stop Sybase Monitor Server task 144
SybaseAvailability_IXB resource model 58
TBSM Synchronization task 168
TrafficRM_IXB resource model 128
WaitsRM_IXB resource model 106
event classes 169
eventsclasses 169
clearingdescription 8
sending 29
customizing for resource models 29
problems 204
relationship to indications 6
rules for 177
severitydescription 8
examining the monitoring environment 17
Ffailures
DependencyMgr problem 202
Endpoint 202
Product not installed on the endpoint gateway 202
features, IBM Tivoli Monitoring for Databases: Sybase ASE 1
filesData provider trace 193
IBM Tivoli Enterprise Console trace 196
installation trace 193
MOF 179
resource model trace 195
rls 177
task trace 196
fixes, obtaining 206
functions, IBM Tivoli Monitoring for Databases: Sybase
ASE 2
Ggathering information 191
HHealth Console
See IBM Tivoli Web Health Console
holesdescription 7
modifying number 29
230 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
IIBM Software Support
gathering information for 191
IBM Tivoli Business Systems Managersending events to 29
TBSM Synchronization task 167
IBM Tivoli Enterprise Consoleevent classes 169
event rules 177
resource model events 7
sending events to 29
IBM Tivoli Monitoring for Databases: Sybase ASEenvironment 3
event rules 177
features 1
functions 2
purposes 17
IBM Tivoli Monitoring Resource Model Builder 5
IBM Tivoli Monitoring Web Health Consoleattribute values for events 203
enabling logging 35
interface for viewing data 36
logging 9
identifying resources 21
indicationsconfiguration 7
customizing for resource models 29
DataCacheRM resource modelCacheHitRatio Threshold Violation 76
DataCacheRM_IXB resource modellist 75
description 6
holesdescription 7
LocksRM resource modelLocksInUse Threshold Violation 66
LockWaitTime Threshold Violation 64
NumberOfAvailableLocks Threshold Violation 65
NumberOfDeadlocks Threshold Violation 61
NumberOfLockWaits Threshold Violation 62
LocksRM_IXB resource modellist 61
Log Monitor resource modellist 44
Maximum Log Bytes Exceeded 44
Severity 0 Log Event 45
Severity 1 Log Event 46
Severity 2 Log Event 47
Severity 3 Log Event 48
Severity 4 Log Event 48
occurrencesdescription 7
recovery tasks 8
sending events to IBM Tivoli Enterprise Console 7
severity, description 8
SpaceUsageRM resource modelDBAllocatedSizeInKB Threshold Violation 83
DBIndexSizeInKB Threshold Violation 85
DBUnallocatedSizeInKB Threshold Violation 87
DBUsedSizeInKB Threshold Violation 84
NumberFreePages Threshold Violation 89
NumberTotalPages Threshold Violation 88
NumberUsedPages Threshold Violation 90
PercentFreeSpace Threshold Violation 92
SpaceUsageRM_IXB resource modellist 82
specifying a task 27
indications (continued)StateRM resource model
EngineIdleTimeInSeconds Threshold Violation 110
NumberDatabasesOpen Threshold Violation 109
NumberEngineConnections Threshold Violation 111
StateRM_IXB resource modellist 109
SybaseAvailability resource modelApplication Unavailable 54
SybaseAvailability_IXB resource modellist 54
TrafficRM resource modelNumberPacketsReceivedPerSecond Threshold
Violation 123
NumberPacketsSentPerSecond Threshold Violation 122
NumberServerConnections Threshold Violation 119
NumberServerConnectionsAvailable Threshold
Violation 120
TrafficRM_IXB resource modellist 119
WaitsRM resource modelNumberWaitingProcesses Threshold Violation 103
WaitsRM_IXB resource modellist 102
information centers, searching to find software problem
resolution 206
installationlog file 193
problems 197
interconnected regionsconfiguring the event server 152
Create SybaseASEServer_IXB Object 156
discover task 161
interface, user 4
Internet, searching to find software problem resolution 206
Kknowledge bases, searching to find software problem
resolution 206
Llegal notices 225
Locks RM resource modeldescription 60
parameters 70
LocksInUse Threshold Violation indication 66
LocksInUse_lowerBound threshold 69
LocksInUse_upperBound threshold 69
LocksRM resource modelindications
LocksInUse Threshold Violation 66
LockWaitTime Threshold Violation 64
NumberOfAvailableLocks Threshold Violation 65
NumberOfDeadlocks Threshold Violation 61
NumberOfLockWaits Threshold Violation 62
LocksInUse Threshold Violation indication attributes 66
LockWaitTime Threshold Violation indication attributes 64
NumberOfAvailableLocks Threshold Violation indication
attributes 65
NumberOfDeadlocks Threshold Violation indication
attributes 61
NumberOfLockWaits Threshold Violation indication
attributes 63
Index 231
LocksRM_IXB resource modelindications
list 61
logged data 71, 72
return codes 73
thresholds 68
LockWaitTime Threshold Violation indication 64
LockWaitTime_lowerBound threshold 69
LockWaitTime_upperBound threshold 68
log filesinstallation 193
location and configuration 192
trace 192
Log Metrics parameter 50
Log Monitor provider 179
Log Monitor resource modelconfiguration file 182
description 43
indicationslist 44
Maximum Log Bytes Exceeded 44
Severity 0 Log Event 45
Severity 1 Log Event 46
Severity 2 Log Event 47
Severity 3 Log Event 48
Severity 4 Log Event 48
logged data 52
Maximum Log Bytes Exceeded indication attributes 44
parameters 49
return codes 52
Severity 0 Log Event indication attributes 45
Severity 1 Log Event indication attributes 46
Severity 2 Log Event indication attributes 47
Severity 3 Log Event indication attributes 48
Severity 4 Log Event indication attributes 49
thresholds 49
Log Name parameter 50
logging 191
Data provider trace logs 193
DataCacheRM_IXB resource model 78
enabling 35
IBM Tivoli Enterprise Console trace logs 196
LocksRM_IXB resource model 71, 72
Log Monitor resource model 52
resource model trace logs 195
resource models, description 9
SpaceUsageRM_IXB resource model 99
StateRM_IXB resource model 116
SybaseAvailability_IXB resource model 55, 56
task trace logs 196
TrafficRM_IXB resource model 128
WaitsRM_IXB resource model 105
LogMonitor Configuration Filename parameter 50
LogMonitorLogname parameter 50
LogMonitorMaxReadBytes threshold 49
LogMonitorMetrics parameter 50
LogMonitorSev0Formats parameter 51
LogMonitorSev1Formats parameter 51
LogMonitorSev2Formats parameter 51
LogMonitorSev3Formats parameter 51
LogMonitorSev4Formats parameter 51
logsSee also data
types 35
MManage Tivoli Logs task
description 162
return codes 163
managed resourcesdescription 1
monitored 25
recovering operation of 27
manualsfeedback x
online x
ordering x
see publications xi
Maximum Log Bytes Exceeded indication 44
Maximum Read Bytes Available Threshold 49
message files 192
messages 191
format 209
overview 208
severity 209
metricsresource models 179
Modify Object Properties taskdescription 164
return codes 165
modifying resource model values to detect problems 18
MOF files 179
monitoringbeginning 17
examining the environment 17
preconfigured resource models 17
restarting 26
stopping 26
Nnotation
environment variables xiii
path names xiii
typeface xiii
NumberDatabasesOpen Threshold Violation indication 109
NumberDatabasesOpen_lowerBound threshold 113
NumberDatabasesOpen_upperBound threshold 113
NumberEngineConnections Threshold Violation
indication 111
NumberEngineConnections_lowerBound threshold 114
NumberEngineConnections_upperBound threshold 114
NumberFreePages Threshold Violation indication 89
NumberFreePages_lowerBound threshold 95
NumberFreePages_upperBound threshold 95
NumberOfAvailableLocks Threshold Violation indication 65
NumberOfAvailableLocks_lowerBound threshold 69
NumberOfAvailableLocks_upperBound threshold 69
NumberOfDeadlocks Threshold Violation indication 61
NumberOfDeadlocks_lowerBound threshold 68
NumberOfDeadlocks_upperBound threshold 68
NumberOfLockWaits Threshold Violation indication 62
NumberOfLockWaits_lowerBound threshold 68
NumberOfLockWaits_upperBound threshold 68
NumberPacketsReceivedPerSecond Threshold Violation
indication 123
NumberPacketsReceivedPerSecond_lowerBound
threshold 126
NumberPacketsReceivedPerSecond_upperBound
threshold 126
232 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
NumberPacketsSentPerSecond Threshold Violation
indication 122
NumberPacketsSentPerSecond_lowerBound threshold 125
NumberPacketsSentPerSecond_upperBound threshold 125
NumberServerConnections Threshold Violation
indication 119
NumberServerConnections_lowerBound threshold 125
NumberServerConnections_upperBound threshold 124
NumberServerConnectionsAvailable Threshold Violation
indication 120
NumberServerConnectionsAvailable_lowerBound
threshold 125
NumberServerConnectionsAvailable_upperBound
threshold 125
NumberTotalPages Threshold Violation indication 88
NumberTotalPages_lowerBound threshold 95
NumberTotalPages_upperBound threshold 95
NumberUsedPages Threshold Violation indication 90
NumberUsedPages_lowerBound threshold 96
NumberUsedPages_upperBound threshold 95
NumberWaitingProcesses Threshold Violation indication 103
NumberWaitingProcesses_lowerBound threshold 104
NumberWaitingProcesses_upperBound threshold 104
Oobjects
discovering resources 21
identifying resources 21
list 4
managed resources 1
overview 4
TBSM Synchronization task 167
occurrencesdescription 7
modifying number 29
online publicationsaccessing xi
operation of resource, recovering 18
operational modes for thresholds 9
ordering publications xi
Pparameters
customizing 31
Data Cache RM resource model 77
description 6
Locks RM resource model 70
Log Monitor resource model 49
Process Waits RM resource model 104
Space Usage RM resource model 96
State RM resource model 114
Sybase Availability resource model 55
Traffic RM resource model 126
path names, notation xiii
PercentFreeSpace Threshold Violation indication 92
PercentFreeSpace_lowerBound threshold 96
PercentFreeSpace_upperBound threshold 96
performance reports 38
preconfigured resource models 17
problem determinationdescribing problem for IBM Software Support 208
determining business impact for IBM Software
Support 207
submitting problem to IBM Software Support 208
problemsAvailability resource model 203
detecting 18
discovery 200
events 204
resource models 201
tasks 203
wtdumprl command 204
problems and workarounds 200
Process Waits RM resource modeldescription 102
parameters 104
profilesdeleting 26
distributing 23
starting 26
stopping 26
providers, data 179
publicationsaccessing online xi
feedback x
online x
ordering x, xi
purposesbeginning monitoring 17
collecting data 18
creating reports 18
examining the monitoring environment 17
modifying resource model values 18
recovering resource operation 18
RRaw Group Retention Count parameter 71, 78, 98, 105, 115,
127
re-training resource model thresholds 34
recovering the operation of a resource 18
recovery tasks, running 27
reportscollecting data 18
creating 18
creating with Tivoli Data Warehouse 38
performance 38
Tivoli Data Warehouse reports 38
resourcerecovering operation 18
resource modeldistribution during discovery 21
Resource Model BuilderSee IBM Tivoli Monitoring Resource Model Builder
resource models 5
Availability 203
clearing eventsdescription 8
modifying 29
configuration 5
customizing 5
cycle time 28
holes 29
indications 29
logging data 35
occurrences 29
parameters 31
severity 29
tasks 27
thresholds 32
Index 233
resource models 5 (continued)cycle time
customizing 28
description 6
Data Cache RMdescription 75
parameters 77
data providers, LogMonitor 179
DataCacheRMCacheHitRatio Threshold Violation indication 76
DataCacheRM_IXBlogged data 78
return codes 79
thresholds 77
details 41
distributing 23
events 6, 29
failing 202
general problems 201
holesdescription 7
modifying 29
IBM Tivoli Enterprise Console 7
indicationscustomizing 29
description 6
listed 41
Locks RMdescription 60
parameters 70
LocksRMLocksInUse Threshold Violation indication 66
LockWaitTime Threshold Violation indication 64
NumberOfAvailableLocks Threshold Violation
indication 65
NumberOfDeadlocks Threshold Violation indication 61
NumberOfLockWaits Threshold Violation indication 62
LocksRM_IXBlogged data 71, 72
return codes 73
thresholds 68
Log Monitor 49
description 43
logged data 52
Maximum Log Bytes Exceeded indication 44
return codes 52
Severity 0 Log Event indication 45
Severity 1 Log Event indication 46
Severity 2 Log Event indication 47
Severity 3 Log Event indication 48
Severity 4 Log Event indication 48
thresholds 49
loggingdescription 9
logging datacustomizing 35
metrics 179
occurrencesdescription 7
modifying 29
overview 5
parameterscustomizing 31
description 6
preconfigured 17
problemsAvailability 203
resource models 5 (continued)Process Waits RM
description 102
parameters 104
recovery tasksdescription 8
running on endpoints 25, 38
scheduling 9
sending eventsIBM Tivoli Enterprise Console 7
severitydescription 8
modifying 29
Space Usage RMdescription 81
parameters 96
SpaceUsageRMDBAllocatedSizeInKB Threshold Violation
indication 83
DBIndexSizeInKB Threshold Violation indication 85
DBUnallocatedSizeInKB Threshold Violation
indication 87
DBUsedSizeInKB Threshold Violation indication 84
NumberFreePages Threshold Violation indication 89
NumberTotalPages Threshold Violation indication 88
NumberUsedPages Threshold Violation indication 90
PercentFreeSpace Threshold Violation indication 92
SpaceUsageRM_IXBlogged data 99
return codes 100
thresholds 93
starting 26
State RMdescription 108
parameters 114
StateRMEngineIdleTimeInSeconds Threshold Violation
indication 110
NumberDatabasesOpen Threshold Violation
indication 109
NumberEngineConnections Threshold Violation
indication 111
StateRM_IXBlogged data 116
return codes 116
thresholds 113
statistical thresholding 34
stopping 26
Sybase Availabilitydescription 54
parameters 55
thresholds 55
SybaseAvailabilityApplication Unavailable indication 54
SybaseAvailability_IXBlogged data 55, 56
return codes 58
taskscustomizing 27
description 8
tasks, specifying 27
thresholdscustomizing 32
description 6
Traffic RMdescription 118
parameters 126
234 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
resource models 5 (continued)TrafficRM
NumberPacketsReceivedPerSecond Threshold Violation
indication 123
NumberPacketsSentPerSecond Threshold Violation
indication 122
NumberServerConnections Threshold Violation
indication 119
NumberServerConnectionsAvailable Threshold Violation
indication 120
TrafficRM_IXBlogged data 128
return codes 128
thresholds 124
values, modifying 18
WaitsRMNumberWaitingProcesses Threshold Violation
indication 103
WaitsRM_IXBlogged data 105
return codes 106
thresholds 104
resourcesdiscovering 21
identifying 21
which ones are monitored 25
response taskSee tasks
restarting monitoring 26
return codesCheck Sybase ASE Server Status task 147
Configure Event Server task 150
Create SybaseASEServer_IXB Object task 156
DataCacheRM_IXB resource model 79
Discover task 161
LocksRM_IXB resource model 73
Log Monitor resource model 52
Manage Tivoli Logs task 163
Modify Object Properties task 165
SpaceUsageRM_IXB resource model 100
Start Sybase Adaptive Server task 134
Start Sybase Backup Server task 138
Start Sybase Monitor Server task 142
StateRM_IXB resource model 116
Stop Sybase Adaptive Server task 136
Stop Sybase Backup Server task 140
Stop Sybase Monitor Server task 144
SybaseAvailability_IXB resource model 58
TBSM Synchronization task 168
TrafficRM_IXB resource model 128
WaitsRM_IXB resource model 106
rls files 177
rules 169
running a task automatically 27
Sscheduling resource models 9
severitydescription 8
modifying level 29
Severity 0 Log Event indication 45
Severity 0 Matching Formats parameter 51
Severity 1 Log Event indication 46
Severity 1 Matching Formats parameter 51
Severity 2 Log Event indication 47
Severity 2 Matching Formats parameter 51
Severity 3 Log Event indication 48
Severity 3 Matching Formats parameter 51
Severity 4 Log Event indication 48
Severity 4 Matching Formats parameter 51
Software Supportcontacting 207
describing problem for IBM Software Support 208
determining business impact for IBM Software
Support 207
submitting problem to IBM Software Support 208
Space Usage RM resource modeldescription 81
parameters 96
SpaceUsageRM resource modelDBAllocatedSizeInKB Threshold Violation indication
attributes 83
DBIndexSizeInKB Threshold Violation indication
attributes 85
DBUnallocatedSizeInKB Threshold Violation indication
attributes 87
DBUsedSizeInKB Threshold Violation indication
attributes 84
indicationsDBAllocatedSizeInKB Threshold Violation 83
DBIndexSizeInKB Threshold Violation 85
DBUnallocatedSizeInKB Threshold Violation 87
DBUsedSizeInKB Threshold Violation 84
NumberFreePages Threshold Violation 89
NumberTotalPages Threshold Violation 88
NumberUsedPages Threshold Violation 90
PercentFreeSpace Threshold Violation 92
NumberFreePages Threshold Violation indication
attributes 89
NumberTotalPages Threshold Violation indication
attributes 88
NumberUsedPages Threshold Violation indication
attributes 91
PercentFreeSpace Threshold Violation indication
attributes 92
SpaceUsageRM_IXB resource modelindications
list 82
logged data 99
return codes 100
thresholds 93
Start Sybase Adaptive Server taskdescription 134
return codes 134
Start Sybase Backup Server taskdescription 138
return codes 138
Start Sybase Monitor Server taskdescription 142
return codes 142
startingprofiles 26
resource models 26
State RM resource modeldescription 108
parameters 114
StateRM resource modelEngineIdleTimeInSeconds Threshold Violation indication
attributes 110
indicationsEngineIdleTimeInSeconds Threshold Violation 110
NumberDatabasesOpen Threshold Violation 109
NumberEngineConnections Threshold Violation 111
Index 235
StateRM resource model (continued)NumberDatabasesOpen Threshold Violation indication
attributes 109
NumberEngineConnections Threshold Violation indication
attributes 112
StateRM_IXB resource modelindications
list 109
logged data 116
return codes 116
thresholds 113
Statistical Minimum Data Required parameter 71, 78, 98, 105,
115, 127
statistical thresholdingre-training resource models 34
Stop Sybase Adaptive Server taskdescription 136
return codes 136
Stop Sybase Backup Server taskdescription 140
return codes 140
Stop Sybase Monitor Server taskdescription 144
return codes 144
stoppingprofiles 26
resource models 26
stopping monitoring 26
Summary Group Retention Count parameter 71, 78, 98, 105,
115, 127
Summary Group Size parameter 71, 78, 98, 105, 115, 127
Sybase Availability resource modeldescription 54
parameters 55
thresholds 55
SybaseAvailability resource modelApplication Unavailable indication attributes 55
indicationsApplication Unavailable 54
SybaseAvailability_IXB resource modelindications
list 54
logged data 55, 56
return codes 58
Ttasks
automaticSee response tasks
Check Sybase ASE Server Statusdescription 146
return codes 147
Configure Event Serverdescription 148
return codes 150
Create Sybase ASE Server Objectdescription 153
Create SybaseASEServer_IXB Objectreturn codes 156
customizing 27
details 131
Discoverdescription 157
return codes 161
discovery 21
general problems 203
tasks (continued)invoking 131
Manage Tivoli Logs 162
return codes 163
Modify Object Propertiesdescription 164
return codes 165
recovery 8
See response tasks
specifying for an indication 27
Start Sybase Adaptive Serverdescription 134
return codes 134
Start Sybase Backup Serverdescription 138
return codes 138
Start Sybase Monitor Serverdescription 142
return codes 142
Stop Sybase Adaptive Serverdescription 136
return codes 136
Stop Sybase Backup Serverdescription 140
return codes 140
Stop Sybase Monitor Serverdescription 144
return codes 144
TBSM Synchronizationdescription 167
return codes 168
TBSM Synchronization taskdescription 167
return codes 168
Threshold CacheHitRatio calculation method parameter 77
Threshold CacheHitRatio relevant time interval(s)
parameter 78
Threshold DBAllocatedSizeInKB calculation method
parameter 96
Threshold DBAllocatedSizeInKB relevant time interval(s)
parameter 96
Threshold DBIndexSizeInKB calculation method
parameter 97
Threshold DBIndexSizeInKB relevant time interval(s)
parameter 97
Threshold DBUnallocatedSizeInKB calculation method
parameter 97
Threshold DBUnallocatedSizeInKB relevant time interval(s)
parameter 97
Threshold DBUsedSizeInKB calculation method parameter 97
Threshold DBUsedSizeInKB relevant time interval(s)
parameter 97
Threshold EngineIdleTimeInSeconds calculation method
parameter 114
Threshold EngineIdleTimeInSeconds relevant time interval(s)
parameter 114
Threshold LocksInUse calculation method parameter 71
Threshold LocksInUse relevant time interval(s) parameter 71
Threshold LockWaitTime calculation method parameter 70
Threshold LockWaitTime relevant time interval(s)
parameter 70
Threshold NumberDatabasesOpen calculation method
parameter 114
Threshold NumberDatabasesOpen relevant time interval(s)
parameter 114
Threshold NumberEngineConnections calculation method
parameter 115
236 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
Threshold NumberEngineConnections relevant time interval(s)
parameter 115
Threshold NumberFreePages calculation method
parameter 97
Threshold NumberFreePages relevant time interval(s)
parameter 97
Threshold NumberOfAvailableLocks calculation method
parameter 70
Threshold NumberOfAvailableLocks relevant time interval(s)
parameter 70
Threshold NumberOfDeadlocks calculation method
parameter 70
Threshold NumberOfDeadlocks relevant time interval(s)
parameter 70
Threshold NumberOfLockWaits calculation method
parameter 70
Threshold NumberOfLockWaits relevant time interval(s)
parameter 70
Threshold NumberPacketsReceivedPerSecond calculation
method parameter 127
Threshold NumberPacketsReceivedPerSecond relevant time
interval(s) parameter 127
Threshold NumberPacketsSentPerSecond calculation method
parameter 126
Threshold NumberPacketsSentPerSecond relevant time
interval(s) parameter 127
Threshold NumberServerConnections calculation method
parameter 126
Threshold NumberServerConnections relevant time interval(s)
parameter 126
Threshold NumberServerConnectionsAvailable calculation
method parameter 126
Threshold NumberServerConnectionsAvailable relevant time
interval(s) parameter 126
Threshold NumberTotalPages calculation method
parameter 97
Threshold NumberTotalPages relevant time interval(s)
parameter 97
Threshold NumberUsedPages calculation method
parameter 97
Threshold NumberUsedPages relevant time interval(s)
parameter 98
Threshold NumberWaitingProcesses calculation method
parameter 104
Threshold NumberWaitingProcesses relevant time interval(s)
parameter 105
Threshold PercentFreeSpace calculation method parameter 98
Threshold PercentFreeSpace relevant time interval(s)
parameter 98
thresholdingSee thresholds
thresholdsconditioning
metrical 10
temporal 10
customizing for resource models 32
DataCacheRM_IXB resource model 77
description 6
fixed 9
LocksRM_IXB resource model 68
Log Monitor resource model 49
operational modes 9
SpaceUsageRM_IXB resource model 93
StateRM_IXB resource model 113
statisticalcontrolling 14
overview 9
thresholds (continued)statistical (continued)
training modes 15
Sybase Availability resource model 55
TrafficRM_IXB resource model 124
WaitsRM_IXB resource model 104
Tivoli Data Warehouse 35
reports 38
Tivoli software information center xi
Tivoli technical training xii
trace logsSee also log files
directories 192
trademarks 226
Traffic RM resource modeldescription 118
parameters 126
TrafficRM resource modelindications
NumberPacketsReceivedPerSecond Threshold
Violation 123
NumberPacketsSentPerSecond Threshold Violation 122
NumberServerConnections Threshold Violation 119
NumberServerConnectionsAvailable Threshold
Violation 120
NumberPacketsReceivedPerSecond Threshold Violation
indication attributes 123
NumberPacketsSentPerSecond Threshold Violation
indication attributes 122
NumberServerConnections Threshold Violation indication
attributes 119
NumberServerConnectionsAvailable Threshold Violation
indication attributes 120
TrafficRM_IXB resource modelindications
list 119
logged data 128
return codes 128
thresholds 124
Training Methodology parameter 71, 78, 98, 105, 115, 127
training, Tivoli technical xii
typeface conventions xii
Uuninstallation problems 197
user interfacesinvoking tasks 131
options 4
Vvalues, modifying resource model 18
variables, notation for xiii
WWaitsRM resource model
indicationsNumberWaitingProcesses Threshold Violation 103
NumberWaitingProcesses Threshold Violation indication
attributes 103
WaitsRM_IXB resource modelindications
list 102
logged data 105
Index 237
WaitsRM_IXB resource model (continued)return codes 106
thresholds 104
wdepset command 202
wdmcmd -restart -e ep command 35
wdmcmd -restart command 27
wdmcmd -stop -e ep command 35
wdmcmd -stop command 27
wdmcmd command 27
wdmdistrib command 24
wdmeng -delete -e endpoint command 27
wdmeng -start command 27
wdmeng -stop -e endpoint command 27
wdmlseng command 26
Web Health ConsoleSee IBM Tivoli Web Health Console
wgateway command 202
wlookup command 202
wtdumprl command 204
238 IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide
����
Printed in USA
GC32-9136-00