IBM Tivoli Monitoring for Databases: DB2: …publib.boulder.ibm.com/tividd/td/ITMD/SC23-4727-00/en_US/PDF/SC23...IBM posts all publications for this and all other Tivoli products,

IBM Tivoli Monitoring for Databases: DB2

Reference GuideVersion 5.1.0

SC23-4727-00

��

IBM Tivoli Monitoring for Databases: DB2

Reference GuideVersion 5.1.0

SC23-4727-00

��

NoteBefore using this information and the product it supports, read the information in Appendix E, “Notices” on page 497.

First Edition (September 2002)

This edition applies to version 5.1.0 of IBM Tivoli Monitoring for Databases: DB2 and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2002. All rights reserved. US Government UsersRestricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this guide . . . . . . . . . . . vWho should read this guide . . . . . . . . . vWhat this guide contains . . . . . . . . . . vPublications . . . . . . . . . . . . . . vi

IBM Tivoli Monitoring for Databases: DB2 library viPrerequisite publications . . . . . . . . . viRelated publications . . . . . . . . . . viiAccessing softcopy publications . . . . . . viiUsing the guide online . . . . . . . . . viiiViewing online help . . . . . . . . . . viiiOrdering publications . . . . . . . . . viiiProviding feedback about publications . . . . viii

Accessibility . . . . . . . . . . . . . . ixContacting Customer Support . . . . . . . . ixConventions used in this guide . . . . . . . . ix

Typeface conventions . . . . . . . . . . ixOperating system-dependent variables and paths ix

Chapter 1. Introduction . . . . . . . . 1Running Tivoli commands . . . . . . . . . . 1

Running Tivoli commands on UNIX operatingsystems . . . . . . . . . . . . . . . 2Running Tivoli commands on Windows NToperating systems . . . . . . . . . . . 2Where to find additional information about shells 2Establishing the Tivoli environment within a shell 3Establishing the Tivoli environment on anendpoint. . . . . . . . . . . . . . . 3

Tivoli command syntax . . . . . . . . . . . 4Common parameters . . . . . . . . . . . 4

Chapter 2. DB2 resource models . . . . 7DB2 Agent. . . . . . . . . . . . . . . 12DB2 Apply Replication Status . . . . . . . . 21DB2 Buffer Pools . . . . . . . . . . . . 27DB2 Buffer Pool/Extended Storage . . . . . . 58DB2 Catalog Cache . . . . . . . . . . . . 64DB2 CPU Utilization . . . . . . . . . . . 68DB2 Database Activity . . . . . . . . . . . 73DB2 Direct IO . . . . . . . . . . . . . 95DB2 Fast Communication Manager . . . . . . 113DB2 Host Throughput . . . . . . . . . . 123DB2 Instance Status . . . . . . . . . . . 131DB2 Locks and Deadlocks . . . . . . . . . 136DB2 Lock Waits . . . . . . . . . . . . 157DB2 Logging . . . . . . . . . . . . . 165DB2 Package Cache . . . . . . . . . . . 176DB2 Replication Capture . . . . . . . . . 183DB2 SAP Tablespace Usage/Status . . . . . . 188DB2 Sorting . . . . . . . . . . . . . . 201DB2 SQL Cursor Activity . . . . . . . . . 213DB2 SQL Statement Activity . . . . . . . . 218DB2 Table Activity . . . . . . . . . . . 228DB2 Table Apply Replication . . . . . . . . 231

Chapter 3. About task libraries . . . . 237

Chapter 4. Monitor and administrationtasks . . . . . . . . . . . . . . . 239ECC_Broadcast_Message . . . . . . . . . 240ECC_Configure_Audit . . . . . . . . . . 242ECC_Configure_TEC_Classes . . . . . . . . 245ECC_Create_Import_Audit_Log . . . . . . . 248ECC_Extract_Audit_Log. . . . . . . . . . 251ECC_Flush_Audit_Buffer . . . . . . . . . 254ECC_Get_Audit_Configuration . . . . . . . 255ECC_Prune_Audit_Log . . . . . . . . . . 256ECC_Purge_Audit_Log . . . . . . . . . . 258ECC_Reset_Audit_Configuration . . . . . . . 259ECC_Reset_Counters . . . . . . . . . . . 261ECC_Send_Files_To_TEC_TMR . . . . . . . 262ECC_Send_Notice . . . . . . . . . . . . 264ECC_Set_Up_Monitoring_Agent . . . . . . . 266ECC_Start_Auditing . . . . . . . . . . . 268ECC_Start_Monitoring_Agent . . . . . . . . 269ECC_Stop_Auditing . . . . . . . . . . . 270ECC_Stop_Monitoring_Agent . . . . . . . . 271ECC_TBSM_Discovery . . . . . . . . . . 272

Chapter 5. Database tasks . . . . . . 273ECC_Activate_Database . . . . . . . . . . 275ECC_Alter_Bufferpool . . . . . . . . . . 277ECC_Backup_Database . . . . . . . . . . 280ECC_Create_Admin_Server. . . . . . . . . 284ECC_Create_Explain_Tables . . . . . . . . 286ECC_Create_Sample_Database. . . . . . . . 287ECC_Deactivate_Database . . . . . . . . . 289ECC_Drop_Admin_Server . . . . . . . . . 291ECC_Drop_Sample_Database . . . . . . . . 292ECC_Force_All_Applications . . . . . . . . 293ECC_Force_Applications . . . . . . . . . 295ECC_Get_Admin_Configuration . . . . . . . 297ECC_Get_Admin_Server_Instance . . . . . . 298ECC_Get_Database_Configuration . . . . . . 299ECC_Get_Database_Manager_Configuration . . . 301ECC_Invoke_Stored_Procedure . . . . . . . 302ECC_List_Applications . . . . . . . . . . 304ECC_List_Backup_Recovery_File . . . . . . . 306ECC_List_DCS_Applications . . . . . . . . 309ECC_List_Node_Directory . . . . . . . . . 312ECC_Prune_Recovery_History_File . . . . . . 314ECC_Quiesce_Tablespaces . . . . . . . . . 317ECC_Rebind_All_Packages . . . . . . . . . 321ECC_Rebind_Package . . . . . . . . . . 323ECC_Reorganize_Table . . . . . . . . . . 325ECC_Reorgchk . . . . . . . . . . . . . 328ECC_Reset_Admin_Configuration . . . . . . 331ECC_Reset_Database_Configuration . . . . . . 332ECC_Reset_Database_Manager_Configuration . . 334ECC_Restart_Database . . . . . . . . . . 336

iii

ECC_Run_Statistics . . . . . . . . . . . 338ECC_Set_Admin_Server_ID . . . . . . . . 342ECC_Start_Admin_Server . . . . . . . . . 344ECC_Start_DB2. . . . . . . . . . . . . 345ECC_Start_DB2_NT_Security . . . . . . . . 349ECC_Stop_Admin_Server . . . . . . . . . 350ECC_Stop_DB2 . . . . . . . . . . . . . 351ECC_Stop_DB2_NT_Security . . . . . . . . 354ECC_Update_Admin_Configuration . . . . . . 355ECC_Update_Database_Configuration . . . . . 357ECC_Update_Database_Manager_Configuration 360

Chapter 6. Data replication tasks . . . 363ECC_Apply_Start . . . . . . . . . . . . 364ECC_Apply_Stop . . . . . . . . . . . . 367ECC_Capture_Get_Log_Seq . . . . . . . . 369ECC_Capture_Prune . . . . . . . . . . . 371ECC_Capture_Reinit . . . . . . . . . . . 373ECC_Capture_Resume . . . . . . . . . . 375ECC_Capture_Start . . . . . . . . . . . 377ECC_Capture_Stop . . . . . . . . . . . 379ECC_Capture_Suspend . . . . . . . . . . 381

Appendix A. Monitor to resourcemodel migration table. . . . . . . . 383

Appendix B. Creating customresource models using CIM classes . 399Creating custom resource models using the IBMTivoli Monitoring Workbench . . . . . . . . 399Classes and properties to use in resource models 402

DB2Agents . . . . . . . . . . . . . 404DB2ApplicationActivity . . . . . . . . . 405DB2ApplicationAgent . . . . . . . . . 406DB2ApplicationBufferPool . . . . . . . . 407DB2ApplicationDirectIO . . . . . . . . . 409DB2ApplicationSorts . . . . . . . . . . 410DB2ApplicationStatement . . . . . . . . 411DB2ApplLocks . . . . . . . . . . . . 414DB2ApplyReplication. . . . . . . . . . 415DB2BufferPool . . . . . . . . . . . . 416DB2CatalogCache . . . . . . . . . . . 421DB2Configuration . . . . . . . . . . . 422DB2Content . . . . . . . . . . . . . 424DB2DatabaseRepl . . . . . . . . . . . 426DB2DirectInOut . . . . . . . . . . . 427DB2GatewayConnections . . . . . . . . 429DB2GatewayThroughput . . . . . . . . 431DB2InstanceAgents . . . . . . . . . . 432DB2InstanceConfiguration . . . . . . . . 434DB2InstanceConnections. . . . . . . . . 436DB2InstanceSorts . . . . . . . . . . . 438

DB2InstanceStatus . . . . . . . . . . . 439DB2Locks . . . . . . . . . . . . . 440DB2Logging . . . . . . . . . . . . . 442DB2PackageCache . . . . . . . . . . . 444DB2PartitionFCMActivity . . . . . . . . 445DB2PartitionGroups . . . . . . . . . . 447DB2Sorts . . . . . . . . . . . . . . 448DB2SQLStatements . . . . . . . . . . 449DB2Status . . . . . . . . . . . . . 452DB2TableActivity . . . . . . . . . . . 453DB2TableContent . . . . . . . . . . . 454DB2TableReplication . . . . . . . . . . 455DB2TablespaceBufferPool . . . . . . . . 456DB2TablespaceContent . . . . . . . . . 460DB2TablespaceDirectIO . . . . . . . . . 461DB2TablespaceSizeDMS . . . . . . . . . 463DB2TablespaceSizeSMS . . . . . . . . . 464DB2TablespaceStatus . . . . . . . . . . 465DB2TableStatus . . . . . . . . . . . . 466

Appendix C. Tivoli Enterprise Consoleclasses . . . . . . . . . . . . . . 467Resource Models . . . . . . . . . . . . 467

Appendix D. DB2 snapshotapplication ID formats . . . . . . . 495APPC . . . . . . . . . . . . . . . . 495

Format . . . . . . . . . . . . . . 495Example . . . . . . . . . . . . . . 495Details . . . . . . . . . . . . . . 495

IPX/SPX . . . . . . . . . . . . . . . 495Format . . . . . . . . . . . . . . 495Example . . . . . . . . . . . . . . 495Details . . . . . . . . . . . . . . 495

Local applications . . . . . . . . . . . . 496Format . . . . . . . . . . . . . . 496Example . . . . . . . . . . . . . . 496Details . . . . . . . . . . . . . . 496

NetBIOS . . . . . . . . . . . . . . . 496Format . . . . . . . . . . . . . . 496Example . . . . . . . . . . . . . . 496Details . . . . . . . . . . . . . . 496

TCP/IP . . . . . . . . . . . . . . . 496Format . . . . . . . . . . . . . . 496Example . . . . . . . . . . . . . . 496Details . . . . . . . . . . . . . . 496

Appendix E. Notices . . . . . . . . 497Trademarks . . . . . . . . . . . . . . 499

Index . . . . . . . . . . . . . . . .X-1

iv IBM Tivoli Monitoring for Databases: DB2: Reference Guide

About this guide

The IBM Tivoli Monitoring for Databases: DB2 Reference Guide describes how toinstall and use the IBM Tivoli Monitoring for Databases: DB2 software to manageDB2 resources with Tivoli Enterprise software.

Who should read this guideThis guide is for system administrators and database administrators. It explains theconcepts you should know to use the IBM Tivoli Monitoring for Databases: DB2software. It contains information about database management using this softwareand how IBM Tivoli Monitoring for Databases: DB2 software is integrated into theTivoli environment.

Readers should be familiar with the following:v Windows NT® or UNIX® operating systemsv Tivoli® environmentv DB2® database administration

What this guide containsThis guide contains the following chapters:v Chapter 1, “Introduction” on page 1

Provides information on how the guide is organized. This chapter also describescommands, resource model output, and IBM Tivoli Monitoring logging.

v Chapter 2, “DB2 resource models” on page 7

Provides information on how to use the resource models to manage databases.v Chapter 3, “About task libraries” on page 237

Provides information on how to run the IBM Tivoli Monitoring for Databases:DB2 tasks in the DB2ManagerAdminTasks, DB2ManagerDatabaseTasks, andDB2ManagerReplicationTasks task libraries.

v Chapter 4, “Monitor and administration tasks” on page 239

Provides information on how to run tasks that are used for monitoring andadministration of DB2.

v Chapter 5, “Database tasks” on page 273

Provides information on how to run tasks that provide basic administrationfunctions for DB2 and the database manager.

v Chapter 6, “Data replication tasks” on page 363

Provides information on how to run tasks that are used with DB2 Replication.

This guide contains the following appendixes:v Appendix A, “Monitor to resource model migration table” on page 383

Provides a table that matches old monitors to new resource models and CIMclasses.

v Appendix B, “Creating custom resource models using CIM classes” onpage 399

Provides DB2 CIM classes and details on how to create custom resource modelsusing the CIM classes.

v

v Appendix C, “Tivoli Enterprise Console classes” on page 467

Provides Tivoli Enterprise Console classes for IBM Tivoli Monitoring forDatabases: DB2.

v Appendix D, “DB2 snapshot application ID formats” on page 495

Provides the formats used for DB2 snapshot application IDs.v Appendix E, “Notices” on page 497

Provides notices, copyright, and trademark information available to the user.

PublicationsThis section lists publications in the IBM Tivoli Monitoring for Databases: DB2 libraryand any other related documents. It also describes how to access Tivolipublications online, how to order Tivoli publications, and how to make commentson Tivoli publications.

IBM Tivoli Monitoring for Databases: DB2 libraryThe following documents are available in the IBM Tivoli Monitoring for Databases:DB2® library:v IBM Tivoli Monitoring for Databases: DB2 User’s Guide, SC23-4726

Provides information about how to use the IBM Tivoli Monitoring for Databases:DB2 software to manage DB2 database resources with Tivoli Enterprise software.

v IBM Tivoli Monitoring for Databases: DB2 Reference Guide, SC23-4727Provides task and resource model information about procedures described in theIBM Tivoli Monitoring for Databases: DB2 User’s Guide.

v IBM Tivoli Monitoring for Databases: DB2 Limitations and Workarounds Supplement,SC23-4786Provides the latest information about known product limitations andworkarounds. To ensure that the information is the latest available, thisdocument is provided only on the Web, where it is updated on a regular basis.You can access the Limitations and Workarounds document through the IBMTivoli Monitoring for Databases: DB2 link on the Tivoli Information Center Website:http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

v IBM Tivoli Monitoring for Databases: Installation and Setup Guide, GC23-4730Provides information on how to install the IBM Tivoli Monitoring for Databases:DB2 software.

v IBM Tivoli Monitoring for Databases, Version 5.1.0 Release Notes, GI11-0933Describes product features and provides information about the latest changes tothe installation requirements and procedures. The release notes also describeknown limitations related to installation and explain how to work around eachlimitation.

Prerequisite publicationsTo to use the information in this book effectively, you must have some prerequisiteknowledge, which you can get from the following books:v Tivoli Management Framework User’s Guide

Provides information about profiles and profile management.v Tivoli Management Framework Planning and Installation Guide

Provides information about server and hardware requirements.

vi IBM Tivoli Monitoring for Databases: DB2: Reference Guide

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html


v Tivoli Management Framework Reference Guide

Provides information about command line commands, such as the winstallcommand.

v IBM Tivoli Monitoring User’s Guide

Provides information about distributed monitoring.v Tivoli Enterprise Console User’s Guide

Provides information about using the Tivoli Enterprise Console®.v Tivoli Software Installation Service User’s Guide, Version 4.0

Provides information about using Tivoli Software Installation Service to installthe IBM Tivoli Monitoring for Databases: DB2 software.

Related publicationsThe following documents also provide useful information:v DB2 System Monitor Guide and Reference

Provides information about how to collect different kinds of information aboutdatabases and the database manager. This book explains how to use theinformation to understand database activity, improve performance, anddetermine the causes of problems.

v DB2 Administration Guide: Planning

Provides an overview of DB2 database concepts, information about design issues(such as logical and physical database design), and a discussion of highavailability.

v DB2 Administration Guide: Implementation

Provides information about DB2 implementation issues such as implementingyour design, accessing databases, auditing, backup, and recovery.

The Tivoli Glossary includes definitions for many of the technical terms related toTivoli software. The Tivoli Glossary is available, in English only, at the followingWeb site:

http://www.tivoli.com/support/documents/glossary/termsm03.htm

Accessing softcopy publicationsThe publications for this product are available in PDF and HTML formats throughthe following media:v IBM Tivoli Monitoring for Databases: DB2, Version 5.1.0: Documentation CD,

LK3T-8517-00The Documentation CD contains all of the English language publications for thisproduct, except for the Web-only limitations and workarounds supplements. Toaccess the publications, use a Web browser to open the start.html file, which islocated in the root directory of the CD.

v IBM Tivoli Monitoring for Databases: DB2, Version 5.1.0: NLS Documentation CD,LK3T-8611-00The NLS (national language support) Documentation CD contains both Englishand non-English language publications for this product, except for the Web-onlylimitations and workarounds supplements. To access the publications, use a Webbrowser to open the start.html file, which is located in the root directory of theCD.

v Tivoli Information Center

About this guide vii

http://www.tivoli.com/support/documents/glossary/termsm03.htm

IBM posts all publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Information Center Website. The Tivoli Information Center is located at the following Web address:http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

Click the IBM Tivoli Monitoring for Databases: DB2 link to access the productlibrary.

Using the guide onlineThis document is available on the IBM Tivoli Monitoring for Databases, Version 5.1.0:Documentation CD, LK3T-8517–00 in PDF and HTML formats. Refer to thereadme.txt file on the CD for instructions on downloading the Acrobat Reader,Version 3.0 or later, to view, save, and print the manual.

Use your HTML browser to open the start.html file on the CD to access the .htmldocumentation files. Every navigation page also includes a link at the bottom todownload the Acrobat reader for viewing, saving, and printing the files.

Viewing online helpOnline help is available in several forms:v Desktop — Access online help by clicking the Help buttons in dialog boxes.v Commands — You can desplay command syntax and parameter information for

command line interface (CLI) commands by typing the name of the command ata command prompt and pressing the Enter key.

v Management Console — Access help by pressing the F1 key in the ManagementConsole.

Ordering publicationsYou can order hardcopy publications online from the following IBM PublicationsCenter Web site:

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

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968v In other countries, for a list of telephone numbers, see the following Web site:

http://www.tivoli.com/inside/store/lit_order.html

Providing feedback about publicationsIf you have comments or suggestions about Tivoli products and documentation,complete the customer feedback survey at the following Web site:

http://www.tivoli.com/support/survey/

viii IBM Tivoli Monitoring for Databases: DB2: Reference Guide



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

http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey/

AccessibilityAccessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

For additional information, see the Accessibility Appendix in IBM Tivoli Monitoringfor Databases: DB2 User’s Guide.

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact IBM CustomerSupport for Tivoli products. See the Tivoli Customer Support Handbook at thefollowing Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Customer Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv What information you should gather before contacting Customer Support

Conventions used in this guideThis book uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

Typeface conventionsThe following typeface conventions are used in this book:

Bold Lowercase and mixed-case commands, command options, file andpath names, and flags that appear within text appear like this, inbold type.

Graphical user interface elements (except for titles of windows anddialogs) and names of keys also appear like this, in bold type.

Italic Variables, values you must provide, new terms, and words andphrases that are emphasized appear like this, in italic type.

Monospace Commands, command options, and flags that appear on a separateline, code examples, output, and message text appear like this, inmonospace type.

Names of text strings you must type, when they appear withintext, names of Java™ methods and classes, and HTML and XMLtags also appear like this, in monospace type.

Operating system-dependent variables and pathsThis book uses the UNIX convention for specifying environment variables and fordirectory notation.

About this guide ix

http://www.tivoli.com/support/handbook/

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) indirectory paths.

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

x IBM Tivoli Monitoring for Databases: DB2: Reference Guide

Chapter 1. Introduction

This book is a reference guide designed for use with the procedures described inthe IBM Tivoli Monitoring for Databases: DB2 User’s Guide. It provides alphabeticallistings and detailed descriptions of the following software functions:v Resource modelsv Tasksv Server commands

Running Tivoli commandsYou can perform system operations from a UNIX or Windows NT command lineinterface (CLI) in addition to using the Tivoli desktop. Operations that you runfrom the command line are referred to as CLI commands.

Consider using the command line interface rather than the graphical user interfaceto invoke a Tivoli management application operation in the followingcircumstances:v You do not have access to a graphical user interface, such as when you dial in

over a modem.v You want to group a number of operations together inside a shell script.v You want to use accessibility tools that require text-based input of commands.

All Tivoli CLI commands begin with the letter w to identify them as Tivolicommands. Command names use a w+verb+object syntax. Example: Use thewdmrm command to add or remove a resource model.

Most Tivoli commands run within a bash shell on a managed node or on a Tivolimanagement region server. A shell is a command interpreter that enables theoperating system to process commands. You can run commands from a shellcommand line or include them in shell scripts on UNIX or Windows NT operatingsystems. A Tivoli management region server is a Tivoli server and the set of clientsthat it serves. A Tivoli management region addresses the physical connectivity ofresources whereas a policy region addresses the logical organization of resources.

Before running Tivoli commands, you must set the Tivoli environment variables forthe shell. The managed node or Tivoli management region server installationprocess supplies the scripts to set the Tivoli environment variables. The followingsections of this guide contain descriptions of the procedures to run these scripts:“Setting the Tivoli environment on UNIX operating systems” on page 3 and“Setting the Tivoli environment on Windows NT operating systems” on page 3.

You must also have the appropriate Tivoli authorization role for running eachcommand. Refer to the reference information for each command to see the requiredauthorization role.

Note: A few Tivoli commands can run on an endpoint. To set the Tivolienvironment variables on an endpoint, see “Establishing the Tivolienvironment on an endpoint” on page 3.

1

Running Tivoli commands on UNIX operating systemsThe UNIX operating systems contain shells. Tivoli commands can run in theBourne, Korn, C, and bash shells. The Bourne shell is the standard UNIX shell.Every UNIX system includes the Bourne shell. The Korn shell supports the featuresof the Bourne shell and has extensions applicable only to the Korn shell. The Cshell name comes from the C programming language syntax. The bash shellsupports many features of the UNIX shells. Both UNIX and Windows NT systemsuse the bash shell.

Running Tivoli commands on Windows NT operating systemsWhen you install a Windows NT managed node or Windows NT Tivolimanagement region server, the installation process copies the bash shell executablefile to the machine. The bash shell supports many UNIX commands and UNIXcommand syntax. An example is the forward slash (/) for the directory separator.The bash shell supports the features of the Bourne shell plus it has someextensions applicable only to the bash shell.

Note: You can use the Windows NT MS-DOS shell instead of the bash shell to runmost Tivoli commands (after you set the Tivoli environment variables withthe %SystemRoot%\system32\drivers\etc\Tivoli\setup_env command).However, some commands and Tivoli tasks may require a bash shell to runsuccessfully. All examples of Tivoli commands in Tivoli publications usebash shell syntax.

Where to find additional information about shellsThe following lists include resources where you can find additional informationabout the various shells. These resources were available at the time the lists werecreated. The lists do not show all of the material that is available, and Tivoli doesnot provide opinions or recommendations about any of these resources.

UNIX shells:

v UNIX in a Nutshell: A Desktop Quick Reference for System V Release 4 and Solaris 7(O’Reilly Nutshell handbook) by Arnold Robbins. ISBN: 1-56592-427-4.

v Portable Shell Programming: An Extensive Collection of Bourne Shell Examples byBruce Blinn. ISBN: 0-13-451494-7.

v Learning the Korn Shell (O’Reilly Nutshell handbook) by Bill Rosenblatt and MikeLoukides. ISBN: 1-56592-054-6.

v UNIX C Shell Desk Reference by Martin Arick. ISBN: 0-47-155680-7.

Bash shell:

v Learning the bash Shell (O’Reilly Nutshell handbook) by Cameron Newham andBill Rosenblatt. ISBN: 1-56592-347-2.

v A Brief Introduction to the bash Shell by Jane Anna Langley.http://www.cs.ups.edu/acl/unix_talk/bash.html

v Bash FAQ (GNU documentation). http://www.delorie.com/gnu/docs/bash/FAQv Bash Reference Manual (GNU documentation).

http://www.gnu.org/manual/bash/index.htmlv bash command reference information (GNU documentation).

http://www.delorie.com/gnu/docs/bash/bash.1.html

2 IBM Tivoli Monitoring for Databases: DB2: Reference Guide

Establishing the Tivoli environment within a shellWhen you install a managed node or Tivoli management region server, theinstallation process supplies shell setup scripts. You use these scripts to set theenvironment variables needed for running Tivoli commands.

Setting the Tivoli environment on UNIX operating systemsThe following steps describe how to set the Tivoli environment within a UNIXshell:1. Log in to a UNIX managed node or Tivoli management region server.2. Run the appropriate setup script for the shell.

For the Bourne, Korn, or bash shell, run the following command:. /etc/Tivoli/setup_env.sh

For the C shell, run the following command:source /etc/Tivoli/setup_env.csh

Setting the Tivoli environment on Windows NT operatingsystemsThe following steps describe how to set the Tivoli environment and start a bashshell on Windows NT.1. Log in to a Windows NT managed node or Tivoli management region server.2. Open a command window.3. Run the following command in the command window to set Tivoli

environment variables:%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

4. Run one of the following commands in the command window to start the bashshell:sh

—OR—bash

Establishing the Tivoli environment on an endpointWhen you install an endpoint, the installation process supplies setup scripts. Usethese scripts to set the environment variables required for running Tivolicommands on an endpoint.

The following steps describe how to set the Tivoli environment on an endpoint:1. Log in to an endpoint.2. Open a command window.3. Run the appropriate setup script in the command window. The following table

contains setup scripts for the different endpoint operating systems.

Table 1. Setup scripts for endpoint operating systems

OperatingSystem Setup Script Location Setup Script Name

AIX, Solaris /etc/Tivoli/lcf/endpoint_label lcf_env.sh (for Bourne, Korn, andbash shells)

—OR—

lcf_env.csh (for C shell)

Chapter 1. Introduction 3

Table 1. Setup scripts for endpoint operating systems (continued)

OperatingSystem Setup Script Location Setup Script Name

Windows NT %SystemRoot%\Tivoli\lcf\endpoint_label

lcf_env.cmd (for MS-DOS) orlcf_env.sh (for bash shell)

Tivoli command syntaxThe following special characters define Tivoli command syntax:

[ ] Identifies elements that are optional. Required elements do not havebrackets around them.

... Indicates that you can specify multiple values for the previous element.Separate multiple values by a space, unless otherwise directed bycommand information.

If the ellipsis for an element follows a closing bracket, use the syntaxwithin the brackets to specify multiple values. For example, to specify twoadministrators for the option [–a admin]..., use –a admin1 –a admin2.

If the ellipsis for an element is within the brackets, use the syntax of thelast element to specify multiple values. For example, to specify two hostsfor the option [–h host...], use –h host1 host2.

| Indicates mutually exclusive information. You can use the element oneither the left or right of the vertical bar.

{ } Delimits a set of mutually exclusive elements when a command requiresone of them. Brackets ([ ]) are around elements that are optional.

In addition to the special characters, Tivoli command syntax uses the typefaceconventions described in the Preface of this document.

The following examples illustrate the typeface conventions used in Tivolicommand syntax:v wcrtpr [–a admin]... [–s region] [–m resource]... name

The name argument is the only required element for the wcrtpr command. Thebrackets around the options indicate they are optional. The ellipsis after the –aadmin resource option means that you can specify multiple administratorsmultiple times. The ellipsis after the –m resource option means that you canspecify multiple resources multiple times.

v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}The –f, –i, and object elements are mutually exclusive. Braces that surroundelements indicate that you are including a required element. If you specify theobject argument, you can specify more than one object.

Common parametersThis section describes the names used to refer to DB2 servers, Tivoli endpoints,and hosts. For detailed information on IBM Tivoli Monitoring for Databases: DB2objects, see the IBM Tivoli Monitoring for Databases: DB2 User’s Guide.

DB2 Server Object NameIBM Tivoli Monitoring for Databases: DB2 assigns the DB2 server objectname to the DB2 server when installing the server using standard DB2


procedures. This name is usually a string comprised of a server anddomain, such as DB21/Org. The variable for this name is ServerObjectName.

Endpoint NameIBM Tivoli Monitoring for Databases: DB2 assigns the endpoint label whencreating the endpoint within the Tivoli environment. Some IBM TivoliMonitoring for Databases: DB2 commands use this label, but an IBM TivoliMonitoring for Databases: DB2 command cannot assign or modify thelabel. This label is usually a string, such as Endpoint1. The variable for thislabel is EndpointName.

Host NameThe host name is the name that is assigned to the server within thenetwork. Some IBM Tivoli Monitoring for Databases: DB2 commands usethis name, but an IBM Tivoli Monitoring for Databases: DB2 commandcannot assign or modify the name. The network determines the format ofthis name. The name might be a string, such as acme.sp.dynamite.com, oran IP address, such as 123.123.123.1. The variable for this label isHostName. Type hostname at the command line to determine the hostname.

Chapter 1. Introduction 5


Chapter 2. DB2 resource models

This chapter contains detailed information about the DB2 resource models for IBMTivoli Monitoring for Databases: DB2. DB2 resource models capture and returninformation, such as database status and server availability, about a resource orsoftware application in the Tivoli management environment. You can change manyof the settings for a resource model to customize it for your monitoring needs.

In this reference guide, a section for each resource model describes theconfiguration of the resource model by covering the following information,including the settings that you can change:

DescriptionPurpose of the resource model and a table that contains an overview of theresource model. The overview table contains the following informationabout the resource model:v Internal name

Name of the resource model as you use it in the command line.v Category

Type of operating system on which the resource model runs.v Indications

List of indications for the resource model. A resource model generates anindication if certain conditions implied by the resource model settingsare not satisfied in a given cycle. The resource model uses an algorithmto determine the combination of settings that generates an indication.

v Tasks and built-in actionsList of tasks and built-in actions for the resource model, if any. For anyevent, recovery actions, such as Tivoli Management Framework tasks orbuilt-in actions, can be run automatically. The actions can take positivesteps to remedy the situation, and can ensure that information about theevent is distributed to the appropriate authorities or entities.

v Default cycle timeSpecifies the default cycle time for the resource model. Cycle time is theduration of the interval within which a resource model gathers data.Each of the resource models supplied with the software has a defaultcycle time, which you can modify according to your needs.

Target managed resourceName of the managed resource (endpoint, server, and so on) to which thisresource model is relevant.

Indications and eventsInformation about all of the indications for the resource model in tableformat and a section of more specific information about each indication.

The table contains the following information for each indication:v Event

An event verifies the persistence of a given indication by eliminatingunrepresentative peaks and troughs for the indication.

v Default severity

7

Indicates how serious an event is if it is triggered, for example fatal,critical, warning, harmless, or minor.

v Clearing eventsSpecifies whether the resource model has clearing events: Yes or No. Aclearing event is a resource model function that, if enabled, allows IBMTivoli Monitoring to close an error event when the circumstances thatcaused the event are no longer present. Clearing events can be processedby the Tivoli Enterprise Console server and by Tivoli Business SystemsManager.

v PagePage number where the indication is described in this guide.

Each section about a specific indication contains the following information:v When the resource model sends the indication and whyv List of the attributes for the indication and notation regarding which

attributes are keysv Table that describes the following default settings for the indication:

– Send indications to Tivoli Enterprise ConsoleSpecifies whether the resource model sends indications to TivoliEnterprise Console: YES or NO. If YES and Tivoli Enterprise Consoleis installed, IBM Tivoli Monitoring sends indications to TivoliEnterprise Console. If Tivoli Business Systems Manager is installed,Tivoli Enterprise Console sends the indications to Tivoli BusinessSystems Manager.

– Send indications to Tivoli Business Systems ManagerSpecifies whether IBM Tivoli Monitoring sends indications to TivoliBusiness Systems Manager. The default is NO. Do not change theconfiguration of the indication to send events to Tivoli BusinessSystems Manager.

– OccurrencesThe number of occurrences refers to the number of cycles duringwhich an indication occurs for a given resource model.

– HolesThe number of holes refers to the number of cycles during which anindication does not occur for a given resource model. In other words,the number of cycles during which none of the conditions specifiedfor the generation of the indication are met.

– Associated tasks and built-in actionsList of tasks and built-in actions associated with the indication.

ThresholdsList of the thresholds, if any, for the resource model in a table format witha short description and default value for each threshold associated with theresource model. A threshold is a named property of the resource with adefault value that you can modify. Typically, the value of a thresholdrepresents a significant reference level of a performance-related entity,which, if exceeded or not reached, a system administrator might want toknow about.

ParametersList of parameters, if any, for the resource model in a table format with ashort description and default value for each threshold associated with theresource model. A parameter can take the form of a list of strings, a list of


numeric values, a list of predetermined Boolean values from which youcan make any combination of selections, or a choice list of mutuallyexclusive alternatives.

Tasks and built-in actionsList of tasks and built-in actions including a description of each one.

LoggingA table shows the name of the managed resource, context, and propertiesthat the resource model logs with key properties noted. The resourcemodel does not log data by default. You can enable logging to collect datafor any endpoint and write it in a local database. You can store raw oraggregated data and view it through the Web Health Console.

Return codesInformation that the resource model returns such as status or availability.

CLI exampleExample of the syntax for a resource model that illustrates some of thevariable options of the wdmeditprf command that are specific to theresource model such as the name of the resource model, thresholds,parameters, parameter values, and events.

See the Customizing resource models chapter of the IBM Tivoli Monitoring forDatabases: DB2 User’s Guide for more information on resource models and resourcemodel procedures.

Table 2 contains the internal name and a brief description of each DB2 resourcemodel. The sections of information about each resource model follow the table inalphabetical order.

Table 2. DB2 resource models

Resource model name Internal name Description

“DB2 Agent” on page 12 DB2Agents Monitors database agents andtheir related applications.

“DB2 Apply ReplicationStatus” on page 21

DB2ApplyReplication Monitors the status of theDB2 Apply component fromIBM Replication.

“DB2 Buffer Pools” on page27

DB2BufferPool Monitors buffer pool input,output, and utilization on adatabase, tablespace, andapplication level.

“DB2 Buffer Pool/ExtendedStorage” on page 58

DB2BufferPoolExtStorage Provides extended storagemonitoring of buffer poolextended storage at thedatabase and tablespace levelby monitoring the ratio, as apercentage, of data + indexpages copied from extendedstorage to pages copied toextended storage during themonitoring interval.

“DB2 Catalog Cache” onpage 64

DB2CatalogCache Monitors the effectiveness ofthe catalog cache.

Chapter 2. DB2 resource models 9

Table 2. DB2 resource models (continued)


“DB2 CPU Utilization” onpage 68

DB2CpuUtilization Monitors the total DB2system and user centralprocessing unit time used bythe applications databasemanager agents.

“DB2 Database Activity” onpage 73

DB2DatabaseStatus Monitors general activity andavailability of DB2 at thedatabase level.

“DB2 Direct IO” on page 95 DB2DirectIO Monitors non-buffered inputand output at the database,tablespace, and applicationlevels.

“DB2 Fast CommunicationManager” on page 113

DB2FCMActivity Monitors the FastCommunication Manager’skey health indications.

“DB2 Host Throughput” onpage 123

DB2HostThroughput Monitors the DB2 hostthroughput.

“DB2 Instance Status” onpage 131

DB2InstanceStatus Monitors the availability ofthe DB2 Instance.

“DB2 Locks and Deadlocks”on page 136

DB2Locks Monitors locks and deadlocksat the database andapplication levels.

“DB2 Lock Waits” on page157

DB2LockWaits Monitors the change in thenumber of lock waits withina database as well as thepercentage of applications ina lock wait state.

“DB2 Logging” on page 165 DB2Logging Monitors the activity of DB2logging.

“DB2 Package Cache” onpage 176

DB2PackageCache Monitors the package cachethat stores the package andsection information requiredfor the execution of dynamicand static SQL statements.

“DB2 Replication Capture”on page 183

DB2ReplicationCapture Monitors the status of theDB2 Capture component fromIBM Replication.

“DB2 SAP TablespaceUsage/Status” on page 188

DB2SAPTablespaceUsageStatusMonitors DB2 SAP tablespaceusage and status.

“DB2 Sorting” on page 201 DB2Sorts Monitors the sorting activityof the database manager aswell as at the database andapplication levels.

“DB2 SQL Cursor Activity”on page 213

DB2Cursor Monitors the total number oflocal and remote open andblocking cursors that arecurrently open for thedatabase.

“DB2 SQL StatementActivity” on page 218

DB2SQLStatementActivity Monitors the DB2 StructuredQuery Language statementactivity.


Table 2. DB2 resource models (continued)


“DB2 Table Activity” onpage 228

DB2TableActivity Logs the rate, per second, atwhich rows in a table areread and changed during themonitoring interval.

“DB2 Table ApplyReplication” on page 231

DB2TableApplyReplication Monitors the status of thetables in the DB2 Applycomponent from IBMReplication.


DB2 Agent

DescriptionMonitors database agents and their related applications. An agent is a process orthread that carries out the requests made by a client application. Each connectedapplication is served by exactly one coordinator agent and possibly by a set ofsubagents. Subagents are used for parallel SQL processing in partitioned databasesand on System Modification Program (SMP) machines.

For each database transaction (unit of work) that occurs when the client isconnected to a database, an agent requests permission from the database managerto process the transaction. The database manager grants permission by giving theagent a processing token. Only agents with tokens are permitted to execute a unitof work against a database. The number of tokens available is controlled by the<max_coordagents> configuration parameter. If a token is not available, the agentwaits until one is available.

The DB2 Agent resource model monitors the following information:v The percentage of registered agents that are waiting to execute a transaction.v The number of times that agents are created when there are no more free agents

available in the agent pools within the database manager instance.v The ratio of the maximum number of subagents associated with the application

to the number of agents that are stolen from the application by DB2 to work ona different application.

See the DB2 System Monitor Guide and Reference manual for detailed informationabout DB2 agents.

Resource model overview

Internal name DB2Agents

Category DB2

Indications Agent Creation Ratio too high occurs when theAgentCreationRatio counter exceeds the AgentCreationRatioupper bound threshold.

Agent Creation Ratio too low occurs when theAgentCreationRatio counter is lower than theAgentCreationRatio lower bound threshold.

High Application Workload occurs when the ratio of themaximum number of subagents associated with anapplication to the number of agents stolen from theapplication was too low during a monitoring interval.

Percent Agents Waiting too high occurs when thepercentage of agents waiting exceeds the Percent AgentsWaiting upper bound threshold.

Tasks and built-in actions None

Default cycle time 1800 seconds

Target managed resourceDB2DatabaseManager, DB2PartitionManager


Indications and eventsThe following table summarizes the indications for this resource model, the eventsassociated with the indications, the default severity of the events, and where tofind a detailed description of the indication.

Indication Generated event Defaultseverity

Clearingevents

Page

Agent CreationRatio too high

DB2_High_AgentCreationRatio Warning No 13

Agent CreationRatio too low

DB2_Low_AgentCreationRatio Warning No 14

HighApplicationWorkload

DB2_High_ApplicationWorkload Warning No 15

Percent AgentsWaiting toohigh

DB2_High_PctAgentsWaiting Critical No 16

Agent Creation Ratio too high indicationOccurs when the AgentCreationRatio counter exceeds the AgentCreationRatioupper bound threshold. A high ratio indicates that the overall workload for thisnode is too high. Lower the maximum number of coordination agents specified bythe <maxcagents> configuration parameter or redistribute data among the nodes toadjust the workload.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Agent Creation Ratio on DB2 Instance <db2InstanceName> is<AgentCreationRatio>, which is greater than <UpperBound>.

If you have Tivoli Business Systems Manager configured for your system, TivoliEnterprise Console forwards the message to Tivoli Business Systems Manager.

You can check the health of this resource model in the IBM Tivoli Monitoring WebHealth Console. For more information, see the IBM Tivoli Monitoring Web HealthConsole documentation.

The indication has the following attributes:

db2InstanceNameSpecifies the name of the DB2 instance that contains the database.

AgentCreationRatioSpecifies the number of times that agents are created when there are nomore free agents available in the agent pools within the database managerinstance.

UpperBoundSpecifies the indication’s threshold value.

This indication has the following threshold:v Agent Creation Ratio upper bound

For more information about this threshold, see “Thresholds” on page 17.


The following table describes the default settings for this indication.

Setting Default value

Send indications to Tivoli Enterprise Console No

Send indications to Tivoli Business SystemsManager

No

Occurrences 5

Holes 3

Associated tasks and built-in actions 0

Note: If you have Tivoli Business Systems Manager configured for your systems,Tivoli Enterprise Console automatically forwards events to Tivoli BusinessSystems Manager. Do not change the configuration of the indication to sendevents to Tivoli Business Systems Manager.

Agent Creation Ratio too low indicationOccurs when the AgentCreationRatio counter is lower than the AgentCreationRatiolower bound threshold. A low ratio indicates that the <num_poolagents>configuration parameter is set too high and that some of the agents in the pool arerarely used and wasting system resources. The <num_poolagents>configurationparameter defines the agent pool size. The number of agents in the agent poolcannot exceed the <num_poolagents> value.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Agent Creation Ratio on DB2 Instance <db2InstanceName> is<AgentCreationRatio>, which is lower than <LowerBound>.




db2InstanceNameSpecifies the name of the DB2 instance that contains the database.

AgentCreationRatioSpecifies the number of times that agents are created when there are nomore free agents available in the agent pools within the database managerinstance.

LowerBoundSpecifies the indication’s threshold value.

This indication has the following threshold:v Agent Creation Ratio lower bound







No

Occurrences 5

Holes 3



High Application Workload indicationOccurs when the ratio of the maximum number of subagents associated with anapplication to the number of agents stolen from the application that was too lowduring a monitoring interval. A stolen agent is an idle agent associated withanother application that DB2 tries to take when an agent cannot be created becausemaxagents has been reached. The <maxagents> configuration parameter defines themaximum number of agents, regardless of type, that can exist for an instance.

Increase the num_poolagents configuration parameter or redistribute the databaseto other nodes to adjust the number of agents.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Application Workload on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Application <db2AppName>,Application ID <db2AppID is <WorkLoad>, which is greaterthan <UpperBound>.




db2DatabaseSpecifies the name of the DB2 database.

db2InstanceSpecifies the name of the DB2 instance that contains the database.

db2NodeSpecifies the name of the DB2 node.

db2AppNameSpecifies the name of the DB2 application.

db2AppIDSpecifies the unique application identification that is generated when theapplication connects to the database.


WorkLoadThe ratio of the maximum number of subagents associated with thisapplication to the number of agents that are stolen from the application byDB2 to work on a different application.


This indication has the following threshold:v High Application Workload lower bound






No

Occurrences 4

Holes 2



Percent Agents Waiting too high indicationOccurs when the percentage of agents waiting exceeds the Percent Agents Waitingupper bound threshold. If you receive a high percentage, increase the <dbms:maxcagents> configuration parameter to improve concurrency in the databasemanager.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of Agents Waiting on DB2 Instance <db2Instance> is<PctAgentsWaiting>, which is greater than <UpperBound>.





PctAgentsWaitingSpecifies the percentage of registered agents that are waiting to execute atransaction. The number of agents waiting for token or maximum agentsregistered multiplied by 100 defines this value.



This indication has the following threshold:v Percent Agents Waiting upper bound






No

Occurrences 5

Holes 3



ThresholdsThe following table lists the thresholds that can be set for the DB2 Agents resourcemodel. For each threshold it shows the name, a short description, and the defaultvalue:

Threshold Description Defaultvalue

Agent Creation Ratiolower bound

The number of times that agents are createdwhen there are no more free agents available inthe agent pools within the database instancemanager. The ratio of the number of agentscreated from pool to the number of agentsassigned from pool multiplied by 100 defines thisvalue.

A low ratio indicates that the <num_poolagents>configuration parameter is set too high and thatsome of the agents in the pool are rarely usedand wasting system resources.

20



Agent Creation Ratioupper bound

The number of times that agents are createdwhen there are no more free agents available inthe agent pools within the database instancemanager. The value is defined as the ratio of thenumber of agents created from pool to thenumber of agents assigned from pool multipliedby 100.

A high ratio indicates that the overall workloadfor this node is too high. Lower the maximumnumber of coordination agents specified by the<maxcagents> configuration parameter orredistribute data among the nodes to adjust theworkload.

80

High ApplicationWorkload lower bound

The ratio of the maximum number of subagentsassociated with this application to the number ofagents that are stolen from the application byDB2 to work on a different application. A valueless than one indicates that the <num_poolagents>configuration parameter is set too low.

1

Percent Agents Waitingupper bound

The percentage of registered agents that arewaiting to execute a transaction. The value isdefined as agents waiting for a token/maximumagents registered multiplied by 100.

If the percentage is high, increase the <dbmmaxcagents> configuration parameter to improveconcurrency in the database manager.

90

ParametersThe following table lists the parameters that can be set for the DB2 Agents resourcemodel. The table shows the name, a short description, and the default value foreach parameter.

Note: A plus symbol (+) denotes parameters that feature selective logging.Selective logging enables you to choose properties that you want to log. Theselective logging properties are listed in the value field of the Parameterswindow.

Parameter Description Default value

Application Agentproperties to log+

The Application Agent propertiesavailable for logging.

v Application Workload

Instanceproperties to log+

The Instance Agent propertiesavailable for logging.

v Percent Agents Waiting

v Agent Creation Ratio

Tasks and built-in actionsNone

LoggingYou can log data for the properties of the managed resource listed in the followingtable. The table shows the context of the managed resource and the properties that


the resource model logs for the IBM Tivoli Monitoring Web Health Console.

Managed resource Context Properties

DB2Applicaton ApplicationAgentsApplication Workload

The ratio of themaximum numberof subagentsassociated with theapplication to thenumber of agentsthat are stolen fromthe application byDB2 to work on adifferent application.

DB2Application.db2ApplyID*Specifies thesubscriber user IDthat started thisinvocation of theApply program.

db2AppNameSpecifies the nameof the DB2application.

DB2Database.db2Database*Specifies the nameof the DB2 database.

DB2Instance.db2Instance*Specifies the nameof the DB2 instancethat contains thedatabase.

DB2Partition.db2Node*Specifies the nameof the DB2 node.

DB2Instance InstanceAgentsAgent Creation Ratio

Specifies thenumber of timesthat agents arecreated when thereare no more freeagents available inthe agent poolswithin the databasemanager instance.



DB2Instance InstanceAgents (continued)DB2Instance.db2Instance*

Specifies the nameof the DB2 instancethat contains thedatabase.

Percent Agents WaitingSpecifies thepercentage ofregistered agentsthat are waiting toexecute atransaction.

Note: An asterisk (*) denotes a key property.

Return codesNone

CLI exampleThe following example adds the DB2 Agent resource model toMyProfile#MyRegion. This example sets the severity of theDB2_High_InstanceAgents_AgentCreationRatio event to critical.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2Agents -c 600 \-t High_AgentCreationRatio 75.000000 \-e DB2_High_InstanceAgents_AgentCreationRatio -o 3 -h 1 -severity CRITICAL


DB2 Apply Replication Status

DescriptionMonitors the status of the DB2 Apply component from IBM Replication. Replicationis the process of maintaining a defined set of data in more than one location. Itinvolves copying designated changes from one location (a source) to another (atarget), and synchronizing the data in both locations. IBM Replication copiesrelational data from source tables to target tables, which are typically in differentDB2 databases.

IBM Replication uses the Apply program and Capture program components. TheApply program refreshes or updates a target table, depending on the applicablesource-to-target rules. The Capture program reads the DB2 database log or journalrecords to capture data about changes made to source tables.

The Apply program reads data directly from source tables or views to initiallypopulate the target table.

The DB2 Apply Replication Status resource model monitors the followinginformation for Apply availability:v The number of lagging subscriptions for the Apply program. Lagging

subscriptions define the number of your subscriptions that are not processed ontime according to their subscription frequencies and priorities.

v The number of subscriptions that the Apply program failed to replicate.v When the Apply program status shuts down.

See the DB2 Replication Guide and Reference manual for detailed information aboutdata replication in DB2.


Internal name DB2ApplyReplication

Category DB2

Indications Apply Status is down occurs when the Apply ProgramStatus is down.

Failed Subscriptions too high occurs when FailedSubscriptions exceeds the Failed Subscriptions upper boundthreshold.

Lagging Subscriptions too high occurs when LaggingSubscriptions exceeds the Lagging Subscriptions upperbound threshold.



Target managed resourceDB2DatabaseManager




Clearingevents

Page

ApplyStatus isdown

DB2_ApplyStatus_Down Critical Yes 22

FailedSubscriptionstoo high

DB2_High_ApplyReplication_FailedSubscriptions

Warning No 23

LaggingSubscriptionstoo high

DB2_High_ApplyReplication_LaggingSubscriptions

Warning No 24

Apply Status is down indicationOccurs when the Apply Program Status is down.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The DB2 Apply Program is down for DB2 Instance <db2Instance>,Database <db2Database>.






This indication has no thresholds.



Send indications to Tivoli Enterprise Console Yes


Yes

Occurrences 1

Holes 0




Failed Subscriptions too high indicationOccurs when Failed Subscriptions exceeds the Failed Subscriptions upper boundthreshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Failed Subscriptions on DB2 Database <db2Database>,Instance <db2Instance>, Apply ID <db2ApplyID> is<FailedSubscriptions>, which is higher than<UpperBound>.






db2ApplyIDSpecifies the subscriber user ID that started this invocation of the Applyprogram.

FailedSubscriptionsSpecifies the number of subscriptions that the Apply program failed toreplicate.


This indication has the following threshold:v Failed Subscriptions upper bound

For more information about these thresholds, see “Thresholds” on page 25.





Yes

Occurrences 2

Holes 0




Lagging Subscriptions too high indicationOccurs when Lagging Subscriptions exceeds the Lagging Subscriptions upperbound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Lagging Subscriptions on DB2 Database <db2Database>, Instance <db2Instance>,Apply ID <db2ApplyID> is <LaggingSubscriptions>,which is higher than <UpperBound>.







LaggingSubscriptionsSpecifies the number of lagging subscriptions for the Apply program.


This indication has the following threshold:v Lagging Subscriptions upper bound






Yes

Occurrences 2

Holes 0




ThresholdsThe following table lists the thresholds that can be set for the DB2 ApplyReplication Status resource model. For each threshold it shows the name, a shortdescription, and the default value:


Failed Subscriptionsupper bound

If the failed subscriptions exceeds the thresholdvalue often enough, the Failed Subscriptions toohigh indication triggers an event.

5

Lagging Subscriptionsupper bound

If the lagging subscriptions exceeds the thresholdvalue often enough, the Lagging Subscriptionstoo high indication triggers an event.

5

ParametersThe following table lists the parameters that can be set for the DB2 ApplyReplication Status resource model. The table shows the name, a short description,and the default value for each parameter.



Apply IDs tomonitor

A list of Apply IDs to monitor. Thefollowing are options to enter for eachApply ID to monitor:

v Apply ID name for each schema tomonitor

v Wildcard designator, (*), to monitorall Apply IDs

v Combine partial Apply ID namesand use the wildcard designator,(*), to separate

*

Apply propertiesto log+

The replication properties availablefor logging.

v Apply Program Status

v Failed Subscriptions

v Lagging Subscriptions


LoggingYou can log data for the properties of the managed resource listed in the followingtable. The table shows the context of the managed resource and the properties thatthe resource model logs for the IBM Tivoli Monitoring Web Health Console.



DB2Apply Apply ReplicationApply Program Status

Specifies the statusof the ApplyProgram.

Failed SubscriptionsSpecifies thenumber ofsubscriptions thatthe Apply programfailed to replicate.

Lagging SubscriptionsSpecifies thenumber of laggingsubscriptions for theApply program.

db2ApplyID*Specifies thesubscriber user IDthat started thisinvocation of theApply program.




Return codesNone

CLI exampleThe following example adds the DB2 Apply Replication resource model toMyProfile#MyRegion. This example enables aggregated logging for a period of 15minutes with a historical duration period of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2ApplyReplication \-Log -LogEnable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \-t High_FailedSubscriptions 8.000000 \-AddPar Apply_IDs "abc" \-AddPar Apply_IDs "xyz"


DB2 Buffer Pools

DescriptionMonitors buffer pool input, output, and utilization on a database, tablespace, andapplication level. The buffer pool is a storage area where database pages thatcontain table rows or index entries are read and changed. The purpose of thebuffer pool is to improve database system performance. You can access data muchfaster from memory than from a disk. Therefore, the fewer times the databasemanager needs to read from or write to a disk, the better the performance.

The configuration of the buffer pool is the most important area that you can refinebecause most of the data manipulation for applications connected to the databasetakes place there.

The DB2 Buffer Pools resource model monitors the following information:v The total time, in milliseconds, applied to physical synchronous and

asynchronous buffer pool input and output operations for a database.v The rate, per second, of buffer pool input and output operations for databases

and tablespaces.v The average time, in milliseconds, for performing buffer pool input and output

operations for databases and tablespaces.v The average time, in milliseconds, for synchronous data reads or writes for the

tablespace.v The average time, in milliseconds, for processing database read or write requests

that cause data or index pages to be physically read or written from the disk tothe buffer pool.

v The average time, in milliseconds, for processing read or write requests thatcause data or index pages to be physically read or written from disk to bufferpool for the tablespace.

v The average time, in milliseconds, to perform synchronous data reads, writes, orinput and output operations for the database.

v The ratio of buffer pool asynchronous data reads or writes to the total numberof pool reads or writes for the database.

v The ratio of total pool writes to pool reads for a database.v The overall buffer pool hit ratio, as a percentage, for applications and

tablespaces during the monitoring interval.v The application’s and tablespace’s index page hit ratio, as a percentage, for the

buffer pool during the monitoring interval.


Internal name DB2BufferPool

Category DB2

Indications Application Percent Buffer Pool Hits too low occurs whenthe Percentage Buffer Pool Hits is lower than the PercentBuffer Pool Hits lower bound threshold for an application.

Application Percent Index Buffer Pool Hits too low occurswhen the Percentage Index Buffer Pool Hits is lower than thePercent Index Buffer Pool Hits lower bound threshold for anapplication.



Indications (continued) Average Asynchronous Reads Per Pool Read too low occurswhen the Average Asynchronous Reads Per Pool Read islower than the Average Asynchronous Reads Per Pool Readlower bound threshold.

Average Asynchronous Writes Per Pool Write too low occurswhen the Average Asynchronous Writes Per Pool Write is lessthan the Average Asynchronous Writes Per Pool Write lowerbound threshold.

Average Pool Writes Per Pool Read too high occurs whenthe Average Pool Writes Per Pool Read exceeds the AveragePool Writes Per Pool Read upper bound threshold.

Average Synchronous IO Time too high occurs when theAverage Synchronous IO Time exceeds the AverageSynchronous IO Time upper bound threshold.

Average Synchronous Read Time too high occurs when theAverage Synchronous Read Time exceeds the AverageSynchronous Read Time upper bound threshold for any ofthe tablespaces in the tablespace parameter list or at thedatabase level.

Average Synchronous Write Time too low occurs when theAverage Synchronous Write Time exceeds the AverageSynchronous Write Time upper bound threshold.

Database Average Pool IO Time too high occurs when theAverage Pool IO Time exceeds the Average Pool IO Timeupper bound threshold for a database.

Database Average Pool Read Time too high occurs when theAverage Pool Read Time exceeds the Average Pool Read Timeupper bound threshold for a database.

Database Average Pool Write Time too high occurs when theAverage Pool Write Time upper bound threshold is exceededat the database level.

Database Percent Buffer Pool Hits too low occurs when thePercentage Buffer Pool Hits is lower than the Percent BufferPool Hits lower bound threshold for a database.

Database Percent Index Buffer Pool Hits too low occurswhen the Percentage Index Buffer Pool Hits is lower than thePercent Index Buffer Pool Hits lower bound threshold for adatabase.

Tablespace Average Pool IO Time too high occurs when theAverage Pool IO Time exceeds the Average Pool IO Timeupper bound threshold for a tablespace.

Tablespace Average Pool Read Time too high occurs whenthe Average Pool Read Time exceeds the Average Pool ReadTime upper bound threshold for a tablespace.

Tablespace Average Pool Write Time too high indicationoccurs when the Average Pool Write Time upper boundthreshold is exceeded at the tablespace level.

Tablespace Percent Buffer Pool Hits too low occurs whenthe Percentage Buffer Pool Hits is lower than the PercentBuffer Pool Hits lower bound threshold for a tablespace.







Clearingevents

Page

ApplicationPercentBuffer PoolHits too low

DB2_Low_App_PctBufferPoolHits Warning Yes 30

ApplicationPercentIndex BufferPool Hitstoo low

DB2_Low_App_PctIndexHits Warning Yes 31

AverageAsynchronousReads PerPool Readtoo low

DB2_Low_DB_AvgAsyncReadsPerPoolRead Warning Yes 33

AverageAsynchronousWrites PerPool Writetoo low

DB2_Low_DB_AvgAsyncWritesPerPoolWrite Warning Yes 34

AveragePool WritesPer PoolRead toohigh

DB2_High_DB_AvgPoolWritesPerPoolRead Warning Yes 35

AverageSynchronousIO Time toohigh

DB2_High_DB_AvgSyncIOTime Warning Yes 35

AverageSynchronousRead Timetoo high

DB2_High_DB_AvgSyncReadTime Warning Yes 36

AverageSynchronousWrite Timetoo high

DB2_High_DB_AvgSyncWriteTime Warning Yes 37

DatabaseAveragePool IOTime toohigh

DB2_High_DB_AvgPoolIOTime Warning Yes 38



Clearingevents

Page

DatabaseAveragePool ReadTime toohigh

DB2_High_DB_AvgPoolReadTime Warning Yes 39

DatabaseAveragePool WriteTime toohigh

DB2_High_DB_AvgPoolWriteTime Warning Yes 40

DatabasePercentBuffer PoolHits too low

DB2_Low_DB_PctBufferPoolHits Warning Yes 41

DatabasePercentIndex BufferPool Hitstoo low

DB2_Low_DB_PctIndexHits Warning Yes 42

TablespaceAveragePool IOTime toohigh

DB2_High_Tbsp_AvePoolIOTime Warning Yes 43

TablespaceAveragePool ReadTime toohigh

DB2_High_Tbsp_AvgPoolReadTime Warning Yes 44

TablespaceAveragePool WriteTime toohigh

DB2_High_Tbsp_AvgPoolWriteTime Warning Yes 45

TablespacePercentBuffer PoolHits too low

DB2_Low_Tbsp_PctBufferPoolHits Warning Yes 46

Application Percent Buffer Pool Hits too low indicationOccurs when the Percentage Buffer Pool Hits is lower than the Percent Buffer PoolHits lower bound threshold for an application.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The application’s Percent Buffer Pool Hits on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Application Name <db2AppName>,Application ID <db2AppID is <PctBufferPoolHits>, which islower than <LowerBound>.










PctBufferPoolHitsSpecifies the percentage of the hit ratio for the buffer pool during themonitoring interval.


This indication has the following threshold:v Percent Buffer Pool Hits lower bound






Yes

Occurrences 3

Holes 2



Application Percent Index Buffer Pool Hits too low indicationOccurs when the Percentage Index Buffer Pool Hits is lower than the Percent IndexBuffer Pool Hits lower bound threshold for an application.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:


The application’s Percent Index Buffer Pool Hits on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Application Name <db2AppName>,Application ID <db2AppID> is <PctIndexHits>,which is lower than <LowerBound>.









PctIndexHitsSpecifies the percentage of the index page hit ratio for the buffer poolduring the monitoring interval.


This indication has the following threshold:v Percent Index Buffer Pool Hits lower bound






Yes

Occurrences 3

Holes 2




Average Asynchronous Reads Per Pool Read too low indicationOccurs when the Average Asynchronous Reads Per Pool Read is lower than theAverage Asynchronous Reads Per Pool Read lower bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Asynchronous Reads Per Pool Read on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgAsyncReadsPerPoolRead>, which islower than <LowerBound>.







AvgAsyncReadsPerPoolReadSpecifies the ratio of buffer pool asynchronous data reads to the totalnumber of pool reads.


This indication has the following threshold:v Average Asynchronous Reads Per Pool Read lower bound






No

Occurrences 1

Holes 0




Average Asynchronous Writes Per Pool Write too low indicationOccurs when the Average Asynchronous Writes Per Pool Write is less than theAverage Asynchronous Writes Per Pool Write lower bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Asynchronous Writes Per Pool Write on DB2 Database<db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgAsyncWritesPerPoolWrite>, which islower than <LowerBound>.







AvgAsyncWritesPerPoolWriteSpecifies the ratio of data and index buffer pool asynchronous writes to thetotal number of pool writes.


This indication has the following threshold:v Average Asynchronous Writes Per Pool Write lower bound






No

Occurrences 1

Holes 0




Average Pool Writes Per Pool Read too high indicationOccurs when the Average Pool Writes Per Pool Read exceeds the Average PoolWrites Per Pool Read upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Pool Writes Per Pool Read on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgPoolWritesPerPoolRead>,which is higher than <UpperBound>.







AvgPoolWritesPerPoolReadSpecifies the ratio of total pool writes to pool reads.


This indication has the following threshold:v Average Pool Writes Per Pool Read upper bound






No

Occurrences 1

Holes 0



Average Synchronous IO Time too high indicationOccurs when the Average Synchronous IO Time exceeds the Average SynchronousIO Time upper bound threshold.


When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Synchoronous IO Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgSyncIOTime>,which is higher than <UpperBound>.







AvgSyncIOTimeSpecifies the average time to perform synchronous input and outputoperations.


This indication has the following threshold:v Average Synchronous IO Time upper bound






No

Occurrences 1

Holes 0



Average Synchronous Read Time too high indicationOccurs when the Average Synchronous Read Time exceeds the AverageSynchronous Read Time upper bound threshold for any of the tablespaces in thetablespace parameter list or at the database level.


When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Synchronous Read Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgSyncReadTime>,which is higher than <UpperBound>.







AvgSyncReadTimeSpecifies the average time to perform synchronous data reads.


This indication has the following threshold:v Average Synchronous Read Time upper bound






No

Occurrences 1

Holes 0



Average Synchronous Write Time too high indicationOccurs when the Average Synchronous Write Time exceeds the AverageSynchronous Write Time upper bound threshold.



The Average Synchronous Write Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgSyncWriteTime>,which is higher than <UpperBound>.







AvgSyncWriteTimeSpecifies the average time to perform synchronous data writes.


This indication has the following threshold:v Average Synchronous Write Time too low






No

Occurrences 1

Holes 0



Database Average Pool IO Time too high indicationOccurs when the Average Pool IO Time exceeds the Average Pool IO Time upperbound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Pool IO Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgPoolIOTime>,which is higher than <UpperBound>.








AvgPoolIOTimeSpecifies the average time for performing buffer pool input and outputoperations.


This indication has the following threshold:v Average Pool IO Time upper bound






No

Occurrences 1

Holes 0



Database Average Pool Read Time too high indicationOccurs when the Average Pool Read Time exceeds the Average Pool Read Timeupper bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Pool Read Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgPoolReadTime>,which is higher than <UpperBound>.








AvgPoolReadTimeSpecifies the average time for processing read requests that cause indexpages to be physically read from disk to buffer pool.


This indication has the following threshold:v Average Pool Read Time upper bound






No

Occurrences 1

Holes 0



Database Average Pool Write Time too high indicationOccurs when the Average Pool Write Time upper bound threshold is exceeded atthe database level.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Pool Write Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgPoolWriteTime>,which is higher than <UpperBound>.








AvgPoolWriteTimeSpecifies the average time for processing write requests that cause data orindex pages to be physically written from buffer pool to disk.


This indication has the following threshold:v Average Pool Write Time upper bound






No

Occurrences 1

Holes 0



Database Percent Buffer Pool Hits too low indicationOccurs when the Percentage Buffer Pool Hits is lower than the Percent Buffer PoolHits lower bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Percent Buffer Pool Hits on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <PctBufferPoolHits>,which is lower than <LowerBound>.








PctBufferPoolHitsSpecifies the percentage of the database’s hit ratio for the buffer poolduring the monitoring interval.








Yes

Occurrences 3

Holes 2



Database Percent Index Buffer Pool Hits too low indicationOccurs when the Percentage Index Buffer Pool Hits is lower than the Percent IndexBuffer Pool Hits lower bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Percent Index Buffer Pool Hits on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <PctIndexHits>,which is lower than <LowerBound>.








PctIndexHitsSpecifies the database’s index page hit ratio, as a percentage, for the bufferpool during the monitoring interval.


This indication has the following threshold:v Percent Index Buffer Pool Hits lower bound






Yes

Occurrences 3

Holes 2



Tablespace Average Pool IO Time too high indicationOccurs when the Average Pool IO Time exceeds the Average Pool IO Time upperbound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Pool IO Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Tablespace name <db2TbspName> is<AvgPoolIOTime>, which is higher than <UpperBound>.








db2TbspNameSpecifies the name of the DB2 tablespace.

AvgPoolIOTimeSpecifies the average time for performing buffer pool input and outputoperations.


This indication has the following threshold:v Average Pool IO Time upper bound






No

Occurrences 1

Holes 0



Tablespace Average Pool Read Time too high indicationOccurs when the Average Pool Read Time exceeds the Average Pool Read Timeupper bound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Pool Read Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Tablespace Name <db2TbspName>is <AvgPoolReadTime>, which is higher than <UpperBound>.









AvgPoolReadTimeSpecifies the average time for processing read requests that cause indexpages to be physically read from disk to buffer pool.


This indication has the following threshold:v Average Pool Read Time upper bound






No

Occurrences 1

Holes 0



Tablespace Average Pool Write Time too high indicationOccurs when the Average Pool Write Time upper bound threshold is exceeded atthe tablespace level.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Pool Write Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Tablespace Name <db2TbspName>is <AvgPoolWriteTime>, which is higher than <UpperBound>.









AvgPoolWriteTimeSpecifies the average time for processing write requests that cause data orindex pages to be physically written from buffer pool to disk.


This indication has the following threshold:v Average Pool Write Time upper bound






No

Occurrences 1

Holes 0



Tablespace Percent Buffer Pool Hits too low indicationOccurs when the Percentage Buffer Pool Hits is lower than the Percent Buffer PoolHits lower bound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Percent Buffer Pool Hits on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Tablespace Name <db2TbspName>is <PctBufferPoolHits>, which is lower than <LowerBound>.









PctBufferPoolHitsSpecifies the percentage of the tablespace’s hit ratio for the buffer poolduring the monitoring interval.








Yes

Occurrences 3

Holes 2



ThresholdsThe following table lists the thresholds that can be set for the DB2 Buffer Poolsresource model. For each threshold it shows the name, a short description, and thedefault value:



Average AsynchronousReads Per Pool Readlower bound

The ratio, as a percentage, of buffer poolasynchronous data reads to the total number ofpool reads for the database. Log the returnedvalue to monitor the prefetchers and the<num_ioservers> configuration parameter.

When there is not enough input and outputservers to prefetch data into the buffer, thedatabase agents spend extra time on physicalreads and return a low value. Increase the valueof the <num_ioservers> configuration parameter toincrease the number of input and output. If toomany servers are allocated, the systemperformance does not reduce because the extrainput and output servers are not used.

If the current value is less than the thresholdvalue often enough, the Average AsynchronousReads Per Pool Read too low indication triggersan event.

50

Average AsynchronousWrites Per Pool Writelower bound

The ratio, as a percentage, of data and indexbuffer pool asynchronous writes to the totalnumber of pool writes for the database. Log thereturned value to monitor the page cleaners andthe <num_iocleaners> configuration parameter.

For a low returned value, increase the number ofinput and output cleaners by increasing the valueof the <num_iocleaners> parameter. For a highreturned value, save system resources bydecreasing the number of input and outputcleaners by decreasing the value of the<num_iocleaners> parameter.

If the average number of asynchronous writes perpool write is less than the threshold value oftenenough, the Average Asynchronous Writes PerPool Write too low indication triggers an event.

30

Average Pool IO Timeupper bound

The average time, in milliseconds, for performingreading or writing buffer pool input and outputoperations to the database and tablespacecontained in the tablespace parameter list.

The returned value indicates the time applied toasynchronous input and output operationsperformed by prefetchers and page cleaners. Ahigh average time indicates the existence of aninput and output conflict. Move data to adifferent device to resolve this conflict.

If the average number of pool input/output timeexceeds the threshold value at a database ortablespace level often enough, the Average PoolIO Time too high indication triggers an event.

200



Average Pool Read Timeupper bound

The average time, in milliseconds, for processingread requests that cause data or index pages to bephysically read from disk to buffer pool fortablespaces in the tablespace parameter list and atthe database level.

The returned value includes the time applied toasynchronous read operations that are performedby prefetchers. A high average time indicates thatan input and output conflict exists. Move data toa different device to resolve this conflict.

If the average number of pool read time exceedsthe threshold value often enough, the AveragePool Read Time too high indication triggers anevent.

200

Average Pool Write Timeupper bound

The average time, in milliseconds, for processingwrite requests that cause data or index pages tobe physically written from disk to buffer pool fortablespaces in the tablespace parameter list and atthe database level.

The returned value includes the time applied toasynchronous write operations that areperformed by page cleaners. A high average timeindicates that an input and out put conflict exists.Move data to a different device to resolve thisconflict.

If the average number of pool write time exceedsthe threshold value often enough, the AveragePool Write Time too high indication triggers anevent.

200

Average Pool Writes PerPool Read upper bound

The ratio, as a percentage, of total pool writes topool reads for the database.

A returned value greater than 100 indicates thatyou need to improve your performance byincreasing the available buffer pool space. Areturned value greater than 1 indicates that atleast one write to disk occurred before a pagecould be read into the buffer pool.

You can increase the available buffer pool spaceby increasing the <chngpgs_thresh> or<num_iocleaners> configuration parameters to freespace or by increasing the <buffpage>configuration parameter to increase the totalspace for the buffer pool.

If the average number of pool writes per poolread exceeds the threshold value often enough,the Average Pool Writes Per pool Read is toohigh indication triggers an event.

100



Average Synchronous IOTime upper bound

The average time, in milliseconds, to performsynchronous input and output operationsperformed by database manager agents at adatabase level. Synchronous input and outputoperations for a database are performed bydatabase manager agents. Asynchronous inputand output operations are performed byprefetchers for reads and page cleaners for writes.Asynchronous input and output helps yourapplications run faster.

Log the returned value to analyze the input andoutput operations performed for the database.

If the average number of synchronousinput/output time exceeds the threshold valueoften enough, the Average Synchronous IO Timetoo high indication triggers an event.

200

Average SynchronousRead Time upper bound

The average time, in milliseconds, to perform forsynchronous data reads for the tablespaces in thetablespace parameter list and at the databaselevel. Synchronous read operations are performedby database manager agents. Asynchronous readsare performed by prefetchers which read datapages from disk into the buffer pool inanticipation of their use.

Log the returned value to analyze the input andoutput operations performed for the tablespacesand database. A high returned value compared tothe average time applied to asynchronous datareads indicates that you need to increase theamount of prefetching. Make this adjustment byincreasing the <num_ioservers> configurationparameter or turn on the <seqdetect>configuration parameter.

If the average number of synchronous read timeexceeds the threshold value often enough, theAverage Synchronous Read Time too highindication triggers an event.

200



Average SynchronousWrite Time upper bound

The average time, in milliseconds, to performsynchronous data writes for the database.Synchronous write operations for a database areperformed by database manager agents.Asynchronous writes are performed by pagecleaners, which write out changed pages to diskand free up space in the buffer pool.

Log the returned value to analyze the input andoutput operations performed for the database. Ahigh returned value compared to the averagetime applied to asynchronous data writesindicates that you need to increase the number ofpage cleaners. Make this adjustment byincreasing the <num_ioservers> configurationparameter.

If the average number of synchronous write timeexceeds the threshold value often enough, theAverage Synchronous Write Time too highindication triggers an event.

200

Percent Buffer Pool Hitslower bound

The overall buffer pool hit ratio for index anddata page activity, as a percentage, for thedatabase during the monitoring interval. Theoverall buffer pool hit ratio indicates thepercentage of page requests for which thedatabase manager did not need to load from diskto service because the index page already existedin the buffer pool. The greater the buffer pool hitratio, the lower the frequency of disk input andoutput.

A high return value indicates a low frequency ofdisk input and output. A low frequency of diskinput and output indicates fast performance. Fora low return value, increase the number of bufferpool pages to improve performance. A returnvalue of zero indicates that the monitoringinterval needs to read pages for every request.

For a large database, increasing the buffer poolsize can have a minimal effect on the buffer poolhit ratio. Such a database can have so large anumber of data pages that the statistical chanceof a hit does not increase by an increase of thebuffer pools. However, even though the data maybe too large to fit in the buffer pool, the entireindex may fit. In this case, you can refine bufferpool sizes until the overall buffer pool hit ratiostops increasing, then refine the buffer pool untilthe buffer pool index hit ratio (Percent IndexBuffer Pool Hits) no longer increases.

If the percentage of buffer pool hits is lower thanthe threshold value often enough at the database,tablespace, and application levels, the PercentBuffer Pool Hits too low indication triggers anevent.

90



Percent Index BufferPool Hits lower bound

The index page hit ratio, as a percentage, for thebuffer pools during the monitoring interval at thedatabase, tablespace, and application levels. Theindex page hit ratio for the buffer pool indicatesthe percentage of index page requests for whichthe database manager did not need to load fromdisk to service because the index page alreadyexisted in the buffer pool.

A high return value indicates a low frequency ofdisk input and output. A low frequency of diskinput and output indicates fast performance. Fora low return value, increase the number of bufferpool pages to improve performance.

If the hit ratio is lower than the threshold valuefor the database often enough, tablespaces in thetablespace parameter list, or any connectedapplications, the Percent Index Buffer Pool Hitstoo low indication triggers an event.

90

ParametersThe following table lists the parameters that can be set for the DB2 Buffer Poolsresource model. The table shows the name, a short description, and the defaultvalue for each parameter.



Applicationproperties tolog+

The application buffer poolproperties that are available forlogging.

v Percent Index Hits

v Percent Buffer Pool Hits

Databaseproperties tolog+

The database buffer poolproperties that are available forlogging.


v Percent Index Hits

v Average Synchronous Write Time

v Average Pool Read Time

v Average Synchronous Read Time

v Average Asynchronous ReadsPer Pool Read

v Average Asynchronous WritesPer Pool Read

v Average Pool Writes Per Pool Read

v Average Pool Write Time

v Average Pool IO Time

v Average Synchronous IO Time



TablespaceNames tomonitor

The tablespace name for eachtablespace that you want tomonitor. You can enter thewildcard (*) designator tomonitor all tablespaces.

*

Tablespaceproperties tolog+

The tablespace buffer poolproperties that are available forlogging.

v Average Pool Read Time

v Average Pool IO Time

v Average Pool Write Time


v Input Output Rate




DB2Application ApplicationBufferPoolDB2Application.db2AppID*

Specifies the uniqueapplication identificationthat is generated whenthe application connectsto the database.



DB2Application ApplicationBufferPool(continued) db2AppName

Specifies the name of theDB2 application.

DB2Database.db2Database*Specifies the name of theDB2 database.

DB2Instance.db2Instance*Specifies the name of theDB2 instance thatcontains the database.

DB2Partition.db2NodeSpecifies the name of theDB2 node.

Percent Buffer Pool HitsSpecifies the percentageof the hit ratio for thebuffer pool during themonitoring interval.

Percent Index HitsSpecifies the percentageof the index page hitratio for the buffer poolduring the monitoringinterval.

DB2Partition DatabaseBufferPoolAverage Async Reads Per Pool Read

Specifies the ratio ofbuffer pool asynchronousdata reads to the totalnumber of pool reads.

Average Async Writes Per PoolWrite Specifies the ratio of data

and index buffer poolasynchronous writes tothe total number of poolwrites.

Average Pool IO TimeSpecifies the averagetime for performingbuffer pool input andoutput operations.

Average Pool Read TimeSpecifies the averagetime for processing readrequests that cause indexpages to be physicallyread from disk to bufferpool.



DB2Partition DatabaseBufferPool(continued) Average Pool Write Time

Specifies the averagetime for processing writerequests that cause dataor index pages to bephysically written frombuffer pool to disk.

Average Pool Writes Per Pool ReadSpecifies the ratio of totalpool writes to pool reads.

Average Synchronous IO TimeSpecifies the averagetime to performsynchronous input andoutput operations.

Average Synchronous Read TimeSpecifies the averagetime to performsynchronous data reads.

Average Synchronous Write TimeSpecifies the averagetime to performsynchronous data writes.

DB2Database.db2Database*Specifies the name of theDB2 database.

DB2Instance.db2Instance*Specifies the name of theDB2 instance thatcontains the database.

DB2Partition.db2Node*Specifies the name of theDB2 node.

Percent Buffer Pool HitsSpecifies the percentageof the hit ratio for thebuffer pool during themonitoring interval.

Percent Index HitsSpecifies the percentageof the index page hitratio for the buffer poolduring the monitoringinterval.



DB2Tablespace TablespaceBufferPoolAverage Pool IO Time

Specifies the averagetime for performingbuffer pool input andoutput operations.

Average Pool Read TimeSpecifies the averagetime for processing readrequests that causeindex pages to bephysically read fromdisk to buffer pool.

Average Pool Write TimeSpecifies the averagetime for processingwrite requests thatcause data or indexpages to be physicallywritten from buffer poolto disk.

DB2Database.db2Database*Specifies the name ofthe DB2 database.

DB2Instance.db2Instance*Specifies the name ofthe DB2 instance thatcontains the database.

DB2Partition.db2Node*Specifies the name ofthe DB2 node.

db2TbspName*Specifies the name ofthe DB2 tablespace.

Input Output RateSpecifies the rate oftime for performinginput and outputoperations.

Percent Buffer Pool HitsSpecifies the percentageof the tablespace’s hitratio for the buffer poolduring the monitoringinterval.


Return codesNone


CLI exampleThe following example adds the DB2 Buffer Pools resource model toMyProfile#MyRegion. This example does not send theDB2_Low_App_PctBufferPoolHits event to Tivoli Business Systems Manager or toTivoli Enterprise Console.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2BufferPool -c 1200 \-DelPar TbspNames_List "*" \-AddPar TbspNames_List "Sales" \-AddPar TbspNames_List "Inventory" \-AddPar TbspNames_List "Expenses" \-e DB2_Low_App_PctBufferPoolHits -o 4 -NoSendTBSM -NoSendTec \


DB2 Buffer Pool/Extended Storage

DescriptionProvides extended storage monitoring of buffer pool extended storage at thedatabase and tablespace level by monitoring the ratio, as a percentage, of data +index pages copied from extended storage to pages copied to extended storageduring the monitoring interval. Extended storage provides a secondary level ofstorage for buffer pools. This allows a user to access memory beyond themaximum amount allowed for each process.

The DB2 Buffer Pool/Extended Storage resource model helps to determine if youwould benefit from using extended storage. When a page is transferred fromextended storage to the buffer pool, you save a system input and output call.However, you still incur the cost of attaching to the extended memory segment,copying the page, and detaching from the segment. A high ratio of input andoutput activity means that you will benefit from extended storage.


Internal name DB2BufferPoolExtStorage

Category DB2

Indications Database level Percent Extended Storage Read Write ratiotoo low occurs when the Database level Percent ExtendedStorage Read Write ratio is less than the Database PercentExtended Storage Read Write ratio lower bound threshold.

Tablespace level Percent Extended Storage Read Write ratiotoo low occurs when the Percent Extended Storage ReadWrite tablespace level is less than the Tablespace PercentExtended Storage Read Write ratio lower bound threshold.






Clearingevents

Page

Databaselevel PercentExtendedStorage ReadWrite ratiotoo low

DB2_Low_DB_PctExtStorageReadWrite Harmless Yes 59



Clearingevents

Page

Tablespacelevel PercentExtendedStorage ReadWrite ratiotoo low

DB2_Low_Tbsp_PctExtStorageReadWrite Harmless Yes 60

Database Percent Extended Storage Read Write ratio too lowindicationOccurs when the Database level Percent Extended Storage Read Write ratio is lessthan the Database Percent Extended Storage Read Write ratio lower boundthreshold. This event suggests that you are wasting memory.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of the Extended Storage Read/Write Ratio onDB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node>is <PctExtStorageReadWrite>, which is less than <LowerBound>.







PctExtStorageReadWriteSpecifies the percentage of data+index pages copied from extended storageto pages copied to extended storage during the monitoring interval.


This indication has the following threshold:v Database level Percent Extended Storage Read Write ratio lower bound






No



Occurrences 1

Holes 0



Tablespace Percent Extended Storage Read Write ratio too lowindicationOccurs when the Percent Extended Storage Read Write tablespace level is less thanthe Tablespace Percent Extended Storage Read Write ratio lower bound threshold.This event suggests that you are wasting memory.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of the Extended Storage Read/Write Ratio onDB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node>,tablespace <db2TbspName> is <PctExtStorageReadWrite>,which is less than <LowerBound>.








PctExtStorageReadWriteSpecifies the percentage of data+index pages copied from extended storageto pages copied to extended storage during the monitoring interval.


This indication has the following threshold:v Tablespace level Percent Extended Storage Read Write ratio lower bound







No

Occurrences 1

Holes 0



ThresholdsThe following table lists the thresholds that can be set for the DB2 BufferPool/Extend Storage resource model. For each threshold it shows the name, ashort description, and the default value:


Database level PercentExtended Storage ReadWrite ratio lower bound

The ratio, as a percentage, of data and indexpages that are copied from extended storage topages copied to extended storage during themonitoring interval. The higher the ratio, themore the user benefits from using extendedstorage.

If the ratio of extended storage reads and writesat the database level is less than the thresholdvalue often enough, the Database PercentExtended Storage Read Write ratio too lowindication triggers an event.

50

Tablespace level PercentExtended Storage ReadWrite ratio lower bound

The ratio, as a percentage, of data and indexpages that are copied from extended storage topages copied to extended storage during themonitoring interval. The higher the ratio, themore the user benefits from using extendedstorage.

If the ratio of extended storage reads and writesat the tablespace level is less than the thresholdvalue often enough, the Tablespace PercentExtended Storage Read Write ratio too lowindication triggers an event.

50

ParametersThe following table lists the parameters that can be set for the DB2 BufferPool/Extend Storage resource model. The table shows the name, a shortdescription, and the default value for each parameter:



Database BufferPool properties tolog

The Database properties available forlogging.

v Percent Extended StorageRead Write

Tablespace BufferPool properties tolog

The Tablespace properties availablefor logging.

v Percent Extended StorageRead Write

Tablespace Names The List of Tablespace names tomonitor. The default list is ALLtablespaces, denoted by the asterisk(*) wildcard designation.

*




DB2Partition DB_BufferPool_ExtStorageDB2Database.db2Database*

Specifies the nameof the DB2database.

DB2Instance.db2Instance*Specifies the nameof the DB2instance thatcontains thedatabase.


Percent Extended StorageRead Write

Specifies thepercentage ofdata+index pagescopied fromextended storageto pages copied toextended storageduring themonitoringinterval.



DB2Tablespace Tbsp_BufferPool_ExtStorageDB2Database.db2Database*

Specifies the nameof the DB2database.

DB2Instance.db2Instance*Specifies the nameof the DB2instance thatcontains thedatabase.


db2TbspName*Specifies the nameof the DB2tablespace.

Percent Extended StorageRead Write

Specifies thepercentage ofdata+index pagescopied fromextended storageto pages copied toextended storageduring themonitoringinterval.


Return codesNone

CLI exampleThe following example adds the DB2 Buffer Pool/Extended Storage resourcemodel to MyProfile#MyRegion. This example sends theDB2_Low_Tbsp_PctReadWriteExtStorage event to Tivoli Enterprise Console andsets the severity to critical.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2BufferPoolExtStorage -c 1800 \-Log -LogDisable \-DelPar TbspNames_List "*" \-AddPar TbspNames_List "SA*" \-AddPar TbspNames_List "*ACCT*" \-e DB2_Low_Tbsp_PctReadWriteExtStorage -o 3 -severity CRITICAL -SendTec \


DB2 Catalog Cache

DescriptionMonitors the effectiveness of the catalog cache. The catalog cache stores tabledescriptors for tables, views, and aliases. A descriptor stores information about atable, view, or alias in a condensed internal format. When a transaction referencesa table, it causes an insert of a table descriptor into the cache, so that subsequenttransactions that reference that same table can use that descriptor and avoidreading from a disk.

The DB2 Catalog Cache resource model monitors the percentage of catalog cachehits during the monitoring interval.


Internal name DB2CatalogCache

Category DB2

Indications Percent Catalog Cache Hits too low occurs when thePercent Catalog Cache Hits is lower than the Percent CatalogCache Hits lower bound threshold.






Clearingevents

Page

Percent CatalogCache Hits toolow

DB2_Low_PctCatCacheHits Warning Yes 64

Percent Catalog Cache Hits too low indicationOccurs when the Percent Catalog Cache Hits is lower than the Percent CatalogCache Hits lower bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percentage of Catalog Cache Hits on DB2Database <db2Database>, Instance <db2Instance>, Node <db2Node>is <PctCatCacheHits>, which is lower than <LowerBound>.





PctCatCacheHitsSpecifies the percentage of catalog cache hits during the monitoringinterval.





This indication has the following threshold:v Percent Catalog Cache Hits lower bound






Yes

Occurrences 3

Holes 1



ThresholdsThe following table lists the thresholds that can be set for the DB2 Catalog Cacheresource model. For each threshold it shows the name, a short description, and thedefault value:



Percent Catalog CacheHits lower bound

The catalog cache hit ratio, as a percentage, forthe database during the monitoring interval. Thecatalog cache hit ratio indicates the success of thecatalog cache. The returned value is the ratio ofsuccessful catalog cache lookups to the totalnumber of catalog cache lookups.

A low ratio indicates the failure of more lookupsmade to the catalog cache while a table, view, oralias reference in an SQL statement was beingprocessed. For a low ratio, increase the size of thecatalog cache by increasing the <catalogcache_sz>configuration parameter. You can expect a smallratio following the first connection to thedatabase. In addition, heavy use of DDL SQLstatements also decrease this ratio.

If the percentage of catalog cache hits is lowerthan the threshold value often enough, thePercent Catalog Cache Hits too low indicationtriggers an event.

90

ParametersThe following table lists the parameters that can be set for the DB2 Catalog Cacheresource model. The table shows the name, a short description, and the defaultvalue for each parameter.




The Database Catalog Cacheproperties available for logging.Mark each check box for eachproperty that you want to log.

v Percent Catalog Cache Hits





DB2Partition CatalogCacheDB2Database.db2Database*

Specifies the nameof the DB2 database.



Percent Catalog Cache HitsSpecifies thepercentage ofcatalog cache hitsduring themonitoring interval.

Return codesNone

CLI exampleThe following example adds the DB2 Catalog Cache resource model toMyProfile#MyRegion. This example enables logging with a historical durationperiod of four hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2CatalogCache \-Log -LogEnable -p 04:00 -Agg no -NoMin -NoMax -Avg \-t Low_PctCatCacheHits 83.000000 \


DB2 CPU Utilization

DescriptionMonitors the total DB2 system and user central processing unit time used by theapplications database manager agents. The user central processing unit timerepresents time spent executing database manager code. The system centralprocessing unit time represents the time, in seconds, spent in system calls.

The DB2 CPU Utilization resource model identifies applications or queries thatconsume large amounts of central processing unit time. This resource modelmonitors the total system and user time used by the database manager agents.


Internal name DB2CpuUtilization

Category DB2

Indications Total System CPU Time too high occurs when the Totalsystem CPU Time exceeds the Total System CPU Time upperbound threshold.

Total User CPU Time too high occurs when the Total UserCPU Time exceeds the Total User CPU Time upper boundthreshold.

Associated tasks and built-inactions

None





Clearingevents

Page

TotalSystemCPU Timetoo high

DB2_High_ApplicationAgent_TotSystemCpuTime

Warning Yes 68

Total UserCPU Timetoo high

DB2_High_DB2ApplicationAgent_TotUserCpuTime

Warning Yes 70

Total System CPU Time too high indicationOccurs when the Total System CPU Time exceeds the Total System CPU Timeupper bound threshold.



The Total System CPU Time of the DB2 Database<db2Database>, Instance <db2Instance>, Node <db2Node>,Application Name <db2AppName>, Application ID <db2AppID was <TotSystemCpuTime>,which is greater than <UpperBound>.









TotSystemCpuTimeSpecifies the total system CPU time used by the database manager agents.System CPU time represents the time, in seconds, spent in system calls.


This indication has the following threshold:v Total System CPU Time upper bound






No

Occurrences 1

Holes 0




Total User CPU Time too high indicationOccurs when the Total User CPU Time exceeds the Total User CPU Time upperbound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Total User CPU Time of the DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Application Name <db2AppName>,Application ID <db2AppID was <TotUserCpuTime>, which isgreater than <UpperBound>.









TotUserCpuTimeSpecifies the total user CPU time used by the database manager agents.User CPU time represents time spent executing database manager code.


This indication has the following threshold:v Total User CPU Time upper bound






No

Occurrences 1

Holes 0




ThresholdsThe following table lists the thresholds that can be set for the DB2 CPU Utilizationresource model. For each threshold it shows the name, a short description, and thedefault value:


Total System CPU Timeupper bound

If the total amount of system CPU time exceedsthe threshold value often enough, the TotalSystem CPU Time too high indication triggers anevent.

5000

Total User CPU Timeupper bound

If the total amount of user CPU time exceeds thethreshold value often enough, the Total User CPUTime too high indication triggers an event.

5000

ParametersThe following table lists the parameters that can be set for the DB2 CPU Utilizationresource model. The table shows the name, a short description, and the defaultvalue for each parameter.



Databaseproperties to log+

The Database CPU Utilizationproperties that are available forlogging.

v Total User CPU Time

v Total System CPU Time




DB2Application CpuUtilizationDB2Application.db2AppID*

Specifies the uniqueapplicationidentification that isgenerated when theapplication connectsto the database.



DB2Application CpuUtilization (continued)db2AppName

Specifies the nameof the DB2application.



DB2Partition.db2NodeSpecifies the nameof the DB2 node.

Total System CPU TimeSpecifies the totalsystem CPU timeused by thedatabase manageragents. System CPUtime represents thetime, in seconds,spent in systemcalls.

Total User CPU TimeSpecifies the totaluser CPU time usedby the databasemanager agents.User CPU timerepresents timespent executingdatabase managercode.


Return codesNone

CLI exampleThe following example adds the DB2 CPU Utilization resource model toMyProfile#MyRegion. This example enables aggregated logging for a period of 15minutes with a historical duration period of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2CpuUtilization -c 120 \-Log -LogEnable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -NoAvg \


DB2 Database Activity

DescriptionMonitors general activity and availability of DB2 at the database level.

The DB2 Database Activity resource model monitors the following information:v The number of applications that are currently connected to the database.v The number of currently connected applications for which the database manager

is currently processing a request.v The percentage of the allowed number of connections that are concurrent

connections.v The number of all packages and triggers that are currently marked invalid in the

database.v The number of SYSTEM packages that are currently marked invalid in the

database.v The number of packages owned by a user that are currently marked invalid in

the database.v The RESTORE PENDING status in the database during the last monitoring

interval.v The date and time when the last database backup completed.v The percentage of space used in the Database Managed Space tablespace.v The number of bytes allocated to the System Managed Space tablespace.v The tablespace status.


Internal name DB2DatabaseStatus

Category DB2

Indications Database Backup past due occurs when the last backuptimestamp on a database is older than the Database Backupdue date threshold.

Database in Restore Pending State occurs when it receivesconfirmation that the Restore Pending state threshold runson a database.

Gateway Connection Errors too high occurs when theConnection Errors to the gateway exceeds the ConnectionErrors upper bound threshold.

Gateway Connections Waiting for Host too high occurswhen the Connections Waiting For Host to the gatewayexceeds the Connections Waiting For Host upper boundthreshold.

Gateway Current Connections too high occurs when theCurrent Connections to the gateway exceeds the CurrentConnections upper bound threshold.



Indications (continued) Most Recent Connect Response Time too high occurs whenthe Most Recent Connect Response Time to the gatewaysexceeds the Most Recent Connect Response Time upperbound threshold.

Percent Connections Used too high occurs when the PercentConnections Used to the database exceeds the PercentConnections Used upper bound threshold.

Percent Space Used in a DMS Tablespace too high occurswhen the percentage space used in a Database ManagedSpace tablespace exceeds the Percent Space Used in the DMSTablespace upper bound threshold.

Space Used in a SMS Tablespace too high occurs when theSystem Managed Space used, in bytes, exceeds the SpaceUsed in a SMS Tablespace upper bound threshold.

Tablespace Status is not normal occurs when any of thetablespaces in the tablespace parameter list are not in thenormal state.



Target managed resourceDB2DatabaseManager, DB2Gateway, DB2PartitionManager

Note: The DB2DatabaseManager and DB2PartitionManager managed resourcesonly monitor database and partition classes and metrics and ignore thegateway. The DB2Gateway managed resource only monitors the gatewayand ignores all database and partition classes and metrics.



Clearingevents

Page

DatabaseBackup pastdue

DB2_Old_LastBackupTimestamp Critical No 75

Database inRestorePending State

DB2_True_RestorePending Critical Yes 76

GatewayConnectionErrors toohigh

DB2_High_ConnectionErrors Warning Yes 77

GatewayConnectionsWaiting forHost too high

DB2_High_ConnWaitingForHost Warning No 78



Clearingevents

Page

GatewayCurrentConnectionstoo high

DB2_High_CurrentConnections Warning No 79

Most RecentConnectResponseTime too high

DB2_High_MostRecentConnectResponse Warning No 80

PercentConnectionsUsed too high

DB2_High_PctConnectionsUsed Warning Yes 81

Percent SpaceUsed in aDMSTablespacetoo high

DB2_High_SpaceUsedDMSTablespace Critical Yes 82

Space Used ina SMSTablespacetoo high

DB2_High_SpaceUsedSMSTablespace Critical Yes 83

TablespaceStatus is notnormal

DB2_False_TablespaceNormalStatus Warning No 84

Database Backup past due indicationOccurs when the last backup timestamp on a database is older than the DatabaseBackup due date threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Last Backup timestamp <LastBackupTimestamp> for DB2 Instance <db2Instance>,Database <db2Database>, Node <db2Node> has beenmore than <LastBackup> days.




LastBackupTimestampSpecifies the date and time when the last database backup was completed.





LastBackupSpecifies the instance’s threshold value.

This indication has the following threshold:v Database Backup due date






No

Occurrences 2

Holes 0



Database in Restore Pending State indicationOccurs when it receives confirmation that the Restore Pending state threshold runson a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Restore Pending State is <RestorePending> for DB2 Instance <db2Instance>,Database <db2Database>, Node <db2Node>.




RestorePendingSpecifies the RESTORE PENDING status in the database during the lastmonitoring interval.




This indication has the following threshold:v Restore Pending State







Yes

Occurrences 1

Holes 0



Gateway Connection Errors too high indicationOccurs when the Connection Errors to the gateway exceeds the Connection Errorsupper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The gateway’s Connection Errors on DB2 Database <db2Database>,Instance <db2Instance> is <ConnectionErrors>,which is higher than <UpperBound>.






ConnectionErrorsSpecifies the number of connection errors that occurred on a database.


This indication has the following threshold:v Connection Errors upper bound







Yes

Occurrences 1

Holes 0



Gateway Connections Waiting for Host too high indicationOccurs when the Connections Waiting For Host to the gateway exceeds theConnections Waiting For Host upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The gateway’s Connections Waiting For Host on DB2 Database <db2Database>,Instance <db2Instance> is <ConnWaitingForHostCurrent>,which is higher than <UpperBound>.






ConnWaitingForHostCurrentSpecifies the number of gateway connections that are currently waiting fora host.


This indication has the following threshold:v Connections Waiting for Host upper bound








Yes

Occurrences 3

Holes 2



Gateway Current Connections too high indicationOccurs when the Current Connections to the gateway exceeds the CurrentConnections upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The gateway’s Current Connections on DB2 Database <db2Database>,Instance <db2Instance> is <CurrentConnections>,which is higher than <UpperBound>.






CurrentConnectionsSpecifies the number of local databases that have applications connected.


This indication has the following threshold:v Current Connections upper bound






No

Occurrences 3



Holes 2



Most Recent Connect Response Time too high indicationOccurs when the Most Recent Connect Response Time to the gateways exceeds theMost Recent Connect Response Time upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The gateway’s Most Recent Connect Response Time on DB2 Database <db2Database>,Instance <db2Instance> is <MostRecentConnectResponseTime>,which is higher than <UpperBound>.






MostRecentConnectResponseTimeSpecifies the most recent response time for the database connection to theapplication.


This indication has the following threshold:v Most Recent Connect Response Time upper bound






Yes

Occurrences 3

Holes 2




Percent Connections Used too high indicationOccurs when the Percent Connections Used to the database exceeds the PercentConnections Used upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Connections Used on DB2 Database <db2Database>, Instance <db2Instance>,Node <db2Node> is <PctConnectionsUsed>, whichis higher than <UpperBound>.







PctConnectionsUsedSpecifies the percentage of the allowed number of connections that areconcurrent connections.


This indication has the following threshold:v Percent Connections Used upper bound






Yes

Occurrences 3

Holes 1


Note: If you have Tivoli Business Systems Manager configured for your systems,Tivoli Enterprise Console automatically forwards events to Tivoli Business


Systems Manager. Do not change the configuration of the indication to sendevents to Tivoli Business Systems Manager.

Percent Space Used in a DMS Tablespace too high indicationOccurs when the percentage space used in a Database Managed Space tablespaceexceeds the Percent Space Used in the DMS Tablespace upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Space Used DMS for tablespace <db2TbspName>on DB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node>is <PctSpaceUsedDMS>, which is higher than <UpperBound>.








PctSpaceUsedDMSSpecifies the percentage of space used in the Database Managed Spacetablespace.


This indication has the following threshold:v Percent Space Used in a DMS Tablespace upper bound






No

Occurrences 1

Holes 0




Space Used in a SMS Tablespace too high indicationOccurs when the System Managed Space used, in bytes, exceeds the Space Used ina SMS Tablespace upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Space Used SMS for tablespace <db2TbspName> on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <SpaceUsedSMS>,which is higher than <UpperBound>.








SpaceUsedSMSSpecifies the number of bytes allocated to the System Managed Spacetablespace.


This indication has the following threshold:v Space Used in a SMS Tablespace upper bound






No

Occurrences 1

Holes 0




Tablespace Status is not normal indicationOccurs when any of the tablespaces in the tablespace parameter list are not in thenormal state.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Tablespace Status for tablespace <db2TbspName> on theDB2 Instance <db2Instance>, Database <db2Database>,Node <db2Node> is not equal to zero (Normal State).













Yes

Occurrences 2

Holes 1



ThresholdsThe following table lists the thresholds that can be set for the DB2 DatabaseActivity resource model. For each threshold it shows the name, a short description,


and the default value:


Connection Errors upperbound

The number of times that a communication erroroccurred while a DCS application was attemptingto connect to a host database, or while it wasprocessing an SQL statement.

If the number of connections errors exceeds thethreshold value often enough, the GatewayConnection Errors too high indication triggers anevent.

100

Connections Waiting ForHost upper bound

The current number of connections to the hostdatabase handled by the DB2 Connect gatewaythat are waiting for a reply from the host.

If the number of connections waiting for a hostexceeds the threshold value often enough, theGateway Connections Waiting for Host too highindication triggers an event.

30

Current Connectionsupper bound

The current number of connections to hostdatabases handled by the DB2 Connect gateway.

If the number of current connections exceeds thethreshold value often enough, the GatewayCurrent Connections too high indication triggersan event.

50

Database Backup duedate

Compares the database last backup timestampwith the current date.

If the timestamp value is older than the numberof days indicated by the threshold value oftenenough, the Database Backup past due indicationtriggers an event.

2

Most Recent ConnectResponse Time upperbound

The elapsed time between the start of connectionprocessing and actual establishment of aconnection for the most recent DCS applicationthat connected to this database.

If the most recent connection response timeexceeds the threshold value often enough, theMost Recent Connect Response Time too highindication triggers an event.

5

Percent ConnectionsUsed upper bound

The percentage of the allowed number ofconnections that are concurrent connections.

A high return value indicates that you need toadjust the value of the <maxappls> configurationparameter or schedule your applications so thatthey do not run concurrently. The <maxappls>configuration parameter limits the number ofconcurrent applications that are locally andremotely connected to a database.

If the percentage of connections used exceeds thethreshold value often enough, the PercentConnections Used too high indication triggers anevent.

80



Percent Space Used in aDMS Tablespace upperbound

Specifies the percentage of space used in theDatabase Managed Space tablespace.

If the space used in a DMS tablespace in thetablespace parameter list exceeds the thresholdvalue often enough, the Percent Space Used in aDMS Tablespace too high indication triggers anevent.

85

Restore Pending state Checks for the RESTORE PENDING status of adatabase.

If the database is in the RESTORE PENDINGstate often enough, the Database in RestorePending indication triggers an event.

1

Space Used in a SMSTablespace upper bound

Specifies the number of bytes allocated to theSystem Managed Space tablespace in the SystemManaged Space tablespace parameter list. Log thereturned value to determine if the number ofbytes used by a System Managed Spacetablespace exceeds the file system on which thetablespace resides.

If the space used in a System Managed Spacetablespace exceeds the threshold value oftenenough, the Space Used in a SMS Tablespace toohigh indication triggers an event.

0

ParametersThe following table lists the parameters that can be set for the DB2 DatabaseActivity resource model. The table shows the name, a short description, and thedefault value for each parameter.




Specifies the application activityproperties available for logging.

v Percent Spaced Used DMS

DatabaseConfigurationproperties tolog+

Specifies the database configurationproperties available for logging.

v Restore Pending

Database statusproperties tolog+

Specifies the database statusproperties available for logging.

v Last Backup Timestamp



DMS Tablespacenames to monitor

Specifies a list of DatabaseManaged Space tablespaces tomonitor. The following are optionsto enter for tablespaces to monitor:

v Tablespace name for eachtablespace to monitor

v Wildcard designator, (*), tomonitor all tablespaces

v Combine partial tablespacenames and use the wildcarddesignator, (*), to separate

*

Gatewayproperties tolog+

Specifies the gateway propertiesavailable for logging.

v Current Connections

v Most Recent ConnectionResponse Time

v Connection Errors

v Connections Waiting ForHost Currently

SMS TablespaceNames tomonitor

Specifies a list of System ManagedSpace tablespaces to monitor. Thefollowing are options to enter fortablespaces to monitor:




*

Tablespace DMSproperties tolog+

Specifies the tablespace DatabaseManaged Space properties availablefor logging.

v Percent Spaced Used DMS


Specifies a list of tablespaces tomonitor. The following are optionsto enter for tablespaces to monitor:




*

Tablespace SMSproperties tolog+

Specifies the tablespace SystemManaged Space properties availablefor logging.

v Space Used SMS

Tablespace statusproperties tolog+

Specifies the tablespace propertiesavailable for logging.

v Tablespace Status





DB2Partition Application ActivityDB2Database.db2Database*




Percent Connections UsedSpecifies thepercentage of theallowed number ofconnections that areconcurrentconnections.

DB2Partition Database ConfigurationDB2Database.db2Database*




Restore PendingSpecifies theRESTOREPENDING status inthe database duringthe last monitoringinterval.



DB2Partition Database StatusDB2Database.db2Database*




Last Backup TimestampSpecifies the dateand time when thelast database backupwas completed.

DB2Gateway Gateway StatusConnection Errors

Specifies thenumber ofconnection errorsthat occurred on adatabase.

Connections Waiting For HostCurrently

Specifies thenumber of gatewayconnections that arecurrently waiting fora host.

Current ConnectionsSpecifies thenumber of localdatabases that haveapplicationsconnected.



Most Recent ConnectionResponse Time

Specifies the mostrecent response timefor the databaseconnection to theapplication.



DB2TableSpace Tablespace DMSDB2Database.db2Database*





Percent Spaced Used DMSSpecifies thepercentage of spaceused in theDatabase ManagedSpace tablespace.

DB2TableSpace Tablespace SMSDB2Database.db2Database*





Space Used SMSSpecifies thenumber of bytesallocated to theSystem ManagedSpace tablespace.



DB2TableSpace Tablespace StatusDB2Database.db2Database*





TbspBackupPendingIndicates a backuppending state forthe tablespace.

TbspBackupProgressIndicates that abackup is inprogress for thetablespace.

TbspDeletePendingIndicates a deletepending state forthe tablespace.

TbspDisablePendingIndicates a disablepending state forthe tablespace.

TbspDMSRebalanceIndicates that theDMS rebalancer isactive for thetablespace.

TbspDropPendingIndicates that a dropis pending for thetablespace.



DB2TableSpace Tablespace Status (continued)TbspLoadPending

Indicates a loadpending state forthe tablespace.

TbspNormalIndicates a normalstate for thetablespace.

TbspOfflineIndicates that thetablespace is offlineand not accessible.

TbspQuiescedShIndicates aQuiesced: SHAREstate for thetablespace.

TbspQuiescedUpIndicates aQuiesced: UPDATEstate for thetablespace.

TbspQuiescedExIndicates aQuiesced:EXCLUSIVE statefor the tablespace.

TbspReorgProgressIndicates that areorganization is inprogress for thetablespace.

TbspRestorePendingIndicates a restorepending state forthe tablespace.

TbspRestoreProgressIndicates that arestore is inprogress for thetablespace.

TbspRFpendingIndicates a rollforward is pendingfor the tablespace.



DB2TableSpace Tablespace Status (continued)TbspRFprogress

Indicates a rollforward is inprogress for thetablespace.

TbspStorDefIndicates that thestorage may bedefined for thetablespace.

TbspStorDefChangedIndicates that thestorage waschanged prior to theroll forward statefor the tablespace.

TbspStorDefFinalIndicates that thestorage is in thefinal stage for thetablespace.

TbspStorageUndefinedIndicates that youmust define thestorage for thetablespace.

TbspTBScreateIndicates that atablespace creationis in progress for thetablespace.

TbspTBSdeleteIndicates that atablespace deletionis in progress for thetablespace.

Return codesNone

CLI exampleThe following example adds the DB2 Database Activity resource model toMyProfile#MyRegion. This example disables logging.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2DatabaseStatus \-Log -LogDisable \-t High_ConnectionErrors 65.000000 \-t Old_LastBackupTimestamp 5.000000 \-DelPar SMS_TbspNames_List "*" \


-AddPar SMS_TbspNames_List "Inventory" \-AddPar SMS_TbspNames_List "CapitalEquipment" \-DelPar DMS_TbspNames_List "*" \-AddPar DMS_TbspNames_List "EXPENSE*" \


DB2 Direct IO

DescriptionMonitors non-buffered input and output at the database, tablespace, andapplication levels.

The DB2 Direct IO resource model monitors the following information:v The average number of sectors that are read by a direct read for the database,

tablespace, or application.v The average number of sectors that are written by a direct write for the

database, tablespace, or application.v The average time, in milliseconds, that is used to perform direct reads or writes

to the database or tablespace.


Internal name DB2DirectIO

Category DB2

Indications Application Average Sectors Per Direct Read too highoccurs when the Average Sectors Per Direct Read exceedsthe Average Sectors Per Direct Read upper bound thresholdfor an application.

Application Average Sectors Per Direct Write too highoccurs when the Average Sectors Per Direct Write exceedsthe Average Sectors Per Direct Write upper bound thresholdfor an application.

Database Average Direct Read Time too high occurs whenthe Average Direct Read Time exceeds the Average DirectRead Time upper bound threshold for a database.

Database Average Direct Write Time too high occurs whenthe Average Direct Write Time exceeds the Average DirectWrite Time upper bound threshold for a database.

Database Average Sectors Per Direct Read too high occurswhen the Average Sectors Per Direct Read exceeds theAverage Sectors Per Direct Read upper bound for a database.

Database Average Sectors Per Direct Write too high occurswhen the Average Sectors Per Direct Write exceeds theAverage Sectors Per Direct Write upper bound threshold fora database.

Tablespace Average Direct Read Time too high occurswhen the Average Direct Read Time exceeds the AverageDirect Read Time upper bound threshold for a tablespace.

Tablespace Average Direct Write Time too high occurswhen the Average Direct Write Time exceeds the TablespaceAverage Direct Write Time upper bound threshold for atablespace.



Indications (continued) Tablespace Average Sectors Per Direct Read too highoccurs when the Average Sectors Per Direct Read exceedsthe Average Sectors Per Direct Read upper bound thresholdfor a tablespace.

Tablespace Average Sectors Per Direct Write too highoccurs when the Average Sectors Per Direct Write exceedsthe Average Sectors Per Direct Write upper bound thresholdfor a tablespace.






Clearingevents

Page

ApplicationAverageSectors PerDirect Readtoo high

DB2_High_App_AvgSectorsPerDirectRead Harmless Yes 97

ApplicationAverageSectors PerDirect Writetoo high

DB2_High_App_AvgSectorsPerDirectWrite Harmless Yes 98

DatabaseAverageDirect ReadTime too high

DB2_High_DB_AvgDirectReadTime Harmless Yes 99

DatabaseAverageDirect WriteTime too high

DB2_High_DB_AvgDirectWriteTime Harmless Yes 100

DatabaseAverageSectors PerDirect Readtoo high

DB2_High_DB_AvgSectorsPerDirectRead Harmless Yes 101

DatabaseAverageSectors PerDirect Writetoo high

DB2_High_DB_AvgSectorsPerDirectWrite Harmless Yes 102



Clearingevents

Page

TablespaceAverageDirect ReadTime too high

DB2_High_Tbsp_AvgDirectReadTime Harmless Yes 103

TablespaceAverageDirect WriteTime too high

DB2_High_Tbsp_AvgDirectWriteTime Harmless Yes 104

TablespaceAverageSectors PerDirect Readtoo high

DB2_High_Tbsp_AvgSectorsPerDirectRead Harmless Yes 105

TablespaceAverageSectors PerDirect Writetoo high

DB2_High_Tbsp_AvgSectorsPerDirectWrite Harmless Yes 106

Application Average Sectors Per Direct Read too high indicationOccurs when the Average Sectors Per Direct Read exceeds the Average Sectors PerDirect Read upper bound threshold for an application.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The application’s Average Sectors Per Direct Read on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Application Name <db2AppName>,Application ID <db2AppID is <AvgSectorsPerDirectRead>,which is higher than <UpperBound>.










AvgSectorsPerDirectReadSpecifies the average number of sectors that are read by a direct read.


This indication has the following threshold:v Average Sectors Per Direct Read upper bound






No

Occurrences 1

Holes 0



Application Average Sectors Per Direct Write too high indicationOccurs when the Average Sectors Per Direct Write exceeds the Average Sectors PerDirect Write upper bound threshold for an application.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The application’s Average Sectors Per Direct Write on DB2 Database<db2Database>, Instance <db2Instance>, Node <db2Node>,Application Name <db2AppName>, Application ID <db2AppID is<AvgSectorsPerDirectWrite>, which is higher than <UpperBound>.










AvgSectorsPerDirectWriteSpecifies the average number of sectors that are written.


This indication has the following threshold:v Average Sectors Per Direct Write upper bound






No

Occurrences 1

Holes 0



Database Average Direct Read Time too high indicationOccurs when the Average Direct Read Time exceeds the Average Direct Read Timeupper bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Direct Read Time on DB2 Database<db2Database>, Instance <db2Instance>, Node <db2Node>is <AvgDirectReadTime>, which is higher than <UpperBound>.








AvgDirectReadTimeSpecifies the average time applied to performing direct reads.


This indication has the following threshold:v Average Direct Read Time upper bound






No

Occurrences 1

Holes 0



Database Average Direct Write Time too high indicationOccurs when the Average Direct Write Time exceeds the Average Direct Write Timeupper bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Direct Write Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgDirectWriteTime>,which is higher than <UpperBound>.







AvgDirectWriteTimeSpecifies the average time for performing direct writes.



This indication has the following threshold:v Average Direct Write Time upper bound






No

Occurrences 1

Holes 0



Database Average Sectors Per Direct Read too high indicationOccurs when the Average Sectors Per Direct Read exceeds the Average Sectors PerDirect Read upper bound for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Sectors Per Direct Read on DB2 Database<db2Database>, Instance <db2Instance>, Node <db2Node>is <AvgSectorsPerDirectRead>, which ishigher than <UpperBound>.
















No

Occurrences 1

Holes 0



Database Average Sectors Per Direct Write too high indicationOccurs when the Average Sectors Per Direct Write exceeds the Average Sectors PerDirect Write upper bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The database’s Average Sectors Per Direct Write onDB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node>is <AvgSectorsPerDirectWrite>, which is higherthan <UpperBound>.
















No

Occurrences 1

Holes 0



Tablespace Average Direct Read Time too high indicationOccurs when the Average Direct Read Time exceeds the Average Direct Read Timeupper bound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Direct Read Time on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node>, Tablespace Name <db2TbspName>is <AvgDirectReadTime>, which is higher than <UpperBound>.








AvgDirectReadTimeSpecifies the average time applied to performing direct reads.


This indication has the following threshold:v Average Direct Read Time upper bound







No

Occurrences 1

Holes 0



Tablespace Average Direct Write Time too high indicationOccurs when the Average Direct Write Time exceeds the Tablespace Average DirectWrite Time upper bound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Direct Write Time on DB2 Database<db2Database>, Instance <db2Instance>, Node <db2Node>,Tablespace Name <db2TbspName> is <AvgDirectWriteTime>,which is higher than <UpperBound>.








AvgDirectWriteTimeSpecifies the average time for performing direct writes.


This indication has the following threshold:v Average Direct Write Time upper bound







No

Occurrences 1

Holes 0



Tablespace Average Sectors Per Direct Read too high indicationOccurs when the Average Sectors Per Direct Read exceeds the Average Sectors PerDirect Read upper bound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Sectors Per Direct Write onDB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node>,Tablespace Name <db2TbspName> is <AvgSectorsPerDirectRead>,which is higher than <UpperBound>.

















No

Occurrences 1

Holes 0



Tablespace Average Sectors Per Direct Write too high indicationOccurs when the Average Sectors Per Direct Write exceeds the Average Sectors PerDirect Write upper bound threshold for a tablespace.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The tablespace’s Average Sectors Per Direct Write on DB2 Database<db2Database>, Instance <db2Instance>, Node <db2Node>,Tablespace Name <db2TbspName> is <AvgSectorsPerDirectWrite>,which is higher than <UpperBound>.

















No

Occurrences 1

Holes 0



ThresholdsThe following table lists the thresholds that can be set for the DB2 Direct IOresource model. For each threshold it shows the name, a short description, and thedefault value:


Average Direct ReadTime upper bound

The average time, in milliseconds, used toperform direct reads to the database andtablespaces in the tablespace parameter list. Ahigh average time indicates the existence of aninput and output conflict.

If the average direct read time exceeds thethreshold value often enough, the Average DirectRead Time too high indication triggers an event.

500

Average Direct WriteTime upper bound

The average time, in milliseconds, used toperform direct writes to the database andtablespaces in the tablespace parameter list. Ahigh average time indicates the existence of aninput and output conflict.

If the average direct write time exceeds thethreshold value often enough, the Average DirectWrite Time too high indication triggers an event.

500



Average Sectors PerDirect Read upperbound

The average number of sectors that are read by adirect read for a database, tablespaces in thetablespace parameter list, and all connectedapplications.

Direct writes do not use the buffer pool butphysically writes the data from the disk eachtime. This results in poor performance. If you usesystem monitoring sources to track input andoutput, log this value to distinguish databaseinput and output from non-database input andoutput.

If the average number of sectors per direct readexceeds the threshold value often enough, theAverage Sectors Per Direct Read too highindication triggers an event.

50

Average Sectors PerDirect Write upperbound

The average numbers of sectors that are writtenby a direct write for a database, tablespaces inthe tablespace parameter list, and all connectedapplications.

Direct writes do not use the buffer pool butphysically writes the data from the disk eachtime. This results in poor performance. If you usesystem monitoring sources to track input andoutput, log this value to distinguish databaseinput and output from non-database input andoutput.

If the average number of sectors per direct writeexceeds the threshold value often enough, theAverage Sectors Per Direct Write too highindication triggers an event.

50

ParametersThe following table lists the parameters that can be set for the DB2 Direct IOresource model. The table shows the name, a short description, and the defaultvalue for each parameter.




Application Direct IO propertiesavailable for logging.

v Average Sectors Per Direct Read

v Average Sectors Per Direct Write



Applications tomonitor

A list of applications to monitor.The following are options toenter for applications to monitor:

v Application name for eachapplication to monitor

v Wildcard designator, (*), tomonitor all applications

v Combine partial applicationnames and use the wildcarddesignator, (*), to separate

*


Database Direct IO propertiesavailable for logging.

v Average Direct Write Time

v Average Direct Read Time




A list of tablespaces to monitor.The following are options toenter for tablespaces to monitor:




*

Tablespaceproperties tolog+

Tablespace Direct IO propertiesavailable for logging.

v Average Direct Write Time

v Average Direct Read Time






DB2Application Application Direct IOAverage Sectors Per DirectRead Specifies the

average number ofsectors that are readby a direct read.

Average Sectors Per DirectWrite Specifies the

average number ofsectors that arewritten.



DB2Application Application Direct IO(continued) DB2Application.db2AppID*

Specifies the uniqueapplicationidentification that isgenerated when theapplication connectsto the database.




DB2Partition.db2NodeSpecifies the nameof the DB2 node.

DB2Partition Database Direct IOAverage Direct Read Time

Specifies theaverage timeapplied toperforming directreads.

Average Direct Write TimeSpecifies theaverage time forperforming directwrites.

Average Sectors Per DirectRead Specifies the







DB2Partition Database Direct IO(continued) DB2Instance.db2Instance*



DB2Tablespace Tablespace Direct IOAverage Direct Read Time

Specifies theaverage timeapplied toperforming directreads.

Average Direct Write TimeSpecifies theaverage time forperforming directwrites.

Average Sectors Per DirectRead Specifies the








Return codesNone

CLI exampleThe following example adds the DB2 Direct IO resource model toMyProfile#MyRegion. This example sends the


DB2_High_DB_AvgSectorsPerDirectWrite event to Tivoli Business SystemsManager and to Tivoli Enterprise Console and sets the severity to fatal.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2DirectIO \-Log -LogEnable -p 12:00 -Agg no -ap 00:15 -NoAvg \-DelPar TbspNames_List "*" \-AddPar TbspNames_List "SALES*" \-DelPar AppNames_List "*" \-AddPar AppNames_List "INVOICING" \-AddPar AppNames_List "CHECK_PRINT" \-e DB2_High_DB_AvgSectorsPerDirectWrite -o 3 -h 1 -severity FATAL \–SendTBSM -SendTec


DB2 Fast Communication Manager

DescriptionMonitors the key health indications of a Fast Communication Manager. A FastCommunication Manager is a group of functions that provide internodalcommunication support. In a partitioned database environment, the FastCommunication Manager handles most communication between databasepartitions.

The DB2 Fast Communication Manager resource model monitors the followinginformation:v The percentage of Fast Communication Manager buffers or connection entries

used during processing within the partitioned database server.v The percentage of maximum Fast Communication Manager buffers, connection

entries, message anchors, or request blocks used during processing within thepartitioned database server.

v The status of the communication connection.


Internal name DB2FCMActivity

Category DB2

Indications Percent of Maximum FCM anchors In Use too high occurswhen the percentage of the maximum number of FastCommunication Manager message anchors used exceeds thePercent of Maximum FCM Message Anchors Used upperbound threshold.

Percent FCM Buffers In Use too high occurs when thepercentage of the maximum number of Fast CommunicationManager buffers currently in use exceeds the Percent ofMaximum FCM Buffers Used upper bound threshold.

Percent FCM Connections In Use too high occurs when thepercentage of the maximum number of Fast CommunicationManager connections currently in use exceeds the Percent ofMaximum FCM Connections Used upper bound threshold.

Percent of Maximum FCM Buffers Used too high occurswhen the percentage of the maximum number of FastCommunication Manager buffers used exceeds the Percent ofMaximum FCM Buffers Used upper bound threshold.

Percent of Maximum FCM Connections Used too highoccurs when the percentage of the maximum number of FastCommunication Manager connections used exceeds thePercent of Maximum FCM Connections Used upper boundthreshold.



Target managed resourceDB2PartitionManager




Clearingevents

Page

DB2 Percent ofMaximumFCM anchorsIn Use toohigh

DB2_High_PctMaxFcmMsgAnchorUsed Critical Yes 114

Percent FCMBuffers In Usetoo high

DB2_High_PctFcmBuffsInUse Critical Yes 115

Percent FCMConnections InUse too high

DB2_High_PctFcmConnInUse Critical Yes 116

Percent ofMaximumFCM BuffersUsed too high

DB2_High_PctMaxFcmBuffUsed Critical Yes 117

Percent ofMaximumFCMConnectionsUsed too high

DB2_High_PctMaxFcmConnUsed Critical Yes 118

Percent of Maximum FCM anchors In Use too high indicationOccurs when the percentage of the maximum number of Fast CommunicationManager message anchors used exceeds the Percent of Maximum FCM MessageAnchors Used upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of maximum FCM anchors used (<PctMaxFcmMsgAnchorUsed>) onDB2 instance <db2Instance>, database <db2Database>, and node number <db2Node>,has exceeded the threshold of <UpperBound>.




PctMaxFcmMsgAnchorUsedSpecifies the percentage of maximum Fast Communication Managermessage anchors during processing within the partitioned database server.






This indication has the following threshold:v Percent of Maximum FCM Message Anchors Used upper bound






Yes

Occurrences 3

Holes 2



Percent FCM Buffers In Use too high indicationOccurs when the percentage of the maximum number of Fast CommunicationManager buffers currently in use exceeds the Percent of Maximum FCM BuffersUsed upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of FCM buffers in use (<PctFcmBuffsInUse>) onDB2 instance <db2Instance>, database <db2Database>,and node number <db2Node> has exceeded the threshold of <UpperBound>.




PctFcmBuffsInUseSpecifies the percentage of Fast Communication Manager buffers usedduring the monitoring interval.






This indication has the following threshold:v Percent FCM Buffers In Use upper bound






Yes

Occurrences 3

Holes 2



Percent FCM Connections In Use too high indicationOccurs when the percentage of the maximum number of Fast CommunicationManager connections currently in use exceeds the Percent of Maximum FCMConnections Used upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of FCM connections in use (<PctFcmConnInUse>)on DB2 instance <db2Instance>, database <db2Database>,and node number <db2Node> has exceeded the thresholdof <UpperBound>.




PctFcmConnInUseSpecifies the percentage of Fast Communication Manager connectionentries that are used during the monitoring interval.






This indication has the following threshold:v Percent FCM Connections Currently In Use upper bound






Yes

Occurrences 3

Holes 2



Percent of Maximum FCM Buffers Used too high indicationOccurs when the percentage of the maximum number of Fast CommunicationManager buffers used exceeds the Percent of Maximum FCM Buffers Used upperbound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of maximum FCM buffers used (<PctMaxFcmBuffUsed>)on DB2 instance <db2Instance>, database <db2Database>, and node number <db2Node>,has exceeded the threshold of <UpperBound>.




PctMaxFcmBuffUsedSpecifies the percentage of maximum Fast Communication Managerbuffers used during processing.






This indication has the following threshold:v Percent of Maximum FCM Buffer Utilization upper bound






Yes

Occurrences 3

Holes 2



Percent of Maximum FCM Connections Used too high indicationOccurs when the percentage of the maximum number of Fast CommunicationManager connections used exceeds the Percent of Maximum FCM ConnectionsUsed upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of maximum FCM connections used (<PctMaxFcmConnUsed>)on DB2 instance <db2Instance>, database <db2Database>, and node number <db2Node>has exceeded the threshold of <UpperBound>.




PctMaxFcmConnUsedSpecifies the maximum percentage of Fast Communication Managerconnection entries used during processing.






This indication has the following threshold:v Percent of Maximum FCM Connections Used upper bound






Yes

Occurrences 3

Holes 2



ThresholdsThe following table lists the thresholds that can be set for the DB2 FastCommunication Manager resource model. For each threshold it shows the name, ashort description, and the default value:


Percent FCM Buffers InUse upper bound

The percentage of the maximum number of FastCommunication Manager buffers that arecurrently used within the partitioned databaseserver during the monitoring interval. The dbm<fcm_num_buffers> configuration parameter setsthe maximum number of Fast CommunicationManager buffers.

If the percentage of FCM buffers in use exceedsthe threshold value often enough, the PercentFCM Buffers In Use too high indication triggersan event.

90



Percent FCMConnections Currently InUse upper bound

The percentage of the maximum number of FastCommunication Manager connections that arecurrently used within the partitioned databaseserver during the monitoring interval. The dbm<fcm_num_connect> configuration parameter setsthe maximum number of Fast CommunicationManager buffers.

If the percentage of FCM connections currently inuse exceeds the threshold value often enough, thePercent FCM Connections In Use too highindication triggers an event.

90

Percent of MaximumFCM Buffer Utilizationupper bound

The percentage of the maximum number of FastCommunication Manager buffers that is thelowest number of free Fast CommunicationManager buffers reached since the last systemstart or restart. The dbm <fcm_num_buffers>configuration parameter sets the maximumnumber of Fast Communication Manager buffers.

If the percentage of maximum FCM bufferutilized exceeds the threshold value oftenenough, the Percent of Maximum FCM Buffers InUse too high indication triggers an event.

90

Percent of MaximumFCM Connections Usedupper bound

The percentage of the maximum number of FastCommunication Manager connections that is thelowest number of free Fast CommunicationManager connections reached since the lastsystem start or restart. The dbm<fcm_num_connect> configuration parameter setsthe maximum number of Fast CommunicationManager buffers.

If the percentage of Maximum FCM connectionsused exceeds the threshold value often enough,the Percent of Maximum FCM Connections InUse too high indication triggers an event.

90

Percent of MaximumFCM Message AnchorsUsed upper bound

The percentage of the maximum number of FastCommunication Manager anchors that is thelowest number of free Fast CommunicationManager anchors reached since the last systemstart or restart. The dbm <fcm_num_anchors>configuration parameter sets the maximumnumber of Fast Communication Manager buffers.

If the percentage of maximum FCM messageanchors used exceeds the threshold value oftenenough, the Percent of Maximum FCM anchorsIn Use too high indication triggers an event.

90

ParametersThe following table lists the parameters that can be set for the DB2 FastCommunication Manager resource model. The table shows the name, a shortdescription, and the default value for each parameter.




Partitionproperties tolog+

The partition FastCommunication Managerproperties available for logging.

v Percent FCM Buffers In Use

v Percent of Maximum FCM BuffersUsed

vPercent of Maximum FCM MessageAnchors Used

vPercent FCM Connections CurrentlyIn Use

v Percent of Maximum FCMConnections Used




DB2Partition Fast CommunicationsManager DB2Database.db2Database*

Specifies the name ofthe DB2 database.

DB2Instance.db2Instance*Specifies the name ofthe DB2 instance thatcontains thedatabase.


Percent FCM Buffers In UseSpecifies thepercentage of FastCommunicationManager buffersused during themonitoring interval.



DB2Partition Fast CommunicationsManager (continued) Percent FCM Connections

Currently In UseSpecifies thepercentage of FastCommunicationManager connectionentries that are usedduring themonitoring interval.

Percent of Maximum FCMBuffers Used

Specifies thepercentage ofmaximum FastCommunicationManager buffersused duringprocessing.

Percent of Maximum FCMConnections Used

Specifies themaximumpercentage of FastCommunicationManager connectionentries used duringprocessing.

Percent of Maximum FCMMessage Anchors Used

Specifies thepercentage ofmaximum FastCommunicationManager messageanchors duringprocessing withinthe partitioneddatabase server.


Return codesNone

CLI exampleThe following example adds the DB2 Fast Communication Manager resourcemodel to MyProfile#MyRegion. This example does not send theDB2_High_DB_PctMaxFcmBuffUsed event to Tivoli Business Systems Manager, butdoes send the event to Tivoli Enterprise Console.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2FCMActivity -c 60 \-Log -LogDisable \-e DB2_High_PctMaxFcmBuffUsed -o 5 -h 1 -severity FATAL -NoSendTBSM -SendTec \


DB2 Host Throughput

DescriptionMonitors the DB2 host throughput. The DB2 Host Throughput resource modelmonitors following for DB2 Connect DCS Database connections to host systems,represented by DB2Gateway objects:v The number of bytes sent plus the number of bytes received divided by the

cumulate host response time as total Host Throughput.v Statement execution elapsed time divided by the total number of statements

attempted.v The total network time for processing statements divided by the number of

statements attempted.v The host response time divided by the number of statements attempted.


Internal name DB2HostThroughput

Category DB2

Indications Host Throughput too low occurs when Host Throughput islower than the Host Throughput lower bound threshold.

Host Time Per Statement too high occurs when the HostTime Per Statement exceeds the Host Time Per Statementupper bound threshold.

Network Time Per Statement too high occurs whenNetwork Time Per Statement exceeds the Network Time PerStatement upper bound threshold.

Time Per Statement too high occurs when Time PerStatement exceeds the Time Per Statement upper boundthreshold.



Target managed resourceDB2Gateway



Clearingevents

Page

HostThroughputtoo low

DB2_Low_HostThroughput Critical Yes 124

Host Time PerStatement toohigh

DB2_High_HostTimePerStatement Critical Yes 125



Clearingevents

Page

Network TimePer Statementtoo high

DB2_High_NetworkTimePerStatement Critical Yes 126

Time PerStatement toohigh

DB2_High_TimePerStatement Critical Yes 126

Host Throughput too low indicationOccurs when Host Throughput is lower than the Host Throughput lower boundthreshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Host Throughput on DB2 Database <db2Database>, Instance <db2Instance>is <HostThroughput>, which is lower than <LowerBound>.






HostThroughputSpecifies the number of bytes sent plus the number of bytes receiveddivided by the cumulative host response time.

LowerBound.Specifies the indication’s threshold value.

This indication has the following threshold:v Host Throughput lower bound






Yes

Occurrences 3

Holes 2




Host Time Per Statement too high indicationOccurs when the Host Time Per Statement exceeds the Host Time Per Statementupper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Host Time Per Statement on DB2 Database <db2Database>, Instance <db2Instance>is <HostTimePerStatement>, which is higher than <UpperBound>.






HostTimePerStatementSpecifies the host response time divided by the number of statementsattempted.


This indication has the following threshold:v Host Time Per Statement upper bound






Yes

Occurrences 3

Holes 2




Network Time Per Statement too high indicationOccurs when Network Time Per Statement exceeds the Network Time PerStatement upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Network Time Per Statement DB2 Database <db2Database>, Instance <db2Instance>is <NetworkTimePerStatement>, which is higher than <UpperBound>.






NetworkTimePerStatementSpecifies the host response time minus the statement execution timedivided by the number of statements attempted.


This indication has the following threshold:v Network Time Per Statement upper bound






Yes

Occurrences 3

Holes 2



Time Per Statement too high indicationOccurs when Time Per Statement exceeds the Time Per Statement upper boundthreshold.


When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Time Per Statement DB2 Database <db2Database>, Instance <db2Instance>is <TimePerStatement>, which is higher than <UpperBound>.






TimePerStatementSpecifies the statement execution elapsed time divided by the number ofstatements attempted.


This indication has the following threshold:v Time Per Statement upper bound






Yes

Occurrences 3

Holes 2



ThresholdsThe following table lists the thresholds that can be set for the DB2 HostThroughput resource model. For each threshold it shows the name, a shortdescription, and the default value:



Host Throughput lowerbound

Specifies the number of bytes sent plus thenumber of bytes received divided by thecumulative host response time.

If the amount of host throughput is lower thanthe threshold value often enough, the HostThroughput is too low indication triggers anevent.

10000

Host Time Per Statementupper bound

Specifies the host response time divided by thenumber of statements attempted.

If the amount of host time per statement exceedsthe threshold value often enough, the Host TimePer Statement is too high indication triggers anevent.

3

Network Time PerStatement upper bound

Specifies the host response time minus thestatement execution time divided by the numberof statements attempted.

If the amount of network time per statementexceeds the threshold value often enough, theNetwork Time Per Statement is too highindication triggers an event.

2

Time Per Statementupper bound

Specifies the statement execution elapsed timedivided by the number of statements attempted.

If the amount of time per statement exceeds thethreshold value often enough, the Time PerStatement is too high indication triggers an event.

5

ParametersThe following table lists the parameters that can be set for the DB2 HostThroughput resource model. The table shows the name, a short description, andthe default value for each parameter.



Gatewayproperties tolog+

The gateway properties availablefor logging.

v Host Throughput

v Time Per Statement

v Network Time Per Statement

v Host Time Per Statement





DB2Gateway Host GatewayDB2Database.db2Database*



Host ThroughputSpecifies thenumber of bytessent plus thenumber of bytesreceived divided bythe cumulative hostresponse time.

Host Time Per StatementSpecifies the hostresponse timedivided by thenumber ofstatementsattempted.

Network Time Per StatementSpecifies the hostresponse time minusthe statementexecution timedivided by thenumber ofstatementsattempted.

Time Per StatementSpecifies thestatement executionelapsed timedivided by thenumber ofstatementsattempted.


Return codesNone


CLI exampleThe following example adds the DB2 Host Throughput resource model toMyProfile#MyRegion. This example sets logging with a historical duration period of12 hours. This example also sets the severity of the DB2_Low_HostThroughputevent to warning.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2HostThroughput -c 1800 \-Log -LogEnable -p 12:00 -Agg no -NoMin -NoMax -Avg \-t High_HostTimePerStatement 5.000000 \-e DB2_Low_HostThroughput -o 4 -h 1 -severity WARNING


DB2 Instance Status

DescriptionMonitors the availability of a DB2 instance. A database manager instance is alogical database manager environment similar to an image of the actual databasemanager environment. You can have several instances of the database managerproduct on the same workstation. You can use these instances to separate thedevelopment environment, and protect sensitive information from a particulargroup of people.

The DB2 Instance Status resource model monitors percentage of the maximumnumber of applications allowed that are connected to a database and processing aunit of work within the database manager instance during the monitoring interval.


Internal name DB2InstanceStatus

Category DB2

Indications Instance Status is down occurs when the Status propertycontains at least one of the values of the Status containedvalues parameter.

Percent Connections Executing is too high occurs when thepercentage of instances executing on an instance exceeds theupper threshold.



Target managed resourceDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager



Clearingevents

Page

Instance Statusis down

DB2_Down_Status Critical Yes 131

PercentConnectionsExecuting istoo high

DB2_High_PctConnectionsExecuting Warning No 132

Instance Status is down indicationOccurs when the Status property contains at lease one of the values of the Statuscontained values parameter.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The DB2 Instance <db2Instance> has a status of <db2Status>.






db2StatusSpecifies whether the DB2 instance is up or down.






Yes

Occurrences 1

Holes 0



Percent Connections Executing is too high indicationWhen the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of Connections Executing for DB2 Instance <db2Instance>is <PctConnectionsExecuting>, which is greater than <UpperBound>.





PctConnectionsExecutingSpecifies the percentage of the maximum number of applications allowedthat are connected to a database and processing a unit of work (within thedatabase manager instance) during the monitoring interval. The value isdefined as number of applications/maximum applications.



This indication has the following threshold:v Percent Connections Executing upper bound






No

Occurrences 3

Holes 2



ThresholdsThe following table lists the thresholds that can be set for the DB2 Instance Statusresource model. For each threshold it shows the name, a short description, and thedefault value:


Percent ConnectionsExecuting upper bound

If the percentage of private connections usedexceeds the threshold value often enough, thePercent Connections Executing is too highindication triggers an event.

75

ParametersThe following table lists the parameters that can be set for the DB2 Instance Statusresource model. The table shows the name, a short description, and the defaultvalue for each parameter.



InstanceConnectionproperties tolog+

The Instance Connection propertiesthat are available for logging.

v Percent Connections Executing



Instance StatusDown

The Instance Status is down eventis generated when the propertystatus contains one of the values ofthis parameter.

v down

Instance Statusproperties tolog+

The Instance Status properties thatare available for logging.

v Status

v Counter Reset Timestamp




DB2Instance ConnectionsDB2Instance.db2Instance*


Percent Connections ExecutingSpecifies thepercentage of themaximum numberof applicationsallowed that areconnected to adatabase andprocessing a unit ofwork (within thedatabase managerinstance) during themonitoring interval.



DB2Instance StatusCounter Reset Timestamp

Specifies the dateand time that thecounters were resetfor the database.

DB2Up Indicates that theDB2 instance isrunning.


DB2DownIndicates that theDB2 instance is notrunning.


Return codesNone

CLI exampleThe following example adds the DB2 Instance Status resource model toMyProfile#MyRegion.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2InstanceStatus -c 1200 \-t High_PctConnectionsExecuting 65.000000 \


DB2 Locks and Deadlocks

DescriptionProvides statistics about locks and deadlocks for applications and databases. A lockis a means of preventing uncommitted changes made by one application processfrom being perceived by another application process and for preventing oneapplication process from updating data that is being accessed by another process.A deadlock is a condition under which a transaction cannot proceed because it isdependent on exclusive resources that are locked by some other transaction, whichin turn is dependent on exclusive resources in use by the original transaction.

This resource model can aid in diagnosing throughput problems either at theapplication or database level. The occurrence of a deadlock causes the applicationsinvolved to halt execution and at least one application to be rolled back, whichcauses a large reduction in database effectiveness. Infrequently, an isolateddeadlock might occur during normal processing, which usually does not indicate aproblem. However, a frequent pattern of deadlocks (or isolated deadlocks thatalways occur when certain applications are run simultaneously) indicates afundamental problem with the design and interaction of applications accessing thesame tables simultaneously.

The DB2 Locks and Deadlocks resource model monitors the following information:v The average number of locks held by each currently connected application in the

database.v The number of deadlocks or lock escalations detected in the database during the

last monitoring interval.v The number of times that a request to lock an object timed out instead of being

granted during the monitoring interval.v The percentage of rollbacks that were due to deadlock during the monitoring

interval.v The total number of deadlocks or lock escalations that occurred for the

application during the monitoring interval.v The percentage of the total number of internal rollbacks due to internal

deadlocks.v The percentage of space used in the locklist by the database or application.v The average number of lock escalations per connection.


Internal name DB2Locks

Category DB2



Indications Application Deadlocks too high occurs when the number ofdeadlocks by any connected application exceed theApplication Deadlocks upper bound threshold during themonitoring interval.

Average Lock Escalations Per Connection too high occurswhen the Average Lock Escalations Per Connection in adatabase exceeds the Average Lock Escalations PerConnection upper bound threshold.

Average Locks Held Per Application too high occurs whenthe Average Locks Held Per Application in a databaseexceeds the Average Locks Held Per Application upperbound threshold.

Deadlocks Delta too high occurs when the Deadlocks Deltafrom the last monitoring interval exceeds the DeadlocksDelta upper bound threshold.

Lock Escalations by an Application too high occurs whenthe number of lock escalations by any connected applicationduring the monitoring interval exceed the Lock Escalationsby an Application upper bound threshold.

Indications (continued) Lock Escalations Delta too high occurs when the LockEscalations Delta in a database exceeds the Lock EscalationsDelta upper bound threshold.

Lock Timeouts Delta too high occurs when the LockTimeouts Delta in a database exceeds the Lock TimeoutsDelta upper bound threshold.

Percent Deadlock Rollbacks too high occurs when thePercent Deadlock Rollbacks in a database exceeds thePercent Deadlock Rollbacks upper bound threshold.

Percent Internal Deadlocked Rollbacks too high occurswhen the Percent Internal Deadlocked Rollbacks exceeds thePercent Internal Deadlocked Rollbacks upper boundthreshold.

Percent Lock List Used By An Application too high occurswhen the Percent Lock List Used in a database by anapplication exceeds the Percent Lock List Used by anApplication upper bound threshold.

Percent Lock List Used in a database too high occurs whenthe Percent Lock List Used In a database exceeds the PercentLock List Used in a Database upper bound threshold.







Clearingevents

Page

ApplicationDeadlocks toohigh

DB2_High_App_Deadlocks Warning No 138

Average LockEscalations PerConnection toohigh

DB2_High_AvgLockEscalationConn Warning No 139

Average LocksHeld PerApplicationtoo high

DB2_High_AvgLocksHeld Warning No 140

DeadlocksDelta too high

DB2_High_DeadlocksDelta Warning No 141

LockEscalations byan Applicationtoo high

DB2_High_App_LockEscalations Warning No 142

LockEscalationsDelta too high

DB2_High_LockEscalationsDelta Warning No 143

Lock TimeoutsDelta too high

DB2_High_LockTimeoutsDelta Warning No 144

PercentDeadlockRollbacks toohigh

DB2_High_PctDeadlockRollbacks Critical Yes 145

PercentInternalDeadlockedRollbacks toohigh

DB2_High_PctIntDeadlockedRollbacks Critical Yes 146

Percent LockList Used ByAn Applicationtoo high

DB2_High_App_PctLockListUsed Warning No 147

Percent LockList Used in adatabase toohigh

DB2_High_DB_PctLockListUsed Warning No 148

Application Deadlocks too high indicationOccurs when the number of deadlocks by any connected application exceed theApplication Deadlocks upper bound threshold during the monitoring interval.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Deadlocks by Application <db2AppName> on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <ApplDeadLocks>,which is higher than <UpperBound>.









ApplDeadLocksSpecifies the total number of deadlocks that occurred for the applicationduring the monitoring interval.


This indication has the following threshold:v Application Deadlocks upper bound






No

Occurrences 3

Holes 0



Average Lock Escalations Per Connection too high indicationOccurs when the Average Lock Escalations Per Connection in a database exceedsthe Average Lock Escalations Per Connection upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Lock Escalations Per Connection on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgLockEscalationsConn>,which is higher than <UpperBound>.








AvgLockEscalationsConnSpecifies the average lock escalations per connections during themonitoring interval.


This indication has the following threshold:v Average Lock Escalations Per Connection upper bound






No

Occurrences 2

Holes 1



Average Locks Held Per Application too high indicationOccurs when the Average Locks Held Per Application in a database exceeds theAverage Locks Held Per Application upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Average Locks Held Per Application on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <AvgLocksHeld>,which is higher than <UpperBound>.








AvgLocksHeldSpecifies the average number of locks currently held.


This indication has the following threshold:v Average Locks Held Per Application upper bound






No

Occurrences 3

Holes 2



Deadlocks Delta too high indicationOccurs when the Deadlocks Delta from the last monitoring interval exceeds theDeadlocks Delta upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Deadlocks Delta on DB2 Database <db2Database>, Instance <db2Instance>,Node <db2Node> is <DeadlocksDelta>,which is higher than <UpperBound>.








DeadlocksDeltaSpecifies the total number of deadlocks that occurred for the applicationduring the monitoring interval.


This indication has the following threshold:v Deadlocks Delta upper bound






No

Occurrences 3

Holes 2



Lock Escalations by an Application too high indicationOccurs when the number of lock escalations by any connected application duringthe monitoring interval exceed the Lock Escalations by an Application upperbound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Lock Escalations by Application <db2AppName> on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <LockEscalations>,which is higher than <UpperBound>.









LockEscalationsSpecifies the total number of lock escalations for the application during themonitoring interval.


This indication has the following threshold:v Lock Escalations by an Application upper bound






No

Occurrences 3

Holes 0



Lock Escalations Delta too high indicationOccurs when the Lock Escalations Delta in a database exceeds the Lock EscalationsDelta upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Lock Escalations Delta on DB2 Database <db2Database>, Instance <db2Instance>,Node <db2Node> is <LockEscalationsDelta>,which is higher than <UpperBound>.








LockEscalationsDeltaSpecifies the total number of lock escalations during the monitoringinterval.


This indication has the following threshold:v Lock Escalations Delta upper bound






No

Occurrences 3

Holes 2



Lock Timeouts Delta too high indicationOccurs when the Lock Timeouts Delta in a database exceeds the Lock TimeoutsDelta upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Lock Timeouts Delta on DB2 Database <db2Database>, Instance <db2Instance>,Node <db2Node> is <LockTimeoutsDelta>,which is higher than <UpperBound>.








LockTimeoutsDeltaSpecifies the total time that the application waits for a lock to be granted toit during the monitoring interval.


This indication has the following threshold:v Lock Timeouts Delta upper bound






No

Occurrences 3

Holes 2



Percent Deadlock Rollbacks too high indicationOccurs when the Percent Deadlock Rollbacks in a database exceeds the PercentDeadlock Rollbacks upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Deadlock Rollbacks on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is<PctDeadlockRollbacks, which is higher than <UpperBound>.








PctDeadlockRollbacksSpecifies the percentage of the total number of rollbacks due to deadlocks.


This indication has the following threshold:v Percent Deadlock Rollbacks upper bound






Yes

Occurrences 3

Holes 1



Percent Internal Deadlocked Rollbacks too high indicationOccurs when the Percent Internal Deadlocked Rollbacks exceeds the PercentInternal Deadlocked Rollbacks upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Internal Deadlocked Rollbacks on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <PctIntDeadlockedRollbacks>,which is higher than <UpperBound>.








PctIntDeadlockedRollbacksSpecifies the percentage of the total number of internal rollbacks due todeadlocks.


This indication has the following threshold:v Percent Internal Deadlocked Rollbacks upper bound






Yes

Occurrences 3

Holes 1



Percent Lock List Used By An Application too high indicationOccurs when the Percent Lock List Used in a database by an application exceedsthe Percent Lock List Used by an Application upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Lock List Used by Application <db2AppName> onDB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node>is <PctLockListUsed>, which is higher than <UpperBound>.









PctLockListUsedSpecifies the percentage of space used in the locklist.


This indication has the following threshold:v Percent Lock List Used by an Application upper bound






No

Occurrences 3

Holes 1



Percent Lock List Used in a database too high indicationOccurs when the Percent Lock List Used In a database exceeds the Percent LockList Used in a Database upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Lock List Used on DB2 Database <db2Database>, Instance <db2Instance>,Node <db2Node> is <PctLockListUsed>, which is higher than <UpperBound>.







PctLockListUsedSpecifies the percentage of space used in the locklist.



This indication has the following threshold:v Percent Lock List Used in a Database upper bound






No

Occurrences 3

Holes 1



ThresholdsThe following table lists the thresholds that can be set for the DB2 Locks andDeadlocks resource model. For each threshold it shows the name, a shortdescription, and the default value:


Application Deadlocksupper bound

The total number of deadlocks that occurred foran application during the monitoring interval.Log the returned value to determine if anapplication has contention problems. Modify theapplication to enable it to execute concurrently.

If the number of deadlocks for an applicationexceeds the threshold value often enough, theApplication Deadlocks too high indicationtriggers an event.

6



Average Lock EscalationsPer Connection upperbound

The average number of lock escalations perconnection at the database level.

A high returned value indicates that the locklistspace available to applications keeps filling upcausing escalations and excessive lock waits foryour applications. The following conditions cancause the return of a high value:

v The size of the maximum storage for locklistsis too small and causes the locklist to fill up.

v The <maxlocks> configuration parameter is toosmall.

v Applications are receiving more locks thanthey really need.

A low returned value indicates that the value forthe locklist is too high and wasting memory inthe locklist.

If the average number of lock escalations perconnection exceeds the threshold value oftenenough, the Average Lock Escalations PerConnection too high indication triggers an event.

5

Average Locks Held PerApplication upper bound

The average number of locks held by eachcurrently connected application in the database.You receive a high return value if one or moreapplications uses an excessive number of locks.

If the average number of locks held perapplication exceeds the threshold value oftenenough, the Average Locks Held Per Applicationtoo high indication triggers an event.

5

Deadlocks Delta upperbound

The number of deadlocks detected in thedatabase during the last monitoring interval. Logthe returned value to determine whetherapplications are experiencing conflict problems inthe database.

The following are possible causes of deadlocks:

v Lock escalations are occurring for the database.

v An application locks tables explicitly whensystem generated row locks are sufficient.

v An application uses an inappropriate isolationlevel when binding.

v Database catalog tables are locked forrepeatable read.

v Applications are receiving the same locks indifferent orders.

If the deadlocks delta exceeds the threshold valueoften enough, the Deadlocks Delta too highindication triggers an event.

4



Lock Escalations by anApplication upper bound

The total number of lock escalations for anapplication during the monitoring interval. Logthe returned value to evaluate the settings of thelocklist and the <maxlocks> databaseconfiguration parameters.

A lock is escalated when the total number oflocks held by the application reaches themaximum amount of lock list space available tothe application. Lock escalations can result in adecrease in concurrency between applicationsconnected to a database.

The following are possible causes of lockescalations:

v A small locklist size for the number ofconcurrent applications. The value of thelocklist parameter determines the size of thelock list.

v A small percentage of the locklist usable byeach application. The value of the <maxlocks>parameter determines the percentage.

The following are resolutions to the previouscauses:

v Increase the value of the locklist.

v Increase the value of the <maxlocks> parameter.

v Determine if one or more applications uses anexcessive number of locks.

v Identify the applications that have a largenumber of locks.

v Use the returned value from Percent Lock ListUsed by an Application to identify theapplications that hold too much of the locklist.

If any connected application exceeds thethreshold value often enough, the LockEscalations by an Application too high indicationtriggers an event.

6

Lock Escalations Deltaupper bound

The number of lock escalations that occurred inthe database during the monitoring interval.

Log the value to evaluate the settings of thelocklist and the <maxlocks> configurationparameters. Lock escalations can result in adecrease in concurrency between applicationsconnected to a database.

If the lock escalations delta exceeds the thresholdvalue often enough, the Lock Escalations Deltatoo high indication triggers an event.

3



Lock Timeouts Deltaupper bound

The number of times that a request to lock anobject timed out instead of being granted duringthe monitoring interval.

A high return value indicates that yourapplication holds locks for long durations. A lowreturn value indicates that the <locktimeout>parameter is set too high.

If the lock timeouts delta in a database exceedsthe threshold value often enough, the LockTimeouts Delta too high indication triggers anevent.

10

Percent DeadlockRollbacks upper bound

The percentage of rollbacks that are due to thedeadlock during the monitoring interval.

A high returned value indicates that applicationsare experiencing conflict problems. Rollbacks dueto deadlocks lower the database throughput.Attempt to resolve the problem by determiningin which applications the deadlocks areoccurring. Modify those applications to betterenable them to execute concurrently.

If the percentage of deadlock rollbacks in adatabase exceeds the threshold value oftenenough, the Percent Deadlock Rollbacks too highindication triggers an event.

80

Percent InternalDeadlocked Rollbacksupper bound

The percentage of the total number of internalrollbacks due to deadlocks.

Log the returned value to distinguish betweenrollbacks caused by internal deadlocks fromrollbacks caused by other situations. The returnedvalue specifies the percentage of internaldeadlocks since the first database connections orthe last reset of the database monitor counters.

If the percentage of internal deadlocked rollbacksexceeds the threshold value often enough, thePercent Internal Deadlocked Rollbacks too highindication triggers an event.

80

Percent Lock List Usedby an Application upperbound

The percentage of space used in the locklist byany connected application. Log the returnedvalue to determine if an application holds toomuch of the locklist. Other applicationsexperience lock escalations when an applicationholds too much of the locklist.

If the percentage of lock lists used by anyconnected application in the database exceeds thethreshold value often enough, the Percent LockList Used by an Application too high indicationtriggers an event.

50



Percent Lock List Usedin a Database upperbound

The percentage of space used in the database’slocklist.

If the percentage of lock lists used in the databaseexceeds the threshold value often enough, thePercent Lock List Used in a Database too highindication triggers an event.

50

ParametersThe following table lists the parameters that can be set for the DB2 Locks andDeadlocks resource model. The table shows the name, a short description, and thedefault value for each parameter.



ApplicationNames tomonitor

The application name for eachapplication to monitor. Thefollowing are options to enterfor application names tomonitor:




*


Application lock propertiesavailable for logging.

v Deadlocks

v Percent Lock List Used

v Lock Escalations


Database lock propertiesavailable for logging.

v Percent Lock List Used

v Lock Timeouts Delta

v Percent Internal DeadlockedRollbacks

v Deadlocks Delta

v Percent Deadlock Rollbacks

v Lock Escalations Delta

v Average Lock Escalation Connection





DB2Partition Database Locks/DeadlocksAverage Lock EscalationConnection

Specifies theaverage lockescalations perconnections duringthe monitoringinterval.

Average Locks HeldSpecifies theaverage number oflocks currently held.




Deadlocks DeltaSpecifies the totalnumber ofdeadlocks thatoccurred for theapplication duringthe monitoringinterval.

Lock Escalations DeltaSpecifies the totalnumber of lockescalations duringthe monitoringinterval.

Lock Timeouts DeltaSpecifies the totaltime that theapplication waits fora lock to be grantedto it during themonitoring interval.



DB2Partition Database Locks/Deadlocks(continued) Percent Deadlock Rollbacks

Specifies thepercentage of thetotal number ofrollbacks due todeadlocks.

Percent Int DeadlockedRollbacks

Specifies thepercentage of thetotal number ofinternal rollbacksdue to deadlocks.

Percent Lock List UsedSpecifies thepercentage of spaceused in the locklist.

DB2Application ApplicationLocks/Deadlocks DB2Application.db2ApplyID*

Specifies thesubscriber user IDthat started thisinvocation of theApply program.





DeadlocksSpecifies the totalnumber ofdeadlocks thatoccurred for theapplication duringthe monitoringinterval.



DB2Application ApplicationLocks/Deadlocks (continued) Lock Escalations

Specifies the totalnumber of lockescalations for theapplication duringthe monitoringinterval.

Percent Lock List UsedSpecifies thepercentage of spaceused in the locklist.


Return codesNone

CLI exampleThe following example adds the DB2 Locks and Deadlocks resource model toMyProfile#MyRegion.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2Locks \-t High_AppPctLockListUsed 60.000000 \-DelPar AppNames_List "*" \-AddPar AppNames_List "ACCT*" \


DB2 Lock Waits

DescriptionMonitors the change in the number of lock waits within a database as well as thepercentage of applications in a lock wait state. Lock waits is the total number oftimes that applications or connections waited for locks. At the database level, thisis the total number of times that applications have had to wait for locks within thisdatabase. At the application-connection level, this is the total number of times thatthis connection requested a lock but had to wait because another connection wasalready holding a lock on the data. Excessive or repeatable patterns of lock waitsindicate problems with the interaction of applications accessing the same tables.

If the average lock wait time is high, you should look for applications that holdmany locks, or have lock escalations, with a focus on tuning your applications toimprove concurrency. If escalations are the for a high average lock wait time, thenthe values of one or both of the <locklist> and <maxlocks> configuration parametersmight be too low.

The DB2 Lock Waits resource model monitors the following information:v The number of applications that are currently waiting for locks in the database.v The average time, in seconds, that applications wait for a lock within the

database within the monitoring interval.v The number of times that applications had to wait for locks in the database

during the monitoring interval.v The percentage of currently connected applications that are waiting for a lock in

the database.v The total time, in seconds, that the application waits for a lock to be granted to

it during the monitoring interval.


Internal name DB2LockWaits

Category DB2

Indications Application Lock Wait Time too high occurs when the lockwait time for any application running in the monitored limitis set in the Application Lock Wait Time upper boundthreshold.

Lock Waits Delta too high occurs when the number of timesan application has to wait for a lock exceeds the Lock WaitsDelta upper bound threshold.

Percent Applications In Lock Wait too high occurs when thepercentage of applications active in the database exceeds thePercent Applications In Lock Wait upper bound threshold.







Clearingevents

Page

ApplicationLock Wait Timetoo high

DB2_High_ApplLockWaitTime Critical Yes 158

Lock WaitsDelta too high

DB2_High_LockWaitsDelta Warning No 159

PercentApplications InLock Wait toohigh

DB2_High_PctApplsInLockWait Critical Yes 160

Application Lock Wait Time too high indicationOccurs when the lock wait time for any application running in the monitored limitis set in the Application Lock Wait Time upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Lock Wait Time (<LockWaitTime>) of the instance(db2Instance=<db2Instance>; db2Database=<db2Database>; db2Node=<db2Node>)is greater than <UpperBound>.




LockWaitTimeSpecifies the total time, in seconds, that the application waits for a lock tobe granted to it during the monitoring interval.






This indication has the following threshold:v Application Lock Wait Time upper bound







No

Occurrences 1

Holes 0



Lock Waits Delta too high indicationOccurs when the number of times an application has to wait for a lock exceeds theLock Waits Delta upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property LockWaitsDelta (<LockWaitsDelta>) of the instance(db2Node=<db2Node>; db2Database=<db2Database>; db2Instance=<db2Instance>)is greater than <UpperBound>.




LockWaitsDeltaSpecifies the total time that the application waits for a lock to be granted toit during the monitoring interval.





This indication has the following threshold:v Lock Waits Delta upper bound







No

Occurrences 3

Holes 1



Percent Applications In Lock Wait too high indicationOccurs when the percentage of applications active in the database exceeds thePercent Applications In Lock Wait upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property PctApplsInLockWait (<PctApplsInLockWait>) of the instance(db2Node=<db2Node>; db2Database=<db2Database>; db2Instance=<db2Instance>)is greater than <UpperBound>.




PctApplsInLockWaitSpecifies the percentage of currently connected applications that arewaiting for a lock in the database.





This indication has the following threshold:v Percent Applications In Lock Wait upper bound







Yes

Occurrences 2

Holes 1



ThresholdsThe following table lists the thresholds that can be set for the DB2 Lock Waitsresource model. For each threshold it shows the name, a short description, and thedefault value:


Application Lock WaitTime upper bound

The total time, in seconds, that the applicationwaits for a granted lock during the monitoringinterval.

A high average lock wait time indicates thatsome applications are holding many locks orhave lock escalations. Refine those applications toimprove concurrency. If lock escalations are thereason for a high average lock wait time, increasethe values of the <locklist> and <maxlocks>configuration parameters.

If the application lock wait time exceeds thethreshold value often enough, the ApplicationLock Wait Time too high indication triggers anevent.

10

Lock Waits Delta upperbound

The number of times that applications wait forlocks in the database during the monitoringinterval.

If the lock waits delta exceeds the threshold valueoften enough, the Lock Waits Delta too highindication triggers an event.

10



Percent Applications InLock Wait upper bound

The percentage of applications that are currentlyconnected and are waiting on a lock in thedatabase.

A high value indicates that the applications haveconcurrency problems. Identify applications thatare holding locks or exclusive locks for longperiods of time and determine whether they canrelease their locks more often.

If the percentage of applications in lock waitexceeds the threshold value often enough, thePercent Applications in Lock Wait too highindication triggers an event.

85

ParametersThe following table lists the parameters that can be set for the DB2 Lock Waitsresource model. The table shows the name, a short description, and the defaultvalue for each parameter.



DatabaseApplicationproperties tolog+

The Database Application Lockproperties available for logging.

v Lock Wait Time


The Database Lock propertiesavailable for logging.

v Percent Applications in Lock Wait

v Lock Waits Delta




DB2Partition DatabaseLocksDB2Database.db2Database*




DB2Partition DatabaseLocks (continued)DB2Instance.db2Instance*



Lock Waits DeltaSpecifies the totaltime that theapplication waits fora lock to be grantedto it during themonitoring interval.

Percent Applications in LockWait Specifies the

percentage ofcurrently connectedapplications that arewaiting for a lock inthe database.

DB2Application ApplicationLocksDB2Application.db2ApplyID*






Lock Wait TimeSpecifies the totaltime, in seconds,that the applicationwaits for a lock tobe granted to itduring themonitoring interval.



Return codesNone

CLI exampleThe following example adds the DB2 Lock Waits resource model toMyProfile#MyRegion. This example disables logging and sends theDB2_High_LockWaitsDelta event to Tivoli Enterprise Console.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2LockWaits -c 600 \-Log -LogDisable\-e DB2_High_LockWaitsDelta -o 2 -h 0 -severity CRITICAL -SendTec


DB2 Logging

DescriptionMonitors logging functions performed by the DB2 logging system. All databaseshave logs associated with them that keep records of database changes. DB2 usescircular and archive logging. In circular logging, records are overwritten when ifthey are no longer needed by an active database. Archive logging enables forwardrecovery using active and archived logs to any point in time before the failure,rather than only to the point in time of a full backup.

The DB2 Logging resource model helps quantify the amount of input and outputon a device that is attributable to activity from the database, helps determine ifmoving a log will improve performance, and helps evaluate the allocated amountof log space.

The DB2 Logging resource model monitors the following informationv The number of log pages read from and written to disk.v The number of secondary log files that are currently used for a database.v The total amount of log input and output. This amount is the sum of the

number of log pages read and the number of log pages written within themonitoring interval.

v The percentage of log space used by the primary and secondary log.


Internal name DB2Logging

Category DB2

Indications Log Page Reads too high occurs when the Log Page Readscounter exceeds the Log Page Reads upper bound threshold.

Log Page Writes too high occurs when the Log Page Writescounter exceeds the Log Page Writes upper bound threshold.

Percent Log Space Used By Primary Log too high occurswhen the Percent Log Space Used By Primary Log counterexceeds the Percent Log Space Used By Primary Log upperbound threshold.

Percent Log Space Used By Secondary Log too high occurswhen the Percent of Log Space Used By the Secondary logexceeds the Percent Log Space Used By Secondary upperbound threshold.

Total Log Input Output too high occurs when the Total LogInput Output counter exceeds the Total Log Input Outputupper bound threshold.

Total Secondary Logs In Use too high occurs when theTotal Secondary Logs In Use counter exceeds the TotalSecondary Logs In Use upper bound threshold.







Clearingevents

Page

Log PageReads toohigh

DB2_High_LogPageReads Warning Yes 166

Log PageWrites toohigh

DB2_High_LogPageWrites Warning Yes 167

Percent LogSpace UsedBy PrimaryLog too high

DB2_High_PctLogSpaceUsedByPrimary Critical Yes 168

Percent LogSpace UsedBy SecondaryLog too high

DB2_High_PctLogSpaceUsedBySecondary Critical Yes 169

Total LogInput Outputtoo high

DB2_High_TotalLogInputOutput Warning Yes 170

TotalSecondaryLogs In Usetoo high

DB2_High_TotalSecondaryLogInUse Warning Yes 171

Log Page Reads too high indicationOccurs when the Log Page Reads counter exceeds the Log Page Reads upperbound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The number of log page reads (<LogPageReads>) of the instance(db2Node=<db2Node>;db2Database=<db2Database>;db2Instance=<db2Instance>)is greater than <UpperBound>.




LogPageReadsSpecifies the number of log pages read from the disk by the DB2 loggingsystem.






This indication has the following threshold:v Log Page Reads upper bound






No

Occurrences 1

Holes 0



Log Page Writes too high indicationOccurs when the Log Page Writes counter exceeds the Log Page Writes upperbound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The number of Log Page Writes (<LogPageWrites>) of the instance(db2Node=<db2Node>;db2Database=<db2Database>;db2Instance=<db2Instance>)is greater than <UpperBound>.




LogPageWritesSpecifies the number of log pages written to the disk by the DB2 loggingsystem.






This indication has the following threshold:v Log Page Writes upper bound






No

Occurrences 1

Holes 0



Percent Log Space Used By Primary Log too high indicationOccurs when the Percent Log Space Used By Primary Log counter exceeds thePercent Log Space Used By Primary Log upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of log space used by the primary log(<PctLogSpaceUsedByPrimary>) on DB2 instance <db2Instance>,database <db2Database>, node <db2Node>)is greater than <UpperBound>.




PctLogSpaceUsedByPrimarySpecifies the percentage of log space used by the primary log.






This indication has the following threshold:v Percent Log Space Used By Primary Log upper bound






Yes

Occurrences 2

Holes 1



Percent Log Space Used By Secondary Log too high indicationOccurs when the Percent of Log Space Used By the Secondary log exceeds thePercent Log Space Used By Secondary upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of log space used by the secondary log(<PctLogSpaceUsedBySecondary>) on DB2 instance <db2Instance>,database <db2Database>, node <db2Node> is greater than<UpperBound>.




PctLogSpaceUsedBySecondarySpecifies the percentage of log space used by the secondary log.






This indication has the following threshold:v Percent Log Space Used By Secondary Log upper bound






Yes

Occurrences 2

Holes 1



Total Log Input Output too high indicationOccurs when the Total Log Input Output counter exceeds the Total Log InputOutput upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Total Log Input Output (<TotalLogInputOutput>)on DB2 instance <db2Instance>, database <db2Database>, node <db2Node>is greater than <UpperBound>.




TotalLogInputOutputSpecifies the total amount of log input and output. This amount consists ofthe sum of the number of log pages read and the number of log pageswritten within the monitoring interval.





This indication has the following threshold:


v Total Log Input Output upper bound






No

Occurrences 1

Holes 0



Total Secondary Logs In Use too high indicationOccurs when the Total Secondary Logs In Use counter exceeds the Total SecondaryLogs In Use upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The total number of secondary logs in use (<TotalSecondaryLogsInUse>)of the instance (db2Node=<db2Node>;db2Database=<db2Database>;db2Instance=<db2Instance>) is greater than <UpperBound>.




TotalSecondaryLogsInUseSpecifies the total number of secondary log files that are currently beingused.





This indication has the following threshold:v Total Secondary Logs In Use upper bound







No

Occurrences 1

Holes 0



ThresholdsThe following table lists the thresholds that can be set for the DB2 Loggingresource model. For each threshold it shows the name, a short description, and thedefault value:


Log Page Reads upperbound

The number of log pages read from the disk bythe logger. You can use this element inconjunction with an operating system monitor toquantify the amount of I/O on a device that isattributable to database activity.

If the number of log pages read exceeds thethreshold value often enough, the Log PageReads too high indication triggers an event.

50

Log Page Writes upperbound

The number of log pages written to the disk bythe logger. You can use this element inconjunction with an operating system monitor toquantify the amount of I/O on a device that isattributable to database activity.

If the number of log pages written exceeds thethreshold value often enough, the Log PageWrites too high indication triggers an event.

50

Percent Log Space UsedBy Primary Log upperbound

If the percent of log space used by a primary logexceeds the threshold value often enough, thePercent Log Space Used by Primary Log too highindication triggers an event.

Uses the returned value to help you evaluate theallocated amount of primary log space and refinethe <logbufsz>, <logfilsiz>, and <logprimary>parameters. You must use circular logging toreceive a valid value.

85



Percent Log Space UsedBy Secondary Log upperbound

This value indicates the current dependency onsecondary logs. You use secondary logs whenyou have a circular logging and the primary logfiles are full.

A consistently high value indicates that you needone or more of the following:

v Larger log files

v Additional primary log files

v More frequent COMMIT statements withinyour applications

This value is zero if the no secondary log files aredefined or if you enable log retention.

If the percent of log space used by a secondarylog exceeds the threshold value often enough, thePercent Log Space Used by Secondary Log toohigh indication triggers an event.

85

Total Log Input Outputupper bound

The sum of the number of log pages read and thenumber of log pages written within themonitoring interval determines the amount. Youcan use this element in conjunction with anoperating system monitor to quantify the amountof I/O on a device that is attributable to databaseactivity. The total amount of log input andoutput.

If the total log input exceeds the threshold valueoften enough, the Total Log Input Output to highindication triggers an event.

1000

Total Secondary Logs InUse upper bound

The total number of secondary log files that thedatabase currently uses. This value is zero if thedatabase does not have any secondary log filesthat are defined or if you enable log retention oruser exit.

If the total number of secondary logs in useexceeds the threshold value often enough, theTotal Secondary Logs In Use too high indicationtriggers an event.

10

ParametersThe following table lists the parameters that can be set for the DB2 Loggingresource model. The table shows the name, a short description, and the defaultvalue for each parameter.





The Database Log propertiesavailable for logging.

v Log Page Writes

v Total Log Input/Output

v Percent Log Space Used by Primary

v Total Secondary Logs in Use

v Log Page Reads

v Percent Log Space Used by Secondary




DB2Partition LoggingDB2Database.db2Database*

Specifies the name ofthe DB2 database.



Log Page ReadsSpecifies the numberof log pages readfrom the disk by theDB2 logging system.

Log Page WritesSpecifies the numberof log pages writtento the disk by theDB2 logging system.

Percent Log Space Used byPrimary Specifies the

percentage of logspace used by theprimary log.

Percent Log Space Used bySecondary

Specifies thepercentage of logspace used by thesecondary log.



DB2Partition Logging (continued)Total Log Input/Output

Specifies the totalamount of log inputand output.

Total Secondary Logs in UseSpecifies the totalnumber of secondarylog files that arecurrently being used.


Return codesNone

CLI exampleThe following example adds the DB2 Logging resource model toMyProfile#MyRegion. This example enables logging with a historical durationperiod of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2Logging -c 600 \-Log -LogEnable -p 12:00 -Agg no -NoMin -NoMax -Avg \-t High_LogPageReads 45.000000 \-t High_LogPageWrites 70.000000 \


DB2 Package Cache

DescriptionMonitors the package cache that stores the package and section informationrequired for the execution of dynamic and static SQL statements. The package andsection information required for the execution of dynamic and static SQLstatements are placed in the package cache as required. This information isrequired whenever a dynamic or static statement is being executed. The packagecache exists at a database level. This means that agents with similar environmentscan share the benefits of another agent’s work. For static SQL statements, this canmean avoiding catalog access. For dynamic SQL statements, this can meanavoiding the cost of compilation.

The DB2 Package Cache resource model monitors the following information:v The number of times that a section is loaded into the package cache because an

application finds that the section it wants is not in the package cache.v The number of times that an application looked for a section in the package

cache.v The percentage of the package cache hit ratio for the last monitoring interval.


Internal name DB2PackageCache

Category DB2

Indications Package Cache Inserts too high occurs when the PackageCache Inserts counter exceeds the Package Cache Insertsupper bound threshold.

Package Cache Lookups too high occurs when the numberof Package Cache Lookups exceeds the Package CacheLookups upper bound threshold.

Percent Package Cache Hits too low occurs when thePercent Package Cache Hits counter is lower than thePercent Package Cache Hits lower bound threshold.






Clearingevents

Page

Package CacheInserts too high

DB2_High_PackageCacheInserts Warning Yes 177

Package CacheLookups toohigh

DB2_High_PackageCacheLookups Warning Yes 178



Clearingevents

Page

Percent PackageCache Hits toolow

DB2_Low_PctPackageCacheHits Warning Yes 179

Package Cache Inserts too high indicationOccurs when the Package Cache Inserts counter exceeds the Package Cache Insertsupper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The number of Package Cache Inserts (<PackageCacheInserts>) forDB2 database <db2Database> and instance <db2Instance>is greater than <UpperBound>.




PackageCacheInsertsSpecifies the number of times that a section is loaded into the packagecache because an application finds that the section it wants is not in thepackage cache.




This indication has the following threshold:v Package Cache Inserts upper bound






No

Occurrences 1

Holes 0




Package Cache Lookups too high indicationOccurs when the number of Package Cache Lookups exceeds the Package CacheLookups upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property Package Cache Lookups (<PackageCacheLookups>)of the DB2 database <db2Database> and instance <db2Instance>is greater than <UpperBound>.




PackageCacheLookupsSpecifies the number of times that an application looked for a section inthe package cache.




This indication has the following threshold:v Package Cache Lookups upper bound






No

Occurrences 1

Holes 0




Percent Package Cache Hits too low indicationOccurs when the Percent Package Cache Hits counter is lower than the PercentPackage Cache Hits lower bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of Package Cache Hits <PctPackageCacheHits>of DB2 database <db2Database> and instance <db2Instance>is lower than <LowerBound>.




PctPackageCacheHitsSpecifies the percentage of the package cache hit ratio for the lastmonitoring interval. The package cache hit ratio specifies the ratio of thedifference between the package cache lookups and the package cacheinserts to all package cache lookups.




This indication has the following threshold:v Percent Package Cache Hits lower bound






Yes

Occurrences 3

Holes 2




ThresholdsThe following table lists the thresholds that can be set for the DB2 Package Cacheresource model. For each threshold it shows the name, a short description, and thedefault value:


Package Cache Insertsupper bound

The total number of times that a requestedsection was not available for use and had to beloaded into the package cache. This countincludes any implicit prepares performed by thesystem.

If the total number of package cache insertsexceeds the threshold value often enough, thePackage Cache Inserts too high indication triggersan event.

100

Package Cache Lookupsupper bound

The overall number of references to the packagecache since the database was started or themonitor data was reset. This occurs when thesection is already loaded in the cache and whenthe section has to be loaded into the cache.

If the overall number of package cache lookupsexceeds the threshold value often enough, thePackage Cache Lookups too high indicationtriggers an event.

200

Percent Package CacheHits lower bound

Specifies when the package cache is usedeffectively. A value of more than 80 percentindicates a high value and a well performingcache. A smaller ratio indicates that you need toincrease the package cache.

If the percentage of package cache hits is lowerthan the threshold value often enough, thePercent Package Cache Hits too low indicationtriggers an event.

80

ParametersThe following table lists the parameters that can be set for the DB2 Package Cacheresource model. The table shows the name, a short description, and the defaultvalue for each parameter.




The Database Package Cacheproperties available for logging.

v Package Cache Lookups

v Package Cache Inserts

v Percent Package Cache Hits





DB2Partition PackageCacheDB2Database.db2Database*




Package Cache InsertsSpecifies thenumber of timesthat a section isloaded into thepackage cachebecause anapplication findsthat the section itwants is not in thepackage cache.

Package Cache LookupsSpecifies thenumber of timesthat an applicationlooked for a sectionin the packagecache.

Percent Package Cache HitsSpecifies thepercentage of thepackage cache hitratio for the lastmonitoring interval.


Return codesNone


CLI exampleThe following example adds the DB2 Package Cache resource model toMyProfile#MyRegion. This example enables logging with a historical durationperiod of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2PackageCache -c 600 \-Log -LogEnable -p 12:00 -Agg no -NoMin -NoMax -Avg \-t High_PackageCacheInserts 120.000000 \


DB2 Replication Capture

DescriptionMonitors the status of the DB2 Capture component from IBM Replication.Replication is the process of maintaining a defined set of data in more than onelocation. It involves copying designated changes from one location (a source) toanother (a target), and synchronizing the data in both locations. IBM Replicationcopies relational data from source tables to target tables, which are typically indifferent DB2 databases.

IBM Replication uses the Capture program and Apply program components. TheCapture program reads the DB2 database log or journal records to capture dataabout changes made to source tables. The Apply program refreshes or updates atarget table, depending on the applicable source-to-target rules.

The Capture program reads the DB2 database log or journal records to capturedata about changes made to source tables. The Capture program is the most criticalreplication component in the replication system. If the Capture program is notactive, new change records are not created to apply to the target systems.

The DB2 Replication Capture resource model monitors the following information:v The number of errors encountered by the program within the last five minutes.v The time difference, in minutes, between the current timestamp and the last

timestamp recorded by the Capture program.

See the DB2 Replication Guide and Reference manual for detailed information aboutdata replication in DB2.


Internal name DB2ReplicationCapture

Category DB2

Indications Capture Errors too high occurs when the number of CaptureErrors in the last five minutes exceeds the Capture Errorsupper bound threshold.

Capture Lag too high occurs when the Capture Lag exceedsthe Capture Lag upper bound threshold.

Tasks and built-in actions No





Clearingevents

Page

Capture Errorstoo high

DB2_High_CaptureErrors Warning Yes 184



Clearingevents

Page

Capture Lag toohigh

DB2_High_CaptureLag Critical Yes 185

Capture Errors too high indicationOccurs when the number of Capture Errors in the last five minutes exceeds theCapture Errors upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property Capture Errors (<CaptureErrors>) of the instance(db2Database=<db2Database>; db2Instance=<db2Instance>)is greater than <UpperBound>.




CaptureErrorsSpecifies the number of errors encountered by the Capture program withinthe last five minutes.




This indication has the following threshold:v Capture Errors upper bound






Yes

Occurrences 1

Holes 0





Capture Lag too high indicationOccurs when the Capture Lag exceeds the Capture Lag upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property CaptureLag (<CaptureLag>) of the instance(db2Database=<db2Database>; db2Instance=<db2Instance>)is greater than <UpperBound>.




CaptureLagSpecifies the time difference, in minutes, between the current timestampand the last timestamp recorded by the Capture program.




This indication has the following threshold:v Capture Lag upper bound






Yes

Occurrences 3

Holes 2




ThresholdsThe following table lists the thresholds that can be set for the DB2 ReplicationCapture resource model. For each threshold it shows the name, a short description,and the default value:


Capture Errors upperbound

The number of capture errors that the Captureprogram, the most critical replication componentin the replication system, encounters within a fiveminute period. Errors prevent the Captureprogram from running. A non-active Captureprogram indicates that, there are not any newchange records to apply to the target systems.

If the number of capture errors exceeds thethreshold value often enough, the Capture Errortoo high indication triggers an event.

5

Capture Lag upperbound

The time difference, in minutes, between thecurrent timestamp and the last timestamprecorded by the Capture program.

If the capture lag time difference exceeds thethreshold value often enough, the Capture Lagtoo high indication triggers an event.

10

ParametersThe following table lists the parameters that can be set for the DB2 ReplicationCapture resource model. The table shows the name, a short description, and thedefault value for each parameter.



Database propertiesto log+

The Database Replication propertiesavailable for logging.

v Capture Lag

v Capture Errors





DB2Database ReplicationCapture Errors

Specifies the numberof errorsencountered by theCapture programwithin the last fiveminutes.

Capture LagSpecifies the timedifference, inminutes, between thecurrent timestampand the lasttimestamp recordedby the Captureprogram.

DB2Database.db2Database*Specifies the name ofthe DB2 database.



Return codesNone

CLI exampleThe following example adds the DB2 Replication Capture resource model toMyProfile#MyRegion. This example enables logging with a historical durationperiod of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2ReplicationCapture -c 600 \-Log -LogEnable -p 12:00 -Agg no -NoMin -NoMax -Avg \-e DB2_High_CaptureLag -o 3


DB2 SAP Tablespace Usage/Status

DescriptionMonitors DB2 SAP tablespace usage and status. The DB2 SAP Tablespace Usageresource model monitors the following information:v The percentage of space used in the Database Managed Space SAP tablespace.v When the status is something other than normal for the SAP tablespace.v Specifies the number of bytes allocated to the System Managed Space tablespace.


Internal name DB2SAPTablespaceUsageStatus

Category DB2

Indications Percent Space Used in SAP DMS Tablespace too highoccurs when the percentage space used in a DMS tablespaceexceeds the Percent Space Used in SAP DMS Tablespaceupper bound threshold.

SAP Table needs reorganizing indication occurs when theSAP Table Reorganize Status indicates that the table needsreorganizing.

SAP Tablespace Status is not normal occurs when the SAPTableSpaceStatus differs from the Tablespace Status notnormal threshold.

Space Used in SAP SMS Tablespace too high occurs whenthe space used, in bytes, exceeds the Space Used in SAPSMS Tablespace upper bound threshold.

Tasks and built-in actions No





Clearingevents

Page

Percent SpaceUsed in SAPDMSTablespacetoo high

DB2_High_SAP_SpaceUsedDMSTablespace Critical No 189

SAPTablespaceStatus is Notnormal

DB2_False_SAP_TablespaceNormalStatus Critical Yes 191



Clearingevents

Page

Space Usedin SAP SMSTablespacetoo high

DB2_High_SAP_SpaceUsedSMSTablespace Warning Yes 191

Percent Space Used in SAP DMS Tablespace too high indicationOccurs when the percentage space used in a Database Managed Space tablespaceexceeds the Percent Space Used in SAP DMS Tablespace upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Space Used DMS for tablespace <db2TbspName>,on DB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node> is<PctSpaceUsedDMS>, which is higher than <UpperBound>.








PctSpaceUsedDMSSpecifies the percentage of space used in the Database Managed Spacetablespace.


This indication has the following thresholds:v Percent Space Used in a DMS Tablespace upper bound






Yes

Occurrences 3



Holes 2



SAP Table needs reorganizing indicationOccurs when the SAP Table Reorganize Status indicates that the table needsreorganizing.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Table Reorganize Status of <ReorgStatus> for table <db2TableName> on the SAPinstance <db2Instance>, Database <db2Database>, Schema <db2Schema>indicates reorganize is needed.




ReorgStatusIndicates whether the table or its indexes need to be reorganized.

db2TableNameSpecifies the name of the DB2 table.



db2SchemaSpecifies a schema name to use as a qualifier for a table name.






Yes

Occurrences 3

Holes 2




SAP Tablespace Status is not normal indicationOccurs when the SAP TableSpaceStatus differs from the Tablespace Status notnormal threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The TablesSpace Status for tablespace <db2TbspName>on the SAP instance <db2Instance>, Database <db2Database>,Node <db2Node> is not equal to zero (Normal State).













Yes

Occurrences 3

Holes 1



Space Used in SAP SMS Tablespace too high indicationOccurs when the space used, in bytes, exceeds the Space Used in SAP SMSTablespace upper bound threshold.


When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Space Used SMS for tablespace <db2TbspName> onDB2 Database <db2Database>, Instance <db2Instance>, Node <db2Node> is<SpaceUsedSMS>, which is higher than <UpperBound>.








SpaceUsedSMSSpecifies the number of bytes allocated to the System Managed Spacetablespace.


This indication has the following threshold:v Space Used in a SMS Tablespace upper bound

For more information about this threshold, see “Thresholds”.





No

Occurrences 1

Holes 0



ThresholdsThe following table lists the thresholds that can be set for the DB2 SAP TablespaceUsage resource model. For each threshold it shows the name, a short description,


and the default value:


Percent Space Used in aDMS Tablespace upperbound

If the space used in a Database Managed Spacetablespace in the tablespace parameter listexceeds the threshold value often enough, thePercent Space Used in a DMS Tablespace too highindication triggers an event.

80

Space Used in a SMSTablespace upper bound

The number of bytes allocated to the SystemManaged Space tablespace in the SystemManaged Space tablespace parameter list. Log thereturned value to determine whether the numberof bytes used by a System Managed Spacetablespace is excessive in relation to the filesystem on which the tablespace resides.

If the space used in a System Managed Spacetablespace exceeds the threshold value oftenenough, the Space Used in a SMS Tablespace toohigh indication triggers an event.

0

ParametersThe following table lists the parameters that can be set for the DB2 SAP TablespaceUsage resource model. The table shows the name, a short description, and thedefault value for each parameter.



DMS Tablespaceproperties tolog+

The Database Managed Spacetablespace properties available forlogging.

v Percent DMS Spaced Used

SAP Tables tomonitor

A list of SAP table names to monitor. v VBLOG

v VBHDR

v ADRC

v ADRV

v ADRCT

v DOKCLU

v ADRG

v EUDB

v INDX

v NAST

v NRIV

v NRIV_LOKAL

v RSMPTEXTS

v SADR

v TFDIR



SAP Tablespacesto monitor

A list of SAP tablespace names tomonitor.

v *#DDICD

v *#POOLI

v *#USER1I

v *#CLUD

v *#SOURCED

v *#BTABI

v *#LOADI

v *#CLUI

v *#DOCUI

v *#STABD

v *#PROTI

v *#BTABD

v *#PROTD

v *#LOADD

v *#SOURCEI

v *#USER1D

v *#STABI

v *#DOCUD

v *#POOLD

v *#DDICI

v *#ES610D

v *#ES610I

v *#EL610D

v *#EL610I

SMS Tablespaceproperties tolog+

The System Managed Spacetablespace properties available forlogging.

v SMS Space Used

Table propertiesto log+

The SAP Table properties availablefor logging.

v Table Reorg Status

Tablespace Statusproperties tolog+

The tablespace status propertiesavailable for logging.

v Tablespace Status





DB2Tablespace TableSpace DMSDB2Database.db2Database*





Percent DMS Spaced UsedSpecifies thepercentage of spaceused in theDatabase ManagedSpace tablespace.

DB2Table SAP Table StatusDB2Database.db2Database*



db2Schema*Specifies a schemaname to use as aqualifier for a tablename.



DB2Table SAP Table Status (continued)db2TableName*

Specifies the nameof the DB2 table.

TableDataReorgNeededIndicates that theDB2 table needsdata reorganization.

TableDataReorgNotNeededIndicates that theDB2 table does notneed datareorganization.

TableIndexReorgNeededIndicates that theDB2 table needsindexreorganization.

TableIndexReorgNotNeededIndicates that theDB2 table does notneed datareorganization.

DB2TableSpace Tablespace SMSDB2Database.db2Database*





SMS Space UsedSpecifies thenumber of bytesallocated to theSystem ManagedSpace tablespace.



DB2TableSpace Tablespace StatusDB2Database.db2Database*





TbspBackupPendingIndicates a backuppending state forthe tablespace.

TbspBackupProgressIndicates that abackup is inprogress for thetablespace.

TbspDeletePendingIndicates a deletepending state forthe tablespace.

TbspDisablePendingIndicates a disablepending state forthe tablespace.

TbspDMSRebalanceIndicates that theDMS rebalancer isactive for thetablespace.

TbspDropPendingIndicates that a dropis pending for thetablespace.



DB2TableSpace Tablespace Status (continued)TbspLoadPending

Indicates a loadpending state forthe tablespace.

TbspNormalIndicates a normalstate for thetablespace.

TbspOfflineIndicates that thetablespace is offlineand not accessible.

TbspQuiescedShIndicates aQuiesced: SHAREstate for thetablespace.

TbspQuiescedUpIndicates aQuiesced: UPDATEstate for thetablespace.

TbspQuiescedExIndicates aQuiesced:EXCLUSIVE statefor the tablespace.

TbspReorgProgressIndicates that areorganization is inprogress for thetablespace.

TbspRestorePendingIndicates a restorepending state forthe tablespace.

TbspRestoreProgressIndicates that arestore is inprogress for thetablespace.

TbspRFpendingIndicates a rollforward is pendingfor the tablespace.



DB2TableSpace Tablespace Status (continued)TbspRFprogress

Indicates a rollforward is inprogress for thetablespace.

TbspStorDefIndicates that thestorage may bedefined for thetablespace.

TbspStorDefChangedIndicates that thestorage waschanged prior to theroll forward statefor the tablespace.

TbspStorDefFinalIndicates that thestorage is in thefinal stage for thetablespace.

TbspStorageUndefinedIndicates that youmust define thestorage for thetablespace.

TbspTBScreateIndicates that atablespace creationis in progress for thetablespace.

TbspTBSdeleteIndicates that atablespace deletionis in progress for thetablespace.


Return codesNone

CLI exampleThe following example adds the DB2 SAP Tablespace Usage/Status resourcemodel to MyProfile#MyRegion. This example enables logging with a historicalduration period of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2SAPTablespaceUsageStatus -c 1800 \-Log -LogEnable -p 12:00 -Agg no -NoMin -NoMax -Avg \-t High_SpaceUsedDMSTablespace 50.000000 \-DelPar SAP_Table_List "VBLOG" \


-AddPar SAP_Table_List "MYLOG" \-DelPar SAP_TbspNames_List "*#SOURCED" \-AddPar SAP_TbspNames_List "FURNITURE" \-AddPar SAP_TbspNames_List "TOOLS" \


DB2 Sorting

DescriptionMonitors the sorting activity of the database manager as well as at the databaseand application levels. Sorting is often required during a query. Therefore, properconfiguration of the sort heap areas can be crucial to improving the query’sperformance. By monitoring sort work, you can determine the current sort workperformance and use the information to refine the <sortheap> and <sheapthres>configuration parameters to achieve better performance.

Sorting involves the following two steps:v The sort phasev The return of the results of the sort phase

In the sort phase, if the information being sorted cannot fit entirely into the sortheap, the sort overflows and the information must be stored in temporary databasetables. Sorts that do not overflow perform better than those that do. The sort heapis a block of memory that is allocated each time a sort is performed.

In the return phase, if the sorted information can return directly through the sortheap, it is a piped sort. A piped sort performs better than a nonpiped sort. A pipedsort is sorted information that returns directly without requiring a temporary tableto store a final, sorted list of data. A nonpiped sort is sorted information thatrequires a temporary table to store a final, sorted list of data before it returns.

The DB2 Sorting resource model monitors the following information:v The percentage of piped sort requests that were rejected for the DB2 instance

during the monitoring interval.v The percentage of the allocated sort heap that the DB2 instance used during the

monitoring interval.v The total number of piped sorts that were rejected during the monitoring

interval.v The percentage of sorts that overflowed for the database during the monitoring

interval.v The total number of sorts performed by the application.v The sorting time, in seconds, for the application during the last monitoring

interval.v The piped sort hit ratio, as a percent, for the last monitoring interval.

See the DB2 Administration Guide: Performance for detailed information aboutsorting and the sort heap configuration parameters.


Internal name DB2Sorts

Category DB2



Indications Application Total Sorts too high occurs when anyapplication in the monitored database has executed moresorts than has been set by the Application Total Sorts upperbound threshold.

Percent Allocated Sort Heap too high occurs when whenthe percentage of the sort heap allocated exceeds the PercentAllocated Sort Heap upper bound threshold.

Percent Piped Sort Hits too low occurs when thePctPipedSortHits counter is lower than the PctPipedSortHitslower bound threshold.

Percent Piped Sort Requests Rejected too high occurs whenthe percentage of piped sort requests that are rejected for theDB2 Instance exceeds the Percent Piped Sort RequestsRejected upper bound threshold.

Percent Sorts Overflowed too high occurs when thepercentage of sorts that overflowed the sort heap on adatabase level exceeds the Percent Sort Overflowed upperbound threshold.

Piped Sort Requests Rejected too high occurs when thePipedSortReqRejected counter exceeds thePipedSortReqRejected upper bound threshold.

Associated tasks and built-inactions

No





Clearingevents

Page

ApplicationTotal Sorts toohigh

DB2_High_TotalSorts Critical Yes 203

PercentAllocated SortHeap too high

DB2_High_PctSortHeapUsed Critical No 204

Percent PipedSort Hits toolow

DB2_Low_PctPipedSortHits Critical Yes 205

Percent PipedSort RequestsRejected toohigh

DB2_High_PctPipedSortReqRejected Critical Yes 206

Percent SortsOverflowedtoo high

DB2_High_PctSortOverflowed Warning No 207



Clearingevents

Page

Piped SortRequestsRejected toohigh

DB2_High_PipedSortReqRejected Critical Yes 208

Application Total Sorts too high indicationOccurs when any application in the monitored database has executed more sortsthan has been set by the Application Total Sorts upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:A DB2 application <db2AppName> on DB2 database <db2Database>,instance <db2Instance has executed <TotalSorts> which exceededthe threshold of <UpperBound>.







TotalSortsSpecifies the total number of sorts that were executed during themonitoring interval.



This indication has the following threshold:v Application Total Sorts upper bound






No



Occurrences 1

Holes 0



Percent Allocated Sort Heap too high indicationOccurs when when the percentage of the sort heap allocated exceeds the PercentAllocated Sort Heap upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of the sort heap allocated was (<PctSortHeapUsed>)on DB2 instance (db2Instance=<db2Instance>) which exceeded the thresholdof <UpperBound>.




PctSortHeapUsedSpecifies the percentage of the allocated sort heap that the DB2 instanceused during the monitoring interval.



This indication has the following threshold:v Percent Allocated Sort Heap upper bound






No

Occurrences 3

Holes 2




Percent Piped Sort Hits too low indicationOccurs when the PctPipedSortHits counter is lower than the PctPipedSortHitslower bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of piped sort hits was (<PctPipedSortHits>) on DB2 instance(<db2Instance>) was lower than <LowerBound>.




PctPipedSortHitsSpecifies the piped sort hit ratio, as a percent, for the last monitoringinterval. The hit ratio is the ratio of piped sorts accepted to piped sortsrequested.



This indication has the following threshold:v Percent Piped Sort Hits lower bound






Yes

Occurrences 3

Holes 1




Percent Piped Sort Requests Rejected too high indicationOccurs when the percentage of piped sort requests that are rejected for the DB2Instance exceeds the Percent Piped Sort Requests Rejected upper bound threshold.If the value is high, decrease your sort heap by using the sortheap configurationparameter or increase your sort heap threshold by using the <sheapthres>configuration parameter.

Note: Be aware of the following implications for the previous options:v If you increase the sort heap threshold, more memory can remain

allocated for sorting which causes the paging of memory to disk.v If you decrease the sort heap, an extra merge phase may be required

which slows down the sort.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property PctPipedSortReqRejected (<PctPipedSortReqRejected>)of the instance (db2Instance=<db2Instance>) is greaterthan <UpperBound>.




PctPipedSortReqRejectedSpecifies the percentage of piped sort requests that were rejected for theDB2 instance during the monitoring interval.



This indication has the following threshold:v Percent Piped Sort Requests Rejected upper bound






Yes

Occurrences 3

Holes 1





Percent Sorts Overflowed too high indicationOccurs when the percentage of sorts that overflowed the sort heap on a databaselevel has exceeded the Percent Sort Overflowed upper bound threshold. You needto adjust the sortheap configuration parameter or tune the statement.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The percentage of sorts that overflowed on DB2 database <db2Database>,instance <db2Instance> was <PctSortOverflowed> which exceeded <UpperBound>.






PctSortOverflowedSpecifies the percentage of sorts that overflowed during the monitoringinterval.



This indication has the following threshold:v Percent Sort Overflowed upper bound






No

Occurrences 3

Holes 2




Piped Sort Requests Rejected too high indicationOccurs when the PipedSortReqRejected counter exceeds the PipedSortReqRejectedupper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The property PipedSortReqRejected (<PipedSortReqRejected> ofthe instance (db2Instance=<db2Instance>) is greater than <UpperBound>.




PipedSortReqRejectedSpecifies the percentage of piped sort requests that were rejected for theDB2 instance during the monitoring interval.



This indication has the following threshold:v Percent Allocated Sort Heap too high






Yes

Occurrences 3

Holes 0



ThresholdsThe following table lists the thresholds that can be set for the DB2 Sorting resourcemodel. For each threshold it shows the name, a short description, and the defaultvalue:



Application Total Sortsupper bound

Checks each application for the total number ofsorts that are executed. You can only use thisthreshold to generate the Total Sorts too highevent or for logging purposes.

If the number of sorts executed exceeds thethreshold value often enough, the Total Sorts toohigh indication triggers an event.

50

Percent Allocated SortHeap upper bound

The percentage of the allocated sort heap that theDB2 instance that is used during the monitoringinterval.

If the percent sort heap used exceeds thethreshold value often enough, the PercentAllocated Sort Heap too high indication triggersan event.

80

Percent Piped Sort Hitslower bound

The piped sort hit ratio, as a percent, for the lastmonitoring interval. The piped sort hit ratioindicates the ratio of piped sorts accepted topiped sorts requested.

If the percentage piped sorts hits is lower thanthe threshold value often enough, the PercentPiped Sort Hits too low indication triggers anevent.

80

Percent Piped SortRequests Rejected upperbound

The percentage of piped sort requests that arerejected for the DB2 Instance during themonitoring interval.

A high value indicates for you to decrease yoursort heap by using the <sortheap> configurationparameter or increase your sort heap thresholdby using the <sheapthres> configurationparameter.Note: Be aware of the following implications forthe previous options:

v If you increase the sort heap threshold, morememory can remain allocated for sorting whichcauses the paging of memory to disk.

v If you decrease the sort heap, an extra mergephase is required which slows down the sort.

If the percent piped sort requests rejects exceedsthe threshold value often enough, the PercentPiped Sort Requests Rejected too high indicationtriggers an event.

90

Percent Sort Overflowedupper bound

Indicates that a sort has run out of space in thesort heap and requires disk space for temporarystorage.

This threshold sets the maximum percentage ofsort overflows to total sorts at the database levelbefore the Percent Sorts Overflowed too highindication triggers an event.

90



Piped Sort RequestsRejected upper bound

The total number of piped sorts that are rejectedduring the monitoring interval.

If the piped sort requests rejected value exceedsthe threshold value often enough, the Piped SortRequests Rejected too high indication triggers anevent.

50

ParametersThe following table lists the parameters that can be set for the DB2 Sortingresource model. The table shows the name, a short description, and the defaultvalue for each parameter.




The Application Sort propertiesavailable for logging.

v Total Sorts


The Database Sort propertiesavailable for logging.

v Percent Sorts Overflowed

Instanceproperties tolog+

The Instance Sort propertiesavailable for logging.

v Percent Piped Sort Hits

v Percent Sort Heap Used

v Percent Piped Sort Requestsejected

v Piped Sort Requests Rejected





DB2Application ApplicationSortsDB2Application.db2ApplyID*






Total SortsSpecifies the totalnumber of sorts thatwere executedduring themonitoring interval.

DB2Partition DatabaseSortsDB2Database.db2Database*




Percent Sorts OverflowedSpecifies thepercentage of sortsthat overflowedduring themonitoring interval.



DB2Instance InstanceSortsDB2Instance.db2Instance*


Percent Piped Sort HitsSpecifies the pipedsort hit ratio, as apercent, for the lastmonitoring interval.

Percent Piped Sort RequestsRejected Specifies the

percentage of pipedsort requests thatwere rejected for theDB2 instance duringthe monitoringinterval.

Percent Sort Heap UsedSpecifies thepercentage of theallocated sort heapthat the DB2instance usedduring themonitoring interval.

Piped Sort Requests RejectedSpecifies thepercentage of pipedsort requests thatwere rejected for theDB2 instance duringthe monitoringinterval.


Return codesNone

CLI exampleThe following example adds the DB2 Sorting resource model toMyProfile#MyRegion. This example enables logging with a historical durationperiod of 12 hours. This example also sets the severity of theDB2_High_PctPipedSortReqRejected event to warning.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2Sorts -c 1800 \-Log -LogEnable -p 12:00 -Agg no -NoMin -NoMax -Avg \-t High_TotalSorts 58.000000 \-e DB2_High_PctPipedSortReqRejected -severity WARNING


DB2 SQL Cursor Activity

DescriptionMonitors the total number of local and remote open and blocking cursors that arecurrently open for the database. All active applications in the database aremonitored.

Applications use cursors to point to a specific row within an ordered set of rows.The cursor is used to retrieve rows from a set. Open cursors are the number ofcursors currently open for an application. You can relate the amount of memoryallocated by DB2 to the number of cursors currently open. This information canhelp with capacity planning. Cursors can be defined to allow for blocking.Blocking cursors improve your application’s performance by precompiling multiplerows of data and preventing cursor clocking.

Recognizing the SQL pattern in a database can help you make decisions aboutrefining the database and database manager configuration parameters. Forexample, You can refine certain parameters based on whether you are runningquery-only or update-intensive applications.

The DB2 SQL Cursor Activity resource model uses two indications to monitor thenumber of cursors open in an application. The Open Blocking Cursors too highand Open Cursors too high indications notify you when your open cursors haveexceeded the threshold that you specify for your application.


Internal name DB2Cursor

Category DB2

Indications Open Blocking Cursors too high occurs when the numberof Open Blocking Cursors for an application exceeds theOpen Blocking Cursors upper bound threshold.

Open Cursors too high occurs when the number of OpenCursors for an application exceeds the Open Cursors upperbound threshold






Clearingevents

Page

Open BlockingCursors toohigh

DB2_High_OpenBlockingCursors Warning No 214



Clearingevents

Page

Open Cursorstoo high

DB2_High_OpenCursors Warning No 215

Open Blocking Cursors too high indicationOccurs when the number of Open Blocking Cursors for an application exceeds theOpen Blocking Cursors upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The number of Open Blocking Cursors (<OpenBlockingCursors>)for application <db2AppName>, in database <db2Database>, andDB2 instance <db2Instance> is greater than <UpperBound>.




OpenBlockingCursorsSpecifies the total number of local and remote blocking cursors that arecurrently open for the application.






This indication has the following threshold:v Open Blocking Cursors upper bound






No

Occurrences 3

Holes 2




Open Cursors too high indicationOccurs when the number of Open Cursors for an application exceeds the OpenCursors upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The number of Open Cursors (<OpenCursors>) for application <db2AppName>),in database <db2Database>, and DB2 instance <db2Instance>is greater than <UpperBound>.




OpenCursorsSpecifies the total number of local and remote cursors that are currentlyopen for the application. This value also includes the number of local andremote blocking cursors currently open for the application.






This indication has the following threshold:v Open Cursors upper bound






No

Occurrences 3



Holes 2



ThresholdsThe following table lists the thresholds that can be set for the DB2 SQL CursorActivity resource model. For each threshold it shows the name, a short description,and the default value:


Open Blocking Cursorsupper bound

If the number of Open Blocking Cursors ownedby an application exceeds the threshold valueoften enough, the Open Blocking Cursors toohigh indication triggers an event.

6

Open Cursors upperbound

If the number of Open Cursors owned by anapplication exceeds the threshold value oftenenough, the Open Cursors too high indicationtriggers an event.

10

ParametersThe following table lists the parameters that can be set for the DB2 SQL CursorActivity resource model. The table shows the name, a short description, and thedefault value for each parameter.



Databaseproperties to log+

The Database SQL Cursor propertiesavailable for logging.

v Open Cursors

v Open Blocking Cursors





DB2Application SQLCursorsDB2Application.db2ApplyID*






Open Blocking CursorsSpecifies the totalnumber of local andremote blockingcursors that arecurrently open forthe application.

Open CursorsSpecifies the totalnumber of local andremote cursors thatare currently openfor the application.


Return codesNone

CLI exampleThe following example adds the DB2 SQL Cursor Activity resource model toMyProfile#MyRegion. This example sends the DB2_High_OpenBlockingCursors toTivoli Business Systems Manager and to Tivoli Enterprise Console.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2Cursor -c 600 \-Log -LogEnable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \-t High_OpenBlockingCursors 12.000000 \-e DB2_High_OpenBlockingCursors -SendTBSM -SendTec


DB2 SQL Statement Activity

DescriptionMonitors the DB2 SQL statement activity. SQL activity is a measure of databasethroughput and performance.

Recognizing the SQL pattern in a database can help you make decisions aboutrefining the database and database manager configuration parameters. Forexample, you can refine certain parameters based on whether you are runningquery-only or update-intensive applications.

The DB2 SQL Statement Activity resource model monitors the followinginformation:v The rate, counts per second, at which unit-of-work commits were attempted for

the database during the monitoring interval. Unit-of-work commits include SQLCOMMIT statements that are issued from applications and internal commits thatare initiated by the database manager.

v The rate, statements per second, at which SQL statements were executed duringthe monitoring interval.

v The number of SQL DDL statements that were executed in the database duringthe monitoring interval.

v The percentage of total SQL statements that were SQL DDL statements executedby the database or application during the monitoring interval.

v The number of dynamic SQL statements that were attempted for the databaseduring the monitoring interval.

v The number of failed SQL statements for the database during the monitoringinterval.

v The percentage of total SQL statements that failed during the monitoringinterval.

v The number of SQL SELECT statements that were executed by the database orapplication during the monitoring interval.

v The percentage of total SQL statements that were SQL SELECT statementsduring the monitoring interval.

v The number of SQL UPDATE, INSERT, and DELETE statements that wereexecuted by the database or application during the monitoring interval.

v The percentage of total SQL statements that were SQL UPDATE, INSERT, andDELETE statements executed by the database or application during themonitoring interval.

v The rate, counts per second, at which unit-of-work rollbacks were attemptedduring the monitoring interval.

v The total number of rollbacks attempted by the application. This value includesSQL ROLLBACK statements that are issued from the application and internalrollbacks that are initiated by the database manager for the application.

v The total number of rollbacks explicitly attempted by the application. This valueincludes only the number of SQL ROLLBACK statements issued from theapplication.

v The total number of SQL COMMIT statements that were attempted by theapplication. This value includes SQL COMMIT statements that are issued fromthe application and internal commits that are initiated by the database managerfor the application.

v The number of inserts of SQL sections by an application from its SQL work area.


v The number of lookups of SQL sections by an application from its SQL workarea.

v The number of static SQL statements that were attempted by the application.


Internal name DB2SQLStatementActivity

Category DB2

Indications Percent Failed Sql Statements too high occurs when thePercent Failed Sql Statements exceeds the Percent Failed SqlStatements upper bound threshold for a database.






Clearingevents

Page

Percent FailedSql Statementtoo high

DB2_High_PctFailedSqlStatements Critical Yes 219

Percent Failed Sql Statements too high indicationOccurs when the Percent Failed Sql Statements exceeds the Percent Failed SqlStatements upper bound threshold for a database.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Percent Failed Sql Statements on DB2 Database <db2Database>,Instance <db2Instance>, Node <db2Node> is <PctFailedSqlStatements>,which is higher than <UpperBound>.








PctFailedSqlStatementsSpecifies the percentage of total Structered Query Language statements thatfailed during the monitoring interval.


This indication has the following threshold:v Percent Failed Sql Statements upper bound






Yes

Occurrences 3

Holes 2



ThresholdsThe following table lists the thresholds that can be set for the DB2 SQL StatementActivity resource model. For each threshold it shows the name, a short description,and the default value:


Percent Failed SqlStatement upper bound

If the percent of failed Sql statements exceeds thethreshold value often enough, the Percent FailedSql Statement too high indication triggers anevent.

90

ParametersThe following table lists the parameters that can be set for the DB2 SQL StatementActivity resource model. The table shows the name, a short description, and thedefault value for each parameter.




ApplicationNames tomonitor

A list of applications to monitor.The following are options to enterfor applications to monitor:


v Wildcard designator, (*), tomonitor all applications


*


The application SQL activityproperties available for logging.

v Section Inserts

v Section Lookups

v Commits

v Percent DDL Sql Statements

v Percent UID Sql Statements

v Rollbacks

v Rollback Sql Statements

v Sql Selects Executed

v Sql Requests Since Last Commit

v Static Sql Statements

v UID Sql Executed


The database SQL activityproperties available for logging.

v Commit Rate

v DDL Sql Statements

v Dynamic Sql Statements

v Failed Sql Statements

v Percent Failed Sql Statements

v Percent Select Sql Statements

v Percent UID Sql Statements

v Rollback Rate

v Sql Select Executed

v Sql Statement Rate

v UID Sql Executed





DB2Application Application SQL ActivityCommits

Specifies the totalnumber of SQLCOMMITstatements that wereattempted by theapplication. Thisvalue includes SQLCOMMITstatements that areissued from theapplication andinternal commitsthat are initiated bythe databasemanager for theapplication.

DB2Application.db2ApplyID*Specifies thesubscriber user IDthat started thisinvocation of theApply program.





Percent DDL Sql StatementsSpecifies thepercentage of totalSQL statements thatwere SQL DDLstatements executedby the applicationduring themonitoring interval.



DB2Application Application SQL Activity(continued) Percent UID Sql Statements

Specifies thepercentage of totalSQL statements thatwere SQL UPDATE,INSERT, andDELETE statementsexecuted by theapplication duringthe monitoringinterval.

RollbacksSpecifies thenumber of rollbacksattempted by theapplication. Thisvalue includes SQLROLLBACKstatements that areissued from theapplication andinternal rollbacksthat are initiated bythe databasemanager for theapplication.

Rollback Sql StatementsSpecifies the totalnumber of rollbacksexplicitly attemptedby the application.This value includesonly the number ofSQL ROLLBACKstatements issuedfrom theapplication.

Section InsertsSpecifies thenumber of inserts ofSQL sections by anapplication from itsSQL work area.

Section LookupsSpecifies thenumber of lookupsof SQL sections byan application fromits SQL work area.



DB2Application Application SQL Activity(continued) Sql Requests Since Last

Commit Specifies thenumber of SQLrequests that weresubmitted by theapplication since thelast commit.

Sql Selects ExecutedSpecifies thenumber of SQLSELECT statementsthat were executedby the application.

Static Sql StatementsSpecifies thenumber of staticSQL statements thatwere attempted bythe application.

UID Sql ExecutedSpecifies thenumber of SQLUPDATE, INSERT,and DELETEstatements that wereexecuted by theapplication.

DB2Partition Database SQL ActivityCommit Rate

Specifies the rate atwhich unit-of-workcommits wereattempted for thedatabase during themonitoring interval.Unit-of-workcommits includeSQL COMMITstatements that areissued fromapplications andinternal commitsthat are initiated bythe databasemanager.



DB2Partition Database SQL Activity(continued) DB2Application.db2ApplyID*






DDL Sql StatementsSpecifies thenumber of SQLDDL statements thatwere executed in thedatabase during themonitoring interval.

Dynamic Sql StatementsSpecifies thenumber of dynamicSQL statements thatwere attempted forthe database duringthe monitoringinterval.

Failed Sql StatementsSpecifies thenumber of failedSQL statements forthe database duringthe monitoringinterval.



DB2Partition Database SQL Activity(continued) Percent Failed Sql Statements

Specifies thepercentage of totalStructered QueryLanguagestatements thatfailed during themonitoring interval.

Percent Select Sql StatementsSpecifies thepercentage of totalSQL statements thatwere SQL SELECTstatements duringthe monitoringinterval.

Percent UID Sql StatementsSpecifies thepercentage of totalSQL statements thatwere SQL UPDATE,INSERT, andDELETE statementsduring themonitoring interval.

Rollback RateSpecifies the rate atwhich unit-of-workrollbacks wereattempted duringthe monitoringinterval.Unit-of-workrollbacks includeSQL ROLLBACKstatements that areissued fromapplication andinternal rollbacksthat are initiated bythe databasemanager.



DB2Partition Database SQL Activity(continued) Sql Selects Executed

Specifies thenumber of SQLSELECT statementsthat were executedduring themonitoring interval.

Sql Statement RateSpecifies the rate atwhich SQLstatements wereexecuted during themonitoring interval.

UID Sql ExecutedSpecifies thenumber of SQLUPDATE, INSERT,and DELETEstatements that wereexecuted during themonitoring interval.


Return codesNone

CLI exampleThe following example adds the DB2 SQL Statement Activity resource model toMyProfile#MyRegion. This example enables aggregated logging.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2SQLStatementActivity -c 1800 \-Log -LogEnable -Agg yes -NoAvg \-DelPar AppNames_List "*" \-AddPar AppNames_List "*APPL*" \


DB2 Table Activity

DescriptionLogs table read and write activity. The DB2 Table Activity resource model allowsyou to track growth of a table over a period of time.

The DB2 Table Activity resource model monitors the following information:v The number of rows in a table.v The rate, per second, at which rows were read from the table during the

monitoring interval.v The rate, per second, at which rows were changed (inserted, deleted, or

updated) in the table during the monitoring interval.

A high return value of rows read indicates that there is heavy use of the table.Consider creating additional indexes for the table. To avoid the maintenance ofunnecessary indexes, use the SQL EXPLAIN statement, described in the DB2Administration Guide for the version of DB2 that you are using. The SQL EXPLAINstatement helps you determine if your packages use an index for the table.

A high return value of rows changed indicates that there is heavy use of the table.Consider using the RUNSTATS statement to maintain the efficiency of the packagesused for this table.


Internal name DB2TableActivity

Category DB2

Indications None




Indications and eventsNone

ThresholdsNone

ParametersThe following table lists the parameters that can be set for the DB2 Table Activityresource model. The table shows the name, a short description, and the defaultvalue for each parameter.




Schemas (owners)of Tables tomonitor

A list of schemas for which the tablesare monitored. The following areoptions to enter for each schema tomonitor:

v Schema name for each schema tomonitor

v Wildcard designator, (*), to monitorall schemas

v Combine partial schema names anduse the wildcard designator, (*), toseparate

*

Table Names tomonitor

A list of tables to monitor. Thefollowing are options to enter for eachtable to monitor:

v Table name for each table tomonitor

v Wildcard designator, (*), to monitorall tables

v Combine partial table names anduse the wildcard designator, (*), toseparate

*

Table properties tolog+

The table properties available forlogging.

v Rows Read Rate

v Rows Written Rate




DB2Table Table ActivityRows Read Rate

Specifies the rate atwhich rows wereread from the tableduring themonitoring interval.

Rows Written RateSpecifies the rate atwhich rows werechanged in the tableduring themonitoring interval.Rows are consideredchanged when youinsert, delete, orupdate them.



DB2Table Table Activity (continued)DB2Database.db2Database*



db2Schema*Specifies a schemaname to use as aqualifier for a tablename.

db2TableName*Specifies the nameof the DB2 table.


Return codesNone

CLI exampleThe following example adds the DB2 Table Activity resource model toMyProfile#MyRegion. This example enables aggregated logging with a historicalduration period of 12 hours.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2TableActivity \-Log -LogEnable -p 12:00 -Agg yes \-AddPar TableNames_List "ACCT*" \-DelPar TableNames_List "*" \


DB2 Table Apply Replication

DescriptionMonitors the status of the tables in the DB2 Apply component from IBMReplication. IBM Replication copies relational data from source tables to targettables, which are typically in different DB2 databases.

The DB2 Table Apply Replication resource model monitors the followinginformation:v Whether a target table requires a full refresh.v Whether the system is lagging or is due to run again.v When the Apply subscription for a target table is in error state.


Internal name DB2TableApplyReplication

Category DB2

Indications Apply Full Refresh is required occurs when Apply RequiresRefresh is greater than zero.

Apply Subscription Lag Time too high occurs when ApplySubscription Lag Time exceeds the Apply Subscription LagTime upper bound threshold.

Apply Subscription Status is in error state occurs when theApply Subscription Status is equal to three.



Target managed resourceDB2DatabaseManager



Clearingevents

Page

Apply FullRefresh isrequired

DB2_High_ApplyRequiresRefresh Warning Yes 231

ApplySubscriptionLag Time toohigh

DB2_High_ApplySubscriptionsLagTime Warning Yes 232

ApplySubscriptionStatus is inerror state

DB2_ApplySubscriptionsStatus_Error Critical 233

Apply Full Refresh is required indicationOccurs when Apply Requires Refresh is greater than zero.


When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Apply Requires Refresh on DB2 Database <db2Database>, Instance <db2Instance>,ApplyID <db2ApplyID> is <ApplyRequiresRefresh>, which indicatesan Apply Full Refresh is required.







ApplyRequiresRefreshSpecifies whether a target table requires a full refresh.






Yes

Occurrences 1

Holes 0



Apply Subscription Lag Time too high indicationOccurs when Apply Subscription Lag Time exceeds the Apply Subscription LagTime upper bound threshold.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Apply Subscription Lag Time on DB2 Database <db2Database>,Instance <db2Instance>, Apply ID <db2ApplyID> is<ApplySubscriptionLagTime>, which is higher than <UpperBound>.








ApplySubscriptionLagTimeSpecifies whether the system is lagging or is due to run again.


This indication has the following threshold:v Apply Subscription Lag Time upper bound






Yes

Occurrences 1

Holes 0



Apply Subscription Status is in error state indicationOccurs when the Apply Subscription Status is equal to three.

When the indication occurs often enough to trigger an event, the event delivers amessage to the Tivoli Enterprise Console in the following format:The Apply Subscription Status on DB2 Database <db2Database>,Instance <db2Instance>, Apply ID <db2ApplyID> is <ApplySubscriptionStatus>,which indicates an Apply Subscription error occurred.








ApplySubscriptionStatusSpecifies when the Apply subscription for a target table is in error state.






Yes

Occurrences 2

Holes 0



ThresholdsThe following table lists the thresholds that can be set for the DB2 Table ApplyReplication resource model. For each threshold it shows the name, a shortdescription, and the default value:


Apply Subscription LagTime upper bound

If the apply subscription lag time exceeds thethreshold value often enough, the ApplySubscription Lag Time too high indicationtriggers an event.

5

ParametersThe following table lists the parameters that can be set for the DB2 Table ApplyReplication resource model. The table shows the name, a short description, and thedefault value for each parameter.




Apply IDs tomonitor

A list of Apply IDs to monitor. Thefollowing are options to enter foreach Apply ID to monitor:

v Apply ID name for each schemato monitor

v Wildcard designator, (*), tomonitor all Apply IDs

v Combine partial Apply ID namesand use the wildcard designator,(*), to separate

*

Schemas(owners) ofTables to monitor

A list of schemas for the tables thatare monitored. The following areoptions to enter for schemas tomonitor:

v Schema name for each schema tomonitor

v Wildcard designator, (*), tomonitor all schemas

v Combine partial schema namesand use the wildcard designator,(*), to separate

*

Table Applyproperties tolog+

The table Apply properties availablefor logging.

v Apply Requires Refresh

v Apply Subscription Lag Time

v Apply Subscription Status

Table Names tomonitor forApply

A list of tables to monitor. Thefollowing are options to enter fortables to monitor:

v Table name for each table tomonitor

v Wildcard designator, (*), tomonitor all tables

v Combine partial table names anduse the wildcard designator, (*),to separate

*





DB2TableApply Table Apply ReplicationApply Requires Refresh

Specifies whether atarget table requiresa full refresh.

Apply Subscription Lag TimeSpecifies whetherthe system islagging or is due torun again.

Apply Subscription StatusSpecifies when theApply subscriptionfor a target table isin error state.

db2ApplyID*Specifies thesubscriber user IDthat started thisinvocation of theApply program.




Return codesNone

CLI exampleThe following example adds the DB2 Table Apply Replication resource model toMyProfile#MyRegion.

Using the wdmeditprf command:wdmeditprf -P MyProfile#MyRegion -add DB2TableApplyReplication -c 1800 \-AddPar SchemaNames_List "ACCOUNTING" \-DelPar SchemaNames_List "*" \


Chapter 3. About task libraries

The DB2 tasks are operations or sets of operations that perform server anddatabase operations routinely. This chapter contains information about the DB2tasks for IBM Tivoli Monitoring for Databases: DB2. Table 3 on page 239, Table 4 onpage 273, and Table 5 on page 363 summarize these tasks.

The section for each task describes how to configure and run each task by coveringthe following information:

DescriptionPurpose of the task.

Authorization roleRole required to run the task.

Task libraryThe IBM Tivoli Monitoring for Databases: DB2 tasks are grouped into thefollowing three libraries based on function:v Monitor and Administration Tasks: Contains tasks used for monitoring

and administration.v DB2 Database Tasks: Contains tasks used with DB2 and the database

manager.v Data Replication Tasks: Contains tasks used for data replication with

IBM Replication.

Desktop optionsList of the options for the task that are available in the Tivoli desktopgraphical user interface. These options correspond to the parameters in thecommand syntax.

CLI syntaxSyntax for the wruntask command that you use to run every task from thecommand line. All tasks that you run from the command line contain thefollowing syntax:wruntask -t <"Task Name"> -l <"Task Library Name"> -h <"Object Name"> \-a<"Additional Parameters">

where:

-t <Task Name>Name of the task to run.

-l <Task Library Name>Name of the task library that contains the task.

-h <Object Name>Name of the object about which the task gathers data.

-a <Additional Parameters>Additional parameters for the task, such as Date or DatabaseName. A task can have additional parameters that are required,optional, or both required and optional. The parameters must betyped in the order in which they appear in the syntax. If you donot want to specify a parameter, use empty quotation marks likethe following:

237

-a ""

Use quotation marks around the name of a variable that contains spaces.

CLI exampleThe example for the task contains a brief description of the example andan example of the syntax, such as the following:

The task in the following example stops a DB2 Administration Servernamed db2instl@bburns and does not contain any additional parameters:wruntask -t ECC_Stop_Admin_Server -l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2instl@bburns

Usage notesAdditional notes relevant to using the task.

Return valuesInformation that the command returns.

Tivoli tasks offer the following benefits:v You can set up tasks to run on a schedule within a Tivoli job.v You can set up tasks to run in response to the indications for a resource model.v You can set up tasks to run against multiple DB2 Servers.v You can set arguments for a task in the Tivoli desktop graphical user interface,

and save them to run at another time.v Tasks appear as icons that you can click and run in the Tivoli desktop graphical

user interface.

See the Working with Tasks and Jobs chapter of the IBM Tivoli Monitoring forDatabases: DB2 User’s Guide for more information on creating task libraries, tasks,and jobs.


Chapter 4. Monitor and administration tasks

The DB2ManagerAdminTasks library contains tasks that are used for themonitoring and administration of DB2.

Table 3 briefly describes each task in the DB2ManagerAdminTasks task library.When you view this table online, you can click the task name to go to a fulldescription of that task.

Table 3. DB2ManagerAdmin tasks

Task Description

ECC_Broadcast_Message Broadcasts a message to all Tivoli desktops

ECC_Configure_Audit Enables changes to take effect in the DB2 Auditing Facility

ECC_Configure_TEC_Classes Provides Tivoli Enterprise Console configuration options

ECC_Create_Import_Audit_Log Extracts audit records

ECC_Extract_Audit_Log Places the contents of the DB2 Audit Facility log into aspecified file

ECC_Flush_Audit_Buffer Writes pending DB2 Audit records to the Audit log

ECC_Get_Audit_Configuration Returns the active configuration to audit events

ECC_Prune_Audit_Log Deletes records in the Audit Facility log file

ECC_Purge_Audit_Log Deletes Audit records in the Audit Facility log

ECC_Reset_Audit_Configuration Reverts the DB2 Audit Configuration file to the initialconfiguration

ECC_Reset_Counters Resets the ECC counters for a DB2 instance

ECC_Send_Notice Sends a notice to all Tivoli administrators

ECC_Set_Up_Monitoring_Agent Sets up the monitoring agent

ECC_Start_Auditing Starts auditing events

ECC_Start_Monitoring_Agent Starts the monitoring agent to run DB2 monitors

ECC_Stop_Auditing Stops auditing events

ECC_Stop_Monitoring_Agent Stops the ECC monitoring agent

ECC_TBSM_Discovery Notifies Tivoli Business Systems Manager of added or removedactive instances

239

ECC_Broadcast_Message

DescriptionThis task reads the input data and broadcasts the message text to all desktops inthe IBM Tivoli Monitoring for Databases: DB2 software installation.

Authorization roledb2_dba

Target endpointDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager

GUI data entry fieldsThe following figure shows the desktop fields for this task.

Message to sendSpecifies the message that you want to broadcast.

CLI syntaxv Using the wruntask command:

-t ECC_Broadcast_Message-l DB2ManagerAdminTasks-h <hostname>"<message>"

where:

hostnameThe target endpoint name preceded by @<target endpoint> and a colon(:).

"message"Specifies the message that you want to broadcast. You must enclose themessage in quotation marks.


CLI examplev Using the wruntask command:

wruntask-t ECC_Broadcast_Message-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a "Backing up databases now."

Usage notesSelect only one endpoint in your management region. When you select multipleendpoints, the message generates multiple times. For example, all endpoints in themanagement region receive the message three times when you select threeendpoints.

For more information, see the wbroadcast command in the Tivoli ManagementFramework Reference Manual.

See alsoNone

Chapter 4. Monitor and administration tasks 241

ECC_Configure_Audit

DescriptionEnables changes made to the specified parameters to take effect in the DB2 AuditFacility.


Target endpointDB2InstanceManager, DB2DatabaseManager, DB2PartitionManager,DB2PartitionGroupManager


Scope Specifies the category or categories of events audited in order to reduce thegrowth of the audit log. Limit the number and type of events that arelogged to prevent rapid growth of the audit log. The following are thescope category types:

audit Generates records when you change audit settings or when youaccess the audit log.

checkingGenerates records during authorization checking of attempts toaccess or manipulate DB2 objects or functions.

contextGenerates records to show the operation context when youperform a database operation. This category allows for betterinterpretation of the audit log file. When you use this categorywith the log’s event correlator field, you can associate a group ofevents with a single database operation.

objmaintGenerates records when you create or drop data objects.

secmaintGenerates records when you grant or revoke either object ordatabase privileges or DBADM authority. This category also generates


records when you modify the SYSADM_GROUP, SYSCTRL_GROUP, orSYSMAINT_GROUP database manager security configuration.

sysadminGenerates records when you perform operations requiring theSYSADM, SYSMAINT, or SYSCTRL authority.

validateGenerates records when you authenticate users or retrieve systemsecurity information.

Status Specifies if only successful or failing events, or both successful and failingevents are logged. The following are possible values for this parameter:

successLogs only successful events.

failureLogs only failing events.

both Logs both successful and failing events.

Additional information: Context events occur before the status of anoperation is known. These events are logged if they are successful orfailing.

ErrorTypeSpecifies whether audit errors are returned to the user or if they areignored. The following are possible values for this parameter:

audit All errors are managed by DB2 and all negative SQLCODEs arereported back to the caller. This includes errors that occur withinthe DB2 Audit Facility.

normalThe SLQCODEs are returned to the applications for the errorsassociated with the operation that you are performing. Any errorsthat are generated by the DB2 Audit Facility are ignored.

CLI syntaxUsing the wruntask command:

–t ECC_Configure_Audit–l DB2ManagerAdminTasks–h <hostname>–a <scope>–a <status>–a <errortype>

where:

hostnameThe DB2 target endpoint name preceded by @<target endpoint> and a colon(:).

scope Specifies the category or categories of audited events.

status Specifies if only successful or failing events, or both successful and failingevents are logged.


errortypeSpecifies whether audit errors are returned to the user or if they areignored.

CLI exampleUsing the wruntask command:wruntask-t ECC_Configure_Audit-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a checking-a failure-a audit

Usage notesNone

See alsoNone


ECC_Configure_TEC_Classes

DescriptionProvides Tivoli Enterprise Console configuration options. You can configure theTivoli Enterprise Console to receive events from the following:v Distributed monitorsv Tasks

The ECC_Configure_TEC_Classes task adds the class and rule set definitions ofthe selected configuration option to a valid rule base when the class and rule setdefinitions are not already defined in the specified rule base. For more information,see the IBM Tivoli Monitoring for Databases: DB2 User’s Guide. You must installTivoli Enterprise Console Event Server before you run this task.

The ECC_Configure_TEC_Classes task performs the following functions,depending on the options you choose:v Creates a rule base in the directory where you install Tivoli Enterprise Console.v Provides Tivoli Enterprise Console configuration for the specified options. It

adds class and rule set definitions to a valid rule base for the options if they arenot already defined in the specified rule base.

v Copies a specified rule base into the newly created rule base.v Creates event groups. (This option is not available for Tivoli Enterprise Console,

Version 3.7.)v Loads the rule base.v Restarts the event server.

Authorization rolesenior and super (must have both roles)

Target endpointTivoli event servers (managed nodes)



Rule Base NameSpecifies the name for the rule base.

Copy Base NameSpecifies the name of the rule base to copy.

Event Group NameSpecifies the name of the event group that you are creating.

Note: This option is not available for Tivoli Enterprise Console, Version3.7. For information on creating event groups for that version, referto the Tivoli Enterprise Console, Version 3.7, User’s Guide.

Restart Event ServerSpecifies that the Y option restarts the Event Server, and the N option doesnot restart the event Server.


- t ECC_Configure_TEC_Classes- l DB2ManagerAdminTasks-h <hostname>-a <rulebasename>[-a <copybasename>][-a <eventgroupname>][-a {Y | N}]

where:

hostnameThe DB2 database manager name preceded by @DB2DatabaseManagerand a colon (:).

rulebasenameSpecifies the name for the rule base.

copybasenameSpecifies the name of the rule base to copy. This is usually "default"when given the default Tivoli rule base.

eventgroupnameSpecifies the name of the event group that you are creating.

Note: This option is not available for Tivoli Enterprise Console, Version3.7. For information on creating event groups for that version,refer to the Tivoli Enterprise Console, Version 3.7, User’s Guide.

restart_event_serverY restarts the server. N does not restart the server.


wruntask-t ECC_Configure_TEC_Classes-l DB2ManagerAdminTasks-h @DB2DatabaseManager:db2mgr1@bburns


-a DB2Base1-a Default-a TEC-a N

Usage notesSet the timeout value to at least 600 seconds to avoid premature task failure.

See alsoNone


ECC_Create_Import_Audit_Log

DescriptionExtracts audit records by formatting and copying them from the audit log to a flatfile or ASCII delimited file. The records are extracted either to prepare for analysisor pruning of the log records.




ASCII delimiterSpecifies the hexadecimal value (0x00 through 0xff) used to separate thefields returned from the Audit Facility log. The default ASCII delimiter is0xff.

CategorySpecifies the type of audit event collected. The following are the auditevent category types:

audit Generates records when you change audit settings or when youaccess the audit log.

checkingGenerates records during authorization checking of attempts toaccess or manipulate DB2 objects or functions.

contextGenerates records to show the operation context when youperform a database operation. This category allows for betterinterpretation of the audit log file. When you use this categorywith the log’s event correlator field, you can associate a group ofevents back to a single database operation.



secmaintGenerates records when you grant or revoke either object ordatabase privileges or DBADM authority. This category also generatesrecords when you modify the SYSADM_GROUP, SYSCTRL_GROUP, orSYSMAINT_GROUP database manager security configuration.


validateGenerates records when you authenticate users or retrieve systemsecurity information.

Additional information: The default category type is audit.

Status Specifies if only successful or failing events are logged. The following arepossible values for this parameter:

SuccessLogs only successful events.

FailureLogs only failing events.



–t ECC_Create_Import_Audit_Log–l DB2ManagerAdminTasks–h <hostname>–a <ascii delimiter>–a <category>–a <status>

where:


ascii delimiterSpecifies the hexadecimal value (0x00 through 0xff) used to separate thefields returned from the Audit Facility log.

categorySpecifies the type of audit event collected.


CLI exampleUsing the wruntask command:


wruntask-t ECC_Create_Import_Audit_Log-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a xff-a validate-a success

Usage notesNone

See alsoNone


ECC_Extract_Audit_Log

DescriptionRetrieves the contents of the current DB2 Audit Facility log and places them intothe specified path name file. Uses the Scope and Category parameters to filter theretrieved information.




PathnameSpecifies the destination file name. This file name must include the pathlocation of the retrieved Audit Facility log. The db2audit.out file is thedefault file name.

CategorySpecifies the type of audit event collected. The default category type isaudit. The following are category types:

Audit Generates records when you change audit settings or when youaccess the audit log.

CheckingGenerates records during authorization checking of attempts toaccess or manipulate DB2 objects or functions.

ContextGenerates records to show the operation context when youperform a database operation. This category allows for betterinterpretation of the audit log file. When you use this categorywith the log’s event correlator field, you can associate a group ofevents back to a single database operation.



secmaintGenerates records when you grant or revoke either object ordatabase privileges or DBADM authority. This category also generatesrecords when you modify the SYSADM_GROUP, SYSCTRL_GROUP, orSYSMAINT_GROUP database manager security configuration.


ValidateGenerates records when you authenticate users or retrieve systemsecurity information.

Status Specifies if only successful or failing events are logged. The following arepossible values for this parameter:

SuccessLogs only successful events.

FailureLogs only failing events.


Copy to screenSpecifies if the audit information this task collects displays on the screen.

Yes The screen displays the audit information.

No The screen does not display the audit information.


–t ECC_Extract_Audit_Log–l DB2ManagerAdminTaks–h <hostname>–a <pathname>–a <category>–a <status>

where:


pathnameSpecifies the destination file name. The file name must include the pathlocation of the retrieved Audit Facility log. The db2audit.out file is thedefault file name.

categorySpecifies the type of audit event collected.



CLI exampleUsing the wruntask command:wruntask-t ECC_Configure_Audit-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a /data/db2audit.out-a validate-a success

Usage notesNone

See alsoNone


ECC_Flush_Audit_Buffer

DescriptionWrites any pending DB2 Audit records from the DB2 Instance to the Audit log.



GUI data entry fieldsNone


–t ECC_Flush_Audit_Buffer–l DB2ManagerAdminTasks–h <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Flush_Audit_Buffer-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesNone

See alsoNone


ECC_Get_Audit_Configuration

DescriptionReturns the active configuration that the active DB2 Audit Facility uses to auditevents.





–t ECC_Get_Audit_Configuration–l DB2ManagerAdminTasks–h <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Get_Audit_Configuration-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesNone

See alsoNone


ECC_Prune_Audit_Log

DescriptionDeletes records that appear in the Audit Facility log file on or before the date andtime specified.




Prune audit records up toSpecifies the target date and time of creation. All audit records created onor before this date and time will be deleted. The date and time is specifiedas YYYYMMDDHH.

PathnameSpecifies the path name of a temporary file the the Audit Facility uses toprune the Audit Facility log when the disk that contains the Audit Facilitylog is full.


–t ECC_Prune_Audit_Log–l DB2ManagerAdminTasks–h <hostname>–a <date/time>–a <pathname>

where:



date/timeSpecifies the date and time on or before audit records are deleted.

pathnameSpecifies the path name of a temporary file the the Audit Facility uses toprune the Audit Facility log when the disk that contains the Audit Facilitylog is full.

CLI exampleUsing the wruntask command:wruntask-t ECC_Prune_Audit_Log-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a 2002081202-a "/data/overflow_file"

Usage notesYou can optionally supply a path name for the Audit Facility to use as a temporaryspace when pruning the audit log and the disk is full and does not allow forpruning operations to take place.

See alsoNone


ECC_Purge_Audit_Log

DescriptionDeletes all of the Audit records in the Audit Facility log.





–t ECC_Purge_Audit_Log–l DB2ManagerAdminTasks–h <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Purge_Audit_Log-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesNone

See alsoNone


ECC_Reset_Audit_Configuration

DescriptionReverts the DB2 Audit Configuration file, db2audit.cfg, to the initial configuration.

Creates a new DB2 Audit Configuration file if the original file is lost or damaged.





–t ECC_Reset_Audit_Configuration–l DB2ManagerAdminTasks–h <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Reset_Audit_Configuration-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesThis command reverts the DB2 Audit Configuration file, db2audit.cfg, to the initialconfiguration. The following specifies the initial configuration of that file:

<Scope>all

<Status>failure

<Errortype>normal

<Audit>off


See alsoNone


ECC_Reset_Counters

DescriptionResets the ECC counters for a DB2 instance.


Target endpointDB2DatabaseManager, DB2InstanceManager and DB2PartitionManager



–t ECC_Reset_Counters–l DB2ManagerAdminTasks–h <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Reset_Counters-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesUse this task to force counters to reset that are normally only reset when you startan application or the database manager.

See alsoNone


ECC_Send_Files_To_TEC_TMR

DescriptionCopies files to a remote Tivoli management region that contains Tivoli EnterpriseConsole to allow the user to run the ECC_Configure_TEC_Classes task. Use thistask only if you have Tivoli Enterprise Console installed on a Tivoli managementregion separate from the Tivoli management region where you have IBM TivoliMonitoring and IBM Tivoli Monitoring for Databases: DB2 installed.


Target endpointManagedNode (with Event Server installed).


Remote TMR Server NameSpecifies the name of the Tivoli management region server that containsthe Tivoli Enterprise Console installation that you want to configure.


–t ECC_Send_Files_To_TEC_TMR–l DB2ManagerAdminTasks–h <hostname>–a <TEC Server>

where:

hostnameThe target ManagedNode name preceded by @ManagedNode and a colon(:).

TEC ServerThe target Tivoli Enterprise Console server.



wruntask-t ECC_Send_Files_To_TEC_TMR-l DB2ManagerAdminTasks-h @ManagedNode:nerfherder-a nerfherder

Usage notesYou do not need to run this task if your Tivoli Enterprise Console server is in thesame Tivoli management region as IBM Tivoli Monitoring and IBM TivoliMonitoring for Databases: DB2.

See alsoNone


ECC_Send_Notice

DescriptionSends a notice to the notification server.

Authorization rolesuper and senior



Notice GroupSpecifies the notice group to receive the notice.

PrioritySpecifies the priority level for the notification: The options are Critical,Error, Warning, Notice, or Debug.

Notice Specifies the notice text you want to send.


–t ECC_Send_Notice–l DB2ManagerAdminTasks–h <hostname>-a "<ngroup>"[-a {Critical|Error|Warning|Notice|Debug}] -a <notice>where:

hostnameThe DB2 target endpoint name preceded by <@target endpoint> and acolon (:).


"ngroup"Specifies the notice group. Requires quotation marks around the name.

prioritySpecifies one of the following priorities for the notification: Critical,Error, Warning, Notice, or Debug.

notice Specifies the notice text you want to send.


wruntask-t ECC_Send_Notice-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a "TME Administration"-a Critical-a "Shutting down for maintenance."

Usage notesThis task translates the input data into a message structure and sends it to thenotification server. You can specify that you want the message sent to any noticegroup. For more information, refer to the wsndnotif command in the TivoliManagement Framework Reference Manual.

See alsoNone


ECC_Set_Up_Monitoring_Agent

DescriptionSets up the monitoring agent.

Authorization rolesenior and super



ActionSelect one of the following actions from the drop-down list:

Add and startAdds and starts a monitoring agent. Adds an inittab entry forUNIX or installs the monitoring service for Windows.

Add without startingAdds a monitoring agent. Adds an inittab entry for UNIX orinstalls the monitoring service for Windows.

Remove and stopRemoves and stops a monitoring agent. Removes the inittab entryfor UNIX.

Remove without stoppingRemoves a monitoring agent. Removes the inittab entry for UNIXor the monitoring service for Windows.

Password(For Windows only) Specifies the password used when adding themonitoring service.



-t ECC_Set_Up_Monitoring_Agent-l DB2ManagerAdminTasks-h <hostname>-a <action>-a <password>where:


action Specifies one of the following actions:

AddStartAdds and starts a monitoring agent. Adds an inittab entry forUNIX or installs the monitoring service for Windows.

AddNoStartAdd an inittab entry for UNIX or install the monitoring servicefor Windows.

RemoveStopRemoves and stops a monitoring agent. Removes the inittabentry for UNIX.

RemoveNoStopRemoves a monitoring agent. Removes the inittab entry forUNIX or the monitoring service for Windows.

password(For Windows only) Specifies the password used when adding themonitoring service.


wruntask-t ECC_Set_Up_Monitoring_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a AddStart-a paswrd

Usage notesNone

See alsoNone


ECC_Start_Auditing

DescriptionEnables the DB2 Audit Facility to begin auditing events based on the contents ofthe db2audit.cfg file.





–t ECC_Start_Auditing–l DB2ManagerAdminTasks–h <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Start_Auditing-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesFor a partitioned DB2 Instance, auditing begins on all partitions when you run thistask. When you specify the Audit category of events for the Audit Facility, anaudit record logs when the Audit Facility starts.

See alsoNone


ECC_Start_Monitoring_Agent

DescriptionStarts the monitoring agent to run DB2 monitors.

Authorization roledb2_user




–t ECC_Start_Monitoring_Agent–l DB2ManagerAdminTasks–h <hostname>

where:



wruntask-t ECC_Start_Monitoring_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Default thresholds and actionsNone

Usage notesNone

See alsoNone


ECC_Stop_Auditing

DescriptionEnables the DB2 Audit Facility to stop auditing events.





–t ECC_Stop_Auditing–l DB2ManagerAdminTasks–a <hostname>

where:


CLI exampleUsing the wruntask command:wruntask-t ECC_Stop_Auditing-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesFor a partitioned DB2 Instance, auditing stops on all partitions when you executethis task. When you specify the Audit category of events for the Audit Facility, anaudit record logs when the Audit Facility stops.

See alsoNone


ECC_Stop_Monitoring_Agent

DescriptionStops the monitoring agent.





-t ECC_Stop_Monitoring_Agent- l DB2ManagerAdminTasks-h <hostname>

where:



wruntask-t ECC_Stop_Monitoring_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesNone

See alsoNone


ECC_TBSM_Discovery

DescriptionChecks for recently added or removed active instances and notifies Tivoli BusinessSystems Manager of the changes. Tivoli Business Systems Manager then makes theappropriate changes to its display.


Target endpointManagedNode (with Event Server installed).



–t ECC_TBSM_Discovery–l DB2ManagerAdminTasks–h <hostname>

where:

hostnameThe target DB2 Instance name preceded by @DB2InstanceManager and acolon (:).

CLI exampleUsing the wruntask command:wruntask-t ECC_TBSM_Discovery-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesThis task uses the Tivoli Business Systems Manager generic interface installed on aTivoli Enterprise Console server to send events to Tivoli Business SystemsManager. You must run the task on a managed node that has a Tivoli EnterpriseConsole server and you must configure Tivoli Business Systems Manager tointerface with that Tivoli Enterprise Console server.

Set the timeout value to at least 600 seconds to avoid premature task failure.

See alsoNone


Chapter 5. Database tasks

The DB2ManagerDatabaseTasks library contains tasks that provide basicadministration functions for DB2 and the database manager.

For more information about these tasks, see the following manuals for the versionof DB2 that you are using:v DB2 API Reference

v DB2 Command Reference

v DB2 SQL Reference

Table 4 briefly describes each task in the DB2ManagerDatabaseTasks task library.When you view this table online, you can click the task name to go to a fulldescription of that task.

Table 4. DB2ManagerDatabaseTasks

Task Description

ECC_Activate_Database Activates a database

ECC_Alter_Bufferpool Modifies the size of the buffer pool

ECC_Backup_Database Creates a backup of a DB2 database

ECC_Create_Admin_Server Creates the DB2 administration server

ECC_Create_Explain_Tables Creates explain tables

ECC_Create_Sample_Database Creates a DB2 sample database

ECC_Deactivate_Database Deactivates the database

ECC_Drop_Admin_Server Deletes the DB2 administration server instance

ECC_Drop_Sample_Database Drops the DB2 sample database

ECC_Force_All_Applications Forces all DB2 applications off the system

ECC_Force_Applications Forces specific DB2 applications off the system

ECC_Get_Admin_Configuration Retrieves the DB2 administration configuration

ECC_Get_Admin_Server_Instance Retrieves the DB2 administration configurationserver instance name

ECC_Get_Database_Configuration Returns the values of individual entries in thedatabase configuration file

ECC_Get_Database_Manager_Configuration Returns the values of individual entries in thedatabase manager configuration file

ECC_Invoke_Stored_Procedure Invokes a DB2 stored procedure

ECC_List_Applications Lists the DB2 applications

ECC_List_Backup_Recovery_File Lists the DB2 backup and recovery history file

ECC_List_DCS_Applications Lists the DB2 DCS applications

ECC_List_Node_Directory Lists the contents of the node directory

ECC_Prune_Recovery_History_File Prunes the DB2 recovery history file

ECC_Quiesce_Tablespaces Quiesces DB2 tablespaces

ECC_Rebind_All_Packages Rebinds all DB2 packages

ECC_Rebind_Package Rebinds a specific DB2 package

273

Table 4. DB2ManagerDatabaseTasks (continued)

Task Description

ECC_Reorganize_Table Reorganizes a DB2 table

ECC_Reorgchk Runs the DB2 REORGCHK command

ECC_Reset_Admin_Configuration Resets the parameters in the database managerconfiguration file, relevant to the DB2administration server, to the system defaults

ECC_Reset_Database_Configuration Resets the configuration of a specific database tothe system defaults.

ECC_Reset_Database_Manager_Configuration Resets the parameters in the database managerconfiguration file to the system defaults.

ECC_Restart_Database Restarts a DB2 database

ECC_Run_Statistics Runs DB2 statistics

ECC_Set_Admin_Server_ID Establishes or modify the user account associatedwith the DB2 administration server instance

ECC_Start_Admin_Server Starts the DB2 administration server

ECC_Start_DB2 Starts DB2

ECC_Start_DB2_NT_Security Starts the DB2 security service on a Windowssystem

ECC_Stop_Admin_Server Stops the DB2 administration server

ECC_Stop_DB2 Stops DB2

ECC_Stop_DB2_NT_Security Stops the DB2 security service on a Windowssystem

ECC_Update_Admin_Configuration Modifies individual entries in the databasemanager configuration files that are relevant to theDB2 administration server

ECC_Update_Database_Configuration Updates the DB2 database configuration

ECC_Update_Database_Manager_Configuration Updates the DB2 database manager configuration


ECC_Activate_Database

DescriptionActivates the selected database on an endpoint and starts all necessary databaseservices to make the database available for connection and use by any application.


Target endpointDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager


User NameSpecifies the name of the user starting the database. You must use thisvariable if you specify a password, otherwise it is optional.

PasswordSpecifies the password for the user name. You must use this variable if youspecify a user name, otherwise it is optional.


-t ECC_Activate_Database-l DB2ManagerDatabaseTasks- h <hostname>[-a <username>-a <password>]where:


Chapter 5. Database tasks 275

usernameSpecifies the name of the user starting the database. You must use thisvariable if you specify a password, otherwise it is optional.

passwordSpecifies the password for the <username>. You must use this variable ifyou specify a user name, otherwise it is optional.


wruntask-t ECC_Activate_Database-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a joepw

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it activates thespecified database on all nodes within the system.

If a database has not been started and an application encounters the CONNECTTO command, the application must wait while the database manager starts therequired database. However, after the database starts, other applications canconnect and use it without starting it up.

If you initialize a database by using ECC_Activate_Database, you can shut itdown only by running a deactivate database command (such asECC_Deactivate_Database).

For more information, see the ACTIVATE DATABASE CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoDB2ManagerDatabase tasks: “ECC_Deactivate_Database” on page 289


ECC_Alter_Bufferpool

DescriptionModifies the buffer pool size for a single node or all nodes, turns the use ofextended storage on or off, and adds the buffer pool definition to a new nodegroup.




Buffer Pool NameSpecifies the name of the buffer pool you want altered.

ActionSpecifies one of the following arguments:

Alter size for all nodes (Value: number of pages)Alters the buffer pool size on all nodes that use the default bufferpool size. For more information, see the CREATE BUFFERPOOLcommand in the DB2 Command Reference.

Alter size for selected nodes (Value: number of pages)Alters the size of the buffer pool for the DB2 node represented bythe endpoint you selected.

Set extended storage (Value: YES or NO)Sets the extended storage action.

Add nodegroup (Value: nodegroup name)Adds the buffer pool definition to a node group.

Value Specifies one of the following arguments based on the Action you selected:


(Action: Alter size for all nodes or selected nodes)If you specify this action, enter the size of the buffer pool specifiedas the number of pages. If you specify -1, this variable removes thebuffer pool size from the BUFFPAGE database configurationparameter.

(Action: Set extended storage)If you specify this action, enter one of the following parameters:

YES If you turn on the extended storage configuration, pagesthat are migrating out of this buffer pool are cached in theextended storage.

NO Even if you turn on the extended storage configuration,pages that are migrating out of this buffer pool are notcached in the extended storage.

(Action: Add nodegroup)If you specify this action, enter the node group name where youwant to add this buffer pool definition. This action adds the nodegroup name to all nodes in the specified node group if the nodegroup name does not exist. No action is taken when you define thebuffer pool on a node.

User IDSpecifies the name of the user to attach to a remote partition. You must usethis argument only when you drop this task on a partition group endpoint,and at least one of the partitions in the partition group resides on a remotehost. All nodes included in the partition group, whether they are on a localor remote host, use the user name.

PasswordSpecifies the password used to authenticate with the specified user ID.


-t ECC_Alter_Bufferpool-l DB2ManagerDatabaseTasks- h <hostname>-a <name>-a <action>-a <value>[-a <username>-a <password>]where:


name Specifies the name of the buffer pool altered.

action Specifies one of the following arguments:

ALL Alters the buffer pool size on all nodes that use the defaultbuffer pool size. For more information, see the CREATEBUFFERPOOL command in the DB2 Command Reference.


NODEAlters the size of the buffer pool for the DB2 node representedby the endpoint you selected.

SET Sets the extended storage action.

ADD Adds the buffer pool definition to a node group.

value Specifies one of the following arguments:

size If you specify ALL or NODE for the action variable, type thesize of the buffer pool (specified as the number of pages). If youspecify -1, this variable takes the buffer pool size from theBUFFPAGE database configuration parameter.

cache If you specified SET for the action variable, specify one of thefollowing parameters:

YES If you turn on the extended storage configuration, pagesthat are migrating out of this buffer pool are cached inthe extended storage.

NO If you turn on the extended storage configuration, pagesthat are migrating out of this buffer pool are not cachedin the extended storage.

ng_nameIf you specified ADD for the action variable, specify the nodegroup name for this buffer pool definition. The action variableadds the node group name to all nodes in the specified nodegroup if it currently does not exist. If you define the buffer poolon a node, no action is taken.

usernameSpecifies the name of the user to attach to a remote partition. You mustuse this variable only when you drop this task on a partition groupendpoint, and at least one of the partitions in the partition group resideson a remote host. All nodes included in the partition group, whetherthey are on a local or remote host, use the user name.

passwordSpecifies the password used to authenticate the <username> variable.


wruntask-t ECC_Alter_Bufferpool-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a buff2-a ALL-a 20-a joe-a joepw

Usage notesFor more information, see the ALTER BUFFERPOOL statement in the DB2 SQLReference.

See alsoNone


ECC_Backup_Database

DescriptionCreates a backup copy of a database.


Target endpointDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager


User NameSpecifies the name with which to back up the database. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint andat least one of the partitions in the partition group resides on a remotehost, you must specify a user name. All nodes included in the partitiongroup, whether they are on a local or remote host, use the user name.

NONESpecifies to use the current user name.

PasswordSpecifies the password for user name:


NONESpecifies that you do not supply a password. Use NONE if theuser name is NONE.

OnlineEnter YES or NO to specify an online backup.

Use TSMEnter YES or NO to indicate whether to use Tivoli Storage Managermanaged output (formerly ADSM) for the backup.

Number of TSM SessionsSpecifies the number of I/O sessions used with the Tivoli Storage Managermanaged output. This variable has a default value of 2.

If you are not using managed output, specify any number.

Target AreaSpecifies a directory or tape device name for the backup. If you specify adirectory, you must enter the full path on which the directory resides. Thedirectory must already exist. The UNIX hosts uses the /tmp directory forits default. Windows hosts do not have a default.

Number of BuffersSpecifies the number of buffers to use during the backup process. Thisvariable has a typical value of 1.

Buffer SizeSpecifies the number of pages that the buffer uses when building thebackup image. The buffer size has a minimum size of 16 pages and adefault of 1024.

ParallelismSpecifies the number of buffer manipulators to spawn during the restoreprocess. This variable has a default of 1. Only DB2 Enterprise-ExtendedEdition can use this variable.

Library NameAn optional variable that specifies the name of the shared library thatcontains the vendor backup and restore input and output functions used.This variable can contain the full path and file name of the library. If youdo not specify the full path, the path defaults to where the user exitprogram resides.

TablespaceSpecifies one or more tablespaces to back up. If you do not specify atablespace, all tablespaces are backed up. To specify more than onetablespace, separate them using commas.


-t ECC_Backup_Database-l DB2ManagerDatabaseTasks-h <hostname>-a <username>-a <password>-a <online>-a <adsm>-a <adsmnum>


-a <target>-a <numbuf>-a <bufsize>[-a <parallelism>-a <libname>-a <tablespace>]

where:


usernameSpecifies the name with which to back up the database. If you run thistask with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All nodes included inthe partition group, whether they are on a local or remote host, use theuser name.

NONESpecifies to use the current user name.

usernameSpecifies a specific user name.

passwordSpecifies the password for <username>:

NONESpecifies that you do not supply a password. Use NONE if the<username> is NONE.

passwordSpecifies the password used to authenticate the user nameentered for <username>. You must use this value if you specify auser name.

online Specifies YES or NO to indicate an online backup.

tsm Specifies YES or NO to indicate whether to use Tivoli Storage Managermanaged output (formerly ADSM) for the backup.

tsmnumSpecifies the number of I/O sessions used with the Tivoli StorageManager managed output. This variable uses a typical value of 2.

If you are not using managed output, specify any number.

target Specifies a directory or tape device name to which to write the backup.If you specify a directory, you must enter the full path on which thedirectory resides. The directory must already exist.

numbufSpecifies the number of buffers to use during the backup process. Thisvariable uses a typical value of 1.

bufsize Specifies the number of pages that the buffer uses when building thebackup image. The buffer uses a minimum size of 16 pages. Thisvariable uses a typical value of 1024 (1024 pages).

parallelismSpecifies the number of buffer manipulators to generate during the


restore process. This variable uses a default of 1. Only DB2Enterprise-Extended Edition uses this variable.

libnameAn optional variable that specifies the name of the shared library thatcontains the vendor backup and restore I/O functions used. The libnamevariable can contain the full path and file name of the library. If you donot specify the full path, the path defaults to where the user exitprogram resides.

tablespaceSpecifies one or more tablespaces to back up. If you do not specify atablespace, all tablespaces are backed up. To specify more than onetablespace, place the names in double quotation marks separated bycommas. For example, "tblspc01,tblspc02".


wruntask-t ECC_Backup_Database-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a joepw-a NO-a NO-a 0-a /dev/rmt0-a 1-a 1024-a None-a "tblspc01,tblspc02"

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it backs up only thenode on which you executed.

Because this task takes longer to complete than the default time of 60 seconds, setthe timeout value to a larger value. For example, 600 seconds.

If a database becomes damaged or corrupted, it returns to the state of the backedup copy. If this task enables a successfully restored database for roll-forwardrecovery at the time of the backup, return the database to its previous state prior tothe occurrence of damage. The task directs the backup to hard disk, diskette, tape,Tivoli Storage Manager utility, or to other vendor products enabled for DB2.

For more information, see the BACKUP DATABASE CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Create_Admin_Server

DescriptionCreates the DB2 Administration Server on a Windows host.




User NameSpecifies the name with which to create a DB2 Administration Server.

PasswordSpecifies the password used to authenticate the user name.


-h ECC_Create_Admin_Server-l DB2ManagerDatabaseTasks-t <hostname>[-a <username>-a <password>]

where:


usernameSpecifies the name with which to create a DB2 Administration Server.


passwordSpecifies the password used to authenticate the user name.


wruntask-t ECC_Create_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw

Usage notesIf the user and password variables are specified, the DB2 Administration Serverinstance is associated with this user account. You must use a valid SQL identifierthat exists in the security database for the specified user account.

For more information, see the db2admin system command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_Create_Explain_Tables

DescriptionCreates DB2 Explain tables in the specified database.





-t ECC_Create_Explain_Tables-l DB2ManagerDatabaseTasks-h <hostname>where:



wruntask-t ECC_Create_Explain_Tables-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr@db2dba@bburns

Usage notesThis task uses the EXPLAIN.DLL provided by DB2 to create the following explaintables:v EXPLAIN_ARGUMENTv EXPLAIN_INSTANCEv EXPLAIN_OBJECTv EXPLAIN_OPERATORv EXPLAIN_PREDICATEv EXPLAIN_STATEMENTv EXPLAIN_STREAM

For more information, see the DB2 SQL Reference for the version of DB2 that youare using.

See alsoNone


ECC_Create_Sample_Database

DescriptionCreates a DB2 sample database named SAMPLE.




PathnameSpecifies the path on which to create the SAMPLE database. On Windows,the path is a single drive letter.

NONESpecifies to create SAMPLE on the default database path.


-t ECC_Create_Sample_Database-l DB2ManagerDatabaseTasks-h <hostname>[-a <path>]

where:


path Specifies the path on which to create the SAMPLE database:


NONESpecifies to create SAMPLE on the default database path.

path Specifies a path. On Windows, the path is a single drive letter.


wruntask-t ECC_Create_Sample_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a G

Usage notesWhen this you run this task on DB2 Enterprise-Extended Edition, it affects allnodes in the node group.

You can run this task only on DB2 server nodes. The task cannot create theSAMPLE database on nodes that are database clients only. The task creates thedatabase with the instance authentication type that the database managerconfiguration parameter authentication specifies. The user ID determines thequalifiers for the tables. If the SAMPLE database already exists, this task createsthe tables for the user ID that issued the command and grants the appropriateprivileges.

This task has a default timeout of 60 seconds. This task does not display thecompletion status if the task does not complete in this amount of time. The task,however, continues to completion. To help ensure that the status displays, you canspecify a longer timeout period.

For more information, see the db2sampl system command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_Deactivate_Database

DescriptionStops the database that you specify.




User NameSpecifies the name of the user stopping the database. You must use thisvariable if you specify a password, otherwise it is optional.

PasswordSpecifies the password for the user name. You must use this variable if youspecify a user name, otherwise it is optional.


-t ECC_Deactivate_Database-l DB2ManagerDatabaseTasks-h <hostname>[-a <username>-a <password>]

where:



usernameSpecifies the name of the user stopping the database. You must use thisvariable if you specify a password, otherwise it is optional.

passwordSpecifies the password for the user name. You must use this variable ifyou specify a user name, otherwise it is optional.


wruntask-t ECC_Deactivate_Database-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr@db2dba@bburns-a joe-a joepw

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it deactivates thespecified database on all nodes within the system.

If you initialize a database with an activate database command (such asECC_Activate_Database) you can shut it down only with a deactivate databasecommand (such as this one). If you initialize a database with an activate databasecommand, the last application that disconnects from the database does not shutdown the database.

For more information, see the DEACTIVATE DATABASE CLP command in theDB2 Command Reference for the version of DB2 that you are using.

See alsoDB2ManagerDatabase tasks: “ECC_Activate_Database” on page 275


ECC_Drop_Admin_Server

DescriptionDeletes the DB2 Administration Server instance on a Windows host.

RestrictionsThis task runs only on the DB2 Universal Database Enterprise Edition.





-t ECC_Drop_Admin_Server-l DB2ManagerDatabaseTasks-h <hostname>where:



wruntask-t ECC_Drop_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesFor more information, see the db2admin system command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_Drop_Sample_Database

DescriptionDeletes the contents and all log files of the SAMPLE database, uncatalogs thedatabase, and deletes the database subdirectory.





-t ECC_Drop_Sample_Database-l DB2ManagerDatabaseTasks-h <hostname>where:



wruntask-t ECC_Drop_Sample_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesWhen you run this task on the DB2 Enterprise-Extended Edition, it affects allnodes that are listed in the db2nodes.cfg file.

The SAMPLE database must not be in use when you run this task; you mustdisconnect all users before you can drop the database. You must catalog theSAMPLE database in the system database directory. If the only entry in the localdatabase directory is the SAMPLE database, the local database directory deletesautomatically.

For more information, see the DROP DATABASE CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Force_All_Applications

DescriptionForces local or remote users or applications off of a DB2 instance to allow formaintenance on a server.





-t ECC_Force_All_Applications-l DB2ManagerDatabaseTasks-h <hostname>where:



wruntask-t ECC_Force_All_Applications-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it affects all nodesthat are listed in the $HOME/sqllib/db2nodes.cfg file.

Forcing a user off of a DB2 instance results in the loss of that user’s connections toall databases. To preserve database integrity, you can terminate only those userswho are idling or running interruptible database operations. You cannot force userswho are creating a database.

If an operation that you cannot interrupt is forced, you must successfully rerun theoperation before the database becomes available. You cannot run ECC_Stop_DB2during a force. The database manager remains active so that you can handlesubsequent database manager operations without the need to run ECC_Start_DB2.

After you issue a FORCE command, the database stops accepting requests.Additional force commands are required to completely force all users off.


For more information, see the sqlefrce system command in the DB2 API Referencefor the version of DB2 that you are using.

See alsoDB2ManagerDatabase tasks: “ECC_Start_DB2” on page 345, “ECC_Stop_DB2” onpage 351


ECC_Force_Applications

DescriptionForces specific local or remote DB2 applications and users off of the system toallow for maintenance on a server.




Application 1...Application 10Specifies one to ten application IDs if you are running DB2 UDB or one toten application handles if you are running DB2 Enterprise-ExtendedEdition.


-t ECC_Force_Applications-l DB2ManagerDatabaseTasks-h <hostname>-a <application01>[-a <application02>


-a <application03>-a <application04>-a <application05>-a <application06>-a <application07>-a <application08>-a <application09>-a <application10>]

where:


applicationSpecifies one to ten application IDs if you are running DB2 UDB or oneto ten application handles if you are running or DB2Enterprise-Extended Edition. For example, you might specify 41408.


wruntask-t ECC_Force_Applications-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a 41408-a 42623

Usage notesYou can use the ECC_List_Applications task to find the application IDs orapplication handles of currently running applications. You must specify at least oneapplication ID or application handle.

When you run this task on DB2 Enterprise-Extended Edition, it affects all nodesthat are listed in the $HOME/sqllib/db2nodes.cfg file.

Forcing a user off of a DB2 instance results in the loss of that user’s connections toall databases. To preserve database integrity, you can only terminate users who areidling or running interruptible database operations. You cannot force users creatinga database.

If an operation that you cannot interrupt is forced, you must successfully rerun theoperation before the database becomes available. You cannot run ECC_Stop_DB2during a force. The database manager remains active so that you can handlesubsequent database manager operations without the need to run ECC_Start_DB2.

After you issue a FORCE command, the database stops accepting requests toconnect. Additional force commands are required to completely force all users off.

For more information, see the FORCE APPLICATION CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoDB2ManagerDatabase tasks: “ECC_Start_DB2” on page 345, “ECC_Stop_DB2” onpage 351


ECC_Get_Admin_Configuration

DescriptionRetrieves the DB2 administration configuration.





-t ECC_Get_Admin_Configuration-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Get_Admin_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesThe DB2 Administration Server is a special instance that enables remoteadministration of DB2 servers. For DB2 Enterprise-Extended Edition, thiscommand returns information about all nodes that share the same $HOME/sqllibdirectory, and you can issue it from any of these nodes.

For more information, see the GET ADMIN CONFIGURATION CLP command inthe DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Get_Admin_Server_Instance

DescriptionRetrieves the DB2 Administration Server instance name.





-t ECC_Get_Admin_Server_Instance-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Get_Admin_Server_Instance-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns


See alsoNone


ECC_Get_Database_Configuration

DescriptionReturns the values of individual entries in the database configuration file.




User IDSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resides ona remote host, you must specify a user name. All nodes included in thepartition group, whether they are on a local or remote host, use the username.



-t ECC_Get_Database_Configuration-l DB2ManagerDatabaseTasks-h <hostname>[-a <username>-a <password>]

where:



usernameSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All nodes included inthe partition group, whether they are on a local or remote host, uses theuser name.



wruntask-t ECC_Get_Database_Configuration-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a jjones-a jones

Usage notesWhen you run this command on DB2 Enterprise-Extended Edition, it returnsinformation about the node on which you run it.

For more information, see the GET DATABASE CONFIGURATION CLPcommand in the DB2 Command Reference for the version of DB2 that you are usingand the sqlfxdb command in the DB2 API Reference for the version of DB2 thatyou are using.

See alsoNone


ECC_Get_Database_Manager_Configuration

DescriptionReturns the parameters set in the database manager configuration file.





-t ECC_Get_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Get_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesIf no keys are specified, all database manager configuration parameter values arereturned. If one or more keys are specified, only the values for the specifiedparameters are returned.

For more information, see the GET DATABASE MANAGER CONFIGURATIONCLP command in the DB2 Command Reference for the version of DB2 that you areusing and the sqlfxsys command in the DB2 API Reference for the version of DB2that you are using.

See alsoNone


ECC_Invoke_Stored_Procedure

DescriptionInvokes a specified procedure that you created using DB2 which resides at thelocation of the database.




Program nameSpecifies the name of the procedure in the database to run on the server.

Server input dataSpecifies any data to pass to the server routine. Separate multiple pieces ofdata with commas.


-t ECC_Invoke_Stored_Procedure-l DB2ManagerDatabaseTasks-h <hostname>-a <name>[-a "<data>"]

where:


name Specifies the name of the procedure.


"data" An optional variable that specifies any data to pass to the server routine.Quotation marks are required if you specify more than one piece of data.


wruntask-t ECC_Invoke_Stored_Procedure-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a proc1-a "dob,address"

Usage notesThe server procedure runs at the location of the database and returns data to theclient application.

The program runs in two parts, one on the client and the other on the server. Theserver procedure at the database runs within the same transaction as the clientapplication. If the client application and the server procedure are on the samenode, the server procedure runs locally.

For more information, see the INVOKE STORED PROCEDURE CLP command inthe DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_List_Applications

DescriptionLists the application program name, authorization ID (user name), agent ID,application ID, and database name.




Show Detail?Select Yes to show details. This variable has a default of No.




-t ECC_List_Applications-l DB2ManagerDatabaseTasks-h <hostname>[-a <detail>-a <username>


-a <password>]

where:


detail Specifies YES to show details. This variable uses a default of NO.

usernameSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All nodes included inthe partition group, whether they are on a local or remote host, use theuser name.



wruntask-t ECC_List_Applications-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a YES-a joe-a joepw

Usage notesIf this task runs on a DB2 instance endpoint, all applications are listed. If you runthis task on a DB2 database endpoint, only the applications for the database arelisted.

When you run this task on DB2 Enterprise-Extended Edition, this task lists onlythose applications that are on the selected node.

For more information, see the LIST APPLICATIONS CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_List_Backup_Recovery_File

DescriptionLists a DB2 backup and recovery file.




List TypeSelect the type of list request from the following options:

All Lists all entries in the recovery history file. This option is thedefault.

Since Lists entries based on the time stamp specified in the Time stamptext box.

ContainingLists the table or tablespace specified in the Name text box.

Time StampSpecifies a complete time stamp (yyyymmddhhnnss) or an initial prefixtime stamp using a minimum of yyyy. If you selected All or Containing inthe Type drop-down list, Time stamp is ignored.

Schema NameAn optional variable that specifies a schema name to use as a qualifier fora table name. Specifies None to uniquely identify a tablespace with thename variable. If you specify the All or Since parameters in the typevariable, this variable is ignored.


Object NameIf you entered a schema name, enter a table name to use. The‘schema.name’ identifies the table. If you entered None for the schemaname, specify the unique identifier for a tablespace. If you entered All orSince in the Type text box, this variable is ignored. For more information,see the DB2 SQL Reference for the version of DB2 that you are using.




-t ECC_List_Backup_Recovery_File-l DB2ManagerDatabaseTasks-h <hostname>[-a <type>[-a <timestamp>[-a <schema>]-a <name>-a <username>[-a <password>]

where:


type An optional variable that specifies the type of list request.

ALL Lists all entries in the recovery history file. The variable uses thisoption as the default.

SINCELists entries based on the time stamp specified in the time stampvariable.

CONTAININGLists the table or tablespace specified in the name variable.

timestampAn optional variable that specifies a complete time stamp(yyyymmddhhnnss) or an initial prefix time stamp with a minimum ofyyyy. If you specify the ALL or CONTAINING parameters in the typevariable, this variable is ignored.

schema An optional variable that specifies a schema name to use as a qualifierfor a table name. Specifies NONE to uniquely identify a tablespace withthe name variable. If you specify the ALL or SINCE parameters in thetype variable, this variable is ignored.


name If you specified a schema name, specify the table name to use. The‘schema.name’ identifies the table. If you specified NONE for theschema variable, specify the unique identifier for a tablespace. If youspecify the ALL or SINCE parameters in the type variable, this variableis ignored. For more information, see the DB2 SQL Reference for theversion of DB2 that you are using.

usernameSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All included in thepartition group, whether they are on a local or remote host, use the username.



wruntask-t ECC_List_Backup_Recovery_File-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a SINCE-a 1998-a None-a None-a joe-a joepw

Usage notesFor more information, see the LIST HISTORY CLP command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_List_DCS_Applications

DescriptionLists the contents of the Database Connection Services (DCS) directory.


Target endpointDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager,DB2Gateway, and DB2InstanceManager


Show Detail?Select Yes to include detailed information in the output or No to excludedetailed information.

The detailed information includes:v Application IDv Application sequence numberv Client database aliasv Client product IDv Code page IDv Outbound sequence numberv Host database namev Host product ID

If you specify NO, the task returns the following information:v Host authorization ID (user name)v Application program namev Agent IDv Outbound application ID (luwid)





-h ECC_List_DCS_Applications-l DB2ManagerDatabaseTasks-h <hostname>-a <show_detail>[-a <username>-a <password>]

where:


show_detailSpecifies YES or NO to indicate if the output needs to include detailedinformation.

If you specify YES, the task returns the following information:– Application ID– Application sequence number– Client database alias– Client product ID– Code page ID– Outbound sequence number– Host database name– Host product ID

If you specify NO, the task returns the following information:– Host authorization ID (user name)– Application program name– Agent ID– Outbound application ID (luwid)





wruntask-t ECC_List_DCS_Applications-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a YES-a joe-a joepw

Usage notesYou can use this task to match client application connections to the gateway withcorresponding host connections from the gateway. You can also use agent IDinformation to force specified applications off a DCS server.

For more information, see the LIST DCS APPLICATIONS command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_List_Node_Directory

DescriptionLists the contents of the node directory.




Admin nodesSelect Yes to list the contents of the Administration Server nodes. Thisoption has a default of Yes.

Show DetailSelect Yes to include detailed information about the node directory. Thisoption has a default of Yes.


-t ECC_List_Node_Directory-l DB2ManagerDatabaseTasks-h <hostname>-a <admin>-a <detail>

where:



admin An optional variable that specifies YES to select Administration Servernodes. This option uses a default of NO.

detail An optional variable that specifies YES to show details. This option usesa default of NO.


wruntask-t ECC_List_Node_Directory-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a YES-a NO

Usage notesThis task creates and maintains a node directory on each database client andcontains an entry for each remote workstation that has a database that the clientcan access. This task identifies a range of entries in the recovery history files thatare deleted. All entries with time stamps equal to or less than the time stampprovided are deleted. You can selectively delete the entries even if some entriesfrom the most recent restore set are deleted from the file.

For more information, see the LIST NODE DIRECTORY CLP command in theDB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Prune_Recovery_History_File

DescriptionDeletes entries from the recovery history file.




Time StampSpecifies a complete time stamp (of the form yyyymmddhhmmss) or aninitial prefix (minimum of yyyy) time stamp. All entries in the recoveryhistory file that have time stamps equal to or less than the specified timestamp are deleted from the file.

The following shows an example of the complete time stamp:19971214102030

The following shows an example of an initial prefix:199712

Force OptionSelect Yes to prune the entries based on the time stamp specified, even ifsome entries from the most recent restore set are deleted from the file.Selecting No will not prune the entries.





-t ECC_Prune_Recovery_History_File-l DB2ManagerDatabaseTasks-h <hostname>-a <timestamp>-a <force>[-a <username>-a <password>]

where:


timestampSpecifies a complete time stamp (of the form yyyymmddhhmmss) or aninitial prefix (minimum form of yyyy). All entries in the recovery historyfile that have time stamps equal to or less than the specified time stampare deleted from the file.

The following shows an example of a complete time stamp:19971214102030

The following shows an example of an initial prefix time stamp:199712

force Specifies YES or NO to indicate whether or not to delete entries fromthe most recent store set from the file if they meet the time stampcriteria.

usernameSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All nodes included inthe partition group, whether they are on a local or remote host, use auser name.



wruntask-t ECC_Prune_Recovery_History-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a 199712-a YES-a joe-a joepw


Usage notesThis task identifies a range of entries in the recovery history file that are deleted.All entries with time stamps equal to or less than the time stamp provided aredeleted. You can prune entries even if some entries from the most recent restore setare deleted from the file.

For more information, see the PRUNE HISTORY CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Quiesce_Tablespaces

DescriptionQuiesces tablespaces for a DB2 table.




Table SchemaSpecifies the qualified table name. If you do not provide a schema, the taskuses the authorization ID used for the database connection as the schema.You cannot use a system catalog table for the table.

Table NameSpecifies the unqualified table name. For example, a table with a qualifiedname of USERID.TABLE1 has an unqualified table name of TABLE1.

Quiesce ModeSelect the quiesce mode that you want to set for the tablespaces:

Share Specifies that the tablespaces are put in shared mode. In this mode,all users (yourself included) can read but not change the table data.

Intent to updateSpecifies that the tablespaces are put in update mode. In thismode, only you can update the table data. Other users can readbut not update the data.

ExclusiveSpecifies that the tablespaces are put in exclusive mode. In thismode, only you can read or update the table data.

Reset Specifies that the tablespaces are put in normal mode.





-t ECC_Quiesce_Tablespaces-l DB2ManagerDatabaseTasks-h <hostname>-a <schema>-a <name>-a <mode>[-a <username>-a <password>]

where:


schema Specifies the qualified table name. If you do not provide a schema, thetask uses the authorization ID used for the database connection as theschema. You cannot use a system catalog table for the table.

name Specifies the unqualified table name. For example, a table with aqualified name of USERID.TABLE1 has an unqualified table name ofTABLE1.

mode Specifies the quiesce mode in which you want to put the tablespaces forthe table:

SHARESpecifies that the tablespaces are put in shared mode. In thismode, all users (yourself included) can read but not change thetable data.

INTENTSpecifies that the tablespaces are put in update mode. In thismode, only you can update the table data. Other users can read,but not update the data.

EXCLUSIVESpecifies that the tablespaces are put in exclusive mode. In thismode, only you can read or update the table data.

RESETSpecifies that the tablespaces are put in normal mode.

usernameSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition group


endpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All nodes included inthe partition group, whether they are on a local or remote host, use theuser name.



wruntask-t ECC_Quiesce_Tablespaces-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a userid.table1-a table1-a SHARE-a joe-a joepw

Usage notesWhen this task runs on DB2 Enterprise-Extended Edition in a single-nodeenvironment, it quiesces all tablespaces in a load operation in exclusive mode forthe duration of the load. In an MPP environment, this task acts locally on a nodeand quiesces only the portion of tablespaces that belong to the node where theapplication performs the load.

If the table being quiesced does not have a specified owner, the application usesthe db2ecc user ID as the default.

Valid quiesce modes are share, intent to update, and exclusive. The three possiblestates that result from this task are QUIESCED SHARE, QUIESCED UPDATE, andQUIESCED EXCLUSIVE.

When you make the quiesce share request, the transaction requests intent sharelocks for the tablespaces and a share lock for the table. When the transactionobtains the locks, the state of the tablespaces changes to QUIESCED SHARE. Theapplication grants the state to the quiescer only if other users do not hold aconflicting state. The transaction records the state of the tablespaces in thetablespace table, along with the authorization ID and the database agent ID of thequiescer, to keep the state persistent.

You cannot change the table while the tablespaces for the table are in QUIESCEDSHARE state. Other share mode requests to the table and tablespaces are allowed.When the transaction commits or rolls back, the locks are released, but thetablespaces for the table remain in QUIESCED SHARE state until you explicitlyreset the state.

When you make the quiesce exclusive request, the transaction requests superexclusive locks on the tablespaces, and a super exclusive lock on the table. Whenthe transaction obtains the locks, the state of the tablespaces changes to QUIESCEDEXCLUSIVE. The state of the tablespaces, along with the authorization ID and thedatabase agent ID of the quiescer, are recorded in the tablespace table. Because thetablespaces are held in super exclusive mode, no other access to the tablespaces isallowed. The user who invokes the quiesce function (the quiescer), however, hasexclusive access to the table and the tablespaces.


When you make a quiesce update request, the tablespaces are locked in intentexclusive (IX) mode, and the table locks in update (U) mode. The task records thestate of the tablespaces with the quiescer in the tablespace table.

For more information, see the QUIESCE TABLESPACES FOR TABLE CLPcommand in the DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Rebind_All_Packages

DescriptionRebinds all DB2 packages in a database.




Log fileSpecifies the path (optional) and the file name (mandatory) used forrecording errors that result from the package revalidation procedure.

User IDSpecifies the name of the user who rebinds the database. You must specifythe user ID if you specify a password, otherwise it is optional.

PasswordSpecifies the password used to authenticate with the specified user ID. Youmust specify the password if you specify a user ID, otherwise it isoptional.


-t ECC_Rebind_All_Packages-l DB2ManagerDatabaseTasks-h <hostname>-a <log_file>[-a <username>-a <password>]

where:



log_file Specifies the path (optional) and the file name (required) used forrecording errors that result from the package revalidation procedure.

usernameSpecifies the name of the user who rebinds the database. You mustspecify this variable if you specify a password, otherwise it is optional.

passwordSpecifies the password for the user name. You must specify this variableif you specify a user name, otherwise it is optional.


wruntask-t ECC_Rebind_All_Packages-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a /tmp/pkg.log-a joe-a joepw

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it affects all nodes inthe node group.

This task uses the CLP REBIND command to attempt the revalidation of allpackages in a database. You can allow package revalidation to occur implicitlywhen the packages are first used.

For more information, see the db2rbind system command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_Rebind_Package

DescriptionLets users re-create a package stored in the database without requiring a bind file.




Package SchemaSpecifies the qualifier for the package name. For example, a package with aqualified name of USERID.PACK1 has a schema of USERID.

If you specify _default_, the task uses the user ID.

Package NameSpecifies the unqualified package name. For example, a package with aqualified name of USERID.PACK1 has an unqualified package name ofPACK1.


-t ECC_Rebind_Package-l DB2ManagerDatabaseTasks-h <hostname>-a <schema>-a <name>

where:



schema Specifies the qualifier for the package name. For example, a packagewith a qualified name of USERID.PACK1 has a schema of USERID.

If you specify _default_, the application uses the current user ID.

name Specifies the unqualified package name. For example, a package with aqualified name of USERID.PACK1 has an unqualified package name ofPACK1.


wruntask-t ECC_Rebind_Package-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a pack1

Usage notesThe REBIND command does not automatically commit the transaction following asuccessful rebind. The user must explicitly commit the transaction. This enables“what if” analysis, in which the user updates certain statistics, and then tries torebind the package to see what changes. It also permits multiple rebinds within aunit of work.

The REBIND command commits the transaction if you enable auto-commit.

For more information, see the REBIND CLP command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_Reorganize_Table

DescriptionReorganizes a table by reconstructing the rows to eliminate fragmented data, andby compacting information.




Table SchemaSpecifies the qualifier for the table name. For example, a table with aqualified name of USERID.TABLE1 has a schema of USERID.


Index SchemaSpecifies the qualifier for the index name.

Index NameSpecifies the unqualified index name.

Table Space NameSpecifies the unqualified tablespace name.


-t ECC_Reorganize_Table-l DB2ManagerDatabaseTasks-h <hostname>


-a <schema>-a <name>[-a <i_schema>-a <i_name>[-a <ts_name>]]

where:


schema Specifies the qualifier for the table name. For example, a table with aqualified name of USERID.TABLE1 has a schema of USERID.


i_schemaSpecifies the qualifier for the index name.

i_name Specifies the unqualified index name.

ts_nameSpecifies the unqualified tablespace name.


wruntask-t ECC_Reorganize_Table-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a table1-a NONE-a NONE-a tblspc1


Because this task might take longer to complete than the 60-second default time,set the timeout value to a larger value, such as 600 seconds.

Data fragments and access performance slows down when you modify tablesseveral times. These are candidates for reorganization. Use ECC_Reorgchk todetermine if a table needs reorganizing. Complete all database operations andrelease all locks before running ECC_Reorganize_Table. After reorganizing a table,use ECC_Run_Statistics to update the table statistics and ECC_Rebind_Packagesto rebind the packages that use this table.

If you complete an unsuccessful reorganization, do not delete temporary files. Thedatabase manager uses these files to recover the database.

For more information, see the REORGANIZE TABLE CLP command in the DB2Command Reference for the version of DB2 that you are using.


See alsoDB2ManagerDatabase tasks: “ECC_Reorgchk” on page 328, “ECC_Run_Statistics”on page 338, and “ECC_Rebind_Package” on page 323


ECC_Reorgchk

DescriptionCalculates statistics on the database to determine if you need to reorganize tablesin order to improve performance.




StatisticsSelect the type of table statistics to use:

CurrentSpecifies that the current table statistics are used to determine ifyou need to reorganize tables in order to improve performance.

UpdateSpecifies to use the DB2 RUNSTATS utility to update tablestatistics. These updated statistics are then used to determine ifyou need to reorganize tables in order to improve performance.

On TableSelect the tables to check:

User Specifies that all tables owned by the current authorization ID arechecked.

SystemSpecifies that all system tables are checked.

All Specifies that all user-owned and system-owned tables are checked.

Table Specifies to check a particular table (specified with schema andname).





-t ECC_Reorgchk-l DB2ManagerDatabaseTasks-h <hostname>-a <stats>-a <on_table>[-a <schema>-a <name>]

where:


stats Specifies the type of table statistics to use:

UPDATESpecifies to use the DB2 RUNSTATS utility to update tablestatistics. These updated statistics are then used to determine ifyou need to reorganize tables in order to improve performance.

CURRENTSpecifies that the current table statistics are used to determine ifyou need to reorganize tables in order to improve performance.

on_tableSpecifies the tables to check:

USER Specifies that all tables owned by the current authorization IDare checked.

SYSTEMSpecifies that all system tables are checked.

ALL Specifies that all user-owned and system-owned tables arechecked.

TABLESpecifies to check a particular table (specified with schema andname).





wruntask-t ECC_Reorgchk-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a CURRENT-a SYSTEM-a joe-a table1


This task calculates statistics obtained from six different formulas to determine ifperformance has deteriorated or you can improve performance by reorganizing atable.

For more information, see the REORGCHK CLP command in the DB2 CommandReference for the version of DB2 that you are using.

See alsoNone


ECC_Reset_Admin_Configuration

DescriptionResets the parameters in the database manager configuration file (that are relevantto the DB2 Administration Server) to the system defaults.





-t ECC_Reset_Admin_Configuration-l DB2ManagerDatabaseTasks-h <hostname>


wruntask-t ECC_Reset_Admin_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesThe DB2 Administration Server enables remote administration of DB2 servers. Thiscommand resets the database manager configuration file, $HOME/sqllib/db2systm.This command affects all nodes that are listed in the $HOME/sqllib/db2nodes.cfgfile.

For more information, see the RESET ADMIN CONFIGURATION CLP commandin the DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Reset_Database_Configuration

DescriptionResets the configuration of a specific database to the system defaults.







-t ECC_Reset_Database_Configuration-l DB2ManagerDatabaseTasks-h <hostname>[-a <username>-a <password>]where:



usernameSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resideson a remote host, you must specify a user name. All nodes included inthe partition group, whether they are on a local or remote host, use auser name.



wruntask-t ECC_Reset_Database_Configuration-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a joepw

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it affects only thenode on which run the task.

Changes to the database configuration file become effective only after they areloaded into memory. All applications must disconnect from the database before thechanges can occur.

If an error occurs, the database configuration file does not change. You cannot resetthe database manager configuration file with an invalid checksum. Changing thedatabase configuration file without using the appropriate command causes aninvalid checksum. If this problem occurs, you must restore the database to resetthe database configuration file.

For more information, see the RESET DATABASE CONFIGURATION CLPcommand in the DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Reset_Database_Manager_Configuration

DescriptionResets the parameters in the database manager configuration file to the systemdefaults.


Target endpointDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager,DB2InstanceManager, and Endpoints



-t ECC_Reset_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Reset_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesChanges to the database manager configuration file become effective only afterthey are loaded into memory. For a server configuration parameter, the changesoccur when ECC_Start_DB2 runs. For a client configuration parameter, changesoccur when you restart the application.

If an error occurs, the database manager configuration file does not change.Changing the database manager configuration file without using the appropriatecommand causes an invalid checksum. You cannot reset the database managerconfiguration file with an invalid checksum. If this problem occurs, you mustinstall the database manager again to reset the database manager configuration file.

For more information, see the RESET DATABASE MANAGERCONFIGURATION CLP command in the DB2 Command Reference for the versionof DB2 that you are using.


See alsoDB2ManagerDatabase tasks: “ECC_Start_DB2” on page 345


ECC_Restart_Database

DescriptionRestarts an abnormally terminated database left in an inconsistent state.




User NameSpecifies the user restarting the database. If you run this task with DB2Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group resides on a remote host, you mustspecify a user name. All nodes included in the partition group, whetherthey are on a local or remote host, use the user name.

PasswordSpecifies the password for the user name. The task requires this option ifyou specify the user ID.

Drop Tablespace?Specifies if the user wants the database restart operation to successfullycomplete even if tablespace container problems are encountered.

Tablespace nameSpecifies the name of the new system temporary tablespace name used iftablespace container problems are encountered.


-t ECC_Restart_Database-l DB2ManagerDatabaseTasks-h <hostname>


[-a <username>-a <password>]

where:


usernameSpecifies the user restarting the database. If you run this task with DB2Enterprise-Extended Edition on a partition group endpoint and at leastone of the partitions in the partition group resides on a remote host, youmust specify a user name. All nodes included in the partition group,whether they are on a local or remote host, use the user name.

passwordSpecifies the password for the user name. The task requires this variableif you specify the <username> variable.


wruntask-t ECC_Restart_Database-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a joepw

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it affects only thenode on which you execute the task.

Run this task if an attempt to connect to a database returns an error messageindicating that you must restart the database. An error occurs only if the previoussession with this database terminated abnormally (for example, due to powerfailure).

For more information, see the RESTART DATABASE CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Run_Statistics

DescriptionUpdates statistics about the physical characteristics of a table and the associatedindexes.






With distribution?Enter Yes or No to indicate whether you want distribution statisticscalculated.

IndexesSelect one of the following responses:


Yes Updates statistics on the indexes.

No Does not update statistics on the indexes.

Index Specifies to update statistics on a specific index that theindex-schema and index-name variables define.

Indexes Only?Select Yes or No to indicate whether you want to update statistics on theindexes only.

If you define the Indexes? argument as Yes and Index only? as No,statistics on both the table and its indexes are updated.

If you define the Indexes? argument as No and Index only? as No,statistics on the table only are updated.

Detailed?Enter Yes or No to indicate whether you want extended index statisticscalculated when you are updating statistics on the indexes.

Share LevelSelect Change or Reference to indicate how other users can access thetable while statistics are calculated:

ChangeOther users can read from and write to the table while statistics arecalculated.

ReferenceOther users can only read from the table while statistics arecalculated.

Index SchemaSpecifies the qualifier for the index name. The task requires this variable ifyou specify the Index parameter for the Indexes? variable.

Index NameSpecifies the unqualified index name. The task requires this variable if youspecify the Index parameter for the Indexes? variable.




-t ECC_Run_Statistics-l DB2ManagerDatabaseTasks-h <hostname>-a <schema>-a <name>-a <with_dist>-a <indexes>


-a <index_only>-a <detailed>-a <change>[-a <index-schema>-a <index-name>-a <username>-a <password>]

where:




with_distSpecifies YES or NO to indicate whether you want distribution statisticscalculated.

indexes Specifies one of the following responses:

YES Updates statistics on the indexes.

NO Does not update statistics on the indexes.

INDEXSpecifies to update statistics on a specific index that theindex-schema and index-name variables define.

index_onlySpecifies YES or NO to indicate whether you want to update statisticson the indexes only.

If you define the indexes variable as YES and index_only variable as NO,statistics on both the table and its indexes are updated.

If you define the indexes variable as NO and index_only variable as NO,statistics on the table only are updated.

detailedSpecifies YES or NO to indicate whether you want extended indexstatistics calculated when you are updating statistics on the indexes.

change Specifies how other users can access the table while statistics arecalculated:

changeOther users can read from and write to the table while statisticsare calculated.

referenceOther users can only read from the table while statistics arecalculated.

index-schemaSpecifies the qualifier for the index name. The task requires this variableif you specify the INDEX parameter for the indexes variable.


index-nameSpecifies the unqualified index name. The task requires this variable ifyou specify the INDEX parameter for the indexes variable.




wruntask-t ECC_Run_Statistics-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a table1-a NO-a NO-a NO-a YES-a reference-a NONE-a index2-a joe-a joepw


Run this task when a table has had many updates, or after reorganizing a table.The statistics updated by this task include number of records, number of pages,and average record length. The optimizer uses these statistics when determiningaccess paths to the data.

After statistics are updated, you can create new access paths to the table byrebinding the packages.

Collect statistics that apply only to the tables before you create indexes. By runningthe table statistics first, you ensure that the index statistics are not overlaid by tablestatistics.

For more information, see the RUN STATISTICS CLP command in the DB2Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Set_Admin_Server_ID

DescriptionEstablishes or modifies the user account associated with the DB2 AdministrationServer instance.




User AccountSpecifies the user account used.

PasswordSpecifies the password for the User account.


-t ECC_Set_Admin_Server_ID-l DB2ManagerDatabaseTasks-h <hostname>-a <user>-a <password>

where:


user Specifies the user account used.


passwordSpecifies the password for the user account.


wruntask-t ECC_Set_Admin_Server_ID-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw


See alsoNone


ECC_Start_Admin_Server

DescriptionStarts the DB2 Administration Server.





-t ECC_Start_Admin_Server-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Start_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns


See alsoNone


ECC_Start_DB2

DescriptionStarts the DB2 instance and allocates resources.




ProfileSpecifies the name of the profile, which defines the DB2 environment, toexecute at each node. You can also enter NONE.

Node NumberSpecifies the number of the node that you want to start. Valid nodenumbers are from 0 to 999. If you do not specify the node number,perform a normal on the node where you issued the start command.

Start OptionSelect one of the following start options.

None Select this option to specify no start options.

Add nodeSelect this option to add a new node. You must also specify thevalues for the Host name, Logical port, and Network nameoptions if you select this option.


StandaloneSelect this option to specify that the node starts in stand-alonemode. All further options are ignored if you select this option.

RestartSelect this option to restart the database manager after a failure. Ifyou select this option, the values for the Host name, Logical port,and Network name are not required.

Host NameIf you selected the <Add node> Start option, enter the host name added tothe db2nodes.cfg file. If you selected the <Restart> Start option, enter thehost name used to override it in the node configuration file. The taskignores the value for the <None> or <Stand-alone> Start option.

Logical PortSpecifies the logical port that you want to add to the db2nodes.cfg file.Valid logical port numbers are from 0 to 999.

Network NameSpecifies the network name added to the db2nodes.cfg file or enter NONE.If you do not specify this parameter, or if you have it set to NONE, thenetwork name is the same as the value specified in Host name. If youselected the <Add node> Start option, enter the network name added to thedb2nodes.cfg file. If you selected the <Restart> Start option, enter thenetwork name to use to override the network name in the nodeconfiguration file. For the <None> or <Stand-alone> Start option, this valueis ignored.

Temporary SpaceIf you select the <Add node> Start option, enter the node number toindicate that the temporary tablespace containers are the same as thecontainers on the specified node number for each database in the instance.For the <None>, <Stand-alone>, or <Restart> Start option, this value isignored. Enter WITHOUT to specify that containers for the temporarytablespaces are not created for any of the databases.


-t ECC_Start_DB2-l DB2ManagerDatabaseTasks-h <hostname>[-a <profile>[-a <nodenum>[-a <startopt>[-a <hostname>-a <port>[-a <netname>[-a <temp>]]]]]]where:


profile An optional variable that specifies the name of the profile file, whichdefines the DB2 environment, to execute at each node. You can alsospecify NONE.


nodenumSpecifies the number of the node that you want to start. Valid nodenumbers are from 0 to 999. If you do not specify the node number,perform a normal startup on the node where you issued the startcommand.

startoptSpecifies one of the following start options.

NONESpecifies no start options.

ADDNODESpecifies to add a node. You must enter values for thesevariables:

STANDALONEIf you specify this parameter, all further arguments are ignored.

RESTARTIf you specify this parameter, the following listed variables arespecified according to the following descriptions:

hostnameSpecifies the host name to add to the db2nodes.cfg file. The taskrequires this variable.

port Specifies the logical port that you want to add to the db2nodes.cfg file.The task requires this variable. Valid logical port numbers are from 0 to999.

netnameSpecifies the network name that you want to add to the db2nodes.cfgfile or specify NONE. If you do not specify this parameter, or if you setit to NONE, the network name is the same as the value specified in<hostname>.

temp An optional variable that specifies the node number specifying that thecontainers for the temporary tablespaces are the same as the containerson the specified node number for each database in the instance. SpecifyWITHOUT if you do not want containers for the temporary tablespacesto be created for any of the databases.


wruntask-t ECC_Start_DB2-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a profile1-a 6-a ADDNODE-a bburns-a 662-a NONE-a WITHOUT

Usage notesYou can only run the following arguments on DB2 Enterprise-Extended Edition.


When you run this task on DB2 Enterprise-Extended Edition in a multi-nodeenvironment, it affects all nodes that are listed in the $HOME/sqllib/db2notes.cfgfile unless you specify the <nodenum> variable.

After this task starts, the database manager instance runs until you stop it, even ifall programs that were using it have ended.

For more information when you are running UNIX, see the db2start systemcommand in the DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Start_DB2_NT_Security

DescriptionStarts the DB2 security service on a Windows system.


Target endpointDB2DatabaseManager, DB2InstanceManager, and Endpoints



-t ECC_Start_DB2_NT_Security-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Start_DB2_NT_Security-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesIf you used the “ECC_Stop_DB2_NT_Security” on page 354 task to stop the DB2security service, additional dependent NT services, such as Data Warehouseservices, does not stop. The “ECC_Start_DB2_NT_Security” does not restartdependent services; you must start them manually.

See alsoNone


ECC_Stop_Admin_Server

DescriptionStops the DB2 Administration Server.





-t ECC_Stop_DB2_Admin_Server-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Stop_DB2_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns


See alsoNone


ECC_Stop_DB2

DescriptionStops the DB2 instance and releases resources.




Stop DB2 ProfileAn optional variable that specifies the name of the profile that youexecuted during startup, which defined the DB2 environment for the nodesthat were started.

Type Select one of the following stop options:

None Specifies no stop options.

Node Stops the node specified in the Node Number argument. If youspecify this parameter, you must specify a node in the NodeNumber argument.

Drop Drops the node specified in the Node Number argument and stopsall nodes. If you specify this parameter, you must specify a node inthe Node Number argument.

Force If you specify this parameter, all further arguments are ignored.This parameter specifies that ALL is used when stopping thedatabase manager at each node.

Node numberSpecifies the number of the node that you want to stop. Valid nodenumbers are from 0 to 999.



-t ECC_Stop_DB2-l DB2ManagerDatabaseTasks-h <hostname>[-a <profile>[-a <type>[-a <nodenum>]]]where:


profile An optional variable that specifies the name of the profile that youexecuted during startup, which defined the DB2 environment for thenodes that were started.

type Specifies one of the following stop options:

NONESpecifies no stop options.

NODEStops the node specified in the <nodenum> argument. If youspecify this parameter, you must specify a node in the<nodenum> argument.

DROP Drops the node specified in the <nodenum> argument and stopsall nodes. If you specify this parameter, you must specify a nodeto drop in the <nodenum> argument.

FORCEIf you specify this parameter, all further arguments are ignored.This parameter specifies that ALL is used when stopping thedatabase manager at each node.

nodenumSpecifies the number of the node that you want to stop. Valid nodenumbers are from 0 to 999.


wruntask-t ECC_Stop_DB-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a profile1-a NODE-a 67

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition in a multi-nodeenvironment, it affects all nodes that are listed in the $HOME/sqllib/db2notes.cfgfile, unless you specified the NODE parameter for the <type> variable.


This task does not stop DB2 if any applications are connected to databases. If thereare no database connections, but there are instance attachments, ECC_Stop_DB2forces the instance attachments and stops DB2.

You can run ECC_Stop_DB2 on a DB2 server or on other managed nodes. AfterDB2 stops, the standard output device receives a successful completion message. Ifan error occurs, processing stops, and the standard output device receives an errormessage.

For more information when you are running UNIX, see the db2stop systemcommand in the DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Stop_DB2_NT_Security

DescriptionStops the DB2 security service on a Windows system.


Target endpointDB2DatabaseManager, DB2InstanceManager, and Endpoints



-t ECC_Stop_DB2_NT_Security-l DB2ManagerDatabaseTasks-h <hostname>

where:



wruntask-t ECC_Stop_DB2_NT_Security-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns

Usage notesThis task also stops any dependent services on the DB2 security service. At thetime of this writing (DB2 Version 7.1), only the DB2 Data Warehouse service (anoptionally installed feature) is dependent.

See alsoNone


ECC_Update_Admin_Configuration

DescriptionModifies individual entries in the database manager configuration file that arerelevant to the DB2 Administration Server.




Keyword 1Click the Parameter button and select the name of the database managerconfiguration parameter that you want to update. You can select or specifyfrom one to five keyword-value pairs.

Value 1Specifies the new value for the configuration parameter specified in thecorresponding key.



-t ECC_Update_Admin_Configuration-l DB2ManagerDatabaseTasks-h <hostname>-a <key01 val01>[-a <key02 val02>...-a <key05 val05>]

where:


key Specify the name of the database manager configuration parameter thatyou want to update. You can select or specify from one to fivekeyword-value pairs.

val Specifies the new value for the configuration parameter specified in thecorresponding key.


wruntask-t ECC_Update_Admin_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a MAXAGENTS 300-a MAXCAGENTS 250

Usage notesNone

See alsoNone


ECC_Update_Database_Configuration

DescriptionModifies individual entries in a specific database configuration file.




Keyword 1Click the Parameter button to select the name of the database configurationparameter you want to update. You can specify from one to fivekeyword-value pairs.

Value 1Specifies the new value for the configuration parameter specified in thecorresponding key.

User IDSpecifies the name of the user to attach to a remote partition. If you runthis task with DB2 Enterprise-Extended Edition on a partition groupendpoint and at least one of the partitions in the partition group resides on


a remote host, you must specify a user name. All nodes included in thepartition group, whether they are on a local or remote host, use the username.



-t ECC_Update_Database_Configuration-l DB2ManagerDatabaseTasks-h <hostname>-a <key01 val01>[-a <key02 val02>...-a <key05 val05>[-a <username>-a <password>]]

where:


key Specifies the name of the database configuration parameter you want toupdate. You can specify from one to five keyword-value pairs.





wruntask-t ECC_Update_Database_Configuration-l DB2ManagerDatabaseTasks-h @DB2DatabaseManager:db2mgr1@bburns-a APPLHEAPSZ 256-a DBHEAP 1500-a PCKCACHESZ 129-a CATALOGCACHE_SZ 256-a joe-a joepw

Usage notesWhen you run this task on DB2 Enterprise-Extended Edition, it affects only thenode on which the task executes.


Changes to the database configuration file become effective only after they areloaded into memory. All applications must disconnect from the database beforechanges are loaded. If an error occurs, the database configuration file does notchange.

An invalid checksum prevents you from updating the database configuration file.If this problem occurs, you must restore the database to reset the databaseconfiguration file.

For more information, see the UPDATE DATABASE CONFIGURATION CLPcommand in the DB2 Command Reference for the version of DB2 that you are using.

See alsoNone


ECC_Update_Database_Manager_Configuration

DescriptionModifies individual entries in the database manager configuration file.




Config-keyword 1Specifies the name of the database manager configuration parameter youwant to update. You can specify from one to five keyword-value pairs.

Config-value 1Specifies the new value for the configuration parameter specified in thecorresponding key.


-t ECC_Update_Database_Manager_Configuration-l DB2ManagerDatabaseTasks


-h <hostname>-a <key01 val01>[-a <key02 val02>...-a <key05 val05>]

where:


key Specifies the name of the database manager configuration parameter youwant to update. You can specify from one to five keyword-value pairs.



wruntask-t ECC_Update_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a maxagents 300-a maxcagents 250

Usage notesChanges to the database manager configuration file become effective only afterthey are loaded into memory. For a server configuration, parameter changes areloaded into memory when ECC_Start_DB2 runs. For a client configurationparameter, parameter changes are loaded into memory when you restart theapplication. If an error occurs, the database manager configuration file does notchange.

An invalid checksum prevents you from updating the database managerconfiguration file. If this error occurs, you must reinstall the database manager toreset the database manager configuration file.

For more information, see the UPDATE DATABASE MANAGERCONFIGURATION CLP command in the DB2 Command Reference for the versionof DB2 that you are using.

See alsoDB2ManagerDatabase tasks: “ECC_Start_DB2” on page 345



Chapter 6. Data replication tasks

The DB2ManagerReplicationTasks library contains tasks that are used with DB2Replication.

For more information about data replication tasks, see the DB2 Replication Guideand Reference.

Table 5 briefly describes each task in the DB2ManagerReplicationTasks tasklibrary. When you view this table online, you can click the task name to go to afull description of that task.

Table 5. DB2ManagerReplicationTasks

Task Description

ECC_Apply_Start Starts the data replication Apply program

ECC_Apply_Stop Stops the data replication Apply program

ECC_Capture_Get_Log_Seq Retrieves the current log sequence number andtime stamp

ECC_Capture_Prune Prunes the data replication Capture program

ECC_Capture_Reinit Reinitializes the data replication Captureprogram

ECC_Capture_Resume Resumes the data replication Capture program

ECC_Capture_Start Starts the data replication Capture program

ECC_Capture_Stop Stops the data replication Capture program

ECC_Capture_Suspend Suspends the data replication Capture program

363

ECC_Apply_Start

DescriptionRefreshes or updates a target table.


Target endpointDB2DatabaseManager


User IDSpecifies the user ID for starting the Apply program.

PasswordFor Windows only: Specifies the password to authenticate the User ID.

PathnameSpecifies the full path where you want the Apply program to write files.

QualifierIf this task runs on DB2 Enterprise-Extended Edition, it specifies the Applyqualifier that the Apply instance uses to identify the subscriptions served.Otherwise, specify NONE.

ServerNameIf this task runs on DB2 Enterprise-Extended Edition, it specifies the nameof the server where the replication control tables will reside. Otherwisespecify NONE.


-t wruntask ECC_Apply_Start-l DB2ManagerReplicationTasks


-h <hostname>-a <userid>-a <password>-a "<path>"-a <qualifier>-a <server>-a <asnload>-a <priority>


userid Specifies the user ID for starting the Apply program.

passwordSpecifies the password for <username>:

NONEFor AIX only: Specifies that you do not want to supply apassword.

passwordFor NT only: Specifies the password to authenticate the user IDentered for <userid>.

"path" Specifies the full path to which you want the Apply program to writefiles. You must specify the quotation marks around the name.

qualifierIf you are running this task on DB2 Enterprise-Extended Edition, specifythe Apply qualifier that the Apply instance uses to identify thesubscriptions served. Otherwise, specify NONE.

server If you are running this task on DB2 Enterprise-Extended Edition, specifythe name of the server where the replication control tables will reside, orspecify NONE. Otherwise, specify NONE.

asnloadSpecifies YES or NO to indicate whether to call the ASNLOAD user-exitroutine. ASNLOAD calls an IBM or vendor utility to initialize apoint-in-time table.

priorityFor DB2 for UDB only: Specifies the processing order of subscriptions:

R Specifies round-robin processing of subscriptions by LASTRUN,PRIORITY for this instance of the Apply program.

L Specifies processing of subscriptions by PRIORITY, LASTRUNfor this instance of the Apply program.

OTHERSpecifies that the Apply program selects the next subscription inthe order of PRIORITY, COPY_OWNER, and COPY_TABLE.


wruntask-t ECC_Apply_Start-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns

Chapter 6. Data replication tasks 365

-a joe-a joepw-a "D:\applydir"-a NONE-a NONE

Usage notesAfter you run ECC_Apply_Start, the Apply program runs continuously until anyof the following occurs:v You stop the Apply program with the ECC_Apply_Stop task.v An unexpected error or failure occurs.v The ENABLE field of the global control record in any refresh control table

indicates that the Apply program stops.v The Apply program returns a message (only if it fails within 60 seconds).

You must start the Apply program with an Apply ID. ECC_Apply_Start uses theroot ID and prompts you for an Apply ID. Windows requires a password.

See alsoDB2ManagerReplication tasks: “ECC_Apply_Stop” on page 367


ECC_Apply_Stop

DescriptionStops the Apply program.




User IDSpecifies the user ID for starting the Apply program. You must use thesame ID used to start the Apply program.

PathnameSpecifies the full path where you want the Apply program to write files.

QualifierIf you are running this task on DB2 Enterprise-Extended Edition, itspecifies the Apply qualifier that the Apply instance uses to identify thesubscriptions served. Otherwise specify NONE.


-t ECC_Apply_Stop-l DB2ManagerReplicationTasks-h <hostname>-a <userid>-a "<path>"[-a <qualifier>]where:



userid Specifies the user ID for stopping the Apply program. You must use thesame ID that you use to start the Apply program.

pathnameSpecifies the full path where you want the Apply program to write files.

qualifierIf you are running this task on DB2 Enterprise-Extended Edition, specifythe Apply qualifier that the Apply instance uses to identify thesubscriptions served. Otherwise, specify NONE.


wruntask-t ECC_Apply_Stop-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a joe-a "D:\applydir"-a NONE

Usage notesWhen this task runs with DB2 Enterprise-Extended Edition, it can run on the AIXand Windows platforms. When this task runs with DB2 Enterprise-ExtendedEdition, it affects all nodes in the node group.

See alsoNone


ECC_Capture_Get_Log_Seq

DescriptionRetrieves the current log sequence number and time stamp.




PathnameSpecifies the full path to which you want the Capture program to writefiles. For AIX, the ID used by this task must have write permissions for thedirectory specified.


-t ECC_Capture_Get_Log_Seq-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"where:


"path" Specifies the full path to which you want the Capture program to writefiles. For AIX, the ID used by this task must have write permissions forthe directory specified. You must specify the quotation marks around thename.



wruntask-t ECC_Capture_Get_Log_Seq-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "D:\applydir"

Usage notesThe information retrieved by this task helps determine how far the Captureprogram has read the DB2 log.

See alsoNone


ECC_Capture_Prune

DescriptionPrunes the data replication capture tables if you specified the NOPRUNEargument when you started the Capture program.






-t ECC_Capture_Prune-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"


"path" Specifies the full path to which you want the Capture program to writefiles. You must specify the quotation marks around the name.



wruntask-t ECC_Capture_Prune-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "D:\applydir"

Usage notesIf you disable pruning by using the NOPRUNE argument while starting theCapture program, this command prunes the data replication capture tables onetime.

See alsoNone


ECC_Capture_Reinit

DescriptionCauses the Capture program to reread tables while it runs so that it recognizesnew registrations (for DPROPR) and new source table definitions (for DB2 UDBand DB2 Enterprise-Extended Edition).




PathnameSpecifies the full path where you want the Capture program to write files.For AIX, the ID used by this task must have write permissions for thedirectory specified.


-t ECC_Capture_Reinit-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"where:





wruntask-t ECC_Capture_Reinit-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "D:\applydir"

Usage notesThis command also rereads the tuning parameters table for any changes made tothe tuning parameters.

For DPROPR, do not use ECC_Capture_Reinit to reinitialize the Capture programafter cancelling a registration or dropping a registered table while Capture runs.For DB2 UDB and DB2 Enterprise-Extended Edition, do not useECC_Capture_Reinit to reinitialize the Capture program after cancelling areplication source or dropping a replication source table while Capture runs. Ineither situation, use the ECC_Capture_Stop task to stop the Capture program andthen use the ECC_Capture_Start task with the WARM parameter to restart theCapture program.

See alsoDB2ManagerReplication tasks: “ECC_Capture_Stop” on page 379,“ECC_Capture_Start” on page 377


ECC_Capture_Resume

DescriptionRestarts a suspended Capture program.






-t ECC_Capture_Resume-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"





wruntask-t ECC_Capture_Resume-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "D:\applydir"

Usage notesIf you are pruning a file with ECC_Capture_Prune and you runECC_Capture_Stop or ECC_Capture_Suspend, pruning does not resume after yourun ECC_Capture_Resume. You must run ECC_Capture_Prune again.

See alsoDB2ManagerReplication tasks: “ECC_Capture_Prune” on page 371,“ECC_Capture_Stop” on page 379, and “ECC_Capture_Suspend” on page 381


ECC_Capture_Start

DescriptionStarts the Capture program, which reads database log or journal records to capturedata about changes made to source tables.





Type Specifies where the Capture program starts processing:

WARMSpecifies that the Capture program starts processing where itended in its previous run if warm start information is available.Otherwise, the Capture program switches to a cold start.

WARMNSSpecifies that the Capture program starts processing where itended in its previous run if warm start information is available.Otherwise, the Capture program issues a message and ends.

COLD Specifies that the Capture program starts processing by deleting allrows in its change data table, unit-of-work table, pruning controltable, and trace table during initialization.

Prune?Select YES or NO to indicate if the Capture program automatically prunesthe change data and unit-of-work tables.



-t ECC_Capture_Start-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"-a <type>-a <prune>where:



type Specifies where the Capture program starts processing:

WARMSpecifies that the Capture program starts processing where itended in its previous run if warm start information is available.Otherwise, the Capture program switches to a cold start.

WARMNSSpecifies that the Capture program starts processing where itended in its previous run if warm start information is available.Otherwise, the Capture program issues a message and ends.

COLD Specifies that the Capture program starts processing by deletingall rows in its change data table, unit-of-work table, pruningcontrol table, and trace table during initialization.

prune Specifies YES or NO to indicate whether the Capture programautomatically prunes the change data and unit-of-work tables.


wruntask-t ECC_Capture_Start-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "/w/joe/captdir"-a WARM-a NO

Usage notesThe Capture program runs continuously until you stop it or it detects an error.

See alsoNone


ECC_Capture_Stop

DescriptionStops the data replication Capture program in an orderly manner and commits thelog records that it processed up to that point.






-t ECC_Capture_Stop-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"





wruntask-t ECC_Capture_Stop-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "D:\applydir"

Usage notesIf you are pruning a file with ECC_Capture_Prune and you runECC_Capture_Stop or ECC_Capture_Suspend, pruning does not resume after yourun ECC_Capture_Resume. You must run ECC_Capture_Prune again.

See alsoDB2ManagerReplication tasks: “ECC_Capture_Prune” on page 371,“ECC_Capture_Suspend” on page 381, and “ECC_Capture_Resume” on page 375


ECC_Capture_Suspend

DescriptionRelinquishes resources to operational transactions during peak periods withoutdamaging the Capture environment.






-t ECC_Capture_Suspend-l DB2ManagerReplicationTasks-h <hostname>-a "<path>"where:





wruntask-t ECC_Capture_Suspend-l DB2ManagerReplicationTasks-h @DB2DatabaseManager:db2mgr1@bburns-a "D:\applydir"

Usage notesThis task suspends the Capture program until you run ECC_Capture_Resume.

If you are pruning a file with ECC_Capture_Prune and you runECC_Capture_Stop or ECC_Capture_Suspend, pruning does not resume after yourun ECC_Capture_Resume. You must run ECC_Capture_Prune again.

See alsoDB2ManagerReplication tasks: “ECC_Capture_Resume” on page 375,“ECC_Capture_Prune” on page 371, and “ECC_Capture_Stop” on page 379


Appendix A. Monitor to resource model migration table

The following table compares Tivoli Manager for DB2, Version 2.1.0 monitors toIBM Tivoli Monitoring for Databases, Version 5.1.0: DB2 resource models and CIMclasses. If a monitor does not map to a resource model, the resource model ismarked as None. You can use the CIM class to create a custom resource model fora data point that you monitored using Tivoli Manager for DB2. See Appendix B,“Creating custom resource models using CIM classes” on page 399 for details oncreating custom resource models.

If a monitor’s capabilities have been removed form the product, the resourcemodel is marked as Withdrawn.

Table 6. Monitors for DB2 and the corresponding resource models in IBM Tivoli Monitoringfor Databases: DB2

Tivoli Manager for DB2,Version 2.1.0, Monitor Name

IBM Tivoli Monitoring for Databases, Version 5.1.0: DB2

Resource Model CIM Class

conn: # of direct reads None DB2ApplicationDirectIO

conn: # of direct writes None DB2ApplicationDirectIO

conn: # of times agents arestolen

None DB2ApplicationAgent

conn: Application sectioninserts

DB2 SQL StatementActivity

DB2ApplicationStatement

conn: Application sectionlookups



conn: Application sorts DB2 Sorting DB2ApplicationSorts

conn: Application work load DB2 Agents DB2ApplicationAgent

conn: Average # of sectorsread per direct read

DB2 Direct IO DB2ApplicationDirectIO

conn: Average # of sectorswritten per direct write

DB2 Direct IO DB2ApplicationDirectIO

conn: Binds/precompilesattempted

None DB2ApplicationStatement

conn: Buffer pool time waitedfor prefetch (ms)

None DB2ApplicationBufferPool

conn: Commits DB2 SQL StatementActivity


conn: Data page writes None DB2ApplicationBufferPool

conn: DDL SQL statements None DB2ApplicationStatement

conn: Deadlocks found duringlast interval

DB2 Locks andDeadlocks

DB2ApplicationLocks

conn: Dynamic SQLstatements

None DB2ApplicationStatement

conn: Explicit rollbacks DB2 SQL StatementActivity


conn: Failed SQL statements None DB2ApplicationStatement

conn: Index page reads None DB2ApplicationBufferPool

383

Table 6. Monitors for DB2 and the corresponding resource models in IBM Tivoli Monitoringfor Databases: DB2 (continued)

conn: Index page writes None DB2ApplicationBufferPool

conn: Lock escalations duringlast interval


DB2ApplicationBufferPool

conn: Lock wait time (s) DB2 Lock Waits DB2ApplicationLocks

conn: Lock waits None DB2ApplicationLocks

conn: Locks held None DB2ApplicationLocks

conn: Logical data reads None DB2ApplicationBufferPool

conn: Maximum associatedagents

None DB2ApplicationAgent

conn: Open block cursors DB2 SQL CursorActivity


conn: Open cursors DB2 SQL CursorActivity


conn: Percent buffer pool hitratio, data+index

DB2 Buffer Pools DB2ApplicationBufferPool

conn: Percent buffer pool hitratio, index

DB2 Buffer Pools DB2ApplicationBufferPool

conn: Percent DDL SQL DB2 SQL StatementActivity


conn: Percent locklist spaceused by application


DB2ApplicationLocks

conn: Percent package cachehit ratio

DB2 Package Cache DB2ApplicationPackageCache

conn: Percent UID SQL DB2 SQL StatementActivity


conn: Pool read time (s) None DB2ApplicationBufferPool

conn: Pool write time (s) None DB2ApplicationBufferPool

conn: Rollbacks DB2 SQL StatementActivity


conn: Rows deleted None DB2ApplicationStatement

conn: Rows inserted None DB2ApplicationStatement

conn: Rows selected None DB2ApplicationStatement

conn: Rows updated None DB2ApplicationStatement

conn: Select SQL statements DB2 SQL StatementActivity


conn: Sort time (s) DB2 Sorting DB2ApplicationSorts

conn: Statement sorts None DB2ApplicationSorts

conn: Static SQL statements DB2 SQL StatementActivity


conn: Total pool I/O time (s) None DB2ApplicationBufferPool

conn: Total system CPU timeused by agents

DB2 CPU Utilization DB2ApplicationAgent

conn: Total user CPU timeused by agents

DB2 CPU Utilization DB2ApplicationAgent

conn: UOW lock wait time (s) None DB2ApplicationLocks



conn: Update/Insert/DeleteSQL



db: # of applications connectedcurrently

DB2 Database Activity DB2DatabaseApplicationActivityDB2PartitionApplicationActivity

db: # of applications executing DB2 Database Activity DB2DatabaseApplicationActivityDB2PartitionApplicationActivity

db: # of binds/precompsattempted

None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of catalog cache heapfull

None DB2DatabaseCatalogCacheDB2PartitionCatalogCache

db: # of catalog cache inserts None DB2DatabaseCatalogCacheDB2PartitionCatalogCache

db: # of catalog cache lookups None DB2DatabaseCatalogCacheDB2PartitionCatalogCache

db: # of catalog cacheoverflows

None DB2DatabaseCatalogCacheDB2PartitionCatalogCache

db:# of commit statementsattempted


db: # of connects since 1st dbconnect

None DB2DatabaseApplicationActivityDB2PartitionApplicationActivity

db: # of database files closed None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of database tablespaces None DB2DatabaseContentDB2PartitionContent

db: # of deadlocks detected None DB2DatabaseLocksDB2PartitionLocks

db: # of direct read requests None DB2DatabaseDirectIODB2PartitionDirectIO

db: # of direct reads fromdatabase

None DB2DatabaseDirectIODB2PartitionDirectIO

db: # of direct write requests None DB2DatabaseDirectIODB2PartitionDirectIO

db: # of direct writes todatabase

None DB2DatabaseDirectIODB2PartitionDirectIO

db: # of event monitors None DB2DatabaseContentDB2PartitionContent

db: # of internal automaticrebinds


db: # of internal commits None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of internal rollbacks None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of internal rows deleted None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of internal rows updated None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

Appendix A. Monitor to resource model migration table 385


db: # of invalid triggers DB2 Database Activity DB2DatabaseContentDB2PartitionContent

db: # of lock timeouts None DB2DatabaseLocksDB2PartitionLocks

db: # of log pages read DB2 Logging DB2DatabaseLoggingDB2PartitionLogging

db: # of log pages written DB2 Logging DB2DatabaseLoggingDB2PartitionLogging

db: # of log space cleanersinvoked

None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of package cache inserts DB2 Package Cache DB2DatabasePackageCacheDB2PartitionPackageCache

db: # of package cachelookups

DB2 Package Cache DB2DatabasePackageCacheDB2PartitionPackageCache

db: # of page cleans in aninterval


db: # of pages for eachprefetch request


db: # of pool reads None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of pool writes None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of rollback statementsattempted


db: # of rows deleted None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of rows inserted None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of rows selected None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of rows updated None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: # of secondary logsallocated currently

DB2 Logging DB2DatabaseLoggingDB2PartitionLogging

db: # of synchronous I/O None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of synchronous indexreads


db: # of synchronous indexwrites


db: # of synchronous reads None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of synchronous writes None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: # of system tablespaces None DB2DatabaseContentDB2PartitionContent



db: # of tables None DB2DatabaseContentDB2PartitionContent

db: # of tablespaces None DB2DatabaseContentDB2PartitionContent

db: # of tablespaces withLONG data

None DB2DatabaseContentDB2PartitionContent

db: # of triggers None DB2DatabaseContentDB2PartitionContent

db: # of user indexes None DB2DatabaseContentDB2PartitionContent

db: # of victim page cleanersinvoked


db: # of views None DB2DatabaseContentDB2PartitionContent

db: Active sorts None DB2DatabaseSortsDB2PartitionSorts

db: app_ctl_heap_sz None DB2DatabaseConfigurationDB2PartitionConfiguration

db: ApplHeapSz None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Application in lock wait DB2 Lock Waits DB2DatabaseLocksDB2PartitionLocks

db: Average # of async readsper pool read

DB2 Buffer Pools DB2DatabaseBufferPoolDB2PartitionBufferPool

db: Average # of async Writesper pool read


db: Average # of pool writesper pool read


db: Average # of sectors readper direct read

DB2 Direct IO DB2DatabaseDirectIODB2PartitionDirectIO

db: Average # of sectorswritten per direct write


db: Average direct read time(ms)


db: Average direct write time(ms)


db: Average lock escalationsper connection


DB2DatabaseLocks

db: Average lock wait time (s) DB2 Lock Waits DB2DatabaseLocksDB2PartitionLocks

db: Average locks held perapplication


DB2DatabaseLocksDB2PartitionLocks

db: Average pool I/O time(ms)


db: Average pool read time(ms)




db: Average pool write time(ms)


db: Average sort time (ms) None DB2DatabaseSortsDB2PartitionSorts

db: Average synchronous dataread time (ms)


db: Average synchronous datawrite time (ms)


db: Average synchronous I/O(ms)


db: Avg # of pages for eachcleaner

None DB2DatabaseBufferPool

db: Avg lock escalations perconnection

None DB2PartitionLocks

db: Buffer pool async datareads


db: Buffer pool async datawrites


db: Buffer pool async indexreads


db: Buffer pool async indexwrites


db: Buffer pool async readtime (ms)


db: Buffer pool async writetime (ms)


db: Buffer pool data logicalreads


db: Buffer pool data pagescopied from extended storage


db: Buffer pool data pagescopied to extended storage


db: Buffer pool data physicalreads


db: Buffer pool data writes None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: Buffer pool I/Os persecond


db: Buffer pool index logicalreads


db: Buffer pool index pagescopied from extended storage


db: Buffer pool index pagescopied to extended storage


db: Buffer pool index physicalreads




db: Buffer pool index writes None DB2DatabaseBufferPoolDB2PartitionBufferPool

db: Buffer pool time waitedfor prefetch (ms)


db: buffpage None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Capture errors DB2 ReplicationCapture

DB2DatabaseReplicationDB2PartitionReplication

db: Capture lag DB2 ReplicationCapture

DB2DatabaseReplicationDB2PartitionReplication

db: Capture Pruning None DB2DatabaseReplication

db: catalogcache_sz None DB2DatabaseConfigurationDB2PartitionConfiguration

db: chngpgs_thresh None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Committed statements persecond


DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: dbheap None DB2DatabaseConfigurationDB2PartitionConfiguration

db: DDL SQL statements None DB2DatabaseSQLStatementsDB2PartitionSQLStatements

db: Deadlocks found duringlast interval



db: Direct read time (ms) None DB2DatabaseDirectIODB2PartitionDirectIO

db: Direct write time (ms) None DB2DatabaseDirectIODB2PartitionDirectIO

db: DLL SQL statements DB2 SQL StatementActivity


db: Dynamic SQL statements DB2 SQL StatementActivity


db: Extended storageread/write ratio

DB2 BufferPool/Extended Storage

DB2DatabaseBufferPoolDB2PartitionBufferPool

db: Failed SQL statements DB2 SQL StatementActivity


db: Internal rollback due todeadlock

None DB2DatabaseLocksDB2PartitionLocks

db: Last backup timestamp DB2 Database Activity DB2DatabaseStatusDB2PartitionStatus

db: Lock escalations duringlast interval



db: Lock list in use (bytes) None DB2DatabaseLocksDB2PartitionLocks

db: Lock timeouts during lastinterval



db: Lock waits None DB2DatabaseLocksDB2PartitionLocks



db: Lock waits in an interval DB2 Lock Waits DB2DatabaseLocksDB2PartitionLocks

db: locklist None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Locks held None DB2DatabaseLocksDB2PartitionLocks

db: Log I/O DB2 Logging DB2DatabaseLoggingDB2PartitionLogging

db: logbufsz None DB2DatabaseConfigurationDB2PartitionConfiguration

db: logprimary None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Max # of concurrentconnections

None DB2DatabaseApplicationActivityDB2PartitionApplicationActivity

db: Max primary log spaceused

None DB2DatabaseLoggingDB2PartitionLogging

db: Max secondary log spaceused


db: Max total log space used None DB2DatabaseLoggingDB2PartitionLogging

db: maxappls None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Maximum agentsassociated with application

None DB2DatabaseAgentDB2PartitionAgent

db: Maximum coordinatingagents

None DB2DatabaseAgentDB2PartitionAgent

db: maxlocks None DB2DatabaseConfigurationDB2PartitionConfiguration

db: mincommit None DB2DatabaseConfigurationDB2PartitionConfiguration

db: newlogpath None DB2DatabaseConfigurationDB2PartitionConfiguration

db: num_iocleaners None DB2DatabaseConfigurationDB2PartitionConfiguration

db: num_ioservers None DB2DatabaseConfigurationDB2PartitionConfiguration

db: Number of all invalidpackages

DB2 Database Activity DB2DatabaseContentDB2PartitionContent

db: number of cleaners due todirty threshold


db: Number of invalidSYSTEM packages


db: Number of invalid userpackages


db: pckcachesz None DB2DatabaseConfigurationDB2PartitionConfiguration



db: Percent application in lockwait

DB2 Lock Waits DB2DatabaseLocksDB2PartitionLocks

db: Percent buffer pool hitratio, data+index


db: Percent buffer pool hitratio, index


db: Percent catalog cache hitratio

DB2 Catalog Cache DB2DatabaseCatalogCacheDB2PartitionCatalogCache

db: Percent connections used DB2 Database Activity DB2DatabaseApplicationActivityDB2PartitionApplicationActivity

db: Percent DDL SQL DB2 SQL StatementActivity


db: Percent deadlock rollbacks DB2 Locks andDeadlocks


db: Percent failed SQL DB2 SQL StatementActivity


db: Percent internal rollbacksdue to internal deadlocks


db: Percent locklist space usedby database



db: Percent package cache hitratio

DB2 Package Cache DB2DatabasePackageCacheDB2PartitionPackageCache

db: Percent select SQL DB2 SQL StatementActivity


db: Percent sort overflowed DB2 Sorting DB2DatabaseSortsDB2PartitionSorts

db: Percent UID SQL DB2 SQL StatementActivity


db: Percent used in primarylog


db: Percent used in secondarylog


db: Primary log spaceallocated


db: restore_pending DB2 Database Activity DB2DatabaseStatusDB2PartitionStatus

db: Rollbacks per second DB2 SQL StatementActivity


db: Select SQL statements DB2 SQL StatementActivity


db: Sort heap allocated None DB2DatabaseSortsDB2PartitionSorts

db: SQL statements per second DB2 SQL StatementActivity


db: Synchronous read time(ms)




db: Synchronous write time(ms)


db: Time waited on locks None DB2DatabaseLocksDB2PartitionLocks

db: Total direct I/O time (ms) None DB2DatabaseDirectIODB2PartitionDirectIO

db: Total exclusive lockescalations


db: Total pool physical I/O(ms)


db: Total pool physical read(ms)


db: Total pool physical write(ms)


db: Total Sort Time (ms) None DB2DatabaseSortsDB2PartitionSorts

db: Total sorts DB2DatabaseSortsDB2PartitionSorts

db: Update/Insert/Delete SQL DB2 SQL StatementActivity


db: seqdetect None DB2DatabaseConfigurationDB2PartitionConfiguration

DB2 database state Withdrawn

DB2 server accumulatedconnections

Withdrawn

DB2 server currentconnections

Withdrawn

DB2 server finishedtransactions

Withdrawn

DB2 server status Withdrawn

DB2 server version Withdrawn

dbms: # of idle agents None DB2InstanceAgents

dbms: # of local connections None DB2InstanceConnections

dbms: # of local connectionsexecuting

None DB2InstanceConnections

dbms: # of local databaseswith current connections


dbms: # of piped sortsaccepted

None DB2InstanceSorts

dbms: # of piped sortsrequested


dbms: # of remote connections None DB2InstanceConnections

dbms: # of remote connectionsexecuting


dbms: # of times agents arestolen

None DB2InstanceAgents



dbms: Agent creation ratio DB2 Agents DB2InstanceAgents

dbms: agentpri None DB2InstanceConfiguration

dbms: Agents registered None DB2InstanceAgents

dbms: Agents waiting for atoken


dbms: fcm_num_anchors None DB2InstanceConfiguration

dbms: fcm_num_buffers None DB2InstanceConfiguration

dbms: fcm_num_connect None DB2InstanceConfiguration

dbms: fcm_num_rqb None DB2InstanceConfiguration

dbms: Last reset timestamp DB2 Instance Status DB2InstanceStatus

dbms: max_agents None DB2InstanceConfiguration

dbms: maxcagents None DB2InstanceConfiguration

dbms: Maximum agentsregistered


dbms: Maximum agentswaiting


dbms: Maximum idle agentsin the agent pool

None DB2InstanceConfiguration

dbms: mon_heap_sz None DB2InstanceConfiguration

dbms: num_poolagents None DB2InstanceConfiguration

dbms: Percent agents waiting DB2 Agents DB2InstanceAgents

dbms: Percent piped sort hitratio

DB2 Sorting DB2InstanceSorts

dbms: Percent piped sortsrejected


dbms: Percent private memoryused

Withdrawn

dbms: Percent sort heapallocated


dbms: Percent totalconnections executing

DB2 Instance Status DB2InstanceStatus

dbms: Post threshold sorts None DB2InstanceSorts

dbms: query_heap_sz None DB2InstanceConfiguration

dbms: rqrioblk None DB2InstanceConfiguration

dbms: sheapthres None DB2InstanceConfiguration

dbms: Sort heap allocated None DB2InstanceSorts

dbms: sqlstmtsz None DB2InstanceConfiguration

dbms: Start database managertimestamp

None DB2InstanceStatus

dbms: Total piped sortsrejected


dbp: # of FCM nodes None DB2PartitionFCMActivity



dbp: Connection status DB2 FastCommunicationManager

DB2PartitionFCMActivity

dbp: FCM buffers currentlyfree

None DB2PartitionFCMActivity

dbp: FCM connection entriescurrently free


dbp: FCM request blockscurrently free


dbp: Minimum FCM buffersfree


dbp: Minimum FCMconnection entries free


dbp: Minimum FCM messageanchors free


dbp: Minimum FCM requestblocks free


dbp: Percent FCM bufferscurrently used

DB2 FastCommunicationManager


dbp: Percent FCM connectionentries currently used



dbp: Percent maximum FCMbuffers used



dbp: Percent maximum FCMconnection entries used



dbp: Percent maximum FCMmessage anchors used



dbp: Percent maximum FCMrequest blocks used



dbp: Total buffers received None DB2PartitionFCMActivity

dbp: Total buffers sent None DB2PartitionFCMActivity

dbpg: Data redistributionstatus for a node group

None DB2PartitionGroup

dbpg: DB2 local nodes status None DB2PartitionGroup

dbpg: Partitioned databasedata redistribution status


dbpg: Percentage differentialin row distribution of a table


Maximum number of agentsallowed to register at the sametime

Withdrawn



Maximum number of agentsregistered at the same time

Withdrawn

table: # of rows DB2 Table Activity DB2TableStatus

table: Overflow accesses DB2TableActivity

table: Rows read per second DB2 Table Activity DB2TableActivity

table: Rows written per second DB2 Table Activity DB2TableActivity

tbsp: # of direct read requests None DB2TableSpaceDirectIO

tbsp: # of direct reads fromdatabase

None DB2TableSpaceDirectIO

tbsp: # of direct write requests None DB2TableSpaceDirectIO

tbsp: # of direct writes todatabase


tbsp: # of pool reads None DB2TableSpaceBufferPool

tbsp: # of pool writes None DB2TableSpaceBufferPool

tbsp: # of synchronous indexreads

None DB2TableSpaceBufferPool

tbsp: # of synchronous indexwrites


tbsp: # of synchronous reads None DB2TableSpaceBufferPool

tbsp: # of synchronous writes None DB2TableSpaceBufferPool

tbsp: Average # of sectors readper direct read

DB2 Direct IO DB2TableSpaceDirectIO

tbsp: Average # of sectorswritten per direct write


tbsp: Average direct read time(ms)


tbsp: Average direct write time(ms)


tbsp: Average pool I/O time(ms)

DB2 Buffer Pools DB2TableSpaceBufferPool

tbsp: Average pool read time(ms)


tbsp: Average pool write time(ms)


tbsp: Average synchronousdata read time (ms)


tbsp: Average synchronousdata write time (ms)


tbsp: Average synchronousI/O time (ms)


tbsp: Buffer pool async datareads


tbsp: Buffer pool async datawrites


tbsp: Buffer pool async indexreads




tbsp: Buffer pool async indexwrites


tbsp: Buffer pool async readtime (ms)


tbsp: Buffer pool async writetime (ms)


tbsp: Buffer pool data logicalreads


tbsp: Buffer pool data pagescopied from extended storage


tbsp: Buffer pool data pagescopied to extended storage


tbsp: Buffer pool data physicalreads


tbsp: Buffer pool data physicalwrites


tbsp: Buffer pool I/O persecond


tbsp: Buffer pool index logicalreads


tbsp: Buffer pool index pagescopied from extended storage


tbsp: Buffer pool index pagescopied to extended storage


tbsp: Buffer pool indexphysical reads


tbsp: Buffer pool indexphysical writes


tbsp: Direct read time None DB2TableSpaceDirectIO

tbsp: Direct write time None DB2TableSpaceDirectIO

tbsp: Extended storageread/write ratio

DB2 BufferPool/Extended Storage

DB2TableSpaceBufferPool

tbsp: File closed None DB2TableSpaceBufferPool

tbsp: Percent buffer pool hitratio, data+index


tbsp: Percent buffer pool hitratio, index


tbsp: Percent prefetch satisfied None DB2TableSpaceBufferPool

tbsp: Percent space used inDMS tablespace

DB2 Database Activity DB2TableSpaceSizeDMS

tbsp: Prefetch requests in aninterval


tbsp: Space used in SMStablespace

DB2 Database Activity DB2TableSpaceSizeSMS

tbsp: Synchronous read time(ms)




tbsp: Synchronous write time(ms)


tbsp: Tablespace status DB2 Database Activity DB2TableSpaceBufferPool

tbsp: Total direct I/O time(ms)


tbsp: Total pool physical I/Otime (ms)


tbsp: Total pool physical readtime (ms)


tbsp: Total pool physical writetime (ms)


tbsp: Total synchronous I/O None DB2TableSpaceBufferPool

Total Logical bytes read byDB2 server for all activedatabases

Withdrawn

Total logical pages read byDB2 server for all activedatabases

Withdrawn

Total physical bytes read byDB2 server

Withdrawn

Total physical bytes written byDB2 server for all activedatabases

Withdrawn

Total rows selected returnedby DB2 server for all activedatabases

Withdrawn

Total SQL statements handledby DB2 server for all activedatabases

Withdrawn

Total SQL statements receivedby DB2 server for all activedatabases

Withdrawn



Appendix B. Creating custom resource models using CIMclasses

This section briefly describes how you can use the Resource Model Wizard tocreate your own resource models using the IBM Tivoli Monitoring for Databases:DB2 CIM classes. Refer to the IBM Tivoli Monitoring Workbench documentationfor more information on how to create resource models.

Creating custom resource models using the IBM Tivoli MonitoringWorkbench

ObjectiveTo create customized resource models in the Workbench using IBM TivoliMonitoring for Databases: DB2 CIM classes and the Resource Model Wizard toguide you through the process.

Background informationThe IBM Tivoli Monitoring Workbench is a programming tool for creating,modifying, debugging, and packaging resource models for use with IBM TivoliMonitoring products. Samples of the Best Practice Resource Models have beenprovided for you to use within the IBM Tivoli Monitoring Workbench. The sampleresource models are intended to be used as working examples for creating newresource models.

The Tivoli Maintenance and Support Contract covers assistance with problemsrelating to the operation of the IBM Tivoli Monitoring Workbench, but does notcover assistance for new or modified resource models other than the ones that areincluded in the IBM Tivoli Monitoring Workbench.

The Resource Model Wizard guides you through the process of creating resourcemodels using IBM Tivoli Monitoring for Databases: DB2 CIM classes. Refer to theIBM Tivoli Monitoring Workbench documentation for more information on how tocreate resource models.

Required authorization roleNone

Before you beginBefore you begin, you must perform the following steps:1. Install and configure Windows Management Instrumentation.

Additional Information: You can download Windows ManagementInstrumentation from http://msdn.microsoft.com/downloads/.

2. Install and configure IBM Tivoli Monitoring Workbench.3. Load each IBM Tivoli Monitoring for Databases: DB2 CIM class you want to

use.Additional Information: Load the classes by running the mofcomp commandfrom the Workbench/w32–ix86 directory in the IBM Tivoli Monitoring forDatabases: DB2 installation CD. For more information about the mofcompcommand, refer to the Windows Management Instrumentation documentation.

399

http://msdn.microsoft.com/downloads/

After you finishRefer to IBM Tivoli Monitoring Workbench documentation for instructions on howto build and deploy your new resource model. Resource models created to use theIBM Tivoli Monitoring for Databases: DB2 CIM classes must be distributed to theDB2InstanceManager or the DB2DatabaseManager.

Procedure1. Open the IBM Tivoli Monitoring Workbench.2. Select File to display the File drop-down menu.3. Select New from the File drop-down menu to display the New window.4. Select Java Script Resource Model.5. Click OK to display the New Resource Model Workspace window.6. Select the Resource Model Wizard radio button.7. Click OK.8. Select the CIM/WMI data source type.9. Select all of the available operating systems on which you want the resource

model to run.10. Click Next.11. Type ROOT\CIMV2 in the Connect to namespace field.

Additional Information: ROOT\CIMV2 is the destination where the IBM TivoliMonitoring for Databases: DB2 specific CIM classes are stored.

12. Optional: Type your password.13. Click OK to display the Select a Class window.

Additional Information: The Selected Class field displays all available CIMclasses for use in your custom resource models. All IBM Tivoli Monitoring forDatabases: DB2 CIM classes begin with “DB2”.

14. Select one or more CIM classes.15. Select the CIM class properties to monitor from the Class Properties group

box.16. Click Next.17. Follow the Resource Model Wizard instructions to complete your resource

model. See the IBM Tivoli Monitoring Workbench documentation for detailedinstructions.

18. After the wizard is complete, add the CIM classes as platform-specificdependencies to the resource model by doing the following:a. Open the IBM Tivoli Monitoring Workbench dialog box containing the

decision tree for your new resource model.b. In the decision tree on the left side of the dialog box, click ″+″ to expand

the tree list for the newly created resource model.c. Click ″+″ to the left of Dependencies to expand the Dependencies tree.d. Right-click on a platform-specific dependency element to display the Add

pop-up box.e. Click Add to display the Open dialog box.f. For the Look in: field, scroll to select the IBM Tivoli Monitoring for

Databases: DB2 installation CD.g. Click one of the following directories for the operating system on which

the resource models will run:v Windows: Workbench/w32–ix86.

—OR—


v UNIX (including linux-ix86, aix4–r1, hpux10, solaris2):Workbench/UNIX.

h. Click Open to add the classes to the Dependencies folder.i. Repeat Steps 18d to 18h until all platform-specific dependencies have been

updated with the IBM Tivoli Monitoring for Databases: DB2 CIM classes.

Note: See the DB2Example.dmjsws workbench file for the complete source codeexample. The following text is an excerpt from that file:// This function is used to define the settings of the resource model.// It is called only once, when the resource model is started.// Don’t modify remarks containing tags like <<....>> ... <<\...>>// You can write additional initializing code in this function if required.

function SetDefaultConfiguration (Svc){

Svc.Trace(3, "Start SetDefaultConfiguration - DB2DirectIO");

// General info sectionSvc.SetModelName ("DB2Example");Svc.SetProfileName ("96003195");Svc.SetCycleTime (600);//<<\GENERAL_INFO>>

// Thresholds sectionSvc.DefineThreshold ("High_AvgSectorsPerDirectRead", 50.000000);Svc.DefineThreshold ("High_AvgDirectReadTime", 500.000000);Svc.DefineThreshold ("High_AvgDirectWriteTime", 500.000000);Svc.DefineThreshold ("High_AvgSectorsPerDirectWrite", 50.000000);//<<\THRESHOLDS_INFO>>

// Parameters sectionSvc.DefineStrParameter ("LoggedMetrics_DB", "numAvgDirectWriteTime,numAvgDirectReadTime,numDirectReadAvgSectorsPer,numDirectWriteAvgSectorsPer");Svc.DefineStrParameter ("LoggedMetrics_Apps", "numDirectReadAvgSectorsPer,numDirectWriteAvgSectorsPer");Svc.DefineStrParameter ("TbspNames_List", "*");Svc.DefineStrParameter ("LoggedMetrics_Tbsp", "numAvgDirectWriteTime,numAvgDirectReadTime,numDirectReadAvgSectorsPer,numDirectWriteAvgSectorsPer");Svc.DefineStrParameter ("AppNames_List", "*");//<<\PARAMETERS_INFO>>

// Dynamic model sectionSvc.DefineClass ("CIM", "ROOT\\CIMV2:DB2DirectInOut","ROOT\\CIMV2:DB2DirectInOut", "", "AvgDirectWriteTime,DirectWriteAvgSectorsPer,AvgDirectReadTime,DirectReadAvgSectorsPer","db2Node,db2Database,db2Instance", "None", "", 0, 1);Svc.DefineClass ("CIM", "ROOT\\CIMV2:DB2TablespaceDirectIO","ROOT\\CIMV2:DB2TablespaceDirectIO", "","AvgDirectWriteTime, DirectWriteAvgSectorsPer,AvgDirectReadTime,DirectReadAvgSectorsPer", "db2Node,db2Database,db2TbspName,db2Instance","None", "", 0, 1);Svc.DefineClass ("CIM", "ROOT\\CIMV2:DB2ApplicationDirectIO","ROOT\\CIMV2:DB2ApplicationDirectIO", "","DirectWriteAvgSectorsPer,DirectReadAvgSectorsPer","db2Node,db2Database,db2AppID,db2AppName,db2Instance", "None", "", 0, 1);//<<\DATA_INFO>>

// Event definition sectionSvc.DefineEvent ("DB2_High_App_AvgSectorsPerDirectWrite","UpperBound,DirectWriteAvgSectorsPer", "db2Instance,db2Database,db2Node,db2AppID,db2AppName,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_DB_AvgSectorsPerDirectWrite","UpperBound,DirectWriteAvgSectorsPer", "db2Node,db2Database,db2Instance,

Appendix B. Creating custom resource models using CIM classes 401

application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_DB_AvgDirectWriteTime","AvgDirectWriteTime,UpperBound", "db2Node,db2Database,db2Instance,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_Tbsp_AvgSectorsPerDirectRead","UpperBound,DirectReadAvgSectorsPer", "db2Instance,db2Database,db2Node,db2TbspName,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_DB_AvgDirectReadTime","AvgDirectReadTime,UpperBound", "db2Node,db2Database,db2Instance,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_Tbsp_AvgSectorsPerDirectWrite","UpperBound,DirectWriteAvgSectorsPer", "db2Instance,db2Database,db2Node,db2TbspName,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_Tbsp_AvgDirectReadTime","UpperBound,AvgDirectReadTime", "db2Instance,db2Database,db2Node,db2TbspName,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_App_AvgSectorsPerDirectRead","UpperBound,DirectReadAvgSectorsPer", "db2Instance,db2Database,db2Node,db2AppID,db2AppName,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_DB_AvgSectorsPerDirectRead","UpperBound,DirectReadAvgSectorsPer", "db2Node,db2Database,db2Instance,application_class,application_label,application_oid");Svc.DefineEvent ("DB2_High_Tbsp_AvgDirectWriteTime","UpperBound,AvgDirectWriteTime", "db2Instance,db2Database,db2Node,db2TbspName,application_class,application_label,application_oid");//<<\EVENTS_INFO>>

// Logging definition sectionSvc.DefineLogInst ("DB2Fake", "Fake", "db2Database", "","db2Database,FakeAttribute");//<<\LOGGING_INFO>>

// Place your additional intializing code below

Svc.Trace(3, "End SetDefaultConfiguration - DB2DirectIO");

return (0);

}

Classes and properties to use in resource modelsTo create resource models, you need to use providers and their commoninformation model (CIM) classes, parameters, properties, exceptions, anddependencies. A provider is the component of a resource model that delivers thestatus of the monitored object. Use the following providers to create resourcemodels for DB2 objects:v DB2Agentsv DB2ApplicationActivityv DB2ApplicationAgentv DB2ApplicationBufferPoolv DB2ApplicationDirectIOv DB2ApplicationSortsv DB2ApplicationStatementv DB2ApplLocksv DB2ApplyReplicationv DB2BufferPoolv DB2CatalogCachev DB2Configuration


v DB2Contentv DB2DatabaseReplv DB2DirectInOutv DB2GatewayConnectionsv DB2GatewayThroughputv DB2InstanceAgentsv DB2InstanceConfigurationv DB2InstanceConnectionsv DB2InstanceSortsv DB2InstanceStatusv DB2Locksv DB2Loggingv DB2PackageCachev DB2PartitionFCMActivityv DB2PartitionGroupsv DB2Sortsv DB2SQLStatementsv DB2Statusv DB2TableActivityv DB2TableContentv DB2TableReplicationv DB2TablespaceBufferPoolv DB2TablespaceContentv DB2TablespaceDirectIOv DB2TablespaceSizeDMSv DB2TablespaceSizeSMSv DB2TablespaceStatusv DB2TableStatus


DB2Agents

DescriptionThe following tables detail the CIM Class, parameters, properties, exceptions, anddependencies of this provider.

Table 7. CIM Class

CIM Name ROOT\CIMV2: DB2Agents

MOF File Name DB2Agents.mof

Description The DB2Agents class tracks DB2 agents working within theapplication.

Table 8. Properties

Property Type Description

MaxAgentsAssocWithAppls NUMERIC The maximum number of agentsassociated with all applicationsconnected to the database at onetime.

MaxCoordAgents NUMERIC The maximum number ofcoordinating agents working at onetime since the first connection wasestablished.

Table 9. Dependencies

aix4-r1 mof/unix/DB2Agents.mof

linux-ix86 mof/unix/DB2Agents.mof

solaris2 mof/unix/DB2Agents.mof

hpux10 mof/unix/DB2Agents.mof

w32-ix86 mof/w32-ix86/DB2Agents.mof


DB2ApplicationActivity


Table 10. CIM Class

CIM Name ROOT\CIMV2: DB2ApplicationActivity

MOF File Name DB2ApplicationActivity.mof

Description The DB2ApplicationActivity class keeps track of the overall activityof the applications connected to a DB2 database instance.

Table 11. Properties


AppsCurConnected NUMERIC The number of applications that arecurrently connected to the database.

AppsReqInProcess NUMERIC The number of currently connectedapplications for which the databasemanager is currently processing a request.

db2Database STRING The DB2 database name.

db2Instance STRING The DB2 instance name.

db2Node STRING The DB2 node number.

MaxCurrentConnections NUMERIC The highest number of simultaneousconnections (both local and remote) madeto a database since the first applicationconnected to the database.

PctConnectionsUsed NUMERIC The percentage of the allowed number ofconnections that are concurrentconnections.

TotalConnections NUMERIC The number of connections made to adatabase since the first databaseconnection.


aix4-r1 mof/unix/DB2ApplicationActivity.mof

linux-ix86 mof/unix/DB2ApplicationActivity.mof

solaris2 mof/unix/DB2ApplicationActivity.mof

hpux10 mof/unix/DB2ApplicationActivity.mof

w32-ix86 mof/w32-ix86/DB2ApplicationActivity.mof


DB2ApplicationAgent


Table 13. CIM Class

CIM Name ROOT\CIMV2: DB2ApplicationAgent

MOF File Name DB2ApplicationAgent.mof

Description The DB2ApplicationAgent class keeps track of the number ofapplication agents, subagents, and their activities against a DB2database instance.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2AppID.db2AppName.






db2AppID STRING The DB2 application ID.

db2AppName STRING The DB2 application name.

MaxAssociatedAgents NUMERIC The maximum number of subagentsassociated with the application.

NumStolenAgents NUMERIC The number of times that agents are stolenfrom an application.

TotSystemCpuTime NUMERIC The total system CPU time used by thisapplication’s database manager agents.System CPU time represents the time, inseconds, spent in system calls.

TotUserCpuTime NUMERIC The total user CPU time used by thisapplication’s database manager agents. UserCPU time represents time spent executingdatabase manager code.

WorkLoad NUMERIC The ratio of the maximum number ofsubagents associated with this application tothe number of agents that are stolen fromthe application by DB2 to work on adifferent application.


aix4-r1 mof/unix/DB2ApplicationAgent.mof

linux-ix86 mof/unix/DB2ApplicationAgent.mof

solaris2 mof/unix/DB2ApplicationAgent.mof

hpux10 mof/unix/DB2ApplicationAgent.mof

w32-ix86 mof/w32-ix86/DB2ApplicationAgent.mof


DB2ApplicationBufferPool


Table 16. CIM Class

CIM Name ROOT\CIMV2: DB2ApplicationBufferPool

MOF File Name DB2ApplicationBufferPool.mof

Description The DB2ApplicationBufferPool class keeps track of I/Operformance characteristics of a DB2 database instance’s bufferpool.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2AppID.db2AppName



DataLogicalReads NUMERIC The number of requests made by theapplication to read data pages using thebuffer pool.

DataPhysicalWrites NUMERIC The number of times a buffer pool data pagewas physically written to disk.


db2AppName STRING The DB2 application name.




IndexPhysicalReads NUMERIC The number of physical read requests madeby the application to get index pages into thebuffer pool.

IndexWrites NUMERIC The number of buffer pool index pageswritten to disk by the application.

PctBufferPoolHits NUMERIC The overall buffer pool hit ratio (as apercentage) for the application during themonitoring interval. This hit ratio includesboth index and data page activity.

PctIndexHits NUMERIC The application’s index page hit ratio (as apercentage) for the buffer pool during themonitoring interval.

PrefetcherWaitTime NUMERIC The time (in milliseconds) that an applicationwaited for an input and output server(prefetcher) to finish loading pages into thebuffer pool.

TotIOTime NUMERIC Uses the following expression to return thetotal time spent (in seconds) performing poolI/O operations:

connection.pool_read_time +connection.pool_write_time) / 1000

The input argument is a DB2 snapshotapplication ID, which is a unique ID acrossthe network.


Table 17. Properties (continued)


TotReadTime NUMERIC The total time (in seconds) that an applicationspent performing buffer pool input andoutput operations (reading or writing pages).

TotWriteTime NUMERIC Uses the following expression to to return thetotal time spent performing buffer pool writeI/O operation (seconds):

connection.pool_write_time / 1000

The input argument is a DB2 snapshotapplication ID, which is a unique ID acrossthe network.


aix4-r1 mof/unix/DB2ApplicationBufferPool.mof

linux-ix86 mof/unix/DB2ApplicationBufferPool.mof

solaris2 mof/unix/DB2ApplicationBufferPool.mof

hpux10 mof/unix/DB2ApplicationBufferPool.mof

w32-ix86 mof/w32-ix86/DB2ApplicationBufferPool.mof


DB2ApplicationDirectIO


Table 19. CIM Class

CIM Name ROOT\CIMV2: DB2ApplicationDirectIO

MOF File Name DB2ApplicationDirectIO.mof

Description The DB2ApplicationDirectIO class tracks I/O performancecharacteristics for all I/O on a DB2 database instance that doesnot use the buffer pool.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2AppID.db2AppName




db2AppName STRING A DB2 application name.




DirectDatabaseReads NUMERIC The number of direct reads that donot use the buffer pool.

DirectDatabaseWrites NUMERIC The number of write applicationsthat do not use the buffer pool.

DirectReadAvgSectorsPer NUMERIC The average number of sectors thatare read in a direct read by thisapplication.

DirectWriteAvgSectorsPer NUMERIC The average number of sectors thatare written in a direct write by thisapplication.


aix4-r1 mof/unix/DB2ApplicationDirectIO.mof

linux-ix86 mof/unix/DB2ApplicationDirectIO.mof

solaris2 mof/unix/DB2ApplicationDirectIO.mof

hpux10 mof/unix/DB2ApplicationDirectIO.mof

w32-ix86 mof/w32-ix86/DB2ApplicationDirectIO.mof


DB2ApplicationSorts


Table 22. CIM Class

CIM Name ROOT\CIMV2: DB2ApplicationSorts

MOF File Name DB2ApplicationSorts.mof

Description The DB2ApplicationSorts class keeps statistics on the sortsperformed by an application on a DB2 database instance.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2AppID.db2AppName








SortTime NUMERIC The sorting time (in seconds) for theapplication during the last monitoringinterval.

StatementSorts NUMERIC The total number of times that a set of datawas sorted to process the OPEN operationof the current SQL statement.

TotSorts NUMERIC The total number of sorts performed by theapplication.


aix4-r1 mof/unix/DB2ApplicationSorts.mof

linux-ix86 mof/unix/DB2ApplicationSorts.mof

solaris2 mof/unix/DB2ApplicationSorts.mof

hpux10 mof/unix/DB2ApplicationSorts.mof

w32-ix86 mof/w32-ix86/DB2ApplicationSorts.mof




Table 25. CIM Class

CIM Name ROOT\CIMV2: DB2ApplicationStatement

MOF File Name DB2ApplicationStatement.mof

Description The DB2ApplicationStatement class tracks SQL activities performedby an application on a DB2 database instance.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2AppID.db2AppName



BindsPrecompilesAttempted NUMERIC The number of binds and precompilesattempted by an application

Commits NUMERIC The total number of SQL COMMITstatements that were attempted by theapplication. This value includes SQLCOMMIT statements that are issuedfrom the application and internalcommits that are initiated by thedatabase manager for the application






DDLSqlStatements NUMERIC The total number of SQL DDLstatements that were executed by theapplication.

DynamicSQLStatements NUMERIC The total number of dynamic SQLstatements that were attempted by theapplication.

FailedSqlStatements NUMERIC The total number of failed SQLstatements for the application.

OpenBlockingCursors NUMERIC The total number of blocking cursors(local and remote) that are currentlyopen for the application.

OpenCursors NUMERIC The total number of cursors (local andremote) that are currently open for theapplication. This value also includesthe number of local and remoteblocking cursors currently open for theapplication.

PctDDLSqlStatements NUMERIC The percentage of total SQLstatements that were SQL DDLstatements executed by the applicationduring the monitoring interval.




PctUidSqlStatements NUMERIC The percentage of total SQLstatements that were SQL UPDATE,INSERT, and DELETE statementsexecuted by the application during themonitoring interval.

Rollbacks NUMERIC The total number of rollbacksattempted by the application. Thisvalue includes SQL ROLLBACKstatements that are issued from theapplication and internal rollbacks thatare initiated by the database managerfor the application.

RollbackSqlStatements NUMERIC The total number of rollbacksexplicitly attempted by theapplication. This value includes onlythe number of SQL ROLLBACKstatements issued from theapplication.

RowsDeleted NUMERIC The total number of row deletionsattempted by the application. Thisvalue includes the number of rowsdeleted from the database as a resultof internal database activity performedfor the application.

RowsInserted NUMERIC The total number of row insertsattempted by the application. Thisvalue includes the number of rowsinserted into the database as a resultof internal database activity performedfor the application.

RowsSelected NUMERIC The number of rows that wereselected and returned to theapplication.

RowsUpdated NUMERIC The total number of row updatesattempted by the application. Thisvalue includes the number of rowsupdated in the database as a result ofinternal database activity performedfor the application.

SectionInserts NUMERIC The number of inserts of SQL sectionsby an application from its SQL workarea.

SectionLookups NUMERIC The number of lookups of SQLsections by an application from itsSQL work area.

SqlReqSinceLastCommit NUMERIC The number of SQL requests that weresubmitted by the application since thelast commit.

SqlSelectsExecuted NUMERIC The number of SQL SELECTstatements that were executed by theapplication.




StaticSqlStatements NUMERIC The number of static SQL statementsthat were attempted by theapplication.

UIDSqlExecuted NUMERIC The number of SQL UPDATE,INSERT, and DELETE statements thatwere executed by the application.


aix4-r1 mof/unix/DB2ApplicationStatement.mof

linux-ix86 mof/unix/DB2ApplicationStatement.mof

solaris2 mof/unix/DB2ApplicationStatement.mof

hpux10 mof/unix/DB2ApplicationStatement.mof

w32-ix86 mof/w32-ix86/DB2ApplicationStatement.mof


DB2ApplLocks


Table 28. CIM Class

CIM Name ROOT\CIMV2: DB2ApplLocks

MOF File Name DB2ApplLocks.mof

Description The DB2ApplLocks class tracks statistics pertaining to databaselocks that an application has against a DB2 database instance.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2AppID.db2AppName



ApplDeadlocks NUMERIC The total number of deadlocks that occurredfor the application during the monitoringinterval.

AppLockWaitTime NUMERIC The total time (in seconds) that the applicationwaits for a lock to be granted to it during themonitoring interval.

CurrentLocksHeld NUMERIC The total number of locks currently held by theapplication.






LockEscalations NUMERIC The total number of lock escalations for theapplication during the monitoring interval.

LockWaits NUMERIC The total number of times that the applicationrequested a lock but had to wait becauseanother connection was already holding a lockon the data.

PctLockListUsed NUMERIC The percentage of space used in the locklist bythis application.

UOWLockWaitTime NUMERIC The total amount of elapsed time (in seconds)that the unit of work (UOW) waited for locks.


aix4-r1 mof/unix/DB2ApplLocks.mof

linux-ix86 mof/unix/DB2ApplLocks.mof

solaris2 mof/unix/DB2ApplLocks.mof

hpux10 mof/unix/DB2ApplLocks.mof

w32-ix86 mof/w32-ix86/DB2ApplLocks.mof


DB2ApplyReplication


Table 31. CIM Class

CIM Name ROOT\CIMV2: DB2ApplyReplication

MOF File Name DB2ApplyReplication.mof

Description The DB2ApplyReplication class tracks the history of the Applyprogram on a DB2 database instance.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2ApplyID



ApplyStatus NUMERIC The Apply program status.

db2ApplyID STRING The DB2 apply ID.



FailedSubscriptions NUMERIC The number of subscriptions the Applyprogram failed to replicate.

LaggingSubscriptions NUMERIC The number of lagging subscriptions for theApply program.


aix4-r1 mof/unix/DB2ApplyReplication.mof

linux-ix86 mof/unix/DB2ApplyReplication.mof

solaris2 mof/unix/DB2ApplyReplication.mof

hpux10 mof/unix/DB2ApplyReplication.mof

w32-ix86 mof/w32-ix86/DB2ApplyReplication.mof


DB2BufferPool


Table 34. CIM Class

CIM Name ROOT\CIMV2: DB2BufferPool

MOF File Name DB2BufferPool.mof

Description The DB2BufferPool class makes the next extent and equityproperties that are associated with an Oracle segment available.tracks buffer pool status and I/O statistics for an instance of a DB2database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



AsyncDataReads NUMERIC The number of data pages readasynchronously into the bufferpool for the database.

AsyncDataWrites NUMERIC The name the tablespace inwhich this segment is contained.number of times that a bufferpool data page was writtenasynchronously to disk for thedatabase.

AsyncIndexReads NUMERIC The number of index pages thatare read for the databaseasynchronously into the bufferpool by a prefetcher.

AsyncIndexWrites NUMERIC The number of times that abuffer pool index page waswritten (for the database)asynchronously to disk.

AsyncReadRequests NUMERIC The number of asynchronousread requests for the databaseduring the monitoring interval.

AsyncReadTime NUMERIC The total time (in milliseconds)that the database managerprefetchers spent reading dataor index pages into the bufferpool for the database.

AsyncWriteTime NUMERIC The total time (in milliseconds)that the database manager pagecleaners spent writing data orindex pages from the bufferpool to disk for the database.

AvgAsyncReadsPerPoolRead NUMERIC The ratio of buffer poolasynchronous data reads to thetotal number of pool reads forthe database.




AvgAsyncWritesPerPoolWrite NUMERIC The ratio of buffer poolasynchronous writes (data andindex) to the total number ofpool writes for the database.

AvgPagesPerCleaner NUMERIC The average number of pageswritten per page cleaner that areinvoked for the database duringthe monitoring interval.

AvgPoolIOTime NUMERIC The average time (inmilliseconds) for performingbuffer pool input and outputoperations (reading or writing)to the database.

AvgPoolReadTime NUMERIC The average time (inmilliseconds) for processingdatabase read requests thatcaused data or index pages tobe physically read from the diskto the buffer pool.

AvgPoolWritesPerPoolRead NUMERIC The ratio of total pool writes topool reads for the database.

AvgPoolWriteTime NUMERIC The average time (inmilliseconds) to process writerequests that have caused dataindex pages to be physicallywritten from buffer pool to disk.

AvgSyncIOTime NUMERIC The average time (inmilliseconds) to performsynchronous input and outputoperations for the database.

AvgSyncReadTime NUMERIC The average time (inmilliseconds) for synchronousdata reads to be performed forthe database.

AvgSyncWriteTime NUMERIC The average time (inmilliseconds) to performsynchronous data writes for thedatabase.




FilesClosed NUMERIC The total number of databasefiles that are closed.

IndexCopiedFromExtStorage NUMERIC The number of buffer poolindex pages copied fromextended storage for thedatabase.

IndexCopiedToExtStorage NUMERIC The number of buffer poolindex pages copied to extendedstorage for the database.




InputOutputRate NUMERIC The rate (per second) of bufferpool input and outputoperations for the database. Forthis monitoring source, bufferpool input and output includesall physical data and indexpages that go through the bufferpool when read or written.

LogSpaceCleanersInvoked NUMERIC The number of times a pagecleaner was invoked because theused logging space reached apredefined criterion for thedatabase.

LogicalDataReads NUMERIC The number of logical readrequests for data pages thatwent through the buffer pool forthe database.

LogicalIndexReads NUMERIC The number of logical readrequests applied to index pagesthat went through the bufferpool for the database.

PageCleanersDueToDirtyThreshold NUMERIC Uses the following expression toreturn the total number of pagecleaner invocations due to dirtypage thresholds:

database.pool_drty_pg_thrsh_clns

PageCleans NUMERIC The number of times a pagecleaner was invoked for thedatabase (for any reason) duringthe monitoring interval.

PagesCopiedFromExtStorage NUMERIC The number of buffer pool datapages copied from extendedstorage for the database.

PagesCopiedToExtStorage NUMERIC The number of buffer pool datapages copied to extendedstorage for the database.

PagesPerPrefetch NUMERIC The number of data pages readper prefetch request for thedatabase during the monitoringinterval.

PctBufferPoolHits NUMERIC The overall buffer pool hit ratio(as a percentage) for thedatabase during the monitoringinterval. This hit ratio includesboth index and data pageactivity.

PctExtStorageReadWrite NUMERIC The ratio (as a percentage) ofdata+index pages copied fromextended storage to pagescopied to extended storageduring the monitoring interval.




PctIndexHits NUMERIC The database’s index page hitratio (as a percentage) for thebuffer pool during themonitoring interval.

PhysicalDataReads NUMERIC The number of read requeststhat required input and outputto get data pages into the bufferpool for the database.

PhysicalDataWrites NUMERIC The number of times that abuffer pool data page wasphysically written to disk forthe database.

PhysicalIndexReads NUMERIC The number of physical readrequests to get index pages intothe buffer pool for the database.

PhysicalIndexWrites NUMERIC The number of times that abuffer pool index page wasphysically written to disk forthe database.

PreFetchWaitTime NUMERIC The time (in milliseconds)applied to all applications spentwaiting for an input and outputserver (prefetcher) to finishloading pages into the bufferpool (for the database) duringthe monitoring interval.

SyncDataReads NUMERIC The number of times physicaldata pages were readsynchronously into the bufferpool for the database.

SyncDataWrites NUMERIC The number of times that datapages were writtensynchronously from the bufferpool to disk for the database.

SyncIndexReads NUMERIC The number of physical indexpages that were readsynchronously for the database.

SyncIndexWrites NUMERIC The number of physical indexpage write requests that wereperformed synchronously forthe database.

SyncReadTime NUMERIC The time (in milliseconds)applied to synchronous readsfor the database.

SyncWriteTime NUMERIC The time (in milliseconds)applied in synchronous writesto disk for the database.




TotPhysicalIOTime NUMERIC The total time (in milliseconds)applied to physical buffer poolinput and output operations(including both synchronousand asynchronous reads andwrites) for the database.

TotPhysicalReadTime NUMERIC The total time (in milliseconds)applied to processing readrequests that caused data orindex pages to be physicallyread from disk to the bufferpool for the database.

TotPhysicalWriteTime NUMERIC The total time (in milliseconds)for buffer pool physical writes(including asynchronous writes).

TotPoolReads NUMERIC The total number of physicalread requests to get data orindex pages into the buffer poolfor the database.

TotPoolWrites NUMERIC The total number of times thatbuffer pool data or index pageswere physically written to diskfor the database.

TotSyncInputOutput NUMERIC The total number ofsynchronous reads and writesfor both data and index pages.

VictimPageCleanersInvoked NUMERIC The number of times a pagecleaner was invoked because asynchronous write was neededto make space for new pages inthe buffer pool.


aix4-r1 mof/unix/DB2BufferPool.mof

linux-ix86 mof/unix/DB2BufferPool.mof

solaris2 mof/unix/DB2BufferPool.mof

hpux10 mof/unix/DB2BufferPool.mof

w32-ix86 mof/w32-ix86/DB2BufferPool.mof


DB2CatalogCache


Table 37. CIM Class

CIM Name ROOT\CIMV2: DB2CatalogCache

MOF File Name DB2CatalogCache.mof

Description The DB2CatalogCache class tracks read/write statistics on thecatalog cache of a DB2 database instance.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



CatCacheHeapFull NUMERIC The number of times that an insert into thecatalog cache failed because of a heap-fullcondition in the database heap.

CatCacheInsertAttempts NUMERIC The number of times that the system tried toinsert table descriptor information into thecatalog cache.

CatCacheOverflows NUMERIC The number of times that an insert into thecatalog cache failed because the catalog cachewas full.

CatCacheTableLookups NUMERIC The number of times that the catalog cachewas referenced to obtain table descriptorinformation.




PctCatCacheHits NUMERIC The catalog cache hit ratio (as a percentage)for the database during the monitoringinterval.


aix4-r1 mof/unix/DB2CatalogCache.mof

linux-ix86 mof/unix/DB2CatalogCache.mof

solaris2 mof/unix/DB2CatalogCache.mof

hpux10 mof/unix/DB2CatalogCache.mof

w32-ix86 mof/w32-ix86/DB2CatalogCache.mof


DB2Configuration


Table 40. CIM Class

CIM Name ROOT\CIMV2: DB2Configuration

MOF File Name DB2Configuration.mof

Description The DB2Configuration class tracks overall configuration attributesfor an instance of a DB2 database. The attributes include, but arenot limited to: heap, buffer pool, catalog cache, pages, logging, I/Oservers and applications.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



ApplControlHeapSize NUMERIC The maximum size (in 4-KB pages) forthe application control heap in thedatabase during the monitoring interval.

ApplHeapAvailSize NUMERIC The size (in 4-KB pages) of theapplication heap that is available for eachindividual agent in the database duringthe monitoring interval.

BufferPoolDefaultSize NUMERIC The name of the index. value (in pages)of the default buffer pool size.

CatalogCacheSize NUMERIC The value (in units of 4-KB pages) of thecatalog cache size.

ChangedPagesThreshold NUMERIC The value (in percentage units) of thechanged pages threshold.




InputOutputCleaners NUMERIC The current value of the number ofasynchronous page cleaners.

InputOutputServers NUMERIC The current value of the number of inputand output servers.

LogBufferSize NUMERIC The value (in units of 4-KB pages) of thelog buffer size.

MaxActiveApplications NUMERIC The value of the maximum number ofactive applications.

MaxLocklistStorage NUMERIC The value (in units of 4-KB pages) of thedatabase heap.

MaxPctLocklist NUMERIC The value of the maximum percentage oflock list before escalation.

MinCommits NUMERIC The value of the number of commits togroup.

NewLogPath NUMERIC The current value of the db: newlogpathconfiguration parameter.




NumPrimaryLogs NUMERIC The value of the number of primary logfiles.

PackageCacheSize NUMERIC The current value (in units of 4-KBpages) of the package cache size.

RestorePending NUMERIC The RESTORE PENDING status in thedatabase during the last monitoringinterval.

SequentialDetection NUMERIC The current value of the sequentialdetection flag.


aix4-r1 mof/unix/DB2Configuration.mof

linux-ix86 mof/unix/DB2Configuration.mof

solaris2 mof/unix/DB2Configuration.mof

hpux10 mof/unix/DB2Configuration.mof

w32-ix86 mof/w32-ix86/DB2Configuration.mof


DB2Content


Table 43. CIM Class

CIM Name ROOT\CIMV2: DB2Content

MOF File Name DB2Content.mof

Description The DB2Content class tracks many statistics on an instance of aDB2 database pertaining to its content. These statistics include, butare not limited to: tables, tablespaces, triggers, views, andpackages.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.






NumDMSTablespaces NUMERIC The number of Database ManagedSpace (DMS) tablespaces in thedatabase.

NumEventMonitors NUMERIC The number of event monitorsdefined in the database.

NumInvalidPkgsALL NUMERIC The number of ALL packages that arecurrently marked invalid in thedatabase.

NumInvalidPkgsSYSTEM NUMERIC The number of SYSTEM packagesthat are currently marked invalid inthe database.

NumInvalidPkgsUSER NUMERIC The number of packages owned by aUSER that are currently markedinvalid in the database.

NumInvalidTriggers NUMERIC The number of triggers that aremarked invalid in the database.

NumSMSTablespaces NUMERIC The number of SMS tablespaces inthe database.

NumTables NUMERIC The number of tables in the database

NumTablespaces NUMERIC The number of tablespaces in thedatabase.

NumTablespacesWithLONG NUMERIC The number of tablespaces that storeLONG data in the database.

NumTriggers NUMERIC The number of triggers defined in thedatabase.

NumUserIndexes NUMERIC The number of indexes created byusers in the database. Indexes createdby SYSIBM are not counted.

NumViews NUMERIC The number of view in the database.



aix4-r1 mof/unix/DB2Content.mof

linux-ix86 mof/unix/DB2Content.mof

solaris2 mof/unix/DB2Content.mof

hpux10 mof/unix/DB2Content.mof

w32-ix86 mof/w32-ix86/DB2Content.mof


DB2DatabaseRepl


Table 46. CIM Class

CIM Name ROOT\CIMV2: DB2DatabaseRepl

MOF File Name DB2DatabaseRepl.mof

Description The DB2DatabaseRepl class tracks statistics on database replicationsuccess and frequency.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.



CaptureErrors NUMERIC The number of errors encountered by the Captureprogram within the last five minutes.

CaptureLag NUMERIC The time difference (in minutes) between thecurrent timestamp and the last timestamp recordedby the Capture program. This time difference is theCapture lag.

CapturePruning NUMERIC The number of rows in the unit-of-work (UOW)table.




aix4-r1 mof/unix/DB2DatabaseRepl.mof

linux-ix86 mof/unix/DB2DatabaseRepl.mof

solaris2 mof/unix/DB2DatabaseRepl.mof

hpux10 mof/unix/DB2DatabaseRepl.mof

w32-ix86 mof/w32-ix86/DB2DatabaseRepl.mof


DB2DirectInOut


Table 49. CIM Class

CIM Name ROOT\CIMV2: DB2DirectInOut

MOF File Name DB2DirectInOut.mof

Description The DB2DirectInOut class tracks statistics on non-buffered readsand writes for an instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



AvgDirectReadTime NUMERIC The average time (in milliseconds) thatis used to perform direct reads to thedatabase.

AvgDirectWriteTime NUMERIC The average time (in milliseconds) thatis used to perform direct writes to thedatabase.




DirectReadAvgSectorsPer NUMERIC The average number of sectors that areread by a direct read for the database.

DirectReadRequests NUMERIC The number of requests to perform adirect read from disk of one or moresectors of data for the database.

DirectReadTime NUMERIC The time (in milliseconds) forperforming the direct reads for thedatabase.

DirectReads NUMERIC The number of read operations for thedatabase that do not use the buffer pool

DirectWriteAvgSectorsPer NUMERIC The average number of sectors that arewritten by a direct write to the database.

DirectWriteRequests NUMERIC The number of requests to perform adirect write of one or more sectors ofdata for the database.

DirectWrites NUMERIC The number of write operations for thedatabase that do not use the buffer pool.

TotDirectIOTime NUMERIC The total time (in milliseconds) appliedto direct reads and writes for thedatabase.


aix4-r1 mof/unix/DB2DirectInOut.mof

linux-ix86 mof/unix/DB2DirectInOut.mof

solaris2 mof/unix/DB2DirectInOut.mof


Table 51. Dependencies (continued)

hpux10 mof/unix/DB2DirectInOut.mof

w32-ix86 mof/w32-ix86/DB2DirectInOut.mof


DB2GatewayConnections


Table 52. CIM Class

CIM Name ROOT\CIMV2: DB2GatewayConnections

MOF File Name DB2GatewayConnections.mof

Description The DB2GatewayConnections class tracks connection statisticspertaining to an instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.



AttemptedConnections NUMERIC The number of connectionsattempted from the DB2Connect gateway since the lastdb2start command or the lastreset.

ConnWaitingForClientCurrent NUMERIC The number of connections tohost databases being handled bythe DB2 Connect gateway thatare waiting for the client to senda request.

ConnWaitingForHostCurrent NUMERIC The number of connections tohost database being handled bythe DB2 Connect gateway thatare waiting for reply from thehost.

ConnectionErrors NUMERIC The number of times that acommunication error occurredwhile a DCS application wasattempting to connect to a hostdatabase, or while it wasprocessing an SQL statement.

CurrentConnections NUMERIC The current number ofconnections to host databasesbeing handled by the DB2Connect gateway.



MostRecentConnectElapsedTime NUMERIC The elapsed time that the DCSapplication that most recentlydisconnected from this hostdatabase was connected.

MostRecentConnectResponseTime NUMERIC The elapsed time between thestart of connection processingand actual establishment of aconnection for the most recentDCS application that connectedto this database.




StatementElapsedTime NUMERIC The sum of the elapsed time forall the statements that wereexecuted for the host database.


aix4-r1 mof/unix/DB2GatewayConnections.mof

linux-ix86 mof/unix/DB2GatewayConnections.mof

solaris2 mof/unix/DB2GatewayConnections.mof

hpux10 mof/unix/DB2GatewayConnections.mof

w32-ix86 mof/w32-ix86/DB2GatewayConnections.mof


DB2GatewayThroughput


Table 55. CIM Class

CIM Name ROOT\CIMV2: DB2GatewayThroughput

MOF File Name DB2GatewayThroughput.mof

Description The DB2GatewayThroughput class tracks DB2 Connect gatewaystatistics pertaining to an instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.





HostThroughput NUMERIC The number of bytes sent plus thenumber of bytes received divided bythe cumulative host response time.

HostTimePerStatement NUMERIC The host response time or number ofstatements attempted.

NetworkTimePerStatement NUMERIC Uses the following expression to returnthe total amount of network time usedper statement:

(Host response time - statementexecution time)/number ofstatements attempted

OutboundBytesReceived NUMERIC The number of bytes received by theDB2 Connect gateway from the host,excluding communication protocoloverhead.

OutboundBytesSent NUMERIC The number of bytes sent by the DB2Connect gateway to the host, excludingcommunication protocol overhead.

SQLStatementsAttempted NUMERIC The number of SQL statements thathave been attempted since databasestartup or last reset.

TimePerStatement NUMERIC The statement execution elapsed timeor number of statements attempted.


aix4-r1 mof/unix/DB2GatewayThroughput.mof

linux-ix86 mof/unix/DB2GatewayThroughput.mof

solaris2 mof/unix/DB2GatewayThroughput.mof

hpux10 mof/unix/DB2GatewayThroughput.mof

w32-ix86 mof/w32-ix86/DB2GatewayThroughput.mof


DB2InstanceAgents


Table 58. CIM Class

CIM Name ROOT\CIMV2: DB2InstanceAgents

MOF File Name DB2InstanceAgents.mof

Description The DB2InstanceAgents class tracks statistics pertaining to adatabase manager instance.Note: The Resource Instance Key (OID) is: db2Instance.



AgentCreationRatio NUMERIC The number of times that agents are createdwhen there are no more free agentsavailable in the agent pools within thedatabase manager. The value is defined asthe ratio of the number of agents createdfrom pool/number of agents assigned frompool.

CurAgentsWaiting NUMERIC The number of agents that are waiting for atoken so that they can execute a transactionin the database manager.

db2InstanceName STRING The DB2 instance name.

MaxAgentsRegistered NUMERIC The highest number of agents that thedatabase manager has registered since theDB2 instance started.

MaxAgentsWaiting NUMERIC The highest number of agents that havewaited for a token at the same time sincethe database manager started.

NumAgentsRegistered NUMERIC The number of agents registered in thedatabase manager instance.

NumIdleAgents NUMERIC The number of agents in the agent pool thatare unassigned to an application and idlewithin the database manager instanceduring the monitoring interval.

NumStolenAgents NUMERIC The number of times that agents are stolenfrom all applications that are connected to adatabase within the database managerinstance.

NumUnassignedAgents NUMERIC The number of agents in the agent pool thatare currently unassigned to an application.

PctAgentsWaiting NUMERIC The percentage of registered agents that arewaiting to execute a transaction. The valueis defined as agents waiting for atoken/maximum agents registered x 100.


Note:


aix4-r1 mof/unix/DB2InstanceAgents.mof

linux-ix86 mof/unix/DB2InstanceAgents.mof

solaris2 mof/unix/DB2InstanceAgents.mof

hpux10 mof/unix/DB2InstanceAgents.mof

w32-ix86 mof/w32-ix86DB2InstanceAgents.mof


DB2InstanceConfiguration


Table 61. CIM Class

CIM Name ROOT\CIMV2: DB2InstanceConfiguration

MOF File Name DB2InstanceConfiguration.mof

Description The DB2InstanceConfiguration class tracks statistics pertaining toa given DB2 database instance name.Note: The Resource Instance Key (OID) is: db2InstanceName.



ClientIOBlockSize NUMERIC The current value (in bytes) of the clientinput and output block size.

CurAgentsPriority NUMERIC The current value of the priority of agents.

CurMaxAgents NUMERIC The current value of the maximum numberof agents.


MaxConcurrentAgents NUMERIC The maximum number of database managercoordinator agents that can concurrentlyexecute a database manager transaction inthe DB2 instance during the monitoringinterval.

MaxPoolAgents NUMERIC The maximum number of idle agents in theagent pool within the DB2 instance duringthe monitoring interval.

MaxQueryHeapSize NUMERIC The maximum amount of memory thatcould be allocated for the query heap withinthe DB2 instance during the monitoringinterval.

NumFcmAnchors NUMERIC The number of FCM message anchors forthe DB2 instance during the monitoringinterval.

NumFcmBuffers NUMERIC The number of buffers that are used forinternal communications (messages) amongthe nodes and within the nodes in a DB2instance during the monitoring interval.

NumFcmConnections NUMERIC The number of FCM connection entries forthe DB2 instance during the monitoringinterval.

NumFcmReqBlocks NUMERIC The number of FCM request blocks for theDB2 instance during the monitoring interval.

SortHeapThreshold NUMERIC The current value (in units of 4-KB pages) ofthe sort heap threshold.

SqlStatementSize NUMERIC The current value of the SQL statement size.


aix4-r1 mof/unix/DB2InstanceConfiguration.mof



linux-ix86 mof/unix/DB2InstanceConfiguration.mof

solaris2 mof/unix/DB2InstanceConfiguration.mof

hpux10 mof/unix/DB2InstanceConfiguration.mof

w32-ix86 mof/w32-ix86/DB2InstanceConfiguration.mof


DB2InstanceConnections


Table 64. CIM Class

CIM Name ROOT\CIMV2: DB2InstanceConnections

MOF File Name DB2InstanceConnections.mof

Description The DB2InstanceConnections class data pertains to applicationsconnected to an instance of a DB2 database.Note: The Resource Instance Key (OID) is: db2InstanceName.




NumConnectionsToLocalDBases NUMERIC The number of local databasesthat have applicationsconnected.

NumLocalConnections NUMERIC A number of local applicationscurrently connected to localdatabases within a DB2 instance.

NumLocalConnectionsExecuting NUMERIC The number of localapplications currently connectedto a local database within a DB2instance and that are currentlyprocessing a unit of work.

NumRemoteConnections NUMERIC The number of currentapplication connections thatremote clients have initiated tothe DB2 instance.

NumRemoteConnectionsExecuting NUMERIC The number of remoteapplications currently connectedto a local database within a DB2instance and that are currentlyprocessing a unit of work.

PctConnectionsExecuting NUMERIC The percentage of the maximumnumber of applications allowedthat connected to a databaseand processing a unit of work(within the database managerinstance) during the monitoringinterval. The value is defined asnumber ofapplications/maximumapplications.


aix4-r1 mof/unix/DB2InstanceConnections.mof

linux-ix86 mof/unix/DB2InstanceConnections.mof

solaris2 mof/unix/DB2InstanceConnections.mof

hpux10 mof/unix/DB2InstanceConnections.mof



w32-ix86 mof/w32-ix86/DB2InstanceConnections.mof


DB2InstanceSorts


Table 67. CIM Class

CIM Name ROOT\CIMV2: DB2InstanceSorts

MOF File Name DB2InstanceSorts.mof

Description The DB2InstanceSorts class tracks sort heaps and piped sorts thatpertain to a given instance.Note: The Resource Instance Key (OID) is: db2InstanceName.




NumPipedSortsAccepted NUMERIC The number of piped sorts that wereaccepted.

NumPipedSortsRequested NUMERIC The number of piped sorts that wererequested.

PctPipedSortHits NUMERIC The piped sort hit ratio (as apercentage) for the last interval. Thepiped sort hit ratio is the ratio of pipedsorts accepted to piped sorts requested.

PctPipedSortReqRejected NUMERIC The percentage of piped sort requeststhat were rejected for the DB2 instanceduring the monitoring interval.

PctSortHeapUsed NUMERIC The percentage of the allocated sortheap that the DB2 instance used duringthe monitoring interval.

PipedSortReqRejected NUMERIC The total number of piped sorts thatwere rejected during the monitoringinterval.

PostThresholdSorts NUMERIC The number of sorts that requestedheaps after the sort heap threshold wasreached during the monitoring interval.

SortHeapAlocated NUMERIC The total amount (in pages) of sort heapcurrently allocated for all sorts in allactive databases in the DB2 instance.


aix4-r1 mof/unix/DB2InstanceSorts.mof

linux-ix86 mof/unix/DB2InstanceSorts.mof

solaris2 mof/unix/DB2InstanceSorts.mof

hpux10 mof/unix/DB2InstanceSorts.mof

w32-ix86 mof/w32-ix86/DB2InstanceSorts.mof


DB2InstanceStatus


Table 70. CIM Class

CIM Name ROOT\CIMV2: DB2InstanceStatus

MOF File Name DB2InstanceStatus.mof

Description The DB2InstanceStatus class tracks database manager informationfor a given DB2 database instance.Note: The Resource Instance Key (OID) is: db2InstanceName.



CounterResetTimestamp STRING The date and time that monitoring sourcecounters were reset for the database manager.


DB2StartTimestamp STRING The date and time the database manager wasstarted.

db2Status STRING The DB2 instance status.

Note:


aix4-r1 mof/unix/DB2InstanceStatus.mof

linux-ix86 mof/unix/DB2InstanceStatus.mof

solaris2 mof/unix/DB2InstanceStatus.mof

hpux10 mof/unix/DB2InstanceStatus.mof

w32-ix86 mof/w32-ix86/DB2InstanceStatus.mof


DB2Locks


Table 73. CIM Class

CIM Name ROOT\CIMV2: DB2Locks

MOF File Name DB2Locks.mof

Description The DB2Locks class tracks lock and deadlock information for aninstance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



ApplsInLockWait NUMERIC The number of applications that arecurrently waiting for locks in thedatabase.

AvgLockEscalationConn NUMERIC The average number of lock escalationsper connection.

AvgLockWait NUMERIC The average time (in seconds) thatapplications wait for a lock within thedatabase during the monitoringinterval.

AvgLocksHeld NUMERIC The average number of locks held byeach currently connected application inthe database.




DeadlocksDelta NUMERIC The number of deadlocks detected inthe database during the last monitoringinterval.

ExclusiveLockEscalations NUMERIC The total number of times that lockswere escalated from several row locksto one exclusive table lock, or thenumber of times an exclusive lock on arow caused the table lock to become anexclusive lock.

LockEscalationsDelta NUMERIC The number of lock escalations thatoccurred in the database during themonitoring interval. Exclusive lockescalations are included in this number.

LockTimeouts NUMERIC The number of times that a request tolock an object timed out instead ofbeing granted for the database.

LockTimeoutsDelta NUMERIC The number of times that a request tolock an object that timed out instead ofbeing granted during the monitoringinterval.




LockWaitsDelta NUMERIC The number of times that applicationshad to wait for locks in the databaseduring the monitoring interval.

LocklistMemInUse NUMERIC The total amount of lock list memory(in bytes) that is in use in the database.

PctApplsInLockWait NUMERIC The percentage of currently connectedapplications that are waiting on a lockin the database.

PctDeadlockRollbacks NUMERIC The percentage of rollbacks that weredue to deadlock during the monitoringinterval.

PctIntDeadlockedRollbacks NUMERIC The percentage of the total number ofinternal rollbacks due to deadlocks.

PctLockListUsed NUMERIC The percentage of space used in thedatabase’s locklist.

TotCurLocksHeld NUMERIC The total number of locks currentlyheld by all applications in the database.

TotDeadLocks NUMERIC The total number of deadlocks thathave occurred in the database.

TotDeadlockIntRollbacks NUMERIC The total number of forced rollbacksinitiated by the database managerbecause of a deadlock.

TotLockWaitTime NUMERIC The total elapsed time (in seconds) thatall applications waited for a lock withinthe database.

TotLockWaits NUMERIC The total number of times thatapplications had to wait for lockswithin the database.


aix4-r1 mof/unix/DB2Locks.mof

linux-ix86 mof/unix/DB2Locks.mof

solaris2 mof/unix/DB2Locks.mof

hpux10 mof/unix/DB2Locks.mof

w32-ix86 mof/w32-ix86/DB2Locks.mof


DB2Logging


Table 76. CIM Class

CIM Name ROOT\CIMV2: DB2Logging

MOF File Name DB2Logging.mof

Description The DB2Logging class tracks use of the DB2 logging system by aninstance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.






LogPageReads NUMERIC The number of log pages readfrom disk by the DB2 loggingsystem.

LogPageWrites NUMERIC The number of log pages writtento disk by the DB2 logging system.

MaxPrimaryLogSpaceUsed NUMERIC The maximum number of bytesused by the primary log.

MaxSecondaryLogSpaceUsed NUMERIC The maximum number of bytesused by the secondary log.

MaxTotalLogSpaceUsed NUMERIC The maximum amount (in bytes)of total log space used.

PctLogSpaceUsedByPrimary NUMERIC The percentage of log space usedby the primary log.

PctLogSpaceUsedBySecondary NUMERIC The percentage of log space usedby the secondary log.

PrimaryLogSpaceAllocated NUMERIC The number of bytes allocated tothe primary log.

TotLogInputOutput NUMERIC The total amount of log input andoutput. This amount is the sum ofthe number of log pages read andthe number of log pages writtenwithin the monitoring interval.

TotSecondaryLogsInUse NUMERIC The total number of secondary logfiles that are currently being usedfor the database.


aix4-r1 mof/unix/DB2Logging.mof

linux-ix86 mof/unix/DB2Logging.mof

solaris2 mof/unix/DB2Logging.mof



hpux10 mof/unix/DB2Logging.mof

w32-ix86 mof/w32-ix86/DB2Logging.mof


DB2PackageCache


Table 79. CIM Class

CIM Name ROOT\CIMV2: DB2PackageCache

MOF File Name DB2PackageCache.mof

Description The DB2PackageCache class tracks a DB2 database instance’spackage cache information.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.






PackageCacheInserts NUMERIC The number of times that a section had tobe loaded into the package cache because anapplication found that the section it wantedwas not in the package cache.

PackageCacheLookups NUMERIC The number of times that an applicationlooked for a section in the package cache.

PctPackageCacheHits NUMERIC The package cache hit ratio (as apercentage) for the last monitoring interval.The package cache hit ratio is the ratio of(package_cache_lookups -package_cache_inserts)/all_package_cache_lookups.


aix4-r1 mof/unix/DB2PackageCache.mof

linux-ix86 mof/unix/DB2PackageCache.mof

solaris2 mof/unix/DB2PackageCache.mof

hpux10 mof/unix/DB2PackageCache.mof

w32-ix86 mof/w32-ix86/DB2PackageCache.mof




Table 82. CIM Class

CIM Name ROOT\CIMV2: DB2PartitionFCMActivity

MOF File Name DB2PartitionFCMActivity.mof

Description The DB2PartitionFCMActivity class tracks FCM information,including but not limited to: buffers, request blocks, connectionanchors, and request blocks.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



ConnectionStatus STRING Status of the communicationconnection between the databasepartition specified by the DB2 NodeNumber variable and the databasepartition where this monitoringsource executes.




FreeFcmBuffers NUMERIC The number of FCM that are free inthe partitioned database serverduring the monitoring interval.

FreeFcmConnections NUMERIC The number of connection entriesthat are free in the partitioneddatabase server during themonitoring interval.

FreeFcmRequestBlocks NUMERIC The number of request blocks thatare free in the partitioned databaseserver during the monitoringinterval.

MinFreeFcmBuffers NUMERIC The lowest number of free buffersreached during processing in thepartitioned database server.

MinFreeFcmConnections NUMERIC The lowest number of freeconnection entries during processingin the partitioned database server.

MinFreeFcmMsgAnchors NUMERIC The lowest number of free messageanchors reached during processing inthe partitioned database server.

MinFreeFcmReqBlocks NUMERIC The lowest number of free requestblocks reached during processing inthe partitioned database server.

NumFcmNodes NUMERIC The number of nodes in the currentDB2 partitioned configuration.




PctFcmBuffsInUse NUMERIC The percentage of FCM buffers thatare used within the partitioneddatabase server during themonitoring interval.

PctFcmConnInUse NUMERIC The percentage of FCM connectionentries that are used within thepartitioned database server duringthe monitoring interval.

PctFcmReqBlocksUsed NUMERIC The percentage of FCM requestblocks that are used within thepartitioned database server duringthe monitoring interval.

PctMaxFcmBuffUsed NUMERIC The percentage of maximum FCMbuffers that are used duringprocessing within the partitioneddatabase server.

PctMaxFcmConnUsed NUMERIC The percentage of maximum FCMconnection entries that are usedduring processing within thepartitioned database server.

PctMaxFcmMsgAnchorUsed NUMERIC The percentage of maximum FCMmessage anchors that are usedduring processing within thepartitioned database server.

PctMaxFcmReqBlocksUsed NUMERIC The percentage of maximum FCMrequest blocks that are used duringprocessing within the partitioneddatabase server.

TotFcmBuffsReceived NUMERIC The total number of FCM buffersreceived by the database node wherethis monitoring source executes. Thedatabase node is specified in theDB2_node_number variable.

TotFcmBuffsSent NUMERIC The total number of FCM bufferssent from the database node wherethis monitoring source executes tothe node specified by theDB2_node_number variable.


aix4-r1 mof/unix/DB2PartitionFCMActivity.mof

linux-ix86 mof/unix/DB2PartitionFCMActivity.mof

solaris2 mof/unix/DB2PartitionFCMActivity.mof

hpux10 mof/unix/DB2PartitionFCMActivity.mof

w32-ix86 mof/w32-ix86/DB2PartitionFCMActivity.mof


DB2PartitionGroups


Table 85. CIM Class

CIM Name ROOT\CIMV2: DB2PartitionGroups

MOF File Name DB2PartitionGroups.mof

Description The DB2PartitionGroups class tracks partition and node groupinformation for a given instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.






NodeGrpRedistributeSatus NUMERIC The positive value if row redistributionis in progress in the specified nodegroup in the partitioned databaseduring the monitoring interval.

NumInactiveNodes NUMERIC The number of inactive nodes in thepartition group.

PctDiffTableRowDistr NUMERIC The difference in percentage betweenthe highest and the lowest rowsdistributed across the partitions in theselected partition group during themonitoring interval.

RedistributeStatus NUMERIC The positive value if row redistributionis in progress in any node group in thepartitioned database during themonitoring interval.


aix4-r1 mof/unix/DB2PartitionGroups.mof

linux-ix86 mof/unix/DB2PartitionGroups.mof

solaris2 mof/unix/DB2PartitionGroups.mof

hpux10 mof/unix/DB2PartitionGroups.mof

w32-ix86 mof/w32-ix86/DB2PartitionGroups.mof


DB2Sorts


Table 88. CIM Class

CIM Name ROOT\CIMV2: DB2Sorts

MOF File Name DB2Sorts.mof

Description The DB2Sorts class tracks time and space statistics for sortingactions on a given instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



AvgSortTime NUMERIC The average sorting time (in milliseconds) at thedatabase level.




NumActiveSorts NUMERIC The number of sorts in the database thatcurrently have a sort heap allocated.

PctSortOverflowed NUMERIC The percentage of sorts that overflowed for thedatabase during the monitoring interval.

SortHeapAllocated NUMERIC The Total amount (in pages) of sort heapcurrently allocated for all sorts in the database.

TotSortTime NUMERIC The total elapsed time (in milliseconds) for allsorts that were executed within a databaseduring the monitoring interval.

TotalSorts NUMERIC The total number of sorts that were executedwithin a database during the monitoringinterval.


aix4-r1 mof/unix/DB2Sorts.mof

linux-ix86 mof/unix/DB2Sorts.mof

solaris2 mof/unix/DB2Sorts.mof

hpux10 mof/unix/DB2Sorts.mof

w32-ix86 mof/w32-ix86/DB2Sorts.mof


DB2SQLStatements


Table 91. CIM Class

CIM Name ROOT\CIMV2: DB2SQLStatements

MOF File Name DB2SQLStatements.mof

Description The DB2SQLStatements class tracks database activity pertaining toSQL activity on an instance of a DB2 database. This activity refersto the SQL compiles and commands as well as the row andcolumn activity on the database itself.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.



BindPrecompileAttempts NUMERIC The number of binds and precompilesthat have been attempted in the database.

CommitRate NUMERIC The rate (counts per second) at whichunit-of-work commits were attempted forthe database during the monitoringinterval. Unit-of-work commits includeSQL COMMIT statements that are issuedfrom applications and internal commitsthat are initiated by the database manager.




DDLSqlStatements NUMERIC The number of SQL DDL statements thatwere executed in the database during themonitoring interval.

DynamicSqlStatements NUMERIC The number of dynamic SQL statementsthat were attempted for the databaseduring the monitoring interval.

FailedSqlStatements NUMERIC The number of failed SQL statements forthe database during the monitoringinterval.

InternalRowDeletes NUMERIC The number of rows deleted from thedatabase as a result of internal activity.

InternalRowInserts NUMERIC The number of rows inserted into adatabase as a result of internal activitycaused by triggers.

InternalRowUpdates NUMERIC The number of rows updated in thedatabase as a result of internal activity.

PctDDLSqlStatements NUMERIC The percentage of total SQL statementsthat were SQL UPDATE, INSERT, andDELETE statements during themonitoring interval.

PctFailedSqlStatements NUMERIC The percentage of total SQL statementsthat failed during the monitoring interval.




PctSelectSqlStatements NUMERIC The percentage of total SQL statementsthat were SQL SELECT statements duringthe monitoring interval.

RollbackRate NUMERIC The rate (counts per second) at whichunit-of-work rollbacks were attemptedduring the monitoring interval.Unit-of-work rollbacks include SQLROLLBACK statements that are issuedfrom applications and internal rollbacksthat are initiated by the database manager.

RowDeleteAttempts NUMERIC The number of row deletions attemptedfor the database.

RowInsertAttempts NUMERIC The number of row insertions attemptedfor the database.

RowUpdateAttempts NUMERIC The number of row updates attempted forthe database.

RowsSelected NUMERIC The number of rows that were selectedand returned to an application.

SqlSelectsExecuted NUMERIC The number of SQL SELECT statementsthat were executed during the monitoringinterval.

SqlStatementsRate NUMERIC The rate (statements per second) at whichSQL statements were executed during themonitoring interval.

StaticSqlAttempts NUMERIC The number of static SQL statements thatwere attempted during the monitoringinterval.

TotAutoRebindAttempts NUMERIC The number of automatic rebinds orrecompiles that were attempted in thedatabase.

TotInternalCommits NUMERIC The total number of commits initiatedinternally by the database.

TotInternalRollbacks NUMERIC The total number of rollbacks initiatedinternally by the database.

TotSqlCommitAttempts NUMERIC The total number of SQL COMMITstatements that were attempted.

TotSqlRollbackAttempts NUMERIC The total number of SQL ROLLBACKstatements that were attempted for thedatabase.

UIDSqlExecuted NUMERIC The number of SQL UPDATE, INSERT,and DELETE statements that wereexecuted during the monitoring interval.


aix4-r1 mof/unix/DB2SQLStatements.mof

linux-ix86 mof/unix/DB2SQLStatements.mof

solaris2 mof/unix/DB2SQLStatements.mof

hpux10 mof/unix/DB2SQLStatements.mof



w32-ix86 mof/w32-ix86/DB2SQLStatements.mof


DB2Status


Table 94. CIM Class

CIM Name ROOT\CIMV2: DB2Status

MOF File Name DB2Status.mof

Description The DB2Status class tracks when the last database backup wascompleted for a given instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.






LastBackupTimestamp STRING The date and time when the last databasebackup was completed.

Note:


aix4-r1 mof/unix/DB2Status.mof

linux-ix86 mof/unix/DB2Status.mof

solaris2 mof/unix/DB2Status.mof

hpux10 mof/unix/DB2Status.mof

w32-ix86 mof/w32-ix86/DB2Status.mof


DB2TableActivity


Table 97. CIM Class

CIM Name ROOT\CIMV2: DB2TableActivity

MOF File Name DB2TableActivity.mof

Description The DB2TableActivity class tracks total time and access rates forrow reads and writes on an instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Schema.db2TableName.





db2Schema STRING The DB2 schema name.

db2TableName STRING The DB2 table name.

OverflowAccesses NUMERIC The number of accesses (reads and writes)made to overflowed rows of the table.

RowsReadRate NUMERIC The rate (per second) at which row were readfrom the table during the monitoring interval.

RowsWrittenRate NUMERIC The rate (per second) at which rows werechanged (inserted, deleted, or updated) in thetable during the monitoring interval.


aix4-r1 mof/unix/DB2TableActivity.mof

linux-ix86 mof/unix/DB2TableActivity.mof

solaris2 mof/unix/DB2TableActivity.mof

hpux10 mof/unix/DB2TableActivity.mof

w32-ix86 mof/w32-ix86/DB2TableActivity.mof


DB2TableContent


Table 100. CIM Class

CIM Name ROOT\CIMV2: DB2TableContent

MOF File Name DB2TableContent.mof

Description The DB2TableContent class tracks the number of rows in the tablefor a table in an instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Schema.db2TableName.






db2TableName STRING The DB2 table name.

NumRows NUMERIC The number of rows in the table.


aix4-r1 mof/unix/DB2TableContent.mof

linux-ix86 mof/unix/DB2TableContent.mof

solaris2 mof/unix/DB2TableContent.mof

hpux10 mof/unix/DB2TableContent.mof

w32-ix86 mof/w32-ix86/DB2TableContent.mof


DB2TableReplication



CIM Name ROOT\CIMV2: DB2TableReplication

MOF File Name DB2TableReplication.mof

Description The DB2TableReplication class tracks subscription information foran Apply ID associated with an instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2ApplyID.



ApplyRequiresRefresh NUMERIC The number of subscriptions the Applyprogram failed to replicate.

ApplySubscriptionLagTime NUMERIC The number of lagging subscriptionsfor the Apply program.

ApplySubscriptionStatus NUMERIC The Apply Subscription Status.

db2ApplyID STRING The DB2 Apply ID.




aix4-r1 mof/unix/DB2TableReplication.mof

linux-ix86 mof/unix/DB2TableReplication.mof

solaris2 mof/unix/DB2TableReplication.mof

hpux10 mof/unix/DB2TableReplication.mof

w32-ix86 mof/w32-ix86/DB2TableReplication.mof


DB2TablespaceBufferPool



CIM Name ROOT\CIMV2: DB2TablespaceBufferPool

MOF File Name DB2TablespaceBufferPool.mof

Description The DB2TablespaceBufferPool class tracks statistics pertaining to atablespace’s buffer pool for an instance of a DB2 database. Thesestatistics include, but are not limited to: read and write requests,external storage, physical index, data pages, and synchronous I/O.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2TbspName.



AsyncDataReads NUMERIC The number of data pages readasynchronously into the bufferpool for the tablespace.

AsyncDataReadRequests NUMERIC The number of asynchronousread requests for the tablespaceduring the monitoring interval.

AsyncDataWrites NUMERIC The number of times a bufferpool data page was writtenasynchronously to disk for thetablespace.

AsyncIndexReads NUMERIC The number of index pagesread asynchronously into thebuffer pool by a prefetcherwithin the tablespace.

AsyncIndexWrites NUMERIC The number of times a bufferpool index page was writtenasynchronously to disk for thetablespace.

AsyncReadTime NUMERIC The time (in milliseconds) thatdatabase manager prefetchersspent reading data into thebuffer pool for the tablespace.

AsyncWriteTime NUMERIC The time (in milliseconds) thatdatabase manager page cleanersspent writing data or indexpages from the buffer pool todisk for the tablespace.

AvgPoolIOTime NUMERIC The average time (inmilliseconds) for performingbuffer pool input and outputoperations (reading or writing)for the tablespace.




AvgPoolReadTime NUMERIC The average time (inmilliseconds) for processingread requests that caused dataor index pages to be physicallyread from disk to buffer poolfor the tablespace.

AvgPoolWriteTime NUMERIC The average time (inmilliseconds) for processingwrite requests that caused dataor index pages to be physicallywritten from buffer pool to diskfor the tablespace.

AvgSyncIOTime NUMERIC The average time (inmilliseconds) for synchronousinput and output operations forthe tablespace.

AvgSyncReadTime NUMERIC The average time (inmilliseconds) for synchronousdata reads for the tablespace.

AvgSyncWriteTime NUMERIC The average time (inmilliseconds) for synchronousdata writes for the tablespace.




db2TbspName STRING The DB2 tablespace name.

DataPagesCopiedFromExtStorage NUMERIC The number of buffer pool datapages copied from extendedstorage within the tablespace.

DataPagesCopiedToExtStorage NUMERIC The number of buffer pool datapages copied from extendedstorage for the tablespace.

FilesClosed NUMERIC The total number of closed filesfor the tablespace.

IndexPagesCopiedFromExtStorage NUMERIC The number of buffer poolindex pages copied fromextended storage for thetablespace.

IndexPagesCopiedToExtStorage NUMERIC The number of buffer poolindex pages copied to extendedstorage within the tablespace.

InputOutputRate NUMERIC The rate (per second) for bufferpool input and output for thetablespace. For this monitoringsource, buffer pool input andoutput includes all physicaldata and index pages that gothrough the buffer pool whenread or written.




LogicalDataReads NUMERIC The number of logical readrequests for data pages thatwent through the buffer poolfor the tablespace.

LogicalIndexReads NUMERIC The number of logical readrequests for index pages thatwent through the buffer poolfor the tablespace.

PctAsyncReadReqSatisfied NUMERIC The percentage of asynchronousread requests that were satisfiedfor a tablespace during the lastmonitoring interval.

PctBufferPoolHits NUMERIC The overall buffer pool hit ratio(as a percentage) for thetablespace during themonitoring interval.

PctExtStorageReadWrite NUMERIC The ratio (as a percentage) ofpages (data+index) copied fromextended storage to pagescopied to extended storagewithin the tablespace.

PctIndexHits NUMERIC The tablespace’s index page hitratio (as a percentage) for thebuffer pool during themonitoring interval.

PhysicalDataReads NUMERIC The number of read requestsrequiring input and output toget data pages into the bufferpool for the tablespace.

PhysicalDataWrites NUMERIC The number of times that abuffer pool data page wasphysically written to disk forthe tablespace.

PhysicalIndexReads NUMERIC The number of physical readrequests to get index pages intothe buffer pool for thetablespace.

PhysicalIndexWrites NUMERIC The number of times that abuffer pool index page wasphysically written to disk forthe tablespace.

SyncDataReads NUMERIC The number of times thatphysical data pages were readsynchronously into the bufferpool for the tablespace.

SyncDataWrites NUMERIC The number of times that datapages were writtensynchronously for thetablespace.




SyncIndexReads NUMERIC The number of physical indexpages that were readsynchronously for thetablespace.

SyncIndexWrites NUMERIC The number of physical indexpage write requests that wereperformed synchronously forthe tablespace.

SyncReadTime NUMERIC The time (in milliseconds)applied to synchronous readsfor the tablespace.

SyncWriteTime NUMERIC The time (in milliseconds)applied to synchronous writesto disk for the tablespace.

TotIOTime NUMERIC The total time (in milliseconds)for physical buffer pool inputand output operations(including both synchronousand asynchronous reads anwrites) for the tablespace.

TotPoolReads NUMERIC The total number of physicalread requests to get data orindex pages into the buffer poolfor the tablespace.

TotPoolWrites NUMERIC The total number of timesbuffer pool data or index pageswere physically written to diskfor the tablespace.

TotReadTime NUMERIC The total buffer pool physicalread time (includingasynchronous read times).

TotSyncInputOutput NUMERIC The total number ofsynchronous reads and writesfor both data and index pagesfor the tablespace.

TotWriteTime NUMERIC The total time (in milliseconds)for buffer pool physical writes(including asynchronous writes)for the tablespace.


aix4-r1 mof/unix/DB2TablespaceBufferPool.mof

linux-ix86 mof/unix/DB2TablespaceBufferPool.mof

solaris2 mof/unix/DB2TablespaceBufferPool.mof

hpux10 mof/unix/DB2TablespaceBufferPool.mof

w32-ix86 mof/w32-ix86/DB2TablespaceBufferPool.mof


DB2TablespaceContent



CIM Name ROOT\CIMV2: DB2TablespaceContent

MOF File Name DB2TablespaceContent.mof

Description The DB2TablespaceContent class tracks the number of tables in thetablespace for a given instance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2TbspName.







NumTables NUMERIC The number of tables in the tablespace.


aix4-r1 mof/unix/DB2TablespaceContent.mof

linux-ix86 mof/unix/DB2TablespaceContent.mof

solaris2 mof/unix/DB2TablespaceContent.mof

hpux10 mof/unix/DB2TablespaceContent.mof

w32-ix86 mof/w32-ix86/DB2TablespaceContent.mof


DB2TablespaceDirectIO



CIM Name ROOT\CIMV2: DB2TablespaceDirectIO

MOF File Name DB2TablespaceDirectIO.mof

Description The DB2TablespaceDirectIO class tracks data pertaining tonon-buffered I/O for an instance of a DB2 database. The datatracked includes direct read/writes, including timing and sectorcounts for each.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2TbspName.



AvgDirectReadTime NUMERIC The average time (in milliseconds)applied to performing direct reads forthe tablespace.

AvgDirectWriteTime NUMERIC The average time (in milliseconds) forperforming direct writes for thetablespace.





DirectReadAvgSectorsPer NUMERIC The average number of sectors read perdirect read.

DirectReadRequests NUMERIC The number of requests to perform adirect read from disk of one or moresectors of data for the tablespace.

DirectReadTime NUMERIC The time (in milliseconds) forperforming the direct reads for thetablespace.

DirectReads NUMERIC The number of read operations for thetablespace that did not use the bufferpool.

DirectWriteAvgSecotrsPer NUMERIC The average number of sectors writtenper direct write.

DirectWriteRequests NUMERIC The number of requests to perform adirect write of one or more sectors ofdata for the tablespace.

DirectWriteTime NUMERIC The time (in milliseconds) forperforming the direct writes for thetablespace.

DirectWrites NUMERIC The number of write operations for thetablespace that did not use the bufferpool.




TotDirectIOTime NUMERIC The total time (in milliseconds) fordirect reads to and writes from thetablespace.


aix4-r1 mof/unix/DB2TablespaceDirectIO.mof

linux-ix86 mof/unix/DB2TablespaceDirectIO.mof

solaris2 mof/unix/DB2TablespaceDirectIO.mof

hpux10 mof/unix/DB2TablespaceDirectIO.mof

w32-ix86 mof/w32-ix86/DB2TablespaceDirectIO.mof


DB2TablespaceSizeDMS



CIM Name ROOT\CIMV2: DB2TablespaceSizeDMS

MOF File Name DB2TablespaceSizeDMS.mof

Description The DB2TablespaceSizeDMS class tracks the percentage of spaceused in the database managed space tablespace by an instance of aDB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2TbspName.







PctSpaceUsedDMS NUMERIC The percentage of space used in the DatabaseManaged Space (DMS) tablespace.


aix4-r1 mof/unix/DB2TablespaceSizeDMS.mof

linux-ix86 mof/unix/DB2TablespaceSizeDMS.mof

solaris2 mof/unix/DB2TablespaceSizeDMS.mof

hpux10 mof/unix/DB2TablespaceSizeDMS.mof

w32-ix86 mof/w32-ix86/DB2TablespaceSizeDMS.mof


DB2TablespaceSizeSMS



CIM Name ROOT\CIMV2: DB2TablespaceSizeSMS

MOF File Name DB2TablespaceSizeSMS.mof

Description The DB2TablespaceSizeSMS class tracks the number of bytes usedin the system managed space tablespace by an instance of a DB2database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2TbspName.







SpaceUsedSMS NUMERIC The number of bytes allocated to the SystemManaged Space (SMS) tablespace.


aix4-r1 mof/unix/DB2TablespaceSizeSMS.mof

linux-ix86 mof/unix/DB2TablespaceSizeSMS.mof

solaris2 mof/unix/DB2TablespaceSizeSMS.mof

hpux10 mof/unix/DB2TablespaceSizeSMS.mof

w32-ix86 mof/w32-ix86/DB2TablespaceSizeSMS.mof


DB2TablespaceStatus



CIM Name ROOT\CIMV2: DB2TablespaceStatus

MOF File Name DB2TablespaceStatus.mof

Description The DB2TablespaceStatus class tracks the tablespace status of aninstance of a DB2 database.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Node.db2TbspName.







TableSpaceStatus NUMERIC The numeric value indicating the tablespace status.


aix4-r1 mof/unix/DB2TablespaceStatus.mof

linux-ix86 mof/unix/DB2TablespaceStatus.mof

solaris2 mof/unix/DB2TablespaceStatus.mof

hpux10 mof/unix/DB2TablespaceStatus.mof

w32-ix86 mof/w32-ix86/DB2TablespaceStatus.mof


DB2TableStatus



CIM Name ROOT\CIMV2: DB2TableStatus

MOF File Name DB2TableStatus.mof

Description The DB2TableStatus class indicates whether an instance of a DB2database needs to be reorganized.Note: The Resource Instance Key (OID) is:db2Instance.db2Database.db2Schema.db2TbspName.







ReorgNeeded STRING The string indicating whether the specified table orits indexes need to be reorganized.


aix4-r1 mof/unix/DB2TableStatus.mof

linux-ix86 mof/unix/DB2TableStatus.mof

solaris2 mof/unix/DB2TableStatus.mof

hpux10 mof/unix/DB2TableStatus.mof

w32-ix86 mof/w32-ix86/DB2TableStatus.mof


Appendix C. Tivoli Enterprise Console classes

This appendix contains the Tivoli Enterprise Console classes delivered with IBMTivoli Monitoring for Databases: DB2. The classes contain the new slot values forthe event.

Slots are the fields in a Tivoli event. All Tivoli events have a base set of slots asdescribed in the Tivoli Enterprise Console User’s Guide. In addition to these slots,IBM Tivoli Monitoring for Databases: DB2 adds slots for additional information.You can reference these classes and slots to assist you in writing your ownbusiness rules.

Resource ModelsIBM Tivoli Monitoring for Databases: DB2 includes event class definitions in thefollowing files:

Note: You must insert the DB2_Event.baroc file before any of the other DB2 files.

Tmw2k.barocDefines the IBM Tivoli Monitoring 5.1.1 events.

DB2_Event.baroc

v Defines DB2_Event as a subclass of the main IBM Tivoli Monitoringevent, TMW_Event.TEC_CLASS :DB2_Event ISA TMW_EventDEFINES {application_version : STRING, default=7.x;application_label : STRING;application_oid : STRING;application_class : STRING;

};END

db2Agents.barocDefines the following events as subclasses of DB2Event:v DB2_High_InstanceAgents_AgentCreationRatio

TEC_CLASS :DB2_High_InstanceAgents_AgentCreationRatio ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_oid : STRING;application_label : STRING;agentcreationratio : REAL;upperbound : REAL;

severity: default = WARNING;};END

v DB2_High_InstanceAgents_PctAgentsWaitingTEC_CLASS :DB2_High_InstanceAgents_PctAgentsWaiting ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;

467

application_oid : STRING;application_label : STRING;pctagentswaiting : REAL;upperbound : REAL;


v DB2_High_ApplicationAgents_WorkloadTEC_CLASS :DB2_High_ApplicationAgents_Workload ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_oid : STRING;application_label : STRING;upperbound : REAL;workload : REAL;


v DB2_Low_InstanceAgents_AgentCreationRatioTEC_CLASS :DB2_Low_InstanceAgents_AgentCreationRatio ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_oid : STRING;application_label : STRING;agentcreationratio : REAL;lowerbound : REAL;


DB2ApplyReplication.barocDefines the following events as subclasses of DB2_Event:v DB2_High_ApplyReplication_FailedSubscriptions

v DB2_ApplyStatus_DownTEC_CLASS :DB2_ApplyStatus_Down ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;

severity: default = CRITICAL;};END

v DB2_High_ApplyReplication_FailedSubscriptionsTEC_CLASS :DB2_High_ApplyReplication_FailedSubscriptions ISA DB2_EventDEFINES {db2database : STRING;db2applyid : STRING;


db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;failedsubscriptions : REAL;upperbound : REAL;


v DB2_High_ApplyReplication_LaggingSubscriptionsTEC_CLASS :DB2_High_ApplyReplication_LaggingSubscriptions ISA DB2_EventDEFINES {db2database : STRING;db2applyid : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;laggingsubscriptions : REAL;upperbound : REAL;


DB2BufferPool.barocDefines the following events as subclasses of DB2_Event:v DB2_High_Tbsp_AvgPoolIOTime

TEC_CLASS :DB2_High_Tbsp_AvgPoolIOTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;avgpooliotime : REAL;


v DB2_High_DB_AvgPoolIOTimeTEC_CLASS :DB2_High_DB_AvgPoolIOTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgpooliotime : REAL;upperbound : REAL;


v DB2_Low_DB_PctIndexHits

Appendix C. Tivoli Enterprise Console classes 469

TEC_CLASS :DB2_Low_DB_PctIndexHits ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctindexhits : REAL;lowerbound : REAL;


v DB2_Low_DB_PctBufferPoolHitsTEC_CLASS :DB2_Low_DB_PctBufferPoolHits ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctbufferpoolhits : REAL;lowerbound : REAL;


v DB2_High_DB_AvgPoolReadTimeTEC_CLASS :DB2_High_DB_AvgPoolReadTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgpoolreadtime : REAL;upperbound : REAL;


v DB2_High_Tbsp_AvgPoolWriteTimeTEC_CLASS :DB2_High_Tbsp_AvgPoolWriteTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgpoolwritetime : REAL;upperbound : REAL;



v DB2_High_DB_AvgSyncIOTimeTEC_CLASS :DB2_High_DB_AvgSyncIOTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgsynciotime : REAL;upperbound : REAL;


v DB2_High_DB_AvgSyncReadTimeTEC_CLASS :DB2_High_DB_AvgSyncReadTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgsyncreadtime : REAL;upperbound : REAL;


v DB2_Low_DB_AvgAsyncReadsPerPoolReadTEC_CLASS :DB2_Low_DB_AvgAsyncReadsPerPoolRead ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgasyncreadsperpoolread : REAL;lowerbound : REAL;


v DB2_Low_App_PctBufferPoolHitsTEC_CLASS :DB2_Low_App_PctBufferPoolHits ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lowerbound : REAL;pctbufferpoolhits : REAL;



v DB2_High_DB_AvgPoolWriteTimeTEC_CLASS :DB2_High_DB_AvgPoolWriteTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgpoolwritetime : REAL;upperbound : REAL;


v DB2_High_DB_AvgPoolWritesPerPoolReadTEC_CLASS :DB2_High_DB_AvgPoolWritesPerPoolRead ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgpoolwritesperpoolread : REAL;upperbound : REAL;


v DB2_High_Tbsp_AvgPoolReadTimeTEC_CLASS :DB2_High_Tbsp_AvgPoolReadTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2tbspname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;avgpoolreadtime : REAL;


v DB2_Low_App_PctIndexHitsTEC_CLASS :DB2_Low_App_PctIndexHits ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;


application_oid : STRING;lowerbound : REAL;pctindexhits : REAL;


v DB2_Low_Tbsp_PctBufferPoolHitsTEC_CLASS :DB2_Low_Tbsp_PctBufferPoolHits ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lowerbound : REAL;pctbufferpoolhits : REAL;


v DB2_High_DB_AvgSyncWriteTimeTEC_CLASS :DB2_High_DB_AvgSyncWriteTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgsyncwritetime : REAL;upperbound : REAL;


v DB2_Low_DB_AvgAsyncWritesPerPoolWriteTEC_CLASS :DB2_Low_DB_AvgAsyncWritesPerPoolWrite ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgasyncwritesperpoolwrite : REAL;lowerbound : REAL;


DB2BufferPoolExtStorage.barocDefines the following events as subclasses of DB2_Event:v DB2_Low_Tbsp_PctReadWriteExtStorage

TEC_CLASS :DB2_Low_Tbsp_PctReadWriteExtStorage ISA DB2_EventDEFINES {db2instance : STRING;


db2database : STRING;db2tbspname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lowerbound : REAL;pctextstoragereadwrite : REAL;

severity: default = HARMLESS;};END

v DB2_Low_DB_PctExtStorageReadWriteTEC_CLASS :DB2_Low_DB_PctExtStorageReadWrite ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lowerbound : REAL;pctextstoragereadwrite : REAL;


DB2CatalogCache.barocDefines the following event as a subclass of DB2_Event:v DB2_Low_PctCatCacheHits

TEC_CLASS :DB2_Low_PctCatCacheHits ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctcatcachehits : REAL;lowerbound : REAL;


DB2CpuUtilization.barocDefines the following events as subclasses of DB2_Event:v DB2_High_DB2ApplicationAgent_TotUserCpuTime

TEC_CLASS :DB2_High_DB2ApplicationAgent_TotUserCpuTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;totusercputime : REAL;upperbound : REAL;



v DB2_High_ApplicationAgent_TotSystemCpuTimeTEC_CLASS :DB2_High_ApplicationAgent_TotSystemCpuTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;totsystemcputime : REAL;upperbound : REAL;


DB2Cursor.barocDefines the following events as subclasses of DB2_Event:v DB2_High_OpenCursors

TEC_CLASS :DB2_High_OpenCursors ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2appid : STRING;db2appname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;opencursors : REAL;upperbound : REAL;


v DB2_High_OpenBlockingCursorsTEC_CLASS :DB2_High_OpenBlockingCursors ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;openblockingcursors : REAL;upperbound : REAL;


DB2DatabaseStatus.barocDefines the following events as subclasses of DB2_Event:


v DB2_High_CurrentConnectionsTEC_CLASS :DB2_High_CurrentConnections ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;currentconnections : REAL;


v DB2_High_SpaceUsedDMSTablespaceTEC_CLASS :DB2_High_SpaceUsedDMSTablespace ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2tbspname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;pctspaceuseddms : REAL;


v DB2_High_SpaceUsedSMSTablespaceTEC_CLASS :DB2_High_SpaceUsedSMSTablespace ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;spaceusedsms : REAL;


v DB2_True_RestorePendingTEC_CLASS :DB2_True_RestorePending ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;restorepending : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;



v DB2_High_MostRecentConnectResponseTEC_CLASS :DB2_High_MostRecentConnectResponse ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;mostrecentconnectresponsetime : REAL;


v DB2_High_ConnWaitingForHostTEC_CLASS :DB2_High_ConnWaitingForHost ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;connwaitingforhostcurrent : REAL;


v DB2_High_ConnectionErrorsTEC_CLASS :DB2_High_ConnectionErrors ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;connectionerrors : REAL;


v DB2_Old_LastBackupTimestampTEC_CLASS :DB2_Old_LastBackupTimestamp ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;lastbackuptimestamp : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;db2node : REAL;lastbackup : REAL;


v DB2_High_PctConnectionsUsed


TEC_CLASS :DB2_High_PctConnectionsUsed ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctconnectionsused : REAL;upperbound : REAL;


v DB2_False_TablespaceNormalStatusTEC_CLASS :DB2_False_TablespaceNormalStatus ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;


DB2DirectIO.barocDefines the following events as subclasses of DB2_Event:v DB2_High_DB_AvgSectorsPerDirectWrite

TEC_CLASS :DB2_High_DB_AvgSectorsPerDirectWrite ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;directwriteavgsectorsper : REAL;


v DB2_High_App_AvgSectorsPerDirectWriteTEC_CLASS :DB2_High_App_AvgSectorsPerDirectWrite ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;directwriteavgsectorsper : REAL;



v DB2_High_DB_AvgDirectWriteTimeTEC_CLASS :DB2_High_DB_AvgDirectWriteTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgdirectwritetime : REAL;upperbound : REAL;


v DB2_High_Tbsp_AvgSectorsPerDirectReadTEC_CLASS :DB2_High_Tbsp_AvgSectorsPerDirectRead ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;directreadavgsectorsper : REAL;


v DB2_High_DB_AvgDirectReadTimeTEC_CLASS :DB2_High_DB_AvgDirectReadTime ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avgdirectreadtime : REAL;upperbound : REAL;


v DB2_High_Tbsp_AvgSectorsPerDirectWriteTEC_CLASS :DB2_High_Tbsp_AvgSectorsPerDirectWrite ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;


upperbound : REAL;directwriteavgsectorsper : REAL;


v DB2_High_Tbsp_AvgDirectReadTimeTEC_CLASS :DB2_High_Tbsp_AvgDirectReadTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;avgdirectreadtime : REAL;


v DB2_High_DB_AvgSectorsPerDirectReadTEC_CLASS :DB2_High_App_AvgSectorsPerDirectRead ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;directreadavgsectorsper : REAL;


v DB2_High_App_AvgSectorsPerDirectReadTEC_CLASS :DB2_High_DB_AvgSectorsPerDirectRead ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;directreadavgsectorsper : REAL;


v DB2_High_Tbsp_AvgDirectWriteTimeTEC_CLASS :DB2_High_Tbsp_AvgDirectWriteTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;


db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;avgdirectwritetime : REAL;


DB2FCMActivity.barocDefines the following events as subclasses of DB2_Event:v DB2_High_PctMaxFcmBuffUsed

TEC_CLASS :DB2_High_PctMaxFcmBuffUsed ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctmaxfcmbuffused : REAL;upperbound : REAL;


v DB2_High_PctMaxFcmConnUsedTEC_CLASS :DB2_High_PctMaxFcmConnUsed ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctmaxfcmconnused : REAL;upperbound : REAL;


v DB2_High_PctFcmConnInUseTEC_CLASS :DB2_High_PctFcmConnInUse ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctfcmconninuse : REAL;upperbound : REAL;


v DB2_High_PctFcmBuffsInUse


TEC_CLASS :DB2_High_PctFcmBuffsInUse ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctfcmbuffsinuse : REAL;upperbound : REAL;


v DB2_High_PctMaxFcmMsgAnchorUsedTEC_CLASS :DB2_High_PctMaxFcmMsgAnchorUsed ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctmaxfcmmsganchorused : REAL;upperbound : REAL;


DB2HostThroughput.barocDefines the following events as subclasses of DB2_Event:v DB2_High_HostTimePerStatement

TEC_CLASS :DB2_High_HostTimePerStatement ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;hosttimeperstatement : REAL;upperbound : REAL;


v DB2_High_TimePerStatementTEC_CLASS :DB2_High_TimePerStatement ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;timeperstatement : REAL;upperbound : REAL;



v DB2_High_NetworkTimePerStatementTEC_CLASS :DB2_High_NetworkTimePerStatement ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;networktimeperstatement : REAL;upperbound : REAL;


v DB2_Low_HostThroughputTEC_CLASS :DB2_Low_HostThroughput ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;hostthroughput : REAL;lowerbound : REAL;


DB2InstanceStatus.barocDefines the following events as subclasses of DB2_Event:v DB2_Down_Status

TEC_CLASS :DB2_Down_Status ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;


v DB2_High_PctConnectionsExecutingTEC_CLASS :DB2_High_PctConnectionsExecuting ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctconnectionsexecuting : REAL;upperbound : REAL;


DB2Locks.barocDefines the following events as subclasses of DB2_Event:v DB2_High_LockEscalationsDelta


TEC_CLASS :DB2_High_LockEscalationsDelta ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lockescalationsdelta : REAL;upperbound : REAL;


v DB2_High_App_PctLockListUsedTEC_CLASS :DB2_High_App_PctLockListUsed ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;db2appid : STRING;db2appname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;pctlocklistused : REAL;


v DB2_High_AvgLockEscalationConnTEC_CLASS :DB2_High_AvgLockEscalationConn ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avglockescalationconn : REAL;upperbound : REAL;


v DB2_High_LockTimeoutsDeltaTEC_CLASS :DB2_High_LockTimeoutsDelta ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;locktimeoutsdelta : REAL;upperbound : REAL;



v DB2_High_DeadlocksDeltaTEC_CLASS :DB2_High_DeadlocksDelta ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;deadlocksdelta : REAL;upperbound : REAL;


v DB2_High_PctIntDeadlockedRollbacksTEC_CLASS :DB2_High_PctIntDeadlockedRollbacks ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctintdeadlockedrollbacks : REAL;upperbound : REAL;


v DB2_High_App_LockEscalationsTEC_CLASS :DB2_High_App_LockEscalations ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2appid : STRING;db2appname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lockescalations : REAL;upperbound : REAL;


v DB2_High_DB_PctLockListUsedTEC_CLASS :DB2_High_DB_PctLockListUsed ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctlocklistused : REAL;upperbound : REAL;



v DB2_High_AvgLocksHeldTEC_CLASS :DB2_High_AvgLocksHeld ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;avglocksheld : REAL;upperbound : REAL;


v DB2_High_App_DeadlocksTEC_CLASS :DB2_High_App_Deadlocks ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2appid : STRING;db2appname : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;appldeadlocks : REAL;


v DB2_High_PctDeadlockRollbacksTEC_CLASS :DB2_High_PctDeadlockRollbacks ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctdeadlockrollbacks : REAL;upperbound : REAL;


DB2LockWaits.barocDefines the following events as subclasses of DB2_Event:v DB2_High_PctApplsInLockWait

TEC_CLASS :DB2_High_PctApplsInLockWait ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;


application_class : STRING;application_label : STRING;application_oid : STRING;pctapplsinlockwait : REAL;upperbound : REAL;


v DB2_High_ApplLockWaitTimeTEC_CLASS :DB2_High_ApplLockWaitTime ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;applockwaittime : REAL;


v DB2_High_LockWaitsDeltaTEC_CLASS :DB2_High_LockWaitsDelta ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;lockwaitsdelta : REAL;upperbound : REAL;


DB2Logging.barocDefines the following events as subclasses of DB2_Event:v DB2_High_LogPageReads

TEC_CLASS :DB2_High_LogPageReads ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;logpagereads : REAL;upperbound : REAL;


v DB2_High_PctLogSpaceUsedBySecondary


TEC_CLASS :DB2_High_PctLogSpaceUsedBySecondary ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctlogspaceusedbysecondary : REAL;upperbound : REAL;


v DB2_High_LogPageWritesTEC_CLASS :DB2_High_LogPageWrites ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;logpagewrites : REAL;upperbound : REAL;


v DB2_High_PctLogSpaceUsedByPrimaryTEC_CLASS :DB2_High_PctLogSpaceUsedByPrimary ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctlogspaceusedbyprimary : REAL;upperbound : REAL;


v DB2_High_TotalLogInputOutputTEC_CLASS :DB2_High_TotalLogInputOutput ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;totloginputoutput : REAL;


v DB2_High_TotalSecondaryLogsInUse


TEC_CLASS :DB2_High_TotalSecondaryLogsInUse ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;totsecondarylogsinuse : REAL;upperbound : REAL;


DB2PackageCache.barocDefines the following events as subclasses of DB2_Event:v DB2_Low_PctPackageCacheHits

TEC_CLASS :DB2_Low_PctPackageCacheHits ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctpackagecachehits : REAL;lowerbound : REAL;


v DB2_High_PackageCacheLookupsTEC_CLASS :DB2_High_PackageCacheLookups ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;packagecachelookups : REAL;upperbound : REAL;


v DB2_High_PackageCacheInsertsTEC_CLASS :DB2_High_PackageCacheInserts ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;db2node : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;packagecacheinserts : REAL;upperbound : REAL;



DB2ReplicationCapture.barocDefines the following events as subclasses of DB2_Event:v DB2_High_CaptureLag

TEC_CLASS :DB2_High_CaptureLag ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;capturelag : REAL;upperbound : REAL;


v DB2_High_CaptureErrorsTEC_CLASS :DB2_High_CaptureErrors ISA DB2_EventDEFINES {db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;captureerrors : REAL;upperbound : REAL;


DB2SAPTablespaceUsageStatus.barocDefines the following events as subclasses of DB2_Event:v DB2_False_SAP_TablespaceNormalStatus

TEC_CLASS :DB2_False_SAP_TablespaceNormalStatus ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2tbspname : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;


v DB2_SAP_ReorgStatusTEC_CLASS :DB2_SAP_ReorgStatus ISA DB2_EventDEFINES {db2instance : STRING;db2schema : STRING;db2database : STRING;reorgstatus : STRING;db2tablename : STRING;



v DB2_High_SAP_SpaceUsedDMSTablespaceTEC_CLASS :DB2_High_SAP_SpaceUsedDMSTablespace ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;pctspaceduseddms : REAL;


v DB2_High_SAP_SpaceUsedSMSTablespaceTEC_CLASS :DB2_High_SAP_SpaceUsedSMSTablespace ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2tbspname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;spaceusedsms : REAL;


DB2Sorts.barocDefines the following events as subclasses of DB2_Event:v DB2_High_PctPipedSortReqRejected

TEC_CLASS :DB2_High_PctPipedSortReqRejected ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctpipedsortreqrejected : REAL;upperbound : REAL;


v DB2_High_PctSortOverflowedTEC_CLASS :DB2_High_PctSortOverflowed ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;application_class : STRING;application_label : STRING;


application_oid : STRING;upperbound : REAL;pctsortoverflowed : REAL;


v DB2_High_TotalSortsTEC_CLASS :DB2_High_TotalSorts ISA DB2_EventDEFINES {db2instance : STRING;db2database : STRING;db2node : STRING;db2appid : STRING;db2appname : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;upperbound : REAL;totsorts : REAL;


v DB2_High_PipedSortReqRejectedTEC_CLASS :DB2_High_PipedSortReqRejected ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pipedsortreqrejected : REAL;upperbound : REAL;


v DB2_Low_PctPipedSortHitsTEC_CLASS :DB2_Low_PctPipedSortHits ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctpipedsorthits : REAL;lowerbound : REAL;


v DB2_High_PctSortHeapUsedTEC_CLASS :DB2_High_PctSortHeapUsed ISA DB2_EventDEFINES {db2instancename : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctsortheapused : REAL;upperbound : REAL;



DB2SQLStatementActivity.barocDefines the following event as a subclass of DB2_Event:v DB2_High_PctFailedSqlStatements

TEC_CLASS :DB2_High_PctFailedSqlStatements ISA DB2_EventDEFINES {db2node : STRING;db2database : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;pctfailedsqlstatements : REAL;upperbound : REAL;


DB2TableApplyReplication.barocDefines the following events as subclasses of DB2_Event:v DB2_High_ApplySubscriptionLagTime

TEC_CLASS :DB2_High_ApplySubscriptionLagTime ISA DB2_EventDEFINES {db2database : STRING;db2applyid : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;applysubscriptionlagtime : REAL;upperbound : REAL;


v DB2_High_ApplyRequiresRefreshTEC_CLASS :DB2_High_ApplyRequiresRefresh ISA DB2_EventDEFINES {db2database : STRING;db2applyid : STRING;db2instance : STRING;application_class : STRING;application_label : STRING;application_oid : STRING;applyrequiresrefresh : REAL;


v DB2_ApplySubscriptionStatus_ErrorTEC_CLASS :DB2_ApplySubscriptionStatus_Error ISA DB2_EventDEFINES {db2database : STRING;db2applyid : STRING;db2instance : STRING;


application_class : STRING;application_label : STRING;application_oid : STRING;applysubscriptionstatus : REAL;


Collectively, these files implement the following class hierarchy:EVENT

TMW_Event (inherits from EVENT)DB2_Event (inherits from TMW_Event)The following files inherit from DB2_Event:

DB2AgentsDB2ApplyReplicationDB2BufferPoolDB2BufferPoolExtStorageDB2CatalogCacheDB2CpuUtilizationDB2CursorDB2DatabaseStatusDB2DirectIODB2FCMActivityDB2HostThroughputDB2InstanceStatusDB2LocksDB2LockWaitsDB2LoggingDB2PackageCacheDB2ReplicationCaptureDB2SAPTablespaceUsageStatusDB2SortsDB2SQLStatementActivityDB2TableApplyReplication

The definition for TMW_Event is provided in the class definition files for IBMTivoli Monitoring.

The definition for EVENT is provided in the class definition files for the TivoliEnterprise Console.


Appendix D. DB2 snapshot application ID formats

The DB2 snapshot application ID is an identifier that is generated when theapplication connects to the database at the database manager. The application ID isunique across the network.

The format used for the application ID depends on the communication protocolbetween the client and the server computers on which the database manager isrunning. Each of the formats consists of three parts separated by periods.

APPC

FormatNetwork.LU_Name.Application_inst

ExampleCAIBMTOR.OSFDBX0.930131194520

DetailsThe application ID that is generated for an application using the APPC protocol isa concatenation of the network name, the logical unit (LU) name, and the logicalunit-of-work ID (LUWID) instance number. In Systems Network Architecture(SNA), a logical unit is a port through which an end user access the SNA networkto communicate with another end user.

NetworkCan consist of a maximum of 8 characters.

LU_nameCan consist of a maximum of 8 characters.

Application_instCorresponds to the 12–decimal-character LUWID instance number.

IPX/SPX

FormatNetid.nodeid.Identifier

ExampleC11A8E5C.400011528250.1116183045

DetailsThe application ID that is generated for an application using the IPX/SPX protocolis a concatenation of a character network ID (8 hexadecimal characters), a node ID(12 hexadecimal characters), and a unique identifier for this particular application(Identifier).

495

IdentifierCorresponds to a 10-decimal-character timestamp of the formmmddhhmmss.

Local applications

Format*LOCAL.DB2_instance.Identifer

Example*LOCAL.DBINST1.930131214645

DetailsThe application ID that is generated for a local application is a concatenation of thestring *LOCAL, the name of the DB2 instance, and a unique identifier for thisparticular application.

NetBIOS

Format*NETBIOS.nname.Identifier

Example*NETBIOS.DBERE.930131214645

DetailsThe application ID generated for an application using the NetBIOS protocol is aconcatenation of the string *NETBIOS, the NetBIOS node name (nname) defined inthe client’s database configuration file, and a unique identifier for this particularapplication.

TCP/IP

Format*TCPIP.IPAddr.Identifier

Example*TCPIP.A12CF9E8.930131214645

DetailsThe application ID generated for an application using the TCP/IP protocol is aconcatenation of the string *TCPIP, the IP address in hexadecimal characters(maximum of 8), and a unique identifier for this particular application.

You can use “ECC_List_Applications” on page 304 to list the application IDs for allapplications that are currently active for a particular database.


Appendix E. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

497

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksIBM, the IBM logo, Tivoli, the Tivoli logo, Tivoli Enterprise Console, and TivoliManager for Domino are trademarks or registered trademarks of InternationalBusiness Machines Corporation or Tivoli Systems Inc. in the United States, othercountries, or both.

Lotus and Lotus Notes are trademarks of International Business MachinesCorporation and Lotus Development Corporation in the United States, othercountries, or both.

Microsoft and Windows NT are registered trademarks of Microsoft Corporation inthe United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Appendix E. Notices 499


Index

Aaccessibility ixAgent Creation Ratio too high indication 13

attributes 13occurrences and holes 14

Agent Creation Ratio too low indication 14attributes 14occurrences and holes 15

agentsmonitoring

setting up 266starting 269stopping 271

Application Average Sectors Per Direct Read too highindication 97


Application Average Sectors Per Direct Write too highindication 98


Application Deadlocks too high indication 138attributes 139occurrences and holes 139

application IDs 495Application Lock Wait Time too high indication 158


Application Percent Buffer Pool Hits too low indication 30attributes 31occurrences and holes 31sends events to Tivoli Business Systems Manager 31sends events to Tivoli Enterprise Console 31

Application Percent Index Buffer Pool Hits too lowindication 31

attributes 32occurrences and holes 32sends events to Tivoli Business Systems Manager 32sends events to Tivoli Enterprise Console 32

Application Total Sorts too high indication 203attributes 203occurrences and holes 203

applicationsforce all 293force specific 295list 304

Apply Full Refresh is required indication 231attributes 232occurrences and holes 232sends events to Tivoli Business Systems Manager 232sends events to Tivoli Enterprise Console 232

apply programstop 367

Apply Status is down indication 22attributes 22occurrences and holes 22sends events to Tivoli Business Systems Manager 22sends events to Tivoli Enterprise Console 22

Apply Subscription Lag Time too high indication 232attributes 233occurrences and holes 233

Apply Subscription Lag Time too high indication (continued)sends events to Tivoli Business Systems Manager 233sends events to Tivoli Enterprise Console 233

Apply Subscription Status is in error state indication 233attributes 234occurrences and holes 234sends events to Tivoli Business Systems Manager 234sends events to Tivoli Enterprise Console 234

Average Asynchronous Reads Per Pool Read too lowindication 33


Average Asynchronous Writes Per Pool Write too lowindication 34


Average Lock Escalations Per Connection too highindication 139


Average Locks Held Per Application too high indication 140attributes 141occurrences and holes 141

Average Pool Writes Per Pool Read too high indication 35attributes 35occurrences and holes 35

Average Synchronous IO Time too high indication 35attributes 36occurrences and holes 36

Average Synchronous Read Time too high indication 36attributes 37occurrences and holes 37

Average Synchronous Write Time too high indication 37attributes 38occurrences and holes 38

Bbackups

database 280list file 306

bash shell 2books

feedback vionline viordering vi

Bourne shell 2broadcast message 240buffer pool

alter size 277

CC shell 2Capture Errors too high indication 184


Capture Lag too high indication 185

X-1

Capture Lag too high indication (continued)attributes 185occurrences and holes 185sends events to Tivoli Business Systems Manager 185sends events to Tivoli Enterprise Console 185

capture programprune tables 371reading DB2 log 370reinitialize 374reread tables 373restart 375resume 375start 377stop 379suspend 381

CIM classes 383clearing events

Agent Creation Ratio too high indication 13Agent Creation Ratio too low indication 13Application Average Sectors Per Direct Read too high

indication 96Application Average Sectors Per Direct Write too high

indication 96Application Deadlocks too high indication 137Application Lock Wait Time too high indication 158Application Percent Buffer Pool Hits too low

indication 29Application Percent Index Buffer Pool Hits too low

indication 29Application Total Sorts too high indication 202Apply Full Refresh is required indication 231Apply Status is down indication 21Apply Subscription Lag Time too high indication 231Apply Subscription Status is in error state indication 231Average Asynchronous Reads Per Pool Read too low

indication 29Average Asynchronous Writes Per Pool Write too low

indication 29Average Lock Escalations Per Connection too high

indication 137Average Locks Held Per Application too high

indication 137Average Pool Writes Per Pool Read too high indication 29Average Synchronous IO Time too high indication 29Average Synchronous Read Time too high indication 29Average Synchronous Write Time too high indication 29Capture Errors too high indication 183Capture Lag too high indication 183Database Average Direct Read Time too high

indication 96Database Average Direct Write Time too high

indication 96Database Average Pool IO Time too high indication 29Database Average Pool Read Time too high indication 29Database Average Pool Write Time too high indication 29Database Average Sectors Per Direct Read too high

indication 96Database Average Sectors Per Direct Write too high

indication 96Database Backup past due indication 74Database in Restore Pending State indication 74Database Percent Buffer Pool Hits too low indication 29Database Percent Extended Storage Read Write ratio too

low indication 58Database Percent Index Buffer Pool Hits too low

indication 29DB2 Agent resource model 13

clearing events (continued)DB2 Apply Replication Status resource model 21DB2 Buffer Pool/Extended Storage resource model 58DB2 Buffer Pools resource model 29DB2 Catalog Cache resource model 64DB2 CPU Utilization resource model 68DB2 Database Activity resource model 74DB2 Direct IO resource model 96DB2 Fast Communication Manager resource model 114DB2 Host Throughput resource model 123DB2 Instance Status resource model 131DB2 Lock Waits resource model 158DB2 Locks and Deadlocks resource model 137DB2 Logging resource model 166DB2 Package Cache resource model 176DB2 Replication Capture resource model 183DB2 SAP Tablespace Usage/Status resource model 188DB2 Sorting resource model 202DB2 SQL Cursor Activity resource model 213DB2 SQL Statement Activity resource model 219DB2 Table Apply Replication resource model 231Deadlocks Delta too high indication 137Failed Subscriptions too high indication 21Gateway Connection Errors too high indication 74Gateway Connections Waiting for Host too high

indication 74Gateway Current Connections too high indication 74High Application Workload indication 13Host Throughput too low indication 123Host Time Per Statement too high indication 123Instance Status is down indication 131Lagging Subscriptions too high indication 21Lock Escalations by an Application too high

indication 137Lock Escalations Delta too high indication 137Lock Timeouts Delta too high indication 137Lock Waits Delta too high indication 158Log Page Reads too high indication 166Log Page Writes too high indication 166Most Recent Connect Response Time too high

indication 74Network Time Per Statement too high indication 123Open Blocking Cursors too high indication 213Open Cursors too high indication 213Package Cache Inserts too high indication 176Package Cache Lookups too high indication 176Percent Agents Waiting too high indication 13Percent Allocated Sort Heap too high indication 202Percent Applications In Lock Wait too high indication 158Percent Catalog Cache Hits too low indication 64Percent Connections Executing is too high indication 131Percent Connections Used too high indication 74Percent Deadlock Rollbacks too high indication 137Percent Failed Sql Statements too high indication 219Percent FCM Buffers In Use too high indication 114Percent FCM Connections In Use too high indication 114Percent Internal Deadlocked Rollbacks too high

indication 137Percent Lock List Used By An Application too high

indication 137Percent Lock List Used in a database too high

indication 137Percent Log Space Used By Primary Log too high

indication 166Percent Log Space Used By Secondary Log too high

indication 166

X-2 IBM Tivoli Monitoring for Databases: DB2: Reference Guide

clearing events (continued)Percent of Maximum FCM anchors In Use too high

indication 114Percent of Maximum FCM Buffers Used too high

indication 114Percent of Maximum FCM Connections Used too high

indication 114Percent Package Cache Hits too low indication 176Percent Piped Sort Hits too low indication 202Percent Piped Sort Requests Rejected too high

indication 202Percent Sorts Overflowed too high indication 202Percent Space Used in a DMS Tablespace too high

indication 74Percent Space Used in SAP DMS Tablespace too high

indication 188Piped Sort Requests Rejected too high indication 202SAP Table needs reorganizing indication 188SAP Tablespace Status is not normal indication 188Space Used in a SMS Tablespace too high indication 74Space Used in SAP SMS Tablespace too high

indication 188Tablespace Average Direct Read Time too high

indication 96Tablespace Average Direct Write Time too high

indication 96Tablespace Average Pool IO Time too high indication 29Tablespace Average Pool Read Time too high

indication 29Tablespace Average Pool Write Time too high

indication 29Tablespace Average Sectors Per Direct Read too high

indication 96Tablespace Average Sectors Per Direct Write too high

indication 96Tablespace Percent Buffer Pool Hits too low indication 29Tablespace Percent Extended Storage Read Write ratio too

low indication 58Tablespace Status is not normal indication 74Time Per Statement too high indication 123Total Log Input Output too high indication 166Total Secondary Logs In Use too high indication 166Total System CPU Time too high indication 68Total User CPU Time too high indication 68

commandsrunning 1running on UNIX 2running on Windows NT 2special characters 4syntax 4typeface 4

configurationget database entry 299get database manager entry 301get DB2 administration server 297reset database 332reset database manager 334reset DB2 administration server 331update database 357update database manager 360update DB2 administration server 355

counters, resetting 261Customer Support ix

Ddata, capture 377Database Average Direct Read Time too high indication 99


Database Average Direct Write Time too high indication 100attributes 100occurrences and holes 101

Database Average Pool IO Time too high indication 38attributes 39occurrences and holes 39

Database Average Pool Read Time too high indication 39attributes 40occurrences and holes 40

Database Average Pool Write Time too high indication 40attributes 41occurrences and holes 41

Database Average Sectors Per Direct Read too highindication 101


Database Average Sectors Per Direct Write too highindication 102


Database Backup past due indication 75attributes 75occurrences and holes 76

database connection services, listing directory 309Database in Restore Pending State indication 76


database managerget configuration entry 301update configuration entries 360

Database Percent Buffer Pool Hits too low indication 41attributes 42occurrences and holes 42sends events to Tivoli Business Systems Manager 42sends events to Tivoli Enterprise Console 42

Database Percent Extended Storage Read Write ratio too lowindication 59


Database Percent Index Buffer Pool Hits too lowindication 42


databasesactivate 275backup 280create sample 287deactivate 289delete sample 292force off connection 293get configuration entry 299invoke procedure 302reset configuration 332reset manager configuration 334restart 336services 275stop 289update configuration entries 357

Index X-3

DB2 administration servercreate 284delete 291get configuration 297get instance name 298list contents 312reset parameters 331start 344stop 350update configuration entries 355user account 342

DB2 Agentabout 12

DB2 Agent resource modelclearing events 13CLI example 20cycle time 12events generated 13logging properties 18managed resource 12message, Agent Creation Ratio too high indication 13message, Agent Creation Ratio too low indication 14message, High Application Workload indication 15message, Percent Agents Waiting too high indication 16occurrences and holes 14, 15, 16, 17parameters 18severity, default 13thresholds 17

DB2 Apply Replication resource modelcycle time 21

DB2 Apply Replication Statusabout 21

DB2 Apply Replication Status resource modelclearing events 21CLI example 26events generated 21indication sends events to Tivoli Enterprise Console 22,

23, 24logging properties 25managed resource 21message, Apply Status is down indication 22message, Failed Subscriptions too high indication 23message, Lagging Subscriptions too high indication 24occurrences and holes 22, 23, 24parameters 25severity, default 21thresholds 25

DB2 Audit Facilityconfigure 242

DB2 Buffer Pool/Extended Storageabout 58

DB2 Buffer Pool/Extended Storage resource modelclearing events 58CLI example 63cycle time 58events generated 58logging properties 62managed resource 58message, Database Percent Extended Storage Read Write

ratio too low indication 59message, Tablespace Percent Extended Storage Read Write

ratio too low indication 60occurrences and holes 59, 61parameters 61severity, default 58thresholds 61

DB2 Buffer Poolsabout 27

DB2 Buffer Pools resource modelclearing events 29CLI example 57cycle time 29events generated 29indication sends events to Tivoli Enterprise Console 31,

32, 42, 43, 47logging properties 53managed resource 29message, Application Percent Buffer Pool Hits too low

indication 30message, Application Percent Index Buffer Pool Hits too

low indication 31message, Average Asynchronous Reads Per Pool Read too

low indication 33message, Average Asynchronous Writes Per Pool Write too

low indication 34message, Average Pool Writes Per Pool Read too high

indication 35message, Average Synchronous IO Time too high

indication 36message, Average Synchronous Read Time too high

indication 37message, Average Synchronous Write Time too high

indication 37message, Database Average Pool IO Time too high

indication 38message, Database Average Pool Read Time too high

indication 39message, Database Average Pool Write Time too high

indication 40message, Database Percent Buffer Pool Hits too low

indication 41message, Database Percent Index Buffer Pool Hits too low

indication 42message, Tablespace Average Pool IO Time too high

indication 43message, Tablespace Average Pool Read Time too high

indication 44message, Tablespace Average Pool Write Time too high

indication 45message, Tablespace Percent Buffer Pool Hits too low

indication 46occurrences and holes 31, 32, 33, 34, 35, 36, 37, 38, 39, 40,

41, 42, 43, 44, 45, 46, 47parameters 52severity, default 29thresholds 47

DB2 Catalog Cacheabout 64

DB2 Catalog Cache resource modelclearing events 64CLI example 67cycle time 64events generated 64indication sends events to Tivoli Enterprise Console 65logging properties 66managed resource 64message, Percent Catalog Cache Hits too low

indication 64occurrences and holes 65parameters 66severity, default 64thresholds 65


DB2 CPU Utilizationabout 68

DB2 CPU Utilization resource modelclearing events 68CLI example 72cycle time 68events generated 68logging properties 71managed resource 68message, Total System CPU Time too high indication 68message, Total User CPU Time too high indication 70occurrences and holes 69, 70parameters 71severity, default 68thresholds 71

DB2 Database Activityabout 73

DB2 Database Activity resource modelclearing events 74CLI example 93cycle time 74events generated 74indication sends events to Tivoli Enterprise Console 77,

78, 80, 81, 84logging properties 88managed resource 74message, Database Backup past due indication 75message, Database in Restore Pending State indication 76message, Gateway Connection Errors too high

indication 77message, Gateway Connections Waiting for Host too high

indication 78message, Gateway Current Connections too high

indication 79message, Most Recent Connect Response Time too high

indication 80message, Percent Connections Used too high indication 81message, Percent Space Used in a DMS Tablespace too high

indication 82message, Space Used in a SMS Tablespace too high

indication 83message, Tablespace Status is not normal indication 84occurrences and holes 76, 77, 78, 79, 80, 81, 82, 83, 84parameters 86severity, default 74thresholds 84

DB2 Direct IOabout 95

DB2 Direct IO resource modelclearing events 96CLI example 111cycle time 96events generated 96logging properties 109managed resource 96message, Application Average Sectors Per Direct Read too

high indication 97message, Application Average Sectors Per Direct Write too

high indication 98message, Database Average Direct Read Time too high

indication 99message, Database Average Direct Write Time too high

indication 100message, Database Average Sectors Per Direct Read too

high indication 101message, Database Average Sectors Per Direct Write too

high indication 102

DB2 Direct IO resource model (continued)message, Tablespace Average Direct Read Time too high

indication 103message, Tablespace Average Direct Write Time too high

indication 104message, Tablespace Average Sectors Per Direct Read too

high indication 105message, Tablespace Average Sectors Per Direct Write too

high indication 106occurrences and holes 98, 99, 100, 101, 102, 103, 104, 105,

106, 107parameters 108severity, default 96thresholds 107

DB2 Fast Communication Managerabout 113

DB2 Fast Communication Manager resource modelclearing events 114CLI example 122cycle time 113events generated 114indication sends events to Tivoli Enterprise Console 115,

116, 117, 118, 119logging properties 121managed resource 113message, Percent FCM Buffers In Use too high

indication 115message, Percent FCM Connections In Use too high

indication 116message, Percent of Maximum FCM anchors In Use too

high indication 114message, Percent of Maximum FCM Buffers Used too high

indication 117message, Percent of Maximum FCM Connections Used too

high indication 118occurrences and holes 115, 116, 117, 118, 119parameters 120severity, default 114thresholds 119

DB2 Host Throughputabout 123

DB2 Host Throughput resource modelclearing events 123CLI example 130cycle time 123events generated 123indication sends events to Tivoli Enterprise Console 124,

125, 126, 127logging properties 129managed resource 123message, Host Throughput too low indication 124message, Host Time Per Statement too high indication 125message, Network Time Per Statement too high

indication 126message, Time Per Statement too high indication 127occurrences and holes 124, 125, 126, 127parameters 128severity, default 123thresholds 127

DB2 Instance Statusabout 131

DB2 Instance Status resource modelclearing events 131CLI example 135cycle time 131events generated 131indication sends events to Tivoli Enterprise Console 132

Index X-5

DB2 Instance Status resource model (continued)logging properties 134managed resource 131message, Instance Status is down indication 131message, Percent Connections Executing is too high

indication 132occurrences and holes 132, 133parameters 133severity, default 131thresholds 133

DB2 Lock Waitsabout 157

DB2 Lock Waits resource modelclearing events 158CLI example 164cycle time 157events generated 158indication sends events to Tivoli Enterprise Console 161logging properties 162managed resource 157message, Application Lock Wait Time too high

indication 158message, Lock Waits Delta too high indication 159message, Percent Applications In Lock Wait too high

indication 160occurrences and holes 159, 160, 161parameters 162severity, default 158thresholds 161

DB2 Locks and Deadlocksabout 136

DB2 Locks and Deadlocks resource modelclearing events 137CLI example 156cycle time 137events generated 137indication sends events to Tivoli Enterprise Console 146,

147logging properties 154managed resource 137message, Application Deadlocks too high indication 138message, Average Lock Escalations Per Connection too

high indication 139message, Average Locks Held Per Application too high

indication 140message, Deadlocks Delta too high indication 141message, Lock Escalations by an Application too high

indication 142message, Lock Escalations Delta too high indication 143message, Lock Timeouts Delta too high indication 144message, Percent Deadlock Rollbacks too high

indication 145message, Percent Internal Deadlocked Rollbacks too high

indication 146message, Percent Lock List Used By An Application too

high indication 147message, Percent Lock List Used in a database too high

indication 148occurrences and holes 139, 140, 141, 142, 143, 144, 145,

146, 147, 148, 149parameters 153severity, default 137thresholds 149

DB2 Loggingabout 165

DB2 Logging resource modelclearing events 166

DB2 Logging resource model (continued)CLI example 175cycle time 165events generated 166indication sends events to Tivoli Enterprise Console 169,

170logging properties 174managed resource 165message, Log Page Reads too high indication 166message, Log Page Writes too high indication 167message, Percent Log Space Used By Primary Log too high

indication 168message, Percent Log Space Used By Secondary Log too

high indication 169message, Total Log Input Output too high indication 170message, Total Secondary Logs In Use too high

indication 171occurrences and holes 167, 168, 169, 170, 171, 172parameters 173severity, default 166thresholds 172

DB2 Package Cacheabout 176

DB2 Package Cache resource modelclearing events 176CLI example 182cycle time 176events generated 176indication sends events to Tivoli Enterprise Console 179logging properties 181managed resource 176message, Package Cache Inserts too high indication 177message, Package Cache Lookups too high indication 178message, Percent Package Cache Hits too low


DB2 Replication Captureabout 183

DB2 Replication Capture resource modelclearing events 183CLI example 187cycle time 183events generated 183indication sends events to Tivoli Enterprise Console 184,

185logging properties 186managed resource 183message, Capture Errors too high indication 184message, Capture Lag too high indication 185occurrences and holes 184, 185parameters 186severity, default 183thresholds 186

DB2 SAP Tablespace Usage/Statusabout 188

DB2 SAP Tablespace Usage/Status resource modelclearing events 188CLI example 199cycle time 188events generated 188indication sends events to Tivoli Enterprise Console 189,

190, 191logging properties 194managed resource 188


DB2 SAP Tablespace Usage/Status resource model (continued)message, Percent Space Used in SAP DMS Tablespace too

high indication 189message, SAP Table needs reorganizing indication 190message, SAP Tablespace Status is not normal

indication 191message, Space Used in SAP SMS Tablespace too high

indication 192occurrences and holes 189, 190, 191, 192parameters 193severity, default 188thresholds 192

DB2 security servicestart 349stop 354

DB2 Sortingabout 201

DB2 Sorting resource modelclearing events 202CLI example 212cycle time 202events generated 202indication sends events to Tivoli Enterprise Console 205,

206, 208logging properties 210managed resource 202message, Application Total Sorts too high indication 203message, Percent Allocated Sort Heap too high

indication 204message, Percent Piped Sort Hits too low indication 205message, Percent Piped Sort Requests Rejected too high

indication 206message, Percent Sorts Overflowed too high

indication 207message, Piped Sort Requests Rejected too high

indication 208occurrences and holes 203, 204, 205, 206, 207, 208parameters 210severity, default 202thresholds 208

DB2 SQL Cursor Activityabout 213

DB2 SQL Cursor Activity resource modelclearing events 213CLI example 217cycle time 213events generated 213logging properties 216managed resource 213message, Open Blocking Cursors too high indication 214message, Open Cursors too high indication 215occurrences and holes 214, 215parameters 216severity, default 213thresholds 216

DB2 SQL Statement Activityabout 218

DB2 SQL Statement Activity resource modelclearing events 219CLI example 227cycle time 219events generated 219indication sends events to Tivoli Enterprise Console 220logging properties 221managed resource 219message, Percent Failed Sql Statements too high

indication 219

DB2 SQL Statement Activity resource model (continued)occurrences and holes 220parameters 220severity, default 219thresholds 220

DB2 Table Activityabout 228

DB2 Table Activity resource modelCLI example 230cycle time 228indications 228logging properties 229managed resource 228parameters 228thresholds 228

DB2 Table Apply Replicationabout 231

DB2 Table Apply Replication resource modelclearing events 231CLI example 236cycle time 231events generated 231indication sends events to Tivoli Enterprise Console 232,

233, 234logging properties 235managed resource 231message, Apply Full Refresh is required indication 232message, Apply Subscription Lag Time too high

indication 232message, Apply Subscription Status is in error state


DCS, See Database Connection Services 309Deadlocks Delta too high indication 141


directory names, notation ix

Ee-mail contact viiiECC_Activate_Database task 275ECC_Alter_Bufferpool task 277ECC_Apply_Start task 364ECC_Apply_Stop task 367ECC_Backup_Database task 280ECC_Broadcast_Message task 240ECC_Capture_Get_Log_Seq task 369ECC_Capture_Prune task 371ECC_Capture_Reinit task 373ECC_Capture_Resume task 375ECC_Capture_Start task 377ECC_Capture_Stop task 379ECC_Capture_Suspend task 381ECC_Configure_Audit task 242ECC_Create_Admin_Server task 284ECC_Create_Explain_Tables task 286ECC_Create_Import_Audit_Log task 248ECC_Create_Sample_Database task 287ECC_Deactivate_Database task 289ECC_Drop_Admin_Server task 291ECC_Drop_Sample_Database task 292ECC_Extract_Audit_Log task 251ECC_Flush_Audit_Buffer task 254

Index X-7

ECC_Force_All_Applications task 293ECC_Force_Applications task 295ECC_Get_Admin_Configuration task 297ECC_Get_Admin_Server_Instance task 298ECC_Get_Audit_Configuration task 255ECC_Get_Database_Configuration task 299ECC_Get_Database_Manager_Configuration task 301ECC_Invoke_Stored_Procedure task 302ECC_List_Applications task 304ECC_List_Backup_Recovery_File task 306ECC_List_DCS_Applications task 309ECC_List_Node_Directory task 312ECC_Prune_Audit_Log task 256ECC_Prune_Recovery_History_File task 314ECC_Purge_Audit_Log task 258ECC_Quiesce_Tablespaces task 317ECC_Rebind_All_Packages task 321ECC_Rebind_Package task 323ECC_Reorganize_Table task 325ECC_Reorgchk task 328ECC_Reset_Admin_Configuration task 331ECC_Reset_Audit_Configuration task 259ECC_Reset_Counters task 261ECC_Reset_Database_Configuration task 332ECC_Reset_Database_Manager_Configuration task 334ECC_Restart_Database task 336ECC_Run_Statistics task 338ECC_Send_Files_To_TEC_TMR task 262ECC_Send_Notice task 264ECC_Set_Admin_Server_ID task 342ECC_Set_Up_Monitoring_Agent task 266ECC_Start_Admin_Server task 344ECC_Start_Auditing task 268ECC_Start_DB2 task 345ECC_Start_DB2_NT_Security task 349ECC_Start_Monitoring_Agent task 269ECC_Stop_Admin_Server task 350ECC_Stop_Auditing task 270ECC_Stop_DB2 task 351ECC_Stop_DB2_NT_Security task 354ECC_Stop_Monitoring_Agent task 271ECC_TBSM_Discovery task 272ECC_Update_Admin_Configuration task 355ECC_Update_Database_Configuration task 357ECC_Update_Database_Manager_Configuration task 360endpoint

setting up the Tivoli environment on 3environment variables, notation ixevents generated





indication 29Application Total Sorts too high indication 202Apply Full Refresh is required indication 231Apply Status is down indication 21Apply Subscription Lag Time too high indication 231Apply Subscription Status is in error state indication 231

events generated (continued)Average Asynchronous Reads Per Pool Read too low










indication 29DB2 Agent resource model 13DB2 Apply Replication Status resource model 21DB2 Buffer Pool/Extended Storage resource model 58DB2 Buffer Pools resource model 29DB2 Catalog Cache resource model 64DB2 CPU Utilization resource model 68DB2 Database Activity resource model 74DB2 Direct IO resource model 96DB2 Fast Communication Manager resource model 114DB2 Host Throughput resource model 123DB2 Instance Status resource model 131DB2 Lock Waits resource model 158DB2 Locks and Deadlocks resource model 137DB2 Logging resource model 166DB2 Package Cache resource model 176DB2 Replication Capture resource model 183DB2 SAP Tablespace Usage/Status resource model 188DB2 Sorting resource model 202DB2 SQL Cursor Activity resource model 213DB2 SQL Statement Activity resource model 219DB2 Table Apply Replication resource model 231Deadlocks Delta too high indication 137Failed Subscriptions too high indication 21Gateway Connection Errors too high indication 74Gateway Connections Waiting for Host too high


indication 137


events generated (continued)Lock Escalations Delta too high indication 137Lock Timeouts Delta too high indication 137Lock Waits Delta too high indication 158Log Page Reads too high indication 166Log Page Writes too high indication 166Most Recent Connect Response Time too high






indication 166Percent of Maximum FCM anchors In Use too high













indication 96

events generated (continued)Tablespace Percent Buffer Pool Hits too low indication 29Tablespace Percent Extended Storage Read Write ratio too


explain tablescreate 286

FFailed Subscriptions too high indication 23


feedback about publications viiiFORCE commands 293, 295formats

application IDs 495

GGateway Connection Errors too high indication 77


Gateway Connections Waiting for Host too highindication 78


Gateway Current Connections too high indication 79attributes 79occurrences and holes 79

HHigh Application Workload indication 15


history file, recovery 314Host Throughput too low indication 124


Host Time Per Statement too high indication 125attributes 125occurrences and holes 125sends events to Tivoli Business Systems Manager 125sends events to Tivoli Enterprise Console 125

Iindications

Agent Creation Ratio too high 13Agent Creation Ratio too low 14Application Average Sectors Per Direct Read too high 97

Index X-9

indications (continued)Application Average Sectors Per Direct Write too high 98Application Deadlocks too high 138Application Lock Wait Time too high 158Application Percent Buffer Pool Hits too low 30Application Percent Index Buffer Pool Hits too low 31Application Total Sorts too high 203Apply Full Refresh is required 231Apply Status is down 22Apply Subscription Lag Time too high 232Apply Subscription Status is in error state 233Average Asynchronous Reads Per Pool Read too low 33Average Asynchronous Writes Per Pool Write too low 34Average Lock Escalations Per Connection too high 139Average Locks Held Per Application too high 140Average Pool Writes Per Pool Read too high 35Average Synchronous IO Time too high 35Average Synchronous Read Time too high 36Average Synchronous Write Time too high 37Capture Errors too high 184Capture Lag too high 185Database Average Direct Read Time too high 99Database Average Direct Write Time too high 100Database Average Pool IO Time too high 38Database Average Pool Read Time too high 39Database Average Pool Write Time too high 40Database Average Sectors Per Direct Read too high 101Database Average Sectors Per Direct Write too high 102Database Backup past due 75Database in Restore Pending State 76Database Percent Buffer Pool Hits too low 41Database Percent Extended Storage Read Write ratio too

low 59Database Percent Index Buffer Pool Hits too low 42Deadlocks Delta too high 141Failed Subscriptions too high 23Gateway Connection Errors too high 77Gateway Connections Waiting for Host too high 78Gateway Current Connections too high 79High Application Workload 15Host Throughput too low 124Host Time Per Statement too high 125Instance Status is down 131Lagging Subscriptions too high 24Lock Escalations by an Application too high 142Lock Escalations Delta too high 143Lock Timeouts Delta too high 144Lock Waits Delta too high 159Log Page Read too high 166Log Page Writes too high 167Most Recent Connect Response Time too high 80Network Time Per Statement too high 126Open Blocking Cursors too high 214Open Cursors too high 215Package Cache Inserts too high 177Package Cache Lookups too high 178Percent Agents Waiting too high 16Percent Allocated Sort Heap too high 204Percent Applications In Lock Wait too high 160Percent Catalog Cache Hits too low 64Percent Connections Used too high 81Percent Deadlock Rollbacks too high 145Percent Failed Sql Statements too high 219Percent FCM Buffers In Use too high 115Percent FCM Connections In Use too high 116Percent Internal Deadlocked Rollbacks too high 146Percent Lock List Used By An Application too high 147

indications (continued)Percent Lock List Used in a database too high 148Percent Log Space Used By Primary Log too high 168Percent Log Space Used By Secondary Log too high 169Percent of Maximum FCM anchors In Use too high 114Percent of Maximum FCM Buffers Used too high 117Percent of Maximum FCM Connections Used too

high 118Percent Package Cache Hits too low 179Percent Piped Sort Hits too low 205Percent Piped Sort Requests Rejected too high 206Percent Sorts Overflowed too high 207Percent Space Used in a DMS Tablespace too high 82Percent Space Used in SAP DMS Tablespace too high 189Piped Sort Requests Rejected too high 208SAP Table needs reorganizing 190SAP Tablespace Status is not normal 191Space Used in a SMS Tablespace too high 83Space Used in SAP SMS Tablespace too high 191Tablespace Average Direct Read Time too high 103Tablespace Average Direct Write Time too high 104Tablespace Average Pool IO Time too high 43Tablespace Average Pool Read Time too high 44Tablespace Average Pool Write Time too high 45Tablespace Average Sectors Per Direct Read too high 105Tablespace Average Sectors Per Direct Write too high 106Tablespace Percent Buffer Pool Hits too low 46Tablespace Percent Extended Storage Read Write ratio too

low 60Tablespace Status is not normal 84Time Per Statement too high 126Total Log Input Output too high 170Total Secondary Logs In Use too high 171Total System CPU Time too high 68Total User CPU Time too high 70

Instance Status is down indication 131attributes 132occurrences and holes 132sends events to Tivoli Business Systems Manager 132sends events to Tivoli Enterprise Console 132

instancesallocate resources 345get DB2 administration server 298reset ECC counter 261start 345stop 351

intent exclusive (IX) mode 320

KKorn shell 2

LLagging Subscriptions too high indication 24


listapplications 304backup and recovery file 306database connection services directory 309node directory 312

Lock Escalations by an Application too high indication 142attributes 142


Lock Escalations by an Application too high indication(continued)

occurrences and holes 143Lock Escalations Delta too high indication 143


Lock Timeouts Delta too high indication 144attributes 144occurrences and holes 145

Lock Waits Delta too high indication 159attributes 159occurrences and holes 160

Log Page Reads too high indication 166attributes 166occurrences and holes 167

Log Page Writes too high indication 167attributes 167occurrences and holes 168

log sequenceretrieve number 369retrieve time stamp 369

Mmanuals

feedback vionline viordering vi

messagesbroadcasting 240DB2 Agent resource model, Agent Creation Ratio too high

indication 13DB2 Agent resource model, Agent Creation Ratio too low

indication 14DB2 Agent resource model, High Application Workload

indication 15DB2 Agent resource model, Percent Agents Waiting too

high indication 16DB2 Apply Replication Status resource model, Apply

Status is down indication 22DB2 Apply Replication Status resource model, Failed

Subscriptions too high indication 23DB2 Apply Replication Status resource model, Lagging

Subscriptions too high indication 24DB2 Buffer Pool/Extended Storage resource model,

Database Percent Extended Storage Read Write ratio toolow indication 59

DB2 Buffer Pool/Extended Storage resource model,Tablespace Percent Extended Storage Read Write ratio toolow indication 60

DB2 Buffer Pools resource model, Application PercentBuffer Pool Hits too low indication 30

DB2 Buffer Pools resource model, Application PercentIndex Buffer Pool Hits too low indication 31

DB2 Buffer Pools resource model, Average AsynchronousReads Per Pool Read too low indication 33

DB2 Buffer Pools resource model, Average AsynchronousWrites Per Pool Write too low indication 34

DB2 Buffer Pools resource model, Average Pool Writes PerPool Read too high indication 35

DB2 Buffer Pools resource model, Average Synchronous IOTime too high indication 36

DB2 Buffer Pools resource model, Average SynchronousRead Time too high indication 37

DB2 Buffer Pools resource model, Average SynchronousWrite Time too high indication 37

messages (continued)DB2 Buffer Pools resource model, Database Average Pool

IO Time too high indication 38DB2 Buffer Pools resource model, Database Average Pool

Read Time too high indication 39DB2 Buffer Pools resource model, Database Average Pool

Write Time too high indication 40DB2 Buffer Pools resource model, Database Percent Buffer

Pool Hits too low indication 41DB2 Buffer Pools resource model, Database Percent Index

Buffer Pool Hits too low indication 42DB2 Buffer Pools resource model, Tablespace Average Pool

IO Time too high indication 43DB2 Buffer Pools resource model, Tablespace Average Pool

Read Time too high indication 44DB2 Buffer Pools resource model, Tablespace Average Pool

Write Time too high indication 45DB2 Buffer Pools resource model, Tablespace Percent Buffer

Pool Hits too low indication 46DB2 Catalog Cache resource model, Percent Catalog Cache

Hits too low indication 64DB2 CPU Utilization resource model, Total System CPU

Time too high indication 68DB2 CPU Utilization resource model, Total User CPU Time

too high indication 70DB2 Database Activity resource model, Database Backup

past due indication 75DB2 Database Activity resource model, Database in Restore

Pending State indication 76DB2 Database Activity resource model, Gateway

Connection Errors too high indication 77DB2 Database Activity resource model, Gateway

Connections Waiting for Host too high indication 78DB2 Database Activity resource model, Gateway Current

Connections too high indication 79DB2 Database Activity resource model, Most Recent

Connect Response Time too high indication 80DB2 Database Activity resource model, Percent

Connections Used too high indication 81DB2 Database Activity resource model, Percent Space Used

in a DMS Tablespace too high indication 82DB2 Database Activity resource model, Space Used in a

SMS Tablespace too high indication 83DB2 Database Activity resource model, Tablespace Status is

not normal indication 84DB2 Direct IO resource model, Application Average Sectors

Per Direct Read too high indication 97DB2 Direct IO resource model, Application Average Sectors

Per Direct Write too high indication 98DB2 Direct IO resource model, Database Average Direct

Read Time too high indication 99DB2 Direct IO resource model, Database Average Direct

Write Time too high indication 100DB2 Direct IO resource model, Database Average Sectors

Per Direct Read too high indication 101DB2 Direct IO resource model, Database Average Sectors

Per Direct Write too high indication 102DB2 Direct IO resource model, Tablespace Average Direct

Read Time too high indication 103DB2 Direct IO resource model, Tablespace Average Direct

Write Time too high indication 104DB2 Direct IO resource model, Tablespace Average Sectors

Per Direct Read too high indication 105DB2 Direct IO resource model, Tablespace Average Sectors

Per Direct Write too high indication 106DB2 Fast Communication Manager resource model, Percent

FCM Buffers In Use too high indication 115

Index X-11

messages (continued)DB2 Fast Communication Manager resource model, Percent

FCM Connections In Use too high indication 116DB2 Fast Communication Manager resource model, Percent

of Maximum FCM anchors In Use too highindication 114

DB2 Fast Communication Manager resource model, Percentof Maximum FCM Buffers Used too high indication 117

DB2 Fast Communication Manager resource model, Percentof Maximum FCM Connections Used too highindication 118

DB2 Host Throughput resource model, Host Throughputtoo low indication 124

DB2 Host Throughput resource model, Host Time PerStatement too high indication 125

DB2 Host Throughput resource model, Network Time PerStatement too high indication 126

DB2 Host Throughput resource model, Time Per Statementtoo high indication 127

DB2 Instance Status resource model, Instance Status isdown indication 131

DB2 Instance Status resource model, Percent ConnectionsExecuting is too high indication 132

DB2 Lock Waits resource model, Application Lock WaitTime too high indication 158

DB2 Lock Waits resource model, Lock Waits Delta too highindication 159

DB2 Lock Waits resource model, Percent Applications InLock Wait too high indication 160

DB2 Locks and Deadlocks resource model, ApplicationDeadlocks too high indication 138

DB2 Locks and Deadlocks resource model, Average LockEscalations Per Connection too high indication 139

DB2 Locks and Deadlocks resource model, Average LocksHeld Per Application too high indication 140

DB2 Locks and Deadlocks resource model, Deadlocks Deltatoo high indication 141

DB2 Locks and Deadlocks resource model, Lock Escalationsby an Application too high indication 142

DB2 Locks and Deadlocks resource model, Lock EscalationsDelta too high indication 143

DB2 Locks and Deadlocks resource model, Lock TimeoutsDelta too high indication 144

DB2 Locks and Deadlocks resource model, PercentDeadlock Rollbacks too high indication 145

DB2 Locks and Deadlocks resource model, Percent InternalDeadlocked Rollbacks too high indication 146

DB2 Locks and Deadlocks resource model, Percent LockList Used By An Application too high indication 147

DB2 Locks and Deadlocks resource model, Percent LockList Used in a database too high indication 148

DB2 Logging resource model, Log Page Reads too highindication 166

DB2 Logging resource model, Log Page Writes too highindication 167

DB2 Logging resource model, Percent Log Space Used ByPrimary Log too high indication 168

DB2 Logging resource model, Percent Log Space Used BySecondary Log too high indication 169

DB2 Logging resource model, Total Log Input Output toohigh indication 170

DB2 Logging resource model, Total Secondary Logs In Usetoo high indication 171

DB2 Package Cache resource model, Package Cache Insertstoo high indication 177

DB2 Package Cache resource model, Package CacheLookups too high indication 178

messages (continued)DB2 Package Cache resource model, Percent Package Cache

Hits too low indication 179DB2 Replication Capture resource model, Capture Errors

too high indication 184DB2 Replication Capture resource model, Capture Lag too

high indication 185DB2 SAP Tablespace Usage/Status resource model, Percent

Space Used in SAP DMS Tablespace too highindication 189

DB2 SAP Tablespace Usage/Status resource model, SAPTable needs reorganizing indication 190

DB2 SAP Tablespace Usage/Status resource model, SAPTablespace Status is not normal indication 191

DB2 SAP Tablespace Usage/Status resource model, SpaceUsed in SAP SMS Tablespace too high indication 192

DB2 Sorting resource model, Application Total Sorts toohigh indication 203

DB2 Sorting resource model, Percent Allocated Sort Heaptoo high indication 204

DB2 Sorting resource model, Percent Piped Sort Hits toolow indication 205

DB2 Sorting resource model, Percent Piped Sort RequestsRejected too high indication 206

DB2 Sorting resource model, Percent Sorts Overflowed toohigh indication 207

DB2 Sorting resource model, Piped Sort Requests Rejectedtoo high indication 208

DB2 SQL Cursor Activity resource model, Open BlockingCursors too high indication 214

DB2 SQL Cursor Activity resource model, Open Cursorstoo high indication 215

DB2 SQL Statement Activity resource model, Percent FailedSql Statements too high indication 219

DB2 Table Apply Replication resource model, Apply FullRefresh is required indication 232

DB2 Table Apply Replication resource model, ApplySubscription Lag Time too high indication 232

DB2 Table Apply Replication resource model, ApplySubscription Status is in error state indication 233

sending multiple 241sending to notice groups 264

migrationresource models 383

modesintent exclusive (IX) 320quiesce 319

Most Recent Connect Response Time too high indication 80attributes 80occurrences and holes 80sends events to Tivoli Business Systems Manager 80sends events to Tivoli Enterprise Console 80

NNetwork Time Per Statement too high indication 126


node directory, list 312notation

environment variables ixpath names ixtypeface ix

notices 497sending 264


Oonline publications viiOpen Blocking Cursors too high indication 214


Open Cursors too high indication 215attributes 215occurrences and holes 215

ordering publications viii

PPackage Cache Inserts too high indication 177


Package Cache Lookups too high indication 178attributes 178occurrences and holes 178

packagesrebind 321recreate without bind 323

parameter, reset 331parameters

endpoint 4host 4object 4

path names, notation ixPercent Agents Waiting too high indication 16


Percent Allocated Sort Heap too high indication 204attributes 204occurrences and holes 204

Percent Applications In Lock Wait too high indication 160attributes 160occurrences and holes 161sends events to Tivoli Business Systems Manager 161sends events to Tivoli Enterprise Console 161

Percent Catalog Cache Hits too low indication 64attributes 65occurrences and holes 65sends events to Tivoli Business Systems Manager 65sends events to Tivoli Enterprise Console 65

Percent Connections Executing is too high indicationattributes 132occurrences and holes 133

Percent Connections Used too high indication 81attributes 81occurrences and holes 81sends events to Tivoli Business Systems Manager 81sends events to Tivoli Enterprise Console 81

Percent Deadlock Rollbacks too high indication 145attributes 145occurrences and holes 146sends events to Tivoli Business Systems Manager 146sends events to Tivoli Enterprise Console 146

Percent Failed Sql Statements too high indication 219attributes 219occurrences and holes 220sends events to Tivoli Business Systems Manager 220sends events to Tivoli Enterprise Console 220

Percent FCM Buffers In Use too high indication 115attributes 115occurrences and holes 116sends events to Tivoli Business Systems Manager 116sends events to Tivoli Enterprise Console 116

Percent FCM Connections In Use too high indication 116attributes 116occurrences and holes 117sends events to Tivoli Business Systems Manager 117sends events to Tivoli Enterprise Console 117

Percent Internal Deadlocked Rollbacks too highindication 146


Percent Lock List Used By An Application too highindication 147


Percent Lock List Used in a database too high indication 148attributes 148occurrences and holes 149

Percent Log Space Used By Primary Log too highindication 168


Percent Log Space Used By Secondary Log too highindication 169


Percent of Maximum FCM anchors In Use too highindication 114


Percent of Maximum FCM Buffers Used too highindication 117


Percent of Maximum FCM Connections Used too highindication 118


Percent Package Cache Hits too low indication 179attributes 179occurrences and holes 179sends events to Tivoli Business Systems Manager 179sends events to Tivoli Enterprise Console 179

Percent Piped Sort Hits too low indication 205attributes 205occurrences and holes 205sends events to Tivoli Business Systems Manager 205sends events to Tivoli Enterprise Console 205

Percent Piped Sort Requests Rejected too high indication 206attributes 206occurrences and holes 206sends events to Tivoli Business Systems Manager 206sends events to Tivoli Enterprise Console 206

Percent Sorts Overflowed too high indication 207attributes 207occurrences and holes 207

Index X-13

Percent Space Used in a DMS Tablespace too highindication 82


Percent Space Used in SAP DMS Tablespace too highindication 189


Piped Sort Requests Rejected too high indication 208attributes 208occurrences and holes 208sends events to Tivoli Business Systems Manager 208sends events to Tivoli Enterprise Console 208

procedure, invoke 302prune

after capture stop 376capture table 371

publicationsfeedback vionline viordering vi

Qquiesce modes 319

Rrebinds

package 321without bind file 323

recovery history file, delete entries 314recovery, list file 306remote administration 331reorg, table 328reset, parameter 331resource models

DB2 Agent 12DB2 Apply Replication Status 21DB2 Buffer Pool/Extended Storage 58DB2 Buffer Pools 27DB2 Catalog Cache 64DB2 CPU Utilization 68DB2 Database Activity 73DB2 Direct IO 95DB2 Fast Communication Manager 113DB2 Host Throughput 123DB2 Instance Status 131DB2 Lock Waits 157DB2 Locks and Deadlocks 136DB2 Logging 165DB2 Package Cache 176DB2 Replication Capture 183DB2 SAP Tablespace Usage/Status 188DB2 Sorting 201DB2 SQL Cursor Activity 213DB2 SQL Statement Activity 218DB2 Table Activity 228DB2 Table Apply Replication 231migration 383

Ssample database

create 287delete 292

SAP Table needs reorganizing indication 190attributes 190occurrences and holes 190sends events to Tivoli Business Systems Manager 190sends events to Tivoli Enterprise Console 190

SAP Tablespace Status is not normal indication 191attributes 191occurrences and holes 191sends events to Tivoli Business Systems Manager 191sends events to Tivoli Enterprise Console 191

serversstart DB2 administration 344

services, database 275severity, default





indication 29Application Total Sorts too high indication 202Apply Full Refresh is required indication 231Apply Status is down indication 21Apply Subscription Lag Time too high indication 231Apply Subscription Status is in error state indication 231Average Asynchronous Reads Per Pool Read too low










indication 29


severity, default (continued)DB2 Agent resource model 13DB2 Apply Replication Status resource model 21DB2 Buffer Pool/Extended Storage resource model 58DB2 Buffer Pools resource model 29DB2 Catalog Cache resource model 64DB2 CPU Utilization resource model 68DB2 Database Activity resource model 74DB2 Direct IO resource model 96DB2 Fast Communication Manager resource model 114DB2 Host Throughput resource model 123DB2 Instance Status resource model 131DB2 Lock Waits resource model 158DB2 Locks and Deadlocks resource model 137DB2 Logging resource model 166DB2 Package Cache resource model 176DB2 Replication Capture resource model 183DB2 SAP Tablespace Usage/Status resource model 188DB2 Sorting resource model 202DB2 SQL Cursor Activity resource model 213DB2 SQL Statement Activity resource model 219DB2 Table Apply Replication resource model 231Deadlocks Delta too high indication 137Failed Subscriptions too high indication 21Gateway Connection Errors too high indication 74Gateway Connections Waiting for Host too high


indication 137Lock Escalations Delta too high indication 137Lock Timeouts Delta too high indication 137Lock Waits Delta too high indication 158Log Page Reads too high indication 166Log Page Writes too high indication 166Most Recent Connect Response Time too high






indication 166

severity, default (continued)Percent of Maximum FCM anchors In Use too high













indication 96Tablespace Percent Buffer Pool Hits too low indication 29Tablespace Percent Extended Storage Read Write ratio too


shellsbash 2Bourne 2C 2establishing the Tivoli environment in 3Korn shell 2UNIX 2

sizealter buffer pool 277

Space Used in a SMS Tablespace too high indication 83attributes 83occurrences and holes 83

Space Used in SAP SMS Tablespace too high indication 191attributes 192occurrences and holes 192

statistics, update for table 338

Ttables

calculate statistics 328explain 286reorganize 325

Index X-15

tables (continued)update statistics 338

Tablespace Average Direct Read Time too high indication 103attributes 103occurrences and holes 104

Tablespace Average Direct Write Time too high indication 104attributes 104occurrences and holes 105

Tablespace Average Pool IO Time too high indication 43attributes 44occurrences and holes 44

Tablespace Average Pool Read Time too high indication 44attributes 45occurrences and holes 45

Tablespace Average Pool Write Time too high indication 45attributes 46occurrences and holes 46

Tablespace Average Sectors Per Direct Read too highindication 105


Tablespace Average Sectors Per Direct Write too highindication 106


Tablespace Percent Buffer Pool Hits too low indication 46attributes 47occurrences and holes 47sends events to Tivoli Business Systems Manager 47sends events to Tivoli Enterprise Console 47

Tablespace Percent Extended Storage Read Write ratio too lowindication 60


Tablespace Status is not normal indication 84attributes 84occurrences and holes 84sends events to Tivoli Business Systems Manager 84sends events to Tivoli Enterprise Console 84

tablespacesquiesce 317

target table, refresh 364task libraries 237

data replication 363database 273monitor and administration 239

tasksECC_Activate_Database 275ECC_Alter_Bufferpool 277ECC_Apply_Start 364ECC_Apply_Stop 367ECC_Backup_Database 280ECC_Broadcast_Message 240ECC_Capture_Get_Log_Seq 369ECC_Capture_Prune 371ECC_Capture_Reinit 373ECC_Capture_Resume 375ECC_Capture_Start 377ECC_Capture_Stop 379ECC_Capture_Suspend 381ECC_Configure_Audit 242ECC_Configure_TEC_Classes 245ECC_Create_Admin_Server 284ECC_Create_Explain_Tables 286ECC_Create_Import_Audit_Log 248ECC_Create_Sample_Database 287ECC_Deactivate_Database 289

tasks (continued)ECC_Drop_Admin_Server 291ECC_Drop_Sample_Database 292ECC_Extract_Audit_Log 251ECC_Flush_Audit_Buffer 254ECC_Force_All_Applications 293ECC_Force_Applications 295ECC_Get_Admin_Configuration 297ECC_Get_Admin_Server_Instance 298ECC_Get_Audit_Configuration 255ECC_Get_Database_Configuration 299ECC_Get_Database_Manager_Configuration 301ECC_Invoke_Stored_Procedure 302ECC_List_Applications 304ECC_List_Backup_Recovery_File 306ECC_List_DCS_Applications 309ECC_List_Node_Directory 312ECC_Prune_Audit_Log 256ECC_Prune_Recovery_History_File 314ECC_Purge_Audit_Log 258ECC_Quiesce_Tablespaces 317ECC_Rebind_All_Packages 321ECC_Rebind_Package 323ECC_Reorganize_Table 325ECC_Reorgchk 328ECC_Reset_Admin_Configuration 331ECC_Reset_Audit_Configuration 259ECC_Reset_Counters 261ECC_Reset_Database_Configuration 332ECC_Reset_Database_Manager_Configuration 334ECC_Restart_Database 336ECC_Run_Statistics 338ECC_Send_Files_To_TEC_TMR 262ECC_Send_Notice 264ECC_Set_Admin_Server_ID 342ECC_Set_Up_Monitoring_Agent 266ECC_Start_Admin_Server 344ECC_Start_Auditing 268ECC_Start_DB2 345ECC_Start_DB2_NT_Security 349ECC_Start_Monitoring_Agent 269ECC_Stop_Admin_Server 350ECC_Stop_Auditing 270ECC_Stop_DB2 351ECC_Stop_DB2_NT_Security 354ECC_Stop_Monitoring_Agent 271ECC_TBSM_Discovery 272ECC_Update_Admin_Configuration 355ECC_Update_Database_Configuration 357ECC_Update_Database_Manager_Configuration 360

TECevent class

definition files 467Time Per Statement too high indication 126


Tivoli Business Systems Managerreceives events for Application Percent Buffer Pool Hits too

low indication 31receives events for Application Percent Index Buffer Pool

Hits too low indication 32receives events for Apply Full Refresh is required

indication 232receives events for Apply Status is down indication 22


Tivoli Business Systems Manager (continued)receives events for Apply Subscription Lag Time too high

indication 233receives events for Apply Subscription Status is in error

state indication 234receives events for Capture Errors too high indication 184receives events for Capture Lag too high indication 185receives events for Database in Restore Pending State

indication 77receives events for Database Percent Buffer Pool Hits too

low indication 42receives events for Database Percent Index Buffer Pool Hits

too low indication 43receives events for Failed Subscriptions too high

indication 23receives events for Gateway Connection Errors too high

indication 78receives events for Gateway Connections Waiting for Host

too high indication 78receives events for Host Throughput too low

indication 124receives events for Host Time Per Statement too high

indication 125receives events for Instance Status is down indication 132receives events for Lagging Subscriptions too high

indication 24receives events for Most Recent Connect Response Time

too high indication 80receives events for Network Time Per Statement too high

indication 126receives events for Percent Applications In Lock Wait too

high indication 161receives events for Percent Catalog Cache Hits too low

indication 65receives events for Percent Connections Used too high

indication 81receives events for Percent Deadlock Rollbacks too high

indication 146receives events for Percent Failed Sql Statements too high

indication 220receives events for Percent FCM Buffers In Use too high

indication 116receives events for Percent FCM Connections In Use too

high indication 117receives events for Percent Internal Deadlocked Rollbacks

too high indication 147receives events for Percent Log Space Used By Primary

Log too high indication 169receives events for Percent Log Space Used By Secondary

Log too high indication 170receives events for Percent of Maximum FCM anchors In

Use too high indication 115receives events for Percent of Maximum FCM Buffers Used

too high indication 118receives events for Percent of Maximum FCM Connections

Used too high indication 119receives events for Percent Package Cache Hits too low

indication 179receives events for Percent Piped Sort Hits too low

indication 205receives events for Percent Piped Sort Requests Rejected

too high indication 206receives events for Percent Space Used in SAP DMS

Tablespace too high indication 189receives events for Piped Sort Requests Rejected too high

indication 208

Tivoli Business Systems Manager (continued)receives events for SAP Table needs reorganizing

indication 190receives events for SAP Tablespace Status is not normal

indication 191receives events for Tablespace Percent Buffer Pool Hits too

low indication 47receives events for Tablespace Status is not normal

indication 84receives events for Time Per Statement too high

indication 127Tivoli Customer Support ixTivoli Enterprise Console

event classhierarchy 494

receives events for Application Percent Buffer Pool Hits toolow indication 31

receives events for Application Percent Index Buffer PoolHits too low indication 32

receives events for Apply Full Refresh is requiredindication 232

receives events for Apply Status is down indication 22receives events for Apply Subscription Lag Time too high

indication 233receives events for Apply Subscription Status is in error

state indication 234receives events for Capture Errors too high indication 184receives events for Capture Lag too high indication 185receives events for Database in Restore Pending State

indication 77receives events for Database Percent Buffer Pool Hits too

low indication 42receives events for Database Percent Index Buffer Pool Hits

too low indication 43receives events for Failed Subscriptions too high

indication 23receives events for Gateway Connection Errors too high

indication 78receives events for Gateway Connections Waiting for Host

too high indication 78receives events for Host Throughput too low

indication 124receives events for Host Time Per Statement too high

indication 125receives events for Instance Status is down indication 132receives events for Lagging Subscriptions too high

indication 24receives events for Most Recent Connect Response Time

too high indication 80receives events for Network Time Per Statement too high

indication 126receives events for Percent Applications In Lock Wait too

high indication 161receives events for Percent Catalog Cache Hits too low

indication 65receives events for Percent Connections Used too high

indication 81receives events for Percent Deadlock Rollbacks too high

indication 146receives events for Percent Failed Sql Statements too high

indication 220receives events for Percent FCM Buffers In Use too high

indication 116receives events for Percent FCM Connections In Use too

high indication 117receives events for Percent Internal Deadlocked Rollbacks

too high indication 147

Index X-17

Tivoli Enterprise Console (continued)receives events for Percent Log Space Used By Primary

Log too high indication 169receives events for Percent Log Space Used By Secondary

Log too high indication 170receives events for Percent of Maximum FCM anchors In

Use too high indication 115receives events for Percent of Maximum FCM Buffers Used

too high indication 118receives events for Percent of Maximum FCM Connections

Used too high indication 119receives events for Percent Package Cache Hits too low

indication 179receives events for Percent Piped Sort Hits too low

indication 205receives events for Percent Piped Sort Requests Rejected

too high indication 206receives events for Percent Space Used in SAP DMS

Tablespace too high indication 189receives events for Piped Sort Requests Rejected too high

indication 208receives events for SAP Table needs reorganizing

indication 190receives events for SAP Tablespace Status is not normal

indication 191receives events for Tablespace Percent Buffer Pool Hits too

low indication 47receives events for Tablespace Status is not normal

indication 84receives events for Time Per Statement too high

indication 127Tivoli Enterprise Console, configure with task 245Tivoli environment

establishing in a shell 3establishing on an endpoint 3establishing on UNIX 3establishing on Windows NT 3

Total Log Input Output too high indication 170attributes 170occurrences and holes 171

Total Secondary Logs In Use too high indication 171attributes 171occurrences and holes 172

Total System CPU Time too high indication 68attributes 69occurrences and holes 69

Total User CPU Time too high indication 70attributes 70occurrences and holes 70

UUNIX

running commands on 2setting up the Tivoli environment 3shell 2

usersforce off 293force off specific 295set DB2 administration server ID 342

Vvariables, notation for ix

WWindows NT

running commands on 2setting up the Tivoli environment 3

wruntask commandECC_Activate_Database task 275ECC_Alter_Bufferpool task 278ECC_Apply_Start task 364ECC_Apply_Stop task 367ECC_Backup_Database task 281ECC_Broadcast_Message task 240ECC_Capture_Get_Log_Seq task 369ECC_Capture_Prune task 371ECC_Capture_Reinit task 373ECC_Capture_Resume task 375ECC_Capture_Start task 378ECC_Capture_Stop task 379ECC_Capture_Suspend task 381ECC_Configure_Audit task 243ECC_Configure_TEC_Classes task 246ECC_Create_Admin_Server task 284ECC_Create_Explain_Tables task 286ECC_Create_Import_Audit_Log task 249ECC_Create_Sample_Database task 287ECC_Deactivate_Database task 289ECC_Drop_Admin_Server task 291ECC_Drop_Sample_Database task 292ECC_Extract_Audit_Log task 252ECC_Flush_Audit_Buffer task 254ECC_Force_All_Applications task 293ECC_Force_Applications task 295ECC_Get_Admin_Configuration task 297ECC_Get_Admin_Server_Instance task 298ECC_Get_Audit_Configuration task 255ECC_Get_Database_Configuration task 299ECC_Get_Database_Manager_Configuration task 301ECC_Invoke_Stored_Procedure task 302ECC_List_Applications task 304ECC_List_Backup_Recovery_File task 307ECC_List_DCS_Applications task 310ECC_List_Node_Directory task 312ECC_Prune_Audit_Log task 256ECC_Prune_Recovery_History_File task 315ECC_Purge_Audit_Log task 258ECC_Quiesce_Tablespaces task 318ECC_Rebind_All_Packages task 321ECC_Rebind_Package task 323ECC_Reorganize_Table task 325ECC_Reorgchk task 329ECC_Reset_Admin_Configuration task 331ECC_Reset_Audit_Configuration task 259ECC_Reset_Counters task 261ECC_Reset_Database_Configuration task 332ECC_Reset_Database_Manager_Configuration task 334ECC_Restart_Database task 336ECC_Run_Statistics task 339ECC_Send_Files_To_TEC_TMR task 262ECC_Send_Notice task 264ECC_Set_Admin_Server_ID task 342ECC_Set_Up_Monitoring_Agent task 266ECC_Start_Admin_Server task 344ECC_Start_Auditing task 268ECC_Start_DB2 task 346ECC_Start_DB2_NT_Security task 349ECC_Start_Monitoring_Agent task 269ECC_Stop_Auditing task 270ECC_Stop_DB2 task 352


wruntask command (continued)ECC_Stop_DB2_Admin_Server task 350ECC_Stop_DB2_NT_Security task 354ECC_Stop_Monitoring_Agent task 271ECC_TBSM_Discovery task 272ECC_Update_Admin_Configuration task 355ECC_Update_Database_Configuration task 358ECC_Update_Database_Manager_Configuration task 360

Index X-19


��

Printed in U.S.A.

SC23-4727-00

IBM Tivoli Monitoring for Databases: DB2: …publib.boulder.ibm.com/tividd/td/ITMD/SC23-4727-00/en_US/PDF/SC23...IBM posts all publications for this and all other Tivoli products,

Documents