Tivoli Manager for DB2 Reference Guide -...
744
Tivoli Manager for DB2 Reference Guide Version 2.1.0 GC32-0452-01
Transcript of Tivoli Manager for DB2 Reference Guide -...
Tivoli Manager for DB2Reference GuideVersion 2.1.0 GC32-0452-01
Tivoli Manager for DB2Reference GuideVersion 2.1.0 GC32-0452-01
Tivoli Manager for DB2 Reference Guide
Copyright Notice
© Copyright IBM Corporation 1998, 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. Nopart of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without priorwritten permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions ofany machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporationcopyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document isnot intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.
U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorporation.
Trademarks
IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, DB2, OS/2, RS/6000, Tivoli Enterprise Console, and TME are trademarks orregistered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, orboth.
Microsoft, Windows, Windows NT, Windows 2000, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.Notices
References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents orpending patent applications covering subject matter in this document. The furnishing of this document does not give you any licenseto these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xixWho Should Read This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
What This Document Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Conventions Used in this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Platform-specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Using this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How this Document is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Running Tivoli Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Command Line Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Using the waddmon Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Using the wruntask Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Using the wdb2tlib Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2. About Monitoring Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Using a Tivoli Manager for DB2 Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Adding a Monitor Using the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Adding a Monitor Using the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using Monitors That Have Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Using Monitors that Return Numeric Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3. DB2 Agents and Applications Monitors. . . . . . . . . . . . . . . . . . . . . . . 11conn: # of times agents are stolen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
conn: Application work load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
conn: Maximum associated agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
conn: Total system CPU time used by agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
conn: Total user CPU time used by agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
db: Agents associated with application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
db: Maximum agents associated with application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
db: Maximum coordinating agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
iiiTivoli Manager for DB2 Reference Guide
dbms: # of idle agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
dbms: # of times agents are stolen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
dbms: Agent creation ratio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
dbms: Agents registered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
dbms: Agents waiting for a token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
dbms: Maximum agents registered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
dbms: Maximum agents waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
dbms: Percent agents waiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
dbms: Percent total connections executing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 4. DB2 Basic Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35DB2 ECC monitoring communication agent status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
DB2 instance status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DB2 SNMP agent status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
User-defined OS command (numeric results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
User-defined OS command (string result). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
conn: Percent locklist space used by application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
db: # of applications connected currently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
db: # of applications executing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
db: # of binds/precomps attempted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
db: # of catalog cache heap full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
db: # of catalog cache inserts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
db: # of catalog cache lookups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
db: # of catalog cache overflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
db: # of commit statements attempted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
db: # of connects since 1st db connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
db: # of deadlocks detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
db: # of internal automatic rebinds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
db: # of internal commits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
db: # of internal rollbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
db: # of internal rows deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
db: # of internal rows inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
db: # of internal rows updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
db: # of lock timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
db: # of log pages read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
db: # of log pages written . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
iv Version 2.1.0
db: # of package cache inserts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
db: # of package cache lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
db: # of rollback statements attempted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
db: # of rows deleted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
db: # of rows inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
db: # of rows selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
db: # of rows updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
db: # of secondary logs allocated currently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
db: Avg lock escalations per connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
db: Internal rollback due to deadlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
db: Last backup timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
db: Log I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
db: Max # of concurrent connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
db: Max database heap allocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
db: Max primary log space used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
db: Max secondary log space used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
db: Max total log space used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
db: Percent connections used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
db: Percent internal rollbacks due to internal deadlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
db: Percent locklist space used by database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
db: Percent package cache hit ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
db: Percent used in primary log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
db: Percent used in secondary log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
db: Primary log space allocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
dbms: # of idle agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
dbms: # of local connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
dbms: # of local connections executing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
dbms: # of local databases with current connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
dbms: # of piped sorts accepted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
dbms: # of piped sorts requested . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
dbms: # of remote connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
dbms: # of remote connections executing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
dbms: Committed private memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
dbms: Last reset timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
dbms: Percent piped sort hit ratio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
vTivoli Manager for DB2 Reference Guide
dbms: Start database manager timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
dbpg: Data redistribution status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
dbpg: Data redistribution status for a nodegroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
dbpg: DB2 local nodes status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
dbpg: Partitioned database data redistribution status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
dbpg: Percentage differential in row distribution of a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
tbsp: Percent space used in DMS tablespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
tbsp: Space used in SMS tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
tbsp: Tablespace status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Chapter 5. DB2 Buffer Pool I/O Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117conn: # of direct reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
conn: # of direct writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
conn: Average # of sectors read per direct read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
conn: Average # of sectors written per direct write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
conn: Buffer pool time waited for prefetch (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
conn: Data page writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
conn: Index page reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
conn: Index page writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
conn: Logical data reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
conn: Percent buffer pool hit ratio, data+index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
conn: Percent buffer pool hit ratio, index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
conn: Percent package cache hit ratio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
conn: Pool read time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
conn: Pool write time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
conn: Total pool I/O time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
db: # of cleaners due to dirty threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
db: # of database files closed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
db: # of direct read requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
db: # of direct reads from database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
db: # of direct write requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
db: # of direct writes to database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
db: # of log space cleaners invoked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
db: # of page cleans in an interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
db: # of pages for each prefetch request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
db: # of pool reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
vi Version 2.1.0
db: # of pool writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
db: # of prefetch requests in an interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
db: # of synchronous I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
db: # of synchronous index reads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
db: # of synchronous index writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
db: # of synchronous reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
db: # of synchronous writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
db: # of victim page cleaners invoked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
db: Average # of async reads per pool read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
db: Average # of async writes per pool write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
db: Average # of pool writes per pool read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
db: Average # of sectors read per direct read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
db: Average # of sectors written per direct write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
db: Average direct read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
db: Average direct write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
db: Average pool I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
db: Average pool read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
db: Average pool write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
db: Average synchronous data read time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
db: Average synchronous data write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
db: Average synchronous I/O (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
db: Avg # of pages for each cleaner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
db: Buffer pool async data reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
db: Buffer pool async data writes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
db: Buffer pool async index reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
db: Buffer pool async index writes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
db: Buffer pool async read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
db: Buffer pool async write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
db: Buffer pool data logical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
db: Buffer pool data pages copied from extended storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
db: Buffer pool data pages copied to extended storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
db: Buffer pool data physical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
db: Buffer pool data writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
db: Buffer pool index logical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
db: Buffer pool index pages copied from extended storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
viiTivoli Manager for DB2 Reference Guide
db: Buffer pool index pages copied to extended storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
db: Buffer pool index physical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
db: Buffer pool index writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
db: Buffer pool I/Os per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
db: Buffer pool time waited for prefetch (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
db: Direct read time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
db: Direct write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
db: Extended storage read/write ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
db: Percent buffer pool hit ratio, data+index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
db: Percent buffer pool hit ratio, index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
db: Percent catalog cache hit ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
db: Synchronous read time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
db: Synchronous write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
db: Total direct I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
db: Total pool physical I/O (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
db: Total pool physical read (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
db: Total pool physical write (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
db: Total synchronous I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
dbp: # of FCM nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
dbp: Connection status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
dbp: FCM buffers currently free. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
dbp: FCM connection entries currently free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
dbp: FCM request blocks currently free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
dbp: Minimum FCM buffers free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
dbp: Minimum FCM connection entries free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
dbp: Minimum FCM message anchors free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
dbp: Minimum FCM request blocks free . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
dbp: Percent FCM buffers currently used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
dbp: Percent FCM connection entries currently used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
dbp: Percent FCM request blocks currently used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
dbp: Percent maximum FCM buffers used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
dbp: Percent maximum FCM connection entries used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
dbp: Percent maximum FCM message anchors used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
dbp: Percent maximum FCM request blocks used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
dbp: Total buffers received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
viii Version 2.1.0
dbp: Total buffers sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
tbsp: # of direct read requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
tbsp: # of direct reads from database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
tbsp: # of direct write requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
tbsp: # of direct writes to database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
tbsp: # of pool reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
tbsp: # of pool writes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
tbsp: # of synchronous index reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
tbsp: # of synchronous index writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
tbsp: # of synchronous reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
tbsp: # of synchronous writes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
tbsp: Average # of sectors read per direct read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
tbsp: Average # of sectors written per direct write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
tbsp: Average direct read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
tbsp: Average direct write time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
tbsp: Average pool I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
tbsp: Average pool read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
tbsp: Average pool write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
tbsp: Average synchronous data read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
tbsp: Average synchronous data write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
tbsp: Average synchronous I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
tbsp: Buffer pool async data reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
tbsp: Buffer pool async data writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
tbsp: Buffer pool async index reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
tbsp: Buffer pool async index writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
tbsp: Buffer pool async read time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
tbsp: Buffer pool async write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
tbsp: Buffer pool data logical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
tbsp: Buffer pool data pages copied from extended storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
tbsp: Buffer pool data pages copied to extended storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
tbsp: Buffer pool data physical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
tbsp: Buffer pool data physical writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
tbsp: Buffer pool index logical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
tbsp: Buffer pool I/Os per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
tbsp: Buffer pool index pages copied from extended storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
ixTivoli Manager for DB2 Reference Guide
tbsp: Buffer pool index pages copied to extended storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
tbsp: Buffer pool index physical reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
tbsp: Buffer pool index physical writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
tbsp: Direct read time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
tbsp: Direct write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
tbsp: Extended storage read/write ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
tbsp: File closed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
tbsp: Percent buffer pool hit ratio, data+index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
tbsp: Percent buffer pool hit ratio, index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
tbsp: Percent prefetch satisfied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
tbsp: Percent total I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
tbsp: Prefetch requests in an interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
tbsp: Synchronous read time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
tbsp: Synchronous write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
tbsp: Total direct I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
tbsp: Total pool physical I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
tbsp: Total pool physical read time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
tbsp: Total pool physical write time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
tbsp: Total synchronous I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
tbsp: Total synchronous I/O time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Chapter 6. DB2 Configuration Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313db: app_ctl_heap_sz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
db: ApplHeapSz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
db: avg_appls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
db: buffpage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
db: catalogcache_sz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
db: chngpgs_thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
db: dbheap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
db: locklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
db: logbufsz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
db: logprimary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
db: maxappls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
db: maxlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
db: mincommit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
db: newlogpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
x Version 2.1.0
db: num_iocleaners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
db: num_ioservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
db: pckcachesz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
db: Percent space used in databaseheap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
db: restore_pending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
db: seqdetect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
db: sortheap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
dbms: agentpri. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
dbms: aslheapsz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
dbms: fcm_num_anchors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
dbms: fcm_num_buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
dbms: fcm_num_connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
dbms: fcm_num_rqb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
dbms: max_agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
dbms: max_coordagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
dbms: maxcagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
dbms: Maximum idle agents in the agent pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
dbms: Minimum committed private memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
dbms: mon_heap_sz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
dbms: num_poolagents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
dbms: Percent private memory used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
dbms: query_heap_sz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
dbms: rqrioblk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
dbms: sheapthres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
dbms: sqlstmtsz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Chapter 7. DB2 Data Replication Relational Monitors . . . . . . . . . . . . . . . . . . 357DataJoiner status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Data replication Apply status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
SNA link status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
TCP/IP communication link status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
db: # of Apply lagging subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
db: Apply failed subscriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
db: Apply requires full refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
db: Apply subscriptions lag time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
db: Apply subscription status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
xiTivoli Manager for DB2 Reference Guide
db: Capture errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
db: Capture lag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
db: Capture pruning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Chapter 8. DB2 Locks and Deadlocks Monitors. . . . . . . . . . . . . . . . . . . . . . . . . 375conn: Deadlocks found during last interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
conn: Lock escalations during last interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
conn: Lock wait time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
conn: Lock waits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
conn: Locks held . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
conn: UOW lock wait time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
db: Applications in lock wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
db: Average lock wait time (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
db: Average locks held per application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
db: Deadlocks found during last interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
db: Lock escalations during last interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
db: Lock list in use (bytes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
db: Lock timeouts during last interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
db: Lock waits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
db: Lock waits in an interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
db: Locks held. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
db: Percent application in lock wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
db: Percent deadlock rollbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
db: Time waited on locks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
db: Total exclusive lock escalations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Chapter 9. DB2 Query Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405db: # of database tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
db: # of event monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
db: # of invalid triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
db: # of system tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
db: # of tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
db: # of tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
db: # of tablespaces with LONG data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
db: # of triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
db: # of user indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
db: # of views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
xii Version 2.1.0
db: User-defined SQL (numeric result) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
db: User-defined SQL (string result). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
table: # of rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
tbsp: # of tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
user: # of tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Chapter 10. DB2 SNMP Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423DB2 database state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
DB2 server accumulated connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
DB2 server current connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
DB2 server finished transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
DB2 server status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
DB2 server version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Maximum number of agents allowed to register at the same time . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Maximum number of agents registered at the same time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Total Logical bytes read by DB2 server for all active databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Total logical pages read by DB2 server for all active databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Total physical bytes read by DB2 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Total physical bytes written by DB2 server for all active databases. . . . . . . . . . . . . . . . . . . . . . . . . 447
Total physical pages written by DB2 server for all active databases . . . . . . . . . . . . . . . . . . . . . . . . 449
Total rows selected returned by DB2 server for all active databases . . . . . . . . . . . . . . . . . . . . . . . . 451
Total SQL statements handled by DB2 server for all active databases . . . . . . . . . . . . . . . . . . . . . . . 453
Total SQL statements received by DB2 server for all active databases . . . . . . . . . . . . . . . . . . . . . . 455
Chapter 11. DB2 Sort Work Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457conn: Application sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
conn: Sort time (s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
conn: Statement sorts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
db: Active sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
db: Average sort time (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
db: Percent sort overflowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
db: Sort heap allocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
db: Sort overflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
db: Total sort time (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
db: Total sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
dbms: Percent piped sorts rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
dbms: Percent sort heap allocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
xiiiTivoli Manager for DB2 Reference Guide
dbms: Post threshold sorts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
dbms: Sort heap allocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
dbms: Total piped sorts rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Chapter 12. DB2 SQL Statement Activity Monitors. . . . . . . . . . . . . . . . . . . . . . 479conn: Application section inserts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
conn: Application section lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
conn: Binds/precompiles attempted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
conn: Commits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
conn: DDL SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
conn: Dynamic SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
conn: Explicit commits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
conn: Explicit rollbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
conn: Failed SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
conn: Open block cursors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
conn: Open cursors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
conn: Percent DDL SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
conn: Percent UID SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
conn: Rollbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
conn: Rows deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
conn: Rows inserted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
conn: Rows selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
conn: Rows updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
conn: Select SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
conn: SQL requests since last commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
conn: Static SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
conn: Update/Insert/Delete SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
db: Committed statements per second. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
db: DDL SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
db: Dynamic SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
db: Failed SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
db: Percent DDL SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
db: Percent failed SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
db: Percent select SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
db: Percent UID SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
db: Rollbacks per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
xiv Version 2.1.0
db: Select SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
db: SQL statements per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
db: Static SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
db: Update/Insert/Delete SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Chapter 13. DB2 Table Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539db: Number of all invalid packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
db: Number of invalid SYSTEM packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
db: Number of invalid user packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
table: Overflow accesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
table: Reorg needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
table: Rows read per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
table: Rows written per second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Chapter 14. About Task Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553Running Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Chapter 15. Monitor and Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . 555Running Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
ECC_Broadcast_Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
ECC_Configure_TEC_Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
ECC_Reset_Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
ECC_Send_Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
ECC_Set_Up_Monitoring_Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
ECC_Start_DB2SNMP_Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
ECC_Start_Monitoring_Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
ECC_Stop_DB2SNMP_Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
ECC_Stop_Monitoring_Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Chapter 16. DB2 Database Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571Running Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
ECC_Activate_Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
ECC_Alter_Bufferpool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
ECC_Backup_Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
ECC_Create_Admin_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
ECC_Create_Explain_Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
ECC_Create_Sample_Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
ECC_Deactivate_Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
xvTivoli Manager for DB2 Reference Guide
ECC_Drop_Admin_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
ECC_Drop_Sample_Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
ECC_Force_All_Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
ECC_Force_Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
ECC_Get_Admin_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
ECC_Get_Admin_Server_Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
ECC_Get_Database_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
ECC_Get_Database_Manager_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
ECC_Invoke_Stored_Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
ECC_List_Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
ECC_List_Backup_Recovery_File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
ECC_List_DCS_Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
ECC_List_Node_Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
ECC_Prune_Recovery_History_File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
ECC_Quiesce_Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
ECC_Rebind_All_Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
ECC_Rebind_Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
ECC_Reorganize_Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
ECC_Reorgchk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
ECC_Reset_Admin_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
ECC_Reset_Database_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
ECC_Reset_Database_Manager_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
ECC_Restart_Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
ECC_Run_Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
ECC_Set_Admin_Server_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
ECC_Start_Admin_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
ECC_Start_DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
ECC_Start_DB2_NT_Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
ECC_Stop_Admin_Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
ECC_Stop_DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
ECC_Stop_DB2_NT_Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
ECC_Update_Admin_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
ECC_Update_Database_Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
ECC_Update_Database_Manager_Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Chapter 17. Data Replication Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
xvi Version 2.1.0
Running Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
ECC_Apply_Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
ECC_Apply_Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
ECC_Capture_Get_Log_Seq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
ECC_Capture_Prune . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
ECC_Capture_Reinit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
ECC_Capture_Resume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
ECC_Capture_Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
ECC_Capture_Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
ECC_Capture_Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Appendix A. DB2 Snapshot Application ID Formats . . . . . . . . . . . . . . . . . . . . 699APPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
IPX/SPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Local applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
NetBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Appendix B. Operator Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701Numeric Operator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
String Operator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Status Operator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .X-1
xviiTivoli Manager for DB2 Reference Guide
xviii Version 2.1.0
Preface
The Tivoli Manager for DB2 Reference Guide provides information about how to install anduse the Tivoli Manager for DB2® software and how to manage DB2 database resourcesthrough Tivoli.
Who Should Read This DocumentThis document is intended for system architects (during the planning stage) and systemadministrators and database administrators (for implementation and operation). Readersshould have an administrator-level understanding of the Windows® or UNIX® operatingsystem, Tivoli software, and DB2 software.
Prerequisite and Related DocumentsThese documents contain detailed information that can help you operate Tivoli Manager forDB2.
¶ Tivoli Framework User’s Guide
Provides information about the Tivoli environment.
¶ Tivoli Framework Planning and Installation Guide
Provides information about software and hardware requirements.
¶ Tivoli Framework Reference Guide
Provides information about Tivoli command line syntax, such as the winstall commandand the Tivoli command syntax.
¶ Tivoli Distributed Monitoring User’s Guide
Provides information about Tivoli distributed monitoring.
¶ Tivoli Enterprise Console User’s Guide
Provides information about using the Tivoli Enterprise Console (TEC).
¶ Tivoli Software Installation Service (SIS) User’s Guide, Version 3.6.1
Provides information about using SIS to install the Tivoli Manager for DB2 software.
¶ DB2 System Monitor Guide and Reference
Provides information about how to collect different kinds of information about databasesand the database manager. This book explains how to use the information to understanddatabase activity, improve performance, and determine the causes of problems.
¶ DB2 Administration Guide: Planning
Provides an overview of DB2 database concepts, information about design issues (suchas logical and physical database design), and a discussion of high availability.
¶ DB2 Administration Guide: Implementation
Provides information about DB2 implementation issues such as implementing yourdesign, accessing databases, auditing, backup, and recovery.
xixTivoli Manager for DB2 Reference Guide
What This Document ContainsThe Tivoli Manager for DB2 Reference Guide contains the following sections:
¶ Chapter 1, “Overview” on page 1
Provides an overview of the Tivoli Manager for DB2 product.
¶ Chapter 2, “About Monitoring Collections” on page 7
Provides an overview of the Tivoli Manager for DB2 monitoring collections.
¶ Chapter 3, “DB2 Agents and Applications Monitors” on page 11
Provides information about the monitors that manage a database manager’s agents andrelated applications.
¶ Chapter 4, “DB2 Basic Monitors” on page 35
Provides information about the monitors that manage general DB2 functions.
¶ Chapter 5, “DB2 Buffer Pool I/O Monitors” on page 117
Provides information about the monitors that manage the database buffer pool.
¶ Chapter 6, “DB2 Configuration Monitors” on page 313
Provides information about the monitors that manage the configuration parameters fordatabase managers and databases.
¶ Chapter 7, “DB2 Data Replication Relational Monitors” on page 357
Provides information about the monitors that manage the data replication activity fromthe DB2 DataPropagator Relational (DPROPR) component.
¶ Chapter 8, “DB2 Locks and Deadlocks Monitors” on page 375
Provides information about the monitors that manage the locks and deadlocks forapplications and databases.
¶ Chapter 9, “DB2 Query Monitors” on page 405
Provides information about the monitors that manage database objects.
¶ Chapter 10, “DB2 SNMP Monitors” on page 423
Provides information about the monitors that manage the DB2 Simple NetworkManagement Protocol (SNMP) subagent.
¶ Chapter 11, “DB2 Sort Work Monitors” on page 457
Provides information about the monitors that manage the database manager sort work.
¶ Chapter 12, “DB2 SQL Statement Activity Monitors” on page 479
Provides information about the monitors that manage Structured Query Language (SQL)statement activity.
¶ Chapter 13, “DB2 Table Monitors” on page 539
Provides information about the monitors that manage DB2 database tables.
¶ Chapter 14, “About Task Libraries” on page 553
Provides an overview of the Tivoli Manager for DB2 task libraries.
¶ Chapter 15, “Monitor and Administration Tasks” on page 555
Provides information about the tasks in the DB2ManagerAdminTasks library.
¶ Chapter 16, “DB2 Database Tasks” on page 571
xx Version 2.1.0
Provides information about the tasks in the DB2ManagerDatabaseTasks library. Thesetasks are used with DB2 administration and database manager functions.
¶ Chapter 17, “Data Replication Tasks” on page 677
Provides information about the tasks in the DB2ManagerReplicationTasks library.These tasks are used with DB2 Replication.
¶ Appendix A, “DB2 Snapshot Application ID Formats” on page 699
Provides information about the formats to be used for DB2 snapshot applicationidentifiers that are generated when an application connects to the database at thedatabase manager.
¶ Appendix B, “Operator Groups” on page 701
Provides information about the various operators used with Tivoli Manager for DB2.
Conventions Used in this DocumentThis document uses several typeface conventions for special terms and actions. Theseconventions have the following meanings:
Bold Commands, keywords, file names, authorization roles, URLs, or other informationthat you must use literally appear in bold. Names of windows, dialogs, and othercontrols also appear in bold.
<Italics>Variables and values that you provide appear in <bracketed italics>. Words andphrases that new or emphasized appear in italics.
MonospaceCode examples, output, and system messages appear in a monospace font.
This guide uses the UNIX convention for specifying environment variables and for directorynotation. When using the Windows command line, replace $variable with %variable% forenvironment variables, and replace each forward slash (/) with a backslash (\) in directorypaths.
Note: When using the bash shell on a Windows system, you can use the UNIX conventions.
Platform-specific InformationSee the Tivoli Manager for DB2 Release Notes for information about the supported platformversions on which Tivoli Manager for DB2 runs.
Accessing Publications OnlineThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide tosupport services (the Customer Support Handbook); frequently asked questions (FAQs); andtechnical information, including release notes, user’s guides, redbooks, and white papers.You can access Tivoli publications online at http://www.tivoli.com/support/documents/.The documentation for some products is available in PDF and HTML formats. Translateddocuments are also available for some products.
To access most of the documentation, you need an ID and a password. To obtain an ID foruse on the support Web site, go to http://www.tivoli.com/support/getting/.
xxiTivoli Manager for DB2 Reference Guide
Resellers should refer to http://www.tivoli.com/support/smb/index.html for moreinformation about obtaining Tivoli technical documentation and support.
Business Partners should refer to “Ordering Publications” for more information aboutobtaining Tivoli technical documentation.
Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of thefollowing telephone numbers:
¶ U.S. customers: (800) 879-2755
¶ Canadian customers: (800) 426-4968
Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:
¶ Send e-mail to [email protected].
¶ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.
Contacting Customer SupportIf you need support for this or any Tivoli product, contact Tivoli Customer Support in one ofthe following ways:
¶ Submit a problem management record (PMR) electronically from our Web site athttp://www.tivoli.com/support/reporting/. For information about obtaining supportthrough the Tivoli Customer Support Web site, go tohttp://www.tivoli.com/support/getting/.
¶ Submit a PMR electronically through the IBMLink™ system. For information aboutIBMLink registration and access, refer to the IBM Web page athttp://www.ibmlink.ibm.com.
¶ Send e-mail to [email protected].
¶ Customers in the U.S. can call 1-800-TIVOLI8 (1-800-848-6548).
¶ Customers outside the U.S. should refer to the Tivoli Customer Support Web site athttp://www.tivoli.com/support/locations.html for customer support telephone numbers.
When you contact Tivoli Customer Support, be prepared to provide the customer number foryour company so that support personnel can assist you more readily.
xxii Version 2.1.0
Overview
Tivoli Manager for DB2 provides the ability to manage and monitor DB2 databases byproviding extensions to the Tivoli Framework, Tivoli Distributed Monitoring, TivoliEnterprise Console, and Tivoli User Administration.
A monitor captures and returns information about a resource or application in the Tivolimanagement environment, such as the database status or whether or not a server is available.A task is an operation, such as backing up a database, that must be performed routinely onvarious endpoints and managed nodes throughout the management environment.
Using monitors and tasks included with Tivoli Manager for DB2, you can managedistributed DB2 computing resources effectively and to the granularity that you need. Theset of database management tasks enables you to define operations that can run on anymachine without consideration of platform type. These tasks automate repetitive databaseadministrator (DBA) tasks. You can define tasks once and then perform them on multipleservers and databases in a single action.
Using this DocumentThis section contains information about how to use this reference guide. It includes thefollowing information:
¶ How this document is organized
¶ How to use the desktop or command line interface (CLI)
How this Document is OrganizedThis document is organized alphabetically by monitoring collection and task. Each monitoror task is divided into the following sections:
¶ Description briefly defines the monitor or task.
¶ Authorization Role provides permissions that an administrator needs to run a monitoror task.
¶ DB2 Versions Supported is used when only a specific version of DB2 is supported bya monitor or task.
¶ Target Endpoints provides the Tivoli resources to which a monitor or task isdistributed.
¶ Desktop Data Entry Fields describes each field on a specific monitor or task dialog.
¶ Partial Program Syntax (for tasks only) provides the necessary arguments for runningtasks from the monitor with the wdb2tlib command. The Partial Program Syntaxcorresponds to the Desktop Data Entry Fields and includes definitions for the arguments.
1
1Tivoli Manager for DB2 Reference Guide
1.O
verview
¶ CLI Synopsis provides a partial CLI syntax for the waddmon and wruntaskcommands. The CLI Synopsis corresponds to the Desktop Data Entry Fields andincludes definitions for each of the arguments. For the full waddmon command syntax,refer to to the Tivoli Distributed Monitoring User’s Guide. For the full wruntaskcommand syntax, refer to the Tivoli Framework Reference Manual.
¶ Examples provides an example for configuring the monitor or task by using thewaddmon, wruntask, or wdb2tlib commands. The example includes any additionalinformation and arguments necessary for executing the commands.
¶ Default Thresholds and Actions (for monitors only) provides the default and actionthreshold values for the monitor (if any). These values are inserted when you click theAdd with Defaults button when configuring the monitor. For more information, see theTivoli Manager for DB2 User’s Guide.
¶ Usage Notes provides additional information about a monitor or task.
¶ See Also provides a list of related monitors and tasks.
Running Tivoli CommandsMost Tivoli commands are run within a shell on a managed node or on a Tivoli managementregion server. A shell is a command interpreter that enables the operating system to processcommands. You can run commands from a shell’s command line or include them in shellscripts, on either the UNIX or Windows operating system.
Before running Tivoli commands, you must set the Tivoli environment variables for theshell. The managed node or Tivoli management region server installation process suppliesthe scripts to set the Tivoli environment variables. The procedures to run these scripts aredescribed in “Setting the Tivoli Environment on UNIX” on page 3 and “Setting the TivoliEnvironment on Windows” on page 3.
A few Tivoli commands can run on an endpoint. To set the Tivoli environment variables onan endpoint, see “Establishing the Tivoli Environment on an Endpoint” on page 4.
You must also have the appropriate Tivoli authorization role for running each command. TheTivoli authorization role required for running a command is specified in the referenceinformation for the command.
Running Tivoli Commands on UNIXShells are provided with UNIX operating systems. Tivoli commands can run in the Bourne,Korn, C, and bash shells. The Bourne shell is considered the standard UNIX shell and isincluded with every UNIX system. The bash shell can be used on both UNIX and Windowssystems.
Running Tivoli Commands on WindowsWhen you install a Windows managed node or Windows Tivoli management region server,the installation process copies the bash shell executable file to the computer. The bash shellsupports many UNIX commands and UNIX command syntax; for example, the forwardslash (/) for the directory separator. The bash shell supports the features of the Bourne shellplus it has some extensions applicable only to the bash shell.
Note: You can use the Windows MS-DOS shell instead of the bash shell to run most Tivolicommands (after you set the Tivoli environment variables with the%SystemRoot%\system32\drivers\etc\Tivoli\setup_env command). However, some
2 Version 2.1.0
commands and Tivoli tasks may require a bash shell to run successfully. All examplesof Tivoli commands in Tivoli publications are shown using bash shell syntax.
Where to Find Additional Information about ShellsThe following lists include resources where you can find additional information about thevarious shells. These resources were available at the time the lists were created. The lists donot show all of the material that is available, and Tivoli does not provide opinions orrecommendations about any of these resources.
UNIX shells:
¶ 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.
¶ Portable Shell Programming: An Extensive Collection of Bourne Shell Examples byBruce Blinn. ISBN: 0-13-451494-7.
¶ Learning the Korn Shell (O’Reilly Nutshell handbook) by Bill Rosenblatt and MikeLoukides. ISBN: 1-56592-054-6.
¶ UNIX C Shell Desk Reference by Martin Arick. ISBN: 0-47-155680-7.
Bash shell:
¶ Learning the bash Shell (O’Reilly Nutshell handbook) by Cameron Newham and BillRosenblatt. ISBN: 1-56592-347-2.
¶ A Brief Introduction to the bash Shell by Jane Anna Langley.http://www.cs.ups.edu/acl/unix_talk/bash.html
¶ Bash FAQ (GNU documentation). http://www.delorie.com/gnu/docs/bash/FAQ
¶ Bash Reference Manual (GNU documentation).http://www.gnu.org/manual/bash/index.html
¶ bash command reference information (GNU documentation).http://www.delorie.com/gnu/docs/bash/bash.1.html
Establishing the Tivoli Environment within a ShellWhen you install a managed node or Tivoli management region server, the installationprocess supplies shell setup scripts. You use these scripts to set the environment variablesneeded for running Tivoli commands.
Setting the Tivoli Environment on UNIXThe following steps describe how to set the Tivoli environment within a UNIX shell:
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 WindowsThe following steps describe how to set the Tivoli environment and start a bash shell onWindows.
3Tivoli Manager for DB2 Reference Guide
1.O
verview
Note: The location of the setup scripts in the following steps assume that the default portnumber of 94 was set for the object dispatcher during the installation of a managednode or Tivoli management region server. If a non-default port number is used, theport number is part of the Tivoli subdirectory name. For example, if port 8613 isused, the setup_env.cmd command is located in the%SystemRoot%\system32\drivers\etc\Tivoli-8613 directory.
1. Log in to a Windows managed node or Tivoli management region server.
2. Open a command window.
3. Run the following command in the command window to set Tivoli environmentvariables:%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd
4. Run either of the following commands in the command window to start the bash shell:sh
—OR—bash
Establishing the Tivoli Environment on an EndpointWhen you install an endpoint, the installation process supplies setup scripts. You use thesescripts to set the environment variables needed for running Tivoli commands 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. Setup scripts for the differentendpoint operating systems are shown in Table 1.
Table 1. Setup Scripts for Operating SystemsOperating System Setup Script Location Setup Script Name
AIX, HP-UX, Solaris /etc/Tivoli/lcf/endpoint_label lcf_env.sh(for Bourne, Korn,and bash shells)orlcf_env.csh(for C shell)
OS/2 %bootdrive%\OS2\Tivoli\lcf\endpoint_label
lcf_env.cmd
Windows %SystemRoot%\Tivoli\lcf\endpoint_label lcf_env.cmd (for MS-DOS) or lcf_env.sh(for bash shell)
Command Line SyntaxThis document uses the following special characters to define the command syntax:
[ ] Identifies optional arguments. Arguments not enclosed in brackets are required.
... Indicates that you can specify multiple values for the previous argument. Separatemultiple values with a space, unless you are instructed otherwise.
| Indicates mutually exclusive arguments or responses. You can use the argument tothe left of the separator (|) or the argument to its right. You cannot use botharguments in a single use of the command.
4 Version 2.1.0
{ } Delimits a set of mutually exclusive arguments when one of the arguments isrequired. If the arguments are optional, they are enclosed in [ ] (brackets).
<variable>Indicates a variable response, such as the subscriber name or the name of thedatabase you want to monitor.
For example:
wsetfpprgs{–t type | –T type}[<keyword option...>] <fp_name>
In this example, the –t type and –T type arguments are mutually exclusive, so you must useone or the other. The <keyword_option> argument is an optional argument; you can specifyit more than once. The <fp_name> argument is required.
Using the waddmon CommandYou can create and run a monitor with the waddmon command. Each monitor description inthis document includes a section called CLI Synopsis that supplies the monitor-specificarguments for the waddmon command. If you want to supply additional arguments for thecommand, refer to the description of the waddmon command in the Tivoli DistributedMonitoring User’s Guide.
Each monitor description also includes a section called Examples that provides an exampleof how you can enter the waddmon command and the monitoring arguments at thecommand line. The example includes such necessary information as the monitoringcollection, the name of the monitor, and the name of the profile that contains the monitor.
Using the wruntask CommandYou can run a task from the command line with the wruntask command. Each taskdescription in this document includes a section called CLI Synopsis that supplies thearguments for the wruntask command. If you want to supply additional arguments for thecommand, refer to the description of the wruntask command in the Tivoli DistributedMonitoring User’s Guide.
Each task description also includes a section called Examples that provides an example ofhow you can enter the wruntask command and the task arguments at the command line.The example includes such necessary information as the name of the task, the name of thetask library, and the managed node on which to run the task.
Using the wdb2tlib CommandYou can run a task from the monitor with the wdb2tlib command. Each task description inthis document includes a section called CLI Synopsis that supplies the arguments for thewdb2tlib command.
Each task description also includes a section called Examples that provides an example ofhow you can enter the wdb2tlib command when configuring the monitor.
For more information about running tasks from a monitor, see the Tivoli Manager for DB2User’s Guide.
5Tivoli Manager for DB2 Reference Guide
1.O
verview
6 Version 2.1.0
About Monitoring Collections
The Tivoli Manager for DB2 monitoring collections provide more than 300 monitors thathelp you manage distributed DB2 resources (servers, databases, partitions, and partitiongroups) from a single entry point. Each collection is a group of monitors that manages adifferent aspect of your DB2 database. For example, the DB2 table monitoring collectioncontains monitors that monitor table row activity. In general, the Tivoli Manager for DB2monitoring collections are based on the various DB2 monitor groups (for information aboutthe DB2 monitor groups, see the DB2 System Monitor Guide and Reference for the versionof DB2 you are using). The eleven monitoring collections are as follows:
¶ DB2Manager Agents and Applications
¶ DB2Manager Basic
¶ DB2Manager Buffer Pool I/O
¶ DB2Manager Configuration
¶ DB2Manager Data Replication Relational
¶ DB2Manager Locks and Deadlocks
¶ DB2Manager Query
¶ DB2Manager SNMP
¶ DB2Manager Sort Work
¶ DB2Manager SQL Statement Activity
¶ DB2Manager Table
This chapter describes each monitoring collection and the monitors in that collection. Whena monitor name contains a prefix such as tbsp or db, the monitor returns information forthat specific DB2 object (for example, a DB2 tablespace or a DB2 database). The prefix alsoindicates the type of endpoint or target for that monitor. A managed resource is an entitythat Tivoli Manager for DB2 manages and is represented by an icon on the Tivoli desktop.
The prefixes and the type of target where you can run the monitor are listed in Table 2:
Table 2. Monitor TargetsPrefix DB2 Object Monitor Targets*
DB DBP DBG IN
conn: Application X X
db: Database, non-partitioned X X
dbms: Instance, non-partitioned X X X
2
7Tivoli Manager for DB2 Reference Guide
2.A
bo
ut
Mo
nito
ring
Co
llection
s
Table 2. Monitor Targets (continued)Prefix DB2 Object Monitor Targets*
DB DBP DBG IN
dbp: Database partition X
dbpg: Database partition group X
tbsp: Tablespace X X
table: Table X X
user: User X X X
None Any
*Monitor Targets: DB = database; DBP = DB2 partition; DBG = DB2partition group; IN = Instance (partitioned or non-partitioned)
You can use many of these monitors to refine DB2 configuration parameters for the databasemanager and its databases. For detailed information about configuration parameters, see theDB2 Administration Guide for the version of DB2 that you are using.
Using a Tivoli Manager for DB2 MonitorYou can use either the Tivoli desktop or the command line interface (CLI) to add or edit amonitor. To perform these actions, you need to know:
¶ The name of the profile where the monitors are stored. For information about profiles,see the Tivoli Manager for DB2 User’s Guide.
¶ The monitoring collection name for the collection that contains the monitor that youwant to use. For example, DB2Manager_Stmt_Monitors is the name for the DB2 SQLstatement activity monitoring collection.
The following sections briefly explain how to use the monitors in the monitoring collections.For detailed information about using the Tivoli Manager for DB2 monitors, see the TivoliManager for DB2 User’s Guide.
Adding a Monitor Using the Tivoli DesktopIn the Add Monitor to Tivoli Distributed Monitoring Profile dialog box, the names of themonitoring collections are listed in the Monitoring Collections scrolling list. If you select acollection name, the names of the monitors in that collection are listed in the MonitoringSources scrolling list.
If a particular monitor requires one or more arguments, you must specify a value for eachargument. You specify these values in the Monitor Arguments scrolling list of the AddMonitor to Tivoli Distributed Monitoring Profile dialog box.
Adding a Monitor Using the CLIYou can add a monitor using the CLI with the Tivoli Distributed Monitoring waddmoncommand. To add a monitor with this command, use the CLI name for the monitor andspecify values for any arguments the monitor requires.
For the syntax of the Tivoli Distributed Monitoring waddmon command, see the TivoliDistributed Monitoring User’s Guide.
8 Version 2.1.0
Using Monitors That Have DefaultsSome monitors have default thresholds, actions, and monitoring schedules. In this book,these defaults are listed in the descriptions for those monitors that have them. When addinga monitor for one of these monitors, you can click the Add With Defaults button in theAdd Monitor to Tivoli Distributed Monitoring Profile dialog to add the monitor withthese default values.
Note: Defaults work only when you are adding monitors from the Tivoli desktop.
For monitors that have default thresholds, the following default actions are provided:
Send Tivoli noticeSend a notice to the DB2 Sentry notice group.
Change iconUpdate the corresponding indicator collection.
None There is no default action for this threshold.
A threshold listed as N/A indicates there is no default threshold for that response level.
Some monitors have only default monitoring schedules and not default thresholds andactions. When you use these monitors, you must set the threshold values yourself becausethe appropriate thresholds depend on the particular database environment (for example, someconfiguration parameters depend on whether the database is on AIX or Windows). See theTivoli Manager for DB2 User’s Guide or the Tivoli Distributed Monitoring User’s Guide formore information about adding monitors with default values.
Unless otherwise noted, the monitors that you can add with defaults have a defaultmonitoring schedule to run the monitor every 60 minutes without any time restrictions.
Using Monitors that Return Numeric ValuesIf a monitor that returns a numeric value does not receive valid data from DB2, the monitorreturns one of two invalid data error numbers:
32767 If the monitor normally returns a positive number to represent valid data, it returns avalue of 32767 for invalid data.
-32767If the monitor normally returns 0 or a negative number to represent valid data, itreturns a value of −32767 for invalid data.
For example, if the conn: Percent buffer pool hit ratio, data + index monitor does notreceive a valid number from DB2 because no active DB2 application is running, the monitorreturns 32767 to represent invalid data.
9Tivoli Manager for DB2 Reference Guide
2.A
bo
ut
Mo
nito
ring
Co
llection
s
10 Version 2.1.0
DB2 Agents and Applications Monitors
The monitors in the DB2Manager_Agent_Monitors collection provide information about adatabase manager’s agents and their related applications. An agent is a process or thread thatcarries out the requests made by a client application. Each connected application is servedby exactly one coordinator agent and possibly by a set of subagents. Subagents are used forparallel SQL processing in partitioned databases and on SMP machines.
For each database transaction (unit of work) that occurs when the client is connected to adatabase, an agent requests permission from the database manager to process the transaction.The database manager grants permission by giving the agent a processing token. Only agentswith tokens are permitted to execute a unit of work against a database. The number oftokens available is controlled by the max_coordagents configuration parameter. If a token isnot available, the agent waits until one is available.
For additional information about DB2 agents and applications, see the DB2 System MonitorGuide and Reference for the version of DB2 that you are using.
Table 3 lists the monitors in this collection.
Table 3. DB2Manager Agents and Applications MonitorsDesktop Name CLI Name Returned Value
Format
conn: # of times agents are stolen connStolenAgents Numeric
conn: Application work load connApplWorkLoad Numeric
conn: Maximum associated agents connMaxAssoAgents Numeric
conn: Total system CPU time used byagents
connSystemCPUTime Numeric: seconds
conn: Total user CPU time used byagents
connUserCPUTime Numeric: seconds
db: Agents associated withapplication
dbAgentsAssoWithAppls Numeric
db: Maximum agents associated withapplication
dbMaxAgentsAssoWithAppls Numeric
db: Maximum coordinating agents dbMaxCoordAgent Numeric
dbms: # of idle agents dbmsTotalIdleAgents Numeric
dbms: # of times agents are stolen dbmsStolenAgents Numeric
dbms: Agent creation ratio dbmsAgentCreationRatio Numeric
dbms: Agents registered dbmsAgentsReg Numeric: ratio
dbms: Agents waiting for a token dbmsAgentsWaiting Numeric
3
11Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
Table 3. DB2Manager Agents and Applications Monitors (continued)Desktop Name CLI Name Returned Value
Format
dbms: Maximum agents registered dbmsHwmAgentsReg Numeric
dbms: Maximum agents waiting dbmsHwmAgentsWaiting Numeric
dbms: Percent agents waiting dbmsPctAgentsWait Numeric: percentage
dbms: Percent total connectionsexecuting
dbmsPctConnectionsExec Numeric: percentage
12 Version 2.1.0
conn: # of times agents are stolen
DescriptionReturns the number of times that agents are stolen from an application. When anotherapplication requires a new subagent and has no subagents in its associated agent pool, itsteals subagents from the agent pools of other applications.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnStolenAgents
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'connStolenAgents'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
13Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
Usage NotesUse the returned value to adjust the num_poolagents configuration parameter. If the numberof agents stolen from this application is high compared to normal operating levels, the valueof num_poolagents might be too low. When the agent pool size is too small, oneapplication might fill the pool with associated subagents. When another application requiresa new subagent and has no subagents in its associated agent pool, it steals subagents fromthe agent pools of other applications.
See AlsoDB2Manager Agents and Applications monitors: “conn: Application work load” on page 15DB2Manager Configuration monitors: “dbms: num_poolagents” on page 350
14 Version 2.1.0
conn: Application work load
DescriptionReturns the ratio of the maximum number of subagents associated with this application tothe number of agents that are stolen from the application by DB2 to work on a differentapplication.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnApplWorkLoad
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'connApplWorkLoad'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
15Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
Usage NotesUse the returned value to evaluate the load that this application places on the system. Anagent working for an application is associated with that application. After the agentcompletes the work for the application, it is placed in the agent pool as an idle agent, but itremains associated with the application. When the application requires an agent again, DB2searches the agent pool for an agent already associated with the application and assignswork to the associated agent.
If another application needs an agent, DB2 attempts to satisfy the request in the followingsequence:
1. Assigning an idle agent that is not associated with any application
2. Creating an agent if an idle agent is not available
3. Assigning an agent that is associated with another application
For example, if an agent cannot be created because the maximum number of agents has beenreached, DB2 assigns an idle agent associated with another application. This reassignedagent is called a stolen agent.
If the returned value is less than 1, you can redistribute the database to other nodes orincrease the num_poolagents configuration parameter to avoid the costs associated withfrequently creating and terminating agents. A returned value of 32767 (no agents werestolen), suggests that the num_poolagents configuration is set too high compared to normaloperating levels, and that some of the agents in the pool are rarely used and are wastingsystem resources.
See AlsoDB2Manager Agents and Applications monitors:“conn: Maximum associated agents” on page 17,“conn: # of times agents are stolen” on page 13DB2Manager Configuration monitors: “dbms: num_poolagents” on page 350
16 Version 2.1.0
conn: Maximum associated agents
DescriptionReturns the maximum number of subagents associated with the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnMaxAssoAgents
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Agent_Monitor' 'connMaxAssoAgents'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
17Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
Usage NotesIf the peak number of subagents is close to the num_poolagents configuration parameter,this can indicate that the workload for this DB2 node is too high compared to normaloperating levels.
See AlsoDB2Manager Configuration monitors: “dbms: num_poolagents” on page 350
18 Version 2.1.0
conn: Total system CPU time used by agents
DescriptionReturns the total system CPU time used by this application’s database manager agents.System CPU time represents the time, in seconds, spent in system calls. This monitor is notavailable for OS/2.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnSystemCPUTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'connSystemCPUTime'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
19Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
Usage NotesUse the returned value to identify applications or queries that consume large amounts ofCPU time. The returned value includes time spent in SQL and non-SQL statements, anyfenced user function (UDF), and stored procedures.
See AlsoNone
20 Version 2.1.0
conn: Total user CPU time used by agents
DescriptionReturns the total user CPU time used by this application’s database manager agents. UserCPU time represents time spent executing database manager code. This monitor is notavailable for OS/2.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnUserCPUTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Agent_Monitor' 'connUserCPUTime'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
21Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
Usage NotesUse the returned value to identify applications or queries that consume large amounts ofCPU time. The returned value includes time spent in SQL and non-SQL statements, anyfenced user function (UDF), and stored procedures.
See AlsoNone
22 Version 2.1.0
db: Agents associated with application
DescriptionReturns the number of agents associated with all applications that are connected to thedatabase at one time.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAgentsAssoWithAppls
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbAgentsAssoWithAppls'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the peak number of agents is close to the num_poolagents configuration parameter, theworkload for this DB2 node might be too high compared to normal operating levels.
See AlsoDB2Manager Configuration monitors: “dbms: num_poolagents” on page 350
23Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
db: Maximum agents associated with application
DescriptionReturns the maximum number of agents associated with all applications connected to thedatabase at one time.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbMaxAgentsAssoWithAppls
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbMaxAgentsAssoWithAppls'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the peak number of agents is close to the num_poolagents configuration parameter, thiscan indicate that the workload for this DB2 node is too high compared to normal operatinglevels.
See AlsoDB2Manager Configuration monitors: “dbms: num_poolagents” on page 350
24 Version 2.1.0
db: Maximum coordinating agents
DescriptionReturns the maximum number of coordinating agents working at one time since the firstconnection was established.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbMaxCoordAgent
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbMaxCoordAgent'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the peak number of coordinating agents represents too high a workload for this DB2 node,you can reduce the number that can concurrently execute a transaction by changing themaxcagents configuration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: maxcagents” on page 346
25Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
dbms: # of idle agents
DescriptionReturns the number of agents in the agent pool that are unassigned to an application and idlewithin the database manager instance during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsTotalIdleAgents
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsTotalIdleAgents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to help set the num_poolagents configuration parameter. Having idleagents available to service requests for agents can improve performance.
See AlsoDB2Manager Configuration monitors: “dbms: num_poolagents” on page 350
26 Version 2.1.0
dbms: # of times agents are stolen
DescriptionReturns the number of times that agents are stolen from all applications that are connectedto a database within the database manager instance.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsStolenAgents
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsStolenAgents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesAgents are stolen when an idle agent associated with an application is reassigned to work ona different application.
See AlsoNone
27Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
dbms: Agent creation ratio
DescriptionReturns the number of times that agents are created when there are no more free agentsavailable in the agent pools within the database manager instance. The value is defined asthe ratio of the number of agents created from pool to the number of agents assigned frompool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsAgentCreationRatio
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsAgentCreationRatio'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to adjust the num_poolagents configuration parameter. A low ratiosuggests that the num_poolagents configuration parameter is set too high, and that some ofthe agents in the pool are rarely used and are wasting system resources. A high ratio canindicate that the overall workload for this node is too high compared to normal operatinglevels. You can adjust the workload by lowering the maximum number of coordinationagents specified by the maxcagents configuration parameter, or by redistributing data amongthe nodes.
For more information, see the DB2 System Monitor Guide and Reference and the DB2Administration Guide for the version of DB2 that you are using.
See AlsoDB2Manager Configuration monitors: “dbms: num_poolagents” on page 350,“dbms: maxcagents” on page 346
28 Version 2.1.0
dbms: Agents registered
DescriptionReturns the number of agents registered in the database manager instance.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsAgentsReg
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsAgentsReg'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe number of registered agents is used to calculate the value for the dbms: Percent agentswaiting monitor.
The number of registered agents is always greater than or equal to the number of localdatabases with current connections. Each application has a dedicated agent to processdatabase requests within the database manager.
See AlsoDB2Manager Agents and Applications monitors:“dbms: Percent agents waiting” on page 33DB2Manager Basic monitors:“dbms: # of local databases with current connections” on page 94
29Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
dbms: Agents waiting for a token
DescriptionReturns the number of agents that are waiting for a token so that they can execute atransaction in the database manager.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsAgentsWaiting
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsAgentsWaiting'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe number of agents waiting for a token is used to calculate the value for the dbms:Percent agents waiting monitor.
Each application has a dedicated agent to process database requests within the databasemanager. Each agent must get a token before it can execute a transaction. If all availabletokens are being used, an agent waits until a token is available.
See AlsoDB2Manager Agents and Applications monitors:“dbms: Percent agents waiting” on page 33
30 Version 2.1.0
dbms: Maximum agents registered
DescriptionReturns the highest number of agents that the database manager has registered since theDB2 instance started.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsHwmAgentsReg
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsHwmAgentsReg'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you evaluate your setting of the max_agents configurationparameter. The value of max_agents is the maximum number of database manager agentsavailable at any given time to accept application requests. If the returned value from thismonitor is near the value for max_agents, you can increase the value for max_agents.
See AlsoDB2Manager Configuration monitors: “dbms: max_agents” on page 344
31Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
dbms: Maximum agents waiting
DescriptionReturns the highest number of agents that have waited for a token at the same time since thedatabase manager started.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsHwmAgentsWaiting
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsHwmAgentsWaiting'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you evaluate your setting of the maxcagents configurationparameter. The value of maxcagents is the maximum number of database manager agentsthat can concurrent execute a database manager transaction. By adjusting this parameter, youcan control the throughput on the system during periods of high simultaneous applicationactivity.
If the maxcagents parameter is set to its default value (−1), no agents should wait for atoken, and the value returned by this monitor should be zero.
See AlsoDB2Manager Configuration monitors: “dbms: max_agents” on page 344
32 Version 2.1.0
dbms: Percent agents waiting
DescriptionReturns the percentage of registered agents that are waiting to execute a transaction. Thevalue is defined as agents waiting for a token/maximum agents registered × 100.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPctAgentsWait
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsPctAgentsWait'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 4 shows the suggested threshold values for severity levels.
Table 4. dbmsPctAgentsWait Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage is high compared to normal operating levels, you can improve concurrencyin the database manager by increasing the dbms: maxcagents configuration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: max_agents” on page 344
33Tivoli Manager for DB2 Reference Guide
3.D
B2
Ag
ents
and
Ap
plicatio
ns
Mo
nito
rs
dbms: Percent total connections executing
DescriptionReturns the percentage of the maximum number of applications allowed that are connectedto a database and processing a unit of work (within the database manager instance) duringthe monitoring interval. The value is defined as number of applications/maximumapplications.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and nonpartitioned DB2InstanceManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPctConnectionsExec
Exampleswaddmon 'DB2Manager_Agent_Monitors' 'dbmsPctConnectionsExec'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 5 shows the suggested threshold values for severity levels.
Table 5. dbmsPctConnectionsExec Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage is close to 100%, you can increase the maximum number of coordinatingagents specified by maxcagents parameter or rebalance your workload.
See AlsoDB2Manager Configuration monitors: “dbms: maxcagents” on page 346
34 Version 2.1.0
DB2 Basic Monitors
The monitors in the DB2Manager_Basic_Monitors collection provide general informationand statistics about the following topics:
¶ Status of the database manager and the Tivoli Manager for DB2 monitoring system
¶ Catalog caching
¶ Database activity
¶ Database connections
¶ Deadlocks and lock escalations
¶ Instance piped sorts
¶ Logging
¶ Package caching
¶ Row operations in databases
Some database system monitors provide information about the Fast CommunicationManager (FCM). In a partitioned database environment, most communication betweendatabase partitions is handled by the FCM, which provides internodal communicationssupport. For more information about the FCM, see the DB2 Administration Guide for theversion of DB2 that you are using.
Table 6 lists the monitors in this collection:
Table 6. DB2Manager Basic MonitorsDesktop Name CLI Name Returned Value
Format
DB2 ECC monitoring communication agentstatus
DBTwoMonCommStatus Status: “up” or “down”
DB2 instance status DBTwoStatus Status: “up” or “down”
DB2 SNMP agent status DBTwoSnmpStatus Status: “up” or “down”
User-defined OS command (numericresults)
DBTwoSystemCmd Numeric
User-defined OS command (string result) DBTwoSystemCmdS String
conn: Percent locklist space used byapplication
connPctLocklistUsed Numeric: percentage
db: # of applications connected currently dbApplsCurCons Numeric
db: # of applications executing dbApplsInDbTwo Numeric
db: # of binds/precomps attempted dbBindsPrecompiles Numeric
4
35Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
Table 6. DB2Manager Basic Monitors (continued)Desktop Name CLI Name Returned Value
Format
db: # of catalog cache heap full dbCatCacheHeapFull Numeric
db: # of catalog cache inserts dbCatCacheInserts Numeric
db: # of catalog cache lookups dbCatCacheLookups Numeric
db: # of catalog cache overflows dbCatCacheOverflows Numeric
db: # of commit statements attempted dbCommitSqlStmts Numeric
db: # of connects since 1st db connect dbTotalCons Numeric
db: # of deadlocks detected dbDeadlocks Numeric
db: # of internal automatic rebinds dbIntAutoRebinds Numeric
db: # of internal commits dbIntCommits Numeric
db: # of internal rollbacks dbIntRollbacks Numeric
db: # of internal rows deleted dbIntRowsDeleted Numeric
db: # of internal rows inserted dbIntRowsInserted Numeric
db: # of internal rows updated dbIntRowsUpdated Numeric
db: # of lock timeouts dbLockTimeouts Numeric
db: # of log pages read dbLogReads Numeric
db: # of log pages written dbLogWrites Numeric
db: # of package cache inserts dbPkgCacheInserts Numeric
db: # of package cache lookups dbPkgCacheLookups Numeric
db: # of rollback statements attempted dbRollbackSqlStmts Numeric
db: # of rows deleted dbRowsDeleted Numeric
db: # of rows inserted dbRowsInserted Numeric
db: # of rows selected dbRowsSelected Numeric
db: # of rows updated dbRowsUpdated Numeric
db: # of secondary logs allocated currently dbSecLogsAllocated Numeric
db: Avg lock escalations per connection dbAvgLockEscalPerConn Numeric
db: Internal rollback due to deadlock dbIntDeadlockRollbacks Numeric
db: Last backup timestamp dbLastBackup String: local timestamp
db: Log I/O dbLogIo Numeric
db: Max # of concurrent connections dbConnectionsTop Numeric
db: Max database heap allocated dbDbHeapTop Numeric
db: Max primary log space used dbMaxPriLogSpaceUsed Numeric: bytes
db: Max secondary log space used dbSecLogUsedTop Numeric: bytes
db: Max total log space used dbTotLogUsedTop Numeric: bytes
db: Percent connections used dbPctConnUsed Numeric: percentage
db: Percent internal rollbacks due tointernal deadlocks
dbPctIntRbPerIntDeadlk Numeric: percentage
db: Percent locklist space used by database dbPctLocklistUsed Numeric: percentage
db: Percent package cache hit ratio dbPkgHitRatio Numeric: percentage
db: Percent used in primary log dbPctUsedInPriLog Numeric: percentage
db: Percent used in secondary log dbPctUsedInSecLog Numeric: percentage
36 Version 2.1.0
Table 6. DB2Manager Basic Monitors (continued)Desktop Name CLI Name Returned Value
Format
db: Primary log space allocated dbPriLogSpaceAlloc Numeric: bytes
dbms: # of idle agents dbmsIdleAgents Numeric
dbms: # of local connections dbmsLocalCons Numeric
dbms: # of local connections executing dbmsLocalConsInExec Numeric
dbms: # of local databases with currentconnections
dbmsConLocalDbases Numeric
dbms: # of piped sorts accepted dbmsPipedSortsAccepted Numeric
dbms: # of piped sorts requested dbmsPipedSortsRequested Numeric
dbms: # of remote connections dbmsRemConsIn Numeric
dbms: # of remote connections executing dbmsRemConsInExec Numeric
dbms: Committed private memory dbmsCommPrivateMem Numeric
dbms: Last reset timestamp dbmsLastReset String: local timestamp
dbms: Percent piped sort hit ratio dbmsPipedSortHitRatio Numeric: percentage
dbms: Start database manager timestamp dbmsDbTwostartTime String: local timestamp
dbpg: Data redistribution status dbpgNodegroupsRedistStatus Numeric
dbpg: Data redistribution status for anodegroup
dbpgNodegroupRedistStatus Numeric
dbpg: DB2 local nodes status dbpgNodeStatus Numeric
dbpg: Partitioned database dataredistribution status
dbpgRedistStatus Numeric
dbpg: Percentage differential in rowdistribution of a table
dbpgPercentDiffRowDistribution Numeric: percentage
tbsp: Percent space used in DMS tablespace tbspPctSpaceUsedDMS Numeric: percentage
tbsp: Space used in SMS tablespace tbspSpaceUsedSMS Numeric: bytes
tbsp: Tablespace status tbspStatus Numeric
37Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
DB2 ECC monitoring communication agent status
DescriptionChecks if the monitoring communication agent is up or down.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisDBTwoMonCommStatus
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'DBTwoMonCommStatus'"ManufacturingProfile"
Default Thresholds and ActionsTable 7 shows the default threshold values for severity levels.
Table 7. DBTwoMonCommStatus Response LevelsResponse Level Trigger When Default Actions
critical Never None
severe Never None
warning Matches ″down″ Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the monitoringcommunication agent is currently up or down. The monitoring communication agentcoordinates the communications between Tivoli Distributed Monitoring and DB2.
See AlsoNone
38 Version 2.1.0
DB2 instance status
DescriptionChecks if the DB2 instance is up or down.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Instance NameSpecifies the name of the DB2 server whose status you want.
CLI SynopsisDBTwoStatus
-a <DB2_instance_name>
The following briefly describes the argument for this monitor:
<DB2_instance_name>Specifies the name of the DB2 server whose status you want.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'DBTwoStatus'-a 'db2inst1'"ManufacturingProfile"
Default Thresholds and ActionsTable 8 shows the default threshold values for severity levels.
Table 8. DBTwoStatus Response LevelsResponse Level Trigger When Default Actions
critical Matches down Send Tivoli Notice; Change Icon
severe Never None
warning Never None
normal N/A None
always N/A None
39Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the DB2 instance iscurrently up or down.
See AlsoNone
40 Version 2.1.0
DB2 SNMP agent status
DescriptionChecks whether the DB2 Simple Network Management Protocol (SNMP) agent is up ordown. This monitor is not supported on Solaris.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisDBTwoSnmpStatus
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'DBTwoSnmpStatus'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the DB2 SNMP agentis currently up or down. The DB2 SNMP agent is a resident program that generates alerts toan SNMP manager and supplies information about the status of the DB2 server anddatabases.
See AlsoDB2Manager SNMP monitors: All
41Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
User-defined OS command (numeric results)
DescriptionRuns a user-defined operating system command at the specified destination. You enter anoperating system command and the path to where you want the command processed.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
OS commandSpecifies the operating system command or a shell script with the completeexecution path. For path separators, use a slash (/).
CLI SynopsisDBTwoSystemCmd
-a <OS_command>
The following briefly describes the argument for this monitor:
<OS_command>Specifies the operating system command or a shell script with the completeexecution path. For path separators, use a slash (/).
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'DBTwoSystemCmd'-a 'returnnumber'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe user-defined command is expected to return a numeric value.
See AlsoNone
42 Version 2.1.0
User-defined OS command (string result)
DescriptionRuns a user-defined operating system command at the specified destination. You enter anoperating system command and the path to where you want the command processed.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
OS commandSpecifies the operating system command or a shell script, with the completeexecution path. For path separators, use a slash (/).
CLI SynopsisDBTwoSystemCmdS
-a <OS_command>
The following briefly describes the argument for this monitor:
<OS_command>Specifies the operating system command or a shell script, with the completeexecution path. Use a slash (/) as the path separator.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'DBTwoSystemCmdS'-a 'returnstring'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe user-defined command is expected to return a string value.
See AlsoNone
43Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
conn: Percent locklist space used by application
DescriptionReturns the percentage of space used in the locklist by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPctLocklistUsed
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'connPctLocklistUsed'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
44 Version 2.1.0
Usage NotesUse the returned value to determine if this application is holding too much of the locklist. Ifan application holds too much of the locklist, other applications can experience lockescalations.
See AlsoDB2Manager Configuration monitors: “db: locklist” on page 322
45Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of applications connected currently
DescriptionReturns the number of applications that are currently connected to the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbApplsCurCons
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbApplsCurCons'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the level of application activity within the database andthe amount of system resource being used.
If the returned value is always the same as the maxappls configuration parameter (meaningactivity is high compared to normal operating levels and you are at the maximum number ofapplications allowed), you can increase the value of maxappls to allow more applications toconnect (if maxappls is less than the value of the max_agents configuration parameter).
If the returned value is always less than maxappls, application activity can be limited by thenumber of available database manager agents. In this case, you might be able to improveconcurrency by increasing the value of the max_agents configuration parameter. You mightalso need to adjust the maxlocks or locklist configuration parameters.
See AlsoDB2Manager Configuration monitors: “db: maxappls” on page 325, “dbms:max_agents” on page 344, “db: maxlocks” on page 326,“db: locklist” on page 322
46 Version 2.1.0
db: # of applications executing
DescriptionReturns the number of currently connected applications for which the database manager iscurrently processing a request.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbApplsInDbTwo
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbApplsInDbTwo'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value indicates the number of database manager tokens that are being used byapplications connected to the database.
See AlsoDB2Manager Agents and Applications monitors:“dbms: Agents waiting for a token” on page 30
47Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of binds/precomps attempted
DescriptionReturns the number of binds and precompiles that have been attempted in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbBindsPrecompiles
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbBindsPrecompiles'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high number of binds and precompiles compared to normal operating levels indicates ahigh level of activity within the database.
This value does not include the number of internal automatic rebinds performed by thedatabase, but it does include binds that occur as a result of the REBIND PACKAGEcommand.
See AlsoNone
48 Version 2.1.0
db: # of catalog cache heap full
DescriptionReturns the number of times that an insert into the catalog cache failed because of aheap-full condition in the database heap.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCatCacheHeapFull
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbCatCacheHeapFull'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe catalog cache draws its storage dynamically from the database heap. Even if the cachestorage has not reached its limit, inserts into the catalog cache can fail because a lack ofspace in the database heap.
If the returned value is not zero, increase the database heap size or reduce the catalog cachesize. You can increase the database heap size by increasing the dbheap configurationparameter. You can decrease the catalog cache size by decreasing the catalogcache_szconfiguration parameter.
See AlsoDB2Manager Configuration monitors: “db: catalogcache_sz” on page 319, “db: dbheap”on page 321
49Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of catalog cache inserts
DescriptionReturns the number of times that the system tried to insert table descriptor information intothe catalog cache.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCatCacheInserts
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbCatCacheInserts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is low compared to the number of catalog cache lookups, the catalogcache is performing well. If this value is high compared to the number of catalog cachelookups, you can increase the catalog cache size (catalogcache_sz) configuration parameter.
A large value is to be expected immediately following the first connection to the database.In addition, heavy execution of DDL SQL statements involving a table, view, or alias canalso increase this value.
This value also includes the number of times an insert failed because of catalog cacheoverflow and heap-full conditions.
See AlsoDB2Manager Configuration monitors: “db: catalogcache_sz” on page 319DB2Manager Basic monitors: “db: # of catalog cache heap full” on page 49
50 Version 2.1.0
db: # of catalog cache lookups
DescriptionReturns the number of times that the catalog cache was referenced to obtain table descriptorinformation.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCatCacheLookups
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbCatCacheLookups'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe catalog cache is referenced whenever a table, view, or alias name is processed duringthe compilation of an SQL statement. The returned value includes both successful andunsuccessful accesses to the catalog cache.
See AlsoNone
51Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of catalog cache overflows
DescriptionReturns the number of times that an insert into the catalog cache failed because the catalogcache was full.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCatCacheOverflows
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbCatCacheOverflows'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf this value is large, the catalog cache might be too small for the workload. Enlarging thecatalog cache can improve its performance. In addition, if the workload includes either ofthe following two conditions:
¶ Transactions that compile many SQL statements that reference many tables, views, andaliases in a single unit of work
¶ Binding of packages that contain many SQL statements that reference many tables,views, and aliases
You can improve performance of the catalog cache by compiling fewer SQL statements in asingle transaction (by issuing more commits or rollbacks) or by splitting packages so thatthey include fewer SQL statements.
See AlsoDB2Manager Configuration monitors: “db: catalogcache_sz” on page 319
52 Version 2.1.0
db: # of commit statements attempted
DescriptionReturns the total number of SQL COMMIT statements that were attempted.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCommitSqlStmts
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbCommitSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how the number of COMMIT statements changes over aperiod of time. A small rate of change can indicate that applications are not doing frequentcommits. Infrequent commits can lead to problems with logging and data concurrency.
The returned value is also used in calculating the returned value for the db: Committedstatements per second monitor.
See AlsoDB2Manager SQL Statement Activity monitors: “db: Committed statements per second”on page 525
53Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of connects since 1st db connect
DescriptionReturns the number of connections made to a database since the first database connection.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalCons
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbTotalCons'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to calculate the frequency at which applications connect to thedatabase (over the monitoring period). If this frequency is low compared to normal operatinglevels, you can perform one of the following actions:
¶ Use the ECC_Activate_Database task to activate the database before any applicationsconnect to the database. Activating the database starts up all necessary database services,so that the database is available for connection and use by any application.
¶ Set up the first connecting application to issue the ACTIVATE DATABASE commandbefore connecting to the database.
Activating the database before connecting applications can avoid the extra overhead that thefirst connection sometimes incurs (for example, initial buffer pool allocation). Subsequentconnections are then processed faster.
See AlsoDB2Manager Database tasks: “ECC_Activate_Database” on page 574DB2Manager Basic monitors: “dbms: Percent piped sort hit ratio” on page 101
54 Version 2.1.0
db: # of deadlocks detected
DescriptionReturns the total number of deadlocks that have occurred in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDeadlocks
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbDeadlocks'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high returned value compared to normal operating levels indicates that applications areexperiencing contention problems. These problems could be caused by the followingsituations:
¶ Lock escalations are occurring for the database.
¶ An application can be locking tables explicitly when system-generated row locks aresufficient.
¶ An application can be using an inappropriate isolation level when binding.
¶ Catalog tables are locked for repeatable read.
¶ Applications are getting the same locks in different orders, resulting in deadlock.
Try to resolve the problem by determining in which applications (or application processes)the deadlocks are occurring.
See AlsoNone
55Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of internal automatic rebinds
DescriptionReturns the number of automatic rebinds or recompiles that were attempted in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntAutoRebinds
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntAutoRebinds'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of database activity. Automatic rebinds are theinternal binds that the system performs when a package is invalidated. They can have asignificant impact on performance and should be minimized where possible.
See AlsoNone
56 Version 2.1.0
db: # of internal commits
DescriptionReturns the total number of commits initiated internally by the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntCommits
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntCommits'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into internal activity within the database. The returnedvalue is also used in calculating the returned value for the db: Committed statements persecond monitor.
See AlsoDB2Manager SQL Statement Activity monitors: “db: Committed statements per second”on page 525
57Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of internal rollbacks
DescriptionReturns the total number of rollbacks initiated internally by the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntRollbacks
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntRollbacks'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into internal activity within the database. The returnedvalue is also used in calculating the returned value for the db: Rollbacks per secondmonitor.
See AlsoDB2Manager SQL Statement Activity monitors: “db: Rollbacks per second” on page 533
58 Version 2.1.0
db: # of internal rows deleted
DescriptionReturns the number of rows deleted from the database as a result of internal activity.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntRowsDeleted
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntRowsDeleted'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into internal activity within the database. If thisactivity is high compared to normal operating levels, you can evaluate your table design todetermine if the referential constraints or triggers that you defined on your database arenecessary.
Internal row deletions can be a result of either of the following situations:
¶ Enforcement of an ON CASCADE DELETE referential constraint.
¶ Firing of a trigger.
See AlsoNone
59Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of internal rows inserted
DescriptionReturns the number of rows inserted into a database as a result of internal activity caused bytriggers.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntRowsInserted
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntRowsInserted'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into internal activity within the database. If thisactivity is high compared to normal operating levels, you can evaluate your design todetermine if you can alter it to reduce this activity.
See AlsoNone
60 Version 2.1.0
db: # of internal rows updated
DescriptionReturns the number of rows updated in the database as a result of internal activity.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntRowsUpdated
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntRowsUpdated'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into internal activity within the database. If thisactivity is high compared to normal operating levels, you can evaluate your table design todetermine if the referential constraints that you defined are necessary.
Internal update activity can be a result of either of the following situations:
¶ Enforcement of a referential constraint with the ON DELETE SET NULL rule.
¶ Firing of a trigger.
See AlsoNone
61Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of lock timeouts
DescriptionReturns the number of times that a request to lock an object timed out instead of beinggranted for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockTimeouts
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbLockTimeouts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you evaluate the setting for the locktimeout configurationparameter. If the returned value is high when compared to normal operating levels, youmight have an application that is holding locks for long durations. Use the DB2ManagerLocks and Deadlocks monitors to determine if an application has a problem.
If the returned value is low compared to normal operating levels, the locktimeout parametermight be set too high. In this case, your applications might take too long to obtain a lock.
If the value of the locktimeout parameter equals −1, lock timeout detection is turned off.For online transaction processing (OLTP) environments, start with locktimeout at 30seconds. For query-only environments, start with locktimeout greater than 30 seconds.
See AlsoDB2Manager Locks and Deadlocks monitors: All
62 Version 2.1.0
db: # of log pages read
DescriptionReturns the number of log pages read from disk by the DB2 logging system.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLogReads
Exampleswaddmon 'DB2_Basic_Monitors' 'dbLogReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value with values from an operating system monitor to quantify the amountof input and output on a device that is attributable to activity from the database.
See AlsoDB2Manager Basic monitors: “db: Log I/O” on page 76
63Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of log pages written
DescriptionReturns the number of log pages written to disk by the DB2 logging system.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLogWrites
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbLogWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value with values from an operating system monitor to quantify the amountof input and output on a device that is attributable to activity from the database.
See AlsoDB2Manager Basic monitors: “db: Log I/O” on page 76
64 Version 2.1.0
db: # of package cache inserts
DescriptionReturns the number of times that a section had to be loaded into the package cache becausean application found that the section it wanted was not in the package cache.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPkgCacheInserts
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPkgCacheInserts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is used with the number of package cache lookups to calculate the package cachehit ratio.
See AlsoDB2Manager Basic monitors: “db: Percent package cache hit ratio” on page 85
65Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of package cache lookups
DescriptionReturns the number of times that an application looked for a section in the package cache.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPkgCacheLookups
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPkgCacheLookups'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is used with the number of package cache inserts to calculate the package cachehit ratio.
See AlsoDB2Manager Basic monitors: “db: Percent package cache hit ratio” on page 85
66 Version 2.1.0
db: # of rollback statements attempted
DescriptionReturns the total number of SQL ROLLBACK statements that were attempted for thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRollbackSqlStmts
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbRollbackSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the amount of activity in the database and the amountof conflict between applications on the database. In general, try to minimize the number ofrollbacks, because higher rollback activity results in lower throughput for the database.
The returned value is also used in calculating the returned value for the db: Rollbacks persecond monitor.
See AlsoDB2Manager SQL Statement Activity monitors: “db: Rollbacks per second” on page 533
67Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of rows deleted
DescriptionReturns the number of row deletions attempted for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRowsDeleted
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbRowsDeleted'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into the current level of activity within the database.This count does not include the attempts counted in the db: # of internal rows deletedmonitor.
See AlsoDB2Manager Basic monitors: “db: # of internal rows deleted” on page 59
68 Version 2.1.0
db: # of rows inserted
DescriptionReturns the number of row insertions attempted for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRowsInserted
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbRowsInserted'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into the current level of activity within the database.This count does not include the attempts counted in the db: # of internal rows insertedmonitor.
See AlsoNone
69Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of rows selected
DescriptionReturns the number of rows that were selected and returned to an application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRowsSelected
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbRowsSelected'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into the current level of activity within the database.This value does not include a count of rows read for actions such as COUNT(*) or joins.
See AlsoNone
70 Version 2.1.0
db: # of rows updated
DescriptionReturns the number of row updates attempted for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRowsUpdated
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbRowsUpdated'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into the current level of activity within the database.This count does not include the attempts counted in the db: # of internal rows updatedmonitor. However, rows that are updated by more than one update statement are counted foreach update.
See AlsoDB2Manager Basic monitors: “db: # of internal rows updated” on page 61
71Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: # of secondary logs allocated currently
DescriptionReturns the total number of secondary log files that are currently being used for thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSecLogsAllocated
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbSecLogsAllocated'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Percent used insecondary log monitor. This value is zero if the database does not have any secondary logfiles (if none are defined or if log retention is enabled).
See AlsoDB2Manager Basic monitors: “db: Percent used in secondary log” on page 88
72 Version 2.1.0
db: Avg lock escalations per connection
DescriptionReturns the average number of lock escalations per connection.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgLockEscalPerConn
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbAvgLockEscalPerConn'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high returned value compared to normal operating levels indicates that the locklist spacethat is available to applications keeps filling up. This situation results in escalations andleads to excessive lock waits for your applications. Check if any of the three followingconditions exist:
¶ The size of the maximum storage for locklists (locklist) is too small, causing the locklistto fill up.
¶ The maxlocks configuration parameter is too small. In this case, the value for locklist isfine, but an application keeps reaching its maximum percent of the locklist, causing lockescalations.
¶ Applications are getting more locks than they really need. In this case, examine yourapplications.
A low returned value compared to normal operating levels can indicate that the value forlocklist is too high and memory is being wasted in the locklist.
See AlsoDB2Manager Configuration monitors: “db: locklist” on page 322, “db: maxlocks” onpage 326
73Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Internal rollback due to deadlock
DescriptionReturns the total number of forced rollbacks initiated by the database manager because of adeadlock. A rollback is performed on the current unit of work in an application selected bythe database manager to resolve the deadlock.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIntDeadlockRollbacks
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbIntDeadlockRollbacks'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value equals the number of deadlocks that the database manager needed tobreak, and can be an indication of concurrency problems –internal rollbacks caused bydeadlocks lower the throughput of the database.
This value is included in the value returned by the db: # of internal rollbacks monitor.
See AlsoDB2Manager Basic monitors: “db: # of internal rollbacks” on page 58
74 Version 2.1.0
db: Last backup timestamp
DescriptionReturns a string that contains the date and time when the last database backup wascompleted.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLastBackup
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbLastBackup'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to identify a database that was not recently backed up, or to identifywhich database backup file is the most recent.
The string returned gives the local date and time. For example, if the database is located inCalifornia and was last backed up on Wednesday, April 30, 2000 at 10:52 PM duringdaylight savings time, this monitor returns the following string:Wed Apr 30 22:52:38 2000
If the database was never backed up, the returned string is None.
See AlsoNone
75Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Log I/O
DescriptionReturns the total amount of log input and output. This amount is the sum of the number oflog pages read and the number of log pages written within the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLogIo
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbLogIo'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine whether you should move the log to a different device.If this input and output is beyond the capabilities of the current device, you can determine ifmoving the log (by changing the newlogpath configuration parameter) will improveperformance.
See AlsoDB2Manager Configuration monitors: “db: newlogpath” on page 329
76 Version 2.1.0
db: Max # of concurrent connections
DescriptionReturns the highest number of simultaneous connections (both local and remote) made to adatabase since the first application connected to the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbConnectionsTop
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbConnectionsTop'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA returned value that equals the value of the maxappls configuration parameter indicatesthat some database connections were probably rejected, because maxappls limits the numberof database connections allowed.
See AlsoDB2Manager Configuration monitors: “db: maxappls” on page 325
77Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Max database heap allocated
DescriptionReturns the largest amount of database heap allocated and used by the database since thefirst application connected to the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDbHeapTop
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbDbHeapTop'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate your setting of the dbheap configuration parameter. Areturned value that equals the value of dbheap indicates that an application has probablyreceived an error, indicating that not enough storage was available. The dbheap parameterlimits the amount of storage that can be allocated for database heap.
See AlsoDB2Manager Configuration monitors: “db: dbheap” on page 321
78 Version 2.1.0
db: Max primary log space used
DescriptionReturns the maximum number of bytes used by the primary log.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbMaxPriLogSpaceUsed
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbMaxPriLogSpaceUsed'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Percent used inprimary log monitor. This value is valid only if circular logging is used.
See AlsoDB2Manager Basic monitors: “db: Percent used in primary log” on page 87
79Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Max secondary log space used
DescriptionReturns the maximum number of bytes used by the secondary log.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSecLogUsedTop
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbSecLogUsedTop'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Percent used insecondary log monitor. This value is zero if the database does not have any secondary logfiles (if none are defined or if log retention is enabled).
See AlsoDB2Manager Basic monitors: “db: Percent used in secondary log” on page 88
80 Version 2.1.0
db: Max total log space used
DescriptionReturns the maximum amount (in bytes) of total log space used.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotLogUsedTop
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbTotLogUsedTop'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Max primary logspace used monitor. This value includes space used in both primary and secondary log filesand is valid only if circular logging is used.
See AlsoDB2Manager Basic monitors: “db: Max primary log space used” on page 79
81Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Percent connections used
DescriptionReturns the percentage of the allowed number of connections that are concurrentconnections.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctConnUsed
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPctConnUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 9 shows the default threshold values for severity levels.
Table 9. dbPctConnUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 80% Send Tivoli Notice; Change Icon
warning Greater than 60% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to help you tune the maxappls configuration parameter. Themaxappls configuration parameter limits the number of concurrent applications that can beconnected (both local and remote) to a database. If the returned value is high compared tonormal operating levels, you might need to adjust the value of maxappls or schedule someof your applications so that they do not run concurrently.
See AlsoDB2Manager Configuration monitors: “db: maxappls” on page 325
82 Version 2.1.0
db: Percent internal rollbacks due to internal deadlocks
DescriptionReturns the percentage of the total number of internal rollbacks due to deadlocks.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctIntRbPerIntDeadlk
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPctIntRbPerIntDeadlk'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 10 shows the default threshold values for severity levels.
Table 10. dbPctIntRbPerIntDeadlk Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 80% Send Tivoli Notice; Change Icon
warning Greater than 70% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to distinguish those rollbacks caused by internal deadlocks fromrollbacks caused by other situations (for example, incomplete imports). The returned value isthe percentage of internal rollbacks due to internal deadlocks since the first databaseconnection or the last reset of the database monitor counters.
See AlsoNone
83Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Percent locklist space used by database
DescriptionReturns the percentage of space used in the database’s locklist.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctLocklistUsed
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPctLocklistUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how much of the locklist space is free for new locks tobe requested.
See AlsoDB2Manager Configuration monitors: “db: locklist” on page 322
84 Version 2.1.0
db: Percent package cache hit ratio
DescriptionReturns the package cache hit ratio (as a percent) for the last monitoring interval. Thepackage cache hit ratio is the ratio of the difference between the package cache lookups andthe package cache inserts to all package cache lookups.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPkgCacheHitRatio
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPkgCacheHitRatio'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 11 shows the default threshold values for severity levels.
Table 11. dbPkgHItRatio Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 85% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesThis percentage indicates whether the package cache is being used efficiently. If the returnedvalue is high (greater than 80%), the package cache is performing well. A smaller percentagecan indicate that the package cache should be increased. The size of the package cache is setby the pckcachesz configuration parameter (pckcachesz). To determine whether or not theexecution of DDL statements is affecting the performance of the package cache, use thereturned value from the db: Percent DDL SQL monitor. Execution of DDL statements canlower the percent package hit ratio (indicating poor performance), but in this case, increasingthe size of the package cache will not necessarily improve overall performance. If DDLstatements rarely occur, performance can improve if you increase pckcachesz. If DDLstatements frequently occur, you can leave pckcachesz as it is and instead limit the use ofDDL statements (for example, to certain time periods). Use the db: Dynamic SQLstatements and the db: Static SQL statements monitors to provide information about thequantity and type of sections being cached. Caching of a section for static or dynamic SQL
85Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
statements can improve performance, especially when the same statement is used multipletimes by applications connected to the database.
See AlsoDB2Manager Configuration monitors: “db: pckcachesz” on page 333DB2Manager SQL Statement Activity monitors:“db: Dynamic SQL statements” on page 527, “db: Static SQL statements” on page 536,“db: Percent DDL SQL” on page 529
86 Version 2.1.0
db: Percent used in primary log
DescriptionReturns the percentage of log space used by the primary log.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctUsedInPriLog
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPctUsedInPriLog'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 12 shows the default threshold values for severity levels.
Table 12. dbPctUsedInPriLog Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 85% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to help you evaluate the allocated amount of primary log space andrefine the logbufsz, logfilsiz, and logprimary configuration parameters.
The returned value is valid only if circular logging is used.
See AlsoDB2Manager Configuration monitors: “db: logprimary” on page 324, “db: logbufsz” onpage 323
87Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Percent used in secondary log
DescriptionReturns the percentage of log space used by the secondary log.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctUsedInSecLog
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPctUsedInSecLog'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 13 shows the default threshold values for severity levels.
Table 13. dbPctUsedInSecLog Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 85% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to show the current dependency on secondary logs. Secondary logsare used when you have circular logging (log retention off) and the primary log files arefull.
If the returned value is high compared to normal operating levels, you might need one ormore of the following:
¶ Larger log files.
¶ More primary log files.
¶ More frequent COMMIT statements within your applications.
The returned value is zero if the database does not have any secondary log files (if none aredefined or if log retention is enabled).
88 Version 2.1.0
See AlsoDB2Manager Configuration monitors: “db: logprimary” on page 324, “db: logbufsz” onpage 323
89Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
db: Primary log space allocated
DescriptionReturns the number of bytes allocated to the primary log.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPriLogSpaceAlloc
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbPriLogSpaceAlloc'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Percent used inprimary log monitor.
The allocated amount (in bytes) of primary log space is determined by the followingformula:
logprimary × logfilsiz × 4096 = primary log space
See AlsoDB2Manager Basic monitors: “db: Percent used in primary log” on page 87DB2Manager Configuration monitors: “db: logprimary” on page 324
90 Version 2.1.0
dbms: # of idle agents
DescriptionReturns the number of agents in the agent pool that are currently unassigned to anapplication.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsIdleAgents
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsIdleAgents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help set the maximum number of idle agents (max_idleagents)configuration parameter. Having idle agents available to service requests for agents canimprove performance.
See AlsoNone
91Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbms: # of local connections
DescriptionReturns the number of local applications that are currently connected to a local databasewithin the DB2 instance.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsLocalCons
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsLocalCons'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of concurrent processing occurring in the DB2instance. This value changes frequently, so you might need to sample it at specific intervalsover an extended period of time to get a realistic view of system usage.
This number includes only applications that are initiated from the same node where the DB2instance is located. The applications are connected but can not be executing a unit of work.
Use this value with the dbms: # of remote connections monitor to evaluate the setting ofthe max_agents configuration parameter.
See AlsoDB2Manager Basic monitors: “dbms: # of remote connections” on page 97, “dbms:max_agents” on page 344
92 Version 2.1.0
dbms: # of local connections executing
DescriptionReturns the number of local applications that are currently connected to a local databasewithin the DB2 instance and that are currently processing a unit of work.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsLocalConsInExec
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsLocalConsInExec'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of concurrent processing occurring in the DB2instance. This value changes frequently, so you might need to sample it at specific intervalsover an extended period of time to get a realistic view of system usage.
This number includes only applications that are initiated from the same node where the DB2instance is located.
Use this value with the dbms: # of remote connections executing monitor to evaluate thesetting of the maxcagents configuration parameter.
See AlsoDB2Manager Basic monitors: “dbms: # of remote connections executing” on page 98DB2Manager Configuration monitors: “dbms: maxcagents” on page 346
93Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbms: # of local databases with current connections
DescriptionReturns the number of local databases that have applications connected.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsConLocalDbases
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsConLocalDbases'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to get an indication of how many database information records youcan expect when gathering monitoring values at the database level.
See AlsoNone
94 Version 2.1.0
dbms: # of piped sorts accepted
DescriptionReturns the number of piped sorts that were accepted.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPipedSortsAccepted
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsPipedSortsAccepted'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you improve sort performance. Every active sort on thesystem allocates memory, which can result in the sorting task taking up too much of theavailable system memory. Piped sorts help reduce disk input and output, so that increasingthe number of accepted piped sorts can improve performance.
When the returned value is low compared to the number of piped sorts requested, you canimprove performance by adjusting either the sort list heap (sortheap) or sort heap threshold(sheapthres) configuration parameter, or by adjusting both.
See AlsoDB2Manager Basic monitors: “dbms: Percent piped sort hit ratio” on page 101DB2Manager Configuration monitors: “db: sortheap” on page 337,“dbms: sheapthres” on page 354
95Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbms: # of piped sorts requested
DescriptionReturns the number of piped sorts that were requested.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPipedSortsRequested
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsPipedSortsRequested'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you improve sort performance. Every active sort on thesystem allocates memory, which can result in the sorting task taking up too much of theavailable system memory. Piped sorts help reduce disk input and output, so increasing thenumber of accepted piped sorts can improve performance.
See AlsoDB2Manager Basic monitors: “dbms: Percent piped sort hit ratio” on page 101
96 Version 2.1.0
dbms: # of remote connections
DescriptionReturns the number of current application connections that remote clients have initiated tothe DB2 instance.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsRemConsIn
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsRemConsIn'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value shows the level of activity between this DB2 instance and other DB2instances.
Use this value, in addition to the value from the dbms: # of local connections monitor, toevaluate the setting of the maxagents configuration parameter.
See AlsoDB2Manager Basic monitors: “dbms: # of local connections” on page 92DB2Manager Configuration monitors: “dbms: max_agents” on page 344
97Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbms: # of remote connections executing
DescriptionReturns the number of remote applications that are currently connected to a database and arecurrently processing a unit of work within the DB2 instance.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsRemConsInExec
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsRemConsInExec'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of concurrent processing occurring in the DB2instance. This value will change frequently, so you might need to sample it at specificintervals over an extended period of time to get a realistic view of system usage.
Use this value, in addition to the value from the dbms: # of local connections executingmonitor, to evaluate the setting of the maxcagents configuration parameter.
See AlsoDB2Manager Basic monitors: “dbms: # of local connections executing” on page 93DB2Manager Configuration monitors: “dbms: max_agents” on page 344
98 Version 2.1.0
dbms: Committed private memory
DescriptionReturns the amount of private memory that the DB2 instance has currently committed.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsCommPrivateMem
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsCommPrivateMem'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help set the min_priv_mem configuration parameter. Thisparameter specifies the number of pages that the database server process will reserve asprivate virtual memory when a DB2 instance is started. If the returned value is close to thecurrent min_priv_mem value, you can increase the value for min_priv_mem to ensure thatyou have enough private memory available.
See AlsoDB2Manager Configuration monitors: “dbms: Minimum committed private memory”on page 348
99Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbms: Last reset timestamp
DescriptionReturns a string that contains the date and time that the monitor counters were reset for thedatabase manager.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsLastReset
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsLastReset'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe ECC_Reset_Counters task resets the monitor counters. Use the returned string toidentify when the database system monitor counters were last reset. This time stampdetermines the scope of information that is based on total counts (for example, the numberof registered agents).
The returned string gives the local date and time. For example, if the database manager islocated in California and the monitor counters were last reset on Wednesday, April 30, 2000at 10:52 PM during daylight savings time, this monitor returns the following string:Wed Apr 30 22:52:38 2000
If the counters were never reset, the returned string is None.
See AlsoMonitor and Administration tasks: “ECC_Reset_Counters” on page 561
100 Version 2.1.0
dbms: Percent piped sort hit ratio
DescriptionReturns the piped sort hit ratio (as a percent) for the last monitoring interval. The piped sorthit ratio is the ratio of piped sorts accepted to piped sorts requested.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPipedSortHitRatio
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsPipedSortHitRatio'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 14 shows the default threshold values for severity levels.
Table 14. dbmsPipedSortHItRatio Response LevelsResponse Level Trigger When Default Actions
critical Less than 80% Send Tivoli Notice; Change Icon
severe Less than 90% Send Tivoli Notice; Change Icon
warning Less than 95% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to help you improve sort performance. Every active sort on thesystem allocates memory, which can result in the sorting process taking up too much of theavailable system memory. Piped sorts help reduce disk input and output, so increasing thenumber of accepted piped sorts can improve performance.
When the returned value is low compared to normal operating levels, you can improveperformance by adjusting either the sort heap size (sortheap) or sort heap threshold(sheapthres) configuration parameter, or by adjusting both. If piped sorts are being rejected(resulting in a low-percentage piped sort hit ratio), consider decreasing your sort heap orincreasing your sort heap threshold. A piped sort is not accepted if the sort heap thresholdwill be exceeded when the sort heap is allocated for that piped sort.
Be aware that adjusting sortheap or sheapthres can have the following consequences:
101Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
¶ Decreasing sortheap can result in the need for extra sort merge phases that could slowdown sorts.
¶ Increasing sheapthres can result in more memory allocated for sorting, causing thepaging of memory to disk and slowing overall system performance.
See AlsoDB2Manager Configuration monitors: “dbms: sheapthres” on page 354, “db: sortheap”on page 337
102 Version 2.1.0
dbms: Start database manager timestamp
DescriptionReturns a string that contains the date and time that the database manager was started.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsDbTwostartTime
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbmsDbTwostartTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned string with the value for the current time to calculate the elapsed time sincethe database manager was started.
The string returned gives the local date and time. For example, if the database manager islocated in California and it was started on Wednesday, April 30, 2000 at 10:52 PM duringdaylight savings time, this monitor returns the following string:Wed Apr 30 22:52:38 2000
If the database manager is not started, the returned string is None.
See AlsoNone
103Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbpg: Data redistribution status
DescriptionReturns a positive value if row redistribution is in progress in one or more node groupswithin any of the partitions in the database partition group during the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionGroupManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpgNodegroupsRedistStatus
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbpgNodegroupsRedistStatus'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf any partition in the database partition group is participating in more than one node group,all the node groups in which the partition is a member will be inspected for dataredistribution status. The monitor also returns a positive value if a failure occurs during dataredistribution on any of the node groups, and user intervention is required to recoverredistribution errors.
To determine which node groups are currently redistributing data (or require userintervention), issue the following query:SELECT NGNAME, REBALANCE_PMAP_ID FROM SYSCAT.NODEGROUPS \WHERE REBALANCE_PMAP_ID <> -1
See AlsoNone
104 Version 2.1.0
dbpg: Data redistribution status for a nodegroup
DescriptionReturns a positive value if row redistribution is in progress in the specified node group inthe partitioned database during the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Nodegroup NameSpecifies the name of the DB2 node group that you want to monitor for dataredistribution.
CLI SynopsisdbpgNodegroupRedistStatus
-a <DB2_node_group_name>
The following briefly describes the argument for this monitor:
<DB2_node_group_name>Specify the name of the DB2 node group that you want to monitor for dataredistribution.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbpgNodegroupRedistStatus'-a 'nodegroup1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA positive value returned by this monitor indicates that the specified node group in thepartitioned database is redistributing data.
105Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
Use the Data Redistribution utility to redistribute data across database partitions. If a failureoccurs during redistribution of data, some tables can be redistributed while others are not.
The monitor returns a positive value if a failure occurs during data redistribution, and userintervention is required to recover from redistribution errors.
See AlsoNone
106 Version 2.1.0
dbpg: DB2 local nodes status
DescriptionReturns the number of inactive nodes in the partition group.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionGroupManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpgNodeStatus
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbpgNodeStatus'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesDepending on the actual partitions defined in the database partition group, it is notnecessarily true that all the nodes defined in the parallel environment will be examined. Toensure that all the nodes in the partitioned environment are examined, define a partitiongroup that contains at least one database partition from each of the nodes in the partitionedenvironment.
See AlsoNone
107Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
dbpg: Partitioned database data redistribution status
DescriptionReturns a positive value if row redistribution is in progress in any node group in thepartitioned database during the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionGroupManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpgRedistStatus
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbpgRedistStatus'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA positive value returned by this monitor indicates the number of nodegroups in thepartitioned database that are actively redistributing data.
Use the Data Redistribution utility to redistribute data across database partitions. If a failureoccurs during redistribution, some tables can be redistributed while others are not.
The monitor returns a positive value if a failure occurs during data redistribution, and userintervention is required to recover from redistribution errors.
To determine which nodegroups are redistributing data or require intervention fromredistribution errors issue the following query:SELECT NGNAME, REBALANCE_PMAP_ID FROM SYSCAT.NODEGROUPS \WHERE REBALANCE_PMAP_ID <> -1
See AlsoNone
108 Version 2.1.0
dbpg: Percentage differential in row distribution of a table
DescriptionReturns the difference in percentage between the highest and the lowest rows distributedacross the partitions in the selected partition group during the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner NameSpecifies the owner of the table.
Table NameSpecifies the name of the table.
Partition Key Column NameSpecifies the name of one of the columns as defined in the table’s partition key.
CLI SynopsisdbpgPercentDiffRowDistribution
-a <Owner_name>
-a <Table_name>
-a <Partition_key_column>
The following briefly describes the arguments for this monitor:
<Owner_name>Specifies the owner of the table.
<Table_name>Specifies the name of the table.
<Partition_key_column>Specifies the name of one of the columns as defined in the table’s partition key.
109Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'dbpgPercentDiffRowDistribution'-a 'operations'-a 'employees'-a 'lastname'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe partitions defined in the partition group can be a subset of the partitions across whichthe table rows are distributed. However, if you define the complete set of partitions to thepartition group, the result returned by this monitor will present a more accurate picture ofthe distribution of the rows in the table.
In computing the percentage of rows being distributed to a partition in the partition group,the total number of rows distributed to all the partitions defined in the partition group isused as the base. This number can be smaller than the total number of the rows in the table.
For example, assume the rows of a table are distributed across four separate nodes (N1, N2,N3, and N4) and the partitions defined in the partition group are just N1, N2, and N3.Table 15 shows the actual number of rows distributed to each node with the computedpercentage of rows distributed.
Table 15. Percentage Differential in Row DistributionNodes N1 N2 N3 N4
Rows Distributed 30 10 140 20
Percentage of Rows Distributed 17% 6% 77% N/A
Using the table example, the monitor returns a value of 71 (which represents the differencebetween 77% and 6%). This value indicates that the distribution of the table rows across thepartitions in the partition group is highly skewed.
See AlsoNone
110 Version 2.1.0
tbsp: Percent space used in DMS tablespace
DescriptionReturns the percentage of space used in the Database Managed Space (DMS) tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 tablespace nameSpecifies the name of the DB2 DMS tablespace.
CLI SynopsistbspPctSpaceUsedDMS
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 DMS tablespace.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'tbspPctSpaceUsedDMS'-a 'tblspc3'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 16 shows the default threshold values for severity levels.
Table 16. tbspPctSpaceUsedDMS Response LevelResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 85% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
111Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
Usage NotesUse the returned value to determine if the tablespace needs more space.
See AlsoNone
112 Version 2.1.0
tbsp: Space used in SMS tablespace
DescriptionReturns the number of bytes allocated to the System Managed Space (SMS) tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 tablespace nameSpecifies the name of the DB2 SMS tablespace.
CLI SynopsistbspSpaceUsedSMS
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 SMS tablespace.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'tbspSpaceUsedSMS'-a 'tblspc3'"ManufacturingProfile"
Default Thresholds and ActionsSchedule the monitor to run every 24 hours without any time restrictions.
Usage NotesUse the returned value to determine whether the number of bytes used by the SMStablespace is excessive in relation to the file system on which the tablespace resides.
See AlsoNone
113Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
tbsp: Tablespace status
DescriptionReturns a numeric value to indicate the tablespace status.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 tablespace nameSpecifies the name of the DB2 DMS tablespace.
CLI SynopsistbspStatus
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Basic_Monitors' 'tbspStatus'-a 'tblspc3'"ManufacturingProfile"
Default Thresholds and ActionsTable 17 shows the default threshold values for severity levels.
Table 17. tbspStatus Response LevelsResponse Level Trigger When Default Actions
critical N/A None
severe N/A None
warning Greater than 0 Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
114 Version 2.1.0
Usage NotesUse the returned value to determine the state of the tablespace. The returned value is one ofthe following values:
Table 18. Tablespace State ValuesValue Tablespace State
0x0 Normal
0x1 Quiesced: SHARE
0x2 Quiesced: UPDATE
0x4 Quiesced: EXCLUSIVE
0x8 Load pending
0x10 Delete pending
0x20 Backup pending
0x40 Roll forward in progress
0x80 Roll forward pending
0x100 Restore pending
0x200 Disable pending
0x400 Reorganization in progress
0x800 Backup in progress
0x1000 Storage must be defined
0x2000 Restore in progress
0x4000 Offline and not accessible
0x8000 Drop pending
0x2000000 Storage may be defined
0x4000000 Storage definition is in ‘final’ state
0x8000000 Storage definition was changed prior to roll forward
0x10000000 DMS rebalancer is active
0x20000000 TBS deletion in progress
0x40000000 TBS creation in progress
0x8 For service use only
See AlsoNone
115Tivoli Manager for DB2 Reference Guide
4.D
B2
Basic
Mo
nito
rs
116 Version 2.1.0
DB2 Buffer Pool I/O Monitors
The monitors in the DB2Manager_Bufio_Monitors collection provide statistics about thedatabase buffer pool. The buffer pool is a storage area where database pages that containtable rows or index entries are read and changed. The purpose of the buffer pool is toimprove database system performance. Data can be accessed much faster from memory thanfrom a disk. Therefore, the fewer times the database manager needs to read from or write toa disk, the better the performance.
The configuration of the buffer pool is the most important area that you can refine becausemost of the data manipulation for applications connected to the database takes place there.
Table 19 lists the monitors in this collection.
Table 19. DB2Manager Buffer Pool I/O MonitorsDesktop Name CLI Name Returned Value
Format
conn: # of direct reads connDirectReads Numeric
conn: # of direct writes connDirectWrites Numeric
conn: Average # of sectorsread per direct read
connAvgSectorsReadPerDirectRead Numeric
conn: Average # of sectorswritten per direct write
connAvgSectorsWritePerDirectWrite Numeric
conn: Buffer pool time waitedfor prefetch (ms)
connTimeWaitedforPreFetch Numeric:milliseconds
conn: Data page writes connPoolDataWrites Numeric
conn: Index page reads connPoolIndexPReads Numeric
conn: Index page writes connPoolIndexWrites Numeric
conn: Logical data reads connPoolDataLReads Numeric
conn: Percent buffer pool hitratio, data+index
connPoolHitRatio Numeric: percentage
conn: Percent buffer pool hitratio, index
connIndxPlHitRatio Numeric: percentage
conn: Percent package cachehit ratio
connPkgCacheHitRatio Numeric: percentage
conn: Pool read time (s) connPoolReadTime Numeric: seconds
conn: Pool write time (s) connPoolWriteTime Numeric: seconds
conn: Total pool I/O time (s) connTotalPoolIoTime Numeric: seconds
db: # of cleaners due to dirtythreshold
dbPlDrtyPgThrshCln Numeric
5
117Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
Table 19. DB2Manager Buffer Pool I/O Monitors (continued)Desktop Name CLI Name Returned Value
Format
db: # of database files closed dbFilesClosed Numeric
db: # of direct read requests dbDirectReadReqs Numeric
db: # of direct reads fromdatabase
dbDirectReads Numeric
db: # of direct write requests dbDirectWriteReqs Numeric
db: # of direct writes todatabase
dbDirectWrites Numeric
db: # of log space cleanersinvoked
dbPoolLsnGapClns Numeric
db: # of page cleans in aninterval
dbPageCleans Numeric
db: # of pages for eachprefetch request
dbPagesPerPrefetch Numeric
db: # of pool reads dbTotalPoolReads Numeric
db: # of pool writes dbTotalPoolWrites Numeric
db: # of prefetch requests inan interval
dbPoolAsyncDatRdRq Numeric
db: # of synchronous I/O dbTotalSyncIos Numeric
db: # of synchronous indexreads
dbSyncIndexReads Numeric
db: # of synchronous indexwrites
dbSyncIndexWrites Numeric
db: # of synchronous reads dbSyncDataReads Numeric
db: # of synchronous writes dbSyncDataWrites Numeric
db: # of victim page cleanersinvoked
dbPlDrtyPgStealCln Numeric
db: Average # of async readsper pool read
dbAvgAsyncReadsPerTotReads Numeric
db: Average # of async writesper pool write
dbAvgAsyncWritesPerTotWrites Numeric
db: Average # of pool writesper pool read
dbAvgPlWritesPerPlReads Numeric
db: Average # of sectors readper direct read
dbAvgSectorsReadPerDirectRead Numeric
db: Average # of sectorswritten per direct write
dbAvgSectorsWritePerDirectWrite Numeric
db: Average direct read time(ms)
dbAvgDirectReadTime Numeric:milliseconds
db: Average direct write time(ms)
dbAvgDirectWriteTime Numeric:milliseconds
db: Average pool I/O time(ms)
dbAvgPoolIoTime Numeric:milliseconds
db: Average pool read time(ms)
dbAvgPoolReadTime Numeric:milliseconds
118 Version 2.1.0
Table 19. DB2Manager Buffer Pool I/O Monitors (continued)Desktop Name CLI Name Returned Value
Format
db: Average pool write time(ms)
dbAvgPoolWriteTime Numeric:milliseconds
db: Average synchronous dataread time (ms)
dbAvgSyncReadTime Numeric:milliseconds
db: Average synchronous datawrite time (ms)
dbAvgSyncWriteTime Numeric:milliseconds
db: Average synchronous I/O(ms)
dbAvgSyncIoTime Numeric:milliseconds
db: Avg # of pages for eachcleaner
dbPagesPerClean Numeric
db: Buffer pool async datareads
dbPoolAsyncDataReads Numeric
db: Buffer pool async datawrites
dbPoolAsyncDataWrites Numeric
db: Buffer pool async indexreads
dbPoolAsyncIndexReads Numeric
db: Buffer pool async indexwrites
dbPoolAsyncIndexWrites Numeric
db: Buffer pool async readtime (ms)
dbPoolAsyncReadTime Numeric:milliseconds
db: Buffer pool async writetime (ms)
dbPoolAsyncWriteTime Numeric:milliseconds
db: Buffer pool data logicalreads
dbPoolDataLReads Numeric
db: Buffer pool data pagescopied from extended storage
dbDataPagesCopiedfromExtendedStorage Numeric
db: Buffer pool data pagescopied to extended storage
dbDataPagesCopiedtoExtendedStorage Numeric
db: Buffer pool data physicalreads
dbPoolDataPReads Numeric
db: Buffer pool data writes dbPoolDataWrites Numeric
db: Buffer pool index logicalreads
dbPoolIndexLReads Numeric
db: Buffer pool index pagescopied from extendedstorage>
dbIndexPagesCopiedfromExtendedStorage Numeric
db: Buffer pool index pagescopied to extended storage
dbIndexPagesCopiedtoExtendedStorage Numeric
db: Buffer pool indexphysical reads
dbPooIndexPReads Numeric
db: Buffer pool index writes dbPoolIndexWrites Numeric
db: Buffer pool I/Os persecond
dbPoolIoRate Numeric
db: Buffer pool time waitedfor prefetch (ms)
dbTimeWaitedforPreFetch Numeric:milliseconds
119Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
Table 19. DB2Manager Buffer Pool I/O Monitors (continued)Desktop Name CLI Name Returned Value
Format
db: Direct read time (ms) dbDirectReadTime Numeric:milliseconds
db: Direct write time (ms) dbDirectWriteTime Numeric:milliseconds
db: Extended storageread/write ratio
dbExtendedStorageReadWriteRatio Numeric: percentage
db: Percent buffer pool hitratio, data+index
dbPoolHitRatio Numeric: percentage
db: Percent buffer pool hitratio, index
dbIndxPlHitRatio Numeric: percentage
db: Percent catalog cache hitratio
dbCatCacheHitRatio Numeric: percentage
db: Synchronous read time(ms)
dbSyncReadTime Numeric:milliseconds
db: Synchronous write time(ms)
dbSyncWriteTime Numeric:milliseconds
db: Total direct I/O time (ms) dbTotalDirectIoTime Numeric:milliseconds
db: Total pool physical I/O(ms)
dbTotalPoolIoTime Numeric:milliseconds
db: Total pool physical read(ms)
dbTotalReadTime Numeric:milliseconds
db: Total pool physical write(ms)
dbTotalWriteTime Numeric:milliseconds
db: Total synchronous I/Otime (ms)
dbTotalSyncIoTime Numeric:milliseconds
dbp: # of FCM nodes dbpTotFcmNodes Numeric
dbp: Connection status dbpConnStatus Numeric
dbp: FCM buffers currentlyfree
dbpFreeFcmBuf Numeric
dbp: FCM connection entriescurrently free
dbpFcmConnFree Numeric
dbp: FCM request blockscurrently free
dbpFcmReqBlkFree Numeric
dbp: Minimum FCM buffersfree
dbpMinFcmBufFree Numeric
dbp: Minimum FCMconnection entries free
dbpMinFcmConnEntries Numeric
dbp: Minimum FCM messageanchors free
dbpMinFcmMsgAnchors Numeric
dbp: Minimum FCM requestblocks free
dbpMinFcmReqBlks Numeric
dbp: Percent FCM bufferscurrently used
dbpPctFcmBufUsed Numeric: percentage
120 Version 2.1.0
Table 19. DB2Manager Buffer Pool I/O Monitors (continued)Desktop Name CLI Name Returned Value
Format
dbp: Percent FCM requestblocks currently used
dbpPctFcmReqBlkUsed Numeric: percentage
dbp: Percent FCM connectionentries currently used
dbpPctFcmConnEntriesUsed Numeric: percentage
dbp: Percent maximum FCMbuffers used
dbpPctMaxFcmBufUsed Numeric: percentage
dbp: Percent maximum FCMconnection entries used
dbpPctMaxFcmConnEntriesUsed Numeric: percentage
dbp: Percent maximum FCMmessage anchors used
dbpPctMaxFcmMsgAnchorsUsed Numeric: percentage
dbp: Percent maximum FCMrequest blocks used
dbpPctMaxFcmReqBlksUsed Numeric: percentage
dbp: Total buffers received dbpTotBufReceived Numeric
dbp: Total buffers sent dbpTotBufSent Numeric
tbsp: # of direct read requests tbspDirectReadReqs Numeric
tbsp: # of direct reads fromdatabase
tbspDirectReads Numeric
tbsp: # of direct writerequests
tbspDirectWriteReqs Numeric
tbsp: # of direct writes todatabase
tbspDirectWrites Numeric
tbsp: # of pool reads tbspTotalPoolReads Numeric
tbsp: # of pool writes tbspTotalPoolWrites Numeric
tbsp: # of synchronous indexreads
tbspSyncIndexReads Numeric
tbsp: # of synchronous indexwrites
tbspSyncIndexWrites Numeric
tbsp: # of synchronous reads tbspSyncDataReads Numeric
tbsp: # of synchronous writes tbspSyncDataWrites Numeric
tbsp: Average # of sectorsread per direct read
tbspAvgSectorsReadPerDirectRead Numeric
tbsp: Average # of sectorswritten per direct write
tbspAvgSectorsWritePerDirectWrite Numeric
tbsp: Average direct read time(ms)
tbspAvgDirectReadTime Numeric:milliseconds
tbsp: Average direct writetime (ms)
tbspAvgDirectWriteTime Numeric:milliseconds
tbsp: Average pool I/O time(ms)
tbspAvgPoolIoTime Numeric:milliseconds
tbsp: Average pool read time(ms)
tbspAvgPoolReadTime Numeric:milliseconds
tbsp: Average pool write time(ms)
tbspAvgPoolWriteTime Numeric:milliseconds
121Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
Table 19. DB2Manager Buffer Pool I/O Monitors (continued)Desktop Name CLI Name Returned Value
Format
tbsp: Average synchronousdata read time (ms)
tbspAvgSyncReadTime Numeric:milliseconds
tbsp: Average synchronousdata write time (ms)
tbspAvgSyncWriteTime Numeric:milliseconds
tbsp: Average synchronousI/O time (ms)
tbspAvgSyncIoTime Numeric:milliseconds
tbsp: Buffer pool async datareads
tbspPoolAsyncDataReads Numeric
tbsp: Buffer pool async datawrites
tbspPoolAsyncDataWrites Numeric
tbsp: Buffer pool async indexreads
tbspPoolAsyncIndexReads Numeric
tbsp: Buffer pool async indexwrites
tbspPoolAsyncIndexWrites Numeric
tbsp: Buffer pool async readtime (ms)
tbspPoolAsyncReadTime Numeric:milliseconds
tbsp: Buffer pool async writetime (ms)
tbspPoolAsyncWriteTime Numeric:milliseconds
tbsp: Buffer pool data logicalreads
tbspPoolDataLReads Numeric
tbsp: Buffer pool data pagescopied from extended storage
tbspDataPagesCopiedfromExtendedStorage Numeric
tbsp: Buffer pool data pagescopied to extended storage
tbspDataPagesCopiedtoExtendedStorage Numeric
tbsp: Buffer pool dataphysical reads
tbspPoolDataPReads Numeric
tbsp: Buffer pool dataphysical writes
tbspPoolDataWrites Numeric
tbsp: Buffer pool I/Os persecond
tbspPoolIoRate Numeric
tbsp: Buffer pool indexlogical reads
tbspPoolIndexLReads Numeric
tbsp: Buffer pool index pagescopied from extended storage
tbspIndexPagesCopiedfromExtendedStorage Numeric
tbsp: Buffer pool index pagescopied to extended storage
tbspIndexPagesCopiedtoExtendedStorage Numeric
tbsp: Buffer pool indexphysical reads
tbspPoolIndexPReads Numeric
tbsp: Buffer pool indexphysical writes
tbspPoolIndexWrites Numeric
tbsp: Direct write time (ms) tbspDirectReadTime Numeric:milliseconds
tbsp: Direct write time (ms) tbspDirectWriteTime Numeric:milliseconds
122 Version 2.1.0
Table 19. DB2Manager Buffer Pool I/O Monitors (continued)Desktop Name CLI Name Returned Value
Format
tbsp: Extended storageread/write ratio
tbspExtendedStorageReadWriteRatio Numeric: percentage
tbsp: File closed tbspFilesClosed Numeric
tbsp: Percent buffer pool hitratio, data+index
tbspPoolHitRatio Numeric: percentage
tbsp: Percent buffer pool hitratio, index
tbspIndxPlHitRatio Numeric: percentage
tbsp: Percent prefetchsatisfied
tbspPctAsyDatRdRqS Numeric: percentage
tbsp: Percent total I/O tbspPctTotalIo Numeric: percentage
tbsp: Prefetch requests in aninterval
tbspPlAsyncDatRdRq Numeric
tbsp: Synchronous read time(ms)
tbspSyncReadTime Numeric:milliseconds
tbsp: Synchronous write time(ms)
tbspSyncWriteTime Numeric:milliseconds
tbsp: Total direct I/O time(ms)
tbspTotalDirectIoTime Numeric:milliseconds
tbsp: Total pool physical I/Otime (ms)
tbspTotalPoolIoTime Numeric:milliseconds
tbsp: Total pool physical readtime (ms)
tbspTotalReadTime Numeric:milliseconds
tbsp: Total pool physicalwrite time (ms)
tbspTotalWriteTime Numeric:milliseconds
tbsp: Total synchronous I/O tbspTotalSyncIos Numeric
tbsp: Total synchronous I/Otime (ms)
tbspTotalSyncIoTime Numeric:milliseconds
123Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: # of direct reads
DescriptionReturns the number of direct reads that do not use the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnDirectReads
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connDirectReads'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
124 Version 2.1.0
Usage NotesThis returned value is used in calculating the returned value for the conn: Average # ofsectors read per direct read monitor. If you are using system monitors to track input andoutput for a particular device, you can use the returned value from this monitor todistinguish database application input and output from non-database application input andoutput. Direct reads are typically used when the following occur:
¶ Reading LONG VARCHAR columns
¶ Reading large object (LOB) columns
¶ Performing a backup
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Average # of sectors read per directread” on page 128
125Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: # of direct writes
DescriptionReturns the number of write applications that do not use the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnDirectWrites
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connDirectWrites'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
126 Version 2.1.0
Usage NotesThis returned value is used in calculating the returned value for the conn: Average # ofsectors written per direct write monitor.
If you are using system monitors to track input and output for a particular device, you canuse the returned value from this monitor to distinguish database application input and outputfrom non-database application input and output.
Direct writes are typically used while:
¶ Writing LONG VARCHAR columns
¶ Writing large object (LOB) columns
¶ Performing a restore
¶ Performing a load
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Average # of sectors written per directwrite” on page 130
127Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Average # of sectors read per direct read
DescriptionReturns the average number of sectors that are read in a direct read by this application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnAvgSectorsReadPerDirectRead
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connAvgSectorsReadPerDirectRead'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
128 Version 2.1.0
Usage NotesDirect reads result in poor performance because the data is physically read from disk eachtime instead of being read from the buffer pool. If you are using system monitors to trackinput and output for the device, this value helps you distinguish database input and outputfrom non-database input and output.
See AlsoNone
129Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Average # of sectors written per direct write
DescriptionReturns the average number of sectors that are written in a direct write by this application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnAvgSectorsWritePerDirectWrite
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connAvgSectorsWritePerDirectWrite'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
130 Version 2.1.0
Usage NotesDirect writes result in poor performance because the data is physically written from diskeach time instead of being written from the buffer pool. If you are using system monitors totrack input and output for the device, this value helps you distinguish database input andoutput from non-database input and output.
See AlsoNone
131Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Buffer pool time waited for prefetch (ms)
DescriptionReturns the time (in milliseconds) that an application waited for an input and output server(prefetcher) to finish loading pages into the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnTimeWaitedforPreFetch
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connTimeWaitedforPreFetch'-a '*Local.DB2Instance1.930131214645'"<profilename>"
Default Thresholds and ActionsNone
132 Version 2.1.0
Usage NotesUse the returned value to measure and refine the number of input and output servers andtheir sizes.
See AlsoNone
133Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Data page writes
DescriptionReturns the number of times a buffer pool data page was physically written to disk.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolDataWrites
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPoolDataWrites'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
134 Version 2.1.0
Usage NotesIf a buffer pool data page is written to disk for a high percentage of the Buffer Pool DataPhysical Reads, you can improve performance by increasing the number of buffer poolpages available for the database.
A buffer pool data page is written to disk for the following two reasons:
¶ To free a page in the buffer pool so that another data page can be read
¶ To flush the buffer pool
The system does not always write a page to make room for a new one. If the page has notbeen updated, it can simply be replaced. This replacement is not counted for this element.
The data page can be written by an asynchronous page-cleaner agent before the buffer poolspace is required. These asynchronous page writes are included in the value of this elementin addition to synchronous page writes.
See AlsoNone
135Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Index page reads
DescriptionReturns the number of physical read requests made by the application to get index pagesinto the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolIndexPReads
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPooIndexPReads'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
136 Version 2.1.0
Usage NotesThe returned value is used in conjunction with logical reads to calculate the buffer poolindex page hit ratio for the application.
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Percent buffer pool hit ratio, index” onpage 144
137Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Index page writesconn: Index page writes
DescriptionReturns the number of buffer pool index pages written to disk by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolIndexWrites
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPoolIndexWrites'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
138 Version 2.1.0
Usage NotesLike a data page, a buffer pool index page is written to disk for the following two reasons:
¶ To free a page in the buffer pool so that another data page can be read
¶ To flush the buffer pool
The system does not always write a page to make room for a new one. If the page has notbeen updated, it can simply be replaced. This replacement is not counted for this element.
The index page can be written by an asynchronous page-cleaner agent before the buffer poolspace is required. These asynchronous index page writes are included in the value of thiselement in addition to synchronous page writes.
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Percent buffer pool hit ratio,data+index” on page 142
139Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Logical data readsconn: Logical data reads
DescriptionReturns the number of requests made by the application to read data pages using the bufferpool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolDataLReads
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPoolDataLReads'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
140 Version 2.1.0
Usage NotesThis count includes access to data that is:
¶ Already in the buffer pool when the database manager needs to process the page
¶ Read into the buffer pool before the database manager can process the page
The returned value is used to calculate the percent buffer pool hit ratio (data and indexreads) for the application.
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Percent buffer pool hit ratio,data+index” on page 142
141Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Percent buffer pool hit ratio, data+index
DescriptionReturns the overall buffer pool hit ratio (as a percentage) for the application during themonitoring interval. This hit ratio includes both index and data page activity.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolHitRatio
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPoolHitRatio'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
142 Version 2.1.0
Usage NotesThe overall buffer pool hit ratio is the ratio of the number of accesses to pages (data andindex) already in the buffer pool to the total number of read requests for pages (data andindex) that use the buffer pool. The total number of read requests for pages includes pagesthat must be loaded into the buffer pool before the request can be fulfilled and pages that arealready in the buffer pool.
If the hit ratio is low (for example, a ratio of zero indicates that pages must be read fromdisk for every request), increasing the buffer pool size can improve performance.
Analyze buffer pool usage at the database level because the buffer pool size is configured atthe database level. However, if the buffer pool hit ratio is low for an application, it canindicate that the application has poor performance when compared to other applicationsconnected to the same database.
See AlsoDB2Manager Configuration monitors: “db: buffpage” on page 318
143Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Percent buffer pool hit ratio, index
DescriptionReturns the application’s index page hit ratio (as a percentage) for the buffer pool during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnIndxPlHitRatio
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connIndxPlHitRatio'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
144 Version 2.1.0
Usage NotesThe index page hit ratio for the buffer pool is the ratio of the number of accesses to indexpages already in the buffer pool to the total number of read requests for index pages that usethe buffer pool. The total number of read requests for index pages includes both those indexpages that must be loaded into the buffer pool before the request can be fulfilled and thoseindex pages that are already in the buffer pool.
If the hit ratio is low compared to normal operating levels, increasing the number of bufferpool pages can improve performance.
Typically, you should analyze buffer pool usage at the database level because the buffer poolsize is configured at the database level. However, if the buffer pool hit ratio is low for anapplication, it can indicate the reason that application has poorer performance whencompared to other applications connected to the same database.
See AlsoDB2Manager Configuration monitors: “db: buffpage” on page 318
145Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Percent package cache hit ratio
DescriptionReturns the application’s package cache hit ratio (as a percentage) during the last interval.The package cache hit ratio is the ratio of the difference between the package cache lookupsand the package cache inserts to all package cache lookups.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPkgCacheHitRatio
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPkgCacheHitRatio'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
146 Version 2.1.0
Usage NotesThis percentage tells you whether the package cache is being used efficiently by thisapplication. If the hit ratio is high (greater than 80%), the package cache is performing well.A smaller percentage can indicate that the package cache should be increased. However, it isnot always worthwhile to increase the size of the package cache for an application thatexecutes only once a day. The size of the package cache is set by the pckcacheszconfiguration parameter.
You can use the returned value from the conn: Percent DDL SQL monitor to determinewhether or not the execution of DDL statements is impacting the performance of thepackage cache. Execution of DDL statements can lower the percent package hit ratio(indicating poor performance), but in this case, increasing the size of the package cache willnot necessarily improve overall performance. If DDL statements rarely occur, thenperformance might improve if you increase pckcachesz. If DDL statements frequently occur,then you can limit the use of DDL statements (for example, to certain time periods).
Use the db: Dynamic SQL statements and db: Static SQL statements monitors to provideinformation about the quantity and type of sections being cached for this application.Caching of a section for static or dynamic SQL statements can improve performance,especially when the same statement is used multiple times by the application.
See AlsoDB2Manager Configuration monitors: “db: pckcachesz” on page 333DB2Manager SQL Statement Activity monitors: “conn: Percent DDL SQL” on page 503,“db: Dynamic SQL statements” on page 527, “db: Static SQL statements” on page 536
147Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Pool read time (s)
DescriptionReturns the total time (in seconds) that the application spent processing read requests thatcaused data or index pages to be physically read from the disk to the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolReadTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPoolReadTime'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
148 Version 2.1.0
Usage NotesThe returned value indicates how much time the application performs input and outputoperations for reading pages from disk and into the buffer pool.
See AlsoNone
149Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Pool write time (s)
DescriptionReturns the total time (in seconds) that an application spent physically writing data or indexpages from the buffer pool to disk.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPoolWriteTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connPoolWriteTime'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
150 Version 2.1.0
Usage NotesThe returned value indicates how much time the application performs input and outputoperations for writing pages from the buffer pool to disk.
See AlsoNone
151Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
conn: Total pool I/O time (s)
DescriptionReturns the total time (in seconds) that an application spent performing buffer pool input andoutput operations (reading or writing pages).
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnTotalPoolIoTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'connTotalPoolIoTime'-a '*Local.DB2Instance1.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
152 Version 2.1.0
Usage NotesThe returned value is an indication of how much time the application performs input andoutput operations using the buffer pool.
See AlsoNone
153Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of cleaners due to dirty threshold
DescriptionReturns the number of times that a page cleaner was invoked because the buffer poolreached the dirty page threshold criterion for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPlDrtyPgThrshCln
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPlDrtyPgThrshCln'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the return value to refine the value for the chngpgs_thresh configuration parameter.This parameter sets a limit on the number of changed pages that can reside in the bufferpool. When the number of changed pages exceeds this value, the page cleaners are triggeredto write out pages.
If the returned value is high compared to normal operating levels, your value forchngpgs_thresh can be too low. In this case, pages can be written out too early, requiringthem to be read back in if requested again. If the returned value is low compared to normaloperating levels, your value for chngpgs_thresh can be too high. In this case, too manypages can accumulate in the buffer pool, resulting in pages written out synchronously andreduced performance.
See AlsoDB2Manager Configuration monitors: “db: chngpgs_thresh” on page 320
154 Version 2.1.0
db: # of database files closed
DescriptionReturns the total number of database files that are closed.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbFilesClosed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbFilesClosed'“ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the best value for the maxfilop configuration parameter.
The database manager opens files for reading into and writing out of the buffer pool. Themaximum number of database files that are open by an application at any time is controlledby the maxfilop parameter. If the maximum is reached, one file is closed before a new fileis opened, which can slow performance. See the DB2 Administration Guide for informationabout maxfilop.
See AlsoNone
155Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of direct read requests
DescriptionReturns the number of requests to perform a direct read from disk of one or more sectors ofdata for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDirectReadReqs
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDirectReadReqs'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of sectorsread per direct read monitors.
Direct reads are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Reading LONG VARCHAR columns
¶ Reading LOB columns
¶ Performing a backup
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of sectors read per direct read”on page 175
156 Version 2.1.0
db: # of direct reads from database
DescriptionReturns the number of read operations for the database that did not use the database bufferpool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDirectReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDirectReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of sectorsread per direct read monitor.
Direct reads are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Reading LONG VARCHAR columns
¶ Reading LOB columns
¶ Performing a backup
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of sectors read per direct read”on page 175
157Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of direct write requests
DescriptionReturns the number of requests to perform a direct write of one or more sectors of data forthe database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDirectWriteReqs
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDirectWriteReqs'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of sectorswritten per direct write monitor.
Direct writes are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Writing LONG VARCHAR columns
¶ Writing LOB columns
¶ Performing a restore
¶ Performing a load
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of sectors written per directwrite” on page 176
158 Version 2.1.0
db: # of direct writes to database
DescriptionReturns the number of write operations for the database that do not use the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDirectWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDirectWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of sectorswritten per direct write monitor.
Direct writes are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Writing LONG VARCHAR columns
¶ Writing LOB columns
¶ Performing a restore
¶ Performing a load
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of sectors written per directwrite” on page 176
159Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of log space cleaners invoked
DescriptionReturns the number of times a page cleaner was invoked because the used logging spacereached a predefined criterion for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolLsnGapClns
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolLsnGapClns'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help determine if you have enough space for logging, log files, orlarger log files.
Page cleaners are invoked if the size of the log that would need to be read during a databaserecovery would exceed the value given by the following formula: logprimary × logfilsiz ×softmax, where:
¶ The logprimary configuration parameter sets the number of primary log files.
¶ The logfilsiz configuration parameter sets the size of the log files.
¶ The softmax configuration parameter determines the percentage of the log to be filledbefore the database manager takes a soft checkpoint.
Knowing how often log space cleaners are invoked can help you to adjust the values forlogfilsiz and softmax. While lowering softmax can reduce database recovery time, it canalso increase system overhead because soft checkpoints are taken more frequently. Whenusing this monitor, it is recommended that you check the percent increase during themonitoring interval. See the DB2 Administration Guide for information.
See AlsoDB2Manager Configuration monitors: “db: logprimary” on page 324
160 Version 2.1.0
db: # of page cleans in an interval
DescriptionReturns the number of times a page cleaner was invoked for the database (for any reason)during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPageCleans
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPageCleans'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how often pages are written to disk by the database’spage cleaners. If this value increases over time, you can define more page cleaners. Thenumber of page cleaners is determined by the num_iocleaners configuration parameter.
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330
161Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of pages for each prefetch request
DescriptionReturns the number of data pages read per prefetch request for the database during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPagesPerPrefetch
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPagesPerPrefetch'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the amount of asynchronous input and output done ineach interaction with the prefetcher.
An excessively low returned value when compared to normal operating levels indicates thatyou need more input and output servers. The more input and output servers that you have,the better your query performance.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332
162 Version 2.1.0
db: # of pool reads
DescriptionReturns the total number of physical read requests to get data or index pages into the bufferpool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalPoolReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalPoolReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned values for other monitors; for example,the overall buffer pool hit ratio, which is returned by the conn: Percent buffer pool hitratio, data+index monitor.
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Percent buffer pool hit ratio,data+index” on page 142
163Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of pool writes
DescriptionReturns the total number of times that buffer pool data or index pages were physicallywritten to disk for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalPoolWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalPoolWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned values for thedb: Average # of poolwrites per pool read and db: Average # of async writers per pool write monitors.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of pool writes per pool read” onpage 174, “db: Average # of async writes per pool write” on page 173
164 Version 2.1.0
db: # of prefetch requests in an interval
DescriptionReturns the number of asynchronous read requests for the database during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncDatRdRq
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncDatRdRq'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the db: # of pages for each prefetch requestmonitor. This value can help you determine the amount of asynchronous input and outputdone in each interaction with the prefetcher.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332
165Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of synchronous I/O
DescriptionReturns the total number of synchronous reads and writes for both data and index pages.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalSyncIos
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalSyncIos'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into how well the prefetchers and page cleaners areworking and help you refine the num_ioservers and num_iocleaners configurationparameters.
Because synchronous input and output operations are performed by database agents, a highnumber of operations can slow performance.
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330, “db:num_ioservers” on page 332,
166 Version 2.1.0
db: # of synchronous index reads
DescriptionReturns the number of physical index pages that were read synchronously for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSyncIndexReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbSyncIndexReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesBy comparing the ratio of asynchronous reads to synchronous reads (db: Buffer pool asyncdata reads), you can determine how well the prefetchers are working. Use this to refine thenum_ioservers configuration parameters.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332DB2Manager Buffer Pool I/O monitors:“db: Buffer pool async data reads” on page 186
167Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of synchronous index writesdb: # of synchronous index writes
DescriptionReturns the number of physical index page write requests that were performedsynchronously for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSyncIndexWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbSyncIndexWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesBy comparing the ratio of asynchronous writes to synchronous writes, you can determinehow well the buffer pool page cleaners are performing. Use this to refine thenum_iocleaners configuration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool async index writes” on page 189DB2Manager Configuration monitors: “db: num_iocleaners” on page 330
168 Version 2.1.0
db: # of synchronous reads
DescriptionReturns the number of times physical data pages were read synchronously into the bufferpool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSyncDataReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbSyncDataReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the db: Buffer pool async data readsmonitor to gain insight into how well the prefetchers are working and to refine thenum_ioservers configuration parameter.
Because synchronous reads are performed by database agents, a high number of reads canslow performance.
See AlsoDB2Manager Buffer Pool I/O monitors:“db: Buffer pool async data reads” on page 186DB2Manager Configuration monitors: “db: num_ioservers” on page 332
169Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: # of synchronous writes
DescriptionReturns the number of times that data pages were written synchronously from the bufferpool to disk for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSyncDataWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbSyncDataWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value with the value returned by the db: Buffer pool async datawrites monitor to gain insight into how well the page cleaners are working and to refine thenum_iocleaners configuration parameter.
Because synchronous writes are performed by database agents, a high number of writes canslow performance.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool async data writes” on page 187DB2Manager Configuration monitors: “db: num_iocleaners” on page 330
170 Version 2.1.0
db: # of victim page cleaners invoked
DescriptionReturns the number of times a page cleaner was invoked because a synchronous write wasneeded to make space for new pages in the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPlDrtyPgStealCln
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPlDrtyPgStealCln'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWhen the number of changed (dirty) pages in the buffer pool reaches the value for thechngpgs_thresh configuration parameter, victim page cleaning is invoked to asynchronouslywrite these pages to disk. Victim pages are pages that have been selected for an action to beperformed on them, for example, pages that will be written to disk.
If the returned value is low compared to normal operating levels, you might have too manypage cleaners defined and they can be writing out changed pages that would be changedagain later. Aggressive cleaning defeats one purpose of the buffer pool, which is to deferwriting to disk until the last possible moment.
If the returned value is high compared to normal operating levels, you might have too fewpage cleaners defined. Too few page cleaners can increase the time for recovering thedatabase after failures.
The number of page cleaners defined is determined by the value of the num_iocleanersconfiguration parameter.
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330
171Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average # of async reads per pool read
DescriptionReturns the ratio of buffer pool asynchronous data reads to the total number of pool readsfor the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgAsyncReadsPerTotReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgAsyncReadsPerTotReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into how well the prefetchers are working and torefine the num_ioservers configuration parameter. If the returned value is low compared tonormal operating levels, there might not be enough input and output servers to prefetch datainto the buffer, causing the database manager agents to spend extra time on physical reads.Increase the number of input and output servers by increasing the value of num_ioserversconfiguration parameter. If too many servers are allocated, system performance is notreduced because the extra input and output servers are not used.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332
172 Version 2.1.0
db: Average # of async writes per pool write
DescriptionReturns the ratio of buffer pool asynchronous writes (data and index) to the total number ofpool writes for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgAsyncWritesPerTotWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgAsyncWritesPerTotWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into how well the page cleaners are working and torefine the num_iocleaners configuration parameter. If the returned value is low compared tonormal operating levels, increase the number of input and output cleaners by increasing thevalue of num_iocleaners. If the returned value is high compared to normal operating levels,you can save system resources by decreasing the number of input and output cleaners (bydecreasing the value of num_iocleaners).
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330
173Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average # of pool writes per pool read
DescriptionReturns the ratio of total pool writes to pool reads for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgPlWritesPerPlReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgPlWritesPerPlReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is greater than 1, you can improve performance by increasing theavailable buffer pool space. A returned value greater than 1 indicates that at least one writeto disk had to occur (either to free a page in the buffer poo, or to flush the buffer pool)before a page could be read into the buffer pool.
You can increase the available buffer pool space by freeing the space more often (byincreasing the chngpgs_thresh or num_iocleaners configuration parameters) or byincreasing the total space for the buffer pool (by increasing the buffpage configurationparameter).
See AlsoDB2Manager Configuration monitors: “db: chngpgs_thresh” on page 320, “db:num_iocleaners” on page 330, “db: buffpage” on page 318
174 Version 2.1.0
db: Average # of sectors read per direct read
DescriptionReturns the average number of sectors that are read by a direct read for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgSectorsReadPerDirectRead
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgSectorsReadPerDirectRead'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesDirect reads do not use the buffer pool, and so result in poor performance because the datais physically read from disk each time. If you are using system monitors to track input andoutput for the device, this value helps you distinguish database input and output fromnon-database input and output.
See AlsoNone
175Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average # of sectors written per direct writewrite
DescriptionReturns the average number of sectors that are written by a direct write to the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgSectorsWritePerDirectWrite
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgSectorsWritePerDirectWrite'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesDirect writes do not use the buffer pool, which results in poor performance because the datais physically written from disk each time. If you are using system monitors to track inputand output for the device, this value helps you distinguish database input and output fromnon-database input and output.
See AlsoNone
176 Version 2.1.0
db: Average direct read time (ms)
DescriptionReturns the average time (in milliseconds) that is used to perform direct reads to thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgDirectReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgDirectReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesNone
See AlsoNone
177Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average direct write time (ms)
DescriptionReturns the average time (in milliseconds) for performing direct writes to the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgDirectWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgDirectWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time can indicate the existence of an input and output conflict.
See AlsoNone
178 Version 2.1.0
db: Average pool I/O time (ms)
DescriptionReturns the average time (in milliseconds) for performing buffer pool input and outputoperations (reading or writing) to the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgPoolIoTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgPoolIoTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time can indicate the existence of an input and output conflict. In this case,you might need to move data to a different device.
The returned value includes the time applied to asynchronous input and output operations(which are performed by prefetchers and page cleaners).
See AlsoNone
179Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average pool read time (ms)
DescriptionReturns the average time (in milliseconds) for processing database read requests that causeddata or index pages to be physically read from the disk to the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgPoolReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgPoolReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time generally indicates the existence of an input and output conflict. In thiscase, you might need to move data to a different device.
The returned value includes the time applied to asynchronous read operations that areperformed by prefetchers.
See AlsoNone
180 Version 2.1.0
db: Average pool write time (ms)
DescriptionReturns the average time (in milliseconds) to process write requests that have caused data orindex pages to be physically written from buffer pool to disk.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgPoolWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgPoolWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time generally indicates the existence of an input and output conflict. In thiscase, you might need to move data to a different device.
The returned value includes the time applied to asynchronous write operations that areperformed by page cleaners.
See AlsoNone
181Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average synchronous data read time (ms)
DescriptionReturns the average time (in milliseconds) for synchronous data reads to be performed forthe database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgSyncReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgSyncReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to analyze the input and output work being performed for thedatabase. Synchronous read operations for a database are performed by database manageragents. Asynchronous reads are performed by prefetchers, which read data pages from diskinto the buffer pool in anticipation of their use.
If the returned value is high compared to the average time applied to asynchronous datareads, you can increase the amount of prefetching by increasing the num_ioserversconfiguration parameter or turning on the seqdetect configuration parameter.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332, “db:seqdetect” on page 336
182 Version 2.1.0
db: Average synchronous data write time (ms)
DescriptionReturns the average time (in milliseconds) to perform synchronous data writes for thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgSyncWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgSyncWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to analyze the input and output work being performed for thedatabase. Synchronous write operations for a database are performed by database manageragents. Asynchronous writes are performed by page cleaners, which write out changed pagesto disk and free up space in the buffer pool.
If the returned value is high compared to the average time applied to asynchronous datawrites, you can increase the number of page cleaners by using the num_iocleanersconfiguration parameter.
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330
183Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Average synchronous I/O (ms)
DescriptionReturns the average time (in milliseconds) to perform synchronous input and outputoperations for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgSyncIoTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbAvgSyncIoTime'"<profilename>"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to analyze the input and output work being performed for thedatabase. Synchronous input and output operations for a database are performed by databasemanager agents. Asynchronous input and output operations are performed by prefetchers(reads) and page cleaners (writes). In general, asynchronous input and output helps yourapplications run faster.
See AlsoNone
184 Version 2.1.0
db: Avg # of pages for each cleaner
DescriptionReturns the average number of pages written per page cleaner that are invoked for thedatabase during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPagesPerClean
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPagesPerClean'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how many pages are handled by this database’s pagecleaners. If this value increases over time, you can define more page cleaners. The numberof page cleaners is determined by the num_iocleaners configuration parameter.
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330
185Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool async data reads
DescriptionReturns the number of data pages read asynchronously into the buffer pool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncDataReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncDataReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of asyncreads per pool read monitor.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of async reads per pool read”on page 172
186 Version 2.1.0
db: Buffer pool async data writes
DescriptionReturns the number of times that a buffer pool data page was written asynchronously to diskfor the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncDataWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncDataWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of asyncwrites per pool write monitor.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average # of async writes per pool write”on page 173
187Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool async index reads
DescriptionReturns the number of index pages that are read for the database asynchronously into thebuffer pool by a prefetcher.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncIndexReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncIndexReads"ManufacturingProfile"
Usage NotesBy comparing the ratio of asynchronous to synchronous reads, you can determine how wellthe prefetchers are working. This ratio can be helpful when you are refining thenum_ioservers configuration parameters. Asynchronous reads are performed by databasemanager prefetchers.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332DB2Manager Buffer Pool I/O monitors:“db: # of synchronous index reads” on page 167
188 Version 2.1.0
db: Buffer pool async index writes
DescriptionReturns the number of times that a buffer pool index page was written (for the database)asynchronously to disk.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncIndexWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncIndexWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the db: Average # of asyncwrites per pool write monitor.
By comparing the ratio of asynchronous to synchronous writes, you can determine how wellthe buffer pool page cleaners are performing. This ratio can be helpful when you are refiningthe num_iocleaners configuration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors:“db: # of synchronous index writes” on page 168,“db: Average # of async writes per pool write” on page 173
DB2Manager Configuration monitors: “db: num_iocleaners” on page 330,
189Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool async read time (ms)
DescriptionReturns the total time (in milliseconds) that the database manager prefetchers spent readingdata or index pages into the buffer pool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the db: Synchronous read time (ms)monitor to understand where input and output time is being spent.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Synchronous read time (ms)” on page 212
190 Version 2.1.0
db: Buffer pool async write time (ms)
DescriptionReturns the total time (in milliseconds) that the database manager page cleaners spentwriting data or index pages from the buffer pool to disk for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolAsyncWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolAsyncWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the db: Synchronous write time (ms)monitor to understand where input and output time is being spent.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Synchronous write time (ms)” on page 213
191Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool data logical reads
DescriptionReturns the number of logical read requests for data pages that went through the buffer poolfor the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolDataLReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolDataLReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the value for the db: Percent buffer pool hit ratio,data+index monitor.
The returned value includes requests for data that is
¶ Already in the buffer pool.
¶ Read from disk into the buffer pool to fulfill the request. The count for these is given bythe db: Buffer pool data physical reads monitor.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Percent buffer pool hit ratio, data+index”on page 207, “db: Buffer pool data physical reads” on page 195
192 Version 2.1.0
db: Buffer pool data pages copied from extended storage
DescriptionReturns the number of buffer pool data pages copied from extended storage for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDataPagesCopiedfromExtendedStorage
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDataPagesCopiedfromExtendedStorage'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesRequired pages are copied from extended storage to the buffer pool if they are not in thebuffer pool but are in extended storage. This copying can incur the cost of connecting to theshared memory segment but saves the cost of a disk read.
See AlsoNone
193Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool data pages copied to extended storage
DescriptionReturns the number of buffer pool data pages copied to extended storage for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDataPagesCopiedtoExtendedStorage
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDataPagesCopiedtoExtendedStorage'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesPages are copied from the buffer pool to extended storage when they are selected as victimpages. This copying is required to make space for new pages in the buffer pool.
See AlsoNone
194 Version 2.1.0
db: Buffer pool data physical reads
DescriptionReturns the number of read requests that required input and output to get data pages into thebuffer pool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolDataPReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolDataPReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the return values for the db: Percent buffer pool hitratio, data+index and db: # of synchronous reads monitors.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Percent buffer pool hit ratio, data+index”on page 207, “db: # of synchronous reads” on page 169
195Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool data writes
DescriptionReturns the number of times that a buffer pool data page was physically written to disk forthe database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolDataWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolDataWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to the value returned by the db: Buffer pool dataphysical reads monitor, you can improve performance by increasing the available bufferpool space. You can increase the available buffer pool space by completing the following:
¶ Free space more often by writing out changed pages. You can achieve this by increasingthe chngpgs_thresh or num_iocleaners configuration parameter.
¶ Increase the total space for the buffer pool. You can achieve this by increasing thebuffpage configuration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool data physical reads” on page 195DB2Manager Configuration monitors: “db: num_iocleaners” on page 330,“db: chngpgs_thresh” on page 320, “db: buffpage” on page 318
196 Version 2.1.0
db: Buffer pool index logical reads
DescriptionReturns the number of logical read requests applied to index pages that went through thebuffer pool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolIndexLReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolIndexLReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the db: Percent buffer pool hit ratio,data+index and db: Percent buffer pool hit ratio, index monitors.
The returned value includes requests for index pages that are as follows:
¶ Already in the buffer pool.
¶ Read from disk into the buffer pool to fulfill the request (the count for these is given bythe db: Buffer pool index physical reads monitor).
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool index physical reads” onpage 200, “db: Percent buffer pool hit ratio, data+index” on page 207, “db: Percentbuffer pool hit ratio, index” on page 209
197Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool index pages copied from extended storage
DescriptionReturns the number of buffer pool index pages copied from extended storage for thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIndexPagesCopiedfromExtendedStorage
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbIndexPagesCopiedfromExtendedStorage'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesRequired index pages are copied from extended storage to the buffer pool if they are not inthe buffer pool but are in extended storage. This copying will incur the cost of connecting tothe shared memory segment but saves the cost of a disk read.
See AlsoNone
198 Version 2.1.0
db: Buffer pool index pages copied to extended storage
DescriptionReturns the number of buffer pool index pages copied to extended storage for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIndexPagesCopiedtoExtendedStorage
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbIndexPagesCopiedtoExtendedStorage'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesPages are copied from the buffer pool to extended storage when they are selected as victimpages. This copying is required to make space for new pages in the buffer pool.
See AlsoNone
199Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool index physical reads
DescriptionReturns the number of physical read requests to get index pages into the buffer pool for thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolIndexPReads
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolIndexPReads'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for other buffer pool monitors, for example, thedb: Percent buffer pool hit ratio, data+index and db: Percent buffer pool hit ratio,index monitors.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Percent buffer pool hit ratio, data+index”on page 207, “db: Percent buffer pool hit ratio, index” on page 209
200 Version 2.1.0
db: Buffer pool index writes
DescriptionReturns the number of times that a buffer pool index page was physically written to disk forthe database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolIndexWrites
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolIndexWrites'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to the value returned by the db: Buffer pool indexphysical reads monitor, you can improve performance by increasing available buffer poolspace. You can increase available buffer pool space by completing the following:
¶ Free space more often by writing out changed pages. You can achieve this by increasingthe chngpgs_thresh or num_iocleaners configuration parameter.
¶ Increase the total space for the buffer pool. You can achieve this by increasing thebuffpage configuration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool data physical reads” onpage 195 DB2Manager Configuration monitors: “db: num_iocleaners” on page 330, “db:chngpgs_thresh” on page 320, “db: buffpage” on page 318
201Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Buffer pool I/Os per second
DescriptionReturns the rate (per second) of buffer pool input and output operations for the database. Forthis monitor, buffer pool input and output includes all physical data and index pages that gothrough the buffer pool when read or written.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolIoRate
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolIoRate'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how efficient your data storage device is. A low valueindicates the presence of an input and output wait, in which case you should move data to adifferent device.
See AlsoNone
202 Version 2.1.0
db: Buffer pool time waited for prefetch (ms)
DescriptionReturns the time (in milliseconds) applied to all applications spent waiting for an input andoutput server (prefetcher) to finish loading pages into the buffer pool (for the database)during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTimeWaitedforPreFetch
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTimeWaitedforPreFetch'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to measure and refine the number of input and output servers andserver sizes.
See AlsoNone
203Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Direct read time (ms)
DescriptionReturns the time (in milliseconds) for performing the direct reads for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDirectReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDirectReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the db: Average direct read time (ms)monitor. A high average time compared to normal operating levels can indicate an input andoutput conflict.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average direct read time (ms)” onpage 177
204 Version 2.1.0
db: Direct write time (ms)
DescriptionReturns the time (in milliseconds) for performing the direct writes for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDirectWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbDirectWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the db: Average direct read time (ms)monitor. A high average time compared to normal operating levels can indicate an input andoutput conflict.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average direct read time (ms)” onpage 177
205Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Extended storage read/write ratio
DescriptionReturns the ratio (as a percentage) of data+index pages copied from extended storage topages copied to extended storage during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbExtendedStorageReadWriteRatio
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbExtendedStorageReadWriteRatio'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWhen a page is transferred from extended storage to the buffer pool, you save a systeminput and output call. However, you still incur the cost of attaching to the extended memorysegment, copying the page, and detaching from the segment.
Use the returned value to determine if you would benefit from using extended storage. Thehigher the ratio, the more likely you are to benefit. In general, extended storage isparticularly useful if input and output activity is very high on your system.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool data pages copied fromextended storage” on page 193, “db: Buffer pool data pages copied to extended storage”on page 194, “db: Buffer pool index pages copied from extended storage” on page 198,
“db: Buffer pool index pages copied to extended storage” on page 199
206 Version 2.1.0
db: Percent buffer pool hit ratio, data+index
DescriptionReturns the overall buffer pool hit ratio (as a percentage) for the database during themonitoring interval. This hit ratio includes both index and data page activity.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPoolHitRatio
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbPoolHitRatio'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 20 shows the suggested threshold values for severity levels.
Table 20. dbPoolHitRatio Response LevelsResponse Level Trigger When Default Actions
critical Less than 80% Send Tivoli Notice; Change Icon
severe Less than 90% Send Tivoli Notice; Change Icon
warning Less than 95% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesThe overall buffer pool hit ratio indicates the percentage of page requests for which thedatabase manager did not need to load a page from disk to service. (That is, the page wasalready in the buffer pool.) The greater the buffer pool hit ratio, the lower the frequency ofdisk input and output.
If the hit ratio is low compared to normal operating levels, increasing the number of bufferpool pages can improve performance. A ratio of zero indicates that pages needed to be readfor every request.
For a large database, increasing the buffer pool size can have a minimal effect on the bufferpool hit ratio. Such a database can have so large a number of data pages that the statisticalchance of a hit is not increased by an increase of the buffer pools. However, even thoughthe data might be too large to fit in the buffer pool, the entire index can fit. In this case, you
207Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
can refine buffer pool sizes until the overall buffer pool hit ratio stops increasing, then refinethe buffer pool until the buffer pool index hit ratio (db: Percent buffer pool hit ratio) nolonger increases.
See AlsoDB2Manager Buffer Pool I/O monitors:“db: Percent buffer pool hit ratio, data+index” on page 207DB2Manager Configuration monitors: “db: buffpage” on page 318
208 Version 2.1.0
db: Percent buffer pool hit ratio, index
DescriptionReturns the database’s index page hit ratio (as a percentage) for the buffer pool during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbIndxPlHitRatio
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbIndxPlHitRatio'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 21 shows the suggested threshold values for severity levels.
Table 21. dbIndxPlHitRatio Response LevelsResponse Level Trigger When Default Actions
critical Less than 80% Send Tivoli Notice; Change Icon
severe Less than 90% Send Tivoli Notice; Change Icon
warning Less than 95% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesThe index page hit ratio for the buffer pool indicates the percentage of index page requestsfor which the database manager did not need to load an index page from disk to service.That is, the index page was already in the buffer pool. The higher the returned value, thelower the frequency of disk input and output, and the faster the performance.
If the hit ratio is low compared to normal operating levels, increasing the number of bufferpool pages can improve performance.
See AlsoDB2Manager Configuration monitors: “db: buffpage” on page 318
209Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Percent catalog cache hit ratio
DescriptionReturns the catalog cache hit ratio (as a percentage) for the database during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCatCacheHitRatio
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbCatCacheHitRatio'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 22 shows the suggested threshold values for severity levels.
Table 22. dbCatCacheHitRatio Response LevelsResponse Level Trigger When Default Actions
critical Less than 85% Send Tivoli Notice; Change Icon
severe Less than 90% Send Tivoli Notice; Change Icon
warning Less than 95% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesThe catalog cache hit ratio indicates how successful the catalog cache is. The returned ratiois the ratio of successful catalog cache lookups to the total number of catalog cache lookups.A low ratio when compared to normal operating levels indicates more failed lookups weremade to the catalog cache while a table, view, or alias reference in an SQL statement wasbeing processed.
If the returned value is low compared to normal operating levels, you can increase the sizeof the catalog cache by increasing the catalogcache_sz configuration parameter. You canexpect a small ratio following the first connection to the database. In addition, heavy use ofDDL SQL statements can also decrease this ratio.
210 Version 2.1.0
See AlsoDB2Manager SQL Statement Activity monitors: “db: Percent DDL SQL” on page 529DB2Manager Configuration monitors:“db: catalogcache_sz” on page 319
211Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Synchronous read time (ms)
DescriptionReturns the time (in milliseconds) applied to synchronous reads for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSyncReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbSyncReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the db: Buffer pool async read time(ms) monitor to understand where input and output time is being applied.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool async read time (ms)” onpage 190
212 Version 2.1.0
db: Synchronous write time (ms)
DescriptionReturns the time (in milliseconds) applied in synchronous writes to disk for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSyncWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbSyncWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the db: Buffer pool async write time(ms) monitor to understand where input and output time is being applied.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool async write time (ms)” onpage 191
213Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Total direct I/O time (ms)
DescriptionReturns the total time (in milliseconds) applied to direct reads and writes for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalDirectIoTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalDirectIoTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value indicates the amount of time that the database performs direct reads andwrites. A high returned value compared to normal operating levels can indicate the presenceof an input and output conflict.
See AlsoNone
214 Version 2.1.0
db: Total pool physical I/O (ms)
DescriptionReturns the total time (in milliseconds) applied to physical buffer pool input and outputoperations (including both synchronous and asynchronous reads and writes) for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalPoolIoTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalPoolIoTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high returned value (as compared to the total number of physical buffer pool input andoutput operations) can indicate the presence of an input and output wait, which in turn canindicate that you should move data to a different device.
See AlsoNone
215Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Total pool physical read (ms)
DescriptionReturns the total time (in milliseconds) applied to processing read requests that caused dataor index pages to be physically read from disk to the buffer pool for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalReadTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalReadTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the average pool read time, which is returned by thedb: Average pool read time (ms) monitor. This average can indicate the presence of aninput and output wait, which in turn can indicate that you should move data to a differentdevice.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average pool read time (ms)” on page 180
216 Version 2.1.0
db: Total pool physical write (ms)
DescriptionReturns the total time (in milliseconds) for buffer pool physical writes (includingasynchronous writes).
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalWriteTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalWriteTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the average pool write time, which is returned by thedb: Average pool write time (ms) monitor. This average can indicate the presence of aninput and output wait, which in turn can indicate that you should move data to a differentdevice.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average pool write time (ms)” on page 181
217Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
db: Total synchronous I/O time (ms)
DescriptionReturns the total time (in milliseconds) applied to processing requests for synchronous readsor writes for the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalSyncIoTime
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbTotalSyncIoTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is the sum of the returned values from the db: Average pool write time(ms) and db: Average pool read time (ms) monitors. This time is the amount of time thatdatabase agents spend doing synchronous reads and writes.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average pool write time (ms)” on page 181,“db: Average pool read time (ms)” on page 180
218 Version 2.1.0
dbp: # of FCM nodes
DescriptionReturns the number of nodes in the current DB2 partitioned configuration.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpTotFcmNodes
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpTotFcmNodes'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesNone
See AlsoNone
219Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Connection status
DescriptionReturns the status of the communication connection between the database partition specifiedby the DB2 Node Number variable and the database partition where this monitor executes.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Node NumberSpecifies the number of the node for which you are checking the communicationconnection status. For node number specifications, see the db2nodes.cfg file.
CLI SynopsisdbpConnStatus
-a <DB2_node_number>
The following briefly describes the argument for this monitor:
<DB2_node_number>Specifies the number of the node for which you are checking the communicationconnection status. For node number specifications, see the db2nodes.cfg file.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpConnStatus'-a '1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesTwo nodes can be active, but the connection between them will remain inactive unless thereis active communication between them.
220 Version 2.1.0
The connection values are given in Table 23.
Table 23. dbpConnStatus Connection ValuesValue Connection Type
0 No current connection
1 Active connection
2 Congested connection
See AlsoNone
221Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: FCM buffers currently free
DescriptionReturns the number of FCM buffers that are free in the partitioned database server duringthe monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpFreeFcmBuf
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpFreeFcmBuf'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_buffers monitor to determine thecurrent buffer pool utilization. Use this information to refine the fcm_num_buffersconfiguration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_buffers” on page 341
222 Version 2.1.0
dbp: FCM connection entries currently free
DescriptionReturns the number of connection entries that are free in the partitioned database serverduring the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpFcmConnFree
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpFcmConnFree'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_connect configuration parameterto determine the current connection entry utilization. You can use this information to refinethe fcm_num_connect parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_connect” on page 342
223Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: FCM request blocks currently free
DescriptionReturns the number of request blocks that are free in the partitioned database server duringthe monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpFcmReqBlkFree
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpFcmReqBlkFree'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_rqb configuration parameter todetermine the current request block utilization. You can use this information to refinefcm_num_rqb.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_rqb” on page 343
224 Version 2.1.0
dbp: Minimum FCM buffers free
DescriptionReturns the lowest number of free buffers reached during processing in the partitioneddatabase server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpMinFcmBufFree
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpMinFcmBufFree'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_buffers monitor to determine themaximum FCM buffer pool utilization. You can use this information to refinefcm_num_buffers.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_buffers” on page 341
225Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Minimum FCM connection entries free
DescriptionReturns the lowest number of free connection entries reached during processing in thepartitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpMinFcmConnEntries
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpMinFcmConnEntries'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_connect configuration parameterto determine the maximum connection entry utilization. If the number of free connectionentries reached during processing is low compared to normal operating levels, you shouldincrease the fcm_num_connect configuration parameter to ensure that operations do notlack connection entries. If the number of free connection entries reached during processing ishigh compared to normal operating levels, you can decrease the fcm_num_connectconfiguration parameter to conserve system resources.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_connect” on page 342
226 Version 2.1.0
dbp: Minimum FCM message anchors free
DescriptionReturns the lowest number of free message anchors reached during processing in thepartitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpMinFcmMsgAnchors
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpMinFcmMsgAnchors'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_anchors configuration parameterto determine the current message anchor utilization. You can use this information to refinefcm_num_anchors.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_anchors” on page 340
227Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Minimum FCM request blocks free
DescriptionReturns the lowest number of free request blocks reached during processing in thepartitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpFcmReqBlk
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpFcmReqBlk'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value in conjunction with the fcm_num_rqb configuration parameter todetermine the maximum request block utilization. If the number of free request blocksreached during processing is low compared to normal operating levels, increase thefcm_num_rqb configuration parameter to ensure that operations do not lack request blocks.If the number of free request blocks reached during processing is high compared to normaloperating levels, you can decrease the fcm_num_rqb configuration parameter to conservesystem resources.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_rqb” on page 343
228 Version 2.1.0
dbp: Percent FCM buffers currently used
DescriptionReturns the percentage of FCM buffers that are used within the partitioned database serverduring the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctFcmBufUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctFcmBufUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 24 shows the suggested threshold values for severity levels.
Table 24. dbpPctFcmBufUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of FCM buffers used is high compared to normal operating levels, you canadjust the fcm_num_buffers configuration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_buffers” on page 341DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
229Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Percent FCM connection entries currently used
DescriptionReturns the percentage of FCM connection entries that are used within the partitioneddatabase server during the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctFcmConnEntriesUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctFcmConnEntriesUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 25 shows the suggested threshold values for severity levels.
Table 25. dbpPctFcmConnEntriesUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of FCM connection entries used is high compared to normal operatinglevels, you can increase the fcm_num_connect configuration parameter; if the percentage islow compared to normal operating levels, you can decrease the parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_buffers” on page 341DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
230 Version 2.1.0
dbp: Percent FCM request blocks currently used
DescriptionReturns the percentage of FCM request blocks used within the partitioned database serverduring the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctFcmReqBlkUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctFcmReqBlkUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 26 shows the suggested threshold values for severity levels.
Table 26. dbpPctFcmReqBlkUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of FCM request blocks used is high compared to normal operating levels,you can adjust the fcm_num_rqb configuration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_buffers” on page 341DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
231Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Percent maximum FCM buffers used
DescriptionReturns the percentage of maximum FCM buffers used during processing within thepartitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctMaxFcmBufUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctMaxFcmBufUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 27 shows the suggested threshold values for severity levels.
Table 27. dbpPctMaxFcmBufUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of maximum FCM buffers used is high compared to normal operatinglevels, you can increase the fcm_num_buffers configuration parameter; if the percentage islow compared to normal operating levels, you can decrease the parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_buffers” on page 341DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
232 Version 2.1.0
dbp: Percent maximum FCM connection entries used
DescriptionReturns the maximum percentage of FCM connection entries used during processing withinthe partitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctMaxFcmConnEntriesUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctMaxFcmConnEntriesUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 28 shows the suggested threshold values for severity levels.
Table 28. dbpPctMaxFcmConnEntriesUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of maximum FCM connection entries used is high compared to normaloperating levels, you can increase the fcm_num_connect configuration parameter; if thepercentage is low compared to normal operating levels, you can decrease the parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_connect” on page 342DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
233Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Percent maximum FCM message anchors used
DescriptionReturns the percentage of maximum FCM message anchors during processing within thepartitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctMaxFcmMsgAnchorsUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctMaxFcmMsgAnchorsUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 29 shows the suggested threshold values for severity levels.
Table 29. dbpPctMaxFcmMsgAnchorsUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of maximum FCM message anchors used is high compared to normaloperating levels, you can increase the fcm_num_anchors configuration parameter; if thepercentage is low compared to normal operating levels, you can decrease the parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_anchors” on page 340DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
234 Version 2.1.0
dbp: Percent maximum FCM request blocks used
DescriptionReturns the percentage of maximum FCM request blocks used during processing within thepartitioned database server.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbpPctMaxFcmReqBlksUsed
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpPctMaxFcmReqBlksUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 30 shows the suggested threshold values for severity levels.
Table 30. dbpPctMaxFcmReqBlksUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the percentage of maximum FCM request blocks used is high compared to normaloperating levels, you can adjust the fcm_num_rqb configuration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_anchors” on page 340,“dbms: fcm_num_rqb” on page 343DB2Manager Buffer Pool I/O monitors: “dbp: FCM buffers currently free” on page 222
235Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Total buffers receivedd
DescriptionReturns the total number of FCM buffers received by the database node where this monitorexecutes. The database node is specified in the DB2_node_number variable.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Node NumberSpecifies the number of the node for which you are checking the communicationconnection status. For node number specifications, see the db2nodes.cfg file.
CLI SynopsisdbpTotBufReceived
-a <DB2_node_number>
The following briefly describes the argument for this monitor:
<DB2_node_number>>Specifies the number of the node that you are monitoring. For node numberspecifications, see the db2nodes.cfg file.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpTotBufReceived'-a '1'"ManufacturingProfile"
Default Thresholds and ActionsNone
236 Version 2.1.0
Usage NotesUse the returned value to measure the level of traffic between the node where this monitorexecutes and another node. If the total number of FCM buffers received from the other nodeis high compared to normal operating levels, you can redistribute the database or movetables to reduce the internode traffic.
See AlsoNone
237Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
dbp: Total buffers sent
DescriptionReturns the total number of FCM buffers sent from the database node where this monitorexecutes to the node specified by the DB2_node_number variable.
DB2 Version SupportedDB2 Enterprise-Extended Edition only
Authorization Roleadmin
Target EndpointsDB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Node NumberSpecifies the number of the node for which you are checking the communicationconnection status. For node number specifications, see the db2nodes.cfg file.
CLI SynopsisdbpTotBufSent
-a <DB2_node_number>
The following briefly describes the argument for this monitor:
<DB2_node_number>Specifies the number of the node that you are monitoring. For node numberspecifications, see the db2nodes.cfg file.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'dbpTotBufSent'-a '1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to measure the level of traffic between the current node where thismonitor executes and the node specified by DB2_node_number. If the total number of
238 Version 2.1.0
FCM buffers sent to the other node is high compared to normal operating levels, you canredistribute the database or move tables to reduce the internode traffic.
See AlsoNone
239Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: # of direct read requests
DescriptionReturns the number of requests to perform a direct read from disk of one or more sectors ofdata for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDirectReadReqs
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' tbspDirectReadReqs'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the tbsp: Average # ofsectors read per direct read monitor.
Direct reads are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Reading LONG VARCHAR columns
¶ Reading LOB columns
240 Version 2.1.0
¶ Performing a backup
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average # of sectors read per directread” on page 257
241Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: # of direct reads from database
DescriptionReturns the number of read operations for the tablespace that did not use the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDirectReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDirectReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the tbsp: Average # ofsectors read per direct read monitor.
Direct reads are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Reading LONG VARCHAR columns
¶ Reading LOB columns
¶ Performing a backup
242 Version 2.1.0
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average # of sectors read per directread” on page 257
243Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: # of direct write requests
DescriptionReturns the number of requests to perform a direct write of one or more sectors of data forthe tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDirectWriteReqs
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDirectWriteReqs'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the tbsp: Average # ofsectors written per direct write monitor.
Direct writes are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Writing LONG VARCHAR columns
¶ Writing LOB columns
244 Version 2.1.0
¶ Performing a restore
¶ Performing a load
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average # of sectors written per directwrite” on page 258
245Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: # of direct writes to database
DescriptionReturns the number of write operations for the tablespace that did not use the buffer pool.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDirectWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDirectWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the tbsp: Average # ofsectors written per direct writemonitor.
Direct writes are performed in units, the smallest being a 512-byte sector. They are usedwhile the system is:
¶ Writing LONG VARCHAR columns
¶ Writing LOB columns
¶ Performing a restore
246 Version 2.1.0
¶ Performing a load
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average # of sectors written per directwrite” on page 258
247Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: # of pool reads
DescriptionReturns the total number of physical read requests to get data or index pages into the bufferpool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalPoolReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalPoolReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used with the total pool physical read time to calculate the averagepool read time. The average pool read time is returned by the tbsp: Average pool read time(ms) monitor. This average can indicate the presence of an input and output wait, which canindicate that you should move data to a different device.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average pool read time (ms)” onpage 262
248 Version 2.1.0
tbsp: # of pool writes
DescriptionReturns the total number of times buffer pool data or index pages were physically written todisk for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalPoolWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalPoolWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to the value returned by the tbsp: # of pool readsmonitor, you can improve performance by increasing the available buffer pool space. Youcan increase available buffer pool space by completing the following:
¶ Free space more often by writing out changed pages. You can have space freed moreoften by increasing the chngpgs_thresh or num_iocleaners configuration parameters.
¶ Increase the total space for the buffer pool. You can increase the space for the bufferpool by increasing the buffpage configuration parameter.
249Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: # of pool reads” on page 248DB2Manager Configuration monitors: “db: num_iocleaners” on page 330,“db: chngpgs_thresh” on page 320,“db: buffpage” on page 318
250 Version 2.1.0
tbsp: # of synchronous index reads
DescriptionReturns the number of physical index pages that were read synchronously for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspSyncIndexReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspSyncIndexReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesBy comparing the ratio of asynchronous reads (tbsp: Buffer pool async index writes) tosynchronous reads, you can determine how well the prefetchers are working. This ratio canbe helpful when you are refining the num_ioservers configuration parameters.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool async index writes” on page 273DB2Manager Configuration monitors: “db: num_ioservers” on page 332
251Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: # of synchronous index writes
DescriptionReturns the number of physical index page write requests that were performedsynchronously for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspSyncIndexReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspSyncIndexReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesBy comparing the ratio of asynchronous writes (tbsp: Buffer pool async index writes) tosynchronous writes, you can determine how well the buffer pool page cleaners areperforming. This ratio can be helpful when you are refining the num_iocleanersconfiguration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool async index writes” on page 273DB2Manager Configuration monitors: “db: num_iocleaners” on page 330
252 Version 2.1.0
tbsp: # of synchronous reads
DescriptionReturns the number of times that physical data pages were read synchronously into thebuffer pool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspSyncDataReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspSyncDataReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the tbsp: Buffer pool async datareads monitor to gain insight into how well the prefetchers are working and to refine thenum_ioservers configuration parameter.
Because synchronous reads are performed by database agents, a high number of reads canslow performance.
253Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool async data reads” on page 269DB2Manager Configuration monitors: “db: num_ioservers” on page 332
254 Version 2.1.0
tbsp: # of synchronous writes
DescriptionReturns the number of times that data pages were written synchronously from the bufferpool to disk for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspSyncDataWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspSyncDataWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value with the value returned by the tbsp: Buffer pool async datawrites monitor to gain insight into how well the page cleaners are working and to refine thenum_iocleaners configuration parameter.
Because synchronous writes are performed by database agents, a high number of writes canslow performance.
255Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool async data writes” on page 270DB2Manager Configuration monitors: “db: num_iocleaners” on page 330
256 Version 2.1.0
tbsp: Average # of sectors read per direct read
DescriptionReturns the average number of sectors that are read by a direct read for this tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgSectorsReadPerDirectRead
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgSectorsReadPerDirectRead'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesDirect reads do not use the buffer pool, and so result in poor performance because the datais physically read from disk each time. If you are using system monitors to track input andoutput for the device, this returned value helps you distinguish database input and outputfrom non-database input and output.
See AlsoNone
257Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Average # of sectors written per direct write
DescriptionReturns the average number of sectors that are written by a direct write for this tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgSectorsWritePerDirectWrite
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgSectorsWritePerDirectWrite'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesDirect writes do not use the buffer pool, and so result in poor performance because the datais physically written from disk each time. If you are using system monitors to track inputand output for the device, this returned value helps you distinguish database input and outputfrom non-database input and output.
See AlsoNone
258 Version 2.1.0
tbsp: Average direct read time (ms)
DescriptionReturns the average time (in milliseconds) applied to performing direct reads for thetablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgDirectReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgDirectReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time compared to normal operating levels can indicate the existence of aninput and output conflict.
See AlsoNone
259Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Average direct write time (ms)
DescriptionReturns the average time (in milliseconds) for performing direct writes for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgDirectWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgDirectWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time compared to normal operating levels can indicate the existence of aninput and output conflict.
See AlsoNone
260 Version 2.1.0
tbsp: Average pool I/O time (ms)
DescriptionReturns the average time (in milliseconds) for performing buffer pool input and outputoperations (reading or writing) for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgPoolIoTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgPoolIoTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time compared to normal operating levels can indicate the existence of aninput and output conflict. In this case, you might need to move data to a different device.
The returned value includes the time applied to asynchronous input and output operations(which are performed by prefetchers and page cleaners).
See AlsoNone
261Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Average pool read time (ms)
DescriptionReturns the average time (in milliseconds) for processing read requests that caused data orindex pages to be physically read from disk to buffer pool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgPoolReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgPoolReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time compared to normal operating levels can indicate the existence of aninput and output conflict. In this case, you might need to move data to a different device.
The returned value includes the time applied to asynchronous read operations that areperformed by prefetchers.
See AlsoNone
262 Version 2.1.0
tbsp: Average pool write time (ms)
DescriptionReturns the average time (in milliseconds) for processing write requests that caused data orindex pages to be physically written from buffer pool to disk for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgPoolWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgPoolWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high average time compared to normal operating levels can indicate the existence of aninput and output conflict. In this case, you might need to move data to a different device.
The returned value includes the time applied to asynchronous write operations that areperformed by page cleaners.
See AlsoNone
263Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Average synchronous data read time (ms)
DescriptionReturns the average time (in milliseconds) for synchronous data reads for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgSyncReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgSyncReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to analyze the input and output work being performed for thetablespace. Synchronous read operations are performed by database manager agents.Asynchronous reads are performed by prefetchers, which read data pages from disk into thebuffer pool in anticipation of their use.
If the returned value is high compared to the average time applied to asynchronous datareads, you can increase the amount of prefetching by increasing the num_ioserversconfiguration parameter or turn on the seqdetect configuration parameter.
264 Version 2.1.0
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332
265Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Average synchronous data write time (ms)
DescriptionReturns the average time (in milliseconds) for synchronous data writes for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgSyncWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgSyncWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to analyze the input and output work being performed for thetablespace. Synchronous write operations are performed by database manager agents.Asynchronous writes are performed by page cleaners, which write out changed pages to diskand free up space in the buffer pool.
If the returned value is high compared to the average time applied to asynchronous datawrites, you can increase the number of page cleaners by changing the num_iocleanersconfiguration parameter.
266 Version 2.1.0
See AlsoDB2Manager Configuration monitors: “db: num_iocleaners” on page 330
267Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Average synchronous I/O time (ms)
DescriptionReturns the average time (in milliseconds) for synchronous input and output operations forthe tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspAvgSyncIoTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspAvgSyncIoTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to analyze the input and output work being performed for thetablespace. Synchronous input and output operations are performed by database manageragents. Asynchronous input and output operations are performed by prefetchers (reads) andpage cleaners (writes). In general, asynchronous input and output helps your applications runfaster.
See AlsoNone
268 Version 2.1.0
tbsp: Buffer pool async data reads
DescriptionReturns the number of data pages read asynchronously into the buffer pool for thetablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolAsyncDataReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolAsyncDataReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value with the value returned by the tbsp: # of synchronous readsmonitor to gain insight into how well the prefetchers are working and to refine thenum_ioservers configuration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: # of synchronous reads” on page 253DB2Manager Configuration monitors: “db: num_ioservers” on page 332
269Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool async data writes
DescriptionReturns the number of times a buffer pool data page was written asynchronously to disk forthe tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolAsyncDataWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolAsyncDataWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value with the value returned by the tbsp: # of synchronous writesmonitor to gain insight into how well the page cleaners are working and to refine thenum_iocleaners configuration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: # of synchronous writes” on page 255DB2Manager Configuration monitors: “db: num_iocleaners” on page 330
270 Version 2.1.0
tbsp: Buffer pool async index reads
DescriptionReturns the number of index pages read asynchronously into the buffer pool by a prefetcherwithin the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolAsyncIndexReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolAsyncIndexReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesBy comparing the ratio of asynchronous to synchronous reads (tbsp: # of synchronousindex reads), you can determine how well the prefetchers are working. This ratio can behelpful when you are refining the num_ioservers configuration parameters. Asynchronousreads are performed by database manager prefetchers.
271Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Buffer Pool I/O monitors:“tbsp: # of synchronous index reads” on page 251DB2Manager Configuration monitors: “db: num_ioservers” on page 332
272 Version 2.1.0
tbsp: Buffer pool async index writes
DescriptionReturns the number of times a buffer pool index page was written asynchronously to diskfor the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolAsyncIndexWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolAsyncIndexWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesSubtract the returned value from the value returned by the tbsp: Buffer pool index writesmonitor to calculate the number of synchronous index writes. By comparing the number ofasynchronous index writes to synchronous index writes, you can gain insight into how wellthe buffer pool page cleaners are performing so you can refine the num_iocleanersconfiguration parameter.
273Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
By comparing the ratio of asynchronous to synchronous writes using the tbsp: # ofsynchronous index reads monitor, you can determine how well the buffer pool pagecleaners are performing. This ratio can be helpful when you are refining the num_iocleanersconfiguration parameter.
See AlsoDB2Manager Buffer Pool I/O monitors:“tbsp: # of synchronous index reads” on page 251,“tbsp: Buffer pool async index writes” on page 273
DB2Manager Configuration monitors: “db: num_iocleaners” on page 330
274 Version 2.1.0
tbsp: Buffer pool async read time (ms)
DescriptionReturns the time (in milliseconds) that database manager prefetchers spent reading data intothe buffer pool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolAsyncReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolAsyncReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the tbsp: Synchronous read time (ms)monitor to understand where input and output time is being spent.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Synchronous read time (ms)” onpage 304
275Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool async write time (ms)
DescriptionReturns the time (in milliseconds) that database manager page cleaners spent writing data orindex pages from the buffer pool to disk for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolAsyncWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolAsyncWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the tbsp: Synchronous write time(ms) monitor to understand where input and output time is being spent.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Synchronous write time (ms)” onpage 305
276 Version 2.1.0
tbsp: Buffer pool data logical reads
DescriptionReturns the number of logical read requests for data pages that went through the buffer poolfor the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolDataLReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolDataLReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the returned value for the tbsp: Percent buffer poolhit ratio, data+index monitor.
The returned value includes requests for data that is already in the buffer pool or read fromdisk into the buffer pool to fulfill the request. The count for these is given by the tbsp:Buffer pool data physical reads monitor.
277Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Percent buffer pool hit ratio,data+index” on page 297, “tbsp: Buffer pool data physical reads” on page 281
278 Version 2.1.0
tbsp: Buffer pool data pages copied from extended storage
DescriptionReturns the number of buffer pool data pages copied from extended storage within thetablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDataPagesCopiedfromExtendedStorage
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDataPagesCopiedfromExtendedStorage'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesRequired pages are copied from extended storage to the buffer pool if they are not in thebuffer pool but are in extended storage. This copying can incur the cost of connecting to theshared memory segment but saves the cost of a disk read.
See AlsoNone
279Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool data pages copied to extended storage
DescriptionReturns the number of buffer pool data pages copied to extended storage for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDataPagesCopiedtoExtendedStorage
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDataPagesCopiedtoExtendedStorage'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesPages are copied from the buffer pool to extended storage when they are selected as victimpages. This copying is required to make space for new pages in the buffer pool.
See AlsoNone
280 Version 2.1.0
tbsp: Buffer pool data physical reads
DescriptionReturns the number of read requests requiring input and output to get data pages into thebuffer pool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolDataPReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolDataPReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the return values for thetbsp: Percent buffer poolhit ratio, data+index and tbsp: # of synchronous reads monitors.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Percent buffer pool hit ratio,data+index” on page 297, “tbsp: # of synchronous reads” on page 253
281Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool data physical writes
DescriptionReturns the number of times that a buffer pool data page was physically written to disk forthe tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolDataWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolDataWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to the value returned by thetbsp: Buffer pool dataphysical reads monitor, you can improve performance by increasing the available bufferpool space. You can increase available buffer pool space by completing the following:
¶ Free space more often by writing out changed pages. You can have space freed moreoften by increasing the chngpgs_thresh or num_iocleaners configuration parameter.
¶ Increase the total space for the buffer pool.
282 Version 2.1.0
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool data physical reads” onpage 281
DB2Manager Configuration monitors: “db: num_iocleaners” on page 330, “db:chngpgs_thresh” on page 320, “db: buffpage” on page 318
283Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool index logical reads
DescriptionReturns the number of logical read requests for index pages that went through the bufferpool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolIndexLReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolIndexLReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned values for the tbsp: Percent bufferpool hit ratio, data+index and tbsp: Percent buffer pool hit ratio, index monitors.
The returned value includes requests for index pages that are already in the buffer pool orread from disk into the buffer pool to fulfill the request. (The count for these is given by thetbsp: Buffer pool index physical reads monitor.)
284 Version 2.1.0
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Percent buffer pool hit ratio,data+index” on page 297, “tbsp: Percent buffer pool hit ratio, index” on page 299,“tbsp: Buffer pool index physical reads” on page 289
285Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool I/Os per second
DescriptionReturns the rate (per second) for buffer pool input and output for the tablespace. For thismonitor, buffer pool input and output includes all physical data and index pages that gothrough the buffer pool when read or written.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolIoRate
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolIoRate'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how efficient your data storage device is. A low valuewhen compared to normal operating levels can indicate the presence of an input and outputwait, which can indicate that you should move data to a different device.
See AlsoNone
286 Version 2.1.0
tbsp: Buffer pool index pages copied from extended storagecopied from extended storage
DescriptionReturns the number of buffer pool index pages copied from extended storage for thetablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspIndexPagesCopiedfromExtendedStorage
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspIndexPagesCopiedfromExtendedStorage'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesRequired index pages are copied from extended storage to the buffer pool if they are not inthe buffer pool but are in extended storage. This copying can incur the cost of connecting tothe shared memory segment but saves the cost of a disk read.
See AlsoNone
287Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool index pages copied to extended storage
DescriptionReturns the number of buffer pool index pages copied to extended storage within thetablespace. The input argument is the monitored DB2 tablespace name.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspIndexPagesCopiedtoExtendedStorage
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspIndexPagesCopiedtoExtendedStorage'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesPages are copied from the buffer pool to extended storage when they are selected as victimpages. This copying is required to make space for new pages in the buffer pool.
See AlsoNone
288 Version 2.1.0
tbsp: Buffer pool index physical reads
DescriptionReturns the number of physical read requests to get index pages into the buffer pool for thetablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolIndexPReads
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolIndexPReads'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the return values for other buffer pool monitors, forexample, the tbsp: Percent buffer pool hit ratio, data+index monitor.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Percent buffer pool hit ratio,data+index” on page 297
289Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Buffer pool index physical writes
DescriptionReturns the number of times that a buffer pool index page was physically written to disk forthe tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolIndexWrites
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolIndexWrites'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to the value returned by the tbsp: Buffer pool indexphysical reads monitor, you can improve performance by increasing the available bufferpool space. You can increase available buffer pool space by completing the following:
Free space more often by writing out changed pages. You can have space freed moreoften by increasing the chngpgs_thresh or num_iocleaners configuration parameters.
Increase the total space for the buffer pool.
290 Version 2.1.0
See AlsoDB2Manager Buffer Pool I/O monitors:“tbsp: Buffer pool index physical reads” on page 289DB2Manager Configuration monitors: “db: num_iocleaners” on page 330,“db: chngpgs_thresh” on page 320,“db: buffpage” on page 318
291Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Direct read time
DescriptionReturns the time (in milliseconds) for performing the direct reads for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDirectReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDirectReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the tbsp: Average direct read time (ms)monitor. A high average time can indicate an input and output conflict.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average direct read time (ms)” onpage 259
292 Version 2.1.0
tbsp: Direct write time (ms)
DescriptionReturns the time (in milliseconds) for performing the direct writes for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspDirectWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspDirectWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the tbsp: Average direct write time (ms)monitor. A high average time can indicate an input and output conflict.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Average direct write time (ms)” onpage 260
293Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Extended storage read/write ratio
DescriptionReturns the ratio (as a percent) of pages (data+index) copied from extended storage to pagescopied to extended storage within the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspExtendedStorageReadWriteRatio
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspExtendedStorageReadWriteRatio'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWhen a page is transferred from extended storage to the buffer pool, you save a systeminput and output call. However, you still incur the cost of attaching to the extended memorysegment, copying the page, and detaching from the segment.
Use the returned value to determine if you would benefit from using extended storage. Thehigher the ratio, the more likely you are to benefit. In general, extended storage isparticularly useful if input and output activity is very high on your system.
294 Version 2.1.0
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool data pages copied fromextended storage” on page 279, “tbsp: Buffer pool data pages copied to extendedstorage” on page 280, “tbsp: Buffer pool index pages copied from extended storage” onpage 287, “tbsp: Buffer pool index pages copied to extended storage” on page 288
295Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: File closed
DescriptionReturns the total number of closed files for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspFilesClosed
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspFilesClosed'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the best value for the maxfilop configuration parameter.
The database manager opens files for reading and writing into and out of the buffer pool.The maximum number of database files that are open by an application at any time iscontrolled by the maxfilop parameter. If the maximum is reached, one file must close beforea new file opens, which can slow performance.
See AlsoNone
296 Version 2.1.0
tbsp: Percent buffer pool hit ratio, data+index
DescriptionReturns the overall buffer pool hit ratio (as a percent) for the tablespace during themonitoring interval. This hit ratio includes both index and data page activity.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPoolHitRatio
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPoolHitRatio'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe overall buffer pool hit ratio indicates the percentage of requests for which the databasemanager did not need to load a page from disk to service. That is, the page was already inthe buffer pool. The greater the buffer pool hit ratio, the lower the frequency of disk inputand output.
If the hit ratio is low (for example, a ratio of zero indicates that pages needed to be read infor every request), increasing the number of buffer pool pages can improve performance.
297Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Buffer Pool I/O monitors:“tbsp: Percent buffer pool hit ratio, index” on page 299DB2Manager Configuration monitors: “db: buffpage” on page 318
298 Version 2.1.0
tbsp: Percent buffer pool hit ratio, index
DescriptionReturns the tablespace’s index page hit ratio (as a percent) for the buffer pool during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspIndxPlHitRatio
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspIndxPlHitRatio'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe index page hit ratio for the buffer pool indicates the percent of index page requests thatthe database manager did not need to load an index page from disk to service. That is, theindex page was already in the buffer pool. The greater the returned value, the lower thefrequency of disk input and output, and the faster the performance.
If the hit ratio is low compared to normal operating levels, increasing the number of bufferpool pages can improve performance.
299Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
See AlsoDB2Manager Configuration monitors: “db: buffpage” on page 318
300 Version 2.1.0
tbsp: Percent prefetch satisfied
DescriptionReturns the percentage of asynchronous read requests that were satisfied for a tablespaceduring the last monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPctAsyDatRdRqS
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPctAsyDatRdRqS'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the amount of asynchronous input and output performedin each interaction with the prefetcher.
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332
301Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Percent total I/O
DescriptionReturns the input and output operations that occurred during the monitoring interval for thetablespace as a percentage of the total input and output operations for the database thatcontains the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPctTotalIo
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPctTotalIo'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine which tablespaces in a particular database account forthe most input and output operations. This information can help you determine which ofyour devices to use for each tablespace.
See AlsoNone
302 Version 2.1.0
tbsp: Prefetch requests in an interval
DescriptionReturns the number of asynchronous read requests for the tablespace during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspPlAsyncDatRdRq
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspPlAsyncDatRdRq'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculations for the tbsp: Percent prefetch satisfied monitor.This value can help you determine the amount of asynchronous input and output done ineach interaction with the prefetcher.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Percent prefetch satisfied” on page 301DB2Manager Configuration monitors: “db: num_ioservers” on page 332
303Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Synchronous read time (ms)
DescriptionReturns the time (in milliseconds) applied to synchronous reads for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspSyncReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspSyncReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the tbsp: Buffer pool async read time(ms) monitor to understand where input and output time for this tablespace is used.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool async read time (ms)” onpage 275
304 Version 2.1.0
tbsp: Synchronous write time (ms)
DescriptionReturns the time (in milliseconds) applied to synchronous writes to disk for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspSyncWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspSyncWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesCompare the returned value to the value returned by the tbsp: Buffer pool async write time(ms) monitor to understand where input and output time for this tablespace is used.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Buffer pool async write time (ms)” onpage 276
305Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Total direct I/O time (ms)
DescriptionReturns the total time (in milliseconds) for direct reads to and writes from the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalDirectIoTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalDirectIoTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value indicates the amount of time applied to direct reads and writes to andfrom this tablespace. A high time can indicate the presence of an input and output conflict.
See AlsoNone
306 Version 2.1.0
tbsp: Total pool physical I/O time (ms)
DescriptionReturns the total time (in milliseconds) for physical buffer pool input and output operations(including both synchronous and asynchronous reads and writes) for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalPoolIoTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalPoolIoTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA high returned value (as compared to the total number of physical buffer pool input andoutput operations) can indicate the presence of an input and output wait, which couldindicate that you should move data to a different device.
See AlsoNone
307Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Total pool physical read time (ms)
DescriptionReturns the total time (in milliseconds) for processing read requests that caused data orindex pages to be physically read from disk to the buffer pool for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalReadTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalReadTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the average pool read time, which is returned by thetbsp: Average pool read time (ms) monitor. This average can indicate the presence of aninput and output wait, which in turn can indicate that you should move data to a differentdevice.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average pool read time (ms)” on page 180
308 Version 2.1.0
tbsp: Total pool physical write time (ms)
DescriptionReturns the total time (in milliseconds) for buffer pool physical writes (includingasynchronous writes) for the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalWriteTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalWriteTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used to calculate the average pool write time, which is returned by thetbsp: Average pool write time (ms) monitor. This average can indicate the presence of aninput and output wait, which in turn can indicate that you should move data for thistablespace to a different device.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Average pool write time (ms)” on page 181
309Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Total synchronous I/O
DescriptionReturns the total number of synchronous reads and writes for both data and index pages forthe tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalSyncIos
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalSyncIos'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into how well the prefetchers and page cleaners areworking and to refine the num_ioservers and num_iocleaners configuration parameters.
Because synchronous input and output operations are performed by database agents, a highnumber of operations can slow performance.
310 Version 2.1.0
See AlsoDB2Manager Configuration monitors: “db: num_ioservers” on page 332, “db:num_iocleaners” on page 330
311Tivoli Manager for DB2 Reference Guide
5.D
B2
Bu
fferP
oo
lI/O
Mo
nito
rs
tbsp: Total synchronous I/O time (ms)
DescriptionReturns the total time (in milliseconds) for processing requests for synchronous reads orwrites within the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalSyncIoTime
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Bufio_Monitors' 'tbspTotalSyncIoTime'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is the sum of the returned values from the tbsp: Synchronous read time(ms) and tbsp: Synchronous write time (ms) monitors. This time is the amount of timethat database agents spend doing synchronous reads and writes for the tablespace.
See AlsoDB2Manager Buffer Pool I/O monitors: “tbsp: Synchronous read time (ms)” onpage 304, “tbsp: Synchronous write time (ms)” on page 305
312 Version 2.1.0
DB2 Configuration Monitors
The monitors in the DB2Manager_Config_Monitors collection provide information aboutthe configuration parameters for database managers and their databases and some actualvalues of resource usage pertaining to particular configuration parameters. Typically, yourefine the values of these parameters to achieve maximum performance for the databaseenvironment. For descriptions of these configuration parameters, their default values, andhow you can refine them to improve the performance of instances and databases, see theDB2 Administration Guide: Performance for the version of DB2 that you are using.
Table 31 lists the monitors in this collection.
Table 31. DB2Manager Configuration MonitorsDesktop Name CLI Name Returned Value
Format
db: app_ctl_heap_sz dbAppCtlHeapSz Numeric: 4-KB pages
db: ApplHeapSz dbApplHeapSz Numeric: 4-KB pages
db: avg_appls dbAvgAppls Numeric
db: buffpage dbBuffpage Numeric
db: catalogcache_sz dbCatalogcacheSz Numeric: 4-KB pages
db: chngpgs_thresh dbChngpgsThresh Numeric
db: dbheap dbDbheap Numeric: 4-KB pages
db: locklist dbLocklist Numeric: 4-KB pages
db: logbufsz dbLogbufsz Numeric: 4-KB pages
db: logprimary dbLogprimary Numeric
db: maxappls dbMaxappls Numeric
db: maxlocks dbMaxlocks Numeric: percentage
db: mincommit dbMincommit Numeric
db: newlogpath dbNewlogpath Numeric
db: num_iocleaners dbNumIocleaners Numeric
db: num_ioservers dbNumIoservers Numeric
db: pckcachesz dbPckcachesz Numeric: 4-KB pages
db: Percent space used in databaseheap dbPctHeapSpaceUsed Numeric: percentage
db: restore_pending dbRestorePending String: “NO” or “YES”
db: seqdetect dbSeqdetect Numeric
db: sortheap dbSortheap Numeric: 4-KB pages
dbms: agentpri dbmsAgentpri Numeric
dbms: aslheapsz dbmsAslheapsz Numeric: 4-KB pages
6
313Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
Table 31. DB2Manager Configuration Monitors (continued)Desktop Name CLI Name Returned Value
Format
dbms: fcm_num_anchors dbmsFcmNumAnchors Numeric
dbms: fcm_num_buffers dbmsFcmNumBuffers NumerNumeric: 4-KBbuffers
dbms: fcm_num_connect dbmsFcmNumConnect Numeric
dbms: fcm_num_rqb dbmsFcmNumRqb Numeric
dbms: max_agents dbmsMaxAgents Numeric
dbms: max_coordagents dbmsMaxcoordagents Numeric
dbms: maxcagents dbmsMaxcagents Numeric
dbms: Maximum idle agents in the agentpool
dbmsMaxIdlePoolAgents Numeric
dbms: Minimum committed private memory dbmsMinCommPrivMem Numeric: 4-KB pages
dbms: mon_heap_sz dbmsMonHeapSz Numeric: 4-KB pages
dbms: num_poolagents dbmsNumPoolagents Numeric
dbms: Percent private memory used dbmsPctPrivMemUsed Numeric: percentage
dbms: query_heap_sz dbmsQueryHeapSz Numeric: 4-KB pages
dbms: rqrioblk dbmsRqrioblk Numeric
dbms: sheapthres dbmsSheapthres Numeric: 4-KB pages
dbms: sqlstmtsz dbmsSqlstmtsz Numeric
314 Version 2.1.0
db: app_ctl_heap_sz
DescriptionReturns the maximum size (in 4-KB pages) for the application control heap in the databaseduring the monitoring interval.
DB2 Version SupportedDB2 Enterprise Editions only
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbApplCtlHeapSz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbApplCtlHeapSz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe heap is required to share information among agents working on behalf of the sameapplication at a node in a massively parallel processing (MPP) or a symmetricmultiprocessor (SMP) system. If complex applications are being run or the MPPconfiguration has a large number of nodes, you should increase the size of this heap.
In a partitioned database environment, this heap is used to store copies of the executingsection of SQL statements for agents and subagents. However, symmetric multiprocessoragents (SMP), subagents, and agents in all other environments use ApplHeapSz.
See AlsoDB2Manager Configuration monitors: “db: ApplHeapSz” on page 316, “db:app_ctl_heap_sz”, “db: avg_appls” on page 317
315Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: ApplHeapSz
DescriptionReturns the size (in 4-KB pages) of the application heap that is available for each individualagent in the database during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbApplHeapSz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbApplHeapSz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIncrease the value of the parameter if your application receives an error indicating that thereis not enough storage in the application heap.
The heap is allocated when an agent or subagent is initialized for an application. Theamount allocated is the minimum amount needed to process the request given to the agent orsubagent. When the agent or subagent requires more heap space to process larger SQLstatements, the database manager will allocate memory as needed, up to the maximumspecified by the parameter.
Use the results from the db: app_ctl_heap_sz monitor to help you refine the applheapszparameter.
See AlsoDB2Manager Configuration monitors: “db: app_ctl_heap_sz” on page 315, “db:ApplHeapSz”
316 Version 2.1.0
db: avg_appls
DescriptionReturns the value of the average number of active applications.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgAppls
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbAvgAppls'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is used by the SQL optimizer to estimate how much of the buffer pool isavailable at runtime for the SQL query access plan chosen. Increasing this parameter caninfluence the optimizer to choose an access plan that is more conservative in its buffer poolusage.
See AlsoDB2Manager Configuration monitors: “db: maxappls” on page 325
317Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: buffpage
DescriptionReturns the value (in pages) of the default buffer pool size.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbBuffpage
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbBuffpage'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIn the currently supported releases of DB2, multiple buffer pools may be defined in a singledatabase. For instance, buffer pools can be defined and associated with a particulartablespace. Each buffer pool created can be given it’s own individual size.
The buffpage parameter serves only as a default value for buffer pools created within aparticular database. Therefore, the value of the buffpage parameter is much less critical toperformance in current releases of DB2, becaue most buffer pools are given an individualsize when created.
The buffpage parameter is still included here to provide continuity, but should not be used toevaluate or tune the performance of DB2 unless it is used as the default value when creatingbuffer pools in a database. Specifically, the buffpage parameter controls the size of a bufferpool when the CREATE BUFFERPOOL or ALTER BUFFERPOOL statement was run withNPAGES -1; otherwise, the buffpage parameter is ignored and the buffer pool will becreated with the number of pages specified by the NPAGES parameter.
To determine whether the buffpage parameter is active for a buffer pool, issue the followingcommand: SELECT * from SYSCAT.BUFFERPOOLS
Each buffer pool that has an NPAGES value of -1 uses buffpage.
See AlsoNone
318 Version 2.1.0
db: catalogcache_sz
DescriptionReturns the value (in units of 4-KB pages) of the catalog cache size.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCatalogcacheSz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbCatalogcacheSz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum amount of space that the catalog cache can use from thedatabase heap (dbheap). The catalog cache is referenced whenever a table, view, or aliasname is processed during the compilation of an SQL statement. It is dynamically allocatedfrom dbheap, as required, until the catalogcache_sz is reached.
See AlsoDB2Manager Basic monitors: “db: # of catalog cache heap full” on page 49,“db: # of catalog cache inserts” on page 50, “db: # of catalog cache lookups” on page 51,
“db: # of catalog cache overflows” on page 52DB2Manager Buffer Pool I/O monitors: “db: Percent catalog cache hit ratio” on page 210DB2Manager SQL Statement monitors: “db: Percent DDL SQL” on page 529DB2Manager Configuration monitors: “db: dbheap” on page 321
319Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: chngpgs_thresh
DescriptionReturns the value (in percentage units) of the changed pages threshold.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbChngpgsThresh
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbChngpgsThresh'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value sets a limit on how much buffer pool space can be occupied by changed pagesbefore the asynchronous page cleaners are started, if they are not currently active.
Asynchronous page cleaners write changed pages from the buffer pool to disk before thespace in the buffer pool is required by a database agent. This means that the agents do notneed to wait for a changed page to be written out before being able to read a page, andapplication transactions run faster.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: # of cleaners due to dirty threshold” onpage 154
320 Version 2.1.0
db: dbheap
DescriptionReturns the value (in units of 4-KB pages) of the database heap.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDbheap
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbDbheap'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum amount of memory allowed for a database heap. There is onedatabase heap for each database. It is used on behalf of all applications connected to thedatabase.
Refining dbheap has minimal impact on performance. The main function of this parameteris to prevent the database manager from allocating an excessive amount of space for aparticular database.
See AlsoDB2Manager Basic monitors: “db: # of catalog cache heap full” on page 49,“db: Max database heap allocated” on page 78DB2Manager Configuration monitors: “db: Percent space used in databaseheap” on page 334
321Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: locklist
DescriptionReturns the value (in units of 4-KB pages) of the maximum storage for lock lists.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLocklist
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbLocklist'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the amount of storage that is allocated to the lock list. There is one lock listfor each database, and it contains the locks held by all applications concurrently connectedto the database. Too small a value can lead to excessive lock waits. Too high a valuecompared to normal operaing levels can deprive the system of resources or memory.
See AlsoDB2Manager Locks and Deadlocks monitors: “conn: Lock escalations during lastinterval” on page 379, “conn: Lock wait time (s)” on page 381, “conn: Lock waits” onpage 383, “conn: Locks held” on page 385, “db: Lock list in use (bytes)” on page 394,“db: Lock waits” on page 396, “db: Locks held” on page 398, “db: Time waited onlocks” on page 401, “db: Total exclusive lock escalations” on page 402
DB2Manager Basic monitors: “conn: Percent locklist space used by application” onpage 44, “db: Avg lock escalations per connection” on page 73, “db: Percent locklistspace used by database” on page 84
322 Version 2.1.0
db: logbufsz
DescriptionReturns the value (in units of 4-KB pages) of the log buffer size.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLogbufsz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbLogbufsz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value specifies the amount of the database heap (dbheap) to use as a buffer for logrecords before writing these records to disk. It is important that the log buffer be able tohold the amount of log space used by an average transaction. Otherwise, loggingperformance will decrease and slow the overall system.
See AlsoDB2Manager Configuration monitors: “db: dbheap” on page 321
DB2Manager Basic monitors:“db: Max primary log space used” on page 79, “db: # ofsecondary logs allocated currently” on page 72, “db: Max secondary log space used” onpage 80, “db: Primary log space allocated” on page 90, “db: Percent used in primarylog” on page 87, “db: Percent used in secondary log” on page 88
323Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: logprimary
DescriptionReturns the value of the number of primary log files.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLogprimary
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbLogprimary'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the number of primary log files to be preallocated by the database manager. Ifyou find that secondary log files are frequently being allocated, you can improveperformance by increasing the value of logprimary.
See AlsoDB2Manager Basic monitors: “db: Max primary log space used” on page 79, “db: # ofsecondary logs allocated currently” on page 72, “db: Max secondary log space used” onpage 80, “db: Primary log space allocated” on page 90, “db: Percent used in primarylog” on page 87, “db: Percent used in secondary log” on page 88
324 Version 2.1.0
db: maxappls
DescriptionReturns the value of the maximum number of active applications.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbMaxappls
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbMaxappls'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum number of concurrent applications that can be connected (bothlocal and remote) to a database. Because each application that attaches to a database causessome private memory to be allocated, allowing a large number of concurrent applicationswill potentially use more memory.
Increasing the value of this parameter without lowering the maxlocks parameter orincreasing the locklist parameter can cause you to reach the database limit on locks(locklist) rather than the application limit. The result can be pervasive lock escalationproblems.
See AlsoDB2Manager Configuration monitors: “db: avg_appls” on page 317, “db: buffpage” onpage 318, “db: locklist” on page 322, “db: maxlocks” on page 326
DB2Manager Agents and Applications monitors: “dbms: Maximum agents registered”on page 31
DB2Manager Basic monitors: “db: Percent connections used” on page 82
325Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: maxlocks
DescriptionReturns the value of the maximum percentage of lock list before escalation.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbMaxlocks
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbMaxlocks'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value specifies the percentage of the lock list that an application that can hold beforethe database manager performs lock escalation. Lock escalation can increase contention,which reduces system throughput and increases user response time.
The values for maxlocks and maxappls must satisfy (maxlocks × maxappls) >100, andeach lock uses 32 bytes. It is recommended that you rebind application packages afterchanging this parameter.
See AlsoDB2Manager Locks and Deadlocks monitors: “conn: Lock escalations during lastinterval” on page 379 , “db: Lock escalations during last interval” on page 393, “db:Total exclusive lock escalations” on page 402
DB2Manager Configuration monitors: “db: locklist” on page 322, “db: maxappls” onpage 325
326 Version 2.1.0
db: mincommit
DescriptionReturns the value of the number of commits to group.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbMincommit
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbMincommit'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWith this parameter you can delay the writing of log records to disk until a minimumnumber of commits have been performed. This delay can help reduce the overheadassociated with writing log records and can improve performance.
The default value for mincommit is 1, which can be too low for your environment. Bysampling the number of transactions per-second throughout the day, you can determine thepeak per second rate and adjust mincommit to accommodate all or most transactions. Thisadjustment would minimize the number of log writes under the heaviest conditions.
You can determine the peak number of transactions per second by adding the values returnedfrom these two monitors:
¶ db: Committed statements per second
¶ db: Rollbacks per second
As you increase mincommit, you might also need to increase the log buffer size (logbufsz)to avoid filling the log buffer. Filling the log buffer also forces the writing of log records todisk.
If you change mincommit, you must change the value for the logbufsz configurationparameter.
See AlsoDB2Manager Basic monitors:“db: # of commit statements attempted” on page 53,“db: # of internal commits” on page 57DB2Manager SQL Statement Activity monitors:“db: Committed statements per second” on page 525,
327Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
“db: Percent DDL SQL” on page 529DB2Manager Configuration monitors: “db: logbufsz” on page 323
328 Version 2.1.0
db: newlogpath
DescriptionReturns the current value of the newlogpath configuration parameter.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbNewlogpath
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbNewlogpath'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesYou use the newlogpath configuration parameter to specify a new location for the log files.The specified path does not become the current log path until both of the followingconditions are met:
¶ The database is in a consistent state.
¶ All users are disconnected from the database.
When the first new connection is made to the database, the database manager moves thelogs to this location.
See AlsoNone
329Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: num_iocleaners
DescriptionReturns the current value of the number of asynchronous page cleaners.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbNumIocleaners
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbNumIocleaners'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis parameter specifies the number of asynchronous page cleaners for a database. Pagecleaners monitor the buffer pool and asynchronously write out changed pages to disk to freespace in the buffer pool. Page cleaners are invoked when the following situations occur:
¶ More space in the buffer pool is needed for a new page.
¶ The percentage of space occupied by changed pages in the buffer pool exceeds the valuespecified for the chngpgs_thresh configuration parameter.
¶ The size of the log that would need to be read during database recovery exceeds thevalue given by the following formula: logprimary × logfilsiz × softmax, wherelogprimary, logfilsiz, and softmax are database configuration parameters for logging.
Page cleaners perform input and output operations that would otherwise need to beperformed by the database agents. As a result, applications can run faster.
Use the following guidelines to help you refine this configuration parameter:
¶ The num_iocleaners parameter can be reduced if both of the following conditions aretrue:
The returned value from the db: Buffer pool data writes monitor is approximatelyequal to the returned value from the db: Buffer pool async data writes monitor.
The returned value from the db: Buffer pool index writes monitor is approximatelyequal to the returned value from the db: Buffer pool async index writes monitor.
¶ The num_iocleaners parameter should be increased if either of the following conditionsis true:
The returned value from the db: Buffer pool data writes monitor is much greater thanthe returned value from the db: Buffer pool async data writes monitor.
330 Version 2.1.0
The returned value from the db: Buffer pool index writes monitor is much greater thanthe returned value from the db: Buffer pool async index writes monitor.
See AlsoDB2Manager Buffer Pool I/O monitors: “db: Buffer pool data writes” on page 196, “db:Buffer pool async data writes” on page 187, “db: Buffer pool index writes” on page 201,“db: Buffer pool async index writes” on page 189, “db: # of synchronous I/O” onpage 166, “db: # of synchronous writes” on page 170, “db: # of victim page cleanersinvoked” on page 171, “db: Avg # of pages for each cleaner” on page 185
331Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: num_ioservers
DescriptionReturns the current value of the number of input and output servers.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbNumIoservers
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbNumIoservers'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value specifies the number of input and output servers for a database. Input and outputservers are used on behalf of the database agents to perform asynchronous input and outputoperations for utilities such as backup and restore, and to perform prefetch input and output(in which case, they are called prefetchers) operations.
Prefetchers read pages from disk into the buffer pool in anticipation of their use. In mostsituations, these pages are read just before they are needed. However, prefetchers can causeunnecessary input and output operations by reading pages into the buffer pool that might notbe used.
For example, an application starts reading through a table, and prefetchers read consecutivepages into the buffer pool before the pages are required by the application. Then theapplication fills the application buffer and stops reading. Meanwhile, the prefetchers alreadyhave performed the input and output operations for additional pages and the buffer pool ispartially taken up with those pages.
To fully exploit all the input and output devices in the system, a good value fornum_ioservers to use is generally one or two more than the number of physical devices onwhich the database resides.
See AlsoDB2Manager Buffer pool I/O monitors: “db: # of synchronous I/O” on page 166, “db: #of synchronous reads” on page 169, “db: Buffer pool async data reads” on page 186
332 Version 2.1.0
db: pckcachesz
DescriptionReturns the current value (in units of 4-KB pages) of the package cache size.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPckcachesz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbPckcachesz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value controls the amount of application heap memory to be used for caching apackage’s static and dynamic SQL statements.
You will need to experiment with the size of the package cache to find the optimal numberof the pckcachesz parameter. For example, you can use a smaller package cache size ifthere is no increase in the number of package cache inserts when you decrease the size ofthe cache. Decreasing the package cache size frees up system resources for other work.However, increasing the package cache size can improve overall system performance if itresults in a decrease of package cache inserts.
See AlsoDB2Manager Buffer Pool I/O monitors: “conn: Percent package cache hit ratio” on page 146DB2Manager Basic monitors: “db: Percent package cache hit ratio” on page 85DB2Manager Configuration monitors: “db: ApplHeapSz” on page 316
333Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: Percent space used in databaseheap
DescriptionReturns the percentage of maximum space used in the database heap.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctHeapSpaceUsed
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbPctHeapSpaceUsed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 32 shows the suggested threshold values for severity levels.
Table 32. dbPctHeapSpaceUsed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 85% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to evaluate your setting of the dbheap configuration parameter. Areturned value of 100% indicates that an application has probably received an errorindicating that there was not enough storage available. The dbheap parameter limits theamount of storage that can be allocated for database heap.
See AlsoDB2Manager Configuration monitors: “db: dbheap” on page 321
334 Version 2.1.0
db: restore_pending
DescriptionReturns the RESTORE PENDING status in the database during the last monitoring interval.
DB2 Version SupportedDB2 Enterprise Editions only
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRestorePending
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbRestorePending'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesNone
See AlsoNone
335Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
db: seqdetect
DescriptionReturns the current value of the sequential detection flag.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSeqdetect
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbSeqdetect'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe seqdetect parameter determines if the database manager should perform sequentialdetection.
The database manager can monitor input and output operations. If sequential page reading isoccurring, the database manager can activate input and output prefetching. This type ofsequential prefetch is known as sequential detection.
If this configuration parameter is set to “no,” prefetching takes place only if the databasemanager determines that it is useful (for example, in table sorts).
See AlsoNone
336 Version 2.1.0
db: sortheap
DescriptionReturns the current value (in units of 4-KB pages) of the sort heap size.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSortheap
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbSortheap'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum amount of memory that can be allocated as sort heap for eachsort within a database. The sort heap is the memory block where data is sorted.
See AlsoDB2Manager Sort Work monitors: “db: Active sorts” on page 465, “db: Percent sortoverflowed” on page 467, “db: Sort heap allocated” on page 468, “db: Sort overflows”on page 469, “db: Total sort time (ms)” on page 470, “db: Total sorts” on page 471,
“dbms: Percent piped sorts rejected” on page 472, “dbms: Percent sort heap allocated”on page 474, “dbms: Sort heap allocated” on page 476
337Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: agentpri
DescriptionReturns the current value of the priority of agents.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsAgentpri
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsAgentpri'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the priority that the operating system scheduler gives to agent and otherdatabase manager instance processes and threads. This priority determines how the operatingsystem gives CPU time to the DB2 processes and threads relative to the other processes andthreads running on the machine.
A value of −1 indicates that no special action is taken and the operating system schedulesthe database manager in the normal way that it schedules all processes and threads. Anyother value indicates that the database manager creates its processes and threads with a staticpriority set to this value.
See AlsoNone
338 Version 2.1.0
dbms: aslheapsz
DescriptionReturns the current value (in units of 4-KB pages) of the application support layer heap size.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsAslheapsz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsAslheapsz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the amount of memory that is allocated for the application support layer heap.This heap is used as a communication buffer between the local application and its associatedagent. In addition, this value is used to determine the input and output block size when ablocking cursor is opened.
See AlsoNone
339Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: fcm_num_anchors
DescriptionReturns the number of FCM message anchors for the DB2 instance during the monitoringinterval.
DB2 Version SupportedDB2 Enterprise-Extended Editions only
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsFcmNumAnchors
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsFcmNumAnchors'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesAgents use the message anchors to send messages among themselves.
Use the results from the following monitors and parameters to help you refine thefcm_num_anchors parameter:
¶ fcm_num_rqb
¶ intra_parallel parameter (see the DB2 Administration Guide for the version of DB2 thatyou are using)
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_rqb” on page 343
340 Version 2.1.0
dbms: fcm_num_buffers
DescriptionReturns the number of buffers that are used for internal communications (messages) amongthe nodes and within the nodes in a DB2 instance during the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Editions only
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsFcmNumBuffers
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsFcmNumBuffers'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesYou might need to increase the value of this parameter if you have either of the followingconditions:
¶ Multiple logical nodes on a processor
¶ Too many users, nodes, or complex applications that exceed the buffer limit
See AlsoNone
341Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: fcm_num_connect
DescriptionReturns the number of FCM connection entries for the DB2 instance during the monitoringinterval.
DB2 Version SupportedDB2 Enterprise-Extended Editions only
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsFcmNumConnect
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsFcmNumConnect'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesAgents use connection entries to pass data among themselves.
Use the results from the fcm_num_rqb monitor to help you refine the fcm_num_connectparameter.
See AlsoDB2Manager Configuration monitors: “dbms: fcm_num_rqb” on page 343
342 Version 2.1.0
dbms: fcm_num_rqb
DescriptionReturns the number of FCM request blocks for the DB2 instance during the monitoringinterval.
DB2 Version SupportedDB2 Enterprise-Extended Editions only
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsFcmNumRqb
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsFcmNumRqb'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesRequest blocks are the media through which information is passed between the FCMdaemon and an agent.
The requirement for request blocks will vary according to the number of users on thesystem, the number of database partition servers in the system, and the complexity ofqueries that are run.
See AlsoNone
343Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: max_agents
DescriptionReturns the current value of the maximum number of agents.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsMaxAgents
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsMaxAgents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum number of database manager agents available at any given timeto accept application requests. It limits the total number of applications that can connect toall databases in the DB2 instance at a given time.
The value of max_agents should be the sum of the values for maxappls in each databasethat is allowed to be accessed concurrently. Increasing max_agents can increase resourceuse because resources for each agent are allocated when the DB2 instance is started.
See AlsoDB2Manager Basic monitors: “db: # of applications connected currently” on page 46,“dbms: # of local connections” on page 92, “dbms: # of remote connections” on page 97
DB2Manager Agents and Applications monitors:“dbms: Maximum agents registered” on page 31DB2Manager Configuration monitors: “db: maxappls” on page 325
344 Version 2.1.0
dbms: max_coordagents
DescriptionReturns the maximum number of database manager coordinating agents that can exist on aserver in a partitioned or nonpartitioned database environment.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsMaxcoordagents
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsMaxcoordagents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesOne coordinating agent is acquired for each local or remote application that connects to adatabase or attaches to an instance. Requests that require an instance attachment includeCREATE DATABASE, DROP DATABASE, and Database System Monitor commands.
Use the results from the following parameters and monitors to help refine themax_coordagents parameter:
¶ intra_parallel parameter (see the DB2 Administration Guide for the version of DB2 thatyou are using)
¶ dbms: max_agents monitor
¶ dbms: num_poolagents monitor
¶ min_priv_mem parameter (see the DB2 Administration Guide for the version of DB2that you are using)
¶ num_initagents parameter (see the DB2 Administration Guide for the version of DB2that you are using)
See AlsoDB2Manager Configuration monitors: “dbms: max_agents” on page 344, “dbms:num_poolagents” on page 350,
345Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: maxcagents
DescriptionReturns the maximum number of database manager coordinator agents that can concurrentlyexecute a database manager transaction in the DB2 instance during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsMaxcagents
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsMaxcagents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWhen this monitor is used with DB2 Universal database servers, the maxcagents value isthe default. This value is the maximum number of database manager agents that can beconcurrently executing a database manager transaction. Use the maxcagents parameter tocontrol the load on the system during periods of high simultaneous application activity.
A value of −1 indicates that the limit is equal to the maximum number of agents(max_agents).
The maxcagents parameter does not limit the number of applications that can haveconnections to the database.
When this monitor is used with DB2 for Enterprise-Extended Editions, the max_coordagentis the default. This parameter determines the maximum number of coordinating agents thatcan exist at one time on a node.
See AlsoDB2Manager Basic monitors:“dbms: # of local connections executing” on page 93,“dbms: # of remote connections executing” on page 98DB2Manager Agents and Applications monitors:“dbms: Agents waiting for a token” on page 30,“dbms: Maximum agents waiting” on page 32,“dbms: Percent agents waiting” on page 33
DB2Manager Configuration monitors:“dbms: max_agents” on page 344,“dbms: max_coordagents” on page 345
346 Version 2.1.0
dbms: Maximum idle agents in the agent pool
DescriptionReturns the maximum number of idle agents in the agent pool within the DB2 instanceduring the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsMaxIdlePoolAgents
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsMaxIdlePoolAgents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWhen this monitor is used with DB2 for common servers, it returns the max_idleagentsconfiguration parameter (see the DB2 Administration Guide for the version of DB2 that youare using) to control the maximum number of idle agents in the agent pool.
When this monitor is used with DB2 UDB and DB2 for Enterprise-Extended Editions, itreturns the max_coordagents configuration parameter to control the maximum number ofidled coordinator agents in the agent pool. The agent pool contains subagents and idleagents. The num_poolagents parameter specifies the maximum number of subagents andidle agents allowed in the agent pool.
See AlsoDB2Manager Configuration monitors: “dbms: max_coordagents” on page 345, “dbms:num_poolagents” on page 350
347Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: Minimum committed private memory
DescriptionReturns the current value (in units of 4-KB pages) of the minimum committed privatememory.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsMinCommPrivMem
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsMinCommPrivMem'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the number of pages that the database server process reserves as private virtualmemory when a DB2 instance is started. If the server later requires more private memory, ittries to obtain more from the operating system at that time.
See AlsoNone
348 Version 2.1.0
dbms: mon_heap_sz
DescriptionReturns the current value (in units of 4-KB pages) of the database system monitor heap size.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsMonHeapSz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsMonHeapSz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the amount of memory that is allocated for database system monitor data. Avalue of zero prevents the database manager from collecting database system monitor data.
See AlsoNone
349Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: num_poolagents
DescriptionReturns the maximum number of agents allowed in the agent pool within the DB2 instanceduring the monitoring interval.
DB2 Version SupportedDB2 Enterprise-Extended Editions only
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsNumPoolAgents
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsNumPoolAgents'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe agent pool contains both idle agents and MPP and SMP associated subagents. If moreagents are created, they are terminated and not returned to the pool when they finishexecuting. If the value of this parameter is calculated at run time using other configurationparameters, the label (calculated) appears to the right of the value shown in the output forGET DATABASE MANAGER CONFIGURATION. If −1 (calculated) is shown in theoutput, the request was issued from a client, and the value was not available.
Use the results from the following parameters and monitors to help you refine thenum_poolagents configuration parameter:
¶ num_initagents parameter (see the DB2 Administration Guide for the version of DB2that you are using)
¶ dbms: max_agents monitor
¶ max_querydegree parameter (see the DB2 Administration Guide for the version of DB2that you are using)
¶ dbms: max_coordagents monitor
See AlsoDB2Manager Configuration monitors: “dbms: max_coordagents” on page 345, “dbms:max_agents” on page 344
350 Version 2.1.0
dbms: Percent private memory used
DescriptionReturns the percentage of private memory used.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPctPrivMemUsed
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsPctPrivMemUsed'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the setting of the minimum committed private memory(min_priv_mem) configuration parameter. The min_priv_mem parameter sets the amountof storage that can be reserved for private virtual memory for a DB2 instance. A returnedvalue of approximately 100% indicates that you are using all of the private memory that wasreserved when the instance was started.
If the returned value is consistently less than 100% over a period of time, the value formin_priv_mem can be too high compared to normal operaing levels. In this case, you arereserving more memory than you are typically using.
A returned value higher than 100% indicates that there was not enough memory available,and the server probably tried to obtain more from the operating system. If the returned valueis consistently higher than 100% over a period of time, the value for min_priv_memory canbe too low. In this case, the overhead is increased because more operating system resourcesare used.
See AlsoDB2Manager Configuration monitors: “dbms: Minimum committed private memory”on page 348
351Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: query_heap_sz
DescriptionReturns the maximum amount of memory that could be allocated for the query heap withinthe DB2 instance during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsQueryHeapSz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsQueryHeapSz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse a query heap to store each query in the agent’s private memory.
Use the results from the dbms: aslheapsz monitor to refine the query_heap_sz parameter.
See AlsoDB2Manager Configuration monitors: “dbms: aslheapsz” on page 339
352 Version 2.1.0
dbms: rqrioblk
DescriptionReturns the current value (in byte units) of the client input and output block size.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsRqrioblk
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsRqrioblk'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the amount of memory that is allocated for the communication buffer betweenremote applications and their database agents on the database server. When a database clientrequests a connection to a remote database, this communication buffer is allocated on theclient. On the database server, a communication buffer of 32767 bytes is initially allocated,until a connection is established and the server can determine the value of rqrioblk at theclient.
In addition to this communication buffer, this parameter is also used to determine the inputand output block size at the database client when a blocking cursor is opened.
See AlsoNone
353Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
dbms: sheapthres
DescriptionReturns the current value (in units of 4-KB pages) of the sort heap threshold.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsSheapthres
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsSheapthres'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum amount of memory that the database manager allocates for pipedsorts. Piped sorts perform better than non-piped sorts and tend to be used more often.However, their use can impact performance.
The value for sheapthres should be at least two times the largest sortheap defined for anydatabase within the instance.
See AlsoDBManager Sort Work monitors: “db: Active sorts” on page 465, “db: Percent sortoverflowed” on page 467, “db: Sort heap allocated” on page 468, “db: Sort overflows” onpage 469, “db: Total sorts” on page 471, “dbms: Post threshold sorts” on page 475
DBManager Basic monitors: “dbms: # of piped sorts accepted” on page 95, “dbms: # ofpiped sorts requested” on page 96, “dbms: Percent piped sort hit ratio” on page 101
354 Version 2.1.0
dbms: sqlstmtsz
DescriptionReturns the current value of the SQL statement size.
Authorization Roleadmin
Target EndpointsDB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsSqlstmtsz
Exampleswaddmon 'DB2Manager_Config_Monitors' 'dbmsSqlstmtsz'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThis value is the maximum amount of dynamic SQL statement text that can be returned bythe database system monitor.
If the amount of the text returned by the database system monitor exceeds the limit set bysqlstmtsz, the excess statement text is truncated. If text truncation is a problem, increase thevalue of sqlstmtsz.
See AlsoDB2Manager SQL Statement Activity monitors: “db: Dynamic SQL statements” onpage 527, “db: Static SQL statements” on page 536
355Tivoli Manager for DB2 Reference Guide
6.D
B2
Co
nfig
uratio
nM
on
itors
356 Version 2.1.0
DB2 Data Replication Relational Monitors
The monitors in the DB2_DataReplication_Monitors collection provide information aboutdata replication activity from IBM Replication, which is an integrated component of DB2UDB Enterprise-Edition and Enterprise-Extended Edition. IBM Replication copies relationaldata from source tables to target tables, which are typically in different DB2 databases (andpotentially on geographically disparate servers).
IBM Replication uses two components: the Capture program and the Apply program. TheCapture program reads the DB2 database log or journal records to capture data aboutchanges made to source tables. The Apply program refreshes or updates a target table,depending on the applicable source-to-target rules.
For more information about data replication in DB2, see the DB2 Replication Guide andReference manual.
Table 33 lists the monitors in this collection.
Table 33. DB2Manager Data Replication Relational MonitorsDesktop Name CLI Name Returned Value
Format
DataJoiner status DataJoinerStatus String: “up” or “down”
Data replication Apply status DproprApplyStatus String: “up” or “down”
SNA link status SnaLinkStatus String: “up” or “down”
TCP/IP communication linkstatus
TcpLinkStatus String: “up” or “down”
db: # of Apply laggingsubscriptions
dbDproprAppTotSubLag Numeric
db: Apply failed subscriptions dbDproprAppFailedSub Numeric
db: Apply requires full refresh dbDproprAppNeedFullRefresh Numeric: 0 = No > 0 =Yes
db: Apply subscriptions lagtime
dbDproprAppSubLagTime Numeric: minutes
db: Apply subscription status dbDproprAppSubStatus Numeric: 0 =Completed 1 = Inprogress 3 = Failed
db: Capture errors dbDproprCapErr Numeric
db: Capture lag dbDproprCapLag Numeric: minutes
db: Capture pruning dbDpropCapPruning Numeric
7
357Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
Eight of these monitors can be used to monitor the Capture and Apply programs executingat DB2 for MVS/ESA databases. These monitors are:
¶ db: # of Apply lagging subscriptions
¶ db: Apply failed subscriptions
¶ db: Apply requires full refresh
¶ db: Apply subscriptions lag time
¶ db: Apply subscription status
¶ db: Capture errors
¶ db: Capture lag
¶ db: Capture pruning
Before you can use these eight monitors on DB2 for MVS/ESA databases, you mustestablish connectivity to the machine that the databases are on, and you must define thedatabases to the DB2 instances (on AIX or NT) that are managed by the Tivoli Manager forDB2 product. Then you can use these eight monitors with these databases as you would withany other database in the DB2 instance. For information about defining DB2 for MVS/ESAdatabases to a DB2 instance on AIX or NT, see the Tivoli Manager for DB2 User’s Guide.
358 Version 2.1.0
DataJoiner status
DescriptionChecks whether the DataJoiner instance is up or down.
Authorization Roleadmin
Target EndpointsNone
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DataJoiner Instance NameSpecifies the name of the DataJoiner instance.
CLI SynopsisDataJoinerStatus
-a <DataJoiner_instance_name>
The following briefly describes the argument for this monitor:
<DataJoiner_instance_name>Specifies the name of the DataJoiner instance.
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'DataJoinerStatus'-a 'datjinst'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the DataJoinerinstance is currently up or down.
See AlsoNone
359Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
Data replication Apply status
DescriptionChecks whether the Apply program is running.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisDproprApplyStatus
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'DproprApplyStatus'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the Apply program iscurrently up or down.
See AlsoNone
360 Version 2.1.0
SNA link status
DescriptionChecks the status of the SNA link to a target SNA link station. This monitor is supported onAIX only.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Link Station NameSpecifies the name of the target SNA link station.
CLI SynopsisSnaLinkStatus
-a <Link_station_name>
The following briefly describes the argument for this monitor:
<Link_station_name>Specifies the name of the target SNA link station.
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'SnaLinkStatus'-a linkstat1"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the SNA link to atarget SNA link station is up or down.
Because your replication environment is highly dependent on the communications betweenthe source and target databases, use this monitor to monitor this communication link.
See AlsoNone
361Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
TCP/IP communication link status
DescriptionReturns the status of the TCP/IP communications link to a target host.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager, DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Host NameSpecifies the name of the target host.
CLI SynopsisTcpLinkStatus
-a <Host_name>
The following briefly describes the argument for this monitor:
<Host_name>Specifies the name of the target host.
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'TcpLinkStatus'-a 'hostname'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is a string (“up” or “down”) that indicates whether the TCP/IP link to atarget host is up or down.
Because your replication environment is highly dependent on the communications betweenthe source and target databases, use this monitor to monitor this communication link.
See AlsoNone
362 Version 2.1.0
db: # of Apply lagging subscriptions
DescriptionReturns the number of lagging subscriptions for the Apply program.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Apply IdSpecifies the subscriber user ID that started this invocation of the Apply program.
CLI SynopsisdbDproprAppTotSubLag
-a <Apply_ID>
The following briefly describes the argument for this monitor:
<Apply_ID>Specifies the subscriber user ID that started this invocation of the Apply program.
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprAppTotSubLag'-a 'userid'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how many of your subscriptions are not processed ontime according to their subscription frequencies and priorities.
See AlsoNone
363Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
db: Apply failed subscriptions
DescriptionReturns the number of subscriptions that the Apply program failed to replicate.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Apply IdSpecifies the subscriber user ID that started this invocation of the Apply program.
CLI SynopsisdbDproprAppFailedSub
-a <Apply_ID>
The following briefly describes the argument for this monitor:
<Apply_ID>Specifies the subscriber user ID that started this invocation of the Apply program.
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprAppFailedSub'-a 'userid'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to see whether any subscriptions failed to be replicated.
See AlsoNone
364 Version 2.1.0
db: Apply requires full refresh
DescriptionReturns a number that indicates whether a target table requires a full refresh.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Apply IdSpecifies the subscriber user ID that started this invocation of the Apply program.
Owner NameSpecifies the owner of the target table.
Table NameSpecifies the name of the target table.
CLI SynopsisdbDproprAppNeedFullRefresh
-a <Apply_ID>
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Apply_ID>Specifies the subscriber user ID that started this invocation of the Apply program.
<Owner_name>Specifies the owner of the target table.
<Table_name>Specifies the name of the target table.
365Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprAppNeedFullRefresh'-a 'userid'-a 'ownid'-a 'ttable'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine whether an Apply target table needs a full refresh. Thereturned value is one of the values listed this table.
Table 34. Returned Values for Determining Full RefreshValue Refresh Needed
0 No
> 0 Yes
If you disabled full refreshes from automatically occurring in your replication environment,you might want to use this monitor to check whether any critical subscriptions need a fullrefresh.
See AlsoNone
366 Version 2.1.0
db: Apply subscriptions lag time
DescriptionReturns a number indicating whether the subscription is lagging or is due to run again.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Apply IdSpecifies the subscriber user ID that started this invocation of the Apply program.
Owner NameSpecifies the owner of the target table.
Table NameSpecifies the name of the target table.
CLI SynopsisdbDproprAppSubLagTime
-a <Apply_ID>
-a <Owner_name>
-a <Table_name>
The following briefly describes the argumenst for this monitor:
<Apply_ID>Specifies the subscriber user ID that started this invocation of the Apply program.
<Owner_name>Specifies the owner of the target table for the subscription.
<Table_name>Specifies the name of the target table for the subscription.
367Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprAppSubLagTime'-a 'userid'-a 'ownid'-a 'ttable'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesA positive number indicates that the subscription is lagging by that number of minutes. Anegative number indicates that the subscription is due to run again in that number ofminutes.
Table 35. Values to Determine whether Subscription is LaggingValue Subscription Status
+|n | Lagging by n minutes
−|n| Will run again in n minutes
where n is the value returned by the monitor.
Even if more than one subscription is eligible for refresh concurrently, the Apply programprocesses a single subscription at a time. The subscription frequency and priority specifiedfor each subscription determine the order of the subscription processing in this situation. TheApply program attempts to replicate your data based on the specified frequencies andpriorities. However, if one subscription takes 30 minutes to process, the next subscription isqueued behind the 30-minute subscription. In this case, the Apply program might not be ableto meet the specified subscription interval for the second subscription and the subscription issaid to be lagging. The lag time is the difference between the current time and the timewhen the subscription was supposed to run according to its subscription frequency.
See AlsoNone
368 Version 2.1.0
db: Apply subscription status
DescriptionReturns the status of the Apply subscription for a target table.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Apply IdSpecifies the subscriber user ID that started this invocation of the Apply program.
Owner NameSpecifies the owner of the target table.
Table NameSpecifies the name of the target table.
CLI SynopsisdbDproprAppSubStatus
-a <Apply_ID>
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Apply_ID>Specifies the subscriber user ID that started this invocation of the Apply program.
<Owner_name>Specifies the owner of the target table.
<Table_name>Specifies the name of the target table.
369Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprAppSubStatus'-a 'userid'-a 'ownid'-a 'ttable"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned values are listed in this table.
Table 36. Values to Determine Subscription StatusValue Subscription Status
0 Completed successfully
1 In progress
3 Error encountered by the Apply program during processing
When using this monitor, make sure that the monitoring interval is synchronized with thesubscription frequency and with the average frequency at which the Apply programprocesses this subscription.
See AlsoNone
370 Version 2.1.0
db: Capture errors
DescriptionReturns the number of errors encountered by the Capture program within the last fiveminutes.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDproprCapErr
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprCapErr'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine whether the Capture program encountered an error thatprevented it from running. If any errors are detected, the Capture program came down at thetime the error occurred. The Capture program might or might not still be down.
The Capture program is the most critical replication component in the replication system. Ifthe Capture program is not active, there will be no new change records to apply to the targetsystems. If your data concurrency requirements are high and you want to ensure that theCapture program runs continuously, use this monitor to determine when the Capture programencounters an error that prevents it from running.
See AlsoNone
371Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
db: Capture lag
DescriptionReturns the time difference (in minutes) between the current timestamp and the lasttimestamp recorded by the Capture program. This time difference is the Capture lag.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDproprCapLag
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDproprCapLa'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine whether the Capture program is keeping up with theDB2 database log. The Capture program uses an interface to the DB2 database log orjournal to detect and save changes to the data in the tables registered for replication.
See AlsoNone
372 Version 2.1.0
db: Capture pruning
DescriptionReturns the number of rows in the unit-of-work (UOW) table.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDpropCapPruning
Exampleswaddmon 'DB2Manager_DataReplication_Monitors' 'dbDpropCapPruning'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you determine whether you need to prune the UOW table orthe change data (CD) table.
See AlsoNone
373Tivoli Manager for DB2 Reference Guide
7.D
B2
Data
Rep
lication
Relatio
nal
Mo
nito
rs
374 Version 2.1.0
DB2 Locks and Deadlocks Monitors
The monitors in the DB2Manager_Lock_Monitors collection provide statistics about locksand deadlocks for applications and databases.
This monitoring collection can aid in diagnosing throughput problems either at theapplication or database level. The occurrence of a deadlock causes the applications involvedto halt execution and at least one application to be rolled back, which causes a tremendousreduction in database effectiveness. Infrequently, an isolated deadlock may occur duringnormal processing, which usually does not indicate a problem. However, a frequent patternof deadlocks (or isolated deadlocks that always occur when certain applications are runsimultaneously) indicates a fundamental problem with the design and interaction ofapplications accessing the same tables simultaneously.
Excessive or repeatable patterns of lock waits or lock escalations also indicate problems withthe interaction of applications accessing the same tables.
Table 37 lists the monitors in this collection.
Table 37. DB2Manager Locks and Deadlocks MonitorsDesktop Name CLI Name Returned
ValueFormat
conn: Deadlocks found duringlast interval
connDeadlocksDelta Numeric
conn: Lock escalations duringlast interval
connLockEscalsDelta Numeric
conn: Lock wait time (s) connLockWaitTimeDelta Numeric:seconds
conn: Lock waits connLockWaits Numeric
conn: Locks held connLocksHeld Numeric
conn: UOW lock wait time (s) connUowLockWaitTime Numeric:seconds
db: Applications in lock wait dbApplsInLkwt Numeric
db: Average lock wait time (s) dbAvgLockWaitTime Numeric:seconds
db: Average locks held perapplication
dbLocksHeldPerAppl Numeric
db: Deadlocks found during lastinterval
dbDeadlocksDelta Numeric
8
375Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Table 37. DB2Manager Locks and Deadlocks Monitors (continued)Desktop Name CLI Name Returned
ValueFormat
db: Lock escalations during lastinterval
dbLockEscalationsDelta Numeric
db: Lock list in use (bytes) dbLockListInUse Numeric
db: Lock timeouts during lastinterval
dbLockTimeoutsDelta Numeric
db: Lock waits dbLockWaits Numeric
db: Lock waits in an interval dbLockWaitsDelta Numeric
db: Locks held dbLocksHeld Numeric
db: Percent application in lockwait
dbPctApplsInLckWt Numeric:percentage
db: Percent deadlock rollbacks dbPctDlckRollbacks Numeric:percentage
db: Time waited on locks dbLockWaitTime Numeric
db: Total exclusive lockescalations
dbXLockEscals Numeric
376 Version 2.1.0
conn: Deadlocks found during last interval
DescriptionReturns the total number of deadlocks that occurred for the application during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnDeadlocksDelta
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'connDeadlocksDelta'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
377Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Usage NotesUse the returned value to determine if the application is experiencing contention problems.Modify the application to better enable it to execute concurrently.
See AlsoNone
378 Version 2.1.0
conn: Lock escalations during last interval
DescriptionReturns the total number of lock escalations for the application during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnLockEscalsDelta
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'connLockEscalsDelta'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
379Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Usage NotesUse the returned value to help you evaluate the settings of the 7locklist and maxlocksconfiguration parameters. Lock escalations can result in a decrease in concurrency betweenapplications connected to a database.
A lock is escalated when the total number of locks held by the application reaches themaximum amount of lock list space available to the application. Possible causes of lockescalations are:
¶ The lock list size is too small for the number of concurrent applications. The lock listsize is determined by the value of the locklist parameter.
¶ The percentage of the lock list usable by each application is too small. This percentageis determined by the value of the maxlocks parameter.
To resolve these causes, consider the following options:
¶ Increasing the value of locklist.
¶ Increasing the value of maxlocks.
¶ One or more applications is using an excessive number of locks.
¶ Identify the applications that have a large number of locks. These can cause lockescalations in other applications. These applications might need to use table locksinstead of row locks, although table locks can cause an increase in the values for theconn: Lock wait time (s) and conn: Lock waits monitors in this collection.
¶ Identify applications holding too much of the lock list, by using the returned value fromconn: Percent locklist space used by application monitor.
See AlsoDB2Manager Basic monitors:“conn: Percent locklist space used by application” on page 44DB2Manager Configuration monitors: “db: maxlocks” on page 326,“db: locklist” on page 322DB2Manager Locks and Deadlocks monitors: “conn: Lock wait time (s)” on page 381,“conn: Lock waits” on page 383
380 Version 2.1.0
conn: Lock wait time (s)
DescriptionReturns the total time (in seconds) that the application waits for a lock to be granted to itduring the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnLockWaitTimeDelta
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'connLockWaitTimeDelta'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
381Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Usage NotesUse the returned value with the value returned by the conn: Lock waits monitor to calculatethe average lock wait time for this application.
If the average lock wait time is high compared to normal operating levels, look forapplications that are holding many locks or have lock escalations, so that you can refinethose applications to improve concurrency. If lock escalations are the reason for a highaverage lock wait time, you might need to increase the values of the locklist and maxlocksconfiguration parameters.
See AlsoDB2Manager Configuration monitors: “db: maxlocks” on page 326, “db: locklist” onpage 322
DB2Manager Locks and Deadlocks monitors: “conn: Lock waits” on page 383
382 Version 2.1.0
conn: Lock waits
DescriptionReturns the total number of times that the application requested a lock but had to waitbecause another connection was already holding a lock on the data.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnLockWaits
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'connLockWaits'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
383Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Usage NotesUse the returned value with the value returned by the conn: Lock wait time (s) monitor tocalculate the average lock wait time for this application.
See AlsoDB2Manager Locks and Deadlocks monitors: “conn: Lock wait time (s)” on page 381
384 Version 2.1.0
conn: Locks held
DescriptionReturns the total number of locks currently held by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnLocksHeld
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'connLocksHeld'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
385Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Usage NotesUse the returned value to determine if the application is approaching the maximum numberof locks available as set by the maxlocks configuration parameter. The maxlocks parameterindicates the percentage of the lock list that each application can use before lock escalationsoccur. If the application holds a large number of locks, it might need to perform morecommits so that some of the locks can be released.
See AlsoDB2Manager Configuration monitors: “db: maxlocks” on page 326
386 Version 2.1.0
conn: UOW lock wait time (s)
DescriptionReturns the total amount of elapsed time (in seconds) that the unit of work (UOW) waitedfor locks.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnUowLockWaitTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'connUowLockWaitTime'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
387Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
Usage NotesUse the returned value to help you determine the severity of the resource contentionproblem.
See AlsoNone
388 Version 2.1.0
db: Applications in lock wait
DescriptionReturns the number of applications that are currently waiting for locks in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbApplsInLkwt
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbApplsInLkwt'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to the total number of applications currentlyconnected to the database, the applications can be having concurrency problems. In this case,you should identify applications that are holding locks or exclusive locks for long periods oftime.
See AlsoNone
389Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Average lock wait time (s)
DescriptionReturns the average time (in seconds) that applications wait for a lock within the databaseduring the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgLockWaitTime
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbAvgLockWaitTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to normal operating levels, you should look for theapplications that hold many locks, or have lock escalations. You can refine those applicationsto improve concurrency. If lock escalations are the reason for a high average lock wait time(see the db: Lock escalations during last interval monitor for more information), youmight need to increase the values of the locklist and maxlocks configuration parameters.
See AlsoDB2Manager Configuration monitors: “db: locklist” on page 322,“db: maxlocks” on page 326DB2Manager Locks and Deadlocks monitors:“db: Lock escalations during last interval” on page 393
390 Version 2.1.0
db: Average locks held per application
DescriptionReturns the average number of locks held by each currently connected application in thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLocksHeldPerAppl
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLocksHeldPerAppl'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to normal operating levels, it can indicate that one ormore applications is using an excessive number of locks. Refine such applications toimprove performance.
See AlsoNone
391Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Deadlocks found during last interval
DescriptionReturns the number of deadlocks detected in the database during the last monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDeadlocksDelta
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbDeadlocksDelta'"<profilename>"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine whether applications are experiencing conflict problemsin the database. These problems could be caused by the following situations:
¶ Lock escalations are occurring for the database.
¶ An application can be locking tables explicitly when system-generated row locks aresufficient.
¶ An application can be using an inappropriate isolation level when binding.
¶ Database catalog tables are locked for repeatable read.
¶ Applications are getting the same locks in different orders, resulting in deadlock.
You can resolve the problem by determining in which applications the deadlocks areoccurring. You could then try to modify the applications to better enable them to executeconcurrently.
See AlsoNone
392 Version 2.1.0
db: Lock escalations during last interval
DescriptionReturns the number of lock escalations that occurred in the database during the monitoringinterval. Exclusive lock escalations are included in this number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockEscalationsDelta
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLockEscalationsDelta'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to help you evaluate the settings of the locklist and maxlocksconfiguration parameters. Lock escalations can result in a decrease in concurrency betweenapplications connected to a database.
See AlsoDB2Manager Locks and Deadlocks monitors: “db: Lock escalations during last interval”DB2Manager Configuration monitors: “db: locklist” on page 322,“db: maxlocks” on page 326
393Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Lock list in use (bytes)
DescriptionReturns the total amount of lock list memory (in bytes) that is in use in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockListInUse
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLockListInUse'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is approximately the value of the locklist configuration parameter, youmight want to consider increasing the size of locklist. Because the value of locklist is givenin 4-KB pages, make sure that you convert it to bytes (locklist × 4096 bytes) to compare thetwo numbers.
See AlsoDB2Manager Configuration monitors: “db: locklist” on page 322
394 Version 2.1.0
db: Lock timeouts during last interval
DescriptionReturns the number of times that a request to lock an object timed out instead of beinggranted during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockTimeoutsDelta
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLockTimeoutsDelta'"ManufacturingProfile"
Default Thresholds and ActionsSchedule the monitor every 60 minutes without time restrictions.
Usage NotesUse the returned value to help you evaluate the locktimeout configuration parameter. If thereturned value is high when compared to normal operating levels, you might have anapplication that is holding locks for long durations. In this case, use some of the othermonitors in this collection to determine if you have an application problem.
If this value is low compared to normal operating levels, your locktimeout parameter mightbe set too high. In this situation, your applications might be waiting excessively to obtain alock.
See AlsoNone
395Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Lock waits
DescriptionReturns the total number of times that applications had to wait for locks within the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockWaits
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLockWaits'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used with the value returned by the db: Time waited on locksmonitor to calculate the average lock wait time for applications using the database. See thedb: Average lock wait time monitor for the implications of a high average lock wait time.
See AlsoDB2Manager Locks and Deadlocks monitors: “db: Time waited on locks” on page 401,“db: Average lock wait time (s)” on page 390
396 Version 2.1.0
db: Lock waits in an interval
DescriptionReturns the number of times that applications had to wait for locks in the database duringthe monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockWaitsDelta
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLockWaitsDelta'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value as an indication of how much time is applied to waiting for locksduring a particular monitoring interval.
See AlsoNone
397Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Locks held
DescriptionReturns the total number of locks currently held by all applications in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLocksHeld
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLocksHeld'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the returned value for the conn: Percent locklistspace used by application monitor.
See AlsoDB2Manager Basic monitors: “conn: Percent locklist space used by application” onpage 44
398 Version 2.1.0
db: Percent application in lock wait
DescriptionReturns the percentage of currently connected applications that are waiting for a lock in thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctApplsInLckWt
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbPctApplsInLckWt'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 38 shows the suggested threshold values for severity levels.
Table 38. dbPctApplsInLckWt Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 85% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIf the returned value is high compared to normal operating levels, the applications couldhave concurrency problems. You should identify applications that are holding locks orexclusive locks for long periods of time and determine whether they can release their locksmore often.
See AlsoNone
399Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Percent deadlock rollbacks
DescriptionReturns the percentage of rollbacks that were due to deadlock during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctDlckRollbacks
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbPctDlckRollbacks'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 39 shows the suggested threshold values for severity levels.
Table 39. dbPctDlckRollbacks Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesA high returned value indicates that applications are experiencing conflict problems.Rollbacks due to deadlocks lower the database throughput. To ensure that applicationsexecute concurrently, modify the applications where deadlocks are occuring.
See AlsoNone
400 Version 2.1.0
db: Time waited on locks
DescriptionReturns the total elapsed time (in seconds) that all applications waited for a lock within thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbLockWaitTime
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbLockWaitTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used with the value returned by the db: Lock waits monitor tocalculate the average lock wait time for applications using the database. See the “db:Average lock wait time (s)” on page 390 monitor for the implications of a high averagelock wait time.
See AlsoDB2Manager Locks and Deadlocks monitors: “conn: Lock wait time (s)” on page 381,“conn: Lock waits” on page 383, “db: Average lock wait time (s)” on page 390
401Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
db: Total exclusive lock escalations
DescriptionReturns the total number of times that locks were escalated from several row locks to oneexclusive table lock, or the number of times an exclusive lock on a row caused the tablelock to become an exclusive lock.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbXLockEscals
Exampleswaddmon 'DB2Manager_Lock_Monitors' 'dbXLockEscals'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to track exclusive locks in the database. Because other applicationscannot access data held by an exclusive lock, these locks can result in a decrease inconcurrency between applications connected to the database.
A lock is escalated when the total number of locks held by an application reaches themaximum amount of lock list space available to the application. Possible causes of exclusivelock escalations include the following:
¶ The lock list size is too small for the number of concurrent applications. The lock listsize is determined by the value of the locklist configuration parameter.
¶ The percentage of the lock list usable by each application is too small. This percentageis determined by the value of the maxlocks configuration parameter.
¶ One or more applications is using an excessive number of locks.
¶ An application is using exclusive locks when share locks are sufficient.
To resolve these causes, consider the following alternatives:
¶ Increase the value of the locklist parameter.
¶ Increase the value of the maxlocks parameter.
¶ Identify the applications that have a large number of locks. These can cause lockescalations in other applications. These applications might need to use table locksinstead of row locks, although table locks can cause an increase in the values for theconn: Lock wait time (s) and conn: Locks wait monitors in this collection.
402 Version 2.1.0
See AlsoDB2Manager Configuration monitors: “db: locklist” on page 322, “db: maxlocks” onpage 326
DB2Manager Locks and Deadlocks monitors: “conn: Lock wait time (s)” on page 381,“conn: Lock waits” on page 383
403Tivoli Manager for DB2 Reference Guide
8.D
B2
Lo
cksan
dD
eadlo
cksM
on
itors
404 Version 2.1.0
DB2 Query Monitors
The monitors in the DB2Manager_Query_Monitors collection provide general statisticsabout database objects.
Table 40 lists the monitors in this collection.
Table 40. DB2Manager Query MonitorsDesktop Name CLI Name Returned Value
Format
db: # of database tablespaces dbTotalDbTbsp Numeric
db: # of event monitors dbTotalEventMonitor Numeric
db: # of invalid triggers dbTotalInvTrigger Numeric
db: # of system tablespaces dbTotalSystemTbsp Numeric
db: # of tables dbTotalTable Numeric
db: # of tablespaces dbTotalTablespace Numeric
db: # of tablespaces with LONG data dbTotalTbspLONG Numeric
db: # of triggers dbTotalTrigger Numeric
db: # of user indexes dbTotalUser Numeric
db: # of views dbTotalView Numeric
db: User-defined SQL (numeric result) dbUserDefinedSqlN Numeric
db: User-defined SQL (string result) dbUserDefinedSqlS String
table: # of rows tableTotalRow Numeric
tbsp: # of tables tbspTotalTable Numeric
user: # of tables userTotalTable Numeric
9
405Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
db: # of database tablespaces
DescriptionReturns the number of Database Managed Space (DMS) tablespaces in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalDbTbsp
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalDbTbsp'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the use of DMS tablespaces and their effects onperformance. When reading table data using the buffer pool, DMS tablespaces do not use thefile system or its cache for data storage, and therefore do not have double buffering that canoccur for system managed space (SMS) tablespaces (for a discussion of this topic, see theDB2 Administration Guide for the version of DB2 that you are using). As a result, if youhave many DMS tablespaces compared to the number of SMS tablespaces, you can increasethe size of the database buffer pool and reduce the file system cache for better input andoutput performance.
See AlsoNone
406 Version 2.1.0
db: # of event monitors
DescriptionReturns the number of event monitors defined in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalEventMonitor
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalEventMonitor'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine how many event monitors are defined for the database.When you define an event monitor, its definition is stored in the database system catalogtable. You can create any number of event monitors. However, the maximum number ofevent monitors that can be active for a database at any given time is 32.
See AlsoNone
407Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
db: # of invalid triggers
DescriptionReturns the number of triggers that are marked invalid in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalInvTrigger
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalInvTrigger'"ManufacturingProfile"
Default Thresholds and ActionsTable 41 shows the suggested threshold values for severity levels.
Table 41. dbTotalInvTrigger Response LevelsResponse Level Trigger When Default Actions
critical Greater than 20 Send Tivoli Notice; Change Icon
severe Greater than 15 Send Tivoli Notice; Change Icon
warning Greater than 1 Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value to determine the number of triggers that must be revalidated.
A trigger is marked invalid if an object on which the trigger depends is dropped. Torevalidate an invalid trigger, you must retrieve its definition from the database systemcatalog and submit a new CREATE TRIGGER statement.
See AlsoNone
408 Version 2.1.0
db: # of system tablespaces
DescriptionReturns the number of SMS tablespaces in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalSystemTbsp
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalSystemTbsp'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the use of SMS tablespaces and their effects onperformance. Table data that is read from disk is normally available in the database’s bufferpool. Sometimes a data page is freed from the buffer pool before it is used. For SMStablespaces, when the database manager requests that data page from the file system, thedata page might still be in the file system’s own cache. Having the page in the file system’scache saves an input and output operation that would otherwise have been required. (Formore information, see the DB2 Administration Guide for the version of DB2 that you areusing.) If you have many SMS tablespaces, you can increase the size of the file systemcache to take advantage of this extra buffering.
See AlsoNone
409Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
db: # of tablesdb: # of tables
DescriptionReturns the number of tables in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalTable
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalTable'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track database growth due to an increased number of tables over aperiod of time.
See AlsoNone
410 Version 2.1.0
db: # of tablespacesdb: # of tablespaces
DescriptionReturns the number of tablespaces in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalTablespace
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalTablespace'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track database growth over a period of time.
See AlsoNone
411Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
db: # of tablespaces with LONG datadb: # of tablespaces with LONG data
DescriptionReturns the number of tablespaces that store LONG data in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalTbspLONG
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalTbspLONG'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track database growth over a period of time. LONG data can take up alarge amount of space in a database.
See AlsoNone
412 Version 2.1.0
db: # of triggersdb: # of triggers
DescriptionReturns the number of triggers defined in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalTrigger
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalTrigger'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track the use of triggers in the database. There are benefits to usingtriggers, including faster application development, easier maintenance, and globalenforcement of business rules. For more information, see the DB2 Administration Guide forthe version of DB2 that you are using.
See AlsoNone
413Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
db: # of user indexesdb: # of user indexes
DescriptionReturns the number of indexes created by users in the database. Indexes created by SYSIBMare not counted.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalUser
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalUser'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track the use of indexes in the database.
The use of indexes can improve performance; for example, faster sorting of data. However,indexes can also have adverse effects on performance; for example, each INSERT orDELETE operation performed on a table requires additional updating of each index on thattable. For a discussion of this topic, see the DB2 Administration Guide for the version ofDB2 that you are using.
See AlsoNone
414 Version 2.1.0
db: # of viewsdb: # of views
DescriptionReturns the number of views in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalView
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbTotalView'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track the use of views in the database.
Views can be created to limit access to sensitive data, while allowing more general access toother data. This provides flexibility in the way your programs and end-user queries can lookat the table data.
See AlsoNone
415Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
db: User-defined SQL (numeric result)db: User-defined SQL (numeric result)
DescriptionRuns a user-defined SQL statement to monitor database resources.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
SQL StatementSpecifies a complete DB2 SQL statement.
CLI SynopsisdbUserDefinedSqlN
-a <SQL_statement>
The following briefly describes the argument for this monitor:
<SQL_statement>Specifies a complete DB2 SQL statement.
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbUserDefinedSqlN'-a 'select count (*) from Employee where (city="Austin")"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe SQL statement is expected to return a numeric value.
See AlsoNone
416 Version 2.1.0
db: User-defined SQL (string result)db: User-defined SQL (string result)
DescriptionRuns a user-defined SQL statement to monitor database resources.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
SQL StatementSpecifies a complete DB2 SQL statement.
CLI SynopsisdbUserDefinedSqlS
-a <SQL_statement>
<SQL_statement>Specifies a complete DB2 SQL statement.
Exampleswaddmon 'DB2Manager_Query_Monitors' 'dbUserDefinedSqlS'-a 'SELECT * from Employee'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe SQL statement is expected to return a string value. Use thedb: User-defined SQL(numeric result) monitor if you need a numeric value returned.
See AlsoDB2Manager Query monitors: “db: User-defined SQL (numeric result)” on page 416
417Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
table: # of rowstable: # of rows
DescriptionReturns the number of rows in the table.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner nameSpecifies the owner of the table.
Table nameSpecifies the name of the table.
CLI SynopsistableTotalRow
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Owner_name>Specifies the owner of the table.
<Table_name>Specifies the name of the table.
Exampleswaddmon 'DB2Manager_Query_Monitors' 'tableTotalRow'-a 'accmgr'-a 'company_names'"ManufacturingProfile"
Default Thresholds and ActionsNone
418 Version 2.1.0
Usage NotesUse this monitor to track growth of the table over a period of time.
See AlsoDB2Manager Query monitors: “db: User-defined SQL (numeric result)” on page 416
419Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
tbsp: # of tablestbsp: # of tables
DescriptionReturns the number of tables in the tablespace.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Tablespace nameSpecifies the name of the DB2 tablespace.
CLI SynopsistbspTotalTable
-a <DB2_table_space_name>
The following briefly describes the argument for this monitor:
<DB2_table_space_name>Specifies the name of the DB2 tablespace.
Exampleswaddmon 'DB2Manager_Query_Monitors' ' tbspTotalTable'-a 'tablespace1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track use of the tablespace over a period of time.
See AlsoNone
420 Version 2.1.0
user: # of tablesuser: # of tables
DescriptionReturns the number of tables owned by the database user.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
User nameSpecifies the name of the user.
CLI SynopsisuserTotalTable
-a <User_name>
The following briefly describes the argument for this monitor:
<User_name>Specifies the name of the user.
Exampleswaddmon 'DB2Manager_Query_Monitors' 'userTotalTable'-a 'accmgr'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse this monitor to track the use of database resources for tables by a particular user over aperiod of time.
See AlsoNone
421Tivoli Manager for DB2 Reference Guide
9.D
B2
Qu
eryM
on
itors
422 Version 2.1.0
DB2 SNMP Monitors
The monitors in the DB2Manager_SNMP_Monitors collection provide information fromthe DB2 Simple Network Management Protocol (SNMP) subagent. This subagent is aprogram that resides on a managed node and facilitates DB2 systems management throughproducts that conform to the SNMP protocol.
The SNMP subagent performs the following tasks:
¶ Generates alerts to an SNMP manager in the case of a severe DB2 error, such as acondition that requires operator intervention.
¶ Supplies information about the status of the DB2 server and databases. The informationprovided is documented in the Internet Engineering Task Force standard (RFC 1697).This monitoring collection implements a subset of this available information.
You can use the monitors in this collection to monitor key aspects of the DB2 environmentwithout specifically defining DB2 endpoints for them, or to monitor DB2 installations onmachines where Tivoli Management Framework services are unavailable. For example, youcan use these monitors to monitor DB2 instances and databases that reside on OS/2computers. See the Tivoli Manager for DB2 User’s Guide for more information.
Table 42 lists the monitors in this collection:
Table 42. DB2Manager SNMP MonitorsDesktop Name CLI Name Returned Value Format
DB2 database state dbRelStat Numeric:1 = Undetermined2 = Active3 = Available4 = Quiesced5 = Unavailable
DB2 server accumulatedconnections
srvAccumInAssoc Numeric
DB2 server current connections srvInAssoc Numeric
DB2 server finished transactions srvInfoFinishedTransactions Numeric
DB2 server status srvStatus Numeric:1 = Up2 = Down3 = Halted4 = Congested5 = Restarting
DB2 server version srvVersion String
10
423Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Table 42. DB2Manager SNMP Monitors (continued)Desktop Name CLI Name Returned Value Format
Maximum number of agentsallowed to register at the sametime
srvMaxInboundAssociations Numeric
Maximum number of agentsregistered at the same time
srvHighwaterInboundAssociations Numeric
Total Logical bytes read by DB2server for all active databases
srvLogicalReads Numeric
Total logical pages read by DB2server for all active databases
srvPageReads Numeric
Total physical bytes read by DB2server
srvDiskReads Numeric
Total physical bytes written byDB2 server for all active databases
srvDiskWrites Numeric
Total physical pages written byDB2 server for all active databases
srvPageWrites Numeric
Total rows selected returned byDB2 server for all active databases
srvRequestSends Numeric
Total SQL statements handled byDB2 server for all active databases
srvHandledRequests Numeric
Total SQL statements received byDB2 server for all active databases
srvRequestRecvs Numeric
424 Version 2.1.0
DB2 database state
DescriptionReturns a number that indicates the current state of the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
Database NameSpecifies the name of the DB2 database.
CLI SynopsisdbRelStat
-a <Community_name>
-a <Instance_name>
-a <Database_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
<Database_name>Specifies the name of the DB2 database.
425Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'dbRelStat'-a 'public'-a 'db2inst1'-a 'acctng'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the state of the database.
Table 43. Values to Determine Database StateValue Database State
1 Other (undetermined)
2 Active
3 Available
4 Quiesced
5 Unavailable (DB2 instance down)
See AlsoNone
426 Version 2.1.0
DB2 server accumulated connections
DescriptionReturns the total number of connections that are made for all active databases in the DB2server.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvAccumInAssoc
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvAccumInAssoc'-a 'public'-a 'db2inst1'"ManufacturingProfile"
427Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the frequency with which applications connect todatabases managed by this DB2 server.
See AlsoNone
428 Version 2.1.0
DB2 server current connections
DescriptionReturns the number of current local and remote connections to the databases in the DB2server.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvInAssoc
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvInAssoc'-a 'public'-a 'db2inst1'"ManufacturingProfile"
429Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the level of activity within the DB2 server and theamount of system resource being used.
See AlsoNone
430 Version 2.1.0
DB2 server finished transactions
DescriptionReturns the total number of SQL COMMIT and ROLLBACK statements for all activedatabases in the DB2 server.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvInfoFinishedTransactions
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvInfoFinishedTransactions'-a 'public'-a 'db2inst1'"ManufacturingProfile"
431Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of database activity for all databases managedby this DB2 server. The returned value is an indication of the units of work performed bythe databases.
See AlsoNone
432 Version 2.1.0
DB2 server status
DescriptionReturns a number that indicates the current status of the DB2 server.
Authorization Roleadmin
Target EndpointsDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvStatus
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvStatus'-a 'public'-a 'db2inst1'"ManufacturingProfile"
433Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the status of the DB2 server.
Table 44. Values to Determine Server StatusValue Server Status
1 Up
2 Down
3 Halted
4 Congested
5 Restarting
See AlsoNone
434 Version 2.1.0
DB2 server versionDB2 server version
DescriptionReturns the DB2 server product version ID.
Authorization Roleadmin
Target EndpointsDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvVersion
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvVersion'-a 'public'-a 'db2inst1'"ManufacturingProfile"
435Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the product version ID of the DB2 server. The returnedvalue is in the form pppvvrrm.
Table 45. Values to Determine Product Version IDValue Definition
ppp SQL
vv A 2-digit version number (with high-order 0 in the case of a 1-digit version)
rr A 2-digit release number (with high-order 0 in the case of a 1-digit release)
m A 1-digit modification level
See AlsoNone
436 Version 2.1.0
Maximum number of agents allowed to register at the same time
DescriptionReturns the maximum number of agents that can be registered at the same time for the DB2server.
Authorization Roleadmin
Target EndpointsDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvMaxInboundAssociations
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvMaxInboundAssociations'-a 'public'-a 'db2inst1'"ManufacturingProfile"
437Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value with the value returned by the Maximum number of agentsregistered at the same time monitor to evaluate the appropriateness of the current settingsfor the maximum agents allowed (maxagents) configuration parameter for the DB2 server. Ifthe values from the two monitors are similar, you can increase the maximum number ofagents allowed.
See AlsoDB2Manager SNMP monitors:“Maximum number of agents registered at the same time” on page 439DB2Manager Configuration monitors: “dbms: max_agents” on page 344
438 Version 2.1.0
Maximum number of agents registered at the same time
DescriptionReturns the maximum number of agents that the DB2 server has registered at the same time.
Authorization Roleadmin
Target EndpointsDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvHighwaterInboundAssociations
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvHighwaterInboundAssociations'-a 'public'-a 'db2inst1'"ManufacturingProfile"
439Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to evaluate the appropriateness of the current setting for themaximum agents allowed (maxagents) configuration parameter for the DB2 server. If thisreturned value is near the value for the maximum agents allowed, you can increase themaximum number of agents allowed.
See AlsoDB2Manager Configuration monitors: “dbms: max_agents” on page 344
440 Version 2.1.0
Total Logical bytes read by DB2 server for all active databases
DescriptionReturns the total number of logical bytes read from disk for all active databases in the DB2server.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvLogicalReads
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvLogicalReads'-a 'public'-a 'db2inst1'"ManufacturingProfile"
441Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of input and output activity due to logicalreads for all databases managed by this server.
See AlsoNone
442 Version 2.1.0
Total logical pages read by DB2 server for all active databases
DescriptionReturns the total number of logical pages read from disk for all active databases in the DB2server. Only data and index reads are included. Other input and output operations, such asreads from the log files, backups, and restores, are not included in this number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvPageReads
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvPageReads'-a 'public'-a 'db2inst1'"ManufacturingProfile"
443Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of input and output activity due to logicalreads for all databases managed by this server.
See AlsoNone
444 Version 2.1.0
Total physical bytes read by DB2 server
DescriptionReturns the total number of physical bytes read from disk for all active databases in theDB2 server. Only data and index reads are included. Other input and output operations, suchas reads from the log files, backups, and restores, are not included in this number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvDiskReads
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvDiskReads'-a 'public'-a 'db2inst1'"ManufacturingProfile"
445Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of input and output activity due to physicalreads for all databases managed by this server.
See AlsoNone
446 Version 2.1.0
Total physical bytes written by DB2 server for all active databases
DescriptionReturns the total number of physical bytes written to disk for all active databases in the DB2server. Only data and index writes are included. Other input and output operations, such aswrites to the log files, backups, and restores, are not included in this number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvDiskWrites
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvDiskWrites'-a 'public'-a 'db2inst1'"ManufacturingProfile"
447Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of input and output activity due to physicalwrites for all databases managed by this server.
See AlsoNone
448 Version 2.1.0
Total physical pages written by DB2 server for all active databases
DescriptionReturns the total number of physical pages written to disk for all active databases in theDB2 server. Only data and index reads are included. Other input and output operations, suchas writes to the log files, backups, and restores, are not included in this number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvPageWrites
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvPageWrites'-a 'public'-a 'db2inst1'"ManufacturingProfile"
449Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of input and output activity due to physicalwrites for all databases managed by this server.
See AlsoNone
450 Version 2.1.0
Total rows selected returned by DB2 server for all active databases
DescriptionReturns the total number of rows selected for all active databases in the DB2 server. OnlySQL SELECT requests are included.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvRequestSends
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvRequestSends'-a 'public'-a 'db2inst1'"ManufacturingProfile"
451Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Default Thresholds and ActionsNone
Usage NotesUse the returned value to gain insight into the current level of activity within the activedatabases in the DB2 server.
See AlsoNone
452 Version 2.1.0
Total SQL statements handled by DB2 server for all activedatabases
DescriptionReturns the total number of SQL statements handled for all active databases in the DB2server. Only SQL statements are included. Other statements, such as SQL DDL statements,are not included in this number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvHandledRequests
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
453Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvHandledRequests'-a 'public'-a 'db2inst1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value indicates the rate of database activity for databases managed by this DB2server. Use the returned value with the value returned by the Total SQL statementsreceived by DB2 server for all active databases monitor to calculate the number of failedSQL statements (total received minus total handled). This calculation can help you determinereasons for poor performance, because failed statements indicate lower throughput fordatabases.
See AlsoDB2Manager SNMP monitors: “Total SQL statements received by DB2 server for allactive databases” on page 455
454 Version 2.1.0
Total SQL statements received by DB2 server for all activedatabases
DescriptionReturns the total number of SQL statements received for all active databases. Only SQLstatements are included. Other statements, such as SQL DDL statements, are not included inthis number.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Community NameSpecifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public”.
Instance NameSpecifies the name of the DB2 instance that contains the database.
CLI SynopsissrvRequestRecvs
-a <Community_name>
-a <Instance_name>
The following briefly describes the arguments for this monitor:
<Community_name>Specifies the identifier used to group a set of SNMP agents that are managedtogether. Unless explicitly set by the user, the default community name honored bySNMP agents is the string “public.”
<Instance_name>Specifies the name of the DB2 instance that contains the database.
455Tivoli Manager for DB2 Reference Guide
10.D
B2
SN
MP
Mo
nito
rs
Exampleswaddmon 'DB2Manager_SNMP_Monitors' 'srvRequestRecvs-a 'public'-a 'db2inst1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value indicates the rate of database activity for databases managed by this DB2server. Use the returned value, with the value returned by the Total SQL statementshandled by DB2 server for all active databases monitor, to calculate the number of failedSQL statements (total received minus total handled). This calculation can help you determinereasons for poor performance, because failed statements indicate lower throughput fordatabases.
See AlsoDB2Manager SNMP monitors: “Total SQL statements handled by DB2 server for allactive databases” on page 453
456 Version 2.1.0
DB2 Sort Work Monitors
The monitors in the DB2Manager_Sort_Monitors collection provide information about thedatabase manager sort work. Sorting is often required during a query. Therefore, properconfiguration of the sort heap areas can be crucial to improving the query’s performance. Bymonitoring sort work, you can determine the current sort work performance and use theinformation to refine the sort heap configuration parameters (sortheap and sheapthres) andachieve better performance.
Sorting involves the following two steps:
¶ The sort phase
¶ The return of the results of the sort phase
In the sort phase, if the information being sorted cannot fit entirely into the sort heap, thesort overflows and the information must be stored in temporary database tables. Sorts that donot overflow perform better than those that do.
In the return phase, if the sorted information can return directly through the sort heap, it is apiped sort. A piped sort performs better than a nonpiped sort.
For more information about sorting and the sort heap configuration parameters, see the DB2Administration Guide: Performance for the version of DB2 that you are using.
Table 46 lists the monitors in this collection.
Table 46. DB2Manager Sort Work MonitorsDesktop Name CLI Name Returned Value
Format
conn: Application sorts connSorts Numeric
conn: Sort time (s) connSortTime Numeric: seconds
conn: Statement sorts connStmtSorts Numeric
db: Active sorts dbActiveSorts Numeric
db: Average sort time (ms) dbAvgSortTime Numeric: milliseconds
db: Percent sort overflowed dbPctSortOvflowed Numeric: percentage
db: Sort heap allocated dbSortHeapAllocated Numeric
db: Sort overflows dbSortOverflows Numeric
db: Total sort time (ms) dbTotalSortTime Numeric: milliseconds
db: Total sorts dbTotalSorts Numeric
dbms: Percent piped sorts rejected dbmsPctPipSrtsRej Numeric: percentage
11
457Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
Table 46. DB2Manager Sort Work Monitors (continued)Desktop Name CLI Name Returned Value
Format
dbms: Percent sort heap allocated dbmsPctSortHeapAlloc Numeric: percentage
dbms: Post threshold sorts dbmsPostThreshSorts Numeric
dbms: Sort heap allocated dbmsSortHeapAllocated Numeric
dbms: Total piped sorts rejected dbmsPipSrtsRej Numeric
458 Version 2.1.0
conn: Application sorts
DescriptionReturns the total number of sorts performed by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnSorts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'connSorts'-a '*TCPIP.A12CF9E8.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
459Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
Usage NotesUse this value with the value returned by the conn: Sort time (s) monitor to calculate theaverage time that the application spends in sorting. This average time can indicate whethersorting is lowering the performance of the application.
See AlsoDB2Manager Sort Work monitors: “conn: Sort time (s)” on page 461
460 Version 2.1.0
conn: Sort time (s)
DescriptionReturns the sorting time (in seconds) for the application during the last monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnSortTime
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'connSortTime'-a '*TCPIP.A12CF9E8.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
461Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
Usage NotesUse the returned value with the value returned by the conn: Application sorts monitor tocalculate the average time that the application spends in sorting. This average time canindicate if sorting is lowering the performance of the application.
See AlsoDB2Manager Locks and Deadlocks monitors: c“conn: Application sorts” on page 459
462 Version 2.1.0
conn: Statement sorts
DescriptionReturns the total number of times that a set of data was sorted to process the OPENoperation of the current SQL statement.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnStmtSorts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'connStmtSorts'-a '*TCPIP.A12CF9E8.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
463Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
Usage NotesUse the returned value to help identify the need for an index, because indexes can reducethe need for sorting a set of data. Identify the SQL statement for which this returned value isproviding sort information. Then, analyze this SQL statement to determine index candidatesby looking at columns that are being sorted. For example, a column used in an ORDER BYclause can be an index candidate.
See AlsoNone
464 Version 2.1.0
db: Active sorts
DescriptionReturns the number of sorts in the database that currently have a sort heap allocated.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbActiveSorts
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbActiveSorts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value with the value from the db: Sort heap allocated monitor todetermine the average sort heap space used by each sort in the database. If the sortheapconfiguration parameter is substantially larger than the average sort heap used, you canlower the value of this parameter.
This value includes heaps for sorts of temporary tables that are created during relationaloperations.
See AlsoDB2Manager Sort Work monitors: “dbms: Sort heap allocated” on page 476DB2Manager Configuration monitors: “db: sortheap” on page 337
465Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
db: Average sort time (ms)
DescriptionReturns the average sorting time (in milliseconds) at the database level.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbAvgSortTime
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbAvgSortTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine whether sorting is lowering the performance of thedatabase.
See AlsoNone
466 Version 2.1.0
db: Percent sort overflowed
DescriptionReturns the percentage of sorts that overflowed for the database during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctSortOvflowed
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbPctSortOvflowed'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t) parameter is not needed.
Default Thresholds and ActionsTable 47 shows the default threshold values for severity levels.
Table 47. dbPctSortOvflowed Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesA sort overflows when it runs out of sort heap and needs to store information in temporarytables for sorting. If the returned value is high compared to normal operating levels, youmight want to adjust the ApplHeapSz, stmtheap, stat_heap_sz, sortheap, and sheapthresconfiguration parameters. When a sort overflows, performance can be lowered because theoverflowed sort needs a merge phase and could require more input and output.
See AlsoDB2Manager Configuration monitors: “db: ApplHeapSz” on page 316, “db: sortheap”on page 337, “dbms: sheapthres” on page 354
467Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
db: Sort heap allocated
DescriptionReturns the total amount (in pages) of sort heap currently allocated for all sorts in thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSortHeapAllocated
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbSortHeapAllocated'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value with the value from the Active sorts monitor to determine theaverage sort heap space used by each sort in the database. If the average sort heap used issubstantially less than the value of the sortheap configuration parameter, you can lower thevalue of sortheap and reduce the memory allocated for the sort heap. If you adjust the valueof sortheap, also adjust the ApplHpSz, stmtheap,stat_heap_sz, and sheapthresconfiguration parameters.
See AlsoDB2Manager Sort Work monitors: “db: Active sorts” on page 465DB2Manager Configuration monitors: “db: sortheap” on page 337,“db: ApplHeapSz” on page 316, “dbms: sheapthres” on page 354,
468 Version 2.1.0
db: Sort overflows
DescriptionReturns the total number of sorts that overflowed within a database. A sort overflows whenit runs out of sort heap and needs to store information in temporary tables for sorting.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSortOverflows
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbSortOverflows'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesWhen a sort overflows, performance can be lowered because the overflowed sort needs amerge phase and could require more input and output space. If the returned value is highcompared to normal operating levels, use the Percent sort overflowed monitor to determinewhether you want to increase the sort heap size. If you adjust the value of sortheap, alsoadjust the applheapsz, stmtheap, stat_heap_sz, and sheapthres configuration parameters.
If the number of sort overflows is small with respect to the total sorts, increasing the sortheap size will have little impact on performance, unless the buffer pool size is increasedsubstantially.
See AlsoDB2Manager Sort Work monitors: “db: Percent sort overflowed” on page 467DB2Manager Configuration monitors: “db: sortheap” on page 337,“db: ApplHeapSz” on page 316, “dbms: sheapthres” on page 354,“db: buffpage” on page 318
469Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
db: Total sort time (ms)
DescriptionReturns the total elapsed time (in milliseconds) for all sorts that were executed within adatabase during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalSortTime
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbTotalSortTime'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the average sort time (db: Average sort time(ms)). Use the average sort time to determine if sorting is lowering the performance of thedatabase.
The returned value includes the sort time of temporary tables that are created during relatedoperations.
See AlsoDB2Manager Sort Work monitors: “db: Average sort time (ms)” on page 466
470 Version 2.1.0
db: Total sorts
DescriptionReturns the total number of sorts that were executed within a database during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbTotalSorts
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbTotalSorts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value is used in calculating the average sort time (db: Average sort time (ms))and in calculating the percentage of sorts that need more heap space (db: Percent sortoverflowed).
See AlsoDB2Manager Sort Work monitors: “db: Average sort time (ms)” on page 466, “db:Percent sort overflowed” on page 467
471Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
dbms: Percent piped sorts rejected
DescriptionReturns the percentage of piped sort requests that were rejected for the DB2 instance duringthe monitoring interval.
Authorization Roleadmin
Target EndpointsNonpartitioned DB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPctPipSrtsRej
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbmsPctPipSrtsRej'-t '20 minutes'"ManufacturingProfile"
If the default duration of one hour is desired, the (-t parameter is not needed.
Default Thresholds and ActionsTable 48 shows the default threshold values for severity levels.
Table 48. dbmsPctPipSrtsRej Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesIn the sort return phase, if the sorted information can return directly through the sort heap, itis a piped sort. However, even if the optimizer requests a piped sort, this request is rejectedat run time if the total amount of sort heap memory for all sorts on the database is close toexceeding the sheapthres value.
If this returned value is high compared to normal operating levels, consider decreasing yoursort heap (using the sortheap configuration parameter) or increasing your sort heapthreshold (using the sheapthres configuration parameter). However, be aware of theimplications of these options. If you increase the sort heap threshold, more memory canremain allocated for sorting, causing the paging of memory to disk. If you decrease the sortheap, you can require an extra merge phase that could slow down the sort.
472 Version 2.1.0
See AlsoDB2Manager Configuration monitors: “dbms: sheapthres” on page 354, “db: sortheap”on page 337
473Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
dbms: Percent sort heap allocated
DescriptionReturns the percentage of the allocated sort heap that the DB2 instance used during themonitoring interval.
Authorization Roleadmin
Target EndpointsNonpartitioned DB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPctSortHeapAlloc
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbmsPctSortHeapAlloc'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf this returned percentage is high compared to normal operating levels, the percentage ofpiped sorts rejected can be increasing. See the dbms: Percent piped sorts rejected monitorfor more information.
See AlsoDB2Manager Sort Work monitors: “dbms: Percent piped sorts rejected” on page 472
474 Version 2.1.0
dbms: Post threshold sorts
DescriptionReturns the number of sorts that requested heaps after the sort heap threshold was reachedduring the monitoring interval.
Authorization Roleadmin
Target EndpointsNonpartitioned DB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPostThreshSorts
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbmsPostThreshSorts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIf the returned value is high compared to normal operating levels, you could improve yoursort performance by increasing the sheapthres configuration parameter.
Sort heaps are allocated at the beginning of sorts and the beginning of merge phases. If atany time during a sort a request to allocate a sort heap would exceed the sheapthres, thesort is considered to be a post-threshold sort. In post-threshold sorts, the amount of sort heapallocated is smaller than the sortheap value.
See AlsoDB2Manager Configuration monitors: “dbms: sheapthres” on page 354, “db: sortheap”on page 337
475Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
dbms: Sort heap allocated
DescriptionReturns the total amount (in pages) of sort heap currently allocated for all sorts in all activedatabases in the DB2 instance.
Authorization Roleadmin
Target EndpointsNonpartitioned DB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsSortHeapAllocated
Exampleswaddmon 'DB2Manager_Sort_Monitors' 'dbmsSortHeapAllocated'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to refine the sheapthres configuration parameter. If the returnedvalue is greater than or equal to the sheapthres parameter, the sorts are not getting the fullsort heap as defined by the sortheap configuration parameter.
See AlsoDB2Manager Configuration monitors: “dbms: sheapthres” on page 354, “db: sortheap”on page 337
476 Version 2.1.0
dbms: Total piped sorts rejected
DescriptionReturns the total number of piped sorts that were rejected during the monitoring interval.
Authorization Roleadmin
Target EndpointsNonpartitioned DB2InstanceManager, DB2DatabaseManager, and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbmsPipSrtsRej
Exampleswaddmon 'DB2ManagerManager_Sort_Monitors' 'dbmsPipSrtsRej'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesIn the return phase of sorting, if the sorted information can return directly through the sortheap, it is a piped sort. However, even if the optimizer requests a piped sort, this request isrejected at run time if the total amount of sort heap memory for all sorts on the database isclose to exceeding the sheapthres value.
If this returned value is high compared to the total number of sorts requested, considerdecreasing your sort heap (using the sortheap configuration parameter) or increasing yoursort heap threshold (using the sheapthres configuration parameter). However, be aware ofthe implications of these options. If you increase the sort heap threshold, more memory canremain allocated for sorting, causing the paging of memory to disk. If you decrease the sortheap, you can require an extra merge phase that could slow down the sort.
See AlsoDB2ManagerManager Configuration monitors: “dbms: sheapthres” on page 354, “db:sortheap” on page 337
477Tivoli Manager for DB2 Reference Guide
11.D
B2
So
rtW
ork
Mo
nito
rs
478 Version 2.1.0
DB2 SQL Statement Activity Monitors
The monitors in the DB2Manager_Stmt_Monitors collection provide statistics on SQLstatement activity. SQL activity is a measure of database throughput and performance.
Recognizing the SQL pattern in a database can help you make decisions about refining thedatabase and database manager configuration parameters. For example, you can refinecertain parameters based on whether you are running query-only or update-intensiveapplications.
Table 49 lists the monitors in this collection.
Table 49. DB2Manager SQL Statement Activity MonitorsDesktop Name CLI Name Returned Value Format
conn: Application section inserts connApplSectionInserts Numeric
conn: Application section lookups connApplSectionLookups Numeric
conn: Binds/precompiles attempted connBindsPrecompAttempted Numeric
conn: Commits connCommits Numeric
conn: DDL SQL statements connDdlSqlStmts Numeric
conn: Dynamic SQL statements connDynamicSqlStmts Numeric
conn: Explicit commits connCommitSqlStmts Numeric
conn: Explicit rollbacks connRollbackSqlStmts Numeric
conn: Failed SQL statements connFailedSqlStmts Numeric
conn: Open block cursors connOpenBlkCursors Numeric
conn: Open cursors connOpenCursors Numeric
conn: Percent DDL SQL connPctDdlSql Numeric: percentage
conn: Percent UID SQL connPctUidSql Numeric: percentage
conn: Rollbacks connRollbacks Numeric
conn: Rows deleted connRowsDeleted Numeric
conn: Rows inserted connRowsInserted Numeric
conn: Rows selected connRowsSelected Numeric
conn: Rows updated connRowsUpdated Numeric
conn: Select SQL statements connSelectSqlStmts Numeric
conn: SQL requests since last commit connSQLReqSinceLastCommit Numeric
conn: Static SQL statements connStaticSqlStmts Numeric
conn: Update/Insert/Delete SQL connUidSqlStmts Numeric
db: Committed statements per second dbCommitRate Numeric
12
479Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Table 49. DB2Manager SQL Statement Activity Monitors (continued)Desktop Name CLI Name Returned Value Format
db: DDL SQL statements dbDdlSqlStmts Numeric
db: Dynamic SQL statements dbDySqlStmts Numeric
db: Failed SQL statements dbFailedSqlStmts Numeric
db: Percent DDL SQL dbPctDdlSqlStmts Numeric: percentage
db: Percent failed SQL dbPctFailedSqlStmts Numeric: percentage
db: Percent select SQL dbPctSelectSqlStmts Numeric: percentage
db: Percent UID SQL dbPctUidSqlStmts Numeric: percentage
db: Rollbacks per second dbRollbackRate Numeric
db: Select SQL statements dbSelectSqlStmts Numeric
db: SQL statements per second dbSqlStmtRate Numeric
db: Static SQL statements dbStSqlStmts Numeric
db: Update/Insert/Delete SQL dbUidSqlStmts Numeric
480 Version 2.1.0
conn: Application section inserts
DescriptionReturns the number of inserts of SQL sections by an application from its SQL work area.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnApplSectionInserts
-a <DB2_snapshot_application_ID>
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connApplSectionInserts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe working copy of any executable section is stored in a unique SQL work area. Thereturned value is a count of how many times a copy was not available and had to beinserted.
481Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Application section lookups” onpage 483
482 Version 2.1.0
conn: Application section lookups
DescriptionReturns the number of lookups of SQL sections by an application from its SQL work area.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnApplSectionLookups
-a <DB2_snapshot_application_ID>
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connApplSectionLookups'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
483Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesEach agent has access to a unique SQL work area where the working copy of anyexecutable section is kept. In partitioned databases, this work area is shared by all non-SMPagents. In other environments and with SMP agents, each agent has its own unique SQLwork area.
The returned value indicates how many times the SQL work area was accessed by agents foran application. The returned value is a cumulative total of all lookups on all SQL workheaps for agents working for this application.
Use the returned value in conjunction with the conn: Application section inserts monitor torefine the size of the heap used for the SQL work area. In partitioned databases this size iscontrolled by the app_ctl_heap_sz configuration parameter. The SQL work area size innonpartitioned database environments uses the ApplHeapSz configuration parameter. Thesize of the SQL work area for SMP agents is controlled by ApplHeapSz in allenvironments.
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Application section inserts” onpage 481
DB2Manager Configuration monitors: “db: app_ctl_heap_sz” on page 315, “db:ApplHeapSz” on page 316
484 Version 2.1.0
conn: Binds/precompiles attempted
DescriptionReturns the number of binds and precompiles attempted by an application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnBindsPrecompAttempted
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connBindsPrecompAttempted'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the current level of activity in the database manager.
485Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
The number that is returned does not include the count of Internal Automatic Rebinds, but itdoes include binds that are a result of the REBIND PACKAGE command.
See AlsoDB2Manager Database tasks: “ECC_Rebind_Package” on page 635
486 Version 2.1.0
conn: Commits
DescriptionReturns the total number of SQL COMMIT statements that were attempted by theapplication. This value includes SQL COMMIT statements that are issued from theapplication and internal commits that are initiated by the database manager for theapplication.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnCommits
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connCommits'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
487Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesIf this returned value has a small rate of change over a period of time, applications mightnot be doing frequent commits, which can lead to problems with logging and dataconcurrency.
This number can be used to calculate the total number of units of work (UOW) done by thisapplication: UOW = COMMITs (total number) + ROLLBACK statements attempted +internal rollbacks. This calculation includes only those units of work done since the later ofthe following:
¶ The time of the connection to the database
¶ The last reset of the database monitor counters
The number of units of work is an indication of the level of database activity for thisapplication.
See AlsoNone
488 Version 2.1.0
conn: DDL SQL statements
DescriptionReturns the total number of SQL DDL statements that were executed by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnDdlSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connDdlSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
489Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesDDL statements are expensive to run because of their impact on the system catalog tables. Ifthis returned value is high compared to normal operating levels, determine the cause andrestrict this activity from being performed.
This value is also used to calculate the percentage of DDL activity for this application.
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Percent DDL SQL” on page 503
490 Version 2.1.0
conn: Dynamic SQL statements
DescriptionReturns the total number of dynamic SQL statements that were attempted by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnDynamicSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connDynamicSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
491Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine the level of SQL statement activity attributable to thisapplication.
See AlsoNone
492 Version 2.1.0
conn: Explicit commits
DescriptionReturns the total number of SQL COMMIT statements that were explicitly attempted by theapplication.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnCommitSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connCommitSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
493Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesIf this returned value has a small rate of change over a period of time, applications mightnot be doing frequent commits, which can lead to problems with logging and dataconcurrency.
This number can be used to calculate the total number of units of work (UOW) done by thisapplication: UOW = COMMIT statements attempted + internal commits + ROLLBACKstatements attempted + internal rollbacks. This calculation includes only those units of workdone since the later of the following:
¶ The time of the connection to the database
¶ The last reset of the database monitor counters
The number of units of work is an indication of the level of database activity for thisapplication.
See AlsoNone
494 Version 2.1.0
conn: Explicit rollbacks
DescriptionReturns the total number of rollbacks explicitly attempted by the application. This valueincludes only the number of SQL ROLLBACK statements issued from the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnRollbackSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connRollbackSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
495Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine the level of database activity for the application and theamount of conflict with other applications. Try to minimize the number of rollbacks, becausehigher rollback activity results in lower throughput for the database.
This number can be used to calculate the total number of units of work (UOW) done by thisapplication: UOW = COMMIT statements attempted + internal commits + ROLLBACKstatements attempted + internal rollbacks. This calculation includes only those units of workdone since the later of the following:
¶ The time of the connection to the database
¶ The last reset of the database monitor counters
The number of units of work is an indication of the level of database activity for thisapplication.
See AlsoNone
496 Version 2.1.0
conn: Failed SQL statements
DescriptionReturns the total number of failed SQL statements for the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnFailedSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connFailedSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile>"
Default Thresholds and ActionsNone
497Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine reasons for poor performance. Failed statements indicatethat time is wasted by the database manager and result in lower throughput for the database.
See AlsoNone
498 Version 2.1.0
conn: Open block cursors
DescriptionReturns the total number of blocking cursors (local and remote) that are currently open forthe application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnOpenBlkCursors
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connOpenBlkCursors'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
499Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value along with the value from the conn: Open block cursors monitor tocalculate the percentage of cursors that are blocking cursors. If the percentage is lowcompared to normal operating levels, you can improve performance by improving the rowblocking in the application.
You can improve row blocking by either of the following methods:
¶ Checking the pre-compile options for record blocking for treatment of ambiguouscursors
¶ Redefining cursors to allow for blocking (for example, specify FOR FETCH ONLY onyour cursors)
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Open block cursors” onpage 499
500 Version 2.1.0
conn: Open cursors
DescriptionReturns the total number of cursors (local and remote) that are currently open for theapplication. This value also includes the number of local and remote blocking cursorscurrently open for the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnOpenCursors
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connOpenCursors'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
501Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value along with the value from the conn: Open block cursors monitor tocalculate the percentage of cursors that are blocking cursors. If the percentage is lowcompared to normal operating levels, you can improve performance by improving the rowblocking in the application.
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Open block cursors” onpage 499
502 Version 2.1.0
conn: Percent DDL SQL
DescriptionReturns the percentage of total SQL statements that were SQL DDL statements executed bythe application during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPctDdlSql
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connPctDdlSql'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
503Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesDue to the high activity in the system catalog tables, try to keep DDL statement activity to aminimum. If the returned value is high compared to normal operating levels, determine theactivity causing it to be high and restrict it from being performed. Examples of DDLstatements are CREATE TABLE, CREATE VIEW, ALTER TABLE, and DROP INDEX.
You can also use the returned value to refine the package cache hit ratio for this application.DDL statements can also impact the package cache by invalidating sections that are storedthere and causing additional system overhead due to section recompilation.
See AlsoNone
504 Version 2.1.0
conn: Percent UID SQL
DescriptionReturns the percentage of total SQL statements that were SQL UPDATE, INSERT, andDELETE statements executed by the application during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnPctUidSql
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connPctUidSql'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
505Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine if the application performs frequent updates. If thereturned value is low compared to normal operating levels, the application is query-based;otherwise, it is update-based.
Knowing what type of applications you have (query-based or update-based) can aid you inrefining the database configuration parameters.
See AlsoNone
506 Version 2.1.0
conn: Rollbacks
DescriptionReturns the total number of rollbacks attempted by the application. This value includes SQLROLLBACK statements that are issued from the application and internal rollbacks that areinitiated by the database manager for the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 snapshot application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnRollbacks
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connRollbacks'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
507Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine the level of database activity for the application and theamount of conflict with other applications. Try to minimize the number of rollbacks, becausehigher rollback activity results in lower throughput for the database.
This number can be used to calculate the total number of units of work (UOW) done by thisapplication: UOW = COMMIT statements attempted + internal commits + ROLLBACKs(total). This calculation includes only those units of work done since the later of thefollowing:
¶ The time of the connection to the database
¶ The last reset of the database monitor counters
The number of units of work is an indication of the level of database activity for thisapplication.
See AlsoNone
508 Version 2.1.0
conn: Rows deleted
DescriptionReturns the total number of row deletions attempted by the application. This value includesthe number of rows deleted from the database as a result of internal database activityperformed for the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnRowsDeleted
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connRowsDeleted'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
509Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value as an indication of the level of database activity generated by theapplication.
See AlsoNone
510 Version 2.1.0
conn: Rows inserted
DescriptionReturns the total number of row inserts attempted by the application. This value includes thenumber of rows inserted into the database as a result of internal database activity performedfor the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnRowsInserted
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connRowsInserted'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
511Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value as an indication of the level of database activity generated by theapplication.
See AlsoNone
512 Version 2.1.0
conn: Rows selected
DescriptionReturns the number of rows that were selected and returned to the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnRowsSelected
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connRowsSelected'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
513Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value as an indication of the level of database activity generated by theapplication. This value does not include a count of rows read for actions such as COUNT(*)or joins.
See AlsoNone
514 Version 2.1.0
conn: Rows updated
DescriptionReturns the total number of row updates attempted by the application. This value includesthe number of rows updated in the database as a result of internal database activityperformed for the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnRowsUpdated
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connRowsUpdated'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
515Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value as an indication of the level of database activity generated by theapplication.
See AlsoNone
516 Version 2.1.0
conn: Select SQL statements
DescriptionReturns the number of SQL SELECT statements that were executed by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnSelectSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connSelectSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
517Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine the level of database select SQL statement activitygenerated by the application.
See AlsoNone
518 Version 2.1.0
conn: SQL requests since last commit
DescriptionReturns the number of SQL requests that were submitted by the application since the lastcommit.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnSQLReqSinceLastCommit
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connSQLReqSinceLastCommit'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
519Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to monitor the progress of a transaction.
See AlsoNone
520 Version 2.1.0
conn: Static SQL statements
DescriptionReturns the number of static SQL statements that were attempted by the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnStaticSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connStaticSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
521Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine the level of SQL statement activity attributable to thisapplication.
See AlsoNone
522 Version 2.1.0
conn: Update/Insert/Delete SQL
DescriptionReturns the number of SQL UPDATE, INSERT, and DELETE statements that were executedby the application.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
DB2 Snapshot Application IDSpecifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
CLI SynopsisconnUidSqlStmts
-a <DB2_snapshot_application_ID>
The following briefly describes the argument for this monitor:
<DB2_snapshot_application_ID>Specifies the unique application identification that is generated when the applicationconnects to the database. Different formats for the application ID are dependent onthe communication protocol between the client and the server on which the databasemanager runs. See “DB2 Snapshot Application ID Formats” on page 699 forinformation about these formats.
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'connUidSqlStmts'-a '*NETBIOS.DBERE.930131214645'"ManufacturingProfile"
Default Thresholds and ActionsNone
523Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
Usage NotesUse the returned value to determine the level of database update activity generated by theapplication.
The returned value is also used in calculations for the conn: Percent UID SQL monitor.
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Percent UID SQL” on page 505
524 Version 2.1.0
db: Committed statements per second
DescriptionReturns the rate (counts per second) at which unit-of-work commits were attempted for thedatabase during the monitoring interval. Unit-of-work commits include SQL COMMITstatements that are issued from applications and internal commits that are initiated by thedatabase manager.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbCommitRate
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbCommitRate'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine rates of database activity.
See AlsoNone
525Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
db: DDL SQL statements
DescriptionReturns the number of SQL DDL statements that were executed in the database during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDdlSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbDdlSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesDue to the high activity in the system catalog tables, try to keep DDL statement activity to aminimum. If the returned value is high compared to normal operating levels, determine theactivity causing it to be high and restrict it from being performed. Examples of DDLstatements are CREATE TABLE, CREATE VIEW, ALTER TABLE, and DROP INDEX.
This value is also used to calculate the percentage of DDL activity for the database.
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Percent DDL SQL” on page 503
526 Version 2.1.0
db: Dynamic SQL statements
DescriptionReturns the number of dynamic SQL statements that were attempted for the database duringthe monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbDySqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbDySqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of SQL statement activity in the database.
See AlsoNone
527Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
db: Failed SQL statements
DescriptionReturns the number of failed SQL statements for the database during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbFailedSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbFailedSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine reasons for poor performance. Failed statements indicatetime is wasted by the database manager and result in lower throughput for the database.
See AlsoNone
528 Version 2.1.0
db: Percent DDL SQL
DescriptionReturns the percentage of total SQL statements that were SQL DDL statements during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctDdlSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbPctDdlSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsRun the monitor every 60 minutes without any time restrictions.
Usage NotesDue to the high activity in the system catalog tables, try to keep DDL statement activity to aminimum. If the returned value is high compared to normal operating levels, determine theactivity causing it to be high and restrict it from being performed. Examples of DDLstatements are CREATE TABLE, CREATE VIEW, ALTER TABLE, and DROP INDEX.
DDL statements can also impact the package cache, by invalidating sections that are storedthere and causing additional system overhead due to section recompilation.
See AlsoNone
529Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
db: Percent failed SQL
DescriptionReturns the percentage of total SQL statements that failed during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctFailedSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbPctFailedSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsTable 50 shows the suggested threshold values for severity levels.
Table 50. dbPctFailedSqlStmts Response LevelsResponse Level Trigger When Default Actions
critical Greater than 95% Send Tivoli Notice; Change Icon
severe Greater than 90% Send Tivoli Notice; Change Icon
warning Greater than 80% Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesThe returned value can help determine reasons for poor performance, because failedstatements indicate time wasted by the database manager and result in lower throughput forthe database.
See AlsoNone
530 Version 2.1.0
db: Percent select SQL
DescriptionReturns the percentage of total SQL statements that were SQL SELECT statements duringthe monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctSelectSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbPctSelectSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of application activity and throughput for thedatabase.
See AlsoNone
531Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
db: Percent UID SQL
DescriptionReturns the percentage of total SQL statements that were SQL UPDATE, INSERT, andDELETE statements during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbPctUidSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbPctUidSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of database data change activity.
See AlsoNone
532 Version 2.1.0
db: Rollbacks per second
DescriptionReturns the rate (counts per second) at which unit-of-work rollbacks were attempted duringthe monitoring interval. Unit-of-work rollbacks include SQL ROLLBACK statements thatare issued from applications and internal rollbacks that are initiated by the database manager.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbRollbackRate
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbRollbackRate'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the rates of database activity and the amount of conflictin the database. Try to minimize the number of rollbacks, because higher rollback activityresults in lower throughput for the database.
See AlsoNone
533Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
db: Select SQL statements
DescriptionReturns the number of SQL SELECT statements that were executed during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSelectSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbSelectSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of database activity. The returned value is alsoused in calculations for the db: Percent select SQL monitor.
See AlsoDB2Manager SQL Statement Activity monitors: “db: Percent select SQL” on page 531
534 Version 2.1.0
db: SQL statements per second
DescriptionReturns the rate (statements per second) at which SQL statements were executed during themonitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbSqlStmtRate
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbSqlStmtRate'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesThe returned value indicates the rate of database SQL statement activity.
See AlsoNone
535Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
db: Static SQL statements
DescriptionReturns the number of static SQL statements that were attempted during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbStSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbStSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of SQL statement activity in the database.
See AlsoNone
536 Version 2.1.0
db: Update/Insert/Delete SQL
DescriptionReturns the number of SQL UPDATE, INSERT, and DELETE statements that were executedduring the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbUidSqlStmts
Exampleswaddmon 'DB2Manager_Stmt_Monitors' 'dbUidSqlStmts'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value to determine the level of database activity.
The returned value is also used in calculations for the db: percent UID SQL monitor. Theresult can be useful for analyzing activity and throughput.
See AlsoDB2Manager SQL Statement Activity monitors: “conn: Percent UID SQL” on page 505
537Tivoli Manager for DB2 Reference Guide
12.D
B2
SQ
LS
tatemen
tA
ctivityM
on
itors
538 Version 2.1.0
DB2 Table Monitors
The monitors in the DB2Manager_Table_Monitors collection provide information about thefollowing:
¶ Invalid packages
¶ Table rows (read, written, and overflowed)
¶ The last time the monitor counters were reset at a table header level
¶ The need for table reorganization
Table 51 lists the monitors in this collection.
Table 51. DB2Manager Table MonitorsDesktop Name CLI Name Returned Value
Format
db: Number of all invalid packages dbInvalidPkgAll Numeric
db: Number of invalid SYSTEM packages dbInvalidPkgSystem Numeric
db: Number of invalid user packages dbInvalidPkgUser Numeric
table: Overflow accesses tableOverflowAcc Numeric
table: Reorg needed tableReorgChkOne String: YY YN NYNN
table: Rows read per second tableRowsRead Numeric
table: Rows written per second tableRowsWritten Numeric
13
539Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
db: Number of all invalid packages
DescriptionReturns the number of all packages that are currently marked invalid in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbInvalidPkgAll
Exampleswaddmon 'DB2Manager_Table_Monitors' 'dbInvalidPkgAll'"ManufacturingProfile"
Default Thresholds and ActionsTable 52 shows the defaulted threshold values for severity levels.
Table 52. dbInvalidPkgAll Response LevelsResponse Level Trigger When Default Actions
critical Greater than 20 Send Tivoli Notice; Change Icon
severe Greater than 15 Send Tivoli Notice; Change Icon
warning Greater than 1 Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value as an indication of the current number of invalid packages. Apackage is marked invalid if it depends on an object (for example, a table) and that object isdropped.
The number of invalid packages can indicate how many automatic rebinds are necessary inthe database. An invalid package is usually automatically rebound the next time it isaccessed, unless it was marked invalid because a trigger was dropped or because thedropped object was not recreated. Use of automatic rebinds can significantly lowerperformance and should be minimized where possible.
See AlsoNone
540 Version 2.1.0
db: Number of invalid SYSTEM packages
DescriptionReturns the number of SYSTEM packages that are currently marked invalid in the database.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsNone
CLI SynopsisdbInvalidPkgSystem
Exampleswaddmon 'DB2Manager_Table_Monitors' 'dbInvalidPkgSystem'"ManufacturingProfile"
Default Thresholds and ActionsTable 53 shows the defaulted threshold values for severity levels.
Table 53. dbInvalidPkgSystem Response LevelsResponse Level Trigger When Default Actions
critical Greater than 20 Send Tivoli Notice; Change Icon
severe Greater than 15 Send Tivoli Notice; Change Icon
warning Greater than 1 Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Usage NotesUse the returned value as an indication of the current number of invalid packages owned bySYSTEM. A package is marked invalid if it depends on an object (for example, a table) andthat object is dropped.
The number of invalid packages can indicate how many automatic rebinds are necessary inthe database. An invalid package is usually automatically rebound the next time it isaccessed, unless it was marked invalid because a trigger was dropped or because thedropped object was not recreated. Use of automatic rebinds can significantly lowerperformance and should be minimized where possible.
See AlsoNone
541Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
db: Number of invalid user packages
DescriptionReturns the number of packages owned by a user that are currently marked invalid in thedatabase.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner nameSpecifies the owner of the package.
CLI SynopsisdbInvalidPkgUser
-a <Owner_name>
The following briefly describes the argument for this monitor:
<Owner_name>Specifies the owner of the package.
Exampleswaddmon 'DB2Manager_Table_Monitors' 'dbInvalidPkgUser'-a 'user1'"ManufacturingProfile"
Default Thresholds and ActionsNone
Usage NotesUse the returned value as an indication of the current number of invalid packages owned bythe user. A package is marked invalid if it depends on an object (for example, a table) andthat object is dropped.
The number of invalid packages can indicate how many automatic rebinds are necessary inthe database. An invalid package is usually automatically rebound the next time it isaccessed, unless it was marked invalid because a trigger was dropped or because the
542 Version 2.1.0
dropped object was not recreated. Use of automatic rebinds can significantly lowerperformance and should be minimized where possible.
See AlsoNone
543Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
table: Overflow accesses
DescriptionReturns the number of accesses (reads and writes) made to overflowed rows of this table.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner nameSpecifies the owner of the table.
Table nameSpecifies the name of the table.
CLI SynopsistableOverflowAcc
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Owner_name>Specifies the owner of the table.
<Table_name>Specifies the name of the table.
Exampleswaddmon 'DB2Manager_Table_Monitors' 'tableOverflowAcc'-a 'lovejoy'-a 'employees'"ManufacturingProfile"
Default Thresholds and ActionsNone
544 Version 2.1.0
Usage NotesOverflowed records indicate that data fragmentation occurred. If this number is highcompared to normal operating levels, you can improve table performance by reorganizingthe table. See the Reorg needed monitor to verify whether a table needs reorganizing.
A row overflows if it is updated and no longer fits in the data pages where it was originallywritten. Row overflow usually happens as a result of an update of a VARCHAR column orfrom an ALTER TABLE statement.
See AlsoDB2Manager Table monitors: “table: Reorg needed” on page 546
545Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
table: Reorg needed
DescriptionReturns a string indicating whether the specified table or its indexes need to be reorganized.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner nameSpecifies the owner of the table.
Table nameSpecifies the name of the table.
CLI SynopsistableReorgChkOne
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Owner_name>Specifies the owner of the table.
<Table_name>Specifies the name of the table.
Exampleswaddmon 'DB2Manager_Table_Monitors' 'tableReorgChkOne'-a 'lovejoy'-a 'employees'"ManufacturingProfile"
Default Thresholds and ActionsTable 54 shows the defaulted threshold values for severity levels.
Table 54. tableReorgChkOne Response LevelsResponse Level Trigger When Default Actions
critical N/A None
546 Version 2.1.0
Table 54. tableReorgChkOne Response Levels (continued)Response Level Trigger When Default Actions
severe N/A None
warning Matches Y (in any position) Send Tivoli Notice; Change Icon
normal N/A None
always N/A None
Schedule the monitor to run every 24 hours without any time restrictions.
Usage NotesThe returned value, as shown in Table 55, is a two-character string that indicates whether thetable or any of its indexes need to be reorganized.
Table 55. String Values that Determine Need for Table ReorganizationString Description
YN The table needs to be reorganized.
NY At least one of the indexes needs to be reorganized.
YY The table and at least one of the indexes need to be reorganized.
NN The table does not need to be reorganized.
Reorganizing a table can improve access performance. When you reorganize a table, thetable data is rearranged into a physical sequence, usually according to a specified index. Asa result, SQL statements on that data can be processed more efficiently. In addition, thereorganization process removes unused, empty space from the table, and the reorganizedtable is stored more compactly.
To calculate the returned value, this monitor uses statistics from six DB2 formulas todetermine if performance has deteriorated or if it can be improved by reorganization. The sixformulas are used in the following ways:
¶ Formulas F1, F2, and F3 are used to check the table. If the results indicate that the tableshould be reorganized, the first character of the returned string is a Y.
¶ Formulas F4, F5, and F6 are used to check the indexes one by one. If the resultsindicate that at least one of the indexes should be reorganized, the second character ofthe returned string is a Y. If the table has no indexes, the second character is always anN.
Current table statistics are used when calculating the results. For more information on theformulas, see the REORGCHK command in the DB2 Command Reference for the versionof DB2 that you are using. The DB2 recommended results are given as:
Table 56. DB2 Formula ResultsFormula If the Results are:
F1 Less than 5 do not reorg
F2 Greater than 70 do not reorg
F3 Greater than 80 do not reorg
F4 Greater than 80 do not reorg
547Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
Table 56. DB2 Formula Results (continued)Formula If the Results are:
F5 Greater than 50 do not reorg
F6 Less than 100 do not reorg
Along with the returned value, Tivoli Manager for DB2 writes additional information in acomment in the Tivoli notice or message. The first line of the comment lists the table owner,table name, and the results of formulas F1, F2, and F3 (Table_owner.Table_name=(resultF1resultF2resultF3)) Subsequent lines of the comment list the index owner, indexname, and the results of formulas F4, F5, and F6 (Index_owner.Index_name=(resultF4resultF5resultF6)).
For example:
Suppose you have a table with owner USERID, table name TABLE1, and two indexes,INDX1 and INDX2. INDX1 has the owner USERID and INDX2 has the owner DBADMIN.You use the table:Reorg needed monitor to create a monitor that sends a notice if thereturned string contains a Y (when the table or either index needs reorganizing. The resultsfor each formula for the table and indexes are given as:
Table 57. DB2 Formula ExampleName F1 F2 F3 F4 F5 F6
TABLE1 29 58 60
INDX1 97 64 11
INDX2 97 48 77
Both TABLE1 and INDX2 need reorganizing; a notice is sent that contains the followinglines:
YY USERID.TABLE1 = (295860) USERID.INDX1 = (976411) DBADMIN.INDX2 =(974877)
See AlsoNone
548 Version 2.1.0
table: Rows read per second
DescriptionReturns the rate (per second) at which rows were read from the table during the monitoringinterval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner nameSpecifies the owner of the table.
Table nameSpecifies the name of the table.
CLI SynopsistableRowsRead
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Owner_name>Specifies the owner of the table.
<Table_name>Specifies the name of the table.
Exampleswaddmon 'DB2Manager_Table_Monitors' 'tableRowsRead'-a 'lovejoy'-a 'employees'"ManufacturingProfile"
Default Thresholds and ActionsNone
549Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
Usage NotesA high returned value indicates that there is heavy use of the table. Consider creatingadditional indexes for the table. To avoid the maintenance of unnecessary indexes, use theSQL EXPLAIN statement, described in the DB2 Administration Guide for the version ofDB2 that you are using, to determine if your packages use an index for the table.
This count includes the value returned by the table: Overflow accesses monitor.
See AlsoDB2Manager Table monitors: “table: Overflow accesses” on page 544
550 Version 2.1.0
table: Rows written per second
DescriptionReturns the rate (per second) at which rows were changed (inserted, deleted, or updated) inthe table during the monitoring interval.
Authorization Roleadmin
Target EndpointsDB2DatabaseManager and DB2PartitionManager
Desktop Data Entry FieldsThe following figure shows the Monitor Arguments area of the Add Monitor to TivoliDistributed Monitoring Profile dialog box.
Owner nameSpecifies the owner of the table.
Table nameSpecifies the name of the table.
CLI SynopsistableRowsWritten
-a <Owner_name>
-a <Table_name>
The following briefly describes the arguments for this monitor:
<Owner_name>Specifies the owner of the table.
<Table_name>Specifies the name of the table.
Exampleswaddmon 'DB2Manager_Table_Monitors' 'tableRowsWritten'-a 'lovejoy'-a 'employees'"ManufacturingProfile"
Default Thresholds and ActionsNone
551Tivoli Manager for DB2 Reference Guide
13.D
B2
Table
Mo
nito
rs
Usage NotesA high returned value indicates that there is heavy use of the table. Consider using the DB2Run Statistics (RUNSTATS) utility to maintain the efficiency of the packages used for thistable.
See AlsoNone
552 Version 2.1.0
About Task Libraries
The Tivoli Manager for DB2 task libraries are collections of predefined management tasks,such as backing up databases and running statistics. Running, scheduling, or automaticallyexecuting these predefined tasks helps ease overall management workload in a complexenvironment by carrying out actions against all subscribed task endpoints without the needto define the task for each endpoint separately.
The tasks are grouped into the following three libraries based on function:
¶ Monitor and Administration Tasks: Contains tasks used for monitoring andadministration.
¶ DB2 Database Tasks: Contains tasks used with DB2 and the database manager.
¶ Data Replication Tasks: Contains tasks used for data replication with IBM Replication.
Each task library contains a set of predefined DB2 tasks. A task is an operation or set ofoperations that is performed routinely.
This chapter includes the following information:
¶ Tasks listed by Desktop name and CLI name
¶ Task dialogs used by all tasks
¶ A description of each task in the task libraries
Running TasksThe tasks in the Tivoli Manager for DB2 product can be run from the Tivoli command line,from the Tivoli desktop, or from a Tivoli Manager for DB2 monitoring source.
See the Tivoli Manager for DB2 User’s Guide for information about running tasks from thedesktop, monitoring source, and command line.
For additional information about the wruntask command, see the Tivoli ManagementFramework Reference Manual.
14
553Tivoli Manager for DB2 Reference Guide
14.A
bo
ut
TaskL
ibraries
554 Version 2.1.0
Monitor and Administration Tasks
The DB2ManagerAdminTasks library contains tasks that are used for monitoring andadministration of DB2.
Table 58 lists the tasks and gives a brief description of what they do. The tasks are listedalphabetically.
Table 58. DB2ManagerAdmin TasksTask Description
ECC_Broadcast_Message Broadcasts a message to all Tivoli desktops
ECC_Configure_TEC_Classes Provides Tivoli Enterprise Console configuration options.
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_DB2SNMP_Agent Starts a DB2 SNMP daemon to run any SNMP monitors
ECC_Start_Monitoring_Agent Starts the monitoring agent to run DB2 monitors
ECC_Stop_DB2SNMP_Agent Stops a DB2 SNMP daemon
ECC_Stop_Monitoring_Agent Stops the ECC monitoring agent
Running TasksThis document provides the necessary arguments you need in order to run the TivoliManager for DB2 tasks using one or more of the following methods:
¶ From the Tivoli desktop using the Configure Task Arguments dialog box
¶ From a Tivoli Manager for DB2 monitor using the wdb2tlib command
Note: You must enter the fully qualified path of the executable for this command to runproperly. Refer to the Tivoli Manager for DB2 User’s Guide for moreinformation.
¶ From the Tivoli command line using the wruntask command
For step-by-step information about running tasks using these methods, see the TivoliManager for DB2 User’s Guide.
15
555Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Broadcast_Message
DescriptionThis task reads the input data and broadcasts the message text to all desktops in the TivoliManager for DB2 product installation.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Message to sendSpecifies the message that will be broadcasted.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Broadcast_Message"<message>"
"<message>"Specifies the message that you want to broadcast. The message must be enclosedin quotation marks.
Examples¶ Using the wruntask command:
wruntask-t ECC_Broadcast_Message-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a "Backing up databases now."
556 Version 2.1.0
Usage NotesSelect only one endpoint in your management region. If you select multiple endpoints, themessage is sent multiple times. For example, if you select three endpoints, the message issent to all endpoints in the management region three times.
For more information, see the wbroadcast command in the Tivoli Management FrameworkReference Manual.
See AlsoNone
557Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Configure_TEC_Classes
DescriptionProvides Tivoli Enterprise Console (TEC) configuration options. You can configure theTivoli Enterprise Console to receive events from the following:
¶ Distributed monitors
¶ Tasks
The ECC_Configure_TEC_Classes task adds the class and rule set definitions of theselected configuration option to a valid rule base when the class and rule set definitions arenot already defined in the specified rule base. For more information, see the Tivoli Managerfor DB2 User’s Guide. Before you run this task, the following software must be installed:
¶ Tivoli Enterprise Console Event Server
¶ Tivoli Manager for DB2 on the Tivoli management region server where you want to runthis task
The ECC_Configure_TEC_Classes task does the following, depending on the options youchoose:
¶ Creates a rule base in the directory where TEC is installed.
¶ Provides Tivoli Enterprise Console configuration for the specified options. It adds classand rule set definitions to a valid rule base for the options, if they are not alreadydefined in the specified rule base.
¶ Copies a specified rule base into the newly created rule base.
¶ Creates event groups. (This option is not available for Tivoli Enterprise Console, Version3.7.)
¶ Loads the rule base.
¶ Restarts the event server.
Authorization Rolesenior and super (must have both roles)
Target EndpointsTivoli event servers (managed nodes)
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
558 Version 2.1.0
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, Version 3.7. Forinformation on creating event groups for that version, refer to the TivoliEnterprise Console, Version 3.7, User’s Guide.
Restart Event ServerSpecifying the Y option restarts the Event Server, and specifying the N option doesnot restart the event Server.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Configure_TEC_Classes-a <rulebasename>[-a <rulebasetocopy>][-a <eventgroupname>][-a {Y | N}]
where:
<rulebasename>Specifies the name for the rule base.
<rulebasetocopy>Specifies the name of the rule base to copy. This is usually "default" whengiven the default Tivoli rule base.
<eventgroupname>Specifies the name of the event group that you are creating.
559Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
Note: This option is not available for Tivoli Enterprise Console, Version 3.7.For information on creating event groups for that version, refer to theTivoli Enterprise Console, Version 3.7, User’s Guide.
<restart_event_server>Y restarts the server. N does not restart the server.
Examples¶ Using the wruntask command:
wruntask-t ECC_Configure_TEC_Classes-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@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
560 Version 2.1.0
ECC_Reset_Counters
DescriptionResets the ECC counters for a DB2 instance.
Authorization Roledb2_dba
Target EndpointsDB2InstanceManager and DB2PartitionManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
Not available for this task.
ExamplesNone
Usage NotesUse this task to force counters to reset that are normally only reset when an application orthe database manager is started.
See AlsoNone
561Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Send_Notice
DescriptionSends a notice to the notification server.
Authorization Rolesuper and senior
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
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 to be sent.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Send_Notice-a "<ngroup>"[-a {Critical|Error|Warning|Notice|Debug}][-a <notice>]where:
"<ngroup>"Specifies the notice group. Requires quotation marks around the name.
562 Version 2.1.0
<priority>Specifies one of the following priorities for the notification: Critical, Error,Warning, Notice, or Debug.
<notice>Specifies the notice you want sent.
Examples¶ Using the wruntask command:
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 the notificationserver. You can specify that the message be sent to any notice group. For more information,refer to the wsndnotif command in the Tivoli Management Framework Reference Manual.
See AlsoNone
563Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Set_Up_Monitoring_Agent
DescriptionSets up the monitoring agent.
Authorization Rolesenior and super
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
ActionSelect the action to occur from the drop-down list. The actions are shown as:
Add and startAdds and starts a monitoring agent. Adds an inittab entry for UNIX orinstalls the monitoring service for Windows.
Add without startingAdds a monitoring agent. Adds an inittab entry for UNIX or installs themonitoring service for Windows.
Remove and stopRemoves and stops a monitoring agent. Removes the inittab entry for UNIX.This option does not remove the desktop icon on OS/2 systems.
Remove without stoppingRemoves a monitoring agent. Removes the inittab entry for UNIX or themonitoring service for Windows. This option does not remove the desktopicon on OS/2 systems.
Password(For Windows only) Specifies the password to be used when adding the monitoringservice.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
564 Version 2.1.0
CLI Synopsis¶ Using the wruntask command:
ECC_Set_Up_Monitoring_Agent-a <action>-a <password>where:
<action>Specifies one of the following actions:
AddStartAdds and starts a monitoring agent. Adds an inittab entry for UNIX orinstalls the monitoring service for Windows.
AddNoStartAdd an inittab entry for UNIX or install the monitoring service forWindows.
RemoveStopRemoves and stops a monitoring agent. Removes the inittab entry forUNIX. This option does not remove the desktop icon on OS/2 systems.
RemoveNoStopRemoves a monitoring agent. Removes the inittab entry for UNIX or themonitoring service for Windows. This option does not remove thedesktop icon on OS/2 systems.
<password>(For Windows and OS/2 only) Specifies the password to be used when addingthe monitoring service.
Examples¶ Using the wruntask command:
wruntask-t ECC_Set_Up_Monitoring_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a AddStart-a paswrd
Usage NotesNone
See AlsoDB2Manager Basic monitors: “DB2 ECC monitoring communication agent status” onpage 38
565Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Start_DB2SNMP_Agent
DescriptionStarts a DB2 Simple Network Management Protocol (SNMP) daemon to run any SNMPmonitors. This task does not run on Solaris.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Host NameSpecifies the name of the host on which to start SNMP. This argument must bespecified if this task runs on a Windows server.
Community NameSpecifies the community name group for a set of SNMP agents that are managedtogether. This argument must be specified if this task runs on a Windows server.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Start_DB2SNMP_Agent<hostname><community_name>where:
<hostname>Specifies the name of the host on which to start the SNMP agent. This argumentmust be specified if this task runs on a Windows server.
<community_name>Specifies the community name group for a set of SNMP agents that are managedtogether. This argument must be specified if this task runs on a Windows server.
566 Version 2.1.0
CLI Synopsis¶ Using the wruntask command:
ECC_Start_DB2SNMP_Agent-a <hostname>-a <community_name>where:
<hostname>Specifies the name of the host on which SNMP to start. This argument must bespecified if this task runs on a Windows server.
<community_name>Specifies the community name. The community name group a set of SNMPagents that are managed together. This argument must be specified if this taskruns on a Windows server.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Start_DB2SNMP_Agent bburns public
¶ Using the wruntask command:wruntask-t ECC_Start_DB2SNMP_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns-a bburns-a public
Usage NotesThis task runs on AIX and Windows platforms. Do not run this task on a managed node.
See AlsoDB2Manager SNMP monitors: All
567Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Start_Monitoring_Agent
DescriptionStarts the monitoring agent to run DB2 monitors.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Start_Monitoring_Agent
CLI Synopsis¶ Using the wruntask command:
ECC_Start_Monitoring_Agent
Examples¶ Using the wdb2tlib command on Windows
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Start_Monitoring_Agent
¶ Using the wruntask command:wruntask-t ECC_Start_Monitoring_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns
Default Thresholds and ActionsNone
Usage NotesNone
See AlsoDB2Manager Basic monitors: “DB2 ECC monitoring communication agent status” onpage 38
568 Version 2.1.0
ECC_Stop_DB2SNMP_Agent
DescriptionStops the DB2 Simple Network Management Protocol (SNMP) daemon.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Stop_DB2SNMP_Agent
CLI Synopsis¶ Using the wruntask command:
ECC_Stop_DB2SNMP_Agent
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Stop_DB2SNMP_Agent
¶ Using the wruntask command:wruntask-t ECC_Stop_DB2SNMP_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesNone
See AlsoDB2Manager SNMP monitors: All
569Tivoli Manager for DB2 Reference Guide
15.M
on
itor
and
Ad
min
istration
Tasks
ECC_Stop_Monitoring_Agent
DescriptionStops the monitoring agent.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Stop_Monitoring_Agent
CLI Synopsis¶ Using the wruntask command:
ECC_Stop_Monitoring_Agent
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Stop_Monitoring_Agent
¶ Using the wruntask command:wruntask-t ECC_Stop_Monitoring_Agent-l DB2ManagerAdminTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesNone
See AlsoDB2Manager Basic monitors: “DB2 ECC monitoring communication agent status” onpage 38
570 Version 2.1.0
DB2 Database Tasks
The DB2ManagerDatabaseTasks library contains tasks that provide basic administrationfunctions for DB2 and the database manager.
For more information about these tasks, see the following manuals for the version of DB2that you are using:
¶ DB2 API Reference
¶ DB2 Command Reference
¶ DB2 SQL Reference
Table 59 lists the tasks and gives a brief description of what they do. The tasks are listedalphabetically.
Table 59. DB2ManagerDatabaseTasksTask Description
ECC_Activate_Database Activate a database
ECC_Alter_Bufferpool Modify the size of the buffer pool
ECC_Backup_Database Create a backup of a DB2 database
ECC_Create_Admin_Server Create the DB2 administration server
ECC_Create_Explain_Tables Create explain tables
ECC_Create_Sample_Database Create a DB2 sample database
ECC_Deactivate_Database Deactivate the database
ECC_Drop_Admin_Server Delete the DB2 administration server instance
ECC_Drop_Sample_Database Drop the DB2 sample database
ECC_Force_All_Applications Force all DB2 applications off the system
ECC_Force_Application Force specific DB2 applications off the system
ECC_Get_Admin_Configuration Get the DB2 administration configuration
ECC_Get_Admin_Server_Instance Get the DB2 administration configuration serverinstance name
ECC_Get_Database_Configuration Return the values of individual entries in thedatabase configuration file
ECC_Get_Database_Manager_Configuration Return the values of individual entries in thedatabase manager configuration file
ECC_Invoke_Stored_Procedure Invoke a CB2 stored procedure
ECC_List_Applications List the DB2 applications
ECC_List_Backup_Recovery_File List the DB2 backup and recovery history file
16
571Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
Table 59. DB2ManagerDatabaseTasks (continued)Task Description
ECC_List_DCS_Applications List the DB2 DCS applications
ECC_List_Node_Directory List the contents of the node directory
ECC_Prune_Recovery_History_File Prune the DB2 recovery history file
ECC_Quiesce_Tablespaces Quiesce DB2 tablespaces
ECC_Rebind_All_Packages Rebind all DB2 packages
ECC_Rebind_Package Rebind a specific DB2 package
ECC_Reorganize_Table Reorganize a DB2 table
ECC_Reorgchk Run the DB2 REORGCHK command
ECC_Reset_Admin_Configuration Reset the parameters in the database managerconfiguration file, relevant to the DB2administration server, to the system defaults
ECC_Reset_Database_Configuration Reset the configuration of a specific database to thesystem defaults.
ECC_Reset_Database_Manager_Configuration Reset the parameters in the database managerconfiguration file to the system defaults.
ECC_Restart_Database Restart a DB2 database
ECC_Run_Statistics Run DB2 statistics
ECC_Set_Admin_Server_ID Establish or modify the user account associated withthe DB2 administration server instance
ECC_Start_Admin_Server Start the DB2 administration server
ECC_Start_DB2 Start DB2
ECC_Start_DB2_NT_Security Start the DB2 security service on a Windows system
ECC_Stop_Admin_Server Stop the DB2 administration server
ECC_Stop_DB2 Stop DB2
ECC_Stop_DB2_NT_Security Stop the DB2 security service on a Windows system
ECC_Update_Admin_Configuration Modify individual entries in the database managerconfiguration files that are relevant to the DB2administration server
ECC_Update_Database_Configuration Update the DB2 database configuration
ECC_Update_Database_Manager_Configuration Update the DB2 database manager configuration
Running TasksThis document provides the necessary arguments you need in order to run the TivoliManager for DB2 tasks using one or more of the following methods:
¶ From the Tivoli desktop using the Configure Task Arguments dialog box
¶ From a Tivoli Manager for DB2 monitor using the wdb2tlib command
Note: You must enter the fully qualified path of the executable for this command to runproperly. Refer to the Tivoli Manager for DB2 User’s Guide for moreinformation.
¶ From the Tivoli command line using the wruntask command
572 Version 2.1.0
For step-by-step information about running tasks using these methods, see the TivoliManager for DB2 User’s Guide.
573Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Activate_Database
DescriptionActivates the selected database on an endpoint and starts all necessary database services sothat the database is available for connection and use by any application.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User NameSpecifies the name of the user starting the database. This variable is optional, but itis required if you specify a password.
PasswordSpecifies the password for the username. This variable is optional, but it is requiredif you specify a user name.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Activate_Database[<username><password>]where:
<username>Specifies the name of the user starting the database. This variable is optional,but it is required if you specify a password.
<password>Specifies the password for the <username>. This variable is optional, but it isrequired if you specify a user name.
574 Version 2.1.0
CLI Synopsis¶ Using the wruntask command:
ECC_Activate_Database[-a <username>-a <password>]where:
<username>Specifies the name of the user starting the database. This variable is optional,but it is required if you specify a password.
<password>Specifies the password for the <username>. This variable is optional, but it isrequired if you specify a user name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Activate_Database joe joepw
¶ Using the wruntask command:wruntask-t ECC_Activate_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it activates the specifieddatabase on all nodes within the system.
If a database has not been started and a CONNECT TO command is encountered in anapplication, the application must wait while the database manager starts the requireddatabase. However, after the database is started, other applications can connect and use itwithout starting it up.
If you initialize a databases by using ECC_Activate_Database, you can shut it down onlyby running a deactivate database command (such as ECC_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 AlsoDB2Manager-Database tasks: “ECC_Deactivate_Database” on page 593
575Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Alter_Bufferpool
DescriptionModifies the buffer pool size for a single node or all nodes, turns the use of extendedstorage on or off, and adds the buffer pool definition to a new node group.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
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 buffer pool size.For more information, see the CREATE BUFFERPOOL command in theDB2 Command Reference.
Alter size for selected nodes (Value: number of pages)Alters the size of the buffer pool for the DB2 node represented by theendpoint 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:
576 Version 2.1.0
(Action: Alter size for all nodes or selected nodes)If you specify this action, enter the size of the buffer pool specified as thenumber of pages. If you specify -1, the buffer pool size is taken from theBUFFPAGE database configuration parameter.
(Action: Set extended storage)If you specify this action, enter one of the following parameters:
YES If the extended storage configuration is turned on, pages that aremigrating out of this buffer pool will be cached in the extendedstorage.
NO Even if the extended storage configuration is turned on, pages thatare migrating out of this buffer pool will not be cached in theextended storage.
(Action: Add nodegroup)If you specified this action, enter the node group name where this bufferpool definition will be added. The node group name is added to all nodes inthe specified node group if the node group name does not exist. If the bufferpool is defined on a node, no action is taken.
User IDSpecifies the name of the user to attach to a remote partition. This argument is onlynecessary when you drop this task on a partition group endpoint, and at least one ofthe partitions in the partition group is on a remote host. The user name is used forall nodes included in the partition group whether they are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID variable.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Alter_Bufferpool<name><action><value>[<username><password>]where:
<name>Specifies the name of the buffer pool to be altered.
<action>Specifies one of the following arguments:
ALL Alters the buffer pool size on all nodes that use the default buffer poolsize. For more information, see the CREATE BUFFERPOOLcommand in the DB2 Command Reference.
NODEAlters the size of the buffer pool for the DB2 node represented by theendpoint you selected.
SET Sets the extended storage action.
577Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
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, enter the size ofthe buffer pool (specified as the number of pages). If you specify -1, thebuffer pool size is taken from the BUFFPAGE database configurationparameter.
cache If you specify SET for the action variable, specify one of the followingparameters:
YES If the extended storage configuration is turned on, pages that aremigrating out of this buffer pool will be cached in the extendedstorage.
NO Even if the extended storage configuration is turned on, pagesthat are migrating out of this buffer pool will not be cached inthe extended storage.
ng_nameIf you specified ADD for the action variable, specify the node groupname this buffer pool definition will be added to. The node group nameis added to all nodes in the specified node group if it currently does notexist. If the buffer pool is defined on a node, no action is taken.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_Alter_Bufferpool-a <name>-a <action>-a <value>[-a <username>-a <password>]where:
<name>Specifies the name of the buffer pool to be altered.
<action>Specifies one of the following arguments:
ALL Alters the buffer pool size on all nodes that use the default buffer poolsize. For more information, see the CREATE BUFFERPOOLcommand in the DB2 Command Reference.
578 Version 2.1.0
NODEAlters the size of the buffer pool for the DB2 node represented by theendpoint 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 the size ofthe buffer pool (specified as the number of pages). If you specify -1, thebuffer pool size is taken from the BUFFPAGE database configurationparameter.
cache If you specified SET for the action variable, specify one of thefollowing parameters:
YES If the extended storage configuration is turned on, pages that aremigrating out of this buffer pool will be cached in the extendedstorage.
NO Even if the extended storage configuration is turned on, pagesthat are migrating out of this buffer pool will not be cached inthe extended storage.
ng_nameIf you specified ADD for the action variable, specify the node groupname this buffer pool definition will be added to. The node group nameis added to all nodes in the specified node group if it currently does notexist. If the buffer pool is defined on a node, no action is taken.
<username>Specifies the name of the user to attach to a remote partition. This argument isonly necessary when you drop this task on a partition group endpoint, and atleast one of the partitions in the partition group is on a remote host. The username is used for all nodes included in the partition group whether they are on alocal or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Alter_Bufferpool BUFF2 ALL 20 joe joepw
¶ Using the wruntask command:wruntask-t ECC_Alter_Bufferpool-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a buff2-a ALL-a 20-a joe-a joepw
579Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
Usage NotesFor more information, see the ALTER BUFFERPOOL statement in the DB2 SQLReference.
See AlsoNone
580 Version 2.1.0
ECC_Backup_Database
DescriptionCreates a backup copy of a database.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User NameSpecifies the name with which to back up the database. If you run this task withDB2 Enterprise-Extended Edition on a partition group endpoint and at least one ofthe partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
NONESpecifies that the current user name is used.
PasswordSpecifies the password for user name:
NONESpecifies that no password is supplied. Use NONE if the username isNONE.
581Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
OnlineEnter YES or NO to specify an online backup.
Use TSMEnter YES or NO to indicate whether to use Tivoli Storage Manager managedoutput (formerly ADSM) for the backup.
Number of TSM SessionsSpecifies the number of I/O sessions to be used with the Tivoli Storage Managermanaged output. The default value is 2.
If you are not using managed output, specify any number (it will be ignored).
Target AreaSpecifies a directory or tape device name to which the backup is written. If youspecify a directory, you must enter the full path on which the directory resides. Thedirectory must already exist. The default for UNIX hosts is the /tmp directory. Thereis no default for Windows hosts.
Number of BuffersSpecifies the number of buffers to use during the backup process. A typical value is1.
Buffer SizeSpecifies the number of pages for the buffer that is used when building the backupimage. The minimum size is 16 pages and the default is 1024.
ParallelismSpecifies the number of buffer manipulators to spawn during the restore process. Thedefault is 1. This variable is available only for DB2 Enterprise-Extended Edition.
Library NameSpecifies the name of the shared library that contains the vendor backup and restoreinput and output functions to be used. This variable can contain the full path and filename of the library. If the full path is not specified, the path defaults to where theuser exit program resides. This variable is optional.
TablespaceSpecifies one or more tablespaces to back up. If no tablespace is specified, alltablespaces are backed up. To specify more than one tablespace, separate them usingcommas.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Backup_Database<username><password><online><adsm><adsmnum><target><numbuf><bufsize>[<parallelism>
582 Version 2.1.0
<libname><tablespace>]where:
<username>Specifies the name with which to back up the database. If you run this task withDB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify auser name. The user name is used for all nodes included in the partition groupwhether they are on a local or remote host.
NONESpecifies that the current user name is used.
usernameSpecifies a specific user name.
<password>Specifies the password for <username>:
NONEpecifies that no password is supplied. Use NONE if the username isNONE.
passwordSpecifies the password used to authenticate the user name entered for<username>. This value is required if you specify a user name.
<online>Specifies YES or NO to indicate whether the backup is online.
<tsm> Specifies YES or NO to indicate whether to use Tivoli Storage Managermanaged output (formerly ADSM) for the backup.
<tsmnum>Specifies the number of I/O sessions to be used with the Tivoli Storage Managermanaged output. A typical value to use for tsmnum is 2.
If you are not using managed output, specify any number (it will be ignored).
<target>Specifies a directory or tape device name to which the backup is written. If youspecify a directory, you must enter the full path on which the directory resides.The directory must already exist.
<numbuf>Specifies the number of buffers to use during the backup process. A typicalvalue to use for numbuf is 1.
<bufsize>Specifies the number of pages for the buffer that is used when building thebackup image. The minimum size is 16 pages. A typical value to use for bufsizeis 1024 (1024 pages).
<parallelism>Specifies the number of buffer manipulators to spawn during the restore process.The default is 1. This variable is available only for DB2 Enterprise-ExtendedEdition.
583Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<libname>Specifies the name of the shared library that contains the vendor backup andrestore input and output functions to be used. The libname variable can containthe full path and file name of the library. If the full path is not specified, thepath defaults to where the user exit program resides. This variable is optional.
<tablespace>Specifies one or more tablespaces to back up. If no tablespace is specified, alltablespaces are backed up. To specify more than one tablespace, place the namesin double quotation marks separated by commas. For example,"tblspc01,tblspc02".
CLI Synopsis¶ Using the wruntask command:
ECC_Backup_Database-a <username>-a <password>-a <online>-a <adsm>-a <adsmnum>-a <target>-a <numbuf>-a <bufsize>[-a <parallelism>-a <libname>-a <tablespace>]
where:
<username>Specifies the name with which to back up the database. If you run this task withDB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify auser name. The user name is used for all nodes included in the partition groupwhether they are on a local or remote host.
NONESpecifies that the current user name is used.
usernameSpecifies a specific user name.
<password>Specifies the password for <username>:
NONESpecifies that no password is supplied. Use NONE if the <username> isNONE.
passwordSpecifies the password used to authenticate the user name entered for<username>. This value is required if you specify a user name.
<online>Specifies YES or NO to indicate whether the backup is online.
584 Version 2.1.0
<tsm> Specifies YES or NO to indicate whether to use Tivoli Storage Managermanaged output (formerly ADSM) for the backup.
<tsmnum>Specifies the number of I/O sessions to be used with the Tivoli Storage Managermanaged output. A typical value to use for tsmnum is 2.
If you are not using managed output, specify any number (it will be ignored).
<target>Specifies a directory or tape device name to which the backup is written. If youspecify a directory, you must enter the full path on which the directory resides.The directory must already exist.
<numbuf>Specifies the number of buffers to use during the backup process. A typicalvalue to use for numbuf is 1.
<bufsize>Specifies the number of pages for the buffer that is used when building thebackup image. The minimum size is 16 pages. A typical value to use for bufsizeis 1024 (1024 pages).
<parallelism>Specifies the number of buffer manipulators to generate during the restoreprocess. The default is 1. This variable is available only for DB2Enterprise-Extended Edition.
<libname>Specifies the name of the shared library that contains the vendor backup andrestore I/O functions to be used. The libname variable can contain the full pathand file name of the library. If the full path is not specified, the path defaults towhere the user exit program resides. This variable is optional.
<tablespace>Specifies one or more tablespaces to back up. If no tablespace is specified, alltablespaces are backed up. To specify more than one tablespace, place the namesin double quotation marks separated by commas. For example,"tblspc01,tblspc02".
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Backup_Database joe joepw \NO NO 0 /dev/rmt0 1 1024 1 NONE "tblspc01,tblspc02"
¶ Using the wruntask command:wruntask-t ECC_Backup_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw-a NO-a NO-a 0-a /dev/rmt0
585Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
-a 1-a 1024-a None-a "tblspc01,tblspc02"
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it backs up only the node onwhich it is executed.
Because this task may take longer to complete than the default time of 60 seconds, youshould set the timeout value to a larger value, like 600 seconds.
If a database becomes damaged or corrupted, it can be returned to the state of the backed upcopy. If a successfully restored database was enabled for roll-forward recovery at the time ofthe backup, it can be returned to the state that it was in prior to the occurrence of damage.The backup might be directed to hard disk, diskette, tape, Tivoli Storage Manager utility, orto other vendor products enabled for DB2.
For more information, see the BACKUP DATABASE CLP command in the DB2 CommandReference for the version of DB2 that you are using.
See AlsoNone
586 Version 2.1.0
ECC_Create_Admin_Server
DescriptionCreates the DB2 Administration Server on a Windows host.
Note: This task is not supported on OS/2 hosts.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User NameSpecifies the name with which to create a DB2 Administration Server.
PasswordSpecifies the password used to authenticate the user name.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Create_Admin_Server[-a <username>-a <password>]
where:
<username>Specifies the name with which to create a DB2 Administration Server.
587Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<password>Specifies the password used to authenticate the user name.
Examples¶ Using the wruntask command:
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 Server instance isassociated with this user account. The specified user account must be a valid SQL identifierand must exist in the security database.
For more information, see the db2admin system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
588 Version 2.1.0
ECC_Create_Explain_Tables
DescriptionCreates DB2 Explain tables in the specified database.
Note: This task is not supported on OS/2 endpoints if the Tivoli Management Frameworkand Tivoli Manager for DB2 are not installed on the same drive.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Create_Explain_Table
CLI Synopsis¶ Using the wruntask command:
ECC_Create_Explain_Table
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Create_Explain_Table
¶ Using the wruntask command:wruntask-t ECC_Create_Explain_Table-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage Notes
Note: This task is not supported on OS/2 endpoints if the Tivoli Management Frameworkand Tivoli Manager for DB2 are not installed on the same drive.
This task uses the EXPLAIN.DLL provided by DB2 to create the following explain tables:
¶ EXPLAIN_ARGUMENT
¶ EXPLAIN_INSTANCE
¶ EXPLAIN_OBJECT
¶ EXPLAIN_OPERATOR
¶ EXPLAIN_PREDICATE
¶ EXPLAIN_STATEMENT
¶ EXPLAIN_STREAM
589Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
For more information, see the DB2 SQL Reference for the version of DB2 that you areusing.
See AlsoNone
590 Version 2.1.0
ECC_Create_Sample_Database
DescriptionCreates a DB2 sample database named SAMPLE.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the path on which to create the SAMPLE database. On Windows or OS/2,the path is a single drive letter.
NONESpecifies that SAMPLE is created on the default database path.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Create_Sample_Database[-a <path>]
where:
<path>Specifies the path on which to create the SAMPLE database:
NONESpecifies that SAMPLE is created on the default database path.
path Specifies a path. On Windows, the path is a single drive letter.
591Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
Examples¶ Using the wruntask command:
wruntask-t ECC_Create_Sample_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a G
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes in the nodegroup.
You can run this task only on DB2 server nodes. The SAMPLE database cannot be createdon nodes that are database clients only. The database is created with the instanceauthentication type that is specified by the database manager configuration parameterauthentication. The user ID determines the qualifiers for the tables. If the SAMPLE databasealready exists, this task creates the tables for the user ID that issued the command and grantsthe appropriate privileges.
The default timeout is 60 seconds. If the task does not complete in this amount of time, thecompletion status is not displayed. The task will, however, continue to completion. To helpensure that the status displays, you can specify a longer timeout period.
For more information, see the db2sampl system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
592 Version 2.1.0
ECC_Deactivate_Database
DescriptionStops the database that you specify.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User NameSpecifies the name of the user stopping the database. This variable is optional, but itis required if you specify the password variable.
PasswordSpecifies the password for the user name. This variable is optional, but it is requiredif you specify the <username> variable.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Deactivate_Database[<username><password>]
where:
<username>Specifies the name of the user stopping the database. This variable is optional,but it is required if you specify the password variable.
<password>Specifies the password for the user name. This variable is optional, but it isrequired if you specify the <username> variable.
593Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
CLI Synopsis¶ Using the wruntask command:
ECC_Deactivate_Database[-a <username>-a <password>]
where:
<username>Specifies the name of the user stopping the database. This variable is optional,but it is required if you specify the password variable.
<password>Specifies the password for the user name. This variable is optional, but it isrequired if you specify the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Deactivate_Database joe joepw
¶ Using the wruntask command:wruntask-t ECC_Deactivate_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it deactivates the specifieddatabase 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 database command(such as this one). If you initialize a database with an activate database command, the lastapplication that disconnects from the database will not shut down the database.
For more information, see the DEACTIVATE DATABASE CLP command in the DB2Command Reference for the version of DB2 that you are using.
See AlsoDB2Manager-Database tasks: “ECC_Activate_Database” on page 574
594 Version 2.1.0
ECC_Drop_Admin_Server
DescriptionDeletes the DB2 Administration Server instance on a Windows host.
DB2 Version SupportedThis task only runs on DB2 Universal Database Enterprise Edition. This task is notsupported on OS/2.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Drop_Admin_Server
Examples¶ Using the wruntask command:
wruntask-t ECC_Drop_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesFor more information, see the db2admin system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
595Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Drop_Sample_Database
DescriptionDeletes the contents and all log files of the SAMPLE database, uncatalogs the database, anddeletes the database subdirectory.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Drop_Sample_Database
Examples¶ Using the wruntask command:
wruntask-t ECC_Drop_Sample_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes that are listedin the db2nodes.cfg file.
The SAMPLE database must not be in use when this task is run; you must disconnect allusers before the database can be dropped. The SAMPLE database must be cataloged in thesystem database directory. If the SAMPLE database is the only entry in the local databasedirectory, the local database directory is deleted automatically.
For more information, see the DROP DATABASE CLP command in the DB2 CommandReference for the version of DB2 that you are using.
See AlsoNone
596 Version 2.1.0
ECC_Force_All_Applications
DescriptionForces local or remote users or applications off a DB2 instance to allow for maintenance ona server.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Force_All_Applications
CLI Synopsis¶ Using the wruntask command:
ECC_Force_All_Applications
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Force_All_Applications
¶ Using the wruntask command:wruntask-t ECC_Force_All_Applications-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes that are listedin the $HOME/sqllib/db2nodes.cfg file.
Forcing a user off a DB2 instance results in the loss of that user’s connections to alldatabases. To preserve database integrity, you can terminate only those users who are idlingor running interruptible database operations. Users who are creating a database cannot beforced.
If an operation that cannot be interrupted is forced, the operation must be successfully rerunbefore the database becomes available. ECC_Stop_DB2 cannot be run during a force. Thedatabase manager remains active so that subsequent database manager operations can behandled without the need to run ECC_Start_DB2.
After a FORCE command is issued, the database stops accepting requests. Additional forcecommands might be required to completely force all users off.
597Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
For more information, see the sqlefrce system command in the DB2 API Reference for theversion of DB2 that you are using.
See AlsoDB2Manager-Database tasks: “ECC_Start_DB2” on page 659, “ECC_Stop_DB2” onpage 666
598 Version 2.1.0
ECC_Force_Application
DescriptionForces specific local or remote DB2 applications and users off the system to allow formaintenance on a server.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Application 1...Application 10Specifies one to ten application IDs if you are running DB2 UDB or one to tenapplication handles if you are running DB2 Enterprise-Extended Edition.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Force_Application<application01>[<application02>...<application10>]where:
599Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<application>Specifies one to ten application IDs if you are running DB2 UDB or one to tenapplication handles if you are running or DB2 Enterprise-Extended Edition. Forexample, you might specify 41408.
You can use the ECC_List_Applications task to find the application IDs orapplication handles of currently running applications. You must specify at leastone application ID or application handle.
CLI Synopsis¶ Using the wruntask command:
ECC_Force_Application-a <application01>[-a <application02>-a <application03>-a <application04>-a <application05>-a <application06>-a <application07>-a <application08>-a <application09>-a <application10>]
where:
<application>Specifies one to ten application IDs if you are running DB2 UDB or one to tenapplication handles if you are running or DB2 Enterprise-Extended Edition. Forexample, you might specify 41408.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Force_Application 41408 42623
¶ Using the wruntask command:wruntask-t ECC_Force_Application-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a 41408-a 42623
Usage NotesYou can use the ECC_List_Applications task to find the application IDs or applicationhandles of currently running applications. You must specify at least one application ID orapplication handle.
When this task is run on DB2 Enterprise-Extended Edition, it affects all nodes that are listedin the $HOME/sqllib/db2nodes.cfg file.
Forcing a user off a DB2 instance results in the loss of that user’s connections to alldatabases. To preserve database integrity, only users who are idling or running interruptibledatabase operations can be terminated. Users creating a database cannot be forced.
600 Version 2.1.0
If an operation that cannot be interrupted is forced, the operation must be successfully rerunbefore the database becomes available. ECC_Stop_DB2 cannot be run during a force. Thedatabase manager remains active so that subsequent database manager operations can behandled without the need to run ECC_Start_DB2.
After a FORCE command is issued, the database stops accepting requests to connect.Additional force commands might be 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 AlsoDB2Manager-Database tasks: “ECC_Start_DB2” on page 659, “ECC_Stop_DB2” onpage 666
601Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Get_Admin_Configuration
DescriptionGets the DB2 administration configuration.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Get_Admin_Configuration
CLI Synopsis¶ Using the wruntask command:
ECC_Get_Admin_Configuration
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Get_Admin_Configuration
¶ Using the wruntask command:wruntask-t ECC_Get_Admin_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesThe DB2 Administration Server is a special instance that enables remote administration ofDB2 servers. For DB2 Enterprise-Extended Edition, this command returns information aboutall nodes that share the same $HOME/sqllib directory, and it can be issued from any ofthese nodes.
For more information, see the GET ADMIN CONFIGURATION CLP command in theDB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
602 Version 2.1.0
ECC_Get_Admin_Server_Instance
DescriptionGets the DB2 Administration Server instance name.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Get_Admin_Server_Instance
CLI Synopsis¶ Using the wruntask command:
ECC_Get_Admin_Server_Instance
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Get_Admin_Server_Instance
¶ Using the wruntask command:wruntask-t ECC_Get_Admin_Server_Instance-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesFor more information, see the db2admin system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
603Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Get_Database_Configuration
DescriptionReturns the values of individual entries in the database configuration file.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Key 1...Key 5Click the Parameter button to select the name of the database configurationparameter that you want to retrieve. You can specify up to five keys. If no keys arespecified, all database configuration parameter values are returned. If one or morekeys are specified, only the values for those keys are returned.
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID. For OS/2 ONLY: Enter thepassword for the selected parameter to log in to the User Password Manager.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
604 Version 2.1.0
wdb2tlib ECC_Get_Database_Configuration[<key01>...<key05>[<username><password>]]where:
<key> Specifies the name of the database configuration parameter that you want toretrieve. You can specify up to five keys. This argument is optional. If no keysare specified, all database configuration parameter values are returned.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_Get_Database_Configuration[-a <key01>-a <key02>-a <key03>-a <key04>-a <key05>[-a <username>-a <password>]]
where:
<key> Specifies the name of the database configuration parameter that you want toretrieve. This argument is optional. You can specify up to five keys. If no keysare specified, all database configuration parameter values are returned.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Get_Database_Configuration APPLHEAPSZ
¶ Using the wruntask command:
605Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
wruntask-t ECC_Get_Database_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a APPLHEAPSZ
Usage NotesWhen this command is run on DB2 Enterprise-Extended Edition, it returns information aboutthe node on which it is executed.
If no keys are specified, all database configuration parameter values are returned. If one ormore keys are specified, only the values for the specified parameters are returned.
For more information, see the GET DATABASE CONFIGURATION CLP command in theDB2 Command Reference for the version of DB2 that you are using and the sqlfxdbcommand in the DB2 API Reference for the version of DB2 that you are using.
See AlsoNone
606 Version 2.1.0
ECC_Get_Database_Manager_Configuration
DescriptionReturns the values of individual entries in the database manager configuration file.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Key 1...Key 5Click the Parameter button to select the name of the database managerconfiguration parameter that you want to retrieve. You can specify up to five keys. Ifno keys are specified, all database configuration parameter values are returned. Ifone or more keys are specified, only the values for those keys are returned.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Get_Database_Manager_Configuration[<key01>...<key05>]where:
<key> Specifies the name of the database manager configuration parameter that youwant to retrieve. You can specify up to five keys. This argument is optional.
CLI Synopsis¶ Using the wruntask command:
607Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Get_Database_Manager_Configuration[-a <key01>-a <key02>-a <key03>-a <key04>-a <key05>]where:
<key> Specifies the name of the database manager configuration parameter that youwant to retrieve. You can specify up to five keys. This argument is optional.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Get_Database_Manager_Configuration \KEEPDARI MAXDARI
¶ Using the wruntask command:wruntask-t ECC_Get_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a KEEPDARI-a MAXDARI
Usage NotesIf no keys are specified, all database manager configuration parameter values are returned. Ifone or more keys are specified, only the values for the specified parameters are returned.
For more information, see the GET DATABASE MANAGER CONFIGURATION CLPcommand in the DB2 Command Reference for the version of DB2 that you are using and thesqlfxsys command in the DB2 API Reference for the version of DB2 that you are using.
See AlsoNone
608 Version 2.1.0
ECC_Invoke_Stored_Procedure
DescriptionInvokes a specified procedure that you created using DB2, which is stored at the location ofthe database.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
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 of data withcommas.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Invoke_Stored_Procedure<name>["<data>"]where:
<name>Specifies the name of the procedure.
"<data>"Specifies any data to pass to the server routine. Quotation marks are required ifyou specify more than one piece of data. This variable is optional.
CLI Synopsis¶ Using the wruntask command:
609Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Invoke_Stored_Procedure-a <name>[-a "<data>"]
where:
<name>Specifies the name of the procedure.
"<data>"Specifies any data to pass to the server routine. Quotation marks are required ifyou specify more than one piece of data. This variable is optional.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Invoke_Stored_Procedure \proc1 "dob,address"
¶ Using the wruntask command:wruntask-t ECC_Invoke_Stored_Procedure-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a proc1-a "dob,address"
Usage NotesThe server procedure runs at the location of the database and returns data to the clientapplication.
The program runs in two parts, one on the client and the other on the server. The serverprocedure at the database runs within the same transaction as the client application. If theclient application and the server procedure are on the same node, the server procedure is runlocally.
For more information, see the INVOKE STORED PROCEDURE CLP command in theDB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
610 Version 2.1.0
ECC_List_Applications
DescriptionLists the application program name, authorization ID (user name), agent ID, application ID,and database name.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Show Detail?Select Yes to show details. The default is No.
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate with User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_List_Applications[<detail><username><password>]where:
611Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<detail>Specifies YES to show details. The default is NO.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_List_Applications[-a <detail>-a <username>-a <password>]
where:
<detail>Specifies YES to show details. The default is NO.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_List_Applications YES joe joepw
¶ Using the wruntask command: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 this task is run ona DB2 database endpoint, only the applications for the database are listed.
When this task is run on DB2 Enterprise-Extended Edition, this task lists only thoseapplications that are on the selected node.
612 Version 2.1.0
For more information, see the LIST APPLICATIONS CLP command in the DB2 CommandReference for the version of DB2 that you are using.
See AlsoNone
613Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_List_Backup_Recovery_File
DescriptionLists a DB2 backup and recovery file.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
List TypeSelect the type of list request from the following options:
All Lists all entries in the recovery history file. This option is the default.
Since Lists entries based on the time stamp specified in the Time stamp text box.
ContainingLists the table or tablespace specified in the Name text box.
Time StampSpecifies a complete time stamp (yyyymmddhhnnss) or an initial prefix time stampwhere the minimum is yyyy. If you selected All or Containing in the Typedrop-down list, Time stamp is ignored.
Schema NameSpecifies a schema name to use as a qualifier for a table name. Specifies None touniquely identify a tablespace with the name variable. If you specify the All orSince parameters in the type variable, this variable is ignored. This field is optional.
Object NameIf you entered a schema name, enter a table name to use. The table is identified by‘schema.name’. If you entered None for the schema name, specify the unique
614 Version 2.1.0
identifier for a tablespace. If you entered All or Since in the Type text box, thisvariable is ignored. For more information, see the DB2 SQL Reference for theversion of DB2 that you are using.
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_List_Backup_Recovery_File[<type>[<timestamp>[<schema><name><username>[<password>]]]]
where:
<type>Specifies the type of list request. This variable is optional.
ALL Lists all entries in the recovery history file. This parameter is the default.
SINCELists entries based on the time stamp specified in the time stampvariable.
CONTAININGLists the table or tablespace specified in the name variable.
<timestamp>Specifies a complete time stamp (yyyymmddhhnnss) or an initial prefix timestamp where the minimum is yyyy. If you specify the ALL or CONTAININGparameters in the type variable, this variable is ignored. This variable is optional.
<schema>Specifies a schema name to use as a qualifier for a table name. Specifies NONEto uniquely identify a tablespace with the name variable. If you specify the ALLor SINCE parameters in the type variable, this variable is ignored. This variableis optional.
<name>If you specified a schema name, specify the table name to use. The table isidentified by ‘schema.name’. If you specified NONE for the schema variable,specify the unique identifier for a tablespace. If you specify the ALL or SINCEparameters in the type variable, this variable is ignored. For more information,see the DB2 SQL Reference for the version of DB2 that you are using.
615Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_List_Backup_Recovery_File[-a <type>[-a <timestamp>[-a <schema>]-a <name>-a <username>[-a <password>]
where:
<type>Specifies the type of list request. This variable is optional.
ALL Lists all entries in the recovery history file. This parameter is the default.
SINCELists entries based on the time stamp specified in the time stampvariable.
CONTAININGLists the table or tablespace specified in the name variable.
<timestamp>Specifies a complete time stamp (yyyymmddhhnnss) or an initial prefix timestamp where the minimum is yyyy. If you specify the ALL or CONTAININGparameters in the type variable, this variable is ignored. This variable is optional.
<schema>Specifies a schema name to use as a qualifier for a table name. Specifies NONEto uniquely identify a tablespace with the name variable. If you specify the ALLor SINCE parameters in the type variable, this variable is ignored. This variableis optional.
<name>If you specified a schema name, specify the table name to use. The table isidentified by ‘schema.name’. If you specified NONE for the schema variable,specify the unique identifier for a tablespace. If you specify the ALL or SINCEparameters in the type variable, this variable is ignored. For more information,see the DB2 SQL Reference for the version of DB2 that you are using.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and at
616 Version 2.1.0
least one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_List_Backup_Recovery_File \SINCE 1998 NONE NONE joe joepw
¶ Using the wruntask command:wruntask-t ECC_List_Backup_Recovery_File-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@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
617Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_List_DCS_Applications
DescriptionLists the contents of the Database Connection Services (DCS) directory.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Show Detail?Select Yes to include detailed information in the output or No to exclude detailedinformation.
The detailed information includes:
¶ 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, basic information is returned and includes:
¶ Host authorization ID (username)
¶ Application program name
¶ Agent ID
618 Version 2.1.0
¶ Outbound application ID (luwid)
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID variable.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_List_DCS_Applications<show_detail>[<username><password>]
where:
<show_detail>Specifies YES or NO to indicate if the output should include detailedinformation.
If you specify YES, basic and detailed information is returned. This includes:
v Application ID
v Application sequence number
v Client database alias
v Client product ID
v Code page ID
v Outbound sequence number
v Host database name
v Host product ID
If you specify NO, basic information is returned. This includes:
v Host authorization ID (username)
v Application program name
v Agent ID
v Outbound application ID (luwid)
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
619Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_List_DCS_Applications-a <show_detail>[-a <username>-a <password>]
where:
<show_detail>Specifies YES or NO to indicate if the output should include detailedinformation.
If you specify YES, then basic and detailed information is returned and includes:
v Application ID
v Application sequence number
v Client database alias
v Client product ID
v Code page ID
v Outbound sequence number
v Host database name
v Host product ID
If you specify NO, basic information is returned. This includes:
v Host authorization ID (username)
v Application program name
v Agent ID
v Outbound application ID (luwid)
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_List_DCS_Applications YES joe joepw
¶ Using the wruntask command:
620 Version 2.1.0
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 ID information toforce 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
621Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_List_Node_Directory
DescriptionLists the contents of the node directory.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Admin nodesSelect Yes to list the contents of the Administration Server nodes. The default is No.
Show DetailSelect Yes to include detailed information about the node directory. The default isNo.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_List_Node_Directory[<admin>[<detail>]]
where:
<admin>Specifies YES to select Administration Server nodes. The default is NO. Thisargument is optional.
<detail>Specifies YES to show details. The default is NO. This argument is optional.
622 Version 2.1.0
CLI Synopsis¶ Using the wruntask command:
ECC_List_Node_Directory[-a <admin>[-a <detail>]]
where:
<admin>Specifies YES to select Administration Server nodes. The default is NO. Thisargument is optional.
<detail>Specifies YES to show details. The default is NO. This argument is optional.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_List_Node_Directory YES NO
¶ Using the wruntask command:wruntask-t ECC_List_Node_Directory-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a YES-a NO
Usage NotesA node directory is created and maintained on each database client and contains an entry foreach remote workstation that has a database that the client can access. This task identifies arange of entries in the recovery history files that are deleted. All entries with time stampsequal to or less than the time stamp provided are deleted. Entries can be pruned even ifsome entries from the most recent restore set are deleted from the file.
For more information, see the LIST NODE DIRECTORY CLP command in the DB2Command Reference for the version of DB2 that you are using.
See AlsoNone
623Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Prune_Recovery_History_File
DescriptionDeletes entries from the recovery history file.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Time StampSpecifies a complete time stamp (of the form yyyymmddhhmmss) or an initial prefix(minimum form is yyyy) time stamp. All entries in the recovery history file thathave time stamps equal to or less than the specified time stamp are deleted from thefile.
An example of a complete time stamp is: 19971214102030 and an example of aninitial prefix is: 199712.
Force OptionSelect Yes to prune the entries based on the time stamp specified, even if someentries from the most recent restore set are deleted from the file. Selecting No willnot prune the entries.
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
624 Version 2.1.0
wdb2tlib ECC_Prune_Recovery_History<timestamp><force>[<username><password>]
where:
<timestamp>Specifies a complete time stamp (of the form yyyymmddhhmmss) or an initialprefix (minimum form is yyyy). All entries in the recovery history file that havetime stamps equal to or less than the specified time stamp are deleted from thefile.
An example of a complete time stamp is: 19971214102030
An example of an initial prefix is: 199712
<force>Specifies YES or NO to indicate whether entries from the most recent store setshould be deleted from the file if they meet the time stamp criteria.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_Prune_Recovery_History-a <timestamp>-a <force>[-a <username>-a <password>]
where:
<timestamp>Specifies a complete time stamp (of the form yyyymmddhhmmss) or an initialprefix (minimum form is yyyy). All entries in the recovery history file that havetime stamps equal to or less than the specified time stamp are deleted from thefile.
An example of a complete time stamp is: 19971214102030, and an example ofan initial prefix time stamp is: 199712.
<force>Specifies YES or NO to indicate whether entries from the most recent store setshould be deleted from the file if they meet the time stamp criteria.
625Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Prune_Recovery_History 199712 YES joe joepw
¶ Using the wruntask command:wruntask-t ECC_Prune_Recovery_History-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@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 entrieswith time stamps equal to or less than the time stamp provided are deleted. Entries can bepruned even if some entries from the most recent restore set are deleted from the file.
For more information, see the PRUNE HISTORY CLP command in the DB2 CommandReference for the version of DB2 that you are using.
See AlsoNone
626 Version 2.1.0
ECC_Quiesce_Tablespaces
DescriptionQuiesces tablespaces for a DB2 table.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Table SchemaSpecifies the qualified table name. If schema is not provided, the authorization IDused for the database connection will be used as the schema. The table cannot be asystem catalog table.
Table NameSpecifies the unqualified table name. For example, if the qualified name of a table isUSERID.TABLE1, the unqualified table name is 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 this mode, only youcan update the table data. Other users can read but not update the data.
ExclusiveSpecifies that the tablespaces are put in exclusive mode. In this mode, onlyyou can read or update the table data.
Reset Specifies that the tablespaces are put in normal mode.
627Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Quiesce_Tablespaces<schema><name><mode>[<username><password>]
where:
<schema>Specifies the qualified table name. If schema is not provided, the authorizationID used for the database connection will be used as the schema. The tablecannot be a system catalog table.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
<mode>Specifies the quiesce mode in which you want to put the tablespaces for thetable:
SHARESpecifies that the tablespaces are put in shared mode. In this mode, allusers (yourself included) can read but not change the table data.
INTENTSpecifies that the tablespaces are put in update mode. In this mode onlyyou can update the table data. Other users can read, but not update thedata.
EXCLUSIVESpecifies that the tablespaces are put in exclusive mode. In this mode,only you can read or update the table data.
RESETSpecifies that the tablespaces are put in normal mode.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you must
628 Version 2.1.0
specify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the specified <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_Quiesce_Tablespaces-a <schema>-a <name>-a <mode>[-a <username>-a <password>]
where:
<schema>Specifies the qualified table name. If schema is not provided, the authorizationID used for the database connection will be used as the schema. The tablecannot be a system catalog table.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
<mode>Specifies the quiesce mode in which you want to put the tablespaces for thetable:
SHARESpecifies that the tablespaces are put in shared mode. In this mode, allusers (yourself included) can read but not change the table data.
INTENTSpecifies that the tablespaces are put in update mode. In this mode, onlyyou can update the table data. Other users can read, but not update thedata.
EXCLUSIVESpecifies that the tablespaces are put in exclusive mode. In this mode,only you can read or update the table data.
RESETSpecifies that the tablespaces are put in normal mode.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
629Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Quiesce_Tablespaces \userid.table1 table1 SHARE joe joepw
¶ Using the wruntask command:wruntask-t ECC_Quiesce_Tablespaces-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@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-node environment, itquiesces all tablespaces in a load operation in exclusive mode for the duration of the load. Inan MPP environment, this task acts locally on a node and quiesces only the portion oftablespaces that belong to the node where the load is performed.
If the table being quiesced does not have a specified owner, the db2ecc user ID is used asthe default.
Valid quiesce modes are share, intent to update, and exclusive. The three possible states thatresult from this task are QUIESCED SHARE, QUIESCED UPDATE, and QUIESCEDEXCLUSIVE.
When the quiesce share request is received, the transaction requests intent share locks for thetablespaces and a share lock for the table. When the transaction obtains the locks, the stateof the tablespaces is changed to QUIESCED SHARE. The state is granted to the quiesceronly if no conflicting state is held by other users. The state of the tablespaces is recorded inthe tablespace table, along with the authorization ID and the database agent ID of thequiescer, so that the state is persistent.
The table cannot be changed while the tablespaces for the table are in QUIESCED SHAREstate. Other share mode requests to the table and tablespaces will be allowed. When thetransaction commits or rolls back, the locks are released, but the tablespaces for the tableremain in QUIESCED SHARE state until the state is explicitly reset.
When the quiesce exclusive request is made, the transaction requests super exclusive lockson the tablespaces, and a super exclusive lock on the table. When the transaction obtains thelocks, the state of the tablespaces changes to QUIESCED EXCLUSIVE. The state of thetablespaces, along with the authorization ID and the database agent ID of the quiescer, arerecorded in the tablespace table. Because the tablespaces are held in super exclusive mode,no other access to the tablespaces is allowed. The user who invokes the quiesce function(the quiescer), however, has exclusive access to the table and the tablespaces.
When a quiesce update request is made, the tablespaces are locked in intent exclusive (IX)mode, and the table is locked in update (U) mode. The state of the tablespaces with thequiescer is recorded in the tablespace table.
630 Version 2.1.0
For more information, see the QUIESCE TABLESPACES FOR TABLE CLP command inthe DB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
631Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Rebind_All_Packages
DescriptionRebinds all DB2 packages in a database.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Log fileSpecifies the path (optional) and the file name (mandatory) to be used for recordingerrors that result from the package revalidation procedure.
User IDSpecifies the name of the user who is rebinding the database. The User ID isoptional, but it is required if you specify a password.
PasswordSpecifies the password for the User ID. The password is optional, but it is requiredif you specify a User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Rebind_All_Packages<log_file>[<username><password>]
where:
<log_file>Specifies the path (optional) and the file name (mandatory) to be used forrecording errors that result from the package revalidation procedure.
632 Version 2.1.0
<username>Specifies the name of the user who is rebinding the database. This variable isoptional, but it is required if you specify a password.
<password>Specifies the password for the user name. This variable is optional, but it isrequired if you specify a user name.
CLI Synopsis¶ Using the wruntask command:
ECC_Rebind_All_Packages-a <log_file>[-a <username>-a <password>]
where:
<log_file>Specifies the path (optional) and the file name (mandatory) to be used forrecording errors that result from the package revalidation procedure.
<username>Specifies the name of the user who is rebinding the database. This variable isoptional, but it is required if you specify a password.
<password>Specifies the password for the user name. This variable is optional, but it isrequired if you specify a user name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Rebind_All_Packages \tmp\pkg.log /joe joepw
¶ Using the wruntask command:wruntask-t ECC_Rebind_All_Packages-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a /tmp/pkg.log-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes in the nodegroup.
This task uses the CLP REBIND command to attempt the revalidation of all packages in adatabase. You can allow package revalidation to occur implicitly when the packages are firstused.
For more information, see the db2rbind system command in the DB2 Command Referencefor the version of DB2 that you are using.
633Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
See AlsoNone
634 Version 2.1.0
ECC_Rebind_Package
DescriptionLets users re-create a package stored in the database without needing a bind file.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Package SchemaSpecifies the qualifier for the package name. For example, if the qualified name of apackage is USERID.PACK1, the schema is USERID.
If you specify _default_, the current user ID is used.
Package NameSpecifies the unqualified package name. For example, if the qualified name of apackage is USERID.PACK1, the name is PACK1.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Rebind_Package<schema><name>
where:
<schema>Specifies the qualifier for the package name. For example, if the qualified nameof a package is USERID.PACK1, the schema is USERID.
If you specify _default_, the current user ID is used.
635Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<name>Specifies the unqualified package name. For example, if the qualified name of apackage is USERID.PACK1, the name is PACK1.
CLI Synopsis¶ Using the wruntask command:
ECC_Rebind_Package-a <schema>-a <name>
where:
<schema>Specifies the qualifier for the package name. For example, if the qualified nameof a package is USERID.PACK1, the schema is USERID.
If you specify _default_, the current user ID is used.
<name>Specifies the unqualified package name. For example, if the qualified name of apackage is USERID.PACK1, the name is PACK1.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Rebind_Package joe pack1
¶ Using the wruntask command:wruntask-t ECC_Rebind_Package-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@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 to rebind the package tosee what changes. It also permits multiple rebinds within a unit of work.
The REBIND command commits the transaction if auto-commit is enabled.
For more information, see the REBIND CLP command in the DB2 Command Reference forthe version of DB2 that you are using.
See AlsoNone
636 Version 2.1.0
ECC_Reorganize_Table
DescriptionReorganizes a table by reconstructing the rows to eliminate fragmented data, and bycompacting information.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Table SchemaSpecifies the qualifier for the table name. For example, if the qualified name of atable is USERID.TABLE1, the schema is USERID.
Table NameSpecifies the unqualified table name. For example, if the qualified name of a table isUSERID.TABLE1, the name is TABLE1.
Index SchemaSpecifies the qualifier for the index name.
Index NameSpecifies the unqualified index name.
Table Space NameSpecifies the unqualified tablespace name.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Reorganize_Table<schema><name>
637Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
[<i_schema><i_name>[<ts_name>]]
where:
<schema>Specifies the qualifier for the table name. For example, if the qualified name ofa table is USERID.TABLE1, the schema is USERID.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
<i_schema>Specifies the qualifier for the index name.
<i_name>Specifies the unqualified index name.
<ts_name>Specifies the unqualified tablespace name.
CLI Synopsis¶ Using the wruntask command:
ECC_Reorganize_Table-a <schema>-a <name>[-a <i_schema>-a <i_name>[-a <ts_name>]]
where:
<schema>Specifies the qualifier for the table name. For example, if the qualified name ofa table is USERID.TABLE1, the schema is USERID.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
<i_schema>Specifies the qualifier for the index name.
<i_name>Specifies the unqualified index name.
<ts_name>Specifies the unqualified tablespace name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Reorganize_Table joe table1 NONE \NONE tblspc1
638 Version 2.1.0
¶ Using the wruntask command:wruntask-t ECC_Reorganize_Table-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a table1-a NONE-a NONE-a tblspc1
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes in the nodegroup.
Because this task may take longer to complete than the 60-second default time, set thetimeout value to a larger value, such as 600 seconds.
Tables that have been modified so many times that data is fragmented and accessperformance is noticeably slow are candidates for reorganization. Use ECC_Reorgchk todetermine if a table needs reorganizing. Be sure to complete all database operations andrelease all locks before running ECC_Reorganize_Table. After reorganizing a table, useECC_Run_Statistics to update the table statistics, and ECC_Rebind_Packages to rebindthe packages that use this table.
If the reorganization is not successful, do not delete temporary files. The database manageruses 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 AlsoDB2Manager-Database tasks: “ECC_Reorgchk” on page 640, “ECC_Run_Statistics” onpage 650, and “ECC_Rebind_Package” on page 635
639Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Reorgchk
DescriptionCalculates statistics on the database to determine if tables need to be reorganized.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
StatisticsSelect the type of table statistics to use:
CurrentSpecifies that the current table statistics are used to determine if tablereorganization is needed.
UpdateSpecifies that the DB2 RUNSTATS utility is used to update table statistics.These updated statistics are then used to determine if reorganization isneeded.
On TableSelect the tables to check:
User Specifies that all tables owned by the current authorization ID are to bechecked.
SystemSpecifies that all system tables are to be checked.
All Specifies that all user-owned and system-owned tables are to be checked.
Table Specifies that a particular table (specified with schema and name) is to bechecked.
640 Version 2.1.0
Table SchemaSpecifies the qualifier for the table name. For example, if the qualified name of atable is USERID.TABLE1, the table schema is USERID.
Table NameSpecifies the unqualified table name. For example, if the qualified name of a table isUSERID.TABLE1, the unqualified table name is TABLE1.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Reorgchk<stats><on_table>[<schema><name>]
where:
<stats>Specifies the type of table statistics to use:
UPDATESpecifies that the DB2 RUNSTATS utility is used to update tablestatistics. These updated statistics are then used to determine ifreorganization is needed.
CURRENTSpecifies that the current table statistics are used to determine if tablereorganization is needed.
<on_table>Specifies the tables to check:
USER Specifies that all tables owned by the current authorization ID are to bechecked.
SYSTEMSpecifies that all system tables are to be checked.
ALL Specifies that all user-owned and system-owned tables are to bechecked.
TABLESpecifies that a particular table (specified with schema and name) is tobe checked.
<schema>Specifies the qualifier for the table name. For example, if the qualified name ofa table is USERID.TABLE1, the schema is USERID.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
CLI Synopsis¶ Using the wruntask command:
641Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Reorgchk-a <stats>-a <on_table>[-a <schema>-a <name>]
where:
<stats>Specifies the type of table statistics to use:
UPDATESpecifies that the DB2 RUNSTATS utility is used to update tablestatistics. These updated statistics are then used to determine ifreorganization is needed.
CURRENTSpecifies that the current table statistics are used to determine if tablereorganization is needed.
<on_table>Specifies the tables to check:
USER Specifies that all tables owned by the current authorization ID are to bechecked.
SYSTEMSpecifies that all system tables are to be checked.
ALL Specifies that all user-owned and system-owned tables are to bechecked.
TABLESpecifies that a particular table (specified with schema and name) is tobe checked.
<schema>Specifies the qualifier for the table name. For example, if the qualified name ofa table is USERID.TABLE1, the schema is USERID.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Reorgchk CURRENT SYSTEM joe table1
¶ Using the wruntask command:wruntask-t ECC_Reorgchk-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a CURRENT-a SYSTEM-a joe-a table1
642 Version 2.1.0
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes in the nodegroup.
This task calculates statistics obtained from six different formulas to determine ifperformance has deteriorated or can be improved by reorganizing a table.
For more information, see the REORGCHK CLP command in the DB2 CommandReference for the version of DB2 that you are using.
See AlsoNone
643Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Reset_Admin_Configuration
DescriptionResets the parameters in the database manager configuration file (that are relevant to theDB2 Administration Server) to the system defaults.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Reset_Admin_Configuration
CLI Synopsis¶ Using the wruntask command:
ECC_Reset_Admin_Configuration
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Reset_Admin_Configuration
¶ Using the wruntask command:wruntask-t ECC_Reset_Admin_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesThe DB2 Administration Server is a special instance that enables remote administration ofDB2 servers. This command resets the database manager configuration file,$HOME/sqllib/db2systm. This command affects all nodes that are listed in the$HOME/sqllib/db2nodes.cfg file.
For more information, see the RESET ADMIN CONFIGURATION CLP command in theDB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
644 Version 2.1.0
ECC_Reset_Database_Configuration
DescriptionResets the configuration of a specific database to the system defaults.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Reset_Database_Configuration[<username><password>]where:
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
645Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_Reset_Database_Configuration[-a <username>-a <password>]where:
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Reset_Database_Configuration /joe joepw
¶ Using the wruntask command:wruntask-t ECC_Reset_Database_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects only the node on whichit is run.
Changes to the database configuration file become effective only after they are loaded intomemory. All applications must disconnect from the database before the changes can occur.
If an error occurs, the database configuration file does not change. The databaseconfiguration file cannot be reset if the checksum is invalid. The checksum might be invalidif the database configuration file is changed without using the appropriate command. If thisproblem occurs, the database must be restored to reset the database configuration file.
For more information, see the RESET DATABASE CONFIGURATION CLP command inthe DB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
646 Version 2.1.0
ECC_Reset_Database_Manager_Configuration
DescriptionResets the parameters in the database manager configuration file to the system defaults.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager,DB2InstanceManager, and Endpoints
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Reset_Database_Manager_Configuration
CLI Synopsis¶ Using the wruntask command:
ECC_Reset_Database_Manager_Configuration
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Reset_Database_Manager_Configuration
¶ Using the wruntask command:wruntask-t ECC_Reset_Database_Manager_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesChanges to the database manager configuration file become effective only after they areloaded into memory. For a server configuration parameter, the changes occur whenECC_Start_DB2 runs. For a client configuration parameter, changes occur when theapplication is restarted.
If an error occurs, the database manager configuration file does not change. The databasemanager configuration file cannot be reset if the checksum is invalid. The checksum mightbe invalid if the database manager configuration file is changed without using theappropriate command. If this problem occurs, the database manager must be installed againto reset the database manager configuration file.
For more information, see the RESET DATABASE MANAGER CONFIGURATION CLPcommand in the DB2 Command Reference for the version of DB2 that you are using.
See AlsoDB2Manager-Database tasks: “ECC_Start_DB2” on page 659
647Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Restart_Database
DescriptionRestarts a database that was abnormally terminated and left in an inconsistent state.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User NameSpecifies the user who is restarting the database. If you run this task with DB2Enterprise-Extended Edition on a partition group endpoint and at least one of thepartitions in the partition group is on a remote host, you must specify a user name.The user name is used for all nodes included in the partition group whether they areon a local or remote host.
PasswordSpecifies the password for the user name. This parameter is required if you specifythe User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Restart_Database[<username><password>]
where:
<username>Specifies the user who is restarting the database. If you run this task with DB2Enterprise-Extended Edition on a partition group endpoint and at least one of thepartitions in the partition group is on a remote host, you must specify a user
648 Version 2.1.0
name. The user name is used for all nodes included in the partition groupwhether they are on a local or remote host.
<password>Specifies the password for the user name. This parameter is required if youspecify the <username> parameter.
CLI Synopsis¶ Using the wruntask command:
ECC_Restart_Database[-a <username>-a <password>]
where:
<username>Specifies the user who is restarting the database. If you run this task with DB2Enterprise-Extended Edition on a partition group endpoint and at least one of thepartitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition groupwhether they are on a local or remote host.
<password>Specifies the password for the user name. This parameter is required if youspecify the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Restart_Database joe joepw
¶ Using the wruntask command:wruntask-t ECC_Restart_Database-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects only the node on whichit is executed.
Run this task if an attempt to connect to a database returns an error message indicating thatthe database must be restarted. An error occurs only if the previous session with thisdatabase terminated abnormally (for example, due to power failure).
For more information, see the RESTART DATABASE CLP command in the DB2Command Reference for the version of DB2 that you are using.
See AlsoNone
649Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Run_Statistics
DescriptionUpdates statistics about the physical characteristics of a table and the associated indexes.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Table SchemaSpecifies the qualifier for the table name. For example, if the qualified name of atable is USERID.TABLE1, the schema is USERID.
Table NameSpecifies the unqualified table name. For example, if the qualified name of a table isUSERID.TABLE1, the name is TABLE1.
With distribution?Enter Yes or No to indicate whether you want distribution statistics calculated.
IndexesSelect one of the following responses:
Yes Updates statistics on the indexes.
No Does not update statistics on the indexes.
650 Version 2.1.0
Index Specifies to update statistics on a specific index that is defined in theindex-schema and index-name variables.
Indexes Only?Select Yes or No to indicate whether you want to update statistics on the indexesonly.
If the Indexes? argument is Yes and Index only? is No, statistics on both the tableand its indexes are updated.
If Indexes? is No and Index only? is No, statistics on the table only are updated.
Detailed?Enter Yes or No to indicate whether you want extended index statistics calculatedwhen you are updating statistics on the indexes.
Share LevelSelect Change or Reference to indicate how other users can access the table whilestatistics 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 are calculated.
Index SchemaSpecifies the qualifier for the index name. This variable is required if you specifythe Index parameter for the Indexes? variable.
Index NameSpecifies the unqualified index name. This variable is required if you specify theIndex parameter for the Indexes? variable.
User IDSpecifies the name of the user to attach to a remote partition. If you run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least oneof the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Run_Statistics<schema><name><with_dist><indexes><index_only><detailed><change>[<index-schema>
651Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
<index-name><username><password>]
where:
<schema>Specifies the qualifier for the table name. For example, if the qualified name ofa table is USERID.TABLE1, the schema is USERID.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
<with_dist>Specifies 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 is defined in theindex-schema and index-name variables.
<index_only>Specifies YES or NO to indicate whether you want to update statistics on theindexes only.
If indexes is YES and index_only is NO, statistics on both the table and itsindexes are updated.
If indexes is NO and index_only is NO, statistics on the table only are updated.
<detailed>Specifies YES or NO to indicate whether you want extended index statisticscalculated when you are updating statistics on the indexes.
<change>Specifies how other users can access the table 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 are calculated.
<index-schema>Specifies the qualifier for the index name. This variable is required if youspecify the INDEX parameter for the indexes variable.
<index-name>Specifies the unqualified index name. This variable is required if you specify theINDEX parameter for the indexes variable.
652 Version 2.1.0
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
CLI Synopsis¶ Using the wruntask command:
ECC_Run_Statistics-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:
<schema>Specifies the qualifier for the table name. For example, if the qualified name ofa table is USERID.TABLE1, the schema is USERID.
<name>Specifies the unqualified table name. For example, if the qualified name of atable is USERID.TABLE1, the name is TABLE1.
<with_dist>Specifies 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 is defined in theindex-schema and index-name variables.
<index_only>Specifies YES or NO to indicate whether you want to update statistics on theindexes only.
If indexes is YES and index_only is NO, statistics on both the table and itsindexes are updated.
653Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
If indexes is NO and index_only is NO, statistics on the table only are updated.
<detailed>Specifies YES or NO to indicate whether you want extended index statisticscalculated when you are updating statistics on the indexes.
<change>Specifies how other users can access the table 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 are calculated.
<index-schema>Specifies the qualifier for the index name. This variable is required if youspecify the INDEX parameter for the indexes variable.
<index-name>Specifies the unqualified index name. This variable is required if you specify theINDEX parameter for the indexes variable.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Run_Statistics joe table1 \NO NO NO YES reference NONE index2 joe joepw
¶ Using the wruntask command:wruntask-t ECC_Run_Statistics-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a table1-a NO-a NO-a NO-a YES-a reference-a NONE-a index2-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects all nodes in the nodegroup.
654 Version 2.1.0
Run this task when a table has had many updates, or after reorganizing a table. The statisticsupdated by this task include number of records, number of pages, and average record length.The optimizer uses these statistics when determining access paths to the data.
After statistics are updated, you can create new access paths to the table by rebinding thepackages.
Collect statistics that apply only to the tables before you create indexes. By running the tablestatistics first, you ensure that the indexes statistics are not overlaid by table statistics.
For more information, see the RUN STATISTICS CLP command in the DB2 CommandReference for the version of DB2 that you are using.
See AlsoNone
655Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Set_Admin_Server_ID
DescriptionEstablishes or modifies the user account associated with the DB2 Administration Serverinstance. This task is not supported on OS/2 hosts.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User AccountSpecifies the user account to be used.
PasswordSpecifies the password for the User account.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Set_Admin_Server_ID-a <user>-a <password>
where:
<user>Specifies the user account to be used.
<password>Specifies the password for the user account.
656 Version 2.1.0
Examples¶ Using the wruntask command:
wruntask-t ECC_Set_Admin_Server_ID-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw
Usage NotesFor more information, see the db2admin system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
657Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Start_Admin_Server
DescriptionStarts the DB2 Administration Server. This task is not supported on OS/2 hosts.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Start_Admin_Server
Examples¶ Using the wruntask command:
wruntask-t ECC_Start_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesFor more information, see the db2admin system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
658 Version 2.1.0
ECC_Start_DB2
DescriptionStarts the DB2 instance and allocates resources.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
ProfileSpecifies the name of the profile, which defines the DB2 environment, to execute ateach node. You can also enter NONE.
Node NumberSpecifies the number of the node that you want to start. Valid node numbers arefrom 0 to 999. If you do not specify the node number, a normal startup is performedon the node where the start command was issued.
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 the values forthe Host name, Logical port, and Network name options if you select thisoption.
StandaloneSelect this option to specify that the node be started in stand-alone mode. Allfurther options are ignored if you select this option.
659Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
RestartSelect this option to restart the database manager after a failure. If you selectthis option, the values for the Host name, Logical port, and Network nameare not required.
Host NameIf you selected the <Add node> Start option, enter the host name to be added to thedb2nodes.cfg file. If you selected the <Restart> Start option, enter the host name tobe used to override that in the node configuration file. For the <None> or<Stand-alone> Start option, this value is ignored.
Logical PortSpecifies the logical port that you want to add to the db2nodes.cfg file. Valid logicalport numbers are from 0 to 999.
Network NameSpecifies the network name to be added to the db2nodes.cfg file or enter NONE. Ifyou do not specify this parameter, or if it is set to NONE, the network name is setto the value specified in Host name. If you selected the <Add node> Start option,enter the network name to be added to the db2nodes.cfg file. If you selected the<Restart> Start option enter the network name to use to override that in the nodeconfiguration file. For the <None> or <Stand-alone> Start option, this value isignored.
Temporary SpaceIf you selected the <Add node> Start option, enter the node number to indicate thatthe temporary tablespace containers will be the same as the containers on thespecified node number for each database in the instance. For the <None>,<Stand-alone>, or <Restart> Start option, this value is ignored. Enter WITHOUTto specify that containers for the temporary tablespaces are not created for any of thedatabases.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Start_DB2[<profile>[<nodenum>[<startopt>[<hostname><port>[<netname>[<temp>]]]]]]where:
<profile>Specifies the name of the profile file, which defines the DB2 environment, toexecute at each node. You can also specify NONE. This variable is optional.
<nodenum>Specifies the number of the node that you want to start. Valid node numbers arefrom 0 to 999. If you do not specify the node number, a normal startup isperformed on the node where the start command was issued.
660 Version 2.1.0
<startopt>Specifies one of the following start options.
NONESpecifies no start options.
ADDNODESpecifies that a node will be added. 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 are specifiedaccording to the following descriptions:
<hostname>Specifies the host name to add to the db2nodes.cfg file. This variable isrequired.
<port>Specifies the logical port that you want to add to the db2nodes.cfg file. Thisvariable is required. Valid logical port numbers are from 0 to 999.
<netname>Specifies the network name to be added to the db2nodes.cfg file or specifyNONE. If you do not specify this parameter, or if it is set to NONE, thenetwork name is set to the value specified in <hostname>.
<temp>Specifies the node number to specify that the containers for the temporarytablespaces will be the same as the containers on the specified node number foreach database in the instance. Specifies WITHOUT to specify that containersfor the temporary tablespaces are not created for any of the databases. Thisparameter is optional.
CLI Synopsis¶ Using the wruntask command:
ECC_Start_DB2[-a <profile>[-a <nodenum>[-a <startopt>[-a <hostname>-a <port>[-a <netname>[-a <temp>]]]]]]where:
<profile>Specifies the name of the profile file, which defines the DB2 environment, toexecute at each node. You can also specify NONE. This variable is optional.
<nodenum>Specifies the number of the node that you want to start. Valid node numbers are
661Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
from 0 to 999. If you do not specify the node number, a normal startup isperformed on the node where the start command was issued.
<startopt>Specifies one of the following start options.
NONESpecifies no start options.
ADDNODESpecifies that a node will be added. 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 are specifiedaccording to the following descriptions:
<hostname>Specifies the host name to add to the db2nodes.cfg file. This variable isrequired.
<port>Specifies the logical port that you want to add to the db2nodes.cfg file. Thisvariable is required. Valid logical port numbers are from 0 to 999.
<netname>Specifies the network name to be added to the db2nodes.cfg file or specifyNONE. If you do not specify this parameter, or if it is set to NONE, thenetwork name is set to the value specified in <hostname>.
<temp>Specifies the node number to specify that the containers for the temporarytablespaces will be the same as the containers on the specified node number foreach database in the instance. Specifies WITHOUT to specify that containersfor the temporary tablespaces are not created for any of the databases. Thisparameter is optional.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Start_DB2 profile1 6 ADDNODE /bburns 662 NONE WITHOUT
¶ Using the wruntask command: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
662 Version 2.1.0
Usage NotesThe following arguments can be run only on DB2 Enterprise-Extended Edition.
When this task is run on DB2 Enterprise-Extended Edition in a multi-node environment, itaffects all nodes that are listed in the $HOME/sqllib/db2notes.cfg file, unless you specifythe <nodenum> variable.
After this task starts, the database manager instance runs until you stop it, even if allprograms that were using it have ended.
For more information when you are running UNIX, see the db2start system command inthe DB2 Command Referenc for the version of DB2 that you are using.
See AlsoNone
663Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Start_DB2_NT_Security
DescriptionStarts the DB2 security service on a Windows system.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, and Endpoints
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Start_DB2_NT_Security
Examples¶ Using the wruntask command:
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 669 task to stop the DB2 securityservice, additional dependent NT services, such as Data Warehouse services, may have beenstopped. The “ECC_Start_DB2_NT_Security” will not restart dependent services; theymust be started manually.
See AlsoNone
664 Version 2.1.0
ECC_Stop_Admin_Server
DescriptionStops the DB2 Administration Server.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Stop_DB2_Admin_Server
Examples¶ Using the wruntask command:
wruntask-t ECC_Stop_DB2_Admin_Server-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns
Usage NotesFor more information, see the db2admin system command in the DB2 Command Referencefor the version of DB2 that you are using.
See AlsoNone
665Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Stop_DB2
DescriptionStops the DB2 instance and releases resources.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Stop DB2 ProfileSpecifies the name of the profile that was executed during startup, which defined theDB2 environment for the nodes that were started. This variable is optional.
Type Select one of the following stop options:
None Specifies no stop options.
Node Stops the node specified in the Node Number argument. If you specify thisparameter, you must specify a node in the Node Number argument.
Drop Drops the node specified in the Node Numberargument and stops all nodes.If you specify this parameter, you must specify a node to drop in the NodeNumber argument.
Force If you specify this parameter, all further arguments are ignored. Thisparameter specifies that “ALL” is used when stopping the database managerat each node.
Node numberSpecifies the number of the node to be stopped. Valid node numbers are from 0 to999.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
666 Version 2.1.0
wdb2tlib ECC_Stop_DB2[<profile>[<type>[<nodenum>]]]
where:
<profile>Specifies the name of the profile that was executed during startup, which definedthe DB2 environment for the nodes that were started. This variable is optional.
<type>Specifies one of the following stop options:
NONESpecifies no stop options.
NODEStops the node specified in the <nodenum> argument. If you specifythis parameter, you must specify a node in the <nodenum> argument.
DROPDrops the node specified in the <nodenum> argument and stops allnodes. If you specify this parameter, you must specify a node to drop inthe <nodenum> argument.
FORCEIf you specify this parameter, all further arguments are ignored. Thisparameter specifies that “ALL” is used when stopping the databasemanager at each node.
<nodenum>Specifies the number of the node to be stopped. Valid node numbers are from 0to 999.
CLI Synopsis¶ Using the wruntask command:
ECC_Stop_DB2[-a <profile>[-a <type>[-a <nodenum>]]]where:
<profile>Specifies the name of the profile that was executed during startup, which definedthe DB2 environment for the nodes that were started. This variable is optional.
<type>Specifies one of the following stop options:
NONESpecifies no stop options.
NODEStops the node specified in the <nodenum> argument. If you specifythis parameter, you must specify a node in the <nodenum> argument.
667Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
DROPDrops the node specified in the <nodenum> argument and stops allnodes. If you specify this parameter, you must specify a node to drop inthe <nodenum> argument.
FORCEIf you specify this parameter, all further arguments are ignored. Thisparameter specifies that “ALL” is used when stopping the databasemanager at each node.
<nodenum>Specifies the number of the node to be stopped. Valid node numbers are from 0to 999.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Stop_DB2 profile1 NODE 67
¶ Using the wruntask command:wruntask-t ECC_Stop_DB-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a profile1-a NODE-a 67
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition in a multi-node environment, itaffects all nodes that are listed in the $HOME/sqllib/db2notes.cfg file, unless you specifiedthe NODE parameter for the <type> variable.
This task does not stop DB2 if any applications are connected to databases. If there are nodatabase connections, but there are instance attachments, ECC_Stop_DB2 forces theinstance attachments and stops DB2.
ECC_Stop_DB2 can be run on a DB2 server or on other managed nodes. After DB2 stops,a successful completion message is sent to the standard output device. If an error occurs,processing stops, and an error message is sent to the standard output device.
For more information when you are running UNIX, see the db2stop system command in theDB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
668 Version 2.1.0
ECC_Stop_DB2_NT_Security
DescriptionStops the DB2 security service on a Windows system.
Authorization Roledb2_user
Target EndpointsDB2DatabaseManager, DB2InstanceManager, and Endpoints
Desktop Data Entry FieldsNone
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Stop_DB2_NT_Security
Examples¶ Using the wruntask command:
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 the time of thiswriting (DB2 Version 7.1), only the DB2 Data Warehouse service (an optionally installedfeature) is dependent.
See AlsoNone
669Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Update_Admin_Configuration
DescriptionModifies individual entries in the database manager configuration file that are relevant to theDB2 Administration Server.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Keyword 1Click the Parameter button and select the name of the database managerconfiguration parameter that you want to update. You can select or specify from oneto five keyword-value pairs.
Value 1Specifies the new value for the configuration parameter specified in thecorresponding key.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
670 Version 2.1.0
ECC_Update_Admin_Configuraiton-a <key01 val01>[-a <key02 val02>...-a <key05 val05>]
where:
<key> Specify the name of the database manager configuration parameter that you wantto update. You can select or specify from one to five keyword-value pairs.
<val> Specifies the new value for the configuration parameter specified in thecorresponding key.
Examples¶ Using the wruntask command:
wruntask-t ECC_Update_Admin_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a MAXAGENTS 300-a MAXCAGENTS 250
Usage NotesNone
See AlsoNone
671Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Update_Database_Configuration
DescriptionModifies individual entries in a specific database configuration file.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, and DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Keyword 1Click the Parameter button to select the name of the database configurationparameter you want to update. You can specify from one to five keyword-valuepairs.
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 run this taskwith DB2 Enterprise-Extended Edition on a partition group endpoint and at least one
672 Version 2.1.0
of the partitions in the partition group is on a remote host, you must specify a username. The user name is used for all nodes included in the partition group whetherthey are on a local or remote host.
PasswordSpecifies the password used to authenticate the User ID.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
ECC_Update_Database_Configuration-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 to update.You can specify from one to five keyword-value pairs.
<val> Specifies the new value for the configuration parameter specified in thecorresponding key.
<username>Specifies the name of the user to attach to a remote partition. If you run thistask with DB2 Enterprise-Extended Edition on a partition group endpoint and atleast one of the partitions in the partition group is on a remote host, you mustspecify a user name. The user name is used for all nodes included in thepartition group whether they are on a local or remote host.
<password>Specifies the password used to authenticate the <username> variable.
Examples¶ Using the wruntask command:
wruntask-t ECC_Update_Database_Configuration-l DB2ManagerDatabaseTasks-h @DB2InstanceManager:db2inst1@bburns-a APPLHEAPSZ 256-a DBHEAP 1500-a PCKCACHESZ 129-a CATALOGCACHE_SZ 256-a joe-a joepw
Usage NotesWhen this task is run on DB2 Enterprise-Extended Edition, it affects only the node on whichit is executed.
673Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
Changes to the database configuration file become effective only after they are loaded intomemory. All applications must disconnect from the database before changes can be loaded.If an error occurs, the database configuration file does not change.
The database configuration file cannot be updated if the checksum is invalid. If this problemoccurs, the database must be restored to reset the database configuration file.
For more information, see the UPDATE DATABASE CONFIGURATION CLP commandin the DB2 Command Reference for the version of DB2 that you are using.
See AlsoNone
674 Version 2.1.0
ECC_Update_Database_Manager_Configuration
DescriptionModifies individual entries in the database manager configuration file.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
Config-keyword 1Specifies the name of the database manager configuration parameter you want toupdate. You can specify from one to five keyword-value pairs.
Config-value 1Specifies the new value for the configuration parameter specified in thecorresponding key.
Partial Program Syntax (run from a monitor)You cannot run this task from a monitor.
CLI Synopsis¶ Using the wruntask command:
675Tivoli Manager for DB2 Reference Guide
16.D
B2
Datab
aseTasks
ECC_Update_Database_Manager _Configuration-a <key01 val01>[-a <key02 val02>...-a <key05 val05>]
where:
<key> Specifies the name of the database manager configuration parameter you want toupdate. You can specify from one to five keyword-value pairs.
<val> Specifies the new value for the configuration parameter specified in thecorresponding key.
Examples¶ Using the wruntask command:
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 after they areloaded into memory. For a server configuration, parameter changes are loaded into memorywhen ECC_Start_DB2 is run. For a client configuration parameter, parameter changes areloaded into memory when the application is restarted. If an error occurs, the databasemanager configuration file does not change.
The database manager configuration file cannot be updated if the checksum is invalid. If thiserror occurs, the database manager must be reinstalled to reset the database managerconfiguration file.
For more information, see the UPDATE DATABASE MANAGER CONFIGURATIONCLP command in the DB2 Command Reference for the version of DB2 that you are using.
See AlsoDB2Manager-Database tasks: “ECC_Start_DB2” on page 659
676 Version 2.1.0
Data Replication Tasks
The DB2ManagerReplicationTasks library contains tasks that are used with DB2Replication
For more information about data replication tasks, see the DB2 Replication Guide andReference.
Table 60 lists the tasks in this library and provides a brief description of what they do. Thetasks are listed alphabetically.
Table 60. DB2ManagerReplicationTasksTask Description
ECC_Apply_Start Start the data replication Apply program
ECC_Apply_Stop Stop the data replication Apply program
ECC_Capture_Get_Log_Seq Retrieve the current log sequence number andtime stamp
ECC_Capture_Prune Prune the data replication Capture program
ECC_Capture_Reinit Reinitialize the data replication Capture program
ECC_Capture_Resume Resume the data replication Capture program
ECC_Capture_Start Start the data replication Capture program
ECC_Capture_Stop Stop the data replication Capture program
ECC_Capture_Suspend Suspend the data replication Capture program
Running TasksThis document provides the necessary arguments you need in order to run the TivoliManager for DB2 tasks using one or more of the following methods:
¶ From the Tivoli desktop using the Configure Task Arguments dialog box
¶ From a Tivoli Manager for DB2 monitor using the wdb2tlib command
Note: You must enter the fully qualified path of the executable for this command to runproperly. Refer to the Tivoli Manager for DB2 User’s Guide for moreinformation.
¶ From the Tivoli command line using the wruntask command
For step-by-step information about running tasks using these methods, see the TivoliManager for DB2 User’s Guide.
17
677Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Apply_Start
DescriptionRefreshes or updates a target table.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User IDSpecifies the user ID to be used for starting the Apply program.
PasswordFor Windows only: Specifies the password used to authenticate the User ID.
PathnameSpecifies the full path where you want the Apply program to write files.
QualifierIf this task is run on DB2 Enterprise-Extended Edition, it specifies the Applyqualifier that the Apply instance uses to identify the subscriptions to be served.Otherwise, specify NONE.
ServerNameIf this task is run on DB2 Enterprise-Extended Edition, it specifies the name of theserver where the replication control tables will reside. Otherwise specify NONE.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
For AIX, HP, and Solaris:wdb2tlib ECC_Apply_Start<userid>
678 Version 2.1.0
<password>"<path>"<qualifier><server><asnload><priority>
For Windows:wdb2tlib2 ECC_Apply_Start<userid><password>"<path>"<qualifier><server><asnload><priority>where:
<userid>Specifies the user ID to be used for starting the Apply program.
<password>Specifies the password for <username>:
NONEFor AIX only: Specifies that no password is supplied.
passwordFor Windows only: Specifies the password used to authenticate the userID entered for <userid>.
"<path>"Specifies the full path to which you want the Apply program to write files. Youmust specify the quotation marks around the name.
<qualifier>If this task is being run on DB2 Enterprise-Extended Edition, specify the Applyqualifier that the Apply instance uses to identify the subscriptions to be served.Otherwise specify NONE.
<server>If this task is being run on DB2 Enterprise-Extended Edition, specify the nameof the server where the replication control tables will reside. Otherwise specifyNONE.
<asnload>Specifies YES or NO to indicate whether to call the ASNLOAD user-exitroutine. ASNLOAD calls an IBM or vendor utility to initialize a point-in-timetable.
<priority>For DB2 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, LASTRUN forthis instance of the Apply program.
679Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
OTHERSpecifies that the Apply program selects the next subscription in theorder of PRIORITY, COPY_OWNER, and COPY_TABLE.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Apply_Start-a <userid>-a <password>-a "<path>"-a <qualifier>-a <server>-a <asnload>-a <priority>
<userid>Specifies the user ID to be used for starting the Apply program
<password>Specifies the password for <username>:
NONEFor AIX only: Specifies that no password is supplied.
passwordFor NT only: Specifies the password used to authenticate the user IDentered for <userid>.
"<path>"Specifies the full path to which you want the Apply program to write files. Youmust specify the quotation marks around the name.
<qualifier>If this task is being run on DB2 Enterprise-Extended Edition, specify the Applyqualifier that the Apply instance uses to identify the subscriptions to be served.Otherwise, specify NONE.
<server>If this task is being run on DB2 Enterprise-Extended Edition, specify the nameof the server where the replication control tables will reside, or specify NONE.Otherwise, specify NONE.
<asnload>Specifies YES or NO to indicate whether to call the ASNLOAD user-exitroutine. ASNLOAD calls an IBM or vendor utility to initialize a point-in-timetable.
<priority>For 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, LASTRUN forthis instance of the Apply program.
680 Version 2.1.0
OTHERSpecifies that the Apply program selects the next subscription in theorder of PRIORITY, COPY_OWNER, and COPY_TABLE.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Apply_Start joe\joepw \"D:\applydir" NONE NONE
¶ Using the wruntask command:wruntask-t ECC_Apply_Start-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a joepw-a "D:\applydir"-a NONE-a NONE
Usage NotesAfter you run ECC_Apply_Start, the Apply program runs continuously until any of thefollowing occurs:
¶ You stop the Apply program (ECC_Apply_Stop).
¶ An unexpected error or failure occurs.
¶ The ENABLE field of the global control record in any refresh control table indicatesthat it should stop.
¶ 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 the root IDand prompts you for an Apply ID. Windows requires a password.
See AlsoDB2Manager-Replication tasks: “ECC_Apply_Stop” on page 682
681Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Apply_Stop
DescriptionStops the Apply program.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager,DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
User IDSpecifies the user ID to be used for starting the Apply program. This must be thesame ID used to start the Apply program.
PathnameSpecifies the full path where you want the Apply program to write files.
QualifierIf this task is run on DB2 Enterprise-Extended Edition, it specifies the Applyqualifier that the Apply instance uses to identify the subscriptions to be served.Otherwise specify NONE.
Partial Program Syntax (run from a monitor)Using the wdb2tlib command:
wdb2tlib ECC_Apply_Stop<userid><pathname>[<qualifier>]where:
<userid>Specifies the user ID to be used for stopping the Apply program. This must be thesame ID used to start the Apply program.
682 Version 2.1.0
"<pathname>"Specifies the full path where you want the Apply program to write files.
<qualifier>If this task is being run on DB2 Enterprise-Extended Edition, specify the Applyqualifier that the Apply instance uses to identify the subscriptions to be served.Otherwise, specify NONE.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Apply_Stop-a <userid>-a "<path>"[-a <qualifier>]where:
<userid>Specifies the user ID to be used for stopping the Apply program. This must bethe same ID used to start the Apply program.
<pathname>Specifies the full path where you want the Apply program to write files.
<qualifier>If this task is being run on DB2 Enterprise-Extended Edition, specify the Applyqualifier that the Apply instance uses to identify the subscriptions to be served.Otherwise, specify NONE.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Apply_Stop joe \"D:\applydir" NONE
¶ Using the wruntask command:wruntask-t ECC_Apply_Stop-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a joe-a "D:\applydir"-a NONE
Usage NotesWhen this task is run with DB2 Enterprise-Extended Edition, it can run on the AIX andWindows platforms. When this task is run with DB2 Enterprise-Extended Edition, it affectsall nodes in the node group.
See AlsoNone
683Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Capture_Get_Log_Seq
DescriptionRetrieves the current log sequence number and time stamp.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2PartitionManager, DB2PartitionGroupManager, andDB2InstanceManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Prune"<path>"where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Get_Log_Seq-a "<path>"where:
684 Version 2.1.0
"<path>"Specifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified. You must specify the quotation marks around the name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Get_Log_Seq \"D:\applydir"
¶ Using the wruntask command:wruntask-t ECC_Capture_Get_Log_Seq-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a "D:\applydir"
Usage NotesThe information retrieved by this task helps determine how far the Capture program has readthe DB2 log.
See AlsoNone
685Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Capture_Prune
DescriptionPrunes the data replication capture tables if you specified the NOPRUNE argument whenyou started the Capture program.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager,DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Prune"<path>"where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Prune-a "<path>"
686 Version 2.1.0
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Prune \"D:\applydir"
¶ Using the wruntask command:wruntask-t ECC_Capture_Prune-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a "D:\applydir"
Usage NotesIf pruning was disabled by using the NOPRUNE argument while starting the Captureprogram, this command prunes the data replication capture tables one time.
See AlsoNone
687Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Capture_Reinit
DescriptionCauses the Capture program to reread tables while it is running so that it recognizes newregistrations (for DPROPR) and new source table definitions (for DB2 UDB and DB2Enterprise-Extended Edition).
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager,DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
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 the directory specified.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Prune"<path>"where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Reinit-a "<path>"where:
688 Version 2.1.0
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Reinit "D:\applydir"
¶ Using the wruntask command:wruntask-t ECC_Capture_Reinit-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a "D:\applydir"
Usage NotesThis command also rereads the tuning parameters table for any changes made to the tuningparameters.
For DPROPR, do not use ECC_Capture_Reinit to reinitialize the Capture program aftercancelling a registration or dropping a registered table while Capture is running. For DB2UDB and DB2 Enterprise-Extended Edition, do not use ECC_Capture_Reinit to reinitializethe Capture program after cancelling a replication source or dropping a replication sourcetable while Capture is running. In either situation, use the ECC_Capture_Stop task to stopthe Capture program and then use the ECC_Capture_Start task with the WARM parameterto restart the Capture program.
See AlsoDB2Manager-Replication tasks: “ECC_Capture_Stop” on page 695,“ECC_Capture_Start” on page 692
689Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Capture_Resume
DescriptionRestarts a suspended Capture program.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager,DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Prune"<path>"where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Resume-a "<path>"
690 Version 2.1.0
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Resume "D:\applydir"
¶ Using the wruntask command:wruntask-t ECC_Capture_Resume-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a "D:\applydir"
Usage NotesIf you are pruning a file with ECC_Capture_Prune and you run ECC_Capture_Stop orECC_Capture_Suspend, pruning does not resume after you run ECC_Capture_Resume.You must run ECC_Capture_Prune again.
See AlsoDB2Manager-Replication tasks: “ECC_Capture_Prune” on page 686,“ECC_Capture_Stop” on page 695, and “ECC_Capture_Suspend” on page 697
691Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
ECC_Capture_Start
DescriptionStarts the Capture program, which reads database log or journal records to capture dataabout changes made to source tables.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager,DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified.
Type Specifies where the Capture program should start processing:
WARMSpecifies that the Capture program starts processing where it ended in itsprevious run if warm start information is available. Otherwise, the Captureprogram switches to a cold start.
WARMNSSpecifies that the Capture program starts processing where it ended in itsprevious run if warm start information is available. Otherwise, the Captureprogram issues a message and ends.
COLDSpecifies that the Capture program starts processing by deleting all rows inits change data table, unit-of-work table, pruning control table, and tracetable during initialization.
692 Version 2.1.0
Prune?Select YES or NO to indicate if the Capture program should automatically prune thechange data and unit-of-work tables.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Start"<path>"<type><prune>where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
<type>Specifies where the Capture program should start processing:
WARMSpecifies that the Capture program starts processing where it ended in itsprevious run if warm start information is available. Otherwise, theCapture program switches to a cold start.
WARMNSSpecifies that the Capture program starts processing where it ended in itsprevious run if warm start information is available. Otherwise, theCapture program issues a message and ends.
COLDSpecifies that the Capture program starts processing by deleting all rowsin its change data table, unit-of-work table, pruning control table, andtrace table during initialization.
<prune>Specifies YES or NO to indicate whether the Capture program shouldautomatically prune the change data and unit-of-work tables.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Start-a "<path>"-a <type>-a <prune>where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
<type>Specifies where the Capture program should start processing:
693Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
WARMSpecifies that the Capture program starts processing where it ended in itsprevious run if warm start information is available. Otherwise, theCapture program switches to a cold start.
WARMNSSpecifies that the Capture program starts processing where it ended in itsprevious run if warm start information is available. Otherwise, theCapture program issues a message and ends.
COLDSpecifies that the Capture program starts processing by deleting all rowsin its change data table, unit-of-work table, pruning control table, andtrace table during initialization.
<prune>Specifies YES or NO to indicate whether the Capture program shouldautomatically prune the change data and unit-of-work tables.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Start "/w/joe/captdir" \WARM NO
¶ Using the wruntask command:wruntask-t ECC_Capture_Start-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@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
694 Version 2.1.0
ECC_Capture_Stop
DescriptionStops the data replication Capture program in an orderly manner and commits the logrecords that it processed up to that point.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Stop"<path>"where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Stop-a "<path>"
695Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Stop "D:\applydir"
¶ Using the wruntask command:wruntask-t ECC_Capture_Stop-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@bburns-a "D:\applydir"
Usage NotesIf you are pruning a file with ECC_Capture_Prune and you run ECC_Capture_Stop orECC_Capture_Suspend, pruning does not resume after you run ECC_Capture_Resume.You must run ECC_Capture_Prune again.
See AlsoDB2Manager-Replication tasks: “ECC_Capture_Prune” on page 686,“ECC_Capture_Suspend” on page 697, and “ECC_Capture_Resume” on page 690
696 Version 2.1.0
ECC_Capture_Suspend
DescriptionRelinquishes resources to operational transactions during peak periods without damaging theCapture environment.
Authorization Roledb2_dba
Target EndpointsDB2DatabaseManager, DB2InstanceManager, DB2PartitionManager,DB2PartitionGroupManager
Desktop Data Entry FieldsThe following figure shows the desktop fields for this task.
PathnameSpecifies the full path to which you want the Capture program to write files. ForAIX, the ID used by this task must have write permissions for the directoryspecified.
Partial Program Syntax (run from a monitor)¶ Using the wdb2tlib command:
wdb2tlib ECC_Capture_Suspend"<path>"where:
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
CLI Synopsis¶ Using the wruntask command:
wruntask ECC_Capture_Suspend-a "<path>"where:
697Tivoli Manager for DB2 Reference Guide
17.D
ataR
eplicatio
nTasks
"<path>"Specifies the full path to which you want the Capture program to write files.You must specify the quotation marks around the name.
Examples¶ Using the wdb2tlib command on Windows:
perl -S c:\Tivoli\bin\w32-ix86\bin\wdb2tlib ECC_Capture_Suspend "D:\applydir"
¶ Using the wruntask command:wruntask-t ECC_Capture_Suspend-l DB2ManagerReplicationTasks-h @DB2InstanceManager:db2inst1@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 run ECC_Capture_Stop orECC_Capture_Suspend, pruning does not resume after you run ECC_Capture_Resume.You must run ECC_Capture_Prune again.
See AlsoDB2Manager-Replication tasks: “ECC_Capture_Resume” on page 690,“ECC_Capture_Prune” on page 686, and “ECC_Capture_Stop” on page 695
698 Version 2.1.0
DB2 Snapshot Application ID Formats
The DB2 snapshot application ID is an identifier that is generated when the applicationconnects to the database at the database manager. The application ID is unique across thenetwork.
The format used for the application ID depends on the communication protocol between theclient and the server computers on which the database manager is running. Each of theformats 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 is aconcatenation of the network name, the logical unit (LU) name, and the logical unit-of-workID (LUWID) instance number. In Systems Network Architecture (SNA), a logical unit is aport through which an end user access the SNA network to communicate with another enduser.
NetworkCan be a maximum of 8 characters.
LU_nameCan be a maximum of 8 characters.
Application_instCorresponds to the 12–decimal-character LUWID instance number.
IPX/SPX
FormatNetid.nodeid.Identifier
ExampleC11A8E5C.400011528250.1116183045
A
699Tivoli Manager for DB2 Reference Guide
A.
DB
2S
nap
sho
tA
pp
lication
IDF
orm
ats
DetailsThe application ID that is generated for an application using the IPX/SPX protocol is aconcatenation of a character network ID (8 hexadecimal characters), a node ID (12hexadecimal characters), and a unique identifier for this particular application (Identifier).
IdentifierCorresponds to a 10-decimal-character timestamp of the form mmddhhmmss.
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 the string*LOCAL, the name of the DB2 instance, and a unique identifier for this particularapplication.
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 in theclient’s database configuration file, and a unique identifier for this particular application.
TCP/IP
Format*TCPIP.IPAddr.Identifier
Example*TCPIP.A12CF9E8.930131214645
DetailsThe application ID generated for an application using the TCP/IP protocol is a concatenationof the string *TCPIP, the IP address in hexadecimal characters (maximum of 8), and aunique identifier for this particular application.
You can use “ECC_List_Applications” on page 611 to list the application IDs for allapplications that are currently active for a particular database.
700 Version 2.1.0
Operator Groups
The Edit Monitor dialog contains the trigger when menu, which allows you to define theconditions that must occur for a monitor to send an alert. The values displayed in this menuvary, depending on whether the monitor uses a numeric value, a string value, or a statusmessage. These options are defined in operator groups. Each option of an operator groupserves as a mathematical or logical evaluator. Each operator description includes the valuefor the waddmon –R argument. The quotation marks for each operator are required. If youwant to specify the (never) operator from the command line, omit the –R argument.
Numeric Operator GroupTo define the threshold value, select one of the following options and enter a number in theargument field.
(never)Does not trigger a response. This value only affects the specific response level, notthe entire monitor.
Greater thanRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is greater than the specified value. Because itchecks only against the current sample, this type of threshold can trigger after anysample. This operator can be specified at the command line by entering “>”.
Less thanRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is less than the specified value. Because it checksonly against the current sample, this type of threshold can trigger after any sample.This operator can be specified at the command line by entering “<”.
Equal toRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is equal to the specified value. Because it checksonly against the current sample, this type of threshold can trigger after any sample.This operator can be specified at the command line by entering “==”.
Not equalRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is not equal to the specified value. Because itchecks only against the current sample, this type of threshold can trigger after anysample. This operator can be specified at the command line by entering “!=”.
Increases beyondCompares the current value against the previous value and triggers only if the
B
701Tivoli Manager for DB2 Reference Guide
B.
Op
erator
Gro
up
s
current value is greater than both the previous value and the threshold specified inthe argument field. This operator can be specified at the command line by entering“->>”.
Decrease belowRecords the value of each sample and triggers a response when the previousresource value is above the threshold specified in the text field, but the current valueis below the specified threshold. This operator can be specified at the command lineby entering “-<<”.
Increase ofChecks the current value against the previous value and triggers a response when thedifference is greater than or equal to the threshold value. This operator can bespecified at the command line by entering “->=”.
% increase ofChecks the current value as a percentage of the previous value and triggers aresponse when the current value has increased over the previous value by thespecified percentage. This operator can be specified at the command line by entering“%>=”.
Changes byMeasures an absolute difference between the previous and current value. Thisoperator can be specified at the command line by entering “+>”.
Outside rangeCompares each sample against the defined range limit and triggers a response whenthe current value falls outside the specified range. Because the range check is madeagainst the current sample, this monitor type can trigger after any sample. To definethe acceptable range, enter a lower and upper limit separated by a dash in theargument field. This operator can be the argument field. This operator can bespecified at the command line by entering “<>”.
String Operator GroupTo define the threshold value, select one of the following options and enter a string (whichcan include wildcard characters) in the argument field.
(never)Indicates the response level does not trigger a response. This value only affects thespecific response level, not the entire monitor.
Equal toRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is equal to the specified value. Because it checksonly against the current sample, this type of threshold can trigger after any sample.This operator can be specified at the command line by entering “==”.
Not equal toRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is not equal to the specified value. Because itchecks only against the current sample, this type of threshold can trigger after anysample. This operator can be specified at the command line by entering “!=”.
MatchesChecks the value returned by the query script against the threshold value providedfor user-defined and asynchronous string monitors. A response is triggered if the
702 Version 2.1.0
response matches the value provided. The query program is named in the AddMonitor to Tivoli Distributed Monitoring Profile dialog. This operator can bespecified at the command line by entering “=x”.
MismatchesChecks the value returned by the query script against the threshold value providedfor the user-defined and asynchronous string monitors. A response is triggered if theresponse does not match the value provided. The query program is named in theAdd Monitor to Tivoli Distributed Monitoring Profile dialog. This operator canbe specified at the command line by entering “!x”.
Changes toCompares the current value (returned by the query script and compared to thethreshold value provided for user-defined and asynchronous string monitors) againstthe previous value. A response is triggered if the current value matches the valueprovided, but the previous value did not. The query program is named in the AddMonitor to Tivoli Distributed Monitoring Profile dialog. This operator can bespecified at the command line by entering “->”.
Changes fromCompares the current value (returned by the query script value and compared to thethreshold value provided for user-defined and asynchronous string monitors) againstthe previous value. A response is triggered if the current value does not match thevalue provided, but the previous value did. The query program is named in the AddMonitor to Tivoli Distributed Monitoring Profile dialog. This operator can bespecified at the command line by entering “-<”.
Status Operator GroupTo define the status value, select one of the following options. The resource to be monitoredis named in the Add Monitor to Tivoli Distributed Monitoring Profile dialog.
(never)Indicates the response level does not trigger a response. This value only affects thespecific response level, not the entire monitor.
Is up/availableChecks the status of system resources, such as daemons, host, and print queues. Aresponse is triggered if the resource is available. This operator can be specified atthe command line by entering “==” “up”.
Is down/unavailableChecks the status of system resources, such as daemons, hosts, and print queues. Aresponse is triggered if the resource is not available. This operator can be specifiedat the command line by entering “==” “down”.
Becomes availableChecks the status of system resources, such as daemons, host, and print queues. Aresponse is triggered if the resource was not available in the previous sample and isavailable in the current sample. This operator can be specified at the command lineby entering “->” “up”.
Becomes unavailableChecks the status of system resources, such as daemons, host, and print queues. A
703Tivoli Manager for DB2 Reference Guide
B.
Op
erator
Gro
up
s
response is triggered if the resource was available in the previous sample and is notavailable in the current sample. This operator can be specified at the command lineby entering “->” “up”.
Same asChecks the return string. A response is triggered if the return string matches the oneprovided. To define the threshold value, enter a string in the argument field. Thisoperator can be specified at the command line by entering “>”.
Different fromChecks the return string. A response is triggered if the return string is not the sameas the one provided. This operator can be specified at the command line by entering“>”.
704 Version 2.1.0
Index
Aactive applications 325agent pool, agents allowed 350agents
accepting application requests 344DB2 ECC monitoring communication agent
checking status 38DB2 SNMP
starting 566status 41stopping 569
idle 347max concurrent coordinator 346max coordinating 345maximum number 344monitoring
setting up 564starting 568stopping 570
number idle 91priority 338registered
max allowed to register 437max registered 439
application control heap, max size 315application heap
controlling memory 333max size 316
application support layer, heap size 339applications
active 325application heap storage 316average lock wait 390average locks held by connected 391average number 317buffer pool data pages written 134buffer pool wait 132concurrent 325concurrent connections used 82connected locally 92connected remotely 97connected to local database 94connection frequency 54DDL SQL statments executed 489, 503delete rows 509direct reads 124direct writes 126dynamic SQL statment attempted 491explicit SQL COMMIT statements attempted 493failed SQL statements 497force all 597force specific 599index page read request 136index page write 138
applications (continued)insert rows 511inserts of SQL 481issuing rollbacks 507list 611local connections executing 93logical data read 140number connected 46number executing 47number of locks held 385number of sorts 459number waiting for locks 389open block cursors 499open cursors 501percent buffer pool hit ratio, data+index 142percent buffer pool hit ratio, index 144percent package cache hit ratio 146pool I/O time 152pool read time 148pool write time 150processing connections faster 54REBIND PACKAGE attempts 485remote connections executing 98sectors read per direct read 128sectors written per direct write 130select rows 513simulataneous connections 77sorting statements 463sorting time 461SQL COMMIT statements attempted 487SQL requests submitted 519SQL rollbacks attempted 495SQL SELECT statements executed 517static statements 521total deadlocks 377total lock escalations 379Update/Insert/Delete SQL statements 505, 523update rows 515wait for locked data 383wait time for lock 381wait time for locks within database 401
apply programcheck status 360failed subscriptions 364lagging subscriptions 363stop 682subscription lag time 367subscription status 369table refresh 365
asynchronousbuffer pool index reads 188buffer pool index writes 189buffer pool reads 186, 190buffer pool writes 187, 191page cleaners 320, 330
X-1Tivoli Manager for DB2 Reference Guide
Ind
ex
asynchronous (continued)reads for database 165reads per pool read 172writes per pool read 173
Bbackups
database 581list file 614timestamp 75
binds, See rebinds 48broadcast message 556buffer pool
alter size 576asynchronous index reads 188asynchronous index writes 189asynchronous reads 172, 186, 190asynchronous writes 173, 187, 191average read time 180average write time 181configuring usage 317data pages written 134dirty page threshold 154extended storage read/write ratio 206, 294I/O time 152index logical reads 197, 284index pages copied from extended storage 198, 287index pages copied to extended storage 199, 288index physical reads 200, 289index physical writes 201index writes 290logical reads 192pages copied from extended storage 193, 279pages copied to extended storage 194, 280physical read time 216, 308physical reads 195, 281, 282physical write time 217, 309physical writes 196prefetch wait 132read per direct read 175read time 148reads for database 163write time 150writes for database 164writes per pool read 174written per direct write 176
buffer pool hit ratiodata+index 142, 207, 297defined 143index 144, 209, 299
buffer pool size 318buffer size, log 323bytes
logical read 441physical read 445physically written 447
Ccache size
catalog 319package 333
capture programerrors 371lag time 372prune tables 686pruning 373reading DB2 log 685reinitialize 689reread tables 688restart 690resume 690start 692stop 695suspend 697
catalog cacheinsert
failure due to cache full 52failure due to heap full 49number of 50
lookups and accesses 51size 319
changed pages threshold 320cleaners
asynchronous page 320, 330log space 160
client input and output client block size 353closed files
database 155tablespace 296
commandsoperating system
running user-defined with numeric results 42running user-defined with string results 43
syntax 4waddmon 5wdb2tlib 5wruntask 5
commitsminimum to group 327number initiated 57
committed private memory 348communication, connection status 220concurrency, decrease 402concurrent applications 325configuration
get database entry 604get database manager entry 607get DB2 administration server 602reset database 645reset database manager 647reset DB2 administration server 644update database 672update database manager 675update DB2 administration server 670
coordinating agentsmaximum on server 345
coordinator agents, concurrently executing 346counters, resetting 561
X-2 Version 2.1.0
cursorsblock 499open for application 501
Ddata, capture 692data reads 140data redistribution
for any node within a partitioned database 108for nodes within any partition 104for specified node group 105
database connection services, listing directory 618database heap 321
max allocated 78space used percentage 334
Database Managed Space (DMS) tablespace 111database manager
buffer pool asynchronous reads 190buffer pool asynchronous writes 191get configuration entry 607update configuration entries 675
database system monitor heap 349databases
activate 574applications wait for locks 396applications wait for locks during interval 397asynchronous buffer pool reads 186asynchronous read requests 165asynchronous reads per pool read 172asynchronous reads per pool write 173average buffer pool read time 180average buffer pool write time 181average sort time 466average synchronous data reads 182average synchronous data writes 183average time for direct read 177average time for direct write 178average time for I/O 179average time for synchronous I/O 184backup 581buffer pool asynchronous index reads 188buffer pool asynchronous index writes 189buffer pool asynchronous writes 187buffer pool copied from extended storage 193buffer pool copied to extended storage 194buffer pool I/O per second 202buffer pool index logical 197buffer pool index pages copied from extended storage 198buffer pool index pages copied to extended storage 199buffer pool index physical reads 200buffer pool index physical writes 201buffer pool logical reads 192buffer pool physical reads 195buffer pool physical writes 196buffer pool reads 163buffer pool waited for prefetch 203buffer pool writes 164cleaner invoked 154
databases (continued)connect frequency 54create sample 591data pages read 162DDL SQL statments 526, 529deactivate 593deadlocks during interval 392delete sample 596direct I/O time 214direct read request 156direct read time 204direct reads 157direct write request 158direct write time 205direct writes 159dynamic SQL statments 527exclusive escalations 402extended storage read/write ratio 206failed SQL statments 528, 530files closed 155force off connection 597get configuration entry 604invoke procedure 609issuing rollbacks 533issuing SELECT state 534lock escalations during interval 393lock list in use 394lock timeouts during interval 395locks held 398log space cleaners 160number of active sorts 465number of overflowed sorts 469number with connected applications 94page cleaner invoked 171page cleans 161pages for each cleaner 185percent buffer pool hit ratio, data+index 207percent buffer pool hit ratio, index 209percent package cache hit ratio 210percent SQL SELECT statments 531percentage of applications waiting for locks 399percentage of overflowed sorts 467physical buffer I/O time 215pool writes per pool read 174reset configuration 645reset manager configuration 647restart 648sectors read per direct read 175sectors written per direct write 176services 574sort heap allocated 468SQL statement rate of execution 535SQL UPDATE, INSERT, and DELETE statements 537state 425static SQL statement 536stop 593synchronous I/O 166synchronous I/O time 218synchronous index reads 167synchronous index writes 168synchronous read time 212
X-3Tivoli Manager for DB2 Reference Guide
Ind
ex
databases (continued)synchronous reads 169synchronous write time 213synchronous writes 170total pool physical 216, 217total sort number 471total sort time 470update configuration entries 672Update/Insert/Delete SQL statements 532
datajoinercheck status 359
DB2 administration servercreate 587delete 595get configuration 602get instance name 603list contents 622reset parameters 644start 658stop 665update configuration entries 670user account 656
DB2 security servicestart 664stop 669
DCS, See Database Connection Services 618DDL statements 147
activity for application 490examples of 504executed by application 503number executed by database 526percent executed by database 529
deadlocksnumber detected 55number detected during interval 392percent of rollbacks 400total for application 377
detection flag, sequential 336DMS, See Database Managed Space (DMS) tablespace 111dynamic SQL statements 527
Eenvironment
on endpoint 4environment variables, notation for xxievent monitors
maximum allowed 407number defined 407
explain tablescreate 589
extended storageindex pages copied from 198, 287index pages copied to 199, 288pages copied from 193pages copied to 194read/write ratio 206, 294
FFCM
buffers 341buffers free 222, 225buffers received 236buffers sent 238connection entries 342connection entries free 223, 226connection entries used 233FCM request blocks used 231maximum buffers used 232message anchors 340message anchors free 227message anchors used 234minimum request blocks free 228nodes in partition configuration 219percent buffers used 229percent connection entries used 230request blocks 343request blocks currently free 224request blocks used 235
files, primary log 324flag, sequential detection 336FORCE commands 597, 599
Hheap
database 321database system monitor 349query 352
history file, recovery 624
Iidle agents 347index pages
read into buffer pool 136written into buffer pool 138
index readssynchronous 167
index writessynchronous 168
input and outputaverage pool 261average synchronous 268buffer pool operations 152buffer pool per second 202, 286buffer pool time 179client block size 353direct time 214, 306number of synchronous for database 166percent total 302physical buffer pool time 215, 307servers 133, 332synchronous 184, 310
X-4 Version 2.1.0
input and output (continued)synchronous time 218, 312
instance priority 338instances
allocate resources 659checking status 39database connections
frequency 427local and remote 429
DB2 version 435finished transactions 431get DB2 administration server 603percentage of piped sorts rejected 472percentage of sort heap used 474post threshold sorts 475reset ECC counter 561start 659status 433stop 666total piped sorts rejected 477total ROLLBACK statements 431total sort heap allocated 476total SQL COMMIT statements 431
intent exclusive (IX) mode 630
Llist
applications 611backup and recovery file 614database connection services directory 618node directory 622
lock escalationscauses of exclusive lock escalations 402in monitoring interval 393number per connection 73total for application 379
lock listsin use 394maximum 326maximum storage 322
locklistspercent space used by application 44percent space used by database 84
locksapplications wait for 383applications waits in database 396applications waits in database during interval 397average held by connected applications 391average wait time 390exclusive escalations 402held by applications in database 398monitoring timeouts 62number held by application 385number of applications waiting 389percentage of applications in wait 399time unit of work waited for 387timeout during interval 395total wait time for application 381
locks (continued)total wait time within database 401
log buffer size 323log files, primary 324log pages
read 63total read and written 76written 64
log sequenceretrieve number 684retrieve time stamp 684
log size 160log space cleaners 160logical pages, read 443logical reads
buffer pool asynchronous 192buffer pool index 197index 284
logsdelaying writes 327primary
max space used 79percent space used 87space allocated 90
secondarymax space used 80number allocated 72percent space used 88when used 88
total space used 81
Mmemory
committed private 348piped sort allocation 354private, percentage used 351
message anchors, FCM 340messages
broadcasting 556buffer configuration 341sending multiple 557sending to notice groups 562
modesintent exclusive (IX) 630quiesce 630
monitordefaults 9targets 7
monitor heap size, database system 349monitoring collection, about 7monitors
conn: # of direct reads 124conn: # of direct writes 126conn: # of times agents are stolen 13conn: Application section inserts 481conn: Application section lookups 483conn: Application sorts 459conn: Application work load 15
X-5Tivoli Manager for DB2 Reference Guide
Ind
ex
monitors (continued)conn: Average # of sectors read per direct read 128conn: Average # of sectors written per direct write 130conn: Binds/precompiles attempted 485conn: Buffer pool time waited for prefetch (ms) 132conn: Commits 487conn: Data page writes 134conn: DDL SQL statements 489conn: Deadlocks found during last intervall 377conn: Dynamic SQL statements 491conn: Explicit commits 493conn: Explicit rollbacks 495conn: Failed SQL statements 497conn: Index page reads 136conn: Index page writes 138conn: Lock escalations during last interval 379conn: Lock wait time (s) 381conn: Lock waits 383conn: Locks held 385conn: Logical data reads 140conn: Maximum associated agents 17conn: Open block cursors 499conn: Percent buffer pool hit ratio, data+index 142conn: Percent buffer pool hit ratio, index 144conn: Percent DDL SQL 503conn: Percent locklist space used by application 44conn: Percent package cache hit ratio 146conn: Percent UID SQL 505conn: Pool read time (s) 148conn: Pool write time (s) 150conn: Rollbacks 507conn: Rows deleted 509conn: Rows inserted 511conn: Rows selected 513conn: Rows updated 515conn: Select SQL statements 517conn: Sort time (s) 461conn: SQL requests since last commit 519conn: Statement sorts 463conn: Static SQL statements 521conn: Total pool I/O time (s) 152conn: Total system CPU time used by agents 19conn: Total user CPU time used by agents 21conn: UOW lock wait time (s) 387conn: Update/Insert/Delete SQL 523Data replication Apply status 360DataJoiner status 359db: # of applications connected currently 46db: # of applications executing 47db: # of Apply lagging subscriptions 363db: # of binds/precomps attempted 48db: # of catalog cache heap full 49db: # of catalog cache inserts 50db: # of catalog cache lookups 51db: # of catalog cache overflow 52db: # of cleaners due to dirty threshold 154db: # of commit statements attempted 53db: # of connects since 1st db connect 54db: # of database files closed 155db: # of database tablespaces 406db: # of deadlocks detected 55
monitors (continued)db: # of direct read requests 156db: # of direct reads from database 157db: # of direct write requests 158db: # of direct writes to database 159db: # of event monitors 407db: # of internal automatic rebinds 56db: # of internal commits 57db: # of internal rollbacks 58db: # of internal rows deleted 59db: # of internal rows inserted 60db: # of internal rows updated 61db: # of invalid triggers 408db: # of lock timeouts 62db: # of log pages read 63db: # of log pages written 64db: # of log space cleaners invoked 160db: # of package cache inserts 65db: # of package cache lookup 66db: # of page cleans in an interval 161db: # of pages for each prefetch request 162db: # of pool reads 163db: # of pool writes 164db: # of prefetch requests in an interval 165db: # of rollback statements attempted 67db: # of rows deleted 68db: # of rows inserted 69db: # of rows selected 70db: # of rows updated 71db: # of secondary logs allocated currently 72db: # of synchronous I/O 166db: # of synchronous index reads 167db: # of synchronous index writes 168db: # of synchronous reads 169db: # of synchronous writes 170db: # of system tablespaces 409db: # of tables 410db: # of tablespaces 411db: # of tablespaces with LONG data 412db: # of triggers 413db: # of user indexes 414db: # of victim page cleaners invoked 171db: # of views 415db: Active sorts 465db: Agents associated with application 23db: app_ctl_heap_sz 315db: ApplHeapSz 316db: Applications in lock wait 389db: Apply failed subscriptions 364db: Apply requires full refresh 365db: Apply subscription status 369db: Apply subscriptions lag time 367db: Average # of async reads per pool read 172db: Average # of async writes per pool write 173db: Average # of pool writes per pool read 174db: Average # of sectors read per direct read 175db: Average # of sectors written per direct write 176db: Average direct read time (ms) 177db: Average direct write time (ms) 178db: Average lock wait time (s) 390db: Average locks held per application 391
X-6 Version 2.1.0
monitors (continued)db: Average pool I/O time (ms) 179db: Average pool read time (ms) 180db: Average pool write time (ms) 181db: Average sort time (ms) 466db: Average synchronous data read time (ms) 182db: Average synchronous data write time (ms) 183db: Average synchronous I/O (ms) 184db: Avg # of pages for each cleaner 185db: avg_appls 317db: Avg lock escalations per connection 73db: Buffer pool async data reads 186db: Buffer pool async data writes 187db: Buffer pool async index reads 188db: Buffer pool async index writes 189db: Buffer pool async read time (ms) 190db: Buffer pool async write time (ms) 191db: Buffer pool data logical reads 192db: Buffer pool data pages copied from extended
storage 193db: Buffer pool data pages copied to extended storage 194db: Buffer pool data physical reads 195db: Buffer pool data writes 196db: Buffer pool I/Os per second 202db: Buffer pool index logical reads 197db: Buffer pool index pages copied from extended
storage 198db: Buffer pool index pages copied to extended
storage 199db: Buffer pool index physical reads 200db: Buffer pool index writes 201db: Buffer pool time waited for prefetch (ms) 203db: buffpage 318db: Capture errors 371db: Capture lag 372db: Capture pruning 373db: catalogcache_sz 319db: chngpgs_thresh 320db: Committed statements per second 525db: dbheap 321db: DDL SQL statements 526db: Deadlocks found during last interval 392db: Direct read time (ms) 204db: Direct write time (ms) 205db: Dynamic SQL statements 527db: Extended storage read/write ratio 206db: Failed SQL statements 528db: Internal rollback due to deadlock 74db: Last backup timestamp 75db: Lock escalations during last interval 393db: Lock list in use (bytes) 394db: Lock timeouts during last interval 395db: Lock waits 396db: Lock waits in an interval 397db: locklist 322db: Locks held 398db: Log I/O 76db: logbufsz 323db: logprimary 324db: Max # of concurrent connections 77db: Max database heap allocated 78
monitors (continued)db: Max primary log space used 79db: Max secondary log space used 80db: Max total log space used 81db: maxappls 325db: Maximum agents associated with application 24db: Maximum coordinating agents 25db: maxlocks 326db: mincommit 327db: newlogpath 329db: num_iocleaners 330db: num_ioservers 332db: Number of all invalid packages 540db: Number of invalid SYSTEM packages 541db: Number of invalid user packages 542db: pckcachesz 333db: Percent application in lock wait 399db: Percent buffer pool hit ratio, data+index 207db: Percent buffer pool hit ratio, index 209db: Percent catalog cache hit ratio 210db: Percent connections used 82db: Percent DDL SQL 529db: Percent deadlock rollbacks 400db: Percent failed SQL 530db: Percent internal rollbacks due to internal deadlocks 83db: Percent locklist space used by database 84db: Percent package cache hit ratio 85db: Percent select SQL 531db: Percent sort overflowed 467db: Percent space used in databaseheap 334db: Percent UID SQL 532db: Percent used in primary log 87db: Percent used in secondary log 88db: Primary log space allocated 90db: restore_pending 335db: Rollbacks per second 533db: Select SQL statements 534db: seqdetect 336db: Sort heap allocated 468db: Sort overflows 469db: sortheap 337db: SQL statements per second 535db: Static SQL statements 536db: Synchronous read time (ms) 212db: Synchronous write time (ms) 213db: Time waited on locks 401db: Total direct I/O time (ms) 214db: Total exclusive lock escalations 402db: Total pool physical I/O (ms) 215db: Total pool physical read (ms) 216db: Total pool physical write (ms) 217db: Total sort time (ms) 470db: Total sorts 471db: Total synchronous I/O time (ms) 218db: Update/Insert/Delete SQL 537db: User-defined SQL (numeric result) 416db: User-defined SQL (string result) 417DB2 database state 425DB2 ECC monitoring communication agent status 38DB2 instance status 39DB2 server accumulated connections 427
X-7Tivoli Manager for DB2 Reference Guide
Ind
ex
monitors (continued)DB2 server current connection 429DB2 server finished transactions 431DB2 server status 433DB2 server version 435DB2 SNMP agent status 41dbms: # of idle agents 26, 91dbms: # of local connections 92dbms: # of local connections executing 93dbms: # of local databases with current connections 94dbms: # of piped sorts accepted 95dbms: # of piped sorts requested 96dbms: # of remote connections 97dbms: # of remote connections executing 98dbms: # of times agents are stolen 27dbms: Agent creation ratio 28dbms: agentpri 338dbms: Agents registered 29dbms: Agents waiting for a token 30dbms: aslheapsz 339dbms: Committed private memory 99dbms: fcm_num_anchors 340dbms: fcm_num_buffers 341dbms: fcm_num_connect 342dbms: fcm_num_rqb 343dbms: Last reset timestamp 100dbms: max_agents 344dbms: max_coordagents 345dbms: maxcagents 346dbms: Maximum agents registered 31dbms: Maximum agents waiting 32dbms: Maximum idle agents in the agent pool 347dbms: Minimum committed private memory 348dbms: mon_heap_sz 349dbms: num_poolagents 350dbms: Percent agents waiting 33dbms: Percent piped sort hit ratio 101dbms: Percent piped sorts rejected 472dbms: Percent private memory used 351dbms: Percent sort heap allocated 474dbms: Percent total connections executing 34dbms: Post threshold sorts 475dbms: query_heap_sz 352dbms: rqrioblk 353dbms: sheapthres 354dbms: Sort heap allocated 476dbms: sqlstmtsz 355dbms: Start database manager timestamp 103dbms: Total piped sorts rejected 477dbp: # of FCM nodes 219dbp: Connection status 220dbp: FCM buffers currently free 222dbp: FCM connection entries currently free 223dbp: FCM request blocks currently free 224dbp: Minimum FCM buffers free 225dbp: Minimum FCM connection entries free 226dbp: Minimum FCM message anchors free 227dbp: Minimum FCM request blocks free 228dbp: Percent FCM buffers currently used 229dbp: Percent FCM connection entries currently used 230dbp: Percent FCM request blocks currently used 231
monitors (continued)dbp: Percent maximum FCM buffers used 232dbp: Percent maximum FCM connection entries used 233dbp: Percent maximum FCM message anchors 234dbp: Percent maximum FCM request blocks used 235dbp: Total buffers received 236dbp: Total buffers sent 238dbpg: Data redistribution status 104dbpg: Data redistribution status for a nodegroup 105dbpg: DB2 local nodes status 107dbpg: Partitioned database data redistribution status 108dbpg: Percentage differential in row distribution of a
table 109Maximum number of agents allowed to register at the same
time 437Maximum number of agents registered at the same
time 439SNA link status 361table: # of rows 418table: Overflow accesses 544table: Reorg needed 546table: Rows read per second 549table: Rows written per second 551tbsp: # of direct read requests 240tbsp: # of direct reads from database 242tbsp: # of direct write requests 244tbsp: # of direct writes to database 246tbsp: # of pool reads 248tbsp: # of pool writes 249tbsp: # of synchronous index reads 251tbsp: # of synchronous index writes 252tbsp: # of synchronous reads 253tbsp: # of synchronous writes 255tbsp: # of tables 420tbsp: Average # of sectors read per direct read 257tbsp: Average # of sectors written per direct write 258tbsp: Average direct read time (ms) 259tbsp: Average direct write time (ms) 260tbsp: Average pool I/O time (ms) 261tbsp: Average pool read time (ms) 262tbsp: Average pool write time (ms) 263tbsp: Average synchronous data read time (ms) 264tbsp: Average synchronous data write time (ms) 266tbsp: Average synchronous I/O time (ms) 268tbsp: Buffer pool async data reads 269tbsp: Buffer pool async data writes 270tbsp: Buffer pool async index reads 271tbsp: Buffer pool async index writes 273tbsp: Buffer pool async read time (ms) 275tbsp: Buffer pool async write time (ms) 276tbsp: Buffer pool data logical reads 277tbsp: Buffer pool data pages copied from extended
storage 279tbsp: Buffer pool data pages copied to extended
storage 280tbsp: Buffer pool data physical reads 281tbsp: Buffer pool data writes 282tbsp: Buffer pool I/Os per second 286tbsp: Buffer pool index logical reads 284tbsp: Buffer pool index pages copied from extended
storage 287
X-8 Version 2.1.0
monitors (continued)tbsp: Buffer pool index pages copied to extended
storage 288tbsp: Buffer pool index physical reads 289tbsp: Buffer pool index writes 290tbsp: Direct read time 292tbsp: Direct write time (ms) 293tbsp: Extended storage read/write ratio 294tbsp: File closed 296tbsp: Percent buffer pool hit ratio, data+index 297tbsp: Percent buffer pool hit ratio, index 299tbsp: Percent prefetch satisfied 301tbsp: Percent space used in DMS tablespace 111tbsp: Percent total I/O 302tbsp: Prefetch requests in an interval 303tbsp: Space used in SMS tablespace 113tbsp: Synchronous read time (ms) 304tbsp: Synchronous write time (ms) 305tbsp: Tablespace status 114tbsp: Total direct I/O time (ms) 306tbsp: Total pool physical I/O time (ms) 307tbsp: Total pool physical read time (ms) 308tbsp: Total pool physical write time (ms) 309tbsp: Total synchronous I/O 310tbsp: Total synchronous I/O time (ms) 312TCP/IP communication link status 362Total Logical bytes read by DB2 server for all active
databases 441Total logical pages read by DB2 server for all active
databases 443Total physical bytes read by DB2 server 445Total physical bytes written by DB2 server for all active
databases 447Total physical pages written by DB2 server for all active
databases 449Total rows selected returned by DB2 server for all active
databases 451Total SQL statements handled by DB2 server for all active
databases 453Total SQL statements received by DB2 server for all active
databases 455user: # of tables 421User-defined OS command (numeric results) 42User-defined OS command (string result) 43
Nnewlogpath, value 329node directory, list 622nodes
FCM 219number of inactive 107
noticessending 562
Ooperating system command
running user-defined with numeric results 42running user-defined with string results 43
Ppackage cache
hit ratio 85, 146, 210inserts 65lookups 66performance 147size 333
packagesinvalid 540invalid SYSTEM 541rebind 632recreate without bind 635user-owned invalid 542
page cleanersasynchronous 320, 330invoked 154victim 171written 185
page cleans 161pages, physically written 449pages threshold, changed 320parameter, reset 644partition
connection status 220FCM buffers free 222, 225FCM connection entries free 223, 226FCM message anchors free 227FCM request blocks currently free 224maximum FCM buffers used 232maximum FCM connection entries used 233maximum FCM message anchors used 234minimum FCM request blocks free 228percent FCM buffers used 229percent FCM connection entries used 230percent FCM request blocks used 231, 235total buffers received 236total buffers sent 238
partition groupinactive nodes 107row distribution differential 109
physical readsbuffer pool 216, 281, 308index 200, 289
physical writesbuffer pool 217, 282, 309index 201
piped sortsaccepted 95hit ratio 101requested 96total rejected 477
pool, buffer 317pool size, buffer 318
X-9Tivoli Manager for DB2 Reference Guide
Ind
ex
prefetchbuffer pool waited for 203pages read per 162percent satisfied 301requests 165requests in interval 303
primary log files 324private memory
commited to instance 99committed 348percentage used 351
procedure, invoke 609prune
after capture stop 691capture table 686
Qquery heap 352quiesce modes 630
Rreads
applicationaverage direct 128data pages 140direct 124index pages physical 136
average sector 125database
asynchronous buffer pool 186average asynchronous 172average buffer pool time 180average direct 175average direct time 177average synchronous time 182direct 156, 157direct time for database 204index page asynchronous 188index page asynchronous time 190physical 195synchronous 169synchronous time 212
direct 292synchronous time 304tablespace
average direct 257average pool time 262average synchronous time 264buffer pool asynchronous 269buffer pool time 275data sector 240direct 242direct time 259index page asynchronous 271index page synchronous 251
reads (continued)tablespace (continued)
logical 277pool 248synchronous 253
rebindsdefined 56internal automatic 56number attempted 48number necessary 540, 541, 542package 632without bind file 635
recompiles 56recovery, list file 614recovery history file, delete entries 624remote administration 644reorg, table 640replication communication, monitoring links 361request blocks, FCM 343reset, parameter 644RESTORE PENDING status 335rollbacks
internal 58number due to deadlocks 74percent due to deadlocks 83, 400statements attempted 67total attempted 507, 533
rowsaccess to overflowed 544deleted 68deleted by application 509inserted 69inserted by application 511internally updated 61number in table 418percentage differential between distributed 109redistribution status of node groups 104redistribution status of specified node group 105selected 70selected by application 513selected by database 451updated 71updated by application 515
Ssample database
create 591delete 596
sectorsnumber read for database 157number written for database 159read 125read per direct read 175reads requested for database 156write 127writes requested for database 158written per direct write 176
sequential detection flag 336
X-10 Version 2.1.0
serversinput and output 133start DB2 administration 658
services, database 574shells
additional info 3defined 2establishing Tivoli environment 3setting up Tivoli on UNIX 3setting up Tivoli on Windows 3Tivoli-supported UNIX 2Tivoli-supported Windows 2
sizealter buffer pool 576application support layer heap 339catalog cache 319client input and output block 353database system monitor heap 349log buffer 323package cache 333query heap 352sort heap 337SQL statement 355
SNA link, check status 361sort heap
allocated for database 468determine space used 465improving performance 477size 337threshold 354
sortsaverage time for database 466heap size 337improving performance 95, 96, 101in seconds 461number of active in database 465number overflowed 469number performed 459percentage of heap used 474percentage overflowed 467post threshold 475rejected piped 472, 477sort heap allocated 468sort heap full 467statement 463total number in database 471total sort heap 476total time for executions 470
SQL statementsapplication
static 521COMMIT 487
number attempted 53total for instances 431
DDL 489, 526DELETE 505, 523, 532dynamic 491, 527failed 497INSERT 505, 523, 532number failed 528percent DDL SQL 503
SQL statements (continued)percent failed 530percent of DDL SQL 529rate executed 535requests submitted by application 519ROLLBACK 431rollbacks 495run user-defined
numeric result 416string result 417
section inserts by application 481section lookups by application 483SELECT 531, 534
executed by application 517size 355sorts 463static 536total handled by DB2 server 453total received by DB2 server 455UPDATE 505, 523, 532Update/Insert/Delete 505, 537
statement text, see SQL statements 355statistics, update for table 650status, RESTORE PENDING 335Structured Query Language, See SQL statements 481subscription, See apply program 368synchronous
data reads 182data writes 183I/O for database 166I/O time 184physical index page reads 167physical index page writes 168read time 212reads 169tablespace
synchronous time 304write time 213, 305writes 170
syntaxcommand line characters 4
System Managed Space 113System Managed Space (SMS) tablespace 113
Ttables
calculate statistics 640check for reorg needs 546explain 589number in database 410number in tablespace 420number owned by user 421reading from rows rate 549reorganize 637update statistics 650writing to rows rate 551
tablespacesaverage direct read time 259
X-11Tivoli Manager for DB2 Reference Guide
Ind
ex
tablespaces (continued)average direct write time 260average pool I/O time 261average pool read time 262average pool write time 263average sectors read per direct read 257average sectors written per direct write 258average synchronous data read time 264average synchronous data write time 266average synchronous I/O 268buffer pool async data reads 269buffer pool async data writes 270buffer pool async index reads 271buffer pool async index writes 273buffer pool async read time 275buffer pool async write time 276buffer pool data logical 277buffer pool I/O per second 286buffer pool index pages copied from extended storage 287buffer pool index pages copied to extended storage 288buffer pool index physical reads 289buffer pool index writes 290buffer pool pages copied from extended storage 279buffer pool pages copied to extended storage 280buffer pool physical reads 281, 284buffer pool physical writes 282direct I/O time 306direct read request 240direct read time 292direct reads from database 242direct write time 293direct writes from database 244direct writes to database 246extended storage read/write ratio 294file closed 296number in database 411number with LONG data 412percent buffer pool hit ratio, data+index 297percent buffer pool hit ratio, index 299percent prefetch satisfied 301percent total I/O 302physical buffer I/O time 307pool reads 248pool writes 249prefetch request 303quiesce 627status 114synchronous I/O 310synchronous I/O time 312synchronous index reads 251synchronous index writes 252synchronous read time 304synchronous reads 253synchronous write time 305synchronous writes 255total DMS 406total pool physical 308, 309total SMS 409
target table, refresh 678targets, monitor 7
task librariesabout 553data replication 677database 571monitor and administration 555
tasksECC_Activate_Database 574ECC_Alter_Bufferpool 576ECC_Apply_Start 678ECC_Apply_Stop 682ECC_Backup_Database 581ECC_Broadcast_Message 556ECC_Capture_Get_Log_Seq 684ECC_Capture_Prune 686ECC_Capture_Reinit 688ECC_Capture_Resume 690ECC_Capture_Start 692ECC_Capture_Stop 695ECC_Capture_Suspend 697ECC_Configure_TEC_Classes 558ECC_Create_Admin_Server 587ECC_Create_Explain_Tables 589ECC_Create_Sample_Database 591ECC_Deactivate_Database 593ECC_Drop_Admin_Server 595ECC_Drop_Sample_Database 596ECC_Force_All_Applications 597ECC_Force_Application 599ECC_Get_Admin_Configuration 602ECC_Get_Admin_Server_Instance 603ECC_Get_Database_Configuration 604ECC_Get_Database_Manager_Configuration 607ECC_Invoke_Stored_Procedure 609ECC_List_Applications 611ECC_List_Backup_Recovery_File 614ECC_List_DCS_Applications 618ECC_List_Node_Directory 622ECC_Prune_Recovery_History 624ECC_Quiesce_Tablespaces 627ECC_Rebind_All_Packages 632ECC_Rebind_Package 635ECC_Reorganize_Table 637ECC_Reorgchk 640ECC_Reset_Admin_Configuration 644ECC_Reset_Counters 561ECC_Reset_Database_Configuration 645ECC_Reset_Database_Manager_Configuration 647ECC_Restart_Database 648ECC_Run_Statistics 650ECC_Send_Notice 562ECC_Set_Admin_Server_ID 656ECC_Set_Up_Monitoring_Agent 564ECC_Start_Admin_Server 658ECC_Start_DB2 659ECC_Start_DB2_NT_Security 664ECC_Start_DB2SNMP_Agent 566ECC_Start_Monitoring_Agent 568ECC_Stop_Admin_Server 665ECC_Stop_DB2 666ECC_Stop_DB2_NT_Security 669ECC_Stop_DB2SNMP_Agent 569
X-12 Version 2.1.0
tasks (continued)ECC_Stop_Monitoring_Agent 570ECC_Update_Admin_Configuration 670ECC_Update_Database_Configuration 672ECC_Update_Database_Manager_Configuration 675
TCP/IP link, status 362text, SQL statement 355threshold
changed pages 320sort heap 354
timestampfor backups 75for database manager 103for monitor counters 100
Tivoli Enterprise Console, configure with task 558Tivoli environment
on endpoint 4triggers
causing row insertions 60number in database 413total invalid in database 408
Uunit of work
commits 525number of rows 373time waited for locks 387
UNIXrunning Tivoli commands 2
Update/Insert/Delete SQL statementsnumber executed by application 523percent executed by application 505percent executed by database 532
usersforce off 597force off specific 599indexes created 414set DB2 administration server ID 656tracking tables 421
Vvariables, environment xxiversion, get DB2 server 435victim page cleaners, invoked 171views, number in database 415
Wwaddmon command 5wdb2tlib command 5Windows
running Tivoli commands 2
writesasynchronous buffer pool 187asynchronous index 189average asynchronous 173average buffer pool 181average direct 178, 260average per pool read 174average pool 263average sectors 258average sectors per direct write 176average synchronous data 183, 266buffer pool async 270buffer pool async index 273buffer pool async time 276buffer pool asynchronous 191direct 293direct for database 158, 159direct time for database 205index 290index pages 138number of direct 126per page cleaner invoked 185physical 196pool 249sector 127sectors direct 130synchronous 170, 255synchronous index 252synchronous time 213, 305tablespace
direct 246tablespace direct 244
wruntask command 5
X-13Tivoli Manager for DB2 Reference Guide
Ind
ex
X-14 Version 2.1.0
Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.
GC32-0452-01
