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

Transcription

1 Database Administration Guide Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows For SAP Systems based on SAP Enhancement Package 1 for SAP NetWeaver 7.0 Document Version 1.00 September 8th, 2008 Public SAP AG Dietmar-Hopp-Allee Walldorf Germany T +49/18 05/ F +49/18 05/

2 Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the 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 the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

3 Typographic Conventions Icons Type Style Example Text Example text EXAMPLE TEXT Example text Example text <Example text> EXAMPLE TEXT Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. Icon Meaning Caution Example Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

4 Contents Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows The DBA Cockpit SAP GUI-Based User Interface Central System Data Maintenance Actions in the DBA Cockpit Configuration of Systems for Remote Monitoring Configuring Systems for Remote Monitoring Using Remote Database Connections Configuration of Database Connections Deleting a Database Connection Configuring Systems for Remote Monitoring Using the System Landscape Directory (SLD) Web Browser-Based User Interface (Web Dynpro) Performance Performance: Partitions Performance: Database Database: Buffer Pool Database: Cache Database: Asynchronous I/O Database: Direct I/O Database: Real Time Statistics Database: Locks and Deadlocks Database: Logging Database: Calls Database: Sorts Database: XML Storage Performance: Schemas Performance: Buffer Pools Buffer Pool Buffer Pools: Asynchronous I/O Buffer Pools: Direct I/O Buffer Pools: XML Storage Performance: Tablespaces Tablespaces: Buffer Pool Tablespaces: Asynchronous I/O Tablespaces: Direct I/O Tablespaces: XML Storage Performance: Tables Performance: Applications Applications: Application Applications: Agents Applications: Assigned Agents Applications: Agents Memory September 2008

5 2.7.5 Applications: Buffer Pool Applications: Direct I/O Applications: XML Storage Applications: Locks and Deadlocks Applications: Calls Applications: Sorts Applications: Cache Applications: Unit of Work Applications: Statement Applications: Statement Text Applications: SQL Workspace Performance: SQL Cache Performance: Lock Waits and Deadlocks Performance: Inplace Table Reorganization Performance: History - Database Performance: History Tables Performance: Performance Warehouse Performance Warehouse: Reporting Performance Warehouse: Configuration Space Space: Automatic Storage Space: Tablespaces Maintaining Tablespaces Space: Containers Space: Tables and Indexes Space: Single Table Analysis Space: Virtual Tables Space: History - Overview Space: History - Database and Tablespaces Space: History - Tables and Indexes Backup and Recovery Backup and Recovery: Backup Overview Backup and Recovery: Logging Parameters Configuration Configuration: Overview Configuration: Database Manager Configuration: Database Maintaining the Database Configuration Comparing Database Configuration Parameters for Several Database Partitions Configuration: Registry Variables (DB2 for Linux, UNIX, and Windows Configuration: Parameter Changes Configuration: Database Partition Groups Maintaining Database Partition Groups Configuration: Buffer Pools Maintaining Buffer Pools September

6 5.8 Configuration: Special Tables Regarding RUNSTATS Configuration: File Systems Configuration: Data Classes Maintaining Data Classes Configuration: Monitoring Settings Configuration: Automatic Maintenance Settings Configuring General Maintenance Settings Configuring Automatic Backup Settings Configuring Automatic RUNSTATS Settings Configuring Automatic REORG Settings Jobs Central Calendar Using the Central Calendar The DBA Planning Calendar Setting Up the DBA Planning Calendar Scheduling an Action Changing an Action Deleting an Action Executing an Action Displaying the Status of a Day s Actions Displaying Scheduled Actions Troubleshooting Updating Statistics Scheduling a REORGCHK for All Tables Reorganizing Tables Database Backups Archiving Log Files To Tape Scheduling Scripts The DBA Log Back-End Configuration The SQL Script Maintenance Alerts Alerts: Database System Monitoring in CCMS Alerts: Configuring Database System Monitoring Alerts: Alert Monitor Alerts: Alert Message Log Alerts: Alert Configuration Diagnostics Diagnostics: Displaying the Audit Log The EXPLAIN Function The EXPLAIN Function (New Web Browser-Based Version) The EXPLAIN Function (SAP GUI-Based Version) EXPLAIN Options Diagnostics: Missing Tables and Indexes Diagnostics: Deadlock Monitor Creating the Deadlock Monitor September 2008

7 8.4.2 Deadlock Monitor Analysis Diagnostics: SQL Command Line Diagnostics: The Index Advisor Retrieving Index Recommendations Defining Virtual User-Defined Indexes Validating Indexes Using the EXPLAIN Function Creating Indexes in the ABAP Dictionary Diagnostics: Cumulative SQL Trace Diagnostics: DBSL Trace Directory Diagnostics: Trace Status Diagnostics: Database Notification Log Diagnostics: Database Diag Log Diagnostics: DB2 Logs Diagnostics: Dump Directory Diagnostics: DB2 Help Center Workload Management Workload Management: Workloads and Service Classes Workload Management: Critical Activities Workload Management: SAP WLM Setup Status BI Administration BI Administration: BI Data Distribution BI Administration: MDC Advisor September

8 Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows This document explains how you administer your database using the DBA Cockpit, which allows you to monitor, control and configure your database. The DBA Cockpit [page 9] provides you with access 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 or database system, which could adversely affect the SAP system Analyzing and tuning the SAP system and environment (host and database systems) to optimize the throughput of the SAP system Configuring the database This document applies to SAP systems that are based on SAP Enhancement Package 1 for SAP NetWeaver 7.0 More Information For more information about running an SAP system on DB2 for Linux, UNIX, and Windows, choose the SAP on DB2 for LUW in the SDN pushbutton in the navigation frame of the DBA Cockpit. For DB2-specific information, see the respective IBM DB2 Information Center for your database and the following IBM manuals: IBM DB2 System Monitor Guide and Reference IBM DB2Performance Guide. 8 September 2008

9 1 The DBA Cockpit The DBA Cockpit is a platform-independent tool that you can use to monitor and administer your database. You access the DBA Cockpit by calling transaction DBACOCKPIT. Then, the initial screen DBA Cockpit: System Configuration Maintenance appears. Features You can choose between the following user-interfaces: SAP GUI-based user interface Web browser-based user interface Activities You can use the DBA Cockpit to: Navigate between different actions Change to another action without closing the previous action and still hold all data retrieved 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 system you want to monitor. The local system is configured automatically when you start the DBA Cockpit for the first time. After having configured the connection and depending on the database, more actions are required to configure the database monitor and to set up database administration. Caution For systems that are monitored using a remote database connection, constraints depend on whether: o o The database release of the remote system is compatible to the database release of the local system. You want to monitor an ABAP-only or a Java-only SAP system. End of the caution. More Information SAP GUI-Based User Interface [page 10] Web Browser-Based User Interface (Web Dynpro) [page 22] September

10 1.1 SAP GUI-Based User Interface The entry screen of the DBA Cockpit using the GUI-based user interface is divided into the following areas: Application toolbar System landscape toolbar Central system data Action area Navigation frame Action message window Framework message window Application Toolbar Provides a minimum of functions, for example, to display or hide the areas on the left side. System Landscape Toolbar Provides central functions to manage the system landscape, for example: Access to system configuration where you configure and set up your system landscape Management of database connections Lets you choose the system to monitor. Additional information about a distributed database system is displayed if available. Navigation Frame Displays a tree structure divided at the top level into the main task areas of database administration. These are, for example, performance monitoring, space management, and job scheduling. Within each task area, there is a set of related action nodes. 10 September 2008

11 Central System Data This area is common to most actions. It provides, for example, the following data: Time of last refresh Database startup time Name of database Action Area Displays the details of the currently selected action. Action Message Window Only appears with certain actions and displays additional information that is related to the selected action. Framework Message Window Displays the message window provided by the framework. Unlike the classic SAP GUI messaging process, the framework message window contains a complete history of all messages sent during the session. In addition, you can: Clean up the window by choosing the Clear Message Window pushbutton. Collapse or expand or the window by choosing either the Minimize Message Window or the Show Message Window pushbutton. Check if a long text for a message is available by double-clicking the message or by choosing Show Long Text. Print the message text by choosing the Print Version pushbutton. Changes to the screen area sizes are user-specific and are restored when you next start the DBA Cockpit. More Information Central System Data [page 12] Maintenance Action in the DBA Cockpit [page 13] Configuration of Systems for Remote Monitoring [page 14] September

12 1.1.1 Central System Data Most of the DBA Cockpit screens provide a unique subscreen area displaying the central system data of the selected screen: Field Last Refresh DB Name Started DB Release Date and time when the screen data was last refreshed Name of database of the selected system Date and time when the database engine started Database release Date and time of last reset or checkpoint of the monitored data Last Reset/Checkpoint This field is available only for actions that support Reset/Since Reset or Set Checkpoint/Delta to Checkpoint. The currently selected set of data. This is available for actions that support Reset/Since Reset: Since DBM Start Reset Current Selection Since Reset And for actions supporting checkpoints: Current Configuration Checkpoint Set Delta to Checkpoint Currently selected system System This field is only available if the navigation frame has been hidden using the Full Screen on/off function. In this case, you can select the required system in this field. 12 September 2008

13 Partition of currently selected system Partition This field is only available if the navigation frame has been hidden using the Full Screen on/off function. In this case, you select the required partition in this field Maintenance Actions in the DBA Cockpit The DBA Cockpit provides a set of actions to monitor and to maintain the database. To be able to perform these actions, the SAP user requires some additional authorizations. The maintenance actions provided in the DBA Cockpit set locks to prevent parallel processing. All changes to the database are recorded in an audit log file. Authorization Check When you start the DBA Cockpit or change to another system in the DBA Cockpit, an authorization check is performed. Granting of Database Permissions To be able to access the database, the user used for remote monitoring must at least have sufficient authorizations. Local systems use the connect user for monitoring tasks. This user already has sufficient permissions. If more authorizations are required for administrative actions, a second connection using the database administration user is used. Systems monitored via remote database connections use the user specified for the database connections. This user must have sufficient authorizations. Locking of Actions For each maintenance action that you have selected using the DBA Cockpit, a lock is set for the system being monitored. All locks are released when you exit the DBA Cockpit or when you change to another system. Auditing of Maintenance Actions The following only applies to Oracle and IBM DB2 for Linux, UNIX, and Windows. When you make changes that affect database objects such as database configuration parameters or tablespaces, an audit log is written. You can display this audit log in the DBA Cockpit. For more information, see Displaying the Audit Log. September

14 1.1.3 Configuration of Systems for Remote Monitoring To be able to use the DBA Cockpit to monitor remote systems, you have to configure those systems in the DBA Cockpit. You can configure your database system either using database information that is stored in the system landscape directory (SLD) for automatic generation and update of system entries or manually using database connections and system entries. You access the screen DBA Cockpit: System Configuration Maintenance by choosing System Configuration in the DBA Cockpit. A list of all monitored systems is displayed with an icon showing the current status of a system. You can change the status of a system by choosing Stop or Go. In the event of severe errors, we recommend that you disable your system to prevent further problems. After you have investigated and corrected the error, you have to enable your system again. Normally, when you start the DBA Cockpit, the local system is set as default system. To change this setting, select a system from the list and choose Default System. This setting only applies to the user currently logged on to the system. It is not a system-wide setting. You use one of the following methods to monitor a system remotely: Remote database connections This method uses additional connections. It is the main access method for monitoring and administration tasks and is mandatory. You can specify remote connections for any database and maintain the connections using the DBA Cockpit. For more information, see Maintaining Database Connections. RFC connection For this method you have to assign an RFC connection to your system. RFC connections are available for SAP ABAP systems only. You can use RFC connections: As an optional access path for ABAP-related monitoring functions, for example, for the consistency check of the ABAP Dictionary. That is, the DBA Cockpit uses the RFC connection in parallel to the database connection for the same system. You can only maintain RFC connections with transaction SM59, not with the DBA Cockpit. More Information: Configuring Systems for Remote Monitoring Using Remote Database Connections Configuring Systems for Remote Monitoring Using the System Landscape Directory (SLD) 14 September 2008

15 ... Database Administration Using the DBA Cockpit: IBM DB2 for LUW Configuring Systems for Remote Monitoring Using Remote Database Connections Use You use this procedure to configure systems that you want to monitor using remote database connections. Depending on the database platform of the selected system, some options might not be available. In this case you cannot enter any data in the corresponding fields. Prerequisites The system(s) you want to monitor must have a database release that is compatible with the database release of your local database. The user for the database connection must have sufficient database permissions. For more information, see Maintenance Actions in the DBA Cockpit. Procedure Adding a System 1. Call the DBA Cockpit. The screen DBA Cockpit: System Configuration Maintenance appears. It displays a list of all systems available with a Stop, Go, or Inactive icon, which shows the current system status. When you start the DBA Cockpit for the first time, the local system is automatically added to the list of all systems available. At least one system entry is displayed. 2. Choose Add. The screen Configuration: System Administration Add System Entry appears. 3. Specify the connection data as follows: a. In the System field, enter the name of the system you want to monitor. This name is a unique ID and does not need to be the SAP system ID. You can choose any name except the SAP system ID of the local system, which is reserved for the local system entry. Except for the local system entry, Remote Database is already selected. b. Select Database Connection. Enter the name of the database connection. If the database connection does not yet exist, you are directed to the DB Connections: Add Connection Entry screen where you can specify all relevant data for the new connection. For more information, see Configuration of Database Connections. c. After you have saved your entries, you are redirected to the screen System Administration Details. September

16 Database Administration Using the DBA Cockpit: IBM DB2 for LUW d. If an additional RFC destination is used for special ABAP monitoring functions or if the connection is initially routed using an RFC connection (MS SQL Server only), select RFC Destination, too. e. If required, enter the name of the RFC connection. After the connection data has been completed, it is displayed on the System Data tab page. You can enter additional data on the Administration Data tab page as follows: Enter a description of your system. Depending on the database platform, select the options for how you want to collect monitoring data: If alerts are to be provided for the RZ20 alert monitor, select Collect Alert Data. If data about the performance or the size of database objects is to be collected, select Collect Space and Performance History Data. If the task of collecting monitoring data is running on the remote system, select Data Collection by Remote System. This function is only available for IBM DB2 for i. If data for the central planning calendar is to be provided, select Collect Central Planning Calendar Data. 4. Save your changes. Changing the Connection Parameters of a System 1. Perform step 1 as described above under Adding a System. 2. Select a system. 3. Choose Edit. The screen Configuration: System Administration Change System Entry appears. 4. Enter your changes in the corresponding fields. 5. Save your changes. Deleting a System Entry 1. Perform step 1 as described above under Adding a System. 2. Select a system. 3. Choose Delete. 16 September 2008

17 ... Database Administration Using the DBA Cockpit: IBM DB2 for LUW Configuration of Database Connections Purpose This section describes how you set and maintain technical attributes for remote database connections. The DBA Cockpit uses these connections for administration and monitoring or for application programs that use secondary connections to external databases. Process Flow 1. You call the DBA Cockpit and choose DB Connections in the system landscape toolbar. The screen DBA Cockpit: Database Connections appears displaying a list of all available database connection definitions grouped by database platform: Column Remote Database Name of database connection Connections DB Name DB Host DB Schema User Permanent Max. Connections Opt. Connections Name of database Name of database host This is a unique name that you can freely choose. Name of the database schema to be monitored Name of the connection user Specifies whether the connect user must be permanently available Maximum allowed number of open connections Optimal number of connections By default, the database connections that are defined in the local system are displayed. 2. You are able to perform one of the following tasks: You add database connections. You change an existing database connection. You delete a database connection. You test a database connection. More Information: Adding a Database Connection Changing a Database Connection Deleting a Database Connection Testing a Database Connection September

18 ... Database Administration Using the DBA Cockpit: IBM DB2 for LUW Adding a Database Connection 1. Call the DBA Cockpit. 2. In the system landscape toolbar, choose DB Connections. 3. Choose Add. The screen DB Connections Add Connection Entry appears. 4. In the Connection Name field, specify the name of the connection. This name is a unique ID that you can choose freely except for names that are reserved by SAP for generated connections. These can be, for example, administrator connections or connections that are used by systems from the system landscape directory (SLD). 5. Specify the database connection attributes as follows: a. In the Database System field, specify the name of the database platform. b. In the Connection Maximum field, enter an appropriate value. This value limits the number of database connections that are currently held by the SAP system. The SAP system does not let you exceed this limit. c. In the Connection Optimum field, enter an appropriate value. This value is a more flexible limit that can be exceeded. d. If you want the connection to be mandatory for the SAP system, select Permanent Connection. This parameter defines the availability of the database connection. It is then handled like the local default connection, that is, if this database connection is not available for a work process, the work process of the SAP system cannot run. You should set this parameter only if this connection is absolutely required to run your SAP system. e. In the User Name field, enter the name of the connect user. Make sure that you choose a user with the appropriate authorizations. For more information, see Maintenance Actions in the DBA Cockpit. f. In the Password field, enter a password for the connect user. 18 September 2008

19 C... Database Administration Using the DBA Cockpit: IBM DB2 for LUW 6. In the Connection Parameters table, specify the following additional database-specific attributes: Attribute Database Name Name of database Service Name Database Host Schema Name Name or number of the service This value corresponds to the parameter SVCENAME of the database manager configuration (DBM) of the remote database. Name of the remote database server Name of schema to be monitored If you omit this field, the name of the specified connect user is used as default schema. To support new connection parameters and for support scenarios, you might have to add connection parameters in an unchecked raw format. To be able to do so, choose Guided Mode <-> Expert Mode and switch to the expert mode. In the expert mode, you can enter connection parameters as a string instead of using the guided mode. However, we do not recommend that you use the expert mode. 7. To confirm your entries, choose Save. Result As soon as the connection has been specified, the DBA Cockpit connects automatically to the newly added database system and displays data on the System Data tab page Changing a Database Connection 1. Call the DBA Cockpit. 2. In the system landscape toolbar, choose DB Connections. 3. Select a database connection entry and choose Edit. The screen DB Connections Change Connection Entry appears. 4. Enter your changes in the appropriate fields as described in Adding a Database Connection. 5. Save your changes. September

20 Database Administration Using the DBA Cockpit: IBM DB2 for LUW Testing a Database Connection Use You test a database connection to make sure that, for example, you entered the correct user and password information as well as the correct technical connection data, such as host name. Procedure 1. Call the DBA Cockpit. 2. In the system landscape toolbar, choose DB Connections. 3. Select a system and choose Test. The result is displayed in the message window below Deleting a Database Connection 4. Call the DBA Cockpit. 5. In the system landscape toolbar, choose DB Connections. 6. Select a system and choose Delete. If the selected database connection is still in use by a system that is registered in the DBA Cockpit, you cannot delete it Configuring Systems for Remote Monitoring Using the System Landscape Directory (SLD) Use The system landscape directory (SLD) contains data from all database systems available in your system landscape. You can use this data to set up the system configuration in the DBA Cockpit instead of setting it up manually. When you set up the DBA Cockpit for the first time, you use this procedure to import the appropriate data from the SLD. During production operation, you use the procedure to synchronize the data between the SLD and the DBA Cockpit periodically. Procedure 1. To import database connection data from the SLD, call the DBA Cockpit. 2. In the system landscape toolbar, choose System Configuration. The screen The DBA Cockpit: System Configuration Maintenance appears. 3. Choose SLD System Import. The SLD System Import screen appears. Depending on the system landscape, one or more of the following nodes are displayed: 20 September 2008

21 New Database Systems in the SLD All database systems registered in the SLD that are so far unknown to the DBA Cockpit are displayed. Changed Systems From Earlier SLD Imports All database systems for which the main data differs between the SLD and the DBA Cockpit are displayed. Systems No Longer Registered in the SLD All systems that were originally imported from the SLD into the DBA Cockpit but that are no longer registered in the SLD are displayed. Systems Identical in the SLD and in the DBA Cockpit All systems that are registered in the SLD and that are identical in the DBA Cockpit are displayed. Unsupported Database Systems in the SLD All database systems that are registered in the SLD but not supported by the DBA Cockpit are displayed. Each database system is described as follows: <Name (system ID) of the database system> on <main database host> ( <database platform> ) The actions allowed for each database system are displayed in the second column of the tree. 4. To import database system data, select the actions that you want to execute for the selected database systems and choose Import. By default, only the import of new database systems is selected. The selected actions are executed. A short message for each executed action is displayed in the message window below. Connection data that is retrieved from the SLD might not be complete for one of the following reasons: Depending on the data provided by a system to the SLD, some connection data can be incomplete. User or password data is generally not available via SLD. When you establish the connection to an imported system, the DBA Cockpit checks the completeness of a configured system. That is, if necessary, you are prompted for user, password and connection information. If additional connection information is required, enter the required data according to the maintenance dialog that is described in Configuration of Database Connections. September

22 1.2 Web Browser-Based User Interface (Web Dynpro) The Web browser-based user interface differs from the classical SAP GUI-based user interface with regard to the overall screen layout and navigation, customizing of the user interface and the provided functions. To start the Web browser-based user interface, call the DBA Cockpit and choose Start Web Dynpro GUI, which starts the browser in a separate window. Like on the SAP GUI-based user interface, the entry screen displays the list of the configured systems. Caution The Web browser-based user interface does not support all functions available on the SAP GUI-based user interface; especially maintenance actions are not provided. On the other hand, actions that have been introduced with DB2 Version 9.5 are available only on the Web browser-based user interface, for example, workload management and performance warehouse (SAP BI). End of the caution. Navigation and Screen Layout The entry screen of the DBA Cockpit with the Web browser-based user interface is divided into the following areas: Common header area Top level navigation including second-level navigation Framework message window Detail navigation Central system data System landscape selector Content area Favorite list Content detail area 22 September 2008

23 Common Header Area Provides a standard set of functions, for example, to refresh or to customize the layout. Top Level Navigation Including Second-Level Navigation In the top level navigation, you can switch between the following two areas: Cross-system area Provides information about the overall system landscape. Database-specific area Provides information about the selected database. In the second-level navigation, the main task areas of database administration are provided for this area, for example, performance monitoring, space management and job scheduling. Detail Navigation Contains the main actions of the main task areas. Depending on the selected main action, a subset of related actions is available. Example If you chose Performance in the top level navigation area, the following main actions are available: Inplace Table Reorganization Performance Warehouse Snapshots History If you choose Performance Warehouse, the subactions Reporting and Configuration become available. End of the example. System Landscape Selector Provides a quick overview of all configured systems. This area is described in more detail under Customizing of the System Landscape Selector later in this section. September

24 Favorite List Contains a list of favorite links to special actions. To provide quick access to specific actions, choose Personalize Add Favorite in the common header area. An entry is added to your list of favorites. By choosing Personalize Organize Favorites, you can rename or delete favorites. By default, the favorite list contains a link to the EXPLAIN Access Plan and to the SQL Command Line. Both entries cannot be removed. Framework Message Window Displays the message window that is provided by the framework. Unlike the classic SAP GUI message processing, this window contains a complete history of all messages that are sent during the session. In addition, you can: Collapse or expand the window by choosing Expand Message Window or Collapse Message Window. Check if a long text for a message is available by double-clicking the message or by choosing Details. By default, the message window is collapsed. When a new message is generated, it is automatically expanded. Central System Data This area is common to most actions providing, for example, the time of the last refresh, the startup time and the database name. Content Area Displays details of the currently selected action. Content Detail Area Only appears with certain actions and displays additional information that is related to the selected action. Typically, this area shows details that are related to some list display. 24 September 2008

25 Customizing the System Landscape Selector By default, all systems are displayed without any grouping or filtering. For each configured system, the alert status, the name of the system and its database host is displayed. The following 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 the selected criteria: o o o o Database Platform Name Custom 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 Group Systems by Selected Criteria. Specify a name for the custom group and assign the systems of your choice. As soon as you have added a custom group, the option Organize Groups becomes available in the pop-up menu of the menu button Group Systems by Selected Criteria, 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 the filter 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 Information The EXPLAIN Function [page 202] Diagnostics: SQL Command Line [page 217] September

26 2 Performance The following sections provide information on performance: Performance: Partitions [page 26] Performance: Database [page 28] Performance: Schemas [page 42] Performance: Buffer Pools [page 43] Performance: Tablespaces [page 50] Performance: Tables [page 56] Performance: Application [page 57] Performance: SQL Cache [page 81] Performance: Lock Waits and Deadlocks [page 85] Performance: Inplace Table Reorganization [page 87] Performance: History Database [page 89] Performance: History Tables [page 91] Performance: Performance Warehouse [page 92] 2.1 Performance: Partitions In multi-partition database systems this overview screen provides a selection of performance data that is related to each partition. You can use the information to identify performancecritical partitions before starting a more detailed analysis of your database. You can access the Partition Overview screen by calling the DBA Cockpit and choosing Performance Partitions in the navigation frame of the DBA Cockpit. For each partition of your database system, the following information is displayed: Partition Column Number of the partition (only displayed in a multi-partition database) No. Buffer Pools Number of buffer pools used for a partition Total Size Buffer Pools Data Logical Reads Index Logical Total size in KB of all buffer pools used for a partition Number of read accesses to data in the buffer pool Number of read accesses to index data in the buffer pool 26 September 2008

27 Column Reads Data Physical Reads Index Physical Reads Avg. Phys. Read Time (ms) Avg. Phys. Write Time (ms) Executed SQL Statements Package Cache Size Package Cache Quality (%) Number of read accesses to data on disk (I/O) The value includes the number of physical reads that were performed synchronously (by the database manager agents) and asynchronously (by the I/O servers). 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 index pages. Average time in milliseconds required to read data from disk into the buffer pool Average time in milliseconds required to write data from the buffer pool to disk Number of executed SQL statements (SELECT, INSERT, UPDATE, DELETE) Amount of application heap memory to be used for caching a package s static and dynamic SQL statements As of DB2 Version 5, each database agent accesses a global cache. Tells you whether or not the package or catalog cache is being used effectively. If the hit ratio of the package or catalog cache is greater than 95%, the cache is performing well. If you double-click a line, a database snapshot data is retrieved and displayed as described in Performance: Database [page 28]. September

28 2.2 Performance: Database The Database Snapshot screen provides an overview of the following critical database performance indicators: Buffer Pool [page 28] Cache [page 31] Asynchronous I/O [page 32] Direct I/O [page 33] Real-Time Statistics [page 34] Locks and Deadlocks [page 35] Logging [page 36] Calls [page 38] Sorts [page 40] XML Storage [page 41] You can access the Database Snapshot screen by calling the DBA Cockpit and choosing Performance Database in the navigation frame of the DBA Cockpit. The Database Snapshot screen is the initial screen of the SAP database monitor for DB2 for Linux, UNIX and Windows. The system displays values collected since the database was started. If the database is shut down, the values are deleted. The values displayed are not really meaningful until the database has been running for some time. The longer the database has been running, the more useful the values Database: Buffer Pool To display an overview of buffer pool information, call the DBA Cockpit. 1. In the navigation frame, choose Performance Database. The Database Snapshot screen appears. 2. Choose Buffer Pool. 28 September 2008

29 Field Buffer Pools Number Total Size Number of buffer pools Total size in KB of all buffer pools Buffer Quality Overall Buffer Quality Data Hit Ratio Index Hit Ratio No Victim Buffers Indicates percentage at which the data is read from the buffer pool, rather than directly from the hard disk This is calculated using the following formula: (logical reads - physical reads) / (logical reads) * 100 Indicates percentage at which data (without index data) is read from the buffer pool, rather than directly from the hard disk Indicates the frequency as a percentage at which index data is read from the buffer pool, rather than directly from the hard disk Number of times an agent did not have a preselected victim buffer available Average Time Physical Reads Physical Writes Average time in milliseconds required to read data from disk into the buffer pool Average time in milliseconds required to write data from the buffer pool to disk Data Logical Reads Number of read accesses to data in the buffer pool Number of read accesses to data on disk (I/O) Physical Reads The value includes the number of physical reads that were performed synchronously (by the database manager agents) and asynchronously (by the I/O servers). Number of write accesses to data on disk (I/O) Physical Writes Synchronous Reads The value includes the number of physical writes that were performed synchronously (by the database manager agents) and asynchronously (by the I/O cleaners). Number of read accesses to data on disk (by agents) September

30 Field 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 data pages into the temporary tablespace Temporary Physical Reads Number of physical read requests that required I/O to get data pages into the temporary tablespace Index Logical Reads Physical Reads Number of read accesses to index data in the buffer pool 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 index pages. Number of write accesses to index data on disk (I/O) Physical Writes Synchronous Reads Synchronous Writes The value includes the number of physical writes that were performed synchronously (by the database manager agents) and asynchronously (by the I/O cleaners). Number of read accesses to index data on disk (by agents) 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 index pages into the temporary tablespace Temporary Physical Reads Number of physical read requests that required I/O to get index pages into the temporary tablespace 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 asynchronous accesses. 30 September 2008

31 2.2.2 Database: Cache To display information on the cache, call the DBA Cockpit. 1. In the navigation frame, choose Performance Database. The Database Snapshot screen appears. 2. Choose Cache. Field Catalog Cache Maximum allowed size in KB for the catalog cache Size The catalog cache is accessed each time a transaction accesses a table, view or alias. The cache is allocated dynamically from the heap. The maximum allowed size is determined by database configuration parameter CATALOGCACHE_SZ. Quality Lookups Inserts Overflows High-Water Mark Indicates percentage at which the data is read from the catalog cache, rather than directly from the hard disk This is calculated using the following formula: (catalog cache lookups - catalog cache inserts) / catalog cache lookups * 100 Number of times that the catalog cache was referenced to obtain table descriptor information Number of times that the system tried to insert table descriptor information into the catalog cache Number of times that an insert into the catalog cache failed due to the catalog cache being full Largest size reached by package cache Package Cache Size Maximum allowed size in KB for the package cache The package cache contains access plans. The maximum allowed size is determined by database configuration parameter PCKCACHESZ. September

32 ... Database Administration Using the DBA Cockpit: IBM DB2 for LUW Quality Lookups Inserts Overflows High-Water Mark Indicates percentage at which the data is read from the package cache, rather than directly from the hard disk This is calculated using the following formula: (package cache lookups - package cache inserts) / package cache lookups *100 Number of times an application looked for a section in the package cache Total number of times that an access plan was not available for use and had to be loaded into the package cache Number of times that the package cache overflowed the bounds of its allocated memory Largest size reached by the package cache Database: Asynchronous I/O To display information on I/O servers and I/O cleaners, call the DBA Cockpit. 1. In the navigation frame, choose Performance Database. The Database Snapshot screen appears. 2. Choose Asynchronous I/O. Field I/O Number of I/O Servers Number of I/O Cleaners Average Time Asynchronous Physical Reads Asynchronous Physical Writes Number of I/O servers that read data asynchronously from the hard disk into the buffer pool Number of I/O cleaners that write data asynchronously from the buffer pool to the hard disk Average time in milliseconds required by the I/O servers to read a page from disk and write it to the buffer pool Average time in milliseconds required by the I/O cleaners to read a page from the buffer pool and write it to the hard disk 32 September 2008

33 ... Database Administration Using the DBA Cockpit: IBM DB2 for LUW Data Asynchronous Physical Reads Asynchronous Physical Writes Asynchronous Read Requests Index Asynchronous Physical Reads Asynchronous Physical Writes Asynchronous Read Requests Number of data pages that were read asynchronously from disk and written to the buffer pool by the I/O servers (prefetch) Number of data pages that were written asynchronously from buffer pool to disk (I/O cleaners) Number of asynchronous data read requests Number of index pages that were read asynchronously from disk and written to the buffer pool by the I/O servers (prefetch) Number of index pages that were written asynchronously from buffer pool to disk (I/O cleaners) Number of asynchronous index read requests Data is read or written in pages. A page can be 4 KB, 8 KB, 16 KB, or 32 KB in size Database: Direct I/O To display information on direct I/O, call the DBA Cockpit. 1. In the navigation frame, choose Performance Database. The Database Snapshot screen appears. 2. Choose Direct I/O. Field Average Time Direct Reads Direct Writes I/O Direct Reads Direct Writes Average time in milliseconds required to read directly from disk Average time in milliseconds required to write directly to disk Read accesses from disk that do not use the buffer pool (LONG VARCHAR fields, backup) Write accesses to disk that do not use the buffer pool (LONG VARCHAR fields, restore, load) September

34 Average I/O per Request Direct Reads Direct Writes Average number of requests to read directly from disk Average number of requests to write directly to disk Database: Real Time Statistics To display information on real-time statistics, call the DBA Cockpit. 1. In the navigation frame, choose Performance Database. The Database Snapshot screen appears. 2. Choose Real-Time Statistics. Field Size of Statistics Cache Number of Asynchronously Collected Statistics Number of Statistics Collections During Query Compilation Time Spent During Query Compilation Number of Synchronously Collected Statistics Time Spent on Synchronous Statistics Collection Activities Size of statistics cache in bytes Total number of successful asynchronous statistics collection activities Total number of statistics collection activities for creating statistics by the system without table or index scan during query compilation Total time spent on creating statistics by system without table or index scan during query compilation in milliseconds Total number of synchronous statistics collection activities during query compilation Total time spent on asynchronous statistics collection activities in milliseconds 34 September 2008