All SLIDES Hana Administration

Week 1: Basics and Tooling
Unit 1: Database Administration Tasks

Database Administration Tasks
Course overview – Introduction to SAP HANA Administration
Course Content:
▪ Week 1: Basics and Tooling
▪ Week 2: Managing the Landscape of Databases
▪ Week 3: Managing Individual Databases
▪ Week 4: Performance Analysis
▪ Week 5: Final Exam
System Exercises (optional):

▪ Some course units have hands-on system exercises
▪ To complete the exercises:
– Install your own copy of SAP HANA cockpit
– Download and install SAP HANA, express edition
(a working copy of SAP HANA cockpit comes with it)
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Deepen your knowledge
▪ Learning Journey: SAP HANA Administration & Operations

▪ HA200 SAP HANA 2.0 Installation and Administration
▪ HA215 SAP HANA – Monitoring & Performance Tuning
▪ HA240 Authorization, Security and Scenarios
▪ HA250 Migration to SAP HANA using DMO Migration
Get certified by SAP

The database administrator is responsible for many tasks…
Optimal Management
performance tasks
Peak database Essential database

Upkeep and performance improves management tasks
business processes increase productivity Security
maintenance
and end-user and maximize system
experience efficiency
A well-maintained A secure database
database limits failures allows safe access to
and ensures applications and
acceptable levels of protects business
performance DBA information
Lifecycle Business
management continuity
Diagnosis and
resolution
Sound high availability
Keeping databases
and disaster recovery
and their components Effective database strategies guarantee
up to date reduces the monitoring and continuous database
maintenance effort troubleshooting operations
prevents or minimizes
unplanned downtime
Database administration for SAP HANA
Optimal Management
performance tasks
Properly configure
Upkeep and Observe resources, SAP HANA
particularly memory, parameters, services, Security
maintenance
and analyze workloads alerts, and tenant
databases
SAP HANA provides a Secure the SAP HANA
comprehensive toolset database and restrict
to monitor and capabilities in
administer databases databases
DBA
Lifecycle Business
management continuity
Diagnosis and
resolution
Install and update SAP
Utilize SAP HANA
HANA components, as
In addition to backup/recovery and
well as SAP HANA-
monitoring tools, query system replication
based applications
system views and
inspect trace files

Database monitoring
Databases Resource Utilization Performance

Aggregate System Health Memory Connections
Tenant Databases CPU Transactions
Alerts Disk Statements
Services Network Table Usage
Swap Threads
Sessions
Admission Control

Database management
Tenant Databases Alerts Services System Properties
Backup and
System Licensing Users and Roles System Replication
Recovery
Execute SQL
Database Catalog Trace Files Troubleshooting
Statements
Password Policy Encryption Auditing Certificates

Performance analysis
Provides execution details on

all SQL statements currently SQL Plan Cache
cached in the SAP HANA
database to get insights into
processed workloads Statement Hints
Workload management
Add statement hints to a SQL
allows the user to control
statement without having to
modify the actual statement Workload Management resource consumption within
SAP HANA on system/
or application code
session/statement level
Identify the root cause of Workload Analysis

performance issues on Capture the workload of a
system level by analyzing source system and replay it
threads or engine Capture & Replay on a target system
instrumentation

Platform and application lifecycle management
Platform Lifecycle Management Application Lifecycle Management

▪ Install, update, or uninstall SAP HANA ▪ Install, update, or uninstall SAP HANA
components extended application services,
▪ Add or remove hosts and host roles advanced model (XSA) software
▪ Configure SAP HANA components and products
▪ Display application installation history

Thank you.
Contact information:
open@sap.com
© 2017 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.
The information contained herein may be changed without prior notice. 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 or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP 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 docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ st rategy 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,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Unit 2: SAP HANA Architecture
SAP HANA Architecture
SAP HANA platform
SAP HANA is an in-memory data management and application platform that keeps all relevant
information in main memory (RAM), thus significantly accelerating data processing operations

Single host configured as multi-tenant database container
Web Client SQL/MDX Client Web Client
SAP Web Dispatcher
Name Server Index Server Index Server

Embedded Embedded Embedded Embedded Embedded Embedded
XSA XSC Server Stats Server XSC Server Stats Server XSC Server Stats Server
Preprocessor Other Services Other Services

Other
Compile Services
Server
System Database Tenant Database 1 Tenant Database 2
Data Volumes Disk Storage Log Volumes

Core services
• Most important server Index Server • Runs only in the system database
• Contains actual data stores and • Owns topology of the SAP HANA
temp results system, including knowledge of
• Engines for processing data Name Server tenant databases
• Performs compilation of stored Compile Server • Used by index server to analyze

procedures and programs text data
• Runs on every host and does not • Extracts information on which text
persist data Preprocessor searches are based
• Processes inbound HTTP and Web Dispatcher • Responsible for starting and
stopping other services in the
HTTPS connections to SAP HANA
correct order
extended application services,
• Provides basic monitoring
classic model (XSC) services SAP Start Service capabilities

Optional services
Script server Extended store server
Document store server Data provisioning server
XS Advanced runtime Streaming cluster
HDI server SAP HANA remote data sync
XS Classic server Accelerator for SAP ASE

SAP HANA memory usage
▪ SAP HANA maintains its own memory pool to store

all the in-memory data and system tables, thread
stacks, temporary computations, and all the other
data structures required for managing a database
▪ Used memory is the total amount of memory
currently in use by SAP HANA. This is the most
precise indicator of the amount of memory that
SAP HANA requires at any time
Database administrators need to monitor and

understand SAP HANA memory utilization to
prevent and diagnose memory problems

Properties
▪ An SAP HANA system has several configuration (*.ini) files that contain properties for configuring the system
as a whole, individual tenant databases, hosts, and services
▪ Configuration files contain parameters for global system configuration (global.ini), as well as the
configuration of each service in the system (e.g. indexserver.ini)
▪ Properties are configured at different layers, depending on the configuration file:
Layer Description
DEFAULT ▪ The default value for the property
▪ In general, we do not recommend changing the default values of parameters unless stated in the
documentation or instructed by SAP Support
SYSTEM ▪ The system-specific value for the property
▪ If a system-specific value is not configured for a property, the default value applies
HOST ▪ The host-specific value for the property
▪ For some properties, it is possible to set host-specific values for multiple-host systems. If a host-specific
value is not configured for a property that can be set at host level, the system-specific value applies
DATABASE ▪ The database-specific value for the property
Thank you.
open@sap.com
Unit 3: Administration Tooling
Administration Tooling
SAP HANA administration tools
Non-Native SAP HANA Native SAP HANA

Administration Tools Administration Tools
▪ SAP Solution Manager ▪ SAP HANA cockpit

▪ SAP Landscape Management ▪ SAP DB Control Center
▪ SAP IT Operations Analytics (SAP HANA 1.0 only)
▪ SAP HANA studio

Non-native SAP HANA administration tools
SAP Solution Manager SAP Landscape Management SAP IT Operations Analytics
Offers E2E application lifecycle An automation and orchestration Provides a holistic view of the entire
management, increasing efficiency solution to simplify, automate, and data center in real time by collecting,
and decreasing risk within your centralize the management of your processing, and analyzing massive
existing maintenance agreement. SAP landscapes. volumes of log data.
▪ Monitors the entire SAP stack ▪ Clone, copy, refresh SAP HANA ▪ Data acquisition and Big Data
(SAP HANA and application layer) systems handling
▪ SAP EarlyWatch Alert reporting ▪ Perform single/mass operations ▪ Dashboards
▪ Root cause analysis for SAP HANA ▪ Dashboards, reports, and landscape ▪ Predictive capabilities
▪ Runs on SAP NetWeaver AS for visualization ▪ Runs on SAP HANA XS Classic
ABAP ▪ Runs on SAP NetWeaver AS for
Java

Native SAP HANA administration tools – SAP HANA 1.0
Native Tools for SAP HANA 1.0 Database Administration
SAP HANA 1.0 Cockpit SAP DB Control Center (DCC) SAP HANA Studio
Web-based tool for administration and Web-based tool for centralized Eclipse-based environment for
monitoring of individual SAP HANA administration and monitoring of administration of SAP HANA
1.0 SPS 09 to SPS 12 databases. multiple SAP HANA 1.0 SPS 09 or databases and development of native
higher databases. SAP HANA applications.
▪ Introduced in SAP HANA 1.0 SPS ▪ Introduced in SAP HANA 1.0 SPS 09 ▪ Initial administration tool for SAP
09 ▪ Built as an SAP HANA XS Classic HANA databases
▪ Built as an SAP HANA XS Classic application ▪ Built as a Java application
application ▪ Employs SAP Fiori launchpad for ▪ No longer in feature development
▪ Employs SAP Fiori launchpad for role-based and personalized UI
role-based and personalized UI ▪ Must be installed on an existing SAP
▪ Each SAP HANA 1.0 SPS 09 to HANA database
SPS 12 database includes an SAP ▪ Only one installation of DCC is
HANA 1.0 cockpit necessary in your corporate
deployment

Native SAP HANA administration tools – SAP HANA 2.0
Native Tools for SAP HANA 2.0 Database Administration
SAP HANA 2.0 Cockpit SAP HANA Studio

Web-based tool for centralized administration and Eclipse-based environment for administration of
monitoring of multiple SAP HANA 2.0 and SAP HANA SAP HANA databases and development of native
1.0 SPS 12 databases. SAP HANA applications.
▪ Introduced in SAP HANA 2.0 SPS 00 ▪ Initial administration tool for SAP HANA databases
▪ Absorbs functionality of SAP DB Control Center ▪ Built as a Java application
▪ Built as an SAP HANA XS Advanced application ▪ No longer in feature development
▪ SAPUI5 user interface
▪ Installed as a single stack, but does not require a
dedicated instance of SAP HANA to operate
In the future, the SAP HANA 2.0 cockpit will be the main and only
native tool for administration and monitoring of SAP HANA
databases, running both on-premise and in the cloud
Thank you.
open@sap.com
Unit 4: The SAP HANA Cockpit
SAP HANA Cockpit
Simplified architecture
Three main pieces:

SAP HANA Database Explorer
SAP HANA
1. Built on SAP HANA extended application
cockpit MTA MTA
services, advanced model (XSA), a micro-
XSA
services platform for the development and Cockpit admin + View/interact with
database database objects +
execution of native, data-intensive applications management analyze SQL queries
2. Cockpit features are implemented as XSA multi-
target applications (MTAs) Persistence (embedded SAP HANA, express edition)
3. Persistence: configuration and historical data
SAP HANA cockpit
store
<sidadm> OS user Named database user
The SAP HANA cockpit is installed as a HTTP/XML SQL client

single software stack – no need to install SPS12
each piece individually Host HANA SPS12
Host
SAP SAP HANA 1.0orSPS12
Agent or
Agent
Host HANA 2
or
HANA 2
Agent SAP HANA 2.0

SAP HANA Cockpit
Internals
Cockpit Cockpit
Administrator User
Cockpit manager UAA SAP HANA cockpit Database Explorer MTA

(cockpit-admin-web-app) (cockpit-web-app)
Cockpit admin UI / App Router Security Cockpit UI / App Router sqlanlz-
sqlanlz-ui
SAP HANA cockpit MTA
svc
cockpit-landscape-svc
SAP HANA XSA
Info about systems in the enterprise

hrtt-
hrtt-core
cockpit-adminui-svc cockpit-hdbui-svc service
Cockpit Manager back-end services Micro- Cockpit back-end services
services
interact
with each
cockpit-persistence-svc cockpit-hdb-svc SAP Host Agent
Local persistence of app data other Monitored db service
SAP HANA 1.0 SPS12
cockpit-collection-svc or
Scheduled tasks to retrieve monitored db info
SAP HANA 2.0
Monitored
Persistence (embedded SAP HANA, express edition) databases
SAP HANA Cockpit
System requirements
Processor Memory Hard Disk Operating Web Browser

System
For Intel x64: Google Chrome
Minimum 16 GB + ▪ Red Hat Enterprise
Minimum 16 GB Linux for SAP HANA
Intel x64 space required for
RAM 7.2
data
Mozilla Firefox
▪ SUSE Linux
Enterprise Server for
SAP Applications 12
Microsoft Internet
SP1
Explorer 11
For IBM PPC LE:

Microsoft Edge
IBM PowerPC Little ▪ SUSE Linux
Endian Enterprise Server for
SAP Applications 12
SP1 Apple Safari

SAP HANA Cockpit
Deployment scenarios
Dedicated Hardware Shared Hardware
Server 1 Server 2 Server

SAP SAP
Application Application
SAP SAP
System System
SAP HANA SAP HANA
Cockpit Cockpit
DB Schema DB Schema
SAP HANA SAP HANA
Operating System Operating System Operating System
Storage Storage Storage
Production Non-Production
SAP HANA Cockpit
Getting started – Download
▪ SAP HANA platform 2.0 includes the installation media for SAP HANA cockpit
▪ SAP HANA cockpit periodically releases support packages (SPs) including new functionality, fixes, and
security patches. Each SP includes all the features of the previous SP
▪ The cockpit also provides patches for the most recently released SP that include fixes and security patches.
Once a new SP is released, SAP provides no patches for earlier SPs
▪ Download the latest SAP HANA cockpit SP and patch from the “Support Packages & Patches” section of the
SAP Software Download Center:
Support SAP HANA SAP HANA

SAP Support Software SAP HANA
My Support Packages & H Platform Platform
Portal Home Downloads Cockpit 2.0
Patches Edition Edition 2.0

SAP HANA Cockpit
Getting started – Installation
Installation scripts
▪ For command-line installation, execute hdblcm.sh
▪ For GUI installation, execute hdblcmgui.sh
Default install configuration

▪ Settings in the file auto_install.cfg inside the folder HDB_SERVER_LINUX_X86_64/configurations
▪ Database server properties in *.ini files inside the folder custom
▪ DBAs are free to change these settings and properties as appropriate for their deployment
Installation/upgrade log file created in /var/tmp
Application URLs provided at the end of installation:

▪ Launch SAP HANA cockpit by opening https://<hostname>:51021
▪ Launch SAP HANA cockpit manager by opening https://<hostname>:51023
▪ Installation assigns free ports, but it’s possible to specify them beforehand – see SAP Note 2389709
SAP HANA Cockpit
Launching cockpit manager and SAP HANA cockpit
Cockpit Manager SAP HANA Cockpit

[https://<hostname>:51023] [https://<hostname>:51021]
▪ Use for cockpit administration ▪ Use to manage remote SAP HANA systems
(users/resources/groups/settings) (called “resources”)

Thank you.
open@sap.com
Week1: Basics and Tooling
Unit 5: Registering Resources to Manage
Registering Resources to Manage
The registration process
To administer and monitor an SAP HANA database (aka a resource), it must first be registered to the
SAP HANA cockpit
Registration of resources is performed with the cockpit manager application

▪ A user needs proper authentication to open the cockpit manager (and the SAP cockpit as well)
▪ Normally, a “cockpit admin” accesses the cockpit manager, while a “cockpit user” accesses the cockpit
Required database users:
During registration After registration

▪ A database user called the “technical user” must exist ▪ A database user that can perform the database
in that resource management tasks must also exist in that resource
▪ It gathers resource information during the registration ▪ It has the roles and privileges required to execute the
process desired operations
▪ Once registered, it collects alert and system health
data from that resource and regularly sends it to the
cockpit

SAP HANA cockpit security model
▪ The cockpit user has access to the cockpit application SAP HANA Cockpit
▪ The technical user only requires minimum privileges Cockpit User
Used to access web-based interface of cockpit
to collect alert and system health data:
– GRANT CATALOG READ Technical User
– GRANT SELECT on SCHEMA _SYS_STATISTICS Used to retrieve basic

health data for alerts
Technical User Technical User
▪ The database user needs the appropriate
Database User Database User
authorizations to perform the desired database Database User
management tasks (e.g. DATABASE ADMIN, Used to monitor and administer
BACKUP ADMIN, CATALOG READ, etc.) SAP HANA database
▪ SAP recommends to not use SYSTEM as the SAP HANA SAP HANA SAP HANA
technical user or the database user

Registering your first resource
▪ You can register any SAP HANA resource, but it’s a good idea to register the embedded
SAP HANA, express edition database included with the cockpit, to allow you to:
– Monitor the health of the local cockpit persistence
– Change database properties as necessary (e.g. enable the statistics server)
– Perform database management operations (e.g. make a full data backup)
▪ Registering SAP HANA databases that only have one database user: SYSTEM
– You cannot create users/roles until the resource is registered in the cockpit
– You can temporarily use SYSTEM as both the technical user and database user
– Once registered, create users/roles using cockpit and change the authentication
settings accordingly
– SAP recommends to deactivate the SYSTEM user to prevent uncontrolled access

Thank you.
open@sap.com
Week 2: Managing the Landscape of Databases
Unit 1: The SAP HANA Cockpit Manager
The SAP HANA Cockpit Manager
Managing the landscape of databases – SAP HANA deployment example
SystemDB SAP HANA Cockpit (Cockpit Manager) SystemDB

My Resources Group PRODUCTION Group DEVELOPMENT Group
QATN1 DB DEVTN1 DB
SYSTEMDB@HSR SYSTEMDB@HQA SYSTEMDB@HSR (x2) SYSTEMDB@HDV
QATN2 DB (x2)
REPTN1@HSR (x2)
QATN1@HQA
QATN2@HQA
REPTN1@HSR (x2)
REPTN2@HSR (x2)
DEVTN1@HDV
DEVTN5@HDV
DEVTN2 DB
REPTN2@HSR (x2)
SYSTEMDB@HMH
SYSTEMDB@HDV
DEVTN1@HDV
SYSTEMDB@HMH
MHTN1@HMH
QA Group DEVTN3 DB
SYSTEMDB@HQA
SAP HANA MHTN1@HMH DEVTN5@HDV SYSTEMDB@H4C QATN1@HQA
DEVTN4 DB
SYSTEMDB@H4C QATN2@HQA
(HQA)
DEVTN5 DB
PRODUCTION
QA
SAP HANA
(HDV)
SystemDB SystemDB DEVELOPMENT

SystemDB
REPTN1 DB REPTN1 DB
MHTN1 DB
REPTN2 DB REPTN2 DB
MHTN2 DB
Sys Rep
Host 1 Host 2 Host 3
SAP HANA SAP HANA
(HSR) (HSR) SAP HANA (HMH)
PRODUCTION PRODUCTION
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 2

Overview
▪ The cockpit manager is used to register resources and create groups of resources that other cockpit
users can access with the SAP HANA cockpit
▪ By default, the cockpit manager web app URL is https://<host>:51023
A resource is an SAP
HANA system,
identified by a host
and instance number Resources can be
organized into groups that
can only be accessed by
Cockpit users access
specific cockpit users
the SAP HANA
cockpit and cockpit
manager applications SAP HANA cockpit
settings for data
collection and proxy

Managing resources
▪ Register wizard
– Add resources to SAP HANA cockpit
– Support for single and multiple containers
– Technical user must already exist in the database
– Optionally provide connection encryption, group and contact details
▪ Edit
– Change all settings entered during registration
– Enable and/or enforce single sign-on (SSO)
▪ Import and export wizard
– Export selected, registered resources to JSON-formatted file
– Import selected resources
▪ Unregister
– Remove resources from SAP HANA cockpit
Managing resource groups
▪ Use groups to organize all registered resources in

your deployment
▪ Groups permit specific resources to be managed
only by specific cockpit users
▪ Default groups in SAP HANA cockpit:
– My resources includes all registered resources
available to a given cockpit user
– PRODUCTION includes registered resources
whose “usage” parameter is set to “production”
– DEVELOPMENT includes registered resources
whose “usage” parameter is set to “development”
▪ Create additional groups as appropriate

Managing SAP HANA cockpit users
▪ Two types of cockpit user roles:

– Cockpit user:
monitors specific resources through the SAP HANA
cockpit
– Cockpit resource administrator:
registers/unregisters resources, creates resource
groups, and assigns cockpit users and resources to
groups through the cockpit manager
▪ A default installation of the cockpit creates a single
administration user, COCKPIT_ADMIN
– Employ COCKPIT_ADMIN to create additional
cockpit users with the appropriate roles (either one
or both)

Managing SAP HANA cockpit settings
Data Collection Proxy Server

▪ Polling interval to collect Availability-Performance- ▪ Network and HTTP(S) proxy server settings
Capacity-Alerts information from registered ▪ For HTTP(S) proxy, can use “No Proxy Host”
resources name
▪ Number of worker threads the collection service is
allowed to use
Thank you.
open@sap.com
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 SE’s or its affiliated companies’ strategy and possible future developments, products,
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. All other product and service names mentioned are the trademarks of their respective companies.
Unit 2: Resource Management and Monitoring
Resource Management and Monitoring
Database administration assessment and tasks
View health of all

mission-critical systems
Examine any systems

experiencing problems
What do
DBAs
want at
this level? Navigate to systems
experiencing issues
Execute mass operations

involving many systems

SAP HANA cockpit landscape view
List of groups in my
deployment. Each group
shows the number of high
priority alerts amongst all its
My mission-critical resources
resources
(PRODUCTION – no alerts!)
Total number of resources

in the current group
Click resource name

Resources with the most for quick navigation
high priority alerts in the to its Overview page
current group – quickly and continue
identify resources that need analysis
maintenance
Mass operations for multiple

resources

Resource directory
 Use the resource directory to centrally view detailed information about the registered SAP HANA databases
in a particular group and to manage their access credentials
Add/edit/remove
credentials for database
user (admin and
Single monitoring tasks) and
container operating system user
(start/stop system and
view host diagnostic
files)
SAP HANA SID,

host and instance
number
Multiple database Using SYSTEM for database

containers user – should be changed!
Aggregate health monitor
 Use the aggregate health monitor to obtain a consolidated, high-level view of the health of the resources in a
selected group or in the entire landscape
 Availability: Are managed
resources reachable on the
network? Are they able to
serve the business needs of
their users?
Status can be  Performance: Are managed

running or stopped resources meeting the
response time expectations
of database users?
 Capacity: Do managed
resources have the system
resources to support their
applications?
 Alerts: Do any managed
resources need attention?
The monitor displays the
number of high and medium
priority alerts.

Thank you.
open@sap.com
Unit 3: Configuration Management
Configuration Management
SAP HANA system properties
 Recall: An SAP HANA system has several configuration (*.ini) files that contain properties for configuring
the system as a whole and individual tenant databases, as well as hosts and services
Configuration File  Section  Parameter  Layer  Value
 The SAP HANA cockpit can store and manage snapshots of configurations, allowing DBAs to:
Task Benefit
 Examine current configuration of any resource  View configurations of resources from a central location
 Compare current configuration between two resources  Identify configuration variance between two resources
 Take and save a snapshot of the current configuration  Store “ideal” configuration, particularly before making
of a resource changes (i.e. offers a way to rollback)
 Compare snapshots taken at different times for a  Evaluate whether configuration changes improved
registered resource performance and if not, have ability to undo changes

Comparing configurations between two resources
SAP HANA (Source) SAP HANA (Target)

config.ini  section 1 config.ini  section 1
DEFAULT layer DEFAULT layer
Param1 = a Compare Param1 = a
Param2 = b Param2 = y
Param3 = c Param3 = z
Param4 = d Param4 = d
config.ini (2)
Section Parameter Layer Source Value Target Value
1 Param1 DEFAULT a a
Param2 DEFAULT b y
Param3 DEFAULT c z
Param4 DEFAULT d d

Taking and storing snapshots
17 Aug 2017 20 Sep 2017 31 Oct 2017
SAP HANA SAP HANA SAP HANA

config.ini  section 1 config.ini  section 1 config.ini  section 1
DEFAULT layer DEFAULT layer DEFAULT layer
Param1 = a Param1 = a Param1 = a
Param2 = b Param2 = x
Param3 = c Param3 = y Param3 = y
Param4 = d Param4 = z Param4 = z
snapshots
Timestamp Description
2017/08/17 00:00:00 Clean install
2017/09/20 00:00:00 Updated security settings
2017/10/31 00:00:00 Performance improvements

Comparing snapshots of the same resource
Snapshot 2017/08/17 00:00:00 Snapshot 2017/10/31 00:00:00

config.ini  section 1 config.ini  section 1
DEFAULT layer DEFAULT layer
Param1 = a Param1 = a
Compare
Param2 = b
Param3 = c Param3 = y
Param4 = d Param4 = z
config.ini (3)
Section Parameter Layer Source Value Target Value
1 Param1 DEFAULT a a
Param2 DEFAULT b
Param3 DEFAULT c y
Param4 DEFAULT d z

Thank you.
open@sap.com
Unit 4: Resource Groups
Resource Groups
Concept and benefits
 A typical SAP HANA cockpit deployment Sample SAP HANA cockpit configuration
organizes registered resources in groups Group # of Resources Cockpit User Assigned
 Group visibility is restricted to cockpit users in Group Group(s)
who have access to that/those group(s) DEMO 3 COCKPIT_ADMIN All
openSAP 2 DEMO_USER DEMO
– Allows different DBAs to manage only a
subset of resources PRODUCTION 1 OPENSAP_USER openSAP,
PRODUCTION
– “My Resources” system-generated group is
always present and contains all resources
available to the cockpit user
 Mass operations (resource directory,
aggregate health monitor, and compare COCKPIT_ADMIN:
configs) apply to just the resources in a My Resources (6), DEMO (3), openSAP (2), PRODUCTION (1)
group DEMO_USER:
My Resources (3), DEMO (3)
OPENSAP_USER:
My Resources (3), openSAP (2), PRODUCTION (1)

Resource Groups
SAP HANA cockpit group view
Logged in as DEMO_USER,
assigned only to DEMO group
“My Resources”
group will also show
3 resources
Availability tile allows

quick visibility to state of
databases in this group
Mass operations only apply to

the resources in this group
Thank you.
open@sap.com
Unit 5: Managing Tenant Databases
Managing Tenant Databases
SAP HANA multitenant database containers
 As of SAP HANA 2.0 SPS 01, multitenant database

containers (MDC) is the only operational mode for Application Application Application Application
SAP HANA systems
 An MDC system consists of a system database for
overall system administration tasks and one or more
tenant databases
 SAP HANA cockpit provides management Tenant Tenant
capabilities at both the system database and tenant DB DB
database level Tenant Tenant
DB DB
– SystemDB level: management of all tenants in the System
system + standard administration and monitoring SAP HANA System DB
for the system database
– Tenant level: standard administration and SAP HANA cockpit can manage the system database
monitoring for the tenant database and all tenant databases

SystemDB-level management tasks (1)
Basic Monitoring for Tenants

 Overall tenant statuses
 Tenant databases with most high-priority alerts
 Individual database running status and start time
 Alerts
 Backup details
 Resource utilization (memory, CPU, and disk)
Navigation to Tenant
 For registered tenants, navigation to appropriate
application (alert details, backup, performance
monitor, etc.) or to the tenant’s Overview page

SystemDB-level management tasks (2)
 Create/delete tenants  Start/kill/remove services

Tenant database administration  Start/stop tenants  Assign the operating system user and
 Backup/recover/copy tenants group for high isolation
 Properties that can only be changed by the system admin (i.e. tenant database admins
Manage blacklisted parameters cannot change them)
Manage restricted features  System admin can choose to disable certain SAP HANA database features in tenants
 Define memory allocation limits for database services

Configure workload allocation  Define CPU core allocation limits for each database

Standard administration and monitoring for SystemDB and tenants

Thank you.
open@sap.com
Week 3: Managing Individual Databases
Unit 1: Monitoring
Monitoring
Individual database management – Monitoring in the SAP HANA cockpit
Although SAP HANA databases can self-monitor and generate alerts, it is still critical that
database administrators regularly monitor the operation of SAP HANA databases
Constant monitoring allows:

 Recognition and prevention of serious errors
 Identification of periods with high resource consumption
The SAP HANA cockpit provides a range of dedicated apps

to monitor:
 Overall database health
 Workload performance
 Status and resource usage of individual database services
 Database performance across a range of key performance indicators related to memory, disk, and CPU
usage
 And more!
Monitoring
Overview page
Links let you quickly jump
Directly access the SQL
to section of interest
 Monitor KPIs at a glance console for this database
with the Overview page Monitor high-priority alerts
 Tiles give a high-level from tenant databases
overview of the database
status, while drilling down
gives a detailed Color-coded icons visually
represent status of
breakdown of selected database
features Different categorizations of
database-specific alerts allows quick
 Focus on areas that need
identification of areas in trouble
immediate attention, and
Graphical view of memory,
easily access key CPU, and disk usage
database management makes unusual behavior
and performance analysis easy to detect Performance analysis
and lifecycle management tiles clearly display any
threads, sessions, or
tasks SQL statements that
could be slowing down
performance
Monitoring
Monitoring and managing database services
View alerts associated
with this database
View overall
database status Stop system as a whole
Change columns
displayed in table
View CPU usage in
Performance Monitor
Individually stop
Drill down to see services
Memory Allocation
Analysis application
 Drill down from Overall System Database Status  See key information about systems such as status,
tile on Overview page start time, alerts, CPU and memory usage
 Start missing services, kill service, remove service  Customize columns to show used memory, effective
or (only for tenant databases) add a service allocation limit, allocated shared memory, virtual
memory on host, size of caches, and more!
Monitoring
Performance Monitor – CPU usage Correlate alerts in
CPU usage with graph
 See preview of historical CPU

usage on Overview page tile
Choose an interval of
 Performance Monitor provides time to view on the Enable/disable
graph auto-refresh and
detailed information for analysis set refresh time
of current and past CPU usage
 Import data sets to visually
analyze historical performance
data across a range of
performance indicators
Hover over a KPI line
to see exact value
and time

Monitoring
Performance Monitor – Memory and disk usage
Add chart to see selected Switch between

KPIs separately on Performance Monitor
different chart and Workload Analyzer
 Clicking the Memory Usage and Disk Usage tiles drills down
to the Performance Monitor
 Graphs are automatically populated with relevant KPIs

Monitoring
Monitor Network
 Measure network speed between different

SAP HANA nodes in a multi-host deployment
 In a system replication scenario, measure
how fast data is being transferred from host Choose between packet
to host sizes of 0MB, 10MB,
100MB, and 1000MB
 Allows for easier identification of issues due
to network performance
Check network speed
between every pair of
hosts

Monitoring
Other monitoring tools
Monitoring
Monitoring performance
Monitor table usage
Monitor expensive statements
Open SQL plan cache
Open blocked transactions
Monitor Network

Monitoring
System and statistics views
 System views contain important information about the

database and can be examined to analyze the data
directly as part of more detailed monitoring and
performance analysis
 SYS schema contains various information about the
current state of the database
 _SYS_STATISTICS schema contains historical data
 All views have public synonyms, so it’s not necessary
to specify the schema name when querying them
 Use the SQL Console to query system views
 SAP provides a compilation of useful SQL statements
to analyze complex problems in SAP Note 1969700 –
SQL Statement Collection for SAP HANA

Thank you.
open@sap.com
Unit 2: Security
Security
Individual database security in SAP HANA
User & Role Management Data Encryption

Create standard and restricted Protect your data with data
users; customize roles with a volume, log volume, and backup
variety of privileges encryption
DBA
Authentication Auditing
Authenticate users using Monitor and record selected
passwords and a diverse range Certificate Management actions performed in your
of SSO options Secure internal and external database
communication channels, user
authentication mechanisms

Security
User and role management
Control system
administrative privileges
Choose validity range,

ODBC/JDBC access, and
whether or not public role is
automatically assigned
Users can be authenticated

using passwords or SSO
options
Access and modify

database objects
Configure custom user properties

such as locale, execution priority,
user time zone, etc.  Easily create new users, new roles, and assign roles
to users all through the SAP HANA cockpit interface
Security
Authentication
 Customize the password policy and

blacklist to ensure that corporate
standards are met
 Password policy parameters:
– Customize the password length,
composition, and lifetime
– Configure user lock settings
 Blacklist words to prevent
vulnerabilities due to weak passwords
– Case sensitivity
– Partial or whole word

Security
Data storage security
 Safeguard SAP HANA data saved to disk from

unauthorized access at the operating system View alerts associated with
level data encryption
 Data at Rest Encryption protects data
volumes on disk
 Log Volume Encryption protects log entries Manage master key or
before they are written to disk specific root keys
 Backup Encryption protects against
unauthorized parties accessing content of
backups
 Enabling encryption does not increase data
size

Security
Auditing
Directly enable/disable auditing

 Record important system events from Overview page
with audit logging:
– User management
– System access/configuration
– Data access
 Auditing does not directly increase
system security, but well-designed
audit policies can help achieve
greater security
 Choose audit level, trail target,
audited action status, and Choose actions, objects,
and users to be audited
individually enable/disable audit
policies

Security
Best practices
 User and Role Management

– Only use the SYSTEM user to set up the database and appropriate users
– Deactivate the SYSTEM user afterwards to prevent misuse of its permissions
 Data Storage Security

– Change root keys used for data volume encryption and redo log encryption
– Enable data volume and redo log encryption
– Periodically change root keys in line with your security policy
 Consult the security related links in the SAP HANA cockpit

Thank you.
open@sap.com
Unit 3: Alert Management
Alert Management
Alerts in the SAP HANA cockpit
The SAP HANA cockpit follows an alert-driven guided-procedure

approach
 SAP HANA databases self-monitor their status and performance
Cockpit
– Continually collect and evaluate information about status, notifies the
performance, and resource usage DBA through
email and
– Perform regular checks on data in system tables and views
various
 When a predefined threshold is reached or exceeded, an alert is interfaces
generated to alert administrators of a critical situation
– Customizable alert thresholds map to different alert priorities
– High, medium, low, and info level
 Analyze occurrences of an alert over time to troubleshoot An alert is
DBA
addresses
recurring problems and identify patterns generated in
alert and
an SAP
investigates
 Note: The statistics server for a database must be enabled to HANA
source of
database
generate alerts problem

Alert Management
Landscape page
Alert badge in Group

navigation bar allows quick
understanding of a
resource group’s overall
health
Top Resources with Alerts
tiles gives a global view
of resources that need
attention immediately
Click the tile of a system to
access its Overview page
and investigate the source
4 2 of the alert
Only high priority alerts are

displayed on this tile

Alert Management
Overview page
 Alerts are organized into 10 different

categories internally in SAP HANA
– Cockpit follows this categorization by
displaying each classification in its own tile
on the Overview page
– Only high and medium-priority alerts are
View proposed solution
displayed to quickly identify major issues
 Clicking an alert tile drills down into filtered
view
– Filtered by priority, category, and database
 The Alert Details page shows when the alert
occurred, what category it is from, its priority,
its next scheduled run date/time, and the
interval that the alert checker runs at
See past occurrences of alert in the last
24 hours, last 7 days, and last 30 days

Alert Management
Accessing alerts from other applications
 To enhance navigation, the Alert Details screen can be

accessed from multiple different applications, aside from
the main alert interface
 While working with the cockpit,
you may run into issues with
services or databases
– Clicking an alert link from any of Clicking any of these links
brings you to the alert
these tiles or apps will take you to a details of the relevant alerts
filtered drilldown of any relevant
alerts

Alert Management
Alert Checker Configuration
Change default
thresholds for alerts
 There are over 100 different alerts that
can be triggered in the cockpit
 Enable/disable scheduling for alerts Customize email
– If enabled, will run automatically recipient of this
alert if it is triggered
– If disabled, will only run when
manually initiated
 See the last time the alert checker
was run, description of the alert, alert
checker ID, and category of alert
 Set default email sender/recipient, or Manually run check
specify email recipients for individual to see if alert will
be triggered
alerts to separate responsibilities

Thank you.
open@sap.com
Unit 4: Backup and Recovery
Backup and Recovery
Backup and recovery in SAP HANA
SAP HANA holds the bulk of its data in memory for maximum performance,
but still uses persistent storage to provide a fallback in case of failure
 During normal operation:

– Data is automatically saved from memory to disk Time
at regular savepoints
– All data changes are captured in redo log entries
Savepoint: After each COMMIT,
 After a power failure, SAP HANA can be restarted Data is written log is written to disk
Power failure
and returned to its last consistent state by replaying to disk (data area) (log area)
the redo log entries since the last savepoint
 While savepoints and redo log writing protect your data against power failures, this does
not help when the persistent storage itself is damaged or a logical error occurs
 Backups save the data present in the persistence and are required:
– To protect against disk failures
– To make it possible to reset the database to an earlier point in time
Backup and Recovery
Types of backups in SAP HANA
Full data backup A full data backup contains all current data
 All data  Old data that is no longer valid but might still be physically
present in the data volumes is not part of the data backup
Incremental backup
Delta backups contain data that was changed since an
 Changed data since
the last data backup earlier data backup
(full or delta)  Two types: incremental and differential
 Delta backups contain actual data, in contrast to log backups,
Differential backup
which contain redo log entries (= sequence of changes)
 Changed data since
 Delta backups can be used together with a snapshot for system
the last full data
recovery
backup

Backup and Recovery
Database backup in SAP HANA cockpit
Create complete,
differential, or
incremental backups
Choose start of schedule,

time of backup and
recurrence
 Configure backup type, destination type, backup
name, backup destination, backint parameters
 User can continue working normally while
 Using the backup catalog, easily create manual backups are running
backups or create a schedule to routinely back up a
selected resource
Backup and Recovery
Database recovery in SAP HANA cockpit
 Set the recovery target to restore data from: Choose between default
backup catalog location
– Most recent state or an alternative location
– A specific point in time
 Choose between different options for delta backup usage, If you have multiple
backups, you can choose
backup availability checks, and initialization of log area which one to use
 SAP HANA databases must be offline to be recovered
 Recovery is always initiated from the system database
 Recovery for databases through SAP HANA cockpit is only
supported for SAP HANA 2 databases

Backup and Recovery
Tip: backing up SAP HANA cockpit
 It is highly recommended to back up SAP HANA cockpit prior to upgrades and after
registering a large amount of resources
 Ensure important business information is not lost through regular backups
 Backing up SAP HANA cockpit backs up the persistence and application server which
SAP HANA cockpit runs on
 Recovering SAP HANA cockpit will restore the previous landscape configuration from
the selected backup
 SAP HANA cockpit needs to be offline when recovering

Thank you.
open@sap.com
Unit 5: System Properties
System Properties
System properties in the SAP HANA cockpit
SAP HANA parameters are configuration options that can be used to influence the behavior
of SAP HANA in various ways
 These parameters, which are contained in several configuration (*.ini) files, permit customization of the
system as a whole, individual tenant databases, hosts, and services
– Configuration files are separated into sections. Sections bundle properties of the same category
 Typical reasons for setting parameters are:
– Individual security settings
– Specific changes in behavior and operation of database services and components
– Influencing system-wide resource consumption and workload execution
 Properties can be configured at different levels or layers depending on the
configuration file. The following layers are available:
– Default, host, system, database

System Properties
System property configuration
 Configure system properties

Filter according to
for a selected database configuration, section,
 Required database user host, and database
privileges: Search for a parameter
– INIFILE ADMIN
Add a new section
– DATABASE ADMIN to
change the system
property of a tenant
database from the system
database
 Compare configurations
between systems using the
Edit/delete
Configuration Manager changed values
(Week 2 Unit 3) Add new or restore their
key/values to a default value
selected section

System Properties
Configuration – Adding new sections and parameters
Select file to add

new section to
Choose between
host, system, and
database level
Add a single or
multiple new
key/value pairs

Thank you.
open@sap.com
Week 4: Performance Analysis
Unit 1: Analyzing Memory Usage
Analyzing Memory Usage
Memory Analysis application in SAP HANA cockpit
 Displays the current memory usage statistics and their

trend over time
 Offers charts and filters for easy time-based analysis
 Detailed tabular analysis based on components,
subcomponents, tables, and out-of-memory (OOM) events
– Historical overview for host and service
– Used memory by component, categorized by type
– Used memory by subcomponent, filtered by component
– Used memory historical graphs
– Top 10 tables by size and growth
– Occurrences of OOM events, including their reason
 Useful in determining what caused a memory spike,
especially if it resulted in an OOM situation

Memory Analysis application: technical details
Memory allocation (current and historical) is derived

from SAP HANA system views:
 HOST_RESOURCE_UTILIZATION_STATISTICS
 HOST_SERVICE_MEMORY
 HOST_SERVICE_COMPONENT_MEMORY
 HOST_HEAP_ALLOCATORS
 GLOBAL_ROWSTORE_TABLES_SIZE_BASE
 HOST_COLUMN_TABLES_PART_SIZE
 M_OUT_OF_MEMORY_EVENTS
All views stored in the _SYS_STATISTICS schema

Step 1: Launch the Memory Analysis application
 Open the Manage Services app by clicking the “Overall Database Status” tile on the Overview page
 Open the Memory Analysis app by clicking the mini bar-chart in the memory column of the service whose
memory statistics you want to inspect

Step 2: Pick the desired data using the various controls and selections available
Host & Service selection dropdown Time selection Collection frequency
Unit selection dropdown

Step 3: Inspect the memory statistics using the top chart and select point in time to examine
Memory alerts
Global Allocation Limit

Allocated Memory
Total Used Memory

Step 4: Examine the used memory by the different components
Used memory by component
Used memory by type
Components’ used memory history

Step 5: Examine the subcomponents for more details on memory use
Used memory by subcomponent
Filter by component name
Subcomponents used memory history

Step 6: Examine table size and growth
Top 10 tables by size Top 10 tables by growth
 Table size and growth shows memory distribution across tables and provides a way to determine potentially
fast-growing tables requiring further investigation
Step 7: Examine OOM events
List of OOM events with reason and SQL statement
 Out-of-memory events show the out-of-memory incidents that have occurred, including the reason for
occurrence and related SQL statement
Thank you.
open@sap.com
Unit 2: Analyzing SQL Statements
Analyzing SQL Statements
SAP HANA SQL analyzer
 Provides starting point for query-level SAP HANA SQL Processor
performance analysis
 Use to analyze different aspects of executed
SQL query to evaluate potential bottlenecks
and optimizations
 Includes similar functional scope as PlanViz in
SAP HANA studio
 Offers deeper insights into SQL-based queries
and SQLScript-based queries
 Works in collaboration with other performance
management tools to complement full end-to-
end view of system performance
 Tool invoked via extensive SQL statements
app, plan trace app, or Database Explorer

SAP HANA SQL analyzer: overview
 Overview screen shows details for executed SQL statements

 Displays overall KPIs regarding runtime, dominant operators, tables used, etc.
 Similar to PlanViz overview in SAP HANA studio

SAP HANA SQL analyzer: Plan Graph
 Use Plan Graph to visualize the query

execution plan of a SQL statement
 Displays the operators used with specifics
on data sets transferred and time elapsed
 Click the operator to see more information
such as name, location, summary, etc.

SAP HANA SQL analyzer: Timeline
 Use Timeline view to analyze statement execution based on time

 Different types of tasks can be analyzed, as well as parallelization and operator dependencies

SAP HANA SQL analyzer: Operator List
 Operator List view shows operators of the SQL statement execution

 Use to pinpoint specific operators of interest
 Includes details on execution time of operators, as well as accessed objects and output rows
 Useful to identify expensive operators and which objects they handled
SAP HANA SQL analyzer: Tables Used
 Provides a list of tables accessed during SQL statement execution

 Includes details on location of table, partition (if applicable), number of accesses and entries processed
 Useful to determine filter pushdown, tables accessed, and physical information of tables
 Useful to understand which tables are required during execution of a given SQL statement

SAP HANA SQL analyzer: Statement Statistics
 Only displayed if analyzing a SQL script

 Shows information about SQL statements involved during procedure execution
 Includes details on execution times, statement order, and more
 Useful to identify which part of the procedure has taken up the most time during execution and could be
a potential bottleneck

Thank you.
open@sap.com
Unit 3: Analyzing Workloads
Analyzing Workloads
SAP HANA workload analyzer – Web-based workload analysis tool
 Solution for analyzing database performance using Workload Analysis

thread samples and engine instrumentation
 Provides further insight into system workload and
includes flexible, chart-based analysis options
 Provides timeline analysis and filtering capabilities
 Drilldown to evaluate possible root cause of
performance issues either by analyzing real-time,
historical. or captured data Analyze
 Allows administrators to view the current state and

health of a system at a glance
Dimension (Context)
 Supports multi-dimensional performance analysis (Application, thread, Thread samples/
to evaluate existing dominant bottlenecks session, statement, instrumentation
transaction, pop, etc.) information on
workload in SAP Performance Measure
HANA (Elapsed time, CPU,
memory, # of executions,
network, wait time, etc.)
Analyzing Workloads
SAP HANA workload analyzer – Real-time data analysis
 Enables users to analyze data of system workload in real time

 Offers easy navigation using date picker functionality
 Provides details on system background jobs

Analyzing Workloads
SAP HANA workload analyzer – SQL statement timeline analysis
 Enables users to analyze data of system workload in real time

 Offers timeline-based analysis of system workload
 Enables users to flexibly switch hierarchy levels for easier navigation
 Includes further details on statement level

Analyzing Workloads
SAP HANA workload analyzer – Thread analysis
 Offers flexible analysis

capabilities by providing different
methods of visualization, such
as load graph overview, detail
and trend graphs
 Provides top n comparison and
details of different KPIs, such as
Thread State or Thread Types
 Includes filters and hierarchies
for easier navigation

Analyzing Workloads
SAP HANA workload analyzer – Instrumentation-based analysis
 Feature to analyze captured workloads

 Visualizes system load inside captured
workload, leverages identical tracing
framework as SAP HANA capture and
replay
 Offers insights into captured workloads.
Includes load graph visualization as well
as timeline view with application and
statement hierarchy, similar to sampling-
based workload analyzer

Thank you.
open@sap.com
Unit 4: Workload Capture and Replay
Workload Capture and Replay
General overview
 Capture real system workload in productive environments

 Preprocess and replay captured workload on target systems
4
 Analyze and compare runtimes or results
 Provides competitive replay and analysis for SAP HANA
database
 Helps ensure that landscape changes do not degrade
system performance 1
3
 Enables real simulation of workload without the use of other
3rd party tools
 Reduces manual effort for testing changes in customer
deployments
2

Process overview
Clients Replay Files Replayer
1 CAPTURE 2 PREPROCESS Connection via 3 REPLAY

Capture Reformat and SQLDBC Replay and analyze
incoming SQL reorder SQL workload in similar
statements statements execution order, with
similar concurrency
App Servers and load distribution
Capture Files Capture Files
Manual copy
of data
SAP HANA SAP HANA
Revision XXX DB Backup DB Backup Revision YYY
Manual backup Initialization of 4 ANALYZE

after starting test system
Production System capture Test System
Performance Management tile set
 The tile set includes one tile for capturing workload and one tile for preprocessing and replaying workload on
a target system
 Tiles provide overall status information about capture and replay totals as well as general status
 Other tiles include sampling-based and instrumentation-based workload analyzer
 Clicking a tile navigates to appropriate performance management tool

Capturing workload
 New captures can be configured

via UI
 Includes filters (such as Database
User, Statement Types, Application
Name, etc.) and different
configuration parameters

Preprocessing workload
 Preprocessing can be triggered via

the UI
 All capture files from one system
can be selected for preprocessing
 Status indicates if preprocessing
has already been completed, is
required, or is in progress

Replaying workload
 Replayer information and target

instance information need to be
provided
 Includes logon information, user
information, and various
parameters
 Multiple replayers can be selected
for improved scalability
 Filters can be defined to only
replay desired aspects of capture

Analyzing results
 Detailed report for result

analysis is available after
replay
 Includes differentiation
between deterministic
and non-deterministic
statements
 Compares result number
of rows as well as result
set hash
 Provides additional
details for each
statement

Analyzing runtimes
 Detailed report for runtime analysis is

available after replay
 Classifies statements into categories such
as slower, faster, comparable
 Compares different runtime averages and
differences for each statement
 Provides additional details for each
statement execution

Thank you.
open@sap.com
Unit 5: Analyzing Trace Files
Analyzing Trace Files
SAP HANA trace file viewer
 Web-based UI integrated into the SAP HANA Database Explorer

 Analyze system trace files in the event of problems with the SAP HANA database
– Each service of the SAP HANA database writes to its own trace file
– For SystemDB, they are stored in /usr/sap/<SID>/HDB<instance>/<host>/trace
– For tenants, they are stored in a subdirectory named DB_<database_name>
– There is also one single alert file for each service into which only trace messages of the highest priorities
are written
 Powerful function for searching trace files
 Readable formatting of trace files for simplified user consumption
 When an SAP HANA database is online, you must have either the CATALOG READ, DATA ADMIN, or
INIFILE ADMIN system privilege
 When an SAP HANA database is stopped or cannot be reached, use the SAP HANA cockpit for offline
administration to access trace files (requires operating system user credentials)

Different types of traces
Type Description
Database tracing  Collection of error messages or other output created by database processes
 Useful for single incident analysis or when tracing user-independent activities
SQL tracing  Logs SQL statements filtered by database/application user, table name, application name, or SQL statement
type
 A good starting point for understanding executed statements and their potential effect on the overall application
and system performance
User-specific tracing  Similar to database tracing, except information collected is limited to actions initiated by a specific database user
(via context name)
 Trace levels configured for components in these contexts override those configured in the database trace
End-to-end tracing  Triggered by applications outside of the SAP HANA database (“end-to-end-trace” is used as context in the trace
file name)
 Useful when investigating why a code path has failed, or if you want detailed tracing for performance analysis
Expensive statements  Records information about individual SQL statements whose execution time exceeded a configured threshold
tracing  Enable per-statement memory tracking to show the peak memory size used to execute expensive statements
Plan tracing  Collects SQL queries and their execution plans, executed in a given time frame

Step 1: Open the appropriate trace file
 Use “View trace and diagnostic files” link in

SAP HANA cockpit
 Explore the registered systems to find the
one you want to access
 Use the hierarchical navigation to either
access catalog or trace files
 Select desired database process you want
to analyze and examine its trace files

Step 2: Select the trace file to examine
 Select the desired trace file that

you wish to view
 Use CTRL+F to search the
content of the trace file Search field
 Exceptions can occur when
dealing with special trace files,
for example workload capture
files stored under the trace Available trace
files per process
directory (i.e. *.cpt files)
The file names follow the default naming convention:

<service>_<host>.<port_number>.<3_digit_fi
le_counter>.trc or
<service>_alert_<host>.trc

Trace configuration
 Requires TRACE ADMIN system privilege

 Each service has specific trace components that can
be set for that service
 Database, user-specific, and  SQL trace levels:
end-to-end trace levels:
– NONE – NORMAL
– FATAL – ERROR
– ERROR – ERROR_ROLLBACK
– WARNING – ALL
– INFO – ALL_WITH_RESULTS
– DEBUG

Best practices
 Monitor disk space that is used for diagnosis files and delete files that are no longer needed
 Configure trace file rotation to prevent them from growing indefinitely by limiting their size and number
– Requires system privilege INIFILE ADMIN
– Configure for all services: edit maxfile (default 10 files) and maxfilesize (default 10,000,000 bytes)
parameters in trace section of global.ini
– Configure for individual service: edit maxfile and maxfilesize parameters in trace section of config file
of the relevant service (create these if necessary)
– Rotation occurs in a round robin fashion
– Notify via alert checks 50 (number of diagnosis files) and 51 (size of diagnosis files)
 SQL trace files can impact database performance significantly, and they also consume storage space on
the disk

Deepen your knowledge
 Learning Journey: SAP HANA Administration & Operations

 HA200 SAP HANA 2.0 Installation and Administration
 HA215 SAP HANA – Monitoring & Performance Tuning
 HA240 Authorization, Security and Scenarios
 HA250 Migration to SAP HANA using DMO Migration
Get certified by SAP

Thank you.
open@sap.com

All SLIDES Hana Administration

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

All SLIDES Hana Administration

Enviado por

Direitos autorais:

Formatos disponíveis

Week 1: Basics and Tooling

Unit 1: Database Administration Tasks

System Exercises (optional):

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

▪ Learning Journey: SAP HANA Administration & Operations

Get certified by SAP

Peak database Essential database

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Databases Resource Utilization Performance

Tenant Databases CPU Transactions

Alerts Disk Statements

Services Network Table Usage

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Tenant Databases Alerts Services System Properties

Password Policy Encryption Auditing Certificates

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Provides execution details on

Identify the root cause of Workload Analysis

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Platform Lifecycle Management Application Lifecycle Management

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Web Client SQL/MDX Client Web Client

SAP Web Dispatcher

Name Server Index Server Index Server

Preprocessor Other Services Other Services

Data Volumes Disk Storage Log Volumes

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

• Performs compilation of stored Compile Server • Used by index server to analyze

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Script server Extended store server

Document store server Data provisioning server

XS Advanced runtime Streaming cluster

HDI server SAP HANA remote data sync

XS Classic server Accelerator for SAP ASE

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

▪ SAP HANA maintains its own memory pool to store

Database administrators need to monitor and

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Non-Native SAP HANA Native SAP HANA

▪ SAP Solution Manager ▪ SAP HANA cockpit

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

SAP Solution Manager SAP Landscape Management SAP IT Operations Analytics

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Native Tools for SAP HANA 1.0 Database Administration

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Native Tools for SAP HANA 2.0 Database Administration

SAP HANA 2.0 Cockpit SAP HANA Studio

Three main pieces:

The SAP HANA cockpit is installed as a HTTP/XML SQL client

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Cockpit manager UAA SAP HANA cockpit Database Explorer MTA

Info about systems in the enterprise

Processor Memory Hard Disk Operating Web Browser

For IBM PPC LE:

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Dedicated Hardware Shared Hardware

Server 1 Server 2 Server

Operating System Operating System Operating System

Storage Storage Storage

Support SAP HANA SAP HANA

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Default install configuration

Installation/upgrade log file created in /var/tmp