Installing SAP HANA 2.0

You can customize platform lifecycle management aspects of your SAP HANA system by accessing the SAP HANA database lifecycle manager from three user interfaces: the graphical user interface, the command-line interface, or the Web user interface in a stand-alone Web browser via the SAP HANA cockpit.

SAP HANA platform lifecycle management encompasses the installation and update of an SAP HANA server, mandatory components, and additional components, as well as the post-installation configuration. The complete concepts and procedures for SAP HANA platform installation and update are described in the SAP HANA Server Installation and Update Guide on the SAP Help Portal.

Several system configuration features are integrated into the SAP HANA database lifecycle manager, such as the following:

• The initial configuration of your SAP HANA platform to integrate it into your landscape. For example, by registering it in a system landscape directory, or configuring the usage of the network interface via the inter-service communication
• Adapting the topology of your SAP HANA platform by adding or removing additional SAP HANA hosts
• Reconfiguring the system

It is important to understand the following terms as they apply to the SAP HANA database system:

Host

A host is the (virtual) hardware and operating environment in which the SAP HANA database system runs. SAP HANA is supported on SUSE Linux Enterprise Server and Red Hat Enterprise Server.

The host provides all the resources and services (CPU, memory, network, and storage) that the SAP HANA database system requires. The storage for an installation does not have to be on the host; it can be shared storage as well. Multi-host SAP HANA database systems require shared storage or storage that is accessible on demand from all hosts.

SAP HANA Database System

An SAP HANA database system consists of one or more SAP HANA instances with the same SAP HANA <SID> and instance number. The term SAP HANA database system is interchangeable with the term system.

An SAP HANA database system can be distributed over several hosts. In such a distributed system, each instance must have the same SAP HANA <SID> and SAP HANA Instance number <##>.

The SAP HANA <SID>

The SAP HANA <SID> is the name of your SAP HANA database. This <SID> is assigned during the installation, and is unique throughout your organization. The <SID> consists of exactly three alphanumeric characters, and it contains only uppercase letters. The first character has to be a letter.

Instance Number <##>

The SAP instance number is a two-digit number between 00–99. In the SAP HANA database system all the instances have the same instance number.

SystemDB database

The system database contains information about the system as a whole, as well as all its tenant databases. It is used for central system administration.

A system has exactly one system database. It contains the data and users for system administration. System administration tools, such as the SAP HANA cockpit, can connect to this database. The system database stores overall system landscape information, including knowledge of the tenant databases that exist in the system. However, it doesn't own database-related topology information, that is, information about the location of tables and table partitions in databases. Database-related topology information is stored in the relevant tenant database catalog.

Administration tasks performed in the system database apply to the system as a whole and all of its databases (for example, system-level configuration settings), or can target specific tenant databases (for example, backup of a tenant database).

Tenant Database

SAP HANA supports multiple isolated databases in a single SAP HANA system. These are referred to as tenant databases.

An SAP HANA system is identified by a single system ID (SID). Databases are identified by a SID and a database name. From the administration perspective, there is a distinction between tasks performed at system level and those performed at database level. Database clients, such as the SAP HANA cockpit, connect to specific databases.

All the tenant databases share the same installation of SAP HANA database system software, the same computing resources, and the same system administration. However, each tenant database is self-contained and fully isolated with its own:

• Set of database users
• Persistence
• Backups
• Traces and logs
• Database catalog
• Repository

SAP HANA application lifecycle management tools can be accessed in different user interfaces: an interface that runs as an SAP HANA XS application in a Web browser, a command-line tool hdbalm, or via the SAP HANA cockpit.

SAP HANA application lifecycle management supports you in all phases of the lifecycle of an SAP HANA application or add-on product, from modeling your product structure, through application development, transport, assembly, to install and update products that you have downloaded from SAP Support Portal or which you have assembled yourself.

All application lifecycle management tasks are documented in the guide SAP HANA Application Lifecycle Management on the SAP Help Portal.

SAP HANA database system administrators use SAP HANA platform lifecycle management mainly to install and update SAP HANA applications or add-on products. During this course, we will only focus on these tasks of the SAP HANA platform lifecycle management. Tasks related to SAP HANA development are documented in the SAP HANA Developer Guide for SAP HANA Web-Based Development Workbench on the SAP Help Portal.

The SAP HANA lifecycle management tools allow you to install single- and multi-SID systems. When installing a multi-SID system, the instance numbers and the SIDs must be different.

SAP supports running multiple SAP HANA systems represented by multiple system IDs (SIDs) on a single production SAP HANA hardware installation (or single virtual machine). See SAP Note 1681092 for the details on supported single host systems.

SAP also supports running multiple SAP HANA systems represented by multiple system IDs (SIDs) on a production scale-out hardware installation. For more information, see SAP Note 2680623 for the details on supported single host systems.

The SAP HANA platform lifecycle management tool can be used to install and update an SAP HANA database system and to add mandatory components and additional components.

The SAP HANA database lifecycle management tool also provides a browser-based user interface, but this can only be used for SAP HANA updates and several other lifecycle management tasks.

The SAP HANA database system can be installed using the command-line user interface or by using a graphical user interface. For advanced tailored data center integration (TDI) installations, the command-line interface with a configuration file is the best option.

The location for the HDBLCM tools depends on the download location and the CPU architecture used. From your <download location> base, the tools are to be found in the following locations:

• HDBLCM (Intel based):

  Code Snippet

  Copy codeSwitch to dark mode

  1
  /<download location>/DATA_UNITS/HDB_LCM_LINUX_X86_64

• HDBLCM (IBM Power):

  Code Snippet

  Copy codeSwitch to dark mode

  1
  /<download location>/DATA_UNITS/HDB_LCM_LINUX_PPC64

The command-line version of the HDBLCM can be used if you don’t have a graphical user interface installed on your Linux server. On an Intel-based system, to start the HDBLCM, connect to the SAP HANA server using ssh, and execute the following commands as root user:

123

cd /<download location>/DATA_UNITS/HDB_LCM_LINUX_X864

and start the application:

1
./hdblcm

If you have a graphical user interface installed on your Linux server, the graphical user interface version of the HDBLCM can be used.

On the graphical desktop as root user, use the file explorer to change to the directory:

1
cd /<download location>/DATA_UNITS/HDB_LCM_LINUX_X86_64

and start the application:

1
./hdblcmgui

There are many options to connect to the X Window System – you can use VNC, tunnel X Window over ssh, or even use Remote Desktop via xrdp.