Sap hana server installation guide

PUBLIC
SAP HANA Platform SPS 08
Document Version: 1.0 - 2014-05-28
SAP HANA Server Installation and
Update Guide

Table of Contents
1 SAP HANA Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 SAP HANA Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Before Installing an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 SAP HANA System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 SAP HANA System Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.1 Single-Host System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.2 Multiple-Host (Distributed) System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.3 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3.1 Recommended File System Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
3 Installing an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1 Overview of the LCM Interaction Modes and Parameter Specification Methods. . . . . . . . . . . . . . . . .18
3.2 Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.2.1 Mandatory Installation Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3 Interactive Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
3.3.1 Installing with the Graphical Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.3.2 Installing Interactively from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4 Advanced Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
4.1 Automating SAP HANA System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1.1 Automation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.1.2 Automating with the Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
4.2 Multiple-Host System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.2.1 Multiple-Host System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
4.2.2 Creating a Multiple-Host System During Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5 Updating the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1 Updating an SAP HANA System from a Local Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1.1 Preparing for Update in the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
5.1.2 Prepare for Update Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.1.3 Update an SAP HANA System from a Local Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.2 Updating an SAP HANA System from a Remote Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
5.2.1 Perform an Automated Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3 Updating SAP HANA System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3.1 Update SAP HANA System Components from a Local Host. . . . . . . . . . . . . . . . . . . . . . . 58
5.3.2 Update SAP HANA System Components from a Remote Host. . . . . . . . . . . . . . . . . . . . . 60
6 Parameter Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.1 action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2
P U B L I C
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA Server Installation and Update Guide
Table of Contents

6.2 addhosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.3 autostart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.4 batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.5 certificates_hostmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.6 checkmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.7 client_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
6.8 component_dirs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.9 component_medium. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.10 component_root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.11 components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.12 configfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.13 copy_repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.14 datapath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.15 dump_configfile_template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.16 groupid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.17 help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.18 home. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
6.19 host_agent_package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
6.20 hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.21 install_hostagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.22 install_ssh_key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.23 internal_network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.24 list_systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
6.25 logpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.26 max_mem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.27 number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.28 print_timezones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.29 read_password_from_stdin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.30 repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.31 restrict_max_mem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
6.32 root_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
6.33 sapmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.34 scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.35 shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.36 sid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
6.37 storage_cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.38 studio_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.39 studio_repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.40 system_usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.41 system_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.42 timezone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table of Contents
P U B L I C
© 2014 SAP AG or an SAP affiliate company. All rights reserved. 3

6.43 userid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.44 version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.45 vm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
7 Tutorials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8 Managing the SAP HANA System After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
8.1 Starting and Stopping the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
8.2 Displaying the Process List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.3 Creating a Database User for Update and Rename. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
8.4 Enabling Automatic Start of the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.5 Enable Data Volume Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
8.6 Uninstall the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
10 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
10.1 Configuration File Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10.2 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
11 Important Disclaimers on Legal Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
4
P U B L I C
Table of Contents

1 SAP HANA Installation Overview
This SAP HANA installation guide describes how to install an SAP HANA system with the SAP HANA lifecycle
management tool hdblcm(gui), or update an SAP HANA system using hdblcm(gui) or the lifecycle manager.
The SAP HANA hdblcm tool is used to install either individual or multiple SAP HANA components in
combination with the server. Compared to previous SAP HANA installers, the SAP HANA hdblcm tool provides
an efficient and optimized installation path, allowing users to customize their SAP HANA installation by
selecting which components should be installed and updated. It is also now possible to perform installation in
interactive graphical or interactive command line interfaces, as well as configure the SAP HANA installation to
be automated, using command line, the configuration file, and batch mode.
It is worth noting, that the SAP HANA component installation concept has changed significantly with the fast-
paced development of SAP HANA itself. In the early releases, the SAP HANA components had to be installed
individually, which proved to be a time-consuming task. More recently, the SAP HANA unified installer was
developed to streamline the installation process by installing all required components from one call to the
installer. As of SPS 08, the unified installer is no longer shipped with SAP HANA.
With SAP HANA SPS 07, the SAP HANA hdblcm tool was introduced to offer the efficiency of installing all
components at one time, while providing further flexibility to customize and automate the installation. The
components can now be installed, upgraded, or uninstalled from one tool, in both command-line or graphical
interface.
As of SAP HANA SPS 08, it is possible to also perform post-installation configurations tasks, such as renaming
the system, adding or removing hosts, and reconfiguring the system, using hdblcm(gui). For more
information, see the SAP HANA Administration Guide.
Before starting the installation of SAP HANA, make sure that you have reviewed the SAP HANA Master Guide.
Related Information
SAP HANA Master Guide
SAP HANA Administration Guide
1.1 SAP HANA Software Components
The SAP HANA Platform Edition is composed of the following components:
● SAP HANA database
● SAP HANA client
● SAP HANA client for Microsoft Excel
● SAP HANA studio (including SAP HANA STUDIO RSA PLUGIN)
● SAPUI5 Tools IDE PLUGIN
● SAP Host Agent
● SAP Solution Manager Diagnostics Agent
SAP HANA Installation Overview
P U B L I C

● SAP HANA information composer
● SAP HANA AFL
● SAP HANA LCApps
● SAP HANA lifecycle manager
● SAP HANA INA Toolkit HTML
● SAP HANA INA Fileloader
● SAP HANA EPM Service
● SAP HANA SHINE cntent
● SAP HANA smart data access
● SAP HANA HW Configuration Check Tool
The SAP HANA Platform Edition is bundled together with other products into editions as license bundles for
special purposes. This is a subset of the available editions:
● SAP HANA Enterprise Edition (including components for data replication and acquisition)
● SAP HANA Real-time-data edition (includes SAP Replication Server, SAP HANA edition)
● SAP HANA Database edition for BW
● SAP HANA Limited edition for Apps / Accelerators
● SAP HANA EDGE edition
Note
SAP HANA information composer is a Web-based environment that allows business users to upload data to
the SAP HANA database and to manipulate that data by creating information views. The SAP HANA
information composer is installed separately from the SAP HANA system.
1.2 Software Download
In the SAP Software Download Center, you have access to the installation media and components for SAP
HANA.
You can find the installation media and components for SAP HANA in the following locations:
● Installation media for an SAP HANA SPS:
SAP Software Download Center Installations and Upgrades A-Z Index Installations and Upgrades -
H SAP In-Memory (SAP HANA) HANA Platform Edition SAP HANA PLATFORM EDITION SAP
HANA PLATFORM EDIT. 1.0 Installation
● Support Packages and Patches for SAP HANA:
SAP Software Download Center Support Packages and Patches A-Z Index Support Packages and
Patches - H SAP HANA PLATFORM EDITION SAP HANA PLATFORM EDIT. 1.0
The responsibility for acquiring and installing SAP HANA depends on the chosen deployment model:
● If a customer chooses the SAP HANA tailored data center integration, the components of SAP HANA
have to be installed on validated hardware by a certified administrator.
● If a customer chooses an SAP HANA appliance, the components of SAP HANA can only be installed by
certified hardware partners on validated hardware running a specific operating system. Any other system
6
P U B L I C

or content developed with systems of this type is not supported by SAP. For more information, see the
information page of the product version. Support Package Stacks (SPS) can be downloaded and applied
to appliances in accordance with agreements with the respective hardware partner.
Related Information
SAP Software Download Center
P U B L I C

2 Before Installing an SAP HANA System
Before installing an SAP HANA system, it is important to understand the basic system concepts in order to
optimize the installation process and avoid unnecessary reconfiguration.
Note
The components of SAP HANA can only be installed by certified hardware partners, or any person holding
E_HANAINS131 certification, on validated hardware running an approved operating system.
2.1 SAP HANA System Concepts
An SAP HANA system is composed of three main components: the host, the system, and the instance.
In everyday language, these terms may have different meanings, so it is important to clearly understand what
these terms mean when it comes to an SAP HANA installation.
Host
A host is the operating environment in which the SAP HANA database runs. The host provides all the
resources and services (CPU, memory, network, and operating system) that the SAP HANA database
requires. The host provides links to the installation directory, data directory, and log directory, or the storage
itself. The storage for an installation does not have to be on the host. For multiple-host systems, a shared
storage or a storage that is accessible on-demand from all hosts is required. For more information about
multiple-host system concepts, see Related Information.
Instance
An SAP HANA instance is the set of SAP HANA system components that are installed on one host. A system
can be distributed as several instances among several hosts, but each instance in a multiple-host system must
have the same instance number.
System
8
P U B L I C
Before Installing an SAP HANA System

A system is one or more instances with the same number. The term "system" is interchangeable with the term
"SAP HANA database". If a system has more than one instance, they must be dispersed over several hosts as
a multiple-host system.
Related Information
Multiple-Host System Concepts [page 43]
It is important to review multiple-host system concepts like host grouping and storage options before
installing a multiple-host system.
2.2 SAP HANA System Types
An SAP HANA system can be configured as one of the following types:
● Single-host system - One SAP HANA instance on one host.
● Multiple-host (distributed) system - Multiple SAP HANA instances distributed over multiple hosts, with
one instance per host.
2.2.1 Single-Host System
If there is only one host in a system, it is called a single-host system.
The following graphic shows the file system for a single-host installation:
P U B L I C

A single-host system is the simplest system installation type. It is possible to run an SAP HANA system
entirely on one host and then scale the system up as needed. Both the hdblcm and hdblcmgui SAP HANA
lifecycle management tools can be used to install an SAP HANA single-host system in one of the installer
modes, and with a combination of parameter specification methods.
Interaction Modes
Installation can be performed in one of the following modes:
Interactive Mode
(Default)
Available for hdblcm or hdblcmgui. The person installing the system must enter
parameter specifications iteratively until the installation process finishes. For more details,
see the Interactive Installation information.
Batch Mode Available for hdblcm. The installation accepts the default values for all unspecified
parameters, and runs to completion without any additional input required. Batch mode
must be explicitly specified when the hdblcm installation tool is called. For more details,
see the Enabling Batch Mode information.
Parameter Specification Methods
Installation parameter values can be entered in one or more of the following methods:
Interactively
(Default)
Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui),
most parameters are requested interactively. Parameters that are not requested accept
the default value. For more details about which parameters are requested interactively,
see the Changeable Default Values information.
Command Line
Options
Installation parameters are given in their accepted syntax as a space delimited list after
the program name (hdblcm or hdblcmgui). The specified parameters replace the
defaults. If any mandatory parameters are left out, they are requested interactively (unless
batch mode is specified). All parameters can be entered from the command line. For more
details about the accepted parameter syntax, see the Installation Parameters information.
Configuration
File
The configuration file is a plain text file, of parameters set to their default values, that can
be generated, edited, and saved to be called during installation with either the hdblcm or
hdblcmgui tool. If any mandatory parameters are left out, they are requested
interactively (unless batch mode is specified). All parameters can be entered in the
configuration file. The specified parameters replace the defaults, but if you specify the
same parameter as a command line option and in the configuration file, the command line
version is used by the installer. For more details about the using the configuration file, see
the Automating with the Configuration File information.
Related Information
Interactive Installation [page 25]
Interactive mode is an installation mode, which requires the person installing the SAP HANA system to enter
parameter specifications as they are requested by the installer.
Enabling Batch Mode [page 40]
Batch mode installation can be started from the command line alone or in combination with the
configuration file. It runs all installation tasks without prompting for additional confirmation or input. Batch
mode is designed to automate the installation process.
10
P U B L I C

Changeable Default Values [page 20]
The installer uses the following default values unless you change them during installation.
Installation Parameters [page 19]
Installation parameters are a fundamental aspect of the SAP HANA lifecycle management tools hdblcm and
hdblcmgui, and provide the opportunity to optimize and customize the system during installation.
Automating with the Configuration File [page 36]
The configuration file is a text document where all available installation parameters can be specified.
2.2.2 Multiple-Host (Distributed) System
If there are multiple hosts in a system, it is called a multiple-host (or distributed) system.
The following graphic shows the file system for a multiple-host system with three hosts:
A multiple-host system is a system with more than one host, which can be configured as active worker hosts
or idle standby hosts. Both the hdblcm and hdblcmgui SAP HANA lifecycle management tools can be used to
install an SAP HANA multiple-host system in one of the installer modes, and with a combination of parameter
specification methods. To add hosts to an existing system, use the SAP HANA lifecycle manager (HLM) tool.
For more information about installing a multiple-host system, see the Related Information.
Interaction Modes
Installation can be performed in one of the following modes:
Interactive
Mode (Default)
Available for hdblcm or hdblcmgui. The person installing the system must enter
parameter specifications iteratively until the installation process finishes. For more
information about interactive installation, see Related Information.
Batch Mode Available for hdblcm. The installation accepts the default values for all unspecified
parameters, and runs to completion without any additional input required. Batch mode
P U B L I C

must be explicitly specified when the hdblcm installation tool is called. For more
information about batch mode, see Related Information.
Installation parameter values can be entered in one or more of the following methods:
Interactively
(Default)
Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui),
most parameters are requested interactively. Parameters that are not requested accept
the default value.
To install a multiple-host system interactively with the hdblcm tool, both the action and
the addhosts parameters must be specified from the command line. The rest of the
installation can follow interactively.
For more information about which parameters are requested interactively and have
changeable default values, see Related Information.
Command Line
Options
Installation parameters are given in their accepted syntax as a space delimited list after the
program name (hdblcm or hdblcmgui). The specified parameters replace the defaults. If
any mandatory parameters are left out, they are requested interactively (unless batch
mode is specified). All parameters can be entered from the command line.
To install a multiple-host system, the action and addhosts parameters must be specified
in combination with hdblcm.
For more information about the accepted parameter syntax, see Related Information.
Configuration
File
The configuration file is a plain text file, of parameters set to their default values, that can
be generated, edited, and saved to be called during installation with either the hdblcm or
hdblcmgui tool. If any mandatory parameters are left out, they are requested interactively
(unless batch mode is specified). All parameters can be entered in the configuration file.
The specified parameters replace the defaults, but if you specify the same parameter as a
command line option and in the configuration file, the command line version is used by the
installer. For more information about the using the configuration file, see Related
Information.
Related Information
Multiple-Host System Installation [page 42]
It is possible to configure additional hosts for an SAP HANA system both during and after installation.
However, there are some slight differences with the tools used depending on when you decide to add a host
to the system.
12
P U B L I C

2.3 Hardware and Software Requirements
For SAP HANA several hardware and software requirements need to be fulfilled.
Note
You can find a complete list of all SAP HANA components and the respective SAP HANA hardware and
software requirements in the Product Availability Matrix (PAM) on the SAP Service Marketplace and in the
SAP Community Network.
Software Requirements
Note
Only the software installed by certified hardware partners, or any person holding the certification, is
recommended for use on the SAP HANA system. Do not install additional software on the SAP HANA
system. The person performing the SAP HANA installation has passed the certification exam. Check the
SAP Education resources for information about the SAP HANA certication exams.
Operating System for SAP HANA
For the SAP HANA system the following operating systems are available:
● SUSE Linux Enterprise Server (SLES) 11
● Red Hat Enterprise Linux (RHEL) 6.5
Network Time Protocol (NTP)
We strongly recommend that you set up an NTP server for the SAP HANA system landscape.
Note
If an NTP sever is not available this means that, for example, trace files from distributed hosts cannot be
displayed in the correct chronological order.
Hardware Requirements
During the update and the installation of the SAP HANA database (from the SAP HANA installation manager),
a hardware check is performed in order to ensure that problems do not arise due to wrong or unsupported
hardware configurations in combination with the SAP HANA platform. The check is a script that is
automatically called by the SAP HANA installer and aborts the installation process if it doesn't succeed.
P U B L I C

It is not possible to disable the check because SAP HANA is highly optimized for specific hardware
configurations which have been designed and tested together with our hardware partners. Outside of these
validated configurations, SAP HANA performance and stability cannot be guaranteed.
Before installing or updating SAP HANA, consult the SAP HANA Product Availability Matrix (search for HANA)
to verify if the hardware you are planning to use is supported by SAP HANA. If the hardware is not supported,
the hardware check returns the results "not supported" in the system manufacturer, system product name,
CPU model, OS, memory total, or core count check results.
The check is automatically delivered with the SAP HANA software and can be executed as a standalone check
anytime. Execute the check by going to the /usr/sap/<SID>/HDB<instanceNumber>/exe/
python_support directory and running the Python script named HanaHwCheck.py. Due to some
dmidecode commands in the check it has to be executed as root.
Hardware Requirements for SAP HANA Network Connection
We recommend dedicated server network communication of 10 GBit/s between the SAP HANA landscape and
the source system for efficient data replication.
Related Information
SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System
SAP Note 2009879 - SAP HANA Guidelines for RedHat Enterprise Linux (RHEL)
SAP Traning & Education
Product Availability Matrix (PAM)
SAP Community Network - SAP Certified Appliance Hardware for SAP HANA
2.3.1 Recommended File System Layout
The SAP HANA lifecycle management tool hdblcm requires certain file systems in order to successfully install
an SAP HANA system.
The file systems can be defined manually before installation and then specified during installation, or the
default file systems can be used. It is important that the file systems listed below are available and have the
recommended disk space before starting the hdblcm program.
Table 1: Default File Systems
File System Default Path Recommendations
Root / The recommended disk space is at least 10 GB.
Installation path
(sapmnt)
/hana/shared/ The installation path (mount directory) requires disk space equal to
the default system RAM.
14
P U B L I C

File System Default Path Recommendations
The mount directory is used for shared files between all hosts in an
SAP HANA system. This directory needs to be accessible to each of
the servers in the SAP HANA cluster.
Sub-directories:
● /hana/shared/<SID> - Contains executable kernel programs
(exe), globally shared data (global), instance profiles (pro
file), HDB executables (HDB<number>), and uninstallation
script and instruntime (hdblcm)
● /hana/shared/<SID>/hdbclient - The SAP HANA client in
stallation path.
● /hana/shared/<SID>/hdbstudio - The SAP HANA studio
installation path.
● /hana/shared/<SID>/hdbstudio_update - The studio re
pository installation path. The studio repository is used to up
date the local SAP HANA studio installation.
● /hana/shared/<SID>/HLM - The SAP HANA lifecycle man
ager can be used to update the components of the SAP HANA
installation.
System instance /usr/sap The system instance directory requires at least 50 GB disk space.
This is the path to the local SAP system instance directories.
Sub-directories:
● /usr/sap/hostctrl - The SAP host agent directory.
● /usr/sap/<SID> - Contains system executables (SYS) and
the home directory (home) of the <sid>adm user.
Data volume /hana/data/
<SID>
The data path requires disk space equivalent at least three times
the size of the system RAM.
The default path to the data directory depends on the system ID of
the SAP HANA host.
Log volume /hana/log/
<SID>
The log path requires disk space at least equivalent to the default
system RAM.
The default path to the log directory depends on the system ID of
the SAP HANA host.
It is strongly recommended to use the SAP HANA file system layout shown in the figure below:
P U B L I C

Note
An SAP HANA system in a production environment must not share any infrastructure with another SAP
HANA system.
Hosts running more than one SAP HANA system (sometimes referred to as multiple-SID installations) can
only be used for non-production purposes such as development, quality assurance, or testing.
For production systems with high availability, it is possible to share some temporarily unused resources
from the standby hosts. As soon as the standby resources are needed, they must become exclusively
available for the production system and no longer shared. For more details, refer to the high availability
information in the SAP HANA Administration Guide.
The file systems /hana/data/<SID> and /hana/log/<SID> may use shared file systems like NFS, or block
storage using the SAP HANA storage connector API with non-shared file systems. For more details, Related
Information.
The installation path (/hana/shared) is visible on all hosts. By default, the installation path is also used for
backup. However, backup directories should be manually configured, and must belong to a shared file system.
For more details, refer to the backup information in the SAP HANA Administration Guide.
16
P U B L I C

Related Information
P U B L I C

3 Installing an SAP HANA System
The SAP HANA lifecycle management tools install or update the underlying components of the SAP HANA
platform. An SAP HANA system can be installed or updated from the command line interface (hdblcm) or
from the graphical user interface (hdblcmgui).
Using the SAP HANA hdblcm and hdblcmgui tools, SAP HANA components can by installed, updated, or
uninstalled independently of each other. It is possible to perform installation and update tasks in interactive
mode or batch mode.
3.1 Overview of the LCM Interaction Modes and Parameter
Specification Methods
The SAP HANA lifecycle management toolset includes the installation, update, and configuration tool
hdblcm(gui) as well as the underlying LCM tools. To interact with the SAP HANA lifecycle management tools,
use one interaction mode with a combination of parameter specification methods.
Interaction Modes
Installation, update, and configuration tasks can be performed in one of the following interaction modes:
Interactive
Mode (Default)
Available for graphical interface and command line interface tools. The person performing
system installation, update, or configuration tasks must enter or confirm parameter
specifications iteratively until the process finishes. For more information about interactive
mode, see Related Information.
Batch Mode Available for command line interface tools only. The SAP HANA lifecycle management
command line tool accepts the default values for all unspecified parameters, and runs to
completion without any additional input required. Batch mode must be explicitly specified
when the command line tool is called. For more information about batch mode, see Related
Information.
SAP HANA lifecycle management parameter values can be entered in one or more of the following methods:
Interactively
(Default)
Using either command line interface or graphical interface, most parameters are
requested interactively. Default parameter values are proposed in brackets and can be
changed or confirmed. Parameters that are not requested (or specified via another
method) accept the default value.
Command Line
Options
Parameters are given in their accepted syntax as a space delimited list after the program
name (for example, hdblcm or hdblcmgui). The specified parameters replace the defaults.
If any mandatory parameters are excluded, they are requested interactively (unless batch
mode is specified). All parameters can be entered from the command line. For more
details about the accepted parameter syntax, see the inline help output (help) for the
individual SAP HANA lifecycle management tool.
18
P U B L I C
Installing an SAP HANA System

Configuration
File
The configuration file is a plain text file, for which a template of parameter key-value pairs
can be generated, edited, and saved to be called in combination with the program call. If
any mandatory parameters are not specified, they are requested interactively (unless
batch mode is used). All parameters can be entered in the configuration file. For more
information about the configuration file, see Related Information.
Note
If parameters are specified in the command line, they override the corresponding parameters in the
configuration file. Parameters in the configuration file override default settings.
Order of parameter precedence:
Command Line > Configuration File > Default
Related Information
3.2 Installation Parameters
Installation parameters are used for all methods of parameter specification - interactively, as command line
options, or with the configuration file. The following information is relevant for either installation mode
(interactive mode or batch mode).
P U B L I C

3.2.1 Mandatory Installation Values
The only mandatory parameter without a default value is the SAP system ID (SID, sid), which must be
specified. However, it is also recommended to define an instance number (number), since these two
parameters are meaningful to the identity of the system.
If the installation is run in batch mode from the installation medium, the minimum required parameters are the
SID and the passwords (specified in XML syntax and streamed in, or specified in the configuration file). In the
case that only the SID and passwords are entered as parameters, the other parameters automatically take
their default value.
In batch mode, if one of the mandatory parameters, without a default, is not specified, the installation fails with
an error. If an installation is not run in batch mode, but in interactive mode (default) instead, the missing
mandatory parameters are requested in the console.
When building a multiple-host system, the action and addhosts parameters are mandatory command-line
specifications for the hdblcm installer.
3.2.1.1 Changeable Default Values
Some default values are based on the predefined values on the current host. In a multiple-host system, it is
recommended to manually check the mandatory values on each hosts before installation.
Table 2: Changeable Parameter Defaults
Parameter System Default Value CLI Inter
active
Mode
GUI
action install
(except for multiple-host system installation, for
which action must be specified)
autostart 0
(off)
certificates_host
map
<current host>
client_path ${sapmnt}/${SID}/hdbclient
components client,hlm,server,studio
(dependent on the installer finding installation sour
ces for the components)
copy_repository /hana/shared/${SID}/hdbstudio_update
datapath /hana/data/${SID}
20
P U B L I C

Parameter System Default Value CLI Inter
active
Mode
GUI
groupid 79
home /usr/sap/${SID}/home
hostname <current host>
install_hostagent 1
(on)
logpath /hana/log/${SID}
number <next successive un-used instance number
on the host>
root_user root
sapmnt /hana/shared
shell /bin/sh
studio_path ${sapmnt}/${SID}/hdbstudio
studio_repository 1
(on)
system_usage custom
timezone UTC
userid <next successive un-used user ID on the
host>
vm <Java runtime found in environment
variable PATH or JAVA_HOME>
Note
The default paths written in the form ${<parameter>} indicate that substitution of the parameter occurs
in the configuration file and in batch mode. Substitution also occurs in interactive mode in order to create a
suggested path. The advantage of substitution is that the SAP system ID (sid) and the installation path
(sapmnt, which is /hana/shared, by default) only need to be specified once, and are then substituted in to
the other parameter values. This ensures that the system has unique file system paths if multiple systems
are installed on the same host. However, if it is preferred to deviate from the default paths, it is necessary to
pay attention to the settings, especially in the configuration file, and when installing in batch mode.
P U B L I C

Related Information
action [page 64]
Specifies the action of hdblcm to be either installation or update.
autostart [page 65]
Restarts instance after machine reboot.
certificates_hostmap [page 66]
Specifies the hostname used for generation of self-signed SSL certificates for the SAP host agent. This
certificate is used by the SAP HANA lifecycle manager (HLM).
client_path [page 68]
Specifies the installation path for the client.
components [page 69]
Specifies the components to be installed in combination with the server: studio, client, HLM, AFL, LCAPPS. It
is also possible to specify all components, or to specify a combination of components as a comma-
separated list. The server is always installed, even if it is not explicitly specified.
copy_repository [page 70]
Specifies the target path to which the SAP HANA studio repository should be copied.
datapath [page 70]
Specifies the path to the data directory of the SAP HANA system.
groupid [page 71]
Specifies the SAP system (sapsys) group ID. This parameter is relevant only if a sapsys group does not
already exist on the host. If a sapsys group already exists, passing the groupid parameter does not alter the
existing group.
home [page 72]
Specifies the home directory of the system administrator. This parameter is relevant only if the operating
system administrator (<sid>adm) does not exist prior to installation.
hostname [page 72]
Specifies the host name of the machine.
install_hostagent [page 73]
Enables the installation or update of the SAP host agent.
logpath [page 74]
Specifies the path to the log directory of the SAP HANA system.
number [page 75]
Specifies the instance number of the SAP HANA system.
root_user [page 78]
Specifies the root user name.
sapmnt [page 78]
Specifies the path to the SAP mount directory, which can be used as a shared directory between multiple
hosts.
shell [page 79]
Specifies a system administrator login shell. This parameter is relevant only if the operating system
administrator (<sid>adm) does not exist prior to installation.
studio_path [page 80]
22
P U B L I C

Specifies the installation path for the SAP HANA studio.
studio_repository [page 81]
Enables the copying of the SAP HANA studio repository. When enabled (default), the SAP HANA studio
repository is copied to the location defined by copy_repository from the location defined by
repository.
timezone [page 82]
Specifies the timezone for the system administrator. This parameter is relevant only if the operating system
userid [page 82]
Specifies the user ID of the system administrator. This parameter is relevant only if the operating system
vm [page 83]
Specifies the path of the Java runtime file. This parameter is only relevant if the SAP HANA studio is selected
for installation or update.
3.2.1.2 Users Created During Installation
The following users are automatically created during the installation: <sid>adm, sapadm, and SYSTEM.
User Description
<sid>adm The operating system administrator.
● The user <sid>adm is the operating system user required for administrative
tasks such as starting and stopping the system.
● The user ID of the <sid>adm user is defined during the system installation. The
user ID and group ID of this operating system user must be unique and identical
on each host of a multiple-host system.
● The password of the <sid>adm user is set during installation with the password
parameter.
sapadm The SAP host agent administrator.
● If there is no SAP host agent available on the installation host, it is created during
the installation along with the user sapadm.
● If the SAP host agent is already available on the installation host, it is not modi
fied by the installer. The sapadm user and password are also not modified.
● The password of the sapadm user is set during installation with the sa
padm_password parameter.
SYSTEM The database superuser.
● Initially, the SYSTEM user has all system permissions. Additional permissions can
be granted and revoked again, however the initial permissions can never be re
voked.
● The password of the SYSTEM user is set during installation with the sys
tem_user_password parameter.
P U B L I C

3.2.1.3 Specifying Passwords
Passwords are a mandatory parameter for installing an SAP HANA system. There are three methods for
configuring passwords.
Interactive Mode
Interactive installation is available for both graphical interface (hdblcmgui) and command line (hdblcm)
tools. Passwords are entered manually one-by-one as they are requested by the installer. This method is
preferred for quick, individual system installations.
Command Line
Configuring passwords in the command line is a two-step process. First, a simple text file with passwords in
XML syntax should be created and saved in the home directory of the root user. Then the file can be called
using standard input and the read_password_from_stdin parameter in the command line with batch mode.
Parameters specified in the command line override parameters specified in the configuration file. Since this
method is the most powerful and flexible method, it is often the preferred method for installing multiple SAP
HANA systems at one time.
Example
The following is an example of the password file in XML syntax:
Passwords.xml
<?xml version="1.0" encoding="UTF-8"?>
<Passwords>
<password>Adm1234</password>
<sapadm_password>Agent1234</sapadm_password>
<system_user_password>Sys1234</system_user_password>
<root_password>Root1234</root_password>
</Passwords>
Now, the password file (stored in the root user's home directory) is called from the command line using
standard input, the read_password_from_stdin=xml parameter, and batch mode:
cat ~/Passwords.xml | ./hdblcm sid=DB1 number=42
read_password_from_stdin=xml b
Configuration File
It is possible to specify passwords in the configuration file. A configuration file template is created with all the
parameters set to their default values. The configuration file is edited to the preferred parameter values, then
it is saved, and the values are read by the installer during installation. This method is preferred for a one-step
24
P U B L I C

installation that can be re-created several times. If passwords are specified in the configuration file, the
configuration file should be stored in the home directory of the root user, for security reasons.
Example
The following is an example of the configuration file, with configured password parameters:
configfile1.cfg
# Root User Password
root_password=Root1234
...
# SAP Host Agent (sapadm) Password
sapadm_password=Agent1234
...
# System Administrator Password
password=Adm1234
....
# Database User (SYSTEM) Password
system_user_password=Sys1234
Now, the configuration file (stored in the root user's home directory) is called from the command line using
the configfile parameter:
./hdblcm sid=DB1 configfile=~/configfile1.cfg
3.3 Interactive Installation
An SAP HANA system can be installed interactively:
● With command line options, by running the installation tool hdblcm.
● With the graphical installation tool, hdblcmgui, by selecting installation options from a wizard.
3.3.1 Installing with the Graphical Interface
It is now possible to install an SAP HANA system from a graphical interface, by running the SAP HANA lifecycle
management tool hdblcmgui.
Prerequisites
● You are logged in as root user.
● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
P U B L I C

○ The JRE is accessible either via the PATH or JAVA_HOME variable.
○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java version
Procedure
1. Change to the following directory on the installation medium:
<installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64
2. Start the installer:
./hdblcmgui
3. The following parameters can be defined:
○ Software directory
The software component directories are detected. Component locations can be added or changed.
○ Action of installation or update
○ Components to be installed or updated
○ Authorization data (passwords)
○ Installation parameters:
System type: Single-host system or multiple-host system
Installation path (sapmnt)
SAP system ID (SID)
Instance number
Location of data and log volumes
Restricted memory allocation
User ID
User group ID
System administrator login shell
System administrator home directory
26
P U B L I C

Results
The installation progress is displayed.
The SAP HANA system is now up and running.
3.3.2 Installing Interactively from the Command Line
An SAP HANA system can be installed interactively from the command line. When the SAP HANA lifecycle
management tool hdblcm tool is called, mandatory parameters are requested by the installer.
Prerequisites
follows:
P U B L I C

Procedure
2. Start the installer:
./hdblcm
3. Parameter default values are suggested in brackets, and can be accepted with Enter. Otherwise, enter a
non-default value, then select Enter.
Results
The installation progress is displayed.
28
P U B L I C

4 Advanced Installation
Advanced installation topics are designed for those who are familiar with SAP HANA, and are installing it
regularly, in various production environments. In particular, advanced installation refers to automated
installation and the configuration of a multiple-host system using hdblcm.
In order to provide flexibility, it is possible to install the same SAP HANA system in several ways. The
differences between installation methods are best depicted through a one-to-one comparison of the same
system installed with each available method.
In the following example, there is a hardware partner who plans to install several SAP HANA single-host
systems. His desired system has the following specifications:
● System name: P01
● Instance number: 01
● Installation path: /hana/shared
● Data path: /hana/data/P01
● Log path: /hana/log/P01
● User group ID: 110
He has several customers who have pre-ordered the single-host SAP HANA P01 system and he is expecting
more P01 orders. His goal is to iteratively improve his installation method to the point that he can automate his
ideally configured system installation on several hosts at the same time, come back later, and the installed
SAP HANA platforms will be finished and ready to ship. To reach his goal, he installs the same system (P01)
three times, using:
● Command line options
● Configuration file
● Configuration file in batch mode
Advanced Installation
P U B L I C

Installing the System Using Command Line Options
Since the hardware partner is still new to installing SAP HANA, he tries out the installation first from the
command line. He reviews the installation parameters and finds the corresponding parameter key-value pairs
for his desired P01 single-host system.
System Detail Specification Command Line Parameter
System name P01 sid=P01
Instance num
ber
01 number=01
Installation path /hana/shared sapmnt=/hana/shared
Data path /hana/data/P01 datapath=/hana/data/P01
Log path /hana/log/P01 logpath=/hana/log/P01
User group ID 110 groupid=110
The hardware partner takes the parameter key-value pairs, and builds the command line input as follows:
./hdblcm sid=P01 number=01 groupid=110 sapmnt=/hana/shared datapath=/
hana/data/P01 logpath=/hana/log/P01
Upon review of the parameter syntax, he realizes he did not need to specify sapmnt, datapath, or logpath
parameters because he chose the default values. The rest of the parameters could also have been given the
short-form syntax. Therefore, the same P01 system installation could be simplified to the following syntax:
./hdblcm –s P01 –n 01 –G 110
System Detail Specification Simplified Command Line Parameter
System name P01 s P01
Instance num
ber
01 n 01
Installation path /hana/shared <default>
Data path /hana/data/P01 <default>
Log path /hana/log/P01 <default>
User group ID 110 G 110
Installing the System Using the Configuration File
Now that the hardware partner successfully installed from the command line, he wants to make use of the
configuration file, since his end goal is to automate the installation.
He generates a template of the configuration file:
./hdblcm action=install dump_configfile_template=/home/root/HANA_install.cfg
30
P U B L I C

He opens the blank configuration file template and fills it in as follows:
HANA_install.cfg# SAP HANA System ID
sid=P01
# Instance Number (Default: 00)
number=01
…
# ID of User Group 'sapsys'
Groupid=110
Since it was already discovered that only the SID, instance number, and group ID differ from the default values,
only they are specified in the configuration file. The hardware partner also realizes that there is automatic
substitution of the SID (sid) and installation path (sapmnt) throughout the configuration file according to
default values (for example, datapath default: /hana/data/${sid}), so he does not need to append the SID
(in this case, P01) to the paths.
Now, he can start the installer from the command line with the following simple command:
./hdblcm configfile=/home/root/HANA_install.cfg
Installing the System Using the Configuration File in Batch Mode
Now the hardware partner can take the last step of automation with the SAP HANA lifecycle management tool
hdblcm and use batch mode. It is important to note, up this point the hardware partner has been interactively
entering passwords and confirming other default parameters as part of interactive mode. Batch mode runs the
installer without asking for any confirmation or parameter entry, thereby allowing installation to run to
completion from one push of a button.
There are two choices for password entry in batch mode. Either the passwords can be stored in an XML file
and passed to the installer as a stream by standard input, or they can be specified in the configuration file.
Since the hardware partner is already making use of the configuration file, he decides to enter the passwords
there. The only mandatory parameters in batch mode are the SID and passwords, so he checks the other
defaults of the mandatory installation values before continuing the installation. In batch mode, the installer
accepts default values for any unspecified parameters.
With the addition of passwords to the configuration file, it now looks like this:
HANA_install.cfg# Root User Password
...
# SAP HANA System ID
sid=P01
# Instance Number (Default: 00)
number=01
...
# ID of User Group 'sapsys'
Groupid=110
...
...
password=Adm1234
....
P U B L I C

Now, the partner starts the installer, this time with the addition of the batch mode parameter, b (or
batch):
./hdblcm configfile=/home/root/HANA_install.cfg b
Multiple-Host System Setup
A multiple-host SAP HANA system can be installed using all the methods listed above (with command line
options, in the configuration file, and in batch mode). Additionally, the graphical interface tool hdblcmgui can
also be used to build a multiple-host system. When installing a multiple-host system, the following applies:
● Using the SAP HANA lifecycle management tools, hdblcm or hdblcmgui, multiple hosts can be configured
during installation. Additional hosts cannot be added to existing systems with these tools.
● The addhosts parameter must be specified. It is also possible to specify additional options for hosts such
as: role, storage_partition, and group. For more details, refer to the addhosts parameter
information, and the multiple-host system concepts information.
● The root user on all hosts must be the same.
● If the root user name is something other than the default "root", the root user name must be specified
during installation with the parameter root_user.
Related Information
4.1 Automating SAP HANA System Installation
Installation automation is designed for anyone who wants to install a similar SAP HANA system multiple times
or start an unattended installation.
With the SAP HANA lifecycle management tool hdblcm, it is now possible to automate installation by using a
combination of the configuration file, command line options, and batch mode, so that an SAP HANA system
installation can be executed once without any follow-up selection.
To illustrate the purpose of installation automation, let us assume there is a hardware partner who offers SAP
HANA platforms (SAP HANA system installed on SAP verified hardware) in three sizes: Small, Large, and Extra
Large.
32
P U B L I C

Since the hardware partner prepares the SAP HANA platform on-demand, he needs to be able to react quickly
to orders as they are placed. During slow sales periods, manual installation is feasible, however during busy
sales periods, manual installation could create too much overhead. In this case, installation automation would
allow the hardware partner to start as many installation copies as required, without any further interaction
with the installer. It would even be possible for the partner to start the installation near the end of the business
day, leave the installation, and ship out the order the next morning.
P U B L I C

The hardware partner automates the installation of nine SAP HANA systems (1 Extra Large, 5 Large, and 3
Small). Previously, he has created configuration files for each of the three system types. So, when several
orders come in at the same time, he fine tunes his installation script to include the number of systems and
calls hdblcm with the configuration file parameter in batch mode. When the installation script is run, SAP
HANA is installed on both the single-host and multiple-host systems, without any additional input. By reusing
the same configuration files, the installations are reliable, flexible, and efficient.
4.1.1 Automation Checklist
Automation is ideal for installations that run unattended. Before you start an automated installation, it is
recommended to consider the following.
For All System Types
Do the operating system and additional software
components meet the requirements?
Refer to the Hardware and Software Requirements.
Do you know where the data volumes and the log vol
umes will be located?
For security reasons, the data device and log device
should not be the same. Refer to the SAP HANA Sys
tem Types.
34
P U B L I C

Where will the required file systems be located and is
the storage sufficient?
Refer to the Recommended File System Layout.
Have you performed a hardware check? The installer performs a hardware check before in
stallation, for automated installation it is recom
mended to perform a manual hardware check first.
Refer to the Hardware and Software Requirements.
Where will you specify passwords? SYSTEM, <sid>adm, sapadm, and root passwords
must be specified in the configuration file or in an
XML file. Refer to the Specifying Passwords informa
tion.
For the Multiple-Host System Type Only
How many worker hosts and standby hosts will there
be? How will they be grouped?
System processes and data are distributed among
worker hosts, including the original host. Standby
hosts do not perform tasks. Refer to the Multiple-
Host System Concepts.
How will storage devices be configured? External storage can be configured so that hosts
have shared or non-shared access. Refer to the Multi
ple-Host System Concepts.
The root user name must be the same for all hosts in
a multiple-host system. Will the root user name for all
hosts be "root"?
If not, the root_user parameter must be specified
during installation. Refer to the root_user parameter
information.
Related Information
Hardware and Software Requirements [page 13]
For SAP HANA several hardware and software requirements need to be fulfilled.
SAP HANA System Types [page 9]
An SAP HANA system can be configured as one of the following types:
Recommended File System Layout [page 14]
The SAP HANA lifecycle management tool hdblcm requires certain file systems in order to successfully
install an SAP HANA system.
Specifying Passwords [page 24]
root_user [page 78]
P U B L I C

4.1.2 Automating with the Configuration File
By calling hdblcm with action=install dump_configfile_template=<file> parameters
specified, a text file is output to a specified file path. It can then be opened and edited. The template provides
the available installation parameter values as well as corresponding information about their purpose and
default values. For more information about preparation, see Related Information.
When the configuration file has been prepared, it can be used in a number of ways:
● hdblcm with the configuration file - This method is the simplest. The installation parameter values are
read by the installer from the configuration file. If all mandatory parameters are specified in the file,
minimal interaction is required during installation. For more information, see Related Information.
● hdblcm with the configuration file and command line options - This method offers the most flexibility
and is designed to reuse a configuration file for another installation. For more information, see Related
Information.
● hdblcm with the configuration file and batch mode - This method is used for automated installation. It
can be used to automate installation for several instances in a multiple-host system, or combined with a
script to automate installation of several identical systems. For more information, see Related
Information.
For examples of installing with the configuration file, or for an example of the configuration file itself, refer to
the related information.
Related Information
Preparing the Configuration File [page 37]
The configuration file is an installation tool for those who want to install several of the same system, or save
configuration parameters for reuse or for quick reference.
Using the Configuration File [page 38]
By defining a prepared configuration file during installation, specified parameter values are used by the
installer to build a customized SAP HANA system.
Using the Configuration File with Command Line Options [page 39]
installer to build a customized SAP HANA system. Using the configuration file and command line options at
the same time allows for additional flexibility.
Tutorials [page 84]
The following is a sampling of general use cases, which illustrate the functionality and versatility of the SAP
HANA hdblcm lifecycle management tool.
Configuration File Template [page 101]
The following is the configuration file template that is generated using the dump_configfile_template
parameter in combination with the hdblcm installer.
36
P U B L I C

4.1.2.1 Preparing the Configuration File
Prerequisites
Make sure you have done the following before you start preparing the configuration file.
● You have considered how to set up the required systems and directories. For more information, see
Related Information.
● You have considered which installation parameters the new system requires. For more information, see
Context
The configuration file is a plain text file of specified installation parameters, written in the same syntax as in the
command line (except without the leading two dashes --). A configuration file template can be generated,
edited, and saved to be called during installation.
The configuration file template provides a brief, commented-out summary of each parameter. Each parameter
is set to its default value. The parameters are divided into the following categories: general, server, client,
studio, and LifecycleManager.
Procedure
2. Generate the configuration file template.
Run the hdblcm program using the parameter dump_configfile_template. Specify an action and a file
path for the template:
./hdblcm action=[install|update] dump_configfile_template=<filepath>
3. Edit the configuration file parameters. Save the file.
It is recommended that at least the SAP system ID (sid) and the instance number (number) are uniquely
defined. There are several required parameters, that are provided default values in case they are not
customized. For more information, refer to the default values.
Some file path parameters have automatic substitution values as part of the default file path, using the
sid (SAP HANA system ID) and sapmnt (installation path) parameters, so that the substituted values
create file paths that are unique and system-specific. For example, the default for the data file path is:
datapath=/hana/data/${sid}, where sid is automatically replaced by the unique SAP HANA system
ID.
P U B L I C

Results
You have generated the configuration file template, edited it, and saved it. The configuration file is now ready
for use during installation.
Related Information
Recommended File System Layout [page 14]
The SAP HANA lifecycle management tool hdblcm requires certain file systems in order to successfully
install an SAP HANA system.
Parameter Reference [page 64]
Reference information is provided for each installation parameter.
4.1.2.2 Using the Configuration File
installer to build a customized SAP HANA system.
Prerequisites
● You have prepared the configuration file. For more information, see Preparing the Configuration File.
follows:
Procedure
2. Start the installer with the prepared configuration file specified:
./hdblcm configfile=<file path>
38
P U B L I C

Results
The installation progress is displayed on the command line.
Related Information
4.1.2.3 Using the Configuration File with Command Line
Options
installer to build a customized SAP HANA system. Using the configuration file and command line options at
the same time allows for additional flexibility.
Prerequisites
● You have prepared the configuration file. For more information, see Preparing the Configuration File.
follows:
Context
If parameter values are specified in both the configuration file and the command line, the command line values
override the configuration file values. This feature provides some extra flexibility for reuse, since an existing
configuration file could be used for a new installation where most of the values remain unchanged, but some
values could be modified on the command line ad-hoc.
P U B L I C

Procedure
2. Start the installer with the prepared configuration file specified:
./hdblcm configfile=<file path> <additional parameters>
Results
The installation progress is displayed on the command line.
Example
The following example installs a multiple-host system with the addhosts parameter specified on the
command line, but all other parameters specified from the configuration file. If the addhosts parameter is
also specified in the configuration file, it is overwritten by the command line specification of addhosts.
./hdblcm action=install
addhosts=hanahost2:group=HA1:storage_partition=3,hanahost3:role=standby:group=H
A1 configfile=/var/tmp/H01_configfile
Related Information
4.1.2.4 Enabling Batch Mode
Batch mode installation can be started from the command line alone or in combination with the configuration
file. It runs all installation tasks without prompting for additional confirmation or input. Batch mode is designed
to automate the installation process.
Prerequisites
● When using batch mode, passwords must either be defined in the configuration file, or passed to the
installer using an XML password file and streamed in via standard input. In both cases, it is necessary to
prepare the passwords. For more information, see Specifying Passwords.
40
P U B L I C

follows:
Context
For those new to installation with the SAP HANA lifecycle management tool hdblcm, it is recommended to run
some test installations before using batch mode in a production environment.
Procedure
2. Start the installer with the batch mode parameter specified:
./hdblcm batch <additional parameters>
or
./hdblcm b <additional parameters>
Results
The installation runs without any follow-up.
Example
The following example installs the SAP HANA server, client, and HLM as a single-host system. The SAP
system ID and instance number are also specified from the command line. The system passwords are read
from a standard input stream by the installer. All other parameter defaults are automatically accepted and
no other input is requested in order to complete the installation.
cat ~/Passwords.xml | ./hdblcm batch action=install
components=client,hlm,server sid=DB1 number=42
read_password_from_stdin=xml
If a configuration file is used in combination with batch mode, an identical system can be installed with a
simplified call from the command line. In the following example, passwords are defined in the configuration
file, in addition to the action, components, SAP system ID, and instance number.
./hdblcm batch configfile=/var/tmp/H01_configfile
P U B L I C

Related Information
4.2 Multiple-Host System Installation
It is possible to configure additional hosts for an SAP HANA system both during and after installation.
However, there are some slight differences with the tools used depending on when you decide to add a host to
the system.
● The SAP HANA lifecycle management tool (hdblcm) - By specifying the addhosts parameter during
installation with the hdblcm tool, it is possible to configure a multiple-host system interactively from the
command line, in combination with the configuration file, or in batch mode. Each installation method uses
the same addhosts parameter options. For information about the parameter options, see Related
Information.
● The SAP HANA lifecycle management tool (hdblcmgui) - It is possible to use the graphical installation
tool, alone or in combination with the configuration file, to install a multiple-host system. The host
parameters correspond to those used in the command line. For information about the parameter options,
see Related Information.
The following information only covers building a multiple-host system during installation. Before carrying out
the system installation, review the addhosts parameter options and how they can be set to optimize multiple-
host system performance.
Related Information
addhosts [page 64]
Specifies additional hosts for the SAP HANA system as a comma-separated list. Individual host options are
specified by a colon-separated list.This parameter is used when configuring a multiple-host system during
installation.
42
P U B L I C

4.2.1 Multiple-Host System Concepts
Host Types
When configuring a multiple-host system, the additional hosts must be defined as worker hosts or standby
hosts (worker is default). Worker machines process data; standby machines do not handle any processing and
instead just wait to take over processes in the case of worker machine failure.
Auto-Failover for High Availability
Before installing a multiple-host system, it is important to consider whether high availability is necessary and
how hosts should be grouped to ensure preferred host auto-failover. For host auto-failover to be successful, if
the active (worker) host fails, the standby host takes over its role by starting its database instance using the
persisted data and log files of the failed host. The name server of one of the SAP HANA instances acts as the
cluster manager that pings all hosts regularly. If a failing host is detected, the cluster manager ensures that the
standby host takes over the role and the failing host is no longer allowed write access to the files (called
fencing) so that they do not become corrupted.
Host Grouping
Host grouping does not affect the load distribution among worker hosts - the load is distributed among all
workers in an SAP HANA system. If there are multiple standby hosts in a system, host grouping should be
considered, because host grouping decides the allocation of standby resources if a worker machine fails. If no
host group is specified, all hosts belong to one host group called "default". The more standby hosts in one host
group, the more failover security.
P U B L I C

If the same system is considered, but the standby hosts are each in a different host group, only one worker
host in each group can be compensated if failure occurs. The advantage of this configuration, is that in an SAP
HANA system with mixed machine resources, similar sized machines can be grouped together. If a small
worker host fails, and a small standby in the same group takes over, the processes are moved to a machine
with similar resources, which allows processing to continue as usual with optimal resource allocation.
The installer distinguishes between two types of groups: sapsys groups, and host groups. The SAP system
group (sapsys group) is the group that defines all hosts in a system. Therefore, all hosts in a multiple-host
system must have the same sapsys group ID, which is the default configuration with hdblcm. A host group is
group of hosts that share the same standby resources only. Therefore, if the multiple-host system has one
standby host, it is important to leave all hosts in the same host group ("default") so that all hosts have access
to the standby host in case a worker host fails.
Storage Options
In single-host SAP HANA systems, it is possible to use plain attached storage devices, such as SCSI hard
drives, SSDs, or SANs. However, in order to build a multiple-host system with failover capabilities, the storage
must ensure the following:
● The standby host has file access.
● The failed worker host no longer has access to write to files - called fencing.
There are two fundamentally different storage configurations which meet the two conditions above: shared
storage devices or separate storage devices with failover reassignment.
A shared storage subsystem, such as NFS or IBM's GPFS, is the commonly used storage option because it is
easy to ensure that the standby host has access to all active host files in the system. In a shared storage
solution, the externally attached storage subsystem devices are capable of providing dynamic mount points
for hosts. Since shared storage subsystems vary in their handling of fencing, it is the responsibility of the
hardware partner and their storage partners to develop a corruption-safe failover solution.
A shared storage system could be configured as in the diagram below, however mounts may differ among
hardware partners and their configurations.
44
P U B L I C

It is also possible to assign every SAP HANA host a separate storage, which has nothing mounted except the
shared area. This storage solution must be used in combination with the storage connector API, which SAP
HANA offers storage technology vendors. During failover, SAP HANA uses the storage connector API to tell
the storage device driver to re-mount the required data and logs volumes to the standby host and fence off the
same volumes from the failed host.
In a non-shared environment, separate storage used in combination with the storage connector API are given
logical roles as numbers. If you install a multiple-host system using hdblcm, you must specify the logical role
(assigned by the storage connector API) as the storage_partition option in the addhosts parameter
during installation so that the storage devices are recognized correctly by the installer.
P U B L I C

4.2.2 Creating a Multiple-Host System During Installation
The SAP HANA lifecycle management tools hdblcm and hdblcmgui have the ability to build a multiple-host
system during installation in interactive mode, in batch mode, and with the available parameter specification
methods: interactively, using command line options, or with the configuration file.
Prerequisites
● The shared file systems for the data files and log files are configured so that they are present and mounted
on all hosts, including the primary host. The suggested locations for the file systems are as follows:
○ /hana/shared/
○ /hana/data/<SID>
○ /hana/log/<SID>
● (Optional) Additional storage is configured.
● Root user name must be the same for all hosts in a multiple-host system.
● If the root user name is not root, it must be specified as a parameter during installation using the
parameter root_user.
follows:
● Multiple-host system installation using the hdblcm installation tool requires the parameter
action=install to be specified.
Procedure
2. Start the installer from the command line:
○ Interactive installation from GUI
Start the graphical installation tool, and follow the steps to configure the multiple-host system
installation:
./hdblcmgui
○ Interactive installation from CLI
Start the command line installation tool:
./hdblcm action=install addhosts=<host options>
A multiple-host system can be installed interactively from the command line, however the storage and
host role parameters cannot be entered interactively. Therefore, to carry out interactive installation
from the command line, it required to specify at least the action and addhosts parameters.
46
P U B L I C

○ With the configuration file (CLI or GUI)
○ Start the command line installation tool:
./hdblcm action=install configfile=<file path>
○ Start the graphical installation tool:
./hdblcmgui configfile=<file path>
It is possible to specify the addhosts parameter, and other required system parameters in the
configuration file, and call the configuration file during multiple-host system installation.
○ Command line installation in batch mode
Start the command line installation tool:
./hdblcm action=install addhosts=<host options> sid=<SID>
number=<instance number> b
Multiple-host system installation can be carried out in batch mode. In this case, at least the action,
addhosts, sid, and batch parameters must be specified. It is recommended to check the file paths,
and specify the instance number (number) as well.
Related Information
P U B L I C

5 Updating the SAP HANA System
All components of an SAP HANA system, including server, studio, client, HLM, AFL, LCApps, and SDA, can be
updated using the SAP HANA lifecycle management tools hdblcm(gui) and lifecycle manager.
We recommend to perform an SAP HANA system update from a local host. A local host is defined as a host
that is part of the SAP HANA system, which you are logged on to. Performing an update from a local host
minimizes the risk of failed update due to network glitches.
A remote host is defined as any host which establishes a connection to an SAP HANA host via HTTPS.
In the SAP HANA lifecycle management tool set, hdblcm(gui) is responsible for updating a system from a local
host, and the lifecycle manager updates from a remote host.
Related Information
Updating an SAP HANA System from a Local Host [page 48]
An SAP HANA system can be updated from a local host using the SAP HANA lifecycle management tool
hdblcm(gui).
Updating an SAP HANA System from a Remote Host [page 54]
You can perform an automated update of an SAP HANA system with the SAP HANA lifecycle manager. The
update use cases are applying Support Package Stacks (SPS) for SAP HANA and applying Single Support
Packages for SAP HANA.
5.1 Updating an SAP HANA System from a Local Host
An SAP HANA system can be updated from a local host using the SAP HANA lifecycle management tool
hdblcm(gui).
There are three methods for downloading an SAP HANA installation medium:
● Download the installation medium from Service Marketplace (SMP) - This method is only applicable when
updating to a new SPS.
● Use the Check for Updates functionality in the SAP HANA studio.
See the Download Software Components from SAP Service Marketplace and Prepare the Software Archive
for Update information.
● Download individual components from Service Marketplace (SMP).
Note
The installation medium cannot be patched manually with newer versions of SAP HANA components and
used for installation or update. The result is an error-prone installation.
48
P U B L I C
Updating the SAP HANA System

Related Information
Download Software Components from SAP Service Marketplace [page 49]
You can use your SAP HANA studio to check for available software component updates and download them
from SAP Service Marketplace.
Prepare the Software Archive for Update [page 51]
After downloading the software components from SAP Service Marketplace, the software archive must be
prepared for the update.
Update an SAP HANA System from a Local Host [page 52]
It is possible to update an SAP HANA system from a local host using the hdblcm or hdblcmgui lifecycle
management tools.
5.1.1 Preparing for Update in the SAP HANA Studio
The SAP HANA studio can be configured to check for software updates. Once updates are available, the
software must be downloaded, and the archive prepared before the update software can be installed.
Related Information
Download Software Components from SAP Service Marketplace [page 49]
5.1.1.1 Download Software Components from SAP Service
Marketplace
Prerequisites
● In the SAP HANA studio preferences, you have configured connection properties to the SAP Service
Marketplace.
● Your SAP HANA system must be SPS 08 or newer and must have hdblcm installed.
P U B L I C

● You need to provide system administrator (<sid>adm) credentials.
Context
In order to update an SAP HANA system, you first need to download the corresponding update sources
(components) from SAP Service Marketplace. The SAP HANA studio provides functionality, which helps you
to easily check for available updates of the installed SAP HANA core components and download them locally
on the machine where the SAP HANA studio is started or on a shared file system. In addition to the
downloaded content you will be provided with a shell script, which can automatically extract the archives in a
directory structure, suitable for hdblcm or hdblcmgui.
Procedure
1. Right click on an SAP HANA system and choose Lifecycle Management Platform Lifecycle
Management Check for available software component updates .
2. Choose which versions of the available components you want to download or choose skip to skip the
download of a particular component. The current version column shown the version of the components,
which is currently installed on the SAP HANA system.
Note that you can also select and download SAP HANA core components which are not currently, but can
be installed on the system.
3. Review the selected components and choose a download directory.
4. To start the download process, choose Finish.
5. You can run the download process in background by pressing the Run In Background button. To get the
current progress of the download, open the Progress View ( Window Show View Other…
Progress ).
Next Steps
To prepare for the update process, see Related Information.
Related Information
50
P U B L I C

5.1.1.2 Prepare the Software Archive for Update
Prerequisites
● You have downloaded the software components from SAP Service Marketplace using the SAP HANA
studio.
● You have copied the download directory to the SAP HANA host or in case it is a shared file system, make
sure it is accessible from the SAP HANA host.
Procedure
1. In the directory with the downloaded software component archive, there should be one additional shell
script – hdblcm_prepare.sh. Give execute permissions to the hdblcm_prepare.sh:
chmod 755 hdblcm_prepare.sh
2. Execute the script:
./hdblcm_prepare.sh
The following are parameters of the script hdblcm_prepare.sh:
Option Description Default Value
sapcar Location to the SAPCAR executable /usr/sap/hostctrl/exe/
SAPCAR
target_dir The target directory to extract the software com
ponent archives to
<current dir>/
component_root
The script outputs a message, containing the component root directory to be used with hdblcm (for
example, <component_root_dir>).
3. Start hdblcm or hdblcmgui with the option component_root=<component_root_dir>.
P U B L I C

5.1.2 Prepare for Update Manually
As an alternative to preparing for update in the SAP HANA studio, the update can be prepared manually by
making local package directories, that are recognized by the update tool.
Procedure
1. Create a local directory for the downloaded packages.
Example: /hana/local/downloads
2. Download SAP HANA packages from the SAP Service Marketplace to the local directory.
3. Create a directory, in to which the package contents can be unpacked.
Example: /hana/local/downloads/install
4. Unpack the archive in to the local directory.
Next Steps
You can now update the SAP HANA system with hdblcm or hdblcmgui.
Related Information
Update an SAP HANA System from a Local Host [page 52]
management tools.
5.1.3 Update an SAP HANA System from a Local Host
management tools.
Prerequisites
● You are updating to a new SPS from an installation medium or you have prepared for update, either in the
SAP HANA studio or manually.
● You have stopped the data replication.
52
P U B L I C

You have performed a system backup. Also note that during the update there is a business downtime for
your SAP HANA system.
You know the <sid>adm, and database administrator passwords.
You have applied a valid license key for the SAP HANA system.
Context
Update, like installation, can be carried out using the following three methods:
● Interactive update
From the command line (hdblcm)
From the graphical interface (hdblcmgui)
● Command line option update
● Configuration file update
Procedure
1. Change to the directory where the hdblcm tool is located.
cd <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64/
Note
If you prepared for update manually, change to the directory where you unpacked the archive.
2. Locate the SAP_HANA_DATABASE directory, and run the hdblcm update tool.
○ In interactive mode:
○ For hdblcm interactive on the command line, run the following:
./hdblcm
Select the update option, and enter parameters interactively.
○ For the hdblcmgui graphical interface, run the following:
./hdblcmgui
Select the update option, and follow the update GUI.
○ In command line option mode:
./hdblcm action=update
From the command line, it is possible to specify all necessary update parameters, and even run
update in batch mode. For more details, refer to the inline help: ./hdblcm action=update
help
○ Using the configuration file:
P U B L I C

1. Generate the configuration file template with update parameters:
./hdblcm action=update dump_configfile_template=<filepath>
2. Edit the configuration file template, save it, and call it during update:
./hdblcm action=update configfile=<filepath>
5.2 Updating an SAP HANA System from a Remote Host
You can perform an automated update of an SAP HANA system with the SAP HANA lifecycle manager. The
update use cases are applying Support Package Stacks (SPS) for SAP HANA and applying Single Support
Packages for SAP HANA.
The necessary update content can be provided to the SAP HANA lifecycle manager in the following ways:
● Automated Update - If the SAP HANA appliance has Internet access, the SAP HANA lifecycle manager
can find and download available updates from SAP Service Marketplace. In this case, you can update your
SAP HANA system without leaving the SAP HANA studio. See Related Information.
● Alternative Update Methods
○ Manual Download from SMP - If the SAP HANA appliance does not have Internet access, you can find
and download the updates manually from SAP Service Marketplace. In this case, you have to provide
the location of the downloaded content to the SAP HANA lifecycle manager for SAP HANA. See
Related Information
○ SAP Solution Manager - If you have SAP Solution Manager, you can use it to update your SAP HANA
system like other SAP systems in your landscape. In this case, you have to register your SAP HANA
system using the System Landscape Directory (SLD). For more information, see Related Information.
Once this configuration is performed, the SAP HANA database server will regularly update the SLD
with data about your SAP HANA system. Afterward, SAP Solution Manager can access this data to
calculate updates for this system. You can then use the Maintenance Optimizer (MOPZ) in SAP
Solution Manager to generate an SPS and download the necessary archives to a specified location.
For more information, see Related Information. You can then provide the SPS location to the SAP
HANA lifecycle manager and it will apply it on the system.
Related Information
SAP Solution Manager
54
P U B L I C

5.2.1 Perform an Automated Update
You can perform an automated update of SAP HANA using the SAP HANA lifecycle manager. An automated
update using the lifecycle manager is performed from the SAP HANA studio.
Prerequisites
● If you intend to execute the use case with Internet access, perform the following configuration. The SAP
HANA system needs access to the SAP Service Marketplace using HTTPS, unless you have already
downloaded and copied the target stack to your SAP HANA system. For more information about using
HTTPS to connect to SAP Service Marketplace, see proxy configuration settings in the SAP HANA
Administration Guide.
Caution
S-User is required
For more information about downloading the required content if you do not use SAP Service Marketplace,
see the procedure below.
● You have stopped the data replication before you start the automated update.
● You have performed a system backup before you start the automated update. Also note that during the
automated update there is a business downtime for your SAP HANA system.
● You know the <sid>adm, and database administrator passwords.
● You have applied a valid license key to the SAP HANA system.
● The SAP HANA database is up and running.
● The SAP Host Agent is up and running.
Context
You can use the SAP HANA lifecycle manager to update a single-host or multiple-host system. In a multiple-
host SAP HANA system, you have one primary SAP HANA host and several secondary SAP HANA hosts.
Depending on your SAP Host Agent version, for each host of the system, you might need to enter the
<sid>adm password in the user interface.
You can also use the SAP HANA lifecycle manager in the case of additionally added SAP HANA systems on a
single SAP HANA appliance (multiple SIDs on one host). In this case, the tool updates only one SID. To update
the rest of the SIDs, you need HLM installed per each SID.
Procedure
1. In your SAP HANA studio, add the system to which you want to connect.
P U B L I C

Note
Use the fully qualified host name for all configuration actions (including Add System).
2. In the context menu of the system node in the SAP HANA Systems view, choose Lifecycle Management
SAP HANA platform lifecycle management SAP HANA lifecycle manager .
If you have not previously defined them, you need to enter the user credentials for the <sid>adm user
when you call the SAP HANA lifecycle manager user interface for a specific SAP HANA system for the first
time.
The following users and settings are needed:
○ User <sid>adm
○ You need to enter the user and password when calling the SAP HANA Update user interface for
the first time.
○ You can change the user and password in the context menu for the added system under
Properties SAP System Logon .
○ You can delete the user and password under Windows Preferences General Security
Secure Storage .
In the lifecycle manager, you can choose the following options in the Update SAP HANA System field:
○ Update SAP HANA Lifecycle Manager (HLM)
We strongly recommend that you execute the tool self-update using the Update SAP HANA Lifecycle
Manager user interface option.
Keep in mind that if you do not have Internet access (for example, for security reasons), you need to
select Manually downloaded content as the source, and you need to have the relevant file already
available. You can download the newest archive available for this file, SAPHANALM*.SAR, in advance.
You have to download SAPHANALM*.SAR separately from SAP Service Marketplace: Support
Packages and Patches Search for Support Packages and Patches , where you need to search for
HANA Lifecycle Manager.
Note that you need to provide the full path to the file, not the containing directory.
If you have Internet access, the self-update of the HLM can be executed automatically when you
choose the Update SAP HANA Lifecycle Manager (HLM) option. In this case, the SAP HANA studio
needs to be configured to work properly with SAP Service Marketplace.
○ Apply Support Package Stack (SPS - recommended scenario)
You can update all software components of SAP products that are deployed on the system by
applying a support package stack. Support package stacks are collections of support packages for
software components defined by SAP that work best together.
With this scenario, you can execute an update to a set of SAP HANA components defined by the SPS.
If the stack contains content components for deployment such as SAP HANA Interactive Education
(SHINE), SAP HANA EPM Service, SAP HANA UI toolkit for Information Access (INA), these
components will also be deployed.
This scenario ensures smooth and consistent update.
○ Apply Single Support Packages (Single SP)
If you want to update only particular software components that are deployed on the system and do
not want to apply complete support package stacks, you can apply single support packages.
Furthermore, this scenario allows you to update components of an SAP HANA system which is
56
P U B L I C

running in a high-availability environment. However, if the system whose components you are
updating is running in a high-availability environment, you cannot deploy SAP HANA content
components or update the SAP HANA studio repository.
The user interface will provide information about installed components’ versions, as well as the newer
(target) ones that are available. You can select the component version to which you want to update. If
you have selected SAP Service Marketplace as an update source, the SAP HANA lifecycle manager
offers updates only for components that are part of the SAP HANA product.
After you have selected the update scenario (apply SPS or Single SP), you need to select the source for
the update from the Select the update source field:
○ Automatically downloaded content (SAP Service Marketplace)
The content is automatically downloaded from SAP Service Marketplace. In this case, SAP Service
Marketplace offers new SP versions, not Single SPs. Therefore, SAP Service Marketplace does not
return the latest patch.
○ Manually downloaded content
In this case, you need to manually download the following files to any directory accessible by the
<sid>adm
user in the SAP HANA system:
○ Stack.xml file – XML file containing a model of SAP HANA in the form of product instances,
components, and their versions.
○ IMDB_SERVER*.SAR, IMDB_CLIENT*.SAR, IMC_STUDIO*.SAR, HANALDCTR*.SAR
(optionally, if you need it), SAPHOSTAGENT*.SAR – archives containing new content
needed for the update of the SAP HANA instances.
When updating to an SPS, you can download the files listed above from the SAP Service Marketplace:
Support Packages and Patches Browse our Download Catalog SAP NetWeaver and complementary
products SAP HANA SAP HANA Platform Edition Support Package Stack Download .
When updating to a Single SP (this means different components' versions) use:
Support Packages and Patches Search for Support Packages and Patches . Search for IMDB Server,
for example. Make sure you do the same for the required archives, depending on the component you want
to update (IMDB_SERVER*.SAR, IMDB_CLIENT*.SAR, IMC_STUDIO*.SAR, HANALDCTR*.SAR,
SAPHOSTAGENT*.SAR). When downloading your preferred version, make sure that the selected archive is
suitable for your operating system.
All archives must be located in the same directory as the stack.xml file.
For information about using the Maintenance Optimizer (MOPZ) in SAP Solution Manager to generate an
SPS and download the necessary archives, see Related Information.
3. During the update, if you are prompted for them, enter the user name and password for the <sid>adm
user.
4. Select the proposed software releases.
5. Select the type of the source SAP HANA system. You have the following options:
○ Normal
Select this option if you are updating components of a regular SAP HANA system that is not running in
a high-availability environment. The system database must be running.
○ Primary
P U B L I C

Select this option if the SAP HANA system whose components you are updating is a primary system in
a high-availability setup. This scenario requires you to stop your system database before you perform
the update. During the update, SAP HANA content such as SAP HANA SHINE, SAP HANA EPM
Service, and SAP HANA INA toolkit cannot be deployed. Be aware that in this scenario you cannot
update your SAP HANA studio repository.
○ Secondary
Select this option if the SAP HANA system whose components you are updating is a secondary
system in a high-availability setup. During the update, SAP HANA content such as SAP HANA SHINE,
SAP HANA EPM Service, SAP HANA INA toolkit and cannot be deployed. Be aware that in this
scenario you cannot update your SAP HANA studio repository.
6. Follow the instructions of the wizard.
7. If you want to update your SAP HANA studio to the same version as your SAP HANA system, you need to
refer to the corresponding documentation.
For more information, see the SAP HANA Studio Installation and Update Guide.
Related Information
SAP Service Marketplace
SAP HANA Studio Installation and Update Guide
Maintenance Optimizer (MOPZ) in SAP Solution Manager
5.3 Updating SAP HANA System Components
5.3.1 Update SAP HANA System Components from a Local
Host
SAP HANA system components like the SAP HANA client, SAP HANA studio, HLM, Application Function
Libraries (AFL), SAP liveCache applications (SAP LCA), or SAP HANA smart data access (SDA) can be
updated on an SAP HANA system after installation from a local host using the SAP HANA lifecycle
management tool hdbclm(gui).
Prerequisites
The system component should have the same version as the SAP HANA DATABASE component. This leads to
the following possible variants:
58
P U B L I C

● Patch SAP HANA system components to a higher patch number within the same SPS (revision).
● Update both the SAP HANA system component and the SAP HANA DATABASE to a higher SPS (revision).
The SAP HANA lifecycle management tool hdblcm(gui) does not allow you to update the SAP HANA system
component and the SAP HANA DATABASE to different SPS (revision) numbers.
Context
Note
As of SPS 08, the product-specific AFLs are released individually and are no longer released as part of SAP
HANA AFL. Therefore, before updating AFL, it is necessary to perform a migration. For more information,
see SAP Note 2014334 in Related Information.
Procedure
1. Change to the following directory of the installation medium:
cd <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64/
2. Start the update task:
○ To update system components with the command line interface:
○ Start the hdblcm command line tool interactively:
./hdblcm
and enter the index of the update action, or
○ Start the tool with the update action specified:
./hdblcm action=update
○ To update system components with the graphical interface:
1. Start the hdblcmgui graphical interface tool:
./hdblcmgui
The hdblcmgui interface appears.
2. Review the detected software components, select Next.
3. Select Update existing system.
3. Select the SAP HANA system on which the system component should be updated.
4. Select the desired system component for update:
○ In the command line interface: Enter the index for Update <system component> .
○ In the graphical interface: Select the Update <system component> checkbox.
5. Continue with the update, by entering the <sid>adm and SYSTEM passwords. Confirm the update.
P U B L I C

Results
A system component has been updated on the SAP HANA system. The component list has been updated. A
log has been produced.
Related Information
SAP Note 2014334
5.3.2 Update SAP HANA System Components from a
Remote Host
SAP HANA system components like Application Function Libraries (AFL), SAP liveCache applications (SAP
LCA), or SAP HANA smart data access (SDA) can be updated on an SAP HANA system after installation from
a remote host using the SAP HANA lifecycle manager.
Prerequisites
The system component should have the same version as the SAP HANA DATABASE component. This leads to
the following possible variants:
● Patch the SAP HANA system components to a higher patch number within the same SP (revision).
● Update both the SAP HANA system components and the SAP HANA system to higher SP (revision).
The SAP HANA lifecycle manager will not allow you to update SAP HANA system components and SAP HANA
DATABASE to different SP (revision) numbers.
Context
SAP HANA system components are not installed by default on your SAP HANA system. This also means that
you do not install system components when you perform an automated update of your SAP HANA system to a
higher SPS, either. First you must add them, and you can then update them using the general update options.
Note
As of SPS 08, the product-specific AFLs are released individually and are no longer released as part of SAP
HANA AFL. Therefore, before updating AFL, it is necessary to perform a migration. For more information,
see SAP Note 2014334 in Related Information.
60
P U B L I C

Procedure
1. In your SAP HANA studio, add the system to which you want to connect.
Note
Use the fully qualified host name for all configuration actions (including Add System).
2. In the context menu of the system node in the SAP HANA Systems view, choose Lifecycle Management.
If you have not previously defined them, you need to enter the user credentials for <SID>adm user when
you call the SAP HANA lifecycle manager user interface for a specific SAP HANA system for the first time.
The following users and settings are needed:
○ User <SID>adm
○ You need to enter the user and password when calling the SAP HANA Update user interface for
the first time.
○ You can change the user and password in the context menu for the added system under
Properties SAP System Logon .
○ You can delete the user and password under Windows Preferences General Security
Secure Storage .
On the HLM user interface, you can choose the following options in the Update SAP HANA System field:
○ Update SAP HANA Lifecycle Manager (HLM)
We strongly recommend that you execute the tool self-update using the Update SAP HANA Lifecycle
Manager user interface option.
Keep in mind that if you do not have Internet access (for example, for security reasons), you need to
select Manually downloaded content as the source, and you need to have the relevant file already
available. You can download the newest archive available for this file, SAPHANALM*.SAR, in advance.
You have to download SAPHANALM*.SAR separately using the following link in the SAP Service
Marketplace: http://service.sap.com/swdc -> Support Packages and Patches-> Search for Support
Packages and Patches, where you need to search for HANA Lifecycle Manager.
Note that you need to provide the full path to the file, not the containing directory.
If you have Internet access, the self-update of the HLM can be executed automatically when you
choose the Update SAP HANA Lifecycle Manager (HLM) option. In this case, the SAP HANA studio
needs to be configured to work properly with SAP Service Marketplace.
○ Apply Support Package Stack (SPS - recommended scenario)
You can update all software components of SAP products that are deployed on the system by
applying a support package stack. Support package stacks are collections of support packages for
software components defined by SAP that work best together.
With this scenario, you can execute an update to a set of SAP HANA components defined by the SPS.
If the stack contains content components for deployment such as SAP HANA Interactive Education
(SHINE), SAP HANA EPM Service, SAP HANA UI toolkit for Information Access (INA), these
components will also be deployed.
This scenario ensures smooth and consistent update.
○ Apply Single Support Packages (Single SP)
If you want to update only particular software components that are deployed on the system and do
not want to apply complete support package stacks, you can apply single support packages.
P U B L I C

Furthermore, this scenario allows you to update components of an SAP HANA system which is
running in a high-availability environment. However, if the system whose components you are
updating is running in a high-availability environment, you cannot deploy SAP HANA content
components or update the SAP HANA studio repository.
The user interface will provide information about installed components’ versions, as well as the newer
(target) ones that are available. You can select the component version to which you want to update. If
you have selected SAP Service Marketplace as an update source, the SAP HANA lifecycle manager
offers updates only for components that are part of the SAP HANA product.
After you have selected the update scenario (apply SPS or Single SP), you need to select the source for
the update from the Select the update source field:
○ Automatically downloaded content (SAP Service Marketplace)
The content is automatically downloaded from SAP Service Marketplace. In this case, SAP Service
Marketplace offers new SP versions, not Single SPs. Therefore, SAP Service Marketplace does not
return the latest patch.
○ Manually downloaded content
In this case, you need to manually download the following files to any directory accessible by the
<SID>
adm user in the SAP HANA system:
○ Stack.xml file – XML file containing a model of SAP HANA in the form of product instances,
components, and their versions.
○ IMDB_SERVER*.SAR, IMDB_CLIENT*.SAR, IMC_STUDIO*.SAR, HANALDCTR*.SAR
(optionally, if you need it), SAPHOSTAGENT*.SAR – archives containing new content
needed for the update of the SAP HANA instances.
When updating to an SPS, you can download the files listed above from the SAP Service Marketplace at:
http://service.sap.com/swdc -> Support Packages and Patches-> Browse our Download Catalog ->
SAP NetWeaver and complementary products -> SAP HANA -> SAP HANA Platform Edition ->Support
Package Stack Download.
When updating to a Single SP (this means different components' versions) use:
http://service.sap.com/swdc -> Support Packages and Patches-> Search for Support Packages and
Patches ->Search for IMDB Server for example. Make sure you do the same for the required archives,
depending on the component you want to update (IMDB_SERVER*.SAR, IMDB_CLIENT*.SAR,
IMC_STUDIO*.SAR, HANALDCTR*.SAR, SAPHOSTAGENT*.SAR). When downloading your preferred
version, make sure that the selected archive is suitable for your operating system.
All archives must be located in the same directory as the stack.xml file.
For information about using the Maintenance Optimizer (MOPZ) in SAP Solution Manager to generate an
SPS and download the necessary archives, see SAP Solution Manager documentation.
3. During the update, if you are prompted for them, enter the user name and password for the <SID>adm
user.
4. Select the proposed software releases.
5. Select the update source and browse to the location of the system component.
6. Once the component version is displayed, choose the <Run> button. For some of the components you
have the option to skip the update.
7. Follow the instructions in the wizard.
62
P U B L I C

Note
Keep in mind that, after system components are updated, the SAP HANA database server is restarted.
Related Information
SAP Note 2014334
P U B L I C

6 Parameter Reference
Reference information is provided for each installation parameter.
Each parameter section includes some or all of the following information, depending on the complexity of the
parameter:
● Description - The function of the parameter.
● Syntax - The command line option format and configuration file format for the parameter. Interactive
mode (for both the GUI and CLI) do not require the use of parameter syntax.
● Options - The sub-specifications for the highly configurable parameters.
● Remarks - Important information about the parameters, including default values and whether the
parameter is offered in interactive mode. If it is not available in interactive mode, and the default value is
not wanted, the parameter must be specified as a command line option or in the configuration file in
combination with the call to the installation tool in interactive mode.
● Examples - The syntax in its common usage with acceptable parameter specifications.
● Related Information - Links to relevant sections in the current document or to other documents which
contain more detailed information.
6.1 action
Syntax
In the command line, the following syntax is used:
action=[install|update]
Remarks
The default for this parameter is action=install.
This parameter is available in interactive mode.
6.2 addhosts
installation.
Requirements
If the root user has a user name other than "root", the root_user parameter must
also be specified in combination with addhosts.
When used with hdblcm, the action parameter must be specified in combination with
addhosts.
64
P U B L I C
Parameter Reference

Syntax
addhosts=<host>[,<host2>]
where the <host> syntax is as follows:
<host_name>[:role=worker|standby][:group=<name>]
[:storage_partition=<number>]
Options
The following options can be used to configure the parameter:
● role - Specifies whether the host acts as worker or standby. A worker host
(default) is used for database processing. A standby host is idle and available for
failover in a high-availability environment.
● group - Specifies the host group ID for failover scenarios. If undefined, the host
group is named "default".
(The host group ID is NOT the same as the sapsys group ID, which is specified by
the parameter groupid).
● storage_partition -
Related Information
Creating a Multiple-Host System During Installation [page 46]
The SAP HANA lifecycle management tools hdblcm and hdblcmgui have the ability to build a multiple-host
system during installation in interactive mode, in batch mode, and with the available parameter specification
methods: interactively, using command line options, or with the configuration file.
root_user [page 78]
action [page 64]
6.3 autostart
Restarts instance after machine reboot.
Syntax
autostart=[0|1]
Parameter Reference
P U B L I C

where 0 = no, and 1 = yes
Remarks
The default for this parameter is autostart=0 (off).
6.4 batch
Runs the SAP HANA lifecycle management tool from the command line in batch mode using default values for
unspecified parameters. If mandatory values are omitted or if invalid values are specified, the program issues
an error message.
Syntax
batch
or, in short form:
b
Related Information
6.5 certificates_hostmap
Specifies the hostname used for generation of self-signed SSL certificates for the SAP host agent. This
certificate is used by the SAP HANA lifecycle manager (HLM).
Requirements
The key-value pair action=install must be specified in combination with
certificates_hostmap.
The HLM component must be specified for installation (default).
Syntax
action=install certificates_hostmap=<host name>=<certificate
host name>
or
66
P U B L I C
Parameter Reference

action=install H <host name>=<certificate host name>
Remarks
The default for this parameter is the current host.
Example
The following example generates certificates for two hosts in the long-form syntax:
./hdblcm action=install
certificates_hostmap=hananode01=server1.company.com
certificates_hostmap=hananode02=server2.company.com
The following example generates certificates for two hosts in the short-form syntax:
./hdblcm action=install H hananode01=server1.company.com H
hananode02=server2.company.com
In this example, not all required installation parameters are specified in the command line. If this is the case,
the remaining mandatory parameters are requested interactively.
Related Information
action [page 64]
components [page 69]
Specifies the components to be installed in combination with the server: studio, client, HLM, AFL, LCAPPS. It
is also possible to specify all components, or to specify a combination of components as a comma-
separated list. The server is always installed, even if it is not explicitly specified.
6.6 checkmnt
Specifies a non-standard shared file system, which can be accessed by all hosts during installation. This
parameter is typically used when the SID is included in the mountpoint.
Syntax
checkmnt=<path>
Parameter Reference
P U B L I C

6.7 client_path
Specifies the installation path for the client.
Syntax
client_path=<path for client installation>
Remarks
The default for this parameter is client_path=<sapmnt>/<SID>/hdbclient.
6.8 component_dirs
Specifies the installer component directories as a comma-separated list.
Syntax
component_dirs=<component directory>
6.9 component_medium
Specifies the location of the SAP HANA installation medium.
Syntax
component_medium=<directory of the installation medium>
6.10 component_root
Specifies the directory root to search for components.
Syntax
component_root=<component root directory>
68
P U B L I C
Parameter Reference

6.11 components
Specifies the components to be installed in combination with the server: studio, client, HLM, AFL, LCAPPS. It is
also possible to specify all components, or to specify a combination of components as a comma-separated
list. The server is always installed, even if it is not explicitly specified.
Requirements
The parameter action must be specified in combination with components.
Syntax
action=[install|update] components[=all|afl|client|hlm|
lcapps|server|studio]
Remarks
The default for this parameter is components=client,hlm,server,studio and
is dependent on the installer finding installation sources for the components. If the
installation sources for some components are not found, those components are not
installed, but rest of the components are installed.
Example
The following example installs the SAP HANA client, the SAP HANA studio, and the SAP HANA database
(always installed, despite the specification):
./hdblcm action=install components=client,studio
In this example, not all required installation parameters are specified in the command line. If this is the case,
the remaining mandatory parameters are requested interactively.
Related Information
action [page 64]
6.12 configfile
Loads a configuration file of call option key-value pairs to be passed to the SAP HANA lifecycle management
program.
Syntax
Parameter Reference
P U B L I C

configfile=<file path>
Remarks
The configuration file makes installation and configuration tasks more efficient and
reliable. For more information, see Related Information.
This complement to this call option is the call option dump_configfile_template.
Related Information
dump_configfile_template [page 71]
Specifies a file path to which a template configuration file is exported. The call options in the template
configuration file are set to their default values, and can be edited.
6.13 copy_repository
Syntax
copy_repository=<target path>
Remarks
The default for this parameter is copy_repository=/<sapmnt>/<SID>/
hdbstudio_update
6.14 datapath
Specifies the path to the data directory of the SAP HANA system.
Syntax
datapath=<path to data directory>
Remarks
The default for this parameter is datapath=/hana/data/<SID>.
70
P U B L I C
Parameter Reference

6.15 dump_configfile_template
Specifies a file path to which a template configuration file is exported. The call options in the template
configuration file are set to their default values, and can be edited.
Syntax
dump_configfile_template=<file path>
Remarks
The configuration file makes installation and configuration tasks more efficient and
reliable. For more information, see Related Information.
This complement to this call option is the call option configfile.
6.16 groupid
Specifies the SAP system (sapsys) group ID. This parameter is relevant only if a sapsys group does not already
exist on the host. If a sapsys group already exists, passing the groupid parameter does not alter the existing
group.
Syntax
groupid=<sapsys group ID>
or, in short form:
G <sapsys group ID>
Remarks
The default for this parameter is groupid=79.
6.17 help
Displays the inline help information.
Syntax
help
Parameter Reference
P U B L I C

or, in short form:
h
Remarks
A general help output is available for all SAP HANA lifecycle management programs.
Task-specific help output is available for some programs. Refer to the task
documentation for more details.
6.18 home
Specifies the home directory of the system administrator. This parameter is relevant only if the operating
system administrator (<sid>adm) does not exist prior to installation.
Syntax
home=<home directory>
Remarks
The default for this parameter is home=/usr/sap/<SID>/home.
6.19 host_agent_package
Specifies the RPM or SAR file of the SAP host agent. This parameter is only relevant if the HLM component is
selected for installation or update.
Syntax
host_agent_package=<SAP host agent file path>
6.20 hostname
Specifies the host name of the machine.
Syntax
hostname=<name of the host machine>
72
P U B L I C
Parameter Reference

or, in short form:
H <name of the host machine>
Remarks
Restrictions apply to host names in SAP systems. For more information, see SAP Note
611361 in Related Information.
The default for this parameter is the host name of the current machine.
Related Information
SAP Note 611361
6.21 install_hostagent
Enables the installation or update of the SAP host agent.
Syntax
install_hostagent[=off]
Remarks
The default for this parameter is install_hostagent (on).
6.22 install_ssh_key
Installs SSH key to access remote hosts.
Syntax
install_ssh_key[=off]
Remarks
The default for this parameter is install_ssh_key (on).
Parameter Reference
P U B L I C

6.23 internal_network
Specifies the internal subnet address in prefix notation (CIDR).
Syntax
internal_network=<address>
Example
The following example specifies the internal network address in prefix notation.
internal_network=192.168.1.0/24
6.24 list_systems
Displays a list of the installed SAP HANA systems on the current host, including the SAP system ID (SID),
instance number, version number, and hosts.
Syntax
list_systems
or, in short form:
L
6.25 logpath
Specifies the path to the log directory of the SAP HANA system.
Syntax
logpath=<path to log directory>
Remarks
The default for this parameter is logpath=/hana/log/<SID>.
74
P U B L I C
Parameter Reference

6.26 max_mem
Specifies the maximum memory allocation for a new system in MB.
Requirements
This parameter must be used in combination with restrict_max_mem. For more
information, see Related Information.
Syntax
max_mem=<MB>
Remarks
The default for this parameter is max_mem=0.
Related Information
restrict_max_mem [page 77]
Specifies whether maximum memory allocation is restricted for a new system
6.27 number
Requirements
The instance number must be a two-digit number between 00 and 97.
Syntax
number=<instance number>
or, in short form:
n <instance number>
Remarks
The default value for this parameter is the next successive un-used instance number.
Parameter Reference
P U B L I C

6.28 print_timezones
Lists all valid timezones, which can be specified by the timezone parameter.
Syntax
print_timezones
Related Information
timezone [page 82]
6.29 read_password_from_stdin
Reads passwords in XML syntax via input stream in batch mode.
Requirements
When using read_password_from_stdin in batch mode, the program looks for the
necessary passwords from an input stream. Therefore, the following two requirements
apply:
● A text file with XML tagging is created before calling the
read_password_from_stdin parameter during installation.
● Batch mode is specified from the command line.
Syntax
read_password_from_stdin=xml
Remarks
Passwords can be specified in several ways depending on your installation method of
choice. For more details, refer to the information about passwords specification.
Example
The following example shows the file containing the passwords:
Passwords.xml<?xml version="1.0" encoding="UTF-8"?>
<Passwords>
<password>SysAdm123456</password>
<system_user_password>DBsys12345678</system_user_password>
76
P U B L I C
Parameter Reference

<root_password>RootSecret007</root_password>
</Passwords>
Related Information
6.30 repository
Defines the source path from which the SAP HANA studio repository should be copied.
Syntax
repository=<source path>
or, in short form:
r <source path>
Remarks
If you do not specify this option, the repository contained in the installation kit is
copied.
6.31 restrict_max_mem
Specifies whether maximum memory allocation is restricted for a new system
Requirements
This parameter must be used in combination with max_mem. For more information, see
Syntax
restrict_max_mem
Remarks
Parameter Reference
P U B L I C

Related Information
max_mem [page 75]
Specifies the maximum memory allocation for a new system in MB.
6.32 root_user
Syntax
root_user=<user name>
Remarks
The default for this parameter is root_user=root.
6.33 sapmnt
Specifies the path to the SAP mount directory, which can be used as a shared directory between multiple
hosts.
Syntax
sapmnt=<installation path>
Remarks
The default for this parameter is sapmnt=/hana/shared.
This parameter can be specified once and automatically subsituted throughout all
parameter defaults, which use sapmnt as part of their default value.
6.34 scope
Performs task on the SAP HANA System (all hosts) or only on the local instance.This parameter is available for
update only.
Syntax
78
P U B L I C
Parameter Reference

scope=instance|system
Remarks
The default for this parameter is scope=system.
6.35 shell
Specifies a system administrator login shell. This parameter is relevant only if the operating system
Syntax
shell=<admin login shell>
Remarks
The default for this parameter is shell=/bin/sh.
6.36 sid
Specifies a system ID. The SAP system ID (SID) is the identifier for the SAP HANA system.
Requirements
● The ID must be unique throughout your organization and consistent throughout
your SAP system installation landscape.
● If you want to install an additional application server instance, make sure that no
gateway instance with the same SAP SID exists in your SAP system landscape.
● The ID must consist of exactly three alphanumeric characters. Only uppercase
letters are allowed. The first character must be a letter (not a digit).
● The following IDs are reserved and cannot be used: ADD ALL AMD AND ANY ARE
ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG
LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF
ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR.
Syntax
sid=<SID>
Parameter Reference
P U B L I C

or, in short form:
s <SID>
Remarks
This parameter can be specified once and automatically substituted throughout all
parameter defaults, which use sid as part of their default value.
6.37 storage_cfg
Specifies a location where a global.ini is defined. It is possible to set up a storage connector, allowing SAP
HANA to use hardware vendor-specific scripts for automated resource allocation and input/output fencing
during failover.
Requirements
Resource allocation scripts are dependent on the hardware used. Therefore, only the
hardware partners can provide correct scripts.
Syntax
storage_cfg=<directory of the storage configuration>
Related Information
6.38 studio_path
Specifies the installation path for the SAP HANA studio.
Syntax
studio_path=<installation path>
Remarks
The default for this parameter is studio_path=<sapmnt>/<SID>/hdbstudio.
80
P U B L I C
Parameter Reference

6.39 studio_repository
Enables the copying of the SAP HANA studio repository. When enabled (default), the SAP HANA studio
repository is copied to the location defined by copy_repository from the location defined by repository.
Syntax
studio_repository[=off]
Remarks
The default for this parameter is studio_repository (on).
Related Information
copy_repository [page 70]
repository [page 77]
Defines the source path from which the SAP HANA studio repository should be copied.
6.40 system_usage
Specifies the usage type of the system to be installed. This setting is stored in the global.ini file, and can be
used to identify the intended usage of the system.
Syntax
system_usage=[production|test|development|custom]
Remarks
The default for this parameter is system_usage=custom.
For information about implementing the next steps of the system usage type, see the
SAP HANA Administration Guide.
Related Information
Parameter Reference
P U B L I C

6.41 system_user
Specifies the system user of the database.
Syntax
system_user=<name>
Remarks
The default for this parameter is system_user=SYSTEM.
6.42 timezone
Syntax
timezone=<timezone>
Remarks
The default for this parameter is timezone=UTC.
To display a list of all valid timezones, call the print_timezones parameter.
Related Information
print_timezones [page 76]
Lists all valid timezones, which can be specified by the timezone parameter.
6.43 userid
Requirements
The user ID must be a value in the range of 1000-32000.
82
P U B L I C
Parameter Reference

Syntax
userid=<ID number>
or, in short form:
U <ID number>
Remarks
The default value for this parameter is the next successive un-used user ID number.
6.44 version
Displays the version of the SAP HANA lifecycle management program.
Syntax
version
or, in short form:
v
6.45 vm
Specifies the path of the Java runtime file. This parameter is only relevant if the SAP HANA studio is selected
for installation or update.
Syntax
vm=<Java path>
Remarks
The default value for this parameter is the Java runtime that is found in the
environment variable PATH, or the Java runtime specified with the environment
variable JAVA_HOME.
Parameter Reference
P U B L I C

7 Tutorials
The following is a sampling of general use cases, which illustrate the functionality and versatility of the SAP
HANA hdblcm lifecycle management tool.
Tutorial: Installing a Multiple-Host System Using a Configuration File in
Batch Mode
The following use case installs a multiple-host system, with two hosts (both worker). The installer reads the
parameters from a configuration file. The installation is run in batch mode, so that once the installation is
started, both host installations are configured without any further input required.
1. The following are the desired parameters for the SAP HANA server. They are specified in a combination of
command line options and configuration file:
Parameter Input Location Specified
Passwords # Root User Password
...
# SAP Host Agent (sapadm)
Password sapadm_password=Agent1234
...
# System Administrator
Password password=Adm1234
....
Configuration file
action action=install CLI
sid sid=ABC Configuration file
number number=01 Configuration file
root_user root_user=sysroot Configuration file
addhosts addhosts=hananode1 Configuration file
configfile configfile=/home/sysroot/hdblcm_SPS7.cfg CLI
batch b CLI
userid userid=55 Configuration file
84
P U B L I C
Tutorials

groupid groupid=110 Configuration file
storage_cfg storage_cfg=/home/sysroot/storage Configuration file
2. The reusable installation parameter values are saved in the following configuration file:
[Server]
# Additional Hosts
addhosts=hananode1
# Root User Name (Default: root)
root_user=sysroot
sid=ABC
# Instance Number (Default: <next available number>)
number=01
password=Adm1234
# System Administrator User ID (Default: <next available number>)
userid=55
# ID of User Group 'sapsys' (Default: 79)
groupid=110
# Directory containing a storage configuration
storage_cfg=/home/sysroot/storage
3. Now the installer can be called from the command line, with the remaining parameters read from the
configuration file. The installation is run in batch mode, so no follow-up confirmation is required.
./hdblcm action=install configfile=/home/sysroot/hdblcm_SPS7.cfg b
Tutorial: Overwriting Configuration File Parameters with Command Line
Parameters
The following use case uses the same configuration file as above. However, this time, the desired system
deviates slightly from the one defined the configuration file. By specifying parameters in the command line
which are already specified in the configuration file, the configuration file settings are effectively overwritten.
The command line parameters take precedence over the configuration file parameters.
1. The following are the desired parameters for the SAP HANA server. They are specified in a combination of
command line and configuration file:
Tutorials
P U B L I C

Parameter Input Location Specified Used for Installa
tion
Passwords # Root User Password
...
# SAP Host Agent (sapadm)
Password sapadm_pass
word=Agent1234
...
# System Administrator
Password password=Adm1234
....
# Database User (SYSTEM)
Password
Configuration file yes
action action=install CLI yes
sid sid=ABC Configuration file no
sid sid=DB1 CLI yes
number number=01 Configuration file no
number n 01 CLI yes
root_user root_user=sysroot Configuration file yes
addhosts addhosts=hananode1 Configuration file no
addhosts addhosts=hananode1,hana
node2:role=standby
CLI yes
configfile configfile=/home/sysroot/
hdblcm_SPS7.cfg
CLI yes
batch b CLI yes
userid userid=55 Configuration file yes
groupid groupid=110 Configuration file yes
storage_cfg storage_cfg=/home/sysroot/
storage
Configuration file no
86
P U B L I C
Tutorials

Parameter Input Location Specified Used for Installa
tion
storage_cfg storage_cfg=/home/sysroot/
storage_new
CLI yes
2. The reusable installation parameter values are saved in the following configuration file:
[Server]
# Additional Hosts
addhosts=hananode1
root_user=sysroot
sid=ABC
number=01
password=Adm1234
userid=55
groupid=110
storage_cfg=/home/sysroot/storage
3. Now the installer can be called from the command line, with the remaining parameters read from the
configuration file. The installation is run in batch mode, so no follow-up confirmation is required.
./hdblcm action=install n 01 sid=DB1
addhosts=hananode1,hananode2:role=standby storage_cfg=/home/sysroot/
storage_new configfile=/home/sysroot/hdblcm_SPS7.cfg b
Tutorial: Installing a Single-Host System with Passwords Read from XML
Standard Input Stream
The following use case installs a single-host system. The installer reads the parameters from the command
line, and the passwords from a standard input stream. The installation is run in batch mode, so that once the
installation is started, the host is configured without any further input required.
1. The following are the desired parameters for the SAP HANA server, to be entered in command line in
combination with the call to the installer.
Tutorials
P U B L I C

Passwords read_password_from_stdin=xml CLI
sid sid=P02 CLI
number number=01 CLI
root_user root_user=sysroot CLI
batch batch CLI
2. The following password file is prepared with the accepted XML syntax:
hdb_passwords.xml<?xml version="1.0" encoding= "UTF-8"?>
<Passwords>
<password>Adm1234</password>
<system_user_password>Sys1234</system_user_password>
<root_password>Root1234</root_password>
<sapadm_password>Agent1234</sapadm_password>
</Passwords>
3. Now the installer can be called from the command line, with the passwords read from a standard input
stream. The installation is run in batch mode, so no follow-up confirmation is required.
cat ~/hdb_passwords.xml | ./hdblcm sid=P02 number 01 root_user=sysroot
read_password_from_stdin=xml batch
Related Information
action [page 64]
addhosts [page 64]
installation.
batch [page 66]
Runs the SAP HANA lifecycle management tool from the command line in batch mode using default values
for unspecified parameters. If mandatory values are omitted or if invalid values are specified, the program
issues an error message.
configfile [page 69]
Loads a configuration file of call option key-value pairs to be passed to the SAP HANA lifecycle management
program.
groupid [page 71]
88
P U B L I C
Tutorials

Specifies the SAP system (sapsys) group ID. This parameter is relevant only if a sapsys group does not
already exist on the host. If a sapsys group already exists, passing the groupid parameter does not alter the
existing group.
number [page 75]
read_password_from_stdin [page 76]
Reads passwords in XML syntax via input stream in batch mode.
root_user [page 78]
sid [page 79]
Specifies a system ID. The SAP system ID (SID) is the identifier for the SAP HANA system.
storage_cfg [page 80]
Specifies a location where a global.ini is defined. It is possible to set up a storage connector, allowing
SAP HANA to use hardware vendor-specific scripts for automated resource allocation and input/output
fencing during failover.
userid [page 82]
Tutorials
P U B L I C

8 Managing the SAP HANA System After
Installation
After the installation has finished, it is recommended to perform the following tasks:
● Perform a system backup.
We strongly recommend that you perform an initial backup of your system once you have finished the
installation. For more details, see the system backup information in the SAP HANA Administration Guide.
● Change the passwords.
If you are receiving an newly installed SAP HANA platform from a hardware provider, it is recommended to
update the passwords so they comply with your security guidelines. For more information, see the SAP
HANA Security Guide.
● Finalize your customization.
Use the SAP HANA lifecycle management tools to adapt the existing configuration, if necessary. For more
information, see the SAP HANA Administration Guide.
The following sections in this chapter are optional tasks that can be performed as part of installation
management.
Related Information
SAP HANA Security Guide
8.1 Starting and Stopping the SAP HANA System
After the installation has finished successfully, the SAP HANA system is up and running. So you do not need to
start the SAP HANA system.
Context
However, if required, you can start and stop the SAP HANA system from the command line in one of the
following ways:
Procedure
● By using the sapcontrol program:
90
P U B L I C
Managing the SAP HANA System After Installation

a) Log on to the SAP HANA system host as a user with root authorization.
b) Execute one of the following commands:
○ Start the SAP HANA system by entering the following command: /usr/sap/hostctrl/exe/
sapcontrol nr <Instance_Number> function Start
○ Stop the SAP HANA system by entering the following command: /usr/sap/hostctrl/exe/
sapcontrol nr <Instance_Number> –function Stop
● By using the HDB program:
a) Log on to the SAP HANA system host as user <sapsid>adm.
b) Execute one of the following commands:
○ Start the SAP HANA system by entering the following command: /usr/sap/<SAPSID>/
<Instance_Name>/HDB start
Example:
/usr/sap/KB1/HDB26/HDB start
○ Stop the SAP HANA system by entering the following command: /usr/sap/<SAPSID>/
<Instance_Name>/HDB stop
Example:
/usr/sap/KB1/HDB26/HDB stop
Note
The SAP HANA database does not start automatically by default when the SAP HANA system
is started. But you can enable an automated start of this kind. For more information, see
Related Information
Enabling Automatic Start of the SAP HANA Database [page 93]
8.2 Displaying the Process List
It is possible to display the SAP HANA system processes from the command line.
Prerequisites
You are logged on to the SAP HANA host as the root user.
P U B L I C

Procedure
Display the SAP HANA system processes by running the following from the command line:
/usr/sap/hostctrl/exe/sapcontrol nr <instancenr> function GetProcessList
You can also display the SAP HANA system processes using the SAP Microsoft Management Console
(SAP MMC) from a Microsoft Windows PC.
Results
Example
Displaying the Process List
/usr/sap/hostctrl/exe/sapcontrol nr 00 function GetProcessList
10.10.2013 14:55:01
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
hdbdaemon, HDB Daemon, GREEN, Running, 2013 10 10 09:26:02, 3:28:59, 2606
hdbnameserver, HDB Nameserver, GREEN, Running, 2013 10 10 09:26:03, 3:28:58,
2624
hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2013 10 10 09:26:11,
3:28:50, 2689
hdbindexserver, HDB Indexserver, GREEN, Running, 2013 10 10 09:26:13, 3:28:48,
2719
hdbxsengine, HDB XSEngine, GREEN, Running, 2013 10 10 09:26:13, 3:28:48, 2727
sapwebdisp_hdb, SAP WebDispatcher, GREEN, Running, 2013 10 10 09:29:06,
3:25:55, 3335
hdbcompileserver, HDB Compileserver, GREEN, Running, 2013 10 10 09:26:11,
3:28:50, 2693
8.3 Creating a Database User for Update and Rename
As the most powerful database user, SYSTEM is not intended for use in production systems. Create a
restricted database user for updating and renaming a system.
For security reasons, the SYSTEM user might not be available during a system update. It is, therefore, required
to import the delivery units as another user.
A database user should be created with the following granted roles and object privileges:
● Granted Roles: CONTENT_ADMIN
● Object Privileges: _SYS_REPO (SELECT)
92
P U B L I C

By calling one of the update or rename LCM tools with the system_user option specified, the previously
defined database user is used in place of SYSTEM to authenticate the configuration task.
Related Information
system_user [page 82]
Specifies the system user of the database.
8.4 Enabling Automatic Start of the SAP HANA Database
Prerequisites
By default the SAP HANA database is configured so that it is not started automatically when the SAP HANA
host is rebooted.
Context
If required, you can change this configuration by modifying the profile of the SAP HANA database as follows:
Procedure
1. Log on to the SAP HANA host as a user with root authorization.
2. Change to the system profile directory /usr/sap/<SAPSID>/SYS/profile.
3. Edit the profile <SID>_HDB<Instance_No>_<host_name>.
4. Change the parameter setting Autostart = 0 to Autostart = 1 .
5. Save the profile <SID>_HDB<Instance_No>_<host_name>.
Results
The SAP HANA database is started automatically when the SAP HANA host is rebooted.
P U B L I C

8.5 Enable Data Volume Encryption
To ensure that the SAP HANA database can always be restored to its most recent committed state, all data is
periodically copied to disk. Privacy of data on disk can be ensured by enabling data volume encryption.
Prerequisites
● You have installed a cryptographic service provider on the SAP HANA server. SAP HANA supports the
following cryptographic libraries:
○ CommonCryptoLib (recommended)
You must download CommonCryptoLib from SAP Service Marketplace. CommonCryptoLib is the
recommended cryptographic service provider. The default path for library lookup is set with the
environment variable <$DIR_SECURITY_LIB>. The default path is /usr/sap/<SID>/SYS/global/
security/lib.
○ OpenSSL
The OpenSSL library is installed by default as part of the operating system installation.
○ SAP Cryptographic Library
The SAP Cryptographic Library is supported for backward compatibility only in existing installations.
We recommend upgrading to CommonCryptoLib.
Caution
The distribution of the CommonCryptoLib is subject to and controlled by German export regulations
and is not available to all customers. In addition, usage of the CommonCryptoLib or OpenSSL library
may be subject to local regulations of your own country that may further restrict the import, use, and
export or re-export of cryptographic software. If you have any further questions about this issue,
contact your local SAP office.
● You are logged on to the SAP HANA host as the operating system user, <sid>adm.
Context
Data is stored in persistent disk volumes that are organized in pages. If data volume encryption is enabled, all
pages that reside in the data area on the disk are encrypted using the AES-256-CBC algorithm. Pages are
transparently decrypted as part of the load process. When pages reside in memory they are therefore not
encrypted and there is no performance overhead for in-memory page accesses. When changes to data are
persisted to disk, the relevant pages are automatically encrypted as part of the write operation.
Enabling data volume encryption does not increase data size.
94
P U B L I C

Procedure
1. Generate a root encryption key using the hdbnsutil program.
Caution
Do not generate the root encryption key after you have enabled data volume encryption or created a
remote source in an SAP HANA smart data access scenario, since this would render the SAP HANA
database unusable.
The command is as follows:
#hdbnsutil generateRootKeys type=ALL
2. Enable data volume encryption by executing the following SQL command:
ALTER SYSTEM PERSISTENCE ENCRYPTION ON
Results
Encryption is now active. We recommend that you periodically change the encryption key used to encrypt
pages in the data area in line with your organization's security policy.
Related Information
SAP Note 1848999 - Central Note for CommonCryptoLib 8 (replacing SAPCRYPTOLIB)
8.6 Uninstall the SAP HANA System
If required, you can uninstall the previously installed SAP HANA components by running either the hdblcm or
hdblcmgui SAP HANA lifecycle management tools from the /<sapmnt>/<SID>/hdblcm directory.
Prerequisites
● There is an installed SAP HANA system that should be uninstalled.
● You are logged in as root user on the SAP HANA system.
P U B L I C

Note
Using hdblcm, it is possible to remove server, client, studio, AFL, LCAPPS or HLM components, but it is not
possible to remove the SAP host agent or the SMD agent. If you need to uninstall the SMD agent, see SAP
Note 1858920 in Related Information.
Procedure
1. An hdblcm directory, in which the uninstallation script is contained, is created during system installation.
Change to the directory containing the script:
cd /<sapmnt>/<SID>/hdblcm
2. Start the uninstallation script. This can be performed with both hdblcmgui and hdblcm.
○ Interactive mode with hdblcmgui:
1. Start the hdblcmgui from the command line:
./hdblcmgui
2. When the wizard appears, select the system components for installation, then select Uninstall.
When the process is complete a log is produced.
○ Interactive mode with hdblcm:
1. Start the hdblcm tool from the command line with the uninstall parameter specified.
./hdblcm uninstall
It is also possible to uninstall individual components by specifying
components=<component1>,<component2> in combination with the uninstall parameter. For
detailed information about the uninstallation parameters, review the inline help before uninstalling
from the command line:
./hdblcm uninstall h
2. When the process is complete a log is produced.
Results
The selected components are uninstalled. A log file is available.
Related Information
SAP Note 1858920
96
P U B L I C

9 Troubleshooting
Troubleshooting should be referred to if the installation fails for an unknown reason, or for workarounds in
special circumstances.
Checking the Log Files
The SAP HANA lifecycle management tools hdblcm and hdblcmgui write log files during installation. The
most recent log file is always available under /var/tmp/hdblcm.log or /var/tmp/hdblcmgui.log.
Additionally, a copy of the log files is archived in the directory hdb_<SID>_hdblcm_<action>_<date>..
Since the SAP HANA lifecycle management tools hdblcm and hdblcmgui are wrappers for underlying
component installers, it is also possible to check the component logs. It is recommended to review and
analyze the SAP HANA lifecycle management tools hdblcm and hdblcmgui logs first. Once the source of the
problem is narrowed down to a specific component, then the component logs can be further analyzed.
The component log files are stored in the following path:
/var/tmp/hdb_<SID>_<action>_<time_stamp>
where <action> :: = install | update | addhost | uninstall | and so on
The following log files are written during performing the action:
● <hdbcommand>.log: can be read using a text editor
● <hdbcommand>.msg: XML format for the display in the installation tool with the GUI
● <hostname>_tracediff.tgz: provides a delta analysis of the original trace files, makes a detailed
analysis more easy
You can also view the last three log files in the SAP HANA studio using the administration function Diagnosis
Files. For more information, see the SAP HANA Database - Administration Guide.
Repairing a Partially Installed System
If the installation stops without fully installing, and you would like to remove the components and start over,
run the component uninstaller (hdbuninst) for each component individually. Then start the installation over
again using hdblcm.
Accessing the Underlying Installer Components (pass_through_help)
Since hdblcm and hdblcmgui are wrapper tools, in some troubleshooting cases, it may be useful to pass
component options on to the underlying component tools (hdbinst or hdbupd) in combination with the call to
the hdblcm or hdblcmgui SAP HANA lifecycle management tools.
Troubleshooting
P U B L I C

To view the available underlying component parameters as extended help output, use the
pass_through_help parameter. The action parameter and help or h must be specified in combination
with pass_through_help.
Syntax
To view the help output for the installation or the update pass_through_help
parameters, use the following syntax:
action=[install|update] pass_through_help help
or
action=[install|update] pass_through_help h
Table 3: Available Parameters for pass_through_help
Parameter Install Update
hdbinst_client_ignore=<check1>[]...
Ignores failing prerequisite checks (check_version)
hdbinst_client_path=<hdbinst_client_path>
Installation path [default: hdbinst_client_path=/usr/sap/
hdbclient]
hdbinst_client_sapmnt=<installation_path>
Mount point for shared client installations
[default: hdbinst_client_sapmnt=/hana/shared]
hdbinst_plugin_ignore=<check1>[]...
Ignores failing prerequisite checks (check_busy_files, check_ver
sion)
hdbinst_plugin_nostart
Does not start the instance after installation
hdbinst_server_ignore=<check1>[]...
Ignores failing prerequisite checks (check_busy_files,
check_diskspace, check_hosts, check_license,
check_min_mem, check_pending_upgrade, check_plugin_de
pendencies, check_secondary_system, check_version)
hdbinst_server_import_content[=off]
Imports delivery units [default: hdbinst_server_import_con
tent]
hdbinst_server_xs_engine[=off]
Enables the XS engine [default: hdbinst_server_xs_engine]
hdbinst_server_xs_engine_http_port=<port>
98
P U B L I C
Troubleshooting

Parameter Install Update
Specifies the HTTP port of the XS engine
hdbinst_server_xs_engine_https_port=<port>
Specifies the HTTPS port of the XS engine
hdbinst_studio_path=<hdbinst_studio_path>
Installation path [default: hdbinst_studio_path=/usr/sap/
hdbstudio]
hdbupd_server_ignore=<check1>[]...
Ignores failing prerequisite checks (check_busy_files,
check_diskspace, check_hosts, check_license,
check_min_mem, check_pending_upgrade, check_plugin_de
pendencies, check_secondary_system, check_version)
hdbupd_server_import_content[=off]
Imports delivery units [default: hdbupd_server_import_content]
hdbupd_server_nostart
Does not start the instance after upgrade
hdbupd_server_xs_engine[=off]
Enables the XS engine [default: hdbupd_server_xs_engine]
hdbupd_server_xs_engine_http_port=<port>
Specifies the HTTP port of the XS engine
hdbupd_server_xs_engine_https_port=<port>
Specifies the HTTPS port of the XS engine
XML password tag: <hdbinst_plugin_password>
System administrator password
Enabling the Installer Trace
If the installer crashes or loops it may make sense to trace the installer until the problem occurs, open a CSS
ticket, and attach the trace file for further analysis. You can switch on the installer trace by setting the
environment variable HDB_INSTALLER_TRACE_FILE to <tracefilename>. The directory containing the
trace file must already exist.
Troubleshooting
P U B L I C

Locating all SAP HANA File System Components
In addition to the main components installed in the default file systems described in Recommended File
System Layout [page 14], it may also be necessary to locate the temporary files from the SAP HANA system.
They can be found in the following directories:
● SAP HANA DB files:
○ /var/lib/hdb - IPC data (volatile)
○ /var/tmp - Installer log files, HDB_alive_*
○ /tmp - .hdb_*_lock (volatile)
● sapstartsrv files:
○ /etc/init.d/sapinit* - Boot script
○ /tmp/.sap* - Sockets, lock files (volatile)
100
P U B L I C
Troubleshooting

10 Appendix
The following information is provided for reference and troubleshooting.
10.1 Configuration File Template
The following is the configuration file template that is generated using the dump_configfile_template
parameter in combination with the hdblcm installer.
[General]
# Location of SAP HANA DVD media (Default: <DVD directory>)
component_medium=
# Comma separated list of component directories
component_dirs=
# Directory root to search for components
component_root=
# Select the action to be either installation or update (Default: install)
action=install
# Print all timezones (Default: n)
print_timezones=0
# Index (Default: client,studio,hlm)
components=
[Server]
# Additional Hosts
addhosts=
# Nonstandard Shared File System
checkmnt=
# Installation Path (Default: /hana/shared)
sapmnt=/hana/shared
root_user=root
root_password=
# Internal Network Address
internal_network=
sid=
number=
# Location of Data Volumes (Default: /hana/data/${sid})
datapath=/hana/data/${sid}
# Location of Log Volumes (Default: /hana/log/${sid})
Appendix
P U B L I C

logpath=/hana/log/${sid}
# Host Name of this Location (Default: <current host>)
hostname=
# Enables the installation or upgrade of the SAP Host Agent (Default: y)
install_hostagent=1
sapadm_password=
password=
# System Administrator Home Directory (Default: /usr/sap/${sid}/home)
home=/usr/sap/${sid}/home
# System Administrator Login Shell (Default: /bin/sh)
shell=/bin/sh
userid=
groupid=
# System Administrator Timezone (Default: UTC)
timezone=UTC
storage_cfg=
system_user_password=
# Restart instance after machine reboot? (Default: n)
autostart=0
[LifecycleManager]
# SAP Host Agent Package Location
host_agent_package=
# Certificate Host Names
certificates_hostmap=
[Client]
# Client Installation Path (Default: /hana/shared/${sid}/hdbclient)
client_path=${sapmnt}/${sid}/hdbclient
[Studio]
# SAP HANA Studio Installation Path (Default: /hana/shared/${sid}/hdbstudio)
studio_path=${sapmnt}/${sid}/hdbstudio
# Enables copying of SAP HANA Studio repository (Default: y)
studio_repository=1
# Target path to which SAP HANA Studio repository should be copied
copy_repository=
# Java Runtime (Default: /usr/lib64/jvm/jre/bin/java)
vm=/usr/lib64/jvm/jre/bin/java
# Source path of SAP HANA Studio repository
repository=
102
P U B L I C
Appendix

10.2 Important SAP Notes
Read the following SAP Notes before you start the installation. These SAP Notes contain the latest information
about the installation, as well as corrections to the installation documentation.
Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service
Marketplace at https://service.sap.com/notes .
SAP Note Number Title
1514967 SAP HANA: Central Note
2004651 SAP HANA Platform SPS 08 Release Note
1523337 SAP HANA Database: Central Note
2000003 FAQ: SAP HANA
1944799 SAP HANA Guidelines for SLES Operating System
2009879 SAP HANA Guidelines for RedHat Enterprise Linux (RHEL)
1681092 Support for multiple SAP HANA databases on a single SAP
HANA appliance
1976729 Application Component Hierarchy for SAP HANA
1661202 Support for multiple applications on SAP HANA
1828400 SAPUI5 tools disappeared after updating HANA Studio
1917938 Migrating the Statistic Server During Update to SPS 07
1927949
Standard Behavior for SAP Logon Tickets
1577128 Supported clients for SAP HANA
1514966 SAP HANA: Sizing SAP HANA Database
1637145 SAP BW on HANA: Sizing SAP HANA Database
1793345 Sizing for Suite on HANA
1824819 Optimal settings for SLES 11 SP2 and SLES 11 for SAP SP2
1597355 Swap space recommendation for Linux
For the SAP HANA system there are no special
requirements regarding swap space.
Check the current SAP Notes for the various parts of SAP HANA by searching for any of the following
application areas:
Appendix
P U B L I C

SAP HANA Application Services
● HAN-AS SAP HANA Application Services
● HAN-AS-INA SAP HANA InA Tools and Infrastructure
● HAN-AS-INA-FLY SAP HANA InA Firefly
● HAN-AS-INA-MDS SAP HANA InA Multidimensional Service
● HAN-AS-INA-SCV SAP HANA InA Service
● HAN-AS-INA-UI SAP HANA InA Toolkit, Fiori Search UI
● HAN-AS-RPO SAP HANA Repository
● HAN-AS-RST SAP HANA Development Environment REST API
● HAN-AS-RUL SAP HANA Rules Framework
● HAN-AS-XS SAP HANA Extended Application Services
● HAN-AS-XS-ADM SAP HANA XS Administration
● HAN-AS-XS-JOB SAP HANA XS Scheduled Jobs
● HAN-AS-XSA SAP HANA XS Basis Applications
● HAN-AS-XSA-TM SAP HANA Task management
SAP HANA Database
● HAN-DB SAP HANA Database
● HAN-DB-AFL SAP HANA Application Function Library
● HAN-DB-AFL-DQ SAP HANA Data Quality Library
● HAN-DB-AFL-PAL SAP HANA Predictive Analysis Library
● HAN-DB-AFL-SAL SAP HANA Self Service Analytics Library
● HAN-DB-AFL-SCA SAP HANA Supply Chain Algorithm Library
● HAN-DB-AFL-SOP SAP HANA Sales and Operations Planning
● HAN-DB-AFL-UDF SAP HANA Unified Demand Forecast
● HAN-DB-BAC SAP HANA Backup and Recovery
● HAN-DB-CDS SAP HANA Core Data Services
● HAN-DB-CLI SAP HANA Clients (JDBC, ODBC)
● HAN-DB-ENG SAP HANA DB Engines
● HAN-DB-ENG-BW SAP HANA BW Engine
● HAN-DB-ENG-GPH SAP HANA Graph Engine
● HAN-DB-ENG-GPH-API SAP HANA Graph Engine API
● HAN-DB-ENG-GPH-WIP SAP HANA Graph Engine Wipe
● HAN-DB-ENG-PLE SAP HANA Planning Engine
● HAN-DB-ENG-SPA SAP HANA Spatial Engine
● HAN-DB-ENG-TXT SAP HANA Text Engine
● HAN-DB-ENG-VE SAP HANA Velocity Engine
● HAN-DB-EPM SAP HANA Enterprise Performance Management Platform
● HAN-DB-EPM-PLT SAP HANA EPM Platform
● HAN-DB-EPM-XSL SAP HANA EPM XSJS library
● HAN-DB-HA SAP HANA High Availability
● HAN-DB-LVC SAP HANA integrated liveCache
● HAN-DB-MDX SAP HANA MDX Engine/Excel Client
● HAN-DB-MON SAP HANA Monitoring
● HAN-DB-PER SAP HANA Database Persistence
104
P U B L I C
Appendix

● HAN-DB-R SAP HANA Integration with R
● HAN-DB-SCR SAP HANA SQL Script
● HAN-DB-SDA SAP HANA Smart Data Access
● HAN-DB-SEC SAP HANA Security and User Management
● BC-DB-LCA SAP HANA liveCache Applications
● BC-CCM-HAG SAP Host Agent
● SV-SMG-DIA SAP Solution Manager Diagnostics Agent
SAP HANA Data Provisioning Services
● HAN-DP SAP HANA Data Provisioning Services
● HAN-DP-DS SAP Data Services
● HAN-DP-DXC SAP HANA Direct Extractor Connector
● HAN-DP-LTR SAP Landscape Transformation Replication Server
● HAN-DP-REP SAP Replication Server
SAP HANA Information Composer
● HAN-IC SAP HANA Information Composer
SAP HANA Lifecycle Management
● HAN-LM SAP HANA Lifecycle Management
● HAN-LM-APP SAP HANA Application Lifecycle Management
● HAN-LM-INS SAP HANA Installation
● HAN-LM-INS-DB Installation of HANA Database
● HAN-LM-INS-SAP Installation of SAP Systems on HANA
● HAN-LM-PLT SAP HANA Platform Lifecycle Management
● HAN-LM-UPG SAP HANA Upgrade
● HAN-LM-UPG-DB Upgrade of HANA Database
● HAN-LM-UPG-SAP Upgrade of SAP Systems on HANA
SAP HANA Studio (Eclipse)
● HAN-STD SAP HANA Studio (Eclipse)
● HAN-STD-ADM SAP HANA Administration
● HAN-STD-ADM-BAC SAP HANA Backup and Recovery (Studio)
● HAN-STD-ADM-DBA SAP HANA Database Administration and Monitoring
● HAN-STD-ADM-PVZ SAP HANA Plan Visualizer
● HAN-STD-ADM-SEC SAP HANA Security and User Management (Studio)
● HAN-STD-DEV SAP HANA Development Tools
● HAN-STD-DEV-CDS SAP HANA CDS Tools
● HAN-STD-DEV-CDS-GRA SAP HANA CDS Graphical Modeler
● HAN-STD-DEV-DP SAP HANA Data Provisioning Modeler
● HAN-STD-DEV-EPM SAP HANA EPM Modeler
● HAN-STD-DEV-MOD SAP HANA Analytical Modeling
● HAN-STD-DEV-MOD-CLT SAP HANA Analytical Modeling - Client Component
● HAN-STD-DEV-MOD-SRV SAP HANA Analytical Modeling - Server Component
● HAN-STD-DEV-RUL SAP HANA Rules Editor
● HAN-STD-DEV-SCR SAP HANA SQL Script Editor/Debugger
Appendix
P U B L I C

● HAN-STD-DEV-TP SAP HANA Tools Platform / Team Provider
● HAN-STD-DEV-TP-CM SAP HANA Development Change Management
● HAN-STD-DEV-UIS SAP HANA UI Integration Services
● HAN-STD-DEV-XS SAP HANA XS Editors and Wizards
SAP HANA Web IDE
● HAN-WDE SAP HANA Web IDE
SAP HANA Database (CCMS, Porting and DB Interface)
● BC-DB-HDB-CCM CCMS for SAP HANA
● BC-DB-HDB-POR DB Porting for SAP HANA
● BC-DB-HDB-SYS SAP HANA database interface/DBMS
End User Clients
● BI-BIP, BI-BIP-CMC Business intelligence platform (formerly known as BOE)
● BI-RA-EXP SAP BusinessObjects Explorer
● BI-RA-CR, BI-BIP-CRS SAP Crystal Reports
● BI-RA-XL Dashboard Designer
● BI-BIP-IDT Information design tool
● BI-RA-WBI Web Intelligence
● BI-RA-AO-XLA MS Excel Add-In
The search also supports using the wildcard asterisk (*), so you can, for example, also search for BC-DB-HDB*
or similar and you will get results for all sub-components.
Reporting Incidents
If you encounter any problems with the software, report an incident on the SAP Service Marketplace at http://
service.sap.com/incident .
In addition, the Customer Interaction Center (CIC) is available 24 x 7 in every region to help you resolve any
issues you may run into (https://service.sap.com/supportcenters ).
The CIC requires a valid S-user number. To create an S-user ID, follow the steps in this guide (SAP Active
Global Support Reference Guide ).
When reporting an incident, you can choose from the above list of components for the relevant software part.
106
P U B L I C
Appendix

11 Important Disclaimers on Legal Aspects
This document is for informational purposes only. Its content is subject to change without notice, and SAP
does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF
MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
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 specifically disclaims any liability with respect to this document and no contractual
obligations or commitments are formed either directly or indirectly by this document.
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. Regarding link classification, see: http://help.sap.com/disclaimer
Important Disclaimers on Legal Aspects
P U B L I C

www.sap.com/contactsap
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are
set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Sap hana server installation guide

Recommended

More Related Content

What's hot (20)

Viewers also liked (16)

Similar to Sap hana server installation guide (20)

Sap hana server installation guide