hana e2e adminmonitoring sps08

8/10/2019 HANA E2E AdminMonitoring SPS08

1/62

SAP HANA SPS 08

Administration and MonitoringMay 2014


2/62

2014 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 Monitoring Dashboard

The Memory Overview

The Resource Utilization

The Administration Editor

Diagnosis Mode

Overview

Landscape

Alerts

Performance

Volumes

Configuration

System Information

Diagnosis Files

Trace Configuration

SAP HANA Table Administration

The SQL Console

More Information


3/62

Introduction to the SAP HA

Studio


4/62



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. TheSAP 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.

The SAP HANA studio program accepts command line

parameters that allow you to specify the system to be connectedto immediately on startup.


5/62 2014 SAP AG. All rights reserved.


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


6/62

The Administration Conso

the SAP HANA Studio



Administration Console

SAP HANA Systems View

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

the SAP HANA studio and their contents (database catalog, users, roles). This view allows yoof your systems at glance. It is also the central access point for performing system-specific amonitoring activities.

From the context menu of the SAP HANA Systems view, you can access a range of both sysobject-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




System Usage Type

Display of System Usage Type

You can configure the usage type of anSAP HANA system (for example,

production, development) during

installation with the system_usageparameter or later by changing the system properties.

SAP HANA studio evaluates this parameter to warn users when theyare about to perform critical operations on systems with usage type

production (for example, execute SQL statements, stop or restart the

system, perform a data backup, and so on)

This does not prevent data manipulation in productive systems,

however it keeps reminding you to be careful



Enabled user log on, log off, 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 System Log on and Log off

1 2 3



Allow users to connect efficiently to multiple 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 theSAP HANA Systems view,

chooseAdd 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 thesystem information

c) Optional: A folder in the SAP HANA Systemsview

3. Choose Finish.

1

2

3

a)b)

c)




Monitoring Dashboard

SAPUI5 Based Monitoring Dashboard

The web-browser-based dashboard visualizes keyaspects of system health and configuration, for example:

Current high and medium priority alerts

Memory and CPU usage

Availability of data backups

Drill down to views containing more detailed information

Role sap.hana.admin.roles::Monitoring is required, which

is not granted by default to the standard MONITORING

role


12/62



Memory Overview

It

gth

ca

u

O

re

s

ca

O

A

a

D

The Memory Overview editor is available in the context menu o


13/62



Resource Utilization

T

e

v

u

fo

re

T

aid

fo

T

o

m

S


14/62



Administration Editor

The Administration editor is

available in the AdministrationConsole perspective and is

the main tool for performing

administration and monitoring

activities. You can open the

Administration editor for a

system by simply double-

clicking the system in the SAP

HANA Systems view.

The functions of the

Administration editor are

available across several tabs.


15/62



Diagnosis Mode

Emergency Support Mode SAP HANA studio collects

information about systems using SQL

When a system cannot be reached

by SQL or it is experiencing majorperformance issues due to high load

or blocking situations, information

can instead be collected using theconnection of the SAP start service

(sapstartsrv).

The Administration editor diagnosis mode provides access to: The operational status of all services in the system

Log and trace files

The collection of diagnosis information into a zip file

All connections, transactions, blocked transactions, and threads in the system

If necessary, you can cancel individual connections and transactions, or even

cancel all transactions.

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

credentials of the operating system user adm.

HA

pyth

Indexse

hdbco


16/62



Overview Tab

The Overviewtab 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.


17/62



Landscape > Services Tab

The Landscapetab contains several sub-tabs.

The Servicessub-tab provides you with: A list of all services (nameserver, indexserver, preprocessor,), their status, and d

consumption

A context menu with functions including:

Stop, kill, reconfigure service

Reset memory statistics

Open Memory Allocation Statistics


18/62



Landscape > Services Tab > Memory Allocation Statistics I

The new Memory Al locat ion Stat ist ics 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 Open Memory Allocation Statistics

1 2

3 4


19/62



Landscape > Services Tab > Memory Allocation Statistics II

Analyze the used memory history

of the component and its allocatorsby enabling the history graph

(Show Graph) and exploring the

data.

Several options are available, for

example:

To change the visualized time period, adjust

the From/To values.

To visualize the memory usage of individual

allocators over the same time period as the

selected component, simply select them in

the allocators table.

To see time-specific values, move the

mouse over the graph.

To see the visualized values in table format,choose Show history data in a table


20/62



Landscape > Hosts Tab

The Hostssub-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


21/62


22/62



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.


23/62

Ad i i t ti Edit


24/62



Landscape > System Replication Tab III

Extended system replication configuration

To offer higher levels of availability you can linktogether multiple systems in a multitier system

replication landscape.

After setting up a basic system replicationscenario you add a third system to provide

another level of redundancy.

In a multitier setup the primary system is

always on tier 1, a tier 2 secondary has a

primary system as its replication source anda tier 3 secondary has the tier 2 secondary as

its replication source.

The tier 3 secondary can now also be added

using SAP HANA studio.

On each node only those actions are provided,

which are currently possibledepending on the

system status.

Ad i i t ti Edit


25/62



Alerts Tab I

As one of the main components of themonitoring infrastructure of the SAP

HANA database, the statistics serviceperforms 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% ofavailable disk space is used, a low priorityalert is issued; if 98% is used, a highpriority alert is issued.

The summary header on the Alertstabshows the total number of current alertsby priority and the corresponding list ofalerts

Ad i i t ti Edit


26/62



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

Statistics Service


27/62


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 me

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


28/62



29/62



Performance > Threads Tab I

The Threadssub-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.



30/62



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 orblocked transaction of a threadby right-clicking the thread

View the call stack for a specificthread

Configure the SQL, performanceor expensive statement trace



31/62



Performance > Sessions Tab

The Sessionssub-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.



32/62



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 the Bl

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



33/62



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 Transactioconnection 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



34/62



Performance > Threads, Sessions and Blocked Transaction

Filter to hide idle sessions, as well as sessions originating 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,

Transactionview. 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.



35/62



Performance > SQL Plan Cache Tab I

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.



36/62



Performance > SQL Plan Cache Tab II

Plan Cache: Keep Set of Parameters

The parameter set of a prepared statement is stored in monitoring view M_SQL_PLAN_CACHE_PARAthe easy re-execution of a specific query:

First parameter set is stored when the total execution time of the statement is greater than parameter

plan_cache_parameter_sum_threshold (default 1000ms).

Afterwards, the parameter values will be updated if the statements single execution time is greater th

plan_cache_parameter_threshold (default 100ms) and its last captured execution time.

Parameters to enable this feature:

plan_cache_parameter_enabled: Activate/deactivate

capture of parameter values of prepared statements

plan_cache_parameter_for_lob_enabled: Activate/

deactivate capture of BLOB/CLOB/NCLOBparameter values.

In theAdmineditor of SAP HANA Studio on tabPerformance-> SQL Plan Cache the stored parameter

set is used when you choose Visualize Plan or

Prepare in SQL Console



37/62



Performance > Expensive Statements Trace Tab I

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

Expensive statements may reduce the performance of the database. The expensive stateme

information about these statements for further analysis and displays them on the Expensivesub-tab.

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

You can navigate between the Expensive Statements Trace and the SQL Plan Cache, displaying a spe

other view using the context menu option Navigate To



38/62


Performance > Expensive Statements Trace Tab II

Statement Memory Tracking and Statement Memory Limitation:

Avoid Uncontrolled Statement Memory Allocation The peak memory consumption of a statement can be tracked und displayed in Expensive Statements.

Resource consumption collection has to be enabled manually:

Configuration file global.ini, parameters enable_tracking and memory_tracking

Additionally the HANA administrator is able to define a global statement memory limit in the database:

Configuration file global.ini, parameter statement_memory_limit

If a statement exceeds the memory limit, it will be cancelled



39/62


Performance > Job Progress Tab

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

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

You can monitor the progress of these long-running transactions on the Job 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)



40/62


Performance > Load Tab

The Loadsub-tab provides you with a

graphical display of currentperformance, for example:

CPU usage

Memory consumption

Table unloads

You can compare the performance ofdifferent hosts.



41/62


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 Volumestab, 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.



42/62


Configuration Tab

The properties of an SAP HANA system a

parameters of its configuration files. Confi

separated into sections; sections bundle psame category.

You can view and modify system propertie

Configurationtab.

hostxxx



43/62


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 these statemenInformation tab for convenient repeated execution

Alternatively, you can import multiplestatements as text or ZIP archive files

To organize large numbers ofstatements meaningfully, you can

define a folder structure.

Predefined statements are stored

in the System folder.



44/62


Diagnosis Files Tab I

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 ch

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



45/62


Diagnosis Files Tab II

Runtime Environment Dump File Collection

To analyze issues e.g. if the system is unresponsive, RTE dump files canbe created

On the Diagnosis Files tab, choose Diagnosis Information -> Collect

You can specify:

From which index server(s) RTE dump files are to be collected The number of RTE dump file sets to be collected

The interval (in minutes) at which RTE dump files are to be collected

For each specified index server, an RTE dump file containing informationabout threads, stack contexts, and so on is created and stored in the file

indexserver___runtimedump.trc.



46/62


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 trace

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.



47/62


Trace Configuration Tab II

Performance traceThe performance trace is a performance tracing tool built into the SAP HANA database. It r

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

Kernel profilerThe kernel profiler is a sampling profiler built into the SAP HANA database. It collects, for einformation about frequent and/or expensive execution paths during query processing. By dprofiler is inactive.

Note: You cannot analyze the files generated by the performance trace and the kernel profiler meaningfully in the SAP Hmust use a tool capable of reading the respective output format. SAP Support has tools for evaluating these traces.

Planning engine traceIf the planning engine trace is enabled, the system records information that allows the datathe planning activities to be identified and the same activities to be re-run.

Note: To keep the Trace Configuration tab as simple as possible, this trace section is not available by default but must bthe corresponding database feature is used. Parameter enable_export_wizard in section planningengine of file indexsertrue, to make the Planning Engine Trace section available on the Trace Configuration tab.


48/62


49/62

SAP HANA Table Administ


50/62


O i th T bl D fi iti


51/62


Opening the Table Definition


Table Distribution Editor I


52/62


Table Distribution Editor I

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

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

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


53/62


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.


Importing and Exporting Tables and Other Catalog Objects


54/62


Importing and Exporting Tables and Other Catalog Objects

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

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

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

You can import ESRI shapefiles into dedicated column-store tables


Other Table Administration Options


55/62


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 independentlythe 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.


56/62

SQL Console

SQL Console

Executing SQL Statements in the SAP HANA Studio


57/62


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


58/62


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 Cacheand

Expensive Statements Tracesub-tabs of the

Performance tab.

SQL Console

Plan Visualizer I


59/62


Plan Visualizer I

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

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

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

by choosing Execute in the context menu. Another similar high-level graphic is geneexecution time information for each of the parts.

Visualized Plan ColumExecution

SQL Console

Plan Visualizer II


60/62


Plan Visualizer II

Operator List for Plan Visualizer

The Operator Listlists detailed characteristics of all operators within a current plan (visualized + execut

It can be used to dynamically explore the operator set along user defined filters in order to pinpoint speinterest.

For example you might:

Filter all operators

consuming a certainminimal CPU time

Then order those

operators along the

number of input rows Further restrict the filter

to a specific operator

type (e.g. "Column

Search)

And then double-click on an operator of interest in order to check its positioning within a visualized pla

How to find SAP HANA documentation on this topic?


61/62


SAP HANA Platform SPS

Whats New Release Notes

Installation SAP HANA Server InstallationGuide

Security

Administration SAP HANA Administration Guide

Development SAP HANA Developer Guide

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

presentation, see the SAP HANA Administration Guide, which you can access: Directly in the SAP HANA studio from the Help menu

On SAP Help Portal knowledge center at http://help.sap.com/hana_platform.

The knowledge center is structured according to the product lifecycle: installation, security, admdevelopment. So you can find e.g. the SAP HANA Server Adm inistrat ion Guide

in the Administration section and so forth

http://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdfhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdfhttp://help.sap.com/hana_platformhttp://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdfhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdfhttp://help.sap.com/hana_platformhttp://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdfhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdfhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platformhttp://help.sap.com/hana_platform


62/62


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 produc ts and services

the 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#trademarkfor additional trademark information and notices.
http://www.sap.com/corporate-en/legal/copyright/index.epxhttp://www.sap.com/corporate-en/legal/copyright/index.epxhttp://www.sap.com/corporate-en/legal/copyright/index.epxhttp://www.sap.com/corporate-en/legal/copyright/index.epx

hana e2e adminmonitoring sps08

Documents