hana e2e adminmonitoring sps07

8/11/2019 HANA E2E AdminMonitoring SPS07

http://slidepdf.com/reader/full/hana-e2e-adminmonitoring-sps07 1/55



© 2013 SAP AG. All rights reserved.

Agenda

• Introduction to the SAP HANA Studio

•The Administration Console of the SAP HANA Studio

• The SAP HANA Systems View

• The Administration Editor

• Overview

• Landscape

• Alerts

• Performance

• Volumes

• Configuration

• System Information

• Diagnosis Files

• Trace Configuration

• SAP HANA Table Administration

• The SQL Console

• More Information



Introduction to the SAP HA

Studio




Introduction to the SAP HANA Studio

The Administration Tool for SAP HANA

The SAP HANA studio runs on the Eclipse platform and is

both the central development environment and the mainadministration tool for SAP HANA.

Administrators can use the SAP HANA studio, for

example, to start and stop services, to monitor the

system, to configure system settings, and to manage

users and authorizations. The SAP HANA studio

accesses the servers of the SAP HANA database by SQL.

The SAP HANA studio presents its various tools in the

form of perspectives. Database administration and

monitoring features are contained primarily within the

Administration Console perspective.


http://slidepdf.com/reader/full/hana-e2e-adminmonitoring-sps07 5/55© 2013 SAP AG. All rights reserved.

Introduction to the SAP HANA Studio

Screen Areas of the Administration Console

1. SAP HANA Systems view2. Editor area, for example:

Administration editor

SQL console

Table editor

3. Other views, for example:

Error Log

Properties

Progress

1 2

3



The Administration Conso

the SAP HANA Studio



Administration Console

The SAP HANA Systems View

The SAP HANA Systems view provides you with a hierarchical view of all the

SAP HANA systems managed in the SAP HANA studio and their contents(database catalog, users, roles). This view allows you to see the status of your systems at glance. It is also the central access point for performing system-specific administration and monitoring activities.

From the context menu of the SAP HANA Systems view, you can access arange of both system-specific and object-specific functions, for example:

Add system

Log On to / Log Off from system

Stop, start, restart system

Open system properties

Back up and recover the system

Import and export catalog objects

Open SQL console

Find table

Open table definition



Enabled user log on, log of f, and system delete functionality with automatic log off system

The user can log off actively from a SAP HANA system via the context menu. Every connection (JDBC/Huser executes the Log Off on a selected system (1). If no connection is established the context menu pro

log on to a system or to delete it (2). The start-up behavior of the SAP HANA Studio can be configured. UPreferences the user can decide to restore the logged-on/logged-off status of systems on startup (3).

SAP HANA Systems View

SAP HANA System Log on and Log off

1 2 3



Allow users to connect eff ic iently to mult ip le SAP HANA systems

A centrally-stored archive of SAP HANA systems is an efficient way to deploy system information to all usstudio. It avoids users having to obtain the connection details of all systems individually and then having t

individually.

One user can manage the list of all systems in a centrally-accessible archive (via File > export > SAP H

Other users can then simply link to this archive (read-only mode)

1. In the context menu of the

SAP HANA Systems view,

choose Add System Archive Link.


Linking a centrally-stored archive of SAP HANA Systems

2. Specify the link details:

a) Link name

b) Path to the system archive containing the

system information

c) Optional: A folder in the SAP HANA Systems

view

3. Choose Finish.

12

3

a)b)

c)




Resource Utilization

T

e

vi

u

fo

re

T

aid

fo

T

o

m

S




Memory Overview

T

e

db

fo

ca

u

O

re

si

ca

O

A

The Memory

Overview editor

is available in

the context

menu of the

Systems view.




Administration Console

The Administration Editor

The Adminis tration edi tor is available in the Administration Console perspective a

for performing administration and monitoring activities. You can open the Administrasystem by simply double-clicking the system in the SAP HANA Systems view.

The functions of the Administration editor are available across several tabs:




Administration Editor

Diagnosis Mode

The SAP HANA studio normally collects information about the system using SQL. H

system has not yet started or is down, no SQL connection is available. In this situatistudio collects information about the database using the connection of the SAP star

(sapstartsrv). You can view this information in the Adminis tration editor in diagnos

way, you can analyze any problems that may occur during startup or while the syste

can also access diagnosis files.

Note: To open the Administration editor in diagnosis mode you need the creden

operating system user <sid>adm.





Overview Tab

The Overview tab provides you with the most important information about a system

System status

General system information

Current alerts

Memory usage

CPU usage

Disk usage

From the Overview tab, you can navigate

to more detailed information.





Landscape > Services Tab

The Landscape tab contains several sub-tabs.

The Services sub-tab provides you with:

A list of all services (nameserver, indexserver, preprocessor, statisticsserver), the

detailed resource consumption

A context menu with functions including:

Stop, kill, reconfigure service

Reset memory statistics

Memory Allocation Statistics





Landscape > Services Tab > Memory Allocation Statistics I

The new Memory Al location Statistics editor enables you to visualize and

explore the memory allocation of every service. In the Administration editor, choose the Landscape -> Services tab. Right-click the service whose

allocation history you want to investigate and choose Memory Allocation Statistics

1 2

3 4





Landscape > Hosts Tab

The Hosts sub-tab provides

you with: An overview of all the

hosts in a distributed system

Detailed information about

the auto-failover status and

configuration of hosts

Host re-configuration options Option to remove a host

from the system





Landscape > Redistribution Tab

In a distributed system, tables and table partitions are assigned to an index server

host at their time of creation, but this assignment can be changed. In certain situatnecessary. SAP HANA supports several “redistribution operations” that use comple

evaluate the current distribution and determine a better distribution depending on t

The Redistribution sub-tab allows you to execute redistribution operations if you n

Redistribute data before removing a host from the system

Redistribute data after adding a new host to the system

Optimize current table distribution

Optimize table partitioning

Note: It is always recommended

that you save the current distribution before

executing a table redistribution operation

in case you need to restore it.





Landscape > System Replication Tab I

System replication is a mechanism for ensuring the high availability of an SAP HANA system

continuous replication of data from a primary to a secondary system, including in-memory loa

replication facilitates rapid failover in the event of a disaster. Productive operations can be re

downtime.

On the System Replication sub-tab, you can:

Perform the initial set-up, that is enable system replication and establish the connection b

identical systems.

Monitor the status of system replication to ensure that both systems are in sync.

Trigger failover to the secondary system in the event of a disaster and failback once the pavailable again.





Landscape > System Replication Tab II





Alerts Tab I

As one of the main components of themonitoring infrastructure of the SAPHANA database, the statistics server performs regular checks and issues analert when an alert condition is fulfilled.

The priority of the alert indicates theseverity of the problem and depends onthe nature of the check and configuredthreshold values. For example, if 90% of available disk space is used, a low priorityalert is issued; if 98% is used, a highpriority alert is issued.

The summary header on the Alerts tabshows the total number of current alertsby priority and the corresponding list of alerts

Ad i i i Edi





Alerts Tab II

The Alerts sub-tab provides you with:

• An overview of:• All current unresolved alerts (default view)

• Alerts sorted by time period (last 15, 30, 60, and 120 minutes, today, yesterday, last we

• Detailed information about individual alerts

• Alert filtering options by:

• Specific word

• Priority

• Check ID• Time frame

• Configuration options for:

• E-mail notification

• Alert thresholds

• Check start times

St ti ti S i




Statistics Service

New implementation design as of SAP HANA SPS 07

The new statistics service design leads to performance and flexibility improvemen

The statistics server is the component of the SAP HANA database that provides internal functions. It continuously collects information about system status, performance, and res

issues alerts in the event of problems. As of SPS 07, it is possible to switch to a new mec

data collection and alerting are implemented through the execution of SQLScript proced

following advantages:

The statistics server component is no longer required. By replacing the statistics server with internal pro

system performance is improved with reduced disk usage, memory usage, and data transfer.

The statisticsserver.ini properties file is no longer required to contain all configuration information relatin

alerting. Instead this information is contained in new tables in the _SYS_STATISTICS schema. This incflexibility with which data collection and alerting can be configured. For example, data collectors and ch

more flexibly, new collectors and checks can be added more easily, and data collectors and checks can

For more information about how to migrate to the new mechanism after an upgrade, see SAP Note 191

Ad i i t ti Edit





Performance Tab

You can monitor the following detailed aspects of system performance on thePerfo

• Threads• Sessions*

• Blocked transactions

• Expensive statements*

• SQL plan cache*

• Job progress*

• Load

*The information displayed on these sub-tabs of the Performance tab is detailed an

customizable. To support administrators performing complex analyses, user-specif

settings are saved when the Administration editor is closed. These settings are res

the tab is opened, independent of system.

Ad i i t ti Edit





Performance > Threads Tab I

The Threads sub-tab allows you to monitor all running threads in your system. It m

see, for example, how long a thread is running, if a thread is blocked for an inexplictime. On the Threads sub-tab:

• Transactionally blocked threads are identified with a warning icon

• The Group and sort filter provides a meaningful and clear structure for thread an

• Threads with the same connection ID are grouped.

• Within each group, the call hierarchy is depicted.

• Groups are displayed in order of descending duration.






Performance > Threads Tab II

On the Threads sub-tab, you can also perform the following actions:

• End the operations associatedwith a thread

• See the full details of a thread

• Jump to the related calling andcalled threads, session or blocked transaction of a threadby right-clicking the thread

• View the call stack for a specificthread

• Configure the SQL, performanceor expensive statement trace






Performance > Sessions Tab

The Sessions sub-tab allows you to monitor all sessions in the current landscape:

• Active/inactive sessions and their relation to applications• Whether a session is blocked and if so which session is blocking

• The number of transactions that are blocked by a blocking session

• Statistics like average query runtime and the number of DML and DDL statemen

You can also cancel sessions.






Performance > Blocked Transactions Tab

If there are blocking situations (indicated on the Threads sub-tab), you can see ano

representation of the information about blocked and blocking transactions on theBl

Transactions sub-tab. Sort by transaction ID to see the relationship between the tw






Performance > Threads, Sessions and Blocked Transactions

Easy navigation between the editors: Threads, Sessions, and Blocked Transaction

As of SPS07 it is possible to navigate between Performance Threads, Sessions and Blocked Transacti

connection ID. This functionality is reachable from the context menu from the view under Navigate To.

In the threads view it is possible to navigate from/to callee/caller by using the thread ID.

In the Sessions view it is possible to navigate to the connection which is blocking the selected connecti

The application information (name and user) which is available in the performance threads, sessions an

view can also be used to open a pre-configured dialog for SQL, performance and expensive statement






Performance > Threads, Sessions and Blocked Transactions

Filter to hide idle sessions, as well as sessions or iginating in the Administration e

applications in the SAP HANA studio

As of SAP HANA SPS 07 it is possible to hide different session types from the Performance > Threads,Transaction view. Each option can be selected in the drop down menu Hide Sessions.

If an option is selected a new SQL statement is executed to display only the filtered rows. This filter is n

display level. When an option is selected, the database is queried again for the relevant sessions.






Performance > SQL Plan Cache Tab

You can use the SQL plan cache to get an insight into the workload in the system as it lists fr

queries. Technically, the plan cache stores compiled execution plans of SQL statements for r

performance advantage over recompilation at each invocation. For monitoring reasons, the pstatistics about each plan, for instance number of executions, min/max/total/average runtime

statistics.

Analyzing the plan cache is very helpful as one of the first steps in performance analysis bec

overview about what statements are executed in the system.

Note: Due to the nature of a cache, seldom used entries will be evicted from the plan ca

You can view the SQL plan cache on the SQL Plan Cache sub-tab.






Performance > Expensive Statements Trace Tab

Expensive statements are individual SQL queries whose execution time was above

threshold. Expensive statements may reduce the performance of the database. Th

statements trace records information about these statements for further analysis an

on the Expensive Statements Trace sub-tab.

You can configure for which user, table/view or application statements should get r






Performance > Job Progress Tab

Certain operations typically run for a long time and may consume a considerable a

resources, for example, delta merge operations, data compression, and delta log r

You can monitor the progress of these long-running transactions on theJob Progre

can determine whether or not they are responsible for current high load, see how fa

and when they will finish. The following information is available, for example:

Connection that triggered the operation

Start time of the operation

Steps of the operation that have already finished (CURRENT_PROGRESS) Maximum number of steps in the operation (MAX_PROGRESS)






Performance > Load Tab

The Load sub-tab provides you with a

graphical display of currentperformance, for example:

CPU usage

Memory consumption

Table unloads

You can compare the performance of different hosts.






Volumes Tab

To ensure that the database can always be restored to its most recent committed state,

that there is enough space on disk for data and log volumes. On the Volumes tab, you

Disk usage

Volume size

Other disk activity statistics

There are two views available for monitoring the size of volumes on disk: service and st

can also filter by host.






Configuration Tab

The properties of an SAP HANA system a

parameters of its configuration files. Conf

separated into sections; sections bundle p

same category.

You can view and modify system propertieConfiguration tab.





System Information Tab

The System Information tab lists several predefined SQL SELECT statements on syst

statements provide you with easy access to important system information.

If you have compiled your own SQL statements for monitoring purposes, you can save t

on the System Information tab for convenient repeated execution





Diagnosis Files Tab

Diagnosis files include log and trace files, as well as a mixture of other diagnosis, e

information files. In the event of problems with the SAP HANA database, you can c

diagnosis files for errors.

On the Diagnosis Files tab, you can:

Filter the list of diagnosis files

(by keyword, host)

Display individual files

Review multiple files at the same time usingthe “Merge Diagnosis Files” function

Delete files

Download files

Collect and download diagnosis information





Trace Configuration Tab I

You can configure the following traces on the Trace Configuration tab. Different configu

available for each trace.

Database trace (including user-specific and end-to-end database traces)

The database trace records information about activity in the components of the SAP HA

can use this information to analyze performance and to diagnose and debug errors. Ea

SAP HANA database writes to its own trace file. By default, the database trace is active

level ERROR.

SQL t race

The SQL trace collects information about all executed SQL statements and saves it as

python program. This is good for recording a scenario. By default, the SQL trace is inac

Expensive statements trace

Expensive statements are individual SQL queries whose execution time was above a c

threshold. The expensive statements trace records information about these statements

analysis. By default, the expensive statements trace is inactive.





Trace Configuration Tab II

Performance trace

The performance trace is a performance tracing tool built into the SAP HANA databas

performance indicators for individual query processing steps in the database kernel. Bperformance trace is inactive.

Kernel profiler

The kernel profiler is a sampling profiler built into the SAP HANA database. It collects,

information about frequent and/or expensive execution paths during query processing

kernel profiler is inactive.

Note: Only SAP development support has the technical expertise required to interpret th

collected by the performance trace and the kernel profiler.





Trace Configuration Tab III



SAP HANA Table Administ

SAP HANA Table Administration




Table Editor

Some monitoring and problem analysis may require you to examine individual table

many system views provided by the SAP HANA database. You can open tables and

ways. Several viewing options are available depending on what you want to do:

Table definition

The table definition view provides you with information about the table's structure

example, schema, type, column properties, and indexes). Detailed information rela

memory usage and size is available on the Runtime Information sub-tab.

Table content

Opening a table's content executes a SELECT statement on the table. The resultsactual records in the table.

Data preview

Opening the data preview of a table allows you to analyze the content of the table

Similarly to the table content view, this is particularly useful for analyzing system v





Opening the Table Definition





Table Distribution Editor I

To support the analysis and monitoring of performance issues in a distributed SAP

table distribution editor is available in which you can see how tables and table part

distributed across the hosts. Detailed information about tables/partitions (for exampusage and size) is also available.

You access the Table Distribution editor from the SAP HANA Systems view.

SAP HANA Table Administration and Monitoring




Table Distribution Editor II

In the Table Distribution editor, you can

perform the following additional actions: Move tables and partitions to other hosts in

the system

Partition non-partitioned tables using the

supported partitioning specifications (hash,

range, and round-robin)

Change a partitioned table into a non-partitioned table by merging its partitions

Note: Before moving tables or partitions, the

system checks that the host has sufficient

memory.


I ti d E ti T bl d Oth C t l Obj t




Importing and Exporting Tables and Other Catalog Objects

You can export catalog objects to a file system and then import them back into anot

example, you want to move data from a test system to a productive system, clone y

provide the data to SAP Support so they can replicate a scenario.

You can export/import either meta data only or meta data and content

Column-store tables, procedures, and sequences can be exported in either binary or C

store tables can be exported only in CSV format imported


Oth T bl Ad i i t ti O ti




Other Table Administration Options

Load into and unload from memory

Under normal circumstances, the SAP HANA database

manages the loading and unloading of tables into andfrom memory independently – the aim being to keep all

relevant data in memory. However, you can manually

load and unload individual tables and table columns if

necessary.

Perform manual delta merge

The delta merge operation is related to the memory

management concept of the column store, that is, the partof the SAP HANA database that manages data organized

in columns in memory. You can trigger the delta merge

operation for a column table manually in the SAP HANA

studio, for example, if you need to free up memory.



SQL Console

SQL Console

E ti SQL St t t i th SAP HANA St di




Executing SQL Statements in the SAP HANA Studio

Some tasks may require you to work with SQL statements,

for example, certain administration tasks can only be

performed using SQL.

You can enter, execute, and analyze SQL statements in the

SQL console.

There are several options available for customizing the

behavior of SQL statement execution in the SQL console.

From the main menu choose Window > Preferences > SQL.

SQL Console

Query Analysis Features




Query Analysis Features

The following functions for analyzing query

execution are available in the SQL console:

Explain plan

Visualize plan

Note: Visualize Plan is also available from the

context menu of the SQL Plan Cache and

Expensive Statements Trace sub-tabs of the

Performance tab.

SQL Console

Plan Visualizer




Plan Visualizer

To help you understand and analyze the execution plan of an expensive statemen

statement further, you can generate a graphical view of its plan. A graphical repres

query, with estimated performance, is displayed. You can then validate the estimat

by choosing Execute in the context menu. Another similar high-level graphic is gen

execution time information for each of the parts.

Visualized Plan ColumExecution

Additional Information

SAP HANA Documentation




SAP HANA Documentation

For more information about the administration and monitoring features of the SAP

introduced in this presentation, see theSAP HANA Administration Guide, which y

• Directly in the SAP HANA studio from the Help menu• On SAP Help Portal at http://help.sap.com/hana_appliance

Other useful documentation available on SAP Help Portal:

• SAP HANA Master Guide

• SAP HANA Technical Operations Manual

• SAP HANA Studio Installation Guide


http://help.sap.com/hana_appliance

http://help.sap.com/hana_appliance




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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation

SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and servicesthe express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an ad

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAcountries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

hana e2e adminmonitoring sps07

Documents