The SAP HANA Administration Guide describes the main tasks and concepts necessary for the

ongoing operation of SAP HANA.

The following areas are covered:

SAP HANA studio as an SAP HANA administration tool

Starting and stopping SAP HANA systems

System configuration

License management

User provisioning

Monitoring (for example, performance, memory usage, disk usage, alert situations)

Backup and recovery

The SAP HANA Studio

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 use the SAP HANA studio, 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. Developers can use the SAP HANA studio to create content
such as modeled views and stored procedures. These development artifacts are stored in the repository,
which is part of the SAP HANA database. The SAP HANA studio is developed in Java and based on the
Eclipse platform.
The SAP HANA studio presents its various tools in the form of perspectives. Database administration and
monitoring features are available primarily within the SAP HANA Administration Console perspective.
Additional perspectives include the SAP HANA Modeler perspective and the SAP HANA Development
perspective

SAP HANA Administration Console

To access the database administration and monitoring features of the SAP HANA studio, you open the SAP HANA
Administration Console perspective.

The SAP HANA Administration Console opens. The Systems view is open by default. This view is the central access point for
performing system-specific administration and monitoring activities.

You can always change from another perspective to the SAP HANA Administration Console perspective by choosing Window--
Open Perspective--SAP HANA Administration Console or by choosing the SAP HANA Administration Console button in the
perspective switcher in the upper-right corner of the screen.

The database administration and monitoring features of the SAP HANA studio are presented in the SAP HANA Administration
Console perspective according to a default screen layout.
SAP HANA Administration Console in HANA Studio

Using this feature, you can open HANA database administration and monitoring features in HANA
Studio. By default, it opens in System View.

To open SAP HANA Administration, you can select SAP HANA Administration Console Perspective default
option. You can also access it via Administration button at the top.
Following tabs are available under SAP HANA Administration Console −

 Overview

 Landscape

 Alerts

 Performance

 Volumes

 Configuration
  System Information

 Diagnosis Files

 Trace Configuration

These tabs are used to perform monitoring and administration tasks in your SAP HANA system.

Adding a System in HANA Studio

Single or multiple systems can be added to HANA Studio for administration
and information modeling purposes. To add new HANA system, host name,
instance number and database user name and password is required.

 Port 3615 should be open to connect to Database

 Port 31015 Instance No 10

 Port 30015 Instance No 00

 SSh port should also be open

Port (single Port
Service instance) (multitenant) Details
daemon 3xx00 3xx00 Monitoring and controlling of SAP HANA instance state
Administrative tasks like:
 Taking care of topology information
 Load history collection (SAP Note 2222110)
 Monitoring of system replication (with hdbnsutil
nameserver 3xx01 3xx01 interface)
preprocessor 3xx02 3xx02 Text processing tasks, e.g. for text search
Main SAP HANA service:
 Owner of row and column store (SAP Note 2222277)
3xx40 and  Owner of execution engines for processing database
indexserver 3xx03 higher requests
The standalone statistics server is embedded in the indexserver
with SAP HANA 1.00.93 and higher (SAP Note 2147247), so it
statisticsserver 3xx05 n/a no longer exists as a dedicated service.
webdispatcher 3xx06 3xx06 Processing of http requests
3xx40 and Native SAP HANA application server (XS Classic), will be
xsengine 3xx07 higher over time replaced with XS Advanced
5xx13 5xx13
sapstartsrv 5xx14 5xx14 Start / stop of SAP HANA services and monitoring their state
Authorization for Administration Tasks:
To perform administration tasks in the SAP HANA studio, you require certain privileges and/or roles. These must be granted to
your database user or relevant role by a user administrator.

System Administration and Monitoring:

System Monitoring Tasks

Task Required Authorization

Open the SAP HANA Administration Console System privilege CATALOG READ
perspective with read-only access to the system tables
and monitoring views.

View alert information Object privilege SELECT on the schema

_SYS_STATISTICS

View system information in the System Monitor System privilege CATALOG READ and object privilege
SELECT on the schema _SYS_STATISTICS

Open the Web-browser-based Monitoring Dashboard Role sap.hana.admin.roles::Monitoring

System Administration
Stop, start, restart system Operating system user (<sid>adm) credentials
Stop and start database services System privilege SERVICE ADMIN
Cancel operations System privilege SESSION ADMIN
Mark disk-full events as handled System privilege MONITOR ADMIN

Change the properties of a system as defined System privilege INIFILE ADMIN

in the parameters of the configuration (*.ini)
files

Configure system checks (e-mail notification, System privilege INIFILE ADMIN

alter thresholds)

Catalog Object Administration Tasks

object privileges INSERT/UPDATE, DROP,

ALTER,SELECT,CREATE for the catalog objects

License Management Tasks

Check license information,Installing ,deleting license

keys System privilege LICENSE ADMIN

Security Administration

User and Role Management Tasks

Required Authorization

Create, change, and delete users

System privilege USER ADMIN

Create, change, and delete roles in runtime

System privilege ROLE ADMIN

Backup and Recovery

Perform backups BACKUP ADMIN and CATALOG READ

Recover Need SID<ADM> credentials

2 System Administration
As a database administrator you are responsible for operational tasks related to the administration, monitoring, and maintenance
of your SAP HANA systems.

Several tools are available for system administration:

The SAP HANA Administration Console perspective of the SAP HANA studio is main tool for general system administration
and monitoring tasks.

Specific tasks related to the configuration of system components after installation (such as adding and removing hosts,
renaming systems) are performed using the SAP HANA lifecycle management tools.

2.1.1 Systems View

The Systems view provides you with a hierarchical view of all the SAP HANA systems managed in the SAP HANA studio and
their contents. It is the central access point for performing system-specific administration and monitoring activities.

The Systems view comprises the following elements:

The Catalog folder, which contains all activated database objects, grouped by schema

The Security folder, which contains all database users and activated roles

Starting and Stopping SAP HANA Systems

As the operating system administrator (<sid>adm user), you can stop, start, and restart SAP HANA systems. The SAP start
service (sapstartsrv) is the standard SAP mechanism for starting and stopping systems

Stop and Start a Database Service

You can stop and start the individual database services (nameserver, indexserver, xsengine and so on) running on an SAP HANA
host or hosts.

Prerequisites
You have the system privilege SERVICE ADMIN.

Context

You may need to stop and (re)start services in the following situations, for example:

A host in a distributed system failed and a standby host took over. However, the services of the failed host remain inactive even
after the host is reachable again. In this case, you need to restart the services manually.

Procedure

In the Administration editor open the Landscape--Services tab.

Right-click the service and choose the required Description

option:Option
Stop... The service is stopped normally and then typically
restarted.
Kill... The service is stopped immediately and then typically
restarted.
Reconfigure Service... The service is reconfigured. This means that any changes
made to parameters in the system's configuration files are
applied.
Start Missing Services... Any inactive services are started.

2.3 Configuring SAP HANA System Properties

An SAP HANA system has several configuration (*.ini ) files that you can edit in the Administration editor. Configuration files
are separated into sections; sections bundle properties (or keys) of the same category.

SAP HANA's configuration files contain parameters for global system configuration (global.ini), as well as the configuration of
each service in the system (for example, indexserver.ini). You can access and edit configuration files on the Configuration tab of
the Administration editor. They are stored on the server at the following default location on the server:
/hana/shared/$SID/global/hdb/custom/config.

Set the global_allocation_limit Parameter

The SAP HANA database pre-allocates a pool of memory from the operating system over time, up to a predefined global
allocation limit. You can change the default global allocation limit in the global.ini configuration file.

Configure 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. Clients such as the SAP HANA studio can use this property
to alter behavior.

Prerequisites
You have the system privilege INFILE ADMIN.

Procedure

In the Administration editor, choose the Configuration tab

Navigate to the global.ini file and expand the system_information section.

Configure the usage parameter.

Although you can enter any value, the values listed below can be used by clients to alter behavior. For example, the
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). Note
that there is no change in the behavior of the SAP HANA studio for other values.
production
test
development
custom (default)

Restart the system.

2.4 Managing SAP HANA Licenses

License keys are required to use SAP HANA databases. You can install, and delete license keys using the SAP HANA studio, the
SAP HANA HDBSQL, and SQL.

2.4.1 License Types

License keys are required to use SAP HANA databases. The SAP HANA database supports two kinds of license key: temporary
license keys and permanent license keys.

While temporary license keys are automatically installed in an SAP HANA database, permanent license keys have to be
requested on the SAP Service Marketplace and applied to the individual SAP HANA database.
The global_allocation_limit parameter is used to limit the amount of memory that can be used by the database. The value is the
maximum allocation limit in MB. A missing entry or a value of 0 results in the system using the default settings. The global
allocation limit is calculated by default as follows: 90% of the first 64 GB of available physical memory on the host plus 97% of
each further GB. Or, in the case of small physical memory, physical memory minus 1 GB.

Temporary License Keys

A temporary license key, which is valid for 90 days, is automatically installed with a new SAP HANA database. During this
period, you should request and apply a permanent license key.

Permanent License Keys

You can request a permanent license key on the SAP Service Marketplace under Keys & Requests. Permanent license keys are
valid until the predefined expiration date. Furthermore, they specify the amount of memory licensed to the target SAP HANA
installation. Before a permanent license key expires, you should request and apply a new permanent license key. If a permanent
license key expires, a temporary license key valid for 28 days is automatically installed. During this time, you can request and
install a new permanent license key.
There are two types of permanent license key available for SAP HANA: unenforced and enforced. If an unenforced license key is
installed, the operation of SAP HANA is not affected if its memory consumption exceeds the licensed amount of memory.
However, if an enforced license is installed, the system is locked down when the current memory consumption of SAP HANA
exceeds the licensed amount of memory plus some tolerance. If this happens, either SAP HANA needs to be restarted, or a new
license key that covers the amount of memory in use needs to be installed.

System Lockdown

The system goes into lockdown mode in the following situations:

The temporary license key has expired.

You were using a temporary license key and the hardware key has changed.

The permanent license key has expired and you did not renew it within 28 days.

The installed license key is an enforced license key and the current memory consumption exceeds the licensed amount plus the
tolerance.

You deleted all license keys installed in your database.

In lockdown mode, no queries are possible. Only a user with the system privilege LICENSE ADMIN can connect to the database
and execute license-related queries, such as, obtain previous license data, install a new license key, and delete installed license
keys.

In addition, the database cannot be backed up in lockdown mode.

Monitoring SAP HANA Systems:

To ensure the smooth running of your SAP HANA systems, it is important to monitor system availability and key performance
indicators regularly.

In the Administration editor, you can monitor the following:

Overall system state and resource usage by system and host

Status and resource usage of all system components, for example, name server, index server, and so on

Auto-failover status and configuration of hosts in distributed systems

Alerts issued by the system in relation to its status, performance, and resource consumption

Disk space consumed by system processes for the various storage types (data, log, and trace)

System performance, for example, by analyzing performance indicators such as expensive statements, running threads, and load
history

Monitoring System Availability:

The availability of an SAP HANA system is indicated by its operational status, which you can see in the Systems view, in the
System Monitor, and on the Overview tab of the Administration editor.
An SAP HANA system consists of a number of services (including Indexserver, preprocessor, nameserver, and
compilerserver). The system assumes the status of the service with the most critical status. The status of services is determined
through an SQL connection and/or the SAP start service (sapstartsrv).
Note
Data and logs can only be backed up when all services that persist data are running.

SAP Start Service Unreachable:

An error is also indicated if sapstartsrv cannot be reached. If this is the case but all other services are running (their status having
been determined through an SQL connection), the system itself is operational and accessible.
There are several reasons why sapstartsrv is not reachable. You should first check whether or not it is running. You can do this by
checking the connection to the Web service in a Web browser. Enter the following URL to get the Web service description
(WSDL) from the sapstartsrv of an SAP HANA system:

http://<host>:5<instance_number>13/?wsdl

For a secure connection, enter:

https://<host>:5<instance_number>14/?wsdl

If you receive an XML output that starts with definitions name="SAPControl", then the connection is working.
In many cases, sapstartsrv cannot be reached because the HTTP proxy is incorrectly configured in the SAP HANA studio. To
resolve this, from the main menu, choose Window-Preferences-Network Connections and change the value for active provider
from Native to Direct.

Monitoring Overall System Status and Resource Usage

When you open the Administration editor for a particular SAP HANA system, the Overview tab provides you with a summary of
the overall status of the system, as well as an overview of resource usage.

Monitoring Status and Resource Usage of System Components

To examine resource usage of an SAP HANA system in more detail, for example, to troubleshoot performance bottlenecks, you
monitor its individual components or services.

On the LandscapeServices tab of the Administration editor, you can see the status of the services that start when the system is
started. The initial connection to the system is established by the sapstartsrv service. If you have a multiple-host system, the
services that start depend on which components are actually installed on the instance.
Overview of SAP HANA System Components
Monitoring Host Status and Auto-Failover Configuration
The SAP HANA database supports high availability in a distributed system by providing for host auto-failover. If an active host
fails, for example, because of a hardware failure, standby hosts can take over and thus ensure the continued availability of the
database.

You can monitor the status of individual hosts on the LandscapeHosts tab.

During installation, volumes for storing data and log files are defined. These are the
directories where data and logs are stored. The default directories are:
/usr/sap/<SID>/SYS/global/hdb/data for data
/usr/sap/<SID>/SYS/global/hdb/log for logs

Each active host has exactly one sub-directory beneath these directories called mnt00001,
mnt00002, and so on. The next level in the file hierarchy is the actual volume, with one sub-
directory for each service

Monitoring Alerts
As an administrator, you actively monitor the status of the system, its services, and the consumption of system resources.
However, you are also alerted of critical situations, for example: a disk is becoming full, CPU usage is reaching a critical level, or
a server has stopped.

The statistics server, which is part of the internal monitoring infrastructure of the SAP HANA database, is continuously
collecting and evaluating information about status, performance, and resource usage from all components of the SAP HANA
database.

In addition, it performs regular checks on the collected data and when configurable threshold values are exceeded, issues alerts.
In this way, you are warned of potential problems. 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.

Current alerts are summarized on the Overview tab of the Administration editor and displayed in detail on the Alerts tab.

Monitoring System Performance

Gathering and analyzing data regarding the performance of your SAP HANA systems is important for root-cause analysis and the
prevention of future performance issues.

General information about overall system performance is available in the System Monitor and on the Overview tab of the
Administration editor. You can monitor the following fine-grained aspects of system performance on the Performance tab:

Threads
Sessions

Blocked transactions

Execution statistics of frequently-executed queries in the SQL plan cache

Expensive statements

Progress of long-running jobs

System load

Thread Monitoring
You can monitor all running threads in your system in the Administration editor on the PerformanceThreads sub-tab. It may
be useful to see, for example, how long a thread is running, or if a thread is blocked for an inexplicable length of time

Session Information
The Sessions sub-tab allows you to monitor all sessions in the current landscape. You can see the following information:

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

The operator currently being processed by an active session (Current Operator column).

Blocked Transaction Monitoring

Blocked transactions, or transnationally blocked threads, can impact application responsiveness.

Blocked transactions are transactions that are unable to be processed further because they need to acquire transactional locks
(record or table locks) that are currently held by another transaction. Transactions can also be blocked waiting for other resources
such as network or disk (database or metadata locks).

Monitoring SQL Performance with the SQL Plan Cache

The SQL plan cache can provide you with an insight into the workload in the system as it lists frequently executed queries.

Expensive Statements Monitoring

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

Job Progress Monitoring

Certain operations in SAP HANA typically run for a long time and may consume a considerable amount of resources.

Load Monitoring
A graphical display of a range of system performance indicators is available in the Administration editor on the
PerformanceLoad sub-tab.

You can use the load graph for performance monitoring and analysis.

Monitoring Disk Space

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. You can monitor disk usage, volume size, and other disk activity statistics on the Volumes tab
of the Administration editor.

There are two views available on the Volumes tab for monitoring the size of volumes on disk:

Service

Storage type (that is data, log, and trace)

Directory Hierarchy for Data and Log Storage

During the installation process, the following default directories are created as the storage locations for data and log volumes
respectively:

/usr/sap/<SID>/SYS/global/hdb/data

●
/usr/sap/SID/<SYS>/SYS/global/hdb/log

Note
These default directories are defined in the parameters basepath_datavolumes and basepath_logvolmes in the persistence section
of the global.ini file.