Cockpit 702 730 Final

Database Administration Using the DBA Cockpit: IBM DB2 forLinux, UNIX, and Windows

For SAP Systems based on Enhancement Package 2 for SAP NetWeaver 7.0 and Higher

Target Audience

ConsultantsAdministratorsOthers

PublicDocument version 1.0 – 11/26/2010

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5,POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, SystemStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks orregistered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. andother countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, ClearEnterprise, SAP BusinessObjects Explorer and other SAP productsand services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and othercountries.

Business Objects and the Business Objects logo, BusinessObjects,Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks ofSAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks oftheir respective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may not bemodified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/instguidesnw

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

Typographic Conventions

Type Style Description

Example Text Words or characters quoted fromthe screen. These include fieldnames, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table names,and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directory namesand their paths, messages,names of variables andparameters, source text, andnames of installation, upgradeand database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For moreinformation, see Help on Help GeneralInformation Classes and Information Classesfor Business Information Warehouse on thefirst page of any version of SAP Library.

Installation Guide: mySAP <Solution>

4 November 2010

Contents

Database Administration Using the DBA Cockpit: IBM DB2 forLinux, UNIX, and Windows ................................................................ 9

1 The DBA Cockpit ............................................................................... 101.1 Web Browser-Based User Interface (Web Dynpro) ........................... 111.2 Maintenance Actions in the DBA Cockpit .......................................... 151.3 SAP GUI-Based User Interface (Deprecated) ..................................... 16

2 Special Tools in the Favorites List .................................................. 192.1 The EXPLAIN Function ........................................................................ 19

2.1.1 The EXPLAIN Function (Web Browser-Based Version) ........................................... 192.1.2 The EXPLAIN Function (SAP GUI-Based Version) ............................................... 22

2.1.2.1 EXPLAIN Options ............................................................................................ 232.2 SQL Command Line ............................................................................. 262.3 The Index Advisor ................................................................................ 27

2.3.1 Retrieving Index Recommendations for the Dynamic SQL Cache ........................... 282.3.2 Retrieving Index Recommendations for a Single SQL Statement ............................ 302.3.3 Defining Virtual User-Defined Indexes .................................................................... 322.3.4 Validating Indexes Using the EXPLAIN Function .................................................... 342.3.5 Creating Indexes in the ABAP Dictionary ................................................................ 35

3 Managing the System Landscape ................................................... 363.1 Configuration of Systems for Remote Monitoring ............................ 36

3.1.1 Configuring Systems for Remote Monitoring Manually ............................................ 373.1.2 Enabling the Database for the Data Collection Framework ...................................... 40

3.1.2.1 Setting Up the Data Collection Framework (DCF) Manually ............................... 423.1.2.2 Maintaining Templates for the DCF ................................................................... 42

3.2 Configuring Database Connections ................................................... 463.3 Configuring Systems for Remote Monitoring Using the SystemLandscape Directory (SLD) ....................................................................... 493.4 Central Calendar ................................................................................... 51

3.4.1 Using the Central Calendar .................................................................................... 524 Performance ...................................................................................... 55

4.1 Performance: Performance Warehouse ............................................. 554.1.1 Performance Warehouse: Reporting ....................................................................... 564.1.2 Performance Warehouse: Configuration ................................................................. 57

4.2 Performance: Time Spent Analysis .................................................... 604.3 Performance: Workload Statistics ...................................................... 664.4 Performance: System Resources ....................................................... 694.5 Performance: Snapshots ..................................................................... 70

4.5.1 Snapshots: Database ............................................................................................. 714.5.1.1 Displaying Detail Database Snapshot Data ....................................................... 73

4.5.1.1.1 Database Details: Buffer Pool ...................................................................... 744.5.1.1.2 Database Details: Cache ............................................................................. 764.5.1.1.3 Database Details: Asynchronous I/O ............................................................ 78

November 2010 5

4.5.1.1.4 Database Details: Direct I/O......................................................................... 794.5.1.1.5 Database Details: Real-Time Statistics ........................................................ 794.5.1.1.6 Database Details: Locks and Deadlocks ...................................................... 804.5.1.1.7 Database Details: Logging ........................................................................... 814.5.1.1.8 Database Details: Calls ............................................................................... 834.5.1.1.9 Database Details: Sorts ............................................................................... 854.5.1.1.10 Database Details: XML Storage ................................................................. 86

4.5.2 Snapshots: Schemas.............................................................................................. 874.5.3 Snapshots: Buffer Pools ......................................................................................... 88

4.5.3.1 Buffer Pools Details: Buffer Pool ....................................................................... 894.5.3.2 Buffer Pool Details: Asynchronous I/O ............................................................... 914.5.3.3 Buffer Pool Details: Direct I/O ............................................................................ 924.5.3.4 Buffer Pool Details: XML Storage ...................................................................... 93

4.5.4 Snapshots: Tablespaces ........................................................................................ 944.5.4.1 Tablespace Details: Buffer Pool ........................................................................ 954.5.4.2 Tablespace Details: Asynchronous I/O .............................................................. 974.5.4.3 Tablespace Details: Direct I/O ........................................................................... 984.5.4.4 Tablespace Details: XML Storage ..................................................................... 98

4.5.5 Snapshots: Tables .................................................................................................. 994.5.6 Snapshots: Applications (Only DB2 V9.7 or Higher) .............................................. 1024.5.7 Snapshots: Applications (Only DB2 V9.5 or Lower)............................................... 108

4.5.7.1 Application Details: Application ....................................................................... 1114.5.7.2 Application Details: Agents .............................................................................. 1144.5.7.3 Application Details: Assigned Agents .............................................................. 1154.5.7.4 Application Details: Agents Memory ................................................................ 1174.5.7.5 Application Details: Buffer Pool ....................................................................... 1184.5.7.6 Application Details: Direct I/O .......................................................................... 1194.5.7.7 Application Details: XML Storage .................................................................... 1204.5.7.8 Application Details: Locks and Deadlocks ....................................................... 1214.5.7.9 Application Details: Calls ................................................................................. 1224.5.7.10 Application Details: Sorts .............................................................................. 1234.5.7.11 Application Details: Cache............................................................................. 1244.5.7.12 Application Details: Unit of Work ................................................................... 1254.5.7.13 Application Details: Statement ....................................................................... 1264.5.7.14 Application Details: Statement Text ............................................................... 1274.5.7.15 Application Details: SQL Workspace ............................................................. 129

4.5.8 Snapshots: SQL Cache (Only DB2 V9.7 or Higher)............................................... 1294.5.9 Snapshots: SQL Cache (Only DB2 V9.5 or Lower) ............................................... 131

4.6 Performance: Critical Activities ........................................................ 1364.6.1 Critical Activities: Threshold Violations .................................................................. 1374.6.2 Critical Activities: Threshold Configuration ............................................................ 138

4.7 Performance: Utilities ........................................................................ 1394.7.1 Utilities: Database Utilities .................................................................................... 1404.7.2 Utilities: Inplace Table Reorganization .................................................................. 143

4.8 History: Database ............................................................................... 1464.9 History: Tables ................................................................................... 148

5 Space ................................................................................................ 1515.1 Space: Overview................................................................................. 1515.2 Space: Automatic Storage ................................................................. 153


6 November 2010

5.3 Space: Database................................................................................. 1545.4 Space: Tablespaces ........................................................................... 156

5.4.1 Maintaining Tablespaces ...................................................................................... 1615.5 Space: Containers .............................................................................. 1665.6 Space: File Systems ........................................................................... 1675.7 Space: Tables and Indexes................................................................ 168

5.7.1 Tables and Indexes: Top Space Consumers ......................................................... 1695.7.2 Tables and Indexes: REORG Candidates ............................................................. 1715.7.3 Tables and Indexes: Compression Status ............................................................. 1715.7.4 Tables and Indexes: Virtual Tables ....................................................................... 176

5.8 Analyzing and Maintaining a Single Table ....................................... 1775.8.1 Single Table Analysis: System Catalog ................................................................. 1825.8.2 Single Table Analysis: Table Structure.................................................................. 1845.8.3 Single Table Analysis: Indexes ............................................................................. 185

5.8.3.1 Indexes: System Catalog ................................................................................ 1875.8.3.2 Indexes: Index Structure ................................................................................. 1895.8.3.3 Indexes: Index Status...................................................................................... 1905.8.3.4 Indexes: Compression Status .......................................................................... 1925.8.3.5 Indexes: REORGCHK ..................................................................................... 194

5.8.4 Single Table Analysis: Table Status ...................................................................... 1955.8.5 Single Table Analysis: Compression Status .......................................................... 2005.8.6 Single Table Analysis: REORGCHK ..................................................................... 202

6 Backup and Recovery ..................................................................... 2036.1 Backup and Recovery: Overview ...................................................... 2036.2 Backup and Recovery: Logging Parameters ................................... 203

7 Configuration ................................................................................... 2047.1 Configuration: Overview .................................................................... 2047.2 Configuration: Database Manager .................................................... 2087.3 Configuration: Database .................................................................... 210

7.3.1 Maintaining the Database Configuration ............................................................... 2117.3.2 Comparing Database Configuration Parameters for Several Database Partitions .. 212

7.4 Configuration: Registry Variables .................................................... 2127.5 Configuration: Parameter Check ...................................................... 2137.6 Configuration: Configuration History ............................................... 2177.7 Configuration: Buffer Pools .............................................................. 220

7.7.1 Maintaining Buffer Pools ....................................................................................... 2217.8 Configuration: Workload Management ............................................ 223

7.8.1 Workload Management: Workloads and Service Classes...................................... 2247.8.2 Workload Management: SAP WLM Setup Status .................................................. 227

7.9 Configuration: Database Partition Groups....................................... 2287.9.1 Maintaining Database Partition Groups ................................................................. 230

7.10 Configuration: Special Tables Regarding RUNSTATS .................. 2327.11 Configuring Automatic Maintenance Functions ............................ 234

7.11.1 Automatic Maintenance Settings: General Settings ............................................. 2377.11.2 Automatic Maintenance Settings: Automatic Backup ........................................... 2387.11.3 Automatic Maintenance Settings: Automatic RUNSTATS .................................... 2407.11.4 Automatic Maintenance Settings: Automatic REORG.......................................... 242

7.12 Configuration: Data Classes ........................................................... 245

November 2010 7

7.12.1 Maintaining Data Classes ................................................................................... 2467.13 Configuration: Data Collection Framework.................................... 248

7.13.1 Data Collection Framework: Collector Configuration ........................................... 2487.13.2 Setup of Workloads and Service Classes in SAP Environments .......................... 252

7.14 Configuring Monitoring Settings .................................................... 2538 Jobs .................................................................................................. 255

8.1 The DBA Planning Calendar .............................................................. 2558.1.1 Setting Up and Working with the DBA Planning Calendar ..................................... 257

8.1.1.1 Creating an Action Pattern in the DBA Planning Calendar ............................... 2578.1.1.2 Scheduling an Action ...................................................................................... 2608.1.1.3 Changing an Action ......................................................................................... 2618.1.1.4 Deleting an Action ........................................................................................... 2628.1.1.5 Executing an Action ........................................................................................ 2628.1.1.6 Displaying Scheduled Actions ......................................................................... 2638.1.1.7 Troubleshooting .............................................................................................. 263

8.1.2 Scheduling Typical DBA Actions ........................................................................... 2648.1.2.1 Scheduling Database Backups ........................................................................ 265

8.1.2.1.1 Backup Considerations .............................................................................. 2678.1.2.2 Archiving Log Files To Tape ............................................................................ 2698.1.2.3 Updating Statistics .......................................................................................... 2698.1.2.4 Reorganizing Tables ....................................................................................... 2728.1.2.5 Scheduling a REORGCHK for All Tables ......................................................... 2748.1.2.6 Scheduling Scripts .......................................................................................... 2758.1.2.7 Running the NLS Cleanup Job ........................................................................ 276

8.2 The DBA Log....................................................................................... 2778.3 Back-End Configuration .................................................................... 2778.4 The SQL Script Maintenance ............................................................. 2788.5 Scheduled DB2 Tasks ........................................................................ 279

9 Alerts ................................................................................................ 2829.1 Alerts: Database System Monitoring in CCMS ................................ 2829.2 Alerts: Configuring Database System Monitoring ........................... 2839.3 Alerts: Alert Monitor ........................................................................... 2849.4 Alerts: Alert Message Log ................................................................. 2859.5 Alerts: Alert Configuration ................................................................ 287

10 Diagnostics .................................................................................... 29010.1 Diagnostics: Displaying the Audit Log ........................................... 29010.2 Diagnostics: Lock-Wait Events ....................................................... 29110.3 Diagnostics: Missing Tables and Indexes...................................... 29210.4 Diagnostics: Message History ........................................................ 29310.5 Diagnostics: Dump Directory .......................................................... 29510.6 Diagnostics: CLP Commands ......................................................... 29610.7 Diagnostics: DB2 Logs .................................................................... 296

11 BW Administration ........................................................................ 29811.1 BW Administration: MDC Advisor .................................................. 298


8 November 2010

11.2 BW Administration: Administration and Monitoring of the Near-Line Storage (NLS) Database .................................................................. 298

11.2.1 BW Administration: NLS Configuration................................................................ 29911.2.2 BW Administration: NLS Overview ...................................................................... 300

1 The DBA Cockpit

November 2010 9

Database Administration Using theDBA Cockpit: IBM DB2 for Linux, UNIX,and WindowsUseThis document explains how you administer your database using the DBA Cockpit that allowsyou to monitor, control, and configure your database. The DBA Cockpit provides you withaccess to all the functions and indicators for monitoring and administration:

Checking system status and operation modes

Locating potential problems as quickly as possible

Early diagnosis of potential problems, for example, resource problems in the host ordatabase system, which could adversely affect the SAP system

Analyzing and tuning the SAP system and environment (host and database systems) tooptimize the throughput of the SAP system

Configuring the database

This document applies to SAP systems that are based on SAP EnhancementPackage 2 for SAP NetWeaver 7.0. or higher.

Naming ConventionsThroughout this document, the following naming conventions apply:

IBM DB2 Version 9.7 for Linux, UNIX, and Windows is referred to as DB2 V9.7.



More InformationThe DBA Cockpit [Page 10]

For additional information about running an SAP system on DB2 for Linux, UNIX, andWindows, choose SAP on DB2 for LUW in the SDN in the Useful Links section of theDBA Cockpit.

For DB2-specific information, see the respective IBM DB2 Information Center for yourdatabase and the following IBM manuals:

IBM DB2 System Monitor Guide and Reference

IBM DB2 Performance Guide

1 The DBA Cockpit

10 November 2010

1 The DBA CockpitThe DBA Cockpit is a platform-independent tool that you can use to monitor and administeryour database. You access the DBA Cockpit by calling transaction DBACOCKPIT.

FeaturesBy default, the DBA Cockpit starts with the Web browser-based user interface as entryscreen.

Note

The SAP GUI-based user interface is still available for compatibility reasons but has beendeprecated. Therefore, enhancements for new SAP and database releases are not part ofthe SAP GUI.

End of the note.

ActivitiesYou can use the DBA Cockpit to:

Navigate between different actions

Change to another action without closing the previous action and still hold all dataretrieved by this action

Handle central configuration

Monitor remote systems using remote database connections

To use the functions offered for remote monitoring, you must configure the systemyou want to monitor. The local system is configured automatically when you start theDBA Cockpit for the first time.

After having configured the connection and depending on the database, more actionsare required to configure the database monitor and to set up databaseadministration.

Caution

For systems that are monitored using a remote database connection, constraintsdepend on whether:

o The database release of the remote system is compatible to the databaserelease of the local system.

o You want to monitor an ABAP-only or a Java-only SAP system.

End of the caution.

More InformationWeb Browser-Based User Interface [page 11]

SAP GUI-Based User Interface (Deprecated) [page 16]

1 The DBA Cockpit

November 2010 11

1.1 Web Browser-Based User Interface (WebDynpro)The Web browser-based user interface differs from the classical SAP GUI-based userinterface with regard to the overall screen layout and navigation, customizing of the userinterface, and the provided functions.

By default, transaction DBACOCKPIT starts the Web browser-based user interface (WebDynpro). In contrast to the standard SAPGUI, the Web browser-based user interface requiresan additional configuration of the DBA_COCKPIT Web service.

For more information, see:

SAP Note 124500

Administration: HTTP Communication Using the SAP System in the SAP Library at:

http://help.sap.com/saphelp_sm32/helpdata/en/78/2bff7a01bd11d5991400508b6b8b11/frameset.htm

Navigation and Screen LayoutThe entry screen of the DBA Cockpit with the Web browser-based user interface is dividedinto the following areas:

Content area

Content detail area

Detail navigationFramework message window

System landscapeselector

Common header area

Central system data

Favorites list

Top level navigation including second-level navigation

Global toolbar

Useful Links list

Screen Layout of the Web Browser-Based User Interface

Common Header AreaProvides a standard set of functions, for example, to log off from the DBA Cockpit or tocustomize the layout.



1 The DBA Cockpit

12 November 2010

Top Level Navigation Including Second-Level NavigationIn the top level navigation, you can switch between the following areas:

Cross-system area on the System Landscape tab page

Provides information about the overall system landscape

Database-specific area on the Database tab page

Provides information about the selected database

In the second-level navigation, the main task areas of database administration areprovided for this area, for example, performance monitoring, space management,and job scheduling.

For fast navigation, these main task areas provide pull-down menus corresponding tothe related detail levels.

You can hide the areas Detail Navigation, System Landscape Selector, and Favorites bychoosing the Expand or Collapse Launchpad pushbutton on the left side of the top levelnavigation area. If the launchpad is collapsed, the second-level navigation part provides asimplified system selection field with an attached F4 help. Your chosen screen layout isstored in the user settings and restored at the next start of the DBA Cockpit.

Detail NavigationContains the main actions of the main task areas. Depending on the selected main action, asubset of related actions is available.

Example

If you choose Performance in the top level navigation area, the following main actions areavailable:

Performance Warehouse

Time Spent Analysis

Workload Statistics

Snapshots

System Resources

Critical Activities

Utilities

History

If you choose Performance Warehouse, the subactions Reporting and Configuration becomeavailable.

End of the example.

1 The DBA Cockpit

November 2010 13

System Landscape SelectorProvides a quick overview of all configured systems. This area is described in more detailunder Customizing of the System Landscape Selector later in this section.

Favorites ListContains a list of favorite links to special tools and actions.

To provide quick access to specific tools and actions, choose Personalize Add Favoritein the common header area. An entry is added to your list of favorites. You can rename or

delete favorites by choosing Personalize Organize Favorites .

For more information, see Special Tools in the Favorites List [page 19].

Useful LinksContains the following useful links to:

The IBM DB2 Information Center

By choosing this link, you can directly access online information about DB2.

SAP on DB2 for LUW in the SAP Developer Network (SDN)

By choosing this link, you can directly access information about the DB2 SAPcommunity in the SDN, such as, articles, blogs, and so on.

Framework Message WindowDisplays the message window that is provided by the framework. Unlike the classic SAP GUImessage processing, this window contains a complete history of all messages that are sentduring the session.

In addition, you can:

Collapse or expand the window by choosing Expand Message Window or CollapseMessage Window.

Check if a long text for a message is available by double-clicking the message or bychoosing Details.

Note

By default, the message window is collapsed. When a new message is generated, it isautomatically expanded.

End of the note.

Global ToolbarThe global toolbar provides a set of globally available functions for navigation and content-related functions like Refresh.

Central System DataThis area is common to most actions providing, for example, the time of the last refresh, thestartup time, and the database name.

1 The DBA Cockpit

14 November 2010

Content AreaDisplays details of the currently selected action. The content area is divided into the followingareas that are optionally available depending on the chosen action:

The Selection area where you can enter selection criteria for the content to bedisplayed

The Summary area that provides summarized views of data, for example, totals orexecution times

The content, which depends on the screen and action you have chosen

You can refresh the content by choosing the Refresh pushbutton in the global toolbaror by changing the selection criteria and then choosing the Apply Selectionpushbutton in the Selection area.

Chart View in the Content AreaSome reports are displayed as a chart. To modify the chart view, you can use the ChartType, Values, and Chart Size menu buttons that are optionally available depending on thescreen. By choosing the Chart Size menu button, you can specify the width and height of thechart to be displayed.

In addition, you can open a detailed table view by choosing the Toggle Table Displaypushbutton.

Content Detail AreaOnly appears with certain actions and displays additional information that is related to theselected action. Typically, this area shows details that are related to some list display.

Customizing the System Landscape SelectorBy default, all systems are displayed without any grouping or filtering. For each configuredsystem, the alert status, the name of the system and its database host is displayed. Thefollowing menu buttons are available for the list of systems:

Refresh System Landscape

You can refresh the information about the available systems in the list.

Group Systems by Selected Criteria

You can customize the displayed list of systems by grouping them according to theselected criteria:

o Database Platform

o Name

o Custom

o Alerts

To use a custom grouping, you must first define and add a custom group to the list.To do so, choose Add Group from the pop-up menu of the menu button GroupSystems by Selected Criteria. Specify a name for the custom group and assign thesystems of your choice.

1 The DBA Cockpit

November 2010 15

As soon as you have added a custom group, the option Organize Groups becomesavailable in the pop-up menu of the menu button Group Systems by SelectedCriteria, which lets you maintain an already existing group.

Filter Systems by Selected Criteria

You can filter the list of available systems to show only those systems that match thefilter criteria. You filter, for example, by the alert status of the systems.

Search Systems

Provides an input field where you can search for a specific system in the list.

More InformationSpecial Tools in the Favorites List [page 19].

1.2 Maintenance Actions in the DBA CockpitThe DBA Cockpit provides a set of actions to monitor and to maintain the database. To beable to perform these actions, the SAP user requires some additional authorizations.

The maintenance actions provided in the DBA Cockpit set locks to prevent parallelprocessing. All changes to the database are recorded in an audit log file.

Authorization CheckWhen you start the DBA Cockpit or change to another system in the DBA Cockpit, anauthorization check is performed.

You can enable or disable the database maintenance in general using the profile parameterdbs/db6/ccms_maintenance. If this profile parameter is not set in the instance profile, thedefault value 1 is used.

Depending on the setting of profile parameter dbs/db6/ccms_maintenance, the followingauthorization checks exist:

If the profile parameter is set to 0, SAP users cannot perform any maintenanceactions, regardless of their personal permissions.

If the profile parameter is set to 1, SAP users can perform maintenance actionsdepending on their personal permission for the authorization object S_RZL_ADM. Theattribute ACTVT of this authorization object defines whether a user may maintain oronly monitor objects.

1 The DBA Cockpit

16 November 2010

Granting of Database PermissionsTo be able to access the database, the user that is used for remote monitoring must at leasthave sufficient authorizations.

Local systems use the standard SAP connect user for monitoring tasks. This useralready has sufficient permissions for standard monitoring tasks. If moreauthorizations are required for administrative actions, a special administrationconnection is used where you can freely assign more administration rights to a user.This special connection is called +++DB6ADM and is automatically generated.

You can change the user and password as described in Configuring DatabaseConnections [page 46].

Note

If an action requires the administration connection +++DB6ADM and the user andpassword have not been set correctly, an error message is generated, and therelevant action tries to continue with the standard SAP user connection.

End of the note.

Systems that are monitored via remote database connections use the user that isspecified for the database connections. This user must have sufficient authorizations.

Locking of ActionsFor each maintenance action that you have selected using the DBA Cockpit, a lock is set forthe system that is being monitored. All locks are released when you exit the DBA Cockpit orwhen you change to another system.

Auditing of Maintenance ActionsWhen you make changes that affect database objects such as database configurationparameters or tablespaces, an audit log is written. You can display this audit log in the DBACockpit.

For more information, see Diagnostics: Displaying the Audit Log [page 290].

1.3 SAP GUI-Based User Interface (Deprecated) The SAP GUI-based user interface of the DBA Cockpit has been deprecated. This meansthat new capabilities of the DBA Cockpit that are available with Enhancement Package 2 forSAP NetWeaver 7.0 are not supported, for example:

New functions of DB2 V9.7 such as index compression

Screens that rely on the proper setup of the data collection framework (DCF) thatprovides historized monitoring data of the database

1 The DBA Cockpit

November 2010 17

The following table provides an overview of all functions that are no longer supported or thathave been replaced by new Web Dynpro-based functions:

SAP GUI Web Dynpro

Performance Lock Waitsand Deadlocks Replaced by Diagnostics Lock-Wait Events

Performance HistoryDatabase

Integrated in Performance Snapshots Database ifDCF is installed

Performance HistoryTables

Integrated in Performance Snapshots Tables if DCFis installed

Space Tables and Indexes

Replaced by specialized views under Space Tables andIndexes if DCF is installed

In the submenu, you can choose between the followingviews:

Top Space Consumers

REORG Candidates

Compression Status

Virtual Tables

Space History Overview Available but deprecated

Space History Databaseand Tablespaces Replaced by Space Database if DCF is installed

Space History Tablesand Indexes

Replaced by Space Tables and Indexes Top SpaceConsumers if DCF is installed

Configuration MonitoringSettings

Available but deprecated

To configure the DCF, choose Configuration DataCollection Framework Collector Configuration

Diagnostics CumulativeSQL Trace n/a

Diagnostics Trace Status n/a

Diagnostics DeadlockMonitor n/a

BW Administration BWData Distribution n/a

1 The DBA Cockpit

18 November 2010

Note

If you want to use the SAP GUI-based user interface, you can change the default userinterface as follows:

1. Call transaction DBACOCKPIT.

The SAP GUI-based user interface appears and in parallel, the Web browser-baseduser interface in a separate browser window.

2. In the SAP GUI, choose the Personal Settings menu button and select Use SAPGUIfor DB2 LUW Systems.

The changes take effect with the next call of transaction DBACOCKPIT.

End of the note.

For more information about the functions provided on the SAP GUI screens, see DatabaseAdministration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows (For SAPSystems based on Enhancement Package 1 + 2 of SAP NetWeaver 7.0) at:

http://service.sap.com/instguidesnw70 Operations Database-Specific Guides

http://service.sap.com/instguidesnw70

2 Special Tools in the Favorites List

November 2010 19

2 Special Tools in the Favorites List The Favorites list provides easy access to important tools and actions. By default, theFavorites list contains the following links that cannot be removed:

EXPLAIN Access Plan

SQL Command Line

Index Advisor

Schedule an Action

You can extend the Favorites list, that is, add and organize favorites by choosingPersonalize Add Favorite or Personalize Organize Favorite in the common

header area.

2.1 The EXPLAIN FunctionAs of SAP Enhancement Package 1 for SAP NetWeaver 7.0, you can use the EXPLAINfunction either on the Web browser-based user interface or on the SAP GUI-based userinterface of the DBA Cockpit.

2.1.1 The EXPLAIN Function (Web Browser-BasedVersion) You can use the Web browser-based EXPLAIN to review the access plans of all SELECT,INSERT, UPDATE, or DELETE statements.

You can access the Web browser-based version of the EXPLAIN function as follows:

In the navigation frame of the SAP GUI-based user interface of the DBA Cockpit,choose Diagnostics EXPLAIN (New Version) .

A Web browser opens and displays the screen EXPLAIN Access Plan. Enter an SQLstatement and choose the EXPLAIN pushbutton.

In the Favorites list of the Web browser-based user interface, choose Explain AccessPlan.

In the database-specific area of the Web browser-based user interface, choosePerformance Snapshots Applications . Double-click an application and

choose the Statement Text tab page. If a statement is displayed, choose theEXPLAIN pushbutton to display the access plan.

For more information, see Application Details: Statement [page 126].


20 November 2010

In the database-specific area of the Web browser-based user interface, choosePerformance Snapshots SQL Cache . Select a statement from the list and

choose the EXPLAIN pushbutton.

For more information, see Snapshots: SQL Cache [page 129].

Note

The statements might contain optional comments such as --OPTLEVEL( <optlevel> ) --QUERY_DEGREE(< query_degree> --LOCATION( <report> , <position> ). Ifno comments are specified, the statements are explained using the default <optlevel> andthe default <query_degree> for the work process.

End of the note.

If a statement was explained successfully, information about the SQL statement text isprovided on the following tab pages:

Tab Page Description

OriginalStatement Displays the original SQL statement

OptimizedStatement Displays the SQL statement that was rewritten by the DB2 optimizer

Access Plan Displays the access plan that was generated by the DB2 optimizer

EXPLAINSnapshot

Displays the output of the EXPLAIN snapshot

Note

The EXPLAIN Snapshot tab page is only available if the monitored databaseis DB2 V9.5 for Linux, UNIX, and Windows or higher.

End of the note.

Using the Access PlanThe access plan shows all database operations that are performed when the statement isexecuted. It is displayed as a graphical tree, and each node in the tree represents anoperator of the access plan.

You can do the following:

Display or hide details of an operator by choosing the Open Node or Close Node iconon the respective node

Expand or collapse subtrees by choosing the Show Child Node icon or the Hide ChildNode icon respectively


November 2010 21

View operation details by double-clicking an operator in the graphical tree

Global details about an operator are displayed on the following tab pages:

o General

Displays global details about the access plan

o Operator <Name of operator>

Displays details for the selected operator

o Catalog Information (Optional)

Displays details for the respective catalog object of the selected operator

o Predicates (Optional)

Displays filter predicates for the selected operator

Search for operators in a complex statement by choosing Find Nodes for Labels

Open an extra navigation window for complex access plans by choosing ToggleNavigation Window

Print the graphic by choosing Print the Current Model

Configure the graphic before you print it by choosing Configure the Printout

Display or hide the quick details of all operators by choosing Collapse or Expand

Display global details about the access plan by choosing View Details

Display information about the JNet version used (can be required by SAP Support)by choosing the help button

Note

For each index used in the access plan, the number of key columns that were really usedwithin the access plan is displayed. In the appropriate tool tip, the used index field names arealso displayed.

Volatile tables and indexes of volatile tables are marked with an extra volatile label. Tochange and re-explain the SQL statement, choose Edit Statement.

End of the note.

Changing the DB2 Optimizer ConfigurationIf you want to change the DB2 optimizer parameters, choose the Optimizer pushbutton. Withthis function, you can temporarily change the OPTIMIZER LEVEL, the QUERY DEGREE, andthe VOLATILE flag for all tables referred to in the query. In addition, DB2 experts are able tospecify optimization guidelines.

User Interface SettingsIf you want to change the user interface of the Web browser-based user interface, choose theSettings pushbutton.


22 November 2010

2.1.2 The EXPLAIN Function (SAP GUI-BasedVersion)You can use this function to explain all SELECT, INSERT, UPDATE, or DELETE statements.

The statements might contain optional comments such as --OPTLEVEL( <optlevel> ) --QUERY_DEGREE(< query_degree> --LOCATION( <report> , <position> ). If nocomments are specified, the statements are explained using the default <optlevel> and default<query_degree> for the work process.

Accessing the EXPLAINYou can call the EXPLAIN function in the following ways:

Call the DBA Cockpit and choose Diagnostics EXPLAIN in the navigation frame of theDBA Cockpit. On the Diagnostics: EXPLAIN screen, enter an SQL statement manuallyand choose Explain.

Call the DBA Cockpit and choose Performance Applications in the navigation frame ofthe DBA Cockpit.

Call the DBA Cockpit and choose Performance SQL Cache in the navigation frame ofthe DBA Cockpit.

Call the DBA Cockpit and choose Diagnostics Cumulative SQL Trace in thenavigation frame of the DBA Cockpit.

Call transaction ST05 and choose Enter SQL statement. Enter an SQL statementmanually and choose Explain.

If a statement cannot be explained, the ERROR: Check SQL Statement screenappears providing a detailed error message and the possibility to modify the statement.To continue, choose Explain Again.

Call transaction ST05 and choose Trace list. Select one statement and choose Explain.

Displaying the Access Plan of a StatementIf a statement was explained successfully, the Display Execution Plan for SQL Statement screenappears, providing information on the SQL statement text, the OPTLEVEL and QUERY_DEGREE thatwas used to explain this statement, and the access plan.

The access plan generated by the DB2 optimizer is displayed as a tree structure. It consists of alldatabase operations that will be performed when the statement is executed.

The estimated execution time is displayed in timerons (arbitrary IBM time unit). All operators arenumbered, starting with zero. Operators can have the following extensions:

Extension Description

[O]/[I] Shows whether the operator acts as an outer/inner input branchfor a subsequent join operation

(<Partition>) Shows on which partition this operation was performed

This is only displayed if you are using a multi-partition database.

Non-volatile tables and indexes of non-volatile tables are displayed in blue. Volatile tablesand indexes of volatile tables are displayed in orange.

For each index used in the access plan, the number of key columns, that is, index fields thatwere really used within the access plan, are displayed.


November 2010 23

For further analysis of the displayed information, you can choose from various options in theapplication tool bar. For more information, see EXPLAIN Options [Page 23].

More InformationFor additional information on the EXPLAIN function, see SAP Note 400938.

For more general information, see the IBM documentation: Administration Guide: Chapter 26,SQL Explain Facility.

2.1.2.1 EXPLAIN OptionsOn the Display Execution Plan for SQL Statement screen, the following options are available:

Option Description

Details If no operator in the access plan is highlighted when choosingthis option, a dialog box is displayed providing detailedinformation on the statement and each operator. This output issimilar to the one of the DB2 command line tool db2exfmt.For more information, see the IBM documentationAdministration Guide, Appendix I.

If operator no. 0 is highlighted, only the original statement andoptimized statement are displayed in a separate dialog box.

If any other operator is highlighted, the system displaysdetailed information on the selected operator only.

Optimizer The access plan may vary depending on the optimizerparameters specified. When you choose this button, theChange Query Optimization dialog box appears where youcan change the parameters OPTIMIZER LEVEL, QUERYDEGREE and the flag VOLATILE for the tables used in theaccess plan. To explain the statement with new parameters,choose Explain Again.


24 November 2010

DB Catalog With this option, you can display system catalog informationon tables and indexes that are shown in the access plan. Thefollowing information is displayed:

For a table:Selected information from table SYSCAT.TABLES isdisplayed. Additionally, all indexes of the table are displayedwith their index columns.

For an index:Selected information from table SYSCAT.INDEXES for thisindex is displayed. Additionally, selected information fromtable SYSCAT.COLUMNS is displayed for all indexcolumns.

Depending on whether you have selected a table or an index,the following buttons are available:

Table

Displays selected information from tableSYSCAT.TABLES

Additionally, all indexes of the table are displayed withtheir index columns.

Columns

Displays selected information from tableSYSCAT.COLUMNS for all table columns

Indexes

Displays information from table SYSCAT.INDEXES for allindexes of the table as well as information from tableSYSCAT.COLUMNS for all index columns

Update Statistics

Updates the catalog statistics for the table

If the catalog statistics were updated successfully, thefield <stats-time> is displayed in green.

Table

Displays selected information from tableSYSCAT.TABLES

Additionally, all indexes of the table are displayed withtheir index columns.


November 2010 25

Dictionary With this option, you can display the ABAP Dictionarystructure (definition) of a table by selecting the table in theaccess plan.If you do not select a table in the access plan, the ABAPDictionary structure (definition) of the first dictionary object ofthe SQL statement is displayed.

With this option, you can display the structure of views, eventhough views never appear in the access plan.

This function is not available for systemsmonitored using a remote database connection.

Test Execution This option is only available, if a:

SELECT statement is explained using transaction ST05Trace list, the parameter values for all parameter markers ofthe statement are provided and the operation is other thanPREPARE

SELECT statement without parameter markers is explained

When you use the EXPLAIN function, the entered SQLstatement is only prepared and the access plan of theoptimizer is chosen because of the system catalog statistics.On the basis of this information the optimizer estimates thecosts for the execution of this statement.

However, the estimated costs may not correspond to the realexecution time. Reasons for this might be bad statistics, a baddatabase layout or problems of the optimizer itself.

The Test Execution option measures the real execution timeand provides other snapshot data, such as the number ofbuffer pool accesses and sorts for the selected statement.When the statement is executed, the parameter markers arereplaced by the actual parameter values. A dialog boxappears where you can change these values to investigate thedependence of the execution time from these values.

The result of several test executions of the same statementcan vary because, for example, the buffer pool may alreadycontain data that is necessary for the execution.

This function is not available for systemsmonitored using a remote database connection.


26 November 2010

Tree Info The following additional information is displayed or hidden:

num_rows

Estimated number of rows (result set)

tot_cost

Estimated total cost for this statement

i/o_cost

Estimated I/O cost of the statement

This information is also included in the output informationwhen you choose Details.

Edit When choosing this option, the system switches to an editorwindow in which you can modify the selected SQL statementand explain it again.

Source This option is only available when the statement contains aLOCATION comment, for example, when you call EXPLAINusing transaction ST05 Trace list.

The location of the statement in the ABAP source code isdisplayed in a separate window.

This function is only available for the local systemor ABAP systems for which an additional RFCdestination has been assigned.

The Collect function is no longer available. To collect EXPLAIN data, use thedb2support command line tool.

2.2 SQL Command Line This screen provides a virtual DB2 command line processor.

You can access the SQL Command Line screen by calling the DBA Cockpit and choosingSQL Command Line in the Favorites list of the DBA Cockpit. The SQL Command Line

screen appears in a separate Web browser.

If you enter any SQL command, the output is returned by the DB2 command line processor.You can also execute CLP commands that are supported by the ADMIN_CMD storedprocedure. The data is displayed in the same way as the corresponding CLP commands.


November 2010 27

2.3 The Index Advisor To improve the performance of queries, you can retrieve recommendations about usefulindexes using the index advisor. In addition, you are able to design new virtual indexes thatcan be validated before they are actually created.

You can access the index advisor using one of the following user interfaces:

Web browser-based interface

In your Favorites list, choose Index Advisor. The application starts in a separate Webbrowser.

SAP GUI-based user interface

In the navigation frame of the DBA Cockpit, choose Diagnostics Index Advisor. The Index Advisor starts in a separate Web browser.

ActivitiesYou use the index advisor to perform one of the following actions:

To evaluate the SQL statements in the dynamic SQL cache by receivingrecommendations for potential new indexes that might improve the overall systemperformance

Based on the current content of the dynamic SQL cache, the DB2 Design Advisordetermines and recommends new indexes that might improve the overall systemperformance.

For more information, see Retrieving Index Recommendations for the Dynamic SQLCache [page 28].

To determine and recommend new virtual indexes for a single SQL statement

On the basis of a given SQL statement, the DB2 Design Advisor determines andrecommends new indexes that might improve the performance of the query. .

For more information, see Retrieving Index Recommendations for a Single SQLStatement [page 30].

To create user-defined virtual indexes

If you are not satisfied with the recommendations of the DB2 Design Advisor, youcreate a virtual index specifically tailored to your requirements. For more information,see Defining Virtual User-Defined Indexes [page 32].

To include the indexes in the EXPLAIN function when explaining a query

You can check, for example, if the virtually defined indexes would improve theperformance of a query. For more information, see Validating Indexes Using theEXPLAIN Function [page 34].


28 November 2010

2.3.1 Retrieving Index Recommendations for theDynamic SQL Cache

Note

This application is only available on the Web browser-based user interface.

End of the note.

1. On the Index Advisor screen, choose the SQL Cache radio button in the AdvisorMode area.

2. Choose the Recommend Indexes pushbutton.

A background job starts. The DB2 Design Advisor analyses the current content of thedynamic SQL cache and the background job returns the results as soon as the DB2Design Advisor has finished its analysis.

The user interface remains in read-only mode while the analysis is still running. Tocheck for results, you can either choose the Update pushbutton or wait until it isautomatically checked for results every 60 seconds. The results are displayed in thefollowing table:

Column Description

Index Name Name of the index

Type

o Existing (not-used)

Index exists in the system catalog, but for the investigated SQLquery it is not identified as usable by the DB2 optimizer.

o Recommended

Index is recommended by the DB2 Design Advisor.Recommended indexes that do not exist are candidates for newindexes to be created.

Note

Indexes are displayed with the following background colors:

Green

Recommended index that already exists and that the DB2optimizer would use

White

Existing index that is, however, not appropriate for therespective SQL statement

Red

Recommended index that does not yet exist


November 2010 29

Exists

o Yes

Index exists in the database.

o No

Index is a virtual index.

Table Name Table on which the index is defined

Schema Name of the index schema

Uniqueness

Specifies a unique rule:

o Primary Key

o Unique

o Duplicates Allowed

NLEAF Number of leaf pages

NLEVELS Number of index levels

Rev. Scans

o Yes

Index supports reverse scans.

o No

Index does not support reverse scans.

Columns Number of columns in the key plus the number of included columns ifthere have been any defined

INCLUDEs Number of included columns

Column Names List of column names


30 November 2010

3. To retrieve more information about which SQL statement would benefit from therecommended indexes, select an index from the list.

The details are displayed in the following table in the content detail area:

Column Description

SQL Statement Name of the SQL statement that is in the dynamic package cache and thatwould benefit from the index

Frequency Number of times the statement has been executed since it has entered thedynamic SQL cache

Cost Saving Estimated cost savings in percent after the index was created

Cost Before Estimated SQL cost in timerons before the index was created

Cost After Estimated SQL cost in timerons after the index was created

You can find the complete output of the DB2 design on the Advisor Output tab page.The complete output also includes the estimated space requirements of eachrecommended index.

Note

If you do not want to display unused indexes, you can set a filter on the tableaccordingly.

End of the note.

2.3.2 Retrieving Index Recommendations for a SingleSQL Statement

1. On the Index Advisor screen, enter the SQL statement that you want to investigate inthe SQL Statement editor field.

Note

In the Web browser-based user interface, you first have to choose the SingleStatement radio button. Otherwise, the editor field where you can enter the SQLstatement does not become available.

End of the note.

2. Choose the Recommend Indexes pushbutton.

The DB2 Design Advisor evaluates existing indexes on the affected tables. If the DB2Design Advisor cannot find an appropriate index in the system catalog, the toolrecommends one or more indexes that might improve the performance of the query.


November 2010 31

The results are displayed in the following table:

Column Description


Type

o Existing (not-used)

Index exists in the system catalog, but for the investigatedSQL query it is not identified as usable by the DB2optimizer.

o User-Defined

Index has been virtually defined by the user to determinewhether such an index could be used to improve the queryperformance. Those indexes do not exist in the systemcatalog.

o Recommended

Index is recommended by the DB2 Design Advisor.Recommended indexes that do not exist are candidatesfor new indexes to be created.

Note

Indexes are displayed with the following backgroundcolors:

Green

Recommended index that already exists and thatthe DB2 optimizer would use

White

Existing index that is, however, not appropriate forthe respective SQL statement

Red

Recommended index that does not yet exist

End of the note.

Exists

o Yes

Index exists in the database.

o No

Index is a virtual index.

Table Name Table on which the index is defined


32 November 2010

Column Description

Schema Name of the index schema

Uniqueness

Specifies a unique rule:

o Primary Key

o Unique

o Duplicates Allowed

NLEAF Number of leaf pages

NLEVELS Number of index levels

Rev. Scans

o Yes

Index supports reverse scans.

o No

Index does not support reverse scans.

Columns Number of columns in the key plus the number of includedcolumns if there have been any defined

INCLUDEs Number of included columns

Column Names List of column names

Note

If you do not want to display indexes that are not used, you can set a filter on thetable accordingly.

End of the note.

2.3.3 Defining Virtual User-Defined Indexes Caution

If you are using the Web Browser-based user interface, you can perform the following stepsonly if the Single Statement radio button is selected in the Advisor Mode area of the IndexAdvisor screen.

End of the caution.

If the index recommendations provided by the DB2 Design Advisor do not meet yourrequirements, you can also define virtual user-defined indexes. In addition, you can validatetheir use by calling the EXPLAIN function.


November 2010 33

PrerequisitesYou have already retrieved index recommendations for a single SQL statement [page 30].

ProcedureIn the Index Advisor screen, choose Add Virtual Index. Depending on your user interface,perform the following steps:

SAP GUI-Based User Interface1. In the Define Virtual Index dialog box, enter the schema and the table on which you

want to define the virtual index.

2. Choose the Load Table Columns pushbutton.

The column names of the appropriate table are displayed in the Table Columns Listfield.

3. To define index columns, either choose the Add Column to Index or the RemoveColumn From Index pushbutton.

4. If you want the virtual index to be unique, select the Unique checkbox.

Note

By default, all new virtual indexes are created with the Allow Reverse Scans optionon database level. However, in the ABAP Dictionary, you cannot define this option fornew virtual indexes.

End of the note.

5. To continue, choose the Add pushbutton.

The new user-defined virtual index is added to the list of indexes.

Web Browser-Based User Interface1. In the Diagnostics: Index Advisor dialog box, enter the schema and the table on

which you want to define the virtual index.

2. If you want the virtual index to be unique, select the Unique checkbox.

Note

By default, all new virtual indexes are created with the Allow Reverse Scans optionon database level. However, in the ABAP Dictionary, you cannot define this option fornew virtual indexes.

End of the note.

3. Choose the Index Columns pushbutton.

The column names of the appropriate table are displayed in the Table Columns Listfield.


34 November 2010

4. To define index columns, either choose the Add Column to Index or the RemoveColumn from Index pushbutton.

5. To continue, choose the Add Virtual Index pushbutton.

The new user-defined virtual index is added to the list of indexes.

Note

User-defined indexes are always displayed with a red background color because they do notreally exist like the recommended indexes. If you want to remove all user-defined indexes,choose the Remove User-Defined Indexes pushbutton.

End of the note.

ResultYou can now use the EXPLAIN [page 19] function to validate existing, recommended, andnewly created user-defined indexes.

2.3.4 Validating Indexes Using the EXPLAIN FunctionOn the Index Advisor screen, choose EXPLAIN and one of the following options from thedropdown list:

Only existing indexes

This option corresponds to the normal EXPLAIN function that is known from the SQLcache. Only indexes that are known from the system catalog are used to build theaccess plan.

Existing and recommended indexes

Indexes that are known from the system catalog and indexes that are recommendedby DB2 are used to build the access plan.

Existing, recommended, and user-defined indexes

Indexes that are known from the system catalog and all virtual indexes(recommended and user-defined) are used to build the access plan.

ResultA new dialog window or Web browser appears displaying the access plan that the DB2optimizer considers to be the most efficient one.


November 2010 35

2.3.5 Creating Indexes in the ABAP Dictionary Note

This function is not available for systems that are monitored using a remote databaseconnection.

End of the note.

You use the following procedure to create an index in the ABAP Dictionary that has beenvirtually defined before but does not yet exist.

Recommendation

Additional indexes require additional space and need to be maintained when data is updatedor inserted in a table. We recommend that you only create additional indexes if they reallycan improve the performance of queries that put a heavy load on your database.

End of the recommendation.

Procedure1. On the Index Advisor screen, choose an index (user-defined or recommended) that

does not yet exist.

2. Choose the Create Index in ABAP Dictionary pushbutton (that is located next to theIndex Name column).

The Create Index in ABAP Dictionary dialog box appears.

3. Enter a description for the index and choose Create.

The index is created in the ABAP Dictionary.

After the index has successfully been created, you can decide if you want toschedule a RUNSTATS for the affected table.

Note

If the index to be created is extending an existing unique index (including primary keys) withone or more INCLUDE columns, you have to replace the existing index with a new indexinstead of creating a new one.

In this case, the Replace Existing Unique Index dialog box appears instead of the CreateIndex in ABAP Dictionary dialog box. If you replace the existing index, the system replacesthe index only on database level. This means that no changes are applied to the ABAPDictionary. The replacement is automatically scheduled as an SQL script in the DBA PlanningCalendar.

End of the note.

3 Managing the System Landscape

36 November 2010

3 Managing the System LandscapeThe following sections provide information about how to manage your system landscape:

Configuration of Systems for Remote Monitoring

Configuring Database Connections

Configuring Systems for Remote Monitoring Using the System Landscape Directory(SLD)

Central Calendar

3.1 Configuration of Systems for RemoteMonitoringTo be able to use the DBA Cockpit to monitor remote systems, you have to configure thosesystems in the DBA Cockpit. If the DBA Cockpit is used as part of Solution ManagerDiagnostics, the DBA Cockpit setup is part of the SAP Solution Manager setup. This meansthat when you integrate systems into the SAP Solution Manager landscape, the relateddatabases are configured in the DBA Cockpit and no DBA Cockpit-specific setup is requiredanymore.

Alternatively, you can configure your database system either using database information thatis stored in the system landscape directory (SLD) for automatic generation and update ofsystem entries or by manually creating database connections and system configurationentries.

To access the System Configuration screen, choose System Configuration on the SystemLandscape tab page of the DBA Cockpit. A table of all monitored systems is displayed. In thefirst column, an icon indicates the current status of each system.

Normally, when you start the DBA Cockpit, the local system is set as default system. Tochange this setting, select a system from the list and choose Default System.

Note

This setting only applies to the user that is currently logged on to the system. It is not asystem-wide setting.

End of the note.

To monitor a system remotely, you use the following methods:

Remote database connections (mandatory)

This method uses additional connections. It is the main access method for monitoringand administration tasks and it is mandatory. You can specify remote connections forany database and maintain the connections using the DBA Cockpit.


November 2010 37

RFC connection (additional option for SAP ABAP systems only)

For this method, you have to assign an RFC connection to your system. RFCconnections are available for SAP ABAP systems only. You can use RFCconnections as an optional access path for ABAP-related monitoring functions, forexample, for the consistency check of the ABAP Dictionary. This means that the DBACockpit uses the RFC connection in parallel to the database connection for the samesystem.

Note

You can only maintain RFC connections with transaction SM59, not with the DBACockpit.

End of the note.

3.1.1 Configuring Systems for Remote MonitoringManuallyYou use this procedure to configure systems that you want to monitor using remote databaseconnections. A manual system configuration is only necessary if the monitored database hasnot been configured during the integration of a system using SAP Solution Manager.

The configuration does not include the setup of the monitoring infrastructure, but you performonly a basic setup that is necessary to connect to the monitored database. For subsequentconfiguration steps, see Enabling the Database for the Data Collection Framework [page 40].

Note

Depending on the database platform of the selected system, some options might not beavailable. In this case, you cannot enter any data in the corresponding fields.

End of the note.

Prerequisites

The system(s) that you want to monitor must have a database release that iscompatible with the database release of your local database.

The user for the database connection must have sufficient database permissions. Formore information, see Maintenance Actions in the DBA Cockpit [page 15].

Procedure1. Call the DBA Cockpit.

The System Configuration screen appears displaying a list of all available systemswith a Configuration Status icon that indicates the current system status.

Note

When you start the DBA Cockpit for the first time, the local system is automaticallyadded to the list of all available systems. At least one system entry is displayed.

End of the note.


38 November 2010

2. Choose the Add pushbutton.

In an additional browser window, the wizard Integrate a System appears.

The following table lists the steps and recommended actions:

Step Name Action

IntroductionProvides an overview of the configuration steps

No action to be taken

System Characteristics

Specify the following:

o Name of the system that you want to monitor

Note

This name is a unique ID and does not have to be theSAP system ID. You can choose any name except theSAP system ID of the local system that is reserved forthe local system entry.

End of the note.

o Description of the monitored system

o Connection type

Choose between the following connection types:

Remote Database Connection

Remote Database Connection andRFC Destination

Remote Database Connection viaRFC Destination

RFC Destination

(Optional step that is onlynecessary if, in the previousstep, you have chosen aconnection type that requiresan RFC destination.)

Specify the name of the RFC destination to be used

Note

The specified RFC destination must already exist and beavailable.

End of the note.

You can test the destination by choosing the Test Connectionpushbutton. If the connection is not working, you can onlyproceed if you select the Ignore Communication Errorscheckbox.


November 2010 39

Database Connection


o Name of the database connection

This is a unique name that you can freely choose.Alternatively, you can search for an alreadyexisting connection name using the related searchhelp. In this case, confirm the selected nameusing the Enter key to prefill the connectionattributes.

o Database platform of the monitoreddatabase

o Connection maximum that limits theparallel use of this connection by the kernel

o Connection optimum that sets theoptimum number of open connections

Recommendation

You should set this value to 0 to ensure that thekernel closes connections if they are no longerused.


o User name and password for the user thatis used for monitoring

o List of connection parameters that arerequired to identify the database

Monitoring Settings Specify how you want to collect monitoring data:

o If alerts are to be provided for the RZ20alert monitor, select the Activate Alert Monitoringcheckbox.

Note

If you are using the DBA Cockpit in SAP SolutionManager 7.1, this option should not be usedanymore. Instead, the E2E alerting of SAPSolution Manager is used that requires no specificsetup in the DBA Cockpit.

End of the note.

o If the monitoring data is to be collected bythe remote system, select the Data Collection byRemote System checkbox.


40 November 2010

Continuation of MonitoringSettings

o If data for the Central Planning Calendaris to be provided, select the Show ScheduledJobs in Central Planning Calendar checkbox.

o Deprecated option:

Note

This option has been deprecated and should notbe used anymore. Instead, proceed as describedin Enabling the Database for the Data CollectionFramework [page 40].

End of the note.

Depending on the selected database platform, only asubset of options might be available.

SummarySummarizes all actions to be performed

To save your entries, choose the Execute pushbutton.

Execution Protocol

Summarizes all performed actions including errormessages

To exit the wizard, choose the Finish pushbutton andreturn to the System Configuration screen.

3. Optional:

If you want to change an existing configuration entry, select the system entry in theoverview list and choose the Change pushbutton.

In the dialog box Change System Configuration Entry, enter and save your changes.

4. Optional:

If you want to delete a configuration entry, select the system entry in the overviewlist, choose the Delete pushbutton and confirm the deletion.

3.1.2 Enabling the Database for the Data CollectionFrameworkAfter a system has been configured in the DBA Cockpit, the database to be monitored needsadditional instrumentation to enable the time-based collection and evaluation of data relatedto performance, configuration, and space.

To instrument this data collection framework (DCF), a separate schema is created in themonitored database that contains all relevant monitoring objects, such as:

A set of tables that keep the history

Tablespaces to store these monitoring tables


November 2010 41

A set of stored procedures to collect data on a regular basis

These stored procedures are scheduled by the DB2 administrative task scheduler(ATS).

In case of an SAP system, a work process-based workload managementconfiguration is applied.

Regardless whether the database has been configured for monitoring using SAP SolutionManager or using the DBA Cockpit, the first time you select a database system for monitoringin the DBA Cockpit, the existence of the DCF is checked.

If the DCF does not yet exist, it is automatically set up if the following applies:

The minimum database release level of the monitored database is at least DB2 V9.1.

The database is enabled for automatic storage management or the requiredtablespaces have already been created.

If the DCF cannot automatically be set up because of missing tablespaces or insufficientprivileges of the monitoring user, the DBA Cockpit initially displays the appropriateconfiguration screen where you can perform the required setup steps as described in SettingUp the Data Collection Framework (DCF) Manually [page 42].

All settings for the instrumentation, for example, recurrence patterns for the scheduled datacollectors and the amount of data to be collected are determined by templates. SAP providesthe following standard templates:

SAP Default

Most of the data collectors run hourly. The sliding window is set to two weeks exceptfor the most important tables and indexes.

SAP Detailed

Most of the data collectors run quarter-hourly. The sliding window is set to two weeksexcept for the most important tables and indexes.

By modifying these templates, you can influence the automatic setup of the DCF. For moreinformation, see Maintaining Templates for the DCF [page 42].

Note

If you set up the data collection framework, the monitoring history function that has beendeprecated as of Enhancement Package 2 for SAP NetWeaver 7.0 is switched off, that is:

The option Collect Space and Performance History Data in the system configurationentry is disabled so that the related SAP background jobs do not collect history dataanymore for SAP releases prior to Enhancement Package 2 for SAP NetWeaver 7.0.

The REORGCHK for All Tables job is no longer available in the DBA PlanningCalendar and the respective data is now collected by the DCF.

The special compression function that formerly was provided by the REORGCHK forAll Tables job, has been integrated in the Compression Status screen that isavailable under Space Tables and Indexes .

End of the note.


42 November 2010

3.1.2.1 Setting Up the Data Collection Framework (DCF)ManuallyThe DCF is set up individually for each database based on the database version, the usagetype of the database, and the SAP coding. To set up the DCF manually, you can either use atemplate or activate and configure individual history data collectors.

Recommendation

We recommend that you use templates to ensure that data is collected homogeneously inyour system landscape. Only in rare cases, it might be advisable that you configure individualhistory data collectors.


Procedure1. Call the DBA Cockpit, and on the Database tab page, choose Configuration Data

Collection Framework Collector Configuration .

The Collector Configuration screen appears.

2. Choose the Implement Template pushbutton.

The Implement Template dialog box appears. The default template is marked with anasterisk (*).

By default, deprecated functions are preselected for disabling. If you want to keepany old settings, deselect the relevant checkboxes.

Note

The option to disable deprecated functions or to keep them is only available if thereare deprecated functions that are currently active but recommended for disabling.

End of the note.

3. To set up the template in the monitored database, choose the Implement pushbutton.

More InformationConfiguration: Data Collection Framework [page 248]

3.1.2.2 Maintaining Templates for the DCFThe data collection framework is based on pre-defined templates. These templates ensure ahomogeneous setup of the history data collectors in your system landscape. You can onlymaintain these templates on the Template Definition screen in the DBA Cockpit.


November 2010 43

On the Template Definition screen, you can perform the following actions:

Create new templates

Change single history data collectors in a template

Set a default template

Delete a template

Note

In the SAP Solution Manager setup wizard for managed systems for the database, thetemplates are available for use but cannot be maintained.

End of the note.

SAP provides two default templates as described in Enabling the Database for the DataCollection Framework [page 40].

You can access the Template Definition screen by calling the DBA Cockpit and choosingConfiguration Data Collection Framework Template Definition on the Database tab

page of the DBA Cockpit.

From the Template dropdown list, choose the appropriate template for your setup.

The following information is displayed:

Column Description

Data CollectorName of the history data collector

Typically, the name refers to the data that is collected, for example, thedata collector Tables stores table-related metrics in the history tables.

Type

The following data collector types are available:

SAP Data Collection and Preparation (STP)

These history data collectors have their own mechanism fordelta calculation of the different snapshots.

DB2 Event Monitor and Preparation (STP)

A DB2 event monitor is used to store the data in tables.

Cleanup of Message Logs (STP)

The Framework data collector is not a typical data collectortype, but a cleanup job for the messages generated by theabove mentioned data collector types.

Release (min) Minimum database release required for the history data collector

Release (max) Maximum database release supported by the history data collector


44 November 2010

Column Description

Setup

Indicates the setup status:

Green:

The history data collector is set up as intended.

Yellow:

The history data collector is not set up properly. Werecommend that you repair it.

Red:

The history data collector is not set up. Set up the history datacollector according to the assigned template.

Grey:

The history data collector is not set up and the assignedtemplate also marks this data collector to be deactivated.

Collection Interval Schedule of the history data collector

Event Monitor Active

State of the DB2 event monitor:

Green:

The DB2 event monitor is set up as intended.

Yellow:

The DB2 event monitor is not set up properly. We recommendthat you repair the history data collector.

Red:

The DB2 event monitor is not set up. Set up the data collectoraccording to the assigned template.

Grey:

No DB2 event monitor is used by the data collector.

Days Kept in HistoryNumber of days of the sliding history window

The data in the history is deleted after this number of days.


November 2010 45

Creating a New Data Collector TemplateYou can create a new data collector template either by copying an existing template or bygenerating a template that is based on the configuration of an individual system as follows:

Copying an existing template:

1. On the Template Definition screen, choose a template from the Templatedropdown list and choose the Save As New Template pushbutton.

The Save As New Template dialog box appears.

2. Enter a unique name and a description of the new template.

3. Save the template.

Creating a template based on a system configuration:

1. On the Database tab page of the DBA Cockpit, choose ConfigurationData Collection Framework Collector Configuration .

2. On the Collector Configuration screen, choose the Save as New Templatepushbutton.

Note

The Save As New Template pushbutton is only enabled if the respectivesystem configuration fulfills the minimum template requirements of SAP thatare defined by the SAP Default template. This means that every newtemplate must determine a finer granularity or a longer retention time for thehistory data than the SAP Default template does.

End of the note.

3. In the Save As New Template dialog box, enter a unique name and adescription of the new template.

4. Save the template.

Changing a Single History Data Collector in a TemplateThe Setup status of the history data collector must be green.

1. Choose a non-SAP template from the Template dropdown list.

2. On the Configuration tab page in the content detail area, choose the Change Settingspushbutton.

Note

You cannot change an SAP template. Instead, you can create a custom templatebased on the SAP template and change this newly created template.

End of the note.


46 November 2010

3. In the content detail area, enter your changes in the respective fields.

4. Apply your changes.

Note

If you want to discard your changes, choose the Reset Changes pushbutton.

End of the note.

Setting a Default TemplateThe default template is preselected in the template-based setup and in the SAP SolutionManager setup wizard for managed systems.

To change a default template, choose a template from the Template dropdown list andchoose the Set As Default pushbutton.

Note

The current default template is marked with an asterisk (*). If the default template is currentlyselected, the Set As Default pushbutton is disabled.

End of the note.

Deleting a TemplateYou can delete a template by choosing it from the Template dropdown list and choosing theDelete pushbutton.

A list of all systems is displayed that are assigned to this template. If there are entries in thelist, the default template is assigned to these systems before the template is deleted.

Note

You cannot delete SAP templates or the current default template.

If you want to delete the current default template, you first have to unmark it as the default bysetting a different template as the new default.

End of the note.

3.2 Configuring Database ConnectionsThis section describes how you set and maintain technical attributes for remote databaseconnections on the Database Connections screen in the DBA Cockpit. The DBA Cockpit usesthese connections for administration and monitoring or for application programs that usesecondary connections to external databases.

Usually, new connections are created during the system configuration on the SystemConfiguration screen as described in Configuring Systems for Remote Monitoring Manually[page 37] and, therefore, do not have to be created on the Database Connections screen.


November 2010 47

You can also use the Database Connections screen to set up database connections that areused for non-monitoring components, for example, for the access to external data resourcesby BW.

Procedure1. Call the DBA Cockpit and on the System Landscape tab page, choose Database

Connections.

The Database Connections screen appears displaying a list of all available databaseconnection definitions grouped by database platform:

Column Description

Remote DatabaseConnection

Name of the database connection

Note

This is a unique name that you can freely choose.

End of the note.

DB Name Name of the database

DB Host Name of the database host

DB Schema Name of the database schema to be monitored

User Name Name of the connect user

Permanent Specifies whether the connect user must be permanentlyavailable

Max. Connections Maximum allowed number of open connections

Opt. Connections Optimal number of connections

By default, the database connections that are defined in the local system aredisplayed.

2. To add a database connection, choose the Add pushbutton.

The Add Connection Entry dialog box appears.

3. In the Add Connection Entry dialog box, enter the following:

o In the Connection Name field, specify the name of the connection.

Note

This name is a unique ID that you can choose freely except for names thatare reserved by SAP for generated connections. These can be, for example,administrator connections or connections that are used by systems from thesystem landscape directory (SLD).

End of the note.


48 November 2010

o In the Database System field, select the name of the database platform fromthe dropdown list.

o In the Connection Maximum field, enter an appropriate value. This valuelimits the number of database connections that are currently held by the SAPsystem. The SAP system does not let you exceed this limit.

o In the Connection Optimum field, enter an appropriate value. This value is amore flexible limit that can be exceeded.

o If you want the connection to be mandatory for the SAP system, select thePermanent checkbox. This parameter defines the availability of the databaseconnection. It is then handled in the same way as the local defaultconnection, that is, if this database connection is not available for a workprocess, the work process of the SAP system cannot run.

Caution

You should set this parameter only if the connection is absolutely required torun your SAP system.

End of the caution.

o In the User Name field, enter the name of the connect user. Make sure thatyou choose a user with the appropriate authorizations. For more information,see Maintenance Actions in the DBA Cockpit [page 15].

o In the Password field, enter a password for the connect user and confirm it inthe appropriate field.

o In the parameter table, specify the following additional database-specificparameter values:

Attribute Description

DatabaseName Name of the database

Service Name

Name or number of the service

This value corresponds to the parameter SVCENAME of the databasemanager configuration (DBM) of the remote database.

DatabaseHost Name of the remote database server

SchemaName

Name of the schema to be monitored

Note

If you omit this field, the name of the SAP connect user is used asschema.

End of the note.

4. To save your entries, choose the Add pushbutton.


November 2010 49

5. To change a database connection, expand the respective database platform in theRemote Database Connection column, select a connection, and choose the Changepushbutton.

The Change Connection Entry dialog box appears.

6. Enter your changes in the appropriate fields and choose Save.

7. To check if you have entered the correct user and password information as well asthe correct technical connection data, you can test a database connection. To do so,select a connection and choose the Test pushbutton.

The test result is displayed in the Connection Test Protocol in the content detail area.

8. To delete a connection, select a connection and choose the Delete pushbutton.

Caution

If the selected database connection is still used by a system that is registered in theDBA Cockpit, you cannot delete it.

End of the caution.

3.3 Configuring Systems for Remote MonitoringUsing the System Landscape Directory (SLD)The system landscape directory (SLD) contains data from all database systems that areavailable in your system landscape. You can use this data to set up the system configurationin the DBA Cockpit instead of setting it up manually or using SAP Solution Manager.

When you set up the DBA Cockpit for the first time, you use this procedure to import theappropriate data from the SLD. During production operation, you use the procedure tosynchronize the data between the SLD and the DBA Cockpit periodically.

Note

We recommend that you only use the SLD for the setup of your system landscape if SAPSolution Manager is not available.

End of the note.

Procedure1. To import database connection data from the SLD, call the DBA Cockpit.

2. On the System Landscape tab page, choose SLD System Import.

The SLD System Import screen appears. Depending on the system landscape, oneor more of the following nodes are displayed:

o New Database Systems in the SLD

All database systems that are registered in the SLD and that so far havebeen unknown to the DBA Cockpit are displayed.


50 November 2010

o Changed Systems From Earlier SLD Imports

All database systems for which the main data differs between the SLD andthe DBA Cockpit are displayed.

o Systems No Longer Registered in the SLD

All systems that were originally imported from the SLD into the DBA Cockpitbut that are no longer registered in the SLD are displayed.

o Systems Identical in the SLD and in the DBA Cockpit

All systems that are registered in the SLD and that are identical in the DBACockpit are displayed.

o Unsupported Database Systems in the SLD

All database systems that are registered in the SLD but not supported by theDBA Cockpit are displayed.

Note

Each database system is described as follows:

<Name (system ID) of the database system> on <maindatabase host> ( <database platform> )

End of the note.

3. To import database system data, choose the Change pushbutton.

The actions allowed for each database system are displayed in the second column ofthe tree.

4. Select the actions that you want to execute for the selected database systems andchoose the Import pushbutton. By default, only the import of new database systemsis selected.

The selected actions are executed. A short message for each executed action isdisplayed in the content detail area.

Note

Connection data that is retrieved from the SLD might not be complete for one of thefollowing reasons:

o Depending on the data provided by a system to the SLD, some connectiondata can be incomplete.

o User or password data is not available via SLD.

When you establish the connection to an imported system for the first time, the DBACockpit checks the completeness of the configured system. This means that you areprompted for user, password, and connection information, if necessary. If additionalconnection information is required, enter the required data as described inConfiguring Database Connections [page 46].

End of the note.


November 2010 51

3.4 Central CalendarThe Central Calendar is part of the DBA Cockpit in the SAP system. It gives you a singlepoint from which to manage database administration (DBA) actions in an integrated SAPenvironment. The actions available differ according to the database platform but the methodof use is the same. Examples of actions are backups, database system checks, and so on.

Note

The Central Calendar is only for viewing DBA actions by system. However, you can easilyswitch to the DBA Planning Calendar for any SAP system registered in the DBA Cockpit toplan – that is, schedule, change, delete, or execute – DBA actions.

End of the note.

The Central Calendar gives you a single point from which to manage:

Databases of different types and versions on remote SAP systems

Databases for different versions of the SAP system

Databases of non-ABAP SAP systems

IntegrationThe Central Calendar runs with all database platforms delivered as a standard part of theSAP system and supported by SAP (except DB2 for i5/OS, which has good equivalent tools).

Features

You can manage in real time systems directly administered from the system wherethe DBA Cockpit is running as well as remote systems, including non-ABAP systems.

You can quickly check the color-coded status for each system to see if actions haveexecuted successfully.

You can quickly check the number of actions and number of actions with the higheststatus severity for each system, as shown in the following example:

Example

The entry for February 2007 in the cell for Thursday February, 08 is:

3 FUD 2

On system FUD for Thursday 8th January 2007 (in the past), there were 3 actionsplanned, 2 of which had the highest status severity. For example, the highest statusseverity might be Warning, in which case the entry is displayed with a yellowbackground.

End of the example.


52 November 2010

Activities1. On the system where you normally run the DBA Cockpit, you plan a regular job in the

DBA Planning Calendar to update the results from remote systems using the actionCentral Calendar Log Collector. For example, you plan this job to run daily at 06:00.

2. You define the systems you want to monitor in the DBA Cockpit by setting the flagCollect Central Planning Calendar Data for each system.

3. You regularly check the results using the Central Calendar.

4. If you need to schedule, change, delete, or execute actions, you switch to the DBAPlanning Calendar.

For more information, see Using the Central Calendar.

3.4.1 Using the Central CalendarYou can use the Central Calendar in the DBA Cockpit to view actions on all the databases ofyour SAP systems.

Prerequisites

You have defined the systems to be displayed in the Central Calendar by selectingthe required system on the System Configuration screen on the System Landscapetab page of the DBA Cockpit and selecting the Collect Central Planning CalendarData checkbox under Collector Options in the System Configuration Details area.

For more information, see Configuring Systems for Remote Monitoring Using RemoteDatabase Connections.

In an ABAP system, make sure that you schedule the jobs for the remote database inthe central monitoring system. Jobs that have been scheduled in the remote systemare not displayed.

In the DBA Planning Calendar of the DBA Cockpit where you call the CentralCalendar, you have planned the action Central Calendar Log Collector to runregularly. This collects information from the defined remote systems for display in theCentral Calendar.

For more information, see Setting Up the DBA Planning Calendar.

Procedure1. Start the Central Calendar by choosing Central Calendar on the System Landscape

tab page of the DBA Cockpit. The Central Calendar is displayed. If you have alreadyrun or planned actions, you see entries by day, one for each system, which provide asummary of the scheduled jobs.


November 2010 53

The following is an example of entries for Thursday February, 08 affecting twosystems, FUD and FIB:

Example

3 FUD 2

4 FIB 1

On system FUD for Thursday, February 8th, there were three actions planned, two ofwhich had the highest status severity. For example, the highest status severity forFUD might be Finished with warning, in which case the entry for FUD is displayedwith a yellow background. This means that two actions ended with a warning.

On system FIB for the same day, there were four actions planned, one of whichended with the highest severity. For example, the highest severity for FIB might beFinished with error, in which case the entry for FIB is displayed with a redbackground. This means that one action ended with an error.

The following table shows the color-coded statuses in the Central Calendar, whichyou can also see by choosing the Legend pushbutton:

Color Status

Light blue Planned

Dark blue Running

Green Finished successfully

Yellow Finished with warning

Red Finished with error

Dark yellow No longer available

Dark red Scheduling failed

End of the example.

2. For a summary of the actions for a day, click the relevant day header.

A summary of the actions and the status for each system on the day you selected aredisplayed in the Details area, as in the following example:

System Total No longeravailable Scheduled Running Finished Warning Error Overdue Not yet

available

FUD 3 1 2

FIB 4 3 1


54 November 2010

3. To obtain new statistics of the scheduled jobs for all systems, choose the Refresh inthe Background pushbutton.

4. In the Schedule Refresh dialog box, you can choose between the following options:

Option Description

Run in Dialog Refresh runs in dialog mode, which can take a long time.Therefore, we usually do not recommend this option.

Start Immediately in theBackground Refresh runs immediately as a background job

Schedule on <date> at<time>

Refresh runs in the background on the date and at the time thatyou specify

Recommendation

We recommend that you schedule the action Central Calendar Log Collector torun regularly as described above in Prerequisites.

5. To refresh the display with the newly gathered statistics of the previous step, choosethe Refresh pushbutton.

6. Optional step:

In the Selection area, you can customize the calendar display as follows:

o Specify dates or time periods to be displayed

o Specify a factory calendar

Holidays are displayed in the same background color as weekend days. Thisdoes not restrict the planning of actions in the DBA Planning Calendar.

4 Performance

November 2010 55

4 PerformanceThe following sections provide information about the main task areas that are available underPerformance on the Database tab page of the DBA Cockpit:

Performance Warehouse

Time Spent Analysis

Workload Statistics

Snapshots

System Resources

Critical Activities

Utilities

History

4.1 Performance: Performance WarehouseYou can analyze performance data of your database system using the PerformanceWarehouse. To access the Performance Warehouse, call the DBA Cockpit and choose

Performance Performance Warehouse .

The following content areas are available in the Performance Warehouse:

Reporting

By default, the Reporting content area is displayed.

Configuration

PrerequisitesAn SAP Solution Manager system with Solution Manager Diagnostics (SMD) enabled isrequired.

IntegrationThe Performance Warehouse is part of the DBA Cockpit.

FeaturesIn the Performance Warehouse, all relevant performance indicators that are collected by theDBA Cockpit are stored in an SAP NetWeaver Business Warehouse system. This SAPNetWeaver BW system is used by the Solution Manager Diagnostics (SMD) back-end of anSAP Solution Manager system. SMD already uses this SAP NetWeaver BW to storeworkload data of SAP applications. To configure the extraction of data into the SMD BI, youuse the SMD Setup Wizard.

4 Performance

56 November 2010

Based on this architecture, the DBA Cockpit uses SAP NetWeaver BW technology to providereports for performance analysis, which you can customize according to your needs. Allcollected data has a time dimension, so you can analyze the database performance for anypoint in time or over a specified time frame.

Almost all reports are displayed as a chart to visualize the key performance indicators (KPIs).In addition, there is also a detailed table view. To navigate within these reports, you can usethe SAP NetWeaver BW drilldown feature. Violations to performance thresholds arehighlighted based on predefined BW exceptions to make you immediately aware ofperformance issues.

By default, the Performance Warehouse is delivered with predefined content that you can useto create your own reports according to your needs.

More Information

Performance Warehouse: Reporting

Performance Warehouse: Configuration

4.1.1 Performance Warehouse: ReportingYou use the data provided on the Reporting screen to analyze database performanceproblems in the present or the past. To access the Reporting screen of the PerformanceWarehouse, call the DBA Cockpit and choose Performance Performance Warehouse

Reporting on the Database tab page of the DBA Cockpit.

Specifying the Time FrameTo display detailed reports, you first have to specify the time frame for which you want toanalyze data by defining the following:

Granularity

You can choose between Hour, Day, or Month. Depending on your selection, thevalues for your time frame might change.

Time Frame

If you choose Custom Selection from the dropdown list, you can manually enter thestarting and ending time for your analysis. To activate your custom selection, chooseApply Filter. For any other selection from the dropdown list, the reports areautomatically refreshed.

The reports are categorized and for each category there is one tab page. On every tab page,you find a button row for the reports. Every pushbutton in the button row represents a specificview on the database performance, for example, I/O, Prefetcher, Sort Heap, and so on,

4 Performance

November 2010 57

Displaying a ReportTo display a report, choose the appropriate view pushbutton on the respective tab page.

Note

The availability of the tab pages and of the pushbuttons on each tab page can varydepending on the selected system. Some reports are only available if special databasefeatures are enabled.

End of the note.

The reports consist of two sections:

In the upper section, a chart is displayed to visualize the key performance indicators.The chart provides a subset of the key columns from the detail table view.

Note

The chart display is optional and not available for all available views.

End of the note.

In the lower section, a detailed table view is available.

You can drill down your reports by either using the context menu of a column header in theDetail: <Category – View> screen area or by specifying the respective value using thepushbuttons in the Detail: Navigation screen area. Here, you can also add and removecolumns or key figures, or you can set filters on columns.

In addition, there are predefined exceptions (for example, Chart: Exceptions or Details:Exceptions) for almost all reports on key performance indicators. The used thresholds arebased on Early Watch Alerts and each violation to these thresholds is displayed in red.

Note

If you want to reset a report to its initial state, choose Reset Report in the central systemarea.

End of the note.

4.1.2 Performance Warehouse: ConfigurationYou configure all configuration parameters that are related to the performance warehouse onthe Configuration screen. For example, you can configure the framework, the templates usedfor the reports and the report categories.

The DBA Cockpit uses BI Business Explorer (BEx) Web templates to analyze theperformance data that is stored in the Solution Manager Diagnostics (SMD) BI. You cancreate your own BI BEx Web templates based on this data and integrate new BI BEx Webtemplates into the performance warehouse.

You can access the Configuration screen of the performance warehouse by calling the DBACockpit and choosing Performance -> Performance Warehouse Configuration .

4 Performance

58 November 2010

On the screen Performance Warehouse: Configuration, the following tab pages are available:

Configuration

Web Reports

Report Categories

ConfigurationHere, you can view or modify the configuration parameters of the performance warehouse forthe monitored system. To modify some of these parameters, use the Edit, Save, and Cancelpushbuttons in the toolbar.

Depending on your database platform, the displayed selection of values can vary. Thefollowing parameters are displayed for all database platforms:

Parameter Description

BI Server BI server where the database performance data is located

Managing DBACockpit

This DBA Cockpit is allowed to change any data collectors or performancewarehouse configuration for this database. By default, the DBA Cockpit ofthe Solution Manager system is used for this task.

ReportingTime Zone

The performance data time-stamps are converted to one global time zone forall reports in SMD BI.

Note

The Default checkbox is selected if the default value for your complete landscape is the sameas the one specified for your system.

End of the note.

Web ReportsHere, you can configure the display on the Reporting screen. That is, you can view andmodify the integrated BI BEx Web templates in the tree table. To modify some of theseparameters, use the Edit, Add, and Delete pushbuttons in the toolbar.

The main report categories appear and for each report category, you can view or modify theviews by expanding the appropriate report category. These views appear as pushbuttons onthe respective category tab page on the Reporting screen. To change the sequence within acategory, use the Up or Down pushbuttons.

4 Performance

November 2010 59

To display details about a view, simply select it in the table. The following parameters aredisplayed in the Details for Web Reports area below the table view:


ReportSpecifies the name of the report

This text appears on the view pushbutton on a category tab page.

DescriptionDetailed description for the report

This text appears as a tooltip for the pushbutton of the key indicator ona category tab page.

CategorySpecifies the report category.

Each category is represented on a separate tab page.

Web Report(Default) Technical name of the BI BEx Web templates

Web Report (Day) Technical name of the BI BEx Web templates for granularity Day

Web Report (Month) Technical name of the BI BEx Web templates for granularity Month

Data Providers(Time)

Specifies the data provider of the BI BEx Web templates with a timedimension. The drilldown of the time dimension is changed according tothe selected granularity.

Active If selected, the report is available for performance analysis.

Default If selected, the report is executed as soon as the tab page is selected.

Database Name of database platform

Release (min) Minimum database release for this report

Release (max) Maximum database release for this report

Note

Depending on your database platform, there might be more checkboxes available fordatabase-specific features. If you select these checkboxes, the report is only displayed if thespecific database features have been set up in the monitored database system.

End of the note.

Report CategoriesHere, you can view and modify the categories for BI BEx Web templates of the reports thatare displayed the Reporting screen. To modify some of these parameters, use the Edit, Add,and Delete pushbuttons in the toolbar. To change the sequence of the categories on theReporting screen, use the Up or Down pushbuttons.

4 Performance

60 November 2010

The following parameters are displayed:


Category Name of the category

Description Detailed description for the category

4.2 Performance: Time Spent Analysis Note

The Time Spent Analysis screen is only available if the monitored database is at least DB2V9.7.

End of the note.

You can use the Time Spent Analysis screen as the starting point for performance tuning andto identify time-based problems of your database. The Time Spent Analysis screen providesan aggregated and timeline-based view of the current or past performance situation of yourdatabase. The advantage of time spent monitoring is that you do not only have to rely onstandard database key performance indicators (such as the buffer pool hit-ratio) but you canalso identify how much time is really spent on different kinds of database operations.

You can use time spent monitoring to answer questions such as the following:

How do changes in system performance relate to changes in the total time spent invarious DB2 components or wait situations?

Where is most of the time spent in DB2 so that these areas can be tuned?

What are the most active service classes and members on the database system, andare there any outliers?

To access the Time Spent Analysis screen, call the DBA Cockpit and choose PerformanceTime Spent Analysis on the Database tab page of the DBA Cockpit.

The Time Spent Analysis screen is divided into the following areas:

Selection area

Chart view Time Spent in DB2 by <drill-down criteria>

4 Performance

November 2010 61

Specifying Filter and Drill-Down CriteriaIn the Selection area, you can specify filter and drill-down criteria for the data to be displayedas follows:

Field Description

Source

From the dropdown list, you can choose the source of the data to beanalyzed:

Periodic Data Collection

If you choose this option, the data that has already been collectedby the data collector WLM Statistics is used for the time spentanalysis.

For more information, see Data Collection Framework: CollectorConfiguration [page 248].

Note

The granularity of the data analysis can only be as high as specifiedin the collection interval.

End of the note.

Ad-hoc Data

If you choose this option, real-time monitoring data is collected. Thismeans that specific workload situations can be analyzed in real-time.

To set a time interval for the data collection and the charts to berefreshed, choose an interval from the Refresh Interval dropdownlist.

To start the ad-hoc data collection, choose the Resume pushbutton.

If you want to change the drill-down or filter criteria, you must firststop the current Ad hoc data collection by choosing the Pausepushbutton.

Time Frame You specify the time interval and time frame for which you want data to beanalyzed.

4 Performance

62 November 2010

Type of Display

Aggregate

If you choose the Aggregate option from the dropdown list, a piechart is displayed according to your selected filter and drill-downcriteria.

Timeline

If you choose the Timeline option from the dropdown list, themonitoring data is displayed in a histogram according to your filterand drill-down criteria. You can condense the granularity of the timeinterval from As Collected to Hour, Day, Week, or Month.

Members

Note

You can only filter by members if you are using a distributed databasesystem.

End of the note.

From the dropdown list, you can choose the database member on which youwant to apply the specific workload filter. You can choose all or singlemembers.

If you want to combine multiple members into a group (for example, byphysical host), you can use the Advanced Selection option.

ServiceClass(es)

From the dropdown list, you can choose the service classes that have beenset up on the system. You can choose all or single service classes.

If you want to combine multiple service classes into a group, chooseAdvanced Selection from the dropdown list.

Metric(s)

From the dropdown list, you can choose between the following time-relatedWLM metrics:

All

All known time-related metrics are included

All (Wait Times)

All wait time metrics are selected (W)

All (Processing Times)

All processing times without wait times are selected (P)

Single metrics, for example, (P) Commit Processing Time or (W)Buffer Pool Read Time

For more information, see Monitoring metrics for DB2 workloadmanager in the IBM Information Center.

Advanced Selection:

4 Performance

November 2010 63

When you choose this option, all metrics including their parentmetrics are displayed. You can now select those metrics that arerelevant for your analysis. For example, you select all REORG andRUNSTATS processing times to drill down to specific members ormember groups.

If you choose the Choose Level of Detail link, you can specify one of thefollowing options in the Metrics Hierarchy dialog box:

Total Request Time Only

Aggregates all metrics

Wait vs. Processing vs. Unknown Times

Aggregates metric groups

Detailed Wait and Processing Time

Includes only detailed wait and processing times

Full Details

Includes all time metrics (default)

Note

The metrics are mutually exclusive and are independent of each other. Sinceall metric metadata is retrieved dynamically from the database, theavailability of specific metrics as filter criteria depends on the databaserelease.

End of the note.

Drill-Down

You can drill down into the display by choosing one of the following optionsfrom the dropdown list:

Members

All results are distributed across the different members based on thespecified filter criteria.

Note

You can only drill down by members if you are using a distributeddatabase system.

End of the note.

Metrics

All results are displayed according to the different time-basedmonitoring metric occurrences and their relative values as apercentage of the total request time.

Service Classes

4 Performance

64 November 2010

Based on the specified filter criteria, all results are distributed acrossthe service classes according to their occurrence and their relativepercentage to the total request time.

To avoid the chart becoming overloaded and unclear, the Reduce Display toMost Significant checkbox is by default selected. All metrics, members, andservice classes with insignificantly small values are cumulated to give thevalue of Other Known Times.

Note

Make sure that drill-down and filter criteria are not the same, that is, do notuse, for example, non-aggregated single metrics combined with the option todrill down by metrics.

End of the note.

The Chart ViewAfter applying your filter and drill-down criteria in the Selection area, the relevant time spentanalysis chart is generated.

Depending on the specified display type, either a pie chart or timeline histogram is displayed:

Pie chart

The pie chart is the initial view of any time spent analysis.

All occurrences of metrics or service classes are displayed as well as their relativevalues as a percentage of the total time consumption of the monitored system. Thisview shows the aggregated results of the drill-down dimension for the specified timeframe. The results are displayed clockwise in descending order.

Timeline histogram

The timeline-based chart lets you analyze changes in workload performance for agiven time frame.

This chart type displays the cumulated occurrences of selected time-based metrics,members, or service classes into a histogram that consists of bars that are aligned tothe timeline. The histogram bars are divided according to the time granularity youhave specified in the Selection area.

Displaying Details and Analyzing the ChartsThe analysis of a single pie chart or histogram item can vary due to the drill-down criteria youhave specified (that is, metric vs. member or service class). To analyze a single item of achart, click the item or caption. The relevant details appear in the <metric> Summary areadisplaying all values and occurrences for the selected time frame or time interval as follows:

Percentage of the total time related to the occurrence in the specified time interval ortime frame

Processing times, nominal and worst values per service class or member

Total occurrences for the total time frame or the selected time interval

Line graphs of the absolute and average values

4 Performance

November 2010 65

In the See Also area, you can use links such as the following to directly navigate into areas ofthe DBA Cockpit that might help you analyze the problem:

Configuration Changes

Workload Statistics

Threshold Violations

Previous filter and drill-down criteria are kept if possible.

Customizing the ChartsYou can change the chart type from Stacked Columns to Stacked Area or Lines by choosingthe Chart Type menu button.

To specify whether you want the data to be displayed in absolute or percentage values, youcan use the Values menu button. If you choose the Percentage option, the values aredisplayed in relation to the total request time per time frame or per time interval.

By choosing the Chart Size menu button, you can specify the width and height of the chart tobe displayed. Optionally, you can open a detailed table view by choosing the Toggle TableDisplay pushbutton.

Example ScenariosExample 1

To analyze and identify I/O-related workload on the database, perform the following steps:

1. Set the Metric(s) filter to Advanced Selection and select Direct Read Time, DirectWrite Time, BP Read Time, and BP Write Time.

2. As Type of Display, choose Timeline.

3. As Drill-Down option, choose Service Classes.

4. After applying your selection, you can identify time consumption peaks in thedisplayed charts. To identify the responsible workloads for those peak values, payspecial attention to the nominal total time per service class versus the worst serviceclass in the Summary area.

Example 2

To identify the reason for a general system slowdown, perform the following steps:

1. As Type of Display, choose Timeline, and as Drill-Down option, choose Metrics.

2. In the Members and Service Class(es) fields, choose All and apply your selection.

3. Identify the most significant time metrics in the displayed chart.

4. In the detailed Summary area of those metrics, check for outlier members or serviceclasses to restrict the scope to a smaller group of members or service classes.

4 Performance

66 November 2010

5. For a more detailed analysis of the system slowdown, keep your selection ofmembers and service classes and navigate into other areas of the DBA Cockpit suchas the following:

o Performance SQL Cache

Search for statements with high values for the identified metrics.

o Diagnostics Lock-Wait Events

Analyze lock-wait situations or a switch in data collection.

o Performance Workload Statistics

Analyze statistical metrics for the identified members or service classes.

o Configuration Workload Management Workloads and Service Classes

Check the priority settings of the involved workloads.

More InformationMonitoring metrics for DB2 workload manager in the IBM Information Center at:

https://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.wlm.doc/doc/c0055265.html

4.3 Performance: Workload StatisticsYou can access information about workload statistics by calling the DBA Cockpit andchoosing Performance Workload Statistics on the Database tab page of the DBACockpit.

Note

This screen is only available if the currently monitored database version is at least DB2 V9.5.

End of the note.

On the Workload Statistics screen, basic statistics are displayed that describe the overallbehavior of the database system. This information helps you to:

Understand the type of a system slowdown. For example, most of the queries arerunning slower versus only certain queries are running slower.

Monitor service level agreements (SLAs)

Search for time frames, members, or service classes in which long-running queriesare executed on the database system

Define meaningful workload management thresholds using the high-water markmetrics



4 Performance

November 2010 67

In the Selection area, you can specify the appropriate time frame for which you want data tobe displayed.

Note

In a distributed database system, you can also filter by members and service classes.

End of the note.

After having made your selection using the Apply Selection pushbutton, the Activity Lifetimesand Statistics tab pages are displayed.

Activity LifetimesThe histograms that you can choose from the Histogram Type dropdown list give you a betterunderstanding of your database workload.

The following histogram types are available:

Activity Execution Time Histogram

Displays the history of the histogram for the execution times of all activities that wereexecuted in the selected service classes and members for the selected time frame

The execution time corresponds to the time an activity has spent executing on thecoordinator partition. Execution time does not include the time spent duringinitialization, queuing, or between cursor operations.

Activity Lifetime Histogram

Displays the history of the histogram for the lifetimes of all activities that wereexecuted in the selected service classes and members for the selected time frame

The lifetime corresponds to the total elapse time of an activity, as measured on thecoordinator partition. Lifetime does include the time spent during initialization,queuing, and in between cursor operations.

Activity Queue Time Histogram

Displays the history of the histogram for the queue times of all activities that wereexecuted in the selected service classes and members for the selected time frame

The queue time corresponds to the time an activity has spend in a workloadmanagement (WLM) queue.

The average execution, life, or queue time for all activities is displayed in a dotted line. Thetotal number of activities that have completed, were rejected, or aborted by WLM in theselected time frame is displayed in an additional chart below the histogram chart.

For more information about the histogram types and all other monitoring counters providedhere, see the IBM DB2 Information Center for your database release at:

http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg27009474


4 Performance

68 November 2010

StatisticsThe Statistics tab page provides you with a range of high-watermark and average metricsthat are separated by service class, member, and time. By default, the following informationis displayed:

Column Description

Time from Begin of statistics interval timestamp

Time to End of statistics interval timestamp

Member Member that has captured the statistics

Service Superclass Name of the service superclass for which the statistics werecaptured

Service Subclass Name of the service subclass for which the statistics werecaptured

Coord. Act. Lifetime Top High-water mark in milliseconds for coordinator activity lifetime

Coord. Act. Lifetime Avg. Arithmetic mean of lifetime in milliseconds for coordinatoractivities

UOW Total Time Top High-water mark in milliseconds for unit of work lifetime

Act. Temp. Tablespace Top High-water mark in KB for the temporary tablespace usage of asingle DML activity

Agg. Temp. TablespaceTop

High-water mark in KB for the aggregate temporary tablespaceusage across all DML activities

Activity CPU Time Top High-water mark for processor time used by activities at allnesting levels, in milliseconds

Rows Read Top High-water mark for the number of rows read by activities on allnesting levels

Rows Returned Top High-water mark for the number of rows returned by activities onall nesting levels

For more Information about all available statistics, see the IBM DB2 Information Center foryour database release at:



4 Performance

November 2010 69

4.4 Performance: System ResourcesYou can access information about system resources by calling the DBA Cockpit andchoosing Performance System Resources on the Database tab page of the DBACockpit. The System Resources screen provides you with an overview of all resources thatare available for each of the members of the currently monitored database system.


Column Description

Hostname Name of the host

OS Operating system of the host

Members Members located on this host

CPU Usage (%) Percentage of the current overall CPU usage of the host

CPU Load Short

Short-period CPU load. For example, load samples over the last 5minutes

Note

This information is not available on Windows operating systems.

End of the note.

CPU Load Medium

Medium-period CPU load. For example, load samples over the last10 minutes.

Note


End of the note.

CPU Load Long

Long-period CPU load. For example, load samples over the last 15minutes

Note


End of the note.

CPUs Online Number of CPUs online

Memory Total (MB) Total size of physical memory in MB

Memory Free (MB) Amount of free physical memory in MB

4 Performance

70 November 2010

4.5 Performance: SnapshotsYou can access data on performance snapshots by calling the DBA Cockpit and choosing

Performance Snapshots <snapshot option> on the Database tab page of the DBACockpit.

The following snapshot options are available:

Database

Schemas

Buffer Pools

Tablespaces

Tables

Application

SQL Cache

Note

The layout of these snapshot screens varies depending on the database version.

End of the note.

FeaturesIn the Snapshots task area, monitoring data in both unfiltered and raw format is provided bythe various snapshots. Snapshot data is provided on different levels (for example, database,buffer pools, or SQL statements) and is collected by the database beginning from startup ofthe database instance until the current time. That is, data is accumulated over a long timeperiod and, therefore, cannot reflect short-term decreases in performance or increasing orchanging workloads over a certain time period.

Furthermore, for the interpretation of snapshot data, it is necessary to refer to relatedconfiguration parameters. Configuration parameters, however, do not relate to a certain timeframe either but only describe the current configuration of the database. Especially if yourdatabase is enabled for self-tuning memory management (STMM), there is no way ofcorrelating bad performance data with current storage parameters.

To overcome these problems, you can observe monitoring data over a certain time period bydoing one of the following:

You can explicitly set a starting point for measurements using the Reset and SinceReset pushbuttons that are available for most snapshot options. As a result, a set ofmonitoring data is displayed that is related to the time frame defined by the resetoperation.

In parallel, you can check related configuration parameters for changes by choosingConfiguration Configuration History on the Database tab page of the DBA

Cockpit.

4 Performance

November 2010 71

If the relevant snapshot option supports the evaluation of snapshot data that isperiodically collected by the data collection framework (DCF), you can specify anytime interval for analysis as long as the relevant data is kept in the DCF history.Since the displayed configuration data is also retrieved from the DCF, there is aconsistent, time-related view of both the snapshot and the configuration.

This applies to the following snapshot options:

o Database

o Tables

o SQL Cache

4.5.1 Snapshots: DatabaseYou can access the database snapshot by calling the DBA Cockpit and choosing

Performance Snapshots Database on the Database tab page of the DBA Cockpit.

Depending on the setup of your DBA Cockpit, one of the following snapshots is displayed onthe Database screen:

Enhanced database snapshot with support of the data collection framework (DCF)

Database snapshot without DCF support

For more information about the DCF, see Enabling the Database for the Data CollectionFramework [page 40].

Enhanced Database Snapshot With DCF SupportTo analyze system performance, it is not sufficient to review the key figures provided by thedatabase from startup until the current time. This data has been cumulated over a long timeperiod and, therefore, cannot reflect a short-term degradation of performance or anincreasing or changing workload.

In addition, the interpretation of snapshot data mostly depends on configuration parametersthat do not relate to a certain time frame either but describe only the current configuration ofthe database. Especially, if your database is using self-tuning memory management (STMM),you cannot correlate bad performance data with current storage parameters.

In contrast to the Database snapshot option without DCF support, the database snapshotwith DCF support not only lets you view current global database snapshot data but alsomonitor data that is periodically collected by the DCF.

Note

To monitor data on the enhanced Database screen, you have to make sure that the DCF isset up correctly. If the DCF is not available or wrongly set up, an appropriate warning isdisplayed including a link to the Collector Configuration screen where you can perform therequired steps.

For more information, see Data Collection Framework: Collector Configuration [page 248].

End of the note.

4 Performance

72 November 2010

FeaturesThe enhanced Database screen provides the following:

A selection area where you specify filter criteria for the monitoring data (onlyavailable in a distributed database)

An overview table displaying the retrieved monitoring data with the most importantkey figures that have been aggregated over the selected time period.

A detail view of selected monitoring data of the result list

An option to break down all history data that was collected for the selectedmonitoring data during the specified time frame.

ProcessTo analyze snapshot data, you proceed as follows:

1. You identify the time period where you experienced performance problems, such as,long-running batch jobs, threshold violations detected by workload management, andbad user response time

2. In the Selection area, you specify the appropriate time frame.

Note

If you are using a distributed database system and you want to retrieve a generalsnapshot, you set the member selection to All and you do not drill down by members.To retrieve a more detailed snapshot in a distributed database system, you canfurther drill down the selection by members. If a single member or a subset ofmembers shows deviations compared to other members, you can also restrict themember selection.

End of the note.

3. To refresh the monitoring data, you choose the Apply Selection pushbutton.

The following information is displayed for each partition:

o Number and total size of buffer pools

o Number of data and index logical reads

o Number of data and index physical reads

o Average physical read and write time that is required to read from and writedata into the buffer pool

o Executed SQL statements

o Package cache size

o Package cache quality

4. To display detailed information, you select the appropriate entry that you want toanalyze in the overview table. The detail data is displayed in the content detail areabelow the overview table.

4 Performance

November 2010 73

5. To display detailed history data, you select a line in the overview table and choosethe History pushbutton.

The data is displayed in the History Details content detail area.

6. To isolate the time frame during which the performance problem occurred, you usethe data in the overview table in the History Details content area.

Database Snapshot Without DCF SupportThis Database screen provides a selection of current performance data that is related to eachpartition. You can use the information to identify performance-critical partitions before startinga more detailed analysis of your database.

For each partition of your database system, information about the following performanceindicators is displayed:

Number and total size of buffer pools

Number of data and index logical reads

Number of data and index physical reads

Average physical read and write time that is required to read from and write data intothe buffer pool

Executed SQL statements

Package cache size

Package cache quality

Note

If you choose a line in the overview table of the Database screen, detailed databasesnapshot data is retrieved and displayed in the content detail area below the overview table.

End of the note.

4.5.1.1 Displaying Detail Database Snapshot Data1. On the Database screen, choose a line in the overview table of the Database screen.

Depending on the setup, data has been collected as follows:

o Without DCF support, data has been collected since the database wasstarted. The configuration values show the current configuration.

Note

The data displayed is only meaningful if the database has been running forsome time. The longer the database has been running, the more useful thecollected data is.

End of the note.

4 Performance

74 November 2010

o With DCF support, the displayed monitoring values refer to the time framethat was specified in the Selection area. The configuration values show theconfiguration that was valid during the specified time frame. All values areretrieved from the history that is stored by DCF.

For more information about DCF support, see Enabling the Database for the DataCollection Framework [page 40].

2. In the content detail area of the Database screen, choose the appropriate tab page toget an overview of the following critical database performance indicators:

o Buffer Pool

o Cache

o Asynchronous I/O

o Direct I/O

o Real-Time Statistics

o Locks and Deadlocks

o Logging

o Calls

o Sorts

o XML Storage

The data displayed on these tab pages is described in more detail in the followingsections.

4.5.1.1.1 Database Details: Buffer PoolTo display detailed information about the buffer pool activity, choose the Buffer Pool tab pagein the content detail area of either the Database or the enhanced Database screen.


Field Description

Buffer Pools

Number Number of buffer pools

Total Size Total size in KB of all buffer pools

Buffer Quality

4 Performance

November 2010 75

Overall Buffer Quality

Percentage at which the data is read from the buffer pool, ratherthan directly from the hard disk

This is calculated using the following formula:

(logical reads - physical reads) / (logical reads) * 100

Data Hit Ratio Percentage at which data (without index data) is read from thebuffer pool, rather than directly from the hard disk

Index Hit Ratio Frequency as a percentage at which index data is read from thebuffer pool, rather than directly from the hard disk

No Victim Buffers Number of times an agent did not have a preselected victim bufferavailable

Average Time

Physical Reads Average time in milliseconds required to read data from disk intothe buffer pool

Physical Writes Average time in milliseconds required to write data from the bufferpool to disk

Data

Logical Reads Number of read accesses to data in the buffer pool

Physical Reads

Number of read accesses to data on disk (I/O)

This value includes the number of physical reads that wereperformed synchronously (by the database manager agents) andasynchronously (by the I/O servers).

Physical Writes

Number of write accesses to data on disk (I/O)

This value includes the number of physical writes that wereperformed synchronously (by the database manager agents) andasynchronously (by the I/O cleaners).

Synchronous Reads Number of read accesses to data on disk (by agents)

Synchronous Writes Number of write accesses to data on disk (by agents)

Temporary Logical Reads Number of logical read requests that required I/O to get datapages into the temporary tablespace

Temporary PhysicalReads

Number of physical read requests that required I/O to get datapages into the temporary tablespace

4 Performance

76 November 2010

Index

Logical Reads Number of read accesses to index data in the buffer pool

Physical Reads

Number of read accesses to index data on disk (I/O)

Since index data is read only by the database manager agents,this value includes the number of synchronously read indexpages.

Physical Writes

Number of write accesses to index data on disk (I/O)


Synchronous Reads Number of read accesses to index data on disk (by agents)

Synchronous Writes Number of write accesses to index data on disk (by agents)

Temporary Logical Reads Number of logical read requests that required I/O to get indexpages into the temporary tablespace


Number of physical read requests that required I/O to get indexpages into the temporary tablespace

Note

Data is read or written in pages. A page can be 4 KB, 8 KB, 16 KB, or 32 KB in size.

Unless otherwise specified, no distinction is made between synchronous and asynchronousaccesses.

End of the note.

4.5.1.1.2 Database Details: CacheTo display detailed information about the cache, choose the Cache tab page in the contentdetail area of either the Database or the enhanced Database screen.


Field Description

Catalog Cache

Size

Maximum allowed size in KB for the catalog cache

The catalog cache is accessed each time a transaction accesses atable, view, or alias. The cache is allocated dynamically from the heap.

The maximum allowed size is determined by database configurationparameter CATALOGCACHE_SZ.

4 Performance

November 2010 77

Field Description

Quality

Percentage at which the data is read from the catalog cache, rather thandirectly from the hard disk


(catalog cache lookups - catalog cache inserts) / catalog cache lookups* 100

Lookups Number of times that the catalog cache was referenced to obtain tabledescriptor information

Inserts Number of times that the system tried to insert table descriptorinformation into the catalog cache

Overflows Number of times that an insert into the catalog cache failed due to thecatalog cache being full

High-Water Mark Largest size reached by package cache

Package Cache

SizeMaximum allowed size in KB for the package cache

The package cache contains access plans. The maximum allowed sizeis determined by database configuration parameter PCKCACHESZ.

Quality

Indicates percentage at which the data is read from the package cache,rather than directly from the hard disk


(package cache lookups - package cache inserts) / package cachelookups *100

Lookups Number of times an application looked for a section in the packagecache

Inserts Total number of times that an access plan was not available for use andhad to be loaded into the package cache

Overflows Number of times that the package cache overflowed the bounds of itsallocated memory

High-Water Mark Largest size reached by the package cache

4 Performance

78 November 2010

4.5.1.1.3 Database Details: Asynchronous I/OTo display detailed information about I/O servers and I/O cleaners, choose the AsynchronousI/O tab page in the content detail area of either the Database or the enhanced Databasescreen.


Field Description

I/O

Number of I/O Servers Number of I/O servers that read data asynchronously from thehard disk into the buffer pool

Number of I/O Cleaners Number of I/O cleaners that write data asynchronously from thebuffer pool to the hard disk

Average Time

Asynchronous PhysicalReads

Average time in milliseconds required by the I/O servers to reada page from disk and write it to the buffer pool

Asynchronous PhysicalWrites

Average time in milliseconds required by the I/O cleaners toread a page from the buffer pool and write it to the hard disk

Data


Number of data pages that were read asynchronously from diskand written to the buffer pool by the I/O servers (prefetch)


Number of data pages that were written asynchronously frombuffer pool to disk (I/O cleaners)

Asynchronous ReadRequests Number of asynchronous data read requests

Index


Number of index pages that were read asynchronously from diskand written to the buffer pool by the I/O servers (prefetch)


Number of index pages that were written asynchronously frombuffer pool to disk (I/O cleaners)

Asynchronous ReadRequests Number of asynchronous index read requests

Note


End of the note.

4 Performance

November 2010 79

4.5.1.1.4 Database Details: Direct I/OTo display detailed information about direct I/O, choose the Direct I/O tab page in the contentdetail area of either the Database or the Database (Enhanced) screen.


Field Description

Average Time

Direct Reads Average time in milliseconds required to read directly from disk

Direct Writes Average time in milliseconds required to write directly to disk

I/O

Direct Reads Read accesses from disk that do not use the buffer pool (LONGVARCHAR fields, backup)

Direct Writes Write accesses to disk that do not use the buffer pool (LONGVARCHAR fields, restore, load)

Average I/O per Request

Direct Reads Average number of requests to read directly from disk

Direct Writes Average number of requests to write directly to disk

4.5.1.1.5 Database Details: Real-Time StatisticsTo display detailed information about real-time statistics, choose the Real-Time Statistics tabpage in the content detail area of either the Database or the enhanced Database screen.


Field Description

Size of Statistics Cache Size of statistics cache in bytes

Number of AsynchronouslyCollected Statistics

Total number of successful asynchronous statisticscollection activities

Number of Statistics CollectionsDuring Query Compilation

Total number of statistics collection activities for creatingstatistics by the system without table or index scan duringquery compilation

Time Spent During QueryCompilation

Total time spent on creating statistics by system withouttable or index scan during query compilation in milliseconds

Number of SynchronouslyCollected Statistics

Total number of synchronous statistics collection activitiesduring query compilation

4 Performance

80 November 2010

Field Description

Time Spent on SynchronousStatistics Collection Activities

Total time spent on synchronous statistics collectionactivities in milliseconds

4.5.1.1.6 Database Details: Locks and DeadlocksTo display detailed information about locks and deadlocks, choose the Locks and Deadlockstab page in the content detail area of either the Database or the enhanced Database screen.


Field Description

Lock List

Size

Maximum length of the list (database configuration parameterLOCKLIST)

Database locks are managed in a list. The lock list is allocateddynamically.

In Use Current size of the lock list

Lock Waits

Total Total number of times that applications or connections waited forlocks

Time Waited Total amount of elapsed time in milliseconds that applicationswaited for a lock to be granted

Average Time Waited Average time in milliseconds waited for a lock

Escalations

Lock Escalations

Number of times that locks have been escalated from severalrow locks to a table lock

If the maximum allowed length of the lock list is reached, rowlocks are converted to table locks to save space in the lock list.This process is called lock escalations

Exclusive Lock Escalations

Number of times that locks have been escalated from severalrow locks to one exclusive table lock, or the number of times anexclusive lock on a row caused the table lock to become anexclusive lock

Exclusive locks are important to track since they can impact theconcurrency of your data because other applications cannot

4 Performance

November 2010 81

Field Description

access data held by an exclusive lock.

Locks

Locks Currently Held Total number of locks currently held by the applications

Deadlocks Detected

Number of deadlocks that have occurred

Deadlock situations are recognized and resolved automaticallyby the database. The database configuration parameter lockescalations determines when a lock wait situation is resolved.

Lock Timeouts

Number of times that a request to lock an object timed outinstead of being granted

The database configuration parameter lock escalationsdetermines when a lock wait situation is resolved.

4.5.1.1.7 Database Details: LoggingTo display detailed information about logging, choose the Logging tab page in the contentdetail area of either the Database or the enhanced Database screen.


Field Description

Log Files

PrimaryNumber of primary log files

The database configuration parameter LOGPRIMARY determines thisvalue.

Secondary

Number of secondary log files

The database configuration parameter LOGSECOND determines thisvalue.

SizeNumber of pages in each log file

The database configuration parameter LOGFILSIZ determines thisvalue. Each page has 4 KB.

4 Performance

82 November 2010

Total Log

Available to Database Amount of primary log space in bytes in the database that is notbeing used by uncommitted transactions

Used by Database Total amount of primary log space in bytes currently used in thedatabase

Maximum Space Used Maximum amount of primary log space used in bytes

Node with LeastAvailable Space

Node with the least amount of available log space in bytes

Note

This field is only displayed for global snapshots over all partitions.

End of the note.

Application with OldestTransaction

Application ID (that corresponds to the agent_id value from theapplication snapshot) of the application that has the oldesttransaction

Secondary Log

Logs CurrentlyAllocated

Total number of secondary log files that are currently being used forthe database

Maximum Space Used Maximum amount of secondary log space used in bytes

Log Pages

Read Number of log pages read from disk

Written Number of log pages written to disk

Log BufferConsumption

LSN Gap Percentage of log space held by dirty pages in relation to log spacespecified by parameter SOFTMAX

Restart RangePercentage of log space held that will have to be redone for crashrecovery pages in relation to log space specified by parameterSOFTMAX

4 Performance

November 2010 83

Log Buffer Quality

Log Buffer Hit Ratio Ratio of log data read from the buffer in relation to log data readfrom disk

Log Buffer Overflows

Number of times that agents have to wait for log data to write to diskwhile copying log records into the log buffer

This value is incremented per agent per incident. For example, if twoagents attempt to copy log data while the buffer is full, then thisvalue is incremented by two.

Log Buffer I/O

Average WriteTime/Page

Average time per page in microseconds required to write log data todisk

Average Write Time/IO Average time per I/O in microseconds required to write log data todisk

Average ReadTime/Page

Average time per page in microseconds required to read log datafrom disk

Average Read Time/IO Average time per I/O in microseconds required to read log data fromdisk

4.5.1.1.8 Database Details: CallsTo display detailed information about calls, choose the Calls tab page in the content detailarea of either the Database or the enhanced Database screen.


Field Description

Rows

Read Number of data records that were read

Selected Number of data records that were selected

Deleted Number of data records that were deleted

Inserted Number of data records that were inserted

Updated Number of data records that were updated

4 Performance

84 November 2010

Rows Read / RowsProcessed

Ratio of rows read from the base table compared to rowsprocessed, which can be either rows returned to the application(SELECT statements) or rows written (UPDATE, INSERT,DELETE statements)

A value of 1 indicates an optimal access to the requested data.High values indicate statements with inefficient access.

Note

End of the note.

This metric is only available if your database is DB2 V9.5 forLinux, UNIX, and Windows Fix Pack 1 or higher.

BP Gets / Rows Processed

Average number of pages read from the buffer pool per rowsprocessed, which can be either rows returned to the application(SELECT statements) or rows written (UPDATE, INSERT,DELETE statements)

Note

This metric is only available if your database is DB2 V9.5 forLinux, UNIX, and Windows Fix Pack 1 or higher.

End of the note.

Statements Executed

SELECT SQL Number of SELECT statements that were executed

UPDATE/INSERT/DELETE Number of UPDATE, INSERT, and DELETE statements thatwere executed

DDLNumber of Data Definition Language (DDL) statements thatwere executed, for example, CREATE TABLE, CREATE VIEW,ALTER TABLE, and DROP INDEX

Elapsed Time (sec) Sum of the host execution times in seconds for all thestatements that were executed

Elapsed Time (microsec) Remaining part of the above elapsed time in microseconds

Statements Attempted

COMMITs Number of COMMIT statements that have been attempted

RollbacksNumber of ROLLBACK statements that have been attempted

Automatic rollbacks caused by error situations or deadlocks arenot included.

4 Performance

November 2010 85

Dynamic SQL Number of dynamic SQL statements attempted

Static SQL Number of static SQL statements attempted

Failed SQL Number of attempted SQL statements that failed

Hash Joins

Total Total number of hash joins executed

Total Hash Loops Total number of times that a single partition of a hash join waslarger that the available sort heap space

Overflows Number of times that hash join data exceeded the available sortheap space

Small Overflows Number of times that hash join data exceeded the available sortheap space by less than 10%

Post Threshold

Total number of hash joins that were throttled back by the sortmemory throttling algorithm

A throttled hash join is a hash join that was granted less memorythan requested by the sort memory manager. A hash join isthrottled back when the memory allocation from the shared sortheap is close to the limit set by database configurationparameter sheapthres_shr.

This throttling significantly reduces the number of overflows overthesheapthres_shr limit in a system that is not properlyconfigured. The data reported in this element only reflects hashjoins using memory allocated from the shared sort heap.

4.5.1.1.9 Database Details: SortsTo display detailed information about sorts, choose the Sorts tab page in the content detailarea of either the Database or the enhanced Database screen.


Field Description

Sort Heap

Total Size Amount of memory in KB available for each sort as defined in thedatabase configuration parameter SORTHEAP (in pages)

Allocated Total number of allocated space of sort heap space for all sorts at thelevel chosen and at the time the snapshot was taken

4 Performance

86 November 2010

Field Description

Sort Time

Total Total time in milliseconds required for all sort processes

Average Average sort time in milliseconds

Sorts

Total Sorts Total number of sorts that have been executed

Sort Overflows If the storage area allocated for sorting is not large enough, a sortoverflow occurs. The hard disk is then used temporarily.

Active Sorts Number of sorts in the database that currently have a sort heap allocated

Post ThresholdSorts

Total number of sorts that were throttled back by the sort memorythrottling algorithm. A throttled sort is a sort that was granted lessmemory than requested by the sort memory manager. A sort is throttledback when the memory allocation for sorts is close to the limit set bydatabase configuration parameter sheapthres_shr. This throttlingsignificantly reduces the number of overflows over sheapthres_shrlimit in a system that is not properly configured.

The data reported in this element only reflects sorts using memoryallocated from the shared sort heap.

4.5.1.1.10 Database Details: XML StorageTo display detail information about XML storage, choose the XML Storage tab page in thecontent detail area of either the Database or the enhanced Database screen.


Field Description

Pool Data

Logical ReadsNumber of data pages for XML storage objects (XDAs) that have beenrequested from the buffer pool (logical reads) for regular and largetablespaces

Physical ReadsNumber of data pages for XML storage objects (XDAs) that have beenread from the tablespace containers (physical reads) for regular andlarge tablespaces

Write Accesses Number of times a buffer pool data page for an XML storage object(XDA) was physically written to disk

4 Performance

November 2010 87

Field Description

Temporary Data

Logical ReadsNumber of pages for XML storage objects (XDA) that have beenrequested from the buffer pool (logical reads) for temporarytablespaces.

Physical ReadsNumber of pages for XML storage objects that have been (XDA) readfrom the tablespace containers (physical reads) for temporarytablespaces

Asynchronous I/O

Physical ReadsNumber of XML storage object (XDA) data pages that have been readin from the tablespace containers (physical reads) by asynchronousengine dispatchable units (EDUs) for all types of tablespaces.

Physical Writes

Number of times a buffer pool data page for an XML storage object(XDA) was physically written to disk by either an asynchronous pagecleaner, or a prefetcher

A prefetcher may have written dirty pages to disk to create space forthe pages being prefetched.

Read Requests Number of asynchronous read requests for XML storage object (XDA)data

4.5.2 Snapshots: SchemasThe Schemas screen provides a selection of performance data that is related to thesecomponents if more than one SAP component is installed within the same database. You canuse the information displayed to identify performance-critical components and the workloaddistribution among the components.

For each component (and partition if you are using a multi partition database), the followinginformation is displayed:

Column Description

User Name of connect user to identify the component

Partition Number of the partition (only displayed in a multi-partition database)

SAP Component Indicates whether the connect user is related to an SAP component oranother user that is just connected to the database

Data Logical Reads Number of read accesses to data in the buffer pool

4 Performance

88 November 2010

Data Logical Reads (%) Percentage of logical data read accesses for the component (andpartition if you are using a multi-partition database)

Index Logical Reads Number of read accesses to index data in the buffer pool

Index Logical Reads (%) Percentage of index logical data read accesses for the component(and partition if you are using a multi partition database)

Data Physical Reads


The value includes the number of physical reads that wereperformed synchronously (by the database manager agents) andasynchronously (by the I/O servers).

Data Physical Reads (%) Percentage of physical data read accesses for the component(and partition if you are using a multi partition database)

Index Physical Reads


Since index data is only read by the database manager agents,this value includes the number of synchronously read indexpages.

Index Physical Reads (%) Percentage of index physical read accesses for the component(and partition if you are using a multi partition database)

4.5.3 Snapshots: Buffer PoolsThe Buffer Pool screen provides an overview of the following important key indicators of thebuffer pool activity of your database and enables you to compare these key indicators:

Buffer Pool Name

Buffer Pool Size (KB)

Automatic Size (Yes or No)

Buffer Quality (%)

Data Logical Reads

Data Physical Reads

Index Logical Reads


Temporary Data Logical Reads

Temporary Data Physical Reads

Temporary Index Logical Reads

Temporary Index Physical Reads

4 Performance

November 2010 89

You can display more detailed information by selecting a line in the overview table of theBuffer Pool screen. The following tab pages are displayed in the content detail area:

Buffer Pool

Asynchronous I/O

Direct I/O

XML Storage

4.5.3.1 Buffer Pools Details: Buffer PoolTo display detailed information about the buffer pool activity for your selected buffer pool(s),choose the Buffer Pool tab page in the content detail area of the Buffer Pool screen.


Field Description

Buffer Pool

Name Name of the buffer pool

Current Size

Size of the buffer pool in KB and in pages

Caution

If Automatic is selected, the buffer pool is automatically tuned (ifDB2's Self-Tuning Memory Management is activated).

End of the caution.

New Size Size of the buffer pool in pages after a database restart

Pages Left to Remove Number of pages that are still to be removed

Tablespace UseCount Number of tablespaces that belong to this buffer pool

Buffer Quality


Percentage at which the data is read from the buffer pool, rather thandirectly from the hard disk



Data Hit Ratio Percentage at which only data (without index data) is read from thebuffer pool, rather than directly from the hard disk

4 Performance

90 November 2010

Index Hit Ratio Percentage at which index data is read from the buffer pool, ratherthan directly from the hard disk

Average Time

Physical Reads Average time in milliseconds required to read data from disk into thebuffer pool


Data


Physical Reads


This value includes the number of physical reads that wereperformed synchronously (by the database manager agents) andasynchronously (by the I/O servers).

Physical Writes





Temporary LogicalReads

Number of logical read requests that required I/O to get data pagesinto the temporary tablespace


Number of physical read requests that required I/O to get data pagesinto the temporary tablespace

Index


Physical ReadsNumber of read accesses to index data on disk (I/O)

Since index data is read only by the database manager agents, thisvalue includes the number of synchronously read index pages.

Physical Writes



4 Performance

November 2010 91




Number of logical read requests that required I/O to get index pagesinto the temporary tablespace



4.5.3.2 Buffer Pool Details: Asynchronous I/OTo display detailed information about asynchronous I/O for your selected buffer pool(s),choose the Asynchronous I/O tab page in the content detail area of the Buffer Pool screen.


Field Description

Average Time

AsynchronousPhysical Reads

Average time in milliseconds required by the I/O servers to read apage from disk and write it to the buffer pool

AsynchronousPhysical Writes

Average time in milliseconds required by the I/O cleaners to read apage from the buffer pool and write it to the hard disk

Data


Number of data pages that were read asynchronously from disk andwritten to the buffer pool by the I/O servers (prefetch)

AsynchronousPhysical Writes

Number of data pages that were written asynchronously from bufferpool to disk (I/O cleaners)


Index


Number of index pages that were read asynchronously from disk andwritten to the buffer pool by the I/O servers (prefetch)

4 Performance

92 November 2010


Number of index pages that were written asynchronously frombuffer pool to disk (I/O cleaners)


Note


End of the note.

4.5.3.3 Buffer Pool Details: Direct I/OTo display detailed information about direct I/O for your selected buffer pools, choose theDirect I/O tab page in the content detail area of the Buffer Pool screen.


Field Description

Average Time



I/O



Average I/O per Request



4 Performance

November 2010 93

4.5.3.4 Buffer Pool Details: XML StorageTo display detailed information about XML storage for your selected buffer pools, choose theXML Storage tab page in the content detail area of the Buffer Pool screen.


Field Description

Pool Data

Logical ReadsNumber of data pages for XML storage objects (XDAs) that havebeen requested from the buffer pool (logical reads) for regular andlarge tablespaces

Physical ReadsNumber of data pages for XML storage objects (XDAs) that havebeen read from the tablespace containers (physical reads) for regularand large tablespaces


Temporary Data



Asynchronous I/O

Physical Reads

Number of XML storage object (XDA) data pages that have beenread in from the tablespace containers (physical reads) byasynchronous engine dispatchable units (EDUs) for all types oftablespaces.

Physical Writes



Read Requests Number of asynchronous read requests for XML storage object(XDA) data

4 Performance

94 November 2010

4.5.4 Snapshots: TablespacesThe Tablespaces screen provides an overview of the following tablespace activities of yourdatabase:

Tablespace Name

Partition (DPF systems only)

Buffer Quality (%)

Avg. Physical Read Times (ms)

Avg. Physical Write Time (ms)

Data Logical Reads

Data Physical Reads

Index Logical Reads


The Tablespaces screen displays buffer pool activity and direct access information for eachtablespace defined for the SAP database.

To display more detailed information, choose a line in the overview table of the Tablespacesscreen.

The following tab pages are displayed in the content detail area:

Buffer Pool

Asynchronous I/O

Direct I/O

XML Storage

Buffer Pool and Asynchronous I/O provide information about buffer pool access.

Direct I/O and XML Storage provide information about direct accesses, that is, I/O activitythat does not use the buffer pool (for example, access to LONG VARCHAR columns orbackup).

4 Performance

November 2010 95

4.5.4.1 Tablespace Details: Buffer PoolTo display detailed information about buffer pool activity for your selected tablespace(s),choose the Buffer Pool tab page in the content detail area of the Tablespaces screen.


Field Description

Tablespace

Name Name of the tablespace

Buffer Quality

Buffer Pool Name of the buffer pool associated with the selected tablespace


Percentage at which the data is read from the buffer pool, ratherthan directly from the hard disk

This is calculated using the following formula: (logical reads -physical reads) / (logical reads) * 100

Data Hit Ratio Indicates percentage at which data (without index data) is readfrom the buffer pool, rather than directly from the hard disk

Index Hit Ratio Indicates percentage at which index data is read from the bufferpool, rather than directly from the hard disk

No Victim Buffer Number of times an agent did not have a preselected victim bufferavailable

Average Time



Data


Physical Reads



4 Performance

96 November 2010

Physical Writes


The value includes the number of physical writes that wereperformed synchronously (by the database manager agents) andasynchronously (by the I/O cleaners).







Index


Physical ReadsNumber of read accesses to index data on disk (I/O)


Physical Writes






Number of logical read requests that required I/O to get indexpages into the temporary tablespace



4 Performance

November 2010 97

4.5.4.2 Tablespace Details: Asynchronous I/OTo display detailed information about asynchronous I/O for your selected tablespaces,choose the Asynchronous I/O tab page in the content detail area of the Tablespaces screen.


Field Description

Average Time


Average time in milliseconds required by the I/O servers to read apage from disk and write it to the buffer pool


Average time in milliseconds required by the I/O cleaners to reada page from the buffer pool and write it to the hard disk

Data


Number of data pages that were read asynchronously from diskand written to the buffer pool by the I/O servers (prefetch)


Number of data pages that were written asynchronously frombuffer pool to disk (I/O cleaners)


Index


Number of index pages that were read asynchronously from diskand written to the buffer pool by the I/O servers (prefetch)


Number of index pages that were written asynchronously bufferpool to disk (I/O cleaners)


4 Performance

98 November 2010

4.5.4.3 Tablespace Details: Direct I/OTo display detailed information about direct I/O for your selected tablespaces, choose theDirect I/O tab page in the content detail area of the Tablespaces screen.


Field Description

Average Time



I/O



Average I/O perRequest



4.5.4.4 Tablespace Details: XML StorageTo display detailed information about XML storage for the selected tablespaces, choose theXML Storage tab page in the content detail area of the Tablespace screen.


Field Description

Pool Data

Logical ReadsNumber of data pages for XML storage objects (XDAs) that have beenrequested from the buffer pool (logical reads) for regular and largetablespaces

Physical ReadsNumber of data pages for XML storage objects (XDAs) that have beenread from the tablespace containers (physical reads) for regular andlarge tablespaces

4 Performance

November 2010 99

Field Description


Temporary Data



Asynchronous I/O

Physical ReadsNumber of XML storage object (XDA) data pages that have been readin from the tablespace containers (physical reads) by asynchronousengine dispatchable units (EDUs) for all types of tablespaces.

Physical Writes



Read Requests Number of asynchronous read requests for XML storage object (XDA)data

4.5.5 Snapshots: TablesYou can access the table snapshot by calling the DBA Cockpit and choosing Performance

Snapshots Tables on the Database tab page of the DBA Cockpit.

Depending on the setup of your DBA Cockpit, one of the following snapshots is displayed onthe Tables screen:

Enhanced table snapshot with support of the data collection framework (DCF)

Database snapshot without DCF support


4 Performance

100 November 2010

The Tables screen provides information that you can use to analyze tables under thefollowing aspects:

1. Which tables are accessed the most and require extra tuning?

2. Which tables have frequent update operations and are, therefore, potentialcandidates for new statistics?

3. Which tables are candidates for reorganization due to space fragmentation?

Enhanced Table Snapshot With DCF SupportThe enhanced Tables screen does not only display current global table snapshot data butalso monitoring data that is periodically collected by the DCF.

Note

To monitor data on the enhanced Tables screen, you have to make sure that the DCF is setup correctly. If the DCF is not available or wrongly set up, an appropriate warning is displayedincluding a link to the Collector Configuration screen where you can perform the requiredsteps.


End of the note.

FeaturesThe enhanced Tables screen provides the following areas:

A selection area where you specify filter criteria for the monitoring data (onlyavailable in a distributed database system)

A result list of the retrieved monitoring data providing the most important key figuresthat have been aggregated over the selected time period

An option to break down all history data that was collected for the selectedmonitoring data during the specified time frame

ProcessTo analyze table snapshot data, you proceed as follows:

1. You identify the time period where you experienced performance problems forexample, long running batch jobs, threshold violations detected by workloadmanagement, and bad user response time


Note

If you are using a distributed database system and you want to retrieve a generalsnapshot, you set the member selection to All and you do not drill down by members.To retrieve a more detailed snapshot in a distributed database system, you canfurther drill down the selection by members. If a single member or a subset ofmembers shows deviations compared to other members, you can also restrict themember selection.

4 Performance

November 2010 101

3. You restrict the result set in the overview table, for example, by limiting the maximumnumber of rows, by using wildcards, or specifying lower limits for I/O counters.

Example

For example, by using the appropriate wildcard in the Table Name input field, youcan view special BW tables with a specific naming convention.

End of the example.

4. To refresh table snapshot data, you choose the Apply pushbutton.

5. To display detailed history data, you select a line in the overview table.

The data is displayed in the History Details content area.

6. To isolate the time frame during which the performance problem occurred, you usethe data in the overview table in the History Details content detail area

Table Snapshot Without DCF SupportThe following information is displayed:

Column Description

Table Schema Name of the schema

Table Name Name of the table

Partition Number of partition (only displayed in a multi-partition database)

Table File ID File ID (FID) of the table

Table Type Type of table for which information is displayed, for example, user, system,or temp

Rows Written Number of rows changed (inserted, deleted, or updated) in the table

Rows Read Number of rows read from the table

Overflow Access

Number of accesses (reads and writes) to overflowed rows of the table

Overflowed rows indicate that data fragmentation has occurred. If thisnumber is high, you might be able to improve table performance byreorganizing the table using the REORG utility, which cleans up thisfragmentation.

Note

Pay particular attention to this column. If the value in this column is veryhigh, consider reorganizing the table.

End of the note.

4 Performance

102 November 2010

Page Reorgs

Number of page reorganizations executed for the table

Too many page reorganizations can result in less than optimal insertperformance. You can use the REORG TABLE utility to reorganize a tableand eliminate fragmentation.

Note

If you select a line, detailed table analysis data is displayed as described in Analyzing andMaintaining a Single Table [page 177].

End of the note.

4.5.6 Snapshots: Applications (Only DB2 V9.7 orHigher)

Note

This snapshot option is only available if the following applies:

The currently monitored database is at least DB2 V9.7 or higher

The database configuration parameter MON_REQ_METRICS is set to a value otherthan NONE whereas the database manager configuration parameter DFT_MON_UOWis set to ON.

End of the note.

The Applications screen provides information about applications that are currently connectedto the database. The metrics and information displayed for each application only reflect themost recent unit of work of the selected application but not the metrics since the selectedapplication has connected to the database.

You can use the information provided on the Applications screen to:

Monitor the number and details of active and inactive applications that are connectedto the database.

Monitor, capture, or cancel long-running activities

Analyze lock wait situations by monitoring the progress of the application that isholding the lock

4 Performance

November 2010 103

Process FlowTo analyze application snapshot data, you proceed as follows:

1. If the currently monitored database comprises more than one member, you firstspecify in the Selection area whether you want to retrieve information fromapplications that are connected to any member or only to certain members by settingthe appropriate filter criteria.

Note

At the beginning of a unit of work (UOW), each application is assigned to a workloadand therefore, also to a service class. This assignment is reevaluated at thebeginning of the next UOW. If you want to monitor applications that are assigned to aspecific service class, for example, the ABAP dialog service class, set a filteraccordingly in the Selection area.

End of the note.

In addition, you specify if you want to display information about DB2 autonomicprocesses (for example, STMM or Event Monitor) by selecting the Show DB2Autonomics and Utilities checkbox.

To refresh the monitoring data, choose the Apply pushbutton. The followinginformation is displayed:

Column Description

Application Handle

A system-wide unique ID for the application In a distributed databasesystem

This ID is the same on every member where the application can spansubagents.

Coord. Member ID of the coordinating member of the application

Application State State of the application

Application Name Name of application running at the client as known to the databasemanager or DB2 Connect

UOW Runtime Total runtime of the current unit of work (UOW) in milliseconds

Entity Type of the entity (db2agent, db2fmp, or name of the system entity)

Client PID Process ID of the client application that made the connection to thedatabase

Client Workstation Client workstation as specified in the TPMON special register

Client User ID Client user ID as specified in the TPMON special register. In an SAPABAP system, the client user ID corresponds to the SAP user name

4 Performance

104 November 2010

Client Application

Client application as specified in the TPMON special register

In an SAP ABAP system, the client application is specified as follows:

o ptype BTC for SAP batch work processes

o ptype SPO for SAP spool work processes

o ptype UPD or ptype UPD2 for SAP update workprocesses

o the SAP transaction code for SAP dialog workprocesses

Service Superclass Name of the service superclass to which the coordinating agent iscurrently assigned

Service Subclass Name of the service subclass to which the coordinating agent iscurrently assigned

2. To set a filter on the retrieved snapshot data, you specify the following in theSummary area:

Note

The numbers displayed behind the selectable characteristics indicate the number ofapplications, agents, or activities that are currently in the respective state.

End of the note.

Characteristic Description

ApplicationStates

State of an application

The following states are possible:

o Active:

The application is currently executing activities on the database.

o Inactive (having an uncommitted activity):

The application is currently not executing activities on the database.However, the application has done so in the past and these pastactivities have not yet been committed.

o Inactive (no uncommitted activity):

The application is currently not executing any activities on thedatabase and has committed all activities that were executed in thepast.

o Inactive (no agent assigned):

No coordinator is assigned to the application.

4 Performance

November 2010 105

Characteristic Description

Activity Types

Activity types that are currently being executed on the database

The following values are possible:

o LOAD

o READ DML

o WRITE DML

o DDL

o CALL

o OTHER

Note

Only activity types that are currently processed are displayed.

End of the note.

Activity States

States of the activities that are currently being executed on the database

Possible values include, for example, the following states:

o Cancel Pending

o Executing

o Idle

o Initializing

o Queued

o Terminating

Note


End of the note.

4 Performance

106 November 2010

Events RecentlyProcessed

Events that have recently been processed by agents that are assignedto any of the application handles

Possible values include, for example, the following activity states:

o Process Request

o Process Routine

o Wait Request

o Acquire Lock

o Wait WLM Queue

Note


End of the note.

3. To trace, capture, or cancel an activity, select an application handle in the overviewtable of the Application screen and choose the respective pushbutton as described inTracing, Capturing or Canceling an Activity later in this section.

4. To display a detailed view of a specific application, choose an application handlefrom the result list.

For more information, see Displaying Details about Application Handles later in thissection.

Tracing, Capturing, or Canceling an ActivityIf you discover an activity that is running a long time on the Applications screen, you can doone of the following:

Analyze the progress of the unit of work by selecting the application handle in theoverview table of the Application screen and choosing the Trace Activity pushbutton.

The Application Activity Trace starts in a separate Web browser providing detailedinformation about the selected application handle. By default, the screen is refreshedevery 5 seconds. You can choose different refreshing intervals by pausing the trace,specifying a different time interval, and resuming the trace.

After the screen has been refreshed, all agents that are currently assigned to therespective application handle are displayed in the Assigned Agents table. Especiallyin a distributed database, or if the activity uses intra-parallelism, you can detectwhether the progress of an activity is slowed down by a certain subagent. To identifythe reason for this slowdown, check the event-related and request-relatedinformation in the Assigned Agents table.

4 Performance

November 2010 107

The Unit of Work Progress table grows as the trace continues to collect informationabout activities of the respective application handle.

Note

o The Unit of Work Progress table is sorted by time in descending order. Thismeans new data is inserted at the top of the table.

o You can configure metrics of interest to be displayed by choosing the OpenDialog Settings pushbutton.

o In a distributed database environment or if the activity uses intra-parallelism,you can filter data by member.

End of the note.

To review the status of all assigned agents at a certain point in time, you have topause the trace. After selecting the respecting point in time in the Unit of WorkProgress table, details about the assigned agents of that point in time is againdisplayed in Assigned Agents table. The trace is automatically paused as soon as theapplication disconnects from the database system or as soon as this window isclosed.

Capture detailed information about the currently executed activity of an application asfollows:

1. Select the application and choose the Capture Activity pushbutton.

2. In the DBA Cockpit, choose Performance Critical Activities ThresholdViolations .

On the Threshold Violations screen, activities that have been capturedmanually are displayed with the value MANUAL in the Predicate column.

Note

To find manually captured activities more easily, use the filter function of thelist viewer.

End of the note.

Cancel an activity by selecting the application and choosing the Cancel Activitypushbutton.

If the activity is successfully canceled, the SQL error SQL4725N with statusSQLSTATE 57014 is returned to the canceled application.

Displaying Details About Application HandlesTo display detailed information about an application handle, select a line from the result list.In the content detail area, the following tab pages are displayed:

Unit of Work

Current Activities

Assigned Agents

4 Performance

108 November 2010

Unit of WorkOn the Unit of Work tab page, you can find details about the unit of work (UOW) that theapplication is currently executing on the database system. The pie chart indicates where thisUOW has spent most of its time since having been started by the respective application.

Note

If the selected UOW has just started and therefore no metrics have yet been rolled up into theUOW, the following message is displayed instead of the pie chart:

No data is available

End of the note.

You can find more details in the chart area below, for example, detailed aggregate metricsabout all activities that were or are just running as part of this unit of work as well as detailson the UOW itself and its WLM context.

Current ActivitiesThe Current Activities tab page displays the activities that are currently processed as part ofthe current UOW. In most cases, only a single activity (identified by an activity ID) isdisplayed. Only in certain cases - for example, if the application has opened a cursor thatuses the WITH_HOLD attribute - might more than one activity be displayed. If you are using adistributed database or if the activity uses intra-parallelism, you can review the status of eachactivity on individual members by selecting the relevant row in the table. The details shownbelow also include the SQL statement text of the activity.

Assigned AgentsThe Assigned Agents tab page displays details about all database agents that are currentlyassigned to the selected application. In a distributed database or if the activity uses intra-parallelism, you can check the status of each individual agent that is currently assigned to theselected application.

4.5.7 Snapshots: Applications (Only DB2 V9.5 orLower)

Note


The currently monitored database is DB2 9.5 or lower

The currently monitored database is DB2 V9.7 or higher and the databaseconfiguration parameter MON_REQ_METRICS is set to NONE whereas the databasemanager configuration parameter DFT_MON_UOW is set to ON.

End of the note.

The Application screen displays the performance data for every application that is currentlyconnected to the database.

4 Performance

November 2010 109

You can use the following information to determine the activity of applications, for example, toevaluate which applications are placing the highest load on the database:

Partition (only DPF systems)

User

Appl. Handle

Agent PID

Appl. Name

Appl. PID

Appl. Host Name

Application Status

Buffer Quality (%)

Data Logical Reads

Index Logical Reads

Capturing or Canceling an Activity

Note

This feature is available only if the currently monitored database version is at least DB2 V9.5.

End of the note.

If you discover an activity that is running for a very long time on the Application screen, youcan do one of the following:

Capture detailed information about the execution of an activity as follows:

1. Select the activity and choose the Capture pushbutton.

2. In the DBA Cockpit, choose Performance Critical Activities ThresholdViolations .

On the Threshold Violations screen, activities that have been capturedmanually are displayed with the value MANUAL in the Predicate column.

Note

To find manually captured activities more easily, use the filter function of thelist viewer.

End of the note.

Cancel an activity by selecting it and choosing the Cancel pushbutton.

If the activity is successfully canceled, the SQL error SQL4725N with statusSQLSTATE 57014 is returned to the canceled application.

4 Performance

110 November 2010

Displaying Details on ApplicationsYou can display detailed information by choosing a line in the overview table of theApplication screen. The following tab pages are displayed in the content detail area:

Application

Agents

Note

This tab page is only available if you are using the SAP GUI-based user interface. Itcontains information that you can also find on the Assigned Agents and on theAgents Memory tab pages on the Web browser-based user interface.

End of the note.

Assigned Agents

Note

This tab page is only available if you are using the Web browser-based userinterface.

End of the note.

Agents Memory

Note

This tab page is only available if you are using the Web browser-based userinterface.

End of the note.

Buffer Pool

Direct I/O

XML Storage

Locks and Deadlocks

Calls

Sorts

Cache

Unit of Work

Statement

Statement Text

SQL Workspace

4 Performance

November 2010 111

4.5.7.1 Application Details: ApplicationTo display detailed information about an applications, choose the Application tab page in thecontent detail area of the Applications screen.


Field Description

Application

PID Process ID of the database process belonging to an SAP workprocess

Handle In multi partition database systems, this ID is the same on everymember where the application might span subagents.

Connect Start Start time when the application connected to the database

Platform Operating system on which the client application is running

Host Host name of the application server where the application server isrunning

Name Name of application running at the client as known to the databasemanager or DB2 connect

Status

Current status of the application. Possible values are:

Database Connect Pending

The application has initiated a database connection but therequest has not yet completed.

Database Connect Completed

The application has initiated a database connection andthe request has completed.

Unit of Work Executing

The database manager is executing requests on behalf ofthe unit of work.

Unit of Work Waiting

The database manager is waiting on behalf of the unit ofwork in the application. This status typically means that thesystem is executing in the application's code.

Lock Wait

The unit of work is waiting for a lock. After the lock isgranted, the status is restored to its previous value.

4 Performance

112 November 2010

Field Description

Commit Active

The unit of work is committing its database changes.

Rollback Active

The unit of work is rolling back its database changes.

Recompiling

The database manager is compiling an SQL statement orprecompiling a plan on behalf of the application.

Request Interrupted

An interrupt of a request is in progress.

Database Disconnect Pending

The application has initiated a database disconnect but thecommand has not yet completed executing. Theapplication might not have explicitly executed the databasedisconnect command. The database manager disconnectsfrom a database if the application ends withoutdisconnecting.

Transaction prepared

The unit of work is part of a global transaction that hasentered the prepared phase of the two-phase commitprotocol.

Transaction Heuristically

The unit of work is part of a global transaction that hasbeen heuristically committed.

Transaction Heuristically Rolled Back

The unit of work is part of a global transaction that hasbeen heuristically rolled-back.

Transaction Ended

The unit of work is part of a global transaction that hasended but has not yet entered the prepared phase of thetwo-phase commit protocol.

Creating Database

The agent has initiated a request to create a database andthat request has not yet completed.

4 Performance

November 2010 113

Field Description

Restarting Database

The application is restarting a database to perform crashrecovery.

Restoring Database

The application is restoring a backup image to thedatabase.

Backing Up Database

The application is performing a "fast load" of data into thedatabase.

Data Fast Load

The application is performing a "fast load" of data into thedatabase.

Data Fast Unload

The application is performing a "fast unload" of data fromthe database.

Wait to Disable Tablespace

The application has detected an I/O error and is attemptingto disable a particular tablespace. The application has towait for all other active transactions on the tablespace tocomplete before it can disable the tablespace.

Quiescing a Tablespace

The application is performing a QUIESCE TABLESPACErequest.

Wait for Remote Partition The application iswaiting for a response from a remote partition in apartitioned database instance.

Agent

PID Process ID of an SAP work process that made the connection tothe database

Client Information

User IDClient user ID that is generated by the transaction manager andprovided to the server, if the sqleseti API is used.

For ABAP systems: name of the SAP user

4 Performance

114 November 2010

Field Description

Workstation Identifies the client’s system or workstation (for example, CICSEITERMID) if the sqleseti API was used in this connection.

ApplicationIdentifies the server transaction program performing the transactionif the sqleseti API was used in this connection.

For ABAP systems: name of the SAP transaction

Accounting

The data passed to the target database for logging and diagnosticpurposes, if the sqleseti API was used in this connection.

For ABAP systems: name of the program executing the SQLstatement

4.5.7.2 Application Details: Agents

Note

This tab page is only available if you are using the SAP GUI-based user interface of the DBACockpit.

End of the note.

To display detailed information about agents for your selected application, choose the Agentstab page in the content detail area of the Applications screen.


Field Description

Agents

Coordinator Agent PID Process ID (UNIX systems) or thread ID (OS/2 or Windows systems)of the coordinator agent for the application

Currently Associated Number of agents currently associated with the application

Associated with ThisAppl. Number of agents participating in this application (high-water mark)

Stolen from ApplicationNumber of agents removed from this application and subsequentlyused by another application

This only happens if the agent was not busy.

4 Performance

November 2010 115

Times Used by Agent(s)

User CPU Time Total user CPU time in seconds consumed by agents

System CPU Time Total system CPU time in seconds consumed by agents

Idle Time Total idle time in seconds

Waited for Prefetch Total time in milliseconds waited for prefetch

Memory Pools Allocated toAgent

Displays information about memory pools allocated to thisapplication

The table contains the following columns:

Partition

Partition number

PID

Process ID (UNIX) or thread ID (Windows) of theagent

Pool ID

Type of memory pool

Current Size (KB)

Current size of the memory pool

High-Water Mark (KB)

Largest size of the memory pool since its creation

Configured Size (KB)

Configured size of the memory pool

4.5.7.3 Application Details: Assigned Agents

Note

This tab page is only available if you are using the Web browser-based user interface of theDBA Cockpit.

End of the note.

To display detailed information about assigned agents for your selected application, choosethe Assigned Agents tab page in the content detail area of the Applications screen.

4 Performance

116 November 2010


Field Description

Agents

CoordinatorAgent PID

Process ID (UNIX systems) or thread ID (Windows) of the coordinatoragent for the application

CurrentlyAssociated Number of agents currently associated with the application

Associated withThis Appl. Number of agents participating in this application (high-water mark)

Stolen fromApplication

Number of agents removed from this application and subsequently usedby another application

This only happens if the agent was not busy.

Times Spent byAgent(s)

User CPU Time Total user CPU time in seconds consumed by agents

System CPUTime Total system CPU time in seconds consumed by agents

Idle Time Total idle time in seconds

Waited forPrefetch Total time in milliseconds waited for prefetch

Assigned Agents

This table displays information about all agents that are the coordinatoragent itself or agents working as a subagent for the coordinator agent:

Partition

Partition number

Agent Type

Type of the agent

Nesting Level

Nesting level of the agent

Entity

Entity of the agent

State

Indicates whether an agent is associated or active

4 Performance

November 2010 117

Field Description

TID

Thread ID of the agent

Service Class

Service class the agent is assigned to

Event Type

Type of event that was last processed by the agent

Event Object

Object of the event that was last processed by the agent

Event State

State of the event that was last processed by the agent

4.5.7.4 Application Details: Agents Memory

Note

This tab page is only available if you are using the Web browser-based user interface of theDBA Cockpit.

End of the note.

To display detailed information about agents memory for your selected application, choosethe Agents Memory tab page in the content detail area of the Applications screen.


Column Description

Partition Partition number

PID Process ID (UNIX) or thread ID (Windows) of the agent

Pool ID Type of memory pool

Current Size (KB) Current size of the memory pool

High-Water Mark (KB) Largest size of the memory pool since its creation

Configured Size (KB) Configured size of the memory pool

4 Performance

118 November 2010

4.5.7.5 Application Details: Buffer PoolTo display detailed information about buffer pool activity for your selected application(s),choose the Buffer Pool tab page in the content detail area of the Applications screen.


Field Description

Buffer Quality


Indicates percentage at which the data is read from the bufferpool, rather than directly from the hard disk



Data Hit Ratio Indicates percentage at which data (without index data) is readfrom the buffer pool, rather than directly from the hard disk

Index Hit Ratio Indicates percentage at which index data is read from the bufferpool, rather than directly from the hard disk

Average Time



Data


Physical Reads



Physical Writes


It includes the number of physical writes that were performedsynchronously (by the database manager agents) andasynchronously (by the I/O cleaners).

Temporary Logical Reads Number of logical read requests that required I/O to get datapages into the temporary tablespace



4 Performance

November 2010 119

Field Description

Index


Physical Reads


Since index data is read only by the database manager agents,this value contains the number of synchronously read indexpages.

Physical Writes



Temporary Logical Reads Number of logical read requests that required I/O to get indexpages into the temporary tablespace



4.5.7.6 Application Details: Direct I/OTo display detail information about direct I/O for your selected application, choose the DirectI/O tab page in the content detail area of the Applications screen.


Field Description

Average Time



I/O



4 Performance

120 November 2010

Average I/O perRequest



4.5.7.7 Application Details: XML StorageTo display detailed information about XML storage for the selected application, choose theXML Storage tab page in the content detail area of the Applications screen.


Field Description

Pool Data

Logical ReadsNumber of data pages for XML storage objects (XDAs) that havebeen requested from the buffer pool (logical reads) for regular andlarge tablespaces

Physical ReadsNumber of data pages for XML storage objects (XDAs) that havebeen read from the tablespace containers (physical reads) forregular and large tablespaces


Temporary Data


Physical ReadsNumber of pages for XML storage objects that have been (XDA)read from the tablespace containers (physical reads) for temporarytablespaces

Asynchronous I/O

Physical Reads

Number of XML storage object (XDA) data pages that have beenread in from the tablespace containers (physical reads) byasynchronous engine dispatchable units (EDUs) for all types oftablespaces.

4 Performance

November 2010 121

Physical Writes



Read Requests Number of asynchronous read requests for XML storage object(XDA) data

4.5.7.8 Application Details: Locks and DeadlocksTo display detailed information about locks and deadlocks for your selected application,choose the Locks and Deadlocks tab page in the content detail area of the Applicationsscreen.


Fields Description

Lock Waits

TotalTotal number of times that this application requested a lock, but hadto wait because another application was already holding a lock on thedata

Time Waited Total amount of elapsed time in milliseconds that this application haswaited for a lock to be granted

Average Time Waited Average time in milliseconds waited for a lock

Escalations

Lock Escalations

Number of times that locks have been escalated from several rowlocks to a table lock

If the maximum allowed length of the lock list is reached, row locksare converted to table locks to save space in the lock list. Thisprocess is called "lock escalation".

Exclusive LockEscalations

Number of times that locks have been escalated from several rowlocks to one exclusive table lock, or the number of times an exclusivelock on a row caused the table lock to become an exclusive lock

Exclusive locks are important to track since they can impact theconcurrency of your data because other applications cannot accessdata held by an exclusive lock.

4 Performance

122 November 2010

Locks

Locks Currently Held Total number of locks currently held by the application

Deadlocks Detected

Number of deadlocks that have occurred Deadlock situations arerecognized and resolved automatically by the database

The database configuration parameter DLCHKTIME determines whena lock wait situation is resolved.

Lock Timeouts

Number of times that a request to lock an object timed out instead ofbeing granted

The database configuration parameter LOCKTIMEOUT determineswhen a lock wait situation is resolved.

Lock Timeout Value Value of the database configuration parameterLOCKTIMEOUT

Deadlock EventMonitor

Statement History ListSize

When a detailed deadlock event monitor with history is running, thiselement reports the number of bytes being used from the databasemonitor heap (HON_HEAP_S) to keep track of the statement historylist entries.

4.5.7.9 Application Details: CallsTo display detailed information about calls for your selected application, choose the Calls tabpage in the content detail area of the Applications screen.


Field Description

Rows

Deleted Number of data records that were deleted

Inserted Number of data records that were inserted

Selected Number of data records that were selected

Updated Number of data records that were updated

4 Performance

November 2010 123

Statements Executed

SELECT SQL Number of SELECT statements that were executed

UPDATE/INSERT/DELETE Number of UPDATE, INSERT, and DELETE statements thatwere executed

DDLNumber of Data Definition Language (DDL) statements that wereexecuted, such as CREATE TABLE, CREATE VIEW, ALTERTABLE, and DROP INDEX.

Statements Attempted

COMMITs Number of COMMIT statements that have been attempted

RollbacksNumber of ROLLBACK statements that have been attempted

Automatic rollbacks caused by error situations or deadlocks arenot included.

Dynamic SQL Number of dynamic SQL statements attempted

Static SQL Number of static SQL statements attempted

Failed SQL Number of attempted SQL statements that failed

Hash Joins

Total Total number of hash joins executed

Total Hash Loops Total number of times that a single partition of a hash join waslarger than the available sort heap space

Overflows Number of times that hash join data exceeded the available sortheap space

Small Overflows Number of times that hash join data exceeded the available sortheap space by less than 10 %

4.5.7.10 Application Details: SortsTo display detailed information about sorts for your selected application, choose the Sorts tabpage in the content detail area of the Applications screen.

4 Performance

124 November 2010


Field Description

Sort Time

Total Total time in milliseconds required for all sort processes

Average Average sort time in milliseconds

Sorts

Total Sorts Total number of sorts that have been executed

SortOverflows

If the storage area allocated for sorting is not large enough, a sort overflowoccurs. The hard disk is then used temporarily.

4.5.7.11 Application Details: CacheTo display detailed information about cache for your selected application(s), choose theCache tab page in the content detail area of the Applications screen.


Field Description

Catalog Cache

Quality

Indicates percentage at which the data is read from the catalog cache,rather than directly from the hard disk


(catalog cache lookups - catalog cache insert) / catalog cache lookups *100

Lookups Number of times that the catalog cache was referenced to obtain tabledescriptor information

Inserts Number of times that the system tried to insert table descriptorinformation into the catalog cache

Overflows Number of times that an insert into the catalog cache failed due to thecatalog cache being full

Heap Full Number of times that an insert into the catalog cache failed due to thedatabase heap being full

4 Performance

November 2010 125

Package Cache

Quality

Indicates percentage at which the data is read from the package cache,rather than directly from the hard disk


(package cache lookups - package cache inserts) / package cachelookups * 100

Lookups Number of times an application looked for a section in the package cache

Inserts Total number of times that a request section was not available for useand had to be loaded into the package cache

4.5.7.12 Application Details: Unit of WorkTo display detailed information about units of work for your selected application, choose theUnit of Work tab page in the content detail area of the Applications screen.


Field Description

Unit of Work

Start Time Time that unit of work first required database resources

Stop Time Time that the most recent unit of work completed, which occurs whenthe database changes are committed or rolled back

Elapsed Time (s) Duration of unit of work in seconds

Elapsed Time (µs) Duration of unit of work in microseconds

Log Space Used Log space used in bytes in most recent unit of work

Completion Status Completion status of last transaction

Previous Unit ofWork

Stop Time Previous time that the most recent unit of work completed, which occurswhen the database changes are committed or rolled back

4 Performance

126 November 2010

4.5.7.13 Application Details: StatementTo display detailed information about performance data of the current SQL statements foryour selected application, choose the Statement tab page in the content detail area of theApplications screen.


Field Description

Statement

Start Time Date and time when unit of work starts, the statement starts, or adeadlock is detected

Stop Time Date and time when the statement stopped executing

Elapsed Time(s) Duration of unit of work in seconds

Elapsed Time (µsec) Duration of unit of work in microseconds

Rows

Rows Read Number of rows read from the table

Rows Written Number of rows changed (inserted, deleted, or updated) in thetable

Sort

Sort Overflow If the storage area allocated for sorting is not large enough, a sortoverflow occurs. The hard disk is then temporarily used.

Total Sort Time Total time for all sort processes

Number of StatementSorts Total number of sorts that have been executed

Data


Physical Reads Number of read accesses to data on disk





4 Performance

November 2010 127

Index


Physical Reads Number of read accesses to data on disk


Number of logical read requests that required I/O to get indexpages into the temporary tablespace



4.5.7.14 Application Details: Statement TextTo display detailed information about the current SQL statements for your selectedapplication, choose the Statement Text tab page in the content detail area of the Applicationsscreen.


Field Description

Statement

Type

Type of statement processed

Possible types are:

Static SQL statement

Dynamic SQL statement

An operation other than an SQL statement, for example, a bind orprecompile operation

Operation Operation currently being processed or most recently processed (if none iscurrently running)

Possible operations are:

SELECT

PREPARE

EXECUTE

EXECUTE IMMEDIATE

OPEN

FETCH

4 Performance

128 November 2010

Field Description

Continuation ofOperation

CLOSE

DESCRIBE

STATIC COMMIT

STATIC ROLLBACK

FREE LOCATOR

PREP_COMMIT

CALL

PREP_OPEN

PREP_EXEC

COMPILE

Blocking Cursor

Indicates if the statement that is executed is using a blocking cursor (YES)or not (NO)

If data is transferred in blocks and not row by row, the performance of thecorresponding query is improved.

Statement

Text of dynamic SQL statement that was being processed when thesnapshot was taken

It can also be the text of the statement that was most recently processed ifno statement was being processed at the time when the snapshot wastaken.

If a statement is displayed, you can choose EXPLAIN to list the access plan for the statementexecution. This function provides a detailed analysis of expensive SQL statements.

Note

To display the ABAP source program where the statement was defined, choose Source. Aneditor screen with the related source appears.

However, this function is only available for local system or ABAP systems that have anadditional RFC destination assigned.

End of the note.

More InformationThe EXPLAIN Function [page 19]

4 Performance

November 2010 129

4.5.7.15 Application Details: SQL WorkspaceTo display detailed information about the current SQL workspace for your selectedapplication, choose the SQL Workspace tab page in the content detail area of theApplications screen.


Field Description

PrivateWorkspace

Lookups Number of times an application looked for an SQL section in the agent'sprivate workspace

Inserts Inserts of SQL sections by an application into the private workspace

Overflows Number of times that the private workspace overflowed the bounds of itsallocated memory

High-Water Mark Largest size reached by the private workspace

SharedWorkspace

Lookups Number of times an application looked for an SQL section in the agent'sshared workspace

Inserts Inserts of SQL sections by an application into the shared workspace

Overflows Number of times that the shared workspace overflowed the bounds of itsallocated memory

High-Water Mark Largest size reached by the shared workspace

4.5.8 Snapshots: SQL Cache (Only DB2 V9.7 orHigher)

Note


The currently monitored database is at least DB2 V9.7 or higher.

The database configuration parameter MON_ACT_METRICS is set to a value otherthan NONE.

End of the note.

4 Performance

130 November 2010

The SQL Cache screen displays information about SQL statements that are executed veryoften and stored in the SQL cache of your system. This information helps you identify thoseSQL statements that consume a large number of resources. You can also determine whetherfine-tuning of those statements is necessary to improve the performance of the database.

Depending on your system, the snapshot can give you a wide range of information, whichmight lead to a very large result set.

To limit the result set, you can specify ranking or filter criteria in the Selection area by eitherchoosing the Top SQL Statements by or Custom radio button. If you choose the Top SQLStatements by option, you have to choose a ranking criteria from the relevant dropdown list. Ifyou choose the Custom option, you can specify filter criteria in the relevant fields.

In the Selection area, you can also define the maximum number of returned SQL statements.The default limit is 100 SQL statements. By default, static packages are not displayed as theSAP system uses dynamic SQL only. If you want to analyze static packages, you have toselect the Display Static Packages checkbox.

If you choose the Apply Selection pushbutton, the result set is determined according to yourselection criteria.


Column Description

Statement Text Text of the SQL statement

<ranking metric>The first metric column is used for ranking as chosen in the Selection areafrom the Top SQL Statements by dropdown list.

By default, Coord. Statement Exec. Time is used.

No. of Coord.Executions Number of executions by coordinator agent monitor element

Avg. Coord.Stmt. Exec. Time

Average execution time in milliseconds for statement by coordinator agentmonitor element

Total CPU Time Total CPU time in milliseconds

Rows Read /Rows Processed

Ratio of rows read from the base table compared to rows processed, whichcan be either rows returned to the application (SELECT statements) orrows written (UPDATE, INSERT, DELETE statements).

A value of 1 indicates optimal access to the requested data.

High values indicate statements with inefficient access.

BP Gets / RowsProcessed

Average number of pages read from the buffer pool per rows processed,which can be either rows returned to the application (SELECT statements)or rows written (UPDATE, INSERT, DELETE statements)

4 Performance

November 2010 131

Displaying Details About SQL StatementsTo display detailed information about an SQL statement, select a line from the result list. TheSQL Statement Details area appears displaying the following tab pages:

SQL StatementOn the SQL Statement tab page, the SQL statement text and the compilation environmentare displayed. To show the access plan of the statement, you can choose the EXPLAINpushbutton. For more information, see The EXPLAIN Function.

The Compilation Environment area displays information, for example, about the following:

Isolation

Query optimization

SQL rules

Refresh age

Resolution time stamp

Statement MetricsThe Statement Metrics tab page provides the chart view Time Spent in SQL Statement.Furthermore, detailed information about the following is displayed:

Statement metadata

Miscellaneous metrics

Sorts

Locking

Logger

Buffer pool

Direct I/O

4.5.9 Snapshots: SQL Cache (Only DB2 V9.5 or Lower) Note

This snapshot option is available if one of the following applies:

The currently monitored database is DB2 9.5 or lower.

The currently monitored database is DB2 V9.7 or higher and the databaseconfiguration parameterMON_ACT_METRICS is set to NONE whereas the databasemanager configuration parameter DFT_MON_STMT is set to ON.

End of the note.

4 Performance

132 November 2010

The SQL Cache screen displays information about SQL statements that are executed veryoften and stored in the SQL cache of your system. This information helps you identify thoseSQL statements that consume a large number of resources. You can also determine whetherfine-tuning of those statements is necessary to improve the performance of the database.

Depending on your system, the snapshot can give you a wide range of information, whichmight lead to a very large result set. After the snapshot has been taken and before the resultsare displayed, you can specify filter criteria in the Selection area to limit the result set:

Field Description

Executions Number of times a statement has been executed

Total Execution Time Total execution time in milliseconds for a statement

Avg. Execution Time Average execution time in milliseconds for a statement

Rows Read Number of rows read for a statement

Rows Written Number of rows written by a statement

SQL Text Search using either the wild card "*" or using a text string, forexample, INSERT, to limit the number of statements displayed


Ratio of rows read from the base table compared to rows processed,which can be either rows returned to the application (SELECTstatements) or rows written (UPDATE, INSERT, DELETE statements)

A value of 1 indicates an optimal access to the requested data. Highvalues indicate statements with an inefficient access.

Note

This metric is only evaluated if your database is DB2 V9.5 Fix Pack 1or higher.

End of the note.

If you choose the Apply Selection pushbutton, the result set is determined by filtering thesnapshot results according to your selection criteria and the following information is displayedin the Summary area:

Column Description

Execution Time Total execution time in milliseconds for an SQL statement

Rows Read Total number of rows read

Rows Written Total number of rows written

4 Performance

November 2010 133

Note

The data displayed in the Summary area refers to the entire SQL cache and not only to thecurrently selected result set.

End of the note.

The result set is displayed in a table as follows:

Column Description

SQL Text Text of a dynamic SQL statement that was in the SQL cache at the timeof the snapshot

Executions

Number of times a statement was executed

This value helps you to identify which statements are executed veryoften. A high number of executions does not necessarily mean that astatement is using an excessive amount of resources. You should alsocheck the number of rows read and rows written. If you find relativelyhigh values here, choose EXPLAIN to check whether indexes are notbeing efficiently used or whether indexes are missing.

Total ExecutionTime (ms)

Total execution time in milliseconds for a statement

You can use this value together with Executions to identify thestatements that would benefit from further analysis.

Total ExecutionTime ( %)

Total Execution Time (milliseconds) divided by Total Cache SumExecution Time (milliseconds)

Average ExecutionTime (ms) Total Execution Time (in milliseconds) divided by Executions

Buffer Quality (%) Buffer quality for this statement in percent


Ratio of rows read from the base table compared to rows processed,which can be either rows returned to the application (SELECTstatements) or rows written (UPDATE, INSERT, DELETE statements)

A value of 1 indicates an optimal access to the requested data. Highvalues indicate statements with an inefficient access.

Note

This metric is only available if your database is DB2 V9.5 for Linux,UNIX, and Windows Fix Pack 1 or higher.

End of the note.

4 Performance

134 November 2010

BP Gets / RowsProcessed

Average number of pages read from the buffer pool per rows processed,which can be either rows returned to the application (SELECTstatements) or rows written (UPDATE, INSERT, DELETE statements)

Note

This metric is only available if your database is DB2 V9.5 for Linux,UNIX, and Windows Fix Pack 1 or higher.

End of the note.

BP Gets /Executions

Average number of pages read from the buffer pool per execution of thestatement

Rows Read

Number of rows read

You can use this value to identify statements that would benefit fromadditional indexes. Use EXPLAIN to analyze the statement. The givenvalue does not necessarily correspond to the number of rows of theresult set of the SQL statement. The Rows Read value shows thenumber of rows that needs to be read to obtain the result set.

Rows Written

Number of rows that were changed (inserted, deleted, or modified) in atable

High values might indicate that you should update statistics usingRUNSTATS.

SQL Sorts

Number of sorts that were necessary to execute the statement

You can use this value to determine whether new indexes are needed.Use EXPLAIN to check whether and which indexes were used when theselected statement was executed.

Sort Overflows Number of sort overflows

Total Sort Time(ms) Total sort time in milliseconds

Note

If no hits are found, the result set is empty, and nothing is displayed.

End of the note.

The following functions are available for further actions:

EXPLAIN

To display a detailed performance analysis, you can display the access plan for theSQL statement by choosing the EXPLAIN pushbutton.

For more information, see The EXPLAIN Function [page 19].

4 Performance

November 2010 135

Index Advisor

To improve the performance of a query, you can retrieve recommendations aboutuseful indexes using the Index Advisor pushbutton. In addition, you can design newvirtual indexes that can be validated before they are actually created.

For more information, see The Index Advisor [page 27].

Source

To display the ABAP source program where the statement was defined, choose theSource pushbutton. An editor screen with the related source appears.

Note

This function is only available for local systems or ABAP systems that have anadditional RFC destination assigned.

End of the note.

Displaying Details About SQL StatementsTo display detailed information about an SQL statement, select a line from the result list. Inthe content detail area, the following tab pages are displayed:

CommonOn the Common tab page, you can find details about the statements and rows.

These details include, for example, information about:

Package cache ID

Insert time stamp

Partition

Authorization ID

Buffer pool quality

Executions

Compilations

Rows deleted, inserted, and read

Resource ConsumptionThe Resource Consumption tab page displays details about the total resource consumption,the proportional resource consumption, and the sorts.

4 Performance

136 November 2010

These details include, for example, the following information:

Execution time

User CPU time

System CPU time

Worst and best preparation time

Rows read and written

Average time per row read and per row written

Sort overflows

Total sort time

I/OThe I/O tab page displays details about the buffer pool, temporary data, and XML storage,that is, about the number of logical and physical reads.

Statement TextThe Statement Text tab page displays the complete text of the SQL statement.

4.6 Performance: Critical Activities You can access data about critical activities by calling the DBA Cockpit and choosing

Performance Critical Activities <activity option> on the Database tab page of theDBA Cockpit.

Note

This screen is only available if the currently monitored database version is at least DB2 V 9.5.

End of the note.

The information provided in the Critical Activity task area allows you to define thresholds onresources to capture information or even cancel database activities that are showingabnormal behavior. Thresholds are either controlled proactively before the activity beginsbased on the projected impact, or reactively while the activity is running and consumingresources.

For more information about thresholds, see Control of work with thresholds in the IBM DB2V9.7 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.wlm.doc/doc/c0053451.html



4 Performance

November 2010 137

FeaturesThe following critical activities are available:

Threshold Violations

You can use the information on this screen to review violations of defined thresholds.

Threshold Configuration

You can use the information on this screen to maintain thresholds on the databasesystem.

4.6.1 Critical Activities: Threshold ViolationsOn the Threshold Violations screen, you can analyze threshold violations that occurred onthe database. You can display threshold violations that were captured during a certain timeframe, by specifying a time frame in the Selection area, and choosing the Apply Selectionpushbutton.


Column Description

Violation Time Time when the threshold violation occurred

Member Database member where the violation occurred

Predicate

Predicate that was violated

Note

Activities with the value MANUAL were captured manually on theApplications screen.

For more information, see Snapshots: Applications (Only DB2 V9.7 orHigher) [page 102] or Snapshots: Applications (Only DB2 V9.5 or Lower)[page 108].

End of the note.

Violated Value Value that was exceeded and that violated the threshold predicate

Application ID Application ID of the activity that caused the violation

Agent ID Agent ID of the activity that caused the violation

By default, the history of a threshold violation is kept for two weeks. To delete all recordedthreshold violations, choose the Reset Violation History pushbutton.

For more information about how to change the size of the violation history, see Configuration:Configuration History [page 217].

4 Performance

138 November 2010

Displaying Details about Threshold ViolationsTo display details about a threshold violation, choose a line in the overview table. Detailsabout a selected threshold violation are displayed in the content detail area on the followingtab pages:

General

Displays details about the activity that violated the threshold as well as the executionstatistics for that particular activity

SQL Statement(s)

Displays details about the SQL statement that was executed as part of the activity

For nested statement calls - for example, during the execution of stored procedures -more than one SQL statement can be available.

You can retrieve additional information about the bind values and additional detailsabout a single SQL statement as follows:

o Retrieve a newly generated access plan by choosing an SQL statement fromthe list and then the EXPLAIN pushbutton.

The new access plan is displayed in a separate window.

o Retrieve the access plan as it existed in the SQL cache when the thresholdviolation occurred by choosing the Section EXPLAIN pushbutton

The current access plan is displayed in a separate window.

Note

DB2 V9.5 only

To be able to retrieve the access plan using the Section EXPLAINpushbutton, you have to set the DB2 registry variableDB2_DUMP_SECTION_ENV to ON.

For more information, see SAP Note 1227225.

End of the note.

4.6.2 Critical Activities: Threshold ConfigurationOn the Threshold Configuration screen, all defined thresholds for the database system aredisplayed. You can perform the following actions:

Enable or disable a threshold by selecting a line from the list and choosing theEnable / Disable Threshold pushbutton.

Create a threshold by choosing the Create Threshold pushbutton. A wizard appearsthat guides you through the procedure.

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1227225&_NLANG=en&_NVERS=0

4 Performance

November 2010 139

Note

The predicates that are available in the wizard are limited to those that areconsidered to be a use case in an SAP environment. DB2, however, allows you todefine thresholds on more predicates than are available when using the wizard in theDBA Cockpit.

Be aware that inappropriate predicate values can cause a system slowdown due toincreased I/O. Thresholds that are violated too often force the even monitor to collectand write details of each threshold violation to the respective event monitor tables. Toget meaningful predicate values when you define thresholds, use the statistics thatare available in the Performance: Workload Statistics [page 66] screen.

End of the note.

Drop a threshold by selecting a line from the list and choosing the Drop Thresholdpushbutton.

Note

If the WLM event monitors have not yet been created on the database, you can do so on theCollector Configuration screen under Configuration Data Collection Framework in theDBA Cockpit.

For more information, see Configuration: Data Collection Framework [page 248].

End of the note.

4.7 Performance: UtilitiesYou can access data on utilities by calling the DBA Cockpit and choosing Performance

Utilities <Utilities option> on the Database tab page of the DBA Cockpit.

The following options are available:

Database Utilities

On the Database Utilities screen, you can check if database performance is currentlyinfluenced by utilities, such as RUNSTATS or REORG.

Inplace Table Reorganization

The Inplace Table Reorganization screen provides an overview of all inplace tablereorganizations. Inplace table reorganizations let you access tables while they arebeing reorganized.

4 Performance

140 November 2010

4.7.1 Utilities: Database UtilitiesOn the Database Utilities screen, you can check if database performance is currentlyinfluenced by utilities, such as RUNSTATS or REORG.

Depending on the utility, performance can decrease due to one of the following:

Reduced IO performance because a utility performs much physical I/O

Locking situations on database resources, such as tables that are locked by anoffline REORG

The following information is displayed for all running utilities:

Column Description

Partition Number of the partition on which the utility is running

Type

Type of utility that is running, such as:

ASYNC_INDEX_CLEANUP

BACKUP

CRASH_RECOVERY

LOAD

REBALANCE

REDISTRIBUTE

REORG

RESTART_RECREATE_INDEX

RESTORE

ROLLFORWARD_RECOVERY

RUNSTATS

Description Describes the utility and what it is working on, for example, whether a tableis being processed by a RUNSTATS

Start Time Date and time when utility started

4 Performance

November 2010 141

Processing Mode

Defines how to interpret the progress list that is shown in the contentdetail area after you have selected a line in the overview table

The following values are possible are:

Concurrent

Due to concurrent processing, any element in the progresslist can be updated at any time.

Serial

Interpret the elements in the list as a set of serial phases

This means that completed work must equal the total work forelement n before the completed work of element n+1 is firstupdated. This (?) attribute is used to describe the progress ofa task that consists of a set of serial phases where a phasemust fully complete before the next phase begins.

<space>

The utility is running as one single phase without parallelism

Sequence Number Specifies the current phase the utility is working on

Invoker

Indicates how the utility was started


AUTO

The utility was automatically started by DB2.

USER

The utility was started manually.

PrioritySpecifies the relative importance of a throttled utility

The higher the priority, the more you might experience an impact onoverall database performance.

4 Performance

142 November 2010

State

Shows the current execution state of the utility

ERROR

The utility is stopped due to an unexpected error situation.

EXECUTE

The utility is executing.

WAIT

The utility is waiting, for example, due to blocked resourcesor synchronous I/O requests.

Displaying Details about UtilitiesIf a utility is in concurrent or serial processing mode, you can choose the utility in theoverview table. The Utility Details area appears providing information about all phases of theselected utility. The Utility Data subarea provides a summary of important indicators of theoverview table, such as Utility ID, Invoker, and so on.

The Running Phases table provides the following information:

Column Description

Partition Number of the partition where the utility phase is running

Start Time Date and time when the utility phase started

Sequence Number Specifies the number of the utility phase

Description Description about the action performed in this phase

Progress (%) Work progress in percent (which is the percentage of completedunits compared to the total number of units)

Completed Number of units that have been processed

Total Total number of units that need to be processed by the utility phase

4 Performance

November 2010 143

Work Metrics

Metrics of the work units


NOT_SUPPORT

BYTES

EXTENTS

INDEXES

PAGES

ROWS

TABLES

State Shows the current execution state of the utility phase

4.7.2 Utilities: Inplace Table ReorganizationThe Inplace Table Reorganization screen provides an overview of inplace tablereorganizations that are currently running or that have been interrupted. Inplace tablereorganization allows you to access tables while they are being reorganized.

Note

In contrast to the Database Utilities screen, the Inplace Table Reorganization screen providesa more detailed view of reorganizations. In addition, not only currently active reorganizationsare displayed but also the DB2 history file for finished reorganizations is retrieved.

End of the note.

The information is displayed in the following table:

Column Description

Table Schema Table schema of the table that is currently being reorganized

Table Name Name of the table that is currently being reorganized

Partition Number of the partition (only displayed in a multi-partitiondatabase)

4 Performance

144 November 2010

REORG Status

Status of the inplace table reorganization

Possible values are:

Running

Paused

Suspended

Completed

Progress % Progress of the reorganization

Start Date Start date of the inplace table reorganization

Start Time Start time of the inplace table reorganization

Access Mode

Access mode for other users while the table reorganization isrunning

The following access modes are possible:

READ

WRITE

NO ACCESS

Tablespace Name of the tablespace where the reorganization is performed

Note

If no active inplace table reorganization was found, the system displays the followingmessage: No Inplace Table Reorganizations are running. Only the REORGactivities since the database start are displayed. REORGs that were active before thedatabase start are not displayed.

End of the note.

4 Performance

November 2010 145

Depending on your requirements, you can customize the view on the Performance: ActiveInplace Table Reorganizations screen using the following functions:

Pushbutton Function

Choose View

Active Only

Only inplace table reorganizations with the status Started orPaused are displayed.

All

All inplace table reorganizations are displayed including thosewith status Completed or Suspended.

Choose DataSource

Since DB Start

Only inplace table reorganization that have been started afterthe last restart of the database manager are displayed.

Incl. History File

This option additionally reads the DB2 history file. Thus, thedata of inplace table reorganizations that were started beforethe last restart of the database manager is also retrieved.

ActivitiesYou can perform the following actions for an inplace reorganization:

Pause

Select a running inplace reorganization and choose Pause.

Resume

Select a paused inplace table reorganization and choose Resume.

Suspend

Select any inplace table reorganization and choose Suspend.

As a result of any of these actions, the list of active inplace table reorganizations is refreshed.

4 Performance

146 November 2010

4.8 History: Database Caution

For DB2 V9.5 and DB2 V9.7, this screen has been deprecated and replaced by the enhanceddatabase snapshot [page 71].

End of the caution.

History data is only available if you selected Collect History Data when configuring yourdatabase for remote monitoring. For more information, see Configuration of Systems forRemote Monitoring.

The system provides a day-by-day trend analysis of database activity. You can check theworkload of the days and display the workload peak of a single day.

You can access the History: Database screen by calling the DBA Cockpit and choosingPerformance History Database on the database tab page of the DBA Cockpit.

An overview of all days monitored is displayed:

Column Description

Partition Monitored partition (only displayed if you are using a multi-partitiondatabase)

Date Day when monitoring was performed

Avg. Phys. ReadTime (ms)

Average physical read time

If you have chosen Total Day, this is the average of all measuredaverage read times. If you have chosen Peak, this is the worstmeasured read time.

Avg. Phys. WriteTime (ms)

Average physical write time

If you have chosen Total Day, this is the average of all measuredaverage write times. If you have chosen Peak, this is the worstmeasured write time.

Data Logical Reads Number of read accesses to data in the buffer pool

Data PhysicalReads


The value includes the number of physical reads that were performedsynchronously (by the database manager agents) and asynchronously(by the I/O servers).

Data PhysicalWrites


The value includes the number of physical writes that were performedsynchronously (by the database manager agents) and asynchronously(by the I/O cleaners).

4 Performance

November 2010 147

Index LogicalReads Number of read accesses to index data in the buffer pool

Index PhysicalReads



Index PhysicalWrites


The value includes the number of physical writes that were performedsynchronously (by the database manager agents) and asynchronously(by the I/O cleaners).

COMMITStatements Total number of COMMIT statements that have been attempted

ROLLBACKStatements

Total number of ROLLBACK statements that have been attempted

Automatic ROLLBACKs caused by error situations or deadlocks are notincluded.

Lock Waits Total number of times that applications or connections waited for locks

Lock Wait Time(ms) Total elapsed time in milliseconds waited for a lock

Deadlocks Total number of deadlocks that have occurred

Lock Escalations Number of times that locks have been escalated from several row locksto a table lock

Exclusive LockEscalations

Number of times that locks have been escalated from several row locksto one exclusive table lock, or the number of times an exclusive lock ona row caused the table lock to become an exclusive lock

If you choose Total Day in the Workload field in the Selection area, the total workload of therelevant day is displayed. The value displayed is calculated using formula maximum value -minimum value. Database restarts are taken into consideration.

If you choose Peak in the Workload field in the Selection area, the maximum of all measuredvalues is displayed.

You can display details for a specific day by clicking a field or selecting a row. A detail areaappears with the following tab pages:

Snapshot

The measured values of the selected day are displayed.

Interval

The delta values of the measurements, which are provided under Snapshot, aredisplayed.

4 Performance

148 November 2010

If you select a particular day, snapshots of the database activity are displayed in a two-hourcycle.

Note

If the database is restarted during one day, the interval displayed after the restart does notequal the delta of two measurements because the counter was reset during the restart. In thiscase, the absolute value of the last measurement is displayed.

End of the note.

4.9 History: Tables Caution

For DB2 V9.5 and DB2 V9.7, this screen has been deprecated and replaced by the enhancedtable snapshot [page 99].

End of the caution.

History data is only available if you have selected Collect History Data when configuring yourdatabase for remote monitoring. For more information, see Configuration of Systems forRemote Monitoring.

The system provides a day-by-day trend analysis of table activity.

You can access the History: Tables screen by calling the DBA Cockpit and choosingPerformance History Tables on the Database tab page of the DBA Cockpit.

An overview of the monitored days is displayed:

Column Description

Table Schema Name of the schema to which the table belongs



Rows Written Number of rows written

Rows Read Number of rows read

4 Performance

November 2010 149

Overflow Accesses

Number of read accesses to tables that resulted in overflow pages, thatis, to records that were swapped from their original page.

Note

If there is a high number of overflow accesses in comparison to totalread accesses, the table is a candidate for reorganization.

End of the note.

Page Reorgs Number of internal page reorganizations during INSERT operations

Note

If you want to display history data that is cumulated by day, week, or month, choose therelevant option from the dropdown list in the Statistics field in the Selection area.

End of the ote.

4 Performance

150 November 2010

5 Space

November 2010 151

5 SpaceThe following sections provide information about the main task areas that are available underSpace on the Database tab page of the DBA Cockpit:

Overview

Automatic Storage

Database

Tablespaces

Containers

File Systems

Tables and Indexes

Single Table Analysis

5.1 Space: Overview Note

This function is only available if you have selected Collect Space and Performance HistoryData when you configured your database for remote monitoring. For more information, seeConfiguring Systems for Remote Monitoring Manually [page 37].

End of the note.

You can access general information about space for your database by calling the DBACockpit and choosing Space Overview on the Database tab page of the DBA Cockpit.

The following tab pages are available on the Overview screen:

Databases and Tablespaces

Tables and Indexes

Databases and Tablespaces

Field Description

Tablespaces

Last Analysis Date and time of the last analysis

Total Number Total number of tablespaces in the database

Total Size Total size of all tablespaces in KB

Free Space Free space in all tablespaces in KB

5 Space

152 November 2010

Field Description

Used Space Used space of all tablespaces as a percentage

Minimum Free Space in aTablespace

Free space of the tablespace with the lowest amount of freespace in KB

Maximum Used Space in aTablespace

Used space of the tablespace with the highest fill level as apercentage

Database Partitions

Total NumberNumber of database partitions

The value displayed is only higher than 1 if you are using amulti-partition database.

Tables and Indexes

Field Description

Last Analysis Date and time of the last analysis

Total Number of Tables Total number of tables defined in the database

Total Size of Tables Total amount of used space of all tables defined in the database

Total Number ofIndexes Total number of indexes defined in the database

Total Size of Indexes Total amount of used space of all indexes defined in the database

Oldest REORG Check Date and time of the oldest execution of the job REORGCHKfor alltables

Latest REORG Check Date and time of the latest execution of the job REORGCHK for alltables

The job to collect the database and tablespace history and the job to collect the history oftables and indexes are triggered by the standard performance collector jobSAP_COLLECTOR_FOR_PERFMONITOR. You can display the schedule of these two jobs inthe DBA Planning Calendar by choosing Jobs DBA Planning Calendar on theDatabase tab page of the DBA Cockpit. From the Category dropdown list, you choose DBCollectors. The default setting is All Actions.

Caution

Calculating table values with outdated statistics can result in inaccurate values. To calculateupdate statistics including the calculation of table sizes, use the DBA Planning Calendar[page 255].

End of the caution.

5 Space

November 2010 153

5.2 Space: Automatic Storage Note

For database releases up to and including DB2 V9.5, this function is only available if youenabled your database for automatic storage management during the SAP systeminstallation.

End of the note.

You can access information about automatic storage file systems of the database by callingthe DBA Cockpit and choosing Space Automatic Storage on the Database tab page ofthe DBA Cockpit. The Automatic Storage screen appears displaying all the storage paths thatare available for the storage management of the database.

For each storage path, the following information is displayed:

Column Description

Partition Number of database partition

Storage Path Full path name

FS ID ID of the related file system

FS Free Size (GB) Free size in GB that is available in the file system

FS Total Size (GB) Total size in GB that is available in the file system

State

State of the path


Not in Use

In Use

DROP Pending

Maintaining the List of Storage PathsIf you want to add or delete a storage path, choose the Change pushbutton. The list layoutchanges and only the information about Partition and Storage Path is displayed.

You can do one of the following:

Add one or more storage path(s) as follows:

1. Choose the Add pushbutton.

For each storage path to be added, enter the complete name and pressEnter.

2. Choose the Execute pushbutton.

5 Space

154 November 2010

Delete a storage path as follows:

1. Select a storage path and choose the Delete pushbutton.


Note

Up to and including DB2 V9.5, you can only delete rows that you hadpreviously added.

End of the note.

In the Generated SQL Statement area, all the generated SQL statements to be executed aredisplayed. This area is automatically filled and refreshed as soon as you apply changes to thestorage path list. To switch back to display mode, choose the Display pushbutton.

Note

As of DB2 V9.7, you can enable a database, which was originally created without automaticstorage, for automatic storage management by adding storage paths on the AutomaticStorage screen. This means that after having created the storage path(s), you can convertnon–automatic storage tablespaces to automatic storage tablespaces as described in Space:Tablespaces [page 156].

End of the note.

5.3 Space: DatabaseYou can access information about space consumption of your database by calling the DBACockpit and choosing Space Database on the Database tab page of the DBA Cockpit.

Monitoring the space that is consumed by the database does not only require that you checkthe current space consumption but also that you consider the progress of the space growth toanswer questions such as the following:

Is data continuously growing and is it predictable that the database runs out ofspace?

Did archiving operations or reorganizations successfully reduce the spaceconsumption?

Can I identify any short-term growth that is related to specific activities of anapplication, such as client copy or mass inserts of data to BW?

Note

To monitor data on the Database screen, you have to make sure that the data collectorframework (DCF) is set up correctly. If the DCF is not available or wrongly set up, a warningis displayed including a link to the Collector Configuration screen where you can perform therequired steps.


End of the note.

5 Space

November 2010 155

FeaturesThe Database screen provides the following:

A selection area where you specify filter criteria for the monitoring data

An overview table displaying the retrieved monitoring data and providing the spaceconsumption at the end of the selected time period

An option to break down all history data that was collected for the selectedmonitoring data during the specified time frame

ProcessTo analyze the data provided on this screen, you proceed as follows:

1. You identify the time period where you expect major changes in space consumption.


3. In case of a multi partitioned system, you can do one of the following:

o To retrieve a general snapshot, you set the partition selection to All and youdo not drill down by partitions or tablespaces.

o To retrieve a more detailed snapshot, you drill down the selection by partitionor by tablespace.

Note

If you want to drill drown by tablespace, you can restrict the result set bylimiting it to special tablespaces.

End of the note.

4. To refresh the monitoring data, you choose the Apply pushbutton.

5. To display detailed history data, you select a line in the overview table. The data isdisplayed in the History Details content area.

6. To isolate the time frame during which the problem occurred and to analyze thespace growth in more detail, you use the data displayed in the History Details contentarea.

5 Space

156 November 2010

5.4 Space: TablespacesYou can access information about space for tablespaces by calling the DBA Cockpit andchoosing Space Tablespaces on the Database tab page of the DBA Cockpit.

During the installation of your SAP system, you specified one of the following options for themaintenance of tablespaces:

Automatic Storage

DB2 automatically allocates and extends tablespace containers in the file system.

DMS/SMS Tablespaces

You manually allocate containers for tablespaces. The extension of thecorresponding containers can be performed either manually or automatically.

Depending on your choice, the corresponding tab page is available on the Tablespacesscreen.

Automatic Storage TablespacesIf your database is enabled for automatic storage management, the following information isdisplayed about all tablespaces that are part of automatic storage management:

Column Description

Tablespace Name Name of the tablespace

Partition Number of the database partition (only displayed in a multi partitiondatabase)

Contents Contents of tablespace, for example, any data or temporary data

TS State Status of tablespace, for example, Normal or Load Pending

KB Total Total space in KB used by the tablespace

Page Size Size of a page in bytes

No. Containers Number of containers

KB Free Total amount of free space

High-Water Mark(KB) Indicates the maximum value of used pages reached

Percent Used Used space in relation to available space

Pending Free Pages Number of free pages that are pending

5 Space

November 2010 157

DMS/SMS TablespacesRegardless whether you have chosen automatic storage management tablespaces ormanual maintenance of DMS/SMS tablespaces during the SAP system installation, thefollowing information is displayed for all DMS/SMS tablespaces that are maintained manually:

Column Description


Partition Number of the partition (only displayed in a multi partition database)

TS Type Type of tablespace, for example, DMS or SMS

Contents Contents of tablespace, for example, any data or temporary data

TS State Status of tablespace, for example, Normal or Load Pending

KB Total Total space in KB used by the tablespace

Page Size Size of a page in bytes

No. Containers Number of containers

KB Free Total amount of free space

High-Water Mark (KB) Indicates the maximum value of used pages reached

Percent Used Used space in relation to the available space

AUTORESIZE Indicates if the tablespace is enabled for automatic resizing

Pending Free Pages Number of free pages that are pending

Displaying Technical Details of a Tablespace

Note

The following information applies to automatic storage management and DMS/SMStablespaces.

End of the note.

To display detail information about the tables or indexes of a tablespace, choose a line in theoverview table. In the Tablespace Details area of the Tablespaces screen, the following tabpages are displayed:

Technical Settings

Storage Parameters

Containers

5 Space

158 November 2010

In addition, the following information is displayed for each selected tablespace:

Field Description

Tablespace Maintenance

Name Name of the tablespace

Database Partition GroupName of the partition group where the selected tablespace isdefined

A partition group defines a set of partitions.

Space

TotalTotal space in KB

This information is not displayed when creating tablespaces.

UsedFill level of the selected tablespace as a percentage


FreeFree space in KB


Technical SettingsThe following information is displayed on the Technical Settings tab page:

Field Description

ContentsDescribes the type of data that is stored in the tablespace, forexample, regular data, large objects, temporary user objects, ortemporary system objects

Size of I/O Units Displays the page and extent size in KB, and the number of pages tobe prefetched

Space Managementby

Displays if the space of the tablespace containers is managed by, forexample, the database (DMS), the file system (SMS), or automaticstorage management

Note

If the AUTORESIZE Enabled checkbox is selected,tablespace containers are automatically extended using thefile systems where the containers are located.

If you are using automatic storage tablespaces, theAUTORESIZE Enabled checkbox is selected by default andcannot be deselected.

5 Space

November 2010 159

Field Description

Continuation ofSpace Managementby

If the Reclaimable Storage Enabled checkbox is selected, thetablespace is enabled for reclaimable storage. This meansthat unused extents can be released to the system for reuse.Tablespaces that have been created with DB2 V9.7 or higherdo have this property.

End of the note.

Disk Performance

Displays information about disk performance, such as:

Overhead

Displays I/O controller overhead and disk seek and latencytime in milliseconds. This value is used to determine the costof I/O during query optimization.

Transfer Rate

Time to read one page into memory in milliseconds. Thisvalue is used to determine the cost of I/O during queryoptimization.

File System Caching

The value displayed indicates the use of file system cachingas follows:

o YES

File system caching has been explicitly enabled usingthe FILE SYSTEM CACHING clause of the CREATE orALTER TABLESPACE statement.

o NO

File system caching has been explicitly disabled usingthe FILE SYSTEM CACHING clause of the CREATE orALTER TABLESPACE statement.

o OS

No explicit file system caching clause has beenspecified. Therefore, the default of the file system isused.

Recovery Dropped tables in the specified tablespace may be recovered usingthe RECOVER TABLE ON option of the ROLLFORWARD command.

Buffer PoolBy default, the buffer pools are displayed that match the page size ofthe tablespace. If required, you can add a new buffer pool. For moreinformation, see Maintaining Buffer Pools [page 221].

For more information about technical settings, see the IBM documentation SQL Reference.

5 Space

160 November 2010

Storage ParametersFor tablespaces that are completely managed by automatic storage management or thathave at least AUTORESIZE enabled, the following values are displayed on the StorageParameters tab page:

Field Description

Settings

Initial Size Initial space allocated when a tablespace is created

Size

Current Size Displays the current size

Last Resize Date and time of last automatic resize operation

Last Resize Terminated withSQL Error

Date and time when the automatic resize operation failed

Note

This field only appears if the last automatic resizeoperation failed.

End of the note.

The SQL error is displayed in the lower half of theTablespaces screen.

ContainersThis tab page provides information about the containers of the selected tablespace.

Displaying the Content of a TablespaceTo display detail information about the tables or indexes of a tablespace, select a line in theoverview table and choose the Contents pushbutton. The following information is displayed inthe Tables of a Tablespace content detail area:

Column Description


Schema Name of the schema

Name Name of the table or index

Type Type of object, for example, index, primary index, or table

Maintaining TablespacesYou can maintain tablespaces, for example, Change, Add, or Delete tablespaces.

For more information, see Maintaining Tablespaces.

5 Space

November 2010 161

5.4.1 Maintaining TablespacesUsing the tablespace list on the Tablespace screen, you can maintain tablespaces as follows:

Change tablespace and container settings

Add new tablespaces

Delete tablespaces

As of DB2 V9.1, you can convert a regular tablespace to tablespace of type LARGE

As of DB2 V9.7, you can start and stop the reduction of the high-water mark as wellas rebalance the tablespace.

Changing a Tablespace1. On the Tablespace screen, select a tablespace and choose the Change pushbutton.

The Change Tablespace dialog box appears where you can change the followingsettings:

Field Description

TechnicalSettings

Prefetch Size Number of pages to be prefetched

OverheadI/O controller overhead and disk seek and latency time in milliseconds

You can use this value to determine the cost of I/O during queryoptimization.

Transfer RateTime to read one page in milliseconds

You can use this value to determine the cost of I/O during queryoptimization.

Buffer Pool

Name of the allocated buffer pool

Note

You can enter only buffer pools that match the page size of thetablespace.

End of the note.

5 Space

162 November 2010

File SystemCaching

You can activate or deactivate file system caching.

Note

As long as neither the FILE SYSTEM CACHING nor the NO FILE SYSTEMCACHING clause has been specified, the default caching options of theunderlying file system type are used. The first use of any of these optionsexplicitly sets this value. You cannot fall back to the default behavior.

End of the note.

Dropped Tables Selecting this checkbox enables to you recover dropped tables using theRECOVER TABLE ON option of the ROLLFORWARD command.

StorageParameters

AUTORESIZEEnabled

Enable this option if you want to allow DB2 to automatically enlargetablespace containers using the file system where the containers arelocated.

Maximum Size

You can enter one of the following values:

o NONE

There is no maximum size limit. In this case, you allow DB2 toextend containers until they occupy all file systems where thecontainers are located

o An absolute value in KB

This value defines an upper threshold that shall not be exceeded byautomatic extensions

Note

This field is valid only if the AUTORESIZE Enabled option isselected.

End of the note.

Increase Size

Size in KB or in percent by which the tablespace is extended if it hasbecome full

You can specify an absolute value in KB or a relative percentage.

Note

This field is valid only if the AUTORESIZE Enabled option is selected.

End of the note.

5 Space

November 2010 163

Containers

(Optionallyavailable)

If a tablespace is not managed by automatic storage management, you can addor delete containers as follows:

o To add containers, choose the Add Container pushbutton.

The system automatically suggests a default path where the containeris located. However, you can modify that path by manually editing theline.

Caution

Adding or changing containers might result in rebalancing, which has aheavy impact on system performance.

End of the caution.

At least one container must be available for each partition. If you areusing a multi partition database, you need to add containers for allpartitions of the corresponding partition group. If you have to changecontainer sizes, we recommend that you enter an appropriate value inthe Resize all containers to field to ensure a balanced distribution ofdata on the different containers.

Caution

Different container sizes might result in bad performance of thedatabase.

End of the caution.

o To delete containers, select one or more lines in the table andchoose Delete.

2. To confirm your entries, choose the Execute pushbutton.

Adding a Tablespace1. On the Tablespace screen, choose the Add pushbutton.

2. In the Add Tablespace dialog box, specify a name and a partition group.

Recommendation

We recommend that you use uppercase letters for the tablespace name. Usinglowercase letters or special characters makes accessing the selected tablespacewith the DB2 command line processor less comfortable.


3. Enter the technical settings. By default, the system displays SAP's recommendations.

4. Add containers.

If you are using a multi partition database, you must add containers for all partitionsof the corresponding database partition group.

5 Space

164 November 2010

Caution

This step does not apply to tablespaces managed by automatic storagemanagement.

End of the caution.


Deleting a TablespaceOn the Tablespace screen, select a tablespace and choose the Delete pushbutton.

Caution

You cannot delete tablespaces that are still used by the SAP system, that is, if they arerelated to some data class. You must delete the data class before deleting the tablespace.

End of the caution.

Converting a Regular Tablespace to LARGEBy default, DB2 V9.1 uses large object tablespaces. If you upgraded your database from DB2UDB Version 8 to DB2 V9.1, you can convert your regular tablespaces to large objecttablespaces. To do so, select a tablespace in the overview table of the Tablespace screenand choose the Convert to Large pushbutton.

After having confirmed the conversion, the conversion job is scheduled as a background jobin the DBA Planning Calendar.

Reducing the High-Water Mark (HWM) of a TablespaceAfter major table reorganizations or deleting and archiving operations, free space in atablespace is not necessarily released directly to the file system.

To release free space, you can lower the high-water mark as follows:

1. On the Tablespace screen, select a line in the overview table and choose theReduce HWM pushbutton.

2. In the Reduce High-Water Mark dialog box, you can do one of the following:

o To have DB2 automatically determine the minimum size that can be reached,choose the Reduce Until Minimum radio button.

o To manually specify the size of the free space of a tablespace to bereleased, choose the Reduce radio button.

By default, the unit of reduction is KB. You can, however, switch to MB, GBor to %.


The reduction process starts asynchronously in the background.

To monitor the progress of reduction, you can check the TS State column in the overviewtable. If the column shows the value High-water mark reduction in progress, select thecolumn to see a detail view of the reduction progress.

5 Space

November 2010 165

Stopping the High-Water Mark ReductionTo stop an ongoing high-water mark reduction, select the appropriate tablespace in theoverview table of the Tablespace screen and choose the Stop HWM pushbutton.

Rebalancing a TablespaceRegular and large tablespaces that are managed by automatic storage management have tobe rebalanced if the following applies:

You created new containers on recently added storage paths.

A container and its content has to be distributed to the remaining containers.

If a database was converted to automatic storage by adding storage paths, thetablespaces still reside in the old containers and do not yet have containers in theautomatic storage database.

For the first two cases, the rebalancing process is automatically started. If a database wasconverted to automatic storage, however, you have to manually start the rebalancing processby selecting a tablespace in the overview table and choosing the Rebalance pushbutton.

After the rebalancing process has been started, data is moved from the containers of thedropped storage paths to the containers on new storage paths. The rebalancing process runsasynchronously in the background and does not affect the availability of data.

To monitor the rebalancing process, check the TS State column in the overview table. If thiscolumn shows any of the values Reverse Rebalance, Forward Rebalance or DMS rebalanceris active, select the TS State column to see a detail view of the rebalancing progress.

For each partition, the following data is displayed:

Column Description



Mode

The rebalancer mode can be one the following

No Rebalance:

The rebalancer process has finished on this partition.

Reverse Rebalance:

Data movement starts at the high-water mark extent and movesin reverse order through the tablespace, ending with the firstextent in the tablespace.

Forward Rebalance

Data movement starts with the first extent in the tablespace andends with the high-water mark extent.

5 Space

166 November 2010

Extents Processed Number of tablespace extents that have already been moved to thenew location

Extents Remaining Number of tablespace extents that still need to be moved

Last Extent Moved Number of the last extent that was moved

Priority Priority with which the rebalancing process is running in the database

Restart Time Time when the rebalancing process was restarted after it had beenpaused or stopped

Start Time Time when the rebalancing process was first started

Progress (%) Displays the progress of the reduction process in percent

More InformationConfiguration: Data Classes [page 245]

5.5 Space: ContainersYou can access information on containers by calling the DBA Cockpit and choosing Space

Containers on the Database tab page frame of the DBA Cockpit.

The following information is displayed on the Containers screen:

Column Description


Partition Number of the partition (only displayed in a multi-partition database)

Stripe Set Number of the strip set the container belongs to

Container Name Name of the container in which the tablespace is located

Type Type of the container, for example, disk or file

KB Total Total size of the container in KB

Pages Total Total amount of pages

Accessible Indicates whether the container is accessible (YES) or not (NO)

FS ID File system ID

FS Free Size (KB) Free space in the file system in KB

To display detail information about a container, choose a line in the overview table. For moreinformation, see Space: Tablespaces [page 156].

5 Space

November 2010 167

Maintaining ContainersYou can maintain tablespace containers by selecting a line in the table on the Containerscreen and choosing the Change, Add, or Delete pushbutton. For more information abouthow to maintain container settings, see Maintaining Tablespaces [page 161].

5.6 Space: File Systems Note

This function is not available for systems that are monitored using a remote databaseconnection.

End of the note.

You can access information about file systems by calling the DBA Cockpit and choosingSpace File Systems on the Database tab page of the DBA Cockpit.

The information displayed on the File Systems screen helps you to determine how much freespace is available in your file systems to extend tablespaces.

For DB2 UDB Version 8.2 up to and including DB2 V9.1 Fix Pak 5, the following informationis displayed:

Column Description

Partition Number of the partition (only displayed if you are using a multi-partition database)

File System NameName of the file system

Both local and NFS file systems are displayed.

KB Total Total size of the file system in KB

KB Used Total amount used of the file system in KB

Percentage Used Used percentage of total size of the file system

KB Free Total amount free of the file system in KB

Percentage Free Free percentage of total size of the file system in KB

Inodes UsedNumber of inodes used

Inodes are needed to save files in the file system. For each directoryof files, a minimum of one inode is used.

Inodes Used (%) Percentage of inodes used

5 Space

168 November 2010

As of DB2 V9.1 Fix Pak 6, the following information is displayed:

Column Description

Partition Number of the partition (only displayed if you are using a multipartition database)

Mount Point Location in the OS directory structure where the file systemappears

KB Total Total size of the file system in KB

KB Used Total amount used of the file system in KB

Percentage Used Used percentage of total size of the file system

KB Free Total amount free of the file system in KB

Percentage Free Free percentage of total size of the file system in KB

File System Type File system type

Device Name Name of the device

Block Size Block size of the file system

5.7 Space: Tables and IndexesYou can access data about tables and indexes by calling the DBA Cockpit and choosing

Space Tables and Indexes <Option> on the Database tab page of the DBA Cockpit.

To be able to analyze space with regard to tables and indexes, you have to answer thefollowing questions:

Which are the largest table and indexes in the system?

Which tables and indexes do I need to reorganize regarding space reclaim andperformance degradation?

How can I save space using DB2 or SAP-specific compression features?

To answer these questions, you have to collect the appropriate data about tables first.Typically, there are several thousand tables in an SAP environment. For performancereasons, it is not possible to analyze data that is retrieved on demand. Therefore, data iscontinuously collected by background jobs of the data collection framework (DCF), whichallows a faster evaluation of data that had been collected before by background jobs of theDCF. In addition, not only current data is available but also historized data.

5 Space

November 2010 169

Note

If the DCF is not set up properly, however, data cannot be evaluated.

End of the note.

FeaturesThe following subset of task areas is available:

Top Space Consumers

You can use the information on this screen to identify the top space consumers inyour database for a specified time period.

REORG Candidates

You can use the information on this screen to identify tables that have beenrecommended for a reorganization.

Compression Status

You can use the information on this screen to check the compression status of atable or if a table would be a suitable candidate for compression.

Virtual tables

You can use the information on this screen to check whether or not a table can bevirtualized or materialized to save space.

5.7.1 Tables and Indexes: Top Space ConsumersOn the Top Space Consumers screen, you can access information about the largest tables ofyour database.

Note

The Top Space Consumers screen requires the data collection framework (DCF) to be set upcorrectly. If the DCF is not available or wrongly set up, an appropriate warning is displayedincluding a link to the Collector Configuration screen where you can perform the requiredsteps. For more information, see Data Collection Framework: Collector Configuration [page248].

End of the note.

5 Space

170 November 2010

FeaturesThe Top Space Consumers screen provides the following:

A selection area where you specify filter criteria for the collected data

An overview table displaying the retrieved history data

This overview table also includes a subset of space-relevant data reflecting the lastset of values that was collected during the selected time period.

An option to break down all history data that was collected for the selectedmonitoring data during the specified time frame.

ProcessTo be able to analyze the space situation in your database, you proceed as follows:

1. You identify the time period where you expected a major impact on spaceconsumption of your tables, for example:

o Time periods with archiving and REORG activities

o Mass-processing of application data

o Installation of new application functions


Note

If you are using a multi partition database system and you want to retrieve a generalsnapshot, you set the partition selection to All and you do not filter by partition. Toretrieve a more detailed snapshot, you can drill down the selection by partitions.

If a single partition or a subset of partitions shows deviations compared to othermembers, you can also restrict the partition selection. Deviations are usually anindication for a bad partitioning key.

End of the note.

3. To refresh the result set, you choose the Apply Selection pushbutton.

4. To display detail information about the growth of a table over time, you select theappropriate entry in the overview table. The data is displayed in the History Detailsarea.

5. To display further details of the selected table, you select a line in the overview tableand choose the Detailed Table Analysis pushbutton. You are directed to the Space

Single Table Analysis screen.

For more information about the data provided on the Single Table Analysis screenand how to evaluate it, see Analyzing and Maintaining a Single Table [page 177].

5 Space

November 2010 171

5.7.2 Tables and Indexes: REORG CandidatesOn the REORG Candidates screen, you can access information about tables that theREORGCHK tool recommends to be reorganized.

Note

By default, all tables with REORG recommendations are displayed. You can, however,filter thedata to be displayed by specifying the schema name and the table name.

End of the note.

The following information is displayed on the REORG Candidates screen:

Column Description

Schema Name Name of the table schema


Total Table SizeTotal table size

This value is the summary of all DATA, LONG, LOB, and XML pages overall database partitions

Log. Index Size Total size of all indexes over all database partitions

REORG Table Indicates if a table reorganization is required.

REORG Index Indicates if only an index reorganization is required.

Check Date Date of last REORGCHK

Check Time Time of last REORGCHK

5.7.3 Tables and Indexes: Compression StatusThe Compression Status screen provides information about tables that are alreadycompressed, or that are candidates for compression.

The following tab pages are available on the Compression Status screen:

Compressed Tables

Displays all tables that are already compressed

Compression Candidates

Displays all tables where space could be saved by using compression

5 Space

172 November 2010

Note

As of DB2 V9.7, index compression is available and supported by the DBA Cockpit.

End of the note.

Compressed TablesOn this tab page, all tables meeting at least one of the following requirements are displayed:

The table is enabled for data compression and contains compressed records.

The indexes of a table are enabled for index compression and are compressed

Column Description

Table Schema Name of the table schema


Data Compression If the table is enabled for data compression, this checkbox isselected.

Index Compression If the index of the selected table is enabled for index compression,this checkbox is selected.

Savings (MB)Total savings of space

This includes all savings regardless, whether they are caused bydata or index compression

Total SizeTotal size of the table

The value displayed is the sum of DATA, LONG, LOB, XML, andindex pages over all database partitions,

Savings (%) Percentage of savings

Last Check Date Last check date

Last Check Time Last check time

Compression CandidatesOn this tab page, tables that meet at least one of the following requirements are displayed:

A table is already compressed but more space could be saved by recompressing itbased on a better compression dictionary

A table that is enabled for data compression but still contains compressed recordsthat are not yet compressed

5 Space

November 2010 173

A table whose indexes are not yet enabled for index compression

A table whose indexes are compressed but more space could be saved byrecompressing the table

Column Description

Table Schema Name of the table schema


Data Compression If row compression is enabled, this option is selected.

Index Compression If index compression is enabled, this option is selected.

Estimated Savings(MB)

Total savings of space that can be achieved

This includes all savings regardless, whether they are caused bydata or index compression.

If the table is already compressed, then the value displayed doesnot represent the new total savings but the additional savings.

Total Size Total size of table if the compression would be performed

Estimated Savings (%) Percentage of estimated (additional) savings

Last Check Date Last check date

Last Check Time Last check time

Displaying Details about the Compression Status of a TableYou can display details about the compression status of a table by choosing a line in theoverview table.

Note

The compression results are based on checks that have been performed before in thebackground. These checks evaluate statistics data that was gathered by the RUNSTATSutility. In case of missing or incomplete statistics data, the calculated check results can beinaccurate. In this case, an appropriate message is displayed. To display more details,choose Show more details. You are redirected to the Single Table Analysis screen where youcan do further analysis.

For more information, see Analyzing and Maintaining a Single Table [page 177].

End of the note.

5 Space

174 November 2010

The following information is displayed in the Compression Status Details detail area:

Field Description

Summary

Schema Name Name of database schema


Total Size Total size in KB of the table (including indexes)

Total Table Size Total size in KB of the table

Total Index Size Total size in KB of the index

Data Compression If this checkbox is selected, data in this table is compressed

Index Compression If this checkbox is selected, the index of this table iscompressed

Current Savings

Total Total amount of savings in KB for this table (includingindexes)

Total Compression Ratio Total compression ratio in percent for this table

Data Total amount of savings in KB for the data of this table

Data Compression Ratio Total compression ratio in percent for the data of this table

Index Total amount of savings for all indexes of this table

Index Compression Ratio Total compression ratio in percent for all indexes of thistable

Estimated Savings

Total Total amount of estimated savings in KB of this table(including indexes)

Total Compression Ratio Estimated total compression ratio in percent

Data Amount of estimated savings of data in KB

Data Compression Ratio Estimated data compression ratio in percent

Index Amount of estimated savings in KB for all indexes

Index Compression Ratio Estimated index compression ration

5 Space

November 2010 175

Field Description

Additional Savings afterCompression

Total amount of savings in KB if the table would becompressed again

Check Date Date when table was last checked

Check Time Time when table was last checked

Scheduling a Compression JobTo realize the estimated space savings, the affected tables need to be reorganized asfollows:

1. On the Compression Candidates tab page, select all tables that you want tocompress and choose the Compress pushbutton.

2. In the Schedule Job dialog box, you specify when you want the compression job torun:

o To run the job immediately, choose the Start Immediately in the Backgroundradio button.

o To schedule the job at a certain day and time, choose the Schedule radiobutton and specify an appropriate date and time.

3. To schedule the compression job, choose OK.

The appropriate REORG jobs are scheduled in the DBA Planning Calendar where youcan view the progress of the compression job.

Note

Depending on the required actions to perform the compression, there can beseparate REORG jobs for table and for indexes.

End of the note.

Refreshing the Compression StatusSince compression information is not collected by the data collection framework (DCF) on aregular basis because of performance reasons, you must run compression checks manuallyas follows:

1. On the Compression Status screen, choose the Start Compression Check…pushbutton.

2. In the Schedule Compression Check dialog box, you specify when you want thecompression check job to run:

o To run the job immediately, choose the Start Immediately in the Backgroundradio button.

o To schedule the job at a certain day and time, choose the Schedule radiobutton and specify an appropriate date and time.

5 Space

176 November 2010

3. To schedule the compression job, choose OK.

A job is scheduled in the DB2 administrative task scheduler (ATS).

You can view view the progress of the compression check job either under JobsScheduled DB Tasks or in the DBA Planning Calendar where you choose DB

Collectors from the Category dropdown list.

5.7.4 Tables and Indexes: Virtual TablesAn SAP system contains thousands of empty tables consuming a lot of space in the DB2tablespaces. These empty tables also generate an additional load on database administrationtasks and autonomic features, for example, automatic RUNSTATS and automatic REORG.

Each empty table uses:

One EMP extent

One data extent

Two extents for the index object

One page for each index

Two extents for LONG field object

Four extents for LOB object

An empty table with a primary key requires 5 to 11 extents, which translates into 160 KB to352 KB on a tablespace with a page size of 16 KB and with an extent size of 2. To save thisunnecessary allocated space, you can replace these empty tables with views, which arecalled virtual tables in this context. On the first WRITE operation on such a virtual table, thisvirtual table is automatically replaced with a table by the SAP system.

On the Virtual Tables screen, the following tab pages are available:

Virtual Tables

Contains a list of all virtual tables that exist in your SAP system. To materialize asingle or multiple tables, select one or more tables and choose the Materializepushbutton.

Candidates for Virtualization

Displays a list of tables that are candidates for being dropped and re-created asvirtual tables. If you choose the Convert Empty Tables pushbutton, a background jobis scheduled that checks each table for the following:

o Whether it is empty

o Whether it is not volatile

o Whether it does not have a partitioning key

o Whether it does not use MDC tables

Tables that meet these conditions are dropped and re-created as virtual tables.

5 Space

November 2010 177

Note

The use of virtual tables is transparent to the ABAP Dictionary.

End of the note.

Caution

Before you drop tables and re-create them as virtual tables, make sure that you have readSAP Note 1151343.

End of the caution.

5.8 Analyzing and Maintaining a Single TableBy analyzing and maintaining single tables, you can optimize tables and indexes to:

Save disk space by releasing unused space or by activating the DB2 compressionfeatures

Improve access to a table by keeping statistics up-to-date or by reorganizingfragmented tables or indexes

You can access detailed information about a single table and maintain table statistics bycalling the DBA Cockpit and choosing Space Single Table Analysis on the Databasetab page of the DBA Cockpit.

FeaturesThe Single Table Analysis screen provides the following areas:

A selection area, where you specify the schema and name of the table to beanalyzed

A summary area that provides an extract of important key figures and statusinformation of the specified table

Tab pages with detail information that is relevant for tables or indexes

In the summary area, the following information is displayed:

Field Description

Size

Total Table Size

Total table size

This is the summary of all DATA, LONG, LOB, andXML pages over all database partitions

Total Index Size Total size of all indexes over all database partitions

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1151343&_NLANG=en&_NVERS=0

5 Space

178 November 2010

Field Description

Size

Number of Indexes Number of indexes defined on the selected table

Administrative Actions

RUNSTATS Status

Status of the statistics


Statistics available

No Statistics available

VOLATILE Table Without Statistics

Unwanted Statistics for VOLATILE Table

REORG Status Indicates whether and how a REORG should beperformed

Compression Status

Indicates whether and how the table is compressed

Note

A table or index is assumed to be compressed if thefollowing applies:

In the system catalog, the table or index isenabled for compression.

The data or index pages have beencompressed by performing an appropriatereorganization.

End of the note.

5 Space

November 2010 179

Savings by Compression

Note

The following fields are only relevant ifthe compression status is accordingly.That is, if the Compression Status tabpage displays that a table or at least itsindex is compressed.

End of the note.

Current Compression RatioCurrent percentage of all savings for row and indexcompression compared to the total size of all DATA,LONG,LOB, XML, and index objects

Current SavingsCurrent total savings of space

This value includes all savings regardless whetherthey were caused by data or index compression.

Estimated Compression Ratio

Compression ratio that would be reached aftercompression

Note

This value is only displayed if a compression checkhas already been performed.

End of the note.

Estimated Savings Savings that would be reached after a compression

Additional Savings after Compression Additional savings after compression for tables thathave already been compressed

The following tab pages are available on the Tables and Indexes Details screen providingdetail information about tables or indexes:

System Catalog

Table Structure

Indexes

This tab page contains an overview list of all indexes and provides integrated tabpages with detail information about, for example, system catalog, structure andstatus of the index, as well as information about the compression status andREORGCHK.

5 Space

180 November 2010

Table Status

Compression Status

REORGCHK

ActivitiesTo optimize tables and indexes, you can use the following pushbuttons on the Single TableAnalysis screen:

RUNSTATS

Schedules a RUNSTATS job for a single table using the DBA Planning Calendar. Formore information, see Updating Statistics [page 269].

Note

To decide if statistics are out-of-date, you can check the statistics time. Alternatively,you can count the number of entries in the table by choosing the Count pushbutton tocompare the real number of records with the Cardinality field on the System Catalogtab page.

End of the note.

REORG

Schedules a REORG job for the table using the DBA Planning Calendar. For moreinformation, see Reorganizing Tables [page 272].

Compression Check

Schedules a job that checks whether a table would benefit from compression

Caution

The Compression Check job is expensive and can considerably decrease the systemperformance. We, therefore, recommend that you schedule this job at a time with alow system workload and not in dialog mode.

End of the caution.

Compression On/Off

Switches the compression status of a table or index.

Note

The term compression is used here as a synonym for both data and indexcompression.

End of the note.

5 Space

November 2010 181

The Compression Options dialog box appears displaying the current compressionstatus of the table, that is, if compression is enabled or disabled, and if acompression dictionary exists. Depending on the status, you can choose between theappropriate actions, such as:

Action Description

Enable Compression Switches the compression attributes for the table and its indexes on

Enable Compressionand Run REORG

Switches the compression attributes on and schedules a REORG jobthat compresses the table data and its indexes

Run REORG toRemove Dictionary

Schedules a REORG job with the RESET DICTIONARY option for atable for which the compression attribute was switched off

Disable Compression Switches the compression attributes off

Disable Compressionand Run REORG

Switches the compression attributes off and schedules an REORG thatuncompresses table and index data

Run REORG toRebuild Dictionary

Schedules a REORG job that rebuilds a dictionary on whichcompression is based for an already compressed table

This is recommended if a new compression check indicates a bettercompression ratio or if the compression attributes were switched onbut the table had not yet been reorganized.

Run REORG to BuildDictionary

Schedules a REORG job for a table where the compression attributeswere switched on but the table and indexes have not yet beencompressed.

Note

Before you enable compression, we recommend that you check the possible savingsby starting a compression check using the Compression Check pushbutton.

End of the note.

VOLATILE On/Off

Changes the VOLATILE attribute of a table

Note

If you set the VOLATILE attribute, the table is no longer processed by automaticRUNSTATS.

End of the note.

5 Space

182 November 2010

5.8.1 Single Table Analysis: System CatalogThe System Catalog tab page provides the following information that is available from thesystem catalog entry of the selected table:

Field Description

SpaceManagement

Data Tablespace Name of the tablespace where the data pages of the table are stored

Index Tablespace Name of the tablespace where the index pages of the table are stored

Free SpaceReserved

Percentage of each page to be reserved for future inserts

A value of -1 indicates that the DB2 default value is used.

Technical Attributes

VOLATILE

Indicates whether the table is flagged as VOLATILE in the systemcatalog

If the table is flagged as VOLATILE, statistics are not gathered by DB2’sautomatic RUNSTATS. In addition, statistics data (if available) is not usedby the DB2 optimizer.

Note

Newly created tables and tables that were dropped or re-created duringan upgrade or a table conversion are always marked as VOLATILE aslong as valid statistics available are not yet available.

End of the note.

Pooled, Clustered,or Import Table

Caution

The information displayed only applies to SAP ABAP systems only.

End of the caution.

Indicates whether the table is defined as a pooled table, a cluster or, animport or export table in the ABAP Dictionary

DistributionStatistics

Indicates whether the table has distributed statistics

If this value is selected, further details about column distribution valuesare available on the tab page Table Structure.

5 Space

November 2010 183

Statistics Data

LastRUNSTATS Date and time of the RUNSTATS

Cardinality Number of data records in the table

Counted RowsNumber of rows that have been counted by a SELECT(*) statement

This information is only displayed if you choose the Count pushbutton.

Deviation

Deviation of the number of rows provided by RUNSTATS in the systemcatalog from the number of rows provided by a SELECT COUNT(*)statement

This information is only displayed if you choose the Count pushbutton.

OverflowRecords

Number of records that have overflowed

Records overflow when a data record is updated and the new data record islarger than the old one, or when a column is added to a table. Thepercentage of overflow records is used as a decision criteria for REORG (seeF1 formula on the REORGCHK tab page)

No. of PagesWith Data: Number of pages containing data

Total Numberof Pages Total number of pages in the table

RUNSTATSProfile

If a RUNSTATS was executed using the PROFILE option, this profile isdisplayed. The profile is the same as the RUNSTATS command that wasexecuted with the SET PROFILE option.

Note

If a profiles exists, it is used by automatic RUNSTATS and therefore theresulting statistics can deviate from the default setting for statistics. Inaddition, if you manually execute a RUNSTATS, you have to make sure thatyou update statistics by using the profile or by explicitly choosing anothertype of statistics.

End of the note.

Compression

ValueCompression Indicates whether value compression is enabled for the table

RowCompression Indicates whether the table is enabled for row compression

5 Space

184 November 2010

Average Length of Compressed Rows Average length of compressed records in bytes

Average Compression Ratio by Row Average compression ratio by row

Average Length of Compressed Rows FromTotal Number of Rows

Average length of all rows (compressed anduncompressed) in bytes

Approximate Percentage of Pages Saved

Percentage of pages saved by compression

Note

Only data pages are taken into account.

End of the note.

5.8.2 Single Table Analysis: Table StructureThe Table Structure tab page provides the following information:

Column Description

DB Column No. Number of the column in the database

DB Column Name Name of the column in the database

DB Type Data type of the column in the database

DB Length Length of the column in the database

The following information is only displayed for the local system and if the table is defined as atransparent table in the ABAP Dictionary:

Column Description

SAP Column Name Name of the column defined in the ABAP Dictionary

SAP Key Column is part of the primary key defined in the ABAP Dictionary

SAP Type Data type of the column defined in the ABAP Dictionary

SAP Length Length of the column defined in the ABAP Dictionary

5 Space

November 2010 185

If the statistics for the table have been gathered using the WITH DISTRIBUTION option, thefollowing information is displayed:

Column Name Name of the column to which the statistics apply

Seq. NoIf the Type column contains the value F, the value n in this columnidentifies the nth most frequent value. If the Type column contains thevalue Q, n in this column identifies the nth quantile value.

Value Data value as a character literal

Value Count

If the Type column contains the value F, this is the number of occurrencesof the Value column. If the Type column contains the value Q, this is thenumber of rows whose value is less than or equal to the value in the Valuecolumn.

No. of DistinctValues

If the Type column contains the value Q, this is the number of distinctvalues that are less than or equal to the value in the Value column.

Type

Specifies how to interpret the displayed values


F

Indicates the frequency value

Q

Quantile value

5.8.3 Single Table Analysis: IndexesThe Indexes tab page provides a list of all indexes that are defined on the table summarizingthe following information:

Field Description

Index Schema Name of the index schema


5 Space

186 November 2010

Unique Rule

Rules for index uniqueness


D

Permits duplicates

U

Indicates index uniqueness

P

Implements the primary key

Index Type

Type of index


BLOK

Block index

CLUS

Clustering index that controls the physical placement ofnewly inserted rows

DIM

Dimension block index

REG

Regular index

XPTH

XML path index

XRGN

XML region index

XVIL

Index over XML column (logical)

XVIP

Index over XML column (physical)

Statistics Time Date and time of last RUNSTATS

5 Space

November 2010 187

Together with the summary information, there are detail tab pages displaying all informationthat is related to the currently selected index. By default, the data of the first index isdisplayed. To view the details of another index, select a table from the list.

Note

If there is only one index, the summary list does not appear.

End of the note.

5.8.3.1 Indexes: System CatalogThe integrated System Catalog detail tab page on the Index tab page provides the followinginformation about the selected index(es):

Field Description

Index

Name Name of the index

Schema Schema of the index, which is usually the user who created the index

TypeType of index

For more information, see Single Tables Analysis: Indexes [page 185].

Unique Rule Rules for index uniqueness

Last Used

Date when the index was last used by any DML statement or when itwas used to enforce referential integrity constraints

Note

If the index is used on an HADR standby database, this column is notupdated. The default value is 0001-01-01. This value is updatedasynchronously.

End of the note.

Technical Attributes

Free SpaceReserved

Percentage of free space reserved in the index pages

This free space is taken into account by the LOAD and REORG utilitiesof DB2.

5 Space

188 November 2010

Compression

Note

This field is only available as of DB2 V9.7.

End of the note.

Indicates whether the index is enabled for compression

Reverse ScansSupported Indicates whether the index supports reverse scans

Statistics Data

Last RUNSTATS Date and time of last RUNSTATS

Number of Leaves Number of index leaves

Number of Levels Number of index levels

Sequential Pages Number of index leaves that are physically located on the hard diskand that are sorted by index without large intervals between them

DensityRelative density of the sequential pages as a proportion of the totalnumber of index pages

100% is the optimum value.

Cluster RatioDegree of index fragmentation

A value of 100% means no fragmentation and this is the optimal value.

Cluster FactorFiner measurement of the degree of clustering

If statistics are not collected or if the index is defined on a nickname, avalue of -1 is displayed.

Cardinality

Cardinality of the index

This value might be different from the cardinality of the table forindexes that do not have a one-to-one relationship between the tablerows and the index entries.

First Key Cardinality Number of different values in the first column of the index

First 2 KeyCardinality Number of different values in the first two columns of the index

First 3 KeyCardinality Number of different values in the first three columns of the index

5 Space

November 2010 189

First 4 KeyCardinality Number of different values in the first four columns of the index

Full Key Cardinality Number of different values in all columns of the index

5.8.3.2 Indexes: Index StructureThe integrated Index Structure detail tab page on the Index tab page provides the followinginformation:

Column Description

Position Position of the column in the index

Order

Sorting order of the column


A

Data is sorted in ascending order

D

Data is sorted in descending order

DB Column Number Number of the column in the database

DB Column Name Name of the column in the database

DB Type Data type of the column in the database

DB Length Length of the column in the database

Note

The following information is only displayed for the local system and if the table is defined as atransparent table in the ABAP Dictionary:

Column Description

SAP Column Name Name of the column defined in the ABAP Dictionary

SAP Type Data type of the column defined in the ABAP Dictionary

SAP Length Length of the column defined in the ABAP Dictionary

End of the note.

5 Space

190 November 2010

5.8.3.3 Indexes: Index Status

Note

The following information is only available as of DB2 V9.7.

End of the note.

The integrated Index Status detail tab page on the Index tab page provides the followinginformation:

Field Description

Partition Database partition number

Data Partition ID

Note

This field is only available if the related table is using data partitioning.

End of the note.

Data partition ID

CompressionAttribute

State of the COMPRESSION attribute of the index


Yes

Index compression is enabled

No

Index compression is not enabled

Index Partitioning

Partitioning characteristic of the index


N

Non partitioned index

P

Partitioned index

Blank

Index does not reside on a partitioned table

Index RequiresRebuild Indicates whether the index requires to be rebuilt

5 Space

November 2010 191

Large RIDs

Indicates whether the index is using large row IDs (RIDs), that is, 4-bytepage number, 2-byte slot number


Yes

The index is using large RIDs.

No

The index is not using large RIDs

Pending

The table where the index is defined supports large RIDs, thatis, the table resides in a large tablespace. The index for thetable or data partition, however, has not yet been reorganizedor rebuilt. Therefore, the table is still using 4-byte RIDs, and thetable or index has to be converted to use large RIDs.

Index Compressed

Physical index format


Yes

Index is in compressed format

No

Index is in uncompressed format

Note

If the physical index format does not match the compression attribute,you have to reorganize the index to convert the index to the definedformat.

End of the note.

Logical Size Amount of disk space in KB that is logically allocated for the index

Physical Size Amount of disk space in KB that is physically allocated for the indexes

Index ID Identifier for the index

Note

If the index is defined on a table that is partitioned or using data partitioning, the index statusis separately available for each partition or data partition.

End of the note.

5 Space

192 November 2010

5.8.3.4 Indexes: Compression Status

Note

This information is only available as of DB2 V9.7.

End of the note.

The integrated Compression Status detail tab page on the Index tab page provides thefollowing information:

Field Partition


Data Partition ID

Data partition ID

Note

This field is only available if the related table is using datapartitioning.

End of the note.

Compression

State of the COMPRESSION attribute on the index

Yes

Index compression is enabled

No

Index compression is not enabled

Index Compressed

Physical index format

Yes

Index is in compressed format.

No

Index is in uncompressed format.

If the physical index format does not match the compressionattribute, an index reorganization is required to convert the index.

5 Space

November 2010 193

Saved Pages

Note

This value is the same for each entry of an index or index partitionfor each database partition in a DPF environment.

End of the note.

If the index is not physically compressed (that is,INDEX_COMPRESSED is N), the displayed value represents theestimated percentage of leaf pages saved, as if the index wereactually compressed.

If the index is physically compressed (that is, INDEX_COMPRESSEDis Y), the displayed value reports the PCTPAGESSAVED value fromthe system catalog view (either SYSCAT.INDEXES orSYSCAT.INDEXPARTITIONS).

For more information, see Indexes: System Catalog [page 187].

Saved Leaf Pages

Note

This value is the same for each entry of an index or index partitionfor each database partition in a DPF environment.

End of the note.

If the index is not physically compressed (that is,INDEX_COMPRESSED is N), the displayed value represents theestimated number of leaf pages saved as if the index were actuallycompressed.

If the index is physically compressed (that is, INDEX_COMPRESSEDis Y), the displayed value reports the calculated number of leafpages saved. This calculation is based on the PCTPAGESSAVED andNLEAF values from the system catalog view (eitherSYSCAT.INDEXES or SYSCAT.INDEXPARTITIONS).

If either PCTPAGESSAVED or NLEAF are invalid values (-1), thisvalue is also set to -1.

For more information, see Indexes: System Catalog [page 187].

Time of Collection Date and time of the last compression check for this index

Note

If the index is defined on a table that is partitioned or using data partitioning the index statusis available for each partition or data partition separately.

End of the note.

5 Space

194 November 2010

5.8.3.5 Indexes: REORGCHKThe integrated REORGCHK detail tab page on the Index tab page provides the followinginformation:

Field Description

Summary Brief description which kind of REORG is recommended according tothe recommendations for this index

Data Partition Name

Note

This field is available only if the related table is using datapartitioning.

End of the note.

Name of the data partition

F4: Cluster Ratio Index size divided by allocated space

F5: Index Size /Allocated Space Index size divided by allocated space as a percentage

F6: No. Entries / No.Poss. Entries Number of deleted entries in relation to total entries in index

F7: Ratio of DeletedIndex Entries Number of deleted entries in relation to total entries in index

F8: Ratio of DeletedIndex Leafs Number of deleted tree leafs in relation to total tree leafs of index tree

Cardinality

Number of index entries in the index

For some indexes, this value can be different from table cardinality.For example, the index cardinality on XML columns might be higherthan the table cardinality.

Number of Pseudo-Deleted RIDs Number of pseudo-deleted RIDs.

Note

As of DB2 V9.7, the REORGCHK information for indexes of tables with data partitioning isavailable per data partition. In this case, the data is displayed in list format.

End of the note.

5 Space

November 2010 195

5.8.4 Single Table Analysis: Table StatusThe Table Status tab page provides the following information:

Field Description


Data Partition ID

Data partition ID

Note

This field is only available if the related table is using the datapartitioning feature (DPF).

End of the note.

Physical Size

Data Objects

Amount of disk space in KB that is physically allocated for thetable

For tables using multi dimensional clustering (MDC), the valuedisplayed includes the size of the block map object. Thedisplayed value represents the physical size of the base tableonly. Space that is consumed by LOB data, long data, indexes,and XML objects is reported by other fields as described in thefollowing.

Long Objects Amount of disk space in KB that is physically allocated for longfield data in a table

LOB Objects Amount of disk space in KB that is physically allocated for longfield data in a table

XML Objects Amount of disk space in KB that is physically allocated for XMLdata in a table

Index Objects Amount of disk space in KB that is physically allocated for theindexes

Logical Size

Data Objects

Amount of disk space in KB that is logically allocated for the table

For MDC tables, this size includes the logical size of the blockmap object. This size represents the logical size of the base tableonly. Space that is consumed by LOB data, long data, indexes,and XML objects is reported by other fields described in thefollowing.

5 Space

196 November 2010

Long Objects Amount of disk space in KB that is logically allocated for long fielddata in a table

LOB Objects Amount of disk space in KB that is logically allocated for long fielddata in a table

XML Objects Amount of disk space in KB that is logically allocated for XMLdata in a table

Index Objects Amount of disk space in KB that is logically allocated for theindexes

REORG

Inplace REORG Status

Current status of an inplace table reorganization on the table


ABORTED

The inplace table reorganization has status PAUSED butis unable to resume. A STOP is required. For moreinformation, see Utilities: Inplace Table Reorganization[page 143].

EXECUTING

The inplace table reorganization is currently beingexecuted.

NULL

This value only appears if no inplace reorganization hasbeen performed on the table.

PAUSED

The inplace table reorganization currently pauses andcan be resumed again. For more information, seeUtilities: Inplace Table Reorganization [page 143].

REORG Pending

Indicates whether a REORG is pending for the table

This state is possible for ALTER operations like DROPCOLUMNthat require an offline reorganization of the table

Number of ALTEROperations

Number of ALTER operations after which a reorganization isrequired and that have been performed against this table sincethe last reorganization

5 Space

November 2010 197

Reclaimable MDC Space

For an MDC table in a DMS tablespace, this value indicates theamount of disk space that can be reclaimed by running theREORG command with the RECLAIM option.

For any other table, the value is zero.

Indexes Require Rebuild Indicates whether an index requires rebuilding

Other Technical Attributes

Large RIDs

Indicates if a table is using large row IDs (RIDs) (4-byte pagenumber, 2-byte slot number)


YES

The table is using large RIDs.

NO

The table is not using large RIDs.

PENDING

The table supports large RIDs (that is, the table is in alarge tablespace) but at least one of the indexes for thetable has not yet been reorganized or rebuilt. Therefore,the table is still using 4 byte RIDs, which means that thetable or indexes have to be converted.

Large Slots

Indicates whether the table is using large slots (which allowsmore than 255 rows per page)


YES

The table is using large slots.

NO

The table is not using large slots.

PENDING

The table supports large slots (that is, the table resides ina large tablespace) but an offline table reorganization ora table truncation operation has not yet been performed.Therefore, the table is still using a maximum of 255 rowsper page.

5 Space

198 November 2010

Blocks Pending CleanupIndicates the number of blocks pending cleanup for MDC tables.

For tables that do not use MDC, this value is always 0.

Type of Statistics

Indicates how the statistics were generated


System fabricated

Statistics are gathered by the system without a table oran index scan.

These statistics are stored in-memory and are differentfrom the statistics that are stored in the system catalog.This is a temporary state and finally full statistics aregathered by DB2 and are stored in the system catalog.

System asynchronously gathered

Statistics are gathered asynchronously by the system.

The statistics have been collected automatically by DB2by a background process and stored in the systemcatalogs.

System synchronously gathered

Statistics are gathered synchronously by the system.

User gathered

Statistics are gathered by the user.

Undef

Unknown type of statistics or information that is notavailable for the current database release

Current Dictionary Size Current size of compression dictionary in bytes

Index Type

Indicates the type of indexes that are currently in use for the table


1

Appears if type-1 indexes are being used

2

Appears if type-2 indexes are being used

5 Space

November 2010 199

Availability

Available

Describes the status of the table


No

The table is not available and all other output informationthat relates to the size and state is 0.

YES

The table is available.

Note

Rollforward through an unrecoverable load makes a tableunavailable.

End of the note.

Read Access Only If the table is read-only, the value is YES. Otherwise, the value isNO.

No Load RestartThe value YES indicates that the table is in partially loaded statethat does not allow a load restart. Otherwise, the value NO isreturned.

If the table is partitioned or using data partitioning the table status is available for eachpartition or data partition separately. In this case, an overview list that contains a subset ofthe information described before, is displayed first. To view the full details, you can select anentry in the list. By default the first entry is displayed.

Note

The physical sizes returned consider full extents allocated for the appropriate object andinclude the Extent Map Page (EMP) extents for objects created in DMS tablespaces.

The logical size is the amount of space that is known for this table. It might be less than theamount of space that is physically allocated to hold object data for the table, for example, incase of a logical table truncation. The logical size returned considers full extents that arelogically allocated for the object and, for objects created in DMS tablespaces, an estimate ofthe EMP extents.

End of the note.

5 Space

200 November 2010

5.8.5 Single Table Analysis: Compression StatusThe Compression Status tab page provides the following information:

Field Description


Data Partition ID

Note

This field is available only if the related table is using datapartitioning

End of the note.

Data partition ID

Dictionary

Compression

State of the COMPRESS attribute on the table


Y

Row compression attribute is set to yes.

N

Row compression attribute is set to no.

Built By

Code path taken to build the dictionary


INSPECT

The dictionary was built using the INSPECTROWCOMPESTIMATE command.

LOAD

The dictionary was built using the LOAD INSERT orREPLACE commands

NOT BUILT

The dictionary was not built and is, therefore, notavailable.

REDISTRIBUTE

The dictionary was automatically built during aREDISTRIBUTE operation.

REORG

5 Space

November 2010 201

Field Description

The dictionary was automatically built by the REORGRESETDICTIONARY utility.

TABLE GROWTH

The dictionary was built in the course of INSERToperations.

Build Time Date and time when the dictionary was built

Rows Sampled Rows that have been sampled to calculate the compressionresults

Estimated Compression

Saved Pages Estimated amount of pages in percent that will be saved aftercompression

Saved Bytes Estimated amount of bytes in percent that will be saved aftercompression

Dictionary Size Estimated size of compression dictionary in bytes if the table willbe compressed

Expansion Dictionary SizeSize of the expansion dictionary measured in bytes

If a historical dictionary exists, this value is the sum of the currentand historical dictionary sizes.

Average Length ofCompressed Rows Average length of rows if the table will be compressed

In the following cases, compression information is available more than once:

The table is distributed across several database partitions.

The table uses data partitioning

The table contains XML data that is compressed separately from normal DATApages.

If any of these conditions is fulfilled, an overview list containing a subset of the informationdescribed before, is displayed first. To view the full details, you can select an entry in the list.By default, the first entry is displayed.

5 Space

202 November 2010

5.8.6 Single Table Analysis: REORGCHKThe REORGCHK tab page provides the following information:

Field Description

Summary Provides a brief description which kind of REORG isrecommended according to the recommendations for the table

Data Partition Name

Name of the data partition

Note

This field is only available if the related table is using datapartitioning.

End of the note.

F1: Overflow Rows Overflow rows as a percentage

F2: Table Size / AllocatedSpace Table size divided by allocated space as a percentage

F3: Full Pages / AllocatedPages Full pages divided by allocated pages as a percentage

Number of Overflow Pages

Number of records that have overflowed

Records overflow when a data record is updated and the newdata record is larger than the old one, or when a column isadded to a table.

Note

As of DB2 V9.7, the REORGCHK information for tables with data partitioning is available perdata partition. In this case, the data is displayed as list.

End of the note.

6 Backup and Recovery

November 2010 203

6 Backup and RecoveryThe following sections provide information about the available task areas under Backup andRecovery on the Database tab page of the DBA Cockpit:

Overview

Logging Parameters

6.1 Backup and Recovery: OverviewYou can access the Overview screen by calling the DBA Cockpit and choosing Backupand Recovery Overview on the Database tab page of the DBA Cockpit.

The following information is displayed on the Overview screen:

Tab Page Description

DatabaseBackup

Contains information about database backups

In the Selection area, you can specify a date. After applying your selected date, alist of backups since this date is displayed. For more information about adatabase backup, you can double-click an entry. The details are displayed on thetab pages Backup Details, Tablespaces, and Backup Sequences in the contentdetail area.

Log Files Contains information about log files that have been moved from the log directoryto the log archive or to a storage product, such as Tivoli Storage Manager (TSM)

6.2 Backup and Recovery: Logging ParametersYou can access information about logging parameters by calling the DBA Cockpit andchoosing Backup and Recovery Logging Parameters on the Database tab page of theDBA Cockpit.

The Logging Parameters screen appears displaying the Log Directory and the Failover tabpages. These tab pages provide information about the logging parameters that areconfigured, such as the size of log files, the log retain status, or the user exit status.Furthermore, you can check the available space of the file systems where your database logsand the archived database logs are stored.

However, these directories are only displayed if the monitored systems are SAP ABAPsystems.

Caution

In a production system, the User Exit for Logging Status field must be set to YES.

If this is not the case, you risk losing data and the ability to roll forward your database ifserious database problems occur.

7 Configuration

204 November 2010

7 ConfigurationThe following sections provide information about the main task areas that are available underConfiguration on the Database tab page of the DBA Cockpit:

Overview

Database Manager

Database

Registry Variables

Parameter Check

Configuration History

Buffer Pools

Workload Management

Database Partition Groups

Special Tables Regarding RUNSTATS

Automatic Maintenance Settings

Data Classes

Data Collection Framework

Monitoring Settings

7.1 Configuration: OverviewYou can access general information about the database instance by calling the DBA Cockpitand choosing Configuration Overview on the Database tab page of the DBA Cockpit.

The following information is displayed on the Overview screen:

Database Instance Description

Name Name of the database instance

Partitionable Indicates whether or not the current instance is a partitionabledatabase server instance

Number of PartitionsNumber of database partitions

If the database environment is not partitioned, the value is 1.

7 Configuration

November 2010 205

Address Space Size of the current database instance in Bit (32 or 64)

Database Release DB2-internal release number, as it is returned if you use thedb2level command, for example, 03030106

Service Level Service level, as it is returned if you use the db2level command, forexample, DB2® v8.1.1.80

Build Level Build level, as is returned if you use the db2level command, forexample, n041021

PTF Program temporary fix (PTF) identifier, as it is returned if you use thedb2level command, for example, U498350

Fix Pack Fix Pack number, as it is returned if you use the db2level command,for example, 9

For the operating system, the following information is displayed:

Operating System Description

Host Name Name of the system


OS Name Name of the operating system

OS Version Version number of the operating system

OS Release Release number of the operating system

Total CPUs Total number of physical CPUs of the system

Configured CPUs Number of configured physical CPUs of the system

Total Memory (MB) Total amount of memory in the system in MB

Note

If the database is distributed over several partitions, the operating system data is displayed ina table.

End of the note.

7 Configuration

206 November 2010

If the system has been installed as a high-availability disaster recovery (HADR) system, thefollowing additional information is displayed:

HADR Information Description

Connect Status

Current HADR connection status of the database


CONGESTED

CONNECTED

DISCONNECTED

Local Host

Local HADR host name

The value is displayed as a host name string or an IP address string,for example, 1.2.3.4.

Local ServiceLocal HADR TCP service

The value is displayed as a service name string or a port numberstring.

Log GapAverage of the gap between the primary log sequence number (LSN)and the standby log LSN

The gap is measured in bytes.

Primary Log File Name of the current log file on the primary HADR database

Primary Log LSNCurrent log position of the primary HADR database

The log sequence number (LSN) is a byte offset in the log stream ofthe database.

Primary Log Page

Page number in the current log file indicating the current log positionon the primary HADR database

The page number is relative to the log file, for example, page zero isthe beginning of the file.

HADR Syncmode

Current HADR synchronization mode of the database


ASYNC

NEARSYNC

SYNC

7 Configuration

November 2010 207

HADR TimeoutNumber of seconds without any communication from its partnerserver after which an HADR database server considers that theconnection between them has failed

HeartbeatNumber of missed heartbeats on the HADR connection

If the database is in HADR primary or standby role, this elementindicates the health of the HADR connection.

Connect Time

If the database is in HADR primary or standby role, the meaning ofthis field depends on the value of the Connect Status field. Thefollowing values are possible:

CONNECTED

Displays the connection time

CONGESTED

Displays the time when the congestion began

DISCONNECTED

Displays the disconnection time

If there has been no connection since the HADR engine dispatchableunit (EDU) was started, the connection status is reported asDisconnected, and the HADR EDU startup time is used for thedisconnection time.

Since HADR connect and disconnect events occur relatively seldom,the time is collected and reported even if the DFT_MON_TIMESTAMPswitch is off. This element should be ignored if the database's HADRrole is STANDARD.

Remote HostHost name of the HADR remote host

The value is displayed as a host name string or an IP address string,for example, 1.2.3.4.

Remote Instance Name of the HADR remote instance

Remote ServiceRemote HADR TCP service

This value is displayed as a service name string or a port numberstring.

HADR Role

Current HADR role of the database


PRIMARY

STANDARD

STANDBY

7 Configuration

208 November 2010

HADR State

Current HADR state of the database


DISCONNECTED

LOCAL_CATCHUP

PEER

REM_CATCH_PEN

REM_CATCHUP

Standby Log File Name of the current log file on the standby HADR database

Standby Log LSNCurrent log position of the standby HADR database

Log sequence number (LSN) is a byte offset in the log stream of thedatabase.

Standby Log Page

Page number in the current log file indicating the current log positionon the standby HADR database

The page number is relative to the log file, for example, page zero isthe beginning of the file.

7.2 Configuration: Database ManagerYou can access information about the configuration of the database manager by calling theDBA Cockpit and choosing Configuration Database Manager on the Database tabpage of the DBA Cockpit.

On the Configuration: Database Manager screen, the parameter information is displayed as atree structure with the following first-level nodes:

Tree Node Description

Common Common information about the database manager, for example,release level and CPU speed

Diagnostics Information about diagnostics

Default MonitorSwitches Information about the default monitor switches of the database

Security Groups Information about user groups of the database manager

7 Configuration

November 2010 209

SecurityAuthentication

Information about authentications of the database manager and aboutclients

Memory Information about the memory of the database manager

Agents Information about agents

Application RemoteInterface Information about the database application remote interface (DARI)

Sync Point Manager Information about the configuration of the synchronization manager andthe transaction manager

TransactionManager Information about the transaction manager

Network Information about network characteristics such as communicationprotocols

Fast CommunicationManager

Information about the Fast Communication Manager (FCM), that is, theconfigured communication in a multi-partition database

DB2 Discovery Information about the configuration of the discovery mode

OthersSingle parameters that are not accessible to the groups describedabove as well as parameters that are not known by the DBA Cockpit,for example, those of a new database release

For each node, the following information about the respective parameters is displayed:

Column Description

Configuration Parameter Description of the parameter

Technical Name DB2 technical name of the parameter

Current Value Currently active value of the parameter

Deferred Value Value that becomes active after a restart of the database instance

For more information about these parameters, see the IBM DB2 online documentation.

For information about how to maintain the database configuration parameters, seeMaintaining the Database Configuration [page 211].

7 Configuration

210 November 2010

7.3 Configuration: DatabaseYou can access information about the database configuration by calling the DBA Cockpit andchoosing Configuration Database on the Database tab page of the DBA Cockpit.

On the Database screen, the parameter information is displayed as a tree structure. In caseof a distributed database, the number of partitions are displayed on the first level. Otherwise,the first-level tree nodes are as follows:

Tree Node Description

Common Common information about the database, for example, releaselevel and country code

Automatic Maintenance Information about the automatic maintenance switches

Optimization Information about optimization

I/O Information about I/O

Self-Tuning MemoryManager Information about the self-tuning memory manager

Database SharedMemory Information about the memory that is available for the database

Application Memory Information about the memory that is available for the application

Logging Information about log files and logging parameters

Log File Management Information about log file management parameters

Backup & Recovery Information about recovery availability and backups

TSM Information about Tivoli Storage Management (TSM)

Locks Information about locks, for example, the percentage of lock listsper application

Space Information about containers and tablespaces

Applications Information about applications that connect to the database

DB2 Data LinksManager

Information about the DB2 Data Links Manager (DB2 UDB Version8 only)

7 Configuration

November 2010 211

High Availability Information about the system configuration is only displayed if youare running a high availability system.

OthersSingle parameters that are not accessible to the groups describedabove as well as parameters that are not known by the DBACockpit, for example, those of a new database release

For each node, the following information about the respective parameters is displayed:

Column Description

Configuration Parameter Description of the parameter

Technical Name DB2 technical name of the parameter

Current Value Currently active value of the parameter

Deferred Value Value that becomes active after a restart of the database instance

Note

In a multi partition environment, the parameters can vary for each partition.

For more information about how to compare the configuration of several databasepartitions, see Comparing Database Configuration Parameters For Several DatabasePartitions [page 212].

Depending on your database release level, the tree nodes that are displayed canvary, that is, some might not be visible or others might be added.

End of the note.

For information about how to maintain the database configuration parameters, seeMaintaining the Database Configuration [page 211].

For more information about these parameters, see the IBM DB2 online documentation.

7.3.1 Maintaining the Database ConfigurationYou use the following procedure to maintain configuration parameters either on the Databaseor the Database Manager screen in the Configuration area.

Procedure1. Select the parameter that you want to change and choose the Change pushbutton.

The Change Database Configuration Parameter dialog box appears.

2. Enter the new configuration parameter values.

7 Configuration

212 November 2010

Note

Some configuration parameters are enabled for automatic value adjustment. In thiscase, the AUTOMATIC checkbox is displayed. If you select AUTOMATIC, the valueis automatically maintained by DB2.

End of the note.

3. To check your entries, choose the Check pushbutton.

The generated CLP commands that are based on your input are displayed. This areais automatically filled and refreshed whenever you choose the Check pushbutton.


7.3.2 Comparing Database Configuration Parametersfor Several Database PartitionsOn the Database screen, select the database partitions that you want to compare and choosethe Compare pushbutton.

The Database Configuration Adjustment screen appears displaying the databaseconfiguration parameters for the selected database partitions in a table. The values that differare marked blue.

Note

By default, only the parameters that differ from one another are displayed. If you want todisplay all parameters, choose All Parameters from the Filter dropdown list.

End of the note.

7.4 Configuration: Registry VariablesYou can access information about DB2 registry variables by calling the DBA Cockpit andchoosing Configuration Registry Variables on the Database tab page of the DBACockpit. The Registry Variables screen appears displaying the information as a treestructure. Aggregate variables are displayed as a folder that contain all the registry variablesaffected by the aggregate variable.

Note

The variables that are affected when setting an aggregate variable, such as DB2_WORKLOAD,are grouped in folders. If the value of such a variable has been manually overwritten, it ismarked yellow.

End of the note.

7 Configuration

November 2010 213

The Scope variable indicates the level at which the DB2 registry variable acquires its value.These levels are as follows:

Instance

Global

Environment

7.5 Configuration: Parameter CheckYou use the parameter check to check the existing parameterization of a DB2 databaseagainst SAP recommendations. When you access the Parameter Check screen, the SAPparameter recommendations, which are collected in one SAP Note per DB2 version, areautomatically downloaded and checked for the following against the SAP recommendations:

DB2 database manager configuration

DB2 configuration

DB2 registry variables

Buffer pool settings

The checks are performed depending on the current system characteristics, such as theapplication type, the operating system, or the usage of STMM. The parameter check reportsdeviations from the SAP standard recommendations. To correct these deviations, you caneither change the respective parameters or declare the deviations as intended.

Note

A parameter is deviating if its current or its deferred value is different from the SAPrecommendations.

End of the note.

You can access the parameter check screen by calling the DBA Cockpit and choosingConfiguration Parameter Check on the Database tab page of the DBA Cockpit. The

following tab pages are available on the Parameter Check screen:

Deviations Found

Intended Deviations

Check Environment

7 Configuration

214 November 2010

Deviations FoundOn this tap page, the following information about parameters that deviate from the SAPstandard recommendation is displayed:

Parameter type

Parameter name

Member number to which the parameter values apply to

Recommended parameter value

Current parameter value

Deferred parameter value, that is, its value after the database has been restarted

Intended DeviationsOn this tab page, the same information as on the Deviations Found tab page is displayedplus the following:

User that declared the deviation as intended

Time stamp when it was declared as intended

Comment

Note

To display the comment in full length, click the relevant text in the Comment column.

End of the note.

Check EnvironmentOn this tab page, the following system attributes and attribute values that are relevant for theparameter check are displayed in the System Characteristics area:

Attribute Description

DPF

Indicates if the database is using the database partitioning feature (DPF)


NO

In case of a single-partition system

YES

In case of more than one partition

7 Configuration

November 2010 215

BI Indicates whether the database system has BW content

STMM

Indicates if the database system is using STMM


NO

STMM is not enabled for all partitions.

YES

STMM is enabled for all partitions.

MIXED

STMM is only enabled for some partitions but not for all.

OS Indicates the operating system platform

BIT Indicates if the database instances are 32 bit or 64 bit instances

In the Check Configuration area, you are also provided with the number of the SAPparameter note of the underlying DB2 release. You can download the latest version of thisSAP Note by choosing the Download SAP Note pushbutton.

Maintaining ParametersOn the Parameter Check screen, you can perform the following actions:

Declare parameter deviations as intended

Reverse the declared as intended status

Correct parameter deviations

Declaring Parameter Deviations as IntendedIf a parameter value in the SAP recommendations (that is, in the SAP parameter notes) is notvalid for a specific customer situation, you can declare the parameter deviation as intended.By doing so, you avoid that a specific deviation is displayed every time you run the parametercheck tool.

1. On the Deviations Found tab page, select a row from the table and choose theDeclare as Intended menu button.

Note

In a database environment with multiple database partitions, the deviations ofdatabase configuration parameters and registry variables can occur on severalpartitions. When choosing the Declare as Intended menu button, you have to specifyif this operation applies to a single or to all partitions where this parameter deviationwas found.

End of the note.

7 Configuration

216 November 2010

2. In the Comment dialog box, enter a reason why you consider this deviation asintended and choose the Continue pushbutton.

The relevant parameter deviation is moved to the Intended Deviations tab page.

Note

Since the list of intended deviations is stored in a table of the SAPTOOLS schema, the datacollection framework (DCF) must be set up correctly. Otherwise, the Declared as Intendedpushbutton is disabled.

End of the note.

Reversing the “Declared as Intended” StatusDuring a parameter check, it can occur that a deviation that you formerly declared asintended is no longer valid. The status of intended deviations is automatically reversed to notintended in the following situations:

The current parameter value in the monitored system has changed from the value atthe moment when the deviation was declared as intended

The current deferred parameter value in the monitored system has changed from thevalue at the moment when the deviation was declared as intended

The SAP recommendation has changed, that is, the check has been changed sincethe parameter was declared as intended

The DB2 version or the Fix Pack have changed since the parameter was declared asintended

On the Intended Deviations tab page, all parameter deviations that were declared asintended are displayed. If you want to reverse the status of a parameter deviation, select adeviation from the list and choose the Declare as Not Intended pushbutton. As a result, theselected parameter deviation is removed from the Intended Deviations tab page and appearsagain on the Deviations Found tab page.

Note

In a database environment with multiple database partitions, the deviations of databaseconfiguration parameters and registry variables can occur on several partitions. Whenchoosing the Declare as Not Intended menu button, you have to specify if this operationapplies to a single or to all partitions where this parameter deviation was found.

End of the note.

If you want to reverse the status of all deviations on the Intended Deviations tab page to notintended, you can clear the complete list by choosing the Clear List of Intended Deviationspushbutton. As a result, the deviations appear again on the Deviations Found tab page.

7 Configuration

November 2010 217

Correcting Parameter Deviations1. On the Deviations Found tab page, select a deviation from the list and choose the

Correct this Parameter pushbutton.

Note

This function is not available for buffer pools and registry variables. In a databaseenvironment with multiple database partitions, the deviations of databaseconfiguration parameters and registry variables can occur on several partitions.When choosing the Correct This Parameter menu button, you have to specify if thisoperation applies to a single or to all partitions where this parameter deviation wasfound.

End of the note.

The dialog box Change Database Configuration Parameters or Change DatabaseManager Configuration Parameters appears displaying the SAP-recommended valueas default suggestion.

2. Enter the required value and choose the Execute pushbutton.

The parameter changes are tracked in the DBA Cockpit and you can analyze them in theConfiguration History task area under Configuration.

7.6 Configuration: Configuration HistoryYou can access the information about the configuration history by calling the DBA Cockpitand choosing Configuration Configuration History on the Database tab page of theDBA Cockpit.

Depending on the setup of your DBA Cockpit, the Configuration History screen provides datathat was collected with or without DCF support.


Enhanced Configuration History with DCF SupportYou can use the enhanced Configuration History screen to keep track of changes in thedatabase, instance, or registry configuration.

Note

To monitor data on the enhanced Configuration History screen, you have to make sure thatthe DCF is set up correctly. If the DCF is not available or wrongly set up, the relevant warningis displayed including a link to the Collector Configuration screen where you can perform therequired steps as described in Data Collection Framework: Collector Configuration [page248].

The DCF runs the data collector Diag Log, which keeps a local history of specialconfiguration events that are parsed from db2diag.log.

End of the note.

7 Configuration

218 November 2010

In the Selection area, you can specify the time frame for which you want the configurationhistory details to be displayed.


Column Description

Time Stamp Time when the event was triggered

Event Type

Event type that is associated with the configuration change


REGISTRY

DBM_CFG

DB_CFG

DB_CFG_STMM

DDL_BP

DDL_WLM

Object Name Name of the object the event relates to

Old Value If available, the old state or value of the configuration object

Old Flag

If available, the old flag of the configuration change


COMPUTED

AUTOMATIC

None

New Value If available, the new state or value of the configuration object

New Flag

If available, the new flag of the configuration change


COMPUTED

AUTOMATIC

None

Event Info If available, a short description of the configuration change

Invoked by System authorization identifier of the event

7 Configuration

November 2010 219

To display details about a configuration history entry, select the relevant line in the list. TheConfiguration History Details area appears displaying the full log record.

Configuration History without DCF SupportConfiguration history data is only available on this Configuration History screen if you haveselected Collect History Data when configuring your database for remote monitoring. Formore information, see Configuration of Systems for Remote Monitoring [page 36].

This Configuration History screen without DCF support displays current and previous settingsof the DB2 database manager configuration parameters, the DB2 database configurationparameters, and DB2 registry variables together with the respective date of change.

In the Selection area, you can set a time frame for the parameters to be displayed. After youhave applied your selection, the following information is displayed:

Column Description

ParameterType

Defines whether the parameter is a database manager parameter or adatabase parameter

ParameterName

Parameters in upper case indicate that the parameter is modifiable using DB2CLP. Parameters in lower case indicate that the parameter is maintained byDB2 (read-only).

PartitionMonitored partition

Only displayed if you are using a multi-partition database

Date Date of the change

Time Time of the change

ParameterValue Value of the parameter currently set or set in the past

To further refine the parameters to be displayed, you can choose a parameter type from theParameter Type dropdown list.

7 Configuration

220 November 2010

7.7 Configuration: Buffer PoolsYou can access information about available buffer pools by calling the DBA Cockpit andchoosing Configuration Buffer Pools on the Database tab page of the DBA Cockpit.

The following information is displayed on the Buffer Pools screen:

Column Description

Buffer Pool Name Name of the buffer pool

Partition Number of the partition (only displayed if you are using a multi partitiondatabase)

Size (Pages)

Size of the buffer pool in KB

A value of –1 indicates that the default buffer pool size parameter fromthe database configuration is used (parameter BUFFPAGE).

AUTOMATIC indicates that the selected buffer pool is tuned by the DB2self–tuning memory management (STMM).

If one of these special values is displayed and you want to see the realsize of the buffer pool, you can use the buffer pool snapshot [page 88].

Page Size (Byte) Size of one buffer pool page in bytes

To display details about a buffer pool, choose a buffer pool from the list. The followinginformation is displayed in the Buffer Pool Details area:

Technical Settings

Database Partition Groups

Tablespaces

Technical SettingsThe Technical Settings tab page displays the following technical attributes:

Field Description

Size

Default(BUFFPAGE)

The size of the buffer pool has not been set at creation time, and thedefault size as defined in the database configuration parameter BUFFPAGEis used

Automatic The size of the buffer pool is managed by STMM

Fixed StandardSize

The size of the buffer pool is set to a fixed value

This means that this size is set for all partitions except for those withexception entries

7 Configuration

November 2010 221

Field Description

I/O Units

Page Size Size of one page in the buffer pool

Block Size Size of one block for blocked I/O in pages (only displayed if you are usingDB2 UDB Version 8)

Number of BlockPages

Number of pages that are reserved for block I/O usage (only displayed ifyou are using DB2 UDB Version 8)

For all partitions of the selected buffer pool, the following information is additionally displayed:

Column Description


Buffer PoolSize Size of the buffer pool in pages

Exception Indicates whether an exception entry has been defined for this partition thatspecifies a size different from the default size in the Fixed Standard Size field

Database Partition GroupsThe Database Partition Groups tab page displays a list of all database partition groups towhich the buffer pool is related. A buffer pool can be related to all available partitions or to aset of partitions defined by database partition groups. If the buffer pool is not already definedon all partitions, you can select further database partition groups.

TablespacesThe Tablespaces tab page displays a list of all tablespaces that use this buffer pool as wellas the page size of these tablespaces.

Maintaining Buffer PoolsYou can maintain buffer pools, that is, change, add, or delete them as described in thefollowing section Maintaining Buffer Pools.

7.7.1 Maintaining Buffer PoolsUsing the buffer pool list on the Buffer Pools screen, you can maintain buffer pool as follows:

Change buffer pools, that is, add or remove partitions, resize or control the use ofextended storage

Add new buffer pools

Delete buffer pools

7 Configuration

222 November 2010

Changing Buffer Pools1. On the Buffer Pools screen, select a buffer pool from the list and choose the Edit

pushbutton.

2. In the Change Buffer Pool dialog box, you can modify the buffer pool attributes asfollows:

o Change the buffer pool size from Automatic to Fixed and vice versa.

If you select the Automatic radio button or if the Automatic attribute isalready set for the buffer pool, you can set the initial starting size forSTMM.

If you select the Fixed radio button or if the buffer pool is alreadyusing a fixed size, you can set or change the standard size for allpartitions except for those partitions with exception entries.

If you want to create or delete an exception entry for a partition,select or deselect the relevant Exception checkbox in the partitionlist. After you selected the Exception checkbox for a partition, youcan change the buffer pool size (pages).

o If the buffer pool is specified for a set of database partition groups only andnot yet for all database partition groups, you can add database partitiongroups by selecting them in the Database Partition Groups list.

o You can change the block size and the number of block pages.

3. If you want the changes take effect immediately, select the Change Immediatelycheckbox. Otherwise, the changes will take effect after the next restart of thedatabase.


Adding Buffer Pools1. On the Buffer Pools screen, select a buffer pool from the list and choose the Add

pushbutton.

The Add Buffer Pool dialog box appears.

Note

By default, all available partitions that relate to the new buffer pool are listed. Toreduce this list, you can choose the On Selected Database Partition Groups radiobutton in the Database Partition Groups area, and select single database partitiongroups.

End of the note.

7 Configuration

November 2010 223

2. Specify a name for the new buffer pool.

Recommendation

We recommend that you use uppercase letters for the buffer pool name. Usinglowercase letters or special characters makes it less comfortable to access theselected database partition group with the DB2 command line processor.


3. In the Size and I/O Units area, enter the relevant technical settings, such as the pagesize.

4. If the buffer pool is specified for a set of database partition groups only and not yetfor all database partition groups, you can add database partition groups by selectingthem in the Database Partition Groups list.

5. If you want the new buffer pool to be created immediately, select the CreateImmediately checkbox. Otherwise, the newly created buffer pool is created after thenext restart of the database.


Deleting Buffer Pools1. On the Buffer Pools screen, select a buffer pool from the list and choose the Delete

pushbutton.

2. Confirm the deletion.

SQL StatementsIn the Change Buffer Pool and Add Buffer Pool dialog boxes, the generated SQLstatement(s) to be executed are displayed. This area is automatically filled and refreshed assoon as any changes are entered correctly.

7.8 Configuration: Workload ManagementWorkload management is supported as of DB2 V9.5. It lets you distinguish and prioritizedifferent types of work on the database. Workloads identify the submitters of work byconnection properties and assign incoming work to the service classes. You use serviceclasses to monitor and control resource consumption of the different workloads.

Note

Setting up workload management is optional. If no workload management has beenconfigured, the database does not distinguish different types of work as known from previousDB2 releases.

End of the note.

For information about thresholds, see Introduction to DB2 workload management concepts inthe IBM Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.wlm.doc/doc/c0052594.html



7 Configuration

224 November 2010

You can access information about workload management by calling the DBA Cockpit andchoosing one of the following on the Database tab page of the DBA Cockpit:

Configuration Workload Management Workloads and Service Classes

Configuration Workload Management SAP WLM Setup Status

7.8.1 Workload Management: Workloads and ServiceClassesYou use the data provided on the Workloads and Service Classes screen to obtain anoverview of the workload management configuration of the database system. In addition, youcan maintain the priority of service classes and configure the amount of monitoring data thatis collected for each individual service class.

The following tab pages are displayed on the Workloads and Service Classes screen:

Overview

Workloads

Service Classes

OverviewThis tab page provides an overview of all configured workloads, service superclasses, andtheir subordinate service classes on the database system. The hierarchy of service classes isdisplayed using the inheritance arrows that are known from UML diagrams.

WorkloadsThis tab page provides details of all existing workloads as follows:

Column Description

Position Evaluation order that is used for choosing a workload

Workload Name Name of the workload

Enabled

Workload state


Green

The workload is enabled.

Red

The workload is disabled.

7 Configuration

November 2010 225

DB Access Allowed Determines whether or not units of work (UOWs) that are associatedwith the workload are rejected

Service Class Name of the service subclass to which an UOW that is associatedwith this workload is assigned

Parent Service Class Name of the service super class to which an UOW that is associatedwith this workload is assigned

To display additional information, you can select a workload from the list. The following tabpages are displayed in the content detail area:

Workload Details

Displays details about the workload from the system catalog as well as details aboutthe configuration for collecting statistics on the workload

Connection Attributes

Displays all the attributes that associate an incoming activity with the selectedworkload

For an activity to be associated with a certain workload, all the connection attributesof the incoming activity must match the definition of the workload (Boolean AND). If asingle attribute type is specified more than once, this indicates that only one of themmust match the activity (Boolean OR).

Service ClassesThis tab page provides details of existing service classes as follows:

Column Description

Service Class Name of the service class

Enabled

State of the service class


Green

The service class is enabled.

Red

The service class is disabled.

Agent Priority Graphical display of the thread priority of the agents in the serviceclass

Agent Priority(Remarks)

Thread priority of the agents in the service class in relation to thenormal priority of DB2 threads

The value DEFAULT indicates that the thread priority was inheritedfrom the parent service class.

7 Configuration

226 November 2010

Column Description

Prefetch Priority Graphical display of the agents prefetch priority in the service class

Prefetch Priority(Remarks) Prefetch priority of the agents in the service class

Buffer Pool Priority Graphical display of the buffer pool priority in the service class (onlyapplies to DB2 V9.7)

Buffer Pool Priority(Remarks) Buffer pool priority of the service class (only applies to DB2 V9.7)

If you select a service class from the list, the Service Class Details tab page appears in thecontent detail area displaying further details of the service class.

Changing Data Collection Settings of Service ClassesYou can maintain the amount of data that is collected for each individual service class asfollows:

1. On the Service Class Details tab page, choose Change Data Collection.

2. On the Change Data Collection Settings, enter the required data using the dropdownlists in the fields.

Recommendation

We recommend that you choose Collect Base Aggregate Activity Data in theAggregate Activity Data field for all service classes.


3. Save your entries.

For information about possible data collection settings, see ALTER SERVICE CLASSstatement in the IBM DB2 Information Center at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.sql.ref.doc/doc/r0050551.html

Changing Priorities of Service ClassesBy changing agent priorities or prefetch priorities of certain service classes, you can distributedatabase resources among different types of workloads as follows:

1. On the Service Class Details tab page, choose Change Prioritization.



7 Configuration

November 2010 227

2. In the Change Prioritization dialog box, adjust the agent, prefetch, or buffer poolpriority using of the following pushbuttons:

o Increase <Agent or Prefetcher> Priority

o Decrease <Agent or Prefetcher> Priority

o Inherit <Agent or Prefetcher> Priority from Parent Class (DEFAULT)

Resets the priority from its parent service class to the default value.


Caution

If not chosen carefully, changing the agent or prefetch priority can significantly decrease theperformance of some workloads.

End of the caution.

7.8.2 Workload Management: SAP WLM Setup StatusIn addition to the default workloads and service classes that are created automatically duringthe setup of history data collectors in an SAP environment, you can set up additionalworkloads and service classes using the SAP WLM Setup Status screen. The workloadmanagement setup that is supported by the DBA Cockpit is separated into the followingcategories:

SAP enhanced prioritization scheme

SAPTOOLS workload and service class

Priority aging service class

SAP Enhanced Prioritization SchemeIn addition to the workload management setup that is based on the work process types andthat is set up by default for SAP systems as described in Enabling the Data for the DataCollection Framework [page 40], you can create an additional workload and service classusing the enhanced prioritization scheme. This additional workload and service class consistsof one of the following groups:

SAP users

SAP transactions

SAP application servers

You can monitor and prioritize this special group separately from the workloads that arebased on work process types.

If you want to drop the enhanced prioritization scheme, choose the Modify EnhancedPrioritization Scheme pushbutton. In the wizard that appears, choose No enhanced priorityscheme.

7 Configuration

228 November 2010

If you want to drop the enhanced prioritization scheme as well as the workloads and serviceclasses that identify the SAP work process types, choose the Drop SAP Workloads andService Classes pushbutton.

Recommendation

We recommend that you always keep the work process type- based WLM setup to allowmonitoring based on SAP work process types.


SAPTOOLS Workload and Service ClassFor SAP systems, the separation of SAP monitoring tools is set up by default as described inEnabling the Data for the Data Collection Framework [page 40]. If you want to remove theSAPTOOLS workload and service class, you can do so by choosing the Drop SAPTOOLSWorkload and Service Class pushbutton.

If the SAPTOOLS workload and the service class have not yet been created, you can do soby choosing the Set Up SAPTOOLS Workload and Service Class pushbutton.

Priority Aging Service Class

Note

The priority aging feature is only available as of DB2 V9.7.

End of the note.

The priority aging feature lets you change the priority of in-progress activities over time. Youuse priority aging to decrease the priority of longer-running activities so that the throughputfor shorter-running activities stays at a stable level. If the priority aging service class has notyet been created, you can create it by choosing the Set Up Service Class for Priority Agingpushbutton. To drop the priority aging service class, choose the Drop Service Class forPriority Aging pushbutton. To enable priority aging based on defined thresholds, you have toset up corresponding in-service class thresholds as described in Critical Activities: ThresholdConfiguration [page 138].

For more information about the priority aging feature, see the IBM DB2 Information Center at:


7.9 Configuration: Database Partition GroupsYou can access information about available database partition groups by calling the DBACockpit and choosing Configuration Database Partition Groups on the Database tabpage of the DBA Cockpit.



7 Configuration

November 2010 229

The following information is displayed on the Database Partition Groups screen:

Column Description

Database PartitionGroup Name of the database partition group

Partition Number of the partition

Status

Current status of the partition


Status information not available

Partition not in partitioning map; containers not yet created

Partition not in partitioning map; containers created

Partition in partitioning map; containers created

Partition will be dropped after next redistribution

You can display details about a database partition group by selecting it from the list. Thefollowing tab pages are displayed in the Database Partition Group Details area:

Partitions

Buffer Pools

Tablespaces

PartitionsThe Partitions tab page displays the following information:

Column Description

Partition Number of the partition

Status

Current status of the partition


Status information not available

Partition not in partitioning map; containers not yet created

Partition not in partitioning map; containers created

Partition in partitioning map; containers created

Partition will be dropped after next redistribution

7 Configuration

230 November 2010

Buffer PoolsThe Buffer Pools tab page displays a list of all buffer pools that have been defined for theselected database partition group as follows:

Column Description

Buffer Pool NameTotal space in KB

If you create tablespaces, this information is not displayed.

Buffer Pool Size(KB)

Size of the buffer pool in KB

Value –1 indicates that the default buffer pool size parameter from thedatabase configuration is used (parameter BUFFPAGE).

Page Size Size of one buffer pool page in bytes

You can display more details about a buffer pool by selecting it from the list. The detailinformation is displayed in the Buffer Pool Details area below the Database Partition GroupDetails area.

TablespacesThe Tablespaces tab page displays a list of all tablespaces that have been defined for theselected database partition group including their page size in bytes.

You can display more information about a tablespace of a buffer pool by selecting thetablespace from the list. The detail information is displayed in the Tablespace Details areathat appears below the Database Partition Group Details area.

Maintaining Database Partition GroupsYou can maintain database partition groups, that is, change, add, redistribute, or delete themas described in the following section Maintaining Database Partition Groups.

7.9.1 Maintaining Database Partition GroupsUsing the list of database partition groups on the Database Partition Groups screen, you canmaintain database partition groups as follows:

Change database partition groups, that is, add or remove partitions

Add new database partition groups

Delete database partition groups

Redistribute database partition groups

7 Configuration

November 2010 231

Changing Database Partition Groups1. On the Database Partition Groups screen, select a database partition group from the

list and choose the Edit pushbutton.

2. In the Change Database Partition Group dialog box, select new database partitionsto be added, or deselect existing database partitions to be dropped.

3. Confirm your selection by choosing the Execute pushbutton.

Adding New Database Partition Groups1. On the Database Partition Groups screen, choose the Add pushbutton.

2. In the Add Database Partition Group dialog box, specify a name for the newdatabase partition group.

Recommendation

We recommend that you use uppercase letters for the database partition groupname. Using lowercase letters or special characters makes it less comfortable toaccess the selected database partition group with the DB2 command line processor.


3. From the list of available database partitions, select one or more partitions that youwant to add to the new database partition group.

4. Confirm your entries by choosing the Execute pushbutton.

Deleting Database Partition Groups1. On the Database Partition Groups screen, select a database partition group and

choose the Delete pushbutton.

Caution

You cannot delete database partition groups that contain tablespaces that are stillbeing used by the SAP system.

You must delete the tablespaces first.

End of the caution.


7 Configuration

232 November 2010

Redistributing Database Partition Groups

Note

You can only redistribute database partition groups that have the status Partition notin partitioning map; containers created.

End of the note.

1. On the Database Partition Groups screen, select a database partition group andchoose the Redistribute pushbutton.

2. In the Schedule Job dialog box, define if you want to redistribute the databasepartition group immediately or at a later point in time.

SQL StatementsIn the Change Database Partition Group and Add Database Partition Group dialog boxes, thegenerated SQL statement(s) to be executed are displayed. This area is automatically filledand refreshed whenever changes are correctly entered.

7.10 Configuration: Special Tables RegardingRUNSTATSYou can access information about tables with special RUNSTATS characteristics by calling theDBA Cockpit and choosing Configuration Special Tables Regarding RUNSTATS onthe Database tab page of the DBA Cockpit.

There are two categories of tables that are treated by the optimizer in a special way due totheir characteristics:

Tables marked as VOLATILE in the system catalog

A volatile table is a table whose content can vary from a few entries to a very largeamount of entries at lifetime, that is, statistics data is often out-of-date and may resultin wrong access plans by the optimizer. These tables should be marked asVOLATILE and should have no statistics at all.

Tables with RUNSTATS control parameters that are not in accordance with the defaultsettings of the DBA Planning Calendar, for example, special scheduling patterns,different kinds of RUNSTATS, or tables that have a profile that may influenceautomatic RUNSTATS

On the basis of the list displayed, you can check system catalog-related information againstthe DBSTATC control table.

7 Configuration

November 2010 233

The following information is displayed on the Special Tables Regarding RUNSTATS screen:

Column Description


Table Name Name of the database table

VOLATILE


If the table is flagged as VOLATILE, statistics are not used by theoptimizer.

Active

Type of entry in control table DBSTATC


N

No RUNSTATS is run by any DBA Planning Calendar job. Thisstatus corresponds to the VOLATILE attribute of a databasetable, which prevents the query optimizer from using statistics.

R

No RUNSTATS is run automatically by any DBA PlanningCalendar job. The only exception is that you explicitlyschedule a RUNSTATS for the relevant table.

A

RUNSTATS may be run by DBA Planning Calendar jobs.

This information is only relevant if RUNSTATS is performed byDBA Planning Calendar jobs and not by DB2 automaticRUNSTATS.

Profile Indicates whether a RUNSTATS profile was set for the table

RUNSTATS Date Date of the last RUNSTATS in the system catalog table

RUNSTATS Time Time of the last RUNSTATS in the system catalog table

CardinalityNumber of rows as calculated by the last RUNSTATS

(–1 indicates that there are no statistics available)

For more details about a table, choose a table from the list. The Single Table Analysis screenappears providing detailed information about the selected table. For more information, seeAnalyzing and Maintaining a Single Table [page 177].

7 Configuration

234 November 2010

7.11 Configuring Automatic MaintenanceFunctionsUsing DB2's automatic maintenance functions, you prepare the database for automaticadministration. In addition, you should check the settings from time to time to make sure thatthey meet the requirements of your production system.

You can configure the following automatic maintenance functions on the AutomaticMaintenance screen:

Automatic Backup

Automatic RUNSTATS

Automatic REORG

Note

If you enter this task area for the first time, certain settings are preselected based on the DB2default policy.

End of the note.

Procedure1. Call the DBA Cockpit and choose Configuration Automatic Maintenance on the

Database tab page of the DBA Cockpit.

The Automatic Maintenance screen appears displaying the following tab pages:

o General

o Automatic Backup

o Automatic RUNSTATS

o Automatic REORG

Each of these tab pages provides detailed information about the currently selectedsettings for each of the functions as well as general information applying to allfunctions. These tab pages are described in more detail later in this document.

7 Configuration

November 2010 235

2. To configure the automatic maintenance functions, choose the Configure pushbutton.The Configure Automatic Maintenance Functions wizard appears guiding youthrough the following configuration steps:

Step Action

Introduction Provides an overview of the available configuration steps

General

Note

To be able to use the automatic maintenance functions, you must select thecheckbox Automatic maintenance is switched on.

End of the note.

o Specify the maintenance windows during which automaticmaintenance is performed by DB2:

Online Maintenance Window

Time frame with only low activity on the database

Offline Maintenance Window

Time frame with no activity on the database

o Select the required maintenance task, for example,Automatic REORG, for one of the maintenance windows. DB2 thendecides if any action is required and automatically triggers thecorrect action.

Online Window/ OfflineWindow

Note

Since the tab pages for specifying the online and the offline maintenancewindows are identical, they are only described once.

End of the note.

Specify the following parameters:

o Time

o Day of Week

o Day of Month

o Month of Year

Caution

The definition of all time-related parameters is combined by AND. Therefore,a valid maintenance window must meet all definitions.

End of the caution.

7 Configuration

236 November 2010

Backup


o Backup Operation Mode

o Start Conditions

o Backup Media

RUNSTATS


o Configuration Profile

o Table Filter

Note

You can only specify a table filter if you select Custom asConfiguration Profile.

End of the note.

REORG


o Configuration Profile

o Index Reorganization Mode

o Parameters such as the Maximum Table Size, ReclaimSize for MDC Tables, or whether you want to keep thecompression dictionary.

Note

You can only specify the index reorganization mode and otherparameters if you select Custom as Configuration Profile.

End of the note.

SummarySummarizes all actions to be performed

To apply your configuration entries and to exit the wizard, choose theExecute pushbutton.

7 Configuration

November 2010 237

7.11.1 Automatic Maintenance Settings: GeneralSettingsWhen you open the Automatic Maintenance screen, the General tab page is displayed bydefault providing information about the maintenance windows during which automaticmaintenance is performed by DB2.

The maintenance windows are as follows:

Online Maintenance Window

Time frame with only low activity on the database. For example, during an onlinemaintenance window, you can still be connected to the database.

Offline Maintenance Window

Time frame with no activity on the database. For example, during an offlinemaintenance window, neither connections to the database are allowed nor updatesfor tables and indexes while they are being reorganized.

Note

In this context, online and offline does not mean the state of the database itself but the timeframe with only low activity (online) or no activity (offline) on the database. Since the tabpages specifying the online and the offline maintenance windows are identical, they are onlydescribed once.

End of the note.

On the Online Maintenance Window and Offline Maintenance Window tab pages, thefollowing information is displayed:


Automatic maintenance is switched onEnables or disables automatic maintenance

To be able to use the automatic maintenancefunction, this checkbox must be selected.

Online maintenance window is enabled /Offline maintenance windows is enabled

Indicates if the online or offline maintenancewindow was enabled

Time of Automatic Maintenance Indicates if the maintenance window wasspecified directly or inverted

Time Time frame when the automatic maintenancefunction is to be performed

Day of Week Days of the week during which the automaticmaintenance function is to be performed

7 Configuration

238 November 2010

Day of Month

Days of months during which the automatic maintenance function is tobe performed

You can specify days or day ranges that are separated by comma, forexample, 1, 7–10.

Month of Year Months of the year during which the automatic maintenance function isto be performed

Note

To change the settings, choose the Configure pushbutton. For more information, seeConfiguring Automatic Maintenance Functions [page 234].

End of the note.

7.11.2 Automatic Maintenance Settings: AutomaticBackupThe Automatic Backup tab page screen provides the following information:


General

Automatic backupis switched on /off

Enables or disables the automatic backup function

Backup OperationType

Specifies the type of backup (online or offline)

When an online backup is performed, you are still able to access thedatabase during the online maintenance window. When an offline backupis performed within the offline maintenance window, you cannot accessthe database.

Priority

Specifies the priority of the automatic backup over the other automaticmaintenance features such as Automatic RUNSTATS or AutomaticREORG

Note

1 means highest priority.

End of the note.

7 Configuration

November 2010 239

Starting Conditions

Optimize for DatabaseRecoverability

Backups are created more frequently. Therefore, less time isrequired to recover the database.

The following limits apply:

Maximum time between backups: 1 day

Maximum log space used between backups: 10 MB

Balance BetweenRecoverability andPerformance

Indicates the balance between the number of backups and thetime for recovery.


Maximum time between backups: 7 days


Optimize for DatabasePerformance

Fewer backups are created. Therefore, more time to recoverthe database is required.


Maximum time between backups: 30 days


Customize

If you choose this option, you can customize the followingparameters:

Number of full backups is less than

Minimum number of backups

Time since last full backup exceeds <value> days

Maximum time between backups

Log space used since last full backup is more than<value> MB

Maximum log space between two backups

Number of full backups isless than

If the number of backups is less than the specified value, abackup is created.

Time since last full backupexceeds

If the time since the last backup exceeds the specified value, abackup is created.

Log space used since lastfull backup is more than

If the log space exceeds the specified value, a backup iscreated.

7 Configuration

240 November 2010

Backup Media

File SystemThe backup is created in the specified file systems.

If you choose File System, you also have to specify the FilePaths where the backup is to be created.

Tape DeviceThe backup is created on tape.

If you choose Tape Device, you also have to specify theNumber of Parallel Sessions.

TSMThe backup is created and stored in IBM Tivoli StorageManager (TSM).

If you choose TSM, you also have to specify the File Paths.

XBSAThe backup is created using the XBSA API for storing the data.

If you choose XBSA, you also have to specify the Number ofParallel Sessions.

Vendor Library

The backup is created and data is stored using a vendor library.

If you choose Vendor Library, you also have to specify theLocation (that is, a path and file name of the library) and theOptions.

Note


End of the note.

7.11.3 Automatic Maintenance Settings: AutomaticRUNSTATSThe Automatic RUNSTATS tab page provides the following information:


General

Automatic RUNSTATS isswitched on / off Enables or disables the automatic RUNSTATS function

Maintenance Window Specifies that automatic RUNSTATS can only be performed in theonline maintenance window

7 Configuration

November 2010 241


Priority

Specifies the priority of the automatic RUNSTATS over the otherautomatic maintenance features, such as Automatic REORG orAutomatic Backup.

Note


End of the note.

Parameters

SAP Default Criteria forTables Excluded by Policy

If you select this checkbox, you enable the SAP default criteria,that is, no tables are excluded from automatic RUNSTATS by thepolicy filter.

Note

A full editor for these filter criteria is not provided.

End of the note.

In addition, the following information is displayed for tables that are excluded fromRUNSTATS:

Column Description

Tables Excludedfrom RUNSTATS

The excluded tables are divided into the following categories:

Volatile Tables

Volatile tables are always excluded from automatic RUNSTATS.If you expand this node, the volatile tables are displayed.

Tables Excluded by Policy

Within the policy, there are some filter criteria for tables to beexcluded from automatic RUNSTATS. If you expand this node,the excluded tables are displayed.

Schema Name of the schema to which the table belongs

Volatile


If the table is flagged as VOLATILE, statistics are not used by theoptimizer.

Active A value of N indicates whether the table is marked as VOLATILE bySAP

7 Configuration

242 November 2010

Column Description

Profile Indicates whether a RUNSTATS profile was set for the table

RUNSTATS Date Date of the last RUNSTATS in the system catalog table

RUNSTATS Time Time of the last RUNSTATS in the system catalog table

CardinalityNumber of rows as calculated by the last RUNSTATS

(–1 indicates that no statistics are available)

Note


End of the note.

7.11.4 Automatic Maintenance Settings: AutomaticREORGThe automatic REORG checks regularly if tables or indexes require reorganization. This checkis performed by the REORGCHK. The tables are always defragmented during the offlinemaintenance window. You can specify only for indexes if a reorganization is to be performedduring the online or offline maintenance window.

Note

If the index reorganization mode is configured to be performed online and no offlinemaintenance windows has been defined, only online index reorganizations and no tablereorganizations are performed by automatic maintenance.

End of the note.

The following information is displayed on the Automatic REORG tab page:


General

Automatic REORG is switchedon/off Enables or disables the automatic REORG function

Index Reorganization Mode

Specifies a maintenance window for index reorganization

Recommendation

We recommend that you reorganize indexes during the online

7 Configuration

November 2010 243


maintenance window.


Priority

Specifies the priority of the automatic REORG over the otherautomatic maintenance features, such as AutomaticRUNSTATS or Automatic Backup.

Note


End of the note.

Parameters Description

SAP Default Criteria forTables Excluded by Policy

Enables the SAP default filter criteria for tables that are to beexcluded from automatic REORG

That is, all table filters in the policy are disabled and theparameters are changed according to the SAPrecommendations.

Note

A full editor for these filter criteria is not provided.

End of the note.

Use a System TemporaryTablespace with CompatiblePage Size

If you select this option, a copy of the table or index iscreated in the temporary tablespace, and the table or index iscopied to the original tablespace.

Since temporary tablespaces in SAP systems are SMStablespaces, the required space for defragmentation will beavailable after the reorganization.

Recommendation

We recommend that you use a system temporary tablespace.


Maximum Table Size

Specifies the tables that are excluded from the automaticREORG because of their size

Recommendation

We recommend a maximum table size filter of 1,000,000 KB.


7 Configuration

244 November 2010

Reclaim Size forMDC Tables

Specifies whether MDC tables are reorganized and which size limit isused.

Note

This option is only available as of DB2 V9.7.

End of the note.

CompressionDictionary

Specifies whether you want to keep or rebuild the compressiondictionary

A rebuild of the compression dictionary can lead to a bettercompression ratio but implicates a longer REORG runtime.

Recommendation

We recommend that you rebuild the compression dictionary.


In addition, the following information is displayed for tables that are excluded from anautomatic REORG:

Column Description

Tables Excluded from REORG

The excluded tables are divided into the followingcategories:

Tables Excluded by Policy

Within the policy, there are some filter criteria fortables to be excluded from the automatic REORG. Ifyou expand this node, the excluded tables aredisplayed.

Tables Excluded by Size

If you expand this node, the tables with a size largerthan the threshold are displayed.

Determining the table sizes online is much tooexpensive. To obtain the sizes of the tables, youhave to schedule the job REORGCHK for all Tablesin the DBA Planning Calendar.

Schema Name of database schema to which the table belongs

Table Flagged Table to be reorganized

Index Flagged Indexes to be reorganized

Table Size (KB) Size of the table in KB

7 Configuration

November 2010 245

Column Description

REORG Date Date when the table was last reorganized

REORG Time Time when the table was last reorganized

Note


End of the note.

7.12 Configuration: Data Classes Note

This function is only available for SAP ABAP systems.

End of the note.

The technical settings of SAP tables define data classes that need to be related to databasetablespaces.

You can access the list of available data classes by calling the DBA Cockpit and choosingConfiguration Data Classes on the Database tab page of the DBA Cockpit.

On the Data Classes screen, the following information is displayed:

Column Description

State

Green:

No action required

Yellow:

Indicates warnings

Recommendation

We strongly recommend that you take immediate action.


Red:

Indicates errors, immediate action required

The following errors are checked:

Is there a related data tablespace?

7 Configuration

246 November 2010

Column Description

Does the data tablespace exist in the database?

Is there a related tablespace for indexes?

Does the index tablespace exist in the database?

Does the name of the tablespace comply with the namingconventions for the customer namespace?

Is there a description for the data class?

Data Class Name of the data class known to the ABAB Dictionary

Data Tablespace Name of the tablespace where table data is stored

Index Tablespace Name of the tablespace where table indexes are stored

No. of Tables Number of tables within the related data tablespace

No. of Indexes Number of indexes within the related index tablespace

Category Category of the data class

Description Description of the data class

In addition, you can maintain data classes, that is, change, add, or delete them as describedin Maintaining Data Classes.

7.12.1 Maintaining Data ClassesUsing the data class list on the Data Classes screen, you can maintain data classes asfollows:

Change data classes

Add new data classes

Delete data classes

Changing Data Classes1. On the Data Classes screen, select a data class and choose the Edit pushbutton.

2. If required, change the description in the Change Data Class dialog box.

3. Change the tablespace assignment by selecting an entry from the dropdown list inthe Data Tablespace field.

7 Configuration

November 2010 247

4. Save your changes.

Caution

Changing the related tablespaces does not affect already existing tables. It only hasan impact on new tables.

End of the caution.

Adding Data Classes1. On the Data Classes screen, choose the Add pushbutton.

appears.

2. In the Add Data Class dialog box, specify a name for the data class using the namingconventions for customer-defined data classes. If you do not follow these namingconventions, you might receive an error message.

Caution

If you do not define data classes according to the naming conventions, this has animpact on future upgrades of your system.

Such entries are not recognized as customer entries and will be lost during theupgrade.

End of the caution.

Note

You cannot enter a value in the Category field. It always has the value USR.

End of the note.

3. Enter a description.

4. Select a data and index tablespace from the dropdown list.


Deleting Data Classes1. On the Data Classes screen, select a data class and choose the Delete pushbutton.


7 Configuration

248 November 2010

7.13 Configuration: Data Collection FrameworkThe following sections provide information about how to use the data collection framework(DCF) to collect history data of the monitored databases:

Collector Configuration

Setup of Workloads and Service Classes in SAP Environments

Note

The data collection framework is based on pre-defined templates.

For information about these templates, see Maintaining Templates for the DCF [page 42].

End of the note.

7.13.1 Data Collection Framework: CollectorConfigurationThe Collector Configuration screen provides an overview of the state of the installed historydata collectors. You can use this screen to change the configuration of specific datacollectors. Furthermore, you can set up the data collection framework (DCF) using templatesas described in Setting Up the Data Collection Framework (DCF) Manually [page 42].

You can access information about the history data collectors by calling the DBA Cockpit andchoosing Configuration Data Collection Framework Collector Configuration on theDatabase tab page of the DBA Cockpit.

In the central system data area of the Collector Configuration screen, status messages aredisplayed that provide information such as the following:

Tablespace status

If the database is not enabled for automatic storage and the SAPTOOLS orSAPEVENTMON tablespaces are not available, the appropriate messages withdetailed setup information are displayed.

If back-end automatic update is enabled or disabled

By default, the automatic back-end update function is enabled. This means that onceper day, the installed data collection framework is checked. If it needs to be updateddue to SAP code changes or database changes, these updates are performedautomatically.

Which task scheduler is used

By default, the DB2 Administrative Task Scheduler is used to execute the storedprocedures regularly. However, in some DB2 V9.1 scenarios, the DB2 AdministrativeTask Scheduler is not available so that you have to use an external scheduler. If youupgrade the database at a later date to a version that supports the DB2Administrative Task Scheduler, you can migrate the tasks to the DB2 AdministrativeTask Scheduler using the Migrate to DB2 Admin Task Scheduler link.

7 Configuration

November 2010 249

In the content area, the following information is displayed:

Column Description

Data CollectorName of the data collector

Typically, the name refers to the data that is collected, for example, thedata collector Tables stores table-related metrics in the history tables.

Type

Type of data collector

The following collector types are possible:

SAP Data Collection and Preparation (STP)

These data collectors have their own mechanism to calculate thedelta of the different snapshots.

DB2 Event Monitor and Preparation (STP)

A DB2 event monitor is used to store the data in tables.

Cleanup of Message Logs (STP)

The Framework data collector is not a typical data collector type,but a cleanup job for the messages generated by the abovementioned data collector types.

Setup

Indicates the setup status


Green:

The data collector is set up as intended.

Yellow:

The data collector is not set up properly. We recommend that yourepair the data collector.

Red:

The data collector is not set up. Set up the data collectoraccording to the assigned template.

Grey:

The data collector is not set up and the assigned template alsomarks this data collector to be deactivated.

CollectionInterval Schedule of the data collector

7 Configuration

250 November 2010

Event MonitorActive

State of the DB2 event monitor


Green:

The DB2 event monitor is set up as intended.

Yellow:

The DB2 event monitor is not set up properly. We recommend thatyou repair the data collector.

Red:

The DB2 event monitor is not set up. Set up the data collectoraccording to the assigned template.

Grey:

No DB2 event monitor is used by the data collector.

Available Days Availability of the collected data for the given number of days as of now

Days Kept inHistory

Number of days of the sliding history window

The data in the history is deleted after this number of days.

Size on Disk(MB)

Space consumption in the local history of the data that is stored by thedata collector

Errors Number of errors that the data collector has captured and that thescheduler has recorded

Warnings Number of warnings that the data collector has captured and that thescheduler has recorded

Maintaining History Data CollectorsTo maintain history data collectors, that is, for example, to set them up, change, or analyzethem, or to remove data from them, choose a data collector from the list.

In the content detail area of the Collector Configuration screen, the Configuration and DataCollector Log tab pages appear displaying the relevant data collector details.

7 Configuration

November 2010 251

Depending on your setup status, you can proceed with the following maintenance actions:

Action Setup Status Steps to Be Performed

Setting up asingle history datacollector

Grey or red as the datacollector is not set up yet

On the Configuration tab page, choose the SetUp pushbutton.

Note

You must set up the Framework collector beforeall other data collectors.

End of the note.

Repairing a singlehistory datacollector

Yellow as the datacollector is set up butshould be updated orneeds to be repaired

On the Configuration tab page, choose theRepair pushbutton.

Changing a singlehistory datacollector

Green

1. On the Configuration tab page, choosethe Change Settings pushbutton andenter your changes.

2. To apply your changes, choose theApply Changes pushbutton. If you wantto discard your changes, choose theReset Changes pushbutton.

Removing data ofa single historydata collector

Yellow or green

On the Configuration tab page, choose thePrune pushbutton. By doing so, the collecteddata and the generated messages of the datacollector are removed.

Dropping a singlehistory datacollector

Yellow or green On the Configuration tab page, choose the Droppushbutton.

Analyzing a singlehistory datacollector

Yellow or green

On the Data Collector Log tab page, you canchoose between the following pushbuttons:

Show Error Messages

Show Warnings

Show Information Messages

7 Configuration

252 November 2010

7.13.2 Setup of Workloads and Service Classes inSAP EnvironmentsIf the database that is set up for historical monitoring belongs to an SAP system with SAPBasis Release 6.20 or higher and if the database release level is at least DB2 V 9.5, a set ofSAP-specific workloads and service classes is created with the Framework data collector.

Dedicated workloads are created to identify each of the work process types in an SAPenvironment, that is, one workload per SAP work process type. Each of these workloads isthen assigned to its own service class. This setup lets you prioritize and monitor work perSAP work process type. This means that the drill-down capabilities of monitoring data in anSAP environment are improved significantly.

The following work process types are identified in an SAP environment:

ABAP dialog

ABAP batch

ABAP spool

ABAP updater (primary and secondary)

Java (if available)

Note

Since the SAP Enqueue work process is not connected to the database, no workload andservice class is created for this type of work process.

End of the note.

All work coming from outside the SAP system still runs in the DB2 default workload andservice classes.

The following figure provides an overview of the workloads and service classes that arecreated:

Workloads Service SuperclassesService Subclasses

SAP_ABAPDIA_WL

SAP_DIAGNOSTIC_WL

SAP_ABAPBTC_WL

SAP_ABAPSPO_WL

SAP_ABAPUPD_WL

SAP_ABAPUPD2_WL

SAP_JAVA_WL

SAP_ABAPDIA_SSC

SAP_ABAPBTC_SSC

SAP_ABAPSPO_SSC

SAP_ABAPUPD_SSC

SAP_ABAPUPD2_SSC

SAP_JAVA_SSC

SAP_DIAGNOSTIC_SSC

SAP_SC

SAPTOOLS_WL SAPTOOLS_SSC

Overview of Workloads and Service Classes

7 Configuration

November 2010 253

The SAP_DIAGNOSTIC_WL workload as well as the SAP_DIAGNOSTIC_SSC serviceclass are created for SAP-internal use. Currently, no work is executed in this serviceclass.

The SAP_SAPTOOLS_WL workload as well as the SAP_SAPTOOLS_SSC service classare created to separate work that originates from SAP monitoring tools. You canmonitor the SAP_SAPTOOLS_SSC service class to determine the amount of resourcesthat are consumed by SAP monitoring tools such as the DBA Cockpit or thePerformance Warehouse.

The service superclass SAP_SC is only created for structural reasons. No work isexecuted in service superclasses.

In addition to the default workloads and service classes that are created in SAPenvironments, you can set up additional workloads and service classes as described inWorkload Management: SAP WLM Setup Status [page 227].

7.14 Configuring Monitoring SettingsUsing this screen, you can perform the following actions to configure the monitoring settings:

Change the retention periods for history data

This applies only to systems where you have selected Collect History Data whenconfiguring your database for remote monitoring.

For more information, see Configuring Systems for Remote Monitoring Manually[page 37].

Activate the automatic switching of the db2diag.log file

Note

If the DBM configuration parameter DIAGSIZE is set, this function is not available forDB2 V9.7.

End of the note.

Specify a dedicated server for the background processing

Procedure1. Call the DBA Cockpit and choose Configuration Monitoring Settings on the

Database tab page of the DBA Cockpit.

2. On the Monitoring Settings screen, choose the Change pushbutton.

3. Enter your changes in retention time of the statistics in the relevant fields underDatabase and Tablespace Size, Table and Index Size, and Database Performance.

7 Configuration

254 November 2010

4. If you want to switch the db2diag.log file to automatically restrict its size to amanageable value, select the Switch Weekly checkbox.

This means that the db2diag.log file is saved under a new name with a time stampand a new db2diag.log file is created.

5. If you want to collect history data on a dedicated background server, specify a serverin the Server for Data Collection field by choosing a name from the dropdown list.


8 Jobs

November 2010 255

8 JobsThe following sections provide information about the main task areas that are available underJobs on the Database tab page of the DBA Cockpit:

DBA Planning Calendar

DBA Log

Back-End Configuration

SQL Script Maintenance

Scheduled DB2 Tasks

8.1 The DBA Planning CalendarYou use the DBA Planning Calendar to automate database administration actions that haveto be performed regularly. You can schedule operations such as online backups that are thenautomatically performed, and you can check if the operations were successful.

The main function of the DBA Planning Calendar is to define the start times and parametersfor database actions. Since these actions run without administrator interaction, you have tomake sure in advance that the necessary resources are available.

IntegrationThe DBA Planning Calendar is part of the DBA Cockpit. You can start the DBA PlanningCalendar by calling the DBA Cockpit and choosing Jobs DBA Planning Calendar onthe Database tab page of the DBA Cockpit.

FeaturesThe initial screen of the DBA Planning Calendar consists of a Selection area and thecalendar. In the following, both are described in more detail.

The Selection AreaThe Selection area contains all information and parameters to select the set of actions to bedisplayed. You can:

Select the category of an action:

o DBA Actions

These are plannable actions.

o External Actions

These are plannable actions that have not been started via the DBA PlanningCalendar but that have been started manually or by external job schedulers.

8 Jobs

256 November 2010

o All Actions

These are all plannable actions, regardless how they have been scheduled.

o DB Collectors

These are actions that are automatically selected by the system to collectdata, for example, on performance or history and that are only available forRFC-monitored systems.

Select the week to be displayed

The default is the current week. To navigate to another week, use the F4 help.

Select a factory calendar

Specifying a factory calendar only has an impact on the calendar display. Holidaysare the same color as weekend days. It does not result in any restrictions on plannedactions.

The CalendarThe calendar displays all scheduled jobs. The status of each job is indicated using differentcolors. To display the meaning of each color, choose the Legend pushbutton. The followinginformation is displayed:

Color Status Description Action

Light blue Planned The action has not yet started. –

Dark blue Running The action has not yet finished. –

Green Finishedsuccessfully The action has run successfully. –

YellowFinishedwithwarning

The action has finished with awarning.

Check the job log fordetails.

Red Finishedwith error

An error has occurred and the actionwas interrupted.

Check the job log for detailsand reschedule the action.

Dark yellow No longeravailable No more information is available. –

Dark red Schedulingfailed

Scheduling failed, that is, there is nostatus available and the action isoverdue.

–

8 Jobs

November 2010 257

Note

By default, the DBA Planning Calendar appears in display mode. To switch to editing mode,choose the Change pushbutton in the global toolbar.

End of the note.

More Information

Setting Up and Working with the DBA Planning Calendar

Scheduling Typical DBA Actions

8.1.1 Setting Up and Working with the DBA PlanningCalendarThe following sections provide information about how you set up the DBA Planning Calendarinitially and how you perform standard actions, such as:

Creating a Pattern of Actions in the DBA Planning Calendar

Scheduling an Action

Changing an Action

Deleting an Action

Executing an Action

Displaying Scheduled Actions

Troubleshooting

More InformationScheduling Typical DBA Actions [page 264]

8.1.1.1 Creating an Action Pattern in the DBA PlanningCalendarYou need to set up the DBA Planning Calendar because when you start your system for thefirst time, there are no actions planned. The most important thing when setting up the DBAPlanning Calendar is to choose a pattern of actions that covers your regular databaseadministration (DBA) needs and to specify all required action parameters that take account ofany dependencies between actions.

You must also consider that there is a number of database-related jobs (for example,performed by the DB2 scheduler) that are not controlled by the DBA Planning Calendar butwhich you must take into account when scheduling regular actions.

8 Jobs

258 November 2010

Depending on the underlying DB2 version, some of these jobs might be automaticallyperformed by data collectors of the DCF, or by automatic maintenance settings (for example,automatic RUNSTATS or automatic REORG). If, for example, the DCF has been enabled andcorrectly set up, you can view these data collectors on the Collector Configuration screen.For more information, see Data Collection Framework: Collector Configuration [page 248].

If the DCF is not enabled and the SAP history collection is used instead, the following jobsare involved:

Collection of database performance history data done every two hours starting at00:00

Monitoring of database and database manager configuration changes done daily at8.00 am, 01.00 pm, and 7.00 pm

Collection of database and tablespace history data done daily at 7:00 am and 8.00pm

Collection of space history data for tables and indexes done weekly on Sundays at12.00 pm

Caution

Some of the available actions have an impact on database performance andavailability. Check the start and end times of scheduled actions to make sure thatthey do not interfere with each other and that they do not impact other systemactivities.

You cannot perform all required DBA actions from the DBA Planning Calendar or theDBA Cockpit. For more information about actions that you must perform with the SAPsystem down, such as an offline database backup, see the SAP DatabaseAdministration Guide for your database version.

End of the caution.

Optionally, you can configure the back end of the DBA Planning Calendar to be able tocontrol the execution of these background jobs. For more information, see Back-EndConfiguration [page 277].

PrerequisitesBefore you start using the DBA Planning Calendar, you have to check the following:

SAP system authorizations

Check that you have authorization for DBA and background job scheduling, which isprovided by profiles S_RZL_ADMIN and S_BTCH_ALL.

Check that external programs are able to run on the database server so that actionsaffecting the database can be performed from other application servers.

Database system authorizations

Check that actions requiring authorization to connect to the database are permitted.Some actions, such as online backup, require higher levels of authorization.

Before scheduling database backups, see the information on how to back up thedatabase in the SAP Database Administration Guide for your database.

8 Jobs

November 2010 259

Hardware and backup media

Check that you have enough hardware (such as tape drives) and backup media(such as tapes) for the backup strategy you intend to use.

You make sure that the media are initialized and ready so that the operator does nothave to interrupt scheduled backup runs. For example, check that tapes are alreadyin the specified tape drive or tape changer. You might require different tape drives fordatabase backups and log backups.

Procedure1. On the Database tab page of the DBA Cockpit, choose Jobs DBA Planning

Calendar .

Note

By default, the DBA Planning Calendar appears in display mode. To switch to editingmode, choose the Change pushbutton in the global toolbar.

End of the note.

2. Choose the Pattern Setup pushbutton.

The Setup Planning Pattern wizard appears guiding you through the procedure ofsetting up a pattern of recurring actions that cover your regular DBA needs.

Note

Depending on your database version and configuration, a set of recommendedactions is available and some of these actions might be preselected by default. Youmay change this selection set, for example, if you want to use TSM for backup andarchiving instead of backup and archiving to devices.

End of the note.

3. To enter the pattern into the DBA Planning Calendar, choose the Execute pushbuttonon the Summary screen.

4. Exit the wizard.

Caution

When you start using the DBA Calendar in production operation, you must check daily thatscheduled actions have been executed correctly.

End of the caution.

8 Jobs

260 November 2010

8.1.1.2 Scheduling an Action1. To add new actions to the DBA Planning Calendar, you can do one of the following:

o Click a calendar cell.

o Position the cursor on a calendar cell and choose the Add pushbutton.

o Choose Schedule an Action in your Favorites.

The Schedule an Action wizard appears.

2. In the Job Selection step, do the following:

1. Choose the job that you want to schedule from the Action dropdown list.

2. Specify one of the following options:

Option Description

Start Immediately The job starts immediately in the background after you havecompleted the required steps in the wizard.

Start on Specifies the date and time when the action is to start

Start as RecurringAction

Activates the Recurrence step where you can further specifya recurrence pattern for this job as described later on in thissection

3. In the Parameter step, change, or enter the basic parameters for the action.

4. Optional:

If you previously selected the Start as Recurring Action option in the Job Selectionstep, you now have to enter a recurrence pattern in the Recurrence step.

The following table describes the parameters to be specified in more detail:


RecurrencePattern

Interval for the action in weeks, days, or hours

Depending on the selected recurrence pattern, you need to specify the patternin more detail, that is, the days of the week for weekly periods and the hoursof the day for a daily period. The action is repeated at the interval that youenter.

If you select Once only, the action is executed only once.

RecurrenceRange

Range of time where the action recurs, that is, for a specific time interval or fora limited number of occurrences

Caution

The system warns you if there is a conflict with an existing action, but it does notprevent you from inserting the new action.

8 Jobs

November 2010 261

You must decide whether the actions might conflict in terms of database access orperformance. The system does not check for conflicts between actions with identicalstart times but checks for actions within a range of approximately 30 minutes.

End of the caution.

5. On the Summary screen, review the specified parameters and schedule the job bychoosing the Execute pushbutton.

6. Exit the Schedule an Action wizard.

ResultThe schedule of the DBA Planning Calendar is updated.

8.1.1.3 Changing an ActionThis section tells you how to change an action in the DBA Planning Calendar.

Note

If you want to change a recurring action, the changes only affect recurrences of the action inthe future. The action is split into two actions, one describing the old action, and one the newaction.

End of the note.

PrerequisitesThe action to be changed must be in the state Planned (that is, not already executed). If anaction has already been executed, you can only display it. For more information, seeDisplaying Scheduled Actions [page 263].

Procedure1. In the DBA Planning Calendar, click a calendar cell that contains an action.

The Action Description detail area appears displaying the action parameters and, ifavailable, the recurrence pattern.

2. From the Change menu button, choose one of the following options:

o If you want to edit the currently selected occurrence only, choose SelectedOccurrence.

o If you want to change all occurrences of a recurring job, choose AllOccurrences.

The Change Scheduled Action dialog box appears displaying the action parametersand, if available, the recurrence patterns.

3. Apply and save your changes.

8 Jobs

262 November 2010

8.1.1.4 Deleting an ActionThis section tells you how to delete an action from the DBA Planning Calendar.

PrerequisitesIf you want to delete an action from the DBA Planning Calendar, it must be in the statePlanned (that is, not already executed).

Note

If an action has already been executed, you can only display it. For more information, seeDisplaying Scheduled Actions [page 263].

End of the note.

Procedure1. In the DBA Planning Calendar, click a calendar cell that contains the action to be

deleted.

The Action Description detail area appears displaying the action parameters and, ifavailable, the recurrence pattern.

2. From the Delete menu button, choose one of the following options:

o If you want to delete the currently selected occurrence only, choose SelectedOccurrence.

o If you want to delete all occurrences of a recurring job, choose AllOccurrences.

8.1.1.5 Executing an ActionYou might have to reschedule an action, for example, after it has failed or if there is aresource bottleneck that needs immediate reaction.

Procedure1. Click the action that you want to re-execute.

The Action Description detail area of the action appears where you can check theaction parameters.

2. Choose the Re-Execute pushbutton.

ResultThe action is rescheduled starting at the current time.

8 Jobs

November 2010 263

8.1.1.6 Displaying Scheduled ActionsFrom the DBA Planning Calendar, you can view all action-related information. This includes:

Action parameters

Job logs if the action has already run

These logs provide detailed information on the results of an action.

Recurrence patterns

The status of an action is indicated by the color of the calendar cell where an action isinserted.

ProcedureTo display a scheduled action, click a calendar cell that contains an action. The ActionDescription detail area appears displaying scheduling information or the return status of afinished action.

The following tab pages are displayed:

Action Parameters

Displays the parameters of the action

Recurrence

Displays the recurrence patterns and only appears if the action is part of a recurringaction

Job Log

The background processing job log generated by the action is displayed under JobLog. All messages that have been written by the background job are also displayed.

To display long texts, if any are available, double-click a message.

Program Log

Some actions write log files onto the database server. If such a program log exists, itis displayed on this tab page.

8.1.1.7 TroubleshootingSince any action scheduled in the DBA Planning Calendar can fail, you must at least checkthe more critical actions such as database backups. The following steps describe how youcheck whether a job was executed correctly and how to proceed if it failed.

Procedure1. Check the status of the job in the DBA Calendar. The status of a job is indicated by

different colors.

If the job finished successfully, the calendar cell is marked green.

8 Jobs

264 November 2010

2. If the job terminated with a warning, an error, consult the job log.

Note

If there is no job log available, the background job was probably not started. In thiscase, proceed as follows:

1. In your SAP system, call transaction SM37 and display the job overview.

The jobs related to the planning calendar start with the prefix “DBA:”. Thecomplete name of such a job in SM37 contains a short description of whatthe job is about. The following is an example of, for example, a REORG job:

DBA:REORG_TABLE_____@095534/4000.

2. To search for information about possible errors that prevented the job frombeing executed, double-click the respective background job in the overviewlist.

End of the note.

3. Correct the error using the information that you found the job log or in transactionSM37, and reschedule the job in the DBA Planning Calendar.

Make sure there are no conflicts with other scheduled actions before you reschedulethis job.

Note

If you want to completely clean up your jobs, choose the Cleanup pushbutton. This deletes alljobs, all scheduling data, and all related protocol records. It also resets the DBA PlanningCalendar to its initial state.

We recommend that you clean up after an SAP system upgrade or if jobs have becomecorrupt.

End of the note.

8.1.2 Scheduling Typical DBA ActionsAs already described in previous sections, you can use the DBA Planning Calendar toautomate administrative tasks that have to be performed on a regular basis, such as:

Scheduling backups

Archiving log files to tape

Updating statistics

Reorganizing tables

8 Jobs

November 2010 265

Scheduling a REORGCHK for all tables

Scheduling scripts

Running the NLS cleanup job

Note

Even though some of the tasks are already performed by DB2's automatic maintenancefunctions (for example, automatic RUNSTATS or automatic REORG), there may be situationswhen you have to explicitly update statistics or perform a REORGCHK for all tables.

For more information, see Configuring Automatic Maintenance Settings [page 234].

End of the note.

8.1.2.1 Scheduling Database BackupsA database backup is a complete copy of your database. To be able to restore the databaseto a consistent state that is as up-to-date as possible, you have to perform database backupson a regular basis.

You can perform database backups using the DBA Planning Calendar in the DBA Cockpit.Depending on the storage device that you are using, you can choose one of the followingjobs:

Database Backup into TSM

You back up the database to Tivoli Storage Manager (TSM).

Database Backup to Device

You back up the database to a specified tape or disk.

Database Backup with Vendor Library

You back up the database to any other vendor storage management product.

Snapshot Backup

You back up the database using the fast copying technology of a storage device.

Caution

This job is only available as of DB2 V9.5.

End of the caution.

8 Jobs

266 November 2010

Procedure1. To schedule a database backup in the DBA Planning Calendar, click a calendar cell

or choose the Schedule an Action link in your Favorites.

The Schedule an Action wizard appears guiding you through the procedure. In theParameters step, specify the following parameters:


Backup Mode

Online Access to the database is not blocked. The users can continue to worknormally during the backup.

Offline

Note

This option is no longer supported and is displayed only for upwardcompatibility reasons.

Backup jobs that have this option are automatically performed as onlinebackups with the Include Logs option.

End of the note.

Backup Type

Full The complete database is backed up.

IncrementalCumulative (that is, incremental) backup image

An incremental backup image is a copy of all database data that has changedsince the most recent successful full backup operation.

IncrementalDelta

Non-cumulative (that is, delta) backup image

A delta backup image is a copy of all database data that has changed sincethe most recent successful backup operation.

AdditionalOptions

Compress The backup is to be compressed.

Include Logs

Note

Only choose this option if you want to perform an online backup.

End of the note.

Only those log files are included in the backup that are required to get aconsistent database. Any further log files are not taken into consideration.

8 Jobs

November 2010 267

Caution

The following options are only available for downward-compatibility reasons and westrongly recommend that you do not set them:

o Number of Buffers

o Buffer Size

o Parallelism

End of the caution.

2. Schedule the job by choosing the Execute pushbutton on the Summary screen of theSchedule an Action wizard.

3. Exit the wizard

8.1.2.1.1 Backup ConsiderationsWhen performing a backup, you should consider the following:

Regardless of the selected backup mode, you can only restore the database if youhave at least one valid full backup.

To restore the database completely and to bring the system up-to-date, you have toroll in the log files that were generated after the backup was performed.

The database may be local or remote. The backup, however, remains on thedatabase server unless a storage management product, for example, Tivoli StorageManager (TSM), is used.

After an online backup, DB2 forces the currently active log files to be closed and as aresult they are archived. Therefore, an online backup has a complete set of archivedlog files that are available for database recovery.

Backup of a Multi–Partition DatabaseYou have to back up partition by partition. Therefore, you have to schedule backup jobs foreach partition.

In a multi–partition database system, keep a copy of file db2nodes.cfg with any backupcopy that you take. This copy of file db2nodes.cfg is used as a safety copy in case ofpossible damage to the original file.

Note

As of DB2 V9.5, a “single system view” backup is available that performs the backup for alldatabase partitions in one job. You can use this option by choosing the value All for thedatabase partition in the Schedule an Action wizard.

End of the note.

8 Jobs

268 November 2010

Frequency of Backups and Time RequiredYou should take full database backups on a regular basis, regardless of how often log filesare archived. A current full backup means that there are fewer archived log files that youhave to apply in case of a database recovery. Therefore, the amount of time that is requiredby the ROLLFORWARD utility to recover the database decreases. In addition, the chance of alog file not being available (for example, due to data corruption or data loss) also decreases.

To reduce the amount of time that the database is not available, we recommend that youconsider performing online backups.

Note

You can only use an online backup for recovery if the database log files that were createdduring the online backup are available.

End of the note.

Advanced Backup TechniquesThe following list provides information on advanced backup techniques:

Incremental or delta backups

To reduce the backup and restore time, you can use incremental or delta backups.For more information, see the IBM manual Data Recovery and High AvailabilityGuide and Reference.

Backup of a file system copy using the db2inidb tool

For more information about the db2inidb tool and its use as a mirror for a backupbased on a file system, see the Database Administration Guide: SAP on IBM DB2 forLinux, UNIX, and Windows.

Standby database for backup purposes

For more information about how to use the db2inidb tool to create a standbydatabase for backup purposes, see the Database Administration Guide: SAP on IBMDB2 for Linux, UNIX, and Windows.

More InformationDatabase Administration Guide: SAP on IBM DB2 for Linux, UNIX, and Windows at:

http://service.sap.com/instguidesnw <Your SAP NetWeaver Release> OperationsDatabase-Specific Guides

http://service.sap.com/instguidesnw

8 Jobs

November 2010 269

8.1.2.2 Archiving Log Files To TapeYou can archive log files to tape using the job Archive Log Files to Tape in the DBA PlanningCalendar.

Procedure1. Start the Schedule an Action wizard by clicking a calendar cell or by choosing the

Schedule an Action link in your Favorites.

2. In the Job Selection step, choose Archive Log Files to Tape from the Actiondropdown list.

3. In the Parameter step, specify the required parameters.

Note

The DB2 tape manager is used to archive log files to tape. Besides the standardparameters (for example, start time, date, number of log files to be saved, and tapelabel), you can also specify the option of the tape manager to use for archiving logfiles:

o Double Store

o Overwrite Expired Tapes

o Eject Tape at End of Operation

For more information, see the Database Administration Guide – SAP on IBM DB2 forLinux, UNIX, and Windows

End of the note.

4. Schedule the job by choosing the Execute pushbutton on the Summary and exit thewizard.

More InformationDatabase Administration Guide – SAP on IBM DB2 for Linux, UNIX, and Windows at:

http://service.sap.com/instguidesnw <Your SAP NetWeaver Release>Operations Database-Specific Guides .

8.1.2.3 Updating StatisticsYou can use the DBA Planning Calendar to schedule an update of the database statistics. Ingeneral, DB2 updates the database statistics automatically using its automatic RUNSTATSfunction.

If the automatically maintained statistics need to be up-to-date or if a different type ofstatistics – other than DB2’s default – is required, you can schedule the job RUNSTATS andREORGCHK for Set of Table in the DBA Planning Calendar. This job performs a RUNSTATSfor a single table or a set of tables that is specified by a name using wildcards.


8 Jobs

270 November 2010

Recommendation

Since the RUNSTATS can affect system performance in case of large tables, we recommendthat you schedule the job RUNSTATS and REORGCHK for Single Table to run outsidenormal working hours, for example, on Sundays.




2. In the Job Selection step, choose RUNSTATS and REORGCHK for Set of Tablesfrom the Action dropdown list.

3. In the Parameters step, do the following:

o Specify the tables where the statistics are to be updated. You can usewildcards for the table names.

o Specify how you take statistic profiles into account by choosing one of thefollowing options:

Use Customized Settings or Existing Profiles

For tables that have statistic profiles, the RUNSTATS is performedusing exactly the same settings as specified in the profile. For allother tables, the RUNSTATS is performed as specified in the wizard.

Use Customized Settings Ignoring Existing Profiles

If you choose this option, the RUNSTATS is performed as specified inthe wizard regardless whether or not statistic profiles exist.

o Specify the following settings for the RUNSTATS:

Field Description

Table Analysis Method

Basic Basic statistics for the table

Distributed Statistics Distributed statistics for the table

None

No statistics for the table

Caution

Selecting this option only freezes already existing oldtable statistics but it does neither delete nor invalidatethem.

End of the caution.

8 Jobs

November 2010 271

Field Description

Sampling of [ ] %ofentries

Percentage of entries to be used for sampling

Caution

This field is only active if you are using DB2 UDB forUNIX and Windows Version 8, FixPak 2 or higher.

End of the caution.

System (Page,Sampling)

The data to be sampled is selected page by page.

Caution


End of the caution.

BERNOULLI (RowSampling)

The data to be sampled is selected row by row.

Caution


End of the caution.

Analyze Key Columnsonly

Table statistics are gathered only for key columns of thetable.

Index Analysis Method

Basic Basic statistics for the index are gathered

Detailed Statistics Detailed statistics for the index are gathered

Detailed SampledStatistics

Detailed statistics for the index using sampling aregathered

None

No statistics for the index are gathered

Caution

Selecting this option only freezes already existing oldindex statistics but it does neither delete nor invalidatethem.

End of the caution.

o If you have specified more than one table, you can choose the degree ofparallelism by setting the value for Number of Parallel Jobs higher than one.In this case, the RUNSTATS job can be parallelized if there are enough

8 Jobs

272 November 2010

system resources available (for example, background processes and theappropriate number of processors). Doing so results in additional jobs thatare scheduled by the regular DB13 job and which perform the RUNSTATS ontables in parallel. The SAP system makes sure that the number of paralleljobs does not exceed the number of available background processes.

o Caution

o Handle the parameter Number of Parallel Jobs with care. Starting more jobscan have a high impact on the overall system performance even though theparameter Number of Parallel Jobs significantly reduces the amount of timefor the job execution.

o End of the caution.

4. Schedule the job by choosing the Execute pushbutton on the Summary screen andexit the wizard.

8.1.2.4 Reorganizing TablesYou can use the DBA Planning Calendar to schedule a reorganization of a set of tables. Ingeneral, DB2 reorganizes the tables using its automatic REORG function. If a reorganization isrequired that is not covered by automatic REORG ( for example, due to table compression),you can schedule the job REORG and RUNSTATS for Set of Tables in the DBA PlanningCalendar.

Procedure1. Start the Schedule an Action wizard by choosing the Schedule an Action link in your

Favorites or by clicking a calendar cell.

2. In the Job Selection step, choose REORG and RUNSTATS for Set of Tables fromthe Action dropdown list.

3. In the Parameters step, specify the following parameters:



Table Name of the table

Offline

Schedules an offline reorganization.

Optionally, you can also specify the following parameters:

o Use Temporary Tablespace

If you select this option, a temporary tablespace is used for thereorganization.

Note

If no temporary tablespace is used for the REORG, it is performed in

8 Jobs

November 2010 273


the tablespace where the table or index resides. You must makesure that there is enough free space in this tablespace(approximately the size of the table or index). If this tablespacealready has a high I/O load, we recommend that you use atemporary tablespace for performance reasons.

End of the note.

o With Long Fields and LOB Data

If you select this option, long field and LOB data areas are alsoreorganized.

o Switch Compression on

If you select this option, the table and its indexes are enabled forcompression before the REORG operation is performed.

o Reset Dictionary

If you choose this option, a compression dictionary is rebuilt if thetable is compressed or the Switch Compression on option is set.Otherwise, an existing compression dictionary is removed.

o Keep Dictionary

If you choose this option, an already existing compression dictionaryis kept and not rebuilt. If the table is compressed or the SwitchCompression on option is set and a dictionary does not yet exist, thecompression dictionary is built.

Note

The compression-related options are only available for DB2 V9.1and higher.

End of the note.

Online Schedules an online reorganization of the table

All Indexes Schedules only a reorganization of all indexes

Reclaim Spacefor MDC

Schedules a reorganization that reclaims space for MDC tables

Note

This option is only available for DB2 V9.7 and higher.

End of the note.


8 Jobs

274 November 2010

8.1.2.5 Scheduling a REORGCHK for All Tables

Caution

The following section only applies if your database is DB2 UDB for UNIX and WindowsVersion 8.2 or if the data collection framework has not been set up.

End of the caution.

You can use the DBA Planning Calendar to schedule an overall check of all tables using thejob REORGCHK for All Tables. This job collects the following:

REORG recommendations for tables and indexes that are provided by the DB2REORGCHK command

Information about current table and index sizes

Recommendation

The job REORGCHK for All Tables must run once a week.




2. In the Job Selection step, choose REORGCHK for All Tables from the Actiondropdown list.

3. In the Parameters step, specify the required parameters as follows:


All TablesSpecifies that the job is called for all tables

By default, this parameter is selected.

Selected Tables

Specifies that this job is restricted to a set of tables

If you choose this option, you also have to specify the Table Schema andTable Name.

Note

Only choose this option if you require an up-to-date analysis for theselected tables.

End of the note.

With CompressionCheck

Analyzes the tables and checks for candidates to be compressed

By default, you should not activate this option for the REORGCHK job thatis scheduled weekly. For performance reasons, only performcompression checks in larger time-frames.

8 Jobs

November 2010 275


Minimum TableSize for Check

Defines the minimum size limit for checking how much space can besaved by compressing the table.

Recommendation

We recommend that you set this limit to prevent too small tables that donot benefit from row compression from being checked.


Note

You can only specify this value if you have chosen With CompressionCheck.

End of the note.

Maximum Runtime Restricts the runtime of this job


8.1.2.6 Scheduling ScriptsYou can use scripts to schedule time-consuming and non standard database administrationtasks using the job CLP Script.



2. In the Job Selection step, choose CLP Script from the Action dropdown list.

3. Specify SQL statements directly as job parameters.

Note

Alternatively, you can use scripts that have been created before. For moreinformation, see The SQL Script Maintenance [page 278].

End of the note.

4. Save your entries by choosing the Execute pushbutton on the Summary screen.

5. Exit the wizard

8 Jobs

276 November 2010

8.1.2.7 Running the NLS Cleanup Job

Note

The following section only applies if you are using a near-line storage (NLS) database foryour local BW system.

End of the note.

When data is reloaded from the NLS database into the BW system, it continues to exist in theNLS database. It is marked, however, as invalidated. To remove this invalidated data and toreduce the space consumption in the NLS database, you can use the NLS Cleanup job in theDBA Planning Calendar.



2. In the Job Selection step, choose NLS Cleanup from the Action dropdown list.

3. In the Parameter step, specify the following:

o In the NLS Connection field, choose an existing NLS connection.

o In the InfoProvider field, choose the name of the InfoProvider.

Caution

If you do not specify an InfoProvider, the cleanup is performed for all InfoProviders.To run the job for many InfoProviders with similar names, you can use the wildcardcharacter ‘*’.

End of the caution.

4. Save your entries by choosing the Execute pushbutton on the Summary screen.

5. Exit the wizard.

More InformationFor more information about reloading data from the NLS database into the BW system, seethe separate document Enabling an SAP NetWeaver BW to Use IBM DB2 for Linux, UNIX,and Windows as Near-Line Storage at:

http://service.sap.com/instguidesnw <Your SAP NetWeaver Release> InstallationInstallation - SAP NetWeaver Systems


8 Jobs

November 2010 277

8.2 The DBA LogThe DBA log provides information about protocol records that are written by all database-related programs of the CCMS and SAP-DB2 admin tools.

You can access the DBA log by calling the DBA Cockpit and choosing Jobs DBA Logon the Database tab page of the DBA Cockpit.

The following information is displayed on the DBA Log screen:

Column Description

Partition Name of the partition

Start Date Start date of action

Start Time Start time of action

End Date End date of action

End Time End time of action

Runtime Runtime in HH:MM:SS

Action Description of action

Return Code Return code of action

When you access the DBA log for the first time, the system displays the log information forthe current week.

You can display information about previous weeks by using the F4 help of the From field inthe Selection area.

8.3 Back-End ConfigurationYou can configure the back end of the DBA Planning Calendar to control the execution ofbackground jobs. You can configure the back end for all systems, for selected databaseplatforms, or for single systems only.

The respective system configuration is determined by applying the first availableconfiguration in the following order:

1. The system-specific configuration

2. The configuration for the database platform

3. The configuration valid for all platforms

4. The standard configuration, that is, the current user, selection of background serverby background dispatcher, and low job priority

8 Jobs

278 November 2010

Configuration Steps1. Call the DBA Cockpit and choose Jobs Back End Configuration on the

Database tab page.

2. To switch to editing mode, choose the Change pushbutton.

3. In the Selected Scope area, choose the scope of the configuration entry.

4. In the Background Dispatching area, specify the following parameters:

Field Description

BackgroundServer

Server where scheduled jobs are executed

If no server is specified, the background job dispatcher dynamicallyselects the server.

Job PriorityPriority of the job

If no priority is specified, jobs run with default priority (low).

UserName of the user to execute the job

If no user is specified, the dialog user is used.


8.4 The SQL Script MaintenanceYou use the SQL Script Maintenance function to manage your own DB2 scripts.

IntegrationThe SQL Script Maintenance is part of the DBA Cockpit.

ActivitiesTo access the SQL Script Maintenance, call the DBA Cockpit and choose Jobs SQLScript Maintenance on the Database tab page.

The Jobs: SQL Script Maintenance screen appears displaying all the scripts located on yourlocal monitoring system. You can perform one of the following actions:

Action Steps to Be Performed

Display an existingSQL script

Choose an entry from the list. Detailed information is displayed in theSQL Script Details detail area.

8 Jobs

November 2010 279

Edit an existingSQL script

1. Choose a script from the list and choose the Edit pushbutton.

2. Enter and save your changes in the Change Script dialog box.

Delete an existingSQL script

1. Choose a script from the list and choose the Delete pushbutton.


Add a new SQLscript

1. To add a new script, choose the Add pushbutton.

2. In the Add Script dialog box, enter a name in the Script Namefield and start editing.

3. Save the new script.

Execute anexisting SQL script

1. Choose a script from the list and choose the Execute pushbutton.

2. In the Execute SQL Script dialog box, enter the name of the SAPsystem where you want the script to be executed in the ExecuteSQL Script on System field.

3. To confirm your entry, choose the Execute pushbutton again. TheCLP Output Tray appears showing an editor in the lower half ofthe screen where the result is displayed.

Note

As an alternative to the SQL Script Maintenance function, you can alsouse the DBA Planning Calendar to execute a script by using the CLPScript job as described in Scheduling Scripts [page 275].

End of the note.

8.5 Scheduled DB2 TasksOn the Scheduled DB2 Tasks screen, you can monitor the execution of tasks that have beenscheduled from the DB2 Admin Task Scheduler and the status of the data collectors of theDCF.

To access the Scheduled DB2 Tasks screen, call the DBA Cockpit and choose JobsScheduled DB2 Tasks .

In the Selection area, you can specify the time frame to be displayed. By default, the jobs ofthe current day are displayed.

8 Jobs

280 November 2010


Column Description

Name Name of the task

Status

Status of the task


RUNNING

The task is currently running.

COMPLETED

The task has finished running.

NOTRUN

An error prevented the scheduler from calling the task’sprocedure.

UNKNOWN

The task started running but an unexpected condition preventedthe scheduler from recording the task outcome. This can occur ifthe system ends abnormally or a power failure happens while thetask is running.

Invocation Number of invocations so far

Time Started

Starting time of the task

If the status is RUNNING, COMPLETED, or UNKNOWN, this valueindicates the time when the task started running.

The status is NOTRUN indicates the time that the task should havestarted.

Time Finished

Time when the task finished running

This value is not set as long as the status is RUNNING.

If the status is UNKNOWN, this value is the time when the task schedulerdetected that the task was no longer executing and updated the statustable accordingly.

Agent TID Agent thread ID of the application that executed the task

8 Jobs

November 2010 281

SQL Code

Value displayed depends on the status this field

If the status is COMPLETED, this value indicates the SQL code that isreturned by the CALL to the procedure.

If the status is NOTRUN, this value indicates the SQL code of the errorthat prevented the task from running.

Note

As long as the status is RUNNING or UNKNOWN, this value is notavailable.

End of the note.

SQL State The SQL state that is related to the SQL code

Return CodeReturn code of the procedure that was called

As long as the status is not COMPLETED, this value is not available

Error Message Full message text corresponding to the SQL Code

9 Alerts

282 November 2010

9 AlertsThe following sections provide information about alerts:

Alerts: Database System Monitoring in CCMS

Alerts: Configuring Database System Monitoring

Alerts: Alert Monitor

Alerts: Alert Message Log

Alerts: Alert Configuration

9.1 Alerts: Database System Monitoring inCCMSThe alert monitor checks snapshot data and the database history file. If a critical situation, forexample, a threshold violation, is detected, alerts are raised so that you can recognize andsolve problems at an early stage.

IntegrationThe monitoring functions are fully integrated into the CCMS alert monitoring and architecture.

FeaturesThe following categories of information are monitored:

Disk space of the tablespaces and file systems that are required for the databasesystem

Performance indicators such as the following:

o Access behavior of database buffers

o Lock behavior of the application, monitoring of deadlock situations, and lockescalations

Availability of backup and recovery mechanisms:

o Last available backup

o Availability of the log files that are necessary to achieve the current state ofthe database from the last available backup

Configuration parameters

Availability data of tablespaces and containers

Recommendation

We recommend that you check the alert monitor daily for information about databasesystem monitoring.

9 Alerts

November 2010 283

9.2 Alerts: Configuring Database SystemMonitoringThe DB2 database system monitoring has preconfigured check categories and parameters.

Caution

Only experienced users should make changes to the system check configuration.

End of the caution.

There are two complementary tools available for the configuration of database systemmonitoring:

Configuration using general alert monitoring, that is:

o Automatic e-mail notification

The central, automated notification function informs you of an alert by e-mail.If you want to be notified as soon as an alert is raised, you have to defineyourself as a recipient of mails generated by this function.

o Background monitoring

Configuration of DB2-specific parameters

Enabling Automatic E-Mail Notification1. Call transaction RZ21.

The Monitoring: Settings and Tool Maintenance screen appears.

2. Choose Tool Definition and then Display Overview.

3. Scroll through the list until you find CCMS_OnAlert_Email.

4. Select this entry and choose List Selected Entries Edit (or Edit in theapplication toolbar).

The Monitoring: Tool Administration screen appears.

5. Choose Parameter.

6. Choose Tool Definitions Display Change (or Display Change in the applicationtool bar).

7. In the SENDER line in the Parameter value column, enter a valid user for your SAPsystem.

8. In the RECIPIENT line in the Parameter value column, enter a valid user for yourSAP system who will be notified in the event of an alert.


9 Alerts

284 November 2010

Activating Background Monitoring1. Call transaction RZ21.

2. Choose Technical Infrastructure Method Execution Activate BackgroundDispatching .

Caution

If you do not enable your system for background monitoring, the system will not bemonitored at all.

End of the caution.

Configuring DB2-Specific ParametersYou can specify additional parameters, for example, assign logged values for given alerts.

For more information, see Alerts: Alert Configuration [page 287].

9.3 Alerts: Alert MonitorYou can choose one of the following options to retrieve information about alerts:

For an overview of alert situations, call the DBA Cockpit and choose Alerts AlertMonitor on the Database tab page of the DBA Cockpit. The Alert Monitor screenappears.

To display the message log for an alert, select the relevant alert from the treestructure.

To start a more detailed analysis, call transaction RZ20 and choose SAP CCMSMonitor Templates Database DB2 Universal Database for NT/UNIX in the treestructure CCMS monitor sets.

Note

If you want to use transaction RZ20 for remote database systems, choose SAPCCMS Monitor Templates Remote Database DB2 for Linux, UNIX, and Windows

.

End of the note.

9 Alerts

November 2010 285

Data Displayed in the Alert Monitor TreeRegardless of the view variant you choose, information about the following is displayed:

Space management

Performance

Backup/restore

SAP consistency

Health

The checked parameters are displayed in the following colors depending on the type ofmessage:

Message Type Color

Information Green

Warning Yellow

Error Red

Note

If a check resulted in a warning or an error, a short text is additionally displayed next to theparameter.

End of the note.

9.4 Alerts: Alert Message LogYou can access an overview of the system monitoring results by calling the DBA Cockpit andchoosing Alerts Alert Message Log on the Database tab page of the DBA cockpit. TheAlert Message Log screen appears.

To limit the display to specific error levels or check categories, you can use the list boxes inthe Current Selection area. In the Object and Attribute fields, you can enable restrictions tosingle attributes. Additionally, you can specify a time period for which the messages aredisplayed. By default, the messages of the last seven days are displayed.

Only the most important data is displayed in the overview. The results are displayed as notes,warnings, or errors and are sorted by log date by default.

9 Alerts

286 November 2010

You can display more detailed information by selecting an alert message. The Alert MessageDetails area appears displaying the following:

Alert Message Details

Complete description of the attribute as displayed in the alert monitor tree

Logged Data

Information about the alert message, for example, type of error, reported value, anddate and time when it occurred

Description

Description of the type of error and which value or parameter is being monitored

Deleting Alert MessagesYou can delete alert messages from any given time period by selecting an alert message andchoosing the Delete pushbutton.

If you choose the Delete pushbutton without having selected an alert message, a dialog boxappears. In the Date field, you can specify the date from which you want all messages to bedeleted. You can also enter the category or partition as selection criteria.

Caution

To avoid that the log table becomes too large, automatic clean-up programs run and deleteentries that are older than 30 days.

End of the caution.

Displaying Data in the Alert Monitor Tree1. Call transaction RZ20.

The Alert Monitor Set screen appears.

2. Expand SAP CCMS Monitor Templates and double-click Database.

3. Expand DB2 Universal Database for NT/UNIX.

4. You can display information about the following:

o Space management

o Performance

o Backup/restore

o SAP consistency

o Health

9 Alerts

November 2010 287

The checked parameters are displayed in the following colors depending on the typeof message:

Message Type Color

Information Green

Warning Yellow

Error Red

If a check resulted in a warning or error, a short text is additionally displayed next tothe parameter in the Open alerts view.

9.5 Alerts: Alert ConfigurationThe DB2 database system monitoring has preconfigured check categories and parameters.

Caution

Only experienced users should make changes to the system check configuration.

End of the caution.

The initial screen of the database-specific configuration provides you with an overview of allthe configuration entries.

You can access information about alert configuration by calling the DBA Cockpit andchoosing Alerts Alert Configuration on the Database tab page of the DBA Cockpit. TheAlert Configuration screen appears.

On this screen, you can display alert configuration details and select configuration optionsusing the list boxes in the Selection area. In addition, you can activate or deactivate an alertconfiguration entry by selecting or deselecting the checkbox in the Active column.

Caution

If you deactivate an alert configuration entry, you will no longer be notified of the respectivealerts.

End of the caution.

For more information about an alert configuration entry, select one from the list. The AlertConfiguration Details area appears displaying the following tab pages:

Thresholds

General (RZ21)

Administration

9 Alerts

288 November 2010

ThresholdsThis tab page displays the threshold statuses of an alert configuration as follows:

Error Condition

If the error is not corrected, normal operation is endangered.

Warning Condition

Limited operation, for example, with reduced performance

Normal State Condition

Each condition is described by a relational operator, a comparison value, and the unit ofmeasurement for this value.

Maintaining Alert Conditions1. To maintain these alert conditions, choose the Edit pushbutton. The Alert

Configuration Details dialog box appears.

2. Maintain the configuration values according to which the system is monitored asfollows:

o Relational operators

You can specify how the defined comparison value should be compared withthe current value. In addition to the relational operators, you can enterwhether a value should lie inside or outside of a range of values. A full colon( : ) must separate the two values. You can also specify whether or notdiscrete values are within a set of explicit values. Semicolons ( ; ) mustseparate such values.

o Comparison value

You can specify a value, a list of values, or a value range depending on theoperator. This value will later be compared with the currently measuredvalue.

o Unit of measurement of the comparison value

You can specify the unit of measurement of the comparison value. This isimportant for time values, which are normally calculated internally inseconds, to be correctly converted before comparison.

Note

You do not have to enter values for every operation status. However, youmust make sure that the sum of comparison values covers every possiblevalue. If this is not the case, a special alert is triggered with the followingmessage:

There is no configuration entry for the logged value

End of the note.

9 Alerts

November 2010 289


The changes take effect immediately.

General (RZ21)This tab page displays the scheduling data from the basic alert monitor configuration forcompleteness reasons. You cannot change the values on this tab page. You can makechanges using the general maintenance function (transaction RZ21) in the alert monitor.

AdministrationThis tab page displays the user, date, and time of the last changes.

10 Diagnostics

290 November 2010

10 DiagnosticsThe following sections provide information about the main task areas under Diagnostics onthe Database tab page of the DBA Cockpit:

Audit Log

Lock-Wait Events

Missing Tables and Indexes

Message History

Dump Directory

CLP Commands

DB2 Logs

10.1 Diagnostics: Displaying the Audit LogYou can track changes to the database made from the DBA Cockpit and to the monitoringsetup using the maintenance actions provided in the DBA Cockpit. Changes made fromoutside – for example, using native database commands – are not displayed here.

Procedure1. Call the DBA Cockpit and choose Diagnostics Audit Log on the Database tab

page of the DBA Cockpit.

The Audit Log screen appears displaying the following information

Field Description

Date Start date of the action

Time Start time of the action

System Target system on which the action was performed

Action Type of action (name of the action in the DBA Cockpit)

Command Type of command (for example, ADD, DELETE, or EDIT)

Object Name of the modified object (for example, database or tablespace name)

User Name of the SAP user who performed the action

From System System from where the action was performed

2.

10 Diagnostics

November 2010 291

3. By default, the system displays all audit entries logged during the current week. If youwant to display another week, use the F4 help of the From field.

To display more than one week, you can change the value in the field Number ofDays.

4. To display the details of an action, select the corresponding action and chooseDetails.

In the lower half of the screen, the SQL statements that have been executed aredisplayed.

10.2 Diagnostics: Lock-Wait EventsYou can access information about lock-wait events by calling the DBA Cockpit and choosing

Diagnostics Lock-Wait Events on the Database tab page of the DBA Cockpit.

Using the information provided on this screen, you can:

Review lock wait events that occurred in the past and that were captured by the lockevent monitor. By default, information about lock events is collected by the LockEvent data collector.

For more information, see Data Collection Framework: Collector Configuration [page248].

Review lock wait events that are currently occurring on the database server.

In the Selection area, you can specify the time frame for which you want lock-wait events tobe displayed as well as the type of lock-wait event, such as, lock waits, lock time outs, andlock waits with a specific lock time out.

After having applied your selection, the total number of lock-wait events that occurred andthat you selected in the Selection area is displayed in the Summary area.

For each lock-wait event, the following information is displayed:

Column Description

Event Type Type of lock event, which can be a lock wait, a lock timeout or a deadlock

Event Occurrence Time when the lock event first occurred

Event Resolution

Time when the lock event was solved

Note

For events that are still existing, the status displayed is Still Existing.

End of the note.

10 Diagnostics

292 November 2010

Involved Agents Number of agents involved in the lock event

Max. Wait Time Max. lock-wait time of any of the involved agents

Lock Objects Database objects involved in the lock conflict

ActivitiesYou can display the lock chain - or in case of a deadlock a log circle - of an event graphicallyby choosing a line from the overview table. To display details about the agents involved,select the appropriate agent in the graphical display. The Details of Agent <agent numer>detail area appears providing general information about the application the lock-waiting agentis working for as well as about the application the lock-holding agent is working for.

In addition, information about the activity that is currently being executed or that wasexecuted last by each agent is provided, such as, the SQL statement text and generalinformation about the SQL statement (for example, the compilation environment).

Note

If the lock event monitor has captured past activities or nested activities for a certain agent,the Activity History table appears providing information about the agent ID; its nesting leveland the SQL statement executed by each agent. You can display detailed information foreach activity by choosing a line in the Activity History table. The information is displayed inthe Details of Activity <activity number> detail area.

End of the note.

10.3 Diagnostics: Missing Tables and Indexes Note

This function is only available for local systems or for ABAP systems for which an additionalRFC destination has been assigned.

End of the note.

You can find out whether tables or indexes are missing from either the database or the ABAPDictionary by calling the DBA Cockpit and choosing Diagnostics Missing Tables andIndexes on the Database tab page of the DBA Cockpit.

10 Diagnostics

November 2010 293

The results of the last consistency check are displayed in a tree structure that is grouped intothe following sections:

Section Description

Objects missing fromthe database

Objects that are defined in the ABAP Dictionary, but not found in thedatabase

Unknown objects inthe ABAP Dictionary

Objects that are found in the database, but not defined in the ABAPDictionary

Inconsistent objects Results of the detailed comparison of the ABAP Dictionary and thedatabase are displayed here

Other checks

Different checks are performed here:

It is checked whether the primary index of tables defined in theABAP Dictionary was created uniquely on the database.

Objects in the SAP system tables are checked, which cannotbe described at all or which cannot be completely described inthe ABAP Dictionary for technical reasons.

If inconsistencies for these objects are detected, they are alsodisplayed here. In general, additional information about thetype of inconsistency is provided.

Optional indexes Mismatch between ABAP Dictionary and database regardingsecondary indexes

If the database structure has been changed since the last consistency check, choose theRefresh pushbutton.

Recommendation

To ensure consistency between the ABAP Dictionary and the database, the consistencycheck should be performed once a month or whenever the database structure has changed.


10.4 Diagnostics: Message HistoryYou can access information about the history of messages that are written to log files bycalling the DBA Cockpit and choosing Diagnostics Message History on the Databasetab page of the DBA Cockpit.

On the Message History screen, information about relevant DB2 errors and informationalmessages are displayed that help you identify database events (for example, backup andrecovery), performance bottlenecks, or critical situations.

10 Diagnostics

294 November 2010

Note

To use the information provided on the Message History screen, the data collectionframework has to be set up properly. In particular, you have to ensure that the Diag Logdata collector is correctly configured because it keeps a local history of specialdb2diag.log entries.


End of the note.

In the Selection area, you can specify the time frame for which you want log file messages tobe displayed.

After having applied your selection, the following information is displayed:

Column Description

Timestamp Time the message was created

Level

Indicates the severity level of the message


C

Indicates a critical situation

E

Indicates that an error occurred

I

Displayed message is only informational

S

Indicates a severe situation, for example, dead locks have beendetected

W

Indicates that the message contains a warning

Impact

Qualifies the impact of the message from a DBA’s perspective


CRITICAL

IMMEDIATE

NONE

POTENTIAL

10 Diagnostics

November 2010 295

Column Description

UNLIKELY

MessageNumber

Number of the associated message

Example

6102 is the numerical part of the ADM6102I message code.

End of the example.

Message Type

Type that is related to the message identifier

Example

ADM is used for administration or notification log messages.

End of the example.

Message Text Short description of the message

Note

You can display the complete log record by selecting a line in the overview table. Theinformation is displayed in the Message History Detail area.

End of the note.

10.5 Diagnostics: Dump DirectoryThe DB2 dump directory contains the following files:

DB2 diag log (db2diag.log)

DB2 notification log (<instance_name>.nfy)

DB2 dump files

User exit log and error files

Trace files

The system displays the content of the directory specified by the diagnostic data directorypath (diagpath). This path is configured in the database manager configuration.

You can access the dump directory by calling the DBA Cockpit and choosing DiagnosticsDump Directory on the Database tab page of the DBA Cockpit.

Note

If you want to display the content of an error log or a trace file, click the relevant file. The FileViewer area appears displaying the file contents.

10 Diagnostics

296 November 2010

10.6 Diagnostics: CLP Commands Note

This function is only available for DB2 V9.1 with at least Fix Pack 7 or for DB2 V9.5 with FixPack 1 and higher.

End of the note.

You can access detailed information about CLP commands by calling the DBA Cockpit andchoosing Diagnostics CLP Commands on the Database tab page of the DBA Cockpit.

By selecting a specific database area from theCLP Commands dropdown list (for example,Database Configuration) and choosing the Apply Selection pushbutton, the correspondingDB2 CLP native commands are performed and the native output is provided on the CLPCommands screen.

Note

The information provided on the CLP Commands screen is available in a formatted way alsoon other screens, for example, the Database screen in the Performance task area. But incontrast to these screens that only provide data for current database releases, the nativeview can provide the complete data also for future database releases.

End of the note.

10.7 Diagnostics: DB2 Logs Note

This function is only available if the monitored database is DB2 V9.5 or higher. If yourdatabase is DB2 V9.1 or lower, refer to the following sections:

Diagnostics: Database Notification Log

Diagnostics: Database Diag Log

End of the note.

The Diagnostics: DB2 Logs screen provides you with information about all relevant log files ofDB2 including the following:

The database diagnostic log (db2diag.log)

Note

Since DB2's automatic RUNSTATS have been introduced, the db2diag.log canrapidly grow in size up to several gigabytes – depending on the value of theDIAGLEVEL database configuration parameter. By default, the value of thisparameter is 3. We therefore recommend that you regularly switch thedb2diag.log using the automation function as described in Configuring MonitoringSettings [page 253].

End of the note.

10 Diagnostics

November 2010 297

The database notification log (<instance_name>.nfy)

The statistics log

You can access the DB2 logs by calling the DBA Cockpit and choosing Diagnostics DB2Logs on the Database tab page of the DBA Cockpit.

To avoid unnecessary system workload, you can restrict the amount of data that is processedby specifying the following in the Selection area:

A Log Facility

A Record Type

The minimum impact level (Impact)

A time range (Messages From / To)

If you apply your selection, information according to the specified values is displayedincluding the appropriate DB2 component. To display additional details about a log entry,click the relevant entry in the list.

More InformationIBM DB2 Administration Guide

11 BW Administration

298 November 2010

11 BW Administration Note

All BW–related actions in the DBA Cockpit are only available if the system has beenrecognized as a BW system. A system is recognized as a BW system if the BI_Contentcomponent is installed.

End of the note.

The following sections provide information about BW administration:

The MDC Advisor

NLS Configuration

NLS Overview

11.1 BW Administration: MDC AdvisorThe MDC advisor is a DB2 tool that proposes multidimensional clustering (MDC) settings fortables using queries executed on the table. You use the MDC advisor to collect BW reportingqueries for an InfoProvider, that is, for InfoCubes and DataStore objects. The MDC Advisoranalyzes the collected BW reporting queries and returns a proposal for MDC settings for thefact tables of an InfoCube and for the active table of a DataStore object. Based on this MDCproposal, you can change the clustering of the analyzed InfoProvider using transaction RSA1in your SAP system.

You access the MDC advisor by calling the DBA Cockpit and choosing BW AdministrationMDC Advisor of the Database tab page of the DBA Cockpit.

More InformationFor more information about the MDC advisor, see the Database Administration Guide: SAPNetWeaver Business Warehouse 7.0 and Higher – Administration Tasks: IBM DB2 for Linux,UNIX, and Windows at:

http://service.sap.com/instguidesnw <Your SAP NetWeaver Release>Operations Database-Specific Guides

11.2 BW Administration: Administration andMonitoring of the Near-Line Storage (NLS)DatabaseNear-line storage (NLS) is a new category of data persistency that is similar to archiving. Theoverall goal is to take read-only data out of the BW database and to store it in an additionalnear-line storage DB2 database. The database server and the storage devices of the near-line storage solution can be separated from the SAP NetWeaver database hardware but youcan still access the separated data transparently from an SAP NetWeaver BW system (in thefollowing referred to as BW system).



November 2010 299

Using the NLS database includes the following administrative tasks:

Configuring the NLS database as a monitored system in the DBA Cockpit

For more information, see Configuration of Systems for Remote Monitoring [page36].

Configuring the database connections that are required to access the NLS databasefrom the local BW system using the NLS Configuration screen in the DBA Cockpit

Note that this task is an extension to the standard database connection maintenance.

For more information, see BW Administration: NLS Configuration.

Monitoring the BW objects of which data has been archived to the NLS databaseusing the NLS Overview screen in the DBA Cockpit

On this screen, you can monitor the space consumption of BW objects in both theSAP BW database and in the related NLS database.

For more information, see BW Administration: NLS Overview.

Cleaning up invalidated data in the NLS database using the NLS Cleanup job in theDBA Planning Calendar

For more information, see Running the NLS Cleanup Job.

11.2.1 BW Administration: NLS Configuration

Note

This screen is only available for a local BW system.

End of the note.

The BW Administration – NSL Configuration screen provides you with an overview of all NLSdatabases that are connected to your SAP NetWeaver BW system.

To access the BW Administration – NLS Configuration screen, call the DBA Cockpit andchoose BW Administration NLS Configuration on the Database tab page of the DBACockpit.

A table of all configured NLS connections is displayed providing the following information:

Column Description

Connection Name Name of the database connection that is used to access the database

DB Name Name of the assigned NLS database

DB Server Name of the host where the NLS database is installed

Schema Name Name of the NLS database schema


300 November 2010

Column Description

User Name Name of the database user that is used to connect to the NLS database

To maintain your NLS configurations, you can use the following pushbuttons from theapplication toolbar:

To create a new NLS configuration entry, choose Add.

To change an existing NLS configuration, choose Change.

To delete an existing NLS configuration, choose Delete.

To perform these tasks, the standard maintenance screen for the configuration of databaseconnections is used.

In all cases, a dialog box appears with a detailed maintenance screen for the databaseconnection related to the NLS database. To check the availability of the NLS connection,choose the Test Connection pushbutton. The result of the connection test appears in theaction message window in the lower half of the screen.

Note

If you create the NLS connection using directly the database connection maintenancefunctions without the NLS Configuration screen, the configuration data for the NLSconnection is not created. Make sure that you use the NLS Configuration screen.

End of the note.

More InformationConfiguring Database Connections [page 46]

11.2.2 BW Administration: NLS Overview

Note

This screen is only available for a local BW system.

End of the note.

The NLS Overview screen provides you with an overview of InfoProviders that are connectedto an NLS database. You can use the information on this screen to analyze the spaceconsumption of an InfoProvider in the BW database in comparison to the remote NLSdatabase. In addition, you can update the configuration of your BW queries so that theyautomatically read data from the NLS database.


November 2010 301

To access the NLS Overview screen, call the DBA Cockpit and choose BW AdministrationNLS Overview on the Database tab page of the DBA Cockpit. To specify which

InfoProviders are displayed, enter the required data in the following input fields and choosethe Apply pushbutton:

InfoProvider Name

InfoProvider Size (KB)

NLS Connection

NLS Size

The following table displays all InfoProviders that meet the specified selection criteria:

Column Description

InfoProvider Name Name of the InfoProvider

InfoProvider Size(KB)

Total size of all database tables of the InfoProvider in KB

Note

This size information is not newly calculated but retrieved from values thatwere previously provided by the REORGCHK for All Tables job and mighttherefore not be accurate. If you do not run the REORGCHK for All Tablesjob, the displayed value is -1.

For more information, see Scheduling a REORGCHK for All Tables [page274].

End of the note.

NLS Connection Name of the NLS connection

NLS Name Name of the NLS database schema

NLS Size

Total size of all database tables of the InfoProvider in the NLS database

Note

This value is only available if the NLS database has been configured andproperly set up for monitoring in the DBA Cockpit.

For more information, see Configuration of Systems for Remote Monitoring[page 36] and Scheduling a REORGCHK for All Tables [page 274].

End of the note.

Query Enabled Indicates whether the BW queries of the InfoProvider have been enabled toread data from the NLS database


302 November 2010

Enabling BW Queries to Use the Near-Line Storage DatabaseBy choosing the Enable Queries pushbutton, you activate the Query Enabled option of anInfoProvider. That is, the configuration of all BW queries of a single InfoProvider is updatedand the queries are enabled to also read data from the NLS database. After a data archivingprocess has been created for an InfoProvider, the new property Read Near-Line Storage aswell is assigned to the BW queries. A BW query with this property reads data both from theBW database and from the NLS database. If the Read Near-Line Storage as well property isnot assigned, the NLS data is not used to build the query results.

Displaying Details of InfoProvidersTo display detailed information about an InfoProvider, double-click an InfoProvider, or selectit and choose the Details pushbutton. The NLS Details screen appears displaying details ofthe InfoProviders in two tables:

In the left table, the schema name, table name, and size of the database tables that areassociated with the InfoProvider in the BW database are displayed. The right table displaysthe same information for the database tables representing the InfoProvider in the NLSdatabase.

Analyzing Single Tables of the BW and the NLS DatabaseTo analyze a single table of an InfoProvider, double-click an InfoProvider in the left table onthe NLS Details screen, or select the InfoProvider and choose the Details pushbutton. TheTable and Indexes Detail screen appears providing detailed technical information, forexample, about the structure of the selected table, its indexes, and the tablespaces used.

Caution

If you want to analyze a single NLS table, you cannot navigate to the Single Table Analysisscreen in the Space task area by double-clicking a table cell in the right table of the NLSDetails screen.

Instead, proceed as follows:

1. On the System Landscape tab page, select your NLS database system.

2. Go to the Database tab page and choose Space Single Table Analysis .

3. On the Single Table Analysis screen in the Space task area, enter the schema andthe table name of the NLS table in the appropriate fields.

End of the caution.

More InformationAnalyzing and Maintaining a Single Table [page 177]

Documents

Cockpit 702 730 Final