What's New in the DBA Cockpit with SAP NetWeaver 7.0 Applies to: Database monitoring and administration of SAP systems running on DB2 for Linux, UNIX, and Windows using the latest DBA Cockpit that has been provided with SAP release 7.10 and SAP NetWeaver 7.0 SP12. Summary As of SAP Netweaver 7.0 SP12 and SAP systems based on kernel 7.10, the DBA Cockpit provides new functions and full support of the latest database release DB2 9. This document provides an overview of the main differences to previous releases and describes the required steps that you have to perform to upgrade to the new DBA Cockpit. Author: Ralf Stauffer Company: SAP AG Created on: 29 May 2007 Author Bio Ralf Stauffer is a development architect at SAP AG. He joined SAP in 1993, where he started to work as a developer in the R/2 basis. Today his area of coverage includes database monitoring and adminstration for the DB2 LUW database and platform-independent database monitoring tools. He has a degree in computer science from the University of Kaiserslautern, Germany. You may reach him at ralf.stauffer@sap.com. 2007 SAP AG 1
Table of Contents Support of New Functions in DB2 9... 3 Technical Infrastructure... 3 Extended Monitoring Information... 3 Self Tuning Memory Management (STMM)... 3 Row Compression... 3 AutoStorage for DPF... 3 Managing System Landscapes... 4 Migrating Existing System Landscapes... 4 New Monitoring and Administration Functions... 5 Collection of History Data for Tables and Bufferpools... 5 Alert Monitor Status... 5 DB2 Registry Settings... 5 Configuration of Automatic Maintenance Settings... 5 Integration of the DB2 HelpCenter... 5 Functional Enhancements... 6 Table Reorganization... 6 Table Analysis... 6 Configuration Parameters... 6 DBA Planning Calendar... 6 Evaluation of Database Diagnostic Files... 6 Discarded Functions... 7 CLP Commands... 7 Diagnostics->Control Panel... 7 Diagnostics->Single System Check... 7 Kernel Dependencies... 7 Related Content... 8 Copyright... 9 2007 SAP AG 2
Support of New Functions in DB2 9 With the latest database release of DB2, there are a lot of changes and new functions, that influence monitoring and administration of your database. As the DBA Cockpit for SAP Netweaver 7.0 was originally developed based on DB2 Version 8.2, we had to adapt the DBA Cockpit to support these new features of DB2 9. The major changes refer to the technical infrastructure, support for new functions like the self-tuning memory management and extended monitoring capabilities as described in the following sections. Technical Infrastructure All backend functions of the DBA Cockpit have been implemented based on SQL access and do no longer use any API calls. As a consequence, you can now run all your monitoring functions together with a DB2 thin client installation. Extended Monitoring Information New snapshot monitoring elements have been added to the performance area of the DBA Cockpit. Self Tuning Memory Management (STMM) You can monitor memory areas, which are managed by the STMM, via Performance->Bufferpools. In this area there is an additional history function, that displays a graphic of the recorded history of changes. Row Compression In Space Single Table Analysis, the detailed information of tables has been extended to show all relevant data that is related to row compression, for example System catalog information Table status information retrievable by new ADMIN_GET_TAB_INFO function Estimated savings of space to identify candidates for compression In addition, you can check, enable or disable row compression directly in the Space Single Table Analysis area. Regular checking for compression candidates can be scheduled by using the job REORGCHK for all Tables. This job contains an additional parameter to perform compression checks for all tables. By default, no compression information is evaluated. The calculated data is stored in the local database and you can evaluate it in the Space->Tables and Indexes area, that offers appropriate selection criteria for this data. AutoStorage for DPF Maintenance of DB2's automatic storage management, which has been available already for single node systems in SAP NetWeaver 7.0 is now available for multi-partitioned databases. 2007 SAP AG 3
Managing System Landscapes The system administration has been extended and will be directly coupled with the system landscape directory ( SLD ). The details of the new system configuration are described in the separate document Monitoring System Landscapes using the DBA Cockpit. Migrating Existing System Landscapes Monitoring and administration of a remote database is no longer based on RFC destinations, but you can perform these tasks using remote database connections instead. This has the advantage, that there are no prerequisites for the monitored database. This means, that you can monitor any DB2 database, which offers you the full set of functions of the DBA Cockpit and full DB2 9 support even for outdated SAP releases. On the other hand, you must perform additional configuration steps to enable these new functions wiithin the DBA Cockpit, which is. Activate the alert monitoring Activate of collection of history data Integrate the system into the central DBA planning calendar These configuration steps are part of the system administration and must be explicitly specified when a system is integrated into the DBA cockpit. Using RFC Destinations As the use of RFC destination is no longer supported, already existing system entries will be automatically converted. This is done by generating database connection configuration entries, that are based on the information available through the RFC channel. The only mandatory information, which cannot be automatically retrieved, is user credentials for the database connection. You will be prompted, when a system is selected for monitoring for the first time. Administration Connections As pointed out in the previous section, monitoring technically supports only the DB2 thin client. As a consequence, all activities must be performed via SQL access only. This implies, that the connection user must have the appropriate authorizations, especially when executing administration tasks like tablespace maintenance or changes to the database configuration. In case of remote databases this isn't really a problem, because the DBA is free to setup a database connection with a user, that has all the required authorizations. But for the local system, there is only the SAP standard user available, which typically does not and shall not have administration authorizations. Therefore the DBA Cockpit uses an additional database connection and always asks for a user and password the first time this connection is really required. Note: To enable the collection of history data for remote database, the history tables have been changed and will be recreated when a system is upgraded or the SP12 Support Package is imported into your SAP system. As a consequence, the complete "old" history information will be lost. You can find a more detailed description, about how to configure a database for monitoring in Monitoring System Landscapes Using the DBA Cockpit. 2007 SAP AG 4
New Monitoring and Administration Functions Based on new functions in DB2 9, there is a couple of new monitoring actions available, that are described in more detail in the next sections. Collection of History Data for Tables and Bufferpools Snapshot data of tables and bufferpools is collected regularly and stored in the local database. Table snapshot data is collected daily, bufferpool snapshot data is collected every 2 hours. The data collection is triggered via the standard job SAP_COLLECTOR_FOR_PERFMONITOR. Alert Monitor Status A simplified view of the RZ20 alert monitoring tree has been integrated in the DBA Cockpit. It is available for each monitored system, that has been configured for remote alert monitoring. DB2 Registry Settings The registry settings for the database are displayed under Configuration Registry Settings. SAP standard settings are automatically checked, whether they have been overwritten. Configuration of Automatic Maintenance Settings Configuring the policies for DB2 automatic maintenance is now available in the DBA Cockpit under Configuration Automatic Maintenance Settings. It covers almost all capabilities of the DB2 Control Center and you can use it for the configuration of the time slots available for maintenance actions, starting conditions and parameters for BACKUP, RUNSTATS and REORG. Integration of the DB2 HelpCenter IBM's online documentation has been embedded in an HTML control. Depending on your database release level the appropriate documentation is displayed. 2007 SAP AG 5
Functional Enhancements Table Reorganization In addition to the related snapshot, the action Performance->Inplace Table Reorganization also evaluates the DB2 history file and provides a complete list of all REORGs that have not yet finished REORGs, even if the database was shut down in the mean time. Any of these REORGs can be paused, stopped or resumed accordingly. Table Analysis The action Space->Tables and Indexes provides new selection criteria to filter tables with 'critical' status or tables, that are candidates for a row compression. This analysis is based on the REORGCHK_ALL Job. Therefore you have to schedule this job using the DBA Planning Calendar. Configuration Parameters Both database and database manager configuration display has been re-arranged to appear more generic. This new tree-oriented display is independent from the underlying database release and shows all available parameters that are provided by the database. In addition, you change database managers in the same way you change the database parameters. DBA Planning Calendar A new job is available to run the DB2 tape manager (db2tapemgr) to archive tape archiving. When using DB2 9, the backup job is no longer using the external program dmdb6bkp but uses the ADMIN_CMD stored procedure instead. The backup job does no longer support offline backups. Any offline backup, which has already been scheduled, will automatically be converted into an online backup with the INCLUDE LOGS option. Evaluation of Database Diagnostic Files Both the database diag log and database notify log can be evaluated now by setting filters and time restrictions to limit the output size. If you double-click the appropriate file under Diagnostics->Dump Director y, you can still view the old raw output. 2007 SAP AG 6
Discarded Functions CLP Commands As a consequence of using the new DB2 thin client, you can no longer run most of the CLP commands. Therefore, all pre-configured commands in Configuration->CLP Commands have been discarded and the action has been renamed to SQL Commands (located under Diagnostics). Diagnostics->Control Panel This function has been removed. Diagnostics->Single System Check This function has been removed. There is the new function Alert->Alert Monitor available, that provides information on critical system status in a comparable way. Kernel Dependencies To use the EXPLAIN function, you have to run your SAP system with the latest DBSL kernel patch. Otherwise, EXPLAIN will not work. 2007 SAP AG 7
Related Content You can find more details of platform-independent news and enhancement in Monitoring System Landscapes Using the DBA Cockpit Corresponding up-to-date information is available in SAP Note 1027146 (common) and SAP Note 1027336 Known bugs and problem of SAP NetWeaver 7.0 SP12 are described in SAP Note 1052909 The updated documentation is available in Database Administration Using the DBA Cockpit: IBM DB2 for Linux, UNIX, and Windows 2007 SAP AG 8
Copyright Copyright 2007 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. 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. 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. 2007 SAP AG 9