Dynamic Tiering Option Administration Guide en

Administration Guide
PUBLIC
SAP HANA dynamic tiering 1.0 SP 12

Document Version: 2.1 2016-10-18
SAP HANA Dynamic Tiering: Administration Guide
Content
Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1
SAP HANA Dynamic Tiering Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Dynamic Tiering for Tenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2
Authorization for Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Configure Access to Content in SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Accessing the SAP HANA Cockpit as the SYSTEM User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.3
Tools for Administration and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4
Open SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.5
Tile Catalog for SAP HANA Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
System Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1
Managing the Dynamic Tiering Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Verify that the Dynamic Tiering Service Is Installed and Running. . . . . . . . . . . . . . . . . . . . . . . . .17
View the Status of the Dynamic Tiering Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Stop or Restart the Dynamic Tiering Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Stop or Start the Dynamic Tiering Service Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring Dynamic Tiering Properties (INI Files). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2
Licensing for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.3
Managing Extended Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

The Delta Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Create Extended Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Remove Extended Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.4
Managing Space for Extended Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Types of Dbspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Add a Dbspace File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Enlarge a Dbspace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Drop a Dbspace File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Dbspace File Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.5
Managing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Extended Store Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Trigger a Merge on a Delta Enabled Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.6
Computing Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.7
Importing and Exporting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Extended Store Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Import Partial Rows to an Extended Store Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
2.8
Monitoring Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Monitoring Dynamic Tiering in the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
PUBLIC

Content
Monitoring Dynamic Tiering in the SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2.9
Backup and Recovery for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Backing Up SAP HANA Databases With Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Finding and Checking Backups for Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Recovering SAP HANA Databases with Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.10
Dynamic Tiering High Availability (Failover). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Change High Availability Group Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Manual Failover to Dynamic Tiering Standby Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Dynamic Tiering Automatic Failover with SAN Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Failover in a Same Host Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Security Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.1
Configure Private Internal Communication Using the Command-Line Interface. . . . . . . . . . . . . . . . 82
3.2
Configure Private Internal Communication Using the Graphical User Interface. . . . . . . . . . . . . . . . . 84
Using Dynamic Tiering with Multitenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.1
Verify Configuration of the SAP HANA Core System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Verify That Tenant Databases Exist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Verifying SAP HANA Cockpit Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.2
Adding the Dynamic Tiering Host to a Multitenant Database System. . . . . . . . . . . . . . . . . . . . . . . . 89
4.3
Prepare the Tenant Database Resources for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Prepare Resources Using SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Prepare Resources Using SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
4.4
Provision the Dynamic Tiering Service to a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
4.5
Failing Over with Multitenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.6
Import Dynamic Tiering Delivery Units to a New Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . .93
4.7
Create Extended Storage on the Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
4.8
Remove Dynamic Tiering from a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
4.9
Converting Multitenant Database Containers Using Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . .95

Import SAP HANA Delivery Units (DUs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.10
Using Multitenant Databases with Same Host Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
5.1
Tools and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Dynamic Tiering Administration User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Dynamic Tiering Stack File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Sample Query Plan Showing Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.2
Configuration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Cannot Create Extended Storage Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Cannot Communicate with SAP HANA Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Missing Features in SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.3
Operational Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Content
PUBLIC
Cannot Create Extended Store Table with Delta Enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Verifying Imported Delivery Units (DUs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Importing an Extended Table into HANA Without Dynamic Tiering Returns Error. . . . . . . . . . . . 105
Dynamic Tiering Operations Moving Large Amounts of Data Fail. . . . . . . . . . . . . . . . . . . . . . . 105
Out of Space Errors for Delta Dbspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Query Returns "You have run out of space in <DBSPACE_NAME> DBSpace" Error . . . . . . . . . . 106
Writing Date or Time Data to Extended Storage Violates Unique Constraint . . . . . . . . . . . . . . . 107
Backup Cannot Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Point-In-Time Recovery Fails When the Restore is Unable to Find a Log Backup on the Latest
Timeline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Point-in-Time Recovery Leaves Dynamic Tiering Service in Utility Mode. . . . . . . . . . . . . . . . . . 108
6
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
PUBLIC

Content
Getting Started
The SAP HANA Dynamic Tiering: Administration Guide describes tasks and concepts for managing disk-based
data in a HANA database system.
SAP HANA dynamic tiering is a native big data solution that adds smart, disk-based extended storage to your
SAP HANA database. Dynamic tiering enhances SAP HANA with large volume, warm data management
capability.
This guide provides the following information for dynamic tiering system administration:
Architecture and tools overview
System administration and monitoring procedures
Security administration requirements and procedures
Multitenant database configuration and management
Troubleshooting tools and tips
For more information about SAP HANA dynamic tiering installation, landscape, and security, see the SAP Help
Portal.
In this section:
SAP HANA Dynamic Tiering Architecture [page 6]
SAP HANA and SAP HANA dynamic tiering require separate dedicated hosts in a production
environment. You can only install SAP HANA and SAP HANA dynamic tiering on the same server in a
nonproduction environment.
Authorization for Administration Tasks [page 8]
Administration tasks in dynamic tiering require certain privileges and/or roles. These must be granted
to your database user or relevant role by a user administrator.
Tools for Administration and Monitoring [page 10]
Use the SAP HANA cockpit and the SAP HANA studio to administer and monitor dynamic tiering.
Open SAP HANA Cockpit [page 11]
Access the SAP HANA cockpit from a Web browser.
Tile Catalog for SAP HANA Dynamic Tiering [page 13]
The tile catalog defines the set of all tiles available in the SAP HANA. Within the main tile catalog, tiles
are grouped into sub-catalogs by functional area. The catalog Dynamic Tiering contains the tiles for
dynamic tiering administration and monitoring for a single database.
Related Information
SAP Help Portal

Getting Started
PUBLIC
1.1
SAP HANA Dynamic Tiering Architecture
SAP HANA and SAP HANA dynamic tiering require separate dedicated hosts in a production environment. You
can only install SAP HANA and SAP HANA dynamic tiering on the same server in a nonproduction
environment.
SAP HANA and the dynamic tiering host share a common database, comprised of regular, and extended
tables.
SAP HANA
Cockpit
SAP HANA
Studio
SAP HANA
Clients
Host A
Host B
Host C
Host D
SAP HANA
Server
Dynamic Tiering
ES Server
SAP HANA
Standby Server
Dynamic Tiering
Standby Server
Hot Store
(In-Memory
Tables)
Logs
Warm Store
(Extended
Tables)
Logs
Shared Resources Location

Figure 1: Components of SAP HANA Dynamic Tiering
The main dynamic tiering host is known as the worker. You can also install a second dynamic tiering host,
known as the standby, to provide failover functionality for high availability. A standby does not require a
separate SAP HANA dynamic tiering license.
The SAP HANA host and SAP HANA dynamic tiering worker communicate over a secure, encrypted internal
connection. For network and communication security information, see the SAP HANA Security Guide.
Use the SAP HANA client interfaces to manage and monitor dynamic tiering. Use SAP HANA cockpit to
monitor system information for the dynamic tiering host, including resource utilization, and table usage
statistics. Use the HANA studio for dynamic tiering administration tasks, including managing extended storage
and extended store tables. The OS process for the dynamic tiering host is hdbesserver, and the service
name is esserver.
To maximize native query performance, query optimizations ship the query operations to either the hot store
or extended storage. Query operations against extended storage data are pushed down to the dynamic tiering
worker, minimizing the load on the SAP HANA host.
In this section:
PUBLIC

Getting Started
Dynamic Tiering for Tenant Databases [page 7]

An SAP HANA system that supports multitenant database containers can have multiple tenant
databases. Each tenant database is associated with a maximum of one dynamic tiering worker/
standby pair.
Related Information
SAP HANA Security Guide
1.1.1 Dynamic Tiering for Tenant Databases

An SAP HANA system that supports multitenant database containers can have multiple tenant databases.
Each tenant database is associated with a maximum of one dynamic tiering worker/standby pair.
Conversely, the same dynamic tiering worker/standby pair cannot be associated with multiple databases.
For details about tenant database features, see Multitenant Database Containers in the SAP HANA
Administration Guide.
Figure 2: SAP HANA System with Dynamic Tiering for Tenant Databases

Getting Started
PUBLIC
Related Information
Using Dynamic Tiering with Multitenant Databases [page 86]
SAP HANA Administration Guide
1.2
Authorization for Administration Tasks
Administration tasks in dynamic tiering require certain privileges and/or roles. These must be granted to your
database user or relevant role by a user administrator.
For a complete list of authorizations by task, see Authorization for Basic Administration Tasks in the SAP HANA
Dynamic Tiering Administration Tasks

System administration tasks require system privileges.
Task
Required Authorization
Create, alter, or drop the extended storage configuration,

and stop the dynamic tiering service (esserver)
System privilege EXTENDED STORAGE ADMIN or SERVICE

ADMIN (to stop the dynamic tiering service)
System configuration tasks require system privileges.

Task
Required Authorization
Change the properties of an extended storage engine as de

fined in the parameters of the configuration file
esserver.ini.
System privilege EXTENDED STORAGE ADMIN or INIFILE

ADMIN
In this section:
Configure Access to Content in SAP HANA Cockpit [page 9]
Configure access to the SAP HANA cockpit by assigning roles to users.
Accessing the SAP HANA Cockpit as the SYSTEM User [page 10]
The SYSTEM user, by default, is not granted the required roles to access the SAP HANA cockpit and
manage roles and users.
Related Information
PUBLIC

Getting Started
1.2.1 Configure Access to Content in SAP HANA Cockpit

Configure access to the SAP HANA cockpit by assigning roles to users.
Prerequisites
Requires the sap.hana.admin.roles::Administrator role.
Procedure
1. In the SAP HANA cockpit, select the Manage Users and Roles tile.
2. Grant the required roles to users.
Note
These roles pertain specifically to managing SAP HANA dynamic tiering. See the SAP HANA
Administration Guide for additional roles pertaining to managing an SAP HANA system.
Role
sap.hana.admin.roles::Monitoring
Purpose
Required for access to SAP HANA cockpit.
Required to configure the SAP HANA Database Ad
Allows viewing only of SAP HANA Database Adminis
ministration catalog.
tration tiles.
sap.hana.admin.roles::Administrator
Allows administration of SAP HANA Database Ad

ministration tiles. For example, start and stop serv
ices and configure alerts.
Includes the role of

sap.hana.admin.roles::Monitoring.
sap.hana.tiering.roles::Monitoring
Required to configure the SAP HANA dynamic tiering

catalog.
Allows viewing only of SAP HANA dynamic tiering

catalog tiles.
sap.hana.tiering.roles::Administrator
Required to manage SAP HANA dynamic tiering cat

alog.
Includes the role of

sap.hana.tiering.roles::Monitoring and the
EXTENDED STORAGE ADMIN system privilege.

Getting Started
PUBLIC
Related Information
1.2.2 Accessing the SAP HANA Cockpit as the SYSTEM User

The SYSTEM user, by default, is not granted the required roles to access the SAP HANA cockpit and manage
roles and users.
When the SYSTEM user logs on, the SAP HANA system checks for the required roles. If they are missing, the
system prompts to automatically grant them before proceeding.
Note
This behavior only applies to the SYSTEM user. The required roles to manage users must be manually
granted to all other users.
1.3
Tools for Administration and Monitoring
Use the SAP HANA cockpit and the SAP HANA studio to administer and monitor dynamic tiering.
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. Use the SAP HANA studio to administer and monitor storage on disk
and extended tables. For an overview, see the SAP HANA Administration Guide.
The SAP HANA Cockpit

The SAP HANA cockpit is an SAP Fiori Launchpad site that provides you with a single point of access to a
range of Web-based applications for the administration of SAP HANA. Use the SAP HANA cockpit to
administer and monitor storage on disk.
Note
Before you begin other tasks in Related Links, see "Configure Access to Content in the SAP HANA Cockpit."
10
PUBLIC

Getting Started
Related Information
Configuring Dynamic Tiering Properties (INI Files) [page 22]
Managing Extended Storage [page 38]
Managing Space for Extended Storage [page 44]
Extended Store Tables [page 51]
Monitoring Dynamic Tiering in the SAP HANA Studio [page 66]
Monitoring Dynamic Tiering in the SAP HANA Cockpit [page 66]
Configure Access to Content in SAP HANA Cockpit [page 9]
1.4
Open SAP HANA Cockpit
Access the SAP HANA cockpit from a Web browser.
Prerequisites
You have the role sap.hana.admin.roles::Monitoring or
sap.hana.admin.roles::Administrator.
These roles allow you to open the cockpit and access the tiles in the SAP HANA Database Administration
catalog.
If you're opening the cockpit on the system database of a multiple-container, you also need the role
sap.hana.admin.cockpit.roles::SysDBAdmin so that you can access the tiles in the SAP HANA
System Administration catalog.
You can grant roles using the Assign Roles app of the SAP HANA cockpit. For more information, see
Assign Roles to a User in the SAP HANA Administration Guide.
Note
After database creation, you will have to log on for first time as the user SYSTEM. In this case, the
required roles will be assigned automatically. For more information, see Roles Granted to Database User
SYSTEM.
You have the role sap.hana.tiering.roles::Monitoring or
sap.hana.tiering.roles::Administrator, required to access the SAP HANA dynamic tiering
catalog tiles.
Your Web browser supports the SAPUI5 library sap.m (for example, Internet Explorer 9).
For more information about SAPUI5 browser support, see SAP Note 1716423 and the Product Availability
Matrix (PAM) for SAPUI5.
If you're integrating the SAP HANA cockpit into a single sign-on (SSO) environment, you have specified
and configured the methods for user authentication in the SAP HANA XS Administration Tool.

Getting Started
PUBLIC
11
Here, create a runtime configuration for the following applications:

sap.hana.admin
sap.uis
For more information about how to do this, see Maintaining the SAP HANA XS Classic Model Run Time in
the SAP HANA Administration Guide.
If you're opening the SAP HANA cockpit for a tenant database, you have configured the internal SAP Web
Dispatcher so that it can dispatch HTTP requests coming into the system to the correct database on the
basis of DNS alias hostnames. Every tenant database needs an alias. For more information, see Configure
HTTP Access to Multitenant Database Containers in the SAP HANA Administration Guide.
Procedure
1. Enter the SAP HANA cockpit URL in your browser.
The URL depends on the type of system to which you connect.
Option
Description
Single-container system
http://<host>:<port>/sap/hana/admin/cockpit
System database of a multiplecontainer system
http://<host>:<port>/sap/hana/admin/cockpit
Tenant database
http://<alias_DNS_name_of_tenant_DB>:<port>/sap/hana/
admin/cockpit
2. If required, enter your database user name and password.
Results
The SAP HANA cockpit opens. The SAP HANA Database Administration group is available by default,
displaying all the tiles from the corresponding tile catalog.
Next Steps
Customize the homepage of the SAP HANA cockpit. See Customize the Homepage of SAP HANA Cockpit
in SAP HANA Administration Guide.
If necessary, configure access to further tile catalogs and groups. See Tile Catalogs for Administration and
Monitoring in SAP HANA Administration Guide.
Related Information
12
PUBLIC

Getting Started
1.5
Tile Catalog for SAP HANA Dynamic Tiering
The tile catalog defines the set of all tiles available in the SAP HANA. Within the main tile catalog, tiles are
grouped into sub-catalogs by functional area. The catalog Dynamic Tiering contains the tiles for dynamic
tiering administration and monitoring for a single database.
The table below shows each tile in the Dynamic Tiering tile catalog along with a description of the tile's
functionality. To view the Dynamic Tiering tile catalog, you need the role
sap.hana.tiering.roles::Monitoring. Tile functionality may require additional roles.
Figure 3: Tile Catalog SAP HANA Dynamic Tiering
Tile
Description
Additional Requirements
Creates or deletes extended storage. If The Dynamic Tiering Configuration

wizard requires the
extended storage exists, shows the
sap.hana.tiering.roles::Admin
name of the host where the extended
istrator role to create or delete
storage service is running, and the
extended storage.
initial size and unit of measure of the
extended storage.
Shows the name, type (readwrite or

read only), online status, and size of
each user dbspace. Opens dialogs
where you can add, enlarge, or drop
Operations on dbspace files require

the
istrator role.
dbspace files.

each system dbspace. Opens dialogs
where you can enlarge or drop

the
istrator role.
dbspace files. You cannot add files to a

system dbspace.

Getting Started
PUBLIC
13
Tile
Description
Shows details about connections,

active transactions, and remote
statements. Opens the Dynamic
Tiering Server Configuration dialog
where you can change configuration
properties of the dynamic tiering
Operations on the Dynamic Tiering

Connections dialogs require the
sap.hana.tiering.roles::Monit
oring role. Changing dynamic tiering
server properties requires the
istrator role.
service to address connection issues.

each temporary dbspace. Opens
dialogs where you can add, enlarge, or

the
istrator role.
drop dbspace files.
Shows the default and system settings

of configuration properties for the
extended storage server. Opens the
Edit Server Configuration dialog,
Changing dynamic tiering server

properties requires the
istrator role.
where you can change or reset

parameters that control configuration
properties.

each delta dbspace. Opens dialogs
where you can add, enlarge and drop

the
istrator role.
dbspace files.
14
PUBLIC

Getting Started
Tile
Description
Shows used and available memory by

host, by type, and by memory
component. Opens the Dynamic
Tiering Server Configuration dialog
where you can reallocate memory.
Viewing of memory usage requires no

additional roles. Reallocation of
memory requires the
istrator role.
Opens online help for dynamic tiering

tasks that you can perform with the
No additional roles are required to view

documentation.
SAP HANA cockpit.

Getting Started
PUBLIC
15
System Administration
As a database administrator, you are responsible for operational tasks related to the administration,
monitoring, and maintenance of your SAP HANA systems with dynamic tiering.
In this section:
Managing the Dynamic Tiering Service [page 16]
The dynamic tiering service is the component that provides warm storage capability to an SAP HANA
system.
Licensing for Dynamic Tiering [page 38]
Only one SAP HANA dynamic tiering license is allowed per SAP HANA system.
Managing Extended Storage [page 38]
Each SAP HANA database is associated with a single extended store.
Managing Space for Extended Storage [page 44]
Extended storage is divided into units called dbspaces.
Managing Tables [page 51]
SAP HANA dynamic tiering supports extended store tables.
Computing Statistics [page 62]
Compute statistics for columns to help HANA optimize queries on extended tables.
Importing and Exporting Data [page 63]
You can move data between extended store tables (warm data) and HANA tables (hot data). You can
also move data into extended store tables from an external source.
Monitoring Dynamic Tiering [page 66]
Monitor resource usage and performance to identify patterns, forecast requirements, and correct
problems.
Backup and Recovery for Dynamic Tiering [page 69]
Backup and recovery of an SAP HANA system with dynamic tiering installed differs from the same
operations on an SAP HANA system without dynamic tiering.
Dynamic Tiering High Availability (Failover) [page 77]
SAP HANA Dynamic Tiering supports both automatic and manual failover.
2.1
Managing the Dynamic Tiering Service
The dynamic tiering service is the component that provides warm storage capability to an SAP HANA system.
The OS process for the dynamic tiering host is hdbesserver, and the service name is esserver.
In this section:
Verify that the Dynamic Tiering Service Is Installed and Running [page 17]
16
PUBLIC

Adding the SAP HANA dynamic tiering host creates and starts the dynamic tiering service. Verify that
the service is installed and running either through HANA studio or using the HDB info command on the
host.
View the Status of the Dynamic Tiering Service [page 18]
Use the M_SERVICES view to display the status for the dynamic tiering service on the dynamic tiering
host.
Stop or Restart the Dynamic Tiering Service [page 19]
When the installation of SAP HANA dynamic tiering completes, the dynamic tiering service
(esserver) is running. To manually stop the service for any reason, such as to change a configuration
parameter, use the SAP HANA cockpit or SAP HANA studio, or execute SQL through the SQL console.
Stop or Start the Dynamic Tiering Service Manually [page 21]
You can stop the dynamic tiering service (esserver), and prevent the auto-restart mechanism from
restarting the service. When stopped, the service can only be restarted manually.
INI files contain properties for configuring SAP HANA dynamic tiering.
2.1.1 Verify that the Dynamic Tiering Service Is Installed and

Running
Adding the SAP HANA dynamic tiering host creates and starts the dynamic tiering service. Verify that the
service is installed and running either through HANA studio or using the HDB info command on the host.
Verify Using HANA Studio

Procedure
1. In the SAP HANA studio Administration console, right-click the database in the Systems panel, select
Configuration and Monitoring
Open Administration , then select the Landscape tab.
2. Verify that the status of the esserver on the dynamic tiering host is active (green).
Results
If the esserver service is inactive (red), restart the service.
If the service is not listed, the dynamic tiering worker is not installed. See the SAP HANA Dynamic Tiering:
Installation and Update Guide for steps on adding the dynamic tiering host.

PUBLIC
17
Verify Using the Dynamic Tiering Host

Procedure
1. Log on to the SAP HANA dynamic tiering host as the <sid>adm user, where <sid> is the SAP HANA
system ID.
2. Type the following to display a list of services that are running:
HDB info
If hdbesserver appears on the list, the dynamic tiering service is running. In this example, RH1 is the
<sid> and 00 is the instance number:
rh1adm
13151 13107 0.0 737604 34036
tcpip{port=30012} -hes
\_ hdbesserver -n esRH100 -x
3. Type exit to close the information request.
Results
If the service is not listed, but you know the dynamic tiering host is installed, restart the service.
If you are unsure whether the dynamic tiering host is installed, use HANA studio to verify the service is
installed and running.
2.1.2 View the Status of the Dynamic Tiering Service

Use the M_SERVICES view to display the status for the dynamic tiering service on the dynamic tiering host.
On the SAP HANA dynamic tiering host, the coordinator type of the dynamic tiering service (esserver) can
have one of the following statuses:
Coordinator Type Status
Description
None
Dynamic tiering service is running, but extended storage is not created.
Master
Dynamic tiering service is running and extended storage is created.
Standby
The dynamic tiering host is configured as a standby host.
To view the coordinator type status, execute the SQL command:

SELECT * from M_SERVICES
In this example, abchana1369.corp is the dynamic tiering worker host and abchana1368.corp the standby
host. The status of NONE on the worker host indicates extended storage has not been created.
HOST,PORT,SERVICE_NAME,PROCESS_ID,DETAIL,ACTIVE_STATUS,SQL_PORT,COORDINATOR_TYPE
"abchana1369.corp",30012,"esserver",19453,"","YES",0,"NONE"
"abchana1368.corp",30013,"esserver",19456,"standby","YES",0,"STANDBY"
18
PUBLIC

Once extended storage is created, the coordinator type status changes from NONE to MASTER.
HOST,PORT,SERVICE_NAME,PROCESS_ID,DETAIL,ACTIVE_STATUS,SQL_PORT,COORDINATOR_TYPE
"abchana1369.corp",30012,"esserver",19453,"master","YES",0,"MASTER"
"abchana1368.corp",30013,"esserver",19456,"standby","YES",0,"STANDBY"
A status of MASTER indicates that the installation and configuration of SAP HANA dynamic tiering is complete
and successful.
2.1.3 Stop or Restart the Dynamic Tiering Service

When the installation of SAP HANA dynamic tiering completes, the dynamic tiering service (esserver) is
running. To manually stop the service for any reason, such as to change a configuration parameter, use the
SAP HANA cockpit or SAP HANA studio, or execute SQL through the SQL console.
Context
Note
The SAP HANA auto-restart feature supports high availability. If an SAP HANA service is disabled by failure
or intentional intervention, this auto-restart function detects the failure and restarts the stopped service
process.
Stop the Dynamic Tiering Service with the SAP HANA

Cockpit
Prerequisites
You have the sap.hana.admin.roles::Administrator role.
Procedure
1. In the SAP HANA cockpit, click the Database Status tile.
2. Highlight the esserver service and click Stop Service.
3. Click Yes to confirm. A success message appears.

PUBLIC
19
Stop the Dynamic Tiering Service with the SAP HANA Studio
Prerequisites
You have the system privilege EXTENDED STORAGE ADMIN or SERVICE ADMIN.
Procedure
1. In the SAP HANA studio Administration console, right-click the database in the Systems panel, select
Configuration and Monitoring
Open Administration , then select the Landscape tab.
2. Right-click the dynamic tiering service (esserver) and choose the required option:
Option
Description
Stop...
The service is stopped normally and then typically restarted.
Kill...
The service is stopped immediately and then typically restarted.
Stop the Dynamic Tiering Service using SQL

Prerequisites
You have the system privilege EXTENDED STORAGE ADMIN or SERVICE ADMIN.
Procedure
1. Open the SQL console.
2. Execute the following ALTER SYSTEM STOP SERVICE statement:
ALTER SYSTEM STOP SERVICE <host_port>
[IMMEDIATE [WITH COREFILE]]
Note
If you stop the dynamic tiering service using the ALTER SYSTEM STOP SERVICE statement, no crash
dump file is created.
Example
This example stops the service without waiting for regular shutdown:
ALTER SYSTEM STOP SERVICE
20
PUBLIC

'hdb1.company1.com:30303' IMMEDIATE
For complete syntax and requirements, see the SQL Reference for SAP HANA Options section in the SAP
HANA SQL and System Views Reference Guide.
Related Information
SAP HANA SQL and System Views Reference
2.1.4 Stop or Start the Dynamic Tiering Service Manually

You can stop the dynamic tiering service (esserver), and prevent the auto-restart mechanism from
restarting the service. When stopped, the service can only be restarted manually.
Stop the Dynamic Tiering Service

Procedure
1. Log on to the SAP HANA dynamic tiering host as the system administrator (<sid>adm), where <sid> is
the SAP HANA system ID.
2. Type:
HDB stop
The service begins to shut down. A message appears when the process is complete.
Start the Dynamic Tiering Service

Procedure
1. Log on to the SAP HANA dynamic tiering host as the system administrator (<sid>adm), where <sid> is
the SAP HANA system ID.
2. Type:
HDB start
The service begins to start up. A message appears when the process is complete.

PUBLIC
21
2.1.5 Configuring Dynamic Tiering Properties (INI Files)

INI files contain properties for configuring SAP HANA dynamic tiering.
Configuration files are separated into sections that bundle properties of the same category. Properties can be
configured at different levels or layers depending on the type of system: single or multitenant database. The
following layers apply to the extended storage service:
Layer
Description
Default
The default value for the property.
System
The system-specific value for the property.

If a system-specific value is not configured for a property, the default value applies.
Database
Used only on multitenant database systems, this layer configures properties for tenant da
tabases.
SAP HANA systems include an additional layer, host, which does not apply to SAP HANA dynamic tiering.
In a single database system, change properties at the system layer. On a multitenant database, change
properties at the individual database layer.
In this section:
Dynamic Tiering Service Properties (esserver.ini) [page 22]
The esserver.ini file stores extended storage configuration properties.
Dynamic Tiering Tenant Database Properties (global.ini) [page 33]
The customizable_functionalities section of the global.ini file contains parameters that allow you to
enable and disable certain dynamic tiering operations in a tenant database.
Related Information
SAP HANA SQL and System Views Reference Guide
2.1.5.1
Dynamic Tiering Service Properties (esserver.ini)
The esserver.ini file stores extended storage configuration properties.

In a single database environment, configuration properties are changed at the system layer. In a multitenant
database system, you change them at the system or database layer. Configuration properties changed at the
system layer apply to all tenants unless individually overridden at the database level.
Installing dynamic tiering automatically adjusts startup section parameters to new values based on the
resources available on the dynamic tiering host.
To change dynamic tiering configuration properties, you need the EXTENDED STORAGE ADMIN system
privilege.
22
PUBLIC

Table 1: Startup Section Properties

Name
Description
Min/Max Value
Default Value
catalog_cache
Amount of memory initially reserved for caching the

dynamic tiering catalog.
0/-
32000000 bytes
checkpoint_interval
Maximum interval between checkpoints.
0/-
60 minutes
delta_memory_mb
Amount of memory available to store delta enabled

extended tables.
0/-
2048MB
load_memory_mb
Maximum amount of memory extended storage can

request from the operating system for temporary
use.
0/-
2048MB
main_cache_mb
Amount of memory to be used for caching dynamic

tiering database objects.
0/-
1024MB
max_concurrent_con Maximum number of concurrent connections that

nections
the dynamic tiering service accepts.
1 - 1001
50
max_concur
rent_queries
Maximum number of concurrent queries allowed by

the server.
0/-
32
num_partition_buf
fer_cache
Number of main and temp buffer cache partitions.

Must be a power of 2, otherwise value rounded to
the nearest power of two to a maximum of 64.
0 - 256
None. Value is de
termined at run
time based on the
number of CPUs,
and is not user visi
ble.
num_threads
Maximum number of threads used for dynamic

tiering.
4 - 4096
600
0/-
256
temporary_cache_mb Amount of memory to be used as cache for tempo

rary objects during dynamic tiering operations.
Table 2: Trace Section Properties
Name
Description
Min/Max Value
Default Value
maxfiles
Specifies the number of archives of the old message

log maintained by the server. Only applies if maxfile
size is not 0.
0-64 (inclusive)
10
maxfilesize
Limits the maximum size of the message log.
0 - 2047 (inclusive),
in MB
10000000
Table 3: Zrlog Section Properties

Name
Description
Values
Default Value
filesize_limit
Create a new log file and rename the original log file
when the original log file reaches specified size.
Depends on space
available
maxfiles
Specify number of request log file copies to retain.

Only takes effect if filesize_limit is also specified.
Depends on space
available

PUBLIC
23
Name
Description
Values
Default Value
statement_type
Enable request logging of operations. Separate mul

tiple values with , or +.
SQL | HOSTVARS |
PLAN | PROCE
DURES | TRIGGERS |
OTHER | BLOCKS |
REPLACE | ALL |
NONE
NONE
tracefile
Redirect request logging information to a file sepa

rate from the regular log file.
filename
trace/
es_requestlog
_$HOST_$
{PORT}_$
{COUNT:3}.log
In this section:
Change an esserver.ini Property - Single Database [page 24]
The esserver.ini file defines configuration parameters for dynamic tiering services.
Change an esserver.ini Property - Tenant Database [page 27]
The esserver.ini file defines configuration parameters for dynamic tiering services. Changes can
be made at the system level or to individual tenants once provisioned.
Reset an esserver.ini Property - Single Database [page 30]
You can restore changed configuration parameters in the esserver.ini file to default values.
Reset an esserver.ini Property - Tenant Database [page 32]
You can restore changed configuration parameters in the esserver.ini file for a tenant database to
default values.
2.1.5.1.1
Change an esserver.ini Property - Single

Database
The esserver.ini file defines configuration parameters for dynamic tiering services.
Change an esserver.ini Property in the SAP HANA Cockpit

Prerequisites
You have the role sap.hana.tiering.roles:Administrator.
24
PUBLIC

Procedure
1. In the SAP HANA cockpit, click the Dynamic Tiering Server Configuration tile.
2. Click Edit. You do not need to select the parameter first.
3. Click the pencil icon for the property being changed.
4. Enter the new value and click Save.
Next Steps
If necessary, restart the system.
Change an esserver.ini Property in the SAP HANA Studio

Prerequisites
You have either the EXTENDED STORAGE ADMIN or INIFILE ADMIN system privilege.
Context
The value configured for the system applies to the whole system, including all hosts of multi-host systems.
Procedure
1. In the SAP HANA studio Administration console, double-click the system in the Systems panel, and then
choose the Configuration tab.
A list of all configuration files appears.
2. Expand the esserver.ini file.
All the sections of the file are listed.
3. Expand the required section.
All the parameters of the section are listed. For each parameter, you can see the default value.
4. In the context menu of the configuration parameter that you want to change, choose Change...
5. Enter the new value in the Change Configuration Value dialog.

PUBLIC
25
Results
If you entered a new value for a parameter at system level, it is displayed in the System column with a
green circle (
).
Next Steps
Change an esserver.ini Property Using SQL

Prerequisites
You have the system privilege EXTENDED STORAGE ADMIN or INIFILE ADMIN.
Procedure
1. In a SQL console, connect to the system to be modified.
2. Execute the ALTER SYSTEM ALTER CONFIGURATION statement.
ALTER SYSTEM ALTER CONFIGURATION ('esserver.ini','SYSTEM')
SET ('<parameter_key_value_list>') = '<parameter_key_value>' [WITH
RECONFIGURE]
Note
For complete syntax and requirements, see ALTER SYSTEM ALTER CONFIGURATION Statement
[Dynamic Tiering] in the SAP HANA SQL and System Views Reference guide.
What
How
Change the setting of main_cache_mb.
ALTER SYSTEM ALTER CONFIGURATION

('esserver.ini','SYSTEM') SET ('startup',
'main_cache_mb')='1024'
Related Information
26
PUBLIC

2.1.5.1.2
Change an esserver.ini Property - Tenant

Database
The esserver.ini file defines configuration parameters for dynamic tiering services. Changes can be made
at the system level or to individual tenants once provisioned.
Change an esserver.ini Property in the SAP HANA Cockpit

Prerequisites
Procedure
1. In the SAP HANA cockpit, click the Dynamic Tiering Server Configuration tile.
2. Click Edit. You do not need to select the parameter first.
3. Click the pencil icon for the property being changed.
4. Enter the new value and click Save.
Next Steps
Change an esserver.ini Property in the SAP HANA Studio

Prerequisites
Property Level
Tenant database
System
Privileges Required
DATABASE ADMIN
EXTENDED STORAGE ADMIN
INIFILE ADMIN
INIFILE ADMIN

PUBLIC
27
Context
Properties changed at the system level apply to the whole system, including all hosts of multi-host systems,
and become the default value for any tenant databases without a value defined at the database level.
Properties changed at the database level apply to the specified tenant only, overriding the system value.
Procedure
1. In the SAP HANA studio Administration console, do one of:
Property Level to Change
Select
System
Double-click SYSTEMDB in the Systems panel.
Database
Double-click the tenant database in the Systems panel.
2. Click the Configuration tab.

All the sections of the file are listed.
5. In the context menu of the configuration parameter that you want to change, choose Change...
6. Enter the new value in the Change Configuration Value dialog.
Note
The disabled icon (
) indicates that the property cannot be set at that level.
Results
If you entered a new value for a parameter, it is displayed in the column with a green circle (
).
When connected to the SYSTEMDB, a gray rhombus ( ) appears in the Database column if the
parameter can be entered at the database level. You can show information about a specific database by
selecting the database from the Database filter. This is only possible in the SYSTEMDB.
When connect to the tenant database, the value in the System column does not refer to the value defined
at the system level in the SYSTEMDB and does not override that value.
Next Steps
28
PUBLIC

Change an esserver.ini Property Using SQL

Prerequisites
Procedure
1. In a SQL console, connect to the SYSTEMDB, regardless of the level where the property is changed.
2. Execute the ALTER SYSTEM ALTER CONFIGURATION statement for the desired level:
Level
Syntax
System
ALTER SYSTEM ALTER CONFIGURATION ('esserver.ini, 'SYSTEM')

SET ('<parameter_key_value_list>' = '<parameter_key_value>'
[WITH RECONFIGURE]
Database
ALTER SYSTEM ALTER CONFIGURATION ('esserver.ini, 'DATABASE',

'<database_name>')
SET ('<parameter_key_value_list>') =
'<parameter_key_value>' [WITH RECONFIGURE]
Note
This example changes the setting of the main_cache_mb in the startup section.
Level
How
System

('esserver.ini','SYSTEM') SET ('startup',
'main_cache_mb')='1024'
Database

('esserver.ini','DATABASE','db1') SET
('startup', 'main_cache_mb')='1024'
Related Information

PUBLIC
29
2.1.5.1.3
Reset an esserver.ini Property - Single Database
You can restore changed configuration parameters in the esserver.ini file to default values.
Reset an esserver.ini Property with the SAP HANA Studio

Prerequisites
Procedure
1. In the SAP HANA studio Administration console, double-click the system in the Systems panel, and then
All the sections of the configuration file are listed.
All the parameters in the section are listed.
4. To delete a user-defined value and restore the default value, you can choose one of the following methods:
Procedure
Result
Delete with automatic reset:
The user-defined value(s) are cleared and the default

value(s) are re-applied.
1.
In the context menu of the configuration parameter,

choose Delete.
The Delete Configuration Value dialog box appears.
2. Choose the layer whose user-defined values you

want to delete.
3. Choose Delete.
Manually restore default:
1.

choose Change...
Note
If you added a new parameter to a section, Delete de
letes the parameter.
The user-defined value is cleared and the default value is
re-applied.
The Change Configuration Value dialog box ap

pears.
2. For the required layers, choose Restore Default.
3. Choose Save.
30
PUBLIC

Reset an esserver.ini Property Using SQL

Prerequisites
Procedure
2. Execute the ALTER SYSTEM ALTER CONFIGURATION statement with the UNSET clause.
ALTER SYSTEM ALTER CONFIGURATION ('esserver.ini', 'SYSTEM')
UNSET ('<parameter_key_value_list>') [WITH RECONFIGURE]
Note
What
How
Reset the main_cache_mb parameter.
ALTER SYSTEM ALTER CONFIGURATION (esserver.ini,

SYSTEM) UNSET (startup, main_cache_mb)
Related Information

PUBLIC
31
2.1.5.1.4
Reset an esserver.ini Property - Tenant Database
You can restore changed configuration parameters in the esserver.ini file for a tenant database to default
values.
Prerequisites
Property Level
Tenant database
System
Privileges Required
DATABASE ADMIN
INIFILE ADMIN
INIFILE ADMIN
Context
Changes to properties in the global.ini file for a tenant database are made in the SYSTEMDB, applied to
the tenant database. Properties changed at the system level of the SYSTEMDB apply to the whole system, and
becomes a default value for any tenant databases that do not have a value defined for the corresponding
property at the database level.
Reset an esserver.ini Property with the SAP HANA Studio

Procedure
Property Level to Reset
Select
System level
Double-click SYSTEMDB in the Systems panel.
Database
Double-click the tenant database in the Systems panel.
2. Click the Configuration tab.

All the sections of the configuration file are listed.
All the parameters in the section are listed. You can identify parameters that have user-defined values at
system level and/or database level with a green circle (
32
PUBLIC
) and gray rhombus (
) respectively.

Procedure
Result

1.

choose Delete.

want to delete.
3. Choose Delete.
1.

choose Change...
Note

pears.
2. For the required layers, choose Restore Default, or if
you want to reset all visible layers, choose Restore
Default for All.
3. Choose Save.
Related Information
2.1.5.2
Dynamic Tiering Tenant Database Properties

(global.ini)
The customizable_functionalities section of the global.ini file contains parameters that allow you to enable
and disable certain dynamic tiering operations in a tenant database.
You change these properties at the system level in the SYSTEMDB, but apply them to the database layer.
Customizable_functionalities properties are enabled by default. Refer to the view
M_CUSTOMIZABLE_FUNCTIONALITIES (SYS) of the SYSTEMDB to determine a feature's status.
Property
Default
Operation
dynamic_tiering
true
Changing the setting to false disables all dynamic

tiering operations.
dynamic_tiering.create_extended_storage
true
Changing the setting to false disables CREATE EX

TENDED STORAGE operations.
dynamic_tiering.drop_extended_storage
true
Changing the setting to false disables DROP EX

dynamic_tiering.alter_extended_storage
true
Changing the setting to false disables ALTER EX


PUBLIC
33
Property
Default
Operation
dynamic_tiering.alter_table_type
true
Alter table type operation to convert SAP HANA tables

to extended tables or extended tables to SAP HANA
tables.
dynamic_tiering.bulk_insert_optimization
true
Bulk insert optimization that executes large inserts

into extended tables using a load statement.
dynamic_tiering.query_plan_relocation
true
Query relocation operation that moves data between

SAP HANA and dynamic tiering for optimal query per
formance.
In this section:
Change a global.ini Property - Tenant Database [page 34]
The global.ini file contains the customizable_functionalities section that allows you to enable and
disable some dynamic tiering functions on a tenant database.
Reset a global.ini Property - Tenant Database [page 37]
You can restore changed configuration parameters in the global.ini file for the
customizable_functionalities section in a tenant database to default values.
2.1.5.2.1
Change a global.ini Property - Tenant Database
The global.ini file contains the customizable_functionalities section that allows you to enable and disable
some dynamic tiering functions on a tenant database.
Prerequisites
Property Level
Tenant database
System
Privileges Required
DATABASE ADMIN
INIFILE ADMIN
INIFILE ADMIN
Context
Change global.ini file properties for a tenant database in the SYSTEMDB and applies. Properties changed
at the system level apply to the whole system, including all hosts of multi-host systems, and become the
default value for any tenant databases without a value defined at the database level. Properties changed at the
database level apply to the specified tenant only, overriding the system value.
34
PUBLIC

Change a global.ini Property in the SAP HANA Studio

Procedure
1. In the SAP HANA studio Administration console, double-click SYSTEMDB in the Systems panel, and then
2. Expand global.ini customizable_functionalities .
3. Right-click the property that corresponds to the feature you want to disable and choose Change...
4. Select the relevant tenant database(s) and enter true to enable or false to disable as the new value.
Note
If you want to disable the feature on all tenant databases (including any that will be created in the
future), enter false as the system value.
Results
If you entered a new value for a parameter at system level, it is displayed in the System column with a
green circle (
).
A gray rhombus ( ) appears in the Database column if the parameter can be entered at the database
level. You can show information about a specific database by selecting the database from the Database
filter. This is only possible in the SYSTEMDB.
Next Steps
Change a global.ini Property Using SQL

Procedure
1. In a SQL console, connect to the SYSTEMDB.
2. Execute the ALTER SYSTEM ALTER CONFIGURATION statement for the appropriate layer.

PUBLIC
35
Level
How
System
ALTER SYSTEM ALTER CONFIGURATION ('global.ini','SYSTEM') SET

('customizable_functionalities',
'<parameter_name>')='<parameter_value>'
Database

('global.ini','DATABASE','<database_name>') SET
('customizable_functionalities',
'<parameter_name>')='<parameter_value>'
Note
This example disables the ability to drop extended storage on the tenant database db1.
ALTER SYSTEM ALTER CONFIGURATION ('global.ini','DATABASE','db1')
SET ('customizable_functionalities',
'dynamic_tiering.drop_extended_storage')='false'
This example disables the ability to convert an existing HANA table to an extended store table for all
tenants in the system.
ALTER SYSTEM ALTER CONFIGURATION ('global.ini','SYSTEM')
SET ('customizable_functionalities',
'dynamic_tiering.alter_table_type')='false'
Related Information
36
PUBLIC

2.1.5.2.2
Reset a global.ini Property - Tenant Database
You can restore changed configuration parameters in the global.ini file for the
customizable_functionalities section in a tenant database to default values.
Prerequisites
Property Level
Tenant database
System
Privileges Required
DATABASE ADMIN
INIFILE ADMIN
INIFILE ADMIN
Context
Changes to properties in the global.ini file for a tenant database are made in the SYSTEMDB, applied to
the tenant database. Properties changed at the system level of the SYSTEMDB apply to the whole system, and
becomes a default value for any tenant databases that do not have a value defined for the corresponding
property at the database level. Changes applied to a tenant database override the value defined at the system
level.
Reset a global.ini Property with the SAP HANA Studio

Procedure
1. In the SAP HANA studio Administration console, double-click SYSTEMDB in the Systems panel, and then
2. Expand global.ini customizable_functionalities .
All the parameters in the section are listed. You can identify parameters that have user-defined values at
system level and/or database level with a green circle (
) and gray rhombus (
) respectively.

PUBLIC
37
Procedure
Result

1.

choose Delete.
Note

want to delete.
3. Choose Delete.
1.

choose Change...


pears.
2. For the required layers, choose Restore Default, or if
you want to reset all visible layers, choose Restore
Default for All.
3. Choose Save.
Related Information
2.2
Licensing for Dynamic Tiering
Only one SAP HANA dynamic tiering license is allowed per SAP HANA system.
For dynamic tiering on a multitenant database container SAP HANA system, all tenant databases share the
single license.
Dynamic tiering is licensed by the amount of data in extended storage.
2.3
Managing Extended Storage
Each SAP HANA database is associated with a single extended store.

The table schema is part of the SAP HANA database catalog.
In this section:
The Delta Store [page 39]
The delta store is a write-optimized, in-memory store that works with the existing, read-optimized,
extended storage. It uses row-level versioning (RLV) to allow more than one user to modify the same
38
PUBLIC

table concurrently. Delta stores use row-level versioning to allow concurrent table changes by multiple
users, eliminating waits for transaction locks.
Create Extended Storage [page 40]
Create extended storage on disk for warm data in order to free up space in the in-memory database for
hot data.
Remove Extended Storage [page 42]
Deleting extended storage stops the extended storage service and removes extended storage from the
topology.
2.3.1 The Delta Store

The delta store is a write-optimized, in-memory store that works with the existing, read-optimized, extended
storage. It uses row-level versioning (RLV) to allow more than one user to modify the same table concurrently.
Delta stores use row-level versioning to allow concurrent table changes by multiple users, eliminating waits for
transaction locks.
Concurrent Table Writes RLV allows concurrent, low-latency modifications to extended store tables. This
means that multiple connections can modify the same table, as long as they adding or modifying different
rows.
Blocking and Locking A transaction locks a table, blocking all other connections from writing to the table
while the transaction is open. RLV utilizes multi-version concurrency control (MVCC), for version
management at the row level. Connections can wait for locks (on either the table or a single row),
eliminating the need for retry.
Hybrid Storage The delta store combines with the existing on-disk extended storage to provide a hybrid
storage mechanism that combines the extreme performance and low latency of the in-memory store with
the robust high performance and scalability of on-disk storage. Immediate data modifications (load table /
insert / update / delete) occur within the write-optimized delta store. The delta store is periodically
merged into the read-optimized extended storage through asynchronous data transfer. Thus, most data in
an extended store table can be accessed via indexes, and provides expected dynamic tiering query
performance.
You create the delta store when you create extended storage. Once extended storage is created, you cannot
change the delta setting.

PUBLIC
39
2.3.2 Create Extended Storage

Create extended storage on disk for warm data in order to free up space in the in-memory database for hot
data.
Create Extended Storage with the SAP HANA Cockpit

Prerequisites
Note
If you create extended storage, you cannot enable data volume encryption in the SAP HANA database.
Procedure
1. In the SAP HANA cockpit, click the Dynamic Tiering Configuration tile.
2. Specify the following:
Option
Description
Host
Name of the host on which the dynamic tiering service is running.
Note
The host name must exactly match the host name that appears in the M_SERVICES view.
Size
Initial size and unit of measure of extended storage. You can later increase the size by adding
dbspace files in dbspaces.
Delta
Create a delta dbspace in extended storage to support row level versioning tables. The delta
option supports multiple concurrent writes. The default is OFF. Once extended storage is cre
ated, you cannot change the delta setting.
3. Click Create.
The elapsed time to create the extended storage depends on the size specified.
4. Perform a full backup of the SAP HANA database system. See Backing up SAP HANA Databases With
Dynamic Tiering.
40
PUBLIC

Results
A message indicates the status (success or failure) of the process. A new volume, extendedstorage,
appears in the SAP HANA studio.
Create Extended Storage Using SQL

Prerequisites
You have the system privilege EXTENDED STORAGE ADMIN.
Note
If you create extended storage, you cannot enable data volume encryption in the SAP HANA database.
Procedure
2. Execute the CREATE EXTENDED STORAGE statement, which has this syntax:
CREATE EXTENDED STORAGE [ AT [LOCATION] <host-string> ]
SIZE <size-value> {KB|MB|GB|TB} [{ENABLE|DISABLE} DELTA]
The host name specified must exactly match the host name that appears in the M_SERVICES view.
If you omit the optional AT <host-name> clause, the system uses the first available dynamic tiering host
where esserver is running in utility mode.
This example creates 10 GB of extended storage on host test.wdf.sap.corp with row level versioning
enabled.
Example
CREATE EXTENDED STORAGE AT 'test.wdf.sap.corp' size 10 GB ENABLE DELTA
Note
For complete syntax and requirements, see CREATE EXTENDED STORAGE in the SQL Reference for
SAP HANA Options section in the SAP HANA SQL and System Views Reference.
3. Perform a full backup of the SAP HANA database system. See Backing up SAP HANA Databases With
Dynamic Tiering.

PUBLIC
41
Related Information
Add a Dbspace File [page 45]
Backing Up SAP HANA Databases With Dynamic Tiering [page 70]
2.3.3 Remove Extended Storage

Deleting extended storage stops the extended storage service and removes extended storage from the
topology.
Remove Extended Storage in the SAP HANA Cockpit

Prerequisites
Context
Caution
This process deletes all data within extended storage.
Procedure
1. In the SAP HANA cockpit, click the Dynamic Tiering Configuration tile.
2. Click Delete.
3. Choose one of the following:
42
Option
Description
Cascade
Drops the extended storage and dependent objects.
PUBLIC

Option
Description
Restrict
Drops the extended storage only when dependent objects do not exist. If Restrict is selected
and a dependent object exists, an error message appears.
4. Click Yes to complete removal.
Remove Extended Storage Using SQL

Prerequisites
Procedure
1. Open the SQL.
2. Execute the DROP EXTENDED STORAGE statement.
DROP EXTENDED STORAGE [CASCADE | RESTRICT]
The default option, RESTRICT, returns an error if dependent objects exist.
This statement drops the storage and all associated objects.
Example
DROP EXTENDED STORAGE [CASCADE]
Note
For complete syntax and requirements, see DROP EXTENDED STORAGE in the SQL Reference for SAP
HANA Options section in the SAP HANA SQL and System Views Reference.
Related Information

PUBLIC
43
2.4
Managing Space for Extended Storage
Extended storage is divided into units called dbspaces.

A dbspace is a logical name for a container of files or raw partitions.
When dynamic tiering is configured, the default dashboard for the SAP HANA cockpit contains a tile for each
dbspace. Click any dbspace tile to display details for the associated dbspace.
In this section:
Types of Dbspaces [page 44]
Dbspaces are specialized to manage specific types of data.
Add one or more files to a specified dbspace to allow extended storage growth. Use the SAP HANA
cockpit or execute SQL through the SQL console.
Enlarge a Dbspace File [page 47]
Increase the dbspace size by using some or all of a file's reserved size. Use the SAP HANA cockpit or
execute SQL through the SQL console.
Drop a Dbspace File [page 49]
Drop a dbspace file that is no longer needed. Use the SAP HANA cockpit or execute SQL through the
SQL console.
Dbspace File Details [page 50]
The dbspaces tile displays the options for a dbspace file.
2.4.1 Types of Dbspaces

Dbspaces are specialized to manage specific types of data.
Configuring dynamic tiering creates an ES_USER, an ES_SYSTEM, and an ES_TEMP dbspace. If you enable
delta, an ES_DELTA dbspace is also created.
Dbspace Name
Type
Data Stored
ES_SYSTEM
MAIN
Database structures including One or more

rollforward and rollback data
for each committed transac
tion and each active check
pointed transaction, backup
metadata, and database space
and identity metadata.
ES_USER
MAIN
User data in database objects

such as tables and indexes,
and table metadata.
44
PUBLIC
Files Contained by
Dbspace
One or more

Dbspace Name
Type
Data Stored
Files Contained by
Dbspace
ES_DELTA
RLV
Real-time in-memory data

from row-level versioning
(RLV)-enabled tables. An
ES_DELTA dbspace supports
multiple concurrent writes.
One
ES_TEMP
TEMPORARY
One or more
Set of 1 to n temporary
dbspace files that defines a
single temporary dbspace. Siz
ing depends on workload, but
a rule of thumb is 10 times the
temporary cache setting.
Dbspace Sizing
Given a size X, in MB, the CREATE EXTENDED STORAGE command creates initial dbspaces in the sizes below.
Table 4: Dbspace Sizing Formula
Dbspace
Formula
ES_USER
size=X
ES_DELTA
size=max( min(X, iqrlvmem) , 512 )
ES_SYSTEM
size=max( 10%( ES_USER ) , 128 )
ES_TEMP
size=max( 10%(ES_USER +ES_DELTA) , 16 )
See also SAP Note 2140959
2.4.2 Add a Dbspace File

Add one or more files to a specified dbspace to allow extended storage growth. Use the SAP HANA cockpit or
execute SQL through the SQL console.
Add a Dbspace File with the SAP HANA Cockpit

Prerequisites

PUBLIC
45
Procedure
1. In the SAP HANA cockpit, click the tile for the dbspace where you want to add a file.
2. Select a dbspace and click Edit.
3. On the Edit Dbspace screen, click the Add icon (+).
4. On the New Dbspace File Dialog enter dbspace options.
5. Click Create.
Results
A status message displays.
Add a Dbspace File Using SQL

Prerequisites
Procedure
2. Execute the ALTER EXTENDED STORAGE ALTER DBSPACE statement with the ADD FILE clause.
ALTER EXTENDED STORAGE ALTER DBSPACE <dbspace_name>
ADD FILE <logical_file_name> ['<file_path>']
SIZE {KB|MB|GB|TB}
The <dbspace_name> must be ES_SYSTEM, ES_USER, or ES_TEMP.
This example adds dbspace files f2 and f3 on ES_USER. File f3 has 50MB reserved, and can be enlarged by
that amount.
Example
ALTER EXTENDED STORAGE ALTER DBSPACE dbsp1 ADD FILE f1 'f1_file' SIZE 100
MB;
ALTER EXTENDED STORAGE ALTER DBSPACE ES_USER ADD FILE f2 'f2_file.db' 200
MB, FILE f3 'f3_file.dat' SIZE 100 MB RESERVE 50 MB;
46
PUBLIC

Note
For complete syntax and requirements, see ALTER EXTENDED STORAGE Statement [Dynamic Tiering]
in the SQL Reference for SAP HANA Options section in the SAP HANA SQL and System Views Reference.
Related Information
2.4.3 Enlarge a Dbspace File

Increase the dbspace size by using some or all of a file's reserved size. Use the SAP HANA cockpit or execute
SQL through the SQL console.
Enlarge a Dbspace File with the SAP HANA Cockpit

Prerequisites
The reserved size for the file is sufficient.
Procedure
1. In the SAP HANA cockpit, click the tile for the dbspace where you want to add a file.
2. Select a dbspace and click Edit.
3. On the Edit Dbspace screen, click the Add icon (+).
4. On the New Dbspace File Dialog enter dbspace options.
5. Click Create.
Results

PUBLIC
47
Enlarge a Dbspace File Using SQL

Prerequisites
Procedure
2. Execute the ALTER EXTENDED STORAGE ALTER DBSPACE statement.
ALTER FILE <logical_filename>
ADD <add_file_size> {KB|MB|GB|TB}
This example adds 10 MB on to file f4 on ES_USER.
Example
ALTER EXTENDED STORAGE ALTER DBSPACE ES_USER ALTER FILE f4 ADD 10 MB;
Note
Related Information
48
PUBLIC

2.4.4 Drop a Dbspace File

Drop a dbspace file that is no longer needed. Use the SAP HANA cockpit or execute SQL through the SQL
console.
Drop a Dbspace File with the SAP HANA Cockpit

Prerequisites
The file is empty.
You are the only user connected to extended storage.
Procedure
1. In the SAP HANA cockpit, click the tile for the desired dbspace.
2. Select a dbspace from the list of Dbspaces.
3. In the Dbspace Files list, verify that Is Drop Allowed contains TRUE and click Edit.
4. On the Edit Dbspace page, click the Delete icon (circled X).
5. On the Delete Dbspace File page, click OK.
Results
Drop a Dbspace File Using SQL

Prerequisites

PUBLIC
49
Procedure
2. Execute the ALTER EXTENDED STORAGE ALTER DBSPACE statement with the DROP FILE clause.
DROP FILE <logical_file_name>
This example drops dbspace file f1 from ES_TEMP and files f2, f3, and f4 from ES_USER.
Example
ALTER EXTENDED STORAGE ALTER DBSPACE ES_TEMP DROP FILE f1;
ALTER EXTENDED STORAGE ALTER DBSPACE ES_USER DROP FILE f2, f3, f4;
Note
Related Information
2.4.5 Dbspace File Details

The dbspaces tile displays the options for a dbspace file.
Specify the options in the New Dbspace File dialog.
Option
Description
Dbspace Name
Name of the dbspace to which you are adding a file. You can add files to MAIN, TEMPORARY, and
RLV dbspaces.
Dbspace Logical File

Name
The logical file name and physical file path are required for each dbspace file and must be unique.
You may add a file to a read-only dbspace, but the dbspace remains read-only.
Dbspace File Path
Enter a relative path.
Raw Device
Specifies a raw partition. SAP HANA dynamic tiering automatically sets size to the maximum raw
partition size. Each operating system has its own format for raw device names.
Dbspace File Size
Extends the size of the file. The default unit is MB. Do not specify a file size for raw devices.
50
PUBLIC

Option
Description
Reserve Size
Applies to UFS files only, not raw partitions. The amount of space to reserve for increasing the
dbspace file size in the future. Specify a reserve size so that you can quickly enlarge dbspace files
when needed.
2.5
Managing Tables
SAP HANA dynamic tiering supports extended store tables.

Follow the guidelines in this section to create and manage these tables.
In this section:
Extended tables reside in extended storage in dynamic tiering.
Trigger a Merge on a Delta Enabled Table [page 61]
On a delta-enabled table, trigger a merge of data from the delta dbspace to the user dbspace.
2.5.1 Extended Store Tables

Extended tables reside in extended storage in dynamic tiering.
You can create, modify, and remove extended store tables. You can also convert existing SAP HANA tables to
extended store tables or vice versa.
In this section:
Extended Store Table Limitations [page 52]
Some limitations affect extended store tables.
Extended Store Table Supported Data Types [page 53]
The supported data types of an extended store table differ slightly from a regular SAP HANA column
store table.
Choose Column Tables for Dynamic Tiering [page 54]
Monitor table operations to identify where you can improve performance and reduce memory
utilization. Large in-memory tables that are accessed infrequently are good candidates for the SAP
HANA dynamic tiering option. Note that tables moved into dynamic tiering disappear from table
analysis displays.
Convert HANA Tables to Extended Store Tables Using the SAP HANA Cockpit [page 55]
To move data to warm storage, convert appropriate column tables into extended store tables.
Manage Extended Store Tables Using SQL [page 56]
Use SQL statements to create, modify, and remove extended store tables in dynamic tiering, and
convert existing HANA tables to extended store tables or vice versa.
Manage Extended Tables in the SAP HANA Studio [page 58]

PUBLIC
51
Use the SAP HANA studio graphical interface to create, alter, convert, and drop extended tables.
2.5.1.1
Extended Store Table Limitations
Some limitations affect extended store tables.

Before you can drop a schema, you must drop all extended store tables.
User names and table names are case insensitive in extended storage, but case sensitive in SAP HANA
memory store. Remember that SAP HANA schema names are treated as case insensitive when they qualify an
extended store table name. For example, creating tables named "FundPerf"."ORIG_YEAR" and
"FUNDPERF"."ORIG_YEAR" returns the error SAP DBTech JDBC: [403]: internal error: Unable to
create table extension in Extended Storage: [SAP][ODBC Driver]Item 'ORIG_YEAR'
already exists.
Extended tables do not support:
Primary keys (or secondary indexes) composed of multiple columns where the total key length (sum of all
column sizes) is not greater than 5300 bytes.
Primary keys (or secondary indexes) composed of multiple columns of type NVARCHAR/NCHAR where at
least one column has a length greater than 1765 bytes.
Columns with data type TEXT.
SQL statements that create or alter SAP HANA extended tables do not support these clauses:
<fuzzy_search_index>
<fuzzy_search_mode>
<schema_flexibility_option>
<persistent_merge_option>
<delta_log_option>
<trigger_option>
<referential_constraints_definition>
within <column_definition>, GENERATED ALWAYS AS and FOREIGN KEY parameters
within <column_definition>, the following data types and functions are not supported:
CURRENT_UTCDATE
CURRENT_UTCTIME
CURRENT_UTCTIMESTAMP
within <using_extended_storage_clause>, ENABLE | DISABLE DELTA if the table being converted to
extended store table is a CLOB, BLOB, or NCLOB data type
Before you can drop a schema, you must drop all extended tables. Use the M_VOLUMES monitoring view
to check for extended tables:
SELECT DISTINCT object_name from SYS.TOPOLOGY_INFORMATION_
WHERE schema_name = 'schemaName' AND volume_id IN
(SELECT volume_id FROM SYS.M_VOLUMES WHERE service_name = 'esserver';
52
PUBLIC

2.5.1.2
Extended Store Table Supported Data Types
The supported data types of an extended store table differ slightly from a regular SAP HANA column store
table.
Datatype
Supported
Remarks
DATE
YES
Domain and formats are compatible.
Note
NOTE: Extended store tables do not support the empty string
as a valid value.
TIME
YES*
SECONDDATE
YES
TIMESTAMP
YES*
Domain is compatible.
*Extended store tables do not support format HH12:MI[:SS]

[AM|PM]
Domain and formats are compatible.
*Domain is not compatible.

Column store tables support 7 digit fractions for a second.
Extended store tables support 6 digits fractions for second.
TINYINT
YES
SMALLINT
YES
INTEGER
YES
BIGINT
YES
SMALLDECIMAL
YES*
DECIMAL
YES*
The domain is different.
Extended store tables treat SMALLDECIMAL as fixed precision

DECIMAL(32,16).
Column store tables can represent values for which precision

varies from 1-16 and scale from -369 to 368.
Domain is different.
Extended store tables map to precision = 68 and scale = 34.
Column store table precision can vary from 1-34 and scale can
vary from -6111 to 6176
DECIMAL(p,s)
YES
REAL
YES
DOUBLE
YES
Domains are same for column store and extended store tables.
VARCHAR
YES
Domains are same for column store and extended store tables. VAR
CHAR(n) where n from 1 to 5000.
NVARCHAR
YES*
Since NVARCHAR is not natively supported by extended storage, it

maps NVARCHAR(n) to VARCHAR(3n).
ALPHANUM
YES*
Since ALPHANUM is not natively supported by extended storage,

dynamic tiering maps ALPHANUM to VARCHAR, Results will be dif
ferent if predicates or sorting done on ALPHANUM columns.

Extended store tables allow precision from 1 to 38 and scale from 0

to p.
PUBLIC
53
Datatype
Supported
SHORTTEXT
NO
VARBINARY
YES
BLOB
YES*
CLOB
YES*
NCLOB
YES*
Remarks
The domain is same for column store and extended store tables.
There are certain DML and query operations that do not support
LOB columns > 32K Characters.
TEXT
NO
ARRAY
NO
2.5.1.3
Choose Column Tables for Dynamic Tiering
Monitor table operations to identify where you can improve performance and reduce memory utilization. Large
in-memory tables that are accessed infrequently are good candidates for the SAP HANA dynamic tiering
option. Note that tables moved into dynamic tiering disappear from table analysis displays.
Prerequisites
You have the role sap.hana.admin.roles::Monitoring.
The User Tables tile is visible on the homepage of the SAP HANA cockpit by default. If it is not visible, you
can add it from the tile catalog. For more information, see Customizing the Homepage of SAP HANA
Cockpit in the SAP HANA Administration Guide.
Context
The User Tables app shows the comparative memory utilization by host and the number of high and medium
priority alerts.
54
PUBLIC

Procedure
1. Open the User Tables app by clicking the tile of the same name on the homepage of the SAP HANA
cockpit.
You see the status of the top column tables in the system by usage.
2. To filter tables shown, adjust the Total Access/Size/Display values and click Search. Click Reset to
remove filters.
For the best display, select up to 50 tables. Two options for table analysis are available:
For table format display, choose
For graphical format display, choose
show usage per column table.
(Show table history as table).

(Show table history as graph). Mouse over a bubble to
Related Information
2.5.1.4
Convert HANA Tables to Extended Store Tables

Using the SAP HANA Cockpit
To move data to warm storage, convert appropriate column tables into extended store tables.
Prerequisites
You have the role sap.hana.admin.roles::Monitor.
The SAP HANA User Tables tile is visible on the homepage of the SAP HANA cockpit. This tile is visible by
default, but if not, you can add it from the tile catalog. See Customizing the Homepage of SAP HANA
Cockpit in the SAP HANA Administration Guide.
You have analyzed usage history to identify large in-memory tables that are accessed infrequently, which
are candidates for warm storage. See Monitoring Tables in the SAP HANA Administration Guide.
Context
The User Tables application in the HANA Cockpit catalog lets you make a selected table into an extended
store table.

PUBLIC
55
Procedure
1. Open the User Tables app by clicking the tile of the same name on the homepage of the SAP HANA
cockpit.
The Column Tables display shows the status of the top 50 column tables in the system by usage.
2. Select one or more tables from the Column Tables display.
3. Click the Make Extended button.
The Delta option supports multiple concurrent writes (RLV tables).
4. Choose an option on the Confirm Make Extended screen and click Yes.
After confirmation, the selected tables no longer display in the User Tables app.
Related Information
2.5.1.5
Manage Extended Store Tables Using SQL
Use SQL statements to create, modify, and remove extended store tables in dynamic tiering, and convert
existing HANA tables to extended store tables or vice versa.
Prerequisites
The extended store exists.
Requires the DATA ADMIN system privilege to manage a table not owned by self.
Context
Syntax details cited below are in the SQL Reference for SAP HANA Options section in the SAP HANA SQL and
System Views Reference.
Procedure
56
PUBLIC

2. Enter the appropriate statement for your task.

Task
Syntax
Create
Convert an existing HANA

table to an extended store
table
See Also
CREATE TABLE <table_name>

(<table_element>, ...)
<use_extended_storage_clause>
CREATE TABLE Statement (Ex
ALTER TABLE <table_name>

<using_extended_storage_clause>
ALTER TABLE Statement (Ex
tended Store Table) [Dynamic

Tiering]

Tiering] Syntax 2
Note
Review Extended Store
Table Limitations before
proceeding. Conversion
fails on HANA tables
created with clauses not
supported in extended
store tables.
Convert an extended store

table to a HANA database
table

NOT USING EXTENDED STORAGE
Enable/Disable delta on an
existing extended store ta
ble

<using_extended_storage_clause>

Tiering] Syntax 2
Tiering] Syntax 2
Note
Review Extended Store
Table Limitations before
proceeding. Enabling
delta fails on a con
verted HANA table that
contains data types not
supported in extended
store tables.
Modify
Delete

[<add_column_clause>]
[<drop_column_clause>]
[<alter_column_clause>]
[<add_constraint_clause>]
[<drop_primary_key_clause>]
[<drop_constraint_clause>]
[<using_extended_storage_clause>]
DROP TABLE <table_name>

[<drop_option>]
DROP TABLE Statement [Dy


Tiering] Syntax 1
namic Tiering]
PUBLIC
57
Task
Syntax
Rename
See Also
RENAME TABLE Statement {Dy
RENAME <current_table_name> TO
<new_table_name>
namic Tiering}
Related Information
2.5.1.6
Manage Extended Tables in the SAP HANA Studio
Use the SAP HANA studio graphical interface to create, alter, convert, and drop extended tables.
In this section:
Create an Extended Store Table [page 58]
Use the SAP HANA studio graphical interface to create extended store tables.
Enable/Disable Delta on an Existing Extended Store Table [page 59]
Use the SAP HANA studio graphical interface to enable or disable delta on existing extended store
tables. Enabling delta facilitates faster inserts.
Convert a HANA or Extended Store Table [page 60]
Use the SAP HANA studio graphical interface to convert an existing HANA table to an extended store
table and vice versa. All data in the table is preserved during conversion.
Alter or Delete an Extended Store Table [page 61]
Use the SAP HANA studio graphical interface to alter and delete extended store tables.
2.5.1.6.1
Create an Extended Store Table
Use the SAP HANA studio graphical interface to create extended store tables.
Prerequisites
The extended store exists.
58
PUBLIC

Context
You cannot enable delta when creating an extended store table. You must first create a HANA table and then
convert it to an extended store table with DELTA enabled.
Procedure
1. In the Systems view, open the catalog, and navigate to the schema to contain the new table.
2. Right-click the Tables entry and choose New Table.
3. Enter a name for the new table and select the schema from the Schema dropdown.
4. Do one of:
Option
Description
Create an extended store table with delta disabled
Select Extended from the Type dropdown.
Create a delta enabled extended store table
Select Column Store from the Type dropdown.
5. Choose the Column tab and enter the table parameters.

6. Click the + sign to add additional columns and click F8 to execute.
7. To enable delta on the new table, see Enable/Disable Delta on an Existing Extended Store Table.
Related Information
Enable/Disable Delta on an Existing Extended Store Table [page 59]
2.5.1.6.2
Enable/Disable Delta on an Existing Extended

Store Table
Use the SAP HANA studio graphical interface to enable or disable delta on existing extended store tables.
Enabling delta facilitates faster inserts.
Context
Note
Review Extended Store Table Limitations before proceeding. Enabling delta fails on a converted HANA table
that contains data types not supported in extended tables.

PUBLIC
59
Procedure
1. In the Systems view, open the catalog and schema, and navigate to the table in to be changed.
2. Expand Tables and right-click the table to change.
3. Choose Do Not Use Extended Storage.
4. Click Yes to confirm.
5. Right-click the table again and choose Use Extended Storage.
6. Select Enabled or Disabled from the Use Delta dropdown.
7. Click Move.
2.5.1.6.3
Convert a HANA or Extended Store Table
Use the SAP HANA studio graphical interface to convert an existing HANA table to an extended store table and
vice versa. All data in the table is preserved during conversion.
Context
Note
Review Extended Store Table Limitations before proceeding. Conversion fails on HANA tables created with
clauses not supported in extended tables.
Procedure
1. In the Systems view, open the catalog and schema, and navigate to the table in to be converted.
2. Right-click the table and do one of:
Option
60
Description
Convert to extended store table
1. Choose Use Extended Storage

2. To enable delta, if applicable, choose Enabled from the Use Delta dropdown.
3. Click Move.
Convert to HANA table
1. Choose Do Not Use Extended Storage

2. Click Yes to confirm conversion.
PUBLIC

2.5.1.6.4
Alter or Delete an Extended Store Table
Use the SAP HANA studio graphical interface to alter and delete extended store tables.
Alter an Extended Store Table

Procedure
1. In the Systems view, open the catalog and schema, then navigate to the table in to be altered.
2. Right-click the table to and choose Open Definition.
The table definition appears.
3. Right-click in the definition and choose Edit.
4. Modify the table as needed.
5. Click F8 to execute.
Delete an Extended Store Table

Procedure
1. In the Systems view, open the catalog and schema, then navigate to the table in to be deleted.
2. Right-click the table and choose Delete.
3. Adjust the deletion parameters, if needed, and click OK.
2.5.2 Trigger a Merge on a Delta Enabled Table

On a delta-enabled table, trigger a merge of data from the delta dbspace to the user dbspace.
Prerequisites
The specified table is delta-enabled.

PUBLIC
61
Procedure
2. Execute this MERGE DELTA command:
MERGE DELTA OF '<table_name>'
2.6
Computing Statistics
Compute statistics for columns to help HANA optimize queries on extended tables.
Like virtual tables, extended tables require explicit creation of statistics. In general, you should create
statistics on columns involved in joins, group by clauses, and equality or range predicates.
SAP HANA dynamic tiering supports the CREATE and DROP STATISTICS statements described in the SQL
Reference for SAP HANA Options section in the SAP HANA SQL and System Views Reference, with these
restrictions:
You can create two types of statistics: statistics that affect the whole table, or those that apply per
column. RECORD COUNT applies to the entire table. SIMPLE and HISTOGRAM are created per column.
You can only have one type of statistic on a table. If you create RECORD COUNT statistics then you can't
create per-column statistics. If you create per-column statistics, you can create SIMPLE on some columns
and HISTOGRAM on others. If you don't specify the column names, the statement creates per-column
statistics of the specified type on all columns.
The ALL statistics type is not supported for extended tables.
Example
Columns L_SHIPDATE, L_DISCOUNT, and L_QUANTITY in extended table LINEITEM are involved in range
predicates in this query:
SELECT SUM(L_EXTENDEDPRICE * L_DISCOUNT) AS REVENUE
FROM
COMPANY.LINEITEM
WHERE
L_SHIPDATE >= TO_DATE ('1994-01-01')
AND L_SHIPDATE < ADD_MONTHS(TO_DATE ('1994-01-01'),12)
AND L_DISCOUNT BETWEEN ROUND((0.06 - 0.01), 2) AND ROUND((0.06 +
0.01), 2)
AND L_QUANTITY < 24;
To optimize the query, create simple statistics on the columns used in the query predicates.
CREATE STATISTICS ON COMPANY.LINEITEM(L_SHIPDATE, L_DISCOUNT, L_QUANTITY) TYPE
SIMPLE;
This creates statistics of type SIMPLE on each of the three columns.
62
PUBLIC

Example
This query benefits from histogram statistics:
SELECT TOP 10
L_ORDERKEY,
SUM(L_EXTENDEDPRICE * (1 - L_DISCOUNT)) AS REVENUE,
O_ORDERDATE
FROM
COMPANY.CUSTOMER,
COMPANY.ORDERS,
COMPANY.LINEITEM
WHERE
C_MKTSEGMENT = 'BUILDING'
AND C_CUSTKEY = O_CUSTKEY
AND L_ORDERKEY = O_ORDERKEY
AND O_ORDERDATE < TO_DATE ('1995-03-15')
AND L_SHIPDATE > TO_DATE ('1995-03-15')
GROUP BY
L_ORDERKEY,
O_ORDERDATE
ORDER BY
REVENUE DESC,
O_ORDERDATE
To optimize the query, create statistics on the columns used in the query predicates:
CREATE STATISTICS ON COMPANY.CUSTOMER(C_MKTSEGMENT, C_CUSTKEY) TYPE HISTOGRAM;
CREATE STATISTICS ON COMPANY.ORDERS(O_CUSTKEY,O_ORDERKEY,O_ORDERDATE) TYPE
HISTOGRAM;
CREATE STATISTICS ON COMPANY.LINEITEM(L_ORDERKEY, L_SHIPDATE) TYPE HISTOGRAM;
This creates statistics of type HISTOGRAM on each of the seven columns.
Related Information
2.7
Importing and Exporting Data
You can move data between extended store tables (warm data) and HANA tables (hot data). You can also
move data into extended store tables from an external source.
In this section:
You can move data between extended store tables (warm data) and HANA tables (hot data). You can
also move data into extended store tables from an external source.
Import Partial Rows to an Extended Store Table [page 66]
A CSV file may contain partial rows.

PUBLIC
63
2.7.1 Extended Store Tables

You can move data between extended store tables (warm data) and HANA tables (hot data). You can also
move data into extended store tables from an external source.
In this section:
Import Data into an Extended Store Table [page 64]
Import catalog objects previously exported from dynamic tiering or external data from a CSV file.
Export Data from an Extended Store Table [page 65]
Export tables, views, column views, synonyms, sequences, or procedures in CSV format.
Limitations on Extended Store Table Import/Export [page 65]
Some clauses are not supported when importing and exporting data for extended store tables.
2.7.1.1
Import Data into an Extended Store Table
Import catalog objects previously exported from dynamic tiering or external data from a CSV file.
Execute all SQL statements through an SQL interface or custom applications. See the SQL Reference for SAP
HANA Options section in the SAP HANA SQL and System Views Reference for complete syntax.
IMPORT
Import catalog objects (tables, views, synonyms, sequences, procedures) that have previously been exported
from dynamic tiering.
Sample Code
IMPORT "testsch"."*" AS CSV FROM '/tmp' WITH REPLACE THREADS 10
IMPORT FROM
Import external data from a CSV file into an existing extended store table.
Sample Code
IMPORT FROM CSV FILE 'bigfile.csv' INTO ext_table1
See SAP Note 2050807
tables.
64
PUBLIC
for behavior differences when loading data from SAP HANA and extended store

Related Information
2.7.1.2
Export Data from an Extended Store Table
Export tables, views, column views, synonyms, sequences, or procedures in CSV format.
Execute all SQL statements through an SQL interface or custom applications. See the SQL Reference for SAP
HANA Options section in the SAP HANA SQL and System Views Reference for complete syntax.
BINARY format is not supported for extended store tables.
Sample Code
EXPORT MY_SCHEMA.tab1 AS CSV INTO '/tmp' WITH REPLACE SCRAMBLE THREADS 10
2.7.1.3
Limitations on Extended Store Table Import/Export
Some clauses are not supported when importing and exporting data for extended store tables.
These clauses are not supported when exporting an extended store table using the EXPORT statement.
<export_import_format> - BINARY format is ignored; CSV format is used instead.
SCRAMBLE BY <scramble_seed>
STRIP
These clauses are not supported when importing data previously exported from an extended store table using
the IMPORT statement.
AT LOCATION <indexserver_host_port>
FAILED ON INVALID DATA
IGNORE IDENTICAL
BINARY
These clauses are not supported when importing external data to an extended store table using CSV format
using the IMPORT FROM statement.
THREADS <number_of_threads>
BATCH <number_of_records_of_each_commit>
TABLE LOCK
FAILED ON INVALID DATA
File locations when importing and exporting data must be on a shared file system available to both SAP HANA
and dynamic tiering.
tables.
for behavior differences when loading data from SAP HANA and extended store

PUBLIC
65
2.7.2 Import Partial Rows to an Extended Store Table

A CSV file may contain partial rows.
A partial row exists when the number of columns in the data is less than the number of rows specified in the
IMPORT statement's column specification. During import, any field missing from the partial row is assigned a
NULL value unless the field is not nullable. An error message appears and no data is imported when a missing
field is not nullable.
2.8
Monitoring Dynamic Tiering
Monitor resource usage and performance to identify patterns, forecast requirements, and correct problems.
In this section:
Monitoring Dynamic Tiering in the SAP HANA Studio [page 66]
To optimize performance, monitor the status of the dynamic tiering service in the SAP HANA studio.
Monitoring Dynamic Tiering in the SAP HANA Cockpit [page 66]
The SAP HANA cockpit provides several monitoring applications through a Web browser.
2.8.1 Monitoring Dynamic Tiering in the SAP HANA Studio

To optimize performance, monitor the status of the dynamic tiering service in the SAP HANA studio.
Monitor status in the Administration editor of the dynamic tiering service:
General status displays on the Overview tab.
Details about memory use are on the Landscape tab. To view details for a dynamic tiering service, locate
the appropriate host on a row where the Service column contains esserver.
For storage details, see the system views M_ES_DBSPACES, M_ES_DBSPACE_FILES, and M_ES_TABLES
in the Systems view under
Catalog
SYS
Views .
2.8.2 Monitoring Dynamic Tiering in the SAP HANA Cockpit

The SAP HANA cockpit provides several monitoring applications through a Web browser.
From the SAP HANA cockpit, you can:
Monitor dbspace percentage in use
View alerts for dbspaces nearing capacity
Check availability of dbspaces and dbspace files
Monitor memory usage and change allocation
66
PUBLIC

Diagnose problematic internal connections and cancel corresponding sessions

To get started, see Open SAP HANA Cockpit.
In this section:
Dynamic Tiering Alerts [page 67]
Alerts notify you of critical situations for dynamic tiering storage before processing may be affected.
The Alerts app lets you configure alerts and view alerts related to the usage and availability of
dbspaces and dbspace files used by dynamic tiering.
Dynamic Tiering Memory [page 68]
SAP HANA dynamic tiering uses several types of memory. The HANA Dynamic Tiering Memory
application lets you view and manage the used and available memory by host, by type, and by memory
component.
Dynamic Tiering Connections [page 68]
The Dynamic Tiering Connections app lets you diagnose problematic internal connections and cancel
the corresponding session, if necessary, to correct an unresponsive system.
Related Information
Open SAP HANA Cockpit [page 11]
2.8.2.1
Dynamic Tiering Alerts
Alerts notify you of critical situations for dynamic tiering storage before processing may be affected. The
Alerts app lets you configure alerts and view alerts related to the usage and availability of dbspaces and
dbspace files used by dynamic tiering.
The Alerts tile is visible on the homepage of the SAP HANA cockpit. If it's not, you can add it from the SAP
HANA Database Administration tile catalog. Click the Alerts tile to open the app.
Alert
Description
Dbspace Usage
Lists the percentage of the dbspace

that is used, the total size, and the
amount used.
Use
Trigger the alert to notify you when the

dbspace has passed a threshold, and
add new dbspace files or enlarge
existing files before lack of space
affects processing.
Dbspace Status
Warns you if a dbspace is unavailable.
Trigger the alert to notify you if the

dynamic tiering dbspace goes offline.
Dbspace File Status
Warns you if a dbspace file is
Trigger the alert to notify you if the

dynamic tiering dbspace file goes
offline.
unavailable.
See Monitoring Alerts and Alert Details in the SAP HANA Administration Guide.

PUBLIC
67
Related Information
2.8.2.2
Dynamic Tiering Memory
SAP HANA dynamic tiering uses several types of memory. The HANA Dynamic Tiering Memory application lets
you view and manage the used and available memory by host, by type, and by memory component.
The selected dynamic tiering host displays its machine name, role, total physical memory, total allocated
memory, and cumulative memory used. Allocated memory is the total memory allocated to both SAP HANA
and dynamic tiering. Cumulative usage is the memory used as a percentage of total allocated memory. Total
memory allocated, used, and available then broken down by component.
Click the dropdown beside the host name to display memory for a different dynamic tiering host.
To change allocated memory for dynamic tiering specific components, click Modify Allocation. Select:
Component
Change
Delta
delta_memory_mb
Large / Load
load_memory_mb
Temp Cache
temporary_cache_mb
Main Cache
main_cache_mb
Note
Memory allocation for HANA System cannot be changed.
2.8.2.3
Dynamic Tiering Connections
The Dynamic Tiering Connections app lets you diagnose problematic internal connections and cancel the
corresponding session, if necessary, to correct an unresponsive system.
Prerequisites
You have the role sap.hana.admin.roles::Monitoring.
You have added the Dynamic Tiering Connections tile to your dashboard.
68
PUBLIC

Context
If your system becomes unresponsive, and you suspect that a large load statement is running or a deadlock
has occurred, examine the dynamic tiering connections. Dynamic tiering connections are internal and are not
exposed as user connections.
Procedure
1. In the SAP HANA cockpit, click the Dynamic Tiering Connections tile to display all connections.
2. To filter connections displayed, click Idle or Active.
3. Click any row for connection details.
Click Active Transactions or Remote Statements to view related details for the given connection.
4. Click Cancel Session to stop the session for an unresponsive connection.
5. Click Modify Configuration to change properties of the dynamic tiering service, such as the maximum
number of concurrent connections or the number of threads.
Related Information
Dynamic Tiering Service Properties (esserver.ini) [page 22]
2.9
Backup and Recovery for Dynamic Tiering
Backup and recovery of an SAP HANA system with dynamic tiering installed differs from the same operations
on an SAP HANA system without dynamic tiering.
Backup and recovery applies to the whole database, including the SAP HANA database and dynamic tiering.
SAP HANA dynamic tiering only supports backup and recovery options explicitly documented in the dynamic
tiering option documentation. Other tools and options mentioned in the SAP HANA documentation are
supported for HANA but not necessarily for dynamic tiering.
Systems with dynamic tiering support:
Data backup
Log backup
Database copy
Point-in-time recovery
Recovery to a specific data backup without using logs or log backups
Third-party backup tools certified by SAP
Systems with dynamic tiering installed do not support:

PUBLIC
69
Storage snapshots
Backup of files with customer-specific configuration settings
In this section:
Backing Up SAP HANA Databases With Dynamic Tiering [page 70]
Backing up an SAP HANA database with dynamic tiering backs up both the SAP HANA database and
dynamic tiering.
Finding and Checking Backups for Recovery [page 73]
Use hdbbackupdiag to list the data and log backup files for a successful recovery, and to check
whether recovery of a system with dynamic tiering is possible with the provided data and log backup
files.
Recovering SAP HANA Databases with Dynamic Tiering [page 74]
You can recover using only the data backup, or you can perform a point-in-time recovery.
2.9.1 Backing Up SAP HANA Databases With Dynamic

Tiering
Backing up an SAP HANA database with dynamic tiering backs up both the SAP HANA database and dynamic
tiering.
Data Backups
See "Performing Backups" in the SAP HANA Administration Guide for the procedure to back up an SAP HANA
database.
Backups create files for dynamic tiering in the location specified by the parameter <basepath_databackup>
in the persistence section of the global.ini file. The navigation path defaults to ($DIR_INSTANCE)/
backup/data.
The backup directory for dynamic tiering must be on a shared file system and available to all hosts, including
the host where hdbesserver runs.
Log Backups
After the first data backup, a database with dynamic tiering automatically makes a log backup every 15
minutes. The parameter <es_log_backup_interval>, in the database section of the esserver.ini file,
controls the period between backups.
Log backups create files for dynamic tiering in the location specified by the parameter
<basepath_logbackup> in the persistence section of the global.ini file. The navigation path defaults to
($DIR_INSTANCE)/backup/log.
70
PUBLIC

The log area for dynamic tiering stores information about the data changes in transaction logs. Log backup of
dynamic tiering writes only the transaction log and metadata related to data modifications to the log backup
files.
Note
You can modify global.ini using the Configuration tab in the SAP HANA studio. See the SAP HANA
In this section:
Viewing Backup History [page 71]
The SAP HANA backup catalog maintains information about backup execution history for dynamic
tiering data and backups.
Backups with Third-Party Backup Tools [page 72]
Backint for SAP HANA is an API that enables third-party tool vendors to directly connect their
backup agents to the SAP HANA database.
Set the Log Backup Interval [page 72]
minutes. Change the log backup interval to adjust the backup frequency.
Related Information
Backup Cannot Complete [page 107]
2.9.1.1
Viewing Backup History
The SAP HANA backup catalog maintains information about backup execution history for dynamic tiering data
and backups.
Refer to the backup catalog to determine:
Whether recovery is possible
Which data and log backups for dynamic tiering are required to perform a recovery
Which backups are no longer needed
Which part of the dynamic tiering transaction log is contained in a log backup
Whether a data or log backup was successful or not
The size of data and log backups

PUBLIC
71
2.9.1.2
Backups with Third-Party Backup Tools
Backint for SAP HANA is an API that enables third-party tool vendors to directly connect their backup
agents to the SAP HANA database.
Third-party backup tools certified by SAP provide an alternate destination for data and log backups. All thirdparty backup tools certified for Backint with SAP HANA are supported by SAP HANA dynamic tiering.
Note
In a multitenant database container system, tenant databases configured for SAP HANA dynamic tiering do
not support backup and recovery using Backint.
For more information about the backup catalog and about installing and configuring a third-party backup tool,
see Backup with Third-Party Backup Tool in the SAP HANA Administration Guide and the documentation
provided by the backup tool vendor.
Related Information
2.9.1.3
Set the Log Backup Interval
minutes. Change the log backup interval to adjust the backup frequency.
Prerequisites
You have either the EXTENDED STORAGE ADMIN or INIFILE ADMIN system privilege.
Context
Option values for the interval may be 0 or a range from 5 to 4294967295UL (2^32-1). The value 0 turns off
automatic log backups. Logging remains on, so the point-in-time log continues to grow and unallocated space
on the RLV dbspace is not freed.
72
PUBLIC

Procedure
2. Execute the ALTER SYSTEM ALTER CONFIGURATION statement.
ALTER SYSTEM ALTER CONFIGURATION ('esserver.ini','SYSTEM')
SET ('<parameter_key_value_list>') = '<parameter_key_value>' [WITH
RECONFIGURE]
Note
What
How
Change the setting of log backup interval to ALTER SYSTEM ALTER CONFIGURATION
5 minutes.
('esserver.ini','SYSTEM') SET ('database',
'log_backup_interval')='5' WITH RECONFIGURE

You may also use SAP HANA studio to set the log backup interval. See Change an esserver.ini Property Single Database.
Related Information
Change an esserver.ini Property - Single Database [page 24]
2.9.2 Finding and Checking Backups for Recovery

Use hdbbackupdiag to list the data and log backup files for a successful recovery, and to check whether
recovery of a system with dynamic tiering is possible with the provided data and log backup files.
The hdbbackupdiag tool obtains information about the required data and log backup files from both the SAP
HANA database and its extended storage from the HANA backup catalog. See "Determining and checking
Backups for Recovery (hdbbackupdiag Program)" in the SAP HANA Administration Guide.
Related Information

PUBLIC
73
2.9.3 Recovering SAP HANA Databases with Dynamic Tiering

You can recover using only the data backup, or you can perform a point-in-time recovery.
Restrictions on Recovery
Certain restrictions affect recovery of SAP HANA databases with extended storage:
The number and type of services must be identical in both the source and target system.
Recovery of a system configured with SAP HANA dynamic tiering requires the data and log backups for
both the SAP HANA database and dynamic tiering. You cannot recover one without the other.
If you restore a tenant database from a backup whose source has dynamic tiering configured and
extended storage created, you must provision the esserver service to the destination tenant database
before you restore it. See Assigning the Dynamic Tiering Service to a Tenant Database in the SAP HANA
Dynamic Tiering: Administration Guide. The destination tenant database can be on a different SAP HANA
instance.
After successful recovery using data backups, you cannot perform a point-in-time recovery until a log
backup for dynamic tiering occurs. Log backups for dynamic tiering occur every 15 minutes. To avoid
waiting, you can take a data backup immediately after the successful recovery from data backups.
You must specify the CLEAR LOG option of the RECOVER DATABASE command if you perform a point-intime recovery immediately after upgrade, and the data and log backup are from a version older than SPS
10.
When performing point-in-time recovery through Backint for SAP HANA, omit the CLEAR LOG option of
the RECOVER DATABASE command. Deselect the Initialize log area option in SAP HANA studio.
When recovery uses Backint, SAP HANA materializes log backups from Backint into the backup/log
directory. Allow sufficient disk space in the backup/log directory for the restore to complete
successfully. Disk space required depends on the number of days of log backups that you want to recover
since the data backup.
In a multitenant database container SAP HANA system, tenant databases configured for dynamic tiering
do not support backup and recovery using Backint for SAP HANA.
Preparing for Recovery

Recovery of a system with SAP HANA dynamic tiering requires the data backups for both the SAP HANA
database and dynamic tiering, which are located in the same directory by default.
If the dynamic tiering backup was created using version SPS 09, before attempting recovery, copy the
required data dynamic tiering backup files to the path specified by basepath_databackup.
Point-in-time recovery requires the log backups for both the SAP HANA database and SAP HANA dynamic
tiering.
Log backups for dynamic tiering are located in the same directory as SAP HANA log backups.
74
PUBLIC

Recovery Procedure
Use the command line tool or the Recovery Wizard in the SAP HANA studio. For both recovery procedures, see
Recovering an SAP HANA Database in the SAP HANA Administration Guide.
Recovery includes an option to check availability of required backups. Specify the option to check for log
backups from both SAP HANA and SAP HANA dynamic tiering. If any backups are missing, recovery lists the
missing log backups and stops before changing data.
In cases where the transaction log of dynamic tiering is corrupt, specify the recovery option to initialize the log
area. This option prevents the replay of the active transaction log during recovery, and reinitializes the log.
In this section:
Recovery In Upgraded Databases [page 75]
Certain restrictions affect recovery of data from databases that have been upgraded to the current
version.
Related Information
2.9.3.1
Recovery In Upgraded Databases
Certain restrictions affect recovery of data from databases that have been upgraded to the current version.
Three types of recovery are possible:
Recovery using the data backup or snapshot backup.
Recovery to a specific point in time
Recovery to the latest point in time
Point in time recovery requires both data and log backups.
Recovery Using Data Backup Only

To recover a data backup created before upgrade, requirements vary according to the recovery tool.
When using a SQL client to recover, specify the USING FILE clause. For example:RECOVER DATA USING
FILE ('COMPLETE_DATA_BACKUP' ') CLEAR LOG"
When using SAP HANA studio to recover, choose the recovery type Recover to a specific data backup or
storage snapshot, then choose the backup location option Specify backup without catalog.

PUBLIC
75
Point in Time Recovery

To recover to a point in time after upgrading the database, you must recover using a backup taken after
upgrade. For example, use the full backup that you took immediately after upgrade, as recommended in Post
Update Tasks in the SAP HANA Dynamic Tiering: Administration Guide.
Recovery Using Data and Log Backups

When recovery after upgrade uses data and log backups created before upgrade, always specify CLEAR LOG.
To recover to the latest point-in-time, you have two choices:
a. Before performing upgrade, disconnect all connections and wait for automatic dynamic tiering and SAP
HANA log backup.
b. Take a full data backup before upgrade, then recover from that data backup (no log replay).
When using a SQL client to recover, specify USING DATA PATH, USING LOG PATH, CLEAR LOG, and CHECK
ACCESS ALL clauses in the recovery syntax (as you do in a system copy). For example:
Sample Code
RECOVER DATA USING BACKUP_ID 1432268516180
USING DATA PATH (/usr/sap/C17/HDB17/backup/data)
USING LOG PATH ('/usr/sap/C17/HDB17/backup/log')
CLEAR LOG CHECK ACCESS ALL
When using SAP HANA studio to recover:
a. The Locate Log backups screen supplies the log backup location for you. For example: /usr/sap/C17/
HDB17/backup/log).
Do not remove the log backup location supplied. Dynamic Tiering recovery requires it.
b. On the Select a Backup screen, specify Alternative Locations for data backups as: /usr/sap/C17/
HDB17/backup/data.
c. On the Other Settings screen, select two check boxes: File System and Initialize log area.
d. Click Show SQL Statement to verify that the recovery statement includes USING DATA PATH, USING
LOG PATH, CLEAR LOG and CHECK ACCESS clauses.
Related Information
SAP HANA Dynamic Tiering: Installation and Update Guide
76
PUBLIC

2.10 Dynamic Tiering High Availability (Failover)

SAP HANA Dynamic Tiering supports both automatic and manual failover.
Automatic failover is available when the dynamic tiering worker and standby host are assigned to the same
high availability group. Manual failover is available when the worker and standby hosts are assigned to
different, unique, high availability groups.
Automatic failover is supported for dynamic tiering using NFS, GPFS, and SAN storage.
The same standby host cannot be used for both SAP HANA and dynamic tiering. Each requires its own
dedicated standby host.
Refer to the High Availability for SAP HANA section in the SAP HANA Administration Guide for configuration
details.
In this section:
Change High Availability Group Assignment [page 77]
To switch between automatic and manual failover, you change the assigned high availability group of
the worker and standby host.
Manual Failover to Dynamic Tiering Standby Host [page 78]
Failing over from the SAP HANA dynamic tiering worker host to the standby host is a manual process
when the hosts are assigned to different failover groups.
Dynamic Tiering Automatic Failover with SAN Storage [page 79]
Automatic failover for dynamic tiering data residing on SAN requires configuration in the global.ini
file.
Failover in a Same Host Deployment [page 79]
SAP HANA Dynamic Tiering supports both automatic and manual failover in a same host deployment.
Related Information
2.10.1 Change High Availability Group Assignment

To switch between automatic and manual failover, you change the assigned high availability group of the
worker and standby host.
Context
Automatic failover is available when the dynamic tiering worker and standby hosts belong to the same high
availability group. The default group name is extended_storage, but any name can be used, as long as it is

PUBLIC
77
not already used for automatic failover of the SAP HANA system. The dynamic tiering worker and standby
hosts should never be assigned to an existing SAP HANA high availability group.
When the dynamic tiering worker and standby hosts are assigned to different, unique groups, the failover
process is manual.
Procedure
Database Type
Action
Single database
Double-click the system in the Systems panel.
Tenant database
Double-click the SYSTEMDB in the Systems panel.
2. Choose
Landscape
3. Click the
Hosts .
(Configure Hosts for Failover Situation) button.
4. Modify the values for the dynamic tiering worker and standby hosts in the Configured Group column to be
the same.
5. Click Check, then OK, then Save.
2.10.2 Manual Failover to Dynamic Tiering Standby Host

Failing over from the SAP HANA dynamic tiering worker host to the standby host is a manual process when the
hosts are assigned to different failover groups.
Prerequisites
The dynamic tiering worker and standby host belong to different failover groups.
Context
Fail over to the standby host if the dynamic tiering worker host goes offline.
Procedure
1. Verify that either the dynamic tiering worker host, or the dynamic tiering service process, is inactive.
78
PUBLIC

Caution
Failing over when the dynamic tiering service is still running can result in data inconsistencies.
2. Connect to the index server.
3. Issue this SQL command to fail over from the current dynamic tiering worker host ('<source-hostname>') to the standby host ('<target-host-name>'):
CALL SYS.UPDATE_LANDSCAPE_CONFIGURATION(host failover, '<source-hostname>', '<target-host-name>')
For example:
CALL SYS.UPDATE_LANDSCAPE_CONFIGURATION ('host failover', 'abcdehana1106',
'abcdehana1107')
Results
The dynamic tiering service restarts on the standby host. The standby host is renamed worker in the topology.
If the original worker node comes back online, it is renamed standby in the topology.
2.10.3 Dynamic Tiering Automatic Failover with SAN Storage

Automatic failover for dynamic tiering data residing on SAN requires configuration in the global.ini file.
Set the storage > enable_extended_storage parameter in the global.ini file to true (default) when
dynamic tiering data resides on SAN using the storage connector API. False indicates dynamic tiering data
resides on an NFS share.
Add the parameters partition_1024_data_es__wwid = <wwid3> and
partition_1024_log_es__wwid = <wwid4 > to the storage section.
2.10.4 Failover in a Same Host Deployment

SAP HANA Dynamic Tiering supports both automatic and manual failover in a same host deployment.
A dedicated dynamic tiering standby host is not required in a same host deployment. SAP HANA and dynamic
tiering share the same standby host. This is done by assigning both the SAP HANA and dynamic tiering worker
roles to the same failover group.

PUBLIC
79
Caution
Same host deployments are not supported in production environments.
80
PUBLIC

Security Administration
Security administration is usually handled separately from general system administration tasks.
SAP HANA dynamic tiering adds a new user to the list of SAP HANA standard users.
User
Description
Password Specification
_SYS_ES
_SYS_ES is a technical user used by

dynamic tiering. It is automatically cre
ated when you create extended stor
age.
Not applicable.
This is a technical database user.
_SYS_ES logs on internally through the
dynamic tiering service. You cannot log
on with this user.
To perform operations, users need the necessary privileges. See the GRANT EXTENDED STORAGE ADMIN
System Privilege Statement [Dynamic Tiering] statement in the SAP HANA SQL and System Views Reference.
Network and Communication Security

Internal communication between the dynamic tiering host and the SAP HANA database is secured using the
secure sockets layer (SSL) protocol. In addition to securing internal communications with the SSL protocol,
each dynamic tiering and SAP HANA database host in the system has a public and private key pair and a
public-key certificate.
See Communication Channel Security and Secure Internal Communication in the SAP HANA Security Guide.
To improve performance and security in multiple-host systems, you may configure SAP HANA to use only an
internal IP address to communicate with the dynamic tiering service.
User Privileges
To perform dynamic tiering administration tasks, you need the EXTENDED STORAGE ADMIN system privilege.
It must be granted to your database user or relevant role by a user administrator.
See the GRANT EXTENDED STORAGE ADMIN System Privilege Statement [Dynamic Tiering] statement in the
SAP HANA SQL and System Views Reference.
In this section:
Configure Private Internal Communication Using the Command-Line Interface [page 82]
To increase security and improve performance, configure communication between the SAP HANA
database and the SAP HANA dynamic tiering service over an internal network, using the command-line
interface.
Configure Private Internal Communication Using the Graphical User Interface [page 84]

PUBLIC
81
To increase security and improve performance, configure communication between the SAP HANA
database and the SAP HANA dynamic tiering service over an internal network, using the graphical user
interface.
Related Information
Dynamic Tiering Administration User [page 98]
SAP HANA Security Guide
3.1
Configure Private Internal Communication Using the

Command-Line Interface
To increase security and improve performance, configure communication between the SAP HANA database
and the SAP HANA dynamic tiering service over an internal network, using the command-line interface.
Prerequisites
The SAP HANA system has been installed or updated with the SAP HANA database lifecycle manager
(HDBLCM).
The SAP HANA database server is up and running.
You are logged on with the required root user or system administrator user <sid>adm credentials.
Procedure
1. Change to the SAP HANA resident HDBLCM directory:
cd <sapmnt>/<SID>/hdblcm
By default, <sapmnt> is /hana/shared.
2. Start the SAP HANA database lifecycle manager interactively in the command line:
./hdblcm
3. Select the index for the configure_internal_network action. Then select Enter .
4. Define the required parameters.
82
PUBLIC

Field Name
Description
Inter-Service Communication
Specifies the listen interface for the internal network communication.
global - Binds the processes to all interfaces. This option does not re
quire an internal network address entry.
internal - Binds the processes to this address only and to all local host
interfaces. This option requires an internal network address entry.
local - Opens the communication ports for internal usage on the local
interfaces. This configuration is only an option for single installations as
the server is not reachable from outside. This option does not require an
internal network address entry.
If you define a value other than local, the local interfaces will always be
open.
Internal Network Address
Specifies the internal subnet address in CIDR notation.
5. Review the summary, and select y to finalize the configuration.
Results
When you apply the change, the SAP HANA database lifecycle manager shuts down and restarts the system.
After the restart, the SAP HANA database uses internal IP with other HANA worker nodes and the dynamic
tiering host.
Note
When using the command line, the options can be set interactively during configuration only if they are
marked as interactive in the help description. All other options have to be specified in the command line. To
call the help, in the SAP HANA resident HDBLCM directory of the SAP HANA system, execute the following
command:
./hdblcm --action=configure_internal_network --help
Example
The following example configures the internal network communication with an internal interface:
./hdblcm --action=configure_internal_network --listen_interface=internal -internal_network=192.456.78/21

PUBLIC
83
3.2
Configure Private Internal Communication Using the

Graphical User Interface
To increase security and improve performance, configure communication between the SAP HANA database
and the SAP HANA dynamic tiering service over an internal network, using the graphical user interface.
Prerequisites
The SAP HANA system has been installed or updated with the SAP HANA database lifecycle manager
(HDBLCM).
The SAP HANA database server is up and running.
You are logged on with the required root user or system administrator user <sid>adm credentials.
Procedure
1. Change to the SAP HANA resident HDBLCM directory:
cd <sapmnt>/<SID>/hdblcm
By default, <sapmnt> is /hana/shared.
2. Start the SAP HANA database lifecycle manager interactively in the graphical user interface:
./hdblcmgui
The SAP HANA database lifecycle manager graphical user interface appears.
3. Select Configure Inter-Service Communication from the activity options. Then select Next.
4. Define the required parameters. Then select Next.
Field Name
Description
Inter-Service Communication
Specifies the listen interface for the internal network communication.
global - Binds the processes to all interfaces. This option does not re
quire an internal network address entry.
internal - Binds the processes to this address only and to all local host
interfaces. This option requires an internal network address entry.
local - Opens the communication ports for internal usage on the local
interfaces. This configuration is only an option for single installations as
the server is not reachable from outside. This option does not require an
internal network address entry.
If you define a value other than local, the local interfaces will always be
open.
84
PUBLIC

Field Name
Description
Internal Network Address
Specifies the internal subnet address in CIDR notation.
5. Review the summary, and select Run to finalize the configuration.

You can find more information about SAP HANA system internal network and the network security
recommendations, in the SAP HANA Update Master, SAP HANA Security Guide, and SAP HANA
Results
You have configured the inter-service communication so that the SAP HANA database uses internal IP with
other HANA worker nodes and the dynamic tiering host. The parameter values are entered in the global.ini
configuration file under [communication].

PUBLIC
85
Using Dynamic Tiering with Multitenant

Databases
SAP HANA dynamic tiering is supported in a multitenant database container SAP HANA system.
Use SAP HANA dynamic tiering with any tenant database. Each tenant database using SAP HANA dynamic
tiering requires its own dedicated dynamic tiering worker, but not a dedicated (optional) standby host.
SAP HANA dynamic tiering only supports low tenant isolation. Any attempt to provision the dynamic tiering
service (esserver) to a tenant database in a new installation with high-level tenant isolation will fail. If you
raise the isolation level too high for an existing installation, the dynamic tiering service stops working. To lower
the isolation level , see Decrease the System Isolation Level in the SAP HANA Administration Guide.
The concepts and tasks presented in this section focus on installing and configuring SAP HANA dynamic
tiering on an existing multitenant database container SAP HANA system. Refer to the SAP HANA Server
Installation and Update Guide and SAP HANA Administration Guide to create and configure the multitenant
database container system, then use this guide to configure SAP HANA dynamic tiering on the tenant
database.
For an existing SAP HANA system with SAP HANA dynamic tiering recently converted to a multi-container
system, see Converted Multitenant Containers Using Dynamic Tiering.
The workflow to configure a multitenant database container SAP HANA system to use SAP HANA dynamic
tiering is:
1. Verify that the SAP HANA multitenant database system is installed and running without errors. Ensure
that all tenant databases can be accessed and managed by SAP HANA Cockpit.
2. Install SAP HANA dynamic tiering on a multitenant database container SAP HANA system.
3. Add the dedicated SAP HANA dynamic tiering worker and (optional) standby hosts.
4. Provision the SAP HANA dynamic tiering service (esserver) to the tenant database.
5. Import the SAP HANA dynamic tiering delivery units.
6. Create extended storage on the tenant database.
7. Repeat steps 3 [page 86] through 6 [page 86] for each tenant database to use SAP HANA dynamic tiering.
In this section:
Verify Configuration of the SAP HANA Core System [page 87]
Before configuring an SAP HANA system to use dynamic tiering in a multi-container environment,
verify the core system is correctly configured.
Adding the Dynamic Tiering Host to a Multitenant Database System [page 89]
Adding the SAP HANA dynamic tiering worker and standby hosts to a multitenant database system
uses the same process as adding a host to a single-host SAP HANA system.
Prepare the Tenant Database Resources for Dynamic Tiering [page 90]
You modify properties in the global.ini file to prepare resources on each tenant database to
support SAP HANA dynamic tiering.
Provision the Dynamic Tiering Service to a Tenant Database [page 91]
86
PUBLIC

Using Dynamic Tiering with Multitenant Databases
To use SAP HANA dynamic tiering with a tenant database, assign the dynamic tiering service
(esserver) to the tenant database.
Failing Over with Multitenant Databases [page 92]
Automatic and manual failover is supported with tenant databases.
Import Dynamic Tiering Delivery Units to a New Tenant Database [page 93]
To use SAP HANA Cockpit for Dynamic Tiering, you must import its delivery units to each new tenant
database provisioned for dynamic tiering.
Create Extended Storage on the Tenant Database [page 94]
You create extended storage on the tenant database as you would on a single-host system
Remove Dynamic Tiering from a Tenant Database [page 95]
Unassign the esserver service from a tenant database when it no longer requires dynamic tiering.
Converting Multitenant Database Containers Using Dynamic Tiering [page 95]
When you migrate a single database SAP HANA system that has SAP HANA dynamic tiering installed
to a multitenant database container, the container continues to support dynamic tiering.
Using Multitenant Databases with Same Host Deployment [page 97]
You can use dynamic tiering with multitenant databases in a same host deployment.
Related Information
SAP HANA Server and Update Installation Guide
4.1
Verify Configuration of the SAP HANA Core System
Before configuring an SAP HANA system to use dynamic tiering in a multi-container environment, verify the
core system is correctly configured.
This includes verifying:
The tenant databases to use dynamic tiering exist.
You can access each tenant database using SAP HANA Cockpit.
In this section:
Verify That Tenant Databases Exist [page 88]
A tenant database must exist before you can provision it to use dynamic tiering.
Verifying SAP HANA Cockpit Access [page 88]
In a multi-container environment, configure SAP HANA cockpit to access each tenant database;
otherwise, you can only access the SYSTEMDB using SAP HANA cockpit.

PUBLIC
87
4.1.1 Verify That Tenant Databases Exist

A tenant database must exist before you can provision it to use dynamic tiering.
Prerequisites
You have the system privilege DATABASE ADMIN.
Procedure
1. Open the SQL console and connect to the SYSTEMDB.
2. Execute:
SELECT * from m_databases
Results
A list of tenant databases is returned. If the database to use dynamic tiering is not listed, see Managing
Multitenant Database Containers in the SAP HANA Administration Guide before continuing.
Related Information
4.1.2 Verifying SAP HANA Cockpit Access

In a multi-container environment, configure SAP HANA cockpit to access each tenant database; otherwise,
you can only access the SYSTEMDB using SAP HANA cockpit.
The SAP HANA cockpit URL consists of the machine name, port 80 or 43, and the instance number:
http://<machine_name>:80<instance_number>/sap/hana/admin/cockpit/
https://<machine_name>:43<instance_number>/sap/hana/admin/cockpit/
88
PUBLIC

Since the SYSTEMDB and each tenant database reside on the same machine and are part of the same
instance, configure a unique alias to identify each tenant database. This alias is then used to redirect the URL:
http://<machine_name>-<tenant _alias>:80<instance_number>/sap/hana/admin/cockpit/
Before proceeding, verify that you can successfully access each tenant database to use dynamic tiering. If you
cannot access each tenant database, see Configure HTTP Access to Multitenant Database Containers in the
SAP HANA Administration Guide.
Related Information
4.2
Adding the Dynamic Tiering Host to a Multitenant

Database System
Adding the SAP HANA dynamic tiering worker and standby hosts to a multitenant database system uses the
same process as adding a host to a single-host SAP HANA system.
When you add the SAP HANA dynamic tiering worker host, the dynamic tiering service (esserver) runs in
utility mode. The service is only visible to the SYSTEMDB. You provision the service to a specific tenant
database, making it visible to the tenant database, but invisible to SYSTEMDB. When you add the (optional)
standby host, you do not provision it to a tenant database. It remains assigned to the SYSTEMDB, running in
standby mode.
The same SAP HANA dynamic tiering worker host cannot be provisioned to multiple tenant databases.
Related Information

PUBLIC
89
4.3
Prepare the Tenant Database Resources for Dynamic

Tiering
You modify properties in the global.ini file to prepare resources on each tenant database to support SAP
HANA dynamic tiering.
Context
The customizable_functionalities property controls whether the tenant database can use SAP HANA
dynamic tiering. It is enabled (true), by default, but SAP recommends that you verify this setting before
proceeding.
In a multitenant database container SAP HANA system using dynamic tiering, the paths for datavolumes_es
and logvolumes_es can be unique for each tenant database. These values, which are defined during
installation of SAP HANA dynamic tiering, are used as default values for each tenant database. You manually
modify these values on each tenant database to use dynamic tiering to make them unique. The path specified
need not exist when defining the value, but it must exist before you attempt to create extended storage for the
tenant. The extended storage create process fails if the specified path cannot be found.
Perform these preparation tasks for each tenant database on which you plan to use SAP HANA dynamic
tiering.
Prepare Resources Using SAP HANA Studio

Context
The customizable_functionalities property is defined in the SYSTEMDB globlal.ini file at the
system level.
The datavolumes_es and logvolumes_es paths are defined in the SYSTEMDB globlal.ini file at the
system level, but are applied at the database level. When set, a diamond appears in the database column. The
values are visible in the global.ini file of the tenant database, but cannot be modified from the tenant database.
Procedure
1. In the SAP HANA studio Administration console, logged on as the SYSTEM user, double-click SYSTEMDB
in the Systems panel, and then select the Configuration tab.
2. Expand
global.ini
customizable_functionalities .
3. Verify that the dynamic_tiering property is set to true. If set to false, double-click
dynamic_tiering, enter a value of true, and click Save.
90
PUBLIC

4. Expand
global.ini
persistence .
5. Double-click basepath_datavolumes_es.
6. Click within the Databases field, select the database name, and click OK.
7. Enter a unique path available to both the SAP HANA and dynamic tiering hosts, and click Save.
A diamond appears in the database column. To review the setting, repeat steps 5 and 6.
8. Double-click basepath_logvolumes_es.
9. Click within the Databases field, select the database name, and click OK.
10. Enter a unique path available to both the SAP HANA and dynamic tiering hosts, and click Save.
Prepare Resources Using SQL

Procedure
1. In a SQL console, connect to the SYSTEMDB as a user with the DATABASE ADMIN privilege.
2. Execute the ALTER SYSTEM ALTER CONFIGURATION statement to configure the tenant database can
use dynamic tiering
ALTER SYSTEM ALTER CONFIGURATION ( 'global.ini', 'SYSTEM' )
SET( 'customizable_functionalities', 'dynamic_tiering' ) = 'true'
3. Execute the ALTER SYSTEM ALTER CONFIGURATION statement to change the base path for data_es
and log_es volumes. The paths must be unique for each tenant database and available to the SAP
HANA and dynamic tiering hosts. Use the syntax:
ALTER SYSTEM ALTER CONFIGURATION ( 'global.ini', 'DATABASE' ,
'<database_name>' )
SET( 'persistence', 'basepath_datavolumes_es') =
'<path_basepath_datavolumes_es>' WITH RECONFIGURE
ALTER SYSTEM ALTER CONFIGURATION ( 'global.ini', 'DATABASE' ,
'<database_name>' )
SET( 'persistence', 'basepath_logdatavolumes_es') =
'<path_basepath_logvolumes_es>' WITH RECONFIGURE
4.4
Provision the Dynamic Tiering Service to a Tenant

Database
To use SAP HANA dynamic tiering with a tenant database, assign the dynamic tiering service (esserver) to
the tenant database.
Context
Once the esserver service is assigned to a tenant database, the database, not SYSTEMDB, owns the service.

PUBLIC
91
Procedure
2. Execute the following ALTER DATABASE statement:
ALTER DATABASE <database_name> ADD 'esserver'
[ AT [ LOCATION] '<tiering_hostname>[:<port_number> ]' ]
The host and port information is that of the SAP HANA dynamic tiering host. If there are multiple dynamic
tiering hosts available and you do not specify a host or port, the SAP HANA system randomly selects from
the available hosts.
4.5
Failing Over with Multitenant Databases
Automatic and manual failover is supported with tenant databases.

Unlike with the dynamic tiering worker host, you do not provision the dynamic tiering standby host to a
specific tenant. You leave it assigned to the SYSTEMDB, with the dynamic tiering service (esserver) running
in standby mode.
In the event of a worker host failure, one of the following occurs:
Failover Type
Behavior
Automatic
From the SYSTEMDB, the SAP HANA system selects the first available dynamic tier
ing standby host assigned to the same failover group as the failed dynamic tiering
worker host, and provisions it to the tenant database. The failed dynamic tiering
worker host is then removed from the tenant database and returned to the SYS
TEMDB with a status of standby.
Manual
You execute the same SQL syntax to replace the failed dynamic tiering worker host
with a specific dynamic tiering standby host as with a single-host SAP HANA system.
Related Information
Manual Failover to Dynamic Tiering Standby Host [page 78]
92
PUBLIC

4.6
Import Dynamic Tiering Delivery Units to a New Tenant

Database
To use SAP HANA Cockpit for Dynamic Tiering, you must import its delivery units to each new tenant database
provisioned for dynamic tiering.
Prerequisites
You have provisioned Dynamic Tiering to the new tenant database.
Context
There are two DUs:
HANA_TIERING.tgz
HDC_TIERING.tgz
The DUs must be imported individually.
Procedure
1. In SAP HANA Studio, select
File
Import .
2. Open SAP HANA Content and select Delivery Unit.

3. Select the system where you want to add the DU.
4. Select Server and then click the File dropdown.
5. Select /usr/sap/<sid>/SYS/global/hdb/content/HANA_TIERING.tgz
6. When the contents of the file loads in the Object import simulation window, click Finish.
7. Repeat these steps to import HDC_TIERING.tgz.

PUBLIC
93
4.7
Create Extended Storage on the Tenant Database
You create extended storage on the tenant database as you would on a single-host system
Prerequisites
The path specified under global.ini persistence for the basepath_datavolumes_es and
basepath_logvolumes_es parameters for the tenant database exists.
Context
Each tenant database has its own extended storage.
Procedure
1. Do one of:
Method
Action
SAP HANA cockpit
Log on to the tenant database as a user with the

sap.hana.tiering.roles::Administrator role.
SQL console
Connect to the tenant database as a user with the EXTENDED STORAGE ADMIN
privilege.
2. Refer to the SAP HANA Dynamic Tiering: Administration Guide for details on creating extended storage.
Related Information
94
PUBLIC

4.8
Remove Dynamic Tiering from a Tenant Database
Unassign the esserver service from a tenant database when it no longer requires dynamic tiering.
Context
Unassigning the esserver service from the tenant database returns the service to utility mode on the SAP
HANA dynamic tiering host, and returns ownership to the SYSTEMDB. The service is then available for
assignment to another tenant database.
Procedure
1. Open a SQL console and connect to the tenant database as a user with the EXTENDED STORAGE ADMIN
privilege.
2. Execute the following DROP EXTENDED STORAGE statement:
DROP EXTENDED STORAGE [CASCADE | RESTRICT]
4. Execute the following ALTER DATABASE statement:
ALTER DATABASE <database_name> REMOVE 'esserver'
AT [ LOCATION ] '<hostname>[:<port_number> ]'
where the host and port information is that of the SAP HANA dynamic tiering host provisioned to the
database.
4.9
Converting Multitenant Database Containers Using

Dynamic Tiering
When you migrate a single database SAP HANA system that has SAP HANA dynamic tiering installed to a
multitenant database container, the container continues to support dynamic tiering.
After conversion, the original database becomes the first tenant. Conversion automatically provisions the SAP
HANA dynamic tiering service (esserver) to the first tenant database.
Before creating any additional tenant databases on the converted system, you must import the SAP HANA
delivery units (DUs) into the SYSTEMDB These DUs are required for functionality in the SAP HANA cockpit.
See Import SAP HANA Delivery Units (DUs).
If you did not import the DUs before creating additional tenant databases, you will be unable to use SAP HANA
cockpit to manage them. Drop the additional tenants, do the import, and then recreate them.

PUBLIC
95
To configure new tenant databases, follow the workflow outlined in Using Dynamic Tiering with Multitenant
Databases [page 86].
In this section:
Import SAP HANA Delivery Units (DUs) [page 96]
Use the hdbupdrep utility to manually import the SAP HANA DUs.
Related Information
Using Dynamic Tiering with Multitenant Databases [page 86]
4.9.1 Import SAP HANA Delivery Units (DUs)

Use the hdbupdrep utility to manually import the SAP HANA DUs.
Context
hdbupdrep imports all of the SAP HANA DUs, not just those missing.
Procedure
1. Log on to the SAP HANA host as the <sid>adm.
2. Navigate to /usr/sap/<sid>/SYS/global/hdb/install/bin.
3. Execute hdbupdrep.
4. Accept the database user name and enter the password.
The SAP HANA DUs are imported.
96
PUBLIC

4.10 Using Multitenant Databases with Same Host

Deployment
You can use dynamic tiering with multitenant databases in a same host deployment.
Note
All limitations pertaining to a same host deployment apply to using multitenant databases in a same host
deployment. See Installing Same Host Deployment in the SAP HANA Dynamic Tiering: Installation and
Update Guide.
If the tenant databases to use dynamic tiering reside on the same host as SAP HANA, only one of the tenants
can use the dynamic tiering esserver service running on the SAP HANA host. Each remaining tenant
database using dynamic tiering must use its own dedicated host for the esserver service. For example,
tenant databases DB1 and DB2 reside on SAP HANA Host1. If you wanted to configure these tenants to use
dynamic tiering, you would require a second host, Host2. You would then provision the esserver service on
Host1 to DB1 and the esserver service on Host2 to DB2.
If the tenant databases using dynamic tiering reside on different hosts than the SAP HANA host, each tenant
can use the same esserver service on the SAP HANA host. For example, tenant databases DB3 and DB4
reside on Host3 and Host4, respectively. SAP HANA and the esserver reside on Host1. You would provision
the same esserver service on Host1 to DB3 on Host3 and DB4 on Host4.

PUBLIC
97
Troubleshooting
Familiarize yourself with troubleshooting tools and tracing features of SAP HANA dynamic tiering. Use this
section as a reference to identify and resolve configuration and operation issues.
In this section:
Tools and Tracing [page 98]
This section gives you an overview of tools and tracing options for dynamic tiering troubleshooting.
Configuration Issues [page 100]
Use this section to identify and resolve issues for extended storage configuration, internal
communications with the SAP HANA host, or the SAP HANA delivery units.
Operational Issues [page 103]
Use this section to identify and resolve issues with dynamic tiering transactions, backup, and recovery.
5.1
Tools and Tracing
This section gives you an overview of tools and tracing options for dynamic tiering troubleshooting.
In this section:
Dynamic Tiering Administration User [page 98]
SAP HANA dynamic tiering supports an administration user to help troubleshoot issues on the
dynamic tiering host.
Dynamic Tiering Stack File [page 99]
When the landscape has dynamic tiering installed, a full system dump includes the stack of the
esserver process.
Sample Query Plan Showing Dynamic Tiering [page 99]
You can use the plan visualizer to analyze query plans in systems with dynamic tiering.
5.1.1 Dynamic Tiering Administration User

SAP HANA dynamic tiering supports an administration user to help troubleshoot issues on the dynamic tiering
host.
Always perform troubleshooting with this user under the guidance of the SAP support team and remove this
user after troubleshooting.
Execution of these statements requires the EXTENDED STORAGE ADMIN system privilege.
98
PUBLIC

Troubleshooting
To create the user, run this SQL statement:

ALTER EXTENDED STORAGE CREATE ADMIN USER ES_ADMIN PASSWORD admin123 FORCE
PASSWORD CHANGE OFF
To remove the user, run this SQL statement:
ALTER EXTENDED STORAGE DROP ADMIN USER ES_ADMIN
5.1.2 Dynamic Tiering Stack File

When the landscape has dynamic tiering installed, a full system dump includes the stack of the esserver
process.
The stack file esserverinfo.txt file is included in the .gzip file generated for the system dump by SAP
HANA Studio under:
HDB<instance_no>/<hostname>/trace/ where <hostname> is the dynamic tiering host.
5.1.3 Sample Query Plan Showing Dynamic Tiering

You can use the plan visualizer to analyze query plans in systems with dynamic tiering.
Analysis of the following query is visualized in the figure below:
Sample Code
select count(*)
from tpcds.store_sales,tpcds.store_returns,tpcds.web_sales,
tpcds.web_returns,tpcds.promotion, tpcds.date_dim pdate
where p_promo_name in ('ought', 'able','pri')
and pdate.d_year in (2000,2001)
and pdate.d_date_sk between p_start_date_sk and p_end_date_sk
and p_promo_sk=ss_promo_sk
and p_promo_sk=ws_promo_sk
and ss_ticket_number = sr_ticket_number
and ws_order_number = wr_order_number

Troubleshooting
PUBLIC
99
Figure 4: Plan Visualization Fragment
5.2
Configuration Issues
Use this section to identify and resolve issues for extended storage configuration, internal communications
with the SAP HANA host, or the SAP HANA delivery units.
In this section:
Cannot Create Extended Storage Configuration [page 101]
Issue: Creation of extended storage from the SAP HANA cockpit Dynamic Tiering Configuration
wizard fails if a previous attempt failed.
Cannot Communicate with SAP HANA Host [page 101]
Issue: Problems with internal communications may prevent communication with the SAP HANA host.
Missing Features in SAP HANA Cockpit [page 102]
Issue: The applications accessed through SAP HANA cockpit are installed as separate delivery units
(DUs). Some SAP HANA cockpit functionality might be unavailable if you are missing SAP HANA DUs.
100
PUBLIC

Troubleshooting
5.2.1 Cannot Create Extended Storage Configuration

Issue: Creation of extended storage from the SAP HANA cockpit Dynamic Tiering Configuration wizard fails if
a previous attempt failed.
An error message like the following appears:
ES config create failed: Configuration is already running
This error is valid when multiple users try to create extended storage at the same time. However, if the error
occurs after the failure of a previous attempt to create extended storage, perform the following steps.
Solution:
In the SAP HANA studio or another SQL tool, enter:
SELECT * FROM
"SAP_HANA_TIERING"."sap.hana.tiering.data::HDT_VALUES"
If you see an entry with DT_CONFIG and status RUNNING, run this SQL command:
DELETE FROM
"SAP_HANA_TIERING"."sap.hana.tiering.data::HDT_VALUES"
Return to the SAP HANA cockpit, click the Dynamic Tiering Configuration tile, and retry creating the
configuration.
5.2.2 Cannot Communicate with SAP HANA Host

Issue: Problems with internal communications may prevent communication with the SAP HANA host.
Solution:
Internal communications between the SAP HANA dynamic tiering host and the SAP HANA database are
secured by the SSL protocol and certificate mutual authentication.
Follow the instructions in this topic to resolve issues.
Sample Connectivity Error
ALTER TABLE "DT_SCHEMA"."TAB_A" USING EXTENDED STORAGE
The indexserver trace shows following error:
[4863]{207439}[95/10731633] 2015-05-06 17:50:26.455132 e FedTrace
odbcaccess.cpp(03672) : ODBC error: connected: 1 state: HY000 code: -656 [SAP][ODBC
Driver]Unable to connect to server 'HANA': [SAP AG][LIBODBCHDB SO][HDBODBC] General
error;1033 error while parsing protocol
This error indicates the dynamic tiering host could not communicate with SAP HANA to fetch the contents of
the table required for the conversion.
Enable Traces

Troubleshooting
PUBLIC
101
Collect the required traces and contact SAP Support to resolve the communication problem. Enable these
traces before running the ALTER TABLE statement again:
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini','SYSTEM') SET
( 'authentication','SapLogonTicketTrace' ) = 'true' WITH RECONFIGURE;
('trace','saptracelevel')='3' WITH RECONFIGURE;
('trace','authentication')='debug' WITH RECONFIGURE;
('trace','crypto')='debug' WITH RECONFIGURE;
Check for Different Certificate Sizes
Certificate sizes on the SAP HANA host and dynamic tiering host should be the same. Different certificate
sizes indicate an inconsistency in the certificates that could lead to connection problems. Compare the
certificate sizes.
On the dynamic tiering host, log in as SIDadm and execute these commands:
1. cdglo
2. cd security/rsecssfs/data
3. ls -al sap_system_pki_instance.*
Note the file sizes. The file sizes should match those on the SAP HANA host.
On the SAP HANA host, log in as SIDadm and execute these commands:
1. cdhdb
2. cd $SECUDIR
3. ls -al sap_system_pki_instance.*
Note the file sizes. These sizes should match those on the dynamic tiering host.
Note
For these certificates to work correctly, the clocks on the SAP HANA and dynamic tiering hosts must be
synchronized. To ensure that the clocks are synchronized, run the date command on each host.
5.2.3 Missing Features in SAP HANA Cockpit

Issue: The applications accessed through SAP HANA cockpit are installed as separate delivery units (DUs).
Some SAP HANA cockpit functionality might be unavailable if you are missing SAP HANA DUs.
Solution:
Verify all DUs are imported.
1. In a SQL console, connect to the system as the SYSTEM user.
2. Execute:
select * from "_SYS_REPO"."DELIVERY_UNITS"
The result set should return at least 21 rows.
102
PUBLIC

Troubleshooting
If the result set is empty, or less than 21, you are missing SAP HANA DUs, see Import SAP HANA DUs.
If the HANA_TIERING DU is not included in the result set, see Importing Dynamic Tiering Delivery Units to a
New Tenant Database.
Related Information
5.3
Operational Issues
Use this section to identify and resolve issues with dynamic tiering transactions, backup, and recovery.
In this section:
Cannot Create Extended Store Table with Delta Enabled [page 104]
Issue: Creating an extended store table with the DELTA ENABLED parameter fails because the store
isn't delta enabled.
Verifying Imported Delivery Units (DUs) [page 104]
Issue: When importing DUs, an error occurs and the import fails to complete. Some SAP HANA cockpit
functionality might be unavailable if you are missing SAP HANA DUs.
Importing an Extended Table into HANA Without Dynamic Tiering Returns Error [page 105]
Issue: When you import an extended table into an SAP HANA system with no dynamic tiering
configured, you receive an error and the import fails because SAP HANA dynamic tiering does not exist
on the system where you are importing the table.
Dynamic Tiering Operations Moving Large Amounts of Data Fail [page 105]
Issue: Dynamic tiering operations that move a lot of data fail with an error if executing the operation
exhausts all large memory used to stage extended tables.
Out of Space Errors for Delta Dbspace [page 106]
Issue: Certain transactions, such as bulk loads, may run longer than expected for their workload.
Query Returns "You have run out of space in <DBSPACE_NAME> DBSpace" Error [page 106]
Issue: A query that involves an extended storage object can fail with the error "[SAP][ODBC
Driver]You have run out of space in <DBSPACE_NAME> DBSpace."
Writing Date or Time Data to Extended Storage Violates Unique Constraint [page 107]
Issue: When writing date- or time-related data to an extended table, you receive an error indicating a
unique constraint has been violated.
Backup Cannot Complete [page 107]
Issue: Backup does not complete because a log backup for point-in-time recovery is underway.
Point-In-Time Recovery Fails When the Restore is Unable to Find a Log Backup on the Latest Timeline
[page 108]
Issue: During point-in-time (PIT) recovery, SAP HANA dynamic tiering recovery fails with an error
message.

Troubleshooting
PUBLIC
103
Point-in-Time Recovery Leaves Dynamic Tiering Service in Utility Mode [page 108]
Issue: An issue may occur on systems with SAP HANA dynamic tiering option installed when
performing a point-in-time recovery from a backup where dynamic tiering was not installed.
5.3.1 Cannot Create Extended Store Table with Delta

Enabled
Issue: Creating an extended store table with the DELTA ENABLED parameter fails because the store isn't delta
enabled.
[SAP][ODBC Driver]Cannot enable RLV storage for table '<table name>'. An RLV
dbspace does not exist.
Solution:
Specify DELTA ENABLED when creating extended storage before you can use the DELTA ENABLED parameter
to create an extended store table.
Note
Once you create extended storage, you cannot change the delta option setting.
5.3.2 Verifying Imported Delivery Units (DUs)

Issue: When importing DUs, an error occurs and the import fails to complete. Some SAP HANA cockpit
functionality might be unavailable if you are missing SAP HANA DUs.
Verify all DUs are imported.
Solution:
1. In a SQL console, connect to the system as the SYSTEM user.
2. Execute:
select * from "_SYS_REPO"."DELIVERY_UNITS"
The result set should return at least 21 rows.
If the result set is empty, or less than 21, you are missing SAP HANA DUs, see Import SAP HANA DUs.
If the HANA_TIERING DU is not included in the result set, see Importing Dynamic Tiering Delivery Units to a
New Tenant Database.
Related Information
104
PUBLIC

Troubleshooting
5.3.3 Importing an Extended Table into HANA Without

Dynamic Tiering Returns Error
Issue: When you import an extended table into an SAP HANA system with no dynamic tiering configured, you
receive an error and the import fails because SAP HANA dynamic tiering does not exist on the system where
you are importing the table.
An error like the following appears:
SAP DBTech JDBC: [2048]: column store error: table import failed: [30111] Import
failed (could not execute create statement);object=SAPKIT:/BI0/
B0054680000en,invalid data source name: __esstore$ at ptime/query/checker/
check_table.cc:321
However, you can import the table as a row table in order to preserve its data. Use the
enable_convert_es_to_row_tables parameter.
Solution:
Import the extended table as a row table:
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini',
'SYSTEM') SET ('import_export', 'enable_convert_es_to_row_tables')
= 'true' WITH RECONFIGURE;
5.3.4 Dynamic Tiering Operations Moving Large Amounts of

Data Fail
Issue: Dynamic tiering operations that move a lot of data fail with an error if executing the operation exhausts
all large memory used to stage extended tables.
All large memory has been used, allocation canceled
This occurs if the system has insufficient memory for the operation, or other processes running on the system
are utilizing large amounts of it, leaving insufficient available for the dynamic tiering operation.
Such operations include converting tables to extended tables, loading tables using the IMPORT command,
performing large bulk inserts into extended tables, or altering an extremely large extended table to DELTA
ENABLED, into delta extended table.
Solution:
In the esserver.ini file, in the Startup section, increase the value of the load_memory_mb parameter and
restart the esserver service.

Troubleshooting
PUBLIC
105
5.3.5 Out of Space Errors for Delta Dbspace

Issue: Certain transactions, such as bulk loads, may run longer than expected for their workload.
Check the logs for an error like the following, which indicates a snapshot versioning issue with a dynamic
tiering transaction:
(rv_PersistenceException); SQLCode: -1009170, SQLState: 'QSB66', Severity: 14
esserver_cj7635.12345.004.trc:[00014]{0000030233}[-1/-1] 2015-04-13 19:20:46.037921
i esserver UNKNOWN(0) : [20223]: You have run out of space in ES_DELTA DBSpace.
Long-running transactions may cause dynamic tiering to run out of space, but do not trigger SAP HANA Alerts
73, 74, or 75.
Solution:
1. Identify the statement and connection that cause the issue.
Example:
Run the following statement in the SAP HANA SQL console:
SELECT * FROM SYS.M_TRANS_TOKENS WHERE ES_SNAPSHOT_COUNT > 0 ORDER BY
ES_SNAPSHOTS
Output column ES_SNAPSHOTS returns two values. The first value, 1024, is the volume ID for extended
storage. The second value, 911322, identifies the extended storage snapshot. The column
LOGICAL_CONNECTION_ID holds the connection identifier of the blocked transaction. If the query returns
multiple rows, choose the oldest running dynamic tiering transaction.
For the purposes of this example, the table only shows selected columns from the results of the select
statement.
HOST
PORT
TRANSAC
TION_ID
LOGICAL_CON
NECTION_ID
ES_SNAP
SHOT_COUNT
ES_SNAPSHOT
hostDT4a
20,010
58
301,456
(1024,911322)
2. To kill the blocking connection, use:ALTER SYSTEM DISCONNECT SESSION 'CONNECTION_ID' where
<CONNECTION_ID> is the value in the LOGICAL_CONNECTION_ID column.
In this example, corrective action is to kill long running transactions. It is also possible that the user might have
actually run out of space, and you must add more dbspace or additional dbfiles.
5.3.6 Query Returns "You have run out of space in

<DBSPACE_NAME> DBSpace" Error
Issue: A query that involves an extended storage object can fail with the error "[SAP][ODBC Driver]You have
run out of space in <DBSPACE_NAME> DBSpace."
The <DBSPACE_NAME> identifies which dbspace is out of memory. You can query the complete list of
configured dbspaces in the M_ES_DBSPACES monitoring view, or using the SAP HANA cockpit. For a list of
dbspaces created by default, see Types of Dbspaces.
This error occurs if one of the dbspaces is full and requires you to allocate additional space in order to
complete a failed query or action.
Solution:
106
PUBLIC

Troubleshooting
Identify the dbspace that requires additional space, then add one or more files to that dbspace file, as
described in Add a Dbspace File, or enlarge a dbspace file, as described in Enlarge a Dbspace File, in the SAP
HANA Dynamic Tiering: Administration Guide.
Note
If the dbspace name in the error message does not exactly correlate with names shown, you can reliably
identify the correct dbspace by checking the name and type. For example the name of the main system
dbspace contains SYSTEM_MAIN.
Related Information
5.3.7 Writing Date or Time Data to Extended Storage

Violates Unique Constraint
Issue: When writing date- or time-related data to an extended table, you receive an error indicating a unique
constraint has been violated.
Solution:
In your SAP HANA data, use NULL instead of EMPTY.
For date and time data types, SAP HANA supports a special EMPTY value that is distinct from NULL. SAP
HANA dynamic tiering does not support the EMPTY value.
5.3.8 Backup Cannot Complete

Issue: Backup does not complete because a log backup for point-in-time recovery is underway.
A 447 error like the following appears:
backup could not be completed [110112] Extended storage backup error: [SAP][ODBC Driver]There is already
a backup or selective restore in progress. \n -- (dblib/db_backupID.cxx 2213)
Point-in-time log backups are automatic; the issue can occur without another user running a backup.
Solution:
Query the backup catalog for the state of all log backups that are finished or in progress:
SELECT state_name FROM m_backup_catalog MB,
m_backup_catalog_files MBF
WHERE
MB.backup_id = MBF.backup_id

Troubleshooting
PUBLIC
107
AND
service_type_name = 'esserver'
AND
entry_type_name = 'log backup'
If a state name in the output displays as "prepared" or "running," then a dynamic tiering log backup is in
progress.
When you find the finish entry, the log backup is complete and you can run the data backup. You can query the
views M_BACKUP_CATALOG and M_BACKUP_CATALOG_FILES for dynamic tiering data and log backups just
as you do for SAP HANA database data and log backups.
5.3.9 Point-In-Time Recovery Fails When the Restore is

Unable to Find a Log Backup on the Latest Timeline
Issue: During point-in-time (PIT) recovery, SAP HANA dynamic tiering recovery fails with an error message.
[18847]{-1}[-1/-1] 2015-05-25 23:44:04.143136 i FedTrace
FederationContext.cpp(00634) : FederationException created 0x00007feee3f6bd10:
Exception 10000: (__esstore$) [SAP][ODBC Driver]RESTORE unable to find a log backup
on the latest timeline
This behavior occurs if the timestamp provided is very close to that of the data backup and no transactions
need replaying from the log backups.
Solution:
Perform a data only recovery.
Related Information
5.3.10 Point-in-Time Recovery Leaves Dynamic Tiering

Service in Utility Mode
Issue: An issue may occur on systems with SAP HANA dynamic tiering option installed when performing a
point-in-time recovery from a backup where dynamic tiering was not installed.
1. Install an SAP HANA system and set up a database.
2. Perform a full database backup.
3. Add the dynamic tiering service, and provision the dynamic tiering service to a database.
4. Recover the database from an early full backup without using the delta backup option.
When recovery completes, the dynamic tiering service runs in utility mode.
108
PUBLIC

Troubleshooting
Solution: Perform a full database backup after adding the dynamic tiering service to the HANA system to allow
the recovery of the database to work properly.
Perform a full database backup after adding the dynamic tiering service to the HANA system to allow the
recovery of the database to work properly.
The section Create Extended Storage advises a full backup immediately after you create extended storage.
If a full database backup is not performed after adding the dynamic tiering service to the HANA system, and
the dynamic tiering service is running in utility mode, re-provision the dynamic tiering service to the database
to resolve the issue.

Troubleshooting
PUBLIC
109
Glossary
This glossary describes many commonly used technical terms for the SAP HANA dynamic tiering option.
Term
Description
Cold data
Data stored on-disk.
Column store
Contains in-memory HANA tables.
Column-store table
A HANA table kept in (or that resides in) memory.
Dbspace
A logical name for a container of files or raw partitions within extended storage.
Default store
For dynamic tiering, refers to the HANA column store.
Delta
For dynamic tiering, refers to row-level versioning.
Delta merge
A process that transforms delta storage data into a format optimized for read
performance and memory consumption, and transfers it to main storage.
Delta store
For dynamic tiering, write-optimized, in-memory store that works with the ex
tended store. Delta stores use row-level versioning to allow concurrent table
changes by multiple users without transaction lock waits.
esserver
The name of the dynamic tiering service.
Extended storage
Contains on-disk dynamic tiering extended tables.
Extended table
A dynamic tiering table kept on (or that resides on) disk.
hdbesserver
The executable for esserver.
Hot data
Data stored in memory.
Import
You can import catalog objects (tables, views, synonyms, sequences, proce
dures) that have previously been exported from dynamic tiering by using the IM
PORT statement.
This differs from the IMPORT FROM statement, which imports external data
from a CSV file into an existing extended store table.
Main storage
The part of the column store that contains the main part of the data, compressed
and optimized for read access.
Row-level versioning (RLV)
Allows more than one user to modify the same table concurrently.
Warm storage
Data stored on disk.
110
PUBLIC

Glossary
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be
a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however,
does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of
SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as
"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun
does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does
not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any
damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for
transparency (see: http://help.sap.com/disclaimer).

Important Disclaimers and Legal Information
PUBLIC
111
go.sap.com/registration/
contact.html
2016 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.
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.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Dynamic Tiering Option Administration Guide en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Dynamic Tiering Option Administration Guide en

Загружено:

Авторское право:

Доступные форматы

Administration Guide

SAP HANA dynamic tiering 1.0 SP 12

SAP HANA Dynamic Tiering: Administration Guide

SAP HANA Dynamic Tiering Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Authorization for Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Tools for Administration and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Open SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Tile Catalog for SAP HANA Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Managing the Dynamic Tiering Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Licensing for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Managing Extended Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Managing Space for Extended Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Managing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Importing and Exporting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Monitoring Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

SAP HANA Dynamic Tiering: Administration Guide

Monitoring Dynamic Tiering in the SAP HANA Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Backup and Recovery for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Dynamic Tiering High Availability (Failover). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configure Private Internal Communication Using the Command-Line Interface. . . . . . . . . . . . . . . . 82

Configure Private Internal Communication Using the Graphical User Interface. . . . . . . . . . . . . . . . . 84

Using Dynamic Tiering with Multitenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Verify Configuration of the SAP HANA Core System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Adding the Dynamic Tiering Host to a Multitenant Database System. . . . . . . . . . . . . . . . . . . . . . . . 89

Prepare the Tenant Database Resources for Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Provision the Dynamic Tiering Service to a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Failing Over with Multitenant Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Import Dynamic Tiering Delivery Units to a New Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . .93

Create Extended Storage on the Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Remove Dynamic Tiering from a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Converting Multitenant Database Containers Using Dynamic Tiering. . . . . . . . . . . . . . . . . . . . . . . .95

Using Multitenant Databases with Same Host Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Tools and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuration Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Operational Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

SAP HANA Dynamic Tiering: Administration Guide

Cannot Create Extended Store Table with Delta Enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

SAP HANA Dynamic Tiering: Administration Guide

SAP HANA Dynamic Tiering: Administration Guide

SAP HANA Dynamic Tiering Architecture

Shared Resources Location

SAP HANA Dynamic Tiering: Administration Guide

Dynamic Tiering for Tenant Databases [page 7]

1.1.1 Dynamic Tiering for Tenant Databases

SAP HANA Dynamic Tiering: Administration Guide

Authorization for Administration Tasks

Dynamic Tiering Administration Tasks

Create, alter, or drop the extended storage configuration,

System privilege EXTENDED STORAGE ADMIN or SERVICE

System configuration tasks require system privileges.

Change the properties of an extended storage engine as de

System privilege EXTENDED STORAGE ADMIN or INIFILE

SAP HANA Dynamic Tiering: Administration Guide

1.2.1 Configure Access to Content in SAP HANA Cockpit

Required for access to SAP HANA cockpit.

Required to configure the SAP HANA Database Ad

Allows viewing only of SAP HANA Database Adminis

Allows administration of SAP HANA Database Ad

Includes the role of

Required to configure the SAP HANA dynamic tiering

Allows viewing only of SAP HANA dynamic tiering

Required to manage SAP HANA dynamic tiering cat

Includes the role of