Академический Документы
Профессиональный Документы
Культура Документы
PUBLIC
Content
Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1
1.2
1.3
1.4
1.5
System Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1
2.2
2.3
2.4
2.5
2.6
Computing Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.7
2.8
PUBLIC
2.10
Security Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.1
3.2
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
5.1
5.2
5.3
PUBLIC
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
PUBLIC
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
PUBLIC
1.1
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
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
Related Information
SAP HANA Security Guide
Figure 2: SAP HANA System with Dynamic Tiering for Tenant Databases
PUBLIC
Related Information
Using Dynamic Tiering with Multitenant Databases [page 86]
SAP HANA Administration Guide
1.2
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
Administration Guide.
Required Authorization
Required Authorization
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
SAP HANA Administration Guide
PUBLIC
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
ministration catalog.
tration tiles.
sap.hana.admin.roles::Administrator
sap.hana.tiering.roles::Monitoring
sap.hana.tiering.roles::Administrator
PUBLIC
Related Information
SAP HANA Administration Guide
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
Use the SAP HANA cockpit and the SAP HANA studio to administer and monitor dynamic tiering.
Note
Before you begin other tasks in Related Links, see "Configure Access to Content in the SAP HANA Cockpit."
10
PUBLIC
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]
SAP HANA Administration Guide
1.4
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.
PUBLIC
11
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
http://<host>:<port>/sap/hana/admin/cockpit
Tenant database
http://<alias_DNS_name_of_tenant_DB>:<port>/sap/hana/
admin/cockpit
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
SAP HANA Administration Guide
12
PUBLIC
1.5
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
dbspace files.
PUBLIC
13
Tile
Description
Additional Requirements
dbspace files.
14
PUBLIC
Tile
Description
Additional Requirements
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
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.
Configuring Dynamic Tiering Properties (INI Files) [page 22]
INI files contain properties for configuring SAP HANA dynamic tiering.
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
\_ hdbesserver -n esRH100 -x
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.
Description
None
Master
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.
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.
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
2. Right-click the dynamic tiering service (esserver) and choose the required option:
Option
Description
Stop...
Kill...
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
View the Status of the Dynamic Tiering Service [page 18]
SAP HANA SQL and System Views Reference
PUBLIC
21
Description
Default
System
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
22
PUBLIC
Description
Min/Max Value
Default Value
catalog_cache
0/-
32000000 bytes
checkpoint_interval
0/-
60 minutes
delta_memory_mb
0/-
2048MB
load_memory_mb
0/-
2048MB
main_cache_mb
0/-
1024MB
1 - 1001
50
max_concur
rent_queries
0/-
32
num_partition_buf
fer_cache
0 - 256
None. Value is de
termined at run
time based on the
number of CPUs,
and is not user visi
ble.
num_threads
4 - 4096
600
0/-
256
Description
Min/Max Value
Default Value
maxfiles
0-64 (inclusive)
10
maxfilesize
0 - 2047 (inclusive),
in MB
10000000
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
Depends on space
available
PUBLIC
23
Name
Description
Values
Default Value
statement_type
SQL | HOSTVARS |
PLAN | PROCE
DURES | TRIGGERS |
OTHER | BLOCKS |
REPLACE | ALL |
NONE
NONE
tracefile
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
The esserver.ini file defines configuration parameters for dynamic tiering services.
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.
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
If necessary, restart the system.
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
Related Information
SAP HANA Administration Guide
SAP HANA SQL and System Views Reference
26
PUBLIC
2.1.5.1.2
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.
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.
System
Privileges Required
DATABASE 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
Database
Note
The disabled icon (
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
If necessary, restart the system.
28
PUBLIC
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
Database
Note
For complete syntax and requirements, see ALTER SYSTEM ALTER CONFIGURATION Statement
[Dynamic Tiering] in the SAP HANA SQL and System Views Reference guide.
This example changes the setting of the main_cache_mb in the startup section.
Level
How
System
Database
Related Information
SAP HANA Administration Guide
SAP HANA SQL and System Views Reference
PUBLIC
29
2.1.5.1.3
You can restore changed configuration parameters in the esserver.ini file to default values.
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 configuration file are listed.
3. Expand the required section.
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
1.
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.
30
PUBLIC
Procedure
1. In a SQL console, connect to the system to be modified.
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
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
Related Information
SAP HANA SQL and System Views Reference
PUBLIC
31
2.1.5.1.4
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.
Select
System level
Database
32
PUBLIC
) respectively.
5. To delete a user-defined value and restore the default value, you can choose one of the following methods:
Procedure
Result
1.
Note
If you added a new parameter to a section, Delete de
letes the parameter.
The user-defined value(s) are cleared and the default
value(s) are re-applied.
Related Information
SAP HANA SQL and System Views Reference
2.1.5.2
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
dynamic_tiering.create_extended_storage
true
dynamic_tiering.drop_extended_storage
true
dynamic_tiering.alter_extended_storage
true
PUBLIC
33
Property
Default
Operation
dynamic_tiering.alter_table_type
true
dynamic_tiering.bulk_insert_optimization
true
dynamic_tiering.query_plan_relocation
true
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
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
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
If necessary, restart the system.
PUBLIC
35
Level
How
System
Database
Note
For complete syntax and requirements, see ALTER SYSTEM ALTER CONFIGURATION Statement
[Dynamic Tiering] in the SAP HANA SQL and System Views Reference guide.
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
SAP HANA SQL and System Views Reference
36
PUBLIC
2.1.5.2.2
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.
) respectively.
3. To delete a user-defined value and restore the default value, you can choose one of the following methods:
PUBLIC
37
Procedure
Result
1.
Note
Related Information
SAP HANA SQL and System Views Reference
2.2
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
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.
PUBLIC
39
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
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.
Note
If you create extended storage, you cannot enable data volume encryption in the SAP HANA database.
Procedure
1. Open the SQL console.
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
Authorization for Administration Tasks [page 8]
Add a Dbspace File [page 45]
Backing Up SAP HANA Databases With Dynamic Tiering [page 70]
View the Status of the Dynamic Tiering Service [page 18]
SAP HANA Administration Guide
SAP HANA SQL and System Views Reference
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
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.
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
Authorization for Administration Tasks [page 8]
SAP HANA SQL and System Views Reference
PUBLIC
43
2.4
Type
Data Stored
ES_SYSTEM
MAIN
ES_USER
MAIN
44
PUBLIC
Files Contained by
Dbspace
One or more
Dbspace Name
Type
Data Stored
Files Contained by
Dbspace
ES_DELTA
RLV
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
ES_SYSTEM
ES_TEMP
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.
Procedure
1. Open the SQL console.
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
Drop a Dbspace File [page 49]
Enlarge a Dbspace File [page 47]
Types of Dbspaces [page 44]
SAP HANA SQL and System Views Reference
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.
PUBLIC
47
Procedure
1. Open the SQL console.
2. Execute the ALTER EXTENDED STORAGE ALTER DBSPACE statement.
ALTER EXTENDED STORAGE ALTER DBSPACE <dbspace_name>
ALTER FILE <logical_filename>
ADD <add_file_size> {KB|MB|GB|TB}
The <dbspace_name> must be ES_SYSTEM, ES_USER, or ES_TEMP.
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
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
Add a Dbspace File [page 45]
Authorization for Administration Tasks [page 8]
Drop a Dbspace File [page 49]
Types of Dbspaces [page 44]
SAP HANA SQL and System Views Reference
48
PUBLIC
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
A status message displays.
PUBLIC
49
Procedure
1. Open the SQL console.
2. Execute the ALTER EXTENDED STORAGE ALTER DBSPACE statement with the DROP FILE clause.
ALTER EXTENDED STORAGE ALTER DBSPACE <dbspace_name>
DROP FILE <logical_file_name>
The <dbspace_name> must be ES_SYSTEM, ES_USER, or ES_TEMP.
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
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
Types of Dbspaces [page 44]
SAP HANA SQL and System Views Reference
Description
Dbspace Name
Name of the dbspace to which you are adding a file. You can add files to MAIN, TEMPORARY, and
RLV dbspaces.
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.
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.
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
PUBLIC
51
Use the SAP HANA studio graphical interface to create, alter, convert, and drop extended tables.
2.5.1.1
52
PUBLIC
2.5.1.2
The supported data types of an extended store table differ slightly from a regular SAP HANA column store
table.
Datatype
Supported
Remarks
DATE
YES
Note
NOTE: Extended store tables do not support the empty string
as a valid value.
TIME
YES*
SECONDDATE
YES
TIMESTAMP
YES*
Domain is compatible.
TINYINT
YES
SMALLINT
YES
INTEGER
YES
BIGINT
YES
SMALLDECIMAL
YES*
DECIMAL
YES*
Domain is different.
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*
ALPHANUM
YES*
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.
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.
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
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.
Related Information
SAP HANA Administration Guide
2.5.1.4
To move data to warm storage, convert appropriate column tables into extended store tables.
Prerequisites
You have the role sap.hana.admin.roles::Monitor.
You have the role sap.hana.tiering.roles:Administrator.
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
SAP HANA Administration Guide
2.5.1.5
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
1. Open the SQL console.
56
PUBLIC
Syntax
Create
See Also
Note
Review Extended Store
Table Limitations before
proceeding. Conversion
fails on HANA tables
created with clauses not
supported in extended
store tables.
Enable/Disable delta on an
existing extended store ta
ble
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
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
SAP HANA SQL and System Views Reference Guide
2.5.1.6
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
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
Related Information
Enable/Disable Delta on an Existing Extended Store Table [page 59]
2.5.1.6.2
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
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
PUBLIC
2.5.1.6.4
Use the SAP HANA studio graphical interface to alter and delete extended store tables.
Prerequisites
The specified table is delta-enabled.
PUBLIC
61
Procedure
1. Open the SQL console.
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
SAP HANA SQL and System Views Reference Guide
2.7
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:
Extended Store Tables [page 64]
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.1
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
SAP HANA SQL and System Views Reference Guide
2.7.1.2
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
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.
See SAP Note 2050807
tables.
for behavior differences when loading data from SAP HANA and extended store
PUBLIC
65
2.8
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.
Catalog
SYS
Views .
66
PUBLIC
Related Information
Open SAP HANA Cockpit [page 11]
2.8.2.1
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
Use
Dbspace Status
unavailable.
See Monitoring Alerts and Alert Details in the SAP HANA Administration Guide.
PUBLIC
67
Related Information
SAP HANA Administration Guide
2.8.2.2
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
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 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.
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
Administration Guide.
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]
After the first data backup, a database with dynamic tiering automatically makes a log backup every 15
minutes. Change the log backup interval to adjust the backup frequency.
Related Information
Configuring Dynamic Tiering Properties (INI Files) [page 22]
Finding and Checking Backups for Recovery [page 73]
Recovering SAP HANA Databases with Dynamic Tiering [page 74]
SAP HANA Administration Guide
Backup Cannot Complete [page 107]
2.9.1.1
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
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
Recovering SAP HANA Databases with Dynamic Tiering [page 74]
2.9.1.3
After the first data backup, a database with dynamic tiering automatically makes a log backup every 15
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
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 log backup interval to ALTER SYSTEM ALTER CONFIGURATION
5 minutes.
('esserver.ini','SYSTEM') SET ('database',
Related Information
Change an esserver.ini Property - Single Database [page 24]
Related Information
SAP HANA Administration Guide
PUBLIC
73
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.
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
Finding and Checking Backups for Recovery [page 73]
SAP HANA Administration Guide
2.9.3.1
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.
PUBLIC
75
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
Related Information
SAP HANA Administration Guide
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
1. In the SAP HANA studio Administration console, do one of:
Database Type
Action
Single database
Tenant database
2. Choose
Landscape
3. Click the
Hosts .
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.
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.
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
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.
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 SQL and System Views Reference
SAP HANA Security Guide
3.1
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
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
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
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
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
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
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
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 Dynamic Tiering: Installation and Update Guide
SAP HANA Server and Update Installation Guide
SAP HANA Administration Guide
4.1
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
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
SAP HANA Administration Guide
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
SAP HANA Administration Guide
4.2
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
SAP HANA Dynamic Tiering: Installation and Update Guide
PUBLIC
89
4.3
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.
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.
4.4
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
1. In a SQL console, connect to the SYSTEMDB as a user with the DATABASE ADMIN privilege.
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
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
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 .
PUBLIC
93
4.7
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
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
SAP HANA Dynamic Tiering: Administration Guide
94
PUBLIC
4.8
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]
3. In a SQL console, connect to the SYSTEMDB as a user with the DATABASE ADMIN privilege.
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
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]
SAP HANA Administration Guide
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
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
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.
98
PUBLIC
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
PUBLIC
99
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
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;
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini','SYSTEM') SET
('trace','saptracelevel')='3' WITH RECONFIGURE;
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini','SYSTEM') SET
('trace','authentication')='debug' WITH RECONFIGURE;
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini','SYSTEM') SET
('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.
102
PUBLIC
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
Import Dynamic Tiering Delivery Units to a New Tenant Database [page 93]
Import SAP HANA Delivery Units (DUs) [page 96]
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.
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.
Note
Once you create extended storage, you cannot change the delta option setting.
Related Information
Import Dynamic Tiering Delivery Units to a New Tenant Database [page 93]
104
PUBLIC
PUBLIC
105
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.
106
PUBLIC
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
Types of Dbspaces [page 44]
Enlarge a Dbspace File [page 47]
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.
Related Information
Recovering SAP HANA Databases with Dynamic Tiering [page 74]
108
PUBLIC
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.
PUBLIC
109
Glossary
This glossary describes many commonly used technical terms for the SAP HANA dynamic tiering option.
Term
Description
Cold data
Column store
Column-store table
Dbspace
A logical name for a container of files or raw partitions within extended storage.
Default store
Delta
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
Extended storage
Extended table
hdbesserver
Hot data
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.
Allows more than one user to modify the same table concurrently.
Warm storage
110
PUBLIC
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).
PUBLIC
111
go.sap.com/registration/
contact.html