Tivoli Manager for Oracle** Reference Guide. Version 2.0

Transcription

1 Tivoli Manager for Oracle** Reference Guide Version 2.0

2

3 Tivoli Manager for Oracle** Reference Guide Version 2.0

4 Tivoli Manager for Oracle** Reference Guide (December 2000) Copyright Notice Copyright IBM Corporation 2000 All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, and TME are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Oracle is a registered trademark of Oracle Corporation. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A.

5 Contents Preface... xi Who Should Read This Guide... xi Prerequisite and Related Documents... xi What This Guide Contains... xii Viewing the Guide Online... xiii Getting Online Help... xiii Typeface Conventions.... xiv Contacting Customer Support... xiv Chapter 1. Introduction... 1 Using the Reference Manual... 2 How this Manual is Organized... 2 Using the Desktop or Command Line Interface... 3 Specifying Path Names... 3 Using the Tivoli Desktop Using the Command Line... 3 Command Line Syntax... 4 Using the waddmon Command... 5 Using the wruntask Command... 5 Script for Creating Sample Monitoring Profiles... 6 Understanding Monitor Output... 6 Using Distributed Monitoring Logging Configuring Distributed Monitoring Logging on the TMR Server Configuring Distributed Monitoring Logging on the Endpoint References to Oracle Commands, Tables, and Logs Chapter 2. Database Monitors Tivoli Manager for Oracle** Reference Guide iii

6 List of OracleDatabaseManager Monitoring Sources Advanced Queue Propagation Status (8i) AQ (Advanced Queue) Schedule Propagation errors (8i) Alerts Archive Free Space Archive Percent Free Space Archive Space (Number of Redo Logs) Archive Used Space Average Message Propagation Rate (across schedule) (8i) Average waiting time of READY messages (8i) Background Dump Space Blocked Transactions Chained Rows (cluster) Chained Rows (table) Currently running Heterogeneous Services (8i) Extents Extents by Tablespace Extents by User Free Space Deficit Free Space Deficit by Tablespace Free Space Deficit by User Free Space Fragmentation Free Space Fragmentation by Tablespace Free Tablespace Free Tablespace by Tablespace Index Statistics Long Running Transactions iv Version 2.0

7 Maximum Extents Maximum Extents by Tablespace Maximum Extents by User NT Service Status Number of Datafiles Rows in DUAL Table SQL Number SQL String Temporary Extents Temporary Extents by Tablespace Temporary Extents by User Total waiting time of READY messages Unix Core Dump Space Unix SQL*Net V1 TCP/IP Listener Unix SQL*Net V2 Listener User Dump Space Chapter 3. Instance Monitors Value Ranges List of OracleInstanceManager Monitoring Sources Active Transactions Any v$lock Any v$sysstat Average Redo Entry Size Block Changes Per Transaction Block Get Rate Buffer Cache Hit Ratio Tivoli Manager for Oracle** Reference Guide v

8 Buffer Cache Hit Ratio (Interval) Buffer Waits Ratio Call Rate Calls Per Transaction Changed Block Ratio Cluster Key Ratio Completed Background Checkpoints Consistent Change Ratio Continued Row Ratio DBWR Checkpoints Dictionary Cache Hit Ratio Dictionary Cache Hit Ratio (Interval) Dispatcher Busy Rate Dispatcher Wait Times DML Locks Ratio Enqueue Timeouts Freelist Waits Ratio Library Cache Hit Ratio Library Cache Hit Ratio (Interval) Lock Hit Ratio Parallel Description Long Table Full Table Scans (Interval) Number of Deadlocks Open Cursors PCM Conversion Waits PCM Lock Conversion Time Percentage of False Pings Physical I/O Reads vi Version 2.0

9 Physical I/O Writes Ping Rate Process Ratio RDBMS State Recursive Call Rate Recursive Calls Recursive To User Calls Ratio Redo Allocation Latch Ratio Redo Copy Latch Ratio Redo Log Space Waits Redo Logs Not Archived Redo Small Copy Ratio Rollback Waits Row Source Ratio Shared Server Process Ratio Shared Server Wait Time Sort Overflow Ratio User Rollback Ratio Chapter 4. Async Monitors List of OracleManagerAsync Monitoring Sources Extents Background and Asynchronous Extents Background Extents Asynchronous Extents by Tablespace Background and Asynchronous Extents by Tablespace Background Extents by Tablespace Asynchronous Extents by User Background and Asynchronous Tivoli Manager for Oracle** Reference Guide vii

10 Extents by User Background Extents by User Asynchronous Free Space Deficit Background and Asynchronous Free Space Deficit Background Free Space Deficit Asynchronous Free Space Deficit by Tablespace Background and Asynchronous Free Space Deficit by Tablespace Background Free Space Deficit by Tablespace Asynchronous Free Space Deficit by User Background and Asynchronous Free Space Deficit by User Background Free Space Deficit by User Asynchronous Index Statistics Background and Asynchronous Index Statistics Background Index Statistics Asynchronous Maximum Extents Background and Asynchronous Maximum Extents Background Maximum Extents Asynchronous Maximum Extents by Tablespace Background and Asynchronous Maximum Extents by Tablespace Background Maximum Extents by Tablespace Asynchronous Maximum Extents by User Background and Asynchronous Maximum Extents by User background Maximum Extents by User Asynchronous SQL Number Background and Asynchronous SQL Number Background SQL Number Asynchronous SQL String Background and Asynchronous SQL String Background SQL String Asynchronous viii Version 2.0

11 Temporary Extents Background and Asynchronous Temporary Extents Background Temporary Extents Asynchronous Temporary Extents by Tablespace Background and Asynchronous Temporary Extents by Tablespace Background Temporary Extents by Tablespace Asynchronous Temporary Extents by User Background and Asynchronous Temporary Extents by User Background Temporary Extents by User Asynchronous Unix SQL*Net V1 TCP/IP Listener Background and Asynchronous 385 Unix SQL*Net V1 TCP/IP Listener Background Unix SQL*Net V1 TCP/IP Listener Asynchronous Unix SQL*Net V2 Listener Background and Asynchronous Unix SQL *Net V2 Listener Background Unix SQL *Net V2 Listener Asynchronous Chapter 5. Tasks List of Tasks by GUI and CLI Names Common Task Dialogs Using the Create a Report File Dialog Using the TEC Dialog ConfigureTECOracle CurrentRunningSQL DisableMonitoring EnableMonitoring Listener Appendix A. Running Tivoli Commands Running Tivoli Commands on UNIX Tivoli Manager for Oracle** Reference Guide ix

12 Running Tivoli Commands on Windows NT Where to Find Additional Information about Shells Establishing the Tivoli Environment within a Shell Setting the Tivoli Environment on UNIX Setting the Tivoli Environment on Windows NT Establishing the Tivoli Environment on an Endpoint Appendix B. Classes of Instance Monitors Cache Monitors Cumulative Monitors Interval Monitors Point-in-Time Monitors Rate-based Monitors Appendix C. Operator Groups (Monitor Triggers) 437 Index x Version 2.0

13 Preface The Tivoli Manager for Oracle Reference Guide provides detailed information about the tasks and monitors for Tivoli Manager for Oracle. Use this manual in conjunction with the Tivoli Manager for Oracle User s Guide. Who Should Read This Guide This manual is intended for system architects (for planning) and system administrators and database administrators (for implementation and operation). Readers should have administrator-level understanding of the Windows NT or UNIX operating system, Tivoli software, and Oracle software. Prerequisite and Related Documents The Tivoli Manager for Oracle User s Guide describes how to install and use Tivoli Manager for Oracle. The Tivoli Manager for Oracle User Management Guide describes how to use the Tivoli Manager for Oracle User Management application to manage Oracle users, roles, and resource profiles for Oracle databases. The Tivoli Framework User s Guide contains more detailed information about profiles and profile management. The Tivoli Framework Planning and Installation Guide contains more detailed information about server and hardware requirements. The Tivoli Framework Reference Guide contains additional information about command line commands, such as the winstall command. The Tivoli Distributed Monitoring User s Guide contains more information about distributed monitoring. Tivoli Manager for Oracle** Reference Guide xi

14 The Tivoli Enterprise Console User s Guide contains more detailed information about using the Tivoli Enterprise Console. The Tivoli Software Installation Service (SIS) User s Guide, Version 4.0contains detailed information about using SIS to install the Tivoli Manager for Oracle software. For information about administering the Oracle server, refer to the Server Administrator s Guide for the relevant version of Oracle. For general information about the Oracle server and how it works, refer to the Server Concepts Manual for the relevant version of Oracle. For descriptions of Structured Query Language (SQL) used to manage information in Oracle databases, refer to the Server SQL Reference for the relevant version of Oracle. What This Guide Contains This guide contains the following sections: Introduction on page 1, describes how the manual is organized. This chapter also describes commands, monitor output, and distributed monitoring logging. Database Monitors on page 13, describes how to use the OracleDatabaseManager monitors to manage different aspects of an Oracle database, such as tablespaces, extents, and archive log space. You can also use the SQL Number, SQL String, and other user-defined monitoring sources. Instance Monitors on page 161, describes how to use the OracleInstanceManager monitors to manage different aspects of an Oracle instance, such as server processes, cache hit ratios, and transactions. Async Monitors on page 303, describes how to use the OracleManagerAsync monitors to manage very large databases. Tasks on page 395, describes how to run the Tivoli Manager for Oracle tasks in the OracleManagerTasks library. xii Version 2.0

15 Running Tivoli Commands on page 425, describes how to run Tivoli commands within shells. Classes of Instance Monitors on page 431, defines the five classes of instance monitors and lists the monitors according to their class. Operator Groups (Monitor Triggers) on page 437, describes the operators that allow you to define the conditions that must occur for a monitor to send an alert. Viewing the Guide Online A PDF file of this manual is provided on the product CD. Use Adobe Acrobat Reader Version 3.0 or later to view and print the manual. Acrobat Reader is available free from Adobe at Acrobat Reader provides navigational features that make accessing the manual more convenient: Navigation: Select View Bookmarks and Page from the menu to see a hierarchical table of contents to the left of the manual pages. Clicking on an item in the contents scrolls the manual to the corresponding page. You can open and close higher levels to show and hide lower levels. Hyperlinks: The table of contents, index, table of entries (tasks or monitors), cross references in text, and entries in the See Also section of the book contain hyperlinks. Click on a link to go to the page it refers to. Search: Choose Tools Find from the menu to search the manual. Getting Online Help Online help has been provided for each task and monitor. The help consists of the reference entry from the Tivoli Manager for Oracle Reference Guide, formatted to be viewed online. Help is available online from the desktop as follows: Tivoli Manager for Oracle** Reference Guide xiii

16 Tasks: In the task argument dialog, click the Task Description button. Monitors: 1. In a profile manager, double-click a profile to open it. 2. In the TME 10 Distributed Monitoring Profile Properties window, click Add Monitor. 3. In the Add Monitor dialog, select the desired collection and monitor, then click the About This Monitor button. Typeface Conventions The guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Commands, keywords, file names, authorization roles, URLs, or other information that you must use literally appear in bold. Names of windows, dialogs, and other controls also appear in bold. Italics Variables and values that you must provide appear in italics. Words and phrases that are emphasized also appear in italics. Bold Italics New terms appear in bold italics when they are defined in the text. Monospace Code examples, output, and system messages appear in a monospace font. Contacting Customer Support If you encounter difficulties with any Tivoli products, you can go to to view the Tivoli Support home page. After you link to and submit the customer registration form, you will be able to access many customer support services on the Web. xiv Version 2.0

17 Use the following phone numbers to contact customer support in the United States: the Tivoli number is (1-800-TIVOLI8) and the IBM number is (press or say 8 after you reach this number). Both of these numbers direct your call to the Tivoli Customer Support Call Center. We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send to pubs@tivoli.com. Tivoli Manager for Oracle** Reference Guide xv

18 xvi Version 2.0

19 1 Introduction 1. Introduction A monitor captures and returns information about a resource or application in the Tivoli management environment, such as the database status or whether or not a server is available. A task is an operation, such as backing up a database, that must be performed routinely on various managed nodes throughout the management environment. The monitors and tasks included with Tivoli Manager for Oracle enable you to manage distributed Oracle computing resources effectively and to the granularity that you need. The set of database management tasks enables you to define operations that can run on any machine without consideration of platform type. These tasks automate repetitive database administrator (DBA) tasks. You can define tasks once and then perform them on multiple servers and databases in a single action. Tivoli Manager for Oracle provides the ability to manage and monitor Oracle databases by providing extensions to the Tivoli Framework, Tivoli Distributed Monitoring, Tivoli Enterprise Console, and Tivoli User Administration. Tivoli Manager for Oracle** Reference Guide 1

20 Using the Reference Manual This section contains information on how to use this reference manual. It includes the following information: How this manual is organized How to use the desktop or command line interface (CLI) How this Manual is Organized The manual is organized alphabetically by task and monitoring collection. Each task or monitor is divided into the following sections: Description. A brief description of the task or monitor. Authorization Role. The permissions an administrator needs to run the task or monitor. Target Endpoint. The Tivoli resource to which a monitor or task is distributed. GUI Data Entry Fields. A description of each field on a specific monitor or task dialog. CLI Syntax. The CLI (command line interface) syntax that corresponds to the GUI Data Entry Fields. This section is provided for users who prefer using the CLI. It includes definitions for each of the arguments and an example of the syntax. CLI Example. An example CLI for configuring the monitor. Suggested Response Levels. The suggested monitor threshold values. For more information, see Setting Up Monitoring Profiles in the Tivoli Manager for Oracle User s Guide. Output. An example output for each task and monitor. Usage Notes. Any additional information about a task or monitor. See Also. A list of related tasks and monitors. 2 Version 2.0

21 Using the Desktop or Command Line Interface You can work with monitors and tasks from both the desktop dialog or the command line (CLI). You may choose to use the desktop when you want to take advantage of visual input prompting, which includes drop-down lists of options and the defaults provided by options such as the Notify TEC button. Use the CLI when you want to create scripts, respond to distributed monitoring monitors, or rapidly enter commands. 1. Introduction Note: The commands in this guide assume a Bourne shell. From a Windows NT command prompt, adjust the command syntax as necessary, or to access a Tivoli-ported version of the Bourne shell, enter the command sh before entering other commands in this chapter. For more information on shells, see Running Tivoli Commands on page 425. Specifying Path Names Depending on the platform on which you run this product, use either forward (/) or backward slashes (\) in path names. Examples in this documentation use both forward and backward slashes. Using the Tivoli Desktop You can set up and run tasks and monitors using the procedures described in the Tivoli Manager for Oracle User s Guide. Each task or monitor in this manual has a section called GUI Data Entry Fields. This section has a screen capture (if applicable) of the dialog that is displayed when you select the task or monitor. Following the screen capture is a detailed explanation of each field and button on the dialog. Using the Command Line You also can run monitors and tasks from the command line instead of the Tivoli desktop. This chapter defines the command syntax and provides a script for creating sample profiles with monitors. For detailed information about Tivoli commands, refer to the UNIX online manual pages or to one of the following manuals: Tivoli Manager for Oracle** Reference Guide 3

22 Tivoli Management Framework Reference Manual Tivoli Enterprise Console Reference Manual Tivoli Distributed Monitoring User s Guide Command Line Syntax This guide uses the following special characters to define the command syntax: [] Identifies optional arguments. Arguments not enclosed in brackets are required.... Indicates that you can specify multiple values for the previous argument. Separate multiple values with a space, unless you are instructed otherwise. Indicates mutually exclusive arguments or responses. You can use the argument to the left of the separator ( ) or the argument to its right. You cannot use both arguments in a single use of the command. {} Delimits a set of mutually exclusive arguments when one of the arguments is required. If the arguments are optional, they are enclosed in [](brackets). <variable> For example: wsetfpprgs { t type T type} [<keyword_option...>] <fp_name> Indicates a variable response, such as the subscriber name or the name of the database you want to monitor. In this example, the t type and T type arguments are mutually exclusive; you must use one or the other. The <keyword_option> argument is an optional argument; you can specify it more than once. The <fp_name> argument is required. 4 Version 2.0

23 Using the waddmon Command You can create a monitor with the waddmon command. Each monitor description in this manual includes a section called CLI Syntax that supplies the arguments for the waddmon command. A section called CLI Example provides an example of how you can enter the waddmon command and the monitoring arguments at the command line. 1. Introduction For more information on the waddmon command, see the Tivoli Management Framework Reference Manual or refer to its manual page. Using the wruntask Command There are a number of commands that you can use to run tasks and jobs from the command line. These include the following: The wruntask command, which you use to run a task from the command line. Because not all customers use the same task library, the documentation for the wruntask command in the Tivoli Management Framework Reference Manual does not provide information for specific tasks, such as those in the Oracle library. Tasks on page 395 includes a CLI Syntax section, which supplies the syntax for tasks in the Oracle library. It also includes a CLI Example section, which provides an example of how to enter the wruntask command and the task arguments at the command line. The wcrtjob command creates a job from a task. See the manual page for this command or the Tivoli Management Framework Reference Manual. The wrunjob command runs a job from the command line. For more information, see the manual page for the wrunjob command or the Tivoli Management Framework Reference Manual. The wschedjob command schedules an existing job. For more information, see the manual page for the wschedjob command or the Tivoli Management Framework Reference Manual. Tivoli Manager for Oracle** Reference Guide 5

24 Script for Creating Sample Monitoring Profiles The Best Practices script (install_oraclebestpractices_monitors.sh) installs a set of preconfigured database and instance monitors. These monitors are a good starting point for setting up Oracle database monitoring. The Best Practices script is described in the Tivoli Manager for Oracle User s Guide. Understanding Monitor Output After a monitor runs on a database, it returns with output information. Although much of this output information is generic, data that is specific to a monitor is described in the Output section for that monitor. Note: The monitor outputs shown in this guide are general examples, and may differ from the outputs you receive in your environment. The following shows an example output of the Extents monitor from the OracleDatabaseManager monitor collection and describes the generic output. Distributed Monitoring chad/extents on host manzana-2 chad is the name of the profile. 6 Version 2.0

25 Extents is the name of the monitor. manzana-2 is the TMA endpoint on which the Oracle database resource resides 03/13/ :06:00 The date and time when the monitor was run. Status The returned response level on which the monitor triggered. Response levels are defined when adding a monitor. Depending on the monitor, response levels may be a default value or a user-defined value. For more information on response levels, see Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Normal is returned only when no severity levels are exceeded and the monitor is set to always return a value. E.EXEC is returned when, based on the value returned by the monitor, a response level cannot be determined. Warning, Severe, orcritical is returned when a severity threshold is broken. Previous The value returned by the preceding monitor probe. For example, if the monitor ran at 4:55 p.m., 5:00 p.m., and 5:05 p.m., the previous value for the 5:05 probe would be that value returned by the 5:00 p.m. probe. 1. Introduction Note: The first time the monitor runs in any monitoring session, this field will have no value and return empty. Current The value returned by the most recent monitor probe. For example, if the monitor last ran at 5:05 p.m., the current value would be that of the 5:05 p.m. probe. Effective For most monitors, this value is the same as the Current value. However, if you are monitoring a trend, for example the percentage change between the Previous and Current Tivoli Manager for Oracle** Reference Guide 7

26 monitor values, the Effective value will be that value as defined when adding the monitor. ORACLE_SID The Oracle Server ID. ORACLE_HOME The location of the Oracle binaries and libraries. HOST The TMA endpoint on which the Oracle database resource resides. ENDPOINT_OID The OracleDatabaseManager or OracleInstanceManager profile endpoint object ID. It is used internally by Tivoli and can be used for tracing activities with this object. INTERP The type of operating system on which the monitor executes, such as Solaris or Windows NT. MONITOR_NUMBER An identifier that is assigned to each monitor. This number is used for the new Distributed Monitoring Logging functionality. TRIGGER_INFO Unless otherwise noted, TRIGGER_INFO is the same data that is returned as the Current value. When it differs, a note under the monitor output tells the significance of TRIGGER_INFO. For example, in the previous monitor output, the TRIGGER_INFO is the object with the greatest number of extents. Userinfo Any additional information returned by the monitor is referred to as userinfo and appears below the TRIGGER_INFO field. For example, in the previous monitor output, the userinfo is the number of extents, object name, object owner, and tablespace name. 8 Version 2.0

27 Using Distributed Monitoring Logging For diagnostic purposes, you may need to view the SQL statement on which a monitor executes. Distributed Monitoring Logging is a tool unique to Tivoli Manager for Oracle that allows you to see the SQL statements of certain monitors. A table at the beginning of each monitoring chapter lists whether or not a monitor is logging enabled. You can configure Distributed Monitoring Logging on the TMR server (if you want to activate every logging-enabled endpoint in the TMR) or on a specific endpoint. The SQL statements for Distributed Monitoring Logging appear in the following directory: 1. Introduction $lcf_datadir/amsmonitorlogging/oraclemanagercollection.log Configuring Distributed Monitoring Logging on the TMR Server The following procedure guides you through editing the OracleManagerCollection.sh script so you can enable distributed monitoring logging on the TMR server. Note: When you distribute to endpoints from the TMR Server, you will overwrite the OracleManagerCollection.sh script on the endpoints on which you re enabling logging. 1. Using a text editor, access the OracleManagerCollection.sh script in the following directory: $BINDIR/../lcf_bundle/generic/OracleManagerMonitoring 2. You can enable logging for all monitors, or for specific monitors. To enable logging for all supported monitors across all Oracle monitoring collections, remove the # character from the following lines: COLLECTION_LOG=1 COLLECTION_LOGGING OR To enable logging to specific monitors, do the following: a. Remove the # character from the following lines: COLLECTION_LOG=1 Tivoli Manager for Oracle** Reference Guide 9

28 COLLECTION_LOGGING LOG_MONITORS= b. Enter the specific monitor number you want to log in the LOG_MONITORS= field. Use spaces to separate monitor numbers. Note: Tivoli assigns each monitor a unique number that appears in the monitor output. In addition, a table at the beginning of each monitor chapter in this reference guide lists monitor numbers and whether the monitor supports Distributed Monitoring Logging. You are now ready to distribute logging from the TMR server to the endpoints. 3. To distribute logging from the TMR Server to the endpoints, you need the OID (object identifier) of the instance objects to which you want to distribute logging. To obtain the OID, do one of the following: a. At the command line, enter wlookup ar OracleInstanceManager to see a list of all instance objects and their OID. OR b. Enter wlookup r OracleInstanceManager <label_of_oracle_instance_object> to choose a specific Oracle instance object. 4. Using the OID you obtained in the previous step, run the idlcall OID InitializeEndpoint command to enable logging on the endpoint. Configuring Distributed Monitoring Logging on the Endpoint 1. Access the $LCF_DATDIR/generic/OracleManagerMonitoring directory on the endpoint on which you want to enable distributed monitor logging. 10 Version 2.0

29 2. Edit the OracleManagerCollection.sh script: a. To enable logging for all supported monitors across all Oracle monitoring collections, remove the # character from in front of the following lines: COLLECTION_LOG=1 export COLLECTION_LOGGING OR 1. Introduction b. To enable logging to specific monitors, remove the # character from in front of the following lines: COLLECTION_LOG=1 export COLLECTION_LOGGING LOG_MONITORS= In the LOG_MONITORS= field, fill in the specific monitor numbers you want to log. Use spaces to separate monitor numbers. Note: Tivoli assigns each monitor a unique number that appears in the monitor output. In addition, a table at the beginning of each monitor chapter in this reference guide lists monitor numbers and whether the monitor supports Distributed Monitoring Logging. References to Oracle Commands, Tables, and Logs This manual refers to Oracle commands, tables, and logs. Although you can use either UPPERCASE, lowercase, or Mixed Case, this manual uses UPPERCASE for Oracle commands, tables, and logs. For additional information on these commands, tables, and logs, refer to the Oracle documentation. Tivoli Manager for Oracle** Reference Guide 11

30 12 Version 2.0

31 2 Database Monitors The OracleDatabaseManager Monitoring Collection provides monitoring sources for managing Oracle databases, including tablespaces, extents, and archive log space. This collection also provides SQL Number, SQL String, and other monitoring sources that you define to create your own Oracle monitoring sources. Profiles containing OracleDatabaseManager monitors should be distributed to Oracle database endpoints. 2. Database Monitors List of OracleDatabaseManager Monitoring Sources The following table lists the monitoring sources in this collection alphabetically by their graphical user interface (GUI) names. It also includes their command line interface (CLI) names, monitor numbers, and whether they support Distributed Monitoring Logging. Monitors that support Distributed Monitoring Logging have a Yes in the Log File column. For more information, see Using Distributed Monitoring Logging on page 9. GUI Name CLI Name Monitor Log File Number Advanced Queue Propagation aqpropagationstatus 122 Yes Status (8i) AQ (Advanced Queue) Schedule Propagation errors (8i) aqschpropagationerrors 123 Yes Alerts alerts 2 No Tivoli Manager for Oracle** Reference Guide 13

32 GUI Name CLI Name Monitor Log File Number Archive Free Space archivespace 5 No Archive Percent Free Space archivespacepercent 200 No Archive Space (Number of archivespacerl 75 No Redo Logs) Archive Used Space archiveusedspace 72 No Average Message Propagation aqpropagationrate 121 Yes Rate (across schedule) (8i) Average waiting time of avgwaittimereadymsg 124 Yes READY messages (8i) Background Dump Space backgrounddumpspace 7 No Blocked Transactions blockedtransaction 131 Yes Chained Rows (cluster) chainedclus 14 No Chained Rows (table) chainedrows 15 No Currently running heterogeneousservices 129 Yes Heterogeneous Services (8i) Extents extents 69 Yes Extents by Tablespace extentsbytablespace 70 Yes Extents by User extentsbyuser 71 Yes Free Space Deficit freespacedef 27 Yes Free Space Deficit by freespacedeft 81 Yes Tablespace Free Space Deficit by User freespacedefu 80 Yes Free Space Fragmentation freespacefragmentation 28 Yes Free Space Fragmentation by tfreespacefragmentation 56 Yes Tablespace Free Tablespace freetablespace 29 Yes Free Tablespace by Tablespace freetablespacet 61 Yes Index Statistics indexstatistics 150 No Long Running Transactions longrunningtransaction 130 Yes Maximum Extents maximumextents 34 Yes 14 Version 2.0

33 GUI Name CLI Name Monitor Log File Number Maximum Extents by maximumextentst 66 Yes Tablespace Maximum Extents by User maximumextentstu 67 Yes NT Service Status ntservicestatus 65 No Number of Datafiles numberoffiles 35 Yes Rows in DUAL Table rowsindual 50 Yes SQL Number freeformsqln 30 Yes SQL String freeformsqls 31 Yes Temporary Extents temporaryextents 57 Yes Temporary Extents by temporaryextentst 58 Yes Tablespace Temporary Extents by User temporaryextentsu 68 Yes Total waiting time of READY totwaittimereadymsg 125 Yes messages Unix Core Dump Space coredumpspace 62 No Unix SQL*Net V1 TCP/IP netonetcpip 54 No Listenerr Unix SQL*Net V2 Listener nettwolistener 55 No User Dump Space userdumpspace 59 No 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 15

34 Advanced Queue Propagation Status (8i) Description Monitors the number of messages in a user-specified queue that are in one of the following states: WAITING, READY or EXPIRED. This monitor checks on the progress of a queue s propagation. It shows any anomalies caused by the network or with the destination to which the queue is attempting to propagate. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add monitor to TME10 Distributed Monitoring Profile dialog for the Advanced Queue Propagation Status monitor; a description of each field follows. Status Specifies the appropriate message status that is to be monitored. If you do not select a message status from the dropdown list, the monitor defaults to EXPIRED status. Queue Name Determines which objects are to be checked. If you leave this field blank, the monitor checks all queues. CLI Syntax aqpropagationstatus a {READY WAITING EXPIRED} a <queue_name> 16 Version 2.0

35 CLI Example The following briefly describes the arguments for this monitor. {READY WAITING EXPIRED} Specifies the appropriate message status that is to be monitored. GUI Name: Status <queue_name> Determines which objects are to be checked. If you leave this field blank, the monitor checks all queues. GUI Name: Queue Name waddmon OracleDatabaseManager aqpropagationstatus -a READY -a MESSAGE_QUEUE_1 -t 1 hours -c critical -R > 100 -n OracleManager Sentry -c always -f "manzana:/data/monitor_output/oracle/message_status.log" "ProfileName" Suggested Response Levels There are no default actions for this monitor. 2. Database Monitors Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. The TRIGGER_INFO line for this monitor s output contains the total number of messages per queue that were in the user-specified state (WAITING, READY, or EXPIRED) when the monitor triggered. The total number of messages is followed by a list of all the queues that have messages in the user-specified state. Queues with the greatest number of messages in the user-specified state appear at the top of the list. The information for all queues is reported as text on the userinfo lines, in the following format: Queue Name, Message Status, Number of Messages Tivoli Manager for Oracle** Reference Guide 17

36 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_QUEUES GV$AQ Usage Notes If too many messages return in the READY state, the monitor shows an anomaly with the message processing. This might be caused by a known outage, but if not, the DBA should be alerted that there is a problem. Note: For more accurate propagation results, run this monitor with the Average Message Propagation Rate (across schedule) (8i) monitor and the AQ (Advanced Queue) Schedule Propagation errors (8i) monitor. See Also The following monitors in this chapter: Average Message Propagation Rate (across schedule) (8i) and AQ (Advanced Queue) Schedule Propagation errors (8i). 18 Version 2.0

37 AQ (Advanced Queue) Schedule Propagation errors (8i) Description Monitors messages that could not be propagated and have been recorded as errors. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add monitor to TME 10 Distributed Monitoring Profile dialog for the AQ Schedule Propagation Errors monitor; a description of each field follows. 2. Database Monitors Queue Name Determines which objects are to be checked. If you leave this field blank, the monitor checks all queues. CLI Syntax aqschpropagationerrors a <queue_name> The following briefly describes the argument for this monitor. <queue_name> Determines which objects are to be checked. If you leave this field blank, the monitor checks all queues. GUI Name: Queue Name Tivoli Manager for Oracle** Reference Guide 19

38 CLI Example waddmon OracleDatabaseManager aqschpropagationerrors -a MESSAGE_QUEUE_1 -t 1 hours -c critical -R > 1 -n OracleManager Sentry -c always -f "manzana:/data/monitor_output/oracle/dangling_refs.log" "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. The TRIGGER_INFO line for this monitor s output contains the total number of propagation errors found within the user-specified message queue. The total number of propagation errors is followed by a list of columns that contain the errors and their details. Queues with the most propagation errors appear at the top of the list. The information for all propagation errors is reported as text on the userinfo lines, in the following format: Error Count, Queue Name, Destination, Failures, Error Date, Error Time, Error Message For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_QUEUE_SCHEDULES Usage Notes When a message cannot be propagated, it is recorded as an error in a table. 20 Version 2.0

39 This monitor displays any of these error messages that are associated with the user-specified queue or, if no queue is specified, all the queues in the schedule. Error messages will apply only to enabled queues or queues that have been disabled due to a maximum number of failures. This monitor determines any errors or delays with messages propagating from one application to another. Errors in message propagation can indicate problems with the enqueue or dequeue process or other issues, such as network problems. See Also The following monitors in this chapter: Advanced Queue Propagation Status (8i) and Average Message Propagation Rate (across schedule) (8i). 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 21

40 Alerts Description Monitors the alert log for Oracle errors. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax alerts CLI Example waddmon OracleDatabaseManager alerts -t 1 hours -c critical -R == 1 -n OracleManager Sentry -c severe -R == 2 -n OracleManager Sentry -c warning -R == 3 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Any Oracle error in Send OracleManager Sentry Group 1 notice 22 Version 2.0

41 Severity Trigger When Default Actions Severe Any Oracle error in Send OracleManager Sentry Group 2 notice Warning Any Oracle error in Group 3 Normal N/A None Always N/A None Send OracleManager Sentry notice Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 5 minutes. The following shows an example output from this monitor. 2. Database Monitors The TRIGGER_INFO line contains the latest error of the highest severity found in the alert log. If no error was found, the TRIGGER_INFO line is left blank. The userinfo line reports the BACKGROUND_DUMP_DEST. For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 23

42 Views Accessed None Usage Notes This monitor checks the alert log for the following errors: Note: Any ORA- errors not explicitly stated in the following list are treated as group 4 errors and are ignored unless you change one of the thresholds to include those errors. Group 1 (Critical) ORA-0204 error in reading control file ORA-0206 error in writing control file ORA-0210 cannot open control file ORA-0257 archiver is stuck ORA-0333 redo log read error ORA-0345 redo log write error ORA-0440 ORA-0485 background process failure ORA-0600 ORA-0639 internal errors ORA-1114 datafile I/O write error ORA-1115 datafile I/O read error ORA-1116 cannot open datafile ORA-1118 cannot add a data file ORA-1578 data block corruption Group 2 (Severe) ORA-1135 file accessed for query is offline ORA-1547 tablespace is full ORA-1555 snapshot too old ORA-1562 failed to extend rollback segment ORA-1628 ORA-1632 maximum extents exceeded ORA-1650 ORA-1656 tablespace is full ORA-4031 out of shared memory. Group 3 (Warning) 24 Version 2.0

43 ORA-3113 end of file on communication channel ORA-6501 PL/SQL internal error cannot allocate new log - this error indicates that Oracle is unable to perform a log switch. Increase the number of redo logs to resolve this problem. Group 4 (Others) Any other ORA- error If the monitor reports any errors, check the ALERT log and any associated trace files for the instance. The Oracle ALERT log is named alertsid.log on UNIX (sidalrt.log on Windows NT). It is located in the directory specified by the init.ora parameter BACKGROUND_DUMP_DEST, which defaults to $ORACLE_HOME/rdbms/log on UNIX (\ORANT\RDBMSnn on Windows NT, where nn is the release number of Oracle). The monitor only reports an error once and only checks for new entries in the ALERT log the next time the monitor is run. 2. Database Monitors The Alerts monitor will be enhanced in a future release to enable users to add their own alerts to the list of monitors. See Also The following monitors in this chapter: Archive Free Space, Archive Space (Number of Redo Logs), Archive Used Space, Free Space Deficit, Free Tablespace, Maximum Extents, NT Service Status, Number of Datafiles, and Temporary Extents. Tivoli Manager for Oracle** Reference Guide 25

44 Archive Free Space Description Monitors the amount of free space (in kilobytes) on the archive destination device. The destination device is controlled by the LOG_ARCHIVE_DEST parameter in the init.ora file for the instance. This monitor is only applicable when the database is running in ARCHIVELOG mode. If the database is running in NOARCHIVELOG mode, the monitor returns a value of zero. Use the LOG_ARCHIVE_DEST parameter in the init.ora file for the instance to specify the location of the archiving device. Note: This monitor does not support the evaluation of free space when archiving to tape. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax archivespace CLI Example waddmon OracleDatabaseManager archivespace -t 1 hours -c critical -R < n OracleManager Sentry -c severe -R < n OracleManager Sentry -c warning -R < n OracleManager Sentry -c normal -c always "ProfileName" 26 Version 2.0

45 Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. 2. Database Monitors The percent used figure is reported as text on the userinfo lines in the following format: Available KB, % Free, %Used, MountPoint For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes If the archive process cannot archive a redo log because of insufficient space on the destination device, the database hangs until Tivoli Manager for Oracle** Reference Guide 27

46 space is made available. When necessary, back up existing archive logs and remove the files from the destination device to make room for the next archived redo log. See Also The following monitors in this chapter: Archive Used Space and Archive Percent Free Space. The following monitor in the OracleInstanceManager Monitoring Collection: Average Redo Entry Size. 28 Version 2.0

47 Archive Percent Free Space Description Monitors the percent of free space on the archive destination device. The destination device is controlled by the LOG_ARCHIVE_DEST parameter in the init.ora file for the instance. This monitor is only applicable when the database is running in ARCHIVELOG mode. If the database is running in NOARCHIVELOG mode, the monitor returns a value of zero. Use the LOG_ARCHIVE_DEST parameter in the init.ora file for the instance to specify the location of the archiving device. Note: This monitor does not support the evaluation of free space when archiving to tape. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax archivespacepercent CLI Example waddmon OracleDatabaseManager archivespacepercent -t 1 minutes -c critical -R < 15 -n OracleManager Sentry -c severe -R < 20 -n OracleManager Sentry -c warning -R < 25 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 29

48 Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 15 Send OracleManager Sentry notice Severe Less than 20 Send OracleManager Sentry notice Warning Less than 25 Send OracleManager Sentry notice Normal N/A None Always N/A None Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. The percent-used figure is reported as text on the userinfo lines in the following format: Available KB, %Free, %Used, MountPoint For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

49 Views Accessed None Usage Notes If the archive process cannot archive a redo log because of insufficient space on the destination device, the database hangs until space is made available. When necessary, back up existing archive logs and remove the files from the destination device to make room for the next archived redo log. See Also The following monitor in this chapter: Archive Used Space and Archive Free Space. The following monitor in the OracleInstanceManager Monitoring Collection: Average Redo Entry Size. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 31

50 Archive Space (Number of Redo Logs) Description Monitors the space available, in kilobytes, in the LOG_ARCHIVE_DEST directory to determine how many additional redo logs can be created before the disk is full. This monitor is only applicable when the database is running in ARCHIVELOG mode. If the database is running in NOARCHIVELOG mode, the monitor returns a value of 100. Use the LOG_ARCHIVE_DEST parameter in the init.ora file for the instance to specify the location of the archiving device. Note: This monitor does not support the evaluation of free space when archiving to tape. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax archivespacerl CLI Example waddmon OracleDatabaseManager archivespacerl -t 1 hours -c critical -R < 3 -n OracleManager Sentry -c severe -R < 5 -n OracleManager Sentry -c warning -R < 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli 32 Version 2.0

51 Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 3 logs Send OracleManager Sentry notice Severe Less than 5 logs Send OracleManager Sentry notice Warning Less than 10 logs Send OracleManager Sentry notice Normal N/A None Always N/A None Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. 2. Database Monitors The path name of the archive directory appears in the TRIGGER_INFO field. Additional information for this monitor is reported as text on the userinfo lines in the following format: Available KB, MaxRedoLogSizeBytes, MountPoint Tivoli Manager for Oracle** Reference Guide 33

52 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes If the archive process cannot archive a redo log because of insufficient space on the destination device, the database will hang until space is made available. When necessary, back up existing archive logs and remove the files from the destination device to make room for the next archived redo log. See Also The following monitors in this chapter: Archive Used Space. The following monitor in the OracleInstanceManager Monitoring Collection: Average Redo Entry Size. 34 Version 2.0

53 Archive Used Space Description Monitors the space, in kilobytes, used by archived redo logs in the LOG_ARCHIVE_DEST directory. This monitor is only applicable when the database is running in ARCHIVELOG mode. If the database is running in NOARCHIVELOG mode, the monitor returns a value of zero. This monitor can be used to indicate how fast redo logs are being archived and when they should be backed up to tape or another disk on the local system or on a remote system. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax archiveusedspace CLI Example waddmon OracleDatabaseManager archiveusedspace -t 1 hour -c critical -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. 2. Database Monitors Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Tivoli Manager for Oracle** Reference Guide 35

54 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes None See Also The following monitors in this chapter: Archive Space (Number of Redo Logs). The following monitor in the OracleInstanceManager Monitoring Collection: Average Redo Entry Size. 36 Version 2.0

55 Average Message Propagation Rate (across schedule) (8i) Description Monitors the number of bytes-per-second that have been propagated over all enabled schedules or over a particular queue in a user-specified schedule. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add monitor to TME 10 Distributed Monitoring Profile dialog for the Average Message Propagation Rate monitor. A description of each field follows. 2. Database Monitors Queue Name The name of the queue to be monitored. If this field is left blank, the monitor checks every schedule. CLI Syntax aqpropagationrate a <queue_name> The following briefly describes the argument for this monitor. <queue_name> The name of the queue to be monitored. If this field is left blank, the monitor checks every schedule. GUI Name: Queue name Tivoli Manager for Oracle** Reference Guide 37

56 CLI Example waddmon OracleDatabaseManager aqpropagationrate -a MESSAGE_QUEUE_1 -t 1 hours -c critical -R < n OracleManager Sentry -c severe -R < n OracleManager Sentry -c warning -R < n OracleManager Sentry -c always -f "manzana:/data/monitor_output/oracle/prop_rate.log" "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. The TRIGGER_INFO line for this monitor s output contains the lowest propagation rate of messages on which the monitor triggered. This is followed by a list of user-specified message queues and their respective propagation rates. The queues with the lowest propagation rate appear at the top. The information for all message queues is reported as text on the userinfo lines, in the following format: Propagation Rate, Queue Name, Propagation Destination For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_QUEUE_SCHEDULES Usage Notes Output from this monitor can be used to tune the various parameters in the schedule and ensure that the schedule is optimized. For example, if a queue should propagate data at a certain rate, the user 38 Version 2.0

57 can run the monitor on a regular basis and alert the DBA if propagation falls below the normal rate. A drop in propagation rate can indicate network problems with operations between instances. See Also The following monitors in this chapter: Advanced Queue Propagation Status and AQ Schedule Propagation Errors. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 39

58 Average waiting time of READY messages (8i) Description Monitors the number of messages in the READY state in each queue, and the average waiting time of each message in days, hours, minutes, or seconds. This monitor can be used to find out if messages have been waiting for an inordinate amount of time and if there are potential performance bottlenecks. Messages in the READY state are available for propagation across schedules as soon as a dequeue operation is started. A queue with multiple messages in the READY state can indicate problems with the dequeue process or problems with the queue destination. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add monitor to TME 10 Distributed Monitoring Profile dialog for the Average waiting time of READY messages (8i) monitor; a description of each field follows. Queue Name The name of the queue to be monitored. If this is left blank, the monitor executes on the entire database. Time Interval This interval can be set for days (D), hours (H), minutes (M), or seconds (S). 40 Version 2.0

59 CLI Syntax avgwaittimereadymsg a <queue_name> a {D H M S} CLI Example The following briefly describes the arguments for this monitor. <queue_name> The name of the queue to be monitored. If this is left blank, the monitor executes on the entire database. GUI Name: Queue Name {D H M S} The time interval can be set for days (D), hours (H), minutes (M), or seconds (S). GUI Name: Time Interval waddmon OracleDatabaseManager avgwaittimereadymsg -a MESSAGE_QUEUE_1 -a S -t 1 hours -c critical -R > 1 -n OracleManager Sentry -c always -f "manzana:/data/monitor_output/oracle/dangling_refs.log" "ProfileName" Suggested Response Levels There are no default actions for this monitor. 2. Database Monitors Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. The TRIGGER_INFO line for this monitor s output contains the longest average waiting time for READY messages on which the monitor triggered. It is followed by a list of columns that contain Tivoli Manager for Oracle** Reference Guide 41

60 queue names and the average waiting times of the messages currently in the READY state. Queue names with the longest average waiting times appear at the top of the list. The information for all waiting messages is reported as text on the userinfo lines, in the following format: Queue Name, Average Wait Time, Number of READY Messages For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_QUEUES GV$AQ Usage Notes None See Also The following monitors in this chapter: Average Message Propagation Rate (across schedule) (8i) and AQ (Advanced Queue) Schedule Propagation errors (8i). 42 Version 2.0

61 Background Dump Space Description Monitors the percentage of the allocated space that is used on the background dump destination device. The destination device is controlled by the BACKGROUND_DUMP_DEST parameter in the init.ora file for the instance. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax backgrounddumpspace CLI Example waddmon OracleDatabaseManager backgrounddumpspace -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 2. Database Monitors Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 85% Send OracleManager Sentry notice Normal N/A None Tivoli Manager for Oracle** Reference Guide 43

62 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. The percent-used figure is reported as text on the userinfo lines, in the following format: Available KB, %Used, MountPoint For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes Oracle writes to the alert log and creates trace files for the background processes in the BACKGROUND_DUMP_DEST directory. If this parameter is not set in the init.ora file, the trace files are stored in $ORACLE_HOME/rdbms/log on a UNIX system (\ORANT\RDBMSnn\TRACE on a Windows NT system, 44 Version 2.0

63 where nn is the release of Oracle). If this directory is full, Oracle will be unable to create these files, which might result in instance failure and will make debugging more difficult. See Also The following monitor in this chapter: Alerts. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 45

64 Blocked Transactions Description Monitors whether any transactions are locked by another user, and returns the longest time, in seconds, that a transaction has been blocked. Transactions can become blocked when a user writes freeform SQL that is not optimized or that locks itself and other users. Blocked transactions can also occur when users connect to the system, run some SQL, and do not commit or roll back their transactions, thus stopping others from operating certain tasks on the objects. When configuring the monitor, you should specify an acceptable time limit in seconds that a transaction should wait for an unreleased lock before the monitor triggers. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax blockedtransaction CLI Example waddmon OracleDatabaseManager blockedtransaction -t 30 minutes -c critical -R > 60 -n OracleManager Sentry -c severe -R > 30 -n OracleManager Sentry -c warning -R > 15 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli 46 Version 2.0

65 Output Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 60 seconds Severe Greater than 30 seconds Warning Greater than 15 seconds Normal N/A None Always N/A None Send OracleManager Sentry notice Send OracleManager Sentry notice Send OracleManager Sentry notice Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. 2. Database Monitors Results from this monitor are reported as text on the userinfo lines in the following format: Waiting Time, Username, SID, Object, Lock_ID, SQL Tivoli Manager for Oracle** Reference Guide 47

66 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SQLTEXT V$SESSION V$ACCESS V$LOCK Usage Notes None See Also The following monitor in this chapter: Long Running Transactions. The following monitor in the OracleInstanceManager Monitoring Collection: Any v$lock. 48 Version 2.0

67 Chained Rows (cluster) Description Monitors the number of chained rows calculated for a specified cluster in the endpoint database. Chaining occurs when rows are updated and become too large to be stored on a single Oracle datablock. Chained rows double the amount of I/O required to retrieve data and should be avoided. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add monitor to TME 10 Distributed Monitoring Profile dialog for the Chained rows (Cluster) monitor; a description of each field follows. 2. Database Monitors Cluster Name Designates the schema and cluster name of the cluster the monitor checks for chained rows. CLI Syntax chainedclus a <cluster_name> The following briefly describes the argument for this monitor. <cluster_name> Designates the schema and cluster name of the cluster the monitor checks for chained rows. Tivoli Manager for Oracle** Reference Guide 49

68 CLI Example GUI Name: Cluster Name waddmon OracleDatabaseManager chainedclus -a finance.cluster_account -t 1 hours -c critical -R > 5 -n OracleManager Sentry -c severe -R > 3 -n OracleManager Sentry -c warning -R > 0 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 5 Send OracleManager Sentry notice Severe Greater than 3 Send OracleManager Sentry notice Warning Greater than 0 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every day. 50 Version 2.0

69 Output The following shows an example output from this monitor. The user-specified argument appears as TRIGGER_INFO. The trigger value is repeated as userinfo. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes If chaining is occurring for a cluster, consider recreating the cluster with a larger SIZE parameter. See the Cluster Key Ratio monitor in the OracleInstanceManager collection for further information on this parameter. 2. Database Monitors To run this monitor, there must be a CHAINED_ROWS table to store the information. This is created by running $ORACLE_HOME/rdbms/admin/utlchain.sql as the Oracle user SYS. Note: Chaining is unavoidable if a table has a LONG column or if a row is larger than a block in size (known as a spanned row). Tivoli Manager for Oracle** Reference Guide 51

70 See Also The following monitor in this chapter: Chained Rows (table). 52 Version 2.0

71 Chained Rows (table) Description Monitors the number of chained rows, calculated for a specified table in the endpoint database. Chaining occurs when rows are updated and become too large to be stored on a single Oracle datablock. Chained rows double the amount of I/O required to retrieve data and should be avoided. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Chained rows (Table) monitor; a description of each field follows. 2. Database Monitors Table Name Designates the schema and table name to check for chained rows. CLI Syntax chainedrows a <table_name> The following briefly describes the argument for this monitor. <table_name> Specifies the schema and table name of the table to check for chained rows. Tivoli Manager for Oracle** Reference Guide 53

72 CLI Example GUI Name: Table Name waddmon OracleDatabaseManager chainedrows -a scott.emp -t 1 hours -c critical -R > 5 -n OracleManager Sentry -c severe -R > 3 -n OracleManager Sentry -c warning -R > 0 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 5 Send OracleManager Sentry notice Severe Greater than 3 Send OracleManager Sentry notice Warning Greater than 0 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every day. 54 Version 2.0

73 Output The following shows an example output from this monitor. The user-specified argument appears as TRIGGER_INFO. The trigger value is repeated as userinfo. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes This monitor should be run at non-peak times because it issues an ANALYZE TABLE LIST CHAINED ROWS command, which performs a full-table scan and could have a performance impact if the table is large. This command does not generate statistics for the table and does not affect the Oracle optimizer. 2. Database Monitors If the total number of chained rows is small in comparison to the total number of rows on the table, chaining can be corrected through a copy-out/copy-in sequence for the chained rows (an example of how to do this follows). If there are a considerable number of chained rows, export the data, drop and re-create the table with a larger pctfree storage clause, and then import the data. Tivoli Manager for Oracle** Reference Guide 55

74 To run this monitor, there must be a CHAINED_ROWS table to store the information on the chained rows. This is created by running $ORACLE_HOME/rdbms/admin/utlchain.sql as the Oracle user SYS. Note that chaining is unavoidable if a table has a LONG column or if a row is larger than a block in size (known as a spanned row). The copy-out and copy-in sequence to eliminate chained rows is as follows: 1. ANALYZE TABLE INVOICES LIST CHAINED ROWS; 2. SELECT OWNER_NAME, TABLE_NAME, HEAD_ROWID, TIMESTAMP FROM CHAINED_ROWS WHERE TABLE_NAME = INVOICES ; Owner_name Cluster_name Head_ROWID Timestamp DBMX INVOICES 00000D9E AUG-95 DBMX INVOICES 00000D9E.004E AUG-95 DBMX INVOICES 00000D9E.005C AUG-95 DBMX INVOICES 00000D9E.006A AUG Create an intermediate table to hold the chained rows CREATE TABLE INV_TEMP AS SELECT * FROM INVOICES WHERE ROWID IN (SELECT HEAD_ROWID FROM CHAINED_ROWS WHERE TABLE_NAME = INVOICES ); 4. Delete the chained rows from the existing table. DELETE FROM INVOICE WHERE ROWID IN (SELECT HEAD_ROWID FROM CHAINED_ROWS WHERE TABLE_NAME = INVOICES ); 5. Insert the rows of the intermediate table into the existing table. INSERT INTO INVOICES SELECT * FROM INV_TEMP; 6. Drop the intermediate table. DROP TABLE INV_TEMP; 7. Clean out the CHAINED_ROWS table. 56 Version 2.0

75 DELETE FROM CHAINED_ROWS WHERE TABLE_NAME = INVOICES ; Repeat step 1 to verify that the rows have been unchained. See Also The following monitor in this chapter: Chained Rows (cluster). 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 57

76 Currently running Heterogeneous Services (8i) Description Heterogeneous services connect Oracle and non-oracle systems. This monitor looks at the heterogeneous services accessing the Oracle instance at the monitoring interval and reports how long the service has been running. The monitor enables the user to filter on a particular service. If no filter is entered, the monitor triggers on all services. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Currently running Heterogeneous Services monitor; a description of each field follows. Service Name The name of the heterogeneous service on which the monitor reports. If this parameter is omitted, the monitor reports on all currently active heterogeneous services. CLI Syntax heterogeneousservices a <service_name> The following briefly describes the argument for this monitor. 58 Version 2.0

77 CLI Example <service_name> The name of the heterogeneous service on which the monitor reports. If this parameter is omitted, the monitor reports on all currently running heterogeneous services. GUI Name: Service Name waddmon OracleDatabaseManager heterogeneousservices -a Faustina -t 1 minutes -c critical -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. 2. Database Monitors Results from this monitor are reported as text on the userinfo lines in the following format: Session ID, Oracle Username, OS Username, OS Program_name, Agent Type, Agent Program, Running Time For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$HS_SESSION V$SESSION Tivoli Manager for Oracle** Reference Guide 59

78 Usage Notes None See Also None V$HS_AGENT 60 Version 2.0

79 Extents Description Monitors the number of extents allocated to all objects and reports the largest number of extents found. The monitor also reports all objects that have more extents than the number specified as the <numberofextents> argument to the monitor. It does not check objects of segment_type CACHE. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Extents monitor; a description of each field follows. 2. Database Monitors CLI Syntax extents Extents Greater Than Specifies a threshold number of extents. a <numberofextents> The following briefly describes the argument for this monitor. <numberofextents> Specifies the threshold number of extents. GUI Name: Extents Greater Than Tivoli Manager for Oracle** Reference Guide 61

80 CLI Example waddmon OracleDatabaseManager extents -a 20 -t 30 minutes -c critical -R > 30 -n OracleManager Sentry -p Root_jpc_at_home-region -c severe -c warning -R > 20 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. The object with the greatest number of extents appears in the TRIGGER_INFO field. Information for all extents within the specified extents limit is reported as text on the userinfo lines, in the following format: 62 Version 2.0

81 Number of Extents, Object Name, Object Owner, Tablespace Name Note: Objects are displayed in descending order based on number of extents. If Oracle does not return any rows, it reports an error. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes You can use this monitor to see which objects in a database have a large number of extents. This information can be used to chart the growth of objects. This information also can be used in conjunction with the Maximum Extents monitors to predict when an object is going to run out of extents. You might need to allocate additional extents to the object, or export it and recreate it with a larger extent size. See Also The following monitors in this chapter: Extents by Tablespace, Extents by User, Maximum Extents, Maximum Extents by Tablespace, and Maximum Extents by User. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 63

82 Extents by Tablespace Description Monitors how many extents are allocated to all database objects within specified tablespaces and reports the largest number of extents found. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Extents by tablespace monitor; a description of each field follows. Extents Greater Than Specifies the threshold number of extents. Include/Exclude Includes or excludes the contents of the tablespace names field. Tablespace Names Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the 64 Version 2.0

83 CLI Syntax extentsbytablespace appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. a <numberofextents> a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. <numberofextents> Specifies the threshold number of extents. GUI Name: Extents Greater Than {in not in} Includes or excludes the contents of the tablespace names field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Names 2. Database Monitors CLI Example Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. waddmon OracleDatabaseManager extentsbytablespace -a 0 -a in Tivoli Manager for Oracle** Reference Guide 65

84 -a RBS -t 30 minutes -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. The object with the greatest number of extents appears in the TRIGGER_INFO field. Information for all extents within the specified extents limit is reported on the userinfo lines, in the following format: Number of Extents, Object Name, Object Owner Note: Objects are displayed in descending order based on number of extents. If Oracle does not return any rows, it reports an error. 66 Version 2.0

85 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes You can use this monitor to see which objects in a database have a large number of extents. This information can be used to chart the growth of objects. This information also can be used in conjunction with the Maximum Extents monitors to predict when an object is going to run out of extents. You might need to allocate additional extents to the object, or export it and recreate it with a larger extent size. See Also The following monitors in this chapter: Extents, Extents by User, Maximum Extents, Maximum Extents by Tablespace, and Maximum Extents by User. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 67

86 Extents by User Description Monitors how many extents have been allocated to all database objects for a specified user and reports the largest number of extents found. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Extents by user monitor; a description of each field follows. Extents Greater Than Specifies the threshold number of extents. User Name Specifies the Oracle user name. CLI Syntax extentsbyuser a <numberofextents> a <username> The following briefly describes the arguments for this monitor. <numberofextents> Specifies the threshold number of extents. 68 Version 2.0

87 CLI Example GUI Name: Extents Greater Than <username> Specifies the Oracle user name. GUI Name: User waddmon OracleDatabaseManager extentsbyuser -a 50 -a sys -t 30 minutes -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 69

88 The object with the greatest number of extents appears in the TRIGGER_INFO field. Information for all extents within the specified extents limit is reported as text on the userinfo lines, in the following format: Number of Extents, Object Name, Tablespace Name Note: Objects are displayed in descending order based on number of extents. If Oracle does not return any rows, it reports an error. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes You can use this monitor to see which objects in a database have a large number of extents. This information can be used to chart the growth of objects. This information also can be used in conjunction with the Maximum Extents monitors to predict when an object is going to run out of extents. You might need to allocate additional extents to the object, or export it and recreate it with a larger extent size. See Also The following monitors in this chapter: Extents, Extents by Tablespace, Maximum Extents, Maximum Extents by Tablespace, and Maximum Extents by User. 70 Version 2.0

89 Free Space Deficit Description Checks whether any segments are unable to allocate their next extent because of insufficient free space in the tablespace, and not because the segments reached MAXEXTENTS. The reported trigger value represents the worst-case equity (available space less required space); a negative equity figure means that the next extent for that segment will fail. It does not check objects of segment_type CACHE. If the Exclude Rollback Segments argument is set to Yes, the monitor does not check the free space in any rollback segments. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space deficit monitor; a description of each field follows. 2. Database Monitors Exclude Rollback Segments Yes ignores rollback segments. No does not ignore rollback segments. CLI Syntax freespacedef a {Yes No} The following briefly describes the argument for this monitor. Tivoli Manager for Oracle** Reference Guide 71

90 CLI Example {Yes No} Yes ignores rollback segments. No does not ignore rollback segments. GUI Name: Exclude Rollback Segments waddmon OracleDatabaseManager freespacedef -a No -t 1 hours -c critical -R < 0 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 0 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 30 minutes. 72 Version 2.0

91 Output The following shows an example output from this monitor. The object with the worst-case equity is reported as TRIGGER_INFO. Additional information for all objects returned appears as text in the userinfo lines in the following format: 2. Database Monitors Equity, Object Name, Tablespace Name, Object Owner For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS DBA_FREE_SPACE Usage Notes A table is created with an initial extent of 1 MB, next extent 1 MB, and PCTINCREASE of 25%. If the table grows to six extents, the extent sizes are as follows: Extent Number Extent Size (bytes) 1 1,024,000 Tivoli Manager for Oracle** Reference Guide 73

92 Extent Number Extent Size (bytes) 2 1,024, ,280, ,600, ,000, ,500,000 The size of the seventh extent is 3,125,000 bytes. If the free space in the tablespace is 3 MB (3,072,000 bytes), the table will not be able to allocate its seventh extent. The equity is (3,072,000-3,125,000) = -53,000 bytes. This is the figure that is checked by the monitor. If a segment is unable to allocate another extent, there are a number of corrective actions you can take: add another file to the relevant tablespace, change the size of the next extent using ALTER TABLE ALLOCATE EXTENT, or export the segment and recreate it with different storage parameters. Tivoli recommends that all segments be created with a PCTINCREASE of 0. See Also The following monitors in this chapter: Free Space Deficit by Tablespace, Free Space Deficit by User, Free Tablespace, and Number of Datafiles. 74 Version 2.0

93 Free Space Deficit by Tablespace Description Checks whether any segments, within specified tablespaces, are unable to allocate their next extent because of insufficient free space in the tablespace, and not because the segments reached MAXEXTENTS. The reported trigger value represents the worst-case equity (available space less required space); a negative equity figure means that the next extent for that segment will fail. The monitor does not check objects of segment_type CACHE. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space deficit by tablespace monitor; a description of each field follows. 2. Database Monitors Include/Exclude Includes or excludes the contents of the tablespace names field. Tablespace Names Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may Tivoli Manager for Oracle** Reference Guide 75

94 CLI Syntax freespacedeft CLI Example a {in not in} a <tablespaces> slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace names field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Names Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. waddmon OracleDatabaseManager freespacedeft -a in -a users system -t 1 hours -c critical -R < 0 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" 76 Version 2.0

95 Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Output Severity Trigger When Default Actions Critical Less than 0 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 77

96 The object with the worst-case equity for the specified tablespaces is reported as TRIGGER_INFO. Additional information for all objects returned appears as text in the userinfo lines in the following format: Equity, Object Name, Object Owner For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS DBA_FREE_SPACE Usage Notes A table is created with an initial extent of 1 MB, next extent 1 MB, and PCTINCREASE of 25%. If the table grows to six extents, the extent sizes are as follows: Extent Number Extent Size (bytes) 1 1,024, ,024, ,280, ,600, ,000, ,500,000 The size of the seventh extent is 3,125,000 bytes. If the free space in the tablespace is 3 MB (3,072,000 bytes), the table will not be able to allocate its seventh extent. The equity is (3,072,000-3,125,000) = -53,000 bytes. This is the figure that is checked by the monitor. If a segment is unable to allocate another extent, there are a number of corrective actions you can take: add another file to the relevant tablespace, change the size of the next extent using ALTER TABLE ALLOCATE EXTENT, or export the segment and recreate it with different storage parameters. Tivoli recommends that all segments be created with a PCTINCREASE of Version 2.0

97 See Also The following monitors in this chapter: Free Space Deficit, Free Space Deficit by User, Maximum Extents by Tablespace, and Free Tablespace. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 79

98 Free Space Deficit by User Description Checks whether any segments, for a specified user, are unable to allocate their next extent because of insufficient free space in the tablespace, and not because the segments reached MAXEXTENTS. The reported trigger value represents the worst-case equity (available space less required space); a negative equity figure means that the next extent for that segment will fail. The monitor does not check objects of segment_type CACHE. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space deficit by user monitor; a description of each field follows. User Name Specifies the Oracle user name. CLI Syntax freespacedefu a <username> The following briefly describes the argument for this monitor. <username> Specifies the Oracle user name. 80 Version 2.0

99 CLI Example GUI Name: User Name waddmon OracleDatabaseManager freespacedefu -a SCOTT -t 1 hours -c critical -R < 0 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 0 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None 2. Database Monitors Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 30 minutes. Tivoli Manager for Oracle** Reference Guide 81

100 Output The following shows an example output from this monitor. The object with the worst-case equity for the specified user is reported as TRIGGER_INFO. Additional information for all objects returned appears as text in the userinfo lines in the following format: Equity, Object Name, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS DBA_FREE_SPACE Usage Notes A table is created with an initial extent of 1 MB, next extent 1 MB, and PCTINCREASE of 25%. If the table grows to six extents, the extent sizes are as follows: Extent Number Extent Size (bytes) 1 1,024, ,024, Version 2.0

101 Extent Number Extent Size (bytes) 3 1,280, ,600, ,000, ,500,000 The size of the seventh extent is 3,125,000 bytes. If the free space in the tablespace is 3 MB (3,072,000 bytes), the table will not be able to allocate its seventh extent. The equity is (3,072,000-3,125,000) = -53,000 bytes. This is the figure that is checked by the monitor. If a segment is unable to allocate another extent, there are a number of corrective actions you can take: add another file to the relevant tablespace, change the size of the next extent using ALTER TABLE ALLOCATE EXTENT, or export the segment and recreate it with different storage parameters. Tivoli recommends that all segments be created with a PCTINCREASE of 0. See Also The following monitors in this chapter: Free Space Deficit, Free Space Deficit by Tablespace, Maximum Extents by User, and Free Tablespace. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 83

102 Free Space Fragmentation Description Monitors the free space fragmentation index for all tablespaces. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax freespacefragmentation CLI Example waddmon OracleDatabaseManager freespacefragmentation -t 1 hours -c critical -R < 10 -n OracleManager Sentry -c severe -R < 20 -n OracleManager Sentry -c warning -R < 30 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 10 Send OracleManager Sentry notice Severe Less than 20 Send OracleManager Sentry notice Warning Less than 30 Send OracleManager Sentry notice Normal N/A None Always N/A None 84 Version 2.0

103 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Once every day. The following shows an example output from this monitor. 2. Database Monitors The tablespace with the worst-case Free Space Fragmentation Index (FSFI) appears as TRIGGER_INFO. The information for all tablespaces is reported as text on the userinfo lines, in the following format: FSFI, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_FREE_SPACE Usage Notes This monitor employs an arbitrary scoring system to establish whether a tablespace is in need of a free-space rebuild. The system used is that defined by Loney in Oracle DBA Handbook by Oracle Tivoli Manager for Oracle** Reference Guide 85

104 Press, ISBN The Free Space Fragmentation Index (FSFI) calculates the size of the largest extent as a percentage of the total free space and does not consider the number of extents in a tablespace. This index is not a monitor of the amount of free space available. It is an indication of the structure of the free space. For details on monitoring free space in a database, see Free Tablespace on page 91. The best-case response from this monitor is 100%. As the total number of extents increases for a tablespace, the FSFI rating drops accordingly. Use this monitor with the always and Log To File option to establish a base line. In general, a tablespace with sufficient free space and an FSFI rating of above 30 should not experience free space availability problems. See Also The following monitors in this chapter: Free Space Fragmentation by Tablespace and Free Tablespace. 86 Version 2.0

105 Free Space Fragmentation by Tablespace Description Monitors the free space fragmentation index for specified tablespaces. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space fragmentation by tablespace monitor; a description of each field follows. 2. Database Monitors Include/Exclude Includes or excludes the contents of the tablespace names field. Tablespace Names Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. Tivoli Manager for Oracle** Reference Guide 87

106 CLI Syntax tfreespacefragmentation CLI Example a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace names field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Names Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. waddmon OracleDatabaseManager tfreespacefragmentation -a not in -a users system -t 1 hours -c critical -R < 10 -n OracleManager Sentry -c severe -R < 20 -n OracleManager Sentry -c warning -R < 30 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 88 Version 2.0

107 Severity Trigger When Default Actions Critical Less than 10 Send OracleManager Sentry notice Severe Less than 20 Send OracleManager Sentry notice Warning Less than 30 Send OracleManager Sentry notice Normal N/A None Always N/A None Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every day. The following shows an example output from this monitor. 2. Database Monitors This monitor returns the worst-case Free Space Fragmentation Index (FSFI) for the specified tablespaces. The specified tablespaces appear as TRIGGER_INFO for this monitor. Additional information for all specified tablespaces is reported as text on the userinfo lines, in the following format: FSFI Tivoli Manager for Oracle** Reference Guide 89

108 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_FREE_SPACE Usage Notes This monitor employs an arbitrary scoring system to establish if a tablespace is in need of a free space rebuild. The system used is that defined by Loney in Oracle DBA Handbook by Oracle Press, ISBN This Free Space Fragmentation Index (FSFI) calculates the size of the largest extent as a percentage of the total free space and does not consider the number of extents in a tablespace. It should be noted that this index is not a monitor of the amount of free space available. It is an indication of the structure of the free space. The best-case response from this monitor is 100%. As the total number of extents increases for a tablespace, the FSFI rating drops accordingly. Use this monitor with the always and Log To File option to establish a base line. In general, a tablespace with sufficient free space and an FSFI rating of above 30 should not experience free space availability problems. See Also The following monitors in this chapter: Free Space Fragmentation and Free Tablespace. 90 Version 2.0

109 Free Tablespace Description Monitors the percentage of free space in all tablespaces in a database. The monitor reports percent-free figure for a worst-case tablespace. If the Exclude TS With Rollback Segments argument is set to Yes, the monitor does not check the free space in any tablespaces that contain rollback segments. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free tablespace monitor; a description of each field follows. 2. Database Monitors Exclude TS With Rollback Segments Yes ignores tablespaces that contain rollback segments. No includes tablespaces that contain rollback segments. CLI Syntax freetablespace a {Yes No} The following briefly describes the argument for this monitor. {Yes No} Specifies whether tablespaces that contain rollback segments should be ignored. Tivoli Manager for Oracle** Reference Guide 91

110 CLI Example GUI Name: Exclude TS With Rollback Segments waddmon OracleDatabaseManager freetablespace -a No -t 10 minutes -c critical -R < 5 -n OracleManager Sentry -c severe -R < 10 -n OracleManager Sentry -c warning -R < 20 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 5% Send OracleManager Sentry notice Severe Less than 10% Send OracleManager Sentry notice Warning Less than 20% Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 10 minutes. 92 Version 2.0

111 Output The following shows an example output from this monitor. The percent-free figures for all tablespaces are reported as text on the userinfo lines, in the following format: 2. Database Monitors %Free, MB Free, MB Allocated, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_DATA_FILES DBA_FREE_SPACE Usage Notes A database always contains the SYSTEM rollback segment in the SYSTEM tablespace, so if Exclude TS With Rollback Segments is set to Yes, the SYSTEM tablespace will not be checked. When free space becomes low in a tablespace, either add a new datafile to the offending tablespace or drop unwanted database objects. Tivoli Manager for Oracle** Reference Guide 93

112 With Oracle Version 7.2 and higher, it is possible for datafiles to be automatically extended using the following SQL command: ALTER TABLESPACE tsname ADD DATAFILE file AUTOEXTEND ON; See Also The following monitors in this chapter: Free Space Deficit, Free Tablespace by Tablespace, Maximum Extents, and Number of Datafiles. 94 Version 2.0

113 Free Tablespace by Tablespace Description Monitors the percentage of free space for the specified tablespaces. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free tablespace by tablespace monitor; a description of each field follows. 2. Database Monitors Include/Exclude Includes or excludes the contents of the tablespace names field. Tablespace Names Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. Tivoli Manager for Oracle** Reference Guide 95

114 CLI Syntax freetablespacet CLI Example a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace names field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Names Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. waddmon OracleDatabaseManager freetablespacet -a in -a system -t 10 minutes -c critical -R < 5 -n OracleManager Sentry -c severe -R < 10 -n OracleManager Sentry -c warning -R < 20 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. 96 Version 2.0

115 Output The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 5% Send OracleManager Sentry notice Severe Less than 10% Send OracleManager Sentry notice Warning Less than 20% Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. 2. Database Monitors The percent-free figure for the specified tablespaces is reported as text on the userinfo lines, in the following format: Tablespace Name, File ID, Bytes Allocated, Bytes Free, % Free Tivoli Manager for Oracle** Reference Guide 97

116 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_TABLESPACES DBA_DATA_FILES DBA_FREE_SPACE Usage Notes When free space becomes low in a tablespace, either add a new datafile to the offending tablespace or drop unwanted database objects. With Oracle Version 7.2 and higher, it is possible for datafiles to be automatically extended using the following SQL command: ALTER TABLESPACE tsname ADD DATAFILE file AUTOEXTEND ON; See Also The following monitors in this chapter: Free Space Deficit, Free Tablespace, Maximum Extents, and Number of Datafiles. 98 Version 2.0

117 Index Statistics Description Monitors the percentage of deleted rows from the user-specified index that have not been repopulated. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Index statistics monitor; a description of each field follows. 2. Database Monitors Index Name The name of the index to be monitored. CLI Syntax indexstatistics CLI Example a <index_name> The following briefly describes the argument for this monitor. <index_name> The name of the index to be monitored. GUI Name: Index name waddmon OracleDatabaseManager indexstatistics -a SCOTT.PK_DEPT -t 1 hours Tivoli Manager for Oracle** Reference Guide 99

118 -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. Index information is reported as text on the userinfo lines, in the following format: Index Name, % deleted For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed INDEX_STATS 100 Version 2.0

119 Usage Notes The percentage of space used by an index determines if it needs to be rebuilt or coalesced. To prevent uneven growth of indexes, run this monitor on indexes that will be inserted to and deleted from frequently. See Also None 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 101

120 Long Running Transactions Description This monitor can indicate possible issues and bottlenecks in the SQL or database design. The monitor can be used to determine the identity of long-running transactions and how long those transactions have been running. Set up the response level thresholds to suit your particular environment. Note: If a batch process occurs while this monitor is scheduled, the thresholds might not be valid during the time when the batch process is running. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax longrunningtransaction CLI Example waddmon OracleDatabaseManager longrunningtransaction -t 1 minutes -c critical -R > 180 -c severe -R > 120 -c warning -R > 60 -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 102 Version 2.0

121 Output Severity Trigger When Default Actions Critical Greater than 180 seconds Severe Greater than 120 seconds Warning Greater than 60 seconds Normal N/A None Always N/A None Send OracleManager Sentry notice Send OracleManager Sentry notice Send OracleManager Sentry notice Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Site specific. The following shows an example output from this monitor. 2. Database Monitors Information returned by this monitor is reported on the userinfo lines, in the following format: Time Running, SID, Serial #, Username, SQL Tivoli Manager for Oracle** Reference Guide 103

122 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SESSION V$SQLTEXT V$TRANSACTION Usage Notes None See Also The following monitors in the OracleInstanceManager Monitoring Collection: Active Transactions, Block Get Rate, and Buffer Waits Ratio. 104 Version 2.0

123 Maximum Extents Description This monitor returns the smallest number of free extents found for a segment. This monitor also checks how close each object is to the value of MAXEXTENTS and reports the number of extents that can still be allocated. It does not check objects of segment_type CACHE. If the Exclude Rollback Segments argument is set to Yes, the monitor does not check the number of extents in any rollback segments. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Maximum extents monitor; a description of each field follows. 2. Database Monitors Exclude Rollback Segments Yes ignores rollback segments; No does not ignore rollback segments. CLI Syntax maximumextents a {Yes No} The following briefly describes the argument for this monitor. Tivoli Manager for Oracle** Reference Guide 105

124 CLI Example {Yes No} Yes ignores rollback segments. No does not ignore rollback segments. GUI Name: Exclude Rollback Segments waddmon OracleDatabaseManager maximumextents -a No -t 1 hours -c critical -R < 1 -n OracleManager Sentry -c severe -R < 3 -n OracleManager Sentry -c warning -R < 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 1 Send OracleManager Sentry notice Severe Less than 3 Send OracleManager Sentry notice Warning Less than 5 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every hour. 106 Version 2.0

125 Output The following shows an example output from this monitor. The segment with the smallest number of free extents is reported as TRIGGER_INFO. The free extents for additional segments are listed in ascending order in the userinfo lines, in the following format: 2. Database Monitors Free Extents, Segment Name, Tablespace Name, Object Owner, Segment Type For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter and the object needs to allocate an additional extent, the operation will fail. If the value of MAXEXTENTS is less than the maximum allowable (see the Tivoli Manager for Oracle** Reference Guide 107

126 following table), increase the value of MAXEXTENTS. Otherwise, export the object, drop and recreate the object with larger extent sizes, and import the data. Block Size MAXEXTENTS 1KB 57 2 KB KB KB 505 See Also The following monitors in this chapter: Free Tablespace, Maximum Extents by Tablespace, Maximum Extents by User, and Number of Datafiles. 108 Version 2.0

127 Maximum Extents by Tablespace Description This monitor returns the smallest number of free extents found for a segment within the specified tablespaces. This monitor also checks how close each object within the specified tablespaces is to the value of MAXEXTENTS and reports the number of extents that can still be allocated. It does not check objects of segment_type CACHE. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Maximum extents by tablespace monitor; a description of each field follows. 2. Database Monitors Include/Exclude Includes or excludes the contents of the tablespace names field. Tablespace Names Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the Tivoli Manager for Oracle** Reference Guide 109

128 CLI Syntax maximumextentst CLI Example a {in not in} a <tablespaces> appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace names field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Names Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. waddmon OracleDatabaseManager maximumextentst -a in -a system -t 1 hours -c critical -R < 1 -n OracleManager Sentry -c severe -R < 3 -n OracleManager Sentry -c warning -R < 5 -n OracleManager Sentry -c normal -c always "ProfileName" 110 Version 2.0

129 Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Output Severity Trigger When Default Actions Critical Less than 1 Send OracleManager Sentry notice Severe Less than 3 Send OracleManager Sentry notice Warning Less than 5 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every hour. The following shows an example output from this monitor. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 111

130 The segment with the least amount of free extents for the specified tablespaces is reported as TRIGGER_INFO. The free extents for additional segments are listed in ascending order in the userinfo lines, in the following format: Free Extents, Segment Name, Object Owner, Segment Type For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. If the value of MAXEXTENTS is less than the maximum allowable (see the following table), increase the value of MAXEXTENTS. Otherwise, export the object, drop and recreate the object with larger extent sizes, and import the data. Block Size MAXEXTENTS 1KB 57 2 KB KB KB 505 See Also The following monitors in this chapter: Free Tablespace by Tablespace, Maximum Extents, Maximum Extents by User, and Number of Datafiles. 112 Version 2.0

131 Maximum Extents by User Description This monitor returns the smallest number of free extents found for a segment of a specified user. This monitor checks how close each object for a specified user is to the value of MAXEXTENTS and reports the number of extents that can still be allocated. It does not check objects of segment_type CACHE. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Maximum extents by user monitor; a description of each field follows. 2. Database Monitors User Name Specifies the Oracle user name. CLI Syntax maximumextentsu a <username> The following briefly describes the argument for this monitor. <username> Specifies the Oracle user name. GUI Name: User Name Tivoli Manager for Oracle** Reference Guide 113

132 CLI Example waddmon OracleDatabaseManager maximumextentsu -a SYS -t 1 hours -c critical -R < 1 -n OracleManager Sentry -c severe -R < 3 -n OracleManager Sentry -c warning -R < 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 1 Send OracleManager Sentry notice Severe Less than 3 Send OracleManager Sentry notice Warning Less than 5 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every hour. 114 Version 2.0

133 Output The following shows an example output from this monitor. The segment with the fewest number free extents (worst-case) for the specified user is reported as TRIGGER_INFO. The free extents for additional segments are listed in ascending order in the userinfo lines, in the following format: 2. Database Monitors Free Extents, Segment Name, Segment Owner, Segment Type For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. If the value of MAXEXTENTS is less than the maximum allowable (see the following table), increase the value of MAXEXTENTS. Otherwise, export the object, drop and recreate the object with larger extent sizes, and import the data. Tivoli Manager for Oracle** Reference Guide 115

134 Block Size MAXEXTENTS 1KB 57 2 KB KB KB 505 See Also The following monitors in this chapter: Free Tablespace, Maximum Extents, Maximum Extents by Tablespace, and Number of Datafiles. 116 Version 2.0

135 NT Service Status Description Reports the availability status of an NT service for example, a listener service named SQL*Net V2. This monitor returns one of the following states: Is up/available, Is down/unavailable, Becomes available, and Becomes unavailable. Note: For more information on the availability states for this monitor, see Appendix C, Operator Groups (Monitor Triggers). Use this monitor to check whether a specific listener is running by passing the service name as the argument to this monitor. This service is named OracleTNSListenerid, where id is the name or abbreviated ID associated with the network listener. Note: Do not attempt to run this monitor on a UNIX machine. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the NT service status monitor; a description of each field follows. 2. Database Monitors Service Name Specifies the name of the service on the NT computer for which you want the monitor to check the status. Tivoli Manager for Oracle** Reference Guide 117

136 CLI Syntax ntservicestatus CLI Example a <servicename> The following briefly describes the argument for this monitor. <servicename> Specifies the name of the service on the NT computer for which you want the monitor to check the status. GUI Name: Service Name waddmon OracleDatabaseManager ntservicestatus -a OracleTNSListener -t 1 hours -c critical -R == down -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Is down/unavailable Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 5 minutes. 118 Version 2.0

137 Output The following shows an example output from this monitor. Views Accessed None Usage Notes None See Also The following monitors in this chapter: Unix SQL*Net V1 TCP/IP Listener and Unix SQL*Net V2 Listener. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 119

138 Number of Datafiles Description Monitors how many more datafiles can be added before the database reaches the maximum number of datafiles allowed. When you create the database, you must define the maximum number of datafiles. If the database reaches its limit, it will not be possible to add an additional file to the database. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Number of datafiles monitor; a description of each field follows. Maximum Datafiles Designates the maximum number of datafiles allowable in the database. CLI Syntax numberoffiles a <maxdatafiles> The following briefly describes the argument for this monitor. <maxdatafiles> Designates the maximum number of datafiles allowable in the database. 120 Version 2.0

139 CLI Example GUI Name: Maximum Datafiles waddmon OracleDatabaseManager numberoffiles -a 50 -t 1 weeks -c critical -R > 40 -n OracleManager Sentry -c severe -R > 30 -n OracleManager Sentry -c warning -R > 25 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. 2. Database Monitors The number of current datafiles used appears in the userinfo field. For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 121

140 Views Accessed None Usage Notes When a database is created, the MAXDATAFILES parameter determines the limit on how many files the database can have. The default is operating-system dependent. The control file has a slot for each datafile, so the only way to increase the number of datafiles is to recreate the control file with a larger value for MAXDATAFILES. It is important not to let the database reach the value of MAXDATAFILES; otherwise, it would be impossible to add an additional file to a tablespace if the tablespace ran out of space. With this release of Tivoli Manager for Oracle, you must specify the value of MAXDATAFILES as an argument when configuring the monitor. You can find this value by typing ALTER DATABASE BACKUP CONTROLFILE TO TRACE at the SQL*Plus prompt and by looking for the MAXDATAFILES line in the resulting trace file, which is named ORACLE_SID_ora_UNIXpid.trc in the USER_DUMP_DEST directory on UNIX platforms, and ORA_pid.TRC in the \ORANT\RDBMSnn\TRACE directory on a Windows NT system, where nn is the release of Oracle. Note: This monitor will only give the correct results if the actual value of MAXDATAFILES is supplied as the argument for the monitor. If there are, for example, 20 datafiles in the database, and you specify MAXDATAFILES equal to 15, the value checked by the monitor would be 5. See Also The following monitors in this chapter: Free Space Deficit, Free Tablespace, Extents, and Maximum Extents. 122 Version 2.0

141 Rows in DUAL Table Description This monitor checks the number of rows in the SYS.DUAL table. Many applications rely on there being only one row in this table and can give unpredictable results if the table has more than one row. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax rowsindual CLI Example waddmon OracleDatabaseManager rowsindual -t 1 hours -c critical -R!= 1 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 2. Database Monitors Severity Trigger When Default Actions Critical Not equal to 1 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Tivoli Manager for Oracle** Reference Guide 123

142 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Once every hour. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes DUAL is a one-column, one-row dummy table containing the value X. Use it to test SQL SELECT statements or date manipulation operations without having to modify user tables. If the table has zero rows, or more than one row, the query returns incorrect results. See Also None 124 Version 2.0

143 SQL Number Description Using SQL*Plus syntax, this monitor allows you to define a SQL select statement as the basis of a monitor. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the SQL number monitor; a description of each field follows. 2. Database Monitors Monitor Label Identifies the freeform SQL monitor that the user creates. SQL Statement Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. The statement must return a numeric value. Index Specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. The columns are numbered from zero upward. No Rows As Specifies the value to be returned if no rows are returned from SQL Statement. Tivoli Manager for Oracle** Reference Guide 125

144 CLI Syntax freeformsqln CLI Example a <name> a <SQL_select_statement> a <index> a <value> The following briefly describes the arguments for this monitor. <name> Identifies the freeform SQL monitor that the user creates. GUI Name: Monitor Label <SQL_select_statement> Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. The statement must return a numeric value. GUI Name: SQL Statement <index> Specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. The columns are numbered from zero upward. GUI Name: Index <value> Specifies the value to be returned if no rows are returned from the SQL_select_statement. GUI Name: No Rows As waddmon OracleDatabaseManager freeformsqln -a test -a select count(*) from dba_data_files -a 0 -a 0 -t 1 minutes -c critical -R > 20 -n OracleManager Sentry -c severe -R > 15 -n OracleManager Sentry 126 Version 2.0

145 -c warning -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. 2. Database Monitors The user-specified arguments are reported as TRIGGER_INFO. Information in the userinfo lines appears in the following format: Trigger Value For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Tivoli Manager for Oracle** Reference Guide 127

146 Usage Notes Do not terminate the SQL statement with a semicolon (;) or forward slash (/). The select statement might return multiple columns and multiple rows. The trigger value (the value against which the monitoring criteria are evaluated) must be one of the columns in the first row returned by the statement, and must be a numeric value. The <index> parameter defines which column within the first row contain the trigger value (zero-based). A SQL select statement might return no rows. By default, Tivoli Manager for Oracle treats this as an error. You can override the default behavior with the a <value> option, in which case the monitor returns the value specified by the argument <value>. The ability to define a freeform SQL select statement allows for the integration of existing performance monitoring tools (particularly those reporting monitored values to internal Oracle tables within the subscribing database). See Also The following monitor in this chapter: SQL String. 128 Version 2.0

147 SQL String Description Using SQL*Plus syntax, this monitor enables you to define a SQL select statement as the basis of a monitor. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the SQL string monitor; a description of each field follows. 2. Database Monitors Monitor Label Identifies the freeform SQL monitor that the user creates. SQL Statement Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. The statement must return a string. Index Specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. The columns are numbered from zero upwards. No Rows As Specifies the value to be returned if no rows are returned from SQL Statement. Tivoli Manager for Oracle** Reference Guide 129

148 CLI Syntax freeformsqls CLI Example a <name> a <SQL_select_statement> a <index> a <value> The following briefly describes the arguments for this monitor. <name> Identifies the freeform SQL monitor that the user creates. GUI Name: Monitor Label <SQL_select_statement> Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. The statement must return a string. GUI Name: SQL Statement <index> Specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. The columns are numbered from zero upwards. GUI Name: Index <value> Specifies the value to be returned if no rows are returned from the SQL_select_statement. GUI Name: No Rows As waddmon OracleDatabaseManager freeformsqls -a Archive Status -a select value from v$parameter where name = log -a 0 -a unknown -t 1 minutes -c critical -R == SCOTT -n OracleManager Sentry -p Root_manzana-region 130 Version 2.0

149 -c severe -c warning -c normal -c always -n OracleManager Sentry "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. 2. Database Monitors For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes Do not terminate the SQL statement with a semicolon (;) or forward slash (/). The select statement can return multiple columns and Tivoli Manager for Oracle** Reference Guide 131

150 multiple rows. The trigger value (the value against which the monitoring criteria are evaluated) must be one of the columns in the first row returned by the statement, and must be a string value. The index parameter defines which column within the first row contains the trigger value (zero-based). A SQL select statement can return no rows. By default, Tivoli Manager for Oracle treats this as an error. You can override the default behavior with the a value option in, which case the monitor returns the value specified by the argument value. The ability to define a freeform SQL select statement allows for the integration of existing performance monitoring tools (particularly those reporting monitored values to internal Oracle tables within the subscribing database). See Also The following monitor in this chapter: SQL Number. 132 Version 2.0

151 Temporary Extents Description Monitors how close temporary segments are to their maximum extents limit (the ratio, as a percentage, of extents to the maximum extents limit). A temporary segment is used whenever sorts are too large to be performed in memory; that is, the amount of space required is greater than the value of the init.ora parameter SORT_AREA_SIZE. Oracle creates a segment in the temporary tablespace of the user who performs the sort operation. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax temporaryextents CLI Example waddmon OracleDatabaseManager temporaryextents -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 85 -n OracleManager Sentry -c warning -R > 75 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 133

152 Severity Trigger When Default Actions Critical Greater than 95% used Send OracleManager Sentry notice Severe Greater than 85% used Send OracleManager Sentry notice Warning Greater than 75% used Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. No output available for this monitor. Segments are reported in descending order in the monitor output, based on the percentage of extents allocated, in the following format: Percent Used, Segment Name, Owner, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. Check the storage parameters for the temporary tablespace, and ensure that they are appropriate for your applications. 134 Version 2.0

153 Block Size MAXEXTENTS 1KB 57 2 KB KB KB 505 Over time, the temporary tablespace will become fragmented, and should be dropped and recreated periodically. You can reduce the amount of fragmentation by running the command: alter tablespace [tablespacename] coalesce; You can create a dedicated temporary tablespace, in which a single temporary segment is created. This segment does not get dropped and avoids the costs associated with creating and dropping temporary segments. See Also The following monitors in this chapter: Free Tablespace by Tablespace, Temporary Extents by Tablespace, and Temporary Extents by User. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 135

154 Temporary Extents by Tablespace Description For specified tablespaces, monitors how close temporary segments are to their maximum extents limit (the ratio, as a percentage, of extents to the maximum extents limit). A temporary segment is used whenever sorts are too large to be performed in memory; that is, the amount of space required is greater than the value of the init.ora parameter SORT_AREA_SIZE. Oracle creates a segment in the temporary tablespace of the user who performs the sort operation. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Temporary extents by tablespace monitor; a description of each field follows. Include/Exclude Includes or excludes the contents of the tablespace names field. Tablespace Names Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of 136 Version 2.0

155 CLI Syntax temporaryextentst a {in not in} a <tablespaces> the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace names field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Names 2. Database Monitors CLI Example Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. waddmon OracleDatabaseManager temporaryextentst -a in -a TEMP -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 85 -n OracleManager Sentry Tivoli Manager for Oracle** Reference Guide 137

156 -c warning -R > 75 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% used Send OracleManager Sentry notice Severe Greater than 85% used Send OracleManager Sentry notice Warning Greater than 75% used Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 10 minutes. 138 Version 2.0

157 Output The following shows an example output from this monitor. The segment with the highest percentage of allocated extents, within the specified tablespaces, is reported as TRIGGER_INFO. The monitor may also return additional temporary segments in the userinfo lines. Segments are reported in descending order, based on the percentage of extents allocated, in the following format: 2. Database Monitors % Extents Allocated, Segment Name, Segment Owner For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. Check the storage parameters for the temporary tablespace, and ensure that they are appropriate for your applications. Block Size MAXEXTENTS 1KB 57 Tivoli Manager for Oracle** Reference Guide 139

158 Block Size MAXEXTENTS 2 KB KB KB 505 Over time, the temporary tablespace will become fragmented and should be dropped and recreated periodically. You can reduce the amount of fragmentation by running the command: alter tablespace [tablespacename] coalesce; You can create a dedicated temporary tablespace, in which a single temporary segment is created. This segment does not get dropped and avoids the costs associated with creating and dropping temporary segments. See Also The following monitors in this chapter: Free Tablespace by Tablespace, Temporary Extents, and Temporary Extents by User. 140 Version 2.0

159 Temporary Extents by User Description For a specified user, monitors how close temporary segments are to their maximum extents limit (the ratio, as a percentage, of extents to the maximum extents limit). A temporary segment is used whenever sorts are too large to be performed in memory; that is, the amount of space required is greater than the value of the init.ora parameter SORT_AREA_SIZE. Oracle creates a segment in the temporary tablespace of the user who performs the sort operation. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Temporary extents by user monitor; a description of each field follows. 2. Database Monitors User Name Specifies the Oracle user name. CLI Syntax temporaryextentsu a <username> The following briefly describes the argument for this monitor. Tivoli Manager for Oracle** Reference Guide 141

160 CLI Example <username> Specifies the Oracle user name. GUI Name: User Name waddmon OracleDatabaseManager temporaryextentsu -a SYS -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 85 -n OracleManager Sentry -c warning -R > 75 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% used Send OracleManager Sentry notice Severe Greater than 85% used Send OracleManager Sentry notice Warning Greater than 75% used Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 10 minutes. 142 Version 2.0

161 Output The following shows an example output from this monitor. The segment with the highest percentage of allocated extents for a specified user is reported as TRIGGER_INFO. The monitor may also return additional temporary segments in the userinfo lines. Segments are reported in descending order, based on the percentage of extents allocated, in the following format: 2. Database Monitors % Extents Allocated, Segment Name, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. Check the storage parameters for the temporary tablespace, and ensure that they are appropriate for your applications. Block Size MAXEXTENTS 1KB 57 Tivoli Manager for Oracle** Reference Guide 143

162 Block Size MAXEXTENTS 2 KB KB KB 505 Over time, the temporary tablespace will become fragmented and should be dropped and recreated periodically. You can reduce the amount of fragmentation by running the command: alter tablespace [tablespacename] coalesce; You can create a dedicated temporary tablespace, in which a single temporary segment is created. This segment does not get dropped and avoids the costs associated with creating and dropping temporary segments. See Also The following monitors in this chapter: Free Tablespace, Temporary Extents, and Temporary Extents by Tablespace. 144 Version 2.0

163 Total waiting time of READY messages Description This monitor details the number of messages in the READY state in each queue and the total waiting time of each message in days, hours, minutes, or seconds. Use this monitor to find out if messages have been waiting for an inordinate amount of time and if there are potential performance bottlenecks. Messages in the READY state are available for propagation across schedules as soon as a dequeue operation is started. A queue with multiple messages in the READY state can indicate problems with the dequeue process or problems with the destination. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Total waiting time of READY messages monitor; a description of each field follows. 2. Database Monitors Queue Name The name of the queue to be monitored. If this is left blank, the monitor executes on the entire database. Time Interval This interval can be set for days (D), hours (H), minutes (M), or seconds (S). Tivoli Manager for Oracle** Reference Guide 145

164 CLI Syntax totwaittimereadymsg CLI Example a <queue_name> a {D H M S} The following briefly describes the arguments for this monitor. <queue_name> The name of the queue to be monitored. If this is left blank, the monitor executes on the entire database. GUI Name: Queue Name {D H M S} The time interval can be set for days (D), hours (H), minutes (M), or seconds (S). GUI Name: Time Interval waddmon OracleDatabaseManager totwaittimereadymsg -a queue -a S -t 1 hours -c critical -R > 1 -n OracleManager Sentry -c always -f "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. The specified queue name appears as TRIGGER_INFO in the monitor output. Additional information is reported on the userinfo lines in the following format: 146 Version 2.0

165 Queue Name, Total Wait Time, Time Interval Value, No. of READY Messages For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed DBA_QUEUES GV$AQ Usage Notes None See Also The following monitors in this chapter: Average waiting time of READY messages (8i), Advanced Queue Propagation Status (8i), and AQ (Advanced Queue) Schedule Propagation errors (8i). 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 147

166 Unix Core Dump Space Description Monitors the percentage of space used on the device assigned for Oracle core dumps. The destination device is controlled by the CORE_DUMP_DEST parameter in the init.ora file for the instance. Note: This monitor should not be run on Windows NT systems that do not have a CORE_DUMP_DEST parameter. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax coredumpspace CLI Example waddmon OracleDatabaseManager coredumpspace -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice 148 Version 2.0

167 Severity Trigger When Default Actions Warning Greater than 85% Send OracleManager Sentry notice Normal N/A None Always N/A None Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. 2. Database Monitors The path to the core dump destination device appears as TRIGGER_INFO. Additional information concerning the core dump destination is reported on the userinfo lines in the following format: Available KB, % Free, %Used, Mount Point For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Tivoli Manager for Oracle** Reference Guide 149

168 Usage Notes Oracle writes core files for background processes in the CORE_DUMP_DEST directory. If this parameter is not set in the init.ora file, the core files are stored in $ORACLE_HOME/dbs on a UNIX system. If this directory is full, Oracle will be unable to create these files, which will make debugging more difficult. See Also None 150 Version 2.0

169 Unix SQL*Net V1 TCP/IP Listener Description This monitor determines whether the UNIX SQL*Net Version 1 TCP/IP listener process (orasrv) is running. If this process is not running, the machine cannot accept SQL*Net Version 1 TCP/IP connections from any clients. This monitor returns one of the following states: Is up/available, Is down/unavailable, Becomes available, and Becomes unavailable. Note: For more information on the availability states for this monitor, see Appendix C, Operator Groups (Monitor Triggers). Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax netonetcpip CLI Example waddmon OracleDatabaseManager netonetcpip -t 1 hours -c critical -R == down -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 151

170 Severity Trigger When Default Actions Critical Is down/unavailable Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 5 minutes. No output available for this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes The trigger value can be set to Becomes unavailable, which will only report an error when the listener goes down. This prevents messages from appearing on an administrator s desktop each time the monitor is run and the listener is not running. The monitor checks if the listener is running and whether it has hung by running the command tcpctl stat. You can restart the listener by logging in as the Oracle owner and typing tcpctl start. This monitor will only work if it is distributed to an endpoint that has the SQL*Net V1 software installed, because it must be able to locate the $ORACLE_HOME/bin/tcpctl program. The monitor should only be distributed once on each machine, regardless of the number of the databases on the machine. 152 Version 2.0

171 Note: This monitor is only for UNIX systems; do not run it on Windows NT. See Also The following monitors in this chapter: Unix SQL*Net V2 Listener. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 153

172 Unix SQL*Net V2 Listener Description This monitor determines whether a UNIX SQL*Net Version 2 listener process (tnslsnr) is running. If this process is not running, the machine cannot accept SQL*Net Version 2 connections from any clients. This monitor returns one of the following states: Is up/available, Is down/unavailable, Becomes available, and Becomes unavailable. Note: For more information on the availability states for this monitor, see Appendix C, Operator Groups (Monitor Triggers). Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the UNIX SQL *Net V2 listener monitor; a description of each field follows. Listener Name Specifies the name of a SQL*Net listener. You can leave this blank if there is only one listener running. CLI Syntax nettwolistener a <listener_name> 154 Version 2.0

173 CLI Example The following briefly describes the argument for this monitor. <listener_name> Specifies the name of a SQL*Net listener. You can leave this blank if there is only one listener running. GUI Name: Listener Name waddmon OracleDatabaseManager nettwolistener -a listener -t 1 hours -c critical -R == down -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. 2. Database Monitors Severity Trigger When Default Actions Critical Is down/unavailable Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 5 minutes. Tivoli Manager for Oracle** Reference Guide 155

174 Output The following shows an example output from this monitor. Results for this monitor appear in the TRIGGER_INFO in the following format: Listener Name, TNS_Admin For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes The trigger value can be set to Becomes unavailable, which will only report an error when the listener goes down. This prevents messages from appearing on an administrator s desktop each time the monitor is run and the listener is not running. The monitor checks if the listener is running, and whether it has hung, by running the command lsnrctl stat <listener_name>. You can restart the listener by logging in as the Oracle owner and typing lsnrctl start <listener_name>. If the TNS_ADMIN parameter is entered at registration, the monitor will look in this location for the LISTENER.ORA file. If this parameter has not been entered, the LISTENER.ORA file should be in one of the standard locations; that is, /etc or /var/opt/oracle (the same directory as the oratab 156 Version 2.0

175 file), or $ORACLE_HOME/network/admin. The monitor should only be distributed once on each machine, regardless of the number of the databases on the machine. If multiple listeners are running, this monitor must be configured separately for each listener. Note: For NT systems, use the NT service status monitor to check whether a SQL*Net listener is running. See Also The following monitor in this collection: Unix SQL*Net V1 TCP/IP Listener. 2. Database Monitors Tivoli Manager for Oracle** Reference Guide 157

176 User Dump Space Description This monitor reports the percentage of the allocated space that is used on the user dump destination device. The destination device is controlled by the USER_DUMP_DEST parameter in the init.ora file for the instance. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager GUI Data Entry Fields None CLI Syntax userdumpspace CLI Example waddmon OracleDatabaseManager userdumpspace -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of the Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 85% Send OracleManager Sentry notice Normal N/A None 158 Version 2.0

177 Severity Trigger When Default Actions Always N/A None Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Once every hour. The following shows an example output from this monitor. 2. Database Monitors The path to the user dump destination device appears in the TRIGGER_INFO field. Additional information concerning the user dump destination is reported as text on the userinfo lines, in the following format: Available KB, %Free, % Used, Mount Point For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Tivoli Manager for Oracle** Reference Guide 159

178 Usage Notes Oracle creates trace files for the user processes in the USER_DUMP_DEST directory. If this parameter is not set in the init.ora file, the trace files are stored in $ORACLE_HOME/rdbms/log on a UNIX system and \ORANT\RDBMSnn\TRACE on a Windows NT system, where nn is the release of Oracle. If this directory is full, Oracle will be unable to create these files, which may result in process failure and will make debugging more difficult. See Also None 160 Version 2.0

179 3 Instance Monitors The OracleInstanceManager Monitoring Collection provides monitoring sources for managing Oracle instances, including server processes, cache hit ratios, and transactions. All of the instance monitors (excluding RDBMS State) collect data from the Oracle v$ views. Profiles containing OracleInstanceManager monitors should be distributed to Oracle instance endpoints. Value Ranges If a monitor produces an unexpected result, it may be because the number stored in the v$ view is incorrect. When you select from SQL*Plus, the numbers are returned as signed 32-bit counters, so numbers greater than 1,034,741,823 are displayed as negative numbers. Any calculations using negative numbers return incorrect values, which can cause Oracle to erroneously respond as if a threshold has been exceeded. The longer the database has been running, the greater the chance this will occur. For example, the idle time for dispatcher processes is stored in hundredths of a second and, after a period of approximately 110 days, the idle time statistic could display a negative number. If you suspect that the values returned by a monitor are incorrect, query the underlying v$ views and check for negative numbers. To resolve this problem, restart the database. Restarting the database resets the statistics in the v$ views. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 161

180 List of OracleInstanceManager Monitoring Sources The following table lists the monitoring sources in this collection alphabetically by their graphical user interface (GUI) names. It also includes their command line interface (CLI) names, monitor numbers, and whether they support Distributed Monitoring Logging. Monitors that support Distributed Monitoring Logging have a Yes in the Log File column. For more information, see Using Distributed Monitoring Logging on page 9. GUI Name CLI Name Monitor Log File Number Active Transactions activetrans 1 Yes Any v$lock readlock 3 Yes Any v$sysstat readsysstat 4 Yes Average Redo Entry Size averageredosize 6 Yes Block Changes Per Transaction blockchanges 8 Yes Block Get Rate blockgetrate 9 Yes Buffer Cache Hit Ratio bufcachehitratio 11 Yes Buffer Cache Hit Ratio (Interval) bufcachehitratioi 76 No Buffer Waits Ratio bufferwaits 10 Yes Call Rate callrate 12 Yes Calls Per Transaction callspertransaction 13 Yes Changed Block Ratio changedblockratio 16 Yes Cluster Key Ratio clusterkeyratio 17 Yes Completed Background readsysstatc 18 Yes Checkpoints Consistent Change Ratio consistentchangeratio 19 Yes Continued Row Ratio continuedrowratio 20 Yes DBWR Checkpoints readsysstatw 21 Yes Dictionary Cache Hit Ratio dictcachehitratio 22 Yes Dictionary Cache Hit Ratio dictcachehitratioi 77 No Dispatcher Busy Rate dispatchbusyrate 23 Yes Dispatcher Wait Times dispatchwaits 24 Yes 162 Version 2.0

181 GUI Name CLI Name Monitor Log File Number DML Locks Ratio dmllocks 25 Yes Enqueue Timeouts enqueuetimeouts 26 Yes Freelist Waits Ratio freelistwaits 32 Yes Library Cache Hit Ratio libcachehitratio 33 Yes Library Cache Hit Ratio (Interval) libcachehitratioi 78 No Lock Hit Ratio Parallel lockhitratiopar 142 Yes Description Long Table Full Table Scans longtabscansi 79 No (Interval) Number of Deadlocks readsysstatd 36 Yes Open Cursors opencursors 37 No PCM Conversion Waits pcmconversionwaits 144 Yes PCM Lock Conversion Time pcmlockconversiontime 143 Yes Percentage of False Pings percentfalsepings 140 Yes Physical I/O Reads physicalreads 63 Yes Physical I/O Writes physicalwrites 64 Yes Ping Rate pingrate 141 Yes Process Ratio processratio 38 Yes RDBMS State rdbmsstate 39 No Recursive Call Rate recursivecallrate 40 Yes Recursive Calls readsysstatr 41 Yes Recursive To User Calls Ratio recursivetousercalls 42 Yes Redo Allocation Latch Ratio redolatchratio 43 Yes Redo Copy Latch Ratio redoclatchratio 44 Yes Redo Log Space Waits redologwaits 45 Yes Redo Logs Not Archived redosnotarchived 46 Yes Redo Small Copy Ratio redosmallcopyratio 47 Yes Rollback Waits rollbackwaits 48 Yes Row Source Ratio rowsourceratio 49 Yes Shared Server Process Ratio sharedserverratio 51 Yes 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 163

182 GUI Name CLI Name Monitor Log File Number Shared Server Wait Time sharedserverwait 52 Yes Sort Overflow Ratio sortoverflowratio 53 Yes User Rollback Ratio userrollbackratio 60 Yes 164 Version 2.0

183 Active Transactions Description Monitors the total number of active transactions as a percentage of the TRANSACTIONS parameter in the init.ora file for the instance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax activetrans CLI Example waddmon OracleInstanceManager activetrans -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. 3. Instance Monitors Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 85% Send OracleManager Sentry notice Tivoli Manager for Oracle** Reference Guide 165

184 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$TRANSACTION V$PARAMETER Usage Notes If this monitor regularly reports a 90% usage figure, increase the TRANSACTIONS parameter in the init.ora file for the instance (default of 1.1*PROCESSES). If the number of transactions is 166 Version 2.0

185 increasing, it might be necessary to add rollback segments. Use the Rollback Waits monitor to determine if there is contention for rollback segments. See Also The following monitor in this chapter: Rollback Waits. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 167

186 Any v$lock Description Monitors the number of active locks of a user-specified type. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Any v$lock monitor; a description of each field follows. CLI Syntax readlock Lock Type Specifies the lock type. See the description of the v$lock table in the following section or in the Server Administrator s Guide for the relevant version of Oracle. a <lock_type> The following briefly describes the argument for this monitor. <lock_type> Specifies the lock type (refer to the following table). GUI Name: Lock Type 168 Version 2.0

187 The following table provides the CLI and GUI arguments for the Any v$lockmonitor. For more information, see the Server Administrator s Guide for the relevant version of Oracle. CLI GUI Description RW Row Row wait enqueue lock TM DML DML enqueue lock TX Transaction Transaction enqueue lock UL User User supplied lock BL Buffer Buffer hash table instance lock CF Cross-instance Cross-instance function invocation instance lock CI Control (CI) Control file schema global enqueue lock CS Control (CS) Control file schema global enqueue lock DF Data Data file instance lock DM Mount/startup Mount/ startup db primary/ secondary instance lock DR Distributed (DR) Distributed recovery process lock DX Distributed (DX) Distributed transaction entry lock FI SGA SGA open-file information lock FS File File set lock IR Instance Instance recovery serialization global enqueue lock IV Library Library cache invalidation instance lock LS Log Log start/ log switch enqueue lock MB Master Master buffer hash table instance lock MM Mount Mount definition global enqueue lock MR Media Media recovery lock RE USE_ROW_ENQUEUE USE_ROW_ENQUEUE enforcement lock RT Redo Redo thread global enqueue lock SC System (SC) System commit number instance lock SH System (SH) System commit number high-water mark enqueue lock SN Sequence (SN) Sequence number instance lock 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 169

188 CLI GUI Description SQ Sequence (SQ) Sequence number enqueue lock ST Space Space transaction enqueue lock SV Sequence (SV) Sequence number value lock TA Generic Generic enqueue lock TD DDL DDL enqueue lock TE Extend-segment Extend-segment enqueue lock TS Temporary (TS) Temporary segment enqueue lock TT Temporary (TT) Temporary table enqueue lock UN User User name lock WL Being-written Being-written redo log instance lock WS Write-atomic-log-switch Write-atomic-log-switch global enqueue lock CLI Example waddmon OracleInstanceManager readlock -a MB -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 80 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 170 Version 2.0

189 Output The following shows an example output from this monitor. The specified lock type appears as TRIGGER_INFO. The trigger value is repeated in the userinfo line. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$LOCK Usage Notes None See Also The following monitors in this chapter: DML Locks Ratio, Active Transactions, and Open Cursors. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 171

190 Any v$sysstat Description Monitors the current system-wide value from v$sysstat for the specified statistic. Valid stat_name parameters are taken from the v$statname table. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Any v$sysstat monitor; a description of each field follows. Stat Name Specifies the statistic names from v$statname (case-sensitive). See the description of the v$ tables in the Server Administrator s Guide for the relevant version of Oracle. CLI Syntax readsysstat a <stat_name> The following briefly describes the argument for this monitor. <stat_name> Specifies the statistic names from v$statname 172 Version 2.0

191 CLI Example (case-sensitive). See the description of the v$ tables in the Server Administrator s Guide for the relevant version of Oracle. GUI Name: Stat Name waddmon OracleInstanceManager readsysstat -a user rollbacks -t 1 hours -c critical -R >= 200 -n OracleManager Sentry -c severe -R >= 180 -n OracleManager Sentry -c warning -R >= 150 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes None See Also The following monitors in this chapter: Completed Background Checkpoints, DBWR Checkpoints, Active Transactions, and Recursive Calls. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 173

192 Average Redo Entry Size Description Monitors the average size of a redo entry, which is calculated as the total redo size in bytes, divided by the number of redo entries. This information can be useful in calculating the size of the online redo logs or the log buffer in the system global area (SGA). Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax averageredosize CLI Example waddmon OracleInstanceManager averageredosize -t 1 hours -c critical -R > n OracleManager Sentry -c severe -R > n OracleManager Sentry -c warning -R > n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 174 Version 2.0

193 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes In order to estimate the number of redo logs and the size of the redo logs for a database, you need to know: The total amount of redo generated for a particular time period The average amount of redo per transaction Use the archive log list command from within sqldba to determine the number of redo logs generated. Use this statistic to determine the average redo size per transaction this could be multiplied by the transaction rate to estimate the total amount of redo generated. See Also The following monitors in this chapter: Redo Log Space Waits and Redo Logs Not Archived. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 175

194 Block Changes Per Transaction Description Measures the amount of DML (Data Manipulation Language) work that each transaction performs. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax blockchanges CLI Example waddmon OracleInstanceManager blockchanges -t 1 hours -c critical -R > 3 -n OracleManager Sentry -c severe -R > 2 -n OracleManager Sentry -c warning -R > 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 176 Version 2.0

195 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Creating or dropping indexes impacts this value considerably and might lead to inconclusive values because the figure also includes changes to index blocks. See Also The following monitors in this chapter: Active Transactions. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 177

196 Block Get Rate Description Monitors the block get rate, which is the basic measure of the rate at which the application system references the database. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax blockgetrate CLI Example waddmon OracleInstanceManager blockgetrate -t 1 hours -c critical -R < 0.4 -n OracleManager Sentry -c severe -R < 0.6 -n OracleManager Sentry -c warning -R < 0.8 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 178 Version 2.0

197 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Block get rate is calculated as: (db block gets + consistent gets) / second See Also The following monitors in this chapter: Buffer Cache Hit Ratio (Interval) and Buffer Cache Hit Ratio. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 179

198 Buffer Cache Hit Ratio Description Monitors the rate at which Oracle finds the data blocks it needs in memory over the lifetime of an instance. This monitor indicates the current ratio of buffer cache hits to total requests. The goal of this performance test is to achieve 100% hits, which is to have the entire application in memory. A correctly tuned buffer cache can significantly improve overall database performance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax bufcachehitratio CLI Example waddmon OracleInstanceManager bufcachehitratio -t 1 hours -c critical -R < 70 -n OracleManager Sentry -c severe -R < 80 -n OracleManager Sentry -c warning -R < 90 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Less than 70% Send OracleManager Sentry notice Severe Less than 80% Send OracleManager Sentry notice Warning Less than 90% Send OracleManager Sentry notice 180 Version 2.0

199 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes The hit ratio is calculated as: 3. Instance Monitors [(Logical Reads - Physical Reads) / Logical Reads] * 100 where Logical Reads = consistent gets + db block gets Tivoli Manager for Oracle** Reference Guide 181

200 In general, if the hit ratio is below 90%, and the dictionary cache has been tuned, increase the init.ora parameter DB_BLOCK_BUFFERS to increase the hit ratio. However, note that increasing this parameter also increases the size of the SGA. Use the x$kcbrbh table to determine how many extra buffers are required. See the Server Administrator s Guide for the relevant version of Oracle. Do not run the monitor until the instance has run long enough to have a representative workload. When an instance is started, the Oracle caches are empty and the cache hit rate is low, so running the monitor at this time returns misleading results. See Also The following monitors in this chapter: Buffer Cache Hit Ratio (Interval), Dictionary Cache Hit Ratio, Dictionary Cache Hit Ratio (Interval), Library Cache Hit Ratio and Library Cache Hit Ratio (Interval). 182 Version 2.0

201 Buffer Cache Hit Ratio (Interval) Description Monitors the rate at which Oracle finds the data blocks it needs in memory over the current monitoring interval. This monitor indicates the current ratio of buffer cache hits to total requests. The goal of this performance test is to achieve 100% hits, which is to have the entire application in memory. A correctly tuned buffer cache can significantly improve overall database performance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax bufcachehitratioi CLI Example waddmon OracleInstanceManager bufcachehitratioi -t 1 hours -c critical -R < 70 -n OracleManager Sentry -c severe -R < 75 -n OracleManager Sentry -c warning -R < 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. 3. Instance Monitors Severity Trigger When Default Actions Critical Less than 70% Send OracleManager Sentry notice Severe Less than 75% Send OracleManager Sentry notice Warning Less than 85% Send OracleManager Sentry notice Tivoli Manager for Oracle** Reference Guide 183

202 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes The hit ratio is calculated as: [(Logical Reads - Physical Reads) / Logical Reads] * 100 where Logical Reads = consistent gets + db block gets In general, if the hit ratio is below 90%, and the dictionary cache has been tuned, increase the init.ora parameter 184 Version 2.0

203 DB_BLOCK_BUFFERS to increase the hit ratio. However, note that increasing this parameter also increases the size of the SGA. Use the x$kcbrbh table to determine how many extra buffers are required. See the Server Administrator s Guide for the relevant version of Oracle. Do not run the monitor until the instance has run long enough to have a representative workload. When an instance is started, the Oracle caches are empty and the cache hit rate is low, so running the monitor at this time returns misleading results. See Also The following monitors in this chapter: Buffer Cache Hit Ratio, Dictionary Cache Hit Ratio, Dictionary Cache Hit Ratio (Interval), Library Cache Hit Ratio and Library Cache Hit Ratio (Interval). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 185

204 Buffer Waits Ratio Description Monitors the ratio of buffer busy waits to logical reads. This indicates that a user process attempted to acquire a buffer but had to wait because the buffer was held in an incompatible mode. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax bufferwaits CLI Example waddmon OracleInstanceManager bufferwaits -t 1 hours -c critical -R > 15 -n OracleManager Sentry -c severe -R > 10 -n OracleManager Sentry -c warning -R > 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source: Severity Trigger When Default Actions Critical Greater than 15% Send OracleManager Sentry notice Severe Greater than 10% Send OracleManager Sentry notice Warning Greater than 5% Send OracleManager Sentry notice Normal N/A None Always N/A None 186 Version 2.0

205 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. The information for all buffer waits is reported as text on the userinfo lines, in the following format: busy_waits consistent_gets db_block_gets For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSTEM_EVENT 3. Instance Monitors V$SYSSTAT Tivoli Manager for Oracle** Reference Guide 187

206 Usage Notes A non-zero value for this ratio indicates that block contention is occurring. The ratio is calculated as: buffer busy waits / logical reads where logical reads = consistent gets + db block gets Query the v$waitstat table to determine what kind of waits are occurring. Having studied this table, note the following: Avoid resource waits of any kind. If undo rollback segment waits are occurring, increase the number of private rollback segments the monitored database contains. Run the Rollback Waits monitor to examine rollback segment waits. If data block waits are occurring, increase the FREELIST parameter for heavily inserted tables. If in doubt, set FREELIST to 2 for tables suspected of being an insert or update bottleneck. Use the Freelist Waits Ratio monitor to specifically check for this form of block contention. See Also The following monitors in this chapter: Freelist Waits Ratio and Rollback Waits. 188 Version 2.0

207 Call Rate Description Provides an overview of the work rate being run against the instance. Calls do any of the following: describe, parse, open, fetch, close, or execute. The call rate is dependent on the design of an application. Use of an array interface will also affect this figure. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax callrate CLI Example waddmon OracleInstanceManager callrate -t 1 hours -c critical -R > 0.9 -n OracleManager Sentry -c severe -R > 0.7 -n OracleManager Sentry -c warning -R > 0.5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 3. Instance Monitors Because this monitor operates in the context of the monitoring schedule, the first execution of the monitor will return an invalid value and the following text on the userinfo lines:!!rate_based_monitor_startup!! Tivoli Manager for Oracle** Reference Guide 189

208 Output The following shows an example output from this monitor. The sum of the cumulative counters of the recursive calls and user calls obtained from the v$sysstat appears as TRIGGER_INFO. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Call rate is calculated as: (r + u) /t where: r is the recursive calls for the period u is the user calls for the period t is the time in seconds since the last monitor probe 190 Version 2.0

209 See Also The following monitor in this chapter: Recursive Call Rate. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 191

210 Calls Per Transaction Description Monitors the number of client requests made per transaction. Calls do any of the following: describe, parse, open, fetch, close, or execute. Calls per transaction can be used to detect changes in the application, or in the way in which it is being used. The reported value can change considerably when ad hoc queries are issued. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax callspertransaction CLI Example waddmon OracleInstanceManager callspertransaction -t 1 hours -c critical -R > n OracleManager Sentry -c severe -R > 900 -n OracleManager Sentry -c warning -R > 500 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 192 Version 2.0

211 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes None See Also The following monitors in this chapter: Call Rate and Active Transactions. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 193

212 Changed Block Ratio Description Monitors the percentage of blocks accessed that have been updated. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax changedblockratio CLI Example waddmon OracleInstanceManager changedblockratio -t 1 hours -c critical -R > 20 -n OracleManager Sentry -c severe -R > 15 -n OracleManager Sentry -c warning -R > 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 194 Version 2.0

213 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes This monitor reports the balance between queries made and the DML within the database application. Changes in this ratio indicate and quantify changes to index structures or application usage. The ratio is calculated as: [db block changes /(db block gets + consistent gets)] * 100 See Also The following monitors in this chapter: DBWR Checkpoints and Completed Background Checkpoints. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 195

214 Cluster Key Ratio Description Monitors the ratio of cluster key scan block gets to cluster key scans. If the ratio is greater than one, the rows for a cluster key are stored in multiple data blocks. To analyze the cluster for row chaining, use the Chained Rows (cluster) monitor. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax clusterkeyratio CLI Example waddmon OracleInstanceManager clusterkeyratio -t 10 minutes -c critical -R > 5 -n OracleManager Sentry -c severe -R > 3 -n OracleManager Sentry -c warning -R > 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 10 minutes. 196 Version 2.0

215 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Cluster key ratio is calculated as: cluster key scan block gets / cluster key scans The SIZE parameter specified during the CREATE CLUSTER command determines the number of cluster keys per block. The default is one data block per cluster key value. If all the data for a cluster key does not fit into a block, multiple blocks are read, resulting in additional I/O. Recreate the cluster with a larger SIZE value. See Also The following monitor in this chapter: Long Table Full Table Scans (Interval). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 197

216 Completed Background Checkpoints Description Monitors the number of times a database writer (DBWR) checkpoint is completed. Frequent checkpoints can reduce recovery time in the event of a system failure; this is offset by the momentary reduction in runtime performance while the checkpoint is carried out. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax readsysstatc CLI Example waddmon OracleInstanceManager readsysstatc -t 1 hours -c critical -R < 5 -n OracleManager Sentry -c severe -R < 7 -n OracleManager Sentry -c warning -R < 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 198 Version 2.0

217 Output The following shows an example output from this monitor. The trigger value is returned as TRIGGER_INFO. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Choose the checkpoint frequency based on performance concerns; the frequency is controlled by means of the LOG_CHECKPOINT_INTERVAL and LOG_CHECKPOINT_TIMEOUT parameters in the init.ora file for the instance. You can reduce the number of checkpoints by increasing the size of the redo log files and by setting LOG_CHECKPOINT_INTERVAL to a value greater than the size of the redo log files. Also, consider starting the instance with a CKPT background process, which will write the checkpoint information to the database files (if the CKPT process does not exist, LGWR must perform this task). This procedure reduces the time a checkpoint takes to complete. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 199

218 See Also The following monitors in this chapter: DBWR Checkpoints and Process Ratio. 200 Version 2.0

219 Consistent Change Ratio Description Monitors the ratio of consistent changes to consistent gets. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax consistentchangeratio CLI Example waddmon OracleInstanceManager consistentchangeratio -t 1 hours -c critical -R >= 15 -n OracleManager Sentry -c severe -R >= 10 -n OracleManager Sentry -c warning -R >= 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 201

220 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes This monitor reports the extent to which the applications must exercise the read consistency mechanism. Consistent change ratio is calculated as: (consistent changes / consistent gets) * 100 See Also The following monitor in this chapter: Changed Block Ratio. 202 Version 2.0

221 Continued Row Ratio Description Monitors the percentage of rows retrieved that extend over more than one block, which is called chained rows. The ratio should be very close to 0, except in applications that have long columns, or rows that are larger than one block (spanned rows), where chaining is unavoidable. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax continuedrowratio CLI Example waddmon OracleInstanceManager continuedrowratio -t 10 minutes -c critical -R > 1 -n OracleManager Sentry -c severe -R > 0.5 -n OracleManager Sentry -c warning -R > 0 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. 3. Instance Monitors Severity Trigger When Default Actions Critical Greater than 1% Send OracleManager Sentry notice Severe Greater than 0.5% Send OracleManager Sentry notice Tivoli Manager for Oracle** Reference Guide 203

222 Severity Trigger When Default Actions Warning Greater than 0% Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT 204 Version 2.0

223 Usage Notes If the monitor reports a ratio steadily increasing over time, identify which tables are experiencing chaining (use the Chained Rows (cluster) monitor) and increase the PCTFREE for these tables. Note: A row is recorded as chained only if the access is performed by RowID. Full table scans of tables that contain chained rows do not cause the v$sysstat statistic table fetch continued row to increase. See Also The following monitors in the OracleDatabaseManager Monitoring Collection: Chained Rows (cluster) and Chained Rows (table). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 205

224 DBWR Checkpoints Description Monitors the number of database writer (DBWR) checkpoints requested by the server. Frequent checkpoints can reduce recovery time in the event of a system failure; this is offset by the momentary reduction in runtime performance while the checkpoint is carried out. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax readsysstatw CLI Example waddmon OracleInstanceManager readsysstatw -t 1 hours -c critical -R >= 50 -n OracleManager Sentry -c severe -R >= 40 -n OracleManager Sentry -c warning -R >= 30 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 206 Version 2.0

225 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Choose the checkpoint frequency based on performance concerns; the frequency is controlled by means of the LOG_CHECKPOINT_INTERVAL and LOG_CHECKPOINT_TIMEOUT parameters in the init.ora file for the instance. You can reduce the number of checkpoints by increasing the size of the redo log files and by setting LOG_CHECKPOINT_INTERVAL to a value greater than the size of the redo log files. Also, consider starting the instance with a CKPT background process, which will write the checkpoint information to the database files (if the CKPT process does not exist, LGWR must perform this task). This procedure reduces the time a checkpoint takes to complete. See Also The following monitor in this chapter: Process Ratio. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 207

226 Dictionary Cache Hit Ratio Description Monitors the effectiveness of the dictionary cache over the lifetime of an instance. This monitor shows the ratio, as a percentage, of dictionary cache hits to total requests. A correctly tuned dictionary cache can significantly improve overall database performance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax dictcachehitratio CLI Example waddmon OracleInstanceManager dictcachehitratio -t 10 minutes -c critical -R < 70 -n OracleManager Sentry -c severe -R < 80 -n OracleManager Sentry -c warning -R < 90 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Less than 70% Send OracleManager Sentry notice Severe Less than 80% Send OracleManager Sentry notice Warning Less than 90% Send OracleManager Sentry notice 208 Version 2.0

227 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$ROWCACHE Usage Notes Dictionary cache hit ratio is calculated as: 3. Instance Monitors [1 - (sum(getmisses) / (sum(gets) + sum(getmisses) ) ] * 100 Tivoli Manager for Oracle** Reference Guide 209

228 If the hit ratio is less than 70%, increase the value of the init.ora parameter SHARED_POOL_SIZE. Tivoli recommends that the SHARED_POOL_SIZE be at least 4 MB in size. Large databases might require a shared pool of at least 10 MB. Note that increasing SHARED_POOL_SIZE will increase the size of the SGA (if this is made unnecessarily large, it will impact the amount of memory that is available to other processes). Do not run the monitor until the instance has run long enough to have a representative workload. When an instance is started, the Oracle caches are empty and the cache hit rate is low, so running the monitor at this time returns misleading results. See Also The following monitors in this chapter: Buffer Cache Hit Ratio, Buffer Cache Hit Ratio (Interval), Dictionary Cache Hit Ratio (Interval), Library Cache Hit Ratio and Library Cache Hit Ratio (Interval). 210 Version 2.0

229 Dictionary Cache Hit Ratio (Interval) Description Monitors the effectiveness of the dictionary cache for the current monitoring interval. This monitor shows the ratio, as a percentage, of dictionary cache hits to total requests. A correctly tuned dictionary cache can significantly improve overall database performance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax dictcachehitratioi CLI Example waddmon OracleInstanceManager dictcachehitratioi -t 30 minutes -c critical -R < 70 -n OracleManager Sentry -c severe -R < 80 -n OracleManager Sentry -c warning -R < 90 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. 3. Instance Monitors Severity Trigger When Default Actions Critical Less than 70% Send OracleManager Sentry notice Severe Less than 80% Send OracleManager Sentry notice Warning Less than 90% Send OracleManager Sentry notice Tivoli Manager for Oracle** Reference Guide 211

230 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$ROWCACHE Usage Notes The dictionary cache hit ratio is calculated as: [1 - (sum(getmisses) / (sum(gets) + sum(getmisses) ) ] * 100 If the hit ratio is less than 70%, increase the value of the init.ora parameter SHARED_POOL_SIZE. Tivoli recommends that the SHARED_POOL_SIZE be at least 4 MB in size. Large databases might require a shared pool of at least 10 MB. Note that increasing 212 Version 2.0

231 SHARED_POOL_SIZE will increase the size of the SGA (if this is made unnecessarily large, it will impact the amount of memory that is available to other processes). Do not run the monitor until the instance has run long enough to have a representative workload. When an instance is started, the Oracle caches are empty and the cache hit rate is low, so running the monitor at this time returns misleading results. See Also The following monitors in this chapter: Buffer Cache Hit Ratio, Buffer Cache Hit Ratio (Interval), Dictionary Cache Hit Ratio, Library Cache Hit Ratio and Library Cache Hit Ratio (Interval). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 213

232 Dispatcher Busy Rate Description This monitor reports the percentage of time that dispatcher processes for the protocol with the most contention are busy. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax dispatchbusyrate CLI Example waddmon OracleInstanceManager dispatchbusyrate -t 10 minutes -c critical -R > 90 -n OracleManager Sentry -c severe -R > 70 -n OracleManager Sentry -c warning -R > 50 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 90% Send OracleManager Sentry notice Severe Greater than 70% Send OracleManager Sentry notice Warning Greater than 50% Send OracleManager Sentry notice Normal N/A None 214 Version 2.0

233 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. Information for the busiest network protocol appears as TRIGGER_INFO. Additional information for all protocols is given in the userinfo lines in the following format: 3. Instance Monitors %Busy, Network protocol For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 215

234 Views Accessed V$DISPATCHER Usage Notes If the dispatcher processes for a specific protocol are busy for more than 50% of the time, you can improve performance by adding more dispatcher processes. Do this by increasing the value of the init.ora parameter MTS_MAX_DISPATCHERS. This monitor is only relevant if the instance has been configured for the multi-threaded server. See Also The following monitor in this chapter: Dispatcher Wait Times. 216 Version 2.0

235 Dispatcher Wait Times Description This monitor reports the time (in hundredths of a second) that a response waits in the response queue for a dispatcher process to route it, for the protocol with the longest average wait time. Note: This monitor is only relevant if the instance is configured for the multi-threaded server. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax dispatchwaits CLI Example waddmon OracleInstanceManager dispatchwaits -t 10 minutes -c critical -R > 25 -n OracleManager Sentry -c severe -R > 18 -n OracleManager Sentry -c warning -R > 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. 3. Instance Monitors Severity Trigger When Default Actions Critical Greater than 25 Send OracleManager Sentry notice Severe Greater than 18 Send OracleManager Sentry notice Tivoli Manager for Oracle** Reference Guide 217

236 Severity Trigger When Default Actions Warning Greater than 10 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. The network protocol with the longest average wait time appears as the TRIGGER_INFO. Information for each network protocol returned appears in the userinfo lines. Results are reported in descending order, based on the length of wait time, in the following format: 218 Version 2.0

237 Average wait time, Network protocol For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$QUEUE V$DISPATCHER Usage Notes If the longest average wait time is greater than 0.1 seconds, you can improve performance by adding more dispatcher processes. Do this by increasing the value of the init.ora parameter MTS_MAX_DISPATCHERS. See Also The following monitor in this chapter: Dispatcher Busy Rate. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 219

238 DML Locks Ratio Description Monitors the current number of Data Manipulation Language (DML) locks as a percentage of the maximum number of locks defined for the instance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax dmllocks CLI Example waddmon OracleInstanceManager dmllocks -t 10 minutes -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 80 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 80% Send OracleManager Sentry notice 220 Version 2.0

239 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. Results in the userinfo lines appear in the following format: a = current number of DML locks 3. Instance Monitors b = maximum number of DML locks defined for the instance For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 221

240 Views Accessed V$PARAMETER V$LOCK Usage Notes The instance limit is set through the DML_LOCKS parameter in the init.ora file and represents the maximum number of locks that can be placed on all tables by all users at any one time. The default is four times the maximum number of transactions. When the limit is reached, processing stops and an Oracle error is produced. Within the bounds of the maximum limit, the setting of the DML_LOCKS parameter has little or no effect on the performance of the server. Therefore, it should be set artificially high to prevent hitting the maximum limit, which is operating-system specific. See Also The following monitors in this chapter: Any v$sysstat, Active Transactions, and Enqueue Timeouts. 222 Version 2.0

241 Enqueue Timeouts Description This monitor displays the number of times an enqueue lock was requested and was not granted immediately. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax enqueuetimeouts CLI Example waddmon OracleInstanceManager enqueuetimeouts -t 1 hours -c critical -R ->> 2 -n OracleManager Sentry -c severe -R - >= 2 -n OracleManager Sentry -c warning -R - >= 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Increase beyond 2 Send OracleManager Sentry notice Severe Increase of 2 Send OracleManager Sentry notice Warning Increase of 1 Send OracleManager Sentry notice Normal N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 223

242 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes The default value of the init.ora parameter ENQUEUE_RESOURCES is derived from the init.ora parameter PROCESSES. For three or fewer processes, the default value is 20. For four to 10 processes, the default value is ((PROCESSES - 3) * 5) + 20, and for more than 10 processes, the default value is ((PROCESSES - 10) * 2) If applications are using a large number of tables, increase this value. 224 Version 2.0

243 See Also The following monitor in this chapter: Any v$sysstat. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 225

244 Freelist Waits Ratio Description Monitors the ratio, as a percentage, of freelist waits to the total number of requests for data. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax freelistwaits CLI Example waddmon OracleInstanceManager freelistwaits -t 10 minutes -c critical -R > 2 -n OracleManager Sentry -c severe -R > 1 -n OracleManager Sentry -c warning -R > 0.5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Suggested monitoring schedule: Every 10 minutes. 226 Version 2.0

245 Output The following shows an example output from this monitor. Information is reported in the TRIGGER_INFO field in the following format: a = the number of free list waits b = the total number of requests for data For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$WAITSTAT V$SYSSTAT Usage Notes This monitor calculates the freelist waits ratio as: 3. Instance Monitors (number of free list waits / total number of requests for data) * 100 If the ratio is greater than 1%, increase the number of freelists for the relevant tables. Tivoli Manager for Oracle** Reference Guide 227

246 An Oracle table is created with a default of one freelist. This might not be enough for insert- and update-intensive tables. When two or more processes are searching the freelist at the same time, a process might need to request additional information from disk, which can result in a resource wait. To avoid this problem, export the data from the insert- and update-intensive tables, drop the tables, recreate them with a bigger FREELIST parameter, and import the data. See Also The following monitor in this chapter: DML Locks Ratio. 228 Version 2.0

247 Library Cache Hit Ratio Description Monitors the percentage of entries in the library cache that were parsed more than once (reloads) over the lifetime of the instance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax libcachehitratio CLI Example waddmon OracleInstanceManager libcachehitratio -t 10 minutes -c critical -R < 90 -n OracleManager Sentry -c severe -R < 92 -n OracleManager Sentry -c warning -R < 95 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Less than 90% Send OracleManager Sentry notice Severe Less than 92% Send OracleManager Sentry notice Warning Less than 95% Send OracleManager Sentry notice Normal N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 229

248 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$LIBRARYCACHE Usage Notes The goal is to have reloads as near to zero as possible. You can achieve this goal by allocating more memory to the library cache; that is, increase the value of the init.ora parameter SHARED_POOL_SIZE. 230 Version 2.0

249 The hit ratio is calculated as: [sum(pins) / (sum(pins) + sum(reloads))] * 100 A pin is the number of times an item in the cache was executed. In general, if the hit ratio is below 90%, increase the value of SHARED_POOL_SIZE. Do not run the monitor until the instance has run long enough to have a representative workload. When an instance is started, the Oracle caches are empty and the cache hit rate is low, so running the monitor at this time returns misleading results. See Also The following monitors in this chapter: Buffer Cache Hit Ratio, Buffer Cache Hit Ratio (Interval), Dictionary Cache Hit Ratio, Dictionary Cache Hit Ratio (Interval), and Library Cache Hit Ratio (Interval). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 231

250 Library Cache Hit Ratio (Interval) Description Monitors the percentage of entries in the library cache that were parsed more than once (reloads) for the current monitoring interval. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax libcachehitratioi CLI Example waddmon OracleInstanceManager libcachehitratioi -t 10 minutes -c critical -R < 90 -n OracleManager Sentry -c severe -R < 92 -n OracleManager Sentry -c warning -R < 95 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Less than 90% Send OracleManager Sentry notice Severe Less than 92% Send OracleManager Sentry notice Warning Less than 95% Send OracleManager Sentry notice Normal N/A None 232 Version 2.0

251 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$LIBRARYCACHE Usage Notes The goal is to have reloads as near to zero as possible. You can achieve this goal by allocating more memory to the library cache; that is, increase the value of the init.ora parameter SHARED_POOL_SIZE. 3. Instance Monitors The hit ratio is calculated as: [sum(pins) / (sum(pins) + sum(reloads))] * 100 Tivoli Manager for Oracle** Reference Guide 233

252 A pin is the number of times an item in the cache was executed. In general, if the hit ratio is below 90%, increase the value of SHARED_POOL_SIZE. Do not run the monitor until the instance has run long enough to have a representative workload. When an instance is started, the Oracle caches are empty and the cache hit rate is low, so running the monitor at this time returns misleading results. See Also The following monitors in this chapter: Buffer Cache Hit Ratio,Buffer Cache Hit Ratio (Interval), Dictionary Cache Hit Ratio, Dictionary Cache Hit Ratio (Interval) and Library Cache Hit Ratio. 234 Version 2.0

253 Lock Hit Ratio Parallel Description Description Monitors the proportion of data block accesses that do not require lock conversions. Lock hit ratio indicates how efficiently user processes are distributed across multiple instances. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax lockhitratiopar CLI Example waddmon OracleInstanceManager lockhitratiopar -t 1 minutes -c critical -R <.8 -n OracleManager Sentry "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. 3. Instance Monitors For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Tivoli Manager for Oracle** Reference Guide 235

254 Usage Notes An efficient parallel node configuration returns a lock hit ratio, or trigger value, near one. The lock hit ratio is calculated as: (consistent_gets - async_global_lock_converts) /consistent_gets See Also The following monitors in this chapter: PCM Conversion Waits and PCM Lock Conversion Time. 236 Version 2.0

255 Long Table Full Table Scans (Interval) Description Monitors the percentage of full table scans that come from long tables for the current monitoring interval. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax longtabscansi CLI Example waddmon OracleInstanceManager longtabscansi -t 1 hours -c critical -R %>= 20 -n OracleManager Sentry -c severe -R %>= 15 -n OracleManager Sentry -c warning -R %>= 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 237

256 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes If the percentage of full table scans that come from long tables is greater than 10%, investigate which tables are being scanned and consider adding indexes to reduce the number of full table scans from long tables. See Also The following monitor in this chapter: Cluster Key Ratio. 238 Version 2.0

257 Number of Deadlocks Description Monitors the total number of deadlocks detected since the instance was started. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax readsysstatd CLI Example waddmon OracleInstanceManager readsysstatd -t 30 minutes -c critical -R % >= 5 -n OracleManager Sentry -c severe -R % >= 2 -n OracleManager Sentry -c warning -R % >= 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Increase greater than 5 Send OracleManager Sentry notice Severe Increase greater than 2 Send OracleManager Sentry notice Warning increase greater than 0 Send OracleManager Sentry notice Normal N/A None Always N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 239

258 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 30 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Oracle automatically resolves deadlocks by rolling back one of the processes. When a deadlock is detected, a trace file is produced in the directory that is specified in the init.ora parameter USER_DUMP_DEST that shows which processes were involved in the deadlock and which processes were blocking and waiting. If deadlocks are occurring, there could be an application design problem. 240 Version 2.0

259 See Also The following monitors in this chapter: Any v$sysstat and Buffer Waits Ratio. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 241

260 Open Cursors Description This monitor determines which session has the greatest number of open cursors, and reports this as a percentage of the limit defined by the OPEN_CURSORS parameter in the init.ora file for the instance. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax opencursors CLI Example waddmon OracleInstanceManager opencursors -t 10 minutes -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 85% Send OracleManager Sentry notice 242 Version 2.0

261 Severity Trigger When Default Actions Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. The TRIGGER_INFO is the username with the most open cursors. The number of open cursors for each session is reported as text on the userinfo lines in the following format: 3. Instance Monitors Open Cursors, Username, Session ID For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 243

262 Views Accessed V$PARAMETER V$OPEN_CURSOR Usage Notes The location of private SQL areas is dependent on the use of a multi-threaded or dedicated server. A multi-threaded server uses the shared buffer pool to store private SQL; a dedicated server uses the user s Program Global Area (PGA). In both cases, the maximum number of private SQL areas that an individual session can process is defined by the OPEN_CURSORS parameter in the init.ora file (default of 50). See Also None Within the bounds of the maximum limit, the setting of this parameter has little or no effect on the performance of the server; therefore, it should be set artificially high to prevent hitting the maximum limit. The maximum is operating-system dependent. 244 Version 2.0

263 PCM Conversion Waits Description Monitors the sessions that are waiting for a PCM lock and reports how long (in seconds) those sessions have been waiting. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax pcmconversionwaits CLI Example waddmon OracleInstanceManager pcmconversionwaits -t 10 minutes -c critical -c severe -c warning -c normal -c always -f manzana:/data/oracle_logging/pcmconversionwaits.log "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. 3. Instance Monitors Results from this monitor are reported as text on the userinfo lines of the output in the following format: Tivoli Manager for Oracle** Reference Guide 245

264 Wait_time_secs, Session_id, DB_Username, Event, File #, Block #, Lock_element_#, State For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SESSION_WAIT V$SESSION Usage Notes If the waiting time is longer than usual for your application, you might need to increase the value of the GC_FILES_TO_LOCKS, GC_RELEASABLE_LOCKS, or GC_ROLLBACK_LOCKS parameter in the init<sid>.ora file. These parameters are static and cannot be changed dynamically; the instance must be shut down and restarted before the parameter changes take effect. Parameter values must be the same for each instance within the same Oracle Parallel Server environment. See Also The following monitor in this chapter: PCM Lock Conversion Time. 246 Version 2.0

265 PCM Lock Conversion Time Description Monitors the time in seconds it takes for a PCM lock conversion to take place. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax pcmlockconversiontime CLI Example waddmon OracleInstanceManager pcmlockconversiontime -t 10 minutes -c critical -c severe -c warning -c normal -c always -f manzana:/data/oracle_logging/pcmlockconversiontime.log "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. 3. Instance Monitors The PCM lock conversion time appears in the output as TRIGGER_INFO. Tivoli Manager for Oracle** Reference Guide 247

266 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSTEM_EVENT Usage Notes If lock conversions are taking a long time, relative to your environment, you might have resource problems such as network, user process, or memory issues. See Also The following monitor in this chapter: Any v$lock, Lock Hit Ratio Parallel Description and PCM Conversion Waits. 248 Version 2.0

267 Percentage of False Pings Description False Pinging occurs when two or more blocks are accessed by two nodes concurrently, where each node is updating a separate block. For each node to access these blocks, the lock on each block must be converted to a shared lock. This lock conversion must occur for each block being accessed, even though not all the blocks are being updated by each node. Run this monitor if you are experiencing an inordinate number of lock conversions. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax percentfalsepings CLI Example waddmon OracleInstanceManager percentfalsepings -t 5 minutes -c critical -c severe -c warning -c normal -c always -f "manzana:/data/oracle_logging/percentfalsepings.log "ProfileName" Suggested Response Levels There are no default actions for this monitor. 3. Instance Monitors Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Tivoli Manager for Oracle** Reference Guide 249

268 Output No output available for this monitor. Results for this monitor appear in the userinfo lines of the output in the following format: Percentage of False Pings, Ping Rate, False Pings For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$LOCK_ACTIVITY V$SYSSTAT Usage Notes None See Also The following monitor in this chapter: Any v$lock. 250 Version 2.0

269 Physical I/O Reads Description This monitor reports the number of physical reads for the worst-case datafile in a database; that is, the datafile with the highest number of physical reads. Use this monitor to determine if any particular datafile is being accessed more than other datafiles. This data can be useful in determining whether a datafile should be moved to another disk because one of the disks is an I/O bottleneck, caused by an excessive number of reads from a datafile. The data can also be used for capacity planning by charting the growth in I/O over time. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax physicalreads CLI Example waddmon OracleInstanceManager physicalreads -t 1 hours -c critical -R > n OracleManager Sentry -c severe -R > n OracleManager Sentry -c warning -R > 900 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 251

270 Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. The datafile with the highest number of physical reads appears as TRIGGER_INFO. Additional datafiles may appear in the userinfo lines. The cumulative number of reads for each datafile is reported in descending order in the following format: Number of Reads, Filename For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$DATAFILE V$FILESTAT 252 Version 2.0

271 Usage Notes None See Also The following monitor in this chapter: Physical I/O Writes. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 253

272 Physical I/O Writes Description This monitor reports the number of physical writes for the worst-case datafile in a database; that is, the datafile with the highest number of physical writes. Use this monitor to determine if any particular datafile is being written to more than other datafiles. This data can be useful in determining whether a datafile should be moved to another disk because one of the disks is an I/O bottleneck caused by an excessive number of writes to a datafile. The data can also be used for capacity planning by charting the growth in I/O over time. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax physicalwrites CLI Example waddmon OracleInstanceManager physicalwrites -t 1 hours -c critical -R > 500 -n OracleManager Sentry -c severe -R > 400 -n OracleManager Sentry -c warning -R > 300 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. 254 Version 2.0

273 Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). The following shows an example output from this monitor. The datafile with the highest number of physical writes appears as TRIGGER_INFO. Additional datafiles may appear in the userinfo lines. The cumulative number of writes for each datafile is reported in descending order in the following format: Number of Writes, Filename For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$DATAFILE 3. Instance Monitors V$FILESTAT Usage Notes None Tivoli Manager for Oracle** Reference Guide 255

274 See Also The following monitor in this chapter: Physical I/O Reads. 256 Version 2.0

275 Ping Rate Description Monitors the rate of pinging across instances. Use this monitor to determine how efficiently the user, application, and batch processes have been distributed across instances in the parallel environment you are monitoring. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax pingrate CLI Example waddmon OracleInstanceManager pingrate -t 1 minutes -c critical -c severe -c warning -c normal -c always -p ProfileName Suggested Response Levels There are no default actions for this monitor. 3. Instance Monitors Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. Tivoli Manager for Oracle** Reference Guide 257

276 For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT V$LOCK_ACTIVITY Usage Notes A high ping rate can indicate the need to redistribute the user-access configuration so that users who access the same information can do so through the same instances. See Also The following monitor in this chapter: Any v$lock and Percentage of False Pings. 258 Version 2.0

277 Process Ratio Description Monitors the current number of Oracle processes as a percentage of the instance maximum. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax processratio CLI Example waddmon OracleInstanceManager processratio -t 1 hours -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 85% Send OracleManager Sentry notice Normal N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 259

278 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$PARAMETER V$PROCESS 260 Version 2.0

279 Usage Notes This monitor reports the current total number of Oracle processes running on the instance, as a percentage of the maximum. The maximum is set by the PROCESSES parameter in the init.ora file for the instance (default of 50). When setting this parameter, consider the following: One process for each connected user One process for each background process See Also None Each instance has at least four background processes (SMON, DBWR, LGWR, and PMON), but there can be a number of additional background processes, including the following: ARCH If the database is running in ARCHIVELOG mode RECO If the distributed option has been installed CKPT If the checkpoint process is running DBnn One process for each additional database writer Dnn One process for each dispatcher Snn One process for each shared server LCKn One process for each parallel server lock process Note: If you increase the value of the PROCESSES parameter, you should also increase the value of SESSIONS if it is explicitly set in init.ora. Otherwise, SESSIONS defaults to PROCESSES * 1.1, which is acceptable. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 261

280 RDBMS State Description Monitors the availability of an Oracle instance. This monitor returns one of the following states: Is Up, Is Shutdown, Is Failed, Is Unavailable, Becomes Up, Becomes Shutdown, Becomes Failed, Becomes Unavailable. Note: For more information on the availability states for this monitor, see Appendix C, Operator Groups (Monitor Triggers). Authorization Role user, admin, and oracle_monitor Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax rdbmsstate CLI Example waddmon OracleInstanceManager rdbmsstate -t 5 minutes -c critical -R!= up -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Is unavailable Send OracleManager Sentry notice 262 Version 2.0

281 Severity Trigger When Default Actions Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 5 minutes. The following shows an example output from this monitor. The availability state of the instance is reported as TRIGGER_INFO. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed None Usage Notes This monitor checks the availability of the instance. You can set the trigger on the following values: 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 263

282 Is Up Is Shutdown Is Failed Is Unavailable Becomes Up Becomes Shutdown Becomes Failed Becomes Unavailable If you set the trigger value to Becomes..., the monitor only reports a critical event the first time it is unable to connect to the instance. This prevents the same message from repeatedly being displayed on an administrator s desktop. If you set the trigger value to... Failed, the monitor only reports a critical event if the instance crashes, rather than being shut down by an administrator. Running this monitor changes the icon of the database instance to reflect the state returned by the monitor. When a database is running, no status is displayed. When the database is shut down by a DBA, the status SHUTDOWN appears across the icon. When the database crashes, the status FAILED appears across the icon. It might be appropriate to set the critical level to Becomes Failed and the warning level to Becomes Shutdown. This combination of events gives a critical error when a database crashes and a warning when an instance is shut down by a DBA. See Also The following monitor from the OracleDatabaseManager Monitoring Collection: Alerts. 264 Version 2.0

283 Recursive Call Rate Description Reports the number of recursive calls per second. A recursive call occurs when one SQL statement requires the execution of a further separate SQL statement. A continued increase in the reported figure indicates poor or decreasing system performance. Some recursive activity is unavoidable. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax recursivecallrate CLI Example waddmon OracleInstanceManager recursivecallrate -t 1 hours -c critical -R >= 10 -n OracleManager Sentry -c severe -R >= 7 -n OracleManager Sentry -c warning -R >= 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. 3. Instance Monitors Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Tivoli Manager for Oracle** Reference Guide 265

284 Output The following shows an example output from this monitor. The cumulative number of calls during the lifetime of the instance is reported as userinfo. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Recursive calls can be generated by the following activities: An object requiring an additional extent for storage (dynamic extension) Misses on the dictionary cache Firing of database triggers DDL statements Execution of SQL statements within stored procedures, packages, functions, and anonymous PL/SQL blocks Enforcement of referential integrity constraints 266 Version 2.0

285 If Oracle is making an inordinate number of recursive calls, try to determine which of the previously listed activities is causing most of the recursive calls. Run the application through TKPROF with EXPLAIN PLAN to see what the application is doing. Also, monitor the number of extents in the database to see if there is noticeable dynamic extension. If the recursive calls are caused by dynamic extension, you can reduce the number of calls by allocating larger extents to the relevant objects. A dictionary cache that is too small can also cause recursive calls. See Also The following monitor in this chapter: Recursive Calls. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 267

286 Recursive Calls Description Reports the number of recursive calls for the instance. A recursive call occurs when one SQL statement requires the execution of a further separate SQL statement. Some recursive activity is unavoidable. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax readsysstatr CLI Example waddmon OracleInstanceManager readsysstatr -t 1 hours -c critical -R >= n OracleManager Sentry -c severe -R >= n OracleManager Sentry -c warning -R >= n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 268 Version 2.0

287 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Recursive calls can be generated by the following activities: An object requiring an additional extent for storage (dynamic extension) Misses on the dictionary cache Firing of database triggers DDL statements Execution of SQL statements within stored procedures, packages, functions, and anonymous PL/SQL blocks Enforcement of referential integrity constraints 3. Instance Monitors If Oracle is making an inordinate number of recursive calls, try to determine which of the previously listed activities is causing most of Tivoli Manager for Oracle** Reference Guide 269

288 the recursive calls. Run the application through TKPROF with EXPLAIN PLAN to see what the application is doing. Also, monitor the number of extents in the database to see if there is noticeable dynamic extension. If the recursive calls are caused by dynamic extension, you can reduce the number of calls by allocating larger extents to the relevant objects. A dictionary cache that is too small can also cause recursive calls. See Also The following monitor in this chapter: Recursive Call Rate. 270 Version 2.0

289 Recursive To User Calls Ratio Description Monitors the number of recursive calls as a ratio of the number of user calls. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax recursivetousercalls CLI Example waddmon OracleInstanceManager recursivetousercalls -t 10 minutes -c critical -R % >= 12 -n OracleManager Sentry -c severe -R % >= 10 -n OracleManager Sentry -c warning -R % >= 8 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical % Increase of 12 Send OracleManager Sentry notice Severe % Increase of 10 Send Oracle Sentry notice Warning % Increase of 8 Send Oracle Sentry notice Normal N/A None Always N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 271

290 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes A change in this ratio can reflect an application change or the need to increase the size of the shared buffer pool. Note: A marked change in the data definition language (DDL) workload on the database will also affect this ratio. Use the % Increase of operator to monitor changes in this ratio, and in conjunction with other monitors, to tune the SHARED_POOL_SIZE parameter in the init.ora file for the instance. 272 Version 2.0

291 See Also The following monitors in this chapter: Call Rate, Calls Per Transaction, Recursive Calls, and Recursive Call Rate. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 273

292 Redo Allocation Latch Ratio Description Monitors, as a percentage, the ratio of misses to gets for the redo allocation latch. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax redolatchratio CLI Example waddmon OracleInstanceManager redolatchratio -t 10 minutes -c critical -R > 3 -n OracleManager Sentry -c severe -R > 2 -n OracleManager Sentry -c warning -R > 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 3% Send OracleManager Sentry notice Severe Greater than 2% Send OracleManager Sentry notice Warning Greater than 1% Send OracleManager Sentry notice Normal N/A None 274 Version 2.0

293 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. No output available for this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$LATCH Usage Notes On single-cpu systems, all writes are small and are made on the redo allocation latch. You can improve performance by decreasing the value of the init.ora parameter LOG_SMALL_ENTRY_MAX_SIZE. Before a process changes information in a block, it must create the redo record in the log buffer. The allocation of space in the log buffer is controlled by the redo allocation latch. The process must acquire this latch and can copy it while holding it if the size of the redo entry is smaller than LOG_SMALL_ENTRY_MAX_SIZE. Otherwise, the process must acquire a redo copy latch to create the redo record. Decrease the value of LOG_SMALL_ENTRY_MAX_SIZE to reduce the redo allocation latch contention. This forces Oracle to use more redo copy latches. 3. Instance Monitors Note: For best results, run this monitor only on multiple-cpu systems. Tivoli Manager for Oracle** Reference Guide 275

294 See Also The following monitor in this chapter: Redo Copy Latch Ratio and Redo Small Copy Ratio. 276 Version 2.0

295 Redo Copy Latch Ratio Description Monitors, as a percentage, the ratio of misses to gets for the redo copy latch. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax redoclatchratio CLI Example waddmon OracleInstanceManager redoclatchratio -t 10 minutes -c critical -R %>= 3 -n OracleManager Sentry -c severe -R %>= 2 -n OracleManager Sentry -c warning -R %>= 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical % Increase of 3 Send OracleManager Sentry notice Severe % Increase of 2 Send OracleManager Sentry notice Warning % Increase of 1 Send OracleManager Sentry notice Normal N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 277

296 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. No output available for this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$LATCH Usage Notes If there are an increasing number of timeouts, increase the value of the init.ora parameter LOG_SIMULTANEOUS_COPIES. On a system with multiple CPUs, it is possible to have more than one redo copy latch per CPU. LOG_SIMULTANEOUS_COPIES defaults to the number of CPUs, but must be increased to twice the number of CPUs on the system if you are experiencing redo copy latch contention. Do not rely on the init.ora parameter CPU_COUNT to tell you how many CPUs a machine has. On many Oracle platforms, CPU_COUNT is set to zero and Oracle works out how many CPUs the machine actually has. Note: Run this monitor only on multiple-cpu systems. See Also The following monitor in this chapter: Redo Allocation Latch Ratio and Redo Copy Latch Ratio. 278 Version 2.0

297 Redo Log Space Waits Description This monitor measures the number of times that a user process was unable to allocate space in the redo log buffer. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax redologwaits CLI Example waddmon OracleInstanceManager redologwaits -t 10 minutes -c critical -R ->> 4 -n OracleManager Sentry -c severe -R ->> 2 -n OracleManager Sentry -c warning -R ->> 0 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Increases beyond 4 Send OracleManager Sentry notice Severe Increases beyond 2 Send OracleManager Sentry notice Warning Increases beyond 0 Send OracleManager Sentry notice Normal N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 279

298 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes If this value increments constantly, increase the size of the redo log buffer by increasing the value of the init.ora parameter LOG_BUFFER. Increasing the size of the online redo log files can reduce the number of redo log space waits. 280 Version 2.0

299 This monitor uses the redo log space requests statistic. The size of the LOG_BUFFER parameter must always be a multiple of the database block size. Increasing the size of the online redo log files may also decrease the number of redo log space waits. See Also The following monitor in this chapter: Average Redo Entry Size. The following monitors in the OracleDatabaseManager Monitoring Collection: Archive Free Space and Archive Space (Number of Redo Logs). 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 281

300 Redo Logs Not Archived Description This monitor reports the number of redo log files that have not been archived, which indicates that the archive process is falling behind. This monitor is applicable only when the database is running in ARCHIVELOG mode. If the database is in NOARCHIVELOG mode, the monitor returns a value of zero. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax redosnotarchived CLI Example waddmon OracleInstanceManager redosnotarchived -t 10 minutes -c critical -R > 3 -n OracleManager Sentry -c severe -R > 2 -n OracleManager Sentry -c warning -R > 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 3 Send OracleManager Sentry notice Severe Greater than 2 Send OracleManager Sentry notice 282 Version 2.0

301 Severity Trigger When Default Actions Warning Greater than 1 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$PARAMETER 3. Instance Monitors V$LOG Tivoli Manager for Oracle** Reference Guide 283

302 Usage Notes If this monitor returns a non-zero value, the ARCH process is having difficulty keeping up with the LGWR process. It is not possible to have multiple ARCH processes, so the workaround is to connect to the instance and issue the following command: ALTER SYSTEM ARCHIVE LOG ALL This should help the system catch up to the rate at which redo logs are being created. See Also The following monitors in this chapter: Active Transactions and Block Changes Per Transaction. 284 Version 2.0

303 Redo Small Copy Ratio Description Monitors, as a percentage, the ratio of the total number of redo small copies to the total number of redo entries. A redo small copy is a redo entry that is smaller than the LOG_SMALL_ENTRY_MAX_SIZE parameter in the init.ora file for the instance. Small copy redo entries are copied on the redo allocation latch. If the redo entry is larger than this parameter, copies are made using a redo copy latch on multiple processor systems. On single-cpu systems, all writes are small and are made on the redo allocation latch. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax redosmallcopyratio CLI Example waddmon OracleInstanceManager redosmallcopyratio -t 10 minutes -c critical -R > 3 -n OracleManager Sentry -c severe -R > 2 -n OracleManager Sentry -c warning -R > 1 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 285

304 Severity Trigger When Default Actions Critical Greater than 3 Send OracleManager Sentry notice Severe Greater than 2 Send OracleManager Sentry notice Warning Greater than 1 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT 286 Version 2.0

305 Usage Notes If there are a noticeable number of redo small copies and there is a redo allocation latch contention problem (see the Redo Allocation Latch Ratio monitor), decrease the value of the LOG_SMALL_ENTRY_MAX_SIZE parameter in the init.ora file for the instance. See Also The following monitor in this chapter: Redo Copy Latch Ratio and Redo Allocation Latch Ratio. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 287

306 Rollback Waits Description Monitors, as a percentage, the ratio of rollback segment header waits to rollback segment header gets. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax rollbackwaits CLI Example waddmon OracleInstanceManager rollbackwaits -t 10 minutes -c critical -R > 5 -n OracleManager Sentry -c severe -R > 3 -n OracleManager Sentry -c warning -R > 2 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 5 Send OracleManager Sentry notice Severe Greater than 3 Send OracleManager Sentry notice Warning Greater than 2 Send OracleManager Sentry notice Normal N/A None Always N/A None 288 Version 2.0

307 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. No output available for this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$ROLLSTAT Usage Notes The ratio is calculated as: (Average_waits / Average_gets) * 100 See Also None If this monitor reports a regularly increasing rollback wait ratio, create additional rollback segments in the database. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 289

308 Row Source Ratio Description This monitor reports the percentage of total rows retrieved that came from full-table scans. Ideally, this percentage should be small, but it is dependent on the application design. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax rowsourceratio CLI Example waddmon OracleInstanceManager rowsourceratio -t 1 hours -c critical -R > 15 -n OracleManager Sentry -c severe -R > 12 -n OracleManager Sentry -c warning -R > 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). 290 Version 2.0

309 Output The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes Row source ratio is calculated as: 100 * S/(S+R) where: S = rows obtained by table scans 3. Instance Monitors R = rows obtained by rowid If more than 10 percent (or whatever figure is deemed to be unacceptable) of the rows are retrieved from full table scans, use the Long Table Full Table Scans (Interval) monitor to determine the Tivoli Manager for Oracle** Reference Guide 291

310 percentage of full-table scans that are from short tables. If a table has a small number of rows, a full-table scan may be more efficient than an index scan. See Also The following monitor in this chapter: Long Table Full Table Scans (Interval). 292 Version 2.0

311 Shared Server Process Ratio Description Monitors the current number of shared-server processes as a percentage of the instance limit. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax sharedserverratio CLI Example waddmon OracleInstanceManager sharedserverratio -t 10 minutes -c critical -R > 95 -n OracleManager Sentry -c severe -R > 90 -n OracleManager Sentry -c warning -R > 85 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 95% Send OracleManager Sentry notice Severe Greater than 90% Send OracleManager Sentry notice Warning Greater than 85% Send OracleManager Sentry notice Normal N/A None Always N/A None 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 293

312 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$PARAMETER V$SHARED_SERVER Usage Notes The instance limit is set through the MTS_MAX_SERVERS parameter in the init.ora file for the instance. This controls the maximum number of shared server processes allowed to run simultaneously (the default is 20). If the shared server process ratio is greater than 85%, consider increasing the MTS_MAX_SERVERS parameter in the init.ora file for the instance. 294 Version 2.0

313 See Also None Note: This monitor is relevant only if the instance is configured for the multi-threaded server. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 295

314 Shared Server Wait Time Description This monitor reports the average wait time (in hundredths of a second) that a request waits in the request queue. Note: This monitor is relevant only if the instance is configured for the multi-threaded server. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax sharedserverwait CLI Example waddmon OracleInstanceManager sharedserverwait -t 10 minutes -c critical -R > 25 -n OracleManager Sentry -c severe -R > 18 -n OracleManager Sentry -c warning -R > 10 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than 25 Send OracleManager Sentry notice Severe Greater than 18 Send OracleManager Sentry notice 296 Version 2.0

315 Severity Trigger When Default Actions Warning Greater than 10 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. No output available for this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$QUEUE Usage Notes If the average request time is greater than 0.1 seconds, you can improve performance by adding more shared-server processes. To add more shared-server processes, increase the value of the init.ora parameter MTS_MAX_SERVERS. If the average request time is greater than 0.1 seconds, consider increasing the MTS_MAX_SERVERS parameter in the init.ora file for the instance. See Also The following monitor in this chapter: Dispatcher Busy Rate. 3. Instance Monitors Tivoli Manager for Oracle** Reference Guide 297

316 Sort Overflow Ratio Description This monitor reports the sort overflow ratio. This ratio yields the number of sorts that are using temporary segments. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax sortoverflowratio CLI Example waddmon OracleInstanceManager sortoverflowratio -t 10 minutes -c critical -R >.2 -n OracleManager Sentry -c severe -R >.1 -n OracleManager Sentry -c warning -R >.05 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table lists the default actions for this monitoring source. Severity Trigger When Default Actions Critical Greater than.2 Send OracleManager Sentry notice Severe Greater than.1 Send OracleManager Sentry notice Warning Greater than.05 Send OracleManager Sentry notice Normal N/A None 298 Version 2.0

317 Severity Trigger When Default Actions Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). Output Suggested monitoring schedule: Every 10 minutes. The following shows an example output from this monitor. For a description of the monitor output, see Understanding Monitor Output on page 6. Views Accessed V$SYSSTAT Usage Notes For a system running mainly medium-sized sorts, increasing the SORT_AREA_SIZE can improve performance. 3. Instance Monitors The sort overflow ratio is calculated as: Tivoli Manager for Oracle** Reference Guide 299

318 Sorts(disk) / (Sorts(memory) + Sorts(disk)) Disk sorts require creation of temporary segments on disk to store the intermediate sort results. This happens if the amount of data being sorted is greater than the value of the init.ora parameter SORT_AREA_SIZE. Ideally, the ratio of disk sorts to memory sorts should be less than 5%. To increase the percentage of memory sorts, increase the value of SORT_AREA_SIZE. However, the sort area is allocated on a per-user basis, so increase the value in small increments to avoid allocating too much memory to sort areas. See Also The following monitor in the OracleDatabaseManager Monitoring Collection: Temporary Extents. 300 Version 2.0

319 User Rollback Ratio Description Monitors the ratio of user rollbacks to the total number of transactions. Authorization Role oracle_monitor and user Target Endpoint OracleInstanceManager GUI Data Entry Fields None CLI Syntax userrollbackratio CLI Example waddmon OracleInstanceManager userrollbackratio -t 1 hours -c critical -R >.2 -n OracleManager Sentry -c severe -R >.1 -n OracleManager Sentry -c warning -R >.05 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Output Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). No output available for this monitor. 3. Instance Monitors For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 301

320 Views Accessed V$SYSSTAT Usage Notes User rollback ratio is calculated as: Rollbacks /(Commits + Rollbacks) This ratio indicates that application transactions are failing, or that users are rolling back transactions. When a rollback occurs, considerable system resource is required. See Also The following monitor in this chapter: Block Changes Per Transaction 302 Version 2.0

321 4 Async Monitors 4. Async Monitors The OracleManagerAsync monitoring collection provides monitoring sources for managing large databases with thousands of segments and objects. The monitors in this collection cannot complete monitoring within one minute. For these monitors to return results, you must use an asynchronous monitor and a background monitor for each source. You set the arguments with the background monitor and set the trigger and response criteria with the asynchronous monitor. You must use these monitors in conjunction to receive valid results; however, you can distribute only one instance of each asynchronous monitor to each database endpoint. Profiles that contain OracleManagerAsync monitors should be distributed to Oracle database endpoints. List of OracleManagerAsync Monitoring Sources The following table lists the monitoring sources in this collection alphabetically by their graphical user interface (GUI) names. It also includes their command line interface (CLI) names, monitor numbers, and whether they support Distributed Monitoring Logging. Monitors that support Distributed Monitoring Logging have a Yes in the Log File column. For more information, see Using Distributed Monitoring Logging on page 9. Tivoli Manager for Oracle** Reference Guide 303

322 GUI Name CLI Name Monitor Number Extents Background and Asynchronous Extents by Tablespace Background and Asynchronous Extents by User Background and Asynchronous Free Space Deficit Background and Asynchronous Free Space Deficit by Tablespace Background and Asynchronous Free Space Deficit by User Background and Asynchronous Index Statistics Background and Asynchronous Maximum Extents Background and Asynchronous Maximum Extents by Tablespace Background and Asynchronous Maximum Extents by User Background and Asynchronous SQL Number Background and Asynchronous SQL String Background and Asynchronous Temporary Extents Background and Asynchronous Temporary Extents by Tablespace Background and Asynchronous Temporary Extents by User Background and Asynchronous extentsbackground extentsasync extentsbytablespacebackground extentsbytablespaceasync extentsbyuserbackground extentsbyuserasync freespacedefbackground freespacedefasync freespacedeftbackground freespacedeftasync freespacedefubackground freespacedefuasync indexstatisticsbackground indexstatisticsasync maximumextentsbackground maximumextentsasync maximumextentstbackground maximumextentstasync maximumextentsubackground maximumextentsuasync freeformsqlnbackground freeformsqlnasync freeformsqlsbackground freeformsqlsasync temporaryextentsbackground temporaryextentsasync temporaryextentstbackground temporaryextentstasync temporaryextentsubackground temporaryextentsuasync 94 n/a Yes 100 n/a Yes 101 n/a Yes 93 n/a Yes 106 n/a Yes 107 n/a Yes 151 n/a No 92 n/a Yes 102 n/a Yes 103 n/a Yes 96 n/a Yes 97 n/a Yes 95 n/a Yes 104 n/a Yes 105 n/a Yes Log File 304 Version 2.0

323 GUI Name CLI Name Monitor Number Unix SQL*Net V1 TCP/IP Listener Background and Asynchronous Unix SQL*Net V2 Listener Background and Asynchronous netonetcpipbackground netonetcpipasync nettwolistenerbackground nettwolistenerasync 98 n/a No 99 n/a No Log File 4. Async Monitors Tivoli Manager for Oracle** Reference Guide 305

324 Extents Background and Asynchronous Description Monitors the number of extents allocated to all objects and reports the largest number of extents found. The monitor also reports all objects that have more extents than the number specified as the <numberofextents> argument to the monitor. It does not check objects of segment_type CACHE. Use the Extents Background monitor to set arguments. Use the Extents Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes You can use this monitor to see which objects in a database have a large number of extents. This information can be used to chart the growth of objects. This information also can be used in conjunction with the Maximum Extents Background and Asynchronous monitors to predict when an object is going to run out of extents. You might need to allocate additional extents to the object, or export it and recreate it with a larger extent size. See Also The following monitors in this chapter: Extents by Tablespace Background and Asynchronous, Extents by User Background and Asynchronous, Maximum Extents Background and Asynchronous, Maximum Extents by Tablespace Background and Asynchronous, Maximum Extents 306 Version 2.0

325 by User Background and Asynchronous. 4. Async Monitors Tivoli Manager for Oracle** Reference Guide 307

326 Extents Background CLI Syntax extentsbackground a <numberofextents> The following briefly describes the argument for this monitor. <numberofextents> Specifies the threshold number of extents. GUI Name: Extents Greater Than CLI Example waddmon OracleManagerAsync extentsbackground -a 20 -t 30 minutes "ProfileName" Suggested Monitoring Schedule Site specific GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Extents Background monitor; a description of each field follows. Output None Extents Greater Than Specifies the threshold number of extents. 308 Version 2.0

327 Extents Asynchronous CLI Syntax extentsasync CLI Example waddmon OracleManagerAsync extentsasync -c critical -c severe -c warning -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Tivoli Manager for Oracle** Reference Guide 309

328 Output The following shows an example output from this monitor. This monitor returns, as its trigger value, the largest number of extents for an object. The object with the largest number of extents is reported as TRIGGER_INFO. The monitor may also return additional objects in the userinfo lines. Information for all objects is reported in descending order, based on the number of extents, in the following format: Number of Extents, Object Name, Object Owner, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

329 Extents by Tablespace Background and Asynchronous Description Monitors how many extents are allocated to all database objects within specified tablespaces and reports the largest number of extents found. 4. Async Monitors Use the Extents by Tablespace Background monitor to set arguments. Use the Extents by Tablespace Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes You can use this monitor to see which objects in a database have a large number of extents. This information can be used to chart the growth of objects. This information also can be used in conjunction with the Maximum Extents Background and Asynchronous monitors to predict when an object is going to run out of extents. You might need to allocate additional extents to the object, or export it and recreate it with a larger extent size. See Also The following monitors in this chapter: Extents Background and Asynchronous, Extents by User Background and Asynchronous, Maximum Extents Background and Asynchronous, Maximum Extents by Tablespace Background and Asynchronous, Maximum Extents by User Background and Asynchronous. Tivoli Manager for Oracle** Reference Guide 311

330 Extents by Tablespace Background CLI Syntax extentsbytablespacebackground a <numberofextents> a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. <numberofextents> Specifies the threshold number of extents. GUI Name: Extents Greater Than {in not in} Includes or excludes the contents of the tablespace name field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Name Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. CLI Example waddmon OracleManagerAsync extentsbytablespacebackground -a 30 -a in -a RBS -t 30 minutes "ProfileName" 312 Version 2.0

331 Suggested Monitoring Schedule Site specific GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Extents by tablespace Background monitor; a description of each field follows. 4. Async Monitors Output None Extents Greater Than Specifies the threshold number of extents. Include/Exclude Includes or excludes the contents of the tablespace name field. Tablespace Name Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. Tivoli Manager for Oracle** Reference Guide 313

332 Extents by Tablespace Asynchronous CLI Syntax extentsbytablespaceasync CLI Example waddmon OracleManagerAsync extentsbytablespaceasync -c critical -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Output The following shows an example output from this monitor. 314 Version 2.0

333 This monitor returns, as its trigger value, the largest number of extents for an object in the specified tablespaces. The object with the most extents in the specified tablespaces is reported as TRIGGER_INFO. The monitor may also return additional objects in the userinfo lines. Information for all objects is reported in descending order, based on the number of extents, in the following format: Number of Extents, Object Name, Object Owner 4. Async Monitors Note: If SQL does not return any rows, it reports an error. For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 315

334 Extents by User Background and Asynchronous Description Monitors how many extents have been allocated to all database objects for a specified user and reports the largest number of extents found. Use the Extents by User Background monitor to set arguments. Use the Extents by User Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes You can use this monitor to see which objects in a database have a large number of extents. This information can be used to chart the growth of objects. This information also can be used in conjunction with the Maximum Extents Background and Asynchronous monitors to predict when an object is going to run out of extents. You might need to allocate additional extents to the object, or export it and recreate it with a larger extent size. See Also The following monitors in this chapter: Extents Background and Asynchronous, Extents by Tablespace Background and Asynchronous, Maximum Extents Background and Asynchronous, Maximum Extents by Tablespace Background and Asynchronous, Maximum Extents by User Background and Asynchronous. 316 Version 2.0

335 Extents by User Background CLI Syntax extentsbyuserbackground a <numberofextents> a <username> The following briefly describes the arguments for this monitor. <numberofextents> Specifies the threshold number of extents. GUI Name: Extents Greater Than <username> Specifies the Oracle user name. GUI Name: User Name 4. Async Monitors CLI Example waddmon OracleManagerAsync extentsbyuserbackground -a 0 -a SYS -t 30 minutes "ProfileName" Suggested Monitoring Schedule Site specific GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Extents by User Background monitor; a description of each field follows. Extents Greater Than Specifies the threshold number of extents. Tivoli Manager for Oracle** Reference Guide 317

336 Output None User Name Specifies the Oracle user name. 318 Version 2.0

337 Extents by User Asynchronous CLI Syntax extentsbyuserasync CLI Example waddmon OracleManagerAsync extentsbyuserasync -c critical -c severe -c warning -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Tivoli Manager for Oracle** Reference Guide 319

338 Output The following shows an example output from this monitor. This monitor returns, as its trigger value, the largest number of extents for an object owned by a specified user. The object with the most extents is reported as TRIGGER_INFO. The monitor may also return additional objects in the userinfo lines. Information for all objects is reported in descending order, based on the number of extents, in the following format: Number of Extents, Object Name, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

339 Free Space Deficit Background and Asynchronous Description Checks whether any segments are unable to allocate their next extent because of insufficient free space in the tablespace, and not because the segments reached MAXEXTENTS. The reported trigger value represents the worst-case equity (available space less required space); a negative equity figure means that the next extent for that segment will fail. It does not check objects of segment_type CACHE. If the Exclude Rollback Segments argument is set to Yes, the monitor does not check the free space in any rollback segments. 4. Async Monitors Use the Free Space Deficit Background monitor to set arguments. Use the Free Space Deficit Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS DBA_FREE_SPACE Usage Notes A table is created with an initial extent of 1 MB, next extent 1 MB, and PCTINCREASE of 25%. If the table grows to six extents, the extent sizes are as follows: Extent Number Extent Size (bytes) 1 1,024, ,024, ,280, ,600,000 Tivoli Manager for Oracle** Reference Guide 321

340 Extent Number Extent Size (bytes) 5 2,000, ,500,000 The size of the seventh extent is 3,125,000 bytes. If the free space in the tablespace is 3 MB (3,072,000 bytes), the table cannot allocate its seventh extent. The equity is (3,072,000-3,125,000) = (-53,000 bytes). This is the figure that is checked by the monitor. If a segment is unable to allocate another extent, a number of corrective actions can be taken: add another file to the relevant tablespace, change the size of the next extent using ALTER TABLE ALLOCATE EXTENT, or export the segment and recreate it with different storage parameters. Tivoli recommends that all segments be created with a PCTINCREASE of 0. See Also The following monitors in this chapter: Free Space Deficit by Tablespace Background and Asynchronous, Free Space Deficit by User Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace and Number of Datafiles. 322 Version 2.0

341 Free Space Deficit Background CLI Syntax freespacedefbackground a {Yes No} The following briefly describes the argument for this monitor. {Yes No} Yes ignores the rollback segments. No does not ignore the rollback segments. GUI Name: Exclude Rollback Segments 4. Async Monitors CLI Example waddmon OracleManagerAsync freespacedefbackground -a No -t 30 minutes "ProfileName" Suggested Monitoring Schedule Every 30 minutes. GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space deficit Background monitor; a description of each field follows. Output None Exclude Rollback Segment Yes ignores the rollback segments. No does not ignore the rollback segments. Tivoli Manager for Oracle** Reference Guide 323

342 Free Space Deficit Asynchronous CLI Syntax freespacedefasync CLI Example waddmon OracleManagerAsync freespacedefasync -c critical -R < 0 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 0 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None 324 Version 2.0

343 Output The following shows an example output from this monitor. 4. Async Monitors The object with the worst-case equity is reported as TRIGGER_INFO. Additional information for all objects returned appears as text in the userinfo lines in the following format: Equity, Object Name, Tablespace Name, Object Owner For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 325

344 Free Space Deficit by Tablespace Background and Asynchronous Description Checks whether any segments, within specified tablespaces, are unable to allocate their next extent because of insufficient free space in the tablespace, and not because the segments reached MAXEXTENTS. The reported trigger value represents the worst-case equity (available space less required space); a negative equity figure means that the next extent for that segment will fail. The monitor does not check objects of segment_type CACHE. Use the Free Space Deficit by Tablespace Background monitor to set arguments. Use the Free Space Deficit by Tablespace Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS DBA_FREE_SPACE Usage Notes A table is created with an initial extent of 1 MB, next extent 1 MB, and PCTINCREASE of 25%. If the table grows to six extents, the extent sizes are as follows: Extent Number Extent Size (bytes) 1 1,024, ,024, ,280, ,600, Version 2.0

345 Extent Number Extent Size (bytes) 5 2,000, ,500,000 The size of the seventh extent is 3,125,000 bytes. If the free space in the tablespace is 3 MB (3,072,000 bytes), the table will not be able to allocate its seventh extent. The equity is (3,072,000-3,125,000) = -(53,000) bytes. This is the figure that is checked by the monitor. 4. Async Monitors If a segment is unable to allocate another extent, a number of corrective actions can be taken: add another file to the relevant tablespace, change the size of the next extent using ALTER TABLE ALLOCATE EXTENT, or export the segment and recreate it with different storage parameters. Tivoli recommends that all segments be created with a PCTINCREASE of 0. See Also The following monitors in this chapter: Free Space Deficit Background and Asynchronous, Free Space Deficit by User Background and Asynchronous, Maximum Extents by Tablespace Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace and Number of Datafiles. Tivoli Manager for Oracle** Reference Guide 327

346 Free Space Deficit by Tablespace Background CLI Syntax freespacedeftbackground a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace name field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Name Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. CLI Example waddmon OracleManagerAsync freespacedeftbackground -a in -a users -t 30 minutes "ProfileName" Suggested Monitoring Schedule Every 30 minutes 328 Version 2.0

347 GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space deficit by tablespace Background monitor; a description of each field follows. 4. Async Monitors Output None Include/Exclude Includes or excludes the contents of the tablespace name field. Tablespace Name Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. Tivoli Manager for Oracle** Reference Guide 329

348 Free Space Deficit by Tablespace Asynchronous CLI Syntax freespacedeftasync CLI Example waddmon OracleManagerAsync freespacedeftasync -c critical -R < 0 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 0 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None 330 Version 2.0

349 Output The following shows an example output from this monitor. 4. Async Monitors The object with the worst-case equity for the specified tablespaces is reported as TRIGGER_INFO. Additional information for all objects returned appears as text in the userinfo lines in the following format: Equity, Object Name, Object Owner For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 331

350 Free Space Deficit by User Background and Asynchronous Description Checks whether any segments, for a specified user, are unable to allocate their next extent because of insufficient free space in the tablespace, and not because the segments reached MAXEXTENTS. The reported trigger value represents the worst-case equity (available space less required space); a negative equity figure means that the next extent for that segment will fail. The monitor does not check objects of segment_type CACHE. Use the Free Space Deficit by User Background monitor to set arguments. Use the Free Space Deficit by User Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS DBA_FREE_SPACE Usage Notes A table is created with an initial extent of 1 MB, next extent 1 MB, and PCTINCREASE of 25%. If the table grows to six extents, the extent sizes are as follows: Extent Number Extent Size (bytes) 1 1,024, ,024, ,280, ,600, Version 2.0

351 Extent Number Extent Size (bytes) 5 2,000, ,500,000 The size of the seventh extent is 3,125,000 bytes. If the free space in the tablespace is 3 MB (3,072,000 bytes), the table will not be able to allocate its seventh extent. The equity is (3,072,000-3,125,000) = -(53,000) bytes. This is the figure that is checked by the monitor. 4. Async Monitors If a segment is unable to allocate another extent, a number of corrective actions can be taken: add another file to the relevant tablespace, change the size of the next extent using ALTER TABLE ALLOCATE EXTENT, or export the segment and recreate it with different storage parameters. Tivoli recommends that all segments be created with a PCTINCREASE of 0. See Also The following monitors in this chapter: Free Space Deficit Background and Asynchronous, Free Space Deficit by Tablespace Background and Asynchronous, Maximum Extents by Tablespace Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace. Tivoli Manager for Oracle** Reference Guide 333

352 Free Space Deficit by User Background CLI Syntax freespacedefubackground a <username> The following briefly describes the argument for this monitor. <username> Specifies the Oracle user name. GUI Name: User Name CLI Example waddmon OracleManagerAsync freespacedefubackground -a scott -t 30 minutes "ProfileName" Suggested Monitoring Schedule Every 30 minutes. GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Free space deficit by user Background monitor; a description of each field follows. Output None User Name Specifies the Oracle user name. 334 Version 2.0

353 Free Space Deficit by User Asynchronous CLI Syntax freespacedefuasync CLI Example waddmon OracleManagerAsync freespacedefuasync -c critical -R < 0 -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 0 Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Tivoli Manager for Oracle** Reference Guide 335

354 Output The following shows an example output from this monitor. The object with the worst-case equity for the specified user is reported as TRIGGER_INFO. Additional information for all objects returned appears as text in the userinfo lines in the following format: Equity, Object Name, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

355 Index Statistics Background and Asynchronous Description Monitors the percentage of deleted rows from the user-specified index that have not been repopulated. Use the Index Statistics Background monitor to set arguments. Use the Index Statistics Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role user and oracle_monitor Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS 4. Async Monitors DBA_FREE_SPACE Usage Notes A large percentage of deleted rows in an index can indicate that the index needs to be rebuilt or coalesced. Tivoli does not recommend using this monitor on indexes that will be inserted to and deleted from frequently. See Also The following monitor in the OracleDatabaseManager Monitoring Collection: Index Statistics Tivoli Manager for Oracle** Reference Guide 337

356 Index Statistics Background CLI Syntax indexstatisticsbackground a <index_name> The following briefly describes the argument for this monitor. <index_name> The name of the index to be monitored. GUI Name: Index Name CLI Example waddmon OracleDatabaseManager indexstatisticsbackground -a Index Name -t 1 hours "ProfileName" Suggested Monitoring Schedule Once every hour GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Index statistics monitor; a description of each field follows. Output None Index Name The name of the index to be monitored. 338 Version 2.0

357 Index Statistics Asynchronous CLI Syntax indexstatisticsasync CLI Example waddmon OracleDatabaseManager indexstatisticsasync "ProfileName" 4. Async Monitors Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Output The following shows an example output from this monitor. Index information is reported as text on the userinfo lines, in the following format: Index Name Tivoli Manager for Oracle** Reference Guide 339

358 For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

359 Maximum Extents Background and Asynchronous Description This monitor returns the smallest number of free extents found for a segment. This monitor also checks how close each object is to the value of MAXEXTENTS and reports the number of extents that can still be allocated. It does not check objects of segment_type CACHE. If the Exclude Rollback Segments argument is set to Yes, the monitor does not check the number of extents in any rollback segments. 4. Async Monitors Use the Maximum Extents Background monitor to set arguments. Use the Maximum Extents Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter and the object needs to allocate an additional extent, the operation will fail. If the value of MAXEXTENTS is less than the maximum allowable (see the following table), increase the value of MAXEXTENTS. Otherwise, export the object, drop and recreate the object with larger extent sizes, and import the data. Block Size MAXEXTENTS 1KB 57 2 KB KB 249 Tivoli Manager for Oracle** Reference Guide 341

360 Block Size MAXEXTENTS 8 KB 505 See Also The following monitors in this chapter: Maximum Extents by Tablespace Background and Asynchronous, Maximum Extents by User Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace and Number of Datafiles 342 Version 2.0

361 Maximum Extents Background CLI Syntax maximumextentsbackground a {Yes No} The following briefly describes the argument for this monitor. {Yes No} Yes ignores the rollback segments. No does not ignore the rollback segments. GUI Name: Exclude Rollback Segments 4. Async Monitors CLI Example waddmon OracleManagerAsync maximumextentsbackground -a No -t 1 hours "ProfileName" Suggested Monitoring Schedule Once every hour. GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Maximum Extents Background monitor; a description of each field follows. Output None Exclude Rollback Segments Yes ignores the rollback segments. No does not ignore the rollback segments. Tivoli Manager for Oracle** Reference Guide 343

362 Maximum Extents Asynchronous CLI Syntax maximumextentsasync CLI Example waddmon OracleManagerAsync maximumextentsasync -c critical -R < 1 -n OracleManager Sentry -c severe -R < 3 -n OracleManager Sentry -c warning -R < 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 1 Send OracleManager Sentry notice Severe Less than 3 Send OracleManager Sentry notice Warning Less than 5 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None 344 Version 2.0

363 Output The following shows an example output from this monitor. 4. Async Monitors The segment with the least amount of free extents is reported as TRIGGER_INFO. The free extents for additional segments are listed in ascending order in the userinfo lines, in the following format: Free Extents, Segment Name, Tablespace Name, Object Owner, Segment Type For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 345

364 Maximum Extents by Tablespace Background and Asynchronous Description This monitor returns the smallest number of free extents found for a segment within the specified tablespaces. This monitor also checks how close each object within the specified tablespaces is to the value of MAXEXTENTS and reports the number of extents that can still be allocated. It does not check objects of segment_type CACHE. Use the Maximum Extents by Tablespace Background monitor to set arguments. Use the Maximum Extents by Tablespace Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. If the value of MAXEXTENTS is less than the maximum allowable (see the following table), increase the value of MAXEXTENTS. Otherwise, export the object, drop and recreate the object with larger extent sizes, and import the data. Block Size MAXEXTENTS 1KB 57 2 KB KB Version 2.0

365 Block Size MAXEXTENTS 8 KB 505 See Also The following monitors in this chapter: Maximum Extents Background and Asynchronous and Maximum Extents by User Background and Asynchronous. 4. Async Monitors The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace by Tablespace and Number of Datafiles. Tivoli Manager for Oracle** Reference Guide 347

366 Maximum Extents by Tablespace Background CLI Syntax maximumextentstbackground a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace name field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use spaces to separate names. GUI Name: Tablespace Name Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. CLI Example waddmon OracleManagerAsync maximumextentstbackground -a not in -a system -t 1 hour "ProfileName" Suggested Monitoring Schedule Once every hour. 348 Version 2.0

367 GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Maximum extents by tablespace Background monitor; a description of each field follows. 4. Async Monitors Output None Include/Exclude Includes or excludes the contents of the tablespace name field. Tablespace Name Designates the tablespace names you want to include or exclude. Use spaces to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. Tivoli Manager for Oracle** Reference Guide 349

368 Maximum Extents by Tablespace Asynchronous CLI Syntax maximumextentstasync CLI Example waddmon OracleManagerAsync maximumextentstasync -c critical -R < 1 -n OracleManager Sentry -c severe -R < 3 -n OracleManager Sentry -c warning -R < 5 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 1 Send OracleManager Sentry notice Severe Less than 3 Send OracleManager Sentry notice Warning Less than 5 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None 350 Version 2.0

369 Output The following shows an example output from this monitor. 4. Async Monitors The segment with the least amount of free extents for the specified tablespaces is reported as TRIGGER_INFO. The free extents for additional segments are listed in ascending order in the userinfo lines, in the following format: Free Extents, Segment Name, Object Owner, Segment Type For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 351

370 Maximum Extents by User Background and Asynchronous Description This monitor returns the smallest number of free extents found for a segment of a specified user. This monitor checks how close each object for a specified user is to the value of MAXEXTENTS and reports the number of extents that can still be allocated. It does not check objects of segment_type CACHE. Use the Maximum Extents by User background monitor to set arguments. Use the Maximum Extents by User Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. If the value of MAXEXTENTS is less than the maximum allowable (see the following table), increase the value of MAXEXTENTS. Otherwise, export the object, drop and recreate the object with larger extent sizes, and import the data. Block Size MAXEXTENTS 1KB 57 2 KB KB KB Version 2.0

371 See Also The following monitors in this chapter: Maximum Extents Background and Asynchronous and Maximum Extents by Tablespace Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace and Number of Datafiles. 4. Async Monitors Tivoli Manager for Oracle** Reference Guide 353

372 Maximum Extents by User background CLI Syntax maximumextentsubackground a <username> The following briefly describes the argument for this monitor. <username> Specifies the Oracle user name. GUI Name: User Name CLI Example waddmon OracleManagerAsync maximumextentsubackground -a scott -t 1 hours "ProfileName" Suggested Monitoring Schedule Once every hour. GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Maximum extents by user Background monitor; a description of each field follows. Output None User Name Specifies the Oracle user name. 354 Version 2.0

373 Maximum Extents by User Asynchronous CLI Syntax maximumextentsuasync CLI Example waddmon OracleManagerAsync maximumextentsuasync -c critical -R < 1 -n OracleManager Sentry -c severe -R < 3 -n OracleManager Sentry -c warning -R < 5 -n OracleManager Sentry -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Less than 1 Send OracleManager Sentry notice Severe Less than 3 Send OracleManager Sentry notice Warning Less than 5 Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Tivoli Manager for Oracle** Reference Guide 355

374 Output The following shows an example output from this monitor. The segment with the fewest number free extents (worst-case) for the specified user is reported as TRIGGER_INFO. The free extents for additional segments are listed in ascending order in the userinfo lines, in the following format: Free Extents, Segment Name, Tablespace Name, Segment Type For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

375 SQL Number Background and Asynchronous Description Using SQL*Plus syntax, this monitor allows you to define a SQL select statement as the basis of a monitor. Use the SQL Number Background monitor to set arguments. Use the SQL Number Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed User defined Usage Notes Do not terminate the SQL statement with a semicolon (;), forward slash (/), or backward slash (\). The select statement can return multiple columns and multiple rows. The trigger value (the value against which the monitoring criteria is evaluated) must be one of the columns in the first row returned by the statement, and must be a numeric value. 4. Async Monitors The index parameter defines which column within the first row contains the trigger value (zero-based). A SQL select statement might return no rows. By default, the monitor treats this as an error. You can override the default behavior with the a value option, in which case the monitor returns the value specified by the argument value. Tivoli Manager for Oracle** Reference Guide 357

376 The ability to define a freeform SQL select statement allows for the integration of existing performance monitoring tools (particularly those reporting monitored values to internal Oracle tables within the subscribing database). See Also The following monitor in this chapter: SQL String Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: SQL String and SQL Number. 358 Version 2.0

377 SQL Number Background CLI Syntax freeformsqlnbackground a <monitor name> a <SQL statement> a <index> a <value> 4. Async Monitors The following briefly describes the arguments for this monitor. <monitor name> Designates the name that you want to give to this monitor. GUI Name: Monitor Label <SQL statement> Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. Do not terminate the SQL statement with a semicolon (;), forward slash (/), or backward slash (\). GUI Name: SQL Statement <index> Zero based; specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. GUI Name: Index <value> Specifies the value to be returned if no rows are returned from the SQL statement. GUI Name: No Rows As CLI Example waddmon OracleManagerAsync freeformsqlnbackground -a number_of_sessions -a select count(*) from V$session Tivoli Manager for Oracle** Reference Guide 359

378 -a 0 -a 0 -t 2 hours "ProfileName" Suggested Monitoring Schedule Site specific GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the SQL number Background monitor; a description of each field follows. Output None Monitor Label Designates the name that you want to give to this monitor. SQL Statement Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. Do not terminate the SQL statement with a semicolon (;), forward slash (/), or backward slash (\). Index Zero based; specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. No Rows As Specifies the value to be returned if no rows are returned from SQL Statement. 360 Version 2.0

379 SQL Number Asynchronous CLI Syntax freeformsqlnasync CLI Example waddmon OracleManagerAsync freeformsqlnasync -c critical -R > 24 -c severe -c warning -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Output The following shows an example output from this monitor. Tivoli Manager for Oracle** Reference Guide 361

380 The user-specified arguments are reported as TRIGGER_INFO. Information in the userinfo lines appears in the following format: Trigger Value For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

381 SQL String Background and Asynchronous Description Using SQL*Plus syntax, this monitor enables you to define a SQL select statement as the basis of a monitor. Use the SQL String Background monitor to set arguments. Use the SQL String Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed User defined Usage Notes Do not terminate the SQL statement with a semicolon (;), forward slash (/), or backward slash (\). The select statement can return multiple columns and multiple rows. The trigger value (the value against which the monitoring criteria is evaluated) must be one of the columns in the first row returned by the statement, and must be a string value. 4. Async Monitors The index parameter defines which column within the first row contains the trigger value (zero-based). A SQL select statement can return no rows. By default, the monitor treats this as an error. You can override the default behavior with the a value option, in which case the monitor will return the value specified by the argument value. Tivoli Manager for Oracle** Reference Guide 363

382 The ability to define a freeform SQL select statement allows for the integration of existing performance monitoring tools (particularly those reporting monitored values to internal Oracle tables within the subscribing database). See Also The following monitors in this chapter: SQL Number Background and Asynchronous. The following monitor in the OracleDatabaseManager Monitoring Collection: SQL Number. 364 Version 2.0

383 SQL String Background CLI Syntax freeformsqlsbackground a <monitor name> a <SQL statement> a <index> a <return value> 4. Async Monitors The following briefly describes the arguments for this monitor. <monitor name> Designates the name that you want to give to this monitor. GUI Name: Monitor Label <SQL statement> Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. Do not terminate the SQL statement with a semicolon (;), forward slash (/), or backward slash (\). GUI Name: SQL Statement <index> Zero based; specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. GUI Name: Index <return value> Specifies the value to be returned if no rows are returned <SQL statement>. GUI Name: No Rows As CLI Example waddmon OracleManagerAsync freeformsqlsbackground -a SQL String Monitor -a select one from dual Tivoli Manager for Oracle** Reference Guide 365

384 -a 0 -a There were no rows returned! -t 1 hours "ProfileName" Suggested Monitoring Schedule Site specific GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the SQL String Background monitor; a description of each field follows. Output None Monitor Label Designates the name that you want to give to this monitor. SQL Statement Specifies the selection and calculation criteria, in SQL*Plus syntax, of tables and columns for monitoring. Do not terminate the SQL statement with a semicolon (;), forward slash (/), or backward slash (\). Index Zero based; specifies the column number, within the first row returned, that is to contain the trigger value for the monitor. No Rows As Specifies the value to be returned if no rows are returned <SQL statement>. 366 Version 2.0

385 SQL String Asynchronous CLI Syntax freeformsqlsasync CLI Example waddmon OracleManagerAsync freeformsqlsasync -c critical -c severe -c warning -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels There are no default actions for this monitor. Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Output The following shows an example output from this monitor. Tivoli Manager for Oracle** Reference Guide 367

386 For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

387 Temporary Extents Background and Asynchronous Description Monitors how close temporary segments are to their maximum extents limit (the ratio, as a percentage, of extents to the maximum extents limit). 4. Async Monitors A temporary segment is used whenever sorts are too large to be performed in memory; that is, the amount of space required is greater than the value of the init.ora parameter SORT_AREA_SIZE. Oracle creates a segment in the temporary tablespace of the user who performs the sort operation. Use the Temporary Extents Background monitor to set arguments. Use the Temporary Extents Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. Check the storage parameters for the temporary tablespace, and ensure that they are appropriate for your applications. Block Size MAXEXTENTS 1KB 57 2 KB 121 Tivoli Manager for Oracle** Reference Guide 369

388 Block Size MAXEXTENTS 4 KB KB 505 Over time, the temporary tablespace will become fragmented and should be dropped and recreated periodically. You can reduce the amount of fragmentation by running the command: alter tablespace [tablespacename] coalesce; You can create a dedicated temporary tablespace, in which a single temporary segment is created. This segment does not get dropped and avoids the costs associated with creating and dropping temporary segments. See Also The following monitors in this chapter:temporary Extents by Tablespace Background and Asynchronous and Temporary Extents by User Background and Asynchronous. The following monitors in the OracleDatabaseManager Monitoring Collection: Free Tablespace by Tablespace 370 Version 2.0

389 Temporary Extents Background CLI Syntax temporaryextentsbackground CLI Example waddmon OracleManagerAsync temporaryextentsbackground -t 10 minutes "ProfileName" 4. Async Monitors Suggested Monitoring Schedule Every 10 minutes. GUI Data Entry Fields None Output None Tivoli Manager for Oracle** Reference Guide 371

390 Temporary Extents Asynchronous CLI Syntax temporaryextentsasync CLI Example waddmon OracleManagerAsync temporaryextentsasync -c critical -R > 95 -n OracleManager Sentry -c severe -R > 85 -n OracleManager Sentry -c warning -R > 75 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% used Send OracleManager Sentry notice Severe Greater than 85% used Send OracleManager Sentry notice Warning Greater than 75% used Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None 372 Version 2.0

391 Output The following shows an example output from this monitor. 4. Async Monitors Segments are reported in descending order, based on the percentage of extents allocated, in the following format: % Extents Allocated, Segment Name, Segment Owner, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 373

392 Temporary Extents by Tablespace Background and Asynchronous Description For specified tablespaces, monitors how close temporary segments are to their maximum extents limit (the ratio, as a percentage, of extents to the maximum extents limit). A temporary segment is used whenever sorts are too large to be performed in memory; that is, the amount of space required is greater than the value of the init.ora parameter SORT_AREA_SIZE. Oracle creates a segment in the temporary tablespace of the user who performs the sort operation. Use the Temporary Extents by Tablespace Background monitor to set arguments. Use the Temporary Extents by Tablespace Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. Check the storage parameters for the temporary tablespace, and ensure that they are appropriate for your applications. Block Size MAXEXTENTS 1KB Version 2.0

393 Block Size MAXEXTENTS 2 KB KB KB 505 Over time, the temporary tablespace will become fragmented and should be dropped and recreated periodically. You can reduce the amount of fragmentation by running the command: 4. Async Monitors alter tablespace [tablespacename] coalesce; You can create a dedicated temporary tablespace, in which a single temporary segment is created. This segment does not get dropped and avoids the costs associated with creating and dropping temporary segments. See Also The following monitors in this chapter: Temporary Extents Background and Asynchronous and Temporary Extents by User Background and Asynchronous. The following monitor in the OracleDatabaseManager Monitoring Collection: Free Tablespace by Tablespace. Tivoli Manager for Oracle** Reference Guide 375

394 Temporary Extents by Tablespace Background CLI Syntax temporaryextentstbackground a {in not in} a <tablespaces> The following briefly describes the arguments for this monitor. {in not in} Includes or excludes the contents of the tablespace name field. GUI Name: Include/Exclude <tablespaces> Designates the tablespace names you want to include or exclude. Use space to separate names. GUI Name: Tablespace Name Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. CLI Example waddmon OracleManagerAsync temporaryextentstbackground -a not in -a users system -t 10 minutes "ProfileName" Suggested Monitoring Schedule Every 10 minutes 376 Version 2.0

395 GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Temporary extents by tablespace Background monitor; a description of each field follows. 4. Async Monitors Output None Include/Exclude Includes or excludes the contents of the tablespace name field. Tablespace Name Designates the tablespace names you want to include or exclude. Use space to separate names. Note: Keywords have been defined for several classes of PeopleSoft and SAP tables. When you enter one of the keywords as a tablespace, it calls all of the tables associated with the keyword. Using this approach may slightly reduce system performance. Refer to the appendix titled Best Practices Script in the Tivoli Manager for Oracle User s Guide. Tivoli Manager for Oracle** Reference Guide 377

396 Temporary Extents by Tablespace Asynchronous CLI Syntax temporaryextentstasync CLI Example waddmon OracleManagerAsync temporaryextentstasync -c critical -R > 95 -n OracleManager Sentry -c severe -R > 85 -n OracleManager Sentry -c warning -R > 75 -n OracleManager Sentry -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% used Send OracleManager Sentry notice Severe Greater than 85% used Send OracleManager Sentry notice Warning Greater than 75% used Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None 378 Version 2.0

397 Output The following shows an example output from this monitor. 4. Async Monitors The segment with the highest percentage of allocated extents, within the specified tablespaces, is reported as TRIGGER_INFO. The monitor may also return additional temporary segments in the userinfo lines. Segments are reported in descending order, based on the percentage of extents allocated, in the following format: % Extents Allocated, Segment Name, Segment Owner For a description of the monitor output, see Understanding Monitor Output on page 6. Tivoli Manager for Oracle** Reference Guide 379

398 Temporary Extents by User Background and Asynchronous Description For a specified user, monitors how close temporary segments are to their maximum extents limit (the ratio, as a percentage, of extents to the maximum extents limit). A temporary segment is used whenever sorts are too large to be performed in memory; that is, the amount of space required is greater than the value of the init.ora parameter SORT_AREA_SIZE. Oracle creates a segment in the temporary tablespace of the user who performs the sort operation. Use the Temporary Extents by User Background monitor to set arguments. Use the Temporary Extents by User Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed DBA_SEGMENTS Usage Notes If the number of extents for an object reaches the value of the MAXEXTENTS storage parameter, and the object needs to allocate an additional extent, the operation will fail. Check the storage parameters for the temporary tablespace, and ensure that they are appropriate for your applications. Block Size MAXEXTENTS 1KB 57 2 KB Version 2.0

399 Block Size MAXEXTENTS 4 KB KB 505 Over time, the temporary tablespace will become fragmented and should be dropped and recreated periodically. You can reduce the amount of fragmentation by running the command: 4. Async Monitors alter tablespace [tablespacename] coalesce; You can create a dedicated temporary tablespace, in which a single temporary segment is created. This segment does not get dropped and avoids the costs associated with creating and dropping temporary segments. See Also The following monitors in this chapter: Temporary Extents Background and Asynchronous and Temporary Extents by Tablespace Background and Asynchronous. The following monitor in the OracleDatabaseManager Monitoring Collection: Free Tablespace. Tivoli Manager for Oracle** Reference Guide 381

400 Temporary Extents by User Background CLI Syntax temporaryextentsubackground a <username> The following briefly describes the argument for this monitor. <username> Specifies the Oracle user name. GUI Name: User Name CLI Example waddmon OracleManagerAsync temporaryextentsubackground -a SYS -t 10 minutes "ProfileName" Suggested Monitoring Schedule Every 10 minutes GUI Data Entry Fields The following shows the GUI fields on the Add Monitor to TME 10 Distributed Monitoring Profile dialog for the Temporary extents by user Background monitor; a description of each field follows. Output None User Name Specifies the Oracle user name. 382 Version 2.0

401 Temporary Extents by User Asynchronous CLI Syntax temporaryextentsuasync CLI Example waddmon OracleManagerAsync temporaryextentsuasync -c critical -R > 95 -n OracleManager Sentry -c severe -R > 85 -n OracleManager Sentry -c warning -R > 75 -n OracleManager Sentry -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Greater than 95% used Send OracleManager Sentry notice Severe Greater than 85% used Send OracleManager Sentry notice Warning Greater than 75% used Send OracleManager Sentry notice Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Tivoli Manager for Oracle** Reference Guide 383

402 Output The following shows an example output from this monitor. The segment with the highest percentage of allocated extents for a specified user is reported as TRIGGER_INFO. The monitor may also return additional temporary segments in the userinfo lines. Segments are reported in descending order, based on the percentage of extents allocated, in the following format: % Extents Allocated, Segment Name, Tablespace Name For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

403 Unix SQL*Net V1 TCP/IP Listener Background and Asynchronous Description This monitor determines whether the UNIX SQL*Net Version 1 TCP/IP listener process (orasrv) is running. If this process is not running, the machine cannot accept SQL*Net Version 1 TCP/IP connections from any clients. This monitor returns one of the following states: Is up/available, Is down/unavailable, Becomes available, and Becomes unavailable. 4. Async Monitors Note: For more information on the availability states for this monitor, see Appendix C, Operator Groups (Monitor Triggers). Use the Unix SQL*Net V1 TCP/IP Listener Background monitor to set arguments. Use the Unix SQL*Net V1 TCP/IP Listener Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed Not applicable Usage Notes The trigger value can be set to Becomes unavailable, which will only report an error when the listener goes down. This prevents messages from appearing on an administrator s desktop each time the monitor is run and the listener is not running. The monitor checks if the listener is running and whether it has hung by running the command tcpctl stat. You can restart the listener by logging in as the Oracle owner and typing tcpctl start. This monitor will only work if it is distributed to an endpoint that has the SQL*Net V1 Tivoli Manager for Oracle** Reference Guide 385

404 software installed, because it must be able to locate the $ORACLE_HOME/bin/tcpctl program. The monitor should only be distributed once on each machine, regardless of the number of the databases on the machine. Note: This monitor is only for UNIX systems. Do not run it on Windows NT. See Also The following monitors in this chapter: Unix SQL*Net V2 Listener Background and Asynchronous. The following monitor in the OracleDatabaseManager Monitoring Collection: NT Service Status. 386 Version 2.0

405 Unix SQL*Net V1 TCP/IP Listener Background CLI Syntax netonetcpipbackground CLI Example waddmon OracleManagerAsync netonetcpipbackground -t 5 minutes "ProfileName" 4. Async Monitors Suggested Monitoring Schedule Every 5 minutes GUI Data Entry Fields None Output None Tivoli Manager for Oracle** Reference Guide 387

406 Unix SQL*Net V1 TCP/IP Listener Asynchronous CLI Syntax netonetcpipasync CLI Example waddmon OracleManagerAsync netonetcpipasync -c critical -R == down -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Is down/unavailable Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Output No output is available for this monitor. Results for this monitor appear in the TRIGGER_INFO of the output in the following format: 388 Version 2.0

407 Listener Name, TNS_Admin For a description of the monitor output, see Understanding Monitor Output on page Async Monitors Tivoli Manager for Oracle** Reference Guide 389

408 Unix SQL*Net V2 Listener Background and Asynchronous Description This monitor determines whether a UNIX SQL*Net Version 2 listener process (tnslsnr) is running. If this process is not running, the machine cannot accept SQL*Net Version 2 connections from any clients. This monitor returns one of the following states: Is up/available, Is down/unavailable, Becomes available, and Becomes unavailable. Note: For more information on the availability states for this monitor, see Appendix C, Operator Groups (Monitor Triggers). Use the Unix SQL *Net V2 Listener Background monitor to set arguments. Use the Unix SQL *Net V2 Listener Asynchronous monitor to set the trigger and response criteria. You must use these two monitors in conjunction for valid return values. Authorization Role oracle_user and user Target Endpoint OracleDatabaseManager Views Accessed Not applicable Usage Notes The trigger value can be set to Becomes unavailable, which will only report an error when the listener goes down. This prevents messages from appearing on an administrator s desktop each time the monitor is run and the listener is not running. The monitor checks if the listener is running, and whether it has hung, by running the command lsnrctl stat listener_name. You can restart the listener by logging in as the Oracle owner and typing lsnrctl start listener_name. If the TNS_ADMIN variable is 390 Version 2.0

409 set, the monitor will look in this location for the LISTENER.ORA file. If this variable is not set, the LISTENER.ORA file should be in one of the standard locations; that is, /etc or /var/opt/oracle (the same directory as the oratab file), or $ORACLE_HOME/network/admin. The monitor should only be distributed once on each machine, regardless of the number of databases on the machine. If there are multiple listeners running, this monitor must be configured separately for each listener. 4. Async Monitors Note: For NT systems, use the NT service status monitor to check whether a SQL*Net listener is running. See Also The following monitors in this chapter: Unix SQL*Net V1 TCP/IP Listener Background and Asynchronous. The following monitor in the OracleDatabaseManager Monitoring Collection: NT Service Status. Tivoli Manager for Oracle** Reference Guide 391

410 Unix SQL *Net V2 Listener Background CLI Syntax nettwolistenerbackground a <listener_name> The following briefly describes the argument for this monitor. <listener_name> Specifies the name of a SQL*Net listener. You can leave this blank if only one listener is running. GUI Name: Listener Name CLI Example waddmon OracleManagerAsync nettwolistenerbackground -a listener -t 5 minutes "ProfileName" Suggested Monitoring Schedule Every 5 minutes GUI Data Entry Fields Output None Listener Name Specifies the name of a SQL*Net listener. You can leave this blank if only one listener is running. 392 Version 2.0

411 Unix SQL *Net V2 Listener Asynchronous CLI Syntax nettwolistenerasync CLI Example waddmon OracleManagerAsync nettwolistenerasync -c critical -R == down -n OracleManager Sentry -c severe -c warning -c normal -c always "ProfileName" 4. Async Monitors Suggested Response Levels The following table shows suggested threshold values for severity levels. See Specifying Response Levels in Chapter 6 of Tivoli Manager for Oracle User s Guide. Severity Trigger When Default Actions Critical Is down/unavailable Send OracleManager Sentry notice Severe N/A None Warning N/A None Normal N/A None Always N/A None Because the listener has only two states (running or not running), only one response level is set. If the listener is not running, it is considered to be a serious problem, so you may want to choose the critical response level. If the listener is not running, the following events will occur: A notice will be sent to the OracleManager Sentry notice group. An alert will be displayed on an administrator s desktop. An message will be sent to an administrator. A program will be run to restart the listener. Tivoli Manager for Oracle** Reference Guide 393

412 Monitors that are defined with this monitoring source use operators to evaluate data. For information about these operators, see Appendix C, Operator Groups (Monitor Triggers). GUI Data Entry Fields None Output The following shows an example output from this monitor. Results for this monitor appear in the TRIGGER_INFO in the following format: Listener Name, TNS_Admin For a description of the monitor output, see Understanding Monitor Output on page Version 2.0

413 5 Tasks The OracleManagerTasks task library contains a set of predefined Oracle tasks. A task is an operation or set of operations that is performed routinely. This chapter includes the following information: Tasks listed by GUI name and CLI name Task dialogs used by all tasks A description of each task in the task library 5. Tasks Refer to the Tivoli Manager for Oracle User s Guide for information on running and customizing tasks. Refer to the Tivoli Management Framework Reference Manual for information on the wruntask command. List of Tasks by GUI and CLI Names The following table lists the tasks by their GUI and CLI names. GUI Name ConfigureTECOracle CurrentRunningSQL DisableMonitoring EnableMonitoring Listener CLI Name ConfigureTECOracle CurrentRunningSQL DisableMonitoring EnableMonitoring Listener Tivoli Manager for Oracle** Reference Guide 395

414 Common Task Dialogs Two dialogs are used by all tasks. When you press the Report to File button on a task argument dialog, the system displays the Create a Report File dialog. When you press the Notify TEC button on a task argument dialog, the system displays the TEC dialog. Using the Create a Report File Dialog Use the Create a Report File dialog to save the task output information in a file. This option offers the following advantages over the Save to File option: You can choose to send the task output to the monitored host, or you can specify a host. (This is similar to the options offered by Distributed Monitoring.) You can display a drop-down list of available hosts. You can use a default path and file name from the GUI. You will always get output. The Save to File option may time out before the task finishes, but Create a Report File does not. To display the dialog, you click Report to File in a task s task arguments dialog. 396 Version 2.0

415 The following shows the Create a Report File dialog; a description of each field follows. Report to file Tells Tivoli Manager for Oracle to save the output information for the task as a file when the box is checked. Path and file name Designates the directory path to and the file name of the output file. The output file name is the name specified in the Path and file name field. This field displays a list of variables as the default response. All variables, except WTEMP, are local to the endpoint running the task. You can use some or all of the variables, or you can enter your own specific information. The variables include: ${DATE} is the current date in YYYYMMDD format. ${TIME} is the current time in HHMMSS format. ${NODE} is the name of the managed node (host) the task was run on. Although this information is also included in ${ENDPOINT}, using a separate variable, such as ${NODE}, makes it easier to sort. ${TASK} is the task CLI name, such as DisableMonitoring. ${ENDPOINT} is the name of the endpoint the task was run on. 5. Tasks Tivoli Manager for Oracle** Reference Guide 397

416 ${WTEMP} is a temporary directory on the managed node on which to save the file. The task uses the wtemp command to identify this directory. On monitored host Creates the output file on the monitored host the task was run against. (Mutually exclusive with On specified host.) On specified host Creates the output file on a specified host, which you designate in the Host name field; you cannot save output files on multiple hosts. (Mutually exclusive with On monitored host.) Host Name Displays a list of host names so you can select the host computer on which to save the output file. Use this field with the On specified host field. Using the TEC Dialog The TEC dialog sends the task success or failure status to the Tivoli Enterprise Console event server. The following shows the TEC dialog; a description of each field follows. Send task success/failure status to TEC Sends a message to the TEC to report if the task succeeded or failed when the box is checked. Select TEC server Displays a list of available TEC servers. You can choose one of these to send the message to. 398 Version 2.0

417 ConfigureTECOracle Description Provides Tivoli Enterprise Console (TEC) configuration options. You can configure TEC to receive events from the following: Distributed monitors (OracleDatabaseManager, OracleInstanceManager, and OracleManagerAsync monitors) Tasks (OracleManagerTasks tasks) The task adds the class and rule set definitions of the selected configuration option to a valid rule base, if the class and rule set definitions are not already defined in the specified rule base. For more information, see the Tivoli Manager for Oracle User s Guide. Before you run this task, the following software must be installed: Tivoli Enterprise Console (TEC) Event Server Tivoli Manager for Oracle on the Tivoli Management Region (TMR) server of the TMR on which you want to run this task. 5. Tasks ConfigureTECOracle does the following, depending on the options you choose: Creates a rule base in the directory where TEC is installed. Provides TEC configuration for the specified options. It adds class and rule set definitions to a valid rule base for the options, if they are not already defined in the specified rule base. Copies a specified rule base into the newly created rule base. Creates event groups. Adds filters to an event group for the TEC configuration options specified. Loads the rule base. Restarts the event server. Authorization Role senior and oracle_dba (must have both roles) Tivoli Manager for Oracle** Reference Guide 399

418 Target Endpoint Managed node (where the event server is installed) GUI Data Entry Fields The following shows the ConfigureTECOracle dialog; a description of each field follows. Rule Base Name Name of the rule base to configure. This can be the new name for a rule base that you want to create or the name of an existing rule base. If you specify an existing rule base, ConfigureTECOracle checks to make sure both its class and rule set files are defined correctly. Enter only the name; a full path is ignored. A rule base consists of a set of expressions (rule set files) used by the event server to determine if an event meets the rule conditions. The rules may also define a set of actions that are taken when an event meets the specified rule conditions. Copy Rule Base Uses an existing rule base as the basis for the rule base you are setting up for this configuration option. 400 Version 2.0

419 Rule Base to Copy Name of the rule base to copy. If you leave this field blank after selecting the Copy Rule Base check box, the task uses the Default rule base. If you use a rule base other than Default, it must be a valid rule base. The Default rule base contains correctly defined default classes. Although Tivoli Manager for Oracle does not need these classes, other applications (such as adapters) can require them. Create Event Group An event group is a configured logical area of responsibility. An event group is used to notify users that an event that matches a specified set of criteria has occurred. Event groups are configured on the event server to create a single alarm indicator that represents many different, but related, events. Each event group has its own icon on the event console. Event Group Name Name of the event group that you create. If you select the Create Event Group check box and do not enter an event group name, the task creates and configures an event group called OracleEventBase. If you specify an existing event group, the task configures the event group that you named. Event Server option to configure To set up an event group, you must define the selection criteria of the events you want to monitor. This data constitutes an event group filter. You can select from the following two predefined filters to add to the Event Group Name specified elsewhere in this dialog (see Event Group Name). Configure Event Server for Distributed Monitoring enables the event server to receive all events sent from the OracleDatabaseManager, OracleInstanceManager, and OracleManagerAsync monitors. 5. Tasks Tivoli Manager for Oracle** Reference Guide 401

420 CLI Syntax Configure Event Server for Tasks enables the event server to receive all events sent from OracleManagerTasks tasks. Restart Event Server Loads the rule base and starts the event server, if it is not already running. When you create a new rule base or modify an existing one, you must restart the event server for any rule base configurations to take effect. If the event server is not running, this task starts it. If the event server is running, this task stops and restarts it. If you do not use the task to restart the event server, you must load the rule base and restart the event server manually. (See the Tivoli Enterprise Console User s Guide for information on how to do this.) For best results include the following: Report to File Displays the Create a Report File dialog so that you can save the output information for this task to a file. Notify TEC Displays the TEC dialog so that you can forward the success or failure of the task to a TEC server. ConfigureTECOracle a RuleBaseName = <rulebasename> [ a CreateEventGroup ={Y N} [ a EventGroupName = <eventgroupname>]] [ a CopyBase ={Y N} [ a CopyBaseName = <rulebasetocopy>]] {[ a ConfigureForDM ={Y N}] [ a ConfigureForTask ={Y N}]} [ a RestartServer ={Y N}] [ a NotifyTEC ={Y N} [ a TECServer = <servername>]] [ a ReportToFile ={Y N} [ a ReportFileName = <filename>] 402 Version 2.0

421 [ a SaveReportFileOn ={MonitoredHost SpecifiedHost} [ a ReportHostName = <hostname>]]] where: RuleBaseName <rulebasename> is the name to give to the rule base. GUI Name: Rule Base Name CreateEventGroup Y creates an event group and is the default. N does not create an event group. GUI Name: Create Event Group EventGroupName <eventgroupname> is the name to give to the event group that you are creating. GUI Name: Event Group Name CopyBase Y uses an existing rule base as the basis for the rule base you are setting up. N does not use the existing rule base. GUI Name: Copy Rule Base CopyBaseName <rulebasetocopy> is the name of the rule base to copy. GUI Name: Rule Base to Copy ConfigureForDM Y enables the event server to receive all events sent from the OracleDatabaseManager, OracleInstanceManager, and OracleManagerAsync monitors. N does not set this option. GUI Name: Configure Event Server for Distributed Monitoring ConfigureForTask Y enables the event server to receive all events sent from OracleManagerTasks tasks. N does not set this option. GUI Name: Configure Event Server for Tasks 5. Tasks Tivoli Manager for Oracle** Reference Guide 403

422 CLI Example RestartServer Y restarts the server. N does not restart the server. GUI Name: Restart Event Server NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If you specify Y, specify a valid TECServer argument or no message is sent. TECServer <servername> the name of the TEC server to send the message to. ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the default. If Y, specify the file with ReportFileName and, optionally, the host with SaveReportFileOn. ReportFileName <filename> is the path to and the name of the file to create as the task output. SaveReportFileOn MonitoredHost puts the output file on the host the task was run against. SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName. ReportHostName <hostname> is the name of the host on which to save the file created when you use the SpecifiedHost argument. wruntask -t ConfigureTECOracle -l "OracleManagerTasks" -a RuleBaseName=OracleBase1 -a CopyBase=Y -a CopyBaseName=Default 404 Version 2.0

423 Output -a CreateEventGroup=Y -a EventGroupName=OracleEventBase1 -a ConfigureForDM=Y -a ConfigureForTask=Y The following displays the output for this task. 5. Tasks Usage Notes You must restart the event server after defining new classes so that TEC can recognize and display instances of classes. Because each command defines new classes, you must stop and restart the event server for each instance of these defined classes. Tivoli Manager for Oracle** Reference Guide 405

424 See Also The following commands in the Tivoli Management Framework Reference Manual: wruntask, wcrttask, wcrtjob and wgettask. 406 Version 2.0

425 CurrentRunningSQL Description Shows current SQL statements for one or all users connected to an Oracle database. This task provides a means of identifying problem SQL statements or SQL statements that need to be optimized in order to improve overall database performance. Authorization Role oracle_dba, oracle_monitor, oracle_user and senior Target Endpoint TMA Endpoint GUI Data Entry Fields The following shows the CurrentRunningSQL dialog box; a description of each field follows. 5. Tasks Selection Type All shows the SQL for all connected users. ByUser shows the SQL for one user, which you specify in the User Name text box. User Name Specifies the user for whom you want to show the current SQL statement. Tivoli Manager for Oracle** Reference Guide 407

426 CLI Syntax CurrentRunningSQL a SelectionType ={All ByUser} [ a UserName = <user_name>] [ a NotifyTEC ={Y N} [ a TECServer = <servername>]] [ a ReportToFile ={Y N} [ a ReportFileName = <filename>] [ a SaveReportFileOn ={MonitoredHost SpecifiedHost} [ a ReportHostName = <hostname>]]] where: SelectionType All specifies that you want to display the current SQL statements for all users. ByUser specifies that you want to display the SQL statement for a specific user account. UserName <user_name> specifies the user for whom you want to show the current SQL statement. NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If you specify Y, specify a valid TECServer argument or no message is sent. TECServer <servername> is the name of the TEC server to send the message to. ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the default. If Y, specify the file with ReportFileName and, optionally, the host with SaveReportFileOn. 408 Version 2.0

427 ReportFileName <filename> is the path to and the name of the file to create as the task output. SaveReportFileOn MonitoredHost puts the output file on the host the task was run against. SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName. ReportHostName <hostname> is the name of the host on which to save the file created when you use the SpecifiedHost argument. CLI Example The following example shows the current running SQL for the user SYS. wruntask -t CurrentRunningSQL -l OracleManagerTasks -o 15 -a SelectionType=All -a UserName="SYS" 5. Tasks Tivoli Manager for Oracle** Reference Guide 409

428 Output The following displays the output for this task. Usage Notes Most system performance problems are caused by poorly written SQL and PL/SQL statements. This task enables the DBA to identify SQL statements that are most frequently executed during the course of an applications execution. Analysis and optimization of the SQL statement can improve application performance. See Also The following commands in the Tivoli Management Framework Reference Manual: wruntask, wcrttask, wcrtjob and wgettask. 410 Version 2.0

429 DisableMonitoring Description Disables any monitors that are running on an Oracle database or instance endpoint and optionally shuts down the database. Authorization Role oracle_dba and senior Target Endpoint TMA Endpoint GUI Data Entry Fields The following shows the DisableMonitoring dialog; a description of each field follows. 5. Tasks Shutdown Displays a list of the shutdown options that determine what happens to the database when the monitors are disabled. Abort Specifies that the database will be aborted. Immediate Specifies that the database will shut down immediately. NoShutdown Specifies that the database will not be shut down. Normal Specifies that the database will shut down normally. Tivoli Manager for Oracle** Reference Guide 411

430 CLI Syntax Transactional Allows active transactions to complete before shutting down the database. DisableMonitoring a ShutdownOption ={Abort Immediate NoShutdown Normal Transactional} [ a NotifyTEC ={Y N} [ a TECServer = <servername>]] [ a ReportToFile ={Y N} [ a ReportFileName = <filename>] [ a SaveReportFileOn ={MonitoredHost SpecifiedHost} [ a ReportHostName = <hostname>]]] where: ShutdownOption Specifies what happens to the database when the monitors are disabled. See the description in the GUI Data Entry Fields section. NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If you specify Y, specify a valid TECServer argument or no message is sent. TECServer <servername> the name of the TEC server to send the message to. ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the default. If Y, specify the file with ReportFileName and, optionally, the host with SaveReportFileOn. ReportFileName <filename> is the path to and the name of the file to create as the task output. 412 Version 2.0

431 SaveReportFileOn MonitoredHost puts the output file on the host the task was run against. SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName. ReportHostName <hostname> is the name of the host on which to save the file created when you use the SpecifiedHost argument. CLI Example The following example disables Oracle monitors running against the database v816@manzana, but does not shut down the database. wruntask -t DisableMonitoring -l OracleManagerTasks -o 15 -a ShutdownOption=NoShutdown 5. Tasks Tivoli Manager for Oracle** Reference Guide 413

432 Output The following displays the output for this task. Usage Notes This task disables any monitors that are running on the Oracle database or instance endpoint and optionally shuts down the database. This is useful if the database is taken down for maintenance purposes. If this task is not run, the user must manually disable all monitors to prevent spurious alerts from firing. In a spurious alert, monitors give errors because they are unable to connect to the database endpoint. When this task is run, the Distributed Monitoring engine is updated to disable the monitors, but distributed monitoring profiles are not updated and may still show the monitors as enabled. To selectively disable monitors, edit and distribute the relevant distributed monitoring profiles rather than running this task. 414 Version 2.0

433 See Also The following commands in the Tivoli Management Framework Reference Manual: wruntask, wcrttask, wcrtjob, and wgettask. 5. Tasks Tivoli Manager for Oracle** Reference Guide 415

434 EnableMonitoring Description Enables previously disabled monitors by directly updating the Distributed Monitoring engine at the endpoint and, optionally, starting the database. Authorization Role oracle_dba and senior Target Endpoint TMA Endpoint GUI Data Entry Fields The following shows the EnableMonitoring dialog; a description of each field follows. CLI Syntax Startup Displays the startup options that determine what will happen to the database when the monitors are enabled. If your Oracle server allows multiple instances to access a single database concurrently, specify whether to start the instance in Exclusive or Parallel mode. NoStartup does not start up the database. EnableMonitoring a StartupOption ={Exclusive Parallel NoStartup} [ a NotifyTEC ={Y N} 416 Version 2.0

435 [ a TECServer = <servername>]] [ a ReportToFile ={Y N} [ a ReportFileName = <filename>] [ a SaveReportFileOn ={MonitoredHost SpecifiedHost} [ a ReportHostName = <hostname>]]] where: StartupOption If your Oracle server allows multiple instances to access a single database concurrently, specify whether to start the instance in Exclusive or Parallel mode. NoStartup does not start up the database. NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If you specify Y, specify a valid TECServer argument or no message is sent. TECServer <servername> is the name of the TEC server to send the message to. ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the default. If Y, specify the file with ReportFileName and, optionally, the host with SaveReportFileOn. ReportFileName <filename> is the path to and the name of the file to create as the task output. SaveReportFileOn MonitoredHost puts the output file on the host the task was run against. SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName. ReportHostName <hostname> is the name of the host on which to save the file created when you use the SpecifiedHost argument. 5. Tasks Tivoli Manager for Oracle** Reference Guide 417

436 CLI Example The following example enables Oracle monitors that are running against the database but does not start the database. Output wruntask -t EnableMonitoring -l OracleManagerTasks -h -o 15 -a StartupOption=NoStartup The following displays the output for this task. Usage Notes This task enables previously disabled monitors by directly updating the Distributed Monitoring engine at the endpoint. It does not alter the monitor state in distributed monitoring profiles. The task only enables monitors that were previously disabled by the DisableMonitoring task. The task also optionally starts up the Oracle Database endpoint. 418 Version 2.0

437 See Also The following commands in the Tivoli Management Framework Reference Manual: wruntask, wcrttask, wcrtjob, and wgettask. 5. Tasks Tivoli Manager for Oracle** Reference Guide 419

438 Listener Description Starts or stops the Oracle Listener. The Oracle Listener is a process on the Oracle server that listens for connection requests from clients. Authorization Role oracle_dba and senior Target Endpoint TMA Endpoint GUI Data Entry Fields The following shows the Listener dialog; a description of each field follows. Set listener state Starts or stops the Oracle Listener. Start listener specifies that the listener process will be started. Stop listener specifies that the listener process will be stopped. Name Specifies the name of the specific listener that will be started 420 Version 2.0

439 or stopped. The default listener name,listener, is displayed automatically in the Name text box. Password Specifies the password required to stop a listener process as specified in Oracle. CLI Syntax Note: The value entered in this field must match the value assigned to the PASSWORDS_LISTENER parameter in the Administrator s listener.ora file. The listener.ora file is located in the installed Oracle directory. Listener a listener_mode ={Start Listener Stop Listener} [ a listener_name = <listener_name>] [ a listener_password = <listener_password>] 5. Tasks where: listener_mode Specifies whether to start or stop the listener function on the Oracle Server. listener_name The name of the Oracle Listener as defined by the Oracle Administrator. The default value for this parameter is listener. listener_password Specifies the password required to stop a listener process as specified in Oracle. Note: The value entered in this field must match the value assigned to the PASSWORDS_LISTENER parameter in the Administrator s listener.ora file. The listener.ora file is located in the installed Oracle directory. Tivoli Manager for Oracle** Reference Guide 421

440 CLI Example Output wruntask -t Listener -l OracleManagerTasks -h -o 15 -a listener_mode="start Listener" -a listener_name="ohioserver" -a listener_password="swordfish" The following displays example output for this task. Usage Notes The Listener utility in Oracle establishes listen endpoints on a machine. These listen endpoints are addresses that clients and servers use to connect to a database. The Listener task is used to start and stop the Listener utility in Oracle. Tivoli uses Oracle s lsnrctl utility to start and stop the Listener. 422 Version 2.0