dba cockpit

DBA Cockpit for Oracle

Ralf Hackmann, Matthias Lienert

Database Platforms Group

SAP AG

© SAP AG 2007, New DBA Cockpit / 2

Contents

Introduction Pages 3 - 8Selected New Performance Monitors Pages 9 - 17Space Monitoring Pages 18 - 20New DBA Planning Calendar Pages 21 - 23Connection of Remote databases Pages 24 - 26Documentation und Notes Pages 27 - 28

Introduction

Space MonitoringNew DBA Planning Calendar

Connection of Remote databasesDocumentation and Notes

Selected New Performance Monitors


DBA Cockpit – General Remarks

As of Basis Release 7.00 SP12, DBACOCKPIT is the new central transaction for database administration.Unified framework and look&feel for all SAP-supported database platformsDBACOCKPIT contains former transactions ST04, DB02, and DB13 (DBA Planning Calendar) and also includes several new monitors, particularly for Oracle 10g.Monitoring of Oracle RAC is included.Monitoring and administration of remote Oracle and non-Oracle databases (both ABAP and non-ABAP systems ) is possible with DB MultiConnect.


DBA Cockpit – Entry screen of Transaction DBACOCKPIT

DBA Cockpit Entry Screen: The DBA Cockpit displays the System Configuration Maintenance screen with a list of all available systems. The local system (= system on which the DBA Cockpit runs) is always displayed. If no other (remote) systems are added, it is the only one.


DBA Cockpit – Navigation Tree and Transaction Codes

All monitoring and planning calendar functions for one system can be accessed using a navigation tree with four main areas:

Performance - corresponds to the old transaction ST04Space - corresponds to the old transaction DB02Jobs - corresponds to the old transactions DB13, DB12, DB14,DB13CDiagnostics

These main areas contain the individual functions of the DBA Cockpit, which you can start by double-clicking.There is a button to hide or reveal the navigation tree:The DBA Cockpit provides the relevant functionality from the old transaction codes ST04, DB02, DB13, DB12, DB14, and DB13C. Old transactions ST04, DB02, DB13 and others are still available but have been renamed to ST04OLD, DB02OLD, DB13OLD, and so on. The underlying functions have status “deprecated”. ST04N no longer exists.


DBA Cockpit – Screen Layout

Navigation tree ON/OFF

Dropdown list of available systems. The current system is displayed.

Note: this screen appears if DBA Cockpit is called with transaction code ST04

Navigation tree from which you can access

all functions with double click

Main area of the results and details of the chosen function -

here Performance Overview

Message area


DBA Cockpit – Prerequisites

Prerequisites for implementing the DBA Cockpit:Certain performance monitors in the DBA Cockpit require special database objects. These objects are created with an SQL script. You can find the script and more information in Note 706927.You need BR*Tools 700 patch level 24 or higher for the Planning Calendar.Some DBA Cockpit functions require the Oracle Active Workload Repository. See Note 1028068 for more information on how to set this up.

The above prerequisites apply to the local system, which is the system where the DBA Cockpit is running. See Note 1028624 for more information and details of corrections.

Introduction





DBA Cockpit (Performance Monitoring) - Active Session History

This sub-monitor in the SAP/Oracle Database Monitor lets you view the Oracle history views, which provide sampled session activity in the database instancesChoose Performance -> Wait Analysis -> Active Session History

Current data or historical data as data source Current data: V$ACTIVE_SESSION_HISTORY:

- Contains snapshots of active database sessions taken once a second - History of session activities (wait events, CPU utilization, executed SQL stmt, ...)- View contains one row for each active session per sample

Historical data: DBA_HIST_ACTIVE_SESS_HISTORY: View contains snapshots of V$ACTIVE_SESSION_HISTORY

Graphics supportSorted by wait classes or wait eventsSeveral drill-down optionsDouble click on graph for more details of session activity


DBA Cockpit (Performance Monitoring) - Active Session History

Click leads to wait events of selected wait class

Click on the graph for more details


DBA Cockpit (Performance Monitoring) – AWR Reports

This sub-monitor in the SAP/Oracle Database Monitor lets you display verydetailed reports from Oracle’s Active Workload Repository (AWR)Choose Performance -> Wait Analysis -> Workload Reporting

In the AWR reporting section you can generate AWR reports, AWR diff reports, SQL reports and ADDM reports:

AWR report: workload report with text or web-page outputAWR DIFF report Workload: compares period report (difference report) with text or web-page outputSQL report: workload SQL report with text or web-page outputASH report: active session history report with text or web-page outputADDM report: automatic database diagnostic monitor (ADDM), only available as text output

Snapshots can be chosen manually. The F4 help provides a mapping of snapshots to timestamps.The second pair of snapshots is only needed for an AWR diff report.For an SQL report you have to also specify the SQL_ID of the SQL statement to be analyzed.


DBA Cockpit (Performance Monitoring) – AWR Reports


DBA Cockpit (Performance Monitoring) - Column Usage Monitor

This sub-monitor in the SAP/Oracle Database Monitor lets you check the contents of the system table SYS.COL_USAGE$:Choose Performance -> SQL Statement Analysis -> Column Usage

Use of predicates on columns (equal, like, and so on) in select statementsIt is updated at intervals by smondbms_stats uses this information.Information can be useful for index design


DBA Cockpit (Performance Monitoring) - Column Usage Monitor

Arbitrary selection criteria


DBA Cockpit (Performance Monitoring) - Metrics

This monitor in the SAP/Oracle Database Monitor gives you metrics on the Oracle database system with data derived from the GV$SYSMETRIC_HISTORY or DBA_HIST_SYSMETRIC_HISTORY view:Choose Performance -> Statistical Information -> System Metrics

Provides statistical information:For current time frames (for example, last minute)Longer time frames (for example, last hour)Histories (for example, all minutes in the last hour)

Used Metrics in DB MonitorV$FILEMETRIC, V$FILEMETRIC_HISTORY

Number of I/O requests and average duration for each datafile in the last minute

V$SYSMETRICSystem statistics

V$SYSMETRIC_SUMMARYAverage and peak values of system metrics within the last hour

V$WAITCLASSMETRICWait class information for last minute interval


DBA Cockpit (Performance Monitoring) - Metrics

Space Monitoring

Introduction

New DBA Planning CalendarConnection of Remote databasesDocumentation and Notes



DBA Cockpit – Space Monitoring (DB02)

You can access space monitoring in the DBA Cockpit as follows:With navigation tree: choose Space -> Space OverwiewWith transaction DB02

Entry screen provides an overview of the space consumption of the database.All figures are based on a batch job which gathers the required data.Size information about tablespaces and tables is given in submonitors with drill-down options.History information about the object sizes is given.


DBA Cockpit – Space Monitoring (DB02)

Introduction





DBACOCKPIT – New DBA Planning Calendar (DB13)

The new DBA Planning Calendar is necessary to meet accessibilityrequirements.Planning entries and results of scheduled actions from the old calendar are preserved in the new one.More flexibility in scheduling recurrent actions.The new DBA Planning Calendar offers views by month, week, or day.Planning entries and results are also available for remote databases.The new DBA Planning Calender can be accessed in two ways:

With navigation tree: choose Jobs -> DBA Planning CalendarWith transaction DB13

The old DBA Planning Calendar is still available with transaction DB13OLD.


DBACOCKPIT – New DBA Planning Calendar (DB13)

Introduction





DBA Cockpit – Connection of Remote databases

Remote databases can be added to or deleted from the system administration and configured there.The DBA Cockpit runs with all SAP-supported databases (Oracle, IBM DB2 UDB, IBM DB2 z/OS, IBM DB2 AS/400, MS SQL Server, MaxDB).ABAP und non-ABAP (Java) SAP systems are supported.If remote Unicode databases need to be connected, the system where the DBA Cockpit runs must be a Unicode database.The appropriate database client software und database shared library must be installedA secondary database connection must be set up in the system configuration of DBA Cockpit for the connected remote database.Optionally or for specific functions, you can also set up an ABAP RFC connection in the system configuration.


DBA Cockpit – Connection of Remote Oracle databases

Minimum release of remote Oracle databases is 9.2.For certain performance monitors in the DBA Cockpit, special database objects are required. These objects are created with an SQL script (Note 706927), which is executed on the remote database. Minimum requirements for the external system: BR*Tools 700 patch level 24 (Oracle client 10) or BR*Tools 640 patch level 52 (Oracle client 9).Additional requirements for the DBA Planning Calendar (DB13) andassociated functions DBA Logs (DB14) und Backup Logs (DB12):Either an RFC ABAP connection (only possible for external ABAP systems) or a connection with SAP Gateway or a remote shell must be configured.For more information, see Note 1025707.Certain functions in DBA Cockpit require Oracle Active Workload Repository (AWR). Therefore, this Oracle option must be available on remote databases (see Note 1028068).

Introduction





DBA Cockpit – Documentation and Notes

The documentation is available as a PDF file on SDN or attached to an SAP note:– https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f079d393-a806-2a10-

84a4-d821d4ee092c– http://service.sap.com/sap/support/notes/1028624

Notes for DBA Cockpit:1028624 Overview of DBA Cockpit for Oracle1025707 DBA Cockpit Planning Calendar and Remote Oracle Databases706927 Oracle DB-Mon: Installation Script for ST04N/DBACockpit1028068 Required Oracle Options for the DBA Cockpit

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f079d393-a806-2a10-84a4-d821d4ee092c

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f079d393-a806-2a10-84a4-d821d4ee092c

http://service.sap.com/sap/support/notes/1028624


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, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, 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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. 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.

The content of this presentation and of documents provided in the course of the presentation shall be provided exclusively for informational purposes and shall be non-binding.

dba cockpit

Documents

remote databases

dba planning

active session

dba cockpit

dba cockpit

column usage

party web

remote databases