Professional Documents
Culture Documents
SAP HANA Lation Guide en
SAP HANA Lation Guide en
SAP HANA Lation Guide en
Table of Contents
1
1.1
Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2
Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3
1.4
2.1
2.2
2.3
2.2.1
Single-Host System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.2
3.1
3.2
Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3
3.2.1
Parameter Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.2
Interactive Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.1
3.3.2
3.4
Advanced Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.1
4.2
4.1.1
Automation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.2
4.2.2
Installation Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.1
5.2
5.3
5.4
5.5
5.6
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.1
6.2
6.3
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
This SAP HANA installation guide describes how to install an SAP HANA system with the SAP HANA lifecycle
management tools hdblcm and hdblcmgui.
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 fastpaced 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. With SAP HANA SPS 07, the SAP HANA hdblcm tool has been 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.
Note
The SAP HANA lifecycle management tools hdblcm and hdblcmgui offer the most functionality of any SAP
HANA installer released yet to date. For new installations of an SAP HANA system, it is highly recommend to
use the hdblcm installer. The hdblcm installer can also be used to update previous versions of SAP HANA to
the SPS 07 version. The SAP HANA unified installer is available as part of SAP HANA SPS 07, but is listed as
deprecated, and will not be shipped with future releases.
Before starting the installation of SAP HANA, make sure that you have reviewed the SAP HANA Master Guide.
Related Information
SAP HANA Master Guide
1.1
Software Components
The SAP HANA Platform Edition is the foundation of various other SAP HANA editions, like the SAP HANA
Enterprise Edition. These editions bundle additional components that customers might require, for example, for
data replication.
The SAP HANA Platform Edition is composed of the following components:
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Diagnostics Agent
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 Sybase Replication Server, SAP HANA 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.
Related Information
SAP HANA Information Composer Installation and Configuration Guide
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:
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
A-Z Index
SAP HANA
Installation
A-Z Index
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 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
1.3
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
Title
1514967
1921675
1523337
1681092
1661202
1828400
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Title
1917938
1645183
1823343
1927949
1577128
1514966
1637145
1793345
1824819
Optimal settings for SLES 11 SP2 and SLES 11 for SAP SP2
1597355
Check the current SAP Notes for the various parts of SAP HANA by searching for any of the following application
areas:
SAP HANA Platform
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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 (https://
service.sap.com/~sapidp/011000358700000905192010E.pdf
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
).
When reporting an incident, you can choose from the above list of components for the relevant software part.
1.4
Documentation for the current Support Package Stack of the SAP HANA Platform Edition can be found on the
SAP Help Portal. SAP HANA documentation for previous Support Package Stacks can be found on the SAP HANA
Knowledge Center on SAP Service Marketplace.
For information about SAP HANA landscape, security, installation, and administration, see the resources listed
below:
Topic
Location
Quick Link
http://help.sap.com/hana_platform:
http://help.sap.com/hana_platform:
https://service.sap.com/hana
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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
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 multi-host systems, a shared storage or a storage that is
accessible on-demand from all hosts is required. For more information, refer to the multi-host system concepts.
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 multi-host system must have the
same instance number.
System
10
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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
distributed system.
Related Information
Multi-Host System Concepts [page 63]
It is important to review multi-host system concepts like host grouping and storage options before installing a
multi-host system.
2.2
Multi-host (distributed) system - Multiple SAP HANA instances distributed over multiple hosts, with one
instance per host.
2.2.1
Single-Host System
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
11
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.
Installer 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
Batch Mode
Available for hdblcm. The installation accepts the default values for all unspecified
specifications iteratively until the installation process finishes. For more details, refer to the
Interactive Installation [page 45] information.
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, refer to the
Enabling Batch Mode [page 61] information.
Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui), most
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
parameters are requested interactively. Parameters that are not requested accept the default
value. For more details about which parameters are requested interactively, refer to the
Changeable Default Values [page 41] information.
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, refer to the Installation Parameters [page 21] 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, refer to the Automating with
the Configuration File [page 57] information.
2.2.2
If there are multiple hosts in a system, it is called a multi-host (or distributed) system.
12
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
The following graphic shows the file system for a multi-host system with three hosts:
A multi-host system is a system with multiple hosts, 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 multi-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 details,
refer to the Multi-Host System Installation [page 63] information.
Installer 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
Batch Mode
Available for hdblcm. The installation accepts the default values for all unspecified
specifications iteratively until the installation process finishes. For more details, refer to the
Interactive Installation [page 45] information.
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, refer to the
Enabling Batch Mode [page 61] information.
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 multi-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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
13
For more details about which parameters are requested interactively, refer to the Changeable
Default Values [page 41] 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 multi-host system, the action and addhosts parameters must be specified in
combination with hdblcm.
For more details about the accepted parameter syntax, refer to the Installation Parameters
[page 21] 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, refer to the Automating with
the Configuration File [page 57] information.
2.3
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)
Software Requirements
Note
Only the software installed by certified hardware partners, or any person holding E_HANAINS131 certification,
is recommended for use on the SAP HANA system. Do not install additional software on the SAP HANA system.
Operating System for SAP HANA
SUSE Linux Enterprise Server (SLES) 11 (see Product Availability Matrix (PAM)
installing SLES 11 in an SAP environment, see SAP Note 1310037
SLES 11, see SAP Note 1824819
For the SAP HANA system there are no specific requirements regarding swap space (see SAP Note 1597355
).
The following additional components need to be installed on the SAP HANA system:
14
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
java-1_6_0-ibm (use version as provided with operating system distribution, necessary for the SAP HANA
studio on the SAP HANA system)
ntp
sudo
tcsh
libssh2-1
autoyast2-installation
yast2-ncurses
Turn off the SLES kernel dump function (kdump) if not needed for specific reasons (for example, root cause
analysis).
Adhere to the following shared memory settings (if not already set during installation):
Size
SHMMNI Value
Physical Memory
Small
4096
24 GB RAM < 64 GB
Medium
65536
Large
524288
When using unixODBC for ODBC on Linux, install release 2.3.0 or higher (check with command isql -version).
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
For a new installation, you need to have at least 20 GB RAM in total just for the software - 15 GB for the basic
software plus 5 GB for programs as well as some space for trace files. The additional memory required for data
and log volumes varies according to your requirements.
For an update, you also need to allow the space stated above, since the old software version is not deleted.
Hardware Check
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
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
15
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.
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.
To ensure that both the data device check and log device check pass, make sure that the free disk space of the
data volume is at least four times the size of the physical memory and the free disk space of the log volume is at
least equal to the size of the physical memory otherwise a volume size error appears. You can check the free
memory on your mount points with a df -h command.
Device
Data
4 * RAM
Log
1 * RAM
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.
Note
For more information about validated hardware configurations see the Product Availability Matrix (PAM) on
SAP Service Marketplace at https://service.sap.com/pam
2.3.1
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
16
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
File System
Default Path
Recommendations
Installation path
/hana/shared/
(sapmnt)
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:
System instance
/usr/sap
Data volume
/hana/data/
<SID>
The data path requires disk space equivalent to four times the size of
the system RAM. (GB = 4*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 equivalent to the default system
RAM. (GB = 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:
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
17
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 multi-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, refer to the
Multi-Host System Concepts [page 63] information.
18
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
19
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
Both the hdblcm and hdblcmgui SAP HANA lifecycle management tools can be used to install an SAP HANA in
one of the installer modes, and with a combination of parameter specification methods.
Installer 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 or confirm
Batch Mode
Available for hdblcm. The installation accepts the default values for all unspecified
parameter specifications iteratively until the installation process finishes. For more details,
refer to the Interactive Installation [page 45] information.
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, refer to the
Enabling Batch Mode [page 61] information.
Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui) most
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
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. For more details about which parameters are requested
interactively, refer to the Changeable Default Values [page 41] information.
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, refer to the Installation Parameters [page 21] information, or
refer to the inline help output (--help).
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 during installation with either the hdblcm or
hdblcmgui tool. If any mandatory parameters are not specified, they are requested
interactively (unless batch mode is used). All parameters can be entered in the configuration
20
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
file. For more details about the using the configuration file, refer to the Automating with the
Configuration File [page 57] 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
The SAP HANA lifecycle management tools hdblcm and hdblcmgui must be run as root user from the following
directory on the installation medium: <DVD root directory>/DATA_UNITS/HDB_LCM_LINUX_X86_64
3.2
Installation Parameters
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.
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).
3.2.1
Parameter Reference
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.
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
21
3.2.1.1
action
3.2.1.2
addhosts
Specifies additional hosts for a multi-host system as a comma-separated list. Individual host options are specified
by a colon-separated list. This parameter is only applicable when configuring a multi-host system during
installation and cannot be used in combination with hdblcm to add hosts to existing installations.
Requirements
If the root user has a username other than "root", the root_user parameter must also be
specified in combination with addhosts.
The action parameter must be specified in combination with addhosts.
Syntax
In the command line, the following syntax is used:
--action=[install|update] --addhosts=<host>[,<host2>]
where the <host> syntax is as follows:
<host_name>[:role=worker|standby][:group=<name>]
[:storage_partition=<number>]
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
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 standy 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).
22
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Example
The following example installs a multi-host system of three hosts (two additional hosts) from the command
line. One additional host is configured as worker with a storage partition, and the other is configured as
standby. Both belong to the same host group, HA1:
./hdblcm --action=install -addhosts=hanahost2:group=HA1:storage_partition=3,hanahost3:role=standby:group=HA1
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
Multi-Host System Concepts [page 63]
It is important to review multi-host system concepts like host grouping and storage options before installing a
multi-host system.
Creating a Multi-Host System During Installation [page 66]
The SAP HANA lifecycle management tools hdblcm and hdblcmgui have the ability to build a multi-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 35]
Specifies the root user name.
action [page 22]
Specifies the action of hdblcm to be either installation or update.
3.2.1.3
autostart
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
23
3.2.1.4
batch
Runs the SAP HANA lifecycle management tool hdblcm 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.
Requirements
In order to run a program in batch, at least the following parameters must be specified as
part of the program call, or in the configuration file, if the configuration file is specified as
part of the program call.
Passwords - In batch mode, the user passwords can be specified in two ways: in the
configuration file, or in a password XML file and passed by the parameter
read_password_from_stdin=xml.
Syntax
In the command line, the following syntax is used:
--batch
or
-b
Example
The following example installs the system DB1 with instance number 42, accepting the passwords in the XML
file, and all other parameters are set as default:
cat ~/Passwords.xml | ./hdblcm --batch --sid=DB1 --number=42 -read_password_from_stdin=xml
Related Information
Enabling Batch Mode [page 61]
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.
sid [page 37]
Specifies a system ID. The SAP system ID (SID) is the identifier for the SAP HANA system.
Specifying Passwords [page 43]
Passwords are a mandatory parameter for installing an SAP HANA system. There are three methods for
configuring passwords.
24
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
3.2.1.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
In the command line, the following syntax is used:
--action=install -certificates_hostmap=<hostName>=<certificateHostName>
or
--action=install -H <hostName>=<certificateHostName>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is the current host.
This parameter is available in interactive mode.
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 22]
Specifies the action of hdblcm to be either installation or update.
components [page 27]
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
25
3.2.1.6
checkmnt
Specifies a non-standard shared file system, which can be accessed by all hosts during installation.
Syntax
In the command line, the following syntax is used:
--checkmnt=<path>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
3.2.1.7
client_path
3.2.1.8
component_dirs
3.2.1.9
component_medium
26
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
3.2.1.10
component_root
3.2.1.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
In the command line, the following syntax is used:
--action=[install|update] --components[=all|afl|client|hlm|lcapps|
server|studio]
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
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.
This parameter is available in interactive mode.
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
27
Related Information
action [page 22]
Specifies the action of hdblcm to be either installation or update.
3.2.1.12
configfile
Related Information
Automating with the Configuration File [page 57]
The configuration file is a text document where all available installation parameters can be specified.
3.2.1.13
copy_repository
Specifies the target path to which the SAP HANA studio repository should be copied.
Syntax
In the command line, the following syntax is used:
--copy_repository=<target path>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --copy_repository=/hana/shared/<SID>/
hdbstudio_update
3.2.1.14
datapath
Specifies the path to the data directory of the SAP HANA system.
Requirements
28
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
The data device has specific hardware requirements. For more information, refer to the
hardware requirements for the data device.
Syntax
In the command line, the following syntax is used:
--datapath=<path to data directory>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --datapath=/hana/data/<SID>.
This parameter is available in interactive mode.
Related Information
Hardware and Software Requirements [page 14]
For SAP HANA several hardware and software requirements need to be fulfilled.
3.2.1.15
dump_configfile_template
Specifies a filepath to which a template configuration file is exported. The installation parameters in the template
configuration file are set to their default values, and can be edited.
Requirements
The parameter action must be specified in combination with
dump_configfile_template.
Syntax
In the command line, the following syntax is used:
--action=[install|update] --dump_configfile_template=<filepath>
Remarks
The parameter dump_configfile_template is especially useful in advanced installation
tasks that involve reusing installation configurations. For more information, see the
advanced installation topics.
Example
The following example dumps a template of installation configuration parameters (with defaults) into the file
"configfileDB1":
./hdblcm --action=install --dump_configfile_template=/var/tmp/configfileDB1
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
29
Related Information
Automating with the Configuration File [page 57]
The configuration file is a text document where all available installation parameters can be specified.
action [page 22]
Specifies the action of hdblcm to be either installation or update.
3.2.1.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
In the command line, the following syntax is used:
--groupid=<sapsys group ID>
or
-G <sapsys group ID>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --groupid=79.
This parameter is available in interactive mode.
3.2.1.17
help
30
General help: -h
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Example
The following example displays information about the parameters available for installation.
./hdblcm --action=install -h
3.2.1.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
In the command line, the following syntax is used:
--home=<home directory>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --home=/usr/sap/<SID>/home.
This parameter is available in interactive mode.
3.2.1.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
In the command line, the following syntax is used:
--host_agent_package=<SAP host agent filepath>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
3.2.1.20 hostname
Specifies the host name of the machine.
Syntax
In the command line, the following syntax is used:
--hostname=<name of the host machine>
or
-H <name of the host machine>
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
31
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
Restrictions apply to host names in SAP systems. For more information, see SAP Note
661361
The default for this parameter is the host name of the current machine.
3.2.1.21
install_hostagent
Related Information
action [page 22]
Specifies the action of hdblcm to be either installation or update.
3.2.1.22 internal_network
Specifies the internal subnet address in prefix notation (CIDR).
Syntax
In the command line, the following syntax is used:
--internal_network=<address>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Example
The following example specifies the internal network address in prefix notation.
./hdblcm --internal_network=192.168.1.0/24
32
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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 in the interactive mode of the installation.
3.2.1.23 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
In the command line, the following syntax is used:
--list_systems
or
-L
3.2.1.24 logpath
Specifies the path to the log directory of the SAP HANA system.
Requirements
The log device has specific hardware requirements. For more information, refer to the
hardware requirements for the log device.
Syntax
In the command line, the following syntax is used:
--logpath=<path to log directory>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --logpath=/hana/log/<SID>.
This parameter is available in interactive mode.
Related Information
Hardware and Software Requirements [page 14]
For SAP HANA several hardware and software requirements need to be fulfilled.
3.2.1.25 number
Specifies the instance number of the SAP HANA system.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
33
Requirements
The instance number must be a two-digit number between 00 and 97.
Syntax
In the command line, the following syntax is used:
--number=<instance number>
or
-n <instance number>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default value for this parameter is the next successive un-used instance number.
This parameter is available in interactive mode.
3.2.1.26 print_timezones
Lists all valid timezones, which can be specified by the timezone parameter.
Syntax
In the command line, the following syntax is used:
--print_timezones
Related Information
timezone [page 39]
Specifies the timezone for the system administrator. This parameter is relevant only if the operating system
administrator (<sid>adm) does not exist prior to installation.
3.2.1.27
read_password_from_stdin
Syntax
34
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Example
The first part of the following example shows the file containing the passwords. The second part calls the
password file (stored in the home directory of the root user) as an XML input stream from the command line:
Passwords.xml<?xml version="1.0" encoding="UTF-8"?>
<Passwords>
<password>SysAdm123456</password>
<system_user_password>DBsys12345678</system_user_password>
<root_password>RootSecret007</root_password>
</Passwords>
cat ~/Passwords.xml | ./hdblcm --sid=DB1 --number=42 -read_password_from_stdin=xml -b
Related Information
Specifying Passwords [page 43]
Passwords are a mandatory parameter for installing an SAP HANA system. There are three methods for
configuring passwords.
3.2.1.28 repository
Defines the source path from which the SAP HANA studio repository should be copied.
Syntax
In the command line, the following syntax is used:
--repository=<source path>
or
-r <source path>
Remarks
If you do not specify this option, the repository contained in the installation kit is copied.
3.2.1.29 root_user
Specifies the root user name.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
35
Syntax
In the command line, the following syntax is used:
--root_user=<username>
Remarks
The default for this parameter is --root_user=root. If the root user has a name other
than "root", the root_user parameter must be specified in combination with addhosts.
This parameter is available in interactive mode.
Related Information
addhosts [page 22]
Specifies additional hosts for a multi-host system as a comma-separated list. Individual host options are specified
by a colon-separated list. This parameter is only applicable when configuring a multi-host system during
installation and cannot be used in combination with hdblcm to add hosts to existing installations.
3.2.1.30 sapmnt
Specifies the path to the SAP mount directory, which can be used as a shared directory between multiple hosts.
Requirements
The installation device has specific hardware requirements. For more information, refer to
the hardware requirements for the installation device.
Syntax
In the command line, the following syntax is used:
--sapmnt=<installation path>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --sapmnt=/hana/shared.
This parameter is available in interactive mode.
This parameter can be specified once and automatically subsituted throughout all
parameter defaults, which use sapmnt as part of their default value.
Related Information
Hardware and Software Requirements [page 14]
For SAP HANA several hardware and software requirements need to be fulfilled.
Changeable Default Values [page 41]
The installer uses the following default values unless you change them during installation.
36
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
3.2.1.31
shell
Specifies a system administrator login shell. This parameter is relevant only if the operating system administrator
(<sid>adm) does not exist prior to installation.
Syntax
In the command line, the following syntax is used:
--shell=<admin login shell>
Remarks
The default for this parameter is --shell=/bin/sh.
This parameter is available in interactive mode.
3.2.1.32 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
In the command line, the following syntax is used:
--sid=<system ID>
or
-s <system ID>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
This parameter is a mandatory parameter and has no default value.
This parameter is available in interactive mode.
This parameter can be specified once and automatically subsituted throughout all
parameter defaults, which use sid as part of their default value.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
37
Related Information
Changeable Default Values [page 41]
The installer uses the following default values unless you change them during installation.
3.2.1.33 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
In the command line, the following syntax is used:
--storage_cfg=<directory of the storage configuration>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Related Information
Multi-Host System Concepts [page 63]
It is important to review multi-host system concepts like host grouping and storage options before installing a
multi-host system.
3.2.1.34 studio_path
Specifies the installation path for the SAP HANA studio.
Syntax
In the command line, the following syntax is used:
--studio_path=<installation path>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --studio_path=<sapmnt>/<SID>/hdbstudio.
38
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
3.2.1.35 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
In the command line, the following syntax is used:
--studio_repository[=off]
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --studio_repository (on).
Related Information
copy_repository [page 28]
Specifies the target path to which the SAP HANA studio repository should be copied.
repository [page 35]
Defines the source path from which the SAP HANA studio repository should be copied.
3.2.1.36 timezone
Specifies the timezone for the system administrator. This parameter is relevant only if the operating system
administrator (<sid>adm) does not exist prior to installation.
Syntax
In the command line, the following syntax is used:
--timezone=<timezone>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
Remarks
The default for this parameter is --timezone=UTC.
To display a list of all valid timezones, call the print_timezones parameter.
This parameter is available in interactive mode.
Related Information
print_timezones [page 34]
Lists all valid timezones, which can be specified by the timezone parameter.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
39
3.2.1.37
userid
Specifies the user ID of the system administrator. This parameter is relevant only if the operating system
administrator (<sid>adm) does not exist prior to installation.
Requirements
The user ID must be a value in the range of 1000-32000.
Syntax
In the command line, the following syntax is used:
--userid=<ID number>
or
-U <ID number>
Remarks
The default value for this parameter is the next successive un-used user ID number.
This parameter is available in interactive mode.
3.2.1.38 version
Displays the version of hdblcm.
Syntax
In the command line, the following syntax is used:
--version
or
-v
3.2.1.39 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
In the command line, the following syntax is used:
--vm=<Java path>
In the configuration file, the syntax of the value is identical to the command line syntax.
The key is specified in the configuration file without the leading dashes.
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.
40
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
3.2.2
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 multi-host system, the action and addhosts parameters are mandatory command-line
specifications for the hdblcm installer.
3.2.2.1
The installer uses the following default values unless you change them during installation.
Some default values are based on the predefined values on the current host. In a multi-host system, it is
recommended to manually check the mandatory values on each hosts before installation.
Table 2: Changeable Parameter Defaults
Parameter
action
install
CLI
Interactive
Mode
GUI
0
(off)
${sapmnt}/${SID}/hdbclient
components
client,hlm,server,studio
(dependent on the installer finding installation sources
for the components)
copy_repository
/hana/shared/${SID}/hdbstudio_update
datapath
/hana/data/${SID}
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
41
Parameter
groupid
79
home
/usr/sap/${SID}/home
hostname
<current host>
install_hostagent
CLI
Interactive
Mode
GUI
(on)
logpath
/hana/log/${SID}
number
root_user
root
sapmnt
/hana/shared
shell
/bin/sh
studio_path
${sapmnt}/${SID}/hdbstudio
studio_repository
1
(on)
userid
timezone
UTC
vm
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.
3.2.2.2
The following users are automatically created during the installation: <sid>adm, sapadm, and SYSTEM.
42
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
User
Description
<sid>adm
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 multi-host system.
The password of the <sid>adm user is set during installation with the password
parameter.
sapadm
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 modified
by the installer. The sapadm user and password are also not modified.
The password of the sapadm user is set during installation with the
sapadm_password parameter.
SYSTEM
Initially, the SYSTEM user has all system permissions. Additional permissions can be
granted and revoked again, however the initial permissions can never be revoked.
The password of the SYSTEM user is set during installation with the
system_user_password parameter.
3.2.2.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
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
43
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
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
44
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
3.3
Interactive Installation
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.
An SAP HANA system can be installed interactively:
With the graphical installation tool, hdblcmgui, by selecting installation options from a wizard.
3.3.1
It is now possible to install an SAP HANA system from a graphical interface, by running the SAP HANA lifecycle
management tool hdblcmgui.
Prerequisites
If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
The JRE is up-to-date (version 1.6 or higher). Verify by calling: java -version
Procedure
1.
2.
3.
Software directory
Installation parameters:
The software component directories are detected. Component locations can be added or changed.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
45
Results
The installation progress is displayed.
The SAP HANA system is now up and running.
3.3.2
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.
46
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Prerequisites
If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
The JRE is up-to-date (version 1.6 or higher). Verify by calling: java -version
Procedure
1.
2.
3.
Parameter default values are suggested in brackets, and can be accepted with Enter. Otherwise, enter a nondefault value, then select Enter.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
47
Results
The installation progress is displayed.
The SAP HANA system is now up and running.
3.4
It is also possible to update an SAP HANA system using the hdblcm or hdblcmgui lifecycle management tools.
48
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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)
Most commonly, an SAP HANA system is updated either manually (by downloading individual components to a
specific location), or from a DVD.
For minor software updates, it is likely that some individual SAP HANA system components should be updated. To
update to a new SPS, it is recommended to update all system components from the DVD. From the DVD, update
is carried out identically to installation.
Procedure
1.
2.
1.
2.
Download SAP HANA packages from the SAP Service Marketplace to the local directory.
3.
4.
2.
Locate the SAP_HANA_DATABASE directory in the unpacked archive or on the DVD, and run the hdblcm
update tool.
In interactive mode:
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
49
2.
Edit the configuration file template, save it, and call it during update:
./hdblcm --action=update --configfile=<filepath>
50
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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 multi-host system using hdblcm.
SAP HANA also offers other tools for advanced installation tasks, including registering and renaming hosts, which
are described in detail in the SAP HANA LCM Tools Reference Guide.
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:
Instance number: 01
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:
Configuration file
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
51
Specification
System name
P01
--sid=P01
Instance number 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 shortform syntax. Therefore, the same P01 system installation could be simplified to the following syntax:
./hdblcm s P01 n 01 G 110
System Detail
Specification
System name
P01
-s P01
Instance number 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
52
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
53
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
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 multi-host system concepts information.
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
Installation Parameters [page 21]
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.
Multi-Host System Concepts [page 63]
It is important to review multi-host system concepts like host grouping and storage options before installing a
multi-host system.
SAP HANA LCM Tools Reference Guide
4.1
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.
54
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
55
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 multi-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?
56
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
The root user name must be the same for all hosts in a
multi-host system. Will the root user name for all hosts
be "root"?
4.1.2
The configuration file is a text document where all available installation parameters can be specified.
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 Preparing the Configuration File [page 58].
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. See Using the Configuration File [page 59] for more 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. See Using the Configuration File with Command
Line Options [page 60] for more 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 multi-host system, or combined with a script to
automate installation of several identical systems. See Enabling Batch Mode [page 61] for more information.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
57
For examples of installing with the configuration file, or for an example of the configuration file itself, refer to the
related information.
Related Information
Example Use Cases [page 76]
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 80]
The following is the configuration file template that is generated using the dump_configfile_template
parameter in combination with the hdblcm installer.
4.1.2.1
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.
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
Recommended File System Layout [page 16].
You have considered which installation parameters the new system requires. For more information, see
Installation Parameters [page 21].
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.
58
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Procedure
1.
2.
3.
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
Changeable Default Values [page 41]
The installer uses the following default values unless you change them during installation.
4.1.2.2
By defining a prepared configuration file during installation, specified parameter values are used by the installer to
build a customized SAP HANA system.
Prerequisites
You have prepared the configuration file. For more information, see Preparing the Configuration File [page 58]
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
59
If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
The JRE is up-to-date (version 1.6 or higher). Verify by calling: java -version
Procedure
1.
2.
Results
The installation progress is displayed on the command line.
The SAP HANA system is now up and running.
4.1.2.3
Using the Configuration File with Command Line
Options
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 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 [page 58]
If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
60
The JRE is up-to-date (version 1.6 or higher). Verify by calling: java -version
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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.
Procedure
1.
2.
Results
The installation progress is displayed on the command line.
The SAP HANA system is now up and running.
Example
The following example installs a multi-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=HA1
--configfile=/var/tmp/H01_configfile
4.1.2.4
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
61
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 [page 43].
If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
The JRE is up-to-date (version 1.6 or higher). Verify by calling: java -version
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
1.
2.
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
62
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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
4.2
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 multi-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 detailed information about the parameter options, refer to
addhosts.
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 multi-host system. The host parameters
correspond to those used in the command line. For detailed information about the parameter options, refer to
addhosts.
The SAP HANA lifecycle manager (HLM) - The SAP HANA lifecycle manager is used to add a host to an
existing SAP HANA system. For more information, see the SAP HANA Update and Configuration Guide.
The following information only covers building a multi-host system during installation. Before carrying out the
system installation, review the addhosts parameter options and how they can be set to optimize multi-host
system performance.
4.2.1
It is important to review multi-host system concepts like host grouping and storage options before installing a
multi-host system.
Host Types
When configuring a multi-host system, the additional hosts must be defined as worker machines or standby
machines (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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
63
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.
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 multi-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 multi-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.
64
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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 multi-host system with failover capabilities, the storage must ensure
the following:
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.
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.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
65
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 multi-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.
4.2.2
The SAP HANA lifecycle management tools hdblcm and hdblcmgui have the ability to build a multi-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>
Root user name must be the same for all hosts in a multi-host system.
If the root user name is not root, it must be specified as a parameter during installation using the parameter
root_user.
If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as
follows:
66
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
The JRE is up-to-date (version 1.6 or higher). Verify by calling: java -version
Multi-host system installation using the hdblcm installation tool requires the parameter action=install to
be specified.
Procedure
1.
2.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
67
A multi-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.
It is possible to specify the addhosts parameter, and other required system parameters in the
configuration file, and call the configuration file during multi-host system installation.
Related Information
Installation Parameters [page 21]
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.
Interactive Installation [page 45]
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.
Automating with the Configuration File [page 57]
The configuration file is a text document where all available installation parameters can be specified.
68
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Installation Management
After the installation has finished, it is recommended to perform the following tasks:
The following sections in this chapter are optional tasks that can be performed as part of installation
management.
5.1
Context
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.
However, if required, you can start and stop the SAP HANA system from the command line in one of the following
ways:
Procedure
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
Start the SAP HANA system by entering the following command: /usr/sap/<SAPSID>/
<Instance_Name>/HDB start
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
69
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 Enabling
Automatic Start of the SAP HANA Database [page 71].
5.2
Prerequisites
You are logged on to the SAP HANA host as the root user.
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
70
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
5.3
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.
2.
3.
4.
5.
Results
The SAP HANA database is started automatically when the SAP HANA host is rebooted.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
71
5.4
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 persistence encryption.
Context
Data is stored in persistent disk volumes that are organized in pages. If persistence 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.
Note
You must be logged on to the SAP HANA host as the operating system user, <sid>adm.
Procedure
1.
Caution
Do not generate the root encryption key after you have enabled persistence encryption, since this would
render the SAP HANA database unusable.
The command is as follows:
#hdbnsutil -generateRootKeys --type=ALL
2.
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.
72
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Related Information
SAP HANA Security Guide
SAP HANA Administration Guide
5.5
As the most powerful database user, SYSTEM is not intended for use in production systems. Use it to create
lesser privileged users for particular purposes and then deactivate it.
Prerequisites
You have the system privilege USER ADMIN.
Context
SYSTEM is the database superuser. It has irrevocable system privileges, such as the ability to create other
database users, access system tables, and so on. It is highly recommended that you do not use SYSTEM for dayto-day activities in production systems. Instead, use it to create database users with the minimum privilege set
required for their duties (for example, user administration, system administration). Then deactivate SYSTEM.
Procedure
Execute the following statement, for example, in the SQL console of the SAP HANA studio:
ALTER USER SYSTEM DEACTIVATE USER NOW
Results
The SYSTEM user is deactivated and can no longer connect to the SAP HANA database.
You can verify that this is the case in the USERS system view. For user SYSTEM, check the values in the columns
USER_DEACTIVATED, DEACTIVATION_TIME, and LAST_SUCCESSFUL_CONNECT.
Note
You can still use the SYSTEM user as an emergency user even if it has been deactivated. Any user with the
system privilege USER ADMIN can reactivate SYSTEM with the statement ALTER USER SYSTEM ACTIVATE
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
73
USER NOW. To ensure that an administrator does not do this surreptitiously, it is recommended that you create
an audit policy monitoring ALTER USER statements.
5.6
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
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, do this with
the SAP HANA lifecycle manager, before running uninstallation.
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.
2.
When the wizard appears, select the system components for installation, then select Uninstall. When
the process is complete a log is produced.
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
74
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
2.
Results
The selected components are uninstalled. A log file is available.
Related Information
http://help.sap.com/hana/SAP_HANA_Update_and_Configuration_Guide_en.pdf
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
75
Appendix
6.1
The following is a sampling of general use cases, which illustrate the functionality and versatility of the SAP HANA
hdblcm lifecycle management tool.
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
76
Input
Location Specified
Passwords
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
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Parameter
2.
Input
Location Specified
configfile
--configfile=/home/sysroot/hdblcm_SPS7.cfg
CLI
batch
-b
CLI
userid
userid=55
Configuration file
groupid
groupid=110
Configuration file
storage_cfg
storage_cfg=/home/sysroot/storage
Configuration file
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
# Root User Password
root_password=Root1234
# SAP HANA System ID
sid=ABC
# Instance
number=01
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
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
77
The following are the desired parameters for the SAP HANA server. They are specified in a combination of
command line and configuration file:
Parameter
78
Input
Location Specified
Used for
Installation
Passwords
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,hananode2:
role=standby
CLI
yes
configfile
--configfile=/home/sysroot/
hdblcm_SPS7.cfg
CLI
yes
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Parameter
2.
Input
Location Specified
Used for
Installation
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
storage_cfg
--storage_cfg=/home/sysroot/
storage_new
CLI
yes
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
# Root User Password
root_password=Root1234
# SAP HANA System ID
sid=ABC
# Instance
number=01
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
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
79
The following are the desired parameters for the SAP HANA server. They are specified in a combination of
command line and configuration file.
Parameter
2.
3.
Input
Location Specified
Passwords
--read_password_from_stdin=xml
CLI
sid
--sid=P02
CLI
number
number=01
CLI
root_user
root_user=sysroot
CLI
batch
--batch
CLI
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>
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.
cat ~/hdb_passwords.xml | ./hdblcm --sid=P02 --number 01 --root_user=sysroot -read_password_from_stdin=xml --batch
6.2
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=
80
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
81
6.3
Troubleshooting
Troubleshooting should be referred to if the installation fails for an unknown reason, or for workarounds in special
circumstances.
82
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
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>.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.
Install
Update
--hdbinst_client_ignore=<check1>[]...
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
83
Parameter
Install
Update
84
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
Parameter
Install
Update
check_pending_upgrade, check_plugin_dependencies,
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
sapstartsrv files:
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
85
86
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
www.sap.com/contactsap