Professional Documents
Culture Documents
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
The SAP HANA studio runs on the Eclipse platform and is both
the central development environment and the main
administration tool for SAP HANA.
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 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
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
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.
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
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.
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
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.
2014 SAP SE or an SAP affiliate company. All rights reserved. 28
Administration Editor
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.
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
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.
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.
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.
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.
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.
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
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)
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.
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 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.
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.
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.
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.
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.
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
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).
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
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
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.
2014 SAP SE or an SAP affiliate company. All rights reserved. 69
SAP DB Control Center
Enterprise Health Monitor
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.
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.
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.
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.
2014 SAP SE or an SAP affiliate company. All rights reserved. 82
SAP HANA Cockpit
SAP HANA Database Administration
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.
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
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.
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.
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
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).
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.
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
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
SAP DB Control Center
Groups can be managed using the
Group Panel, all available catalogs and
tiles are shown in the Tile Catalog
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
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.
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.