monitoring ibm db2 for linux%2c unix%2c and windows in sap system landscapes using sap solution...

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com

© 2013 SAP AG 1

Monitoring IBM DB2 for Linux,

UNIX, and Windows in SAP System

Landscapes Using SAP Solution

Manager 7.1

Applies to:

SAP Solution Manager 7.1 Support Package 5 or higher.

Summary

With SAP Solution Manager 7.1, database administrators have a wide range of functions available at their fingertips to monitor their databases from a central system. This includes the following:

Technical monitoring, including an overview of the database status and automated alerts in critical situations

Root cause analysis, which allows database administrators to visualize database workload behavior and general growth

The DBA Cockpit with expert tools for detailed monitoring, administration, and in-depth problem analysis

The paper outlines the available functions in SAP Solution Manager in more detail with a special focus on the functions available for monitoring IBM DB2 for Linux, UNIX, and Windows databases. The paper also describes the architecture and setup of SAP Solution Manager for database monitoring. In addition, the DBA Cockpit, its role for database monitoring, and its functions are presented. The paper concludes with a troubleshooting section, where the most frequent pitfalls when working with SAP Solution Manager are explained, including suggested solutions for issues.

Author(s): Steffen Siegmund, Sabine Reich, Bernhard Grusie

Company: SAP AG

Created on: 20 June 2013

Author Bio

Steffen Siegmund works as a development architect in the IBM DB2 for Linux, UNIX, and Windows development team at SAP. His area of coverage includes database monitoring based on SAP NetWeaver BW, integration with SAP Solution Manager, and the setup of high-availability cluster solutions with IBM DB2 for Linux, UNIX, and Windows and IBM Tivoli System Automation for Multiplatforms.

Sabine Reich works as a knowledge architect in the IBM DB2 for Linux, UNIX, and Windows development team at SAP. Her responsibilities include writing application help for the DBA Cockpit, editing DB2-related guides for database administrators, and creating software demos.

Bernhard Grusie works as a developer in the IBM DB2 for Linux, UNIX, and Windows development team at SAP. His main working areas are database monitoring for IBM DB2 for Linux, UNIX, and Windows and the integration of database monitoring with SAP Solution Manager, especially with the monitoring and alerting infrastructure for all database platforms at SAP.

Monitoring IBM DB2 for Linux, UNIX, and Windows in SAP System Landscapes Using SAP Solution Manager 7.1


© 2013 SAP AG 2

Contents

Applies to: ........................................................................................................................................................... 1

Summary ............................................................................................................................................................. 1

Author Bio ........................................................................................................................................................... 1

Contents .............................................................................................................................................................. 2

Chapter 1: Introduction ....................................................................................................................................... 4

Chapter 2: SAP Solution Manager 7.1 ............................................................................................................... 5

What is SAP Solution Manager? ..................................................................................................................... 5

Database Analysis and Monitoring Functions in SAP Solution Manager ....................................................... 5 Alerting ......................................................................................................................................................................... 5

System Monitoring ....................................................................................................................................................... 7

Interactive Reporting .................................................................................................................................................... 8

Root Cause Analysis .................................................................................................................................................... 9

High-Level Architecture of SAP Solution Manager ....................................................................................... 12 System Landscape Directory (SLD) ........................................................................................................................... 13

Landscape Management Database (LMDB) .............................................................................................................. 13

SAP Diagnostics Agent .............................................................................................................................................. 13

The DBA Cockpit Backend, the Extractor Framework, and Data Flow ...................................................................... 14

Chapter 3: SAP Solution Manager Setup: Setup of Managed Systems .......................................................... 15

Easy Setup for IBM DB2 for LUW ................................................................................................................. 15

Setup – Step by Step .................................................................................................................................... 15 Step 0: Setting Up Solution Manager ......................................................................................................................... 15

Step 1: Deploying SAP Diagnostics Agent 7.30 SP2 or higher .................................................................................. 15

Step 2: Configuring Data Suppliers for the System Landscape Directory (SLD DS) .................................................. 15

Step 3: Configuring Systems Managed by SAP Solution Manager ............................................................................ 15

Step 4: Setting Up Technical Monitoring, Including Alerting ...................................................................................... 16

Chapter 4: The DBA Cockpit ............................................................................................................................ 18

What is the DBA Cockpit? ............................................................................................................................. 18

SAP Solution Manager and the DBA Cockpit ............................................................................................... 18

Database Monitoring Functions in the DBA Cockpit for IBM DB2 for Linux, UNIX, and Windows ............... 19 Performance Monitoring ............................................................................................................................................. 19

Space Monitoring and Administration ........................................................................................................................ 21

Backup and Recovery Overview ................................................................................................................................ 22

Database Configuration ............................................................................................................................................. 22

Job Scheduling .......................................................................................................................................................... 22

Advanced Diagnostics ............................................................................................................................................... 22

Business Warehouse (BW) Administration ................................................................................................................ 22

Chapter 5: Advanced DBA Cockpit Topics ....................................................................................................... 24

Data Collection Framework ........................................................................................................................... 24 What is the Data Collection Framework? ................................................................................................................... 24

Templates for the Data Collection Framework ........................................................................................................... 24

Data Collection Framework and Extractor Framework in SAP Solution Manager ...................................................... 25

Ownership of Data Collectors .................................................................................................................................... 25

Connecting to Non-SAP-NetWeaver Databases from the DBA Cockpit ...................................................... 26



© 2013 SAP AG 3

Security Aspects ........................................................................................................................................... 26 SAP Solution Manager Authorizations ....................................................................................................................... 27

Authorizations in the Landscape Management Database (LMDB) ............................................................................. 27

DBA Cockpit: Roles and Authorizations ..................................................................................................................... 27

Self-Monitoring .............................................................................................................................................. 27

DBA Cockpit Master Note ............................................................................................................................. 28

Chapter 6: Connecting Database Clusters to SAP Solution Manager for Monitoring ...................................... 29

Agent On-The-Fly Feature for SAP Diagnostic Agents ................................................................................ 29

Setting Up the SAP Diagnostic Agent Using Agent On-The-Fly ................................................................... 30

Shared Disk Cluster ...................................................................................................................................... 31

IBM DB2 HADR ............................................................................................................................................. 31

IBM DB2 Database Partitioning Feature (DPF) ............................................................................................ 32

IBM DB2 pureScale ....................................................................................................................................... 33

Chapter 7: Troubleshooting .............................................................................................................................. 35

Landscape Management Database .............................................................................................................. 35 Issue: The database is not available in SAP Solution Manager applications ............................................................. 35

Issue: No extractors are scheduled for the database ................................................................................................. 37

Extractor Framework ..................................................................................................................................... 38 Issue: No data is displayed in BW-based reports ....................................................................................................... 38

Data Collection Framework ........................................................................................................................... 38 Issue: No data is displayed on database-related screens .......................................................................................... 38

Chapter 8: Summary ......................................................................................................................................... 39



© 2013 SAP AG 4

Chapter 1: Introduction

This paper will take you on a sightseeing tour along SAP's special administration and monitoring tools for database administrators. There are a number of database administration and monitoring tools around, but SAP Solution Manager and the DBA Cockpit bridge a gap between the SAP and the database world – many functions are designed in such a way that they specifically support database administration in an SAP environment.

SAP Solution Manager is SAP’s recommended tool to monitor and administrate your system landscape. Database administrators who monitor IBM DB2 for Linux, UNIX, and Windows can particularly profit from the functions in SAP Solution Manager, as it offers a wide range of possibilities to watch the workload of the database and get alerted in critical situations. This paper will outline the advantages of using SAP Solution Manager 7.1 and sketch some of its most important functions for database administration and monitoring.

A further section of the paper will focus on how to set up SAP Solution Manager for database administration and monitoring. The good news is that the setup for database administration is quite straightforward. The paper gives a condensed overview of what needs to be done – step by step.

The second part of the paper is dedicated to the DBA Cockpit, another SAP tool for database administrators. Why another tool? As opposed to SAP Solution Manager, which offers many functions for high-level monitoring and alerting, the DBA Cockpit is a great tool for experts who want to analyze database issues in detail. With its functions for performance monitoring, space management, and diagnostics, this is the right place to drill down to detail views of performance changes or of space consumption and to solve database issues. In addition, functions like the DBA planning calendar make scheduling regular database jobs such as backups or archiving easy.

The paper also covers some tips and tricks for those database administrators that already use the DBA Cockpit heavily and want to get the best out of the tool. The section on advanced DBA Cockpit topics is full of answers to topics that are often asked for by customers and partners – including details about the data collection framework, templates, and security aspects.

We conclude with a troubleshooting section, containing the most frequent issues that users of the DBA Cockpit might come across, and suggestions how to solve these issues.

This paper is written for database administrators who want to learn more about SAP's special administration and monitoring tools. We hope that you can profit from the instructions and tips, and that you will see the many advantages of using SAP Solution Manager and the DBA Cockpit to monitor your database.



© 2013 SAP AG 5

Chapter 2: SAP Solution Manager 7.1

In our sightseeing tour of SAP's tools for database administrators, we will start with SAP Solution Manager, which offers its users many monitoring and alerting functions for databases in an SAP system landscape.

What is SAP Solution Manager?

SAP Solution Manager is the free SAP toolset in your system landscape to monitor the full stack of SAP systems: from operating systems up to business processes. SAP Solution Manager is typically installed on a separate system, where it provides central access to tools, methods and preconfigured contents that you can use during evaluation, implementation, and operations of your systems.

Figure 1 - SAP Solution Manager, a Central Landscape Monitoring Solution

For database administrators, SAP Solution Manager offers a range of tools for root cause analysis, alerting, and reporting, such as the following:

Technical Monitoring

o Alerting: Automated checks help you to discover problems in a system landscape or anapplication stack.

o System monitoring: You can monitor the current status of the database.

o Reporting: You can generate and download reports for single and multiple databases and distribute them via mail.

Root Cause Analysis

o Database analysis: You can watch the workload and state of databases for SAP-NetWeaver-BW-based systems.

o Database configuration: You can display and validate the history of database configurations.

In addition to these tools that provide high-level overviews of possible issues, it is also possible to investigate issues in more detail using the DBA Cockpit, which is tightly integrated with SAP Solution Manager. For more information, see the DBA Cockpit section.

Database Analysis and Monitoring Functions in SAP Solution Manager

We will now have a closer look at the functions for database analysis and monitoring in SAP Solution Manager.

Alerting

When you use SAP Solution Manager for database and system monitoring, the monitoring and alerting infrastructure (MAI) supports you by generating alerts when critical incidents arise. The alert inbox and the system monitoring help you to handle alerts and give you information about the status of your landscape.



© 2013 SAP AG 6

The alert inbox gives you an overview of the alerts from your connected systems. You can see the current worst status and also the number of occurrences. Incident management (for support messages) and notification management (for example, via e-mail) are also included in the alert inbox. To display more information about an alert, click on Show Details. In the details, you can find a short description and a link to the DBA Cockpit, where you can perform a more thorough error analysis or take further actions.

Figure 2 - Alert Inbox

To access the alert inbox directly, call up the work centers of the SAP Solution Manager using the

SM_WORKCENTER transaction, choose the Technical Monitoring tab page and then Alert Inbox in the left

frame. Database alerts are displayed on the Database Alerts tab page.

Figure 3 - Alert Monitor in Technical Monitoring: Alert Details



© 2013 SAP AG 7

System Monitoring

On the System Monitoring screen, you get an overview of the status of your systems. To access the system

monitoring directly, call up the work centers of the SAP Solution Manager using the SM_WORKCENTER

transaction, choose the Technical Monitoring tab page and then System Monitoring in the left frame.

In the overview, you can see database details, information about whether a work mode is configured, and a summary of the metrics for the categories availability, performance, and exceptions. You can also see the configuration status and the number of alerts, from where you can directly navigate to the alert inbox. If you click on the database or on one of the three alert categories, you get to the detail analysis of this database.

Figure 4 - System Monitoring Overview

For the database, the following alert categories are available:

Database availability o Availability check of the database instance and database connect o Tablespace availability

Database exceptions o Lock-wait events o Missing backups

o Critical error messages from the diag.log file

o Disk space usage o Log information o Backup status o WLM threshold violations

Database performance o Buffer quality o Package cache quality o Catalog cache quality

In the left frame, you can see the topology of the system. In the example below, you see three Java application servers and one database (middle tier). These systems run on three different hosts. In the right frame, you can see the grouped alerts, events and metrics in the tree. Next to every metric name, you can see its current status and, depending on the metric, you can also see the current value.



© 2013 SAP AG 8

Figure 5 - System Monitoring Topology

With the small arrow at the end of a metric, you can navigate to the metric documentation. In this documentation, you can find a short description, a possible solution that eliminates the alert and a link to the DBA Cockpit. In this example, you can use the backup and recovery overview to get an overview of existing backup and log files, or you can use the DBA planning calendar to schedule a new backup.

Figure 6 - Metric Documentation Including DBA Cockpit Navigation

For more information about setting up and using alerting, see Setting Up and Using Alerting in SAP Solution Manager and DBA Cockpit.

Interactive Reporting

You can use interactive reporting to centrally display the development of the most important monitoring data over time, to identify potential problems early, and to obtain an overview of the load, usage, availability, and performance of your databases, among other things. The reports contain various periods, from the current day to the previous year, so you can see both the current and the long-term development of the performance values.

To access interactive reporting, call up the work centers of the SAP Solution Manager using the

SM_WORKCENTER transaction, choose the Technical Monitoring tab page and then Interactive Reporting in

the left frame.

The available reports for databases are divided into the following four topic areas:

Availability of the selected database



© 2013 SAP AG 9

Performance of the read and write accesses to the selected database

Usage of the available capacity of the selected database

Usage of the selected database, such as the number of accesses and the changed data records

Figure 7 - Interactive Reporting

Root Cause Analysis

The root cause analysis provides in-depth information about different components, including monitoring of databases, systems, and hosts. As a database administrator, you will find the Database Analysis screen and Configuration Change Database screen particularly useful.

Database Analysis

The Database Analysis screen allows you to:

Visualize database general metrics in easily understandable reports

Watch database workload behavior and general growth

The reports for database analysis in SAP Solution Manager are a subset of the reports in the Database Performance Warehouse. The Database Performance Warehouse is an SAP NetWeaver BW-based component that is reused in the DBA Cockpit to display performance metrics (see also What is the DBA Cockpit?). Note that whereas the reports in SAP Solution Manager focus on general, easy-to-understand issues, the reports in the DBA Cockpit are more DB2-architecture-related and are targeted at the DB2 database specialist.

To access the database analysis, call up the work center of the SAP Solution Manager using the

SM_WORKCENTER transaction, choose the Root Cause Analysis tab page, and then Database Analysis in the

left frame.



© 2013 SAP AG 10

Figure 8 - Database Analysis: Charts for Database Workload and Database Logs

Configuration Change Database

The Configuration Change Database (CCDB) saves information about configuration changes of the database. As a database administrator, you can use the Configuration Change Database screen to get an easy overview of these changes. The information from the CCDB is also reused by the monitoring and alerting infrastructure (MAI), which can generate an alert if a database parameter is not as the user expects it to be. With the configuration validation, you can define a template with valid values for database configuration parameters. The validation report uses the templates to compare the template settings with settings in systems in the system landscape. If the system settings deviate from the valid template settings, an alert is raised.

For every technical system, a store for configuration changes is created automatically if you connect it to SAP Solution Manager. In this store, the configuration changes are saved. The CCDB only works for a technical system, data extraction for a standalone DB2 for Linux, UNIX, and Windows database does not work. In the MAI, there is a template Self- Monitoring Solution Manager ABAP that is used to monitor the CCDB infrastructure itself. For DB2 for Linux, UNIX, and Windows, the CCDB records configuration changes of the following:

Database manager

Database

Registry

DB2level information

The configuration changes for a technical system can be displayed using the transaction SAP Solution

Manager Workcenter (SM_WORKCENTER) -> Root Cause Analysis -> End-to-End Analysis. Select a system

and then choose the Change Analysis button.



© 2013 SAP AG 11

Figure 9 - Configuration Changes

With a click on a change, you can see the old and new value.

Another way to view changes is transaction SAP Solution Manager Workcenter (SM_WORKCENTER) -> Root

Cause Analysis -> System Analysis. Select a system and then choose the Change Reporting button. In this view, you can also compare different systems.

Figure 10 - Database Level Changed

With the help of transaction SAP Solution Manager Workcenter (SM_WORKCENTER) -> Root Cause Analysis -

> Configuration Validation, it is possible to configure a template for a system. In this template, you configure valid values for the database parameters. If such a value does not match the template, the validation report highlights the value.



© 2013 SAP AG 12

To access the administration of the CCDB, use the transaction SAP Solution Manager Workcenter

(SM_WORKCENTER) -> SAP Solution Manager Administration -> Infrastructure -> Button Administration ->

Configuration Change Database.

Figure 11 - Configuration Extraction

High-Level Architecture of SAP Solution Manager

When you work with SAP Solution Manager, it is often useful to know about the high-level architecture of SAP Solution Manager and the tools in its environment that collect database information. Background knowledge about the high-level architecture of SAP Solution Manager and data collection makes it easier to understand what kinds of tools and mechanisms need to be set up to get database monitoring in SAP Solution Manager up and running. In addition, background knowledge about the architecture of SAP Solution Manager is often helpful when you need to identify and solve issues with the data collection for SAP Solution Manager tools.

The architecture of SAP Solution Manager comprises a number of tools and frameworks that collect detail data about databases and their statuses automatically. This means that, with SAP Solution Manager up and running, database administrators have central access to information that they would otherwise have to collect manually, for example, by writing their own scripts. The tools and frameworks for automatic discovery of databases and database details include the landscape management database (LMDB), the system landscape directory (SLD), the SAP diagnostics agent, and the extractor framework, which will be explained in more detail below.



© 2013 SAP AG 13

Figure 12 - SAP Solution Manager: High-Level Architecture

System Landscape Directory (SLD)

The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository for your system landscape. A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces. Information in the SLD is used by various SAP tools, for example, for planning and performing upgrades to the system landscape (Software Lifecycle Manager of SAP NetWeaver), finding destination information for ABAP systems and Web services (Web Dynpro), and for maintaining development information by the SAP NetWeaver Development Infrastructure (NWDI).

Landscape Management Database (LMDB)

In SAP Solution Manager, all elements of a system landscape are modeled in the Landscape Management Database (LMDB). The core task of the LMDB is to provide information about the entire system landscape at a central location. The LMDB copies available data from the SLD, but it enriches the data copied from SLD with additional information. For example, the SLD can provide the information which databases are available. For each database, the LMDB adds details such as the cluster topology of the database, including information about the use of pureScale or the database partitioning feature for IBM DB2 for Linux, UNIX, and Windows. SAP Solution Manager applications are based on LMDB.

SAP Diagnostics Agent

The functions for root cause analysis in SAP Solution Manager require that a special tool for data collection is installed on every local system of your system landscape. This tool is the Solution Manager Diagnostics Agent (Diagnostics Agent), which is the remote component of the end-to-end root cause analysis. It allows building up a connection between SAP Solution Manager as the managing system and the managed systems. It gathers information from the managed systems and reports them to the SAP Solution Manager system. This Diagnostics Agent is used to detect the databases in a system landscape automatically. The Diagnostics Agent also monitors the availability status and other critical metrics of the databases. You need to install a Diagnostics Agent on each server (virtual hostname) that you want to monitor. You can use the SAP installation tool to install the Diagnostics Agent.



© 2013 SAP AG 14

The Diagnostics Agent uses SAP Host Agent to discover all databases installed on a host. The Diagnostics Agent and the SAP Host Agent transfer some basic information, such as the database host, the database type and its name, to the LMDB. In addition, the Diagnostics Agent reports technical attributes like cluster topology, database release, and properties required for a remote database connection to the LMDB. This kind of information is mapped in the LMDB with the data provided by the SLD. Information about databases that do not run with an SAP system are also pushed to the LMDB by the Diagnostics Agent. Since the Diagnostics Agent permanently monitors the database for changes, database changes like movements in clusters, the use of an SAP Landscape Virtualization Manager, or a new database level are detected within a short time period and updated in the LMDB.

The advantage of using the Diagnostics Agent is that many database attributes are detected and reported to LMDB automatically (“outside discovery”). And, most importantly, the high-frequency checks of the Diagnostics Agent ensure that host or database failures are reported quickly back to SAP Solution Manager.

The DBA Cockpit Backend, the Extractor Framework, and Data Flow

The DBA Cockpit backend provides an infrastructure to perform data collection for managed databases. For IBM DB2 for LUW the Data Collection Framework (DCF) is used here. Via remote database connection a set of stored procedures and tables is created in the monitored database. Finally, the stored procedures are scheduled to collect data periodically. Those stored procedures take snapshots of database statuses, and thus generate historical data (time series), which allows database administrators to keep track of short- and mid-term developments in the database. The data collected by the DBA Cockpit backend is fed into the extractor framework, the central infrastructure for SAP Solution Manager for data extraction and distribution. Collected data is used, for example, for interactive reporting, for end-to-end monitoring, and for the alerting infrastructure in SAP Solution Manager.

The extracted data is reused by the following engines and stores:

Event Calculating Engine (ECE)

Metric-Event-Alert (MEA) Store

SAP NetWeaver BW for reporting

These engines and stores then feed the different SAP Solution Manager applications with data, such as reporting, alerting, exception handling, and so on.

The only exception in this setup is the monitoring of instance and of database availability and the related alert generation: To be able to check instance and database availability fast, the SAP Diagnostics Agent is used to query the SAP Host Agent about the database and instance status. If an outage is detected, the SAP Diagnostics Agent sends this information via a push mechanism to SAP Solution Manager, where an alert is generated.



© 2013 SAP AG 15

Chapter 3: SAP Solution Manager Setup: Setup of Managed Systems

Before you start using SAP Solution Manager for monitoring the databases in your system landscape, a few setup steps are required.

Easy Setup for IBM DB2 for LUW

If you already plan to set up SAP Solution Manager for system landscape monitoring, the monitoring of IBM DB2 for LUW databases only requires a few additional entries in the SAP Solution Manager setup wizard. With the automatic discovery of databases as part of the setup, the landscape management database is already filled with the most important database attributes, such as database platform, database name, database level, and hosts. In addition, connect information is also automatically detected, such as ports, services, and the logical host name in a virtualized or clustered systems environment.

During setup, you only need to provide the following information for IBM DB2 for LUW databases:

Enter a password of a monitoring/administration database user.

Optional: Select a template for the data collection framework.

Optional: Enable/disable the auto update feature for the data collection framework (default: enabled).

Optional: Choose the ownership mode for the data collection framework (see also the section Data Collection Framework).

Setup – Step by Step

Step 0: Setting Up Solution Manager

After the installation or after a support package update of SAP Solution Manager, you need to set up SAP

Solution Manager using the SOLMAN_SETUP transaction. The SOLMAN_SETUP transaction serves to perform

the basic configuration of the SAP Solution Manager itself.

Step 1: Deploying SAP Diagnostics Agent 7.30 SP2 or higher

You need to deploy SAP Diagnostics Agent 7.30 SP2 or higher in the SAP systems of your system landscape. The SAP Diagnostics Agent is used to provide database attributes and statuses to SAP Solution Manager.

Since SAP NetWeaver 7.0 Support Release 3 (SR3), the Diagnostics Agent is deployed at the end of every installation requiring the SAP Installation Master Support Release 3 DVD: SAP NetWeaver 7.0 SR3, SAP Business Suite SR3 (SAP ERP, SAP CRM, SAP SCM, SAP SRM) based on AS Java. If the SAP Diagnostics Agent is not installed in your system, you can use the SAP installation tool to install it. During installation, it is important that you enter a connection to the SLD. This connection is used by the Diagnostics Agent to register itself in the SLD. It is highly recommended that you define a connection to SAP Solution Manager during this step.

Note: For more information about required Diagnostic Agent versions, see SAP Note 1365123.

Step 2: Configuring Data Suppliers for the System Landscape Directory (SLD DS)

Use the transaction System Landscape Directory: Local Administration (RZ70) to configure SLD data suppliers in the system landscape. Here, you need to provide the port and the host of the SLD. The SLD data suppliers are programs that collect the database attributes Database Host, Database Type and Database Name at defined periods. Once the SLD data suppliers are up and running, they push database attributes from the database to the SLD (see also High-Level Architecture of SAP Solution Manager).

Step 3: Configuring Systems Managed by SAP Solution Manager

Use the transaction SAP Solution Manager Configuration (SOLMAN_SETUP) -> Managed System Configuration to perform the following activities:

Connect the SAP Diagnostics Agent to the managed databases



© 2013 SAP AG 16

Specify system parameters required to configure the managed databases Most of these parameters, such as hosts or ports, are automatically detected by the Diagnostic Agent, so only a password is required here.

Trigger automatic configuration activities This includes the setup of the database data collectors and extractors.

Figure 13 - Managed System Setup

Step 4: Setting Up Technical Monitoring, Including Alerting

Use the transaction SAP Solution Manager Configuration (SOLMAN_SETUP) -> Technical Monitoring to set up

the technical monitoring of databases in SAP Solution Manager.

a) Maintain templates For databases, SAP provides monitoring templates that contain the definitions or values of metrics, events, and alerts (MEA) that trigger incidents and notifications. The SAP templates have predefined settings, but you can also adapt the templates to your customer-specific needs. With different templates, you can cover several usage scenarios of your databases, for example, productive and test systems. In this step, you can set up also the following:

Activation or deactivation of auto-notifications (for example, e-mail notifications) about database alerts. As a default, auto-notification is activated.

Recipients and recipient lists of auto-notifications

Assignment of monitoring templates to selected systems in scope for monitoring



© 2013 SAP AG 17

b) Define scope In this step, you select a technical system or database.

c) Set up monitoring

In this step, you assign a template to the selected system. You can also select which template you want to assign, including the user-defined templates from step Maintain templates.



© 2013 SAP AG 18

Chapter 4: The DBA Cockpit

After a close look at SAP Solution Manager, we now turn to another database administration and monitoring tool, the DBA Cockpit. Whereas SAP Solution Manager offers a view of the database from an eagle's eye, the DBA Cockpit provides the beaver's perspective: you can have a look at information about performance or space consumption and drill down to data for individual days or to details about individual tables, schemas, tablespaces, and so on.

What is the DBA Cockpit?

The DBA Cockpit is a platform-independent tool that you can use to monitor and administer your database. The advantage of using the DBA Cockpit is that it has been specifically designed for the administration and monitoring of databases in an SAP system landscape. Therefore, the functions of the DBA Cockpit especially support database administrators in adapting their databases for the workload of SAP systems. The DBA Cockpit eases the work of database administrators because all important performance tuning, monitoring, and administration tasks are available in a single transaction.

In addition, the DBA Cockpit can be used to monitor databases that do not run for an SAP system.

SAP Solution Manager and the DBA Cockpit

The tools of the DBA Cockpit complement the available SAP Solution Manager tools, which provide high-level overviews of possible database issues, including reporting and alerting functions. In addition to the high-level overviews of SAP Solution Manager, the DBA Cockpit serves as an in-depth analysis tool for database-related issues. Some of its functions include a time spent analysis for SQL statements, an analysis of lock-wait events, and analysis tools for database objects such as tables, indexes, or tablespaces.

Figure 14 - Granularity of Applications in SAP Solution Manager and the DBA Cockpit

The DBA Cockpit is part of every SAP NetWeaver ABAP system. So the DBA Cockpit is also available on your SAP Solution Manager system, where you can access all databases in your system landscape using remote connections. Alternatively, you can run the DBA Cockpit locally on an SAP NetWeaver ABAP system

by calling up the DBACOCKPIT transaction. If you use the DBA Cockpit as part of the SAP Solution Manager

system, this allows you to update and administrate all databases from a central system rather than logging on to each individual system separately.

The DBA Cockpit not only provides more tools for the expert database administrator, but the DBA Cockpit also plays an important part in the SAP Solution Manager infrastructure. The remote database monitoring infrastructure of the DBA Cockpit is used by SAP Solution Manager to collect or extract metrics from remote databases. These metrics are then passed on to the different applications in SAP Solution Manager.



© 2013 SAP AG 19

Figure 15 - DBA Cockpit as Metrics Provider for SAP Solution Manager

Some features for database monitoring and administration are only available if you run the DBA Cockpit combined with SAP Solution Manager. The DBA Cockpit itself does not provide an alerting and notification framework. Nor does the DBA cockpit provide a discovery mechanism for automatically detecting databases in a system landscape. This is available in SAP Solution Manager. Moreover, the DBA Cockpit uses SAP NetWeaver BW on SAP Solution Manager for compiling data about long-term performance and workload history. Those features are only available in the DBA Cockpit running on SAP Solution Manager.

Database Monitoring Functions in the DBA Cockpit for IBM DB2 for Linux, UNIX, and Windows

If you administer and monitor IBM DB2 for Linux, UNIX, and Windows databases with the DBA Cockpit, the following functions are available:

Performance Monitoring

For example, you can display performance and workload statistics, analyze top SQL statements, perform time spent analyses, or display historical snapshots of database objects.

Time Spent Analysis

The time spent analysis provides a graphical view of the time consumed by requests, including processing and wait times. You can use this screen as the starting point for performance tuning and to identify time-based problems of your database. The Time Spent Analysis screen provides an aggregated and timeline-based view of the current or past performance situation of your database. 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 in various 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, and are there any outliers?

The drill-down and filtering functions allow you to display information according to time-based metrics, service classes, and database hosts or members. The graphics can be set up either as pie chart or as timeline histogram.



© 2013 SAP AG 20

Figure 16 - Time Spent Analysis: Graphical Views

SQL Statement Analysis

The screens for SQL statement analysis help you identify those SQL statements that consume many resources. You can also determine whether fine-tuning of these statements is necessary to improve the performance of the database.

There are various flavors of SQL statement analyses available in the DBA Cockpit:

SQL Cache screen: Displays information about the sections in the package cache

Top SQL statement analysis: Displays information about SQL statements that are executed very often or that are expensive with regard to specific metrics. In contrast to the SQL Cache screen, this screen shows the consumption of all sections of the package cache for the same SQL statement. If you want to analyze expensive SQL statements, use this screen instead of the SQL Cache screen.



© 2013 SAP AG 21

Figure 17 – Top SQL Statement Analysis

Graphical View of the EXPLAIN Access Plan

The graphical view of the EXPLAIN access plan is a tree view with detailed data on each node. The optimal path in the access plan is highlighted in bold. The EXPLAIN function is tightly integrated with other functions of the DBA Cockpit, that is, you can easily navigate to the EXPLAIN function from various areas of the DBA Cockpit. For example, in the database-specific area of the DBA Cockpit, choose Performance Snapshots SQL Cache. Select a statement from the list and choose the EXPLAIN button.

Figure 18 - EXPLAIN Access Plan: Graphical View

Space Monitoring and Administration

The DBA Cockpit allows you to watch the space consumption of your database, including database objects such as tables, indexes, tablespaces, or containers. You can analyze space allocation and perform administration activities to change the storage layout of your database.



© 2013 SAP AG 22

Backup and Recovery Overview

You get an overview of all performed database backups and recoveries. In addition, you can display information about archived log files and about logging parameters.

Database Configuration

In this area, you get an overview of your database configuration. You can also change the database configuration; including configuration settings for buffer pools, database partitions, or the database optimizer.

One special feature for SAP customers in this area is a check tool for databases running with an SAP system, the parameter checker. The parameter checker reads the SAP Notes containing the parameter recommendations from SAP and validates these recommendations against the current database configuration. All deviations from SAP recommendations are highlighted.

Job Scheduling

Direct access to the DBA Planning Calendar, the DBA log, scheduled DB2 tasks, and other tools allows you to plan and keep track of all important jobs for the databases.

Advanced Diagnostics

Various diagnostic functions allow you to identify critical situations in your database, such as lock-wait events or missing tables and indexes. The diagnostics tools also include, for example, the audit log, the dump directory, and the trace status.

Advanced Diagnostics: Lock-Wait Event Monitor

You 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 lock event monitor

Review lock wait events that are currently occurring on the database server In the lock-wait event monitor, you can specify the time frame for which you want lock-wait events to be displayed as well as the type of lock-wait event, such as, lock waits, lock time outs, and lock waits with a specific lock time out. You can also display the lock chain – or, in the case of a deadlock, a log circle - of an event in a graphical view of the lock-wait event. In addition, you can also display more details about the related SQL statement, such as the ABAP source code from where the SQL statement was executed or the access plan.

Figure 19 - Lock-Wait Events: Graphical Views

Business Warehouse (BW) Administration

If you have an SAP NetWeaver BW system in your system landscape, you can use the DBA Cockpit to call up the MDC advisor, a DB2 tool that helps to improve the settings for multi-dimensional clustering in



© 2013 SAP AG 23

partitioned databases. In addition, you can use the DBA Cockpit to perform BW health checks, for example, or perform administration activities relating to near-line storage.



© 2013 SAP AG 24

Chapter 5: Advanced DBA Cockpit Topics

The following chapter is for real DBA Cockpit enthusiasts and includes more details about the infrastructure of the DBA Cockpit and special usage scenarios. Note that SAP provides a default configuration for the DBA Cockpit and SAP Solution Manager, which is fine for most usage scenarios. If you only get started with the DBA Cockpit or if you are happy with the default configuration of the DBA Cockpit, you can ignore this chapter or come back to it later.

Data Collection Framework

What is the Data Collection Framework?

The data collection framework is a part of DBA Cockpit that automatically performs a time-based collection of data about the performance, configuration, and space consumption of a database monitored by the DBA Cockpit. During the setup of the data collection framework (DCF), a separate schema is created in the monitored database that contains all relevant monitoring objects, such as:

Tablespaces

The tablespaces SAPTOOLS and SAPEVENTMON are created to hold the data history. The SAPEVENTMON tablespace is used for DB2 event monitor target tables.

Data Collectors (SQL Stored Procedures)

A set of SQL stored procedures (STP) is created in the managed database to collect data on a regular basis. These STPs are either based on DB2 for LUW monitoring functions or event monitors. These stored procedures are scheduled by the DB2 administrative task scheduler (ATS).

History Tables

The STPs or DB2 event monitors store the database workload and performance history in the history tables.

For more information about available templates for the DCF and about the DCF setup, see the section Templates for the Data Collection Framework.

Templates for the Data Collection Framework

The data collection framework (DCF) is part of the DBA Cockpit backend and is the infrastructure for collecting time-based database metrics. All settings for the data collection, for example, recurrence patterns for the scheduled data collectors and the amount of data to be collected are determined by templates. SAP provides the following standard templates for the DCF:

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

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

If you need settings different from the standard setup, you can create your own template based on a standard template and adapt your template to your needs. To do this, you call the DBA Cockpit and choose Configuration Data Collection Framework Template Definition on the Database tab page of the DBA Cockpit.

Regardless of whether the database has been configured for monitoring using SAP Solution Manager or using the DBA Cockpit, the first time you select a database system for monitoring in 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.



© 2013 SAP AG 25

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

If the DCF cannot be set up automatically because of missing tablespaces or insufficient privileges of the monitoring user, the DBA Cockpit initially displays the appropriate configuration screen where you can perform the required setup steps.

Once the DCF is set up, it can also be reused as a data source about the status and performance of databases by SAP Solution Manager (see The DBA Cockpit Backend, the Extractor Framework, and Data Flow). During SAP Solution Manager setup, the available templates for the DCF are displayed and can be selected for database monitoring.

Data Collection Framework and Extractor Framework in SAP Solution Manager

The data collected by the DBA Cockpit backend is fed into the extractor framework, the central infrastructure for SAP Solution Manager for data collection and distribution. For more information, see High-Level Architecture of SAP Solution Manager.

Ownership of Data Collectors

The DBA Cockpit provides an ownership concept that allows you to maintain data collectors for the IBM DB2 for LUW databases in your system landscape centrally from an SAP Solution Manager system or a system where the DBA Cockpit is running. With this ownership concept, you can have one system that owns the data collectors of the DB2 databases. This means that this is the only system from which a database administrator can set up, update, patch, remove, or drop data collectors. This system is referred to as the owner system.

The idea of this ownership concept is that you can roll out data collectors in a system landscape using one dedicated SAP Solution Manager system. This way, you can distribute patches, updates, or configurations in the system landscape using the template mechanism in the DBA Cockpit. When you work with a single owner system, other systems running the DBA Cockpit can also access the data collectors, but only in read-only mode, so they cannot overwrite changes made to data collectors by the SAP Solution Manager system. The advantage of having a primary owner of data collectors is that you can centrally provide the most up-to-date data collectors for DB2 databases that SAP Solution Manager needs for monitoring. This saves you from applying SAP Notes individually for each managed system.

Single Ownership

The following graphic shows an example of a system landscape with two DBA Cockpits, with DBA Cockpit XYZ as the single owner of the data collectors and DBA Cockpit ABC with read-only authorizations:

Figure 20 - System Landscape with Single Ownership



© 2013 SAP AG 26

Dual Ownership

It might be the case that the owner system of the data collectors is on a lower release or support package level than another SAP Solution Manager system. Then, the more up-to-date SAP Solution Manager system is able to provide and patch data collectors that the current owner system cannot cover because its release or support package level is too low. This is the case, for example, when you want to test a new SAP Solution Manager version on another installation in parallel to your productive SAP Solution Manager system. In this case, you can switch to a dual ownership: In addition to the primary owner, you define the more up-to-date SAP Solution Manager system as a supplementary owner. In the supplementary owner system, the database administrator can set up, update, patch, remove, or drop only those data collectors that the primary owner cannot cover.

Note: You can allow a dual ownership only if the two owner systems are based at least on the following releases and support package levels:

SAP NetWeaver 7.02 with Support Package 10 or higher




The following graphic shows an example of a system landscape with two DBA Cockpits, with DBA Cockpit XYZ as the primary owner of the data collectors and DBA Cockpit ABC as the supplementary owner:

Figure 21 - System Landscape with Dual Ownership

Connecting to Non-SAP-NetWeaver Databases from the DBA Cockpit

The DBA Cockpit also supports the monitoring of databases for non-SAP-NetWeaver-based systems. This is possible because the DBA Cockpit does not use RFC connections to SAP systems, but it directly connects to databases using a native database connection. For more information, see SAP Note 1649092.

Security Aspects

When you work with SAP Solution Manager and the DBA Cockpit, you also need to keep an eye on security, especially on restricting authorizations and privileges to the right group of persons.



© 2013 SAP AG 27

SAP Solution Manager Authorizations

For a detailed overview of the authorization concepts of SAP Solution Manager, see the Security Guide on SAP Service Marketplace at http://service.sap.com/instguides SAP Components SAP Solution Manager <current release> Operations.

Authorizations in the Landscape Management Database (LMDB)

You can restrict the authorizations in SAP Solution Manager per system in the LMDB. This is similar to the S_DBCON authorization object for the DBA Cockpit, which will be introduced later. SAP Solution Manager uses the authorization object AI_LMDB_OB. This authorization object restricts the usage per system in the LMDB. The extended SID is used here to allow access to those systems.

DBA Cockpit: Roles and Authorizations

As of SAP Solution Manager 7.1 SP3 and SAP NetWeaver 7.0, the following security mechanisms are available:

The SAPAPP, SAPTOOLS and SAPMON database roles to restrict user privileges on the database

according to organizational tasks

The separation of duties to ensure that database administrators cannot read business data using a remote database connection

The new S_DBCON authorization object to restrict access to remote databases from the SAP Solution

Manager system

If you work with SAP Solution Manager, a default authorization setup for database administrators is available. In the SAP default setup, database administrators who connect to databases for monitoring and

administration get the SAPTOOLS authorizations. In addition, you can use the S_DBCON authorization object

to assign the right monitoring or administration authorities for remote monitoring to different users on SAP Solution Manager 7.1.

This setup type is provided out-of-the-box. There is no need to change anything on the remote databases, and the setup of the managed systems is very simple.

For more information, see the paper Role-Based Security Concept for Database Users on IBM DB2 for Linux, UNIX, and Windows on SAP Community Network (SCN) at http://www.sdn.sap.com/irj/sdn/db6.

Self-Monitoring

As of SAP Solution Manager 7.1 SP8, a self-monitoring infrastructure for the DBA Cockpit has been introduced. The self-monitoring infrastructure supports you with identifying issues that prevent the DBA Cockpit from running error-free. The self-monitoring framework checks all managed databases once in 24 hours for infrastructure issues. For example, the database connection is checked, or issues are identified

that relate to a missing db6_update_db script or to data collectors.

To check for such issues in the landscape, proceed as follows:

1. Logon to SAP Solution Manager.

2. Call up the DBACOCKPIT transaction.

3. Choose Landscape Self-Monitoring. You get a system overview of the check status, check time, auto update configuration, and the assigned DCF template.

http://service.sap.com/instguides

http://www.sdn.sap.com/irj/sdn/db6



© 2013 SAP AG 28

4. Choose a system and analyze the errors and warnings. Each check with an error or warning has a detailed description of the problem and the impact. Some checks refer to relevant SAP Notes; others provide direct navigation to a repair tool.

DBA Cockpit Master Note

The DBA Cockpit for IBM DB2 for LUW has an SAP Master Note 1456402, which applies all known patches. This master note should be kept at an up-to-date level on all SAP Solution Manager systems.



© 2013 SAP AG 29

Chapter 6: Connecting Database Clusters to SAP Solution Manager for Monitoring

If you want to monitor database clusters using SAP Solution Manager and the DBA Cockpit, this is also possible. However, there are some additional aspects that you have to consider:

Where and how do I have to install the SAP Diagnostic Agents?

Which hostname should be used for the DBA Cockpit?

To install SAP Diagnostic Agents easily, you can profit from the agent on-the-fly feature in SAP Solution Manager. You proceed as follows:

Install one SAP Diagnostic Agent per operating system.

Activate agent on-the-fly in SAP Solution Manager.

Simply connect the database as if it was non-clustered.

In the following sections, we will outline how you activate the agent on-the-fly feature in SAP Solution Manager in more detail. In addition, special aspects that need to be considered for the different types of database clusters (HADR, DPFS, pureScale) are discussed.

Agent On-The-Fly Feature for SAP Diagnostic Agents

In the chapter SAP Diagnostics Agent, you have already learned that the SAP Diagnostic Agent is used for outside database discovery, database availability monitoring, and operating system monitoring. To monitor all nodes of a database cluster, you have to install one SAP Diagnostics Agent per operating system.

Most cluster solutions use a virtual IP (VIP). In the past, you had to install additional SAP Diagnostics agents for each virtual IP. Additionally, you had to add those agents to the cluster manager so the SAP Diagnostics agent is always moved together with the monitored database instance. The agent on-the-fly feature provides an alternative solution that saves you manual efforts. You do not need to install additional agents anymore and there is no need to add them to the cluster manager. The agent on-the-fly feature provides a built-in infrastructure that sets up appropriate SAP Diagnostics Agent landscapes for high-availability environments.

The following graphic visualizes the installation topology of a high availability disaster recovery cluster for

IBM DB2 (DB2 HADR cluster). In this example, there are two hosts involved, db6lpar14 and db6lpar15.

Both hosts are LPARs residing on two different hypervisor hosts. Both hosts are connected to their own storage devices. On the DB2 layer, there are two DB2 instances installed - one on each host. HADR replication is configured between those two DB2 instances, with IBM Tivoli System Automation for Multiplatforms (SA MP) as the cluster manager. There is one resource group modeled in SA MP for DB2 HADR. This resource group also has one configured virtual IP. The VIP is always bound to the host, acting as a primary server.

For each host, there is always one SAP Diagnostic Agent installed. In this example, the SAP Diagnostics

Hosts use the hostnames db6lpar14 and db6lpar15, and they have the SID “DAA” and instance number

79.

The DBA Cockpit always uses the virtual IP to connect to the primary database server.



© 2013 SAP AG 30

Figure 22 - Agent On-The-Fly Topology

Setting Up the SAP Diagnostic Agent Using Agent On-The-Fly

To set up the SAP Diagnostic Agent using agent on-the-fly in SAP Solution Manager, proceed as follows:

1. Logon to SAP Solution Manager.

2. Call up the SOLMAN_SETUP transaction.

3. Choose Managed System Configuration Hosts.

4. Configure both hosts one after the other. The order does not matter. 5. Activate the agent on-the-fly feature.

As a result, the agent installed on the hosts themselves will serve as agent node controller. As soon as a new virtual IP is detected, a new diagnostics agent node will be created. As soon as a virtual IP is gone, the corresponding diagnostics agent node is removed. So this infrastructure will always create a diagnostics

agent assigned to the VIP where the VIP is bound. In our example, the agent node smdagent_db6vdb is

started on host db6lpar14.

If a resource is moved in the cluster as a result of a planned maintenance or unplanned outage, the VIP is

also bound to the other host. For example, the HADR primary role is moved from db6lpar14 to

db6lpar15. The agent node controller on host db6lpar14 will detect that the VIP db6vdb is gone and will

remove the corresponding agent node smdagent_db6vdb. On the host db6lpar15, the agent node



© 2013 SAP AG 31

controller detects the new VIP db6vdb and creates a corresponding agent node smdagent_db6vdb. At

startup time of the agent, it retrieves its configuration from the connected SAP Solution Manager. This ensures a continuous monitoring of the database.

Shared Disk Cluster

In a shared disk cluster environment, activate the agent on-the-fly feature as described in chapter Setting Up the SAP Diagnostic Agent Using Agent On-The-Fly. For the DBA Cockpit connection, use the virtual hostname. The virtual hostname should already be available if you have used outside database discovery in SAP Solution Manager.

Figure 23 - Shared Disk Cluster Setup

IBM DB2 HADR

In an IBM DB2 HADR cluster environment, activate the agent on-the-fly feature as described in chapter Setting Up the SAP Diagnostic Agent Using Agent On-The-Fly. For the DBA Cockpit connection, use the virtual hostname. The virtual hostname should already be available if you have used outside database discovery in SAP Solution Manager.



© 2013 SAP AG 32

Figure 24 - IBM DB2 HADR Cluster Setup

IBM DB2 Database Partitioning Feature (DPF)

In an IBM DB2 DPF clustered environment, activate the agent on-the-fly feature on all hosts as described in chapter Setting Up the SAP Diagnostic Agent Using Agent On-The-Fly. For the DBA Cockpit connection, use the virtual hostname. The virtual hostname should already be available if you have used outside database discovery in SAP Solution Manager.

Figure 25 - IBM DB2 DPF Cluster Setup



© 2013 SAP AG 33

IBM DB2 pureScale

If you want to connect IBM DB2 pureScale clusters to monitoring tools in SAP Solution Manager, your SAP Solution Manager must run on at least release 7.1 with support package 8. In an IBM DB2 pureScale cluster environment, activate the agent on-the-fly function on all member hosts as described in chapter Setting Up the SAP Diagnostic Agent Using Agent On-The-Fly. It is highly recommended to add an IP to this cluster, but do not integrate this VIP to SA MP. For the DBA Cockpit connection, use the virtual hostname and configure another alternative hostname in the setup wizard.

Figure 26 - IBM DB2 pureScale Cluster Setup

If the member fails where the virtual IP is bound, this VIP is not available anymore. But since you configured another alternative host in SOLMAN_SETUP, DBA Cockpit connections are routed by the IBM DB2 client to the alternative host.



© 2013 SAP AG 35

Chapter 7: Troubleshooting

We conclude our sightseeing tour of database administration and monitoring tools with a look at some typical issues that might arise when you use SAP Solution Manager and the DBA Cockpit.

Landscape Management Database

Issue: The database is not available in SAP Solution Manager applications

The outside database discovery runs on the database servers and provides always up-to-date information of the databases in the landscape. The SAP Solution Manager applications including setup are based on the landscape data in LMDB. If the database is not properly discovered, it is not visible in SAP Solution Manager applications.

There are various components involved in the discovery process. Basically, you should check the SAP Host Agent, the Diagnostics Agent and the server side logs on SAP Solution Manager.

Checking the SAP Host Agent

The Diagnostics Agent uses the ListDatabase and the GetDatabaseProperties Web service APIs of

the SAP Host Agent. You could check these Web services on command line as user root. The database

that is used here as an example is BEN. The important data for the discovery process is highlighted in red.

1. Logon as user root. 2. Change to directory /usr/sap/hostctrl/exe.

3. Check the discovery function:

db6xen003:~ # cd /usr/sap/hostctrl/exe

db6xen003:/usr/sap/hostctrl/exe # ./saphostctrl -function ListDatabases

Instance name: db2ben, Hostname: db6xen003, Vendor: DB6, Type: db6, Release: 09.07.0004

Database name: BEN, Status: Running

Component name: db2ben (DB2 instance), Status: Running (DB2 instance started)

Component name: BEN (DB2 database), Status: Running (DB2 connect possible)

4. Check the database properties retrieval function: db6xen003:/usr/sap/hostctrl/exe # ./saphostctrl -function GetDatabaseProperties -dbname BEN

-dbtype db6 -dbinstance db2ben

Webmethod returned successfully

----- Database Properties ----

Database/IsRelocatable=true

Database/DBRelease=09.07.0004

Database/ConfigurationDirectory/Default=/db2/db2ben/sapdbctrl-config

Database/MaxPhysMemSize=1329

Database/CPUCount=4

Database/DBSysBits=64

Database/Distribution=local

Database/InstanceList=Name=0;Host=db6xen003

Database/ConnectAddress=Protocol=tcp;Host=db6xen003;Port=5912;Schema=SAPBEN

Database/IsSharedInstance=false

Database/IsSharedNetService=false

Capability/CopyMethods=Online,Offline

Checking the SAP Diagnostics Agent

The SAP Diagnostics Agent writes a log for the outside discovery of databases. The names of the log files

begin with e2edcc_db*; they are located in the agent directory

/usr/sap/<SID>/SMDA<NR>/SMDAgent/log.

To display the files, proceed as follows:

1. Logon as user root or <smdsid>adm.

2. Change to directory /usr/sap/<SMDSID>/SMDA<SMDNR>/SMDAgent/log.

3. Check for the latest e2edcc_db.* log file.

4. Inspect this file using your favorite editor.



© 2013 SAP AG 36

The following session provides a sample analysis, showing that nothing has changed compared to the agent discovery cache:

db6xen003:/usr/sap/D7C/SMDA79/SMDAgent/log # pwd

/usr/sap/D7C/SMDA79/SMDAgent/log

db6xen003:/usr/sap/D7C/SMDA79/SMDAgent/log # tail -n 10 e2edcc_db.0.log

Feb 14, 2012 11:47:07 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Info

[DatabaseInfoPushJob] Database information do not require update.


[DatabaseInfoPushJob] end.


[DatabaseInfoPushJob] wakeup


[DatabaseInfoPushJob] Check cached database information for Database[db2ben][BEN][db6]






[DatabaseInfoPushJob] wakeup


[DatabaseInfoPushJob] Check cached database information for Database[db2ben][BEN][db6]





This log is configured to write only INFO messages by default. For a detailed error analysis, you can set it to DEBUG, which triggers the creation of very detailed information messages, including the retrieved discovery data of the SAP Host Agent.

To change the log configuration to DEBUG, proceed as follows:

1. Log on to the SAP Solution Manager system and open the agent administration UI like this:

http://<solman_host>:<port>/smd/AgentAdmin

2. Choose the Agent Log Viewer tab page.

3. Choose the agent from the drop-down list.

4. Choose Log Configuration.

5. Change the logging configuration for e2edcc_db.log.

6. Save your configuration

Checking the Server Side Logs Using the Data Enrichment Handler

The landscape browser provides a logging infrastructure, which is also used by the outside database discovery. First you have to enable logging. For this purpose, user SMD_RFC is typically used.

To turn on the logging infrastructure, proceed as follows:

1. Log on to SAP Solution Manager.



© 2013 SAP AG 37

2. Call up transaction SM_WORKCENTER and then choose SAP Solution Manager Administration

Technical Monitoring Landscape Browser.

3. Choose Administration Unified Config.

4. Wait at least 15 minutes, so that you can be sure logs are captured. 5. Choose Administration Unified Logs/Traces.

Filter the string using the expression “Push*Database*<SID>*” for all users.

Issue: No extractors are scheduled for the database

The extractors are scheduled based on the assigned software component version for the system. Check the software component version in the landscape browser.


2. Call up transaction SM_WORKCENTER and then choose SAP Solution Manager Administration

Technical Monitoring Landscape Browser.



© 2013 SAP AG 38

If there is no software component assigned to the database, there might be two potential issues:

You run a new database release that is unknown to your SAP Solution Manager. In this case, update the component repository (CR) content on your SAP Solution Manager according to SAP Note 1625376.

You have issues in the outside discovery of databases. For details, see Issue: The database is not available in SAP Solution Manager applications.

Extractor Framework

Issue: No data is displayed in BW-based reports

Check the EFWK log for errors, especially the number of records processed: 1. Log on to SAP Solution Manager

2. Call up transaction SM_WORKCENTER and choose SAP Solution Manager Administration

Infrastructure Framework Selection Button Extractor Framework.

3. Filter the data (Name = DATABASE*; system ID = <LSID>).

4. Check the Errors and Warnings columns

If no records are processed, check the data collection in the DCF.

Data Collection Framework

Issue: No data is displayed on database-related screens

The DCF collects the history data and stores it in the managed database. If there are issues with the data collectors, you do not get database-related data on most SAP Solution Manager screens or the DBA Cockpit itself.

To check the data collector configuration, proceed as follows:


2. Call up the DBACOCKPIT transaction.

3. Choose your affected system.



© 2013 SAP AG 39

4. Choose Configuration Data Collection Framework Collector Configuration

Check the status messages and the setup status. In addition, check for errors and warnings related to the data collectors:

Figure 28 - Data Collection Framework

Chapter 8: Summary

SAP Solution Manager and the DBA Cockpit provide SAP customers with a wide range of monitoring and database administration functions, especially designed for an SAP system landscape. The smooth integration of the DBA Cockpit into SAP Solution Manager monitoring and the many special features targeted at SAP customers are only two highlights that make SAP Solution Manager the tool of choice for many database administrators. Other highlights of SAP Solution Manager include:

Technical monitoring in SAP Solution Manager, including an overview of the database status and automated alerts in critical situations

Visualizations of database metrics in easily understandable reports

Functions for watching database workload behavior and general growth

Other highlights of the DBA Cockpit include:

Performance monitoring, such as displaying performance and workload statistics, analyzing top SQL statements, performing time spent analyses, or displaying historical snapshots of database objects

Space monitoring and administration, such as watching the space consumption of your database or the analysis of space allocation

Diagnostics to identify critical situations in your database, such as lock-wait events or missing tables and indexes

Backup and recovery overview

Database configuration

Job scheduling, to plan and keep track of all important jobs for databases

The setup of a system landscape for monitoring is quickly done for SAP Solution Manager and the DBA Cockpit. In addition, new features such as the self-monitoring for the DBA Cockpit help the database administrator to identify and solve problems with the monitoring infrastructure itself quickly.



© 2013 SAP AG 40

We hope that this paper has given you some ideas how to set up and use SAP Solution Manager and the DBA Cockpit effectively in your SAP system landscape. Happy monitoring!



© 2013 SAP AG 41

© Copyright 2013 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, 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, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

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

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 Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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.

monitoring ibm db2 for linux%2c unix%2c and windows in sap system landscapes using sap solution...

Documents

sap ag

setup of sap solution

monitoring ibm db2

sap system landscapes

sap netweaver bw

database administrators

sap community network

database status