usdownloads.quest.com.edgesuite.netusdownloads.quest.com.edgesuite.net/Repository/support... ·...

®

User GuideFoglight Catridge for DB2 LUW

© 2007 Quest Software, Inc. ALL RIGHTS RESERVED.This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: [email protected]

Refer to our web site for regional and international office information.

TrademarksQuest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

DisclaimerThe information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

User Guide March 2007 Software Version - 1.4

http://www.quest.com

mailto:[email protected]

Table of Contents

Preface ..................................................................................................................................................................9About This Guide............................................................................................................................................................ 10

How to Use this Guide........................................................................................................................................... 10Who Should Read this Guide ................................................................................................................................ 10Conventions Used in this Guide ............................................................................................................................ 11

Related Documentation ................................................................................................................................................. 12About Quest Software, Inc. ............................................................................................................................................ 13

DB2 Agent...........................................................................................................................................................15DB2 Agent ...................................................................................................................................................................... 16

The DB2 agent monitors the collection of data by the DB2 web-enabled relational database management system.16About the DB2 Agent............................................................................................................................................. 16Sort heap size........................................................................................................................................................ 16

Using DB2 Agent Startup Parameters............................................................................................................................ 22Setting DB2 Connection Details ............................................................................................................................ 22Setting the DB2 Data Management Parameters ................................................................................................... 23Setting Data Purging Parameters.......................................................................................................................... 25

DB2 Agent Tables .......................................................................................................................................................... 28Application_Connection Table............................................................................................................................... 30Application_IO Table ............................................................................................................................................. 34Application_Locking Table..................................................................................................................................... 37Application_Memory Table .................................................................................................................................... 40Application_Sorting Table...................................................................................................................................... 43Client_Connection Table ....................................................................................................................................... 44Client_IO Table...................................................................................................................................................... 48Client_Locking Table ............................................................................................................................................. 52

iv Foglight Cartridge for DB2 LUWUser Guide

Client_Memory Table............................................................................................................................................. 53Client_Sorting Table .............................................................................................................................................. 56Database_Bufferpools Table ................................................................................................................................. 58Database_Connection Table ................................................................................................................................. 64Database_HADR Table ......................................................................................................................................... 68Database_IO Table................................................................................................................................................ 78Database_Locking Table ....................................................................................................................................... 85Database_Logging Table....................................................................................................................................... 86Database_Memory Table....................................................................................................................................... 89Database_Sorting Table ........................................................................................................................................ 93Database_Summary Table .................................................................................................................................... 96Database_Tables Table......................................................................................................................................... 99Database_Tablespaces Table ............................................................................................................................. 102Database_TablespacesTopBP Table .................................................................................................................. 108Instance_Agent Table .......................................................................................................................................... 115

DB2 Agent Investigations ............................................................................................................................................. 119Investigating Application Locks............................................................................................................................ 119Investigating Application Memory ........................................................................................................................ 121Investigating Application Sorting.......................................................................................................................... 122Investigating Application SQL Statistics............................................................................................................... 123Investigating Database Buffer Pool Usage .......................................................................................................... 125Investigating Database Internal Statistics ............................................................................................................ 125Investigating Database Connectivity .................................................................................................................... 126Investigating Database IO.................................................................................................................................... 127Investigating Database Log IO............................................................................................................................. 128Investigating Database Log Space ...................................................................................................................... 128Investigating Database Manager Resources ....................................................................................................... 129Investigating Database Memory .......................................................................................................................... 130Investigating Database Memory Application Sections ......................................................................................... 131Investigating Database Memory Catalog Cache.................................................................................................. 132Investigating Database Memory Database Heap ................................................................................................ 133Investigating Database Memory Package Cache ................................................................................................ 134Investigating HADR.............................................................................................................................................. 135Investigating Tablespace Bufferpool Hit Rates .................................................................................................... 136Investigating Tablespace Space .......................................................................................................................... 136

Table of Contents v

DB2 Agent Views ..........................................................................................................................................................138DB2_Database_Manager_Overview Graph.........................................................................................................138DB2_Database_Overview Table ..........................................................................................................................139DB2_HADR_Overview Table ...............................................................................................................................142DB2_Application_Locking Table ..........................................................................................................................143DB2_Application_Memory Table..........................................................................................................................144DB2_Application_SQL_Statistics Table ...............................................................................................................146DB2_Application_Sorting Table ...........................................................................................................................149DB2_Bufferpool_Analysis Graph..........................................................................................................................150DB2_Bufferpool_Detail Table...............................................................................................................................152DB2_Client_Top_CPU_Usage Table ...................................................................................................................154DB2_Client_Top_Cache_Usage Table ................................................................................................................155DB2_Client_Top_Lock_Usage Table ...................................................................................................................156DB2_Client_Top_Sort_Usage Table ....................................................................................................................157DB2_Database_Connection_Analysis Graph ......................................................................................................158DB2_Database_Connection_Detail Table............................................................................................................159DB2_Database_Connection_Internal_Statistics Graph .......................................................................................160DB2_Database_Connection_SQL_Statistics Table .............................................................................................161DB2_Database_IO_Agent_Analysis Table ..........................................................................................................163DB2_Database_IO_Analysis Graph.....................................................................................................................164DB2_Database_IO_Async Table .........................................................................................................................165DB2_Database_IO_Detail Table ..........................................................................................................................167DB2_Database_IO_Direct Table..........................................................................................................................168DB2_Database_IO_Log Graph ............................................................................................................................170DB2_Database_Lock_Analysis Table ..................................................................................................................171DB2_Database_Log_Analysis Table....................................................................................................................173DB2_Database_Log_Space Graph......................................................................................................................175DB2_Database_Manager_Agents Table..............................................................................................................176DB2_Database_Memory_Analysis Graph............................................................................................................178DB2_Database_Memory_Application_Sections Graph........................................................................................179DB2_Database_Memory_Catalog_Cache Graph ................................................................................................180DB2_Database_Memory_Database_Heap Graph ...............................................................................................181DB2_Database_Memory_Detail Table.................................................................................................................182DB2_Database_Memory_Package_Cache Graph...............................................................................................184DB2_Database_Sort_Analysis Table ...................................................................................................................185

vi Foglight Cartridge for DB2 LUWUser Guide

DB2_Tables_Top_Accessed Table ..................................................................................................................... 187DB2_Tablespace_Top_Bufferpool_Details Table................................................................................................ 188DB2_Tablespace_Top_Bufferpool_HitRates Graph ............................................................................................ 190DB2_Tablespace_Top_Space_Details Table ...................................................................................................... 191DB2_Tablespace_Top_Space_Utilization Graph ................................................................................................ 193

DB2 Agent Rules .......................................................................................................................................................... 194DB2_Agent_Lock_Waits Rule.............................................................................................................................. 194DB2_Agent_Token_Waits Rule ........................................................................................................................... 195DB2_Agent_Utilization Rule................................................................................................................................. 196DB2_Agents_Stolen Rule .................................................................................................................................... 197DB2_Appl_CPU_Time Rule................................................................................................................................. 198DB2_Appl_Lock_Wait Rule.................................................................................................................................. 199DB2_Appl_Sort_Time Rule.................................................................................................................................. 200DB2_Buffer_Pool_Ratio Rule .............................................................................................................................. 201DB2_Catalog_Cache_Heap Rule ........................................................................................................................ 202DB2_Catalog_Cache_Oflow Rule........................................................................................................................ 203DB2_Catalog_Cache_Ratio Rule ........................................................................................................................ 204DB2_Client_CPU_Time Rule............................................................................................................................... 205DB2_Client_Lock_Wait Rule................................................................................................................................ 206DB2_Client_Sort_Time Rule................................................................................................................................ 207DB2_Connection_Util Rule .................................................................................................................................. 208DB2_Db_HADR_CngstdTO Rule ........................................................................................................................ 209DB2_Db_HADR_DisconTO Rule......................................................................................................................... 210DB2_Db_HADR_LogGapEx Rule........................................................................................................................ 211DB2_Db_HADR_MissedHB Rule ........................................................................................................................ 212DB2_Db_HADR_State Rule ................................................................................................................................ 213DB2_Deadlocks_Detected Rule .......................................................................................................................... 214DB2_Index_Ratio Rule ........................................................................................................................................ 215DB2_Lock_List_Util Rule ..................................................................................................................................... 216DB2_Lock_Timeouts Rule ................................................................................................................................... 217DB2_Log_Secondary_Util Rule ........................................................................................................................... 218DB2_Log_Space_Util Rule .................................................................................................................................. 219DB2_Package_Cache_Oflow Rule ...................................................................................................................... 220DB2_Package_Cache_Ratio Rule....................................................................................................................... 221DB2_Sort_Heap_Util Rule ................................................................................................................................... 222

Table of Contents vii

DB2_Sort_Oflow Rule ..........................................................................................................................................223DB2_Tablespace_Util Rule ..................................................................................................................................224

DB2 Monitor Agent ..........................................................................................................................................219DB2Monitor Agent.........................................................................................................................................................220

About the DB2Monitor Agent................................................................................................................................220Using DB2 Monitor Agent Startup Parameters .............................................................................................................222

Setting DB2Monitor Connection Details ...............................................................................................................222Setting the DB2Monitor Connection Parameters .................................................................................................225Setting the DB2Monitor Data Management Parameters ......................................................................................226Editing the DB2Monitor Sampling Frequency or Data Purging Parameters.........................................................227Setting Log Filter and Instance Discovery Parameters ........................................................................................229Editing the DB2Monitor Installation Path Directory Parameters...........................................................................231

DB2Monitor Agent Tables .............................................................................................................................................233DB2DiagLogFiles Table .......................................................................................................................................233DB2DiagLogMessage Table ................................................................................................................................233DB2Instances Table .............................................................................................................................................234DB2ProcessDetails Table ....................................................................................................................................234DB2ProcessTotals Table......................................................................................................................................235DB2ServerTotals Table ........................................................................................................................................236

DB2Monitor Agent Investigations..................................................................................................................................237Investigating the DB2 Server................................................................................................................................237

DB2Monitor Agent Views ..............................................................................................................................................238DB2Server_Overview Graph................................................................................................................................238DB2Instance_Details Graph.................................................................................................................................239DB2Process_Details Graph .................................................................................................................................240

DB2Monitor Agent Rules...............................................................................................................................................242DB2_Availability Rule ...........................................................................................................................................242DB2_Diag_Log_Message Rule ............................................................................................................................242DB2_Diag_Log_File_Size Rule............................................................................................................................243

Glossary............................................................................................................................................................245

viii Foglight Cartridge for DB2 LUWUser Guide

Preface

Contents

About This GuideRelated DocumentationAbout Quest Software, Inc.

10 Foglight Cartridge for DB2 LUWUser Guide

About This GuideThis manual describes the steps required to configure and use the Foglight Cartridge for DB2 LUW v1.4.

For platform support information, and known issues, please see the Foglight Cartridge for DB2 LUW v1.4 Release Notes.

The manual consists of the following sections:

Preface - Provides overview of this Guide, conventions used, and the related documentation available.

Chapter 1 - DB2 Agent: Provides an overview of the DB2 agent.

Chapter 2 - DB2 Monitor Agent: Provides an overview of the DB2Monitor agent.

How to Use this GuideThere is a chapter for each of the agents installed with the Foglight Cartridge for DB2 LUW v1.4. Refer to the chapters about each individual agent to obtain information on that agent and its properties.

Who Should Read this GuideThis manual is written for system administrators and other technical personnel responsible for installation, deployment, and administration of the Foglight Cartridge for DB2 LUW v1.4.

Preface 11

Conventions Used in this Guide

Path VariablesThroughout this document, directory paths are referred to based on standard environment variables expected for the root location (for example, DB2_HOME is equivalent to the DB2 directory). Typically, these are denoted in UNIX path structure

ELEMENT CONVENTION

Courier New Font Source code, scriptsCommands you enterPath names, files names, URLs, and programsConsole output

Bold Text Indicates interface elements the user should select.

Italic Text Provides additional comments about a procedure.The names of other documents referenced in this manual.

Bold Italic Text Introduces a series of procedures.

Used to provide Best Practice information. A best practice details the recommended course of action for the best result.

Used to highlight processes that should be performed with care.

+ Indicates keys on the keyboard are to be used together.

> Indicates you must select elements in exact sequence.


using forward slashes / to separate directories. Note that the variable delimiters for UNIX ($) and Windows (% %) are omitted unless required for clarity. In all cases FGLHOME represents the Foglight Client installation directory on the monitored host.

AssumptionsThis manual assumes that you have a sound understanding of your production environment, and of the architecture of your DB2 server environment. Some operations require DB2 administrative and root/administrator access to configuration files and you should be comfortable editing configuration files for those components. You may need to use scripts to perform certain operations.

This manual does not contain instructions for installing the Foglight Management Server or the Foglight Client; nor does it contain general information on how to use Foglight. Please refer to the Foglight Administration Guide, the Foglight Installation Guide, the Foglight Operations Console User Guide, and the Foglight Management Server online help for the appropriate version.

Related DocumentationTwo additional documents provide information related to the Foglight Cartridge for DB2 LUW v1.4:

• Release Notes for this Cartridge version

• Online help for this Cartridge version

Preface 13

About Quest Software, Inc.Quest Software, Inc. delivers innovative products that help organizations get more performance and productivity from their applications, databases, and Windows infrastructure. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 18,000 customers worldwide meet higher expectations for enterprise IT. Quest Software can be found in offices around the globe and at www.quest.com.

Contacting Quest Software

Refer to our web site for regional and international office information.

Contacting Quest SupportQuest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at: http://support.quest.com

From SupportLink, you can do the following:

• Quickly find thousands of solutions (Knowledgebase articles/documents).

• Download patches and upgrades.

• Seek help from a Support engineer.

• Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

Email [email protected]

Mail Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA

Web site www.quest.com


mailto:[email protected]


http://support.quest.com

http://support.quest.com

http://support.quest.com/pdfs/Global Support Guide.pdf


1

DB2 Agent

Contents

DB2 AgentUsing DB2 Agent Startup ParametersDB2 Agent TablesDB2 Agent InvestigationsDB2 Agent ViewsDB2 Agent Rules


DB2 AgentThe DB2 agent monitors the collection of data by the DB2 web-enabled relational database management system.

About the DB2 AgentData is collected as follows:

• Database Manager - Provides statistics for the active database manager

• Database - Records statistics for all active databases

• Client - Compiles data about each active database connection

• Applications - Compiles data about all active applications connected to a database.

Foglight uses this information to analyze the efficiency of the DB2 database, enabling you to enhance both system and database performance.

Sort heap sizeAn important factor in the performance of any sort is the size of its sort heap, which is determined by these parameters:

SORTHEAP Database Configuration ParameterThis parameter defines the amount of memory to be used as a work area for each sort. Specifically, this parameter defines the maximum amount of private memory to be used for private sorts or the maximum amount of shared memory to be used for shared sorts.

A private sort is performed by an agent assigned to work for a specific application as a result of a connect request or, within a parallel environment, a new SQL request. When the application performs a sort, the database manager provides the sort heap from the agent’s private memory. (The database manager allocates private memory to the agent when the agent is assigned to work for the application.)

A shared sort is performed by agents working on behalf of an application within a partitioned environment or within an instance in which the INTRA_PARALLEL parameter is turned on. When the application requires a sort, the database manager allocates the sort heap from the database shared memory. The agents then share the sort heap to coordinate the sort.

Chapter 1 17DB2 Agent

SHEAPTHRES Database Manager Configuration ParameterThis parameter defines the total amount of memory to be used as the work area for all private sorts across the instance and for all shared sorts in the database at any one time.

For private sorts, this parameter is an instance-wide soft limit on the total amount of memory that all private sorts can use at any given time. That is, when the total private sort memory used in the instance reaches this limit, the database manager continues to allocate sort heap to private sorts. However, the size of each sort heap is reduced considerably.

For shared sorts, this parameter is a database-wide hard limit on the total amount of memory consumed by sorts at any given time. That is, when total sort heap for the database reaches this limit, the database manager no longer allocates sort heap space to do sorts until the total shared sort memory falls below the SHEAPTHRES limit.

A private sort is performed by an agent assigned to work for a specific application as a result of a connect request or, within a parallel environment, a new SQL request. When the application requires a sort, the database manager provides the sort heap from the agent’s private memory. (The database manager allocates private memory to the agent when the agent is assigned to work for the application.)

A shared sort is performed by agents working on behalf of an application within a partitioned environment or within an instance in which the INTRA_PARALLEL parameter is turned on. When the application requires a sort, the database manager allocates the sort heap from the database shared memory. The agents then share the sort heap to coordinate the sort.

A sort includes these phases:

• The actual sort process—If the information being sorted cannot fit into the sort heap, some information is written to temporary database tables. This incident is called a sort overflow. Sorts that do not overflow perform better than those that do.

• Return of the sorted rows—If sorted information can be returned directly without requiring a temporary table to store the final, sorted list of data, the sort is referred to as a piped sort. If the sorted information requires a table to temporarily store the data before it is returned, the sort is referred to as a non-piped sort. A piped sort always performs better than a non-piped sort.

Sorting problems, such as overflows, non-piped sorts, less-than-optimal sort heap allocation size, might indicate a need to adjust the SORTHEAP and SHEAPTHRES parameters. However, these problems might signal a need to tune the SQL within the application.


ASPsThe DB2 agent is shipped with agent startup parameters that dictate how the agent will perform.

Using DB2 Agent Startup Parameters

InvestigationsThe following information is provided to help you start troubleshooting issues that may occur when monitoring your system.

ViewsViews are graphs or tabular presentations of data collected by the DB2 agent.

Investigating Application Locks Investigating Database Manager Resources

Investigating Application Memory Investigating Database Memory

Investigating Application Sorting Investigating Database Memory Application Sections

Investigating Application SQL Statistics Investigating Database Memory Catalog Cache

Investigating Database Buffer Pool Usage

Investigating Database Memory Database Heap

Investigating Database Connectivity Investigating Database Memory Package Cache

Investigating Database Internal Statistics

Investigating HADR

Investigating Database IO Investigating Tablespace Bufferpool Hit Rates

Investigating Database Log IO Investigating Tablespace Space

Investigating Database Log Space

DB2_Application_Locking Table DB2 Database IO Log


DB2_Application_Memory Table DB2 Database Lock Analysis

DB2_Application_SQL_Statistics Table DB2 Database Log Analysis

DB2_Application_Sorting Table DB2_Database_Log_Space Graph

DB2_Bufferpool_Analysis Graph DB2_Database_Manager_Agents Table

DB2_Bufferpool_Detail Table DB2_Database_Manager_Overview Graph

DB2_Client_Top_CPU_Usage Table DB2_Database_Memory_Analysis Graph

DB2_Client_Top_Cache_Usage Table DB2_Database_Memory_Application_Sections Graph

DB2_Client_Top_Lock_Usage Table DB2_Database_Memory_Catalog_Cache Graph

DB2_Client_Top_Sort_Usage Table DB2_Database_Memory_Database_Heap Graph

DB2_Database_Connection_Analysis Graph

DB2_Database_Memory_Package_Cache Graph

DB2_Database_Connection_Detail Table DB2_Database_Overview Table

DB2_Database_Connection_Internal_Statistics Graph

DB2_Database_Sort_Analysis Table

DB2_Database_Connection_SQL_Statistics Table

DB2_HADR_Overview Table

DB2_Database_IO_Agent_Analysis Table

DB2_Tables_Top_Accessed Table

DB2_Database_IO_Analysis Graph DB2_Tablespace_Top_Bufferpool_Details Table

DB2_Database_IO_Async Table DB2_Tablespace_Top_Bufferpool_HitRates Graph

DB2_Database_IO_Detail Table DB2_Tablespace_Top_Space_Details Table

DB2_Database_IO_Direct Table DB2_Tablespace_Top_Space_Utilization Graph


RulesFoglight uses rules to define monitoring parameters and parameter thresholds for notification events.

DB2_Agent_Lock_Waits Rule DB2_Db_HADR_DisconTO Rule

DB2_Agent_Token_Waits Rule DB2_Db_HADR_LogGapEx Rule

DB2_Agent_Utilization Rule DB2_Db_HADR_MissedHB Rule

DB2_Agents_Stolen Rule DB2_Db_HADR_State Rule

DB2_Appl_CPU_Time Rule DB2_Deadlocks_Detected Rule

DB2_Appl_Lock_Wait Rule DB2_Index_Ratio Rule

DB2_Appl_Sort_Time Rule DB2_Lock_List_Util Rule

DB2_Buffer_Pool_Ratio Rule DB2_Lock_Timeouts Rule

DB2_Catalog_Cache_Heap Rule DB2_Log_Secondary_Util Rule

DB2_Catalog_Cache_Oflow Rule DB2_Log_Space_Util Rule

DB2_Catalog_Cache_Ratio Rule DB2_Package_Cache_Oflow Rule

DB2_Client_CPU_Time Rule DB2_Package_Cache_Ratio Rule

DB2_Client_Lock_Wait Rule DB2_Sort_Heap_Util Rule

DB2_Client_Sort_Time Rule DB2_Sort_Oflow Rule

DB2_Connection_Util Rule DB2_Tablespace_Util Rule

DB2_Db_HADR_CngstdTO Rule


TablesThe DB2 agent stores data in the following Foglight Database tables.

Note * These tables will not populate under certain circumstances when the database is in HADR standby mode. For example, certain aspects of snapshot-based monitoring can be turned on or off via monitor switches in DB2. When those elements are turned off or not available in the current context, they are reported as "not collected" and therefore not populated in the denoted tables.

Application_Connection Table* Database_HADR Table

Application_IO Table* Database_IO Table

Application_Locking Table Database_Locking Table

Application_Memory Table* Database_Logging Table

Application_Sorting Table* Database_Memory Table

Client_Connection Table* Database_Sorting Table

Client_IO Table* Database_Summary Table

Client_Locking Table* Database_Tables Table

Client_Memory Table* Database_Tablespaces Table*

Client_Sorting Table* Database_TablespacesTopBP Table*

Database_Bufferpools Table Instance_Agent Table

Database_Connection Table


Using DB2 Agent Startup ParametersThe DB2 agent is shipped with predefined agent startup parameters (ASPs) that dictate how the agent will perform. You can change these parameters to suit your system requirements. The parameters listed in the topics below are specific to the DB2 Agent. For more information regarding common agent startup parameters, such as purging, see the About Agent Startup Parameters topic in the Foglight Management Server online help.

Related TopicsSetting DB2 Connection DetailsSetting the DB2 Data Management Parameters

Setting DB2 Connection DetailsUse the Connection Details tab in the DB2 UDB agent ASP Editor to designate the type of connection parameters to use.

To set connection parameters

1 Right-click the DB2 agent icon and choose Edit, ASPs to display the Edit ASP window.

2 Select the Connection Details tab.


3 In the Instance box, enter the name of the DB2 instance to connect to.

4 Enter a valid node number in the DB2 Node box.Note Default is 0.

Global snapshots can be performed on an EEE (Extended Enterprise Edition) by changing DB2 Node to -2 (the default value is 0).Note The DB2Monitor agent cannot discover all nodes on a EEE node and, thus, cannot

add a DB2 agent for each node. It can add only one DB2 agent per instance. However, a DB2 agent can be added manually to monitor specific nodes and the DB2 Node value can be changed to the node being monitored.

5 In the User box, enter the DB2 user name.Note Note: A valid user must have SYSMON, SYSCTRL, SYSMAINT, or SYSADM

authority.

6 In the Password box, enter the DB2 user's password.

7 In the DB2 Home box, enter the path to the DB2 instance installation's sqllib directory.Note Default for Linux/UNIX is "/home/db2inst1/sqllib"

Note Default for Windows is "C:\Program Files\IBM\SQLLIB"

8 After defining the connection parameters, you can:

a Click OK to save the entry and close the Edit ASP window.

b Select the Data Management tab to set the sample frequency and intervals between data purges.

Setting the DB2 Data Management ParametersUse the Data Management tab in the DB agent ASP Editor to set the sample frequency and intervals between data purges.

Note You can purge tables at the agent or table level. Table level purging is the preferred method.

To set the data management parameters

1 Right-click the DB2 agent icon and choose Edit, ASPs.


2 Click the Data Management tab.

3 In the Sample Frequency (seconds) box, enter the sample frequency in seconds.Note The default is 300 seconds.

4 In the Top Clients box, enter the number of top clients.Note Default is 10.

This number is used to control the amount of data stored in Foglight tables. For example:

• Client_Connection filtering is based on the top consumers of total CPU time.

• Client_IO filtering is based on the top consumers of physical IO.

• Client_Locking filtering is based on the top consumers of locks held.

• Client_Memory filtering is based on the top consumers of total cache inserts.

• Client_Sorting filtering is based on the top consumers of total sort time.

5 In the Top Tables box , enter the number of tables. This number indicates the number of top consumers related to database table activity row access.Note Default is 10.


6 In the Top Util Tablespaces box, enter the number of top utility tablespaces. The filtering is based on tablespace percent utilization.Note Default is 10.

7 In the Top BP Tablespaces box, enter the number of top tablespaces. The filtering is based on bufferpool hit ratio.Note Default is 10.

8 Select the list from the drop-down menu n the DB2 Agent PurgeDays List box. Click Edit to change the data purging characteristics of the table.

9 Click OK to save the entry and close the Edit ASP window, or select the Connections Detail tab to configure the DB2 connection parameters.

Setting Data Purging ParametersUse the DB2 Table Purge Days window in the Data Management ASP tab to change the connection parameters of a table.

To set data purging parameters

1 Right-click the DB2 agent icon and choose Edit, ASPs to display the Edit ASP window.

2 Select the Data Management tab.


3 Click Edit next to the Sample Frequency (seconds) box to open the DB2 Table Purge Days window.

Note The default number of purge days is shown for each table.

Warning! New or Delete is to be used only when directed by Quest Technical Support.


4 Select the table for which you want to change the values and click Edit.Note Only existing tables should be modified.

The Edit SampleFreq window displays. The selected table name displays in the Foglight Table box.

5 In the Purge Days box, enter the purge days value for the selected table.Note Default is 60.

6 Click OK to save the entry and close the Edit SampleFreq window.

7 Click OK to save the entry and close the DB2 Table Purge Days window.

8 Click OK to save the entry and close the Edit ASP window, or select the Connections Detail tab to configure the DB2 connection parameters.


DB2 Agent TablesThe DB2 agent stores data in a series of tables in the DB2 database. Click the hyperlinks to view field definitions.

Data elements are classified by the following categories:

• Counter—Counts the number of times an activity occurs. Counter values increase during monitoring. Most can be reset.

• Calculation—Factors in variables to produce totals, ratios, and percentages.

• Gauge—Indicates the current value for an item. This value can go up or down depending on database activity (for example, the number of locks held).

• Watermark— Indicates the highest (maximum) or lowest (minimum) value an element reached since monitoring was started. These values cannot be reset.

• Information—Provides reference-type details of your monitoring activities. This can include items such as node names, aliases, and path details.

• Timestamp— Indicates the date and time that an activity took place, by providing the number of seconds and microseconds that have elapsed since


January 1, 1970. In the C language, for example, this can be converted to calendar date and time using the ctime() function.

• Time—Returns the number of seconds and microseconds spent on an activity.

Note * These tables will not populate under certain circumstances when the database is in HADR standby mode. For example, certain aspects of snapshot-based monitoring can be turned on or off via monitor switches in DB2. When those elements are turned off or not available in the current context, they are reported as "not collected" and therefore not populated in the denoted tables.

Application_Connection Table* Database_HADR Table

Application_IO Table* Database_IO Table

Application_Locking Table* Database_Locking Table

Application_Memory Table* Database_Logging Table

Application_Sorting Table* Database_Memory Table

Client_Connection Table* Database_Sorting Table

Client_IO Table* Database_Summary Table

Client_Locking Table* Database_Tables Table*

Client_Memory Table* Database_Tablespaces Table*

Client_Sorting Table* Database_TablespacesTopBP Table*Database_Bufferpools Table Instance_Agent Table

Database_Connection Table


Application_Connection TableThe fields included in this table are as follows:

Field Data Element

Description Metric/Calculation

Agent_system_ CPU_time

Time The amount of agent system CPU time, in seconds.

agent_sys_cpu_time

Agent_user_CPU_time

Time The amount of agent user CPU time, in seconds

agent_usr_cpu_time

Agents_stolen Counter The number of times that agents were stolen from an application. Agent theft occurs when an idle agent associated with an application is reassigned to a different application.

agents_stolen

Application_idle_ time

Time The amount of application idle time.

appl_idle_time

Application_name Information The name of the selected application.

Subject field

Binds_and_ precompiles_ attempted

Counter The number of attempted binds and precompiles.

binds_precompiles


Block_cursor_ requests_accepted

Counter The number of block cursor requests accepted.

rej_curs_blk

Block_cursor_ requests_ rejected

Counter The number of block cursor requests rejected.

rej_curs_blk

Database_ application_ name

Information The name of the application associated with the DB2 database.

Subject field

Database_name Information The name of the DB2 database being monitored.

Used for drill-down filter - Subject field

Internal_ automatic_ rebinds

Counter The number of internal automatic rebinds.

int_auto_rebinds

Internal_commits Counter The number of internal commits.

int_commits

Internal_rollbacks Counter The number of internal commits.

int_rollbacks

Internal_rollbacks_due_to_deadlock

Counter The number of internal rollbacks due to deadlock.

int_deadlock_ rollbacks

Internal_rows_ deleted

Counter The number of internal rows deleted.

int_rows_deleted

Field Data Element



Internal_rows_ inserted

Counter The number of internal rows inserted.

Int_rows_inserted

Internal_rows_ updated

Counter The number of internal rows updated.

Int_rows_inserted

Rows_deleted Counter The number of rows deleted.

rows_deleted

Rows_inserted Counter The number of rows inserted.

rows_inserted

Rows_read Counter The number of rows read.

rows_read

Rows_selected Counter The number of rows selected.

rows_selected

Rows_updated Counter The number of rows updated.

rows_updated

Rows_written Counter The number of rows written.

rows_written

SQL_DDL_ statements

Counter The number of SQL DDL statements.

ddl_sql_stmts

SQL_commit_ statements

Counter The number of SQL commit statements.

commit_sql_stmts

Field Data Element



SQL_dynamic_ rate

Calculation The number of dynamic SQL requests received for the database from connected client applications per second.

dynamic_sql_stmts / interval

SQL_dynamic_ statements

Counter The number of SQL dynamic statements.

dynamic_sql_stmts

SQL_failed_ statements

Counter The number of SQL failed statements.

failed_sql_stmts

SQL_rollback_ statements

Counter The number of SQL rollback statements.

rollback_sql_stmts

SQL_select_ statements

Counter The number of SQL select statements.

select_sql_stmts

SQL_static_rate Calculation The number of static SQL requests received for the database from connected client applications per second.

static_sql_stmts / interval

SQL_static_ statements

Counter The number of SQL static statements.

static_sql_stmts

Field Data Element



Application_IO TableThe fields included in this table are as follows:

SQL_update_ insert_delete_ statements

Counter The number of SQL update, insert, and delete statements.

uid_sql_stmts

Total_CPU_time Time The total amount of CPU time, in seconds, expired since the last reset.

Agent user CPU time + Agent_system_CPU_time

Unit_of_work_ rate

Calculation The number of commits and rollbacks issued explicitly by connected client applications, and issued implicitly by the system during imports, binds and deadlock recovery, etc.

(commit_sql_stmts + rollback_sql_stmts + int_commits + int_rollbacks) / interval

Field Data Element



Subject field

Buffer_pool_data_logical_reads

Counter The number of buffer pool data logical reads.

pool_data_l_reads

Field Data Element



Buffer_pool_data_physical_reads

Counter The number of buffer pool data physical reads.

pool_data_p_reads

Buffer_pool_data_writes

Counter The number of buffer pool data writes.

pool_data_writes

Buffer_pool_ index_logical_reads

Counter The number of buffer pool index logical reads.

pool_index_l_reads

Buffer_pool_ index_ physical_reads

Counter The number of buffer pool index physical reads.

pool_index_p_reads

Buffer_pool_ index_writes

Counter The number of buffer pool index writes.

pool_index_writes

Buffer_pool_read_time

Time The amount of buffer pool read time (in milliseconds).

pool_read_time

Buffer_pool_write_time

Time The amount of buffer pool write time (milliseconds).

pool_write_time

Data_pages_from_extended_storage

Counter The number of data pages pulled from extended storage.

pool_data_from_ estore

Data_pages_to_ extended_storage

Counter The number of data pages saved to extended storage.

pool_data_to_estore

Field Data Element



Database_ application_name


Subject field



Direct_read_ requests

Counter The number of direct read requests.

direct_read_reqs

Direct_read_time Time The amount of direct read time (in milliseconds).

direct_read_time

Direct_reads Counter The number of direct reads.

direct_reads

Direct_write_ requests

Counter The number of direct write requests.

direct_write_reqs

Direct_write_time Time The amount of direct write time (in milliseconds).

direct_write_time

Direct_writes Counter The number of direct writes.

direct_writes

Index_pages_from_extended_storage

Counter The number of index pages pulled from extended storage.

pool_index_from_ estore

Field Data Element



Application_Locking TableThe fields included in this table are as follows:

Index_pages_to_ extended_storage

Counter The number of index pages saved to extended storage.

pool_index_to_ estore

Prefetch_wait_ time

Time The amount of prefetch wait time (in milliseconds).

prefetch_wait_time

Field Data Element



Subject field

Average_lock_wait_time

Calculation The average amount of time that an application was waiting for a lock within this database.

lock_wait_time / lock_waits

Database_application_ name


Subject field



Field Data Element



Deadlocks_detected

Counter The number of deadlocks detected.

deadlocks

Exclusive_lock_ escalations

Counter The number of exclusive lock escalations.

x_lock_escals

Lock_escalations Counter The number of lock escalations.

lock_escals

Lock_timeouts Counter The number of lock timeouts.

lock_timeouts

Lock_wait_time Calculation The average lock wait time.

lock_wait_time

Lock_waits Counter The average lock wait time. This is the average amount of time that an application was waiting for a lock.

lock_waits

Locks_held Gauge The number of locks held.

locks_held

Field Data Element



Locks_waiting Gauge The number of agents waiting for a lock. When used in conjunction with Applications Connected Currently, this element indicates the percentage of applications waiting on locks. If this number is high, the applications may have concurrency problems, and you should identify applications that are holding locks or exclusive locks for long periods of time.

locks_waiting

Field Data Element



Application_Memory TableThe fields included in this table are as follows:

Field Data Element



Subject field

Application_ section_hit_ratio

Calculation The percentage of application section hits. This element indicates if the SQL work area is being used effectively. You can use this element to tune the size of the heap used for the SQL work area. In partitioned databases this size is controlled by the app_ctl_heap_sz configuration parameter. SQL work area size in other database environments uses the applheapsz configuration parameter. The size of the SQL work area for SMP agents is controlled by applheapsz in all environments.

(1 (appl_section_inserts / appl_section_lookups)) * 100


Application_section_ inserts

Counter The number of application section inserts.

appl_section_ inserts

Application_section_lookups

Counter The number of application section lookups.

appl_section_lookups

Catalog_cache_failure_ratio

Calculation The catalog cache failure ratio. This item reflects the adequacy of the cache size and, indirectly, on the database heap size, which additionally limits the size of the cache.

(cat_cache_overflows + cat_cache_heap_full) / cat_cache_inserts * 100

Catalog_ cache_heap_full

Counter The number of catalog cache heap fulls.

cat_cache_heap_full

Catalog_cache_hit_ratio

Calculation The percentage of catalog cache hits. This item indicates how well the catalog cache is avoiding catalog accesses.

(1 - (cat_cache_inserts / cat_cache_lookups)) * 100

Catalog_ cache_inserts

Counter The number of catalog cache inserts.

pkg_cache_inserts

Field Data Element



Catalog_ cache_lookups

Counter The number of catalog cache lookups.

pkg_cache_lookups

Catalog_ cache_overflows

Counter The number of catalog cache overflows.

cat_cache_overflows



Subject field

Database_ name

Information The name of the DB2 database being monitored.


Package_ cache_hit_ratio

Calculation The package cache hit ratio. This item indicates if the package cache is being used effectively.

(1 - (pkg_cache_inserts / pkg_cache_lookups)) * 100

Package_ cache_inserts

Counter The number of package cache inserts.

pkg_cache_inserts

Package_ cache_lookups

Counter The number of package cache lookups.

pkg_cache_lookups

Field Data Element



Application_Sorting TableThe fields included in this table are as follows:

Field Data Element



Subject field

Average_sort_ time

Calculation The average amount of sort time.

total_sort_time / total_sorts



Subject field



Hash_join_ overflow_percent

Counter The percentage of hash joins that overflowed to disk.

hash_join_small_overflows / total_hash_joins * 100

Hash_join_ overflows

Counter The number of hash join overflows.

hash_join_ overflows

Hash_join_small_overflows

Counter The number of hash join small overflows.

hash_join_small_overflows

Hash_small_ overflow_percent

Calculation The percentage of small hash joins that overflowed to disk.

hash_join_small_overflows / total_hash_joins * 100


Client_Connection TableThe fields included in this table are as follows:

Sort_overflow_ percent

Calculation The percentage of sorts that had to overflow to disk.

sort_overflows / total_sorts * 100

Sort_overflows Counter The number of sort overflows.

sort_overflows

Total_hash_joins Counter The total number of hash joins.

total_hash_joins

Total_hash_loops Counter The total number of hash loops.

total_hash_loops

Total_sort_time Time The total amount of sort time.

total_sort_time

Total_sorts Counter The total number of sorts.

total_sorts

Field Data Element


Agent_system_ CPU_time

Time The total amount of agent system CPU time, in seconds.

agent_sys_cpu_time

Agent_user_CPU_time

Time The total amount of agent user CPU time, in seconds.

agent_usr_cpu_time

Field Data Element



Agents_stolen Counter The number of agents stolen.

agents_stolen

Application_ID Information The application identification code.

Subject field

Application_idle_ time

Time The total amount of application idle time.

appl_idle_time

Associated_agents_maximum

Watermark The maximum number of associated agents.

associated_agents_ top

Authorization_ID Information The authorization identification code.

auth_id - Subject field

Binds_and_ precompiles_ attempted

Counter The number of binds and precompiles attempted.

binds_precompiles

Block_cursor_ requests_accepted

Counter The number of block cursor requests accepted.

rej_curs_blk

Block_cursor_ requests_rejected

Counter The number of block cursor requests rejected.

acc_curs_blk



Subject field

Field Data Element




Subject field

Execution_ID Information The execution identification code.

execution_id - Subject field

Internal_ automatic_rebinds


int_auto_rebinds


int_commits

Internal_rollbacks Counter The number of internal rollbacks.

int_rollbacks






int_rows_deleted



Int_rows_inserted

Internal_rows_updated


Int_rows_inserted


rows_deleted


rows_inserted

Field Data Element



Rows_read Counter The number of rows read.

rows_read


rows_selected


rows_updated

Rows_written Counter The number of rows written.

rows_written

SQL_DDL_statements

Counter The number of SQL DDL statements.

ddl_sql_stmts


Counter The number of SQL commit statements.

commit_sql_stmts

SQL_dynamic_ rate

Calculation The SQL dynamic rate.



Counter The number of SQL dynamic statements.

dynamic_sql_stmts

SQL_failed_statements

Counter The number of SQL failed statements.

failed_sql_stmts


Counter The number of SQL rollback statements.

rollback_sql_stmts

SQL_select_statements

Counter The number of SQL select statements.

select_sql_stmts

Field Data Element



Client_IO TableThe fields included in this table are as follows:

SQL_statement Information The SQL statement.

sql_statement

SQL_static_rate Calculation The SQL static rate.


SQL_static_statements

Counter The number of SQL static statements.

static_sql_stmts


Counter The SQL update insert delete statements.

uid_sql_stmts

Total_CPU_time Time The total amount of CPU processing time, in seconds, used since the last reset.

agent_usr_cpu_time + agent_sys_cpu_time

Unit_of_work_ rate

Counter The unit of work rate.


Field Data Element



Subject field

Field Data Element







pool_data_l_reads



pool_data_p_reads



pool_data_writes

Buffer_pool_ index_logical_ reads


pool_index_ l_reads

Buffer_pool_ index_physical_ reads


pool_index_ p_reads



pool_index_writes


Time The number of buffer pool read time (in milliseconds).

pool_read_time


Time The number of buffer pool write time (in milliseconds).

pool_write_time

Field Data Element








pool_data_to_ estore



Subject field


Subject field



direct_read_reqs


direct_read_time


direct_reads

Direct_write_ request


direct_write_reqs


direct_write_time

Field Data Element




direct_writes









Physical_IO Calculation The amount of physical I/O.

pool_data_p_reads + pool_data_writes +pool_index_p_reads + pool_index_writes + direct_reads + direct_writes

Prefetch_wait_ time

Time The amount of prefetch wait time (in milliseconds).

prefetch_wait_ time


sql_statement

Field Data Element



Client_Locking TableThe fields included in this table are as follows:

Field Data Element



Subject field



Average_lock_ wait_time

Calculation The average amount of lock wait time.




Subject field


Subject field

Deadlocks_ detected

Counter The number of deadlocks detected.

deadlocks


Counter The number of exclusive lock escalations.

x_lock_escals



Lock_escalations Counter The number of lock escalations.

lock_escals

Lock_timeouts Counter The number of lock timeouts.

lock_timeouts


Client_Memory TableThe fields included in this table are as follows:

Lock_wait_time Time The amount of lock wait time.

lock_wait_time

Lock_waits Counter The number of lock waits.

lock_waits

Locks_held Guage The number of locks held.

locks_held

Locks_waiting Guage The number of locks waiting.

locks_waiting


sql_statement

Field Data Element



Subject field


Calculation The percentage of application section hits.

(1 (appl_section_ inserts / appl_section_lookups)) * 100

Application_ section_inserts

Counter The number of application section inserts.

appl_section_ inserts

Field Data Element



Application_ section_lookups

Counter The number of application section lookups.




Catalog_cache_ failure_ratio

Calculation The percentage of catalog cache failure.


Catalog_cache_ heap_full

Counter The number of catalog cache heap fulls.

cat_cache_heap_ full

Catalog_cache_ hit_ratio

Calculation The percentage of catalog cache hits.


Catalog_cache_ inserts

Counter The number of catalog cache inserts.

cat_cache_inserts

Catalog_cache_ lookups

Counter The number of catalog cache lookups.

cat_cache_ lookups

Catalog_cache_ overflows

Counter The number of catalog cache overflows.

cat_cache_ overflows



Subject field

Field Data Element




Subject field


execution_ id - Subject field

Package_cache_ hit_ratio

Calculation The percentage of package cache hits.

(1 - (pkg_cache_inserts / pkg_cache_lookups)) * 100

Package_cache_ inserts

Counter The number of package cache inserts.

pkg_cache_inserts

Package_cache_ lookups

Counter The number of package cache lookups.

pkg_cache_ lookups


sql_statement

Total_cache_ inserts

qual Counter The total number of cache inserts in the table.

appl_section_ inserts +cat_cache_ inserts +pkg_cache_ inserts

Field Data Element



Client_Sorting TableThe fields included in this table are as follows:

Field Data Element



Subject field



Average_sort_time Calculation The average sort time.

total_sort_time / total_sorts



Subject field





Hash_join_ overflow_percent

Counter The percentage of hash join overflow.

hash_join_overflows / total_hash_joins *100


Counter The number of hash join overflows.

hash_join_ overflows

Hash_join_small_ overflows

Counter The number of hash join small overflows.

hash_join_small_ overflows



Calculation The percentage of hash small overflow.

hash_join_small_ overflows / total_hash_joins * 100

SQL_statement Information The SQL statement. sql_statement


Counter The percentage of sort overflows.


Sort_overflows Counter The number of sort overflows.

sort_overflows


total_hash_joins


total_hash_loops

Total_sort_time Time The amount of sort time.

total_sort_time


total_sorts

Field Data Element



Database_Bufferpools TableA buffer pool is a temporary storage area for database pages. This feature enhances system performance by allowing data to be accessed more rapidly. The fields included in this table are as follows:

Field Data Element


Async_pages_read_per_request

Calculation The number of asynchronous pages read per request.

(pool_async_data_ reads + pool_async_index_reads) / pool_async_data_ read_reqs

Async_pool_data_ page_reads

Counter The number of pages read asynchronously into the buffer pool.

pool_async_data_ reads

Async_pool_data_ page_writes

Counter The number of times a buffer pool data page was physically written to disk by either an asynchronous page cleaner, or a prefetcher.

pool_async_data_ writes

Async_pool_index_page_reads

Counter The number of times a buffer pool index page was physically read from disk by either an asynchronous page cleaner, or a prefetcher.

pool_async_index_reads


Async_pool_index_page_writes

Counter The number of times a buffer pool index page was physically written to disk by either an asynchronous page cleaner, or a prefetcher.

pool_async_index_writes

Async_read_ requests

Counter The number of asynchronous read requests.

pool_async_data_ read_reqs

Async_read_time Time The time spent reading by database manager prefetchers.

pool_async_read_ time

Async_write_time Time The time spent writing data or index pages from the buffer pool to disk by database manager page cleaners.

pool_async_write_ time

Buffer_pool_data_ logical_reads

Counter The number of logical read requests for data pages that have gone through the buffer pool.

pool_data_l_reads

Field Data Element



Buffer_pool_data_ physical_reads

Counter The number of read requests that required I/O to get data pages into the buffer pool.

pool_data_p_reads

Buffer_pool_data_ writes

Counter The number of times a buffer pool data page was physically written to disk.

pool_data_writes

Buffer_pool_hit_ ratio

Calculation Percentage of read requests that were satisfied without having to read from the disk.

100 * (1 ( (pool_data_p_reads + pool_index_p_ reads) / (pool_data_l_reads + pool_index_l_reads) ) )

Buffer_pool_index_logical_reads

Counter The number of logical read requests for index pages that have gone through the buffer pool.

pool_index_l_reads

Buffer_pool_index_physical_reads

Counter The number of physical read requests to get index pages into the buffer pool.

pool_index_p_ reads

Buffer_pool_index_writes


pool_index_writes

Field Data Element



Buffer_pool_name

Information The name of the buffer pool.

Subject field

Bufferpool_page_ size

Information refer to syscat.bufferpools.endpages

The size of pages in the buffer pool.

syscat.bufferpool

Buffer_pool_pages

Information syscat.bufferpools.pagesize

The number of pages in the buffer pool.

syscat.bufferpool

Buffer_pool_read_ time

Time The amount of elapsed time (in milliseconds) spent processing read requests that caused data or index pages to be physically read from disk to buffer pool.

pool_read_time

Buffer_pool_total_ size

Counter The total size of the buffer pool.

NAPGES * PAGESIZE / 1024

Buffer_pool_write_ time

Time The amount of time (in milliseconds) spent physically writing data or index pages from the buffer pool to disk.

Field Data Element



Data_pages_from_ extended_storage

Counter The number of buffer pool data pages copied from extended storage.



Counter The number of buffer pool data pages copied to extended storage. Pages are copied from the buffer pool to extended storage, when they are selected as victim pages.


Database_ bufferpool_name

Information The name of the buffer pool.

Subject field

Database_files_ closed

Counter The number of database files closed.

files_closed




Counter The number of requests to perform a direct read of one or more sectors of data.

direct_read_reqs

Direct_read_time Time The time (in milliseconds) required to perform the direct reads.

direct_read_time

Field Data Element



Direct_reads Counter The number of read operations that do not use the buffer pool.

direct_reads


Counter The number of requests to perform a direct write of one or more sectors of data.

direct_write_reqs

Direct_write_time Time The time (in milliseconds) required to perform the direct writes.

direct_write_time

Direct_writes Counter The number of write operations that do not use the buffer pool.

direct_writes

Index_hit_ratio Calculation The buffer pool index hit ratio.

100 * (1 (pool_index_p_ reads / pool_index_l_reads) )


Counter The number of buffer pool index pages copied from extended storage.


Field Data Element



Database_Connection TableThe fields included in this table are as follows:


Counter The number of buffer pool index pages copied to extended storage. Pages are copied from the buffer pool to extended storage, when they are selected as victim pages.


Field Data Element


Binds_and_ precompiles_attempted

Counter The number of attempted binds and precompiles.

binds_precompiles

Client_percent_ active

Calculation The percentage of active clients to connected clients.

appls_in_db2 / appls_cur_con * 100

Client_percent_of_average

Calculation Client percent of average.

appls_cur_cons / avg_appls * 100

Client_percent_of_maximum

Calculation Client percent of maximum.

Appls_cur_cons / maxappls * 100

Connections_ active

Gauge The number of active connections.

appls_in_db2

Field Data Element



Connections_ concurrent_maximum

Watermark The maximum number of connections.

connections_top

Connections_ current

Gauge The number of current connections.

appls_cur_cons


db_name - Subject field

Internal_ automatic_rebinds


int_auto_rebinds


int_commits

Internal_rollbacks Counter The number of internal rollbacks.

int_rollbacks






int_rows_deleted



Int_rows_inserted

Internal_rows_ updated


int_rows_updated

Field Data Element




rows_deleted


rows_inserted


rows_selected


rows_updated

SQL_DDL_ statements

Counter The total number of SQL DDL statements.

ddl_sql_stmts


Counter The total number of SQL commit statements.

commit_sql_stmts

SQL_dynamic_ rate

Calculation The number of dynamic SQL requests received for the database from connected client applications per second.



Counter The total number of SQL dynamic statements.

dynamic_sql_stmts

SQL_failed_ statements

Counter The total number of SQL failed statements.

failed_sql_stmts

Field Data Element




Counter The total number of SQL rollback statements.

rollback_sql_stmts

SQL_select_ statements

Counter The total number of SQL select statements.

select_sql_stmts

SQL_static_rate Calculation The number of static SQL requests received for the database from connected client applications per second.


SQL_static_ statements

Counter The total number of SQL static statements.

static_sql_stmts


Counter The total number of SQL update insert delete statements.

uid_sql_stmts

Total_connections Counter The total number of connections occurring during this sampling period.

total_cons

Field Data Element



Database_HADR TableThe fields included in this table are as follows:

Unit_of_work_ rate

Calculation The number of commits and rollbacks issued explicitly by connected client applications, and issued implicitly by the system during imports, binds and deadlock recovery, etc.


Field Data Element


Database_name Information The name of the DB2 HADR database being monitored.

Subject field

Field Data Element



hadr_connect_ status

Information The current HADR connection status of the database takes on one of these values:• SQLM_HADR_

CONN_CONNECTED (registry value = 0). The database is connected to its partner node.

• SQLM_HADR_ CONN_DISCONNECTED (registry value = 2). The database is not connected to its partner node.

• SQLM_HADR_ CONN_ CONGESTED (registry value = 1). The database is connected to its partner node, but is having trouble sending data to that partner node.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_connect_ status

Field Data Element



hadr_connect_ time

Time Shows a timestamp whose meeting varies depending on the value if:• hadr_connect_stat

us is SQLM_ HADR_ CONN_ CONNECTED (registry value = 0). hadr_connect_time shows the time the connection was made.

• hadr_connect_status is SQLM_ HADR_ CONN_ CONGESTED (registry value = 1). hadr_connect_time shows the time at which the congestion started happening.

• hadr_connect_status is SQLM_ HADR_ CONN_ DISCONNECTED (registry value = 2). hadr_connect_time shows the

Source: Snapshot streamLDG: hadrMonitor Element: hadr_connect_ time

Field Data Element


time the disconnection occurred.


hadr_elapsed_ connect_time

Calculation The delta of missed connect times on the HADR connection (based on previous collection cycle).

Calculated value.elapsed_connect_ time = (Currrent_Time -hadr_connect_ time)Unit: Minutes

hadr_heartbeats_missed

Calculation The delta of missed heartbeats on the HADR connection (based on previous collection cycle).

Source: Snapshot streamLDG: hadrMonitor Element: hadr_heartbeat

hadr_local_host Information The HADR local host name. This can be a name or a tcp/ip address.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_local_host

hadr_local_ service

Information The local HADR TCP service displayed as a service name string or a port number string.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_local_ service

hadr_log_gap Calculation The running average of the gap between the primary LSN and the standby LSN. Measured in number of bytes.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_log_gap

Field Data Element



hadr_primary_ log_file

Information The name of the current log file on the primary HADR database.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_primary_log_file

hard_primary_ log_lsn

Information The current log position of the primary HADR database.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_primary_ log_lsn

hadr_primary_ log_page

Information The page number in the current log file indicating the current log position on the primary HADR database. The page number is relative to the logfile. Page number 0 corresponds to the beginning of the file.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_primary_ log_page

hadr_remote_ host

Information The remote HADR host name displayed either has a name or a TCP/IP address.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_remote_ host

Field Data Element



hadr_remote_ instance

Information The remote HADR instance name.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_remote_ instance

hadr_remote_ service

Information The remote HADR TCP service displayed as a service name string or a port number string.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_remote_ service

Field Data Element



hadr_role Information The role of the database of interest with respect to HADR:• SQLM_HADR_

ROLE_ STANDARD - the database is not an HADR database.

• SQLM_HADR_ ROLE_ PRIMARY - the database is the primary HADR database.

• SQLM_HADR_ ROLE_ STANDBY - the database is the standby HADR database.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_role

hard_standby_ log_file

Information The name of the current log file on the standby HADR database.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_standby_log_file

Field Data Element



hadr_standby_ log_lsn

Information The current log position of the standby HADR database. The explanation of hadr_primary_log_lsn applies here.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_standby_log_lsn

hadr_standby_ log_page

Information The page number in the current log file on the standby HADR database. Discussion of hadr_primary_log_page applies here too.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_standby_log_ page

Field Data Element



hadr_state Information The current HADR state of the database takes on one of these values:•SQLM_HADR_ STATE_ DISCONNECTED - The database is not connected to its partner database.

•SQLM_HADR_ STATE_LOC_ CATCHUP - The database is doing local catch-up.

•SQLM_HADR_ STATE_REM_ CATCH_ PEND - The database is waiting to connect to its partner to do remote catch-up.

•SQLM_HADR_ STATE_REM_ CATCHUP - The database is doing remote catch-up.

•SQLM_HADR_ STATE_PEER - The primary and secondary databases are connected and are in peer state.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_state

Field Data Element



hadr_syncmode Information The current HADR synchronization mode of the database. Takes on one of these values:•SQLM_HADR_ SYNCMODE_ SYNC - Sync mode

•SQLM_HADR_ SYNCMODE_ NEARSYNC - Nearsync mode

•SQLM_HADR_ SYNCMODE_ ASYNC - Async mode

Source: Snapshot streamLDG: hadrMonitor Element hadr_syncmode

hadr_timeout Time The number of seconds it takes for an HADR database server to consider a communication attempt to have failed. Put another way, if a database server attempts a communication with its partner and does not get a response within this amount of time, the attempt has failed.

Source: Snapshot streamLDG: hadrMonitor Element: hadr_timeout

Field Data Element



Database_IO TableThe fields included in this table are as follows:

Field Data Element


Async_pages_ read_per_request

Calculation The number of asynchronous pages read per request. Measures prefetch effectiveness, should be close to tablespace prefetch size. For example, if the value is 6 and prefetch size is 32, then bufferpool is too small to accommodate prefetch load.

(pool_async_data_reads + pool_async_index_reads) / pool_async_data_ read_reqs

Async_pool_data_page_reads

Counter The number of asynchronous pool data page reads.

pool_async_data_ reads pool_async_data_writes

Async_pool_data_page_writes

Counter The number of asynchronous pool data page writes.

pool_async_data_writes

Async_pool_index_page_reads

Counter The number of asynchronous pool index page reads.

pool_async_index_reads

Async_pool_index_page_writes

Counter The number of asynchronous pool index page writes.

pool_async_index_writes

Async_read_rate Counter The asynchronous read rate.

asynchronous_reads/interval





Async_read_time Time The amount of asynchronous read time (in milliseconds).

pool_async_read_ time

Async_reads Calculation The number of asynchronous reads.

pool_async_index_reads + pool_async_data_ reads

Async_write_rate Calculation The asynchronous write rate.

asynchronous_ writes/interval

Async_write_time Time The amount of asynchronous write time (in milliseconds).

pool_async_write_time

Async_writes Calculation The number of asynchronous writes.

pool_async_index_writes + pool_async_data_writes



pool_data_l_reads



pool_data_p_reads



pool_data_writes

Field Data Element




Calculation Percentage of read requests that were satisfied without having to read from the disk because the page was already in the buffer pool. The greater the buffer pool hit ratio, the lower the frequency of disk I/O.

(1 physical_reads / logical_reads) * 100

Buffer_pool_ index_logical_ reads


pool_index_l_ reads

Buffer_pool_ index_physical_reads


pool_index_p_ reads



pool_index_writes


Time The total read time (in milliseconds). This value is calculated at both interval and total times.

pool_read_time


Time The total write time (in milliseconds). This value is calculated at both interval and total times.

pool_write_time




Field Data Element






Database_files_ closed

Counter The number of database files closed.

files_closed


Subject field

Direct_read_rate Calculation The direct read rate. direct_reads/interval


Counter The total number of direct read requests.

direct_read_reqs


direct_read_time

Direct_reads Counter The total number of direct reads.

direct_reads

Direct_write_rate Calculation The direct write rate. direct_writes/interval


Counter The total number of direct write requests.

direct_write_reqs


direct_write_time

Direct_writes Counter The total number of direct writes.

direct_writes

Field Data Element



Dirty_page_steal_cleaner_triggers

Counter The total number of dirty page steal cleaner triggers.

pool_drty_pg_steal_clns

Dirty_page_ threshold_cleaner_triggers

Counter The total number of dirty page threshold cleaner triggers.

pool_drty_pg_ thrsh_clns

Index_hit_ratio Calculation The percentage of time that the database manager did not need to load a page from disk in order to service an index page request. A high index hit ratio is important for OLTP applications.

(1- (pool_index_p_ reads / pool_index_l_ reads)) * 100



pool_index_from_estore




LSN_Gap_cleaner_triggers

Counter The total number of LSN Gap cleaner triggers.

pool_lsn_gap_clns

Logical_IO Calculation The amount of logical IO.

logical_reads + physical_writes

Logical_reads Calculation The total number of logical reads.

pool_index_l_ reads + pool_data_l_reads

Field Data Element



Number_of_page_cleaners

Counter The total number of page cleaners.

Num_iocleaners

Number_of_ prefetchers

Counter The total number of prefetchers.

Num_ioservers

Page_cleaner_ write_rate

Calculation The rate of asynchronous page cleaner writes.

(pool_async_data_writes + pool_async_index_writes) / intrerval

Page_cleaner_ write_ratio

Calculation The percentage of write requests that have been satisfied asynchronously by a page cleaner.

((pool_async_data_writes + pool_async_index_writes) / (pool_data_writes + pool_index_writes)) * 100

Physical_IO Calculation The amount of physical IO.

physical_reads + physical_writes

Physical_reads Calculation The total number of physical reads.

pool_index_p_ reads + pool_data_p_reads

Physical_writes Calculation The total number of physical writes.

pool_index_writes + pool_data_writes

Prefetch_wait_ time

Time The total amount of prefetch wait time.

prefetch_wait_ time

Prefetcher_read_ rate

Calculation The rate of asynchronous prefetcher reads.

(pool_async_data_reads + pool_async_index_reads) / intrerval

Field Data Element



Prefetcher_read_ ratio

Calculation The percentage of read requests that have been satisfied asynchronously by a prefetcher.

((pool_async_data_reads + pool_async_index_reads) / (pool_data_p_ reads + pool_index_p_ reads)) * 100

Sync_read_rate Calculation The synchronous read rate.

synchronous_reads/interval

Sync_reads Calculation The total number of synchronous reads.

pool_index_p_ reads + pool_data_p_read asynchronous_reads

Sync_write_rate Calculation The synchronous write rate.

synchronous_ writes/interval

Sync_writes Calculation The total number of synchronous writes.

pool_index_writes + pool_data_writes asynchronous_ writes

Total_read_rate Calculation The total write rate.

Total_write_rate Calculation The total read rate. physical_reads/interval

Field Data Element



Database_Locking TableThe fields included in this table are as follows:

Field Data Element


Average_lock_ wait_time

Calculation The average lock wait time. This is the average amount of time that all applications spent waiting for a lock.



Subject field

Deadlocks_ detected

Counter The total number of deadlocks detected.

Deadlocks


Counter The total number of exclusive lock escalations.

x_lock_escals

Lock_escalations Counter The total number of lock escalations.

lock_escals

Lock_list_in_use Gauge The total number of lock lists in use.

lock_list_in_use / 1024

Lock_list_ utilization_percent

Calculation The percentage of available lock lists currently in use.

(Lock list in use / (locklist * 4)) *100

Lock_timeouts Counter The total number of lock timeouts.

lock_timeouts

Lock_wait_time Time The total amount of lock wait time.

lock_wait_time


Database_Logging TableThe fields included in this table are as follows:

Lock_waits Counter The total number of lock waits.

lock_waits

Locks_held Gauge The total number of locks held.

locks_held

Locks_waiting Gauge The total number of locks waiting.

locks_waiting

Field Data Element


Average_log_ space_per_transaction

Calculation The number of transactions per second accommodated by log space in current use. This element is used to adjust the mincommit parameter to accommodate the peak number of transactions per second.

sum(uow_log_ space_used) / (1024 * # appls where (uow_log_space_used > 0) )


Subject field

Field Data Element



Log_IO Calculation The total amount of data moved to and from the log.

log_reads + log_writes

Log_IO_rate Calculation The transfer rate of data to and from the log. Use this element with an operating system monitor to quantify the amount of I/O on a device that is attributable to database activity.

(log_reads + log_writes) / interval

Log_pages_read Counter The total number of log pages read.

log_reads

Log_pages_ written

Counter The total number of log pages written.

log_writes

Log_read_rate Calculation The rate that pages are read from the log.

log_reads / interval

Log_write_rate Calculation The rate that pages are written to the log.

log_writes / interval

Maximum_ secondary_log_ space_used

Watermark The amount of maximum secondary log space used.

sec_log_used_top / 1024

Field Data Element



Maximum_total_ log_space_used

Watermark The maximum total log space used.

tot_log_used_top / 1024

Secondary_log_ percent_allocated

Calculation The percentage of space allocated to secondary logs.

(sec_logs_ allocated / logsecond)

Secondary_logs_ allocated

Gauge The secondary log percent allocated.

sec_logs_ allocated

Total_log_ available

Watermark The total number of logs available.

total_log_ available / 1024

Total_log_percent_utilized

Calculation The percentage of total log space in current use.

(total_log_used /total_log_used + total_log_ available) * 100

Total_log_used Gauge The total number of logs used.

total_log_used / 1024

Total_transaction_per_second

Calculation The number of transactions per second.

(commit_sql_ stmts + rollback_sql_ stmts + int_commits + int_rollbacks) / interval

Field Data Element



Database_Memory TableThe fields included in this table are as follows:

Field Data Element



Calculation The application section hit ratio.

(1 (appl_section_ inserts / appl_section_ lookups)) * 100

Application_ section_inserts

Counter The total number of application section inserts.

appl_section_inserts

Application_ section_lookups

Counter The total number of application section lookups.


Catalog_cache_ failure_ratio

Calculation The percentage of catalog cache failure. This ratio reflects the adequacy of the catalog cache size catalog_cache_sz and indirectly on the database heap size (dbheap), which additionally limits the size of the cache.

((cat_cache_ overflows + cat_cache_heap_ full) / cat_cache_inserts) * 100

Catalog_cache_ heap_full_ overflows

Counter The total number of catalog cache heap full overflows.

cat_cache_heap_full



Calculation The catalog cache access ratio. A high ratio (more than 0.8) indicates that the cache is performing well.


Catalog_cache_ inserts

Counter The total number of catalog cache inserts.

cat_cache_inserts

Catalog_cache_ lookups

Counter The total number of catalog cache lookups.

cat_cache_lookups

Catalog_cache_ overflows

Counter The total number of catalog cache overflows.

cat_cache_overflows

Catalog_cache_ size

Database Configuration Parameter

The size of the catalog cache (in bytes).

catalogcache_sz * 4

Database_heap_ high_water_mark

Watermark The peak number of database heap. This field measures memory usage and is being maintained for DB2 version compatibility.

db_heap_top / 1024

Database_heap_ max_utilization

Calculation The maximum utilization of the database heap.

(Database heap high water mark / (dbheap * 4) ) * 100

Field Data Element



Database_heap_ size


The size of the database heap (in bytes).

dbheap * 4


Subject field

Database_heap_ utilization_percent

Calculation The percentage of available database heap currently in use. Appears on the database details panel, the percentage of the space defined by the dbheap parameter currently being used.

Round(db_heap_ top * 100 / (dbheap * 4096) )

Field Data Element



Package_cache_ extensions_ percent

Calculation The cache extension ratio. This statistic reflects the adequacy of the package cache reserved memory size (pckcachesz) using a ratio to express the number of times that incursions into other database memory (lock list, for example possibly leading to lock escalations) were required.

pkg_cache_ num_overflows / pkg_cache_inserts

Package_cache_ high_water_mark

Watermark The peak number of package cache.

pkg_cache_size_ top / 1024


Calculation The package cache hit ratio. This element indicates if the package cache is being used effectively. If the hit ratio is high (more than 0.8), the cache is performing well. A smaller ratio indicates that the package cache should be increased.

(1 - (pkg_cache_inserts / pkg_cache_ lookups)) * 100

Field Data Element



Database_Sorting TableThe fields included in this table are as follows:

Package_ cache_inserts

Counter The total number of package cache inserts.

pkg_cache_inserts

Package_ cache_lookups

Counter The total number of package cache lookups.

pkg_cache_ lookups

Package_ cache_ overflows

Counter The total number of package cache overflows.

pkg_cache_ num_overflows

Package_ cache_size


The size of the package cache (in bytes).

pckcachesz * 4

Field Data Element


Active_sorts Counter The total number of active sorts.

active_sorts


Subject field

Field Data Element



Hash_Join_ overflow_percent

Calculation The percentage of hash joins that overflowed to disk. . If this percentage is high, you may want adjust the database configuration by increasing the value of sortheap.

(hash_join_overflows + hash_join_small_ overflows) / total_hash_joins *100


Counter The total number of hash join overflows.

hash_join_overflows

Hash_join_small_overflows

Counter The total number of hash join small overflows.

hash_join_small_ overflows


Calculation The percentage of small hash joins that overflowed to disk. If this percentage is high, you may want adjust the database configuration by increasing the value of sortheap.

hash_join_small_ overflows / total_hash_joins * 100

Sort_heap_ allocated

Gauge The amount of sort heap space allocated.

sort_heap_allocated / 1024

Sort_heap_percent_utilization

Calculation The percentage of sort heap currently in use.

(sort_heap_ allocated / sheapthres) * 100

Field Data Element



Sort_heap_size Database Manager Configuration Parameter

The size of the sort heap.

Sortheap * 4

Sort_heap_ threshold

Database Manager Configuration Parameter

The sort heap threshold level.

sheapthres


Calculation The percentage of sorts that had to overflow to disk. If this percentage is high, you may want adjust the database configuration by increasing the value of sortheap.


Sort_overflows Counter The total number of sort overflows.

sort_overflows


total_hash_joins


total_hash_loops

Total_overflow_ percent

Calculation The total overflow percentage.

((sort_overflows + hash_join_ overflows) / (total_sorts + total_hash_joins)) * 100

Field Data Element



Database_Summary TableThe fields included in this table are as follows:

Total_sort_time Time The total amount of sort time.

total_sort_time


total_sorts

Field Data Element


Async_IO Calculation The amount of asynchronous input/output. The calculation is derived from asynchronous reads and writes.

DB IO table, async_reads + async_writes



DB IO table, buffer_pool_hit_ ratio


Calculation The catalog cache access ratio. A high ratio (more than 0.8) indicates that the cache is performing well.

DB Memory table, catalog_cache_hit_ratio

Field Data Element



Client_percent_of_maximum

Calculation The percentage of active clients to connected clients.

DB Connection table, client_percent_of _maximum

Database_heap_ utilization

Calculation The amount of database heap currently in use.

DB Memory table, database_heap_ max_utilization


Subject field

Direct_IO Counter The amount of direct I/O.

DB IO table, direct_reads + direct_writes

Index_hit_ratio Calculation The database hit ratio.

DB IO table, index_hit_ratio

Lock_list_ utilization

Calculation The percentage of available lock lists currently in use.

DB Locking table, lock_list_ utilization_percent

Log_IO Calculation The transfer rate of data to and from the log. Use this element with an operating system monitor to quantify the amount of I/O on a device that is attributable to database activity.

DB Logging table, Log_IO

Log_utilization Calculation The percentage of available log space currently in use.

DB Logging table, total_log_percent_utilized

Field Data Element



Logical_IO Counter The amount of logical I/O.

DB IO table,Logical_IO


Calculation The package cache hit ratio. This element indicates if the package cache is being used effectively. If the hit ratio is high (more than 0.8), the cache is performing well. A smaller ratio indicates that the package cache should be increased.

DB Memory table, package_cache_hit_ratio

Percent_of_agents_in_use

Calculation The percentage of available agents currently in use.

Instance Agent table, percent_of_agents_in_use

Physical_IO Counter The amount of physical I/O.

DB IO table, Physical_IO

Sort_heap_ utilization

Calculation The percentage of available sort heap currently in use.

DB Sorting table, sort_heap_percent_utilization


Calculation The percentage of sorts that had to overflow to disk.

DB Sorting table, sort_overflow_ percent

Sync_IO Counter The amount of synchronous I/O.

DB IO table, sync_reads + sync_writes

Field Data Element



Database_Tables TableThe fields included in this table are as follows:

Unit_of_work_ rate

Counter The unit of work rate.

DB Connection table, unit_of_work_rate

Field Data Element



Subject field

Database_ schema_table_ name

Information A combination of the database, schema and table name to provide uniqueness for a subject field in a graph.

Subject field

Overflow_ accesses

Counter The number of times that access to overflowed rows were required during the last monitoring interval. An overflowed row is an updated row that no longer fits on the data page where it was originally written.

overflow_accesses

Field Data Element



Page_reorgs Counter The number of page reorganizations executed during the last monitoring interval. If this value is high, consider running the DB2 UDB REORG utility to reorganize the table and to clean up fragmentation. You can also reduce page reorganizations on the table by turning the APPEND option on in the table definition (using ALTER TABLE statement).

page_reorgs

Row_accesses Calculation The number of rows read from and written to the table during the last monitoring interval.

rows_read + rows_written

Field Data Element



Rows_read Counter The number of rows changed (inserted, deleted, or update) during the last monitoring interval. If this value is high, consider creating additional indexes on the table.

rows_read

Rows_written Counter The number of rows that were changed (inserted, deleted, or updated) in the table during the last monitoring interval. If this value is high, consider executing the DB2 RUNSTATS utility on this table to keep its statistics up to date for efficient SQL access to the table data.

rows_written

Table_name Information The name of the table.

Subject field

Table_schema_ name

Information The schema of the table. Only catalog and user tables use schema names.

Subject field

Field Data Element



Database_Tablespaces TableThe fields included in this table are as follows:

Table_type Information The type of table. table_type

Field Data Element




(pool_async_data_ reads + pool_async_index_ reads) / pool_async_data_ read_reqs


Counter The number of asynchronous pool data page reads.



Counter The number of asynchronous pool data page writes.


Async_pool_ index_page_reads

Counter The number of asynchronous pool index page reads.

pool_async_index_ reads

Async_pool_ index_page_ writes

Counter The number of asynchronous pool index page writes.

pool_async_index_ writes



pool_async_data_read_reqs

Field Data Element



Async_read_time Time The amount of asynchronous read time (in milliseconds).

pool_async_read_time

Async_write_time Time The amount of asynchronous write time (in milliseconds).




pool_data_l_reads



pool_data_p_reads



pool_data_writes



100 * (1 ( (pool_data_p_reads + pool_index_p_reads) / (pool_data_l_reads + pool_index_l_reads) ) )



pool_index_l_reads



pool_index_p_reads

Field Data Element





pool_index_writes



pool_read_time


Time The amount of buffer pool write time (in milliseconds).

pool_write_time






Pool_data_to_estore



Database_ tablespace_name

Information The name of the tablespace associated with the DB2 database.

Subject field



direct_read_reqs

Field Data Element



Direct_read_time Time The amount of elapsed time for direct reads (in milliseconds).

direct_read_time


direct_reads



direct_write_reqs


direct_write_time


direct_writes

Index_hit_ratio Calculation The percentage of time that the database manager did not need to load a page from disk in order to service an index page request. A high index hit ratio is important for OLTP applications.

100 * (1 (pool_index_p_reads / pool_index_l_reads) )


Counter The amount of index pages pulled from extended storage.


Field Data Element




Counter The amount of index pages saved to extended storage.

Pool_index_to_estore

Number_of_ containers

Counter The total number pages in the tablespace.

Output of tablespace query API

Number_of_files_closed

Counter The number of files closed.

files_closed

Tablespace_ID Information The tablespace identification code.


Tablespace_extent_size

Counter The tablespace extent size (in pages).


Tablespace_free_mb

Counter The amount of free tablespace (in MB).


Tablespace_ managed_type

Information The managed type for the tablespace.


Tablespace_name Information The name of the tablespace.


Tablespace_page_size

Counter The size of pages in the tablespace.


Tablespace_pages_free

Counter The number of tablespace pages currently available.


Field Data Element



Tablespace_pages_usable

Calculation The percentage of the tablespace currently available.


Tablespace_pages_used

Counter The number of tablespace pages currently in use.


Tablespace_ percent_utilization

Calculation The percent of tablespace pages currently in use.

100 * (1 (Tablespace_pages_ free / Tablespace_total_ pages) )

Tablespace_ prefetch_size

Counter The amount of prefetch space included in the tablespace.


Tablespace_size_mb

Counter The total tablespace size (in MB).


Tablespace_state Information The current table space state, represented by a hexadecimal value.


Tablespace_state_code

Information The tablespace state code. This code is displayed only if the table space state is "load pending" or "delete pending".

Stated will be delimited by a colon and a space

Field Data Element



Database_TablespacesTopBP TableThe fields included in this table are as follows:

Tablespace_total_pages

Counter The total tablespace pages.


Field Data Element




(pool_async_data_ reads + pool_async_index_ reads) / pool_async_data_ read_reqs


Counter The number of pages read asynchronously into the buffer pool.



Counter The number of times a buffer pool data page was physically written to disk by either an asynchronous page cleaner, or a prefetcher.


Field Data Element



Async_pool_ index_page_reads

Counter The number of index pages read asynchronously into the buffer pool by a prefetcher.

pool_async_index_ reads

Async_pool_ index_page_ writes

Counter The number of times a buffer pool index page was physically written to disk by either an asynchronous page cleaner, or a prefetcher.

pool_async_index_ writes




Async_read_time Time The time spent reading by database manager prefetchers.

pool_async_read_time

Async_write_time Time The time spent writing data or index pages from the buffer pool to disk by database manager page cleaners.




pool_data_l_reads

Field Data Element





pool_data_p_reads



pool_data_writes



(pool_index_l_ reads + pool_data_I_reads) / (pool_data_p_reads + pool_index_p_reads + pool_data_l_reads + pool_index_l_reads) * 100



pool_index_l_reads



pool_index_p_reads



pool_index_writes



pool_read_time

Field Data Element




Time The amount of buffer pool write time (milliseconds).

pool_write_time






Pool_data_to_estore

Database_name Information The name of the database. Required for drill-down selection.


Database_ tablespace_name

Information Combination of the database and tablespace name to provide uniqueness for a subject field in a graph.

Subject field



direct_read_reqs


direct_read_time


direct_reads

Field Data Element





direct_write_reqs


direct_write_time


direct_writes

Index_hit_ratio Calculation The buffer pool index hit ratio.

Pool_index_l_ reads / (pool_index_l_ reads + pool_index_p_ reads) * 100


Coounter The number of index pages pulled from extended storage.




Pool_index_to_estore

Number_of_ containers

Counter The total number pages in the tablespace.

Output of tablespace query api

Number_of_files_closed

Counter The number of files closed.

files_closed

Tablespace_ID Information The tablespace identification code.

Output of tablespace query api - Subject field

Field Data Element



Tablespace_ extent_size

Counter The tablespace extent size (in pages).


Tablespace_free_mb

Counter The amount of free tablespace (in MB).


Tablespace_ managed_type

Information Type (system managed space or database managed space).

Output of tablespace query api - Subject field

Tablespace_name Information Name of tablespace.

Subject field

Tablespace_page_size

Counter The size of pages in the tablespace.


Tablespace_pages_free

Counter The number of tablespace pages currently available.


Tablespace_pages_usable

Calculation The percentage of tablespace pages currently in use.

Tablespace pages free /Tablespace percent usable

Tablespace_pages_used

Counter The number of tablespace pages currently in use.


Tablespace_ percent_utilization

Calculation The percentage of the tablespace currently available.


Field Data Element



Tablespace_ prefetch_size

Counter The amount of prefetch space included in the tablespace.


Tablespace_size_mb

Counter The total tablespace size (in MB).


Tablespace_state Information The current table space state, represented by a hexadecimal value.


Tablespace_state_code

Information The tablespace state code. This code is displayed only if the table space state is "load pending" or "delete pending".

Stated will be delimited by a colon and a space

Tablespace_total_pages

Counter The total tablespace pages.


Field Data Element



Instance_Agent TableThe fields included in this table are as follows:

Field Data Element


Agent_requests Counter The number of agent requests.

agents_from_pool + agents_created_ empty_pool + agents_stolen

Agents_assigned_from_pool

Counter The number of agents assigned from pool.

agents_from_pool

Agents_created_ due_to_empty_ pool

Counter The number of agents created due to empty pool.

agents_created_ empty_pool

Agents_ dispatchable

Calculation The number of agents that can be dispatched.

agents_registered waiting on lock agents waiting for token

Agents_idle Gauge The number of idle agents.

idle_agents

Agents_registered Gauge The number of registered agents.

agents_registered

Agents_stolen Counter The total number of stolen agents.

agents_stolen

Agents_waiting Calculation The total number of waiting agents.

waiting on lock + agents_waiting_ on_token

Agents_waiting_ on_lock

Gauge The number of agents waiting for a lock.

sum (DBASE.locks_ waiting)


Agents_waiting_ on_token

Gauge The number of agents waiting for a token.

agents_waiting_on_ token

Instance_name Information The name of the instance.

Maximum_agent_overflows

Gauge The maximum number of agent overflows.

max_agent_overflows

Maximum_agents_registered

Watermark The maximum number of registered agents.

agents_registered_top

Maximum_agents_waiting

Watermark The maximum number of waiting agents.

number waiting / (number dispatchable + number waiting) * 100

Maximum_coordinating_agents

Watermark The maximum number of coordinating agents.

coord_agents_top

Percent_of_agents_created

Calculation The percentage of agent requests where an agent was created because the agent pool was empty.

agents_created_empty_pool / agent request * 100

Percent_of_agents_from_pool

Calculation The percentage of agent requests assigned from the agent pool.

agents_from_pool / agent request * 100

Field Data Element



Percent_of_agents_in_use

Calculation The percentage of agents in use.

agents_registered / DbMgrParms.maxagents) * 100

Percent_of_agents_not_from_pool

Calculation The percentage of agent requests that where not from the agent pool.

100 agent from pool percent

Percent_of_agents_stolen

Calculation The percentage of agent requests where agents are stolen when an idle agent associated with an application is reassigned to work on a different application.

Agents_stolen / agent request * 100

Percent_of_agents_waiting

Calculation The percentage of agents waiting.

number waiting / (number dispatchable + number waiting) * 100

Percent_of_agents_waiting_on_ locks

Calculation The percentage of agents waiting on locks.

waiting on lock / (number dispatchable + number waiting) * 100

Percent_of_agents_waiting_on_ tokens

Calculation The percentage of agents waiting on tokens.

agents waiting for token / (number dispatchable + number waiting) * 100

Field Data Element



Percent_of_piped_sorts_rejected

Calculation The percentage of piped sort rejects to piped sort requests computed for all active databases.

(piped_sort_rejects_ count / piped_sorts_requested) * 100

Piped_sort_rejects_count

Counter The number of piped sort rejects.

piped_sorts_requested piped_sorts_ accepted

Sort_heap_percent_utilization

Calculation The percentage of sort heap currently in use.

(Sort_heap_ allocated /(sheapthresh * 1024) ) * 100

Sort_heap_ threshold

Database Manager Configuration Parameter

The sort heap threshold level.

Sheapthresh * 4

Field Data Element



DB2 Agent InvestigationsThe following information is provided to help you start troubleshooting issues that may occur when monitoring your system.

Investigating Application LocksThe DB2_Application_Locking Table view provides details about each lock that the application currently holds and each lock on which the application is waiting. This information can help you pinpoint deadlocks that this application is causing or experiencing. You can also determine whether this application is reaching the maximum number of locks available to it. Application data is the sum, or roll up, of all clients connected using each specific application.

The following lock activity is shown:

• Application Name

Investigating Application Locks Investigating Database Manager Resources

Investigating Application Memory Investigating Database Memory

Investigating Application Sorting Investigating Database Memory Application Sections

Investigating Application SQL Statistics Investigating Database Memory Catalog Cache

Investigating Database Buffer Pool Usage

Investigating Database Memory Database Heap

Investigating Database Connectivity Investigating Database Memory Package Cache

Investigating Database Internal Statistics

Investigating HADR

Investigating Database IO Investigating Tablespace Bufferpool Hit Rates

Investigating Database Log IO Investigating Tablespace Space

Investigating Database Log Space


• Locks Held—The total of number of locks the application is holding.

• Locks Waiting—The total number of locks on which the application is waiting.

• Lock Timeouts—The number of times that a request to lock an object timed out instead of being granted. Use this information to help you adjust the setting of the LOCKTIMEOUT database configuration parameter. When the number of lock timeouts becomes excessive compared to normal operating levels, the following conditions might exist:

• An application is holding locks for long durations.• The LOCKTIMEOUT value needs to be higher. On the other hand, if you have

very few lock timeouts, the LOCKTIMEOUT parameter might be set too high. If the LOCKTIMEOUT value is too low, applications can experience high lock wait times.

• Lock escalation—Lock escalation occurs when an application is reaching its lock list space maximum or when the lock list space used by all applications is approaching the total amount allocated for a database.

• Deadlocks detected—The number of deadlocks that have occurred in the database. If this number is high, applications are experiencing contention problems caused by any of the following conditions:

• Lock escalations are occurring in the database• An application is locking tables explicitly when system-generated row locks

are sufficient• An application is using an inappropriate isolation level during the bind process• Catalog tables are locked for repeatable reads• Applications are obtaining identical locks in different orders, resulting in

deadlocks

• Exclusive Lock Escalation—The number of locks that were escalated from several row locks to one exclusive table lock, or the number of times an exclusive lock on a row caused the table lock to become an exclusive lock. Other applications cannot access the data held by an exclusive lock. Therefore, it is important to track exclusive locks to prevent their impact on the concurrency of your data.

• Lock Waiting time—The total time agents spent waiting on locks.


Start with the Application Locking Table

The DB2_Application_Locking Table view displays the lock information.

• Drill down on the Database Application row to view more details about the selected database with the DB2_Client_Top_Lock_Usage Table view.

Investigating Application MemoryIn general, caches enhance the performance of a database when their respective hit rates are high. The hit rate is the ratio of retrieval requests that were satisfied by data already in the cache to the number of all requests—those satisfied by the cache plus those that required a disk read. If you discover a cache usage issue for a specific database, use this information to help determine whether the selected application is contributing to the problem.

Application data is the sum, or roll up, of all clients connected using each specific application.

The DB2_Application_Memory Table view shows the impact the application has on the database by using memory usage statistics for the following:

• Package cache—This is memory that temporarily stores package and section information required for the execution of static and dynamic SQL statements. When applications obtain static SQL information from package cache, they eliminate I/O on system catalogs. When applications obtain dynamic SQL information from the package cache, they avoid the cost of compiling the SQL statements.

• Catalog cache—This is memory that temporarily stores table descriptors -- information about tables, views, and aliases in a condensed internal format -- found in the database catalog. During SQL statement compilation and dynamic SQL processing, the catalog cache is searched first for descriptors of objects referenced in the SQL statement. If these descriptors are available in cache, the transaction uses descriptor information in cache and avoids having to access the database catalog. High catalog cache hit rates indicate that the I/O required to compile SQL statements is minimal. When the hit rate is low, catalog cache is not being used efficiently.

• SQL work area—Agents have access to a SQL work area where the working copy of any executable section is stored. In partitioned databases, all non-SMP agents share this area. In other environments and with SMP agents, each agent has its own unique SQL work area. If the SQL work area hit rate for the database


is low, the Application Memory Table tells you whether the selected application is contributing to the problem.

• Buffer pools—A buffer pool is memory that temporarily stores data pages from the database. If an application needs to read a page of data, and that page is already in the buffer pool, the application reads the page from the buffer pool, a process that is faster than retrieving the page from disk. Avoiding disk I/O is a critical issue when you are trying to improve database performance. When the buffer pool hit rate is high, many of the index and data pages required to satisfy a query are found in the buffer pool. In general, when the buffer pool hit rate is low, I/O is required to load the required pages from external storage. Certain applications have low buffer hit rates for various reasons. Applications (such as data warehousing applications) that perform frequent table scans of large tables see little buffer pool improvement even with large buffer pools.

Start with the Application Memory Table

The DB2_Application_Memory Table view displays the application memory information.

• Drill down on the Database Application row to view more details about the selected database with the DB2_Client_Top_Cache_Usage Table view.

Investigating Application SortingAn application query often requires that retrieved rows be put in a specific order, or sorted, to satisfy an SQL ORDER BY clause to construct an index, or to perform a hash join. Sort heap is a block of memory that the database manager allocates to an application as workspace whenever the application requires a sort. The DB2_Application_Sorting Table view shows sort activity performed on each selected application.


The following information is returned through the Application Sorting Table:

• Sort times—Use the data in the Sort time field compared to total CPU time for the application. A high ratio could be an indication of inefficient sorting.


• Sort overflows—Sort overflows are sorts that ran out of sort heap and require disk space for temporary storage. If the percentage of overflowed sorts is high, increase the sort heap.

• Hash joins—Join overflows count the number of times that hash join data exceeded the available sort heap space. Join small overflows count the number of times that hash join data exceeded the available sort heap space by less than 10%. Consider the following:

• If the "small overflows" and "overflows" values are high, then you should consider increasing the sort heap threshold. If these values are greater than 10% of the available sort heap space, then you should consider increasing the sort heap size.

• At the database level, if the percentage of "Hash Join Small Overflows" is greater than 10% of the available sort heap space, then you should consider increasing the sort heap size. Values at the application level can be used to evaluate hash join performance for individual applications.

Start with the Application Sorting Table

The DB2_Application_Sorting Table view displays the sorting information.

Investigating Application SQL StatisticsSQL statements of various forms, grouped into transactions, are used to communicate data between the DBMS and an end user or other client program. An examination of the SQL usage statistics provided in the DB2_Application_SQL_Statistics Table view can assist you in keeping track of the behavior of your applications.


The Application Statistics SQL provides counts for the following SQL statement activity:

• Static Statements—The total number of static statements.

• Static SQL Per Sec—The number of static statements per second.

• Dynamic Statements—The total number of dynamic statements.

• Dynamic SQL Per Sec—The number of dynamic statements per second.

• Select Statements—The total number of SQL SELECT statements.


• UID Statements—The total number of SQL UPDATE, INSERT, and DELETE statements.

• DDL Statements—The total number of SQL Data Definition Language (DDL) statements. Because DDL statements rely heavily on the system catalog tables they are expensive to run. If you have a high count for these statements, determine the cause and try to limit their use.

• Commit Statements—The total number of SQL COMMIT statements. A low number in this field could mean infrequent commits by the application, causing possible issues with data concurrency and log I/O.

• Rollback Statements—The total number of SQL ROLLBACK statements. Use this number to assess whether or not there is an unacceptable level of conflict with other applications. In general a high number of rollbacks is undesirable.

• Failed Statements—The total number of SQL statements that did not execute.

• Binds/Precompiles—The total number of binds and precompiles. Binds that occur because of the REBIND PACKAGE command are included, but internal automatic rebinds are not.

• Rows Read

• Rows Written

• Rows Selected

• Rows Updated

• Rows Inserted

• Block Cursor Req Accept—The total number of requests for an I/O block accepted.

• Block Cursor Req Reject—The total number of requests for an I/O block rejected.

Start with the Application SQL Statistics Table

The DB2_Application_SQL_Statistics Table view displays the SQL statistical information.

• Drill down on the Database Application row to view more details about the selected database with the DB2_Client_Top_CPU_Usage Table view.


Investigating Database Buffer Pool UsageThe Buffer Pool component monitors one or more buffer pools allocated for the database. A buffer pool is memory that temporarily stores data and index pages from the database. If an application needs to read a data or index page and that page is already in the buffer pool, the application reads the page from the buffer pool—a process that is faster than retrieving the page from disk. Avoiding disk I/O is a critical issue when you are trying to improve database performance.

Start with the Bufferpool Analysis graph

The DB2_Bufferpool_Analysis Graphview displays buffer pool hit ratio statistics about each listed database. Click anywhere in the graph to display the graph's data in tabular format.

• To view more detailed bufferpool information for the selected database, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click Bufferpool Detail in the list of available views to open the DB2_Bufferpool_Detail Table view.

Investigating Database Internal StatisticsIf an SQL statement causes a large number of internal changes, causing referential integrity restraints to be enforced, you might re-evaluate the design of the table referenced in the statement to determine whether the parameters defined for the table field are necessary.

Use the Database Connection Internal Statistics Graph to view the following statistics:

• Internal Commits—The total number of commits initiated internally by the database manager.

• Internal Rollbacks—The total number of rollbacks initiated internally by the database manager. An internal rollback occurs when an action cannot complete successfully.

• Internal Rows Deleted—An ON CASCADE DELETE referential constraint, or a trigger being fired, can result in internal delete activity. If you observe a large number of internal deletes, you might re-evaluate the design of the table referenced in the statement to determine whether the referential constraints or triggers defined for the table are necessary.

• Internal Rows Updated—SET NULL row update activity enforcing a referential constraint defined with the ON DELETE SET NULL rule, or from a trigger being


fired can result in internal update activity. If you observe a large number of internal updates, you might re-evaluate the design of the table referenced in the statement to determine whether the referential constraints defined for the table are necessary.

• Internal Automatic Rebinds—Automatic rebinds are the binds the system performs when an package has been invalidated. The rebind is performed the first time that the database manager needs to execute an SQL statement from the package. Since internal automatic rebinds can have a significant impact on performance, they should be minimized where possible. You can also use this element to determine the percentage of rebind activity. This information can be useful for analyzing application activity and throughput.

• Internal Rollbacks Due to Deadlock—The total number of forced rollbacks initiated by the database manager due to a deadlock. This element shows the number of deadlocks that have been broken and can be used as an indicator of concurrency problems. Internal rollbacks due to deadlocks lower the throughput of the database.

Start with the Database Connection Internal Statistics graph

• The DB2_Database_Connection_Internal_Statistics Graph view displays internal functionality statistics for each listed database.

Investigating Database ConnectivityThe number of applications currently connected to a database affects the amount of system resources being used. You can adjust your application and agent parameters to better fit this usage.

Database Connectivity tracks statistics about current connections to the database. The following statistics are captured:

• Client_percent_active— The ratio, expressed as a percentage of active clients, to the total number of applications currently connected to the database.

• Percentage of AVG_APPLS parameter value—The ratio, expressed as a percentage, of the number of applications currently connected in the database to the average number of active applications defined by the AVG_APPLS database configuration parameter.

• Percentage of MAXAPPLS parameter value—The ratio, expressed as a percentage, of the number of applications currently connected in the database to


the maximum number of active applications allowed for the database, as defined by the MAXAPPLS database configuration parameter.

Start with the Database Connection Analysis graph

• The DB2_Database_Connection_Analysis Graph view displays application connection statistics for each listed database.

Investigating Database IOThe most important factor in minimizing database I/O is having properly tuned buffer pools. In general a properly configured buffer pool will have a "high" hit rate; that is, the more pages that can be read from the buffer the better your database will perform. As applications require it, data is read from disk into the buffer. When and how this occurs can also affect database performance. Note the following:

• Synchronous I/O—Pages that are read into the buffer by the application agent as part of query processing. Synchronous data reads occur when a query requires an index page that is not already in the buffer pool. The system must read these pages from disk into the buffer pool before execution of the query can continue.

• Asynchronous I/O—Pages that are read into the buffer by prefetchers before these pages are actually needed by the query, are asynchronous because they are performed outside of actual query processing. Asynchronous reads do not block query processing while data pages are retrieved.

Performance could be an issue if you have consistently high rates for the following activities on specific databases:

• Physical read rates (compared to logical read rates)

• Synchronous read or write rates

• Direct I/O rates for a database

These high rates might be indications of performance degradation since the activities involve disk I/O and slow-downs in query processing.

Start with the Database IO Analysis graph

• The DB2_Database_IO_Analysis Graph view displays physical, logical, direct, asynchronous, and synchronous read and write statistics for each listed database.


Investigating Database Log IOThese counters are tallying the total amount of log I/O, as pages per second, for the monitored database.

• Log reads—The number of log reads per second at the database level. This is the rate at which the logger is reading log records from disk to memory during database recovery.

• Log writes—The number of log writes per second at the database level. This is the rate at which the logger is writing log records from log buffers to disk for the database.

Start with the Database IO Log graph

The DB2_Database_IO_Log Graph view displays log read and write statistics for each listed database. Click in the graph to display the graph's data in tabular format.

• To view more detailed log I/O information for the selected database, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Database IO Detail icon in the list of available views to open the DB2_Database_IO_Detail Table view.

Investigating Database Log SpaceLog space is the number of times page cleaners were invoked to write dirty pages to disk (or to extended storage) because the amount of logging space used had reached the predefined limit for the database.

Page cleaner agents perform I/O that database agents would otherwise have to perform. As a result, your applications might run faster because transactions are not forced to wait while their database agents write pages to disk.

The Log space component provides statistics about log space usage in the database. The following statistics are gathered:

• Utilization—The percentage of available active log space in the database that is currently being used to hold uncommitted transactions.

• Secondaries—The number of secondary logs currently being used in the database.


Start with the Database Log Space graph

The DB2_Database_Log_Space Graph view displays log usage statistics for each listed database. Click anywhere in the graph to display the graph's data in tabular format.

• To display more detailed log usage information for the databases, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Database Log Analysis icon in the list of available views to open the DB2_Database_Log_Analysis Table view.

Investigating Database Manager ResourcesProper allocation of the database manager's resources optimizes system performance. Use the Database Manager Overview graph to evaluate the following items:

• Agent information—This graph tracks the allocation of registered DB2 agents in various ways. In addition to monitoring the number of registered agents in use and the number of created agents, Foglight monitors the number of agents assigned from the agent pool, number of agents stolen to work on this application, total number of agents waiting, number of agents waiting on locks, and number of agents waiting for tokens (permission to execute a unit of work against the database).

• Piped Sort rejections—If sorted information can return directly without requiring a temporary table to store a final, sorted list of data, it is referred to as a piped sort. Piped sorts are rejected if the sort heap threshold will be exceeded when the sort heap is allocated. Excessive piped sort rejections may indicate inappropriate sortheap or database manager sheapthres configuration parameters.

• Sort Heap Utilization—A sort heap area is the memory that the database manager allocates to an application when a sort is requested. Sorting is often required for a query. Additionally, some SQL statements require multiple, concurrent sorts, each requiring dedicated sort heap. Therefore, configuring sort heap areas is critical to query performance. Sort heap is controlled by the SHEAPTHRES database manager configuration parameter, which sets the sort heap threshold for the entire instance and by the SORTHEAP database configuration parameter, which sets the sort heap size per sort.

Start with the Database Manager Overview graph

• The DB2_Database_Manager_Overview Graph view displays statistics about each listed database.


Investigating Database MemoryThe DB2 Agent gathers statistics about the usage of memory resources.

Use the DB2_Database_Overview Table view and DB2_Database_Memory_Analysis Graph view to view the following statistics:

• Database heap max used—This figure can be used to evaluate the effectiveness of the current value of the DBHEAP database configuration parameter. This value limits the amount of storage that can be allocated for database heap.

• Package cache hit ratio—The package cache hit ratio tells you whether or not the package cache is being used effectively. If the hit ratio is high (more than 0.8), the cache is performing well. A smaller ratio may indicate that the package cache should be increased.

• Catalog cache hit ratio—High catalog cache hit rates indicate that the I/O required to compile SQL statements is minimal. When the hit rate is low, the catalog cache is not being used efficiently.

• Sort Heap Used—Insufficient sort heap allocation causes the database manager to select less efficient sorting techniques that can severely impact system performance.

• Sort Overflow—The average number of times a sort ran out of sort heap (and might have required disk space for temporary storage) per observed execution of this SQL statement.

• Lock List Used—The memory allocated for locks in a database. As the lock list exceeds thresholds, database performance degrades.

Start with the Database Overview table

The DB2_Database_Overview Table view displays memory, cache, lock and log statistics for each listed database.

• Drill down on the DB Heap Max Use row to view additional heap usage information for the selected database with the DB2_Database_Memory_Database_Heap Graph view.

• Drill down on the Catalog Cache Hit row to view additional catalog cache information for the selected database with the DB2_Database_Memory_Catalog_Cache Graph view.

• Drill down on the Package Cache Hit row to view additional package cache information for the selected database with the DB2_Database_Memory_Package_Cache Graph view.


• Drill down on the Sort Heap Used row to view additional sort information for the selected database with the DB2_Database_Sort_Analysis Table view.

• Drill down on the Total Sorts row to view additional sort information for the selected database with the DB2_Application_Sorting Table view.

• Drill down on the Sort Overflows row to view additional sort information for the selected database with the DB2_Database_Sort_Analysis Table view.

• Drill down on the Lock List Used row to view additional lock information for the selected database with the DB2_Application_Locking Table view.

• Drill down on the Locks Held row to view additional lock information for the selected database with the DB2_Database_Lock_Analysis Table view.

• Drill down on the Log Used row to view additional log information for the selected database with the DB2_Database_Log_Space Graph view.

• Drill down on the Log IO row to view additional log information for the selected database with the DB2_Database_IO_Log Graph view.

Continue with the Database Memory Analysis graph

The DB2_Database_Memory_Analysis Graph view displays detailed memory statistics about each listed database. Click anywhere in the graph to display the graph's data in tabular format.

• To display more detailed memory statistics information for these databases, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Database Memory Detail icon in the list of available views to open the DB2_Database_Memory_Detail Table view.

Investigating Database Memory Application SectionsAgents have access to an SQL work area where the working copy of any executable section is stored. In partitioned databases, all non-SMP agents share this area. In other environments and with SMP agents, each agent has its own unique SQL work area.

The following parameters control the size of the SQL work area:

Agent type and environment Configuration parameter

Non-SMP agents in partitioned database environments

APP_CTL_HEAP_SZ


The DB2_Database_Memory_Application_Sections Graph plots the number of lookups in the SQL work area that were satisfied by statement sections already residing in the work area.

Start with the Database Memory Applications Sections graph

The DB2_Database_Memory_Application_Sections Graph view displays statistics about DB2 memory applications sections and lookups. Click anywhere in the graph to display the graph's data in tabular format.

• To display more detailed information about DB2 memory applications sections and lookups, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Database Memory Detail icon in the list of available views to open the DB2_Database_Memory_Detail Table view.

Investigating Database Memory Catalog CacheThe catalog cache is memory that temporarily stores table descriptors, information about tables, views, and aliases in a condensed internal format found in the database catalog. During SQL statement compilation and dynamic SQL processing, the catalog cache is searched first for descriptors of objects referenced in the SQL statement. If these descriptors are available in cache, the transaction uses descriptor information in cache and avoids having to access the database catalog.

Use the DB2_Database_Memory_Catalog_Cache Graph view to view the following statistics:

• Catalog cache inserts—The number of times that the system tried to insert table descriptor information into the catalog cache.

• Catalog cache lookups—Indicates how well the catalog cache is avoiding catalog accesses. If the ratio is high (more than 0.8), then the cache is performing well. A smaller ratio might suggest that the cache size should be increased.

• Catalog Cache Overflows—The cache entries for transactions that compile SQL statements, either by issuing dynamic SQL statements or by binding a package,

Agents in all other environments APPLHEAPSZ

SMP agents in all environments APPLHEAPSZ

Agent type and environment Configuration parameter


will not be eligible to be removed from the cache until that transaction has either been committed or rolled back. Once a transaction has experienced a catalog cache overflow, all subsequent attempts by the same transaction to insert table descriptor information into the catalog cache will also result in an overflow.

• Catalog Cache Heap Full Overflows—The catalog cache draws its storage dynamically from the database heap and even if the cache storage has not reached its limit, inserts into the catalog cache may fail due to a lack of space in the database heap.

• Catalog Cache Hit Ratio—High catalog cache hit rates indicate that the I/O required to compile SQL statements is minimal. When the hit rate is low, the catalog cache is not being used efficiently.

• Catalog Cache Failure Ratio—This cache failure condition can be corrected by increasing the database heap size or reducing the catalog cache size.

Start with the Database Memory Catalog Cache graph

The DB2_Database_Memory_Catalog_Cache Graph view displays the number of inserts, lookups, and overflows for each listed database. Click anywhere in the graph to display the graph's data in tabular format.

• To view more detailed information about the database inserts, lookups, and overflows, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Database Memory Detail icon in the list of available views to open the DB2_Database_Memory_Detail Table view.

Investigating Database Memory Database HeapIf the maximum database heap value matches the database heap size parameters, you may need to increase your storage space. Low database heap can also contribute to catalog cache overflows.

Use the DB2_Database_Memory_Database_Heap Graph view to track your database heap size. The following statistics are displayed:

• Database heap high water mark—The largest amount (in kilobytes) of database heap space allocated and used by the database since the first application connected to the database. Use this data to evaluate the effectiveness of the current value of the DBHEAP database configuration parameter. This value limits the amount of storage that can be allocated for database heap.


• Database heap max utilization—The maximum utilization of the database heap, expressed as a percentage of DBHEAP.

• Database heap size—The size of the database heap (in bytes).

• Database heap utilization percentage—The percentage of the available database heap (whose limits are defined by the DBHEAP database configuration parameter) currently in use.

Start with the Database Memory Database Heap graph

• The DB2_Database_Memory_Database_Heap Graph view displays statistics about heap usage for each listed database.

Investigating Database Memory Package CacheThe Package cache is memory that temporarily stores package and section information required for the execution of static and dynamic SQL statements. When applications obtain static SQL information from the package cache, they eliminate I/O on system catalogs. When applications obtain dynamic SQL information from the package cache, they avoid the cost of compiling the SQL statements.

Use the DB2_Database_Memory_Package_Cache Graph view to view the following statistics:

• Package Cache Inserts—The total number of times that a requested section was not available for use and had to be loaded into the package cache.

• Package Cache Lookups—The number of times that an application looked for a section or package in the package cache. It indicates the overall number of references since the database was started, or monitor data was reset.

• Package Cache Overflows—Use this element to help determine whether the size of the package cache needs to be increased to avoid overflowing. Overflows of the package cache can cause unnecessary lock escalations.

• Package Cache Hit Ratio—The package cache hit ratio tells you whether or not the package cache is being used effectively. If the hit ratio is high (more than 0.8), the package cache is performing well. A smaller ratio may indicate that the size of the package cache should be increased.

• Package Cache Extensions—The percentage of package cache inserts that have resulted in overflows. The package cache is forced to borrow memory from the database shared memory, causing possible lock list escalation and overall performance degradation.


Start with the Database Memory Package Cache graph

The DB2_Database_Memory_Package_Cache Graph view displays the number of inserts, lookups, and overflows for each listed database. Click anywhere on the graph to display the graph's data in tabular format.

• To view more detailed information, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Database Memory Detail icon in the list of available views to open the DB2_Database_Memory_Detail Table view.

Investigating HADRHigh Availability Disaster Recovery (HADR), available in DB2 8.2 ESE, provides a new alternative for delivering a high-availability solution by replicating data (via logs) from a source database, called the primary, to a target database, called the standby.

The DB2 UDB agent includes an overview table and relevant metrics from the DB2 snapshot to report on the state of HADR.

Start with the DB2_HADR_Overview table

• The DB2_HADR_Overview Table view displays the current role, connection status, remote instance, log gap and missed heartbeats for each listed database.

• When monitoring an instance in a HADR pair, verify that the role is 1 (SQLM_HADR_ROLE_PRIMARY) or 2 (SQLM_HADR_ROLE_STANDBY). Ideally, HADR pairs should be as close as possible to peer state in the connected state. In addition, the log gap should be near or at zero.

• If the current HADR situation deviates from the above normal state, consider these scenarios:

• If the connection state is congested, it is possible that the network is under severe load and the database cannot efficiently handle log synchronization.

• If the connection state is disconnected, inspect the configuration parameters of the database or the database manager. Assuming there is a good physical network connection, and all the parameters are accurate, you might consider restarting one or both of the databases.

• If the log gap widens on each collection cycle, the agent will issue a warning. Monitor this situation over time. As resources permit, DB2 should eventually synchronize the HADR pair. A log gap that never narrows warrants a more detailed inspection of the database infrastructure.


• If the agent reports missed heartbeats, this might be an indication that your database infrastructure is under severe loads. In such cases, you should investigate database resource usage (i.e. bufferpools, IO, memory, etc.) or external factors (i.e. excessive client connections, network traffic, etc.).

• To view all the HADR information collected by the agent, examine the Database_HADR Table in the data browser.

• If the Database_HADR Table is not populating at each collection cycle, you might need to issue the command to start HADR in DB2. Since HADR is an optional feature, the agent will not display any warnings when HADR is turned off.

• The DB2 agent can monitor standby databases. However, due to restrictions in DB2, some tables (related to applications or clients) will not populate when a connection to the database cannot be established.

Investigating Tablespace Bufferpool Hit RatesThe DB2_Tablespace_Top_Bufferpool_HitRates Graph view shows the top n (where n is the ASP value you specify) tablespace bufferpool hit rates, arranged in ascending order. Tablespaces not in use (and therefore have bufferpool hit ratios of 100%) do not appear in the graph.

Start with the Tablespace Top Bufferpool HitRates graph

The DB2_Tablespace_Top_Bufferpool_HitRates Graph graph view includes one bar for each of the top n tablespace bufferpool hit rates. The lowest of these hit rates appears closest to the y-axis, and the highest hit rate appears farthest from the y-axis. Click anywhere in the graph to display the graph's data in tabular format.

• To display more detailed information about bufferpool hit rates for this tablespace, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Tablespace Top Bufferpool Details icon in the list of available views to open the DB2_Tablespace_Top_Bufferpool_Details Tableview.

Investigating Tablespace SpaceThe DB2_Tablespace_Top_Space_Utilization Graph view provides details and statistics about the DMS and SMS tablespaces to which the database you are currently monitoring is mapped. When the graph is displayed, it provides high-level information about each of the following:


• Size (Mb)—The size of the tablespace, expressed in megabytes. A size of 0 (zero) indicates an unavailable tablespace state.

• Free (Mb)—The amount of free space in the tablespace, expressed in megabytes.

• Percent Utilized—The percentage of the tablespace currently being used.

Start with the Tablespace Top Space Utilization graph

The DB2_Tablespace_Top_Space_Utilization Graph view displays the size, percentage of available Mb used, and number of Mb free for each listed tablespace. Click anywhere in the graph to display the graph's data in tabular format.

• To display more detailed information about space usage for this tablespace, click the appropriate DB2 agent icon in the client list pane, select View from the Filter by list, then double-click the Tablespace Top Space Details icon in the list of available views to open the DB2_Tablespace_Top_Space_Details Table view.


DB2 Agent ViewsViews are graphs or tabular presentations of data collected by the DB2 agent.

DB2_Database_Manager_Overview GraphThis graph view displays agent data for the active database, as well as sort heap and piped sort data. The values are derived from the following fields in the Instance_Agent Table:

• Agents In Use (%)

• Agents Stolen (%)

• Agents Waiting (%)

• Agents Created (%)

• Agents Created From Pool (%)

• Agents Waiting On Locks (%)

• Agents Waiting On Tokens (%)

• Piped Sorts Rejected (%)

• Sort Heap Used (%)

To open the DB2_Database_Manager_Overview graph

1 Click the DB2 agent icon. A list of graph and table icons displays.


2 Double-click the DB2_Database_Manager_Overview graph icon to display the view.

DB2_Database_Overview TableThis table view provides information about the DB2 database. This table provides an overview of activity on your database.

Drill down to view more details about the selected database. Foglight updates these statistics in real-time so that you see how your system is performing.

These values are derived from the Database_Summary Table:

• Database

• Connections Used (%)

• Agents Used (%)

• Xacts Per Sec

• DB Heap Max Used (%)

• Cat Cache Hit Ratio (%)

• Pkg Cache Hit Ratio (%)


• Sort Overflows (%)

• Lock List Used (%)


• Bufferpool Hit Ratio (%)

• Index Hit Ratio (%)

• Log Used (%)

• Physical I/O (Pg)

• Logical I/O (Pg)

• Direct I/O (Pg)

• Async I/O (Pg)

• Sync I/O (Pg)

• Log I/O (Pg)

To open the DB2_Database_Overview table



2 Double-click the DB2_Database_Overview table icon to display the view.

To start your investigation

• Right-click or drill down on DB Heap Max Used (%) row to display information about database heap usage on the DB2_Database_Memory_Database_Heap Graph view.

• Right-click or drill down on Cat Cache Hit Ratio (%) row to display information about the catalog cache on the DB2_Database_Memory_Catalog_Cache Graph view.

• Right-click or drill down on Pkg Cache Hit Ratio (%) row to display package cache usage information on the DB2_Database_Memory_Package_Cache Graph view.


• Right-click or drill down on Sort Heap Used (%) row to display sort and hash join statistics for each DB2 database on the DB2_Database_Sort_Analysis Table view.

• Right-click or drill down on Sort Overflows (%) row to display sort and hash join statistics for each DB2 database on the DB2_Database_Sort_Analysis Table view.

• Right-click or drill down on Lock List Used (%) row to display sort and hash join statistics for each DB2 database on the DB2_Database_Lock_Analysis Table table view.

• Right-click or drill down on Log Used (%) row to display information about total and secondary log space usage on the DB2_Database_Log_Space Graph view.

• Right-click or drill down on Log I/O (Pg) row to display information about log page reads and writes per second at the instance interval on the DB2_Database_IO_Log Graph view.

DB2_HADR_Overview TableUse the DB2_HADR_Overview table view to collect data only when a database is configured for HADR and its hadr_role is either SQLM_HADR_ROLE_PRIMARY or SQLM_HADR_ROLE_STANDBY.

For more information, see Investigating HADR.

These values are derived from the Database_HADR Table:

• Database

• Remote Instance

• Remote Host

• HADR Role

• HADR State

• Connection Status

• Missed Heartbeats

• Log Gap

To open the DB2_HADR_Overview table



2 Double-click the DB2_HADR_Overview table icon to display the view.

DB2_Application_Locking TableThis table view provides lock statistics for each application in the DB2 database. For more information on these statistics, see Investigating Application Locks.

These values are derived from the Client_Locking Table:

• Database Application

• Locks Held

• Lock Waits

• Locks Waiting

• Lock Timeouts

• Lock Escalations

• Deadlocks Detected

• Excl Lock Escalations

• Lock Wait Time(s)

• Avg Lock Wait Time(s)


To open the DB2_Application_Locking table


2 Double-click the DB2_Application_Locking table icon to display the view.


• Drill down on the Database Application row to view information about the number of locks that the application currently holds, limited to the top consumers of locks held as defined in the ASPs with the DB2_Client_Top_Lock_Usage Table view. The table displays if the application is running an SQL statement at the time the sample is taken.

DB2_Application_Memory TableThis table view provides statistics for each application in the DB2 database. It displays statistics relating to:

• Application section—Application hit ratio is the percentage of lookups in the SQL work area that were satisfied by statement sections already residing in the work area. This is the ratio of physical data and index reads to logical data and index reads for this application, expressed as a percentage.

• Catalog cache—Memory that temporarily stores table descriptors—information about tables, views, and aliases in a condensed internal format—found in the


database catalog. A transaction that compiles an SQL statement looks in the catalog cache first for descriptors of objects referenced in the SQL statement. If these descriptors are available in cache, the transaction uses descriptor information from the cache and avoids having to access the database catalog.

• Package cache—Memory that temporarily stores package and section information required for the execution of static and dynamic SQL statements. When applications obtain static SQL information from package cache, they eliminate I/O on system catalogs. When applications obtain dynamic SQL information from package cache, they avoid the cost of compiling the SQL statements.

These values are derived from the Application_Memory Table:


• Appl Section Hit Ratio (%)

• Appl Section Lookups

• Appl Section Inserts

• Cat Cache Hit Ratio (%)

• Cat Cache Failure (%)

• Cat Cache Overflows

• Cat Cache Full Overflows

• Cat Cache Inserts

• Cat Cache Lookups


• Pkg Cache Inserts

• Pkg Cache Lookups

For more information, see Investigating Application Memory.

To open the DB2_Application_Memory table



2 Double-click the DB2 Application Memory table icon to display the view.


• Right-click or drill down on the Database Application row to the DB2_Client_Top_CPU_Usage Table view to view information about cache usage in the DB2 application, limited to the top consumers of total cache inserts as defined in the ASPs. The table displays if the application is running an SQL statement at the time the sample is taken.

DB2_Application_SQL_Statistics TableThis table provides statistics about SQL statements for each application in the DB2 database.

For more information, see Investigating Application SQL Statistics.

These values are derived from the Application_Connection Table:


• Static Statements


• Static SQL Per Sec

• Dynamic Statements

• Dynamic SQL Per Sec

• Select Statements

• UID Statements

• DDL Statements

• Commit Statements

• Rollback Statements

• Failed Statements

• Binds / Precompiles

• Rows Read

• Rows Written

• Rows Selected

• Rows Updated

• Rows Inserted

• Rows Deleted

• Block Cursor Req Accept

• Block Cursor Req Reject

To open the DB2_Application_SQL_Statistics table



2 Double-click the DB2_Application_SQL_Statistics table icon to display the view.


• Drill down on the Database Application row to display information about total sort activity generated by the application, limited to the top consumers of total sort time as defined in the ASPs. with the DB2_Client_Top_Sort_Usage Table view. The table displays if the application is running an SQL statement at the time the sample is taken.


DB2_Application_Sorting TableThis table view provides sort and hash join statistics per monitoring interval for each application in the DB2 database.

For more information, see Investigating Application Sorting.

These values are derived from the Application_Sorting Table:


• Sort Time (ms)

• Avg Sort Time (ms)

• Total Sorts

• Sort Overflows

• Sort Overflow (%)

• Hash Joins

• Hash Loops

• Hash Join Overflows

• Hash Join Overflow (%)

• Hash Join Sm Overflows

• Hash Join Sm Overflow (%)

To open the DB2_Application_Sorting table



2 Double-click the DB2_Application_Sorting table icon to display the view.


Drill down on the Database Application row to display information about total sort activity generated by the application, limited to the top consumers of total sort time as defined in the ASPs. with the DB2_Client_Top_Sort_Usage Table view. The table displays if the application is running an SQL statement at the time the sample is taken.

DB2_Bufferpool_Analysis Graph This graph view provides information about buffer pool hit ratios in the DB2 database. The values are derived from the following fields in the Database_Bufferpools Table:

• Overall Hit Ratio (%)


Buffer pool hit ratio is the percentage of read requests for data and index pages instance-wide that were satisfied by a page found in a buffer pool.


To open the DB2_Bufferpool_Analysis graph


2 Double-click the DB2 Bufferpool Analysis graph icon to display the view.

To display graphed data in table format

Press CTRL + Left-click the Overall Hit Ratio icon in the graph display. A table is created that shows the hit ratio data for all databases within the instance in a tabular format.

Understanding the dataWhen the buffer pool hit ratio is high, many, if not all, of the index and data pages required to satisfy a query are found in a buffer pool. When the buffer pool hit ratio is low, I/O is required to load the requested pages from external storage.

This does not mean however, that all low hit ratios are cause for concern. Certain applications have low buffer hit rates for a variety of reasons. For example, applications (such as data warehousing applications) that perform frequent table scans of large tables see little buffer pool hit ratio improvement even with large buffer pools.

So, as a general guideline, the higher the hit ratio the better, bearing in mind that certain types of activity will almost always produce low ratios.


• Drill down on the Overall Hit Ratio (%) bar to view details about buffer pool activity for each DB2 database with the DB2_Bufferpool_Detail Table view.


DB2_Bufferpool_Detail TableThis table provides details about buffer pool activity for each DB2 database.

If an application needs to read a page of data, and that page is already in the buffer pool, the database manager reads the page from the buffer pool, a process that is faster than retrieving the page from disk. Avoiding disk I/O is a critical issue when you are trying to improve database performance.

For more information, see Investigating Database Buffer Pool Usage.

These values are derived from the Database_Bufferpools Table:

• Database

• Bufferpool

• Size (Kb)

• Page Size (Kb)

• Number of Pages

• Overall Hit Ratio (%)


• Files Closed

• Pool Read Time (ms)

• Pool Write Time (ms)

• Async Read Time (ms)

• Async Write Time (ms)

• Async Reads Per Req

• Async Data Reads

• Async Data Writes

• Async Index Reads

• Async Index Writes

• Async Read Reqs

• Logical Data Reads

• Logical Index Reads

• Physical Data Reads


• Physical Data Writes

• Physical Index Reads

• Physical Index Writes

• Direct Reads

• Direct Writes

• Direct Read Reqs

• Direct Write Reqs

• Direct Read Time (ms)

• Direct Write Time (ms)

• Data Pgs From Estore

• Index Pgs From Estore

• Data Pgs To Estore

• Index Pgs To Estore

To open the DB2_Bufferpool_Detail table



2 Double-click the DB2_Bufferpool_Detail table icon to display the view.

DB2_Client_Top_CPU_Usage TableThis table view provides information about CPU time that this application has spent executing database manager code in the database, limited to the top consumers of total CPU time as defined in the ASPs. The table view displays if the application is running an SQL statement at the time the sample is taken.

These values are derived from the Client_Connection Table:


• Execution ID


• Application ID

• SQL Statement

• Total CPU (s)

• User CPU (s)

• System CPU (s)

To open the DB2_Client_Top_CPU_Usage table


2 Double-click the DB2_Client_Top_CPU_Usage table icon to display the view.

DB2_Client_Top_Cache_Usage TableThis table view provides information about cache usage in the DB2 application, limited to the top consumers of total cache inserts as defined in the ASPs. The table view displays if the application is running an SQL statement at the time the sample is taken.

These values are derived from the Client_Memory Table:


• Execution ID

• Application ID


• SQL Statement

• Total Cache Inserts




To open the DB2_Client_Top_Cache_Usage table


2 Double-click the DB2_Client_Top_Cache_Usage table icon to display the view.

DB2_Client_Top_Lock_Usage TableThis table provides information about the number of locks that the application currently holds, limited to the top consumers of locks held as defined in the ASPs. The table displays if the application is running an SQL statement at the time the sample is taken.

Use this number to determine whether the application is reaching the maximum number of locks available to it.

These values are derived from the Client_Locking Table:



• Execution ID

• Application ID

• SQL Statement

• Locks

• Timeouts

• Deadlocks

To open the DB2_Client_Top_Lock_Usage table


2 Double-click the DB2_Client_Top_Lock_Usage table icon to display the view.

DB2_Client_Top_Sort_Usage TableThis table view provides information about total sort activity generated by the application, limited to the top consumers of total sort time as defined in the ASPs. The table view displays if the application is running an SQL statement at the time the sample is taken.

These values are derived from the Client_Sorting Table:



• Execution ID

• Application ID

• SQL Statement

• Sort Time (ms)

• Avg Sort Time (ms)

To open the DB2_Client_Top_Sort_Usage table


2 Double-click the DB2_Client_Top_Sort_Usage table icon to display the view.

DB2_Database_Connection_Analysis GraphThis graph view tracks the number of applications connected to the database that are executing transactions. The values are derived from the following fields in the Database_Connection Table:

• Active (%)

• Avg Appl (%)

• Max Appl (%)


To open the DB2_Database_Connection_Analysis graph


2 Double-click the DB2_Database_Connection_Analysis graph icon to display the view.

DB2_Database_Connection_Detail TableThis table view provides information about DB2 database connections, including:

• Identification information for the selected database

• Key statistics that provide an overview of database activities during the last monitoring interval.

For more information, see Investigating Database Connectivity.

These values are derived from the Database_Connection Table:

• Database

• Xacts Per Sec

• Active Connections

• Current Connections

• Max Concurrent

• Active (%)


• Avg Appl (%)

• Max Appl (%)

To open the DB2_Database_Connection_Detail table


2 Double-click the DB2_Database_Connection_Detail table icon to display the view.

DB2_Database_Connection_Internal_Statistics GraphThis graph view provides statistics about the rate at which applications and the database manager are completing commits and rollbacks within the database. The values are derived from the following fields in the Database_Connection Table:

• Commits

• Rollbacks

• Rows Deleted

• Rows Updated


• Automatic Rebinds

• Rollbacks Due to Deadlock

To open the DB2_Database_Connection_Internal_Statistics graph


2 Double-click the DB2_Database_Connection_Internal_Statistics graph icon to display the view.

DB2_Database_Connection_SQL_Statistics TableThis table view provides information about DB2 SQL statistics for dynamic and static SQL statements, executed against the monitored database.

These values are derived from the Database_Connection Table:

• Database

• Static Statements

• Static SQL Per Sec

• Dynamic Statements

• Dynamic SQL Per Sec

• Select Statements

• UID Statements

• DDL Statements


• Commit Statements

• Rollback Statements

• Failed Statements

• Binds / Precompiles

• Rows Selected

• Rows Updated

• Rows Inserted

• Rows Deleted

To open the DB2_Database_Connection_SQL_Statistics table


2 Double-click the DB2_Database_Connection_SQL_Statistics table icon to display the view.


DB2_Database_IO_Agent_Analysis TableThis table view provides agent information for the DB2 database, including the number of prefetchers and page cleaners defined for the database.

• Page cleaners—Write pages asynchronously to disk. In other words, they perform I/O that would otherwise be performed by database agents and perform this I/O outside of the program instruction processing. As a result, your applications run faster because transactions are not forced to wait while their data agents write pages to disk. Page cleaners help to ensure free pages in the buffer pool for database agents and to allow faster recovery of the database should a system crash occur.

• Prefetchers—Read specific index and data pages into the buffer pool, anticipating an application’s need for these pages. Because these reads are asynchronous, that is, they are performed outside of program instruction processing, prefetchers can improve performance by reducing the time spent waiting for I/O to complete.

These values are derived from the Database_IO Table:

• Database

• Prefetchers

• Prefetch Wait Time (ms)

• Prefetch Reads Per Sec

• Prefetch Read Rate (%)

• Page Cleaners

• Pg Clean Writes Per Sec

• Pg Clean Write Rate (%)

• Dirty Pg Steal Clean Trig

• Dirty Pg Thresh Clean Trig

• LSN Gap Cleaner Trig

To open the DB2_Database_IO_Agent_Analysis table



2 Double-click the DB2_Database_IO_Agent_Analysis table icon to display the view.

DB2_Database_IO_Analysis GraphThis graph view provides information about data and index page reads and writes that occurred in the database within the last monitoring interval. The values are derived from the following fields in the Database_Summary Table:

• Physical_IO (Pg)

• Logical_IO (Pg)

• Async_IO (Pg)

• Sync_IO (Pg)

• Direct_IO (Pg)

To open the DB2_Database_IO_Analysis graph



2 Double-click the DB2_Database_IO_Analysis graph icon to display the view.

DB2_Database_IO_Async TableThis table view provides statistics about page cleaners, and sometime prefetchers, as they write buffer pool pages to the database. These writes are asynchronous because they are not part of the processing of program instructions, and therefore can run in parallel with database agent processes.

Page cleaners write pages to disk to ensure free pages in the buffer pool for database agents and to allow faster recovery of the database should a system crash occur. Prefetchers typically read data and index pages into the buffer pool, anticipating an application’s need for these pages. However, prefetchers might need to write pages from the buffer pool to disk to make space for the pages they are prefetching.


• Database

• Async Reads

• Async Writes






• Async Read Time (ms)

• Async Write Time (ms)

• Async Reads Per Sec

• Async Writes Per Sec

• Async Read Reqs

• Async Reads Per Req

• Prefetch Wait Time (ms)

• Prefetch Read Ratio (%)

To open the DB2_Database_IO_Async table


2 Double-click the DB2_Database_IO_Async table icon to display the view.


DB2_Database_IO_Detail TableThis table view provides detailed information about the different types of database I/O.

• Asynchronous reads and writes—These reads and writes are not part of the processing of program instructions, and therefore can run in parallel with database agent processes.

• Logical reads and writes—These reads and writes involve information read from the tablespace into the buffer pool, or accesses to information already in the buffer pool.

• Physical reads and writes—These reads and writes require I/O to move information from the tablespace into the buffer pool.

• Direct reads and writes—These reads and writes do not use the selected buffer pool to do so. Instead, they read and write directly to and from the database.

• Synchronous reads and writes—These reads and writes occur when a query asks for a page that is not already in the buffer pool, requiring system resources to read or write these pages before execution of the query can continue.


• Database





• Logical Index Reads

• Logical Data Reads

• Physical Index Reads

• Physical Data Reads

• Physical Data Writes

• Physical Index Writes

• Direct Reads

• Direct Writes

• Sync Reads

• Sync Writes


To open the DB2_Database_IO_Detail table


2 Double-click the DB2_Database_IO_Detail table icon to display the view.

DB2_Database_IO_Direct TableThis table view provides information about direct reads and writes into the database, bypassing the buffer pool.


• Database

• Direct Reads

• Direct Writes

• Direct Read Time (ms)


• Direct Write Time (ms)

• Direct Reads Per Sec

• Direct Writes Per Sec

• Direct Read Reqs

• Direct Write Reqs

To open the DB2_Database_IO_Direct table


2 Double-click the DB2_Database_IO_Direct table icon to display the view.


DB2_Database_IO_Log GraphThis graph view provides information about log page reads and writes per second at the instance interval. The values are derived from the following fields in the Database_Logging Table:

• Log Reads (Pg/s)

• Log Writes (Pg/s)

To open the DB2_Database_IO_Log graph


2 Double-click the DB2_Database_IO_Log graph icon to display the view.


• Press CTRL + Left-click on the Log Reads icon in the graph display. A table is created that shows the Log Reads within the instance in a tabular format.


• Right-click or drill down on Log Reads (Pg/s) bar to view information about log files allocated to the database on the DB2_Database_Log_Analysis Table view.


DB2_Database_Lock_Analysis TableThis table view provides locks statistics about locks, waits, and holds for the database over consecutive monitoring intervals.

These values are derived from the Database_Locking Table:

• Database

• Locks Held

• Lock Waits

• Locks Waiting

• Lock Timeouts

• Lock Escalations

• Excl Lock Escalations


• Lock List In Use (Kb)

• Deadlocks Detected

• Lock Wait Time(s)

• Avg Wait Time(s)

To open the DB2_Database_Lock_Analysis table



2 Double-click the DB2_Database_Lock_Analysis table icon to display the view.


• Drill down on the Locks Held row to view lock statistics for each application in the DB2 database with the DB2_Application_Locking Table view.


DB2_Database_Log_Analysis TableThis table view provides information about log files allocated to the database, including:

• Statistics relating to available active log space in the database that is currently being used to hold uncommitted transactions.

• Statistics relating to secondary logs currently being used in the database.

• Statistics relating to log read and writes

These values are derived from the Database_Logging Table:

• Database

• Log Used (%)

• Log Used (Kb)

• Log Available (Kb)

• Max Log Used (Kb)

• Sec Log Used (%)

• Sec Logs Allocated

• Max Sec Log Used (%)

• Log I/O (Pg)

• Log Reads (Pg)

• Log Writes (Pg)

• Log I/O Per Sec (Pg)

• Log Reads Per Sec (Pg)

• Log Writes Per Sec (Pg)

• Xacts Per Sec

• Avg Log Used Per Xact

To open the DB2_Database_Log_Analysis table



2 Double-click the DB2_Database_Log_Analysis table icon to display the view.


DB2_Database_Log_Space GraphThis graph view provides information about total and secondary log space usage. The values are derived from the following fields in the Database_Logging Table:

• Total Log Used (%)

• Secondary Log Used (%)

To open the DB2_Database_Log_Space graph


2 Double-click the DB2_Database_Log_Space graph icon to display the view.


• Press CTRL + Left-click on the Total Log Used icon in the graph display. A table is created that shows the total usage of the log within the instance in a tabular format.


• Right-click or drill down on Total Log Used (%) bar to view information about log files allocated to the database on the DB2_Database_Log_Analysis Table view.


DB2_Database_Manager_Agents TableThis table view provides statistics about application agent usage in the DB2 database.

These values are derived from the Instance_Agent Table:

• Instance

• Registered

• Dispatchable

• Agent Reqs

• Assigned From Pool

• Created - Empty Pool

• Agents Idle

• Agents Stolen

• Agents Waiting

• Waiting on Locks

• Waiting on Tokens

• Max Agents Waiting

• Max Agent Overflows

• Max Agents Registered

• Max Coordinating Agents

To open the DB2_Database_Manager_Agents table



2 Double-click the DB2_Database_Manager_Agents table icon to display the view.


DB2_Database_Memory_Analysis GraphThis graph view provides information about DB2 database memory.

The values are derived from the following fields in the Database_Memory Table:



• Cat Cache Hit Ration (%)

The values are derived from the following fields in the Database_Summary Table:




To open the DB2_Database_Memory_Analysis graph


2 Double-click the DB2_Database_Memory_Analysis graph icon to display the view.


• Press CTRL + Left-click on the DB Heap Max Used icon in the graph display. A table is created that shows the heap usage data for all databases within the instance in a tabular format.



• Right-click or drill down on DB Heap Max Used (%) bar to view information about database memory in the DB2 database on the DB2_Database_Memory_Detail Table view.

DB2_Database_Memory_Application_Sections GraphThis graph view provides information about DB2 memory applications sections and lookups.


• Inserts

• Lookups

Use this graph to evaluate the following items:

• Application Section Inserts — Total count of when a working copy of an executable section copy was not available and had to be inserted.

• Application Section Lookups — Total count of how many times the SQL work area was accessed by an application's agents.

To open the DB2_Database_Memory_Application_Sections graph


2 Double-click the DB2_Database_Memory_Application_Sections graph icon to display the view.



• Right-click or drill down on the Inserts bar to view statistics for each application in the DB2 database. It displays statistics on the DB2_Application_Memory Table view.

DB2_Database_Memory_Catalog_Cache GraphThis graph view provides information about the catalog cache.


• Inserts

• Lookups

• Overflows

• Heap Full Overflows

To open the DB2_Database_Memory_Catalog_Cache graph


2 Double-click the DB2_Database_Memory_Catalog_Cache graph icon to display the view.



Press CTRL + Left-click on the Inserts icon in the graph display. A table is created that shows the catalog cache data for the instance in a tabular format.To start your investigation

• Right-click or drill down on the Inserts bar to view statistics for each application in the DB2 database. It displays statistics on the DB2_Application_Memory Table view.

DB2_Database_Memory_Database_Heap GraphThis graph view provides information about database heap usage.


• Max Used (%)

• Size (Kb)

• Top (Kb)

To open the DB2_Database_Memory_Database_Heap graph


2 Double-click the DB2_Database_Memory_Database_Heap graph icon to display the view.


DB2_Database_Memory_Detail TableThis table view provides information about database memory in the DB2 database, including:

• Application Section—SQL work area inserts and lookups that occurred for the application during the last monitoring interval.

• Catalog Cache—Memory that temporarily stores table descriptors about tables, views, and aliases in a condensed internal format found in the database catalog. A transaction that compiles an SQL statement looks in the catalog cache first for descriptors of objects referenced in the SQL statement. If these descriptors are available in cache, the transaction uses descriptor information in cache and avoids having to access the database catalog.

• Database Heap—The database heap space allocated and used by the database since the first application connected to the database.

• Package Cache—Memory that temporarily stores package and section information required for the execution of static and dynamic SQL statements. When applications obtain static SQL information from package cache, they eliminate I/O on system catalogs. When applications obtain dynamic SQL information from package cache, they avoid the cost of compiling the SQL statements.

These values are derived from the Database_Memory Table:

• Database

• Appl Section Hit Ratio (%)


• Appl Section Lookups

• Cat Cache Hit (%)

• Cat Cache Failure (%)

• Cat Cache Overflows

• Cat Cache Full Overflows


• Cat Cache Lookups

• Cat Cache Size (Kb)

• DB Heap Size (Kb)


• DB Heap Top (Kb)




• Pkg Cache Lookups

• Pkg Cache Overflows

• Pkg Cache Extends (%)

• Pkg Cache Size (Kb)

• Pkg Cache Top (Kb)

To open the DB2_Database_Memory_Detail table


2 Double-click the DB2_Database_Memory_Detail table icon to display the view.


DB2_Database_Memory_Package_Cache GraphThis graph view provides package cache usage information.


• Inserts

• Lookups

• Overflows

To open the DB2_Database_Memory_Package_Cache graph


2 Double-click the DB2_Database_Memory_Package-Cache graph icon to display the view.


• Drill down on the Inserts bar to view statistics for each application in the DB2 database with the DB2_Application_Memory Table view.


DB2_Database_Sort_Analysis TableThis table provides sort and hash join statistics for each DB2 database. This table relates the number of sort and hash join overflows to the total number of sorts and hash joins, respectively, generated by the application.

Sort heap is controlled by the SHEAPTHRES database manager configuration parameter, which sets the sort heap threshold for the entire instance and by the SORTHEAP database configuration parameter, which sets the sort heap size. Sort overflows are sorts that ran out of sort heap and require disk space for temporary storage. Join overflows count the number of times that hash join data exceeded the available sort heap space. Join small overflows count the number of times that hash join data exceeded the available sort heap space by less than 10%.

The Database Sort Analysis table expresses these ratios as percentages:

• Sort overflow - The percentage of sort overflows per monitoring interval. This percentage is based on the ratio of sort overflows to total sorts completed.

• Hash overflow - The percentage of hash joins that encountered insufficient sort heap per monitoring interval. This percentage is based on the ratio of hash joins that overflowed to total hash joins completed.

• Hash small overflow - The percentage of hash join overflows in which the sort heap was short by ten percent or less per monitoring interval.

• Sort Heap Used - The percentage of the sort heap threshold (SHEAPTHRES parameter value) currently being used.

These values are derived from the Database_Sorting Table:

• Database Name

• Total Sorts

• Active Sorts

• Sort Time (ms)

• Sort Overflows


• Hash Joins

• Hash Loops

• Hash Join Overflows

• Hash Join Overflow (%)


• Hash Join Sm Overflows

• Hash Join Sm Overflow (%)

• Sort Heap Size (Kb)

• Sort Heap Allocated (Kb)


• Sort Heap Thresh (Kb)

To open the DB2_Database_Sort_Analysis table


2 Double-click the DB2_Database_Sort_Analysis table icon to display the view.



• Right-click or drill down on Total Sorts row to display sort and hash join statistics per monitoring interval for each application in the DB2 database on the DB2_Application_Sorting Table view.

DB2_Tables_Top_Accessed TableThis table provides information about the number of top consumers, as defined by the user, related to database table activity. The default is 10.

These values are derived from the Database_Tables Table:

• Database Schema Table

• Table Type

• Rows Accesses

• Rows Read

• Rows Written

• Page Reorgs

• Overflow Accesses

To open the DB2_Tables_Top_Accessed table



2 Double-click the DB2_Tables_Top_Accessed table icon to display the view.

DB2_Tablespace_Top_Bufferpool_Details Table This table view shows object identification information, bufferpool and index hit ratios, and information about the number and

type of data and index read/write operations for the selected tablespace. This table can include data for SMS and DMS tablespaces.

The values are derived from the following fields in the Database_Bufferpools Table and the Database_Tablespaces Table:

• Database

• Tablespace Name

• Tablespace State

• Tablespace Id

• Bufferpool Hit Ratio

• Bufferpool Data Logical Reads

• Bufferpool Data Physical Reads

• Bufferpool Data Writes

• Bufferpool Index Logical Reads


• Bufferpool Index Physical Reads

• Bufferpool Index Writes

• Bufferpool Read Time

• Bufferpool Write Time

• Async Pages Read Per Request

• Async Pool Data Page Reads

• Async Pool Data Page Writes

• Async Pool Index Page Reads

• Async Pool Index Page Writes

• Async Read Requests

• Async Read Time

• Async write time

• Direct Read Requests

• Direct Read Time

• Direct Reads

• Direct Write Requests

• Direct Write Time

• Direct Writes

To open the DB2_Tablespace_Top_Bufferpool_Details table



2 Double-click the DB2_Tablespace_Top_Bufferpool_Details table icon to display the view.

DB2_Tablespace_Top_Bufferpool_HitRates GraphThis graph view shows the hit ratios for the top n DMS and SMS tablespaces, where n is the ASP value you specify. The ratios are sorted in ascending order, with the lowest ratio shown closest to the y-axis and the highest ratio shown farthest from the y-axis.

Note SMS and DMS tablespace hit ratios can be displayed in this graph.

This value is derived from the Database_Bufferpools Table:

• Buffer pool hit ratio (%)

To open the DB2_Tablespace_Top_Bufferpool_HitRates graph



2 Double-click the DB2_Tablespace_Top_Bufferpool_HitRates graph icon to display the view.


• Drill down on the Buffer pool hit ratio bar to display object identification information, bufferpool and index hit ratios, and information about the number and type of data and index read/write operations for the selected tablespace with the DB2_Tablespace_Top_Bufferpool_Details Tableview.

DB2_Tablespace_Top_Space_Details TableThis table view shows tablespace identifier and type information, the amount of used space, the number of free pages, usable pages, and used pages, page size, prefetch size, extent size, and the number of containers for the top n DMS tablespaces, where n is the ASP value you specify.

These values are derived from the Database_Tablespaces Table:

• Database Name

• Tablespace Managed Type

• Tablespace Name

• Tablespace State

• Tablespace Id

• Tablespace Free (MB)

• Tablespace Size (MB)


• Tablespace % Utilization

• Tablespace Total Pages

• Tablespace Pages Useable

• Tablespace Pages Free

• Tablespace Pages Used

• Tablespace Prefetch Size

• Tablespace Page Size

• Tablespace Extent Size

• Number of Containers

• Number of Files Closed

To open the DB2_Tablespace_Top_Space_Details table


2 Double-click the DB2_Tablespace_Top_Space_Details table icon to display the view.


DB2_Tablespace_Top_Space_Utilization GraphThis graph view provides tablespace size, free space, and the percentage of used space for the top n DMS tablespaces, where n is the ASP value you specify.

The values are derived from the following fields in the Database_Tablespaces Table:

• Tablespace free (Mb)

• Tablespace size (Mb)

• Tablespace percent utilization

Note This graph does not contain any SMS tablespace data.

To open the DB2_Tablespace_Top_Space_Utilization graph

1 In the client list pane, click the appropriate DB2 agent icon.

2 From the Filter by list, select View to display in the right-hand pane a list of all available views.

3 In the list of views, double-click the DB2_Tablespace_Top_Space_Utilization icon to display the view.


• Drill down on the Tablespace free (Mb) bar to view tablespace identifier and type information, the amount of used space, the number of free pages, usable pages, and used pages, page size, prefetch size, extent size, and the number of containers for the top n DMS tablespaces, where n is the ASP value you specify, with the DB2_Tablespace_Top_Space_Details Table view.


DB2 Agent Rules

DB2_Agent_Lock_Waits RuleThis rule determines when the percentage of registered agents waiting on locks reaches preset thresholds.

Note #WORLD::AgentLockWaitsWarning# is a Foglight Registry entry with a default value of 10.

#WORLD::AgentLockWaitsCritical# with a default value of 20.

Use the Foglight Registry to change thresholds for rules by modifying registry entries.


• Right-click or drill down to the DB2_Database_Manager_Overview Graph view to view agent data for the active database, as well as sort heap and piped sort data.

Rule Condition Severity Level

Action

DB2.Instance_Agent.Percent_of_agents_waiting_ on_locks >= #WORLD::AgentLockWaitsWarning#

Warning Log Message

DB2.Instance_Agent.Percent_of_agents_waiting_ on_locks >= #WORLD::AgentLockWaitsCritical#

Critical Log Message, Email DB2 Administrator


DB2_Agent_Token_Waits RuleThis rule determines when the percentage of registered agents waiting on tokens reaches preset thresholds.

Note #WORLD::AgentTokenWaitsWarning# is a Foglight Registry entry with a default value of 10.

#WORLD::AgentTokenWaitsCritical# with a default value of 20.





Action

DB2.Instance_Agent.Percent_of_agents_waiting _on_tokens >=#WORLD::AgentTokenWaitsWarning#

Warning Log Message

DB2.Instance_Agent.Percent_of_agents_waiting_on_tokens >= #WORLD::AgentTokenWaitsCritical#

Critical Log Message,Email DB2 Administrator


DB2_Agent_Utilization RuleThis rule identifies when a set percentage of the maximum number of agents is reached.

Note #WORLD::AgentUtilizationWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::AgentUtilizationCritical# with a default value of 90.



• Right-click or drill down to the DB2_Database_Manager_Overview Graph view to view statistics about application agent usage in the DB2 database.


Action

DB2.Instance_Agent.Percent_of_agents_in_use >= #WORLD::AgentUtilizationWarning#

Warning Log Message

DB2.Instance_Agent.Percent_of_agents_in_use >= #WORLD::AgentUtilizationCritical#



DB2_Agents_Stolen RuleThis rule determines when the percentage of registered agents stolen by other applications reaches preset thresholds.

Note #WORLD::AgentsStolenWarning# is a Foglight Registry entry with a default value of 10.

#WORLD::AgentsStolenCritical# with a default value of 20.





Action

DB2.Instance_Agent.Percent_of_agents_stolen >= #WORLD::AgentsStolenWarning#

Warning Log Message

DB2.Instance_Agent.Percent_of_agents_stolen >= #WORLD::AgentsStolenCritical#



DB2_Appl_CPU_Time RuleThis rule determines when total application CPU time reaches preset thresholds.

Note #WORLD::ApplCPUTimeWarning# is a Foglight Registry entry with a default value of 600.

#WORLD::ApplCPUTimeCritical# with a default value of 900.





Action

DB2.Application_Connection.Total_CPU_time >= #WORLD::ApplCPUTimeWarning#

Warning Log Message

DB2.Application_Connection.Total_CPU_time >= #WORLD::ApplCPUTimeCritical#



DB2_Appl_Lock_Wait RuleThis rule determines when lock wait time reaches preset thresholds.

Note #WORLD::ApplLockWaitTimeWarning# is a Foglight Registry entry with a default value of 15.

#WORLD::ApplLockWaitTimeCritical# with a default value of 30.



• Right-click or drill down to the DB2_Application_Locking Table view.


Action

DB2.Application_Locking.Lock_wait_time >= #WORLD::ApplLockWaitTimeWarning#

Warning Log Message

DB2.Application_Locking.Lock_wait_time >= #WORLD::ApplLockWaitTimeCritical#



DB2_Appl_Sort_Time RuleThis rule determines when application sort time reaches preset thresholds.

Note #WORLD::ApplSortTimeWarning# is a Foglight Registry entry with a default value of 600000.

#WORLD::ApplSortTimeCritical# with a default value of 900000.



• Right-click or drill down to the DB2_Application_Sorting Table view to view sort and hash join statistics per monitoring interval for each application in the DB2 database.


Action

DB2.Application_Sorting.Total_sort_time >= #WORLD::ApplSortTimeWarning#

Warning Log Message

DB2.Application_Sorting.Total_sort_time >= #WORLD::ApplSortTimeCritical#



DB2_Buffer_Pool_Ratio RuleThis rule determines when the buffer pool hit ratio reaches preset thresholds.

Note #WORLD::BufferPoolRatioWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::BufferPoolRatioCritical# with a default value of 70.



• Right-click or drill down to the DB2_Bufferpool_Analysis Graphview to view information about buffer pool hit ratios in the DB2 database.


Action

DB2.Database_Bufferpools.Buffer_pool_hit_ratio <= #WORLD::BufferPoolRatioWarning#

Warning Log Message

DB2.Database_Bufferpools.Buffer_pool_hit_ratio <= #WORLD::BufferPoolRatioCritical#



DB2_Catalog_Cache_Heap RuleThis rule determines when catalog cache heap reaches preset thresholds.

Note #WORLD::CatalogCacheHeapWarning# is a Foglight Registry entry with a default value of 1.

#WORLD::CatalogCacheHeapCritical# with a default value of 3.



• Right-click or drill down to the DB2_Database_Memory_Catalog_Cache Graph view to view information about the catalog cache.


Action

DB2.Database_Memory.Catalog_cache_heap_full_overflows >= #WORLD::CatalogCacheHeapWarning#

Warning Log Message

DB2.Database_Memory.Catalog_cache_heap_full_overflows >= #WORLD::CatalogCacheHeapCritical#



DB2_Catalog_Cache_Oflow RuleThis rule determines when catalog cache overflow reaches preset thresholds.

Note #WORLD::CatalogCacheOflowWarning# is a Foglight Registry entry with a default value of 1.

#WORLD::CatalogCacheOflowCritical# with a default value of 3.



• Right-click or drill down to the DB2_Database_Memory_Catalog_Cache Graph view to view information about the catalog cache.


Action

DB2.Database_Memory.Catalog_cache_overflows >= #WORLD::CatalogCacheOflowWarning#

Warning Log Message

DB2.Database_Memory.Catalog_cache_overflows >= #WORLD::CatalogCacheOflowCritical#



DB2_Catalog_Cache_Ratio RuleThis rule determines when the catalog cache hit ratio reaches preset thresholds.

Note #WORLD::CatalogCacheRatioWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::CatalogCacheRatioCritical# with a default value of 70.





Action

DB2.Database_Memory.Catalog_cache_hit_ratio <= #WORLD::CatalogCacheRatioWarning#

Warning Log Message

DB2.Database_Memory.Catalog_cache_hit_ratio <= #WORLD::CatalogCacheRatioCritical#



DB2_Client_CPU_Time RuleThis rule determines when total CPU time reaches preset thresholds.

Note #WORLD::ClientCPUTimeWarning# is a Foglight Registry entry with a default value of 180.

#WORLD::ClientCPUTimeCritical# with a default value of 300.



• Right-click or drill down to the DB2_Client_Top_CPU_Usage Table view to view information about CPU time that this application has spent executing database manager code in the database, limited to the top consumers of total CPU time as defined in the ASPs.


Action

DB2.Client_Connection.Total_CPU_time >= #WORLD::ClientCPUTimeWarning#

Warning Log Message

DB2.Client_Connection.Total_CPU_time >= #WORLD::ClientCPUTimeCritical#



DB2_Client_Lock_Wait RuleThis rule determines when number of client lock waits reaches preset thresholds.

Note #WORLD::ClientLockWaitWarning# is a Foglight Registry entry with a default value of 5.

#WORLD::ClientLockWaitCritical# with a default value of 10.



Action

DB2.Client_Locking.Lock_wait_time >= #WORLD::ClientLockWaitWarning#

Warning Log Message

DB2.Client_Locking.Lock_wait_time >= #WORLD::ClientLockWaitCritical#



DB2_Client_Sort_Time RuleThis rule determines when client sort time usage reaches preset thresholds.

Note #WORLD::ClientSortTimeWarning# is a Foglight Registry entry with a default value of 180000.

#WORLD::ClientSortTimeCritical# with a default value of 300000.



• Right-click or drill down to the DB2_Client_Top_Sort_Usage Table view to view information about total sort activity generated by the application, limited to the top consumers of total sort time as defined in the ASPs.


Action

DB2.Client_Sorting.Total_sort_time >= #WORLD::ClientSortTimeWarning#

Warning Log Message

DB2.Client_Sorting.Total_sort_time >= #WORLD::ClientSortTimeCritical#



DB2_Connection_Util RuleThis rule determines when the current number of connections reaches preset capacity thresholds.

Note #WORLD::ConnectionUtilWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::ConnectionUtilCritical# with a default value of 90.



• Right-click or drill down to the DB2_Database_Connection_Detail Table view to view information about DB2 database connections.


Action

DB2.Database_Connection.Client_percent_of_ maximum >= #WORLD::ConnectionUtilWarning#

Warning Log Message

DB2.Database_Connection.Client_percent_of_ maximum >= #WORLD::ConnectionUtilCritical#



DB2_Db_HADR_CngstdTO RuleThis rule fires when a HADR Database has been congested longer than the set threshold value.

Note #WORLD::SQLM_HADR_CONN_CONGESTED# is a Foglight Registry entry with a default value of 1.

#WORLD::HADR_Connection_Timeout_threshold_warning# is a Foglight Registry entry with a default value of 5.

#WORLD::HADR_Connection_Timeout_threshold_critical# is a Foglight Registry entry with a default value of 30.



• Right-click or drill down to the DB2_HADR_Overview Table view to view data only when a database is configured for HADR and its hadr_role is either SQLM_HADR_ROLE_PRIMARY or SQLM_HADR_ROLE_STANDBY.


Action

DB2.Database_HADR.hadr_connect_status == #WORLD::SQLM_HADR_CONN_CONGESTED# && DB2.Database_HADR.hadr_elapsed_connect_time >#WORLD::HADR_Connection_Timeout_ threshold_warning#

Warning Log Message

DB2.Database_HADR.hadr_connect_status == #WORLD::SQLM_HADR_CONN_CONGESTED# && DB2.Database_HADR.hadr_elapsed_connect_time >#WORLD::HADR_Connection_Timeout_ threshold_critical#



DB2_Db_HADR_DisconTO RuleThis rule fires when HADR Database has been disconnected longer than the set threshold value.

Note #WORLD::SQLM_HADR_CONN_DISCONNECTED# is a Foglight Registry entry with a default value of 2.

#WORLD::HADR_Connection_Timeout_threshold_warning# is a Foglight Registry entry with a default value of 5.

#WORLD::HADR_Connection_Timeout_threshold_critical# is a Foglight Registry entry with a default value of 30.





Action

DB2.Database_HADR.hadr_connect_status == #WORLD::SQLM_HADR_CONN_ DISCONNECTED# &&DB2.Database_HADR.hadr_elapsed_connect_time > #WORLD::HADR_Connection_Timeout_threshold_warning#

Warning Log Message

DB2.Database_HADR.hadr_connect_status == #WORLD::SQLM_HADR_CONN_DISCONNECTED# &&DB2.Database_HADR.hadr_elapsed_connect_time > #WORLD::HADR_Connection_Timeout_threshold_critical#



DB2_Db_HADR_LogGapEx RuleThis rule fires when the running average of the gap between the primary and the standby exceeded the threshold.

Note #WORLD::HADR_log_gap_threshold_warning# is a Foglight Registry entry with a default value of 4096.

#WORLD::HADR_log_gap_threshold_critical# is a Foglight Registry entry with a default value of 16384.





Action

DB2.Database_HADR.hadr_log_gap > #WORLD::HADR_log_gap_threshold_warning#

Warning Log Message

DB2.Database_HADR.hadr_log_gap > #WORLD::HADR_log_gap_threshold_critical#



DB2_Db_HADR_MissedHB RuleThis rule fires when heartbeats missed is non-zero over a specified number of collection cycles.

Note By default, the specified number of collection cycles (sample periods) is 3.

Note #WORLD::HADR.hadr_heartbeats_missed# is a Foglight Registry entry with a default value of 60.


Right-click or drill down to the DB2_HADR_Overview Table view to view data only when a database is configured for HADR and its hadr_role is either SQLM_HADR_ROLE_PRIMARY or SQLM_HADR_ROLE_STANDBY.


Action

DB2.Database_HADR.hadr_heartbeats_missed > #WORLD::HADR_heartbeats_missed_threshold_ warning

Warning Log Message


DB2_Db_HADR_State RuleThis rule fires when primary and secondary databases are not HADR peers.

When HADR is in effect, it is important to know when the HADR state is something other than PEER. If the current state is DISCONNECTED, the corresponding severity level is considered Critical. When the state is something else (such as one of CATCHUP states), the severity is lowered to Warning.

Note #WORLD::SQLM_HADR_STATE_DISCONNECTED# is a Foglight Registry entry with a default value of 0.

#WORLD::SQLM_HADR_STATE_PEER# is a Foglight Registry entry with a default value of 4.



Right-click or drill down to the DB2_HADR_Overview Table view to view data only when a database is configured for HADR and its hadr_role is either SQLM_HADR_ROLE_PRIMARY or SQLM_HADR_ROLE_STANDBY.


Action

DB2.Database_HADR.hadr_state != #WORLD::SQLM_HADR_STATE_DISCONNECTED# && DB2.Database_HADR.hadr_state != #WORLD::SQLM_HADR_STATE_PEER#

Warning Log Message

DB2.Database_HADR.hadr_state == #WORLD::SQLM_HADR_STATE_DISCONNECTED#



DB2_Deadlocks_Detected RuleThis rule determines when the number of deadlocks reaches preset thresholds.

Note #WORLD::DeadlocksDetectedWarning# is a Foglight Registry entry with a default value of 5.

#WORLD::DeadlocksDetectedCritical# with a default value of 10.



• Right-click or drill down to the DB2_Database_Lock_Analysis Table view to view locks statistics about locks, waits, and holds for the database over consecutive monitoring intervals.


Action

DB2.Database_Locking.Deadlocks_detected >= #WORLD::DeadlocksDetectedWarning#

Warning Log Message

DB2.Database_Locking.Deadlocks_detected >= #WORLD::DeadlocksDetectedCritical#



DB2_Index_Ratio RuleThis rule determines when the index hit ratio reaches preset thresholds.

Note #WORLD::IndexRatioWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::IndexRatioCritical# with a default value of 70.



• Right-click or drill down to the DB2_Bufferpool_Analysis Graphview to view information about buffer pool hit ratios in the DB2 database.


Action

DB2.Database_IO.Index_hit_ratio <= #WORLD::IndexRatioWarning#

Warning Log Message

DB2.Database_IO.Index_hit_ratio <= #WORLD::IndexRatioCritical#



DB2_Lock_List_Util RuleThis rule determines when lock list usage reaches preset thresholds.

Note #WORLD::LockListUtilWarning# is a Foglight Registry entry with a default value of 50.

#WORLD::LockListUtilCritical# with a default value of 60.





Action

DB2.Database_Locking.Lock_list_utilization_ percent >= #WORLD::LockListUtilWarning#

Warning Log Message

DB2.Database_Locking.Lock_list_utilization_ percent >= #WORLD::LockListUtilCritical#



DB2_Lock_Timeouts RuleThis rule determines when the number of lock timeouts reaches preset thresholds.

Note #WORLD::LockTimeoutsWarning# is a Foglight Registry entry with a default value of 3.

#WORLD::LockTimeoutsCritical# with a default value of 5.





Action

DB2.Database_Locking.Lock_timeouts >= #WORLD::LockTimeoutsWarning#

Warning Log Message

DB2.Database_Locking.Lock_timeouts >= #WORLD::LockTimeoutsCritical#



DB2_Log_Secondary_Util RuleThis rule determines when secondary log usage reaches preset thresholds.

Note #WORLD::LogSecondaryUtilWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::LogSecondaryUtilCritical# with a default value of 90.



• Right-click or drill down to the DB2_Database_Log_Space Graph view to view information about total and secondary log space usage.


Action

DB2.Database_Logging.Secondary_log_percent_allocated >= #WORLD::LogSecondaryUtilWarning#

Warning Log Message

DB2.Database_Logging.Secondary_log_percent_allocated >= #WORLD::LogSecondaryUtilCritical#



DB2_Log_Space_Util RuleThis rule determines when log space usage reaches preset thresholds.

Note #WORLD::LogSpaceUtilWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::LogSpaceUtilCritical# with a default value of 90.



• Right-click or drill down to the DB2_Database_Log_Space Graph view to view information about total and secondary log space usage.


Action

DB2.Database_Logging.Total_log_percent_utilized >= #WORLD::LogSpaceUtilWarning#

Warning Log Message

DB2.Database_Logging.Total_log_percent_utilized >= #WORLD::LogSpaceUtilCritical#



DB2_Package_Cache_Oflow RuleThis rule determines when package cache overflow reaches preset thresholds.

Note #WORLD::PackageCacheOflowWarning# is a Foglight Registry entry with a default value of 1.

#WORLD::PackageCacheOflowCritical# with a default value of 3.



• Right-click or drill down to the DB2_Database_Memory_Package_Cache Graph view to view package cache usage information.


Action

DB2.Database_Memory.Package_cache_overflows >= #WORLD::PackageCacheOflowWarning#

Warning Log Message

DB2.Database_Memory.Package_cache_overflows >= #WORLD::PackageCacheOflowCritical#



DB2_Package_Cache_Ratio RuleThis rule determines when the package cache hit ratio reaches preset thresholds.

Note #WORLD::PackageCacheRatioWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::PackageCacheRatioCritical# with a default value of 70.



• Right-click or drill down to the DB2_Database_Memory_Analysis Graph view to view information about DB2 database memory.


Action

DB2.Database_Memory.Package_cache_hit_ratio <= #WORLD::PackageCacheRatioWarning#

Warning Log Message

DB2.Database_Memory.Package_cache_hit_ratio <= #WORLD::PackageCacheRatioCritical#



DB2_Sort_Heap_Util RuleThis rule determines when sort heap usage reaches preset thresholds.

Note #WORLD::SortHeapUtilWarning# is a Foglight Registry entry with a default value of 90.

#WORLD::SortHeapUtilCritical# with a default value of 100.





Action

DB2.Instance_Agent.Sort_heap_percent_utilization >= #WORLD::SortHeapUtilWarning#

Warning Log Message

DB2.Instance_Agent.Sort_heap_percent_utilization >= #WORLD::SortHeapUtilCritical#



DB2_Sort_Oflow RuleThis rule determines when sort overflow usage reaches preset thresholds.

Note #WORLD::SortOflowWarning# is a Foglight Registry entry with a default value of 10.

#WORLD::SortOflowCritical# with a default value of 20.



• Right-click or drill down to the DB2_Database_Sort_Analysis Table view to view sort and hash join statistics for each DB2 database. This table relates the number of sort and hash join overflows to the total number of sorts and hash joins, respectively, generated by the application.


Action

DB2.Database_Sorting.Sort_overflow_percent >= #WORLD::SortOflowWarning#

Warning Log Message

DB2.Database_Sorting.Sort_overflow_percent >= #WORLD::SortOflowCritical#



DB2_Tablespace_Util RuleThis rule fires when tablespace space used is higher than a warning or a critical threshold.

Note Applies only for tablespaces that are not auto-resizable

Note #WORLD::TablespaceUtilWarning# is a Foglight Registry entry with a default value of 80.

#WORLD::TablespaceUtilCritical# has a default value of 90.



• Right-click or drill down to the DB2_Tablespace_Top_Space_Utilization Graph view to view tablespace size, free space, and the percentage of used space for the top n DMS tablespaces, where n is the ASP value specifed.


Action

DB2.Database_Tablespaces.Tablespace_percent_utilization >= #WORLD::TablespaceUtilWarning#&&DB2.Database_Tablespaces.Tablespace_managed_type == "DMS" &&

Warning Log Message

DB2.Database_Tablespaces.Tablespace_percent_utilization >= #WORLD::TablespaceUtilCritical#&&DB2.Database_Tablespaces.Tablespace_managed_type == "DMS" &&


2

DB2 Monitor Agent

Contents

DB2Monitor AgentUsing DB2 Monitor Agent Startup ParametersDB2Monitor Agent TablesDB2Monitor Agent InvestigationsDB2Monitor Agent ViewsDB2Monitor Agent Rules


DB2Monitor AgentThe DB2Monitor Agent provides a consolidated view of all DB2 instances within a DB2 server.

About the DB2Monitor AgentThis Agent provides DB2 users with a centralized view of the server and a quick overview of the status of all DB2 Instances. DB2Monitor can identify all available DB2 Instances on the server and install a DB2 Cartridge for each DB2 instance found. In addition, this agent collects process level statistics for all running/active DB2 Instances.

ASPsThe DB2Monitor agent is shipped with agent startup parameters that dictate how the agent will perform.

Using DB2 Monitor Agent Startup Parameters

InvestigationsThe following information is provided to help you start troubleshooting issues that may occur when monitoring your system.

Investigating the DB2 Server

ViewsViews are graphs or tabular presentations of data collected by the DB2Monitor agent.

DB2Instance_Details Graph

DB2Process_Details Graph

DB2Server_Overview Graph

RulesFoglight uses rules to define monitoring parameters and parameter thresholds for notification events.

DB2_Availability Rule

DB2_Diag_Log_File_Size Rule

Chapter 2 221DB2Monitor Agent

DB2_Diag_Log_Message Rule

TablesThe DB2Monitor agent stores data in the following Foglight Database tables.

DB2DiagLogFiles Table

DB2DiagLogMessage Table

DB2Instances Table

DB2ProcessDetails Table

DB2ProcessTotals Table

DB2ServerTotals Table


Using DB2 Monitor Agent Startup ParametersThe DB2Monitor agent is shipped with predefined agent startup parameters (ASPs) that dictate how the agent will perform. You can change these parameters to suit your system requirements. The parameters listed in the topics below are specific to the DB2Monitor Agent. For more information regarding common agent startup parameters, such as purging, see the About Agent Startup Parameters topic in the Foglight Management Server online help.

TopicsSetting DB2Monitor Connection DetailsSetting the DB2Monitor Data Management Parameters

Setting DB2Monitor Connection DetailsUse the Connection Details tab in the DB2Monitor agent ASP Editor to designate the type of connection parameters to use.

You can also use the Connection Details tab to exclude DB2 instances from monitoring. Excluding an instance means the specified DB2 agent is not added to the console, and monitoring data is not populated for these instances.

To set connection parameters

1 Right-click the DB2Monitor agent icon and choose Edit, ASPs to display the Edit ASP window.


2 Select the Connections Details tab.

3 By default the Default Username and Default Password box are blank.

These represent a user name and password that will be applied to any instance of the DB2_UDB agent created by DB2_Monitor when a user name and password is not specified for that DB2_UDB agent instance in the DB2Monitor Connection Parameters secondary ASP.

If there are a large number of DB2 servers, enter the username and password and leave blank in the secondary ASP. Username and password in the secondary ASP take precedence over the default username and default password fields.

Note A valid user must have SYSMON, SYSCTRL, SYSMAINT, or SYSADM authority.

4 In the DB2 Connection Parameters box, select the secondary ASP list from the drop-down menu. Click Edit to change the connection parameters.Note The default list name is DB2_Connection_Parameters.

Note You may need to create a secondary ASP list for each host on which you monitor a DB2 database.

5 Select the Search for new DB2 Instances check box to have the DB2Monitor agent search at intervals for new DB2 instances that have been added by the DB2 Administrator. Once the monitor discovers instances that have been added, it adds an agent for each instance.Note The interval is the sample frequency assigned to the DB2Instances table.

6 Select the Remove Stale DB2 Instanc0e from Console check box to have the DB2Monitor agent search at intervals for DB2 instances that have been removed


by the DB2 Administrator. Once the monitor discovers instances that have been removed, it removes an agent for each instance.

7 After defining the connection parameters, you can:

a Click OK to save the entry and close the Edit ASP window.

b Select the Data Management tab to set the sample frequency and intervals between data purges.

To exclude an instance

1 On the Connection Details tab click the Edit button to display the DB2 Instance Connection Parameters window.

2 Select the instance you want to exclude and click Edit. The Edit: DB2ConnectionsTemplate window displays.

3 Clear the Monitor check box and click OK. The selected instance is excluded.

4 Click OK in the DB2 Instance Connection Parameters window to return to the main Edit ASP window.

5 Select the Data Management tab to set the sample frequency and intervals between data purges.


Setting the DB2Monitor Connection ParametersUse the DB2Monitor DB2 Instance Connection Parameters window to change the connection and monitoring parameters for an individual DB2_UDB agent instance.

To set the connection parameters


2 Select the Connection Details tab.

3 Click Edit next to the DB2 Connection Parameters box to open the DB2Instance Connection Parameters window.

4 Click New to display the Add:data window.

5 Enter the following data in the appropriate boxes:

• Select the Monitor check box if you want to monitor the DB2 instance. Clear the check box if you do not want to monitor the DB2 instance.

• Enter the name of the DB2 instance that you want to monitor in the DB2Instance box.

Note Enter an instance name not a partition or node name.


• Enter the user name under which you want to connect to the DB2 instance in the DB2User box.

• Enter the password that corresponds to the above mentioned user name in the DB2Password box.

• Enter the fully qualified path to the diagnostic log file for the specified DB2 instance in the DB2 Diag Log Path box.

Note The Monitor check box must be selected for the instance to be included.

6 Click OK on the DB2 Instance Connection Parameters window to return to the main Edit ASP window.

Setting the DB2Monitor Data Management ParametersUse the Data Management tab in the DB2Monitor agent ASP Editor to set the sample frequency and intervals between data purges.

Note You can purge tables at the agent or table level. Table level purging is the preferred method.

To set the data management parameters




3 In the Sample Frequency List box, select a sampling list from the drop-down list. Click Edit to change the sampling frequency and/or data purging parameters of the table.Note The default sampling list name is DB2_SampleFreq. Create a new ASP list by typing

the name of the list in the Sample Frequency List box.

4 In the DB2 Log Filter List box, select a DB2 log filter list from the drop-down list. Click Edit to change the filter settings.Note The default sampling list name is DB2_Log_Filter_List. Create a new ASP list by

typing the name of the list in the DB2 Log Filter List box.

5 In the DB2 Installation Directories box, select a DB2 installation directory list from the drop-down list. Click Edit to change the directory settings.Note The default sampling list name is DB2InstallationDirectoryList. Create a new ASP list

by typing the name of the list in the DB2 Installation Directories box.

6 Enter the time interval, in seconds, for the collection rate in the Sample Frequency box. Note The default is 300 seconds.

Note Setting intervals at less than 300 seconds is not recommended.

7 Enter the number of days that you want to elapse between each data purge in the Purge Days text box. Note The default is 90 days.

Note These purges apply only to the DB2Monitor Agent. Application and DB2 data, stored in the DB2 Agent tables, are not affected.

8 Click OK to save the changes to the table.

9 Click OK on the Sample Frequencies window. You are returned to the main Edit ASP screen.

10 Click OK to save the entry and close the Edit ASP window, or select the Connections Details tab to configure the DB2Monitor connection parameters.

Editing the DB2Monitor Sampling Frequency or Data Purging ParametersUse the DB2Monitor DB2 Instance Connection Parameters window in the Data Management ASP tab to change the connection parameters of an instance.


To edit the parameters



3 Click Edit next to the Sample Frequency List box to open the Sample Frequencies window. .

Note The default number of purge days is shown for each table.

4 Select the table for which you want to change the values and click Edit.Note Only existing tables should be modified.

The Edit SampleFreq window displays. The selected table name displays in the Table Name box.

5 In the Sample Frequency box, type the frequency that you want to elapse between each sample.

Warning! New or Delete is to be used only when directed by Quest Technical Support.


Use the Select button to select a different table name.Note The default is 5 minutes or 300 seconds.

6 In the Purge Days box, type the number of days that you want to elapse between each data purge.

Use the Select button to select a different sample frequency.Note The default is 90 days.

Note These purges apply only to the DB2Monitor agent. DB2 data, stored in the DB2Monitor agent tables, are not affected.

7 Click OK to save the entry and close the Edit SampleFreq window.

8 Click OK to save the entry and close the Sample Frequencies window.

9 Click OK to save the entry and close the Edit ASP window, or select the Connections Details tab to define connection parameters.

Setting Log Filter and Instance Discovery ParametersDB2 Monitor can be configured to filter the db2diag.log file for error messages by hex code or 8-character string. It can also be configured to detect instances that have been added or deleted by DB2 Administrators between DB2 Monitor agent cycles.

Use the DB2Monitor DB2 Log Filter List in the Data Management ASP tab to select a log filtering list and to indicate if DB2Monitor should search periodically for new and stale instances.

To set the diagnostic log filter and instance discovery parameters




3 Click Edit next to the DB2 Log Filter List box to open the DB2 Error Log Filter window.

4 Highlight a character string from the DB2 Error Log Filter list, then click New to add a simple hex code or an 8 character string based on any ADM, DIA, or SQL log message. The Add: DB2ErrorTemplate window is displayed.

Alternately, you can click Edit to display the Edit: DB2ErrorTemplate window. Note The boxes on both windows are the same.

5 If desired, make any needed changes to the HexString, HexSeverity, and UserMessage fields according to the requirements at your site.


6 Click OK to save the entry and close the Add: DB2ErrorTemplate window or Edit: DB2ErrorTemplate window.

7 Click OK to save the entry and close the DB2 Error Log Filter window.


Editing the DB2Monitor Installation Path Directory ParametersUse the DB2Monitor DB2 Install Directory Path window in the Data Management ASP tab to change the installation path directory search parameters.

To edit the search parameters



3 Click Edit next to the DB2 Installation Directories box to open the DB2 Install Directory Path window.


4 Select the directory path for which you want to change the search parameters and click Edit.Note Paths that do not exist on the server on which DB2Monitor Agent is running are

ignored.

The Edit: data window displays. The selected path displays in the DB2 Installation Directory Path box.

5 Use the Select button to select a different path.

6 Select the Search For Installation Directories check box to enable the search.

7 Click OK to save the entry and close the Edit: data window.

8 Click OK to save the entry and close the DB2 Install Directory Path window.



DB2Monitor Agent TablesThe DB2 agent stores data in a series of tables in the DB2 database. Click the hyperlinks to view field definitions.TablesDB2DiagLogFiles Table

DB2DiagLogMessage Table

DB2Instances Table

DB2ProcessDetails Table

DB2ProcessTotals Table

DB2ServerTotals Table

DB2DiagLogFiles TableThis table displays the current size of the db2diag.log file for all available DB2 instances. The fields included in this table are as follows:

DB2DiagLogMessage TableThis table stores DB2 internal error messages captured from the DB2diag.log. The DB2Monitor agent includes predefined DB2 internal codes to trap. You can define additional hex codes in the db2diag.log file. The fields included in this table are as follows:

Field Description

DB2LogFile The location of the DB2 log file (db2diag.log).

DB2LogFileSize The current size, in MB, of the DB2 log file.

Instance The name of the DB2 instance associated with each log file.

Field Description

DB2ErrorHexCode The hex code for each internal error.


DB2Instances TableThis table contains availability information for all DB2 Instances. The fields included in this table are as follows:

DB2ProcessDetails TableThis table provides process detail information for every available instance on the DB2 server. The fields included in this table are as follows:

DB2ErrorMessageText The actual error message.

DB2LogFile The name of the log file where the error message is stored.

DB2SQLState The SQL State Code of the error.

DB2Severity The severity (fatal, critical, or warning) of each error.

Instance The name of the DB2 instance associated with each error.

Field Description

DB2Process_ Availability

Indicates if a DB2 instance is available (0=Not Available, 100=Available).

DB2Version The DB2 version associated with this instance.

Instance The name of each DB2 instance.

Field Description


PercentCPU The percentage of CPU resources used by each DB2 process.

Field Description


DB2ProcessTotals TableThis table provides the total process statistics for each DB2 instance. The fields included in this table are as follows:

PercentMemory The percentage of memory used by each DB2 process.

Process The name of each monitored DB2 process.

ProcessID An identification code for each monitored DB2 process.

ResidentSetSize The size, in KB, of each DB2 process.

Uptime The amount of time, in hours, required for each DB2 process.

VirtualSetSize The total size, in KB, of each DB2 process (memory and swap).

Field Description


PercentCPU The percentage of CPU resources used by each DB2 instance.

ResidentSetSize The size, in KB, of each DB2 instance.

VirtualSetSize The total size, in KB, of each DB2 instance (memory and swap).

Field Description


DB2ServerTotals TableThis table provides process statistics for the entire DB2 Server, which is the sum of all process statistics from all DB2 Instances. The fields included in this table are as follows:

Field Description

DB2Server The name of the DB2 server.

PercentCPU The percentage of CPU resources used by all DB2 instances.

ResidentSetSize The size, in KB, of all DB2 instances.

TotalDB2Instances The number of instances on the DB2 server.

VirtualSetSize The total size, in KB, of all DB2 instances (memory and swap).


DB2Monitor Agent InvestigationsThe following information is provided to help you start troubleshooting issues that may occur when monitoring your system.

Investigating the DB2 ServerThe DB2Monitor agent includes a series of graphs that provide various levels of detail about each instance, and its associated processes, on the DB2 server.

Start with the Server Overview graph

The DB2Server_Overview Graph displays CPU utilization statistics, expressed as percentages, for all DB2 instances on the server.

For more detailed information, do the following:

• Drill down on any bar to view data about each instance on the server in the DB2Instance_Details Graph.

• Drill down on any bar to view data about the processes associated with each instance in the DB2Process_Details Graph.


DB2Monitor Agent ViewsViews are graphs or tabular presentations of data collected by the DB2Monitor agent.

DB2Server_Overview GraphThis graph view provides CPU usage information about the DB2 server. The values are derived from the following fields in the DB2ServerTotals Table:

• CPU (%)

To open the DB2Server_Overview graph

1 Highlight the DB2Monitor agent icon for the server you want. A list of available graphs is displayed in the right-hand pane.

2 Double-click the DB2Server_Overview graph icon.


Double-clicking anywhere in the DB2Server_Overview graph displays a list of CPU usage percentages over a specified time range.

• Drill down the DB2Instance_Details Graph view to display CPU usage information for each instance on the DB2 server.

• Drill down to the DB2Process_Details Graph view to display uptime, memory, and CPU usage information for all processes on all instances on the selected server.


DB2Instance_Details GraphThis graph view displays CPU usage information for each instance on the DB2 server.

The values are derived from the following fields in the DB2ProcessTotals Table:

• CPU (%)

To open the DB2Instance_Details graph


2 Double-click the DB2Instance_Details graph icon.


• Double-clicking anywhere in the DB2Instance_Details graph view displays a list of CPU usage percentages over a specified time range for all the instances on the selected server.

• Drill down to the DB2Process_Details Graph view to display uptime, memory, and CPU usage information for all processes on all instances on the selected server.

• Drill on the DB2Server_Overview Graph view to display CPU usage information about the DB2 server.


DB2Process_Details GraphThis graph view provides uptime, memory, and CPU usage information for all processes on all instances on the selected server.

The values are derived from the following fields in the DB2ProcessDetails Table:

• Uptime (hrs.)

• Memory (%)

• CPU (%)

To open the DB2Process_Details graph


2 Double-click DB2Process_Details graph icon.

3 Use the vertical scroll bar (not shown in the picture above) to move through the various processes for all instances on the selected server. Right-clicking on the process name displays the entire process ID. Right-click again to toggle it off.

To continue your investigation

• Double-clicking anywhere in the DB2Process_Details graph view displays a list of Uptime (in hours), CPU and memory usage (as percentages) over a specified time range for all the instances on the selected server.


• Drill down to the DB2Instance_Details Graph view to display CPU usage information for each instance on the DB2 server.

• Drill down to the DB2Server_Overview Graph view to display CPU usage information about the DB2 server.


DB2Monitor Agent RulesFoglight uses rules to define monitoring parameters and parameter thresholds for notification events.

DB2_Availability RuleThis rule determines when a DB2 instance is not available.

Note #WORLD::AvailabilityCritical# is a Foglight Registry entry with a default value of 0.


DB2_Diag_Log_Message RuleThis rule monitors the log file and notifies you when it is approaching storage capacity.


Action

DB2Monitor.DB2Instances.DB2Process_ Availability == #WORLD::AvailabilityCritical#Default value = 0

Critical Log Message


Action

DB2Monitor.DB2DiagLogMessage.DB2Severity == "FATAL"

Fatal Log Message

DB2Monitor.DB2DiagLogMessage.DB2Severity == "WARNING"

Warning Log Message

DB2Monitor.DB2DiagLogMessage.DB2Severity == "CRITICAL"



DB2_Diag_Log_File_Size Rule This rule determines when the size of the log file is approaching message storage capacity.

Note #WORLD::DiagLogFileSizeWarning# is a Foglight Registry entry with a default value of 200.

#WORLD::DiagLogFileSizeCritical# is a Foglight Registry entry with a default value of 300.



Action

DB2Monitor.DB2DiagLogFiles.DB2LogFileSize >= #WORLD::DiagLogFileSizeWarning#Default value = 200

Warning Log Message

DB2Monitor.DB2DiagLogFiles.DB2LogFileSize >= #WORLD::DiagLogFileSizeCritical#Default value = 300



Glossary

IIntervalsThe interval is the sample frequency specified on the Data Management tab and assigned to the DB2Instances table.

SSample FrequencyThe collection rate, or sample frequency, is the number of seconds between the end of a collection period and the start of the next. The sample frequency is controlled at the agent level for all the tables.

Sample List NameA sampling list is the name of a secondary ASP.


Date post:	26-Jun-2018
Category:	Documents
Upload:	hoangkiet
View:	213 times
Download:	0 times

usdownloads.quest.com.edgesuite.netusdownloads.quest.com.edgesuite.net/Repository/support... ·...

Documents