SAP HANA Administration and Monitoring PDF

SAP HANA SPS 10
Administration and Monitoring

June 2015
Agenda
Tools Overview
Introduction to the SAP HANA Studio
Administration Console of the SAP HANA Studio
SAP HANA Systems View
Administration Editor
Diagnosis Mode
Overview
Landscape
Alerts
Performance
Volumes
Configuration
System Information
Diagnosis Files
Trace Configuration
SAP HANA Table Administration
SQL Console
SAP DB Control Center and SAP HANA Cockpit
SAP Solution Manager
2014 SAP SE or an SAP affiliate company. All rights reserved. 2

Tools Overview
Tools Overview Status SPS09/SPS10
The SAP HANA studio is

both the central SAP DB Control Center & SAP HANA Cockpit
development Web-based tool for landscape Web-based tool to monitor
environment and the
monitoring of SAP databases individual SAP HANA databases
main administration tool
for the SAP HANA
database.
With SPS09 additionally
a first version of the web- SAP Solution
based tools SAP DB SAP HANA Studio Manager / DBA
control center and SAP Central development Cockpit
HANA cockpit was environment and main Central tool to manage the
introduced for monitoring
SAP HANA. These tools
administration tool for SAP
HANA, based on Eclipse
SAP SAP landscape, based on
the SAP NetWeaver
can also be used on
mobile devices.
HANA Application Server
Furthermore SAP HANA

is fully integrated into
SAP Solution Manager.
Tools Overview Future Plan
Following SAPs cloud

strategy, SAP HANA offers SAP DB Control Center & SAP HANA Cockpit
web-based tools for Web-based tool for landscape Web-based tool to monitor & operate
monitoring and
monitoring of SAP databases individual SAP HANA databases
administration.
SAP HANA cockpit follows
an alert-driven guided-
procedure approach.
A DBA will be enabled to SAP Solution
check the health state of SAP HANA Studio Manager / DBOS
the system and to drill- Central development Cockpit
down to the root cause of environment and main Central tool to manage the
an issue. administration tool for SAP
HANA, based on Eclipse
SAP SAP landscape, based on
the SAP NetWeaver
It is planned to replace the
administration perspective
of HANA studio with SAP
HANA Application Server
DB Control Center and SAP

HANA cockpit in the long
term. This is the current state of planning and may be changed by SAP at any time.

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 main
administration 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.
The SAP HANA studio program accepts command line

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

Screen Areas of the Administration Console
1. SAP HANA Systems view

2. Editor area, for example:
Administration editor
SQL console 1 2
Table editor
3. Other views, for example:
Error Log
Properties
3
Progress

Administration Console of the
SAP HANA Studio
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 a range 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

System Usage Type
Display of System Usage Type

You can configure the usage type of an
SAP HANA system (for example,
production, development) during
installation with the system_usage
parameter or later by changing the system properties.
SAP HANA studio evaluates this parameter to warn users when they
are 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

SAP HANA System Log on and Log off
Enabled user log on, log off, and system delete functionality with automatic log off system functionality
The user can log off actively from a SAP HANA system via the context menu. Every connection (JDBC/HTTP) is closed after the
user executes the Log Off on a selected system (1). If no connection is established the context menu provides the possibility to
log on to a system or to delete it (2). The start-up behavior of the SAP HANA Studio can be configured. Under Windows >
Preferences the user can decide to restore the logged-on/logged-off status of systems on startup (3).
1 2 3

Linking a centrally-stored archive of SAP HANA Systems
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 users of the SAP HANA
studio. It avoids users having to obtain the connection details of all systems individually and then having to add them all
individually.
One user can manage the list of all systems in a centrally-accessible archive (via File > export > SAP HANA > landscape)
Other users can then simply link to this archive (read-only mode)
2. Specify the link details: 2

a) Link name
1 b) Path to the system archive containing the a)
system information b)
1. In the context menu of the c) Optional: A folder in the SAP HANA Systems
view
SAP HANA Systems view, c)
choose Add System Archive Link. 3. Choose Finish.
3

The Administration editor is

available in the Administration
Console 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.

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 major
performance issues due to high load
or blocking situations, information
can instead be collected using the
connection of the SAP start service
(sapstartsrv).
The Administration editor diagnosis mode provides access to: sapstartsrv
The operational status of all services in the system
Log and trace files python
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 hdbcons
cancel all transactions.
Note: To open the Administration editor in diagnosis mode you need the
HANA
Indexserver
credentials of the operating system user <sid>adm.
Overview Tab
The Overview tab provides you with the most important information about a system at a glance:
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,), their status, and detailed resource
consumption
A context menu with functions including:
Stop, kill, reconfigure service
Reset memory statistics
Remove service

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 on a particular
host at their time of creation, but this assignment can be changed. In certain situations, it is even
necessary. SAP HANA supports several redistribution operations that use complex algorithms to
evaluate the current distribution and determine a better distribution depending on the situation.
The Redistribution sub-tab allows you to execute redistribution operations if you need to:
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. Through the
continuous replication of data from a primary to a secondary system, including in-memory loading, system
replication facilitates rapid failover in the event of a disaster. Productive operations can be resumed with minimal
downtime.
On the System Replication sub-tab, you can:
Perform the initial set-up, that is enable system replication and establish the connection between two
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 primary system is
available again.

Landscape > System Replication Tab II

Landscape > System Replication Tab III
Extended system replication configuration

To offer higher levels of availability you can link
together multiple systems in a multitier system
replication landscape.
After setting up a basic system replication
scenario 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 and
a 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 possible depending on the
system status.

Alerts Tab I
As one of the main components of the

monitoring infrastructure of the SAP
HANA database, the statistics service
performs regular checks and issues an
alert when an alert condition is fulfilled.
The priority of the alert indicates the
severity of the problem and depends on
the nature of the check and configured
threshold values. For example, if 90% of
available disk space is used, a low priority
alert is issued; if 98% is used, a high
priority alert is issued.
The summary header on the Alerts tab
shows the total number of current alerts
by priority and the corresponding list of
alerts

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 week)
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
New implementation design as of SAP HANA SPS 07
The new statistics service design leads to performance and flexibility improvements
The statistics server is the component of the SAP HANA database that provides internal monitoring
functions. It continuously collects information about system status, performance, and resource usage, and
issues alerts in the event of problems. As of SPS 07, it is possible to switch to a new mechanism whereby
data collection and alerting are implemented through the execution of SQLScript procedures. This has the
following advantages:
The statistics server component is no longer required. By replacing the statistics server with internal procedure calls, overall
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 relating to data collection and
alerting. Instead this information is contained in new tables in the _SYS_STATISTICS schema. This increases the overall
flexibility with which data collection and alerting can be configured. For example, data collectors and checks can be scheduled
more flexibly, new collectors and checks can be added more easily, and data collectors and checks can be deactivated.
For more information about how to migrate to the new mechanism after an upgrade, see SAP Note 1917938

Performance Tab
You can monitor the following detailed aspects of system performance on the Performance tab:
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 and highly
customizable. To support administrators performing complex analyses, user-specific column and filter
settings are saved when the Administration editor is closed. These settings are restored the next time
the tab is opened, independent of system.
Performance > Threads Tab I
The Threads sub-tab allows you to monitor all running threads in your system. It may be useful to
see, for example, how long a thread is running, if a thread is blocked for an inexplicable length of
time. 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 analysis:
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 associated
with a thread
See the full details of a thread
Jump to the related calling and
called threads, session or
blocked transaction of a thread
by right-clicking the thread
View the call stack for a specific
thread
Configure the SQL, performance
or 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 statements in a session
You can also configure traces for a specific session (SQL trace, performance trace, expensive
statements trace or plan trace) or cancel sessions.

Performance > Blocked Transactions Tab
If there are blocking situations (indicated on the Threads sub-tab), you can see another
representation of the information about blocked and blocking transactions on the Blocked
Transactions sub-tab. Sort by transaction ID to see the relationship between the two views better.

Performance > Threads, Sessions and Blocked Transactions Tab I
Easy navigation between the editors: Threads, Sessions, and Blocked Transaction
As of SPS07 it is possible to navigate between Performance Threads, Sessions and Blocked Transaction view by using the
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 connection.
The application information (name and user) which is available in the performance threads, sessions and blocked transaction
view can also be used to open a pre-configured dialog for SQL, performance and expensive statement trace.

Performance > Threads, Sessions and Blocked Transactions Tab II
Filter to hide idle sessions, as well as sessions originating in the Administration editor or other
applications in the SAP HANA studio
As of SAP HANA SPS 07 it is possible to hide different session types from the Performance > Threads, Sessions and Blocked
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 not only operating on
display level. When an option is selected, the database is queried again for the relevant sessions.

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 frequently executed
queries. Technically, the plan cache stores compiled execution plans of SQL statements for reuse, which gives a
performance advantage over recompilation at each invocation. For monitoring reasons, the plan cache keeps
statistics about each plan, for instance number of executions, min/max/total/average runtime, and lock/wait
statistics.
Analyzing the plan cache is very helpful as one of the first steps in performance analysis because it gives an
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 cache.
You can view the SQL plan cache on the SQL Plan Cache sub-tab.

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_PARAMETERS to allow for
the 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 than parameter
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/NCLOB
parameter values.
In the Admin editor of SAP HANA Studio on tab
Performance -> SQL Plan Cache the stored parameter
set is used when you choose Visualize Plan or
Prepare in SQL Console

Performance > Expensive Statements Trace Tab I
Expensive statements are individual SQL queries whose execution time was above a configured threshold.
Expensive statements may reduce the performance of the database. The expensive statements trace records
information about these statements for further analysis and displays them on the Expensive Statements Trace
sub-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 specific statement in the
other view using the context menu option Navigate To

Performance > Expensive Statements Trace Tab II
Statement Memory Tracking and Statement Memory Limitation

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 and/or a user specific statement memory
limit in the database:
Global limit: Configuration file global.ini, parameter statement_memory_limit
User specific limit: ALTER USER <username> SET PARAMETER STATEMENT MEMORY LIMIT = <gb>
If both a global statement memory limit and a user statement memory limit are set, the user specific one (higher or lower)
will precede
The HANA administrator can specify a threshold as of which the memory limits are evaluated
Parameter statement_memory_limit_threshold in file global.ini, section memorymanager
Allows to specify a percentage of total memory (as per global_allocation_limit)
No statements are cancelled if the total memory usage is below this threshold
If the total memory usage reaches the threshold and a statement exceeds the memory limit, it will be cancelled

Performance > Expensive Statements Trace Tab III
CPU Time Measurement

The CPU time consumption of a statement can be tracked und displayed in Expensive Statements.
Resource consumption collection has to be enabled manually:
Configuration file global.ini, section resource_tracking, parameters enable_tracking and cpu_time_measurement_mode
Expensive statements trace contains column CPU_TIME which shows the CPU usage of the traced statements
Additionally CPU time values are also shown in the Threads view of the Administration editor

Performance > Job Progress Tab
Certain operations typically run for a long time and may consume a considerable amount of
resources, for example, delta merge operations, data compression, and delta log replays.
You can monitor the progress of these long-running transactions on the Job Progress sub-tab. You
can determine whether or not they are responsible for current high load, see how far along they are,
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 current
performance, 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, you must ensure
that there is enough space on disk for data and log volumes. On the Volumes tab, you can monitor:
Disk usage
Volume size
Other disk activity statistics
There are two views available for monitoring the size of volumes on disk: service and storage type. You
can also filter by host.

Configuration Tab
The properties of an SAP

HANA system are defined in
the parameters of its
configuration files.
Configuration files are
separated into sections;
sections bundle parameters
of the same category.
You can view and modify
system properties on the
Configuration tab.

System Information Tab
The System Information tab lists several predefined SQL SELECT statements on system views. These
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 statements on the System
Information tab for convenient repeated execution
Alternatively, you can import multiple
statements as text or ZIP archive files
To organize large numbers of
statements meaningfully, you can
define a folder structure.
Predefined statements are stored
in the System folder.

Diagnosis Files Tab I
Diagnosis files include log and trace files, as well as a mixture of other diagnosis, error, and
information files. In the event of problems with the SAP HANA database, you can check these
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 using
the Merge Diagnosis Files function
Delete files
Download files
Collect and download diagnosis information

Diagnosis Files Tab II
Runtime Environment Dump File Collection

To analyze issues e.g. if the system is unresponsive, RTE dump files can
be 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 information
about threads, stack contexts, and so on is created and stored in the file
indexserver_<SAPLOCALHOST>_<PORT>_runtimedump.trc.

Trace Configuration Tab I
You can configure the following traces on the Trace Configuration tab. Different configuration options are
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 HANA database. You can
use this information to analyze performance and to diagnose and debug errors. Each service of the SAP HANA
database writes to its own trace file. By default, the database trace is active with default trace level ERROR.
SQL trace
The SQL trace collects information about all executed SQL statements and saves it as an executable python
program. This is good for recording a scenario. By default, the SQL trace is inactive.
Expensive statements trace
Expensive statements are individual SQL queries whose execution time was above a configured threshold. The
expensive statements trace records information about these statements for further analysis. By default, the
expensive statements trace is inactive.
Plan trace
If the plan trace is active, you can visualize and analyze the execution plans for every query that has been
executed in the specified application.

Trace Configuration Tab II
Performance trace
The performance trace is a performance tracing tool built into the SAP HANA database. It records
performance indicators for individual query processing steps in the database kernel. By default, the
performance trace is inactive.
Kernel profiler
The kernel profiler is a sampling profiler built into the SAP HANA database. It collects, for example,
information about frequent and/or expensive execution paths during query processing. By default, the
kernel profiler is inactive.
Note: You cannot analyze the files generated by the performance trace and the kernel profiler meaningfully in the SAP HANA
studio, but instead must use a tool capable of reading the respective output format. SAP Support has tools for evaluating
these traces.
Planning engine trace

If the planning engine trace is enabled, the system records information that allows the data sources
used in the 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 be
activated manually, if the corresponding database feature is used. Parameter enable_export_wizard in section planningengine
of file indexserver.ini has to be set to true, to make the Planning Engine Trace section available on the Trace Configuration
tab.

Trace Configuration Tab III

Table Editor
Some monitoring and problem analysis may require you to examine individual tables, for example, the
many system views provided by the SAP HANA database. You can open tables and views in different
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 and properties (for
example, schema, type, column properties, and indexes). Detailed information relating to the table's
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 result set shows the
actual records in the table.
Data preview
Opening the data preview of a table allows you to analyze the content of the table in different ways.
Similarly to the table content view, this is particularly useful for analyzing system views.

Opening the Table Definition

Table Distribution Editor I
To support the analysis and monitoring of performance issues in a distributed SAP HANA system, a
table distribution editor is available in which you can see how tables and table partitions are
distributed across the hosts. Detailed information about tables/partitions (for example, memory
usage and size) is also available.
You access the Table Distribution editor from the SAP HANA Systems view.

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
You can export catalog objects to a file system and then import them back into another database. For
example, you want to move data from a test system to a productive system, clone your system, or
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 CSV format. Row-
store tables can be exported only in CSV format imported
You can import ESRI shapefiles into dedicated column-store tables

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 and
from 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 part
of 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
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. As a default, all SQL statements are prepared before they
are executed (as of SPS09).
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
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
To help you understand and analyze the execution plan of an expensive statement or an SQL
statement further, you can generate a graphical view of its plan. A graphical representation of the
query, with estimated performance, is displayed. You can then validate the estimated performance
by choosing Execute in the context menu. Another similar high-level graphic is generated with
execution time information for each of the parts.
Visualized Plan Execution Column Plan

SQL Console
Plan Visualizer Overview and Statement Statistics
Plan Visualizer - Overview Plan Visualizer - Statement Statistics

Visualization of execution plans will automatically display an Visualization of execution plans for SQLScript procedures
Overview page also displays a set of statistics for each SQL statement
Key KPIs are displayed to provide an overview before involved in the procedure
starting a detailed details Provides easy drill-down into the most expensive SQL
statement

SQL Console
Plan Visualizer Operator List
Plan Visualizer - Operator List

The Operator List lists detailed characteristics of all operators within a current plan (visualized + executed).
It can be used to dynamically explore the operator set along user defined filters in order to pinpoint specific operators of
interest.
For example you might:
Filter all operators
consuming a certain
minimal 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 plan

SQL Console
Plan Visualizer Tables Used
Plan Visualizer - Tables Used

Provides an overview on which tables have been used
during the processing of a statement
Displays 3 metrics per table:
maximum number of entries processed, i.e. the
overall output cardinality of any processing step
on that table in the statement execution.
number of accesses, i.e. how often a table has
been accessed during statement execution
maximum processing time, i.e. the maximum
processing time across the possibly multiple table
accesses
Double-clicking on any row (table) leads to a corresponding operator list filtered for physical operators accessing the selected
table.

SQL Console
Plan Visualizer Network and Performance Trace
Plan Visualizer - Network

For queries executed in a distributed landscape, the Network view visualizes sequential
network data transfers between different servers based on their given timestamps
Information displayed:
X-axis: servers involved
Y-axis: time elapsed since query execution
duration of network data transfers represented by rectangular bars
size of data transferred in bytes
Plan Visualizer - Performance Trace
Displays list of operators for which performance trace data exists
The data can be viewed by selecting any of the operators
given in the list.
The view consists of two main sections:
left: list of operators you can select to view performance
trace data
right: performance trace data for the selected operator

SAP DB Control Center and
SAP HANA Cockpit
SAP DB Control Center and SAP HANA Cockpit
Overview
SAP DB Control Center
Web-based tool for administration and monitoring of your landscape of SAP databases
SAP HANA cockpit
Web-based tool for administration and monitoring of a single SAP HANA database
HANA HANA IQ IQ ASE ASE

Cockpit 1 Cockpit 2 Cockpit 1 Cockpit 2 Cockpit 1 Cockpit 2
HANA 1 HANA 2 IQ 1 IQ 2 ASE 1 ASE 2


Built following the SAP Fiori design principles
Enables monitoring on mobile devices
Focus on usability
Landscape management for SAP databases
Applications designed to monitor the overall health
of systems located within a data center or across
your enterprise
Start and stop systems
SAP HANA, SAP Sybase ASE, SAP Sybase IQ,
URL of SAP DB control center
http://<host>:<port>/sap/hana/dbcc

Systems Directory
Systems Directory
Allows you to add and manage systems and system groups.
You can add systems one at a time or import many systems in a batch.
When you add a system, you make it available to all users of SAP DCC it is not necessary for each user to add the same
systems.

Alert Monitor
Alert Monitor
The Launch Alert Monitor tile tells you how
many total high priority (HP) and medium
priority (MP) alerts have been reported.
On the Alert Monitor screen, you see a list of
systems on the left that shows how many
alerts each one has. Click a system to display
more information.
If the monitored system supports drilling down
into alerts, you can click the listed alerts to
display further details.
For HANA systems, the drill down opens the
HANA cockpit Alert app for further analysis of
the displayed alerts.
If the monitored system supports impact
analysis, you can see the relationship
between the monitored and other systems in
your landscape and how these might be
affected if the monitored system has an issue.
Enterprise Health Monitor
Enterprise Health Monitor

The Monitor Enterprise Health tile tells you
how many systems are running.
The Enterprise Health Monitor displays a list
of systems with health indicators for
availability, capacity, performance, and alerts.
Hover your mouse over a health indicator icon
(an arrow, for example) to see an explanation
of what it means.
Click in the System, Availability, Capacity,
Performance, or Alerts column for a system to
display information provided by the system's
cockpit. The links available vary; some
systems do not provide links for every
column.
You may be prompted to log in to the system.

Start & Stop Systems
Start & Stop Systems

The Start & Stop Systems tile tells you if any
systems are stopped.
On the Start & Stop Systems screen, you see
a list of systems that shows the state of each
one (running, shutting down, stopped, or
unknown).
If the list is long, focus on systems of interest
by clicking Running Systems or Stopped
Systems at the top of the screen, or use the
search and filter tools.
Authenticate with a system before you try to
start or stop it.
SAP DCC starts and stops systems using the
SAP host agent, which is included in a typical
installation. If the agent is missing, you cannot
start or stop the system from SAP DCC.

SAP HANA Cockpit
SAP HANA Cockpit

Built following the SAP Fiori design
principles
Enables monitoring on mobile devices
Focus on usability
Persona-oriented design principle
Launchpad offers wide range of applications
Applications designed to offer solutions for
typical DBA tasks
Web-application installed as HANA
auto-content
Applications can be integrated in other tools
via URL redirect
Ready for cloud deployments
URL of SAP HANA cockpit
http://<host>:<port>/sap/hana/admin/cockpit

SAP HANA Cockpit
Privileges
Automatic grant of privileges

To ensure that SAP HANA cockpit can be
used immediately after database creation,
the database user SYSTEM is
automatically granted several roles the
first time the cockpit is opened with this
user.
Caution: Do not use the SYSTEM user for
day-to-day activities. Instead, use this
user to create dedicated database users
for administrative tasks and to assign
privileges to these users.

SAP HANA Cockpit
Usability
Database Header
The name of the system or database appears in the
shell bar of the launchpad. If the system has the
system usage type production, this is also indicated.
Context Sensitive Help

The cockpit header now also includes a help icon.
This provides easy access to the documentation for the currently opened app.
Automatic Tile Refresh

The information displayed on the tiles of the SAP HANA cockpit are automatically refreshed
at default intervals
Intervals vary according to the type of information displayed.
You can configure the intervals in the homepage settings.

SAP HANA Cockpit
SAP HANA Multitenant Database Containers: Overview
Multitenant database containers are a new way to run multiple applications/scenarios on

one SAP HANA system
1 system database and multiple tenant databases
Application 1 Application 2
Shared installation of database system software
Strong isolation features, the system database and each
of the tenant databases have their own:
database users,
database catalog,
repository, System
persistence, database
backups,
traces and log files
Distinction between tasks performed at system level and Tenant Tenant
those performed at database level database 1* database 2
Integration with data center operation procedures SAP HANA system
*tenant database = database container

SAP HANA Cockpit
MDC Support
SAP HANA System

Administration
For multiple-container systems a new catalog
is available which allows you to monitor and
manage all tenant databases.
It is only available in the system database.
The following tiles are available:
Manage Databases - indicates overall
system health and provides access to the
Manage Databases app where you can
monitor the status and resource usage of
individual databases, as well as perform
other administration tasks
System Alerts - indicates the number of
high and medium alerts currently raised in
tenant databases and provides access to
the Alerts app where you can view and
analyze alert details
SAP HANA Cockpit
SAP HANA System Administration
Manage Databases
You monitor the overall availability, resource
usage, and performance of tenant databases
and the system database itself from the
system database using the Manage
Databases app.
If you want to examine a particular database
in more detail, you can drill-down further by
clicking the aspect you're interested in (for
example, database name, alerts or used
memory).
Further operations on a tenant database
(stop, start, and delete) are available in the
footer toolbar.

SAP HANA Cockpit
Manage Databases Drill Down

If you want to examine a particular database
in more detail, you can drill-down further by
clicking the aspect you're interested in (for
example, database name, alerts or used
memory).
The corresponding applications display tenant
specific information e.g. the alerts of the
selected tenant database or the load graph
for the selected tenant database.

SAP HANA Cockpit
Creating a Tenant Database

You create tenant databases from the system
database using the Manage Databases app.
Choose Create Tenant Database in the footer
toolbar.
Enter the name of the new database and
the password of the SYSTEM user.
Optional: Specify the host on which the
database is to be created.
Click Create Tenant Database.
The system starts creating the database.
This may take a few moments to complete.
The new tenant database is automatically
added to the Manage Databases app.

SAP HANA Cockpit
System Alerts
The System Alerts tile indicates the number of
high and medium alerts currently raised in
tenant databases and provides access to the
Alerts app where you can view and analyze
alert details.
The system administrator can see only those
alerts that identify situations with a potentially
system-wide impact, for example, the physical
memory on a host is running out.
Alerts that expose data in the tenant database
(for example, table names) are not visible to
the system administrator in the system
database.
It may be helpful to see how alerts are
configured in individual tenant databases. The
system administrator cannot change the
configuration.

SAP HANA Cockpit
MDC Support
SAP HANA Database

Administration
Tiles of this catalog are used to administer an
individual database either a single-container
system, a tenant database or the system
database of a multiple-container system.
The following tiles are available:
Manage Services General Information
Alerts Configure Alerts
Used Memory Manage Roles and Users
CPU Usage Administration Guide
Disk Usage
User Tables
Monitor Statements
Service Restarts
Number of Dumps

SAP HANA Cockpit
SAP HANA Database Administration
Manage Services
The tile displays the
overall database
status.
In the app, the status of all services is
displayed. For each service, detailed
information about its memory and CPU
consumption is available.
Service administration tasks (e.g.
start/stop/kill service, remove service) are
available. Most important actions are directly
available in the footer toolbar, more actions
are available using the menu.
If a service is offline, a link to the
corresponding crash dump is available
If high priority alerts exist, this is shown on the
tile as well as in the app. Direct access to the
Alerts app is provided for further analysis of
such alerts.
SAP HANA Cockpit
Memory Allocation Statistics

Open the Memory Allocation Statistics app
from the Manage Services app by clicking the
value in the Used Memory column of the
service whose memory allocation history you
want to see.
Use the History Graph to analyze the used
memory history of the component and its
subcomponents.
Several options are available, for example:
To change the visualized time period, adjust
the From/To values.
To visualize the memory usage of individual
subcomponents over the same time period
as the selected component, simply select
them in the subcomponents table.
To see time-specific values, move the
mouse over the graph.

SAP HANA Cockpit
Alerts
The tile shows a summary of alerts
The Alerts app provides more information
about these alerts and allows to analyze
historical occurrences.
The current alerts are displayed in list format
on the left. To see more detailed information
about a specific alert on the right, simply
select it.
The details include a link to follow-up actions
or analysis apps and a display of past
occurrences of this alert.
To see past alerts, click Past Alerts in the
footer toolbar.
Options for filtering, searching, and sorting
are available to customize the list of alerts.
To get to the check configuration, click
Configuration Alert in the footer toolbar.

SAP HANA Cockpit
Configure Alerts
All alert checkers are displayed in list format
on the left. To see more detailed information
about a specific check on the right,
simply select it.
The following configuration options are
possible for alert checkers:
Change the threshold values that trigger
alerts of different priorities.
Set up e-mail notifications so that specific
people are informed when alerts are issued.
In addition, you can perform the following
actions on checks:
Run checks on a once-off basis, regardless
of their configured schedule or status
Switch checks off and on

SAP HANA Cockpit
User Tables
The tile shows the comparative memory
utilization by host and the number of high and
medium priority alerts.
Using the app you can visualize tables by
size, explore the usage history of tables, and
move tables to extended storage if SAP
HANA dynamic tiering is installed.
Large in-memory tables that are accessed
infrequently are good candidates for extended
storage, which is provided by the SAP HANA
dynamic tiering option.
Tables in extended storage disappear from
table analysis display.
Be aware that you need additional licenses
for SAP HANA options such as SAP HANA
dynamic tiering.

SAP HANA Cockpit
Monitor Statements
Allows to analyze the most critical statements
currently running in the database.
This can help you identify the root cause of
poor performance, CPU bottlenecks, or out-
of-memory situations.
Contains KPIs like statement runtime, lock
wait time, and cursor duration
By default, statements are listed in order of
longest runtime.
You can identify the application, the
application user and the database user
running the statement.
You can easily identify blocking situations.
You can cancel a session in a blocking
situation either the blocking or the blocked
session can be canceled.

SAP HANA Cockpit
Performance Monitor
Allows to visually analyze historical
performance data across a range of key
performance indicators.
Is opened by clicking the CPU Usage, Disk
Usage, or Used Memory tile on the
homepage of the SAP HANA cockpit.
Initially visualizes resource usage on the
master host and master index server
according to the selected tile.
You can customize the information displayed
in several ways, for example:
Add additional KPIs
Add additional hosts and index servers
Increase or decrease the date range of
collected data
Zoom in to a specific time

SAP HANA Cockpit
System Replication
System Replication
The System Replication tile is
available in catalog
SAP HANA System Replication
It indicates whether or not the system is part
of a system replication configuration
With the System Replication app you can
monitor the status of replication between the
primary system and the secondary system(s).

SAP HANA Cockpit
Backup
Backup
Backup operations are now available in SAP
HANA Cockpit (tile catalog SAP HANA
Backup)
The Data Backup tile displays the status of
the current data backup:
Successful, Running, Canceled, Error
By clicking the tile, the backup catalog is
opened. It shows:
Time range that the backup catalog covers
Size of the backup catalog itself
Information on the last data backups
(status, start time, backup type, duration,
size, destination type and comment)
By clicking an entry in the catalog, detailed
information on the respective backup is
displayed
New backups can be created.

SAP HANA Cockpit
SAP HANA User Management
Role Assignment
You can now use SAP HANA Cockpit to
assign roles to a user
Roles are the standard mechanism of
granting privileges to users in SAP HANA
In the Assign Roles to Users app find the user
you want to edit
Then choose Edit and grant the user further
roles by clicking Assign Roles and selecting
the relevant roles

SAP HANA Cockpit
Further Tiles
System Restarts Tile

Indicates the number of services that have been manually or automatically restarted.
If restarts have been detected, this tile provides access to the Alerts app where you can view the related
alerts.
Number of Dumps Tile
Indicates the number of dump files in the system's trace directory.
This tile provides access to the Trace tool of the SAP HANA Web-based Development Workbench.
Note: The Trace tool of the SAP HANA Web-based Development Workbench opens in a new window and
requires additional roles, either sap.hana.xs.ide.roles::TraceViewer or the parent role
sap.hana.xs.ide.roles::Developer.
Manage Users and Roles Tile
Provides access to the Security tool of the SAP HANA Web-based Development Workbench where you can
provision users
Note: The Security tool of the SAP HANA Web-based Development Workbench opens in a new window and
requires additional roles, either sap.hana.xs.ide.roles::SecurityAdmin or the parent role
sap.hana.xs.ide.roles::Developer.

SAP HANA Cockpit
Further Catalogs
Further Catalogs
Applications that provide core
administration and monitoring features
are available by default.
Applications that allow you to manage
optional components are only available if
the optional component has been
installed.
Examples:
SAP HANA dynamic tiering
SAP HANA smart data streaming
Groups can be managed using the
Group Panel, all available catalogs and
tiles are shown in the Tile Catalog

SAP Solution Manager
Solution Manager Integration
Integrating SAP HANA into the Support Landscape I/II
SM7.1 SP03 HANA SPS03
System Monitoring for SAP HANA Appliance
File System and Log Browser
Early Watch Alert

DBA Cockpit for SAP HANA Database
E2E Change Analysis
E2E Workload Analysis

E2E Exception Analysis
Integration with Business Intelligence Monitoring
CTS+ for HANA studio content
Auto-discovery of HANA systems

Integrating SAP HANA into the Support Landscape II/II

E2E Trace Analysis
Guided Procedures for SAP HANA alerts

Support of new Embedded Statistics Service
(available as of SAP HANA SPS07 Revision 74,
please check SAP notes 1917938 and 1925684)
SM7.1 SP11 + SP12 HANA SPS07

Extended E2E Workload Analysis (Planned)

DBA Cockpit
DBACockpit
Platform-independent tool to monitor, control, configure,
backup and administer the database
Available for SAP HANA database as of BW 7.30 SP05
and Solution Manager 7.1 SP04
SAP GUI version available as well as Web Dynpro
DBACockpit contains a subset of the SAP HANA studio
functionality
Additionally available:
DBA Planning Calendar to schedule backups
Audit Log, logging configuration changes done in the
DBACockpit

More Information
How to find SAP HANA documentation on this topic?
In addition to this learning material, you find SAP HANA documentation 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, administration,
development. So you can find e.g. the SAP HANA Administration Guide in the System Administration and
Maintenance section and so forth

2014 SAP SE or an SAP affiliate company. 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 SE or an
SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or
release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP HANA Administration and Monitoring PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP HANA Administration and Monitoring PDF

Uploaded by

Copyright:

Available Formats

SAP HANA SPS 10

Administration and Monitoring

2014 SAP SE or an SAP affiliate company. All rights reserved. 2

The SAP HANA studio is

Furthermore SAP HANA

Following SAPs cloud

DB Control Center and SAP

2014 SAP SE or an SAP affiliate company. All rights reserved. 5

Administrators can use the SAP HANA studio, for example, to

The SAP HANA studio program accepts command line

2014 SAP SE or an SAP affiliate company. All rights reserved. 7

1. SAP HANA Systems view

2014 SAP SE or an SAP affiliate company. All rights reserved. 8

2014 SAP SE or an SAP affiliate company. All rights reserved. 11

Display of System Usage Type

2014 SAP SE or an SAP affiliate company. All rights reserved. 12

2014 SAP SE or an SAP affiliate company. All rights reserved. 13

Allow users to connect efficiently to multiple SAP HANA systems

2. Specify the link details: 2

2014 SAP SE or an SAP affiliate company. All rights reserved. 14

The Administration editor is

The functions of the

2014 SAP SE or an SAP affiliate company. All rights reserved. 16

Emergency Support Mode

2014 SAP SE or an SAP affiliate company. All rights reserved. 18

The Landscape tab contains several sub-tabs.

2014 SAP SE or an SAP affiliate company. All rights reserved. 19

The Hosts sub-tab provides

2014 SAP SE or an SAP affiliate company. All rights reserved. 20

Note: It is always recommended

2014 SAP SE or an SAP affiliate company. All rights reserved. 21

2014 SAP SE or an SAP affiliate company. All rights reserved. 22

2014 SAP SE or an SAP affiliate company. All rights reserved. 23

Extended system replication configuration

2014 SAP SE or an SAP affiliate company. All rights reserved. 24

As one of the main components of the

2014 SAP SE or an SAP affiliate company. All rights reserved. 25

The Alerts sub-tab provides you with:

2014 SAP SE or an SAP affiliate company. All rights reserved. 26

2014 SAP SE or an SAP affiliate company. All rights reserved. 27

2014 SAP SE or an SAP affiliate company. All rights reserved. 29

2014 SAP SE or an SAP affiliate company. All rights reserved. 30

2014 SAP SE or an SAP affiliate company. All rights reserved. 31

2014 SAP SE or an SAP affiliate company. All rights reserved. 32

2014 SAP SE or an SAP affiliate company. All rights reserved. 33

2014 SAP SE or an SAP affiliate company. All rights reserved. 34

2014 SAP SE or an SAP affiliate company. All rights reserved. 35

Plan Cache: Keep Set of Parameters

2014 SAP SE or an SAP affiliate company. All rights reserved. 36

2014 SAP SE or an SAP affiliate company. All rights reserved. 37

Statement Memory Tracking and Statement Memory Limitation

2014 SAP SE or an SAP affiliate company. All rights reserved. 38

CPU Time Measurement

2014 SAP SE or an SAP affiliate company. All rights reserved. 39

2014 SAP SE or an SAP affiliate company. All rights reserved. 40

The Load sub-tab provides you with a

You can compare the performance of

2014 SAP SE or an SAP affiliate company. All rights reserved. 41

2014 SAP SE or an SAP affiliate company. All rights reserved. 42

The properties of an SAP

2014 SAP SE or an SAP affiliate company. All rights reserved. 43

2014 SAP SE or an SAP affiliate company. All rights reserved. 44

On the Diagnosis Files tab, you can: