Tivoli Manager for Microsoft SQL Server** User s Guide. Version 1.3

Transcription

1 Tivoli Manager for Microsoft SQL Server** User s Guide Version 1.3

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

3 Contents Preface...xv Who Should Read This Guide...xv Prerequisite and Related Documents...xv What This Guide Contains... xvi Using the Guide Online... xviii Getting Online Help... xix Typeface Conventions... xix Operating System Information...xx Contacting Customer Support...xx Chapter 1 Overview Introduction Product Capabilities Operations Database Server Control Backups Recovery Error Reporting Maintenance Tivoli Configuration and Control Running SQL Statements Database Server Monitoring Availability Error Logging Resource Consumption Performance Service Usage Custom Tivoli Manager for Microsoft SQL Server User s Guide iii

4 Database Monitoring Availability Resource Consumption Performance Replication PeopleSoft Security Tivoli Authorization Roles Additional Authorization Roles for This Product Microsoft SQL Server Permissions Managed Resources for Microsoft SQL Server Organizing Managed Resources User Interface Options Using the Desktop Using the CLI Using Tivoli Navigator Using GEM Chapter 2 Setup Guidelines Summary of Setup Tasks Table of Setup Tasks Restrictions for Microsoft SQL Server Temporary Tables Reserved Logins for Registration in Version Chapter 3 Installing the Software Installing Tivoli Manager for Microsoft SQL Server Backing Up the TMR Installation Order Installing from the Desktop Refreshing the Desktop Installing from the Command Line iv Version 1.3

5 winstall Syntax Installation Example for Framework Installation Example for Distributed Monitoring Installation Example for GEM Instrumentation Refreshing the Desktop Upgrading a Previous Installation Qualified Versions for Upgrade Upgrade Procedure Chapter 4 Setting Up Tivoli Manager for Microsoft SQL Server Moving the MSSQLManager Policy Region into a Subregion Subscribing to Notice Groups Adding and Removing the MSSQLServer Managed Resource Type Working from the Desktop Working from the Command Line Registering a Database Server and Discovering Its Databases Registering a Server from the Desktop Registering a Server from the Command Line Using Trusted Connections Why Use a Trusted Connection? Default Logins Version 6.5 Checklist Version 7.0 Checklist Facilities for Setting Up Trusted Connections Trusted Connections, Network Protocols, and TRAA Troubleshooting Trusted Connections Chapter 5 Setting Up the TEC Overview of the TEC Events Sources of Events Tivoli Manager for Microsoft SQL Server User s Guide v

6 Event Processing Event Grouping Viewing Events Responses to Events The TEC and Tivoli Manager for Microsoft SQL Server Monitors and the TEC Tasks and the TEC The NT Event Adapter and the TEC GEM Instrumentation and the TEC Event Classes Configuring the TEC Authorization Using ConfigureTECMSSQL from the Desktop Using ConfigureTECMSSQL from the Command Line Using TEC Commands Assumptions for This Example Configuration Checking the TEC Server Creating the Rule Base Copying an Existing Rule Base Importing Classes for Distributed Monitoring Importing Classes for Tasks Importing Classes and Rules for the NT Event Adapter Loading the Rule Base Activating the New Classes and Rules Customizing the NT Event Adapter Authorization Customizing the NT Event Adapter from the Desktop Customizing the NT Event Adapter from the Command Line Viewing Events in the TEC Assumptions for This Example Procedure for Viewing Events from the Desktop vi Version 1.3

7 Listings of Event Classes Monitors and Tasks MSSQLDatabase Monitor Event Classes MSSQLServer Monitor Event Classes NT Event Adapter Additional Slot Definitions Creating Automatic Responses to Events Running a Task as a Response Setting Up the Monitor Writing the Rule Activating the New Rule Testing the New Rule Running a Customized Task as a Response Chapter 6 Setting Up Monitoring Overview of Monitoring Organizing Monitors Defining Monitors Setup Scripts Distributing and Activating Monitors Security Viewing Monitor Information Recommended Monitors Overview of Setting up Monitoring Authorization Roles for Setting Up Monitors Creating a Profile Manager Creating a Profile Creating an Indicator Collection Associating an Indicator Collection with a Profile Adding Monitors to a Profile Defining Monitors Scheduling the Monitor Tivoli Manager for Microsoft SQL Server User s Guide vii

8 Setting Your Own Default Schedule for a Profile Setting Individual Schedules for Individual Monitors Restricting a Schedule Setting User and Group ID for a Profile Saving a Profile Subscribing Endpoints to Profile Managers Distributing a Monitoring Profile Understanding Monitor Output Determining Which Monitors have been Distributed to an Endpoint Determining Which Monitors Are Running at an Endpoint Setting Up Monitors from the Command Line Interface Chapter 7 Using Tivoli Manager for Microsoft SQL Server Opening Database Server Endpoints Viewing Database Server Properties Starting a Database Server Starting a Database Server from the Desktop Starting a Server from the Command Line Shutting Down a Database Server Shutting Down a Server from the Desktop Shutting Down a Server from the Command Line Checking a Server s State from the Desktop Investigating a SUSPECT State Changing the Registration Refreshing Databases from the Desktop Opening a Database Endpoint from the Desktop Using Other Tivoli Facilities Working with Tasks and Jobs Working with Monitors Using Indicators Using the TEC Changing Monitor Settings and Redistributing Them viii Version 1.3

9 Working with the TEC Chapter 8 Using Tasks and Jobs Introduction to Tasks and Jobs Running Tasks Running Tasks from the Desktop Using the Create a Report File Dialog Using the TEC Dialog Running Tasks from the Command Line Using wexectask Using ReportToFile from the CLI Using NotifyTEC from the CLI Getting Help on Tasks Getting Help on Tasks from the Command Line Troubleshooting Tasks Customizing Tasks from the Desktop Recreating the Task Library Creating Jobs Creating Jobs from the Desktop Creating Jobs from the Command Line Running and Scheduling Jobs Running Jobs from the Desktop Running Jobs from the Command Line Scheduling Jobs Scheduling Jobs from the Desktop Scheduling Jobs from the Command Line Chapter 9 Optimizing Microsoft SQL Server Performance Optimization Summary Optimization Questions Tivoli Manager for Microsoft SQL Server User s Guide ix

10 Chapter 10 Installing and Using GEM Instrumentation Overview of Tivoli GEM Purpose of GEM GEM Components The Topology Server The Topology Console Instrumented Components GEM and Microsoft SQL Server Microsoft SQL Server Representation on the Topology Console Running Tasks from the Topology Console Viewing Monitors on the Topology Console GEM and the Tivoli Desktop Discovering the Microsoft SQL Server Components Installing GEM Instrumentation Setting Up GEM Instrumentation Configuring Java Configuring the Java Development Kit (JDK) Configuring the Java Runtime Environment (JRE) Configuring the Topology Server Loading the AMP file Initiating Component Discovery Subscribing Managed Nodes and Distributing File Packages Subscribing Resources and Distributing Monitoring Profiles Confirming Component Discovery Configuring TEC for the Topology Server Introduction Methods Prerequisites Assumptions Used in the Examples Steps in Configuration Authorization x Version 1.3

11 Using ConfigureTECMSSQL from the Desktop Using ConfigureTECMSSQL from the Command Line Using TEC Facilities on the Tivoli Desktop Using TEC Commands Importing TEC Class Files Importing the Rule Set Compiling and Loading the Rule Base Stopping and Restarting the Event Server Using GEM Instrumentation GEM Instrumentation Monitors Supported Monitors from Tivoli Manager for Microsoft SQL Server GEM Instrumentation Tasks Navigating on the Topology Console Using the Tear-Away Log Starting a Component Task Viewing Monitor Status Deleting Components on the Topology Console Unsubscribing Monitors Deleting the Components Troubleshooting Uninstalling GEM Instrumentation Chapter 11 Working with PeopleSoft Software PeopleSoft Monitors Setup Scripts PeopleSoft Groups Base Benefits Human Resources Payroll Overlap and PeopleSoft Space Used Table Tivoli Manager for Microsoft SQL Server User s Guide xi

12 Appendix A Monitoring Collection Information Scripts for Configuring Profiles... A-2 Suggested Monitoring Profiles... A-2 NT Performance Monitors... A-2 MSSQLServer Performance Monitors... A-3 MSSQLServer Availability Monitors... A-4 MSSQLDatabase Performance and Availability Monitors... A-5 Monitor Types... A-5 Monitor Quick Reference... A-7 Database Server Monitors... A-7 Database Monitors... A-14 Appendix B Authorization Roles Quick Reference Tivoli Authorization Roles...B-2 Microsoft SQL Server Authorization Roles...B-5 Fixed Server Roles...B-5 Fixed Database Roles...B-5 Appendix C Operator Groups Numeric Operator Group...C-1 String Operator Group...C-4 Status Operator Group...C-6 Appendix D Removing and Reinstalling the Task Library Deleting a Task from the Library... D-2 Reinstalling the MSSQLManagerTasks Library... D-5 Removing the MSSQLManagerTasks Library Icon from the Desktop... D-6 Appendix E Task Quick Reference xii Version 1.3

13 Appendix F Supporting Connections to Microsoft SQL Server Components Connections to GEM Components...F-2 Connections from External Components...F-2 Relationship Initiation...F-2 Defining Relationships...F-3 Relating Components...F-3 Connection Types...F-4 Communication Information...F-4 Implementing the Relationship...F-6 MSSQLDatabase getinstancerelations( ) Method...F-7 MSSQLServer Heartbeat Event...F-8 Tivoli Manager for Microsoft SQL Server User s Guide xiii

14 xiv Version 1.3

15 Preface Preface The Tivoli Manager for Microsoft SQL Server User s Guide describes how to install and use the Tivoli Manager for Microsoft SQL Server software to manage Microsoft SQL Server resources through the Tivoli Enterprise software. You can install the software from the Tivoli desktop or from the command line. Who Should Read This Guide This book is intended for system administrators and DBAs (database administrators). It explains the concepts you should know to use Tivoli Manager for Microsoft SQL Server. It contains information about server management using this product and how Tivoli Manager for Microsoft SQL Server is integrated into the Tivoli. Readers of this guide should have a knowledge of the Windows NT operating system, Tivoli software, and Microsoft SQL Server software. You will notice that both Tivoli and TME 10 are used in our product documentation. These terms are interchangeable. We will remove references to TME 10 in future product releases. Prerequisite and Related Documents The Tivoli Manager for Microsoft SQL Server Reference Guide contains detailed information about individual monitors in the MSSQLServer and MSSQLDatabase monitoring collections and individual tasks in the MSSQLManagerTasks library. The TME 10 Framework User s Guide contains more detailed information about profiles and profile management. The TME 10 Framework Planning and Installation Guide contains more detailed information about server and hardware requirements. The TME 10 Framework Reference Guide contains additional information about command line commands, such as the winstall command. The TME 10 Distributed Monitoring User s Guide contains more information about distributed monitoring. The TME 10 Enterprise Console User s Guide contains more detailed information about using the TEC. Tivoli Manager for Microsoft SQL Server User s Guide xv

16 Preface The Software Installation Services 1.0 User s Guide contains detailed information about using SIS to install the Tivoli Manager for Microsoft SQL Server software. The Microsoft SQL Server Administrator s Companion contains information about SQL Server administration. The Tivoli Global Enterprise Manager Installation and User s Guide contains more information about Tivoli Global Enterprise Manager (GEM). For information about Transact-SQL, which is the enhanced version of SQL, see the Microsoft SQL Server Transact-SQL Reference. What This Guide Contains The Tivoli Manager for Microsoft SQL Server User s Guide contains the following sections: Chapter 1, Overview Provides an overview of Tivoli Manager for Microsoft SQL Server features, its extensions to TME 10, authorization roles, and the Microsoft SQL Server as an endpoint. Chapter 2, Setup Guidelines Provides an overview chart of the set-up tasks for Tivoli Manager for Microsoft SQL Server, which includes cross-references to additional information. Chapter 3, Installing the Software Contains software and hardware requirements, and provides installation procedures for installing the Tivoli Manager for Microsoft SQL Server software. Chapter 4, Setting Up Tivoli Manager for Microsoft SQL Server Provides procedures for subscribing to notice groups, setting the MSSQLServer managed resource, registering servers and discovering databases. xvi Version 1.3

17 Preface Chapter 5, Setting Up the TEC Provides procedures for setting up the TEC to receive events from tasks, monitors, and the NT Event Adapter; procedures for customizing the NT Event Adapter, procedures for viewing events in the event console, listings of event classes, and procedures for setting up automated actions in response to events. Chapter 6, Setting Up Monitoring Provides procedures for creating profile managers, adding a monitoring profile, associating monitors with the profile, defining monitors, and distributing monitors. Chapter 7, Using Tivoli Manager for Microsoft SQL Server Provides procedures for using the software to open a server or database endpoint, view server properties, start and shut down a server, check the server state, refresh databases, run tasks and jobs, subscribe and distribute a monitoring collection profile, determine which monitors have been distributed to an endpoint, and view events in the TEC. Chapter 8, Using Tasks and Jobs Provides procedures for running tasks, customizing the standard Tivoli Manager for Microsoft SQL Server tasks, creating jobs, running jobs, and scheduling jobs. Chapter 9, Optimizing Microsoft SQL Server Performance Describes how to use Tivoli Manager for Microsoft SQL Server to monitor key Microsoft SQL Server performance issues. Chapter 10, Installing and Using GEM Instrumentation Describes how to install and use GEM Instrumentation, which integrates Tivoli Manager for Microsoft SQL Server with Tivoli Global Enterprise Manager. Chapter 11, Working with PeopleSoft Software Identifies the PeopleSoft monitors provided with Tivoli Manager for Microsoft SQL Server and describes how to set them up and what tables they monitor. Tivoli Manager for Microsoft SQL Server User s Guide xvii

18 Preface Appendix A, Monitoring Collection Information Provides a suggested monitoring profile. It also provides a list of all monitors with their descriptions, functional group (either performance or availability), and monitor type. Appendix B, Authorization Roles Quick Reference Summarizes required authorization roles and activities and tells where to find additional information about them in this manual. Appendix C, Operator Groups Describes the operator groups that allow you to define the conditions that must occur for a monitor to send an alert. Appendix D, Removing and Reinstalling the Task Library Provides information about removing a task from the MSSQLManagerTasks library and reinstalling it from the command line. It also provides instructions for removing the library icon from your desktop. Appendix E, Task Quick Reference Provides a list of all the tasks in the MSSQLManagerTasks library and a brief description of what they do. Appendix F, Supporting Connections to Microsoft SQL Server Components Describes how GEM components connect to components in Tivoli Manager for Microsoft SQL Server. Using 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 positions the manual xviii Version 1.3

19 Preface 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 Microsoft SQL Server Reference Guide, specially formatted for the text format used in Tivoli help. Help is available online from the desktop as follows: Tasks: In the task argument dialog, click the Task Description button. Monitors: a. In a profile manager, double-click a profile to open it. b. In the TME 10 Distributed Monitoring Profile Properties window, click Add Monitor. c. In the Add Monitor dialog, select the desired collection and monitor, then click the About This Monitor button. Help for tasks is also available online from the command line: use the gettaskhelp command with the CLI name for the task. For example, the following command returns help on the Dump Database task: gettaskhelp dumpdatabase 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 Tivoli Manager for Microsoft SQL Server User s Guide xix

20 Preface Italics Bold Italics Monospace appear in bold. Names of windows, dialogs, and other controls also appear in bold. Variables and values that you must provide appear in italics. Words and phrases that are emphasized also appear in italics. New terms appear in bold italics when they are defined in the text. Code examples, output, and system messages appear in a monospace font. Operating System Information See the Release Notes for information on the operating systems that Tivoli Manager for Microsoft SQL Server runs on. Contacting Customer Support If you encounter difficulties with any Tivoli products, you can enter 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. 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. xx Version 1.3

21 1 Overview 1Overview This chapter provides an overview of software. It covers the following topics: An introduction to the product in general terms Specific product capabilities: operations that the product can carry out and SQL Server characteristics that the product can monitor. The security mechanisms used by the product, including their interaction with SQL Server security The managed resources for Microsoft SQL Server: how database servers and databases appear to administrators and how they can be organized for management in large-scale environments. The user interface options available for working with the product Tivoli Manager for Microsoft SQL Server User s Guide 1 1

22 Introduction Introduction Tivoli Manager for Microsoft SQL Server complements existing Microsoft tools for Microsoft SQL Server and adds features so you can manage a large number of database servers in a distributed environment. This product concentrates on those tasks that can be defined and deployed by generic methods. It reduces the complexity of managing large distributed database environments and frees database administrators (DBA s) to concentrate on the non-generic issues associated with each of the individual servers. This product provides the ability to manage and monitor Microsoft SQL Servers by providing extensions to TME 10 Framework, Distributed Monitoring, Enterprise Console, and Global Enterprise Manager (GEM). It includes the MSSQLManagerTasks library and the MSSQLServer and MSSQLDatabase monitoring collections. These tools enable you to manage distributed Microsoft SQL Server computing resources effectively. Using Tivoli Manager for Microsoft SQL Server, you can do the following: Register the Microsoft SQL Server with Tivoli. Automate repetitive DBA operations across all database servers or databases. Tivoli tasks work on multiple servers or databases in a single action. The tasks provided can: Ensure optimal reading of data by monitoring and correcting fragmentation. Ensure query plans are based on the correct statistics. Ensure space availability on log and data devices. Run standard maintenance commands and check for corruption. Check database and server configuration settings. Keep up-to-date recovery information. Back up databases and log files. Use the MSSQLServer and MSSQLDatabase monitoring collections for global database server and database availability 1 2 Version 1.3

23 Product Capabilities and performance monitoring facilities. The monitors can be configured to respond automatically to problems. They can run tasks to perform corrective actions. Alert administrators to performance problems or serious errors and failures. Monitors can notify administrators in a number of ways. They can also send events to the Tivoli Enterprise Console (TEC). Integrate with the ADSM (ADSTAR Distributed Storage Manager) backup tool to take advantage of features such as secure backups and backup device management. Integrate with Tivoli GEM (Global Enterprise Manager) to allow business-system views of managed servers and databases. Integrate with PeopleSoft, using specially provided monitors and scripts. Overview Product Capabilities Operations Tivoli Manager for Microsoft SQL Server provides numerous capabilities for database operations, database server exception monitoring, and database exception monitoring. They are described briefly in the following section. Tivoli Manager for Microsoft SQL Server provides tasks that can run on all or selected database servers or databases. They give administrators capabilities in the following areas: Database Server Control Backups Error Reporting Maintenance Tivoli Configuration and Control Running SQL Statements The tasks provided for each area are discussed below. Tivoli Manager for Microsoft SQL Server User s Guide 1 3

24 Product Capabilities Database Server Control Backups Recovery Start MS SQL Server Services and TME Monitors starts any or all of the Microsoft SQL Server services. It can also enables monitors on a specified endpoint. Stop MS SQL Server Services and TME Monitors pauses, stops, or shuts down any or all of the Microsoft SQL Server services and disables monitors on a specified endpoint. Dump Database performs a full database backup. Dump Transaction Log backs up, truncates, or backs up and truncates transaction logs. ADSMFullBackup performs full database backup to ADSM. ADSMIncBackup performs transaction log backup to ADSM. Recovery Preparation prepares scripts and saves essential information required for recovering a database server. Error Reporting Maintenance MS SQL Server Warnings and Indicators reports on conditions at the database server. NT Event Logging specifies which non-fatal errors and user-defined errors are logged to the Windows NT event log. Database Check-up and Tune-up validates and updates databases. It performs DBCC checks, rebuilds indexes, drops and reloads stored procedures, and updates space usage information. Disable NT Disk Performance Counters disables the physical and logical disk counters used in performance monitoring. Enable NT Disk Performance Counters enables the physical and logical disk counters used in performance monitoring. 1 4 Version 1.3

25 Product Capabilities Rebuild Fragmented Indexes rebuilds clustered and non-clustered indexes on tables. Refresh Query Optimizer Statistics refreshes the optimizer statistics for indexes. Set and Retrieve Database Options reports on or changes database configuration options. Update Space Usage Information updates the sysindexes table to ensure that sp_spaceused returns correct space usage reports. Overview Tivoli Configuration and Control ConfigureTECMSSQL configures the TEC to receive events from one or more of these sources: tasks, monitors, the NT Event Adapter, or GEM Instrumentation options. Customize TEC NT Event Adapter MSSQL enables you to specify what SQL Server events are forwarded from the NT Event Log to the TEC server. Restore TEC NT Event Adapter MSSQL restores the TEC NT Event Adapter to its state before the last customization for SQL Server. It can also remove all customization for SQL Server. Discover MS SQL Servers finds database servers that are on managed nodes and registers them on the Tivoli desktop. Refresh Databases refreshes the list of databases known to Tivoli, required when databases are added or removed on a database server. Start MS SQL Server Services and TME Monitors enables monitors on specified database servers. Stop MS SQL Server Services and TME Monitors disables monitors on specified database servers. Running SQL Statements Execute SQL runs a user-defined TSQL batch statement. Tivoli Manager for Microsoft SQL Server User s Guide 1 5

26 Product Capabilities Database Server Monitoring Availability Tivoli Manager for Microsoft SQL Server provides two monitor libraries: MSSQLServer and MSSQLDatabase. The MSSQLServer monitors can track various conditions on database servers. They provide monitoring in the following areas: Availability Error Logging Resource Consumption Performance, which encompasses CPU, cache, procedure cache, fragmentation, I/O, locks, read-ahead, and replication Service Usage Custom The monitors provided for each area are identified below. The name is usually suggestive enough to identify the resource being monitored. Where it is not, a brief additional note appears. If a category appears in bold, for example I/O, that means that it is part of the monitor names that follow. Database Status (Server) Oldest Open Transaction (Server) Service State (SQLServer, SQLServerAgent/SQLExecutive, MSDTC services) SQLServerAgent Failed Jobs (also SQLExecutive for Version 6.5) SQL Server State (availability and connection capability of database server) Error Logging These monitors work with the Applications section of the Windows NT event log. NT Application Log 1 6 Version 1.3

27 Product Capabilities NT Application Log Age NT Application Log Percent Full Resource Consumption Data Space Percent Used (Server) Log Space Percent Used (Server) Overview Performance CPU: Percent Busy, Percent Busy Doing I/O, Percent Idle Cache: Average Free Page Scan, Configured Free Buffers Percent Used, Hit Ratio, Maximum Free Page Scan, Number of Free Buffers Procedure Cache: Buffers Active, Buffers Total, Buffers Used, Cache Active, Cache Size, Cache Used I/O: Batch Average Size, Batch Maximum Size, Batch Write Rate, Disk Errors, Disk Reads, Disk Writes, Log Write Rate, Outstanding Reads, Outstanding Writes, Page Read Rate, Single Page Write Rate, Transaction Rate, Transactions Per Log Record. Also Network Read Rate and Network Write Rate. Locks: Extent Locks: Exclusive, Total, Update Intent Locks: Exclusive, Shared, Total Number of Blocked Processes Number of Deadlocks Page Locks: Exclusive, Shared, Total, Update Table Locks: Exclusive, Shared, Total Total: Locks, Locks Percent Used, Locks Remaining, Shared Locks Read-Ahead, or RA: Effectiveness, Pages Fetched into Cache Per Second, Pages Found in Cache Per Second, Physical Read Rate, Slots Used Tivoli Manager for Microsoft SQL Server User s Guide 1 7

28 Product Capabilities Service Usage Replication: Delivered Latency, Delivered Transaction Rate, Delivered Transactions, Undelivered Transactions Workstations: Client Count, Client Count Percent Used Connections: User Connections, User Connections Percent Used, User Connections Remaining Custom These monitors execute a T-SQL statement, returning a value of the type indicated. Freeform SQL Numeric Freeform SQL String Database Monitoring Availability Tivoli Manager for Microsoft SQL Server provides two monitor libraries: MSSQLServer and MSSQLDatabase. The MSSQLDatabase monitors can track various conditions on databases. They provide monitoring in the following areas: Availability Resource Consumption Performance Replication PeopleSoft The monitors provided for each area are identified below. The name is usually suggestive enough to identify the resource being monitored. Where it is not, a brief additional note appears. Database Status (Database) Oldest Open Transaction (Database) Suspect Database (unavailable and marked SUSPECT) 1 8 Version 1.3

29 Security Resource Consumption Data Space Used Database Space Percent Used (Database) Log Space Used Log Space Percent Used (Database) Space Used (Table) Overview Performance Fragmentation Optimizer Statistics Age Replication Replicated Transaction Rate Replicated Transaction Rate Replication Latency PeopleSoft PeopleSoft Space Used Table PeopleSoft Fragmentation PeopleSoft Optimizer Statistics Age Security Security is maintained through checking administrator s authorization to perform operations. Administrators are system administrators or database administrators who perform system or database management tasks in policy regions. Each administrator or group of administrators is represented by an icon on the Tivoli desktop. Authorization roles determine what each administrator or group can do. They provide a layer of security above the SQL Server permissions, which administrators need as well. Tivoli Manager for Microsoft SQL Server User s Guide 1 9

30 Security Tivoli Authorization Roles Authorization roles determine the range of actions an administrator can perform in a policy region. You assign roles to administrators so they can perform system or database management tasks. A role may be over the entire Tivoli management region (TMR) or over a specific set of resources, such as those contained in a policy region. Super, senior, admin, and user are examples of authorization roles provided in Tivoli software. This manual documents the context and authorization role required for each procedure in the following manner: Activity Context Required Role Add or remove a managed resource type for a policy region Policy region senior For a complete list of all procedures and their required authorization roles, see Appendix B, Authorization Roles Quick Reference. Additional Authorization Roles for This Product Tivoli Manager for Microsoft SQL Server adds the following authorization roles. mssqlserver_dba mssqlserver_user Allowed to perform all operations. It is required for any operation that involves changing a database server or database. Allowed read-only access to a limited set of functions. It is required for viewing database server and database properties. mssqlserver_monitor Allowed to run a distributed monitoring probe. The user and group ID of a distributed monitoring profile must be set to an administrator with this role. You must assign both Tivoli and Tivoli Manager for Microsoft SQL Server authorization roles to administrators in the policy regions you want them to administer Version 1.3

31 Managed Resources for Microsoft SQL Server Microsoft SQL Server Permissions Administrators need to have the appropriate Microsoft SQL Server permissions as well as the required Tivoli authorization roles. The additional required permissions are documented in the reference entries for each monitor and task. See Tivoli Manager for Microsoft SQL Server Reference Guide. Overview Managed Resources for Microsoft SQL Server In the Tivoli environment, an endpoint is any resource that can be managed. In Tivoli Manager for Microsoft SQL Server the endpoints are managed nodes, database servers, and databases. Each endpoint type has a name: Managed node: Managed Node Database server: MSSQLServer Database: MSSQLDatabase Icons on the desktop represent endpoints. In the following illustration, jfrackow@jfrackow is an example of a database server icon. It represents a server named jfrackow running on a host named jfrackow. When you open a server endpoint icon, its window contains one database endpoint icon for each managed database. In the following illustration, Northwind and master are shown as endpoints at the server jfrackow@jfrackow. Within Tivoli, a database name also includes the name of the server that controls it, so the full name of msdb is msdb@jfrackow@jfrackow. Tivoli Manager for Microsoft SQL Server User s Guide 1 11

32 User Interface Options Organizing Managed Resources You can subscribe server and database endpoints to profiles within profile managers in the same way as any other managed resource. Profiles group individual endpoints. They are convenient to use when you want to run tasks on many endpoints at once or distribute monitors to many endpoints at once. User Interface Options Tivoli software offers a choice of user interfaces. This manual commonly provides instructions for using the desktop and for using the CLI. Using the Desktop Using the CLI The Tivoli desktop is a graphical user interface, or GUI. It provides a simple way to work with your managed resources and monitor their condition. The Tivoli command-line interface (CLI) all to create scripts, or set tasks up to respond to distributed monitoring monitors. Using Tivoli Navigator Using GEM Tivoli Manager for Microsoft SQL Server is enabled in the Tivoli desktop Navigator. MSSQLServer and MSSQLDatabase resource types are added to the resource list. Tivoli Navigator enables you to work in the Tivoli environment without going through layers of windows. Tivoli Global Enterprise Manager (GEM) provides a GUI that represents managed resources in a business-systems view. This alternative view gives administrators a way to view not only the managed resources but their relationships with each other Version 1.3

33 2 2Setup Guidelines This chapter provides an overview chart of the set-up tasks you must perform in order to use Tivoli Manager for Microsoft SQL Server. It covers the following topics: Summary of setup tasks Table of setup tasks, including cross-references to where you can find more information Restrictions associated with Microsoft SQL Server Setup Guidelines Tivoli Manager for Microsoft SQL Server User s Guide 2 1

34 Summary of Setup Tasks Summary of Setup Tasks The tasks can be divided into the following categories: Installing Tivoli Manager for Microsoft SQL Server Setting up administrators to use the software Setting managed resource types Registering the server Setting up the TEC (Tivoli Enterprise Console) Setting up monitors Setting up customized tasks Creating jobs Installing and setting up GEM (Global Enterprise Manager) Table of Setup Tasks Task For More Information See Installing software Make sure you have the appropriate amount of disk space and memory for Tivoli Manager for Microsoft SQL Server. Install the software. Hardware Requirements in the Release Notes Installing Tivoli Manager for Microsoft SQL Server on page Version 1.3

35 Table of Setup Tasks Task For More Information See Setting up administrators Note: You must assign both Tivoli and Microsoft SQL Server authorization roles to administrators in the policy regions you want them to administer. Assign each administrator the appropriate authorization role for the procedures that the administrator performs. Assign the mssqlserver_monitor to the administrator who runs the monitoring probes. Appendix B, Authorization Roles Quick Reference, provides a list of the authorization roles required for each procedure. Use the Edit Default Policies dialog in a Distributed Monitoring profile to set the user and group ID for the profile. The TME 10 Framework User s Guide provides information on how to assign authorization roles to Tivoli administrators. Setup Guidelines Subscribe additional administrators to the appropriate notice groups. Setting managed resource types Add the Microsoft SQL Server as a managed resource type for the policy region. Set the Sentry Profile option as a managed resource for the policy region (if you have not already done so), so you can create Microsoft SQL Server distributed monitor profiles. Subscribing to Notice Groups on page 4-2. Adding and Removing the MSSQLServer Managed Resource Type on page 4-6. TME 10 Distributed Monitoring User s Guide Tivoli Manager for Microsoft SQL Server User s Guide 2 3

36 Table of Setup Tasks Task For More Information See Registering the servers Register the servers. Registering a Database Server and Discovering Its Databases on page 4-9. Setting up the TEC You can set up the TEC to do the following: (optional) Receive monitoring, task, and NT Event Adapter events. Customize the NT Event Adapter. Chapter 5, Setting Up the TEC. Setting up monitors Set up monitors and indicators. Set up the suggested monitoring profiles and run them for a period of time. Edit the monitoring profiles to remove any monitors from the suggested list that are not necessary for your environment. Chapter 6, Setting Up Monitoring, and Scripts for Configuring Profiles on page A-2. Optimization Summary on page 9-2. Setting up tasks and jobs Set up any customized tasks. Customizing Tasks from the Desktop on page Create and schedule jobs. Creating Jobs on page Install and set up GEM (Global Enterprise Manager) Install and set up GEM to provide a business-management view of servers and databases. Chapter 10, Installing and Using GEM Instrumentation. 2 4 Version 1.3

37 Restrictions for Microsoft SQL Server Restrictions for Microsoft SQL Server There are restrictions that you should be aware of before installing and working with Tivoli Manager for Microsoft SQL Server: Temporary tables Reserved logins Temporary Tables Microsoft SQL Server uses the following definitions and restrictions for temporary tables: #<table_name> Designates a private temporary table. It can only be accessed by the connection that created it. ##<table_name> Designates a global temporary table. It can be accessed by anyone on the server. It exists until the connection that created it terminates and all operations on the table by other connections have ceased. Tivoli can only access global temporary tables (##). Currently, the monitors do access global temporary tables and run successfully if they exist. Monitors referencing private temporary tables fail with E.EXEC error. Tasks do not run against temporary tables, whether they are global or private. Setup Guidelines Reserved Logins for Registration in Version 6.5 In Version 6.5, Microsoft SQL Server reserves the probe, repl_subscriber, and repl_publisher logins. If you enter any of these names as the User Name when editing registration details, the logon fails. Tivoli Manager for Microsoft SQL Server User s Guide 2 5

38 Restrictions for Microsoft SQL Server 2 6 Version 1.3

39 3 3Installing the Software This chapter provides instructions for installing Tivoli Manager for Microsoft SQL Server. It covers the following topics: Installing Tivoli Manager for Microsoft SQL Server from both the desktop and the command line Upgrading a previous version of Tivoli Manager for Microsoft SQL Server to Version 1.3 Note: Before installing or upgrading, please consult the Release Notes to review the hardware and software requirements. Installing the Software Tivoli Manager for Microsoft SQL Server User s Guide 3 1

40 Installing Tivoli Manager for Microsoft SQL Server Installing Tivoli Manager for Microsoft SQL Server You install the Tivoli Manager for Microsoft SQL Server on the TMR server and on Windows NT clients that run Microsoft SQL Server. The TMR server can be running on any supported system platform. Clients all run Windows NT. Note: Tivoli Manager for Microsoft SQL Server software also supports installation using Software Installation Services 1.0. For additional information, refer to the Software Installation Services 1.0 User s Guide. When you install the Tivoli Manager for Microsoft SQL Server software, you also install the associated task library, MSSQLManagerTasks. The task library is created in the MSSQLManager policy region. Tivoli recommends that you do not remove the task library from this policy region since it contains default policies that affect how the task library works. The installation also includes scripts to configure profiles with the recommended set of monitors. The scripts are in the $BINDIR/../generic/MSSQLScripts directory. For more information about these scripts, see NT Performance Monitors on page A-2. Note: Before installing the Tivoli Manager for Microsoft SQL Server, review the release notes for this release. They contain hardware and software requirements plus important notes about the product made after the books were sent to press. The following table provides the context and authorization role required for the installation procedure. Activity Context Required Role Install software TMR senior You can perform this procedure from either the Tivoli desktop or the command line. 3 2 Version 1.3

41 Backing Up the TMR Installation Order Installing Tivoli Manager for Microsoft SQL Server Important: Before installing Tivoli Manager for Microsoft SQL Server, back up your TMR server. If there is a system failure or other problem during installation, the backup can be used to restore your Tivoli environment. Never install a new product without first backing up the TMR. You need to perform separate installations for each product that you install, and you must perform them in the following order. 1. Tivoli Manager for Microsoft SQL Server- Framework, Version Tivoli Manager for Microsoft SQL Server- Distributed Monitoring, Version (optional) Tivoli Manager for Microsoft SQL Server- GEM Instrumentation, Version 1.3 Installing the Software Tivoli Manager for Microsoft SQL Server User s Guide 3 3

42 Installing Tivoli Manager for Microsoft SQL Server Installing from the Desktop Use the following steps to install the software from the Tivoli desktop. 1. From the Desktop menu, choose Install -> Install Product. An error message appears if the media path is not set up correctly. You can then set the media path. 3 4 Version 1.3

43 Installing Tivoli Manager for Microsoft SQL Server 2. Do one of the following: If you did not receive the error message, go to step 4. OR If you received an error message, click OK. The Set Path to Tivoli Install Media dialog appears. 3. Use the File Browser dialog to specify the path to the installation media. Do one of the following, then click Set Media & Close when you have specified the correct directory: Type the full path: type the path in in the Path Name field, then click Set Path. Browse for the directory: click the desired host in the Hosts list, then click a directory in the Directories list to open it. Note: In either case, when you open the correct directory, a list of files appears in the Files list similar to the list in the example above. Installing the Software Tivoli Manager for Microsoft SQL Server User s Guide 3 5

44 Installing Tivoli Manager for Microsoft SQL Server The Install Product dialog appears. Three products should appear under Select Product to Install. If no products appear, go back to the previous step to select the installation media 4. In the Select Product to Install list, choose one product. The products must be installed individually. If you install more than one, they must be installed in the following order: Tivoli Manager for Microsoft SQL Server- Framework, Version 1.3 Tivoli Manager for Microsoft SQL Server- Distributed Monitoring, Version 1.3 (optional) Tivoli Manager for Microsoft SQL Server- GEM Instrumentation, Version Version 1.3

45 Installing Tivoli Manager for Microsoft SQL Server 5. Select the clients on which to install the product. a. Select one or more clients in the Available Clients list. b. Click the left arrow button to move the selection to the Clients to Install On list. The Framework and Distributed Monitor components must be installed on the TMR server and on any client where you want to manage Microsoft SQL Server. The GEM Instrumentation component must be installed only on the TMR server. 6. Click Install to install the product. If you click Install, the Install Product dialog stays open. You can then install the same product on other clients or install another product. If you click Install & Close, the Install Product dialog is closed. Installing the Software Tivoli Manager for Microsoft SQL Server User s Guide 3 7

46 Installing Tivoli Manager for Microsoft SQL Server During installation, a Product Install dialog appears. The dialog tells you the actions that are carried out during installation. It also warns if it encounters problems. You may need correct the problems before you continue. 7. Click Continue Install to start the installation. Note: Installation takes several minutes. 3 8 Version 1.3

47 Installing Tivoli Manager for Microsoft SQL Server When the installation is complete, the Product Install dialog shows a completion message similar to the following one. 8. Click Close to close the Product Install dialog. Refreshing the Desktop After the product is installed, you must refresh the top policy region to allow the new MSSQLManager icon to be displayed. You normally set new permissions when you install a new product. You have to stop and restart the desktop to make the new permissions take effect. Stopping and restarting the desktop refreshes the desktop. Installing the Software Tivoli Manager for Microsoft SQL Server User s Guide 3 9

48 Installing Tivoli Manager for Microsoft SQL Server Installing from the Command Line You can use the winstall command to install the Tivoli Manager for Microsoft SQL Server from the command line. For more information about this command, see the TME 10 Framework Reference Manual. winstall Syntax This is the syntax for the winstall command. winstall [-y] -c <dir> -s <managed node> -i MSSQL MSSENTRY MSINST [-n] [<managed_node...>] The following list describes each argument for the winstall command. y Installation continues without prompting or confirmation. -c <dir> Complete path to the installation files (images) for this product. -s <managed node> Managed node in the Tivoli region that has the directory that you specified with <dir>. -i MSSQL MSSENTRY MSINST Specifies the product that you want to install: MSSQL.IND for the Framework component, MSSENTRY.IND for the Distributed Monitoring component, or MSSINST.IND for the GEM Instrumentation component. A product installation index file ends with the extension.ind, but you do not need to specify the.ind extension Version 1.3

49 Installing Tivoli Manager for Microsoft SQL Server n Installs the product on all managed nodes that do not currently have the product installed. This argument is ignored if you enter a value for <managed_node>. <managed_node > Specifies the managed node on which you want to install the product. You can specify multiple managed nodes. If you do not specify a managed node, Tivoli installs the product on all managed nodes in the TMR. Installation Example for Framework The following command installs the Tivoli Manager for Microsoft SQL Server-Framework, Version 1.3 software on the managed node donald. The installation does not prompt for confirmation. The installation files are in the directory called /mssql1.3/install on solaris251. The product is MSSQL. winstall -y -c /mssql1.3/install -s solaris251 -i MSSQL donald Installation Example for Distributed Monitoring The following command installs Tivoli Manager for Microsoft SQL Server-Distributed Monitoring, Version 1.3 on the managed node donald. The installation does not prompt for any confirmation. The install files are in the directory /mssql1.3/install on solaris251. The product installation index file is MSSENTRY. winstall -y -c /mssql1.3/install -s solaris251 -i MSSENTRY donald Installation Example for GEM Instrumentation The following command installs Tivoli Manager for Microsoft SQL Server-GEM Instrumentation, Version 1.3 on the managed node donald. The installation does not prompt for any confirmation. The install files are in the directory /mssql1.3/install on solaris251. The product installation index file is MSINST. Installing the Software winstall -y -c /mssql1.3/install -s solaris251 -i MSINST donald Tivoli Manager for Microsoft SQL Server User s Guide 3 11

50 Upgrading a Previous Installation Refreshing the Desktop After the product is installed, you must refresh the top policy region to allow the new MSSQLManager icon to be displayed. You normally set new permissions when you install a new product. You have to stop and restart the desktop to make the new permissions take effect. Stopping and restarting the desktop refreshes the desktop. Upgrading a Previous Installation If you already have a previous version of Tivoli Manager for Microsoft SQL Server installed, you may elect to upgrade the product rather than reinstall it. Upgrading preserves all of your monitor settings, task settings, and job settings. Qualified Versions for Upgrade You can upgrade to Version 1.3 from Version 1.2 only. Upgrading directly from Version 1.0 is not supported. If you have Version 1.0 and do not want to perform a fresh install of Version 1.3, then do the following: 1. Upgrade from Version 1.0 to Version Upgrade from Version 1.2 to Version 1.3. Upgrade Procedure To install an upgrade for a previous version of Tivoli Manager for Microsoft SQL Server, perform the following procedure from the Tivoli desktop: 1. Backup the Tivoli database, so you can restore it from a previous version, if you encounter a problem during installation. Do one of the following: Choose Backup from the Desktop menu on the Tivoli desktop. OR Use the wbkupdb command. See the TME 10 Framework Reference Manual for more information on the wbkupdb command, which also has a restore option Version 1.3

51 Upgrading a Previous Installation 2. Unsubscribe any distributed monitoring profiles that contain Microsoft SQL Server monitors, servers, or databases. To unsubscribe the databases from the profile managers, do the following: Note: If you do not unsubscribe, the Sentry engine fails, because it still tries to run old monitors. a. Display the Profile Manager dialog. b. Choose the Edit >Subscribers >Unsubscribe menu option to display the Unsubscribe Subscriber dialog. c. Select the Delete all profile copies option. d. Click Unsubscribe. 3. Back up all top level Sentry profiles that contain Tivoli Manager for Microsoft SQL Server monitors by typing the following from a command line prompt: wlsmon -sa profilename > outputfilename.sh Note: If you experience a failure after running the MSSentryMonitors1.3.sh script, delete all monitors from the affected profiles, restore the object database, and recreate the profiles by running the scripts from the wlsmon command. 4. From the Desktop menu, use Install >Install patch to install each of the following upgrades on the TMR server and on each managed node on which a qualifying previous version was installed. Tivoli Manager for Microsoft SQL Server - Framework, Upgrade to Version 1.3 Tivoli Manager for Microsoft SQL Server - Distributed Monitoring, Upgrade to Version 1.3 Note: Immediately after the upgrade, you cannot edit distributed monitoring profiles that contain Tivoli Manager for Microsoft SQL Server monitors because of internal name and argument changes. Installing the Software Tivoli Manager for Microsoft SQL Server User s Guide 3 13

52 Upgrading a Previous Installation 3 14 Version 1.3

53 4 4Setting Up Tivoli Manager for Microsoft SQL Server Setting Up Tivoli Manager for Microsoft SQL Server This chapter provides the general setup procedures for Tivoli Manager for Microsoft SQL Server. Before you begin, you must install the Tivoli Manager for Microsoft SQL Server software. Note: Refer to the chart in Chapter 2, Setup Guidelines, for an overview of all the setup tasks. This chapter covers the following topics: Moving the MSSQLManager policy region into a subregion Subscribing to notice groups Adding the MSSQLServer managed resource type Registering servers and discovering databases, including a discussion of trusted connections and why they are recommended Tivoli Manager for Microsoft SQL Server User s Guide 4 1

54 Moving the MSSQLManager Policy Region into a Subregion Moving the MSSQLManager Policy Region into a Subregion If you want to move the MSSQLManager policy region into a subregion, do the following: 1. Use the wmv command at the command For moves the MSSQLManager policy region to the EnterpriseDatabases policy region and deletes it from the root desktop. 2. Check the destination policy region to be sure that the MSSQLManager policy region and its contents were correctly moved. Open the MSSQLManagerTasksLibrary in the destination policy region. Subscribing to Notice Groups When you install the Tivoli Manager for Microsoft SQL Server software, it creates several notice groups. The software automatically subscribes the Root Administrator to the Microsoft SQL Server Management and Microsoft SQL Server Sentry notice groups during installation. You must subscribe any other administrators to the appropriate notice groups, which include the following: The Microsoft SQL Server Management notice group records database server management activity and contains messages generated by Microsoft SQL Server administrator activity. The notices include registering and removing endpoints and stopping and starting the database server. The Microsoft SQL Server Sentry notice group contains messages that are generated when a threshold is reached by a Tivoli Manager for Microsoft SQL Server Distributed Monitoring probe. 4 2 Version 1.3

55 Subscribing to Notice Groups The SentryStatus notice group contains diagnostic messages if a monitor fails to run. (This notice group is not part of the Tivoli Manager for Microsoft SQL Server installation. It is created as part of the TME 10 Distributed Monitoring installation.) The following table provides the context and authorization role required for this procedure: Activity Context Required Role Change a Tivoli administrator properties Administrators collection senior Setting Up Tivoli Manager for Microsoft SQL Server You can perform this procedure only from the Tivoli desktop. For additional information about notice group subscriptions, see the TME 10 Framework User s Guide. Use the following steps to subscribe to notice groups: 1. Open the Administrators collection. 2. Right-click the administrator you want to subscribe, then choose Edit Notice Group Subscriptions. Tivoli Manager for Microsoft SQL Server User s Guide 4 3

56 Subscribing to Notice Groups The Set Notice Groups dialog appears. The Current Notice Groups list displays the notice groups to which the administrator is currently subscribed. The Available Notice Groups list displays the notice groups to which the administrator can subscribe. 3. In the Available Notice Groups list, select one or more notice groups. 4 4 Version 1.3

57 Subscribing to Notice Groups 4. Click the left arrow button to move your selections to the Current Notice Groups list. Setting Up Tivoli Manager for Microsoft SQL Server Note: You also can move notice groups from one list to the other by double-clicking on them. 5. Click Change & Close to save the changes and return to the Administrators window. Tivoli Manager for Microsoft SQL Server User s Guide 4 5

58 Adding and Removing the MSSQLServer Managed Resource Type Adding and Removing the MSSQLServer Managed Resource Type Each policy region maintains a list of managed resource types that are valid or defined for that specific policy region. A managed resource is any hardware or software entity represented by a database object and an icon on the TME 10 desktop. MSSQLServer is a type of managed resource. You can add or remove managed resource types at any time. To register and manage a server within a policy region, you must set MSSQLServer as a current resource in the policy region. The software then does the following: Assigns a default policy to the managed resource when you first add it to a policy region Adds the managed resource type to the policy region s Create menu so that you can create new instances of the managed resource in the policy region The following table provides the context and authorization role required for adding the MSSQLServer managed resource type: Activity Context Required Role Add or remove a managed resource for a policy region Policy region senior You can perform this procedure from either the Tivoli desktop or the command line. 4 6 Version 1.3

59 Adding and Removing the MSSQLServer Managed Resource Type Working from the Desktop Use the following steps to add or remove the MSSQLServer managed resource type: 1. From the Tivoli desktop, double-click the policy region that contains the Tivoli Manager for Microsoft SQL Server resource. The Policy Region window appears. 2. Choose Properties >Managed Resources. Setting Up Tivoli Manager for Microsoft SQL Server The Set Managed Resources dialog appears. The Current Resources list displays the policy region s current managed resources. Tivoli Manager for Microsoft SQL Server User s Guide 4 7

60 Adding and Removing the MSSQLServer Managed Resource Type The Available Resources list displays the managed resources that you can add to the policy region. 3. In the Available Resources list, select MSSQLServer. 4. Click the left arrow button to move the selection to the Current Resources list. Note: You also can move managed resources from one list to the other by double-clicking on them. 5. Click Set & Close to save changes and return to the policy region window. Working from the Command Line Use the wgetpr and wsetpr commands to examine and change the managed resources of a policy region. For more information on these commands, see the TME 10 Framework Reference Manual. 4 8 Version 1.3

61 Registering a Database Server and Discovering Its Databases Registering a Database Server and Discovering Its Databases To access a database server from the Tivoli desktop, you must register it. Registering the server creates it as an object in the Tivoli environment. The database server you want to register must be installed on a host that is a managed node in the TMR. After you register the server, it appears as an endpoint in the policy region. When you register the database server, Tivoli Manager for Microsoft SQL Server can automatically discover the server s databases. When you register a server in a connected TMR environment, register it in a policy region on the same TMR as the host (managed node) for the server. After you register the database server, you can then subscribe the database server endpoint and database endpoints to profiles in profile managers in the same way as any other managed resource. The following table provides the context and authorization role required for registering servers and discovering databases: Setting Up Tivoli Manager for Microsoft SQL Server Activity Context Required Role Register a database server Policy region mssqlserver_dba and senior at TMR You can perform this procedure from either the Tivoli desktop or the command line. You also can register servers using the Tivoli Manager for Microsoft SQL Server Discover MS SQL Servers task. For more information on this task, see Chapter 2, The MSSQLManagerTasks Library, in the Tivoli Manager for Microsoft SQL Server Reference Guide. Tivoli recommends using the Discover MS SQL Servers task when you want to register more than one database server at a time. Tivoli Manager for Microsoft SQL Server User s Guide 4 9

62 Registering a Database Server and Discovering Its Databases Registering a Server from the Desktop Use the following steps to register a server from the desktop: 1. From the Tivoli desktop, double-click the policy region that contains the Tivoli Manager for Microsoft SQL Server resource. The Policy Region window appears. 2. Choose Create > MSSQLServer. The Register SQLServer dialog appears. 3. Fill in information as follows: SQLServer: enter the name of the database server. Leave the field blank to default to the host name (recommended) Version 1.3

63 Registering a Database Server and Discovering Its Databases If the name of the database server is not the same as the host name because you have set up an alias, enter the alias here. However, Tivoli Systems strongly recommends using the host name, because aliases may change. Note: Do not use data source names (DSN) for ODBC in this field. SQLServer Login: leave blank to use a trusted connection (recommended), or enter a valid database server login. For information on trusted connections, see Using Trusted Connections on page Password: If you entered a login name, enter the password in the field; otherwise, leave this field blank. Host Name: enter the name of the host computer. The host must be a managed node in the TMR and have Tivoli Manager for Microsoft SQL Server installed on it. Ignore Server Status: if the database server is not running, you must check this box. Note: If you use this option, use the Refresh Databases task later, when the server is running. Otherwise the databases are not available to be managed. See Refreshing Databases from the Desktop on page Setting Up Tivoli Manager for Microsoft SQL Server Tivoli Manager for Microsoft SQL Server User s Guide 4 11

64 Registering a Database Server and Discovering Its Databases 4. Click Register & Close. Tivoli Manager for Microsoft SQL Server checks that the database server exists and is accessible. It then registers the database server and updates its collection of objects, which includes databases. Upon successful registration, the database server icon appears in the policy region window. Registering a Server from the Command Line The mregsvr command registers the database server from the command line. You must enter values for the <hostname> and <policy-region> arguments. You can enter empty quotes for the <server_name>, <user_name>, <user_password>, and <ignore_state_flag> arguments. The following briefly describes the arguments for the mregsvr command. For additional information about each option, refer to the descriptions of the corresponding GUI data entry fields, as described in Registering a Server from the Desktop on page mregsvr <hostname> <policy_region> <server_name> "" <user_name> "" <user_password> "" <ignore_state_flag> where arguments are as follows: 4 12 Version 1.3

65 Registering a Database Server and Discovering Its Databases <hostname> Specifies the name of the host computer. The host must be a managed node in the TMR and have Tivoli Manager for Microsoft SQL Server installed. GUI Name: Host Name <policy-region> Designates the name of the region in which you want to register the database server icon. GUI Name: Policy Region (on the DiscoverSQLSRVR dialog in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Microsoft SQL Server Reference Guide.) <server_name> "" Specifies the name of the database server. The name defaults to the name of the Windows NT computer on which you installed database server when you specify "". GUI Name: SQLServer <user_name> "" Specifies the login name that has access to the database server and its databases. It is recommended that you use "" for this value, so Tivoli Manager for Microsoft SQL Server can log on as a trusted connection. GUI Name: SQLServer Login <user_password> "" Specifies the password for the login name specified by <user_name>. The password must match the login name. If you entered "" for <user_name>, enter "" for this option, too. GUI Name: Password Setting Up Tivoli Manager for Microsoft SQL Server Tivoli Manager for Microsoft SQL Server User s Guide 4 13

66 Registering a Database Server and Discovering Its Databases <ignore_state_flag> True registers a server regardless of its state. False registers a server only if a connection can be made to it. GUI Name: Ignore Server Status The following example shows how to use the mregsvr command. mregsvr mmoore MSSQLServers "" "" "" True In the previous example: mmoore is the <hostname>. MSSQLServers is the <policy-region>. The first set of double quotes ("") leaves <server_name> blank, so it defaults to mmoore. The second and third set of double quotes ("") leaves <user_name> and <user_password> blank, so Tivoli Manager for Microsoft SQL Server can log on as a trusted connection. True specifies the value for <ignore state flag>; therefore the database server is registered regardless of its state. Using Trusted Connections If you leave the SQLServer Login field blank when you register the database server, Tivoli Manager for Microsoft SQL Server uses a trusted connection to log on to the database server. A trusted connection is preferable to an explicit System Administrator login and password or any other login. Why Use a Trusted Connection? If you do not use a trusted connection, you must take care to update Tivoli software logins any time you change the name or password of database server logins. The overhead and complexity of synchronizing Tivoli logins and Microsoft SQL Server increases rapidly with the number of database servers that you manage. If a Tivoli login is not updated after a change to a database server login, 4 14 Version 1.3

67 Registering a Database Server and Discovering Its Databases Tivoli is not able to manage that datanbase server or its databases at all. Default Logins The default logins used by Tivoli Manager for Microsoft SQL Server are: Microsoft SQL Server Version 6.5: SA Microsoft SQL Server Version 7.0: BUILTIN\Administrator You must set up the Windows NT login that Tivoli uses to connect to the Tivoli Manager for Microsoft SQL Server as a valid trusted connection. Setting Up Tivoli Manager for Microsoft SQL Server Version 6.5 Checklist Use the following checklist to set up trusted connections in Microsoft SQL Server Version 6.5: 1. Under the Change Network Support option in the Microsoft SQL Server setup program, check Named Pipes or Multi-Protocol Note: If you choose Named Pipes, be sure you understand the information in Trusted Connections, Network Protocols, and TRAA, below. 2. In the Client Configuration Utility, on the Net Library tab, set the Default Network to Named Pipes or Multi-Protocol. 3. Make sure the login used to access the database server is set up as a valid trusted connection. Version 7.0 Checklist Use the following checklist to set up trusted connections in Microsoft SQL Server Version 7.0: Tivoli Manager for Microsoft SQL Server User s Guide 4 15

68 Registering a Database Server and Discovering Its Databases 1. Under the Change Network Support option in the SQL Server Network Utility, check TCP/IP Sockets, Named Pipes or Multi-Protocol. Note: If you choose Named Pipes, be sure you understand the information in Trusted Connections, Network Protocols, and TRAA, below. 2. In the Client Configuration Utility, on the Net Library tab, set the Default Network to TCP/IP Sockets, Named Pipes or Multi-Protocol. 3. Make sure the login used to access the database server is set up as a valid trusted connection. Facilities for Setting Up Trusted Connections Set up trusted connections through the Microsoft Security Manager (Version 6.5 only), the Microsoft Enterprise Manager (Version 7.0), or with the following extended stored procedures: xp_logininfo xp_grantlogin xp_revokelogin xp_enumgroups xp_loginconfig Trusted Connections, Network Protocols, and TRAA The network protocol you choose affects the way Tivoli logs on to the database server over a remote connection. Protocol TCP/IP Sockets Multi-Protocol Named Pipes Login BUILTIN\Administrators BUILTIN\Administrator TRAA 4 16 Version 1.3

69 Registering a Database Server and Discovering Its Databases Windows NT does not allow trusted connections over named pipes from remote machines. Therefore, the Tivoli Remote Access Account (TRAA) is used to log on. Note: The definition of remote in this case refers to the relationship of the machine where an endpoint is located and the machine where the TMR server is running. Note that using named pipes can work without TRAA if the database server and the Tivoli TMR server are running on the same host. This is not a normal (or recommended) configuration, but it is sometimes found in prototype environments. If you use named pipes as the default network protocol, you need to do the following to allow Tivoli Manager for Microsoft SQL Server to work throughout the network: Set up the TRAA. Use the wsettap command to check or change the Windows NT login for the TRAA. Set up the database server to allow the TRAA access over a trusted connection. Setting Up Tivoli Manager for Microsoft SQL Server Troubleshooting Trusted Connections The following questions are intended to help you troubleshoot when trusted connections between Tivoli and the database server do not appear to be working. Why are trusted connections working for other applications but not Tivoli? If trusted connections are working for other applications (such as ISQL) but are not for working for Tivoli, it is possible that the TRAA (Tivoli Remote Access Account) has not been configured correctly as a trusted connection. To check or change the Windows NT login set up for the TRAA account, use the wsettap command. What account is Tivoli using for trusted connections? To determine which Windows NT account Tivoli uses for trusted connections, run the SQL Trace utility and try to register the database server using a trusted connection. The Windows NT login is displayed at User= value. Tivoli Manager for Microsoft SQL Server User s Guide 4 17

70 Registering a Database Server and Discovering Its Databases 4 18 Version 1.3

71 5 5Setting Up the TEC This chapter provides information about setting up the Tivoli Enterprise Console (TEC) for use with Tivoli Manager for Microsoft SQL Server. You can skip this chapter if you do not have the TEC or do not want to have Tivoli Manager for Microsoft SQL Server send events to it. This chapter covers the following topics: An overview of the Tivoli Enterprise Console (TEC) An overview of how Tivoli Manager for Microsoft SQL Server works with the TEC Procedures for setting up the TEC to receive monitoring, task, and NT Event Adapter events Procedures for setting up the TEC NT Event Adapter Procedures for viewing events in the TEC console Listings of event classes and events Procedures for setting up automated task execution in response to events Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 1

72 Overview of the TEC Overview of the TEC In distributed computing environments, it is essential to address events and conditions that can lead to problems in a timely and efficient manner. The TEC provides the tools for: Receiving events from various sources Processing events using rules Grouping events and delegating the groups selectively to administrators Responding to events automatically Viewing events at a console Events An event is a structured piece of information. It carries information about itself, including the event class, event identity, severity, location (host where the event originated) and description. Sources of Events The TEC accepts events from many sources. Typically, Tivoli is set up so that events are sent in response to changes in an application or system resource. For example, distributed monitors can be configured to send events as well as report in other ways. Tivoli tasks can send events. TEC can also accept events from event adapters, small applications that monitor logfiles (or other sources of information), format specific messages into events, and send them to the TEC. The NT Event Adapter works with the Windows NT event log. Event Processing The TEC uses rules to process events. A rule is made up of a set of logic statements. The rule makes decisions on what to do with the event based on information provided in the event, such as the event class, event name, severity, location, and description. A rule s logic provides one or more responses to the event: it can drop insignificant events, escalate important events, create new events, or 5 2 Version 1.3

73 Overview of the TEC respond to defined relationships of multiple events (event correlation). It can also close an old event when a new event indicates that the original condition has been resolved. Event Grouping Viewing Events The TEC can filter events into event groups. These event groups are typically organized by function but can also be configured by other criteria, such as location or organizational jurisdiction. Event groups are especially useful for subdividing all TEC events into manageable chunks. Administrators can be assigned to one or more event groups. The TEC includes a console where administrators can watch for incoming events and respond to them. The TEC console is a useful tool for managing by exception. The TEC can filter out normal events, respond automatically to anticipated problems, and forward only those events that require human intervention. Setting Up the TEC Responses to Events The TEC normally can provide automatic responses to many common events, either by executing response programs or executing Tivoli tasks. For example, you can set a response to respond to the event received when a database server becomes unavailable. The specific response can be to inform an administrator or to attempt automatic restarts of the server, or a combination of both. The automatic response mechanism does not work with Tivoli Manager for Microsoft SQL Server. However, you can write TEC rules that accomplish the same thing. Specific instructions for doing so are included in this chapter. See Creating Automatic Responses to Events. For more information about the TEC, refer to the TME 10 Enterprise Console User s Guide. Tivoli Manager for Microsoft SQL Server User s Guide 5 3

74 The TEC and Tivoli Manager for Microsoft SQL Server The TEC and Tivoli Manager for Microsoft SQL Server When you configure the TEC for use with Tivoli Manager for Microsoft SQL Server, you can have it work with one or more of the following types of events: Events from monitors Events from tasks Events from the NT Event Adapter Events from GEM Instrumentation (if it is installed) Monitors and the TEC All monitors provided by Tivoli Manager for Microsoft SQL Server provide the option to send events to the TEC. For example, the Database Percent Used monitor can be configured such that when a database crosses from Normal (<70% full) to Warning (>70% full), an event is sent to the TEC. In order to use this option, you must first configure the TEC to accept events from Tivoli Manager for Microsoft SQL Server monitors. Tasks and the TEC All tasks provided by Tivoli Manager for Microsoft SQL Server provide the option to send events to the TEC in response to task success or task failure. In order to use this option, you must first configure the TEC to accept events from tasks. The NT Event Adapter and the TEC Tivoli Manager for Microsoft SQL Server builds on the functionality of the NT Event Adapter by providing the ability to receive Microsoft SQL Server entries in the Windows NT event log as events. The NT Event Adapter is a WIN32 process that reads events generated by the Windows NT system, formats them according to 5 4 Version 1.3

75 The TEC and Tivoli Manager for Microsoft SQL Server specifications in the tecad_nt.fmt file, and forwards them using Winsock TCP/IP to the TEC event server for further processing. GEM Instrumentation and the TEC Event Classes The GEM Instrumentation component provided with Tivoli Manager for Microsoft SQL Server provides the option to send events to the TEC. In order to use this option, you must first configure the TEC to accept events from GEM Instrumentation. Configuring the TEC for GEM Instrumentation is described in Chapter 10, Installing and Using GEM Instrumentation. The event classes for these Microsoft SQL Server log events are derived from the NT_Base class that the NT Event Adapter uses. The event classes are extended to include types of events that are specific to Microsoft SQL Server and to provide more information. You must do the following in order to have the TEC receive events from the extended NT Event Adapter: Configure the TEC to allow it to receive events from the NT Event Adapter. Customize the NT Event Adapter with the CustomizeTECNTEventAdapterMSSQL task. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 5

76 Configuring the TEC Configuring the TEC You may configure the TEC in any of the following ways: Use the ConfigureTECMSSQL task from the Tivoli Desktop Use the ConfigureTECMSSQL task from the command line Use TEC commands at the command line Using the ConfigureTECMSSQL task is recommended. It performs all TEC configuration in a single step. It provides options for configuring the TEC to accept events from monitors, tasks, the NT Event Adapter, and (if it is installed), the GEM Instrumentation. The task does all of the following: Creates the specified rule base, if it does not already exist. Copies an existing rule base into a newly created rule base, if you select the option to do so. Configures the rule base for the selected option(s) by importing the appropriate class and rule set files. Compiles the rule base. Creates an event group, if you select the option to do so and the specified event group does not already exist. Configures the event group for the selected option(s) by defining the appropriate filters. For a detailed description of these class definitions, see Listings of Event Classes on page Restarts the event server, if you select the option to do so. Refer to the Tivoli Manager for Microsoft SQL Server Reference Guide for additional information about the ConfigureTECMSSQL task. 5 6 Version 1.3

77 Authorization Configuring the TEC The following table provides the context and authorization roles required for configuring the TEC. Activity Context Required Role Configure the TEC Managed Node (where the event server is installed) super, senior, admin, user, mssqlserver_dba (must have all roles) Using ConfigureTECMSSQL from the Desktop Use the following steps to configure the TEC by running the ConfigureTECMSSQL task from the desktop. 1. On the Tivoli Desktop, double-click on the MSSQLManager policy region. 2. Double-click on the MSSQLManagerTasks icon. The Task Library: MSSQLManagerTasks window is displayed. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 7

78 Configuring the TEC 3. Double-click on the ConfigureTECMSSQL icon to display the Execute Task dialog. 4. In Task Options, do the following: Change the value in the Timeout field from 60 to 600. Select the Display on Desktop check box (required if you want to see the output). 5. In Execution Targets, select a managed node in the Available Task Endpoints, then click the left arrow button to move it into the Selected Task Endpoints list. The Available Task Endpoints list displays only those managed nodes that have TEC servers. 5 8 Version 1.3

79 6. Click Execute or Execute & Dismiss to display the ConfigureTECMSSQL task argument dialog. Configuring the TEC Setting Up the TEC 7. In the dialog, specify how you want the TEC configured: Rule Base Name: Enter the name of the rule base to configure. It can be a new rule base to create or an existing rule base. If you specify an existing rule base, the task checks to make sure that both its class and rule set files are defined correctly. Note: Enter only the name; do not enter a full path. If a full path is entered, only the name portion is used. Copy Rule Base: Check this box if you want to copy an existing rule base. If you do not select this option, a rule base with the specified name is created, but no rule base is copied into it. Note: If you intend to specify a rule base other than Default, be sure that the rule base is valid first. Tivoli Manager for Microsoft SQL Server User s Guide 5 9

80 Configuring the TEC Rule Base to Copy: specify the rule base to copy. If left blank, TEC copies the Default rule base. Note: If you specify an invalid rule base name, the task fails with a message that the rule base is invalid. If this happens, re-run the task with the correct rule base name. If the name is correct but the task fails, check the validity of the specified rule base by compiling the rule base. If the compiler does not report an error, the rule base is valid. Create Event Group: Check this box if you want to create an event group. Creating an event group is useful if you want to be able to assign particular administrators to manage events from Tivoli Manager for Microsoft SQL Server. Event Group Name: You may accept the default event group name of MSSQLEventBase or enter a different event group name. If the event group name you choose already exists, the appropriate filters are added to it if they do not already exist. Configure Event Server for Distributed Monitoring: check this box to configure the event server to accept events sent by monitors. Configure Event Server for Tasks: check this box to configure the event server to accept events sent from tasks. Configure Event Server for TEC NT Event Adapter: check this box to configure the event server to accept events sent from the NT Event Adapter. Configure Event Server for GEM Instrumentation: check this box to configure the event server to accept events sent from GEM Instrumentation. This option appears only if the GEM Instrumentation component has been installed. Restart Event Server: check this box if you want the task to restart the event server. The new rule base (or modified rule base) does not take effect until the event server is restarted Version 1.3

81 Configuring the TEC Note: If you do not have the task restart the event server, you must load the rule base and restart the event server manually. 8. Click Set & Execute to run the task. If the Restart Event Server option is specified, this task starts the server if it is not running, or stops and restarts it if it is currently running. If you set the Display on Desktop option (in step 4), the system displays the results of this task in a dialog similar to the following example: Setting Up the TEC 9. Click Close to return to the previous dialog. Using ConfigureTECMSSQL from the Command Line You can run the ConfigureTECMSSQL task from the command line. See ConfigureTECMSSQL in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Microsoft SQL Server Reference Guide. Tivoli Manager for Microsoft SQL Server User s Guide 5 11

82 Configuring the TEC Using TEC Commands This section describes how to set up a TEC manually using TEC commands. It shows how create and load a rule base that contains the the Tivoli Manager for Microsoft SQL Server event class definitions and rule sets. Assumptions for This Example Configuration In the following example configuration the following assumptions are made: You have the appropriate roles to create event server objects. The TEC server is installed on the same host as the TMR server. This is not an inter-region environment. There is only one TMR server. You want to configure the event server for Distributed Monitoring, tasks, and the NT Event Adapter. An import section is provided for each; you can skip any section. Note: The import steps must be performed in the order given. You create and configure a rule base named MSSQLBase. You copy the Default rule base. If you currrently use a different rule base, you can copy it instead. The rule base directory is $BINDIR/TME/TEC/rulebase_name You create and configure an event group called MSSQLBaseEvent. You configure the Tivoli environment by running the setup_env script. 1. Checking the TEC Server Make sure the TEC server has been installed and registered by using the wlookup command. wlookup -ar EventServer 5 12 Version 1.3

83 Configuring the TEC This should return one line similar to the following line; the object identification number (OID) will be different. EventServer #Tec::Server# If you have an interconnected TMR with an event server installed in each TMR, each TEC server is reported. 2. Creating the Rule Base Create a new rule base using the wcrtrb command. wcrtrb \ -d $BINDIR/TME/TEC/MSSQLBase MSSQLBase 3. Copying an Existing Rule Base Copy the contents of the Default rule base into the new rule base. using the wcprb command. wcprb Default MSSQLBase Note: If your current rule base is not Default, copy your current rule base instead. Setting Up the TEC 3. Importing Classes for Distributed Monitoring Configure the TEC for Tivoli Manager for Microsoft SQL Server distributed monitoring.import the classes, then compile them. Note: Do not type the numbers that precede each entry. They are for reference purposes only. 1 wimprbclass \ tivoli_install_dir/generic/sentrymonitors/ \ Sentry.baroc MSSQLBase 2 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLSentry/ESMSentry.baroc MSSQLBase 3 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLSentry/M7MSSQLServerSentry.baroc\ MSSQLBase 4 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLSentry/M7MSSQLDatabaseSentry.baroc \ MSSQLBase Tivoli Manager for Microsoft SQL Server User s Guide 5 13

84 Configuring the TEC 5 wcomprules \ MSSQLBase 4. Importing Classes for Tasks Configure the TEC for Tivoli Manager for Microsoft SQL Server for tasks. Import the classes, then compile them. 1 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLScripts/ESMTask.baroc MSSQLBase 2 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLScripts/MSSQLTask.baroc MSSQLBase 3 wcomprules \ MSSQLBase 5. Importing Classes and Rules for the NT Event Adapter Configure the TEC for Tivoli Manager for Microsoft SQL Server NT Event Adapter customization. Import the classes and rules, then compile them. Note: If you copied the default rule base, you do not need to import the tecad_nt.baroc file. 1 wimprbclass \ adapter_install_dir/etc/tecad_nt.baroc \ MSSQLBase 2 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLScripts/esm_tecad_nt.baroc MSSQLBase 3 wimprbclass \ tivoli_install_dir/generic/ \ MSSQLScripts/mssql_tecad_nt.baroc MSSQLBase 4 wimprbrules \ tivoli_install_dir/generic/ \ MSSQLScripts/mssql_tecad_nt.rls MSSQLBase 5 wcomprules \ MSSQLBase 6. Loading the Rule Base Load the rule base by entering the following: wloadrb MSSQLBase 5 14 Version 1.3

85 7. Activating the New Classes and Rules Do one of the following: Customizing the NT Event Adapter If the event server is running, enter the following: 1 wstopesvr 2 wstartesvr OR If the event server is not running, enter the following: wstartesvr Customizing the NT Event Adapter The CustomizeTECNTEventAdapterMSSQL task customizes the TEC NT Event Adapter to detect and forward Microsoft SQL Server events from the Windows NT event log to the TEC server. This task does the following: Checks if the NT Event Adapter is already customized for Microsoft SQL Server events. Checks if the NT Event Adapter is configured to accept customization. Makes a backup of the existing TEC NT event configuration. Customizes the NT Event Adapter to format and send Microsoft SQL Server specific events to the TEC. See Customize TEC NT Event Adapter MSSQL in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Microsoft SQL Server Reference Guide for additional information about this task. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 15

86 Customizing the NT Event Adapter Authorization The following table provides the context and authorization role required for customizing the NT Event Adapter: Activity Context Required Role Customize TEC NT Event Adapter Managed Node super, senior, mssqlserver_dba You can perform this procedure from either the Tivoli desktop or the command line. Customizing the NT Event Adapter from the Desktop Follow these steps to customize the NT Event Adapter from the desktop. 1. On the Tivoli Desktop, double-click the MSSQLManager policy region icon. 2. Double-click the MSSQLManagerTasks icon. The Task Library: MSSQLManagerTasks window is displayed. 3. Double-click on the CustomizeTECNTEventAdapter MSSQL icon to display the Execute Task dialog Version 1.3

87 Customizing the NT Event Adapter 4. In Task Options, do the following: Change the value in the Timeout field from 60 to 600. Select the Display on Desktop check box (required if you want to see the output). 5. In Execution Targets, select a managed node in the Available Task Endpoints, then click the left arrow button to move it into the Selected Task Endpoints list. The Available Task Endpoints list displays only those managed nodes that have TEC servers. 6. Click Execute or Execute & Dismiss to display the CustomizeTECNTEventAdapterMSSQL task argument dialog. Setting Up the TEC 7. Specify the task arguments in the dialog: Event class to filter out: If you want to filter out any of the available event classes, check them in the list. If you do not select any check boxes, all of the listed events are sent to the TEC. Tivoli Manager for Microsoft SQL Server User s Guide 5 17

88 Customizing the NT Event Adapter Overwrite any previous MSSQL customization: check this box to overwrite any previous Microsoft SQL Server customization to the NT Event Adapter. Note: When you run this task for the first time, you do not need to select this option to customize the Adapter. If you make subsequent changes to the customization, make sure that you select this option each time you rerun the task. If you rerun this task and do not select Overwrite any previous MSSQL customization, you receive a message that the NT Event Adapter is already customized for Microsoft SQL Server events. 8. Click Set & Execute to run the task. If you set the display options, the system displays the results of this task in a dialog similar to the following: 9. Click Close to return to the previous dialog Version 1.3

89 Customizing the NT Event Adapter from the Command Line Viewing Events in the TEC You can run the CustomizeTECNTEventAdapterMSSQL task from the command line. See Customize TEC NT Event Adapter MSSQL in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Microsoft SQL Server Reference Guide. Viewing Events in the TEC After you have set up the TEC, you can view events. The following table provides the context and authorization role required for this procedure: Activity Context Required Role View events in the TEC Event console user You can perform this procedure only from the Tivoli desktop. Setting Up the TEC Assumptions for This Example The example used in the procedure below relies on the following assumptions: The TEC has been configured and it has been configured to receive MSSQL Distributed Monitor events. (The TEC is represented on the Tivoli Desktop by an Event Server icon.) An event group named MSSQLEventBase was created when the TEC was configured The SQL Server State monitor has been configured to send an event with a severity level of FATAL to the TEC when it detects that the Microsoft SQL Server is unavailable. The SQL Server State monitor has detected this condition and has sent an event. Procedure for Viewing Events from the Desktop Use the following steps to view events: Tivoli Manager for Microsoft SQL Server User s Guide 5 19

90 Viewing Events in the TEC 1. Open the TEC console by double-clicking on the Event Server icon on the Tivoli desktop. A TEC console window appears. It contains an icon for each event group that you are authorized to view. 2. Double-click on the MSSQLEventBase icon. The list of events for that event group is displayed in the MSSQLEventBase window Version 1.3

91 Viewing Events in the TEC 3. To view the details of an event, do one of the following: Double-click on the desired event. OR Select the desired event, then click the View Message button. The Event Group Message Viewer dialog is displayed. Setting Up the TEC Information for each slot (information field) in the event is displayed in this dialog. Tivoli Manager for Microsoft SQL Server User s Guide 5 21

92 Listings of Event Classes Listings of Event Classes This section lists the event classes provided with Tivoli Manager for Microsoft SQL Server. Monitors and Tasks Tivoli Manager for Microsoft SQL Server includes event class definitions in the following files: ESMSentry.baroc Defines ESMSentry as a subclass of Sentry2_0_Base. M7MSSQLServerSentry.baroc Defines MSSQLServer as a subclass of ESMSentry. Defines classes for individual server monitors as a subclass of MSSQLServer. M7MSSQLDatabaseSentry.baroc Defines MSSQLDatabase as a subclass of ESMSentry. Defines classes for individual database monitors as a subclass of MSSQLDatabase. ESMTask.baroc Defines ESMTask as a subclass of Event. MSSQLTask.baroc Defines ESMTask as a subclass of Event. Defines MSSQLTask_Succeeded, MSSQLTask_Failed, and MSSQLTask_Abend as subclasses of ESMTask Version 1.3

93 Listings of Event Classes Collectively these files implement the following class hierarchy: Event ESMTask MSSQLTask_Succeeded MSSQLTask_Failed MSSQLTask_Abend Sentry2_0Base Sentry3_5_Base ESMSentry MSSQLServer <individual server monitor classes> MSSQLDatabase <individual database monitor classes> Note that definitions for Sentry2_0Base and Sentry3_5_Base are provided in the class definition files for Distributed Monitoring. The definition for EVENT is provided in the class definition files for TEC. MSSQLDatabase Monitor Event Classes Event class names are formed by prepending MSSQLDatabase_ to the CLI name of the monitors. Event Class MSSQLDatabase_DatabaseStatusDB MSSQLDatabase_DataSpaceUsed MSSQLDatabase_DataSpacePercentUsedDB MSSQLDatabase_Fragmentation MSSQLDatabase_LogSpaceUsed MSSQLDatabase_LogSpacePercentUsedDB MSSQLDatabase_OldestOpenTransactionDB MSSQLDatabase_OptimizerStatisticsAge MSSQLDatabase_ReplicatedTransactions MSSQLDatabase_ReplicatedTransactionRate MSSQLDatabase_ReplicationLatency MSSQLDatabase_SpaceUsedTable MSSQLDatabase_SuspectDatabase Severity Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 23

94 Listings of Event Classes MSSQLServer Monitor Event Classes Event class names are formed by prepending MSSQLServer_ to the CLI name of the monitors. Event Class MSSQLServer_CacheAverageFreePageScan MSSQLServer_CacheHitRatio MSSQLServer_CacheMaximumFreePageScan MSSQLServer_CacheNumberFreeBuffers MSSQLServer_CacheConfiguredFreeBuffersPercentUsed MSSQLServer_ClientCount MSSQLServer_ClientCountPercentUsed MSSQLServer_CommandQueueLength MSSQLServer_CPUPercentBusy MSSQLServer_CPUPercentBusyDoingIO MSSQLServer_CPUPercentIdle MSSQLServer_DatabaseStatusSRVR MSSQLServer_DataSpacePercentUsedSRVR MSSQLServer_DeliveredTransactionRate MSSQLServer_DeliveredTransactions MSSQLServer_DeliveryLatency MSSQLServer_ExtentLocksExclusive MSSQLServer_ExtentLocksShared MSSQLServer_ExtentLocksTotal MSSQLServer_ExtentLocksUpdate MSSQLServer_FreeFormSQLNumeric MSSQLServer_FreeFormSQLString MSSQLServer_IntentLocksExclusive MSSQLServer_IntentLocksShared MSSQLServer_IntentLocksTotal MSSQLServer_IOBatchAverageSize MSSQLServer_IOBatchMaximumSize MSSQLServer_IOBatchWriteRate MSSQLServer_IODiskErrors Severity Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown 5 24 Version 1.3

95 Listings of Event Classes Event Class MSSQLServer_IODiskReads MSSQLServer_IODiskWrites MSSQLServer_IOLogWriteRate MSSQLServer_IOOutstandingReads MSSQLServer_IOOutstandingWrites MSSQLServer_IOPageReadRate MSSQLServer_IOSinglePageWriteRate MSSQLServer_IOTransactionsPerLogRecord MSSQLServer_IOTransactionRate MSSQLServer_LogSpacePercentUsedSRVR MSSQLServer_NetworkReadRate MSSQLServer_NetworkWriteRate MSSQLServer_NTApplicationLog MSSQLServer_NTApplicationLogAge MSSQLServer_NTApplicationLogPercentFull MSSQLServer_NumberOfDeadlocks MSSQLServer_NumberOfBlockedProcesses MSSQLServer_OldestOpenTransactionSRVR MSSQLServer_PageLocksExclusive MSSQLServer_PageLocksShared MSSQLServer_PageLocksTotal MSSQLServer_PageLocksUpdate MSSQLServer_ProcedureBuffersActive MSSQLServer_ProcedureBuffersTotal MSSQLServer_ProcedureBuffersUsed MSSQLServer_ProcedureCacheActive MSSQLServer_ProcedureCacheSize MSSQLServer_ProcedureCacheUsed MSSQLServer_RAEffectiveness MSSQLServer_RAPagesFetchedIntoCachePerSecond MSSQLServer_RAPagesFoundInCachePerSecond MSSQLServer_RAPhysicalReadRate Severity Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 25

96 Listings of Event Classes Event Class MSSQLServer_RASlotsUsed MSSQLServer_ServiceState MSSQLServer_SQLExecutiveFailedTasks MSSQLServer_SQLServerState MSSQLServer_TableLocksExclusive MSSQLServer_TableLocksShared MSSQLServer_TableLocksTotal MSSQLServer_TotalBlockingLocks MSSQLServer_TotalExclusiveLocks MSSQLServer_TotalLocks MSSQLServer_TotalLocksPercentUsed MSSQLServer_TotalLocksRemaining MSSQLServer_TotalSharedLocks MSSQLServer_UndeliveredTransactions MSSQLServer_UserConnections MSSQLServer_UserConnectionsPercentUsed MSSQLServer_UserConnectionsRemaining Severity Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown NT Event Adapter Normally, the TEC receives Windows NT events as instances of the class NT_Base. If you do not customize the NT Event Adapter, this is the case for Microsoft SQL Server events as well. If you customize the NT Event Adapter, however, Microsoft SQL Server events use different event classes. The NT Event Adapter event class definitions are in the following files: esmtecad_nt.baroc Defines NT_ESMDBBase as a subclass of NT_Base. mssql_tecad_nt.baroc Defines the NT_MSDTCBase, NT_SQLExecutiveBase, NT_SQLServerAgentBase and 5 26 Version 1.3

97 Listings of Event Classes NT_MSSQLServerEventBase as subclasses of NT_ESMDBBase. Defines NT_MSSQLError, NT_MSSQLMessage, and NT_MSSQLInformation as subclasses of NT_MSSQLServerEventBase. Collectively these files implement the following class hierarchy: NT_Base NT_ESMDBBase NT_MSDTCBase NT_SQLExecutiveBase NT_SQLServerAgentBase NT_MSSQLServerBase NT_MSSQLError NT_MSSQLMessage NT_MSSQLInformation Note that the definition for NT_Base is provided in the class definition files for the TEC Event Adapter. The class definitions are used as follows: NT_MSDTCBase: Distributed Transaction Coordination (DTC). NT_SQLExecutiveBase: Microsoft SQL Server tasks and replication. Note: In Microsoft SQL Server Version 7.0 the SQLExecutive was renamed SQLServerAgent. The term tasks was changed to jobs. NT_SQLServerAgentBase: Microsoft SQL Server 7.0 SQLServerAgent support NT_MSSQLError: Microsoft SQL Server logged errors NT_MSSQLMessage: Microsoft SQL Server logged messages NT_MSSQLInformation: various information, such as informational messages logged during backups and when the database server is stopped and started. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 27

98 Listings of Event Classes Additional Slot Definitions The following slots are defined in the NT_MSSQLError class. Defined Slots mssql_error_number:integer mssql_severity_number:integer mssql_state_number:integer severity:default=minor Representing Microsoft SQL Server error number The Microsoft SQL Server severity number Microsoft SQL Server state number Default severity. The following slots are defined in the NT_MSSQLMessage class. Defined Slots mssql_mesg_number:integer Representing Microsoft SQL Server message number The following table shows the NT_MSSQLError TEC class severity level mappings to Microsoft SQL Server severity level groupings. The above mappings are implemented by rules defined in the mssql_tecad_nt.rls. Microsoft SQL Server Severity Numbers NT_MSSQLError Severity Value 1-10 Harmless Warning Critical Fatal 5 28 Version 1.3

99 Creating Automatic Responses to Events Creating Automatic Responses to Events You can create TEC rules that run Tivoli Manager for Microsoft SQL Server tasks as responses to TEC events. The following procedures provide examples of how to write rules using the Tivoli Enterprise Console Rule Builder to execute tasks. Two types of response are shown: Executing a task Executing a customized task See the TME 10 Enterprise Console Rule Builder s Guide for more information on using the Rule Builder. Running a Task as a Response In this example: You configure the LogSpacePercentUsedDB database monitor to send TEC events You write simple rule to execute the ADSMIncBackup task in response to receiving an event from LogSpacePercentUsedDB of severity CRITICAL The task performs a transaction log backup of the database, truncating the log after backup. You activate the rule by compiling and loading the rule base. You check to see that the event successfully triggers the execution of the task. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 29

100 Creating Automatic Responses to Events Setting Up the Monitor The monitor must be configured to send events to TEC. In the Edit Monitor dialog for the LogSpacePercentUsedDB monitor, check the Send Enterprise Console Event box. Writing the Rule Write a rule to execute the ADSMIncBackup task against the monitored database, using the following steps: 1. On the Tivoli Desktop, right-click on the Event Server icon, then choose Rule Bases. The Event Server Rule Bases dialog appears. 2. Right click on the icon for the rule base you want to edit, then choose Edit Rules. The TEC Rule Base dialog appears. 3. From Rule Set, choose New Ruleset Version 1.3

101 Creating Automatic Responses to Events 4. In the Set Name field, type a name, then Enter. 5. Choose Rule Set > Edit Ruleset. The Rule Set dialog appears. 6. Choose Rule > New Rule > Simple. The Simple Rule dialog appears. 7. In Description, enter a description of the rule set. 8. On the Simple Rule dialog, select the event class, which in this case is MSSQLDatabase_LogSpacePercentUsedDB. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 31

102 Creating Automatic Responses to Events 9. Click Conditions. The Conditions in Rule: New Simple Rule dialog appears. Set the conditions as follows: Available Attribute(s): select severity. Relation: select in list. Select Value: select CRITICAL. The dialog should appear as follows: 10. Click the Add button. 11. Click the OK button to return to the Simple Rule dialog Version 1.3

103 Creating Automatic Responses to Events 12. In the Simple Rule dialog, click the Actions button. The Actions in Rule dialog appears. 13. Set up the actions as follows: Add: select When event is received Add Actions: select Launch a Task. The Task Selection dialog appears. Select the ADSMIncBackup task from the MSSQLManagerTask Library. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 33

104 Creating Automatic Responses to Events 14. Edit the arguments: a. In the Actions in Rule dialog, click the Edit Arguments button. The Edit Arguments dialog appears. b. Enter the following in the Format string (optional) text entry box on the Edit Arguments dialog: -l MSSQLManagerTasks c. Move collection and hostname attributes from list of Available Attribute(s) to Selected Attribute(s). Note: The order in which these are selected is important. This is because in the format the %s variables are bound to the collection and hostname attributes of the event, the task will be invoked as the following: wruntask -t ADSMIncBackup \ -l MSSQLManagerTasks \ where collection is MSSQLServer and hostname is sharing@nemuchay@nemuchay d. Click OK Version 1.3

105 Creating Automatic Responses to Events 15. Click OK on the following dialogs: Actions in Rule dialog Simple Rule dialog (the following shows this dialog with the information filled in) Setting Up the TEC Rule Set dialog. 16. Choose Rule Set > Close. 17. In the TEC Rule Base dialog, choose Rule Base > Save 18. Choose Rule Base > Close You are left in the Event Server Rule Bases dialog, where you compile the rule base in the next step. Activating the New Rule To activate the new rule, you must compile the rule base, then load the newly compiled rule base into TEC. Tivoli Manager for Microsoft SQL Server User s Guide 5 35

106 Creating Automatic Responses to Events 1. From the Event Server Rule Bases dialog, right-click the rule base you just edited, then choose Compile. TEC compiles the rule base. 2. From the Event Server Rule Bases dialog, right-click the rule base you just compiled, then choose Load and activate the rule base. The rule created will be similar to the following: /*****rule2:task to do ADSMIncBackup*****/ rule: plain_rule2_8: (event: _ev2 of_class within [ MSSQLDatabase_LogSpacePercentUsedDB ] where [ severity: _ev2_severity within [ CRITICAL ], collection: _ev2_collection, hostname: _ev2_hostname ], reception_action: action0: ((exec_task(_ev2, ADSMIncBackup, -l MSSQLManagerTasks -h [_ev2_collection,_ev2_hostname], YES ))) ). Testing the New Rule Check that the task is executed when event occurs. In this case you can wait for the log to fill up to the point where it triggers the LogSpacePercentUsedDB monitor. An event should be received by the Event Server. 1. Double-click the Event Server icon, then double-click the MSSQLEventBase icon. 2. Select a MSSQLDatabase_LogSpacePercentUsedDB event from TEC Event Console. 3. Click View Action Status.You should see a dialog like the following. It shows the ADSMIncBackup task was run and that it completed successfully Version 1.3

107 Creating Automatic Responses to Events Running a Customized Task as a Response This example uses the same monitor, LogSpacePercentUsedDB. It runs a customized task, ADSMIncBackup_NoTruncate, which is simply the ADSMIncBackup saved with the NOTRUNCATE argument. This procedure assumes that the customized task already exists. 1. Do steps 1 through 12 in Writing the Rule on page Specify the derived task by selecting the Launch a program option rather than Launch a task. 3. In the Select a Program dialog, enter the full path name to wexectask (shown below), then click Set&Close. Setting Up the TEC Tivoli Manager for Microsoft SQL Server User s Guide 5 37

108 Creating Automatic Responses to Events 4. Edit the argumnets. In the Actions in Rule dialog, click the Edit Arguments button. The Edit Arguments dialog appears. In the Edit Arguments dialog, enter the following in the text entry box: t ADSMIncBackup_NoTruncate l MSSQLManagerTasks Note: The task name is specified with the t flag here. Move collection and hostname attributes from list of Available Attribute(s) to Selected Attribute(s). Order is important, because in the format the %s variables are bound to the collection and hostname attributes of the event. The derived task is invoked as the following: C:/Dev/Tivoli/bin/w32-ix86/bin/wexectask.exe \ -t ADSMIncBackup_NoTruncate \ -l MSSQLManagerTasks \ where the collection is MSSQLServer and the hostname is sharing@nemuchay@nemuchay Click OK. 5. Click OK in the following dialogs: Actions in Rule Simple Rule Rule Set 6. Choose Rule Set > Close. 7. In the TEC Rule Base dialog, choose Rule Base > Save. 8. Choose Rule Base > Close. After you have closed the rule base, compile it and test it as described in the previous section Version 1.3

109 6 6Setting Up Monitoring This chapter provides information on how to set up distributed monitoring with Tivoli Manager for Microsoft SQL Server. It includes the following topics: A brief overview of monitoring An overview of setting up monitors, including a chart of all the steps involved in setting up the monitoring profiles Setting up monitors from the Tivoli desktop Determining which monitors have been distributed to an endpoint (server or database) Determining which monitors are running at an endpoint (server or database) Setting up monitors from the CLI Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 1

110 Overview of Monitoring Overview of Monitoring A monitor captures and returns information about a resource or application in the Tivoli Management Environment, such as the database status or whether a server is available or not. In order to work, a monitor must be set up and distributed to an endpoint (server or database). Organizing Monitors Tivoli provides tools for organizing monitors on the Desktop. A profile manager is the top level of organization. Servers and databases are subscribed to profile managers. These subscriptions provide the channel through which monitors are distributed to servers and databases. A profile manager also contains profiles. Each profile contains one or more monitors. Individual profiles within the profile manager can be distributed to subscribers of the profile manager. The way you use profile managers is up to you. They can reflect functional grouping of database resources, functional grouping of monitors, or any grouping at all. Likewise, a profile can contain any combination of monitors. You do need to segregate profiles according to database resources: databases need database monitors and servers need server monitors. Here is an example for monitoring servers: Profile Manager: Server Monitors Profiles: Locks (contains selected lock monitors), Cache (contains selected cache monitors), and IO (contains selected I/O monitors). Subscribers: database servers Here is an example for monitoring databases: Profile Manager: Database Monitors Profiles: Space (contains selected monitors for database space consumption), Performance (contains selected monitors related to I/O throughput and fragmentation, and Availability (contains selected monitors that indicate how available the database is over time) 6 2 Version 1.3

111 Overview of Monitoring Subscribers: databases Subscribers themselves can be grouped into profile managers of their own. Defining Monitors The monitor definition includes: How often to check the status of the monitored resource What conditions are associated with predefined response levels (Always, Normal, Warning, Severe, Critical, Fatal). Not all thresholds have to be defined for a monitor. For example, the monitor for database server status has only two thresholds: Normal and Fatal, depending on whether the database server is running or not. What to do when the thresholds are reached (change an indicator, pop up a dialog, send , send a TEC event, start an automated response). Monitors have no predefined response level settings and response actions. You must define all of the attributes. Setup Scripts Scripts are provided for setting up a set of recommended monitors. See Scripts for Configuring Profiles in Appendix A, Monitoring Collection Information. Distributing and Activating Monitors Monitors are not active until they are distributed to subscribers. After they are distributed, they can be activated and deactivated using the monitor definitions. The monitors can also be started using the Start MS SQL Server Services and TME Monitors task and stopped using the Stop MS SQL Server Services and TME Monitors task. Setting Up Monitoring Security You can set a default user ID and group ID for a profile (collection of monitors). Anyone can read the monitor definitions and distribute them to the first level of subscribers, but only the specified users can Tivoli Manager for Microsoft SQL Server User s Guide 6 3

112 Overview of Monitoring change them. To monitor and distribute profiles, you need Admin, Senior, or Super privileges. Viewing Monitor Information There are two methods for administrators to use to keep up with monitors: indicators and the TEC (Tivoli Enterprise Console). Indicators are shown on the Tivoli Desktop. One or more indicator collections is associated with a policy region. When a monitor reaches a threshold value, it causes the indicator to change. The top level icon of the indicator collection changes as well, making the change immediately obvious on the Desktop. TEC events are shown on a console. Monitors can be configured to send events to the TEC. Administrators can observe the console. TEC provides additional capabilities in processing events, automated responses, and organizing them for presentation to administrators. Recommended Monitors Monitors are organized into groups called monitoring collections. Tivoli Manager for Microsoft SQL Server has two monitoring collections: MSSQLServer and MSSQLDatabase. For a brief description of monitoring collections, recommended monitors, and functional groups of monitors, see Appendix A, Monitoring Collection Information. For a full description of each monitor, see the Tivoli Manager for Microsoft SQL Server Reference Guide. 6 4 Version 1.3

113 Overview of Setting up Monitoring Overview of Setting up Monitoring The following table provides an overview of the procedures used in setting up monitoring. Each of the following steps has its own section later in this chapter. The Desktop is used for all procedures; a summary of comparable steps using the CLI is included in Setting Up Monitors from the Command Line Interface on page For more information on monitors, see the TME 10 Distributed Monitoring User s Guide. Step 1. Identify a policy region to contain the resources you want monitored. 2. Create a profile manager. Description The policy region must have the MSSQL managed resource type activated. See Adding and Removing the MSSQLServer Managed Resource Type on page 4-6 A profile manager is the container for a set of profiles (sets of monitors) and a set of subscribers. See page Create one or more profiles. 4. (Optional) Create an indicator collection. 5. (Optional) Associate an indicator collection with the profile(s) you create. 6. Add monitors to the profile. A profile is the container for a set of monitors. Create one or more profiles in the profile manager. See page An indicator collection gives you the means to track monitor status on the Desktop. See page Profiles are assigned to an indicator collection. Tivoli recommends using just one unless you use more monitors than can be tracked easily. See page Choose one or more monitors for each profile. See page Setting Up Monitoring 7. Define the monitors. Specify response levels, triggering conditions, and the nature of the response for each monitor, including whether it sends an event to the TEC. See page Tivoli Manager for Microsoft SQL Server User s Guide 6 5

114 Overview of Setting up Monitoring Step 8. (Optional) Schedule the monitors. 9. Set a default user and group ID for the profile. Description All monitors have a default schedule. You can change the default schedules or set schedules for individual monitors. See page Setting these IDs restricts others from changing the profile. See page Save the profile. Save the profile to make your changes take effect. See page Subscribe endpoints to the profile manager. 12. Distribute the monitors. 13. After you set up the monitors and use them for a while, you may want to optimize them. Choose the database or server endpoints that will be monitored by a profile of monitors. See page Distributing the monitors delivers them to the subscribers and activates them. See page See Chapter 9, Optimizing Microsoft SQL Server Performance Authorization Roles for Setting Up Monitors To perform all phases of setting up monitors, you need the following authorization roles: admin, senior, and mssqlserver_dba. The following table identifies the required roles for the procedures used in setting up monitors: Activity Context Required Role Add a profile manager and profile Profile manager admin Add an indicator collection Policy region admin Add and edit a monitor Distributed Monitoring profile admin 6 6 Version 1.3

115 Creating a Profile Manager Activity Context Required Role Set user and group ID (default policy) Add one or more subscribers Distribute a profile to next level Distribute a profile to all levels or distribute to an individual server endpoint or database endpoint Distributed Monitoring profile Profile manager s policy region and subscribers policy region(s) Profile Profile and server endpoint senior admin(profile) and mssqlserver_dba (SQL Server server or database endpoint) admin admin (Profile) and mssqlserver_dba (SQL Server server or database endpoint) Creating a Profile Manager Use the following steps to create a profile manager and profile in the policy region: Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 7

116 Creating a Profile Manager 1. Open the Policy Region window. 2. Choose Create >Profile Manager. The Create Profile Manager dialog appears. 3. Type a unique name that identifies the profile manager icon in the Name/Icon Label field. 4. (Optional) Select the Dataless Endpoint Mode check box. Selecting Dataless Endpoint Mode allows the profile manager to distribute to Tivoli endpoints, managed nodes, PC managed nodes, MSSQLServer and MSSQLDatabase endpoints, but not to other profile managers. If you do not select Dataless Endpoint Mode, the profile manager can distribute to other profile managers, managed nodes, and PC managed nodes, MSSQLServer and MSSQLDatabase endpoints, but not to Tivoli endpoints. 5. Click Create & Close to return to the Policy Region window. 6 8 Version 1.3

117 Creating a Profile Manager The icon for the profile manager appears with the assigned name. The following example shows a policy region with three profile manager icons. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 9

118 Creating a Profile Creating a Profile 1. Double-click on the profile manager icon to display the Profile Manager window Version 1.3

119 Creating a Profile 2. Choose Create >Profile to display the Create Profile dialog. Notes: If the SentryProfile selection is not available, it has not been added as a resource for this policy region. Use Properties >Managed Resources to display the Set Managed Resource menu. Move SentryProfile from the Available Resources list to the Current Resources list. 3. Type a unique name for the profile icon in the Name/Icon field. 4. Select SentryProfile in the Type list. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 11

120 Creating a Profile 5. Click Create & Close. The new profile icon appears in the Profile Manager window. After you have created a profile, you can do either of the following: Associate an indicator collection with it (see Creating an Indicator Collection on page 6-13) Add monitors to it (see Adding Monitors to a Profile on page 6-16) 6 12 Version 1.3

121 Creating an Indicator Collection Creating an Indicator Collection Creating an indicator collection is optional. If you want to view the status icons for distributed monitoring profiles, you must create an indicator collection for the policy region. Tivoli suggests that you create only one collection in each policy region. This simplifies keeping track of distributed monitoring profiles in several profile managers. However, if you have a policy region with too many TME 10 Distributed monitoring profiles to handle easily in a single collection, you can create as many collections as you need. Use the following steps to create an indicator collection: 1. Display the Policy Region window for a region containing Tivoli Manager for Microsoft SQL Server. 2. Choose Create >IndicatorCollection. Note: If the IndicatorCollection selection is not on the Create menu, it has not been added as a resource for this policy region. Use Properties >Managed Resources to display the Set Managed Resource menu. Move IndicatorCollection from Available Resources to Current Resources. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 13

122 Creating an Indicator Collection The Create Indicator Collection dialog appears. 3. Type a unique name for the indicator collection in the Name field. The name must be different than any other indicator name in the TMR. If two indicator collections exist with the same name, Distributed Monitoring cannot distribute status information. 4. Click Create & Close. An icon representing the indicator collection that you created appears in the Policy Region dialog. (The indicator icon is called MSSQLServer Indicator in this example.) You can now associate this indicator collection with profiles Version 1.3

123 Associating an Indicator Collection with a Profile Associating an Indicator Collection with a Profile Note: This is an optional procedure. If your monitors send events to the TEC, using the indicators may be redundant. If you want to view the status icons for Distributed Monitoring profiles, you must associate an indicator collection with the profile. If you do not already have an indicator collection, you need to create one. See Creating an Indicator Collection on page The TME 10 Distributed Monitoring User s Guide provides additional information on indicator collections. 1. Display the Policy Region window. 2. Double-click on the profile manager icon in the Policy Region window. 3. Double-click on the profile icon in the Profile Manager dialog to display the TME 10 Distributed Monitoring Profile Properties window. The name of the profile (Locks in this example) is in the Configuration Profile field. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 15

124 Adding Monitors to a Profile 4. Choose Monitoring >Select Indicator Collection to display the Select Indicator Collection dialog. 5. Highlight the indicator collection you want to use. 6. Click Set & Close. The indicator collection is now associated with the profile. Adding Monitors to a Profile This procedure describes how to select the monitor(s) that you want to use in a profile and specify any arguments required by the monitor(s). For more information about specific monitors to include in the profile, see the following: Suggested Monitoring Profiles on page A-2 Chapter 9, Optimizing Microsoft SQL Server Performance You can perform this procedure from either the Tivoli desktop or the command line Version 1.3

125 Adding Monitors to a Profile Use the following steps to add a monitor and specify arguments: 1. Open the Profile Manager window, if it is not already open. 2. Double-click on the profile s icon to display the TME 10 Distributed Monitoring Profile Properties window. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 17

126 Adding Monitors to a Profile 3. Click Add Monitor. The Add Monitor to TME 10 Monitoring Profile dialog appears. 4. Select a collection from the Monitoring Collections list. (Changing from one collection to another changes the Monitoring Sources list.) The collections include the following: MSSQLServer: provides global SQL Server availability and performance monitoring facilities. Distribute these monitors to server endpoints. MSSQLDatabase: provides database availability and performance monitoring facilities. Distribute these monitors to database endpoints. NT Monitors: installed with the Distributed Monitoring product, have some helpful monitors that can complement the monitors for Microsoft SQL Server. Using them is optional Version 1.3

127 Adding Monitors to a Profile 5. Select a monitor from the Monitoring Sources list. Do one of the following: If the selected monitor has no arguments, the monitor argument area remains empty. Go to step 7 on page OR If the selected monitor has arguments, the bottom of the Add Monitor to TME 10 Distributed Monitoring dialog displays the argument fields. Go to step 6 on page 6-20 to fill in the argument fields. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 19

128 Adding Monitors to a Profile 6. Enter responses for any fields in the Monitor Arguments area. You can find information about responses for these fields by: Clicking the About This Monitor button to display the on-line help for this monitor. Refer to the GUI Data Entry Fields sections in Chapter 3, The MSSQLServer Monitoring Collection, and Chapter 4, MSSQLDatabase Monitoring Collection, of the Tivoli Manager for Microsoft SQL Server Reference Guide. 7. Click Add Empty or the Add with Defaults. The Edit Monitor dialog appears. 8. Go to the next section, Defining Monitors Version 1.3

129 Defining Monitors Defining Monitors You define a monitor to: Associate each response level with a monitored condition. Associate each response level with an action to be taken. A response level is a label for monitored conditions. It categorizes the condition and determines when the monitor should take action in response to the monitored condition. Response levels are critical, severe, warning, normal, and always. When you edit the monitor, you associate each response level with a condition in the monitor. For example, in a Disk Space Percent Full monitor you might associate critical with 90% full and severe with 80% full. The always response level triggers every time the monitor runs. You select each response level, then set its trigger values and the action that the monitor takes in response. You can specify any combination of the available actions, such as sending a notice to a notice group and running a task. Refer to the section called Suggested Response Levels, in the monitoring chapters of the Tivoli Manager for Microsoft SQL Server Reference Guide for specific suggestions on response levels for each monitor. For general information about response levels, refer to the TME 10 Distributed Monitoring Users Guide. You can perform this procedure from either the Tivoli desktop or the command line. Note: To perform this procedure, you must have the Edit Monitor dialog displayed. 1. Do one of the following: Go to step 3, if you just added the monitoring source using the procedure in Adding Monitors to a Profile on page 6-16 and the Edit Monitor dialog appears. OR Do the following, if the Edit Monitor dialog is not displayed: a. Double-click on the profile icon that contains the monitor you want to edit. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 21

130 Defining Monitors b. Select the monitor you want to edit. c. Click Edit Monitor. The Edit Monitor dialog appears. It displays any previously entered values at the top of the dialog. 2. Select the argument that you want to edit. a. Click the up-arrow or down arrow buttons by the argument name, if the monitor has multiple arguments. (The buttons are not available when the monitor has no arguments or a single argument.) b. Enter a new value in the text area. 3. Select a response level. a. Click the arrow at the Response level menu to display the selection of responses Version 1.3

131 The drop-down list shows the available responses. Defining Monitors critical indicates an exceedingly serious problem. severe indicates a serious, but not critical, problem. warning indicates a problem important enough to require an alert. normal indicates that the returned value does not meet the thresholds for the critical, severe, or warning. This response does not accept a threshold setting. always responds whenever the monitor returns any value. It blanks out the trigger when and condition fields. b. Select the response level you want by highlighting it. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 23

132 Defining Monitors 4. Specify when you want the monitor to trigger at the selected response level. a. Click the arrow at the trigger when drop-down menu to display the selection of operators, then choose an operator. The operators are described in Appendix C, Operator Groups. b. Enter a value for the operator in the argument field next to the operator field. The value defines the operator threshold. 5. Specify one or more actions when the condition that you just specified is met. Send Tivoli Notice sends a notice to a specified notice group. To receive the notice, you must be subscribed to the group. Click the arrow to display and select the list of notice groups. Popup displays a pop-up alarm window on the desktops of either all administrators (the default) or of the specified administrator. Click the arrow to display and select from the list of administrators. Change Icon changes the icon state in an indicator collection to reflect the response level. (You must have an indicator collection associated with the profile.) Tasks performs a task specified in any task library. Note: Do not use the Tasks button to run Tivoli Manager for Microsoft SQL Server tasks; use the Run program option Version 1.3

133 Defining Monitors Send to sends to one or more addresses. Separate multiple addresses with commas. Log to file writes the information returned by the monitor to a log file. If the file does not exist, Distributed Monitoring creates it. You must specify an existing directory for the file. Run program launches a program or script. This response is executed under the same user ID and group ID as specified in the profile. To trigger a task as a response action: a. Select the Run program check box. b. Type wruntask <Task> in the field to the right of the Run program check box. <Task> is the CLI task name and its arguments. See CLI Syntax in Chapter 2, The MSSQLManagerTasks Library, in the Tivoli Manager for Microsoft SQL Server Reference Guide. Send Enterprise Console event sends the information returned by the monitor to a Tivoli Enterprise Console (TEC) server as an event. If you select this option, specify the severity level for the TEC event and the host on which the TEC event server resides. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 25

134 Scheduling the Monitor The following example shows a completed Edit Monitor dialog. The Total Locks Percent Used monitor sends an event to the TEC when it detects that more than 95% of the locks are used. Scheduling the Monitor You can schedule monitors to capture information at specific times. The Tivoli-defined default schedule for monitors is hourly. You can schedule monitors as frequently as once a minute. Base your monitoring frequency on how often you need updated information and the number of monitors running on a managed node. When you schedule too many monitors too frequently, you may impact system and network performance. You have the following options for scheduling monitors: Set your own default schedule for all monitors in a profile Version 1.3

135 Scheduling the Monitor Set a different schedule for each monitor in the profile. Set your own default schedule for the profile and set individual schedules for specific monitors in that profile. Individual monitor schedules override profile-wide schedules. For example, if you do the following: Set your own default schedule for ProfileX, which contains MonitorA, MonitorB, MonitorC, and MonitorD Set individual schedules for MonitorA and MonitorB in ProfileX When you distribute ProfileX: MonitorA and MonitorB run according to their individual schedules. MonitorC and MonitorD run according to the default schedule for ProfileX. You can perform this task only from the TME 10 desktop. Setting Your Own Default Schedule for a Profile The section describes how to set default profile schedules. Use the following steps to set profile schedules: Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 27

136 Scheduling the Monitor 1. Display the TME 10 Distributed Monitoring Profile Properties window for the profile. 2. Choose Edit Set Default Schedule to display the Set Monitoring Schedule dialog. Notice that the dialog displays the word Default under the profile name (which is Locks in this example) Version 1.3

137 Scheduling the Monitor 3. Do one of the following: To start capturing information when the monitor is distributed, do not specify any values in Start monitoring activity. OR To start the monitor at a specific point in time: a. Specify the date in the Month, Day, and Year fields, b. Specify the hour and the minute and click either the AM or the PM button. 4. Specify how often you want the monitor to run in a given time span with the Check monitor every field and its units list Entering 5 and specifying minutes means the monitor is scheduled to run every five minutes. 5. Do one of the following: Restrict this schedule to certain hours or days of the week. (See Restricting a Schedule on page 6-32.) OR Accept the schedule with the default restrictions, which allows monitoring at all times unless there are profile restrictions. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 29

138 Scheduling the Monitor 6. If you want to set individual schedules for the monitor, leave the Edit Monitor dialog open and go to the next section. Otherwise, click Change & Close. Setting Individual Schedules for Individual Monitors To perform this procedure, you must have the Edit Monitor dialog displayed. 1. Do one of the following: Go to step 3, if the Edit Monitor dialog appears. OR Do the following to display the Edit Monitor dialog: a. Double-click on the profile icon that contains the monitor. b. Select the monitor you want to edit. c. Click Edit Monitor. The Edit Monitor dialog appears Version 1.3

139 Scheduling the Monitor 2. Click Set Monitoring Schedule to display the Set Monitoring Schedule dialog. The dialog displays the name of the monitor that you want to schedule, Total Locks Percent Used, beneath the profile name, Locks. They appear in the upper right corner of the dialog. 3. Do one of the following: To start capturing information immediately when the monitor is distributed, do not change the default values in Start monitoring activity. OR To start the monitor at a specific point in time in the future a. Specify the date in the Month, Day, and Year fields, b. Specify the hour and the minute and click either the AM or the PM button. 4. Enter how often you want the monitor to run in a given time span with Check monitor every and its units list. For example, Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 31

140 Scheduling the Monitor entering 5 and specifying minutes schedules the monitor to run every five minutes. 5. Do one of the following: Click Restrictions to restrict this schedule to certain hours or days of the week. (See Restricting a Schedule on page 6-32.) OR Click Change & Close to accept the schedule. Restricting a Schedule This section tells you how to restrict a specific monitor schedule by setting broad parameters, such as certain hours or days of the week. The default restrictions allow monitoring all the time, unless there are profile restrictions. 1. Before starting this procedure, set up the schedule using the procedures in either Setting Your Own Default Schedule for a Profile on page 6-27 or Setting Individual Schedules for Individual Monitors on page Version 1.3

141 Scheduling the Monitor 2. Click Restrictions. The Monitoring Schedule Restrictions dialog appears. 3. Select one or more of the options under Allow Monitoring Activity. During the day or At night runs during hours set by Distributed Monitoring. These are selected by default. During the week or Weekends runs the monitor on days set by Distributed Monitoring. These are selected by default. 4. You can now do one of the following: Customize the restrictions (go to step 5). OR Click Set & Close to accept the restrictions. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 33

142 Scheduling the Monitor 5. Click Customize. The Customize Monitoring Schedule Restrictions dialog appears. The AM and PM drop-down lists beside the Daytime hours and Nighttime hours labels mark the time spans set for the During the day and At night options on the Monitoring Schedule Restrictions dialog. The day of the week drop-down lists beside Week days and Weekend days mark the time spans set for the During the week and On Weekend options on the Monitoring Schedule Restrictions dialog. The drop-down lists beside Custom hours and Custom days mark the time spans set for the those options on the Monitoring Schedule Restrictions dialog. 6. Select the options that customize the restrictions in the best way for your environment. For example, if you selected the During the day check box in preparation for scheduling the monitor to run from 3 a.m. through 2 p.m., select 3 and 2 in the AM and PM drop-down menus for the Daytime hours field Version 1.3

143 Setting User and Group ID for a Profile 7. Click Set & Close to set your choices and return to the Monitoring Schedule Restrictions dialog. 8. Click Set & Close to set your choices and return to the Edit Monitor dialog. 9. Click Change & Close. This dialog closes. 10. Click Change & Close on the Edit Monitor dialog. Setting User and Group ID for a Profile The user and group ID for a profile are determined by the operating system context under which a monitor executes. Only a Tivoli administrator who has the mssqlserver_monitor role can run Microsoft SQL Server monitors. The administrator must also have a login for any machine on which the monitor runs. You can see the logins for an administrator in the Edit Logins dialog in the Administrators collection. Use the following steps to set the user and group ID: 1. Display the TME 10 Distributed Monitoring Profile Properties window. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 35

144 Setting User and Group ID for a Profile 2. Choose Edit > Set User & Group ID. Tivoli displays the Edit Default Policies dialog. 3. Enter the name of the administrator in the Remote user ID field. The monitor runs in the context of the administrator account. This administrator must have a valid login on the operating system as well as a Tivoli login. The administrator must have the appropriate roles. For example, if the Tivoli administrator: jgough is running monitors on both UNIX and NT hosts, jgough must be a valid login name on both the UNIX and NT hosts and be a valid Tivoli login name Version 1.3

145 Saving a Profile Saving a Profile 4. In the Remote group ID field, enter the remote group ID for that remote user ID. 5. Click Change & Close button to return to the TME 10 Distributed Monitoring Profile Properties window. After you set up your profile, you must save it. 1. Display the TME 10 Distributed Monitoring Profile Properties window. 2. Choose Profile >Save. Subscribing Endpoints to Profile Managers You must add subscribers to the profile manager before you can distribute a monitoring profile. Subscribing an endpoint to a profile manager determines which resources receive the monitors. Tivoli Distributed Monitoring uses the list of subscribers to determine the endpoints that can be and that are being used to monitor resources. Use the following steps to add subscribers to the profile manager: Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 37

146 Subscribing Endpoints to Profile Managers 1. Select the policy region that contains the profiles you want to distribute from the Tivoli desktop. 2. From the Policy Region window, select the profile manager that you want to use by double-clicking on it. 3. Choose Profile Manager >Subscribers Version 1.3

147 The Subscribers dialog appears. Subscribing Endpoints to Profile Managers 4. Select the subscribers (to which you want to distribute the profile that you created) from the Available to become Subscribers list. 5. Click the left arrow button to move the selected subscribers to the Current Subscribers list. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 39

148 Subscribing Endpoints to Profile Managers 6. Click Set Subscriptions & Close. The new subscribers icons are displayed in the Profile Manager window Version 1.3

149 Distributing a Monitoring Profile Distributing a Monitoring Profile Once your monitoring profile is set up and has subscribers, you can distribute it. 1. Select the policy region that contains the profiles you want to distribute from the Tivoli desktop 2. From the Policy Region window select the profile manager that you want to use by double-clicking on it. This displays the Profile Manager window. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 41

150 Distributing a Monitoring Profile 3. Select the profile that you want to distribute and double-click on it to display the TME 10 Distributed Monitoring Profile Properties window. 4. Choose Profile Distribute Version 1.3

151 The Distribute Profile dialog appears. Distributing a Monitoring Profile 5. Select one of the following options in the Distribute To area to specify which subscribers receive the profile. Next Level of Subscribers: distributes the profile only to the endpoint subscribers listed in the Distribute To These Subscribers list. If there are profile managers among the subscribers, the profile is not distributed to their subscribers. Those subscribers are at a deeper level. All Levels of Subscribers: distributes to all levels of subscribers under the selected subscriber. Use this option under either of the following conditions: - The selected profile contains nested profile managers as subscribers and you want to distribute the profile to all subscribers in the distribution hierarchy. - The selected profile contains only server-endpoint or database-endpoint subscribers. 6. Select one of the following options in the Distribute Will area. Preserve modifications in subscribers copy of the profile: keeps entries that appear in the subscriber s profile, Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 43

152 Distributing a Monitoring Profile even though they do not appear in the profile being distributed. Make subscribers profile an EXACT COPY of this profile: overwrites the subscriber s profile with an exact copy of the profile being distributed. Do not use the Distribute to These Subscribers list for this procedure. See Subscribing Endpoints to Profile Managers on page Distribute the profile immediately or designate a time at which it will be distributed. To distribute the profile immediately, click Distribute & Close. The dialog closes after the profile is distributed. OR To set a time to distribute the profile: a. Click Schedule. The Add Scheduled Job dialog appears. b. Use the Add Scheduled Job dialog to schedule the distribution and to tell Distributed Monitoring to try to distribute the profile again if one or more attempts fail Version 1.3

153 Understanding Monitor Output c. Click Distribute & Close on the Distribute Profile dialog. The profile is distribued. You return to the TME 10 Distributed Monitoring Profile Properties window. 8. Choose Profile Close to close the window. Note: You can also distribute monitors by dragging the profile icon and dropping it on a subscriber icon. Understanding Monitor Output The Tivoli Manager for Microsoft SQL Server monitors can provide output information in several forms when they run: Tivoli notices, pop-up dialogs, , log messages, and TEC events. This section describes the information that is provided in monitor output, using a pop-up dialog as an example. The following shows an example of output from the MSSQLServer monitor Cache Average Free Page Scan. Distributed Monitoring prof1 Is the name of the profile. Cache Average Free Page Scan Is the name of the monitor. hbergin@hbergin Is the name of the server and the host (server@host). 08/05/ :07:00 Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 45

154 Understanding Monitor Output Is the time and date on which the monitor was run, read from the Windows NT system clock. You can control the time format in the Regional Settings control panel in Windows NT. Status: <<<normal>>> Is the exit code, which indicates the success or failure of the monitor. Normal is returned only when no severity levels have been breached and the monitor has been set to always return a value. E.EXEC is a problem; an error occurred while running the monitor. Warning, Severe, or Critical are returned when a severity threshold is broken, the appropriate severity level is returned. Previous Current Effective Is the value returned by the preceding monitor probe. For example, if the monitor is run at 4:55 p.m., 5 p.m., and 5.05 p.m., this value is for 5 p.m. The first time this monitor is run in any monitoring session, there is no value for this field. Is the value returned by the most recent monitor probe. For example, if the monitor is run at 4:55 p.m., 5 p.m., and 5:05 p.m., this value is for 5:05 p.m. This value does not apply to any of the Tivoli Manager for Microsoft SQL Server monitors. Trigger Info Provides any additional information that may be helpful. For example, this value might be the name of a database. (Not shown) #ENDPOINT_OID= Is the object ID for the endpoint. It is used internally by Tivoli, but you can also specify it in CLI commands and use it for tracing activities with this object Version 1.3

155 Determining Which Monitors have been Distributed to an Endpoint #MSSQLSERVER_OID= Is the object ID for the Microsoft SQL Server. It is used internally by Tivoli, but you can also specify it in CLI commands and use it for tracing activities with this object. Determining Which Monitors have been Distributed to an Endpoint From the Tivoli desktop, you can quickly determine which monitors have been distributed to a specific endpoint. 1. Locate and double-click on the icon endpoint. The dialog for that endpoint appears. In the following example, the dialog for server endpoint jfrackow@jfrackow appears. 2. On the endpoint s dialog, look for an icon that represents a profile. If you do not find this icon, no monitors have been distributed to the endpoint. Setting Up Monitoring Tivoli Manager for Microsoft SQL Server User s Guide 6 47

156 Determining Which Monitors Are Running at an Endpoint 3. If you do find an icon for a profile, double-click on the icon. The Distributed Monitoring Profile Properties window appears. It lists the monitors distributed to the endpoint. Determining Which Monitors Are Running at an Endpoint Use the wlseng command to determine which monitors are running at an endpoint. You cannot determine which monitors are running at an endpoint from the Tivoli desktop. See the TME 10 Distributed Monitoring User s Guide for more information about this command. Setting Up Monitors from the Command Line Interface Use the steps in this section to set up your monitors from the command line. For additional information about the commands in this section, see the TME 10 Framework Reference Manual and the TME 10 Distributed Monitoring Reference Manual Version 1.3

157 Setting Up Monitors from the Command Line Interface 1. Use the wsetpr command to specify the types of resources that you want to work with in your policy region. For example, to specify that the TestRegion policy region can contain the MSSQLServer and SentryProfile resource types, enter the following command: wsetpr MSSQLServer 2. Use the wcrtprfmgr command to create a profile manager. For example, to create a profile manager called ProfMgr2 in the TestRegion policy region, enter the following command: ProfMgr2 3. Use the wcrtprf command to create a profile. For example, to create a profile called SentryProf2 in the ProfMgr2 profile manager, enter the following command: SentryProfile SentryProf2 4. Use the wcrtsntcoll to create an indicator collection. wcrtntcoll IndicatorCollection2 5. Use the wsetcoll command to set the affiliation of the SentryProf2 profile to the Indicatorcollection2 collection, enter the following command wsetcoll IndicatorCollection2 SentryProf2 6. Use the wsub command to add subscribers to the profile manager. For example, to add subscribers DBMXSERV@DBMXSERV and nemuchay@nemuchay (both MSSQLServer endpoints) to the profile manager ProfMgr2, enter the following command: Setting Up 7. Use the waddmon command to create monitors. For specific examples of how to use the waddmon command for Microsoft SQL Server monitors, refer to the sections called CLI Syntax and CLI Examples in both Chapter 3, The MSSQLServer Tivoli Manager for Microsoft SQL Server User s Guide 6 49

158 Setting Up Monitors from the Command Line Interface Monitoring Collection, and Chapter 4, MSSQLDatabase Monitoring Collection, in the Tivoli Manager for Microsoft SQL Server Reference Guide. To send an event to the TEC using the waddmon command, the syntax would look similar to the following: waddmon"mssqlserver"databasestatussrvr-t "5 minutes" -c critical -R "!=" up -n "Microsoft SQL Server Sentry" -T \ ServerProfile 8. Use the wsetsntid command to set the default user and group ID for a profile. The following example sets user and group IDs for a distributed monitoring profile called SentryProf2. wsetsntid "Administrator" "" SentryProf2 Administrator specifies the user ID. "" specifies a blank group ID. SentryProf2 specifies the distributed monitoring profile. 9. Use the wdistrib command to distribute the profile from the command line. For example, to distribute the profile called Sentry Profile Performance Profile to a Tivoli Manager for Microsoft SQL Server endpoint with the label nemuchay@nemuchay, enter the following command from the command line: wdistrib The example distributes the profile to the subscribing Microsoft SQL Server Endpoint.This distribution overwrites all local changes 6 50 Version 1.3

159 7 7Using Tivoli Manager for Microsoft SQL Server Using Tivoli Manager for Microsoft SQL Server After you finish setting up the various components of Tivoli Manager for Microsoft SQL Server, you are ready to manage Microsoft SQL Server database servers and databases. This chapter provides the procedures for using the software and covers the following topics: Opening a database server endpoint Viewing database server properties Starting and shutting down a database server Checking the state of a database server Changing database server registration Refreshing databases and opening a database endpoint Using other Tivoli facilities Tivoli Manager for Microsoft SQL Server User s Guide 7 1

160 Opening Database Server Endpoints Opening Database Server Endpoints Each database server endpoint has an icon on the desktop. You can open it to do the following: View the distributed monitoring profiles for the database server and its databases Access the Refresh Databases and Change Registration options for the server Remove a database endpoint from the database server endpoint, thus removing the database from Tivoli management The following table shows the context and the required authorization role for this procedure: Activity Context Required Role Opening the endpoint Database server mssqlserver_user or mssqlserver_dba You can perform this procedure from the Tivoli desktop only. Use the following steps to open a database server endpoint: 1. From the Tivoli desktop, select the policy region that contains the Tivoli Manager for Microsoft SQL Server resource by double-clicking on it. This displays the Policy Region window. 2. Right-click the database server icon, then choose Open. 7 2 Version 1.3

161 Opening Database Server Endpoints The MS SQL Server Collection window appears, showing the managed databases and monitors associated with the database server. Using Tivoli Manager for Microsoft SQL Server The SQL Server Collection window displays the following information: The database server identifier is displayed in the window title, typically in the format. The identifier in the sample window is The database server s databases and the profiles it has received are displayed in this window. The database identifier is databasename@ servername@hostname. In this example, there are several database identifiers. One is called pubs@jfrackow@jfrackow. The Distributed Monitoring profile identifier is profilename@servername@hostname. In this example, there are no profiles distributed to the server. Tivoli Manager for Microsoft SQL Server User s Guide 7 3

162 Viewing Database Server Properties Viewing Database Server Properties Using Properties displays the following information about the database server: Database server name Logon name Version number Name of the host where the database server is installed Status of the database server The following table provides the context and authorization role required for this procedure: Activity Context Required Role View properties Database server mssqlserver_user or mssqlserver_dba You can perform this procedure from the Tivoli desktop only. Use the following steps to view Microsoft SQL Server properties: 1. From the Tivoli desktop, select the policy region that contains the Tivoli Manager for Microsoft SQL Server resource by double-clicking on it. This displays the Policy Region window. 2. Right-click the database server icon, then choose Properties. 7 4 Version 1.3

163 The Server Properties dialog appears. Starting a Database Server Using Tivoli Manager for Microsoft SQL Server Starting a Database Server The Startup option can start any or all of the database server s services and start its monitors. You can start services and monitors independently. The option provides the same functionality as the Start MS SQL Server Services and TME Monitors task. For more information on this task, see Chapter 2, The MSSQLManagerTasks Library, in the Tivoli Manager for Microsoft SQL Server Reference Guide. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Start Database server mssqlserver_dba You can perform this procedure from either the Tivoli desktop or the command line. Starting a Database Server from the Desktop Use the following steps to start a database server: Tivoli Manager for Microsoft SQL Server User s Guide 7 5

164 Starting a Database Server 1. From the Tivoli desktop, select the policy region that contains the Tivoli Manager for Microsoft SQL Server resource by double-clicking on it. This displays the Policy Region window. 2. Right-click the database server icon, then choose Startup. The StartServMon dialog appears. It is the same dialog that you see if you start the server using the Start MS SQL Server Services and TME Monitors task. 7 6 Version 1.3

165 Starting a Database Server 3. Select the appropriate response for each field in the StartServMon task argument dialog. For help on the information required for each field in this dialog, click the Task Description button. 4. Click Set & Execute to run the task. Upon successful startup, the database server icon is shown in the OK state. The following example shows the OK state. Using Tivoli Manager for Microsoft SQL Server Starting a Server from the Command Line There are two ways to start the server from the command line. You can run the StartServMon task from the command line. See CLI Syntax and CLI Examples for Start MS SQL Server Services and TME Monitors in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Microsoft SQL Server Reference Guide. You also can start a database server from the command line with the mstartup command. The mstartup command starts the server in NORMAL mode. The following shows the syntax for this command: mstartup <server_name> where <server_name> specifies the database server. The following command starts server mmoore@mmoore: mstartup mmoore@mmoore Tivoli Manager for Microsoft SQL Server User s Guide 7 7

166 Shutting Down a Database Server Shutting Down a Database Server The Shutdown option can stop any or all of the database server s services and stop its monitors. You can stop services and monitors independently. This option provides the same functionality as the Stop MS SQL Server Services and TME Monitors task. For more information on this task, see Chapter 2, The MSSQLManagerTasks Library, in the Tivoli Manager for Microsoft SQL Server Reference Guide. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Shutdown Database server mssqlserver_dba You can perform this procedure from either the Tivoli desktop or the command line. Shutting Down a Server from the Desktop Use the following steps to shut down the database server. 1. From the desktop, double-click the policy region that contains the Tivoli Manager for Microsoft SQL Server resource. The Policy Region window appears. 2. Right-click the database server icon, then choose Shutdown. 7 8 Version 1.3

167 Shutting Down a Database Server Tivoli displays the StopServMon dialog, which is the same dialog that you see if you shut down the server using the Stop MS SQL Server Services and TME Monitors task. Using Tivoli Manager for Microsoft SQL Server 3. Enter information for each field in the StopServMon task argument dialog. For help on the information required for each field in this dialog, click the Task Description button. 4. Click Set & Execute to run the task. Upon successful shutdown, the icon is shown in the SHUTDOWN state. Tivoli Manager for Microsoft SQL Server User s Guide 7 9

168 Checking a Server s State from the Desktop Shutting Down a Server from the Command Line There are two ways to shut down the server from the command line. You can run the StopServMon task from the command line. See Stop MS SQL Server Services and TME Monitors in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Microsoft SQL Server Reference Guide. You can also use the mshutdown command, which performs the same function the StopServMon task using the Shutdown with wait option. The following shows the syntax for the mshutdown command. mshutdown <server_name> where <server_name> specifies the name of the server you want to shut down. For example, the following command shuts down server mmoore@mmoore: mshutdown mmoore@mmoore Checking a Server s State from the Desktop The Check State option tells you if the database server is up, down, or suspect. This function also runs every time a task is run. When a database server crashes or is shut down from outside Tivoli, the server icon does not reflect the new state until one of the following happens: An administrator runs the Check State option. The SQL Server State monitor checks the server. See Chapter 3, The MSSQLServer Monitoring Collection, in Tivoli Manager for Microsoft SQL Server Reference Guide for more information. The following table provides the context and authorization role required for this procedure:. Activity Context Required Role Check state Database server mssqlserver_user or mssqlserver_dba 7 10 Version 1.3

169 Checking a Server s State from the Desktop You can perform this procedure from the Tivoli desktop only. Use the following steps to check the state of a Microsoft SQL Server. 1. From the Tivoli desktop, double-click the policy region that contains the Tivoli Manager for Microsoft SQL Server resource. This displays the Policy Region window. 2. Right-click the database server icon, then choose Check State. Using Tivoli Manager for Microsoft SQL Server If the MSSQLServer service is stopped by the SQL Service Manager, the control panel, or a user-issued SHUTDOWN TSQL statement to the database, the state becomes SHUTDOWN. The server is considered SUSPECT when it is not in a shutdown state but Tivoli Manager for Microsoft SQL Server is unable to get a connection to it. For example, it may be SUSPECT because the logon information is incorrect or the server has been paused. The following examples show the server icon in all three states, OK, SHUTDOWN, and SUSPECT. Tivoli Manager for Microsoft SQL Server User s Guide 7 11

170 Changing the Registration Investigating a SUSPECT State If the server is in a SUSPECT state, right-click on the server icon, then choose Properties. More information about why the server is in a SUSPECT state may be listed there. Changing the Registration You can use the Change Registration command to change the logon details for a currently registered database server when the current logon is no longer valid. The following table provides the context and authorization roles required for registering servers and discovering databases: Activity Context Required Role Change database server registration Policy region mssqlserver_dba and senior at TMR You can perform this procedure from the Tivoli desktop only. Use the following steps to change the registration of the database server: 1. From the Tivoli desktop, double-click the policy region that contains the Tivoli Manager for Microsoft SQL Server resource. The Policy Region window appears Version 1.3

171 Refreshing Databases from the Desktop 2. Right-click the database server icon, then choose Change Registration. The Change Server Registration Details dialog appears. Using Tivoli Manager for Microsoft SQL Server You cannot make entries to the SQLServer, Version, or Host fields. 3. Either make the SQLServer Login field blank or enter a logon name that has access to the database server and its databases. Tivoli recommends leaving this field blank, which causes Tivoli Manager for Microsoft SQL Server to logon using a trusted connection. See Using Trusted Connections on page 4-14 for more information on trusted connections. 4. If you entered a logon name, enter the password in the Password field; if you did not enter a logon, leave this field blank. 5. Select the Ignore Server Status box to change the logon information for a server that is not running. 6. Press the Change and Close button. Refreshing Databases from the Desktop When you register a database server (see Registering a Database Server and Discovering Its Databases on page 4-9), Tivoli Tivoli Manager for Microsoft SQL Server User s Guide 7 13

172 Refreshing Databases from the Desktop automatically updates its objects (databases and monitors) if it succeeds in logging on to the server. The database then appears as an endpoint in the database server s list of databases. In the following illustration, Northwind@jfrackow@jfrackow and master@jfrackow@jfrackow are examples of Microsoft SQL Server database icons. You can also manually update the server s list of objects. During the lifetime of a server, you may add and drop databases at the server. When you use Refresh Databases, it updates the list of endpoints, removing icons for dropped databases and adding icons for new databases. Currently, only information on databases and endpoint profiles are refreshed. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Refresh databases Server mssqlserver_dba or mssqlserver_user To refresh a server s list of objects, do the following: 7 14 Version 1.3

173 Refreshing Databases from the Desktop 1. From the Tivoli desktop, select the policy region that contains the Tivoli Manager for Microsoft SQL Server resource by double-clicking on it. This displays the Policy Region window. 2. Right-click the database server icon, then choose Open. Using Tivoli Manager for Microsoft SQL Server The SQL Server Collection window appears. Tivoli Manager for Microsoft SQL Server User s Guide 7 15

174 Opening a Database Endpoint from the Desktop 3. Choose Server >Refresh Databases. The list of icons in the window is updated. Note: You also can refresh databases using the Refresh Databases task. For more information on this task, see Chapter 2, The MSSQLManagerTasks Library, in the Tivoli Manager for Microsoft SQL Server Reference Guide. Opening a Database Endpoint from the Desktop Tivoli displays a database endpoint as an icon. You can open the database icon to view the profiles distributed to it. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Open the endpoint Database mssqlserver_user or mssqlserver_dba You can perform this procedure from the Tivoli desktop only. Use the following steps to open a database endpoint: 1. From the Tivoli desktop, double-click the policy region that contains the Tivoli Manager for Microsoft SQL Server resource. The Policy Region window appears. 2. Right-click the database server icon, then choose Open Version 1.3

175 Opening a Database Endpoint from the Desktop 3. Right-click the database icon, then choose Open. (You also can double-click on the database icon.) Using Tivoli Manager for Microsoft SQL Server The SQL Server Database window appears. The title is typically displayed as databasename@servername@hostname, which in this example is pubs@mmoore@mmoore. The database window displays the profiles it has received, which in this example is DatabaseMonitors@pubs@mmoore@mmoore. Tivoli Manager for Microsoft SQL Server User s Guide 7 17

176 Using Other Tivoli Facilities Using Other Tivoli Facilities This is a summary of the Tivoli facilities that you commonly use in the course of managing Microsoft SQL Server with Tivoli Manager for Microsoft SQL Server. Cross-references are given to other parts of this book. Working with Tasks and Jobs When you installed and set up Tivoli Manager for Microsoft SQL Server, you registered database servers and discovered their databases. You can now run tasks on those endpoints. You can also create, run, and schedule jobs. See the following pages for more information. Running tasks: see Running Tasks on page 8-3. Creating jobs: see Creating Jobs on page Running and scheduling jobs: see Running and Scheduling Jobs on page Working with Monitors When you set up and distributed monitors (as described in Chapter 6, Setting Up Monitoring ), the monitors were put in place. You can now track information that the monitors provide, using indicators or the TEC. You can also change monitor settings and redistribute the monitors to make the changes take effect. Using Indicators You can view indicators to determine the status of server monitors and database monitors. Before you can view indicators, you must create an indicator collection as described on page 6-13 and associate it with a monitoring profile as described on page To view indicators, do the following: Double-click on the top-level indicator collection that you created. A list of monitors is displayed. Double-click the desired indicator Version 1.3

177 Using Other Tivoli Facilities Using the TEC If you set up individual monitors to send events to the TEC, you can use the TEC to view them. See Working with the TEC, in a later section. Changing Monitor Settings and Redistributing Them If you determine that you want to change threshold conditions or the way monitors respond to changes, you can edit the monitors as described in Defining Monitors on page 6-3, then distribute them as described in Distributing and Activating Monitors on page 6-3. Using Tivoli Manager for Microsoft SQL Server Working with the TEC If you have set up tasks or monitors to send events to the TEC, you can monitor those events in the TEC console. Viewing events is described in Viewing Events on page 5-3. Tivoli Manager for Microsoft SQL Server User s Guide 7 19

178 Using Other Tivoli Facilities 7 20 Version 1.3

179 8 8Using Tasks and Jobs This chapter describes how to use tasks and jobs to carry out administrative operations. This chapter covers the following procedures: Running tasks Customizing the standard Tivoli Manager for Microsoft SQL Server tasks and saving the customized values Creating jobs from the standard Tivoli Manager for Microsoft SQL Server tasks or from any customized tasks Running jobs Scheduling jobs The MSSQLManagerTasks library is installed in the MSSQLManager policy region during installation. Tivoli recommends that you do not remove the task library from this policy region; it contains default policies that affect how the task library works. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 1

180 Introduction to Tasks and Jobs Introduction to Tasks and Jobs A task is an operation, such as backing up a database. The MSSQLManagerTasks library provides a set of standard tasks. When you run a task, you are prompted for: Where to run the task (one or more endpoints or profile managers) Task arguments, parameters that determine how the task works A customized task is based on a standard task. When you create it, you provide the following information: A unique name (to differentiate it from standard tasks on the desktop) Where the task is to run Task arguments When you run a customized task, it does not prompt you for input, because you have already specified all of the necessary information. A job can be executed on specified endpoints at specified times. A job has its own icon in the task library and a name that you choose when you create it. A job consists of a task to run plus information on where and when to run it. You can create jobs from standard tasks or from customized tasks. If you create a job from a standard task, the task may prompt for required arguments when it is run. If you create a job from a customized task, the task does not prompt for input because the arguments are already specified. You can use the Scheduler resource to schedule the jobs to execute at specified times. Only jobs can be scheduled. Tasks must be executed manually. Tasks and jobs are subject to policy, which is enforced by the policy region containing the task library in which the task or job is defined. For more information about tasks and jobs, see the TME 10 Framework User s Guide. 8 2 Version 1.3

181 Running Tasks Running Tasks You execute, or run, Tivoli Manager for Microsoft SQL Server tasks in the same way that you run other Tivoli tasks. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Run a task Database and Managed Node You can perform this procedure from either the Tivoli desktop or the command line. Running Tasks from the Desktop mssqlserver_dba Use the following steps to run a task in a Tivoli Manager for Microsoft SQL Server task library: 1. Display the Task Library: MSSQLManagerTasks window as follows: a. On the TME Desktop, double-click the MSSQLManager policy region icon. b. Double-click the MSSQLManagerTasks icon. The Task Library: MSSQLManagerTasks window appears. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 3

182 Running Tasks 2. Execute the desired task by one of the following methods: Double-click the task icon. Right-click on the task icon, then choose Execute Task. The Execute Task dialog appears, which is a generic dialog of execution parameters for all tasks. 3. Under Execution Mode, select one of the following: Parallel to run the task on all targets in parallel Serial to run the task on all targets, but one target at a time, in alphabetical order Staged to run the task in a staged fashion on sets of managed nodes. When you select this option, the Staging Count and Staging Interval fields in the Execution Parameters area 8 4 Version 1.3

183 Running Tasks become available; you must enter the appropriate values for these fields. The task is executed on the endpoints in alphabetical order. 4. In the Timeout field type a timeout value for the task. This is the number of seconds that the task or job has to complete before an error is returned. The default is 60 (seconds). If the task takes longer to complete than the specified Timeout and is running in Serial or Staged mode, Tivoli moves on to other endpoints after this time expires. The task continues to execute on the endpoint, even though Tivoli has stopped waiting for it to end. 5. If you selected Staged for the Execution Mode, specify the number of endpoints to include in each staged set in the Staging Count field and the number of seconds between each set s start-up time in the Staging Interval field. 6. Under Output Format, select one or more types of output for the task to return: Header includes a descriptive header for each record. Return Code includes the task's return code. Standard Output includes the standard output. Standard Error Output includes the standard error output. 7. Under Output Destination, select the Display on Desktop check box to display the task output on the desktop. 8. To save the task output to a file, you can either use the Report to File option in the individual task dialog or the Save to File option here. Tivoli recommends using the Report to File option because it provides defaults, it allows you to specify a list of hosts where you want the output saved, and it records complete task output. See Using the Create a Report File Dialog later in this chapter. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 5

184 Running Tasks To use the Save to File option, do the following: a. Under Output Destination, select the Save to File check box. The Destination for Task Output dialog appears. b. In the On Host field, enter the name of the managed node on which to save the output. The managed node must be a Tivoli client. c. In the Output File field, enter the absolute pathname for the output file. Example: /tmp/mytask.out. d. Click Set & Close to save your choices and return to the Execute Task dialog. 9. Choose the endpoints on which you want to run the task. You can do one of the following: Run the task on specific endpoints by doing the following: a. In the Available Task Endpoints list, select the desired endpoints. b. Click the left arrow button to move the selected endpoints to the Selected Task Endpoints list. OR Run the task on all subscribers of the specified profile managers by doing the following: a. In the Available Task Endpoints list, select the desired profile managers. b. Click the left arrow button to move the selected profile managers to the Selected Profile Managers list. 8 6 Version 1.3

185 Running Tasks 10. Click Execute to display the task argument dialog. The following example shows the EnableDiskCounters dialog. Enter appropriate responses for the arguments. Click Report to File if you want to save task output to a file. See Using the Create a Report File Dialog below for more instructions. Click the Task Description button to display on-line help for the task. The on-line help consists of a text-only version of the reference entry, which includes a description of the arguments for the task. 11. Click Set & Execute. Using Tasks and Jobs 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. Tivoli Manager for Microsoft SQL Server User s Guide 8 7

186 Running Tasks To display the dialog, you click Report to File in a task s task arguments dialog. The following shows the Create a Report File dialog; a description of each field follows. Report to file Tells Tivoli Manager for Microsoft SQL Server 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 ExecuteSQL. 8 8 Version 1.3

187 Running Tasks ${ENDPOINT} is the name of the endpoint the task was run on. ${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. In the following example, which demonstrates how the variables work, the ExecuteSQL task was run on two endpoints called bigdb@corpserv@corpserv and smalldb@branchserv@branchserv. They were saved on corpserv. The following variables were used in the Create a Report File dialog: ${WTEMP}_${TASK} _${ENDPOINT}_${DATE}_${TIME}.rpt. The wtemp command reports the following: c:/tivoli/db/tmp. The Create a Report File dialog creates the following reports: Using Tasks and Jobs 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. Tivoli Manager for Microsoft SQL Server User s Guide 8 9

188 Running Tasks 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; the 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. Running Tasks from the Command Line Use the wruntask command or the wexectask command to run a task. Each task entry in the Reference Guide includes a description of its CLI syntax and a CLI example that uses the wruntask command. For more information on wruntask, see the TME 10 Framework Reference Manual. Using wexectask The wexectask command is unique to this product. It works identically to the wruntask command when running stock tasks. However, it works differently with a customized task. See Customizing Tasks from the Desktop on page 8-14 for more information on creating a customized task. When it is run against a customized task, wexectask retrieves the stored task arguments and uses them as if they were specified on the command line with the a switch. These arguments appear in the tasks argument list before any arguments that are specified on the command 8 10 Version 1.3

189 Running Tasks line with the a switch. Since MSSQLManagerTasks are designed to use named arguments, the arguments that occur later in the command line override arguments that appear earlier in the command line. For example, if the ExecuteSQL_SaveReports task is a customized version of the Execute SQL task with the following stored arguments: ReportToFile=Y ReportFileName=${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.rpt SaveReportFileOn=SpecifiedHost ReportHostName=myrpthost NotifyTEC=Y TECServer=mytecserver TSQL= You could then use the following: wexectask -t ExecuteSQL_SaveReports -l MSSQLManagerTasks -a ReportFileName=authors.rpt -a ReportHostName=joesnode -a TSQL="select * from authors" to cause the task to receive arguments of: ReportToFile=Y ReportFileName=${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.rpt SaveReportFileOn=SpecifiedHost ReportHostName=myrpthost NotifyTEC=Y TECServer=mytecserver TSQL= ReportFileName=authors.rpt ReportHostName=joesnode TSQL="select * from authors" Using Tasks and Jobs The ExecuteSQL_SaveReports uses named arguments and will override an earlier named argument with one specified later on the command line, so it executes as if the arguments were: ReportToFile=Y SaveReportFileOn=SpecifiedHost NotifyTEC=Y TECServer=mytecserver ReportFileName=authors.rpt ReportHostName=joesnode TSQL="select * from authors" Tivoli Manager for Microsoft SQL Server User s Guide 8 11

190 Running Tasks Using ReportToFile from the CLI There are three ways to specify ReportToFile from the command line interface. a ReportToFile=N OR a ReportToFile=Y a ReportFileName=<filename> [ a SaveReportFileOn=MonitoredHost] OR a ReportToFile=Y a ReportFileName=<filename> [ a SaveReportFileOn=SpecifiedHost a ReportHostName=<hostname>] The following briefly describes the arguments for ReportToFile. 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. ReportFileName <filename> tells the task the path to and the name of the file to create as the task output. SaveReportFileOn Use one of the following: MonitoredHost creates the output file on the monitored host the task was run against. SpecifiedHost creates the output file on a specified host. Specify the host with ReportHostName. ReportHostName <hostname> designates the name of the host on which to save the file created when you use the SpecifiedHost argument Version 1.3

191 Running Tasks Using NotifyTEC from the CLI There are two ways to specify the NotifyTEC task from the command line interface. a NotifyTEC=N a NotifyTEC=Y a TECServer=<servername> The following briefly describes the arguments for NotifyTEC. NotifyTEC TECServer Getting Help on Tasks 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. Note: If NotifyTEC=Y and you do not specify TECServer=<servername>, no message is sent. <servername> the name of the TEC server to send the message to. You can use the Task Description button in the task argument dialog to display a text-only version of the reference entry for a task. Using Tasks and Jobs Getting Help on Tasks from the Command Line To get help on a task from the command line, use the wgettaskhelp command, which is unique to this product. It displays the same help that you get using the Task Description button on the task argument dialogs. The syntax is as follows: wgettaskhelp <task_name> <library_name> For example, to display the help text for the Execute SQL task, type the following at the command line: wgettaskhelp ExecuteSQL MSSQLManagerTasks Troubleshooting Tasks When a task creates temporary files, Tivoli Manager for Microsoft SQL Server creates the files in its temporary directory on the managed Tivoli Manager for Microsoft SQL Server User s Guide 8 13

192 Customizing Tasks from the Desktop node on which the task was run. If a task fails and you cannot determine the cause, examine the files in this directory. The time stamp on the files or directories shows the last time the task was run. Use the wtemp to find the location of the temporary directory. Customizing Tasks from the Desktop A customized task is a standard task with defined arguments, such as the tables and indexes you want examined or whether you want the results sent to a file. Each customized task has its own unique task name and values. Since a customized task already has defined arguments, Tivoli does not display the argument dialogs when you run the task from the desktop. If you run a customized task from the command line, you must still specify the task arguments. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Customize and save a copy of a task Task library admin You can perform this procedure from the Tivoli desktop only Version 1.3

193 Customizing Tasks from the Desktop 1. Display the Task Library: MSSQLManagerTasks window as follows: a. On the TME Desktop, double-click the MSSQLManager policy region icon. b. Double-click the MSSQLManagerTasks icon. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 15

194 Customizing Tasks from the Desktop 2. Double-click on the task icon that you want to customize to display the Execute Task dialog. 3. Specify the endpoints where you want the task to run. Select one or more endpoints from the Available Task Endpoints list, then click the left arrow button to move them to the Selected Tasks Endpoint list Version 1.3

195 Customizing Tasks from the Desktop 4. Click the Execute button to display the appropriate task argument dialog. The task argument dialog for the ExecuteSQL task is shown in this example. Enter arguments as appropriate. In the example above, the single argument consists of a TSQL statement. Click Report to File if you want to save task output to a file. See Using the Create a Report File Dialog below for more instructions. Click the Task Description button to display online help for the task. The online help consists of a text-only version of the reference entry, which includes a description of the arguments for the task. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 17

196 Customizing Tasks from the Desktop 5. Click the Save button to display the Save Argument dialog. 6. To define the customized task, enter the following information: Name: Enter a descriptive name for the task to help distinguish it from other tasks on the desktop. Example: Show number of Authors in the PUBS table. Identifier: Enter an identifier for the task. A randomized identifier appears initially (in this example, ExecuteSQL_aaa). An identifier has two parts. The first part must be the standard task identifier (in this example, ExecuteSQL). The second part should be descriptive information that makes sense to you. Example: If you specify an identifier for the customized task that does not include the standard task name and still want to enable filtering, you can edit the tl_def_man_nodes policy method in the MSSQLTasks policy object. See the Tivoli Framework Reference Manual for more information. Description: type a brief description of what the customized task does. This description becomes the online help for the task. When you click the Task Description button in the task argument dialog for this customized task, it displays the description 8 18 Version 1.3

197 Customizing Tasks from the Desktop that you enter at the Description field. For example, you might enter This task is a customized version of ExecuteSQL that displays the record count of the AUTHORS table in the PUBS database. We use this task to.... Show by Identifier: Optional tool: Select the check box to change the library contents list to use the task identifier instead of the task name. Parent Description: Optional tool: Click this button to show the help text from the task from which you are creating a customized task. You can display this dialog only while you are in the Save Argument dialog. 7. Click Save & Close to return to the task argument dialog. 8. Click Cancel in the task argument dialog. 9. Click Close button to return to the task library window. 10. Select the Refresh option from the View menu in the Task Library window to display the new customized task. Using Tasks and Jobs You can now run the task by following the procedure in Running Tasks on page 8-3. When you run a customized task, the task argument dialog is not displayed the task runs with the arguments you specified. Tivoli Manager for Microsoft SQL Server User s Guide 8 19

198 Creating Jobs Recreating the Task Library Creating Jobs If a Tivoli Manager for Microsoft SQL Server task is edited or deleted from the task library, you cannot recreate it with the wgettask or wcrttask commands. If you must recreate the task library, do the following: 1. On the TMR server, change to the following directory: tivoli_install_directory>/bin/generic/mssqltasks 2. Enter the following command to recreate all the tasks in the MSSQLManagerTasks library and remove any custom tasks and jobs: sh x Install.sh When you create a job, you create a resource that consists of a task and its configured execution parameters, such as the managed resources on which you want to run the job. You create jobs so you can use the Scheduler resource to run the task at predetermined times. This section provides the procedures for creating a job and defining its execution parameters. You can create a job from the following: The standard set of tasks for Microsoft SQL Server. Individual tasks are described in Chapter 2, The MSSQLManagerTasks Library, in the Tivoli Manager for Microsoft SQL Server Reference Guide. Customized tasks. The following table provides the context and authorization role required for this procedure: Activity Context Required Role Create a job Task library admin 8 20 Version 1.3

199 Creating Jobs You can perform this procedure from either the Tivoli desktop or the command line. Creating Jobs from the Desktop Use the following steps to create a job: 1. Display the Task Library: MSSQLManagerTasks window. a. On the TME Desktop, double-click the MSSQLManager policy region icon. b. Double-click the MSSQLManagerTasks icon. 2. Choose Create >Job. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 21

200 Creating Jobs Tivoli displays the Create Job dialog. 3. Type a descriptive job name in the Job Name field. The job label can include letters, numbers, underscores, dashes, periods, and blanks. If you do not specify a label, the task name is used. 4. Select the task on which the job is based from the Task Name list Version 1.3

201 Creating Jobs 5. Under Execution Mode, select one of the following: Parallel runs the task on all targets in parallel. Serial runs the task on all targets, one at a time, in alphabetical order. Staged runs the task in a staged fashion on sets of managed nodes. When you select this option, the Staging Count and Staging Interval fields under Execution Parameters become available; you must enter the appropriate values at step 7. The task is executed on the endpoints in alphabetical order. 6. In the Timeout field, type the timeout value for the task. This value specifies the number of seconds Tivoli waits for the task or job to complete before it issues an error. The default is 60 (seconds). If the task takes longer to complete than the specified Timeout and is running in Serial or Staged mode, Tivoli moves on to other endpoints after this time expires. The task continues to execute on the endpoint, even though Tivoli has stopped waiting for it to end. 7. If you selected Staged in step 5, specify the number of endpoints to include in each staged set in the Staging Count field and the number of seconds between each set s start-up time in the Staging Interval field. 8. Under Output Format, choose the type of output you want the task to return by selecting one or more of the following check boxes : Header includes a descriptive header for each record. Return Code includes the task s return code. Standard Output includes the standard output. Standard Error Output includes the standard error output. 9. Under Output Destination, select the Display on Desktop check box to display the task output on the desktop. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 23

202 Creating Jobs 10. (Optional) Save the task output to a file. a. Under Output Destination, select the Save to File check box to display the Destination for Task Output dialog. b. In the On Host field, enter the name of the managed node on which to save the output. The managed node must be a Tivoli client. c. In the Output File field, enter the absolute pathname for the output file. Example: /tmp/mytask.out. d. Click Set & Close to save your choices and return to the Execute Task dialog. 11. Choose the endpoints on which you want to run the task. You can do one of the following: Run the task on specific endpoints. a. From the Available Task Endpoints list, select the desired endpoints. b. Click the left arrow button to move the selected endpoints to the Selected Task Endpoints list. OR Run the task on all subscribers of the specified profile managers. a. From the Available Profile Managers list, select the desired profile managers. b. Click the left arrow button to move the selected profile managers to the Selected Profile Managers list Version 1.3

203 Running and Scheduling Jobs 12. Click Create & Close to create the job and return to the Task Library window. The new job appears in the list. The window below shows a new job, ExecuteSQLAuthors Record Count. Creating Jobs from the Command Line Use the wcrtjob command to create jobs from the command line. For more information about this command, see the TME 10 Framework Reference Manual. Using Tasks and Jobs Running and Scheduling Jobs Before you can run a job, you must create it, as described in Creating Jobs on page Depending on how the job was created, it may ask for input when you run it: If you created the job from an uncustomized task, the appropriate task argument dialog appears to prompt you for any required input. If you created the job from a customized task, the job runs without prompting for further input. All required information was entered when the customized task was created. Tivoli Manager for Microsoft SQL Server User s Guide 8 25

204 Running and Scheduling Jobs The following table provides the context and authorization role required for this procedure: Activity Context Required Role Run a job Task library mssqlserver_dba You can perform this procedure from either the Tivoli desktop or the command line. Running Jobs from the Desktop Use the following steps to run the job. 1. Display the Task Library: MSSQLManagerTasks window: a. On the TME Desktop, double-click the MSSQLManager policy region icon. b. Double-click the MSSQLManagerTasks icon. 2. Double-click the icon for the job you want to run. If the job was created from a customized task, it begins executing. OR If the job was created from a standard task, you are prompted for input. Enter the values in the task dialog. The job is run. It displays the output on the Tivoli desktop or sends it to a file as you specified. Running Jobs from the Command Line Use the wrunjob command to run jobs from the command line. For more information about this command, see the TME 10 Framework Reference Manual Version 1.3

205 Scheduling Jobs Running and Scheduling Jobs Tivoli Manager for Microsoft SQL Server uses the Scheduler to schedule tasks. To schedule a job, you must first create it (see Creating Jobs on page 8-20), then schedule it with the Add Scheduled Job dialog. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 27

206 Running and Scheduling Jobs The following table provides the context and authorization role required for this procedure. Activity Context Required Role Schedule a job Task library mssqlserver_dba You can perform this procedure from either the Tivoli desktop or the command line. Scheduling Jobs from the Desktop Follow these steps to schedule a job: 1. Display the Task Library: MSSQLManagerTasks window. a. On the TME Desktop, double-click the MSSQLManager policy region icon. b. Double-click the MSSQLManagerTasks icon. 2. Drag the job icon that you want to schedule onto the Scheduler icon. 3. Do one of the following If the task does not require any arguments, the Add Scheduled Job dialog appears. Go to step 5 on page OR If the task requires that certain arguments be specified, a task argument dialog appears. Go to step If a task argument dialog is displayed, enter arguments as appropriate, then click Set & Execute. In the example above, the single argument consists of a TSQL statement. You can also do the following: Click Report to File if you want to save task output to a file. See Using the Create a Report File Dialog above for more instructions. Click the Task Description button to display online help for the task. The online help consists of a text-only version of the 8 28 Version 1.3

207 Running and Scheduling Jobs reference entry, which includes a description of the arguments for the task. When you click the Set & Execute, the Add Scheduled Job dialog appears. 5. In the Job Label field of the Add Scheduled Job dialog, type a label for the job icon. The label identifies the icon on the desktop. The job label can include letters, numbers, underscores, dashes, periods, and blanks. If you do not specify a label, the task name is used. 6. In the Schedule Job For area, do the following: a. Enter the date in the Month, Day, and Year fields. b. Enter the time using the Hour and Minute lists and the AM and PM buttons. 7. Specify whether or not you want the job to repeat. If you want the job to run only one time, go to the next step. OR If you want to repeat the job, specify the repeat options in the Repeat The Job area. a. Choose one of the following repeat options: Select the Repeat the job indefinitely check box to repeat the job indefinitely. OR Select the Repeat the job check box to repeat the job a finite number of times. Type the number of times you want the job to run. b. Specify the interval between start times for the job at the The job should start every field. 8. Under When Job Complete, select one or more of the following check boxes to specify what you want to happen when the job completes. Post Tivoli Notice sends a notice to a group that you specify. Press the Available Groups button to display the Available Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 29

208 Running and Scheduling Jobs Groups dialog. Choose a group from the list of notice groups. Post Status Dialog on Desktop displays a status message on the desktop. Type the message you want displayed in the field next to the check box. Send to sends an message to a specified user when the job completes. Type the address in the field next to the check box. Log to File writes the status to a file when the job completes. You can specify the file either with the Host and File fields or by pressing the File Browser button and selecting a file. 9. Set any retry, cancel, or restriction options for the job. a. Click the Set Retry/Cancel/Restriction Options button to display Set Retry/Cancel Restrictions Options dialog. b. Optional: Select the Cancel job check box and specify an amount of time to wait before cancelling a job. c. Select one of the retry options Version 1.3

209 Running and Scheduling Jobs - Retry the job until success continues to retry the job until it runs successfully. - Retry the job retries to run the job a specified number of times. Type the number of times that you want in the field. - The job should retry every fields designates how often you want to retry to run the job. d. (Optional) Specify the available run times by selecting the appropriate check boxes in the Restrictions area and filling in the appropriate fields. The run times specify the times during the week that the job can run. e. Press the Set button to set the options and return to the Add Scheduled Job dialog. 10. Press the Schedule Job & Close button to schedule the job and return to the Tivoli desktop. Scheduling Jobs from the Command Line Use the wschedjob command to schedule a job that exists in a Tivoli Manager for Microsoft SQL Server task library from the command line. You can schedule only jobs that exist in a task library from the command line. Using Tasks and Jobs Tivoli Manager for Microsoft SQL Server User s Guide 8 31

210 Running and Scheduling Jobs 8 32 Version 1.3

211 9 9Optimizing Microsoft SQL Server Performance This chapter presents key performance issues and describes how you can use Tivoli NT monitors and Tivoli Manager for Microsoft SQL Server monitors to identify performance bottlenecks. It explains the purpose behind monitoring particular aspects of Windows NT and the database. Database servers are closely tied to Windows NT, so it is impossible to analyze their performance without reference to underlying operating system activity. This chapter covers the following topics: A summary of optimization questions A list of optimization questions, including recommendations on how the monitors to use to get answers to the questions Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 1

212 Optimization Summary Optimization Summary To optimize your monitors, Tivoli recommends the following: Establish a control range of values to use for setting monitor thresholds. Run the monitors for a period of days and store the values to file. Analyze the data, using the following table of questions. Analysis of many of these monitors is qualitative and site-specific. Often the text refers to values being consistently high, which means that a monitor returns values consistently towards or above the upper limit of the previously determined control range. Optimization Questions For Additional Information See Is the CPU causing the bottleneck? page 9-4 Are other processes causing the CPU bottleneck? page 9-4 Is the CPU overloaded with network interrupt requests? page 9-4 Is memory causing the bottleneck? page 9-5 Is the Data Cache sized appropriately? page 9-6 Is the procedure cache sized correctly? page 9-8 Is it possible to allocate more memory to the database server? page 9-9 Is the hard disk I/O causing a bottleneck? page 9-9 Is the Microsoft SQL Server s throughput restricted by transaction log I/O? page 9-10 Is Read Ahead effective? page 9-11 Is the database server using the disk subsystem at optimum capacity? page Version 1.3

213 Optimization Summary Optimization Questions For Additional Information See Is the Lazywriter running efficiently? page 9-12 Is the database server s network throughput affected by other processes network traffic? Is the database server placing too high a load on the network? page 9-12 page 9-13 Do I have a high number of blocks occurring? page 9-14 Is the database server experiencing a large number of deadlocks? page 9-14 Is the database server detecting critical errors? page 9-14 Is the transaction log space full? page 9-15 Is a database data space full? page 9-15 Is there a rogue transaction? page 9-15 Is replication synchronizing the subscribing databases within the prescribed period? page 9-16 Is fragmentation causing data reads to be inefficient? page 9-17 Are my query plans based on statistics that are out of date? Is my Windows NT event log keeping the minimum history of information I require? Are the number of locks for the server correctly configured and are they being used efficiently? page 9-17 page 9-17 page 9-18 Optimizing Microsoft SQL Server Performance Are the necessary services running? page 9-18 Tivoli Manager for Microsoft SQL Server User s Guide 9 3

214 Optimization Questions Optimization Questions The remainder of this chapter consists of questions and answers that help optimize Microsoft SQL Server. Is the CPU causing the bottleneck? High values from the NT_System: Percent Total Processor Time and the NT_System: Processor Queue Length monitors indicate that the CPU may not be fast enough for the normal workload. Consider moving to a faster CPU to improve performance, unless you can determine that factors described in Are other processes causing the CPU bottleneck? on page 9-4 are causing the bottleneck. Are other processes causing the CPU bottleneck? If the CPU appears to be the bottleneck, use the following monitors to identify whether the database server processes or other processes are the cause: NT_Process: Percent Processor Time (Use SQLServer as the Process argument) NT_System: Percent Total Processor Time If the value returned by NT_System: Percent Total Processor Time is high but the value of NT_Process: Percent Processor Time is low, the CPU bottleneck may be caused by a process other than the database server s. Run Percent Total Processor Time against each process to identify the application causing the problem. If other processes appear to be dominating CPU time, you may want to move Microsoft SQL Server to its own or to a less utilized machine. Is the CPU overloaded with network interrupt requests? Because the Microsoft SQL Server client-server architecture is network intensive, make sure that the CPU is not overloaded with interrupt handling. Many older network cards and drivers can cause this by deferring most of the interrupt handling to the main CPU. 9 4 Version 1.3

215 Optimization Questions If the following monitors are consistently high, Tivoli recommends a more efficient, up-to-date network card and driver. NT_System: Percent Total Interrupt Time NT_System: Percent Total DPC Time NT_System: Total Interrupts/sec Is memory causing the bottleneck? The databse server locks off the portion of memory allocated to it. If the remaining memory is not enough for the non-microsoft SQL Server processes, Windows NT will page fault excessively. It is best to run the database server on a dedicated Windows NT machine. In addition, if you are running Version 7.0, you should use its dynamic memory allocation capability. However, if you are running other critical processes (or simply wish to control memory usage) you can use min server memory and max server memory server configuration options to put limits on the buffer cache. If you are using those server configuration options, then Scenario 1 below may apply to you. If the NT_Memory: Page Faults/sec monitor is consistently high, this indicates excessive page faulting. You must determine which of the following scenarios is causing the problem: Scenario 1 There is enough memory on the machine, but the database server has been allocated more than it needs. The rest of the system is starved of memory, causing other processes to page. Check the NT_Process: Working Set monitor. (Use SQLServer as the Process argument.) If this value is considerably less than the Microsoft SQL Server s configured memory during high database server workload periods, the database server probably has been allocated more of the machine s memory than it needs. Re-allocate memory so that the database server has less than before. This should leave enough memory for the other processes on the machine to function without excessive paging. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 5

216 Optimization Questions Scenario 2 You may need to experiment with the precise amount of memory to allocate to the Microsoft SQL Server. Initially, try to allocate 25% more memory than the NT_Process: Working Set observed during high workload. There is not enough memory on the machine for the current workload. Check the NT_Memory: Pages/sec monitor. If the average of this value is greater than 0 and it increases and decreases approximately in proportion to the load on the database server, then it is causing the page faulting. Increase the amount of memory allocated to the database server (bearing in mind Scenario 1). You may also need to add memory to the machine as well as increase the memory allocated to the database server. Is the Data Cache sized appropriately? In general terms, maximizing the data cache is good. There are several ways to determine if the data cache is large enough. If you are running Microsoft SQL Server Version 6.5: use the MSSQLServer: I/O single page write rate monitor. If it consistently returns high values, it means your system is regularly running out of free buffers in the data cache. Increase the size of the data cache. You can configure the Lazywriter to maintain a minimum amount of free buffers. If this monitor returns a value greater than 0, then the Lazywriter is having trouble maintaining the minimum number of free buffers and causes single page writes. This can be a sign of an overloaded cache. See Is the hard disk I/O causing a bottleneck? on page 9-9, to determine if disk I/O is affecting the Lazywriter s ability to clear buffers efficiently. If you are running Microsoft SQL Server Version 7.0: the Lazywriter is not configurable in this version. Use the MSSQLServer: Cache Number of Free Buffers monitor. If 9 6 Version 1.3

217 Optimization Questions the value is consistently low (taking dynamic memory allocation into account), it can indicate excessive single-page writes. The Lazywriter could also be working hard to maintain the free buffer pool. Increase the size of the data cache. Use the MSSQLServer: Cache hit ratio monitor, which indicates the percentage of pages read from the data cache versus those read from the hard disk. Reading from the data cache is much faster than reading from disk. The cache, however, uses a Most Recently Used/Least Recently Used algorithm, which means that older pages are dropped from the cache as new pages are required. As the amount of memory allocated to the data cache increases, the number of times the database server must perform an expensive physical I/O to retrieve a page decreases. The values returned by Cache Hit Ratio vary, depending on how large the cache is and (more importantly) how many frequently used pages there are in your database. If an application has a very small subset of data that is constantly in use, the Cache Hit Ratio value probably will be consistently high even with a small data cache. You should try to achieve a Cache Hit Ratio value that is as close to 100% as possible. You can do this by increasing the amount of memory allocated to the database server so that the memory left for data cache is as large as possible. A high value for Cache Hit Ratio alone is not an indication that your system is performing efficient reads from the data cache. The Read Ahead Manager may be pre-emptively reading the required pages into the cache directly before the page is required. This means that as far as Cache Hit Ratio is concerned, the page was found in memory. However, in real terms the Read Ahead Manager must have performed a physical I/O for that to happen. See Is Read Ahead effective? on page Note: Following a database server start-up, values from the Cache Hit Ratio monitor are not representative since the cache is initially empty. The cache fills over time as each user begins to make use of pages in the database. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 7

218 Optimization Questions You also may have allocated too much memory to the procedure cache. See Is the procedure cache sized correctly? on page 9-8. Is the procedure cache sized correctly? The database server procedure cache is sized by default to use 30% of available memory once all other resources (such as objects and databases) receive their allocation. The size of the procedure cache can be configured manually in Microsoft SQL Server Version 6.5. In Version 7.0 it is maintained automatically and cannot be configured manually. The optimum size of the procedure cache is determined by the following factors: The use that all applications make of stored procedures The number of users that are likely to need their own copies of these procedures You can estimate the optimum size of the procedure cache in bytes based upon the total size of all stored procedures and the number of users. The optimal size will change as the following factors change: Number of users Total memory allocated to the database server The number and size of stored procedures Use MSSQLServer: Procedure cache used to monitor the cache size. If this monitor consistently returns a value in the range of 90 to 95%, then the procedure cache size is optimum. If the monitor consistently returns a value below 90%, the cache may be too large. Consider reducing the percentage of memory allocated to the procedure cache. If the value is consistently above 95%, the procedure cache is too small. Either increase the total memory available to the database server, thereby automatically increasing the amount of memory allocated to the procedure cache, or increase the percentage of available memory allocated to the procedure cache. 9 8 Version 1.3

219 Optimization Questions Note: Following a database server start-up, the values from this monitor are not representative since the cache is initially empty. The cache fills over time as each user begins to make use of the available procedures. Is it possible to allocate more memory to the database server? For Microsoft SQL Server Version 7.0, use dynamic memory allocation if possible. Microsoft SQL Server then automatically concedes memory to Windows NT if the free buffer pool drops below 5 MB. It also automatically allocates more memory if it needs it. For Microsoft SQL Server Version 6.5 (or Version 7.0 if you are using manual memory limits): use NT_Memory: Available Bytes to monitor for excess memory available. Microsoft recommends maintaining a pool of 5 MB of unallocated memory for Windows NT. Consider allocating any available memory in excess of 5 MB to the database server. If available memory drops below 5 MB, Windows NT will reclaim space from the working sets of other processes. This degrades overall machine performance. If you are running processes other than Microsoft SQL Server and Windows NT on the machine, consider moving them to another machine. Is the hard disk I/O causing a bottleneck? If the monitor NT_Physical_Disk: Percent Disk Time is consistently high, the machine s hard disk may be causing a bottleneck. 1. Determine whether the disk activity is caused by paging. See Is memory causing the bottleneck? on page Based on your findings, do one of the following: If disk activity is caused by paging, fixing the memory problem that caused the paging should help cure the high disk usage. OR If the system is not paging excessively, go to step 3. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 9

220 Optimization Questions 3. If the system is not paging excessively, investigate other ways of reducing the physical I/O. If MSSQLServer: I/O outstanding reads and MSSQLServer: I/O outstanding writes are consistently greater then zero, this indicates that physical disk I/O is the primary bottleneck. The most effective ways of reducing physical I/O are the following: Increase the size of the data cache. Revisit the application design. Look at how efficiently it accesses data and whether it uses efficient mechanisms, such as software data-caching to avoid rereading data more than necessary. Change to a faster disk or a disk array to improve I/O throughput. Make sure that your queries are efficient so that applications are reading only the data they need. Use MSSQLServer: I/O page read rate to monitor the amount of physical I/O occurring due to the database server. Is the Microsoft SQL Server s throughput restricted by transaction log I/O? Because all changes must be physically logged to disk before a transaction can be considered complete, the disk drive storing the log can limit the overall throughput. If MSSQLServer: I/O log write rate reaches the maximum sequential write capability of the disk drive, the system will be restricted by this limit. The maximum is 60 to 70 sequential writes per second for a typical 12 to 15 millisecond seek time disk drive; more for disk arrays. Consider placing the log on a striped disk set to increase the I/O capacity. For best performance, the log device should be placed on a disk or logical disk capable of optimal write performance. Place the TRANSACTION LOG on a different device than the data to stop access conflicts Version 1.3

221 Optimization Questions Is Read Ahead effective? Depending upon specific system usage, Read Ahead may not actually assist processing. Use the following information to evaluate whether or not Read Ahead is effective: If Read Ahead is effective, the value from MSSQLServer: RA pages fetched into cache rate is high and the value returned by MSSQLServer: RA pages found in cache rate is low. This means that the Read Ahead Manager is correctly identifying and loading pages into the cache and that the pages have not otherwise been loaded into cache already. If Read Ahead is not effective, the value from MSSQLServer: RA pages fetched into cache rate is low and the value from MSSQLServer: RA pages found in cache rate is high. This means that the Read Ahead Manager is attempting to pull pages into the cache that are already there. If Read Ahead is not effective, turn it off by setting the RA worker threads configuration option to zero. The RA Effectiveness monitor returns a value of 100% when the number of pages read into cache (by the Read Ahead Manager) are the same as found in cache (by the Read Ahead Manager). Any value below 100% means that Read Ahead is not effective. Is the database server using the disk subsystem at optimum capacity? The configuration options max async IO and max lazywrite IO control the maximum number of asynchronous I/Os that database server can request of the disk subsystem. In Microsoft SQL Server Version 7.0, max async IO is available as a configuration option but max lazywrite IO is not. Both are available in Version 6.5. If the NT_Physical_Disk: Disk Queue Length monitor is consistently less than the value for max async IO, the disk subsystem has enough capacity to handle the I/O from the database server and can handle more. You may want to increase max async IO and max lazywrite IO to increase throughput. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 11

222 Optimization Questions If the monitor is consistently greater than the value for max async IO, the disk-subsystem is being overloaded. Reduce the values for max async IO and max lazywrite IO. Is the Lazywriter running efficiently? Note: The Lazywriter is configured automatically in Microsoft SQL Server Version 7.0. The following analysis is recommended for Version 6.5 only. For Version 7.0, you can address Lazywriter performance indirectly: make sure system I/O is functioning properly and that the system is not starving for memory. The Lazywriter ensures that there are always enough free buffers in the data cache. The Lazywriter should run continuously. Use the Cache Configured Free Buffers Percent Used monitor to check it. This monitor should return a value of 100% or higher when the Lazywriter does its job. If the value is less than 100%, then Lazywriter may not be able to maintain the free buffers because either the cache is overloaded, or it is impeded from clearing buffers efficiently by disk I/O restrictions. See Is the Data Cache sized appropriately? on page 9-6 for more information. If the value MSSQLServer: Cache number of free buffers falls below the configuration option free buffers, you can improve Lazywrite throughput by increasing the server configuration option max lazywrite IO. However, whether or not you should make such an increase is dependent on individual I/O setup/capacity. Is the database server s network throughput affected by other processes network traffic? Network hardware performance is a potential bottleneck for Microsoft SQL Server in a client server architecture. The most significant improvement to network performance you can make is to reduce non-microsoft SQL Server network traffic to a minimum. This allows the Microsoft SQL Server to make full use of available bandwidth. Use the following monitors to identify significant network traffic caused by non-microsoft SQL Server processes: 9 12 Version 1.3

223 Optimization Questions MSSQLServer: Network read rate is substantially lower than NT_Server: Bytes Received/sec MSSQLServer: Network write rate is substantially lower than NT_Server: Bytes Transmitted/sec One example of this bottleneck is a machine operating as a Primary Domain Controller (PDC) that is also running the database server. The administrative functions that a PDC invokes will increase network traffic, which reduces the bandwidth available to the Microsoft SQL Server. The general rule is not to run a database server on a PDC unless performance degradation is acceptable. Is the database server placing too high a load on the network? Assuming that the database server is the main user of the network adapter, there are several factors which may cause less efficient use of that adapter. The factors are as follows: If MSSQLServer: Network read rate and/or MSSQLServer: Network write rate are consistently high, this indicates a large amount of network traffic. If MSSQLServer: User connections is also high, the problem may be that there is too much workload for the network adapter to handle. You can do the following to correct this problem: Reduce the maximum number of allowable user connections with the user connections configuration option. Restructure the applications and databases to employ a more distributed architecture. This reduces the workload on a particular machine. If the number of user connections is acceptable but NT_ServerWorkQueues: Queue Length is high (greater than 4), it is possible that the network hardware is functioning acceptably but the database server is not making efficient use of it. It could indicate congestion at the processor. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 13

224 Optimization Questions One possible remedy is to increase the worker threads available to process network requests. You can increase the max worker threads configuration option to increase the number of available worker threads. Do I have a high number of blocks occurring? Application design and usage may cause users to block each other from accessing resources. Blocks are normal and cannot be completely eradicated; however a consistently high number of blocked processes, as indicated by the monitor MSSQLServer: Number of blocked processes, could indicate a rogue transaction, bad application design, or severe performance issues. Is the database server experiencing a large number of deadlocks? Deadlocks are a normal occurrence in a shared resource system, because they cannot always be completely eradicated. Your goal should be to minimize their occurrence. Use MSSQLServer: Number of deadlocks to determine if any system is detecting high numbers of deadlocks. To reduce the number of deadlocks, you must review the application design to determine the source of each of the detected deadlocks. Review especially the access order of requests and the application s ability to resubmit a request when it recovers from a deadlock. To reduce the number of deadlocks, an application can be written to access tables in a fixed order and to resubmit a statement a number of times before indicating failure. Is the database server detecting critical errors? The database server writes errors to the NT Event Log. Use MSSQLServer: NT Application Log to monitor the number of fatal errors (severity level 19+). You should investigate and act upon critical errors immediately, depending on their level of severity Version 1.3

225 Is the transaction log space full? Optimization Questions Each database has its own transaction log that is allocated finite disk space. The MSSQLDatabase: Log Space Percent Used (Database) and MSSQLServer: Log Space Percent Used (Server) monitors reports the percentage of allocated space used. To maximize this disk space, do the following: Dump the transaction log to a backup device on a regularly scheduled basis to recover space. If usage is exceptionally high, regularly scheduled dumps may not be frequent enough to prevent the transaction log from filling up. If the monitor MSSQLDatabase: Log Space Percent Used (Database) reports that the log is becoming full, execute an interim dump. You can set up automatic interim dumps by setting up the Dump Transaction Log task as a response action for this monitor Is a database data space full? The database server allocates finite space to each database s data. The MSSQLServer: Data Space Percent Used (Server) and MSSQLDatabase: Data Space Percent Used (Database) monitors report the percentage of data space used and may indicate when the database needs to be resized. The percentage that you choose is based on usage. You should set a threshold that allows you enough time to fix the problem before it becomes critical. Is there a rogue transaction? A rogue transaction is one that runs too long or one that never commits. Its locks prevent other processes from accessing the resources it ties up for too long a time. An unnecessarily old transaction can prevent the transaction log from being fully cleared. A dump of the transaction log only clears the log up to the oldest open transaction. The MSSQLServer: Oldest Open Transaction (Server) and MSSQLServer: Oldest Open Transaction (Database) monitors return the age of the oldest transaction in minutes. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 15

226 Optimization Questions A strategic response to this situation is to determine the maximum data loss window that is tolerable for the application. A data loss window is the period of time during which all transactions are lost in the event of server or other failure. For example, if you back up the database nightly and back up the transaction log every 15 minutes, your data loss window is 15 minutes. Should the server fail, the maximum data loss is the last 15 minutes worth of transactions. To preserve the integrity of the data loss window in this case, you should monitor for transactions that take longer than 15 minutes to complete. Another alternative is to write a timer into the application that rolls back a transaction and retries if a transaction takes too long to complete. Is replication synchronizing the subscribing databases within the prescribed period? There are several monitors that check the flow of replication transactions from the distributor to the subscriber. These are the MSSQLServer: Delivered Latency, Delivered Transaction Rate, Delivered Transactions, and Undelivered Transactions monitors. In addition, there are several monitors that check the flow of replication transactions from the publisher to the distributor. These are the MSSQLDatabase Replicated Transactions, Replicated Transaction Rate, and Replication Latency monitors. If delays are reported, you can do the following: Check the network between the publication database and distribution database, if they are on different servers. (Use the MSSQLServer: Network Read Rate and Network Write Rate monitors.) Check the workload on one or both servers to determine if it is overloaded. (Use the MSSQLServer: CPU Percent Busy monitor.) Determine if the distribution database is unavailable. (Use the MSSQLDatabase: Database Status (Database) monitor.) 9 16 Version 1.3

227 Optimization Questions Is fragmentation causing data reads to be inefficient? The MSSQLDatabase: Fragmentation monitor reports the degree of fragmentation for a specified index or table. Use this monitor to determine when fragmentation reaches a level that causes performance degradation. Performance degradation is due to non-contiguous table reads that require additional extent switches. Are my query plans based on statistics that are out of date? The MSSQLDatabase: Optimizer Statistics Age monitor reports the time (in minutes) since statistics were updated for the specified index. Use this monitor to ensure that queries are basing their query plans on up-to-date information. If query plans are based on old information, they may be inefficient. The efficiency of query plans is integral to overall server performance. The repercussions of query plans based on out-of-date statistics show up as problems elsewhere in the system, such as queries doing unnecessary reads, the incorrect use of indexes, and blocking locks. Is my Windows NT event log keeping the minimum history of information I require? Applications, audit trails, or error checking may rely on being able to view events on the server through the Windows NT event log. This log has a finite size and may fill up, unless it is configured to be circular. If the log fills up, no more events can be written to it. If the log is circular, events can be overwritten. To ensure that the Windows NT event log holds an audit trail for a minimum period of time, you can run the MSSQLServer: NT Application Log Age monitor. To check if the Windows NT event log is filling up, you can run the MSSQLServer: NT Application Log Percent Full monitor. The NT Application Log monitor searches the Application section of the event log for Microsoft SQL Server errors. It can return the number of entries matching any combination of the following criteria: Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 17

228 Optimization Questions Error Number Error Severity Error Text (matching string) Are the number of locks for the server correctly configured and are they being used efficiently? In Microsoft SQL Server Version 7.0, you can enable dynamic lock allocation. The following analysis is recommended for use with Version 6.5 and with fixed lock allocation in Version 7.0. If the maximum number of locks configured for the server (using the locks configuration option) is too low, then performance degrades as commands wait for locks to be freed before proceeding. If the maximum number of locks configured is too high, the excess locks waste valuable memory resources. Use the MSSQLServer: Total Locks Percent Used monitor to track the maximum number of locks used during peak periods. If the maximum number of locks is consistently at 100%, increase the amount of locks. If the maximum number of locks is consistently below 75%, for example, you can decrease the number of locks by one quarter. Note: The monitor returns 0 when dynamic lock allocation is in effect (Microsoft SQL Server Version 7.0 only) In addition to the number of locks used, the type of locks being taken out is also important. You can decrease the number of locks used by upgrading a number of page locks to a single table lock. Use the LE threshold maximum and LE threshold percent server configuration options to manage lock escalation. The threshold must take into account that once a table lock is taken out, it affects any user wanting to access pages that may not be in use. Note: The LE threshold maximum and LE threshold percent server configuration options are available only in Microsoft SQL Server Version 6.5. Are the necessary services running? The MSSQLServer: ServiceState monitor reports the state of the following services: MSSQLServer, MSDTC, and SQLExecutive 9 18 Version 1.3

229 Optimization Questions (renamed SQLServerAgent in Version 7.0). The MSSQLServer service may have three states: stopped, paused, started. The other two services have two states: stopped and started. Use this monitor to ensure server availability and that the replication process and scheduled SQL tasks are running. This monitor does not need a connection; it reports accurately even if no connection can be established to the SQL server. The monitor only returns one TRUE or FALSE value that relates to the state of all specified services. To check that a particular service is started, enter Yes for that service option. The monitor does not check the service state if you enter No. The MSSQLServer service must be running for any operations to be carried out on the server or its databases. The server may have stopped due to a user request or an internal error. It may also have stopped if the NT computer was rebooted and the service is not automatically set to restart at boot time. This monitor helps identify the problem by alerting the DBA. You also can configure an automatic response to try to start the service again. This reduces the amount of time the server is unavailable to users and applications. If the server is paused, then it cannot accept new logons, which causes an availability issue. SQLExecutive (SQLServerAgent in Version 7.0) must be running for SQL scheduled tasks and replication to operate. This monitor helps to identify a replication bottleneck quickly and to avoid a backlog of replicated transactions or an unacceptable delay in subscribers getting published information. It also alerts you when scheduled tasks are unable to run. MSDTC must be running in order for distributed transactions to be coordinated correctly. Optimizing Microsoft SQL Server Performance Tivoli Manager for Microsoft SQL Server User s Guide 9 19

230 Optimization Questions 9 20 Version 1.3

231 10 10Installing and Using GEM Instrumentation Installing and Using GEM Instrumentation This chapter describes how to install Tivoli Global Enterprise Manager (GEM) instrumentation and use Tivoli GEM to monitor and control Microsoft SQL Server resources (servers and databases). This chapter includes the following topics: Overview of Tivoli GEM Instrumentation Installing GEM Instrumentation for Tivoli Manager for Microsoft SQL Server Setting up GEM Instrumentation for Tivoli Manager for Microsoft SQL Server Configuring TEC for the Topology Console Using GEM Instrumentation tasks and monitors with Tivoli Manager for Microsoft SQL Server Deleting Components on the Topology Console Troubleshooting Uninstalling GEM Instrumentation See Appendix F, Supporting Connections to Microsoft SQL Server Components, for additional information, including details on how Tivoli GEM supports connections to external components. Tivoli Manager for Microsoft SQL Server User s Guide 10 1

232 Overview of Tivoli GEM Overview of Tivoli GEM Purpose of GEM The following sections describe the components of Tivoli GEM. For more information, refer to the Tivoli Global Enterprise Manager Installation and User s Guide. Tivoli GEM uses the concept of business systems to organize and manage computer systems and applications. It allows you to represent your computer systems, applications, and resources in terms of how they relate to your business processes. Expressing your resources in terms of business processes can help administrators understand the impact of resource problems and make better decisions more quickly. GEM Components Tivoli GEM consists of the following: A topology server, which monitors system resources, carries out tasks to be performed on them, and updates their status on topology consoles. The server runs as an application on a Tivoli managed node. One or more topology consoles, which represent your computer resources as business systems to administrators. The consoleis a Java application that runs as a client for the topology server. One or more instrumented components. System resources to be managed through GEM must be instrumented to allow them to communicate with and be controlled by the topology server. Tivoli GEM uses application instrumentation to get the necessary data to display and to manipulate these applications in the context of business systems. The Topology Server The topology server performs services in the following areas: Discovery: instrumented components send heartbeat events to the topology server at configured intervals. The heartbeat 10 2 Version 1.3

233 Overview of Tivoli GEM events identify the components and confirm that they are operational. Relationship Definitions: the topology server is the repository for all of the relationships defined among instrumented components. When a business system is defined using the topology console, its definition is stored on the topology server. Status: The topology server changes icons on the topology console in response to changes in the status of instrumented components. Tasks: the topology server carries out tasks that administrators specify from the topology console. The available tasks vary by component. For example, common tasks are stopping and starting services, applications, or other components; viewing component properties; and viewing componenet error log files. Storage: the topology server stores files and resources that the topology console uses, for example: icons, help files, views, and settings. Installing and Using GEM Instrumentation The Topology Console The topology console graphically displays business system information, as follows: Icons represent components. Lines between the icons represent links or relationships between components. Color indicates status, both of individual components and the entire business system. The topology console gets its information from the topology server. As the topology server receives status updates from instrumented components, it updates the topology console to display the status of the business system. Instrumented Components An instrumented component is simply a resource you wish to monitor. It must be instrumented in order for it to communicate with and be controlled by the topology server. Tivoli Manager for Microsoft SQL Server User s Guide 10 3

234 Overview of Tivoli GEM Tivoli GEM supports aggregation, which is the logical grouping of components. Some logical grouping may be performed for you automatically. You can specify other logical groups by defining component relationships on the topology console. GEM and Microsoft SQL Server You can view and manage database servers (MSSQLServer resource) and databases (MSSQLDatabase resource) from the GEM console. GEM instrumentation provides automatic aggregation of all Microsoft SQL Server components, as follows: MSSQL: represents the product, Tivoli Manager for Microsoft SQL Server. It is the top-level component and contains all of database servers that it manages. MSSQLServer: represents database servers. Database servers contain one or more databases. MSSQLDatabase: represent databases, the lowest-level component that can be managed. You can specify other relationships manually. For example, databases at different database servers may be defined as members of a business group, for example Transaction Databases. Microsoft SQL Server Representation on the Topology Console In the following example, the MSSQL icon is displayed in the Middleware/DB branch of the topology tree Version 1.3

235 Overview of Tivoli GEM When you open the MSSQL icon, you see all of the database servers managed by Tivoli Manager for Microsoft SQL Server. There is only one database server in the following example. Installing and Using GEM Instrumentation When you open the MSSQLServer icon, you see the databases associated with the server. Relationships between the components are also shown on this view. The MSSQLServer component supports connections to it, but does not discover connections. All other MSSQLDatabase components initiate connections to the MSSQLServer component. Tivoli Manager for Microsoft SQL Server User s Guide 10 5

236 Overview of Tivoli GEM Running Tasks from the Topology Console You can right-click on a component to see a menu of tasks that can be performed on the component. To run these tasks from the topology server, you must be a valid Tivoli administrator with the necessary mssqlserver_dba role authorization. Note: There might be authorization issues when instrumentation is run on remote systems. For a description of each supported task, see GEM Instrumentation Tasks on page Version 1.3

237 Overview of Tivoli GEM Viewing Monitors on the Topology Console Double-click on a component to view the current monitors for that component.. Installing and Using GEM Instrumentation To view actions that you can perform on a monitor, right-click a monitor icon, as shown in the following example. Tivoli Manager for Microsoft SQL Server User s Guide 10 7

238 Overview of Tivoli GEM For a list of supported monitors and what they do, see GEM Instrumentation Monitors on page GEM and the Tivoli Desktop When the GEM instrumentation for Tivoli Manager for Microsoft SQL Server is installed, the following desktop components are created: Top Level Policy Region: Applications_hostname-region Policy Region: PR_MSSQL_Default_hostname-region Profile Managers: PM_ Component_1.3. Task Libraries: TL_MSSQL_1.3_Default_Component_1.3_hostname-region File Packages (containing instrumentation code): FP_MSSQL_1.3_Default_Component_1.3_hostname-region Sentry Profiles (containing instrumentation monitors): SN_MSSQL_1.3_Default_Component_1.3_hostname-region 10 8 Version 1.3

239 Installing GEM Instrumentation Discovering the Microsoft SQL Server Components The means by which the Microsoft SQL Server components are discovered are events sent as a result of monitors distributed to the component of interest. The MSSQLServer and MSSQLDatabase components are each discovered by the Sentry monitors (defined for that component by Tivoli Manager for Microsoft SQL Server GEM Instrumentation) distributed to the Microsoft SQL Server resource profile endpoint. These monitors are typed; therefore, it is not possible to discover the MSSQLDatabase by distributing the MSSQLServer monitors to a MSSQLDatabase profile endpoint. On the GEM console view, all the logically-related MSSQLDatabase components have lines drawn to their associated MSSQLServer component to show their relationships. For more information, see Connections to GEM Components on page F-2. Installing and Using GEM Instrumentation Installing GEM Instrumentation To install the GEM Instrumentation, do the following: Read the prerequisites given for GEM Instrumentation in the Release Notes. Specific parts of GEM, TEC, and Java must be installed and configured before you install the GEM Instrumentation package. Note also that the GEM Instrumentation runs only on operating systems that GEM supports. Install the GEM Instrumentation package, using the instructions in Installing Tivoli Manager for Microsoft SQL Server on page 3-2. You can install the package from the Tivoli desktop or the command line. Setting Up GEM Instrumentation As part of the installation, Tivoli Manager for Microsoft SQL Server GEM Instrumentation creates a policy region, profile managers, profiles, file packages, and task libraries. Tivoli Manager for Microsoft SQL Server User s Guide 10 9

240 Setting Up GEM Instrumentation Note: Because a task library is created for each Microsoft SQL Server component, installation might take a while. Configuring Java You need to configure Java as part of setting up the GEM Instrumentation. The configuration depends on what you have installed: Java Development Kit (JDK) Java Runtime Environment (JRE) Instructions for configuring each are given below. Configuring the Java Development Kit (JDK) If you installed the JDK on the managed nodes where the Microsoft SQL Server components to be managed reside, perform the following steps: Version 1.3

241 Setting Up GEM Instrumentation 1. On w32-ix86 platforms, you can use Settings > Control Panel > System > Environment to set the PATH and CLASSPATH variables. Note that these variables are case sensitive. 2. Set up the PATH and CLASSPATH variables as follows: a. Add the JDK bin directory to the PATH variable. For example: Installing and Using GEM Instrumentation PATH=%PATH%;\jdk1.1.6\bin b. Add the JDK classes.zip to the CLASSPATH variable. For example: CLASSPATH=%CLASSPATH%;\jdk1.1.6\lib\classes.zip 3. On UNIX platforms, you will have to configure the Tivoli environment to include jdk1.1.6/bin and jdk1.1.6/lib/classes.zip by using the following command: odadmin environ get > odenv.txt 4. Edit the file odenv.txt to include the Java paths and reset the environment by using the following command: odadmin environ set < odenv.txt This command takes the updated file and resets the environment with its contents. 5. Recycle the oserv daemon by using the following command: odadmin reexec For more information and access to JDK, visit the following Internet site: For more information on supported version levels of JDK, refer to the Tivoli Global Enterprise Manager Release Notes, Version 2.2. Tivoli Manager for Microsoft SQL Server User s Guide 10 11

242 Setting Up GEM Instrumentation Configuring the Java Runtime Environment (JRE) Tivoli Manager for Microsoft SQL Server GEM Instrumentation can use JRE in place of the JDK. To do so, the JRE must be installed in a known location. The installation directory is as follows: $BINDIR/GEM/Instrumentation/jre The JRE s bin and lib directories should also be located in this directory. If the JRE s bin directory exists, the Tivoli Manager for Microsoft SQL Server GEM Instrumentation will use the JRE installed in the bin directory rather than the JDK. If the JRE s bin directory does not exist, then the Tivoli Manager for Microsoft SQL Server GEM Instrumentation will attempt to use the JDK. If the JRE is removed, then the $BINDIR/GEM/Instrumentation/jre directory should also be removed or the invocation will fail. Configuring the Topology Server For Tivoli GEM to manage Microsoft SQL Server components, the following steps must be completed: 1. The Tivoli Manager for Microsoft SQL Server mssql.pkg AMP file must be loaded on the topology server. See the following subsection, Loading Tivoli Manager for Microsoft SQL Server mssql.pkg AMP file. 2. Microsoft SQL Server components discovery must be initiated for the topology server. See Initiating Component Discovery on page This section also describes how to confirm Tivoli GEM discovery of Microsoft SQL Server components. The mssql.pkg file is a jar (zipped) file that contains all the AMS description files, icon files, and Hypertext Markup Language (HTML) help files that define Tivoli Manager for Microsoft SQL Server business components and their management capabilities to the Version 1.3

243 Setting Up GEM Instrumentation topology server. The following table lists the contents of the mssql.pkg AMP file. Type of File File Name General files that relate to all Microsoft SQL Server components: Description Files: MSSQLCompon1_3Tivol.bcdf MSSQL1_3Microsoft.gdf MSSQL1_3Tivoli.bsdf Installing and Using GEM Instrumentation Icon Files: Help File: 16_mssql_server_normal.gif 32_mssql_server_normal.gif dialog_mssql_437.html MSSQLServer component: Description Files: Icon Files: Help File: MSSQLServer1_3Micros.cdf MSSQLServer1_3Tivoli.bmdf 16_mssql_server_normal.gif 32_mssql_server_normal.gif dialog_mssqlserver_437.html MSSQLDatabase component: Description Files: Icon Files: Help File: MSSQLDatabas1_3Micro.cdf MSSQLDatabas1_3Tivol.bmdf 16_mssql_database_normal.gif 32_mssql_database_normal.gif dialog_mssqldatabase_437.html Loading the AMP file To configure the topology server for Tivoli Manager for Microsoft SQL Server, you must load the mssql.pkg file. This can be done in one of two ways: If this is the first time the set of description files is being loaded into the topology server, you can load the mssql.pkg file from the topology console client. From the topology console menu, choose File > Load New AMP and select the mssql.pkg file. Tivoli Manager for Microsoft SQL Server User s Guide 10 13

244 Setting Up GEM Instrumentation The mssql.pkg file is located in the tivoli_install_dir/bin/generic/mssqlscripts directory on the TMR server. Note: OR If the topology server is not installed on the same node as the TMR server, this file might need to be copied to a location accessible from the topology server console. The mssql.pkg file also can be found in the SUPPORT directory on the Tivoli Manager for Microsoft SQL Server, Version 1.3, CD-ROM. If the description files have been loaded previously, the mssql.pkg as well as the Microsoft SQL Server description files must be deleted from the topology server s appdefs directory. Use the following steps: a. Stop the topology server if it is running. b. Remove all the Microsoft SQL Server description files as well as the mssql.pkg file from the topology server s appdefs directory c. Copy the new mssql.pkg file into the appdefs directory and use the ihsaunpk command line utility to unpack mssql.pkg. For more information, refer to the description of the ihsaunpk command in the Tivoli Global Enterprise Manager Installation and User s Guide Version 1.3

245 Setting Up GEM Instrumentation d. Reset the topology server database if the description files have been modified. Note: This step must be done with caution because of the likelihood of data loss. For a full description of the process and implications, refer to the Tivoli Global Enterprise Manager Installation and User s Guide. e. Restart the topology server. f. Start the topology console. g. Initiate discovery of Microsoft SQL Server components. See the following subsection, Initiating Component Discovery. h. Interact with discovered components. See Using GEM Instrumentation on page Installing and Using GEM Instrumentation Initiating Component Discovery Component discovery is the means of informing the topology server of the existence of components. Tivoli Distributed Monitoring is the means of discovery for Microsoft SQL Server components. A heartbeat event, which specifies information that uniquely identifies a component, is generated and sent to the TEC. This event is then forwarded to the topology server. The topology server then makes available the management capabilities defined for this component in its description files. Prior to initiating the discovery of Microsoft SQL Server components procedure, make sure all the Microsoft SQL Server components you wish to manage using Tivoli GEM have been registered using Tivoli Manager for Microsoft SQL Server. For information on registering Microsoft SQL Server components, see Chapter 4, Setting Up Tivoli Manager for Microsoft SQL Server. It is important to perform this action because the means of discovery of these components by the topology server depends on them having been registered by Tivoli Manager for Microsoft SQL Server. To initiate the discovery of Tivoli Manager for Microsoft SQL Server components, do one of the following: Tivoli Manager for Microsoft SQL Server User s Guide 10 15

246 Setting Up GEM Instrumentation Auto-initiate Microsoft SQL Server component discovery. See Auto-initiating Component Discovery on page OR Manually initiate Microsoft SQL Server component discovery. See Manually Initiating Component Discovery on page Note: Information in the following subsections assumes that you have installed Tivoli Manager for Microsoft SQL Server and registered all Microsoft SQL Server resources to be managed from Tivoli GEM. For installation information, see Chapter 3, Installing the Software. For registration information, see Registering a Database Server and Discovering Its Databases on page 4-9. Auto-initiating Component Discovery You can initiate the discovery of Tivoli Manager for Microsoft SQL Server components with the DiscoverMSSQLComponents.sh script. The DiscoverMSSQLComponents.sh script is located in the tivoli_install_dir/bin/generic/mssqlscripts directory on the TMR server. The Tivoli Manager for Microsoft SQL Server, Version 1.3, CD-ROM also contains the DiscoverMSSQLComponents.sh script in the SUPPORT directory (however, you will need to rename DISCMSS.SH to DiscoverMSSQLComponents.sh). This script automates the Microsoft SQL Server components discovery initiation process by doing the following: 1. Lists all the available profile endpoints for a Microsoft SQL Server component type. 2. Prompts for user input for endpoints to discover. Accepts all selected endpoints by default. 3. Subscribes specified endpoints to their appropriate GEM-specific component profile managers. 4. Subscribes appropriate managed nodes to GEM-specific component profile manager Version 1.3

247 Setting Up GEM Instrumentation 5. Distributes component File Package profiles to specified profile endpoint managed nodes. 6. Unsubscribes managed nodes from a GEM-specific profile manager. 7. Distributes Sentry profiles to profile-selected endpoints. 8. Reports all status to the following log file: $wtemp/discovermssqlcomponents_$timestamp.log. Installing and Using GEM Instrumentation To successfully run the DiscoverMSSQLComponents.sh script, the following prerequisites must be met: You have configured your Tivoli environment by running setup_env.sh. Tivoli Manager for Microsoft SQL Server is installed and all resources for which component discovery initiation is required are registered using Tivoli Manager to Microsoft SQL Server. Tivoli Manager for Microsoft SQL Server is installed on the TMR server. The oserv process is running. You are running a Korn or Bash shell. To run the DiscoverMSSQLComponents.sh script, enter the following at a command prompt on the TMR server: bash$ cd <tivoli_install_dir>/bin/generic/mssqlscripts bash$ sh DiscoverMSSQLComponents.sh A menu similar to the following example will be displayed. Tivoli Manager for Microsoft SQL Server User s Guide 10 17

248 Setting Up GEM Instrumentation Explanations for the menu prompts are as follows: 1. PRODUCT Indicates that the product for which component discovery will be made is MSSQL. The default setting is MSSQL. 2. COMPONENT Indicates that the component type for which discovery will be made is MSSQLServer. Valid entries are MSSQLServer and MSSQLDatabase. 3. PROFILE MANAGER Indicates the valid GEM-specific profile manager for the MSSQLServer component. 4. SENTRY PROFILE Indicates the valid Sentry profile for the MSSQLServer component. 5. PROFILE ENDPOINT(S) Indicates the valid profile endpoints for the MSSQLServer component. This list is dynamic and will change depending on the available registered Microsoft SQL Server resources and the component option selected. 6. DISCOVER COMPONENTS Initiates discovery for the options selected, gives status of action being taken, and writes detailed output to a log file. 7. EXIT Quits menu option selection. Note: Entries for the DiscoverMSSQLComponents.sh script are case sensitive; therefore, an entry for COMPONENT such as mssqlserver is not valid. ENTER OPTION Prompts you to select the desired option by typing in its option number. Then press Enter Version 1.3

249 Setting Up GEM Instrumentation For example, to select the resource as the endpoint for the MSSQLServer component, enter 5 at the ENTER OPTION prompt and press Enter. A message appears listing the current values for the selected resource, and prompts you to either enter one of the resource names or press Enter to accept all of the resources. For this example, enter nemuchay@nemuchay and press Enter. Soon after pressing Enter, you will see the menu re-displayed with, for example, nemuchay@nemuchay listed as the only profile endpoint, as shown in the following example. Installing and Using GEM Instrumentation To discover the MSSQLServer component, for example, enter 6 at the ENTER OPTION prompt and press Enter. After pressing Enter, a message appears asking you to wait while the MSSQLServer component is discovered, followed by another message when the discovery is complete. It also displays steps for you to complete the discovery, as shown in the following example. Tivoli Manager for Microsoft SQL Server User s Guide 10 19

250 Setting Up GEM Instrumentation Shortly after this action, events will be sent to the TEC that are then forwarded to the specified topology server for component discovery to complete. See Confirming Component Discovery on page Component discovery initiation can also be done manually. See the following subsection, Manually Initiating Component Discovery. Manually Initiating Component Discovery This subsection describes the procedure that you must perform before you can use the Tivoli GEM Instrumentation. Note: The following procedure assumes that you have installed Tivoli Manager for Microsoft SQL Server and registered all the Microsoft SQL Server resources to be managed from Tivoli GEM using Tivoli Manager for Microsoft SQL Server. Perform the following steps: 1. Distribute the Tivoli Manager for Microsoft SQL Server GEM Instrumentation file packages. See the following subsection, Subscribing Managed Nodes and Distributing File Packages on page To discover the Microsoft SQL Server components on the topology server, distribute the appropriate Tivoli Manager for Microsoft SQL Server GEM Instrumentation Sentry profiles to those components. See Subscribing Resources and Distributing Monitoring Profiles on page Make sure the GEM Administrators have valid Tivoli logins and are assigned the appropriate Microsoft SQL Server roles. Subscribing Managed Nodes and Distributing File Packages After you install Tivoli Manager for Microsoft SQL Server GEM Instrumentation, you can distribute the following Tivoli Manager for Microsoft SQL Server GEM Instrumentation file packages: FP_MSSQL_1.3._Default_MSSQLServer_1.3._\ hostname-region FP_MSSQL_1.3._Default_MSSQLDatabase_1.3._\ hostname-region Version 1.3

251 Setting Up GEM Instrumentation Distribute these file packages to the managed nodes on which the Microsoft SQL Server components exist in order to have the instrumentation code available for local execution. The order of distribution is not important. Note: Distribute all file packages to all nodes where Tivoli Manager for Microsoft SQL Server objects exist that you wish to manage from the topology server. Subscribing Resources and Distributing Monitoring Profiles After you install Tivoli Manager for Microsoft SQL Server GEM Instrumentation, subscribe and distribute the component Sentry profiles as follows. 1. Subscribe the MSSQLServer endpoint to profile manager PM_MSSQLServer_1.3. and distribute the Microsoft SQL Server Sentry profile: Installing and Using GEM Instrumentation SN_MSSQL_1.1_Default_MSSQLServer_1.3_\ hostname-region to the MSSQLServer resources you wish to manage from the topology server. 2. Subscribe the MSSQLDatabase endpoint to profile manager PM_MSSQLDatabase_1.3. and distribute the Microsoft SQL Server Database Sentry profile: SN_MSSQL_1.3_Default_MSSQLDatabase_1.3_\ hostname-region to the MSSQLDatabase resources you wish to manage from the topology server. Tivoli GEM receives the monitor status through TEC events forwarded to the topology server. To subscribe and distribute the Tivoli Manager for Microsoft SQL Server GEM Instrumentation profiles to a MSSQLServer endpoint, do the following: Tivoli Manager for Microsoft SQL Server User s Guide 10 21

252 Setting Up GEM Instrumentation 1. Double-click the PM_MSSQLServer_1.3. profile manager icon. 2. Add the MSSQLServer endpoints you wish to manage from Tivoli GEM to the list of subscribers. Do this by dragging and dropping the MSSQLServer component on the Profile Manager window s Subscribers palette. OR On the Profile Manager window s main menu, choose Profile Manager > Subscribers. 3. On the Subscribers dialog, make sure your MSSQLServer components are in the Current Subscribers list. Otherwise, select your target MSSQLServer instances from the Available to become Subscribers list and click the left-arrow button to transfer the entries to the Current Subscribers list. 4. Click the Set Subscriptions & Close button. 5. Set the Sentry profile distribution defaults. a. On the Profile Manager window, double-click on the following profile icon: SN_MSSQL_1.3_Default_MSSQLServer_1.3_\ hostname-region b. On the TME 10 Distributed Monitoring Profile Properties dialog s main menu, chose Profile > Distribution Defaults Version 1.3

253 Setting Up GEM Instrumentation c. On the Distribution Defaults dialog, make sure the following options are selected: - All Levels Of Subscribers - Make subscribers profile an EXACT COPY of this profile 6. Click the Set & Close button to return to the TME 10 Distributed Monitoring Profile Properties dialog. 7. Distribute the Sentry profile for: Installing and Using GEM Instrumentation SN_MSSQL_1.3_Default_MSSQLServer_1.3_hostname-region to the subscribing MSSQLServer instances. Do this by dragging and dropping the Sentry profile on the MSSQLServer instances you wish to manage using Tivoli GEM. OR Double-click the Sentry profile icon 8. On the Profile Manager window s main menu, choose Profile Manager > Distribute. 9. On the Distribute Profile dialog, make sure only the MSSQLServer components you wish to manage using Tivoli GEM are in the Distribute To These Subscribers list. 10. Click the Distribute & Close button to distribute the profile and return to the TME 10 Distributed Monitoring Profile Properties dialog. Note: The monitors contained in these profiles are typed; therefore, a component discovery will not occur if a specific component profile is distributed to the wrong endpoint. For example, if a MSSQLServer profile is distributed to the MSSQLDatabase component, a successful discovery of the MSSQLDatabase component will not be made by Tivoli GEM. The Microsoft SQL Server Sentry profiles should not be distributed to managed nodes. For individual components, the order of subscription and distribution is not important. However, Tivoli advises that the Microsoft SQL Tivoli Manager for Microsoft SQL Server User s Guide 10 23

254 Configuring TEC for the Topology Server Server is included in all discoveries since all other Microsoft SQL Server components draw a relationship to the MSSQLServer component and all external components wishing to connect to Microsoft SQL Server components must do so by way of the MSSQLServer component. Confirming Component Discovery Observe the active topology console to make sure that the Microsoft SQL Server components are displayed as they are discovered. Note that only components that receive a distribution are discovered. The heartbeat monitor for each Microsoft SQL server component sends a heartbeat event for each resource at a user-specified interval. When the TEC server receives a heartbeat event, it forwards the event to the topology server and an icon is displayed on the topology console. Configuring TEC for the Topology Server Introduction Methods If you wish for events sent by the GEM Instrumentation monitors to affect the displayed status of Microsoft SQL Server components on the topology console, you must configure the TEC to forward events sent by these monitors to the topology server. Performing this configuration ensures that Tivoli GEM heartbeat, state, connection and component information events are supported by the TEC and that the TEC forwards these events successfully to the topology server. For more information on configuring a topology server, refer to the Tivoli Global Enterprise Manager Installation and User s Guide. You can configure the TEC using any of the following methods: Use the ConfigureTECMSSQL task from the Tivoli desktop (recommended) Version 1.3

255 Configuring TEC for the Topology Server Use the ConfigureTECMSSQL task from the command line (recommended) Use TEC facilities on the Tivoli Desktop Use TEC commands on the command line Procedures are given for each method. Using the ConfigureTECMSSQL task is recommended because it performs all of the necessary steps automatically and in the right order. Installing and Using GEM Instrumentation Prerequisites Before configuring the TEC server the following software must be installed on the host where the TEC server runs: Tivoli GEM Event Enablement Assumptions Used in the Examples The following assumptions are used in the examples: The rule base configured to support GEM events is named GemEvent. The event server is in the local TMR. Steps in Configuration If you choose to configure the TEC from the Tivoli Desktop or using TEC commands on the command line, you perform the same general steps in both cases: Import class files Import the rule set Compile and load the rule base Stop and restart the event server These steps are all performed automatically when you use the ConfigureTECMSSQL task. Tivoli Manager for Microsoft SQL Server User s Guide 10 25

256 Configuring TEC for the Topology Server Authorization The following table provides the context and authorization roles required for configuring the TEC. Activity Context Required Role Configure the TEC Managed node (where the TEC server is installed) super, senior, admin, user, mssqlserver_dba Note: Only the senior role is required if you configure use TEC commands on the command line. Using ConfigureTECMSSQL from the Desktop The following procedure shows how to use the ConfigureTECMSSQL task on the Tivoli Desktop to configure TEC to forward GEM Instrumentation monitor events to the topology server Version 1.3

257 Configuring TEC for the Topology Server 1. On the Tivoli Desktop, double-click the MSSQLTasks icon. The MSSQLTasks window appears. 2. Double-click the ConfigureTECMSSQL task. The ConfigureTECMSSQL dialog appears as follows. Installing and Using GEM Instrumentation 3. Specify options in the dialog as follows: Rule Base Name: Enter the name of the rule base you want to create or configure. Copy Rule Base: this option is selected by default and the Rule Base to Copy is set to GemEvent. If you wish to copy a rule base order than GemEvent, then enter the rule base name in the Rule Base to Copy field. Note: The rule base to copy should be one that has been enabled for GEM. Tivoli Manager for Microsoft SQL Server User s Guide 10 27

258 Configuring TEC for the Topology Server If you do not wish to copy a rule base but wish to configure and existing enabled rule base, enter the name of the existing rule base Rule Base Name field and deselect the Copy Rule Base option. Configure Event Server for Tivoli GEM: select this option. If this option does not appear, then the GEM instrumentation has not been installed. Quit the task, install the GEM instrumentation, and then execute the task again. Create Event Group: Specify the name of the event group you wish to configure, if any. Event Server Option to Configure. Select at least Configure Event Server for Tivoli GEM. You can also configure the event server for the other facilities as well. Restart Event Server. Select this option. 4. Press Set & Execute. The ConfigureTECMSSQL task displays output of all the actions performed on task completion. Using ConfigureTECMSSQL from the Command Line You can run the ConfigureTECMSSQL task from the command line. See ConfigureTECMSSQL in Chapter 2, The MSSQLManagerTasks Library, of the Tivoli Manager for Sybase Reference Guide. Using TEC Facilities on the Tivoli Desktop The following section demonstrates how to use the Tivoli Desktop to configure TEC to forward GEM Instrumentation monitor events to the topology server Version 1.3

259 Configuring TEC for the Topology Server Importing TEC Class Files 1. Right-click the Event Server icon on the Tivoli desktop and choose Rule Bases. 2. On the Event Server Rule Bases dialog, right-click the GemEvent rule base (or your GEM enabled rule base) then choose Import. The Import Into Rule Base dialog appears.. Installing and Using GEM Instrumentation 3. On the Import Into Rule Base dialog, select the Import Class Definitions check box, the Insert After for the Position to insert imported class file option, and specify that the imported rules be positioned after Sentry.baroc, as shown above. Tivoli Manager for Microsoft SQL Server User s Guide 10 29

260 Configuring TEC for the Topology Server Note: You must position the class files after the Sentry.baroc file. The imported classes inherit from classes defined in the Sentry.baroc file. 4. Click the Class Definitions File button to display File Browser dialog. Navigate to the $BINDIR/../generic/MSSQLSentry directory, then select the ESMSentry.baroc file. 5. Select the Select File and Close button to select the ESMSentry.baroc file and return to the Import Into Rule Base dialog. 6. On the Import Into Rule Base dialog, select Import to import the ESMSentry.baroc file into the GemEvent rule base. 7. On the Import Into Rule Base dialog, make sure the Import Class Definitions check box and the Insert After option for the Position to insert imported class file are selected, then select the ESMSentry.baroc file. 8. Select the Class Definitions File button to display File Browser dialog. Navigate to: the $BINDIR/../generic/MSSQLSentry directory, then select the M7MSSQLServerSentry.baroc file Version 1.3

261 Configuring TEC for the Topology Server 9. Select the Select File and Close button to select the M7MSSQLServerSentry.baroc file and return to the Import Into Rule Base dialog. 10. On the Import Into Rule Base dialog, select the Import button to import the M7MSSQLServerSentry.baroc file into the GemEvent rule base. 11. Repeat steps 7-10 to import the M7MSSQLDatabaseSentry.baroc file. Installing and Using GEM Instrumentation Tivoli Manager for Microsoft SQL Server User s Guide 10 31

262 Configuring TEC for the Topology Server Importing the Rule Set 1. On the Import Into Rule Base dialog, select the Import Rule Set check box and deselect the Import Class Definitions check box. Also select the Insert After option for the Position to insert imported rule set option, then select interapp.rls as below. Note: It is important to import the rule set after the interapp.rls file because the Tivoli Manager for Microsoft SQL Server definitions depend on the heartbeat events forwarded to the topology server by the interapp.rls rules set Version 1.3

263 Configuring TEC for the Topology Server 2. Choose the Rule Sets File button to display File Browser dialog. Navigate to the $BINDIR/../generic/MSSQLScripts directory, then select the mssql_gemevents1_3.rls file. Note: If you configure the TEC for Tivoli Manager for Microsoft SQL Server, Version 1.2, use the mssql_gemevents1_2.rls rule set file. Using the mssql_gemevents1_3.rls rule set on a Tivoli Manager for Microsoft SQL Server, Version 1.2, installation will result in a compilation error. Installing and Using GEM Instrumentation 3. Click Select File and Close to select the mssql_gemevents1_3.rls file and return to the Import Into Rule Base dialog. 4. On the Import Into Rule Base dialog, click Import & Close to import the mssql_gemevents1_3.rls file into the GemEvent rule base. Compiling and Loading the Rule Base 1. On the Event Server Rule Bases dialog, right-click the GemEvent rule base and select Compile to display the Compile Rule Base dialog. 2. Select the Trace Rules option if you wish to trace TEC rule invocations. Refer to the TME 10 Enterprise Console Rule Tivoli Manager for Microsoft SQL Server User s Guide 10 33

264 Configuring TEC for the Topology Server Builder s Guide for information on the TME 10 Enterprise Console s rule tracing facility. 3. Click Compile to compile the rule base. 4. Click Close to exit the Compile Rule Base dilaog. 5. On the Event Server Rule Bases dialog, right-click the GemEvent rule base and select Load to display the Load Rule Base dialog. 6. Select the Load, but activate only when server restarts option. 7. Press Load & Close. Stopping and Restarting the Event Server 1. On the Tivoli desktop, right-click the event server icon and select Shutdown (if the event server is already shut down, then go to step three). 2. Press the Halt Server button on the Halt the Tivoli Enterprise Console Server dialog. 3. On the Tivoli desktop, right-click the event server icon and select Start-up to restart the TEC with the configured rule base loaded Version 1.3

265 Configuring TEC for the Topology Server Events sent from the Tivoli Manager for Microsoft SQL Server monitors should now be successfully sent to the topology server. Using TEC Commands The following sections demonstrate how to use TEC commands to configure the TEC for the topology server. Importing TEC Class Files Installing and Using GEM Instrumentation wimprbclass \ $BINDIR/../generic/MSSQLSentry/ESMSentry.baroc GemEvent wimprbclass \ $BINDIR/../generic/MSSQLSentry/M7MSSQLServerSentry.baroc GemEvent wimprbclass \ $BINDIR/../generic/MSSQLSentry/M7MSSQLDatabaseSentry.baroc GemEvent Importing the Rule Set wimprbrules \ $BINDIR/../generic/MSSQLScripts/mssql_gemevents1_3.rls GemEvent Note: User the mssql_gemevents1_2.rls rule set if you have Tivoli Manager for Microsoft SQL Server, Version 1.2 installed. Compiling and Loading the Rule Base wcomprules GemEvent Note: If you do not compile the rule base before attempting to load it, you will get an error message. wloadrb GemEvent Stopping and Restarting the Event Server To stop the event server, use the following command: wstopesvr To start the event server, use the following command: wstartesvr Tivoli Manager for Microsoft SQL Server User s Guide 10 35

266 Using GEM Instrumentation Using GEM Instrumentation After you install Tivoli Manager for Microsoft SQL Server GEM Instrumentation, you can use tasks and monitors to manage your registered Microsoft SQL Server components from the topology console. This section describes the Tivoli Manager for Microsoft SQL Server GEM Instrumentation tasks and monitors. GEM Instrumentation Monitors This subsection outlines the monitors supported by each instrumented component: Heartbeat - Informs the topology server of the existence of an instrumented component by sending an APM_HEARTBEAT event. State - Informs the topology server of the state of an instrumented component by sending an APM_THRESHOLD event. Connection - Detects and notifies the topology server about new and deleted connections of a particular instrumented component connection type by sending an APM_CONNECTION_CHANGE event. Component information change - Informs the topology server that an instrumented component s information has changed by sending an APM_CI_CHANGE event. Note: You might need to redistribute GEM monitors after oserv shutdown. Supported Monitors from Tivoli Manager for Microsoft SQL Server The following monitors are supported. Database Monitors DataSpacePercentUsedDB Fragmentation Version 1.3

267 Using GEM Instrumentation LogSpacePercentUsedDB OptimizerStatisticsAge OldestOpenTransactionDB PeopleSoftSpaceUsedTable PeopleSoftOptimizerStatisticsAge PeopleSoftFragmentation ReplicationLatency Installing and Using GEM Instrumentation Server Monitors CacheConfiguredFreeBuffersPercentUsed ClientCountPercentUsed CacheHitRatio DataSpacePercentUsedSRVR DeliveryLatency IODiskErrors IOSinglePageWriteRate IOPageReadRate IOOutstandingWrites IOOutstandingReads IOLogWriteRate SQLServerAgentFailedJobs LogSpacePercentUsedSRVR NumberOfDeadlocks NetworkReadRate NetworkWriteRate NTApplicationLog OldestOpenTransactionSRVR ProcedureBuffersUsed Tivoli Manager for Microsoft SQL Server User s Guide 10 37

268 Using GEM Instrumentation ProcedureCacheUsed RAEffectiveness ServiceState TotalLocksPercentUsed UserConnectionsPercentUsed GEM Instrumentation Tasks Tivoli Manager for Microsoft SQL Server GEM Instrumentation component tasks are contained in component task libraries, as described in Overview of Tivoli GEM on page Instrumentation tasks may be run from the topology console, the Tivoli desktop, or from the command line. Tivoli recommends running all instrumentation tasks from the topology console, as described in Starting a Component Task on page Note: The instrumentation library may time out when a task is run and returns no output or causes aggregation not to occur. The tasks supported by each instrumented component are outlined below: Query State - Returns the status of the instrumented component. Returns UP if status is available, or DOWN if not. Start - Starts the instrumented component and sends an event to update the GEM console view. The Start task also starts the SQL Executive/SQL Server Agent and MSDTC Services Notes: The MSSQLServer component starts in the Normal mode. The MSSQLDatabase component does not support a Start task. Stop - Stops the instrumented component with the net stop option and sends an event to update the GEM console view. The Stop task also stops the SQL Executive/SQL Server Agent and MSDTC Services Version 1.3

269 Using GEM Instrumentation Note: The MSSQLDatabase component does not support a Stop task. MSSQLServerLabel - Returns the MSSQLDataServer label. (Used in aggregation.) View Component Properties - Displays the instrumented component s Tivoli Manager for Microsoft SQL Server registration details. View Error Log - Displays the last 75 lines of the instrumented component s error log. Note: The MSSQLDatabase component does not support a View Error Log task. Query Value - Returns the current value for a specified monitor. Set Polling Interval - Sets the monitoring schedule to the specified interval in minutes. Query Thresholds - Sends one or more threshold events to the TEC for use by the Tivoli GEM environment. Query Threshold Settings - Returns current threshold settings. Set Pulse - Adjusts the frequency at which the heartbeat monitor is run. Set Thresholds - Defines the circumstances under which threshold events are sent to the topology server. Installing and Using GEM Instrumentation Navigating on the Topology Console An aggregate MSSQL icon is the highest level Microsoft SQL Server aggregate component. This is displayed at the Middleware/DB Tivoli Manager for Microsoft SQL Server User s Guide 10 39

270 Using GEM Instrumentation branch of the topology server tree view, as shown in the following example. Double-click the MSSQL aggregate icon on the Middleware/DB branch to display the MSSQLServer aggregate icons, as shown in the following example. On the topology console, you can navigate from an aggregate MSSQLServer icon to the specific Microsoft SQL Server components associated with that MSSQLServer component. Right-click on a component icon to access a pop-up menu from which you can select tasks and other options, as shown in the following example, or you can continue clicking icons to navigate down the tree to see monitors defined at the topology server for that component Version 1.3

271 Using GEM Instrumentation Using the Tear-Away Log Prior to starting a task, open the tear-away log provided by the topology console. The log provides current messages that show the progress of the tasks you run. To tear away the topology console log, do the following: From the topology console menu bar, select the Options > Tear Away Log option. Tivoli displays the GEM - Log window, as shown in the following example. Installing and Using GEM Instrumentation Starting a Component Task The following procedure allows you run all Microsoft SQL Server GEM Instrumentation tasks from the topology console. The following table provides the context and authorization roles required for this procedure: Activity Context Required Role Starting a component task Microsoft SQL Server GEM component mssqlserver_dba To perform a task such as shutting down the Microsoft SQL Server, perform the following steps: Tivoli Manager for Microsoft SQL Server User s Guide 10 41

272 Using GEM Instrumentation 1. Right-click the MSSQLServer icon, then choose Stop. 2. Enter Y in the Confirmation window and click the Set and Execute button. The topology console tear-away log window provides a progress report listing of the task just executed. In the example GEM - Log window above, the messages indicate that the Microsoft SQL Server was shutdown Version 1.3

273 Deleting Components on the Topology Console Viewing Monitor Status To view the status of the Tivoli Manager for Microsoft SQL Server monitors supported by Tivoli GEM on the topology console, do the following: Navigate to the Microsoft SQL Server component you wish to view monitors for. See Navigating on the Topology Console on page Double-click on the component to see the monitors associated with that component, as shown in the following example. Installing and Using GEM Instrumentation Deleting Components on the Topology Console The actions described in this section delete the Microsoft SQL Server component from the topology server database but does not delete the Tivoli Microsoft SQL Server itself. To delete the Microsoft SQL Server component, you must Unsubscribe the monitors Delete the components Tivoli Manager for Microsoft SQL Server User s Guide 10 43

274 Deleting Components on the Topology Console Unsubscribing Monitors To stop monitors running, unsubscribe the Microsoft SQL Server resources from the profile manager by selecting the Delete all profile copies option. -OR- Use the DiscoverMSSQLComponents.sh to unsubscribe the resources for which components have been deleted. Do the following to unsubscribe resources from the GEM-specific monitors and stop component monitors from running: 1. Make sure that the resources to unsubscribe from the GEM-specific profile manager are those listed in option 5. If this is not so, select option 5 and enter the resource names you want to unsubscribe. 2. At the ENTER OPTION prompt, enter a u as above and press Enter. 3. Press Enter again to confirm the unsubscribe action Version 1.3