hana sps5 inst en

PUBLIC

SAP HANA Appliance Software SPS 05Document Version: 1.0 - 2013-06-20

SAP HANA Installation Guide with SAP HANA Unified Installer

Table of Contents1 Installing SAP HANA Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61.4 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.5 SAP HANA Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.6 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Running SAP HANA Unified Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.1 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1.1 Recommended File System Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2 Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.2.1 Installed SAP HANA Components and Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.2.2 Uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.2.3 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Using SAP HANA On-Site Configuration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1 Global Call Options for the On-Site Configuration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273.2 Add Additional SAP HANA Systems on a Single SAP HANA Appliance. . . . . . . . . . . . . . . . . . . . . . . . . 28

3.2.1 Call Options for Adding SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 Remove Additionally Added SAP HANA Systems From a Single SAP HANA Appliance . . . . . . . . . . . . . .29

3.3.1 Call Options for Removing Additionally Added SAP HANA Systems. . . . . . . . . . . . . . . . . . . . 303.4 Installing and Configuring Solution Manager Diagnostics (SMD) Agent on a SAP HANA System. . . . . . . 31

3.4.1 Installing SMD on a SAP HANA System with the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.2 Installing SMD on a SAP HANA System in Interactive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . 313.4.3 Installing SMD on a SAP HANA System in Batch Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4.4 Call Options for Installing SMD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5 Uninstalling the Solution Manager Diagnostics (SMD) Agent from a SAP HANA System . . . . . . . . . . . . 343.5.1 Uninstalling SMD Agent in GUI mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.2 Uninstalling SMD Agent in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.5.3 Uninstalling SMD Agent in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5.4 Call Options for Uninstalling SMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.6 Renaming a SAP HANA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6.1 Renaming a SAP HANA System with GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373.6.2 Renaming a SAP HANA System in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.6.3 Renaming a SAP HANA System in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.6.4 Call Options for Renaming a SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.7 Configuring a SAP HANA System to Connect to System Landscape Directory (SLD) . . . . . . . . . . . . . . . 413.7.1 Configuring Connection to SLD in GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2P U B L I C© 2013 SAP AG or an SAP affiliate company. All rights reserved.

SAP HANA Installation Guide with SAP HANA Unified InstallerTable of Contents

3.7.2 Configuring Connection to SLD in Interactive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.7.3 Configuring Connection to SLD in Batch Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.7.4 Call Options for Connecting to SLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

3.8 Installing Application Function Libraries (AFLs) on a SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . .433.8.1 Call Options for Installing AFLs on SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

3.9 Installing SAP liveCache Applications (SAP LCA) on a SAP HANA System. . . . . . . . . . . . . . . . . . . . . . 443.9.1 Call Options for Installing SAP liveCache Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.10 Changing SAP HANA System Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453.10.1 Call Options for Changing SAP HANA System Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.11 Perform a Distributed SAP HANA Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.11.1 Call Options for Adding/Removing Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.1 Starting and Stopping the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.2 Performing Initial Backup of SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .504.3 Enabling Persistence Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .504.4 Displaying the Process List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.5 Logging on to the SAP HANA System Using the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.6 Ensuring User Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .524.7 Configuring the Software Update Manager for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.8 Accessing the SAP HANA Studio Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.9 Enabling Automatic Start of the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.10 Applying Updates and Support Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .544.11 Monitoring the SAP HANA System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5 Installing Trigger-Based Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6 Installing the SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7 Installing ETL-Based Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.1 Applying Single Support Package 02 for SAP HANA Unified Installer SPS 05 . . . . . . . . . . . . . . . . . . . . 59

SAP HANA Installation Guide with SAP HANA Unified InstallerTable of Contents

P U B L I C© 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

1 Installing SAP HANA OverviewThis SAP HANA installation guide describes how to install SAP HANA with the SAP HANA unified installer. Before starting the installation of SAP HANA, make sure that you have read the SAP HANA Master Guide.

Related LinksSAP HANA Master Guide

1.1 Software Components

SAP HANA appliance software is available in different editions:

● SAP HANA appliance software platform edition● SAP HANA appliance software enterprise edition

The SAP HANA appliance software platform edition is intended for customers who want to use ETL-based replication and already have a license for SAP Data Services. It is comprised of the following components:

● SAP HANA database● SAP HANA studio● SAP HANA client


SAP HANA Installation Guide with SAP HANA Unified InstallerInstalling SAP HANA Overview

https://service.sap.com/~sapidb/011000358700000604552011

● SAP Host Agent 7.20● SAP HANA information composer● Diagnostics Agent 7.3● SAP HANA client package for Microsoft Excel● SAP HANA UI for Information Access (INA)

As of SAP HANA SPS 05, this component is part of the SAP HANA database.● Software Update Manager for SAP HANA● SAP HANA AFL 1.0

This library has to be installed using the SAP HANA on-site configuration tool which is located on the installation DVD.

The SAP HANA appliance software enterprise edition is intended for customers who want to use either trigger-based replication or ETL-based replication and do not already have all of the necessary licenses for SAP Data Services. It is comprised of the following components:

● SAP HANA database● SAP HANA studio● SAP HANA client● SAP Host Agent 7.20● SAP HANA information composer● Diagnostics Agent 7.3● SAP HANA client package for Microsoft Excel● SAP HANA UI for Information Access (INA)

As of SAP HANA SPS 05, this component is part of the SAP HANA database.● Software Update Manager for SAP HANA● SAP HANA AFL 1.0

This library has to be installed using the SAP HANA on-site configuration tool which is located on the installation DVD.

● SAP LT Replication AddOn● SAP LT Replication Server● SAP HANA Direct Extractor Connection (DXC)

As of SAP HANA SPS 05, this component is part of the SAP HANA database.● SAP Data Services 4.0

The editions of the SAP HANA appliance software are included in the following editions for special purposes:

● SAP HANA Database edition for BW● SAP HANA Limited edition for Apps / Accelerators● SAP HANA EDGE edition

NoteThe Software Update Manager (SUM) for SAP HANA is installed by the SAP HANA unified installer together with other SAP HANA components. For a more complete list of the components actually installed on the SAP HANA appliance, see SAP HANA Installation Guide with SAP HANA Unified Installer, section "Installed SAP HANA Components and Directories".

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. For more information, see the SAP HANA Information Composer – Installation and Configuration Guide.

1.2 Software Download

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 such systems 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 according to agreements with the respective hardware partner.

1.3 Important SAP Notes

You must read the following SAP Notes before you start the installation. These SAP Notes contain the latest information about the installation, as well as corrections to the installation documentation.

Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at https://service.sap.com/notes.

SAP Note Number Title

1514967 SAP HANA: Central Note

1771591 SAP HANA Appliance Software SPS 05 Release Note

1523337 SAP HANA Database: Central Note

1681092 Support for multiple SAP HANA databases on a single SAP HANA appliance

1661202 Support for multiple applications on SAP HANA

1577128 Supported clients for SAP HANA

1514966 SAP HANA: Sizing SAP HANA Database

1637145 SAP BW on HANA: Sizing SAP HANA Database

1597355 Swap space recommendation for Linux

For the SAP HANA system there are no special requirements regarding swap space.

Check the current SAP Notes for the various parts of SAP HANA by searching for any of the following application areas:



https://service.sap.com/~sapidb/011000358700000993102011E


https://service.sap.com/notes

https://service.sap.com/sap/support/notes/1514967









SAP HANA Platform Edition

● BC-DB-HDB SAP HANA Database● BC-DB-HDB-AFL SAP HANA Advanced Function Library● BC-DB-HDB-AFL-PAL SAP HANA Predictive Analysis Library● BC-DB-HDB-AFL-SOP SAP HANA Sales and & Operations Planning● BC-DB-HDB-BAC SAP HANA Backup & Recovery● BC-DB-HDB-CCM CCMS for SAP HANA● BC-DB-HDB-CLI SAP HANA Clients (JDBC, ODBC)● BC-DB-HDB-DBA SAP HANA database administration (DBA cockpit)● BC-DB-HDB-DXC SAP HANA direct extractor connector● BC-DB-HDB-ENG SAP HANA database engine● BC-DB-HDB-MDX MDX Engine / MS Excel client● BC-DB-HDB-PER SAP HANA database persistence● BC-DB-HDB-PLE Planning Engine● BC-DB-HDB-POR DB Porting for SAP HANA● BC-DB-HDB-R SAP HANA Integration with R● BC-DB-HDB-SCR SAP HANA SQL Script● BC-DB-HDB-SEC SAP HANA Security & User Management● BC-DB-HDB-SYS SAP HANA database interface/DBMS● BC-DB-HDB-TXT SAP HANA Text & Search Features● BC-DB-HDB-XS SAP HANA Application Services● BC-HAN-MOD SAP HANA studio / information modeler● BC-HAN-3DM SAP HANA information composer● BC-HAN-SRC SAP HANA UI Toolkit● BC-CCM-HAG SAP Host Agent● SV-SMG-DIA SAP Solution Manager Diagnostics Agent

SAP HANA Lifecycle Management

● BC-HAN-SL-STP SAP HANA unified installer● BC-DB-HDB-INS SAP HANA database installation (hdbinst)● BC-HAN-UPD Software Update Manager for SAP HANA● BC-DB-HDB-UPG SAP HANA database upgrade (hdbupd)

SAP HANA Enterprise Edition

● BC-HAN-LOA SAP HANA load controller (log-based replication)● BC-HAN-REP Sybase rep. server (log-based replication)● BC-HAN-LTR SAP Landscape Transformation (trigger-based replication)● BC-HAN-DXC SAP HANA Direct Extractor Connection● EIM-DS Data Services (ETL-based replication)

End User Clients

● BI-BIP, BI-BIP-CMC Business intelligence platform (formerly known as BOE)● BI-RA-EXP SAP BusinessObjects Explorer● BI-RA-CR, BI-BIP-CRS SAP Crystal Reports● BI-RA-XL Dashboard Designer● BI-BIP-IDT Information design tool



● BI-RA-WBI Web Intelligence● BI-RA-AO-XLA MS Excel Add-In

The search also supports using the wildcard asterisk (*) in searches, so you can, for example, also search for BC-DB-HDB* or similar and you will get results for all sub-components.

Customer Messages

If you encounter any problems with the software, create a customer message on the SAP Service Marketplace athttp://service.sap.com/message.

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. Follow the steps in this guide to create an S-user ID (https://service.sap.com/~sapidp/011000358700000905192010E.pdf).

While creating a customer message, you can chose from the above list of components for the relevant software part.

1.4 Hardware and Software Requirements

NoteYou can find a complete list of all SAP HANA components and the respective SAP HANA hardware and software requirements in the Product Availability Matrix (PAM) on the SAP Service Marketplace.

Software Requirements

NoteOnly the software installed by your hardware partners is recommended for use on the SAP HANA box. Do not install additional software on the SAP HANA box.

Operating System for SAP HANA

SUSE Linux Enterprise Server (SLES) 11 (see Product Availability Matrix (PAM)) – for information about installing SLES 11 in an SAP environment see SAP Note 1310037. 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 box:

● saphostagentThe package saphostagent.rpm is contained on the SAP HANA DVD. You need to install it manually on each additional host that is not a primary host, and on which you have not installed the software with the unified installer.

● gtk2 (use version as provided with operating system distribution (SLES11 SPS1))



http://service.sap.com/message

http://service.sap.com/message

https://service.sap.com/supportcenters

https://service.sap.com/~sapidp/011000358700000905192010E.pdf

https://service.sap.com/~sapidp/011000358700000905192010E.pdf

https://service.sap.com/pam




● java-1_6_0-ibm (use version as provided with operating system distribution (SLES11 SPS1), necessary for the SAP HANA studio on the SAP HANA system)

● libicu (use version as provided with operating system distribution (SLES11 SPS1))● mozilla-xulrunner192-1.9.2.xx-x.x.x (use version as provided with operating system, but at given

minimum version)● ntp● sudo● syslog-ng (use version as provided with operating system distribution (SLES11 SPS1))● tcsh● libssh2-1● expect● autoyast2-installation● yast2-ncurses

Observe the following requirements:

● Turn off the SLES kernel dump function (kdump) if not needed for specific reasons (for example, root cause analysis).

● Configure the following SLES kernel parameter as follows:net.ipv4.tcp_slow_start_after_idle=0

● Adhere to the following shared memory settings (if not already set during installation):

Size shmmni value Physical Memory

S(mall) 4096 >= 24 GB & < 64 GB

M(edium) 65536 > 64 GB & < 256 GB

L(arge) 524288 > 256 GB

Network Time Protocol (NTP)

We strongly recommend that you set up an NTP server for the SAP HANA system landscape.

NoteIf an NTP sever is not available, for example, trace files from distributed nodes cannot be displayed in the correct chronological order.

Hardware Requirements

Hardware Check

During the update and the installation of the SAP HANA database (part of installation by the unified installer), a hardware check is performed. For more information, see SAP Note 1652078.

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.

1.5 SAP HANA Guides

For more information about SAP HANA landscape, security, installation, and administration, see the resources listed below:

Topic Location Quick Link

SAP HANA landscape, deployment, and installation

SAP HANA Knowledge Center on SAP Service Marketplace

https://service.sap.com/hana:

● SAP HANA Master Guide● SAP HANA Installation Guide with SAP HANA Unified

Installer● SAP HANA Master Update Guide● SAP HANA Automated Update Guide

SAP HANA administration and security

SAP HANA Knowledge Center on the SAP Help Portal

http://help.sap.com/hana_appliance:

● SAP HANA Technical Operations Manual● SAP HANA Security Guide

1.6 Technical System Landscape

The figure below shows an overview of the technical system landscape for the SAP HANA appliance software and its related components, such as the SAP HANA studio and other applications, one of which is the SAP HANA information composer. Note that the figure below shows a sample configuration with three SAP HANA database servers. The figure also shows some optional components that may be purchased separately.




https://service.sap.com/hana






http://help.sap.com/hana_appliance

http://help.sap.com/hana/hana_tom_en.pdf

http://help.sap.com/hana/hana_sec_en.pdf

2 Running SAP HANA Unified InstallerThe SAP HANA unified installer is a tool to install the SAP HANA appliance software in a single, unified and predefined way. It is targeted to be used by the SAP HANA hardware partners within their factory process.

Related LinksPerforming a Distributed System Installation (Optional) [page 18]Preparation [page 12]Running the Installer [page 22]Post-Installation [page 49]

2.1 Preparation

You have to perform the preparation steps described in the following sections to be able to run SAP HANA unified installer.

NoteWhen you plan your initial SAP HANA implementation make sure that you discuss possible future changes to your initial setup with your hardware partner. Each hardware partner provides specific technologies and best practices to ensure the feasibility of the changes and to ensure sufficient system performance.

Possible changes could be:

● Change from a single-host implementation with one SAP HANA system (single-sid) to a single-host system with multiple SAP HANA systems. For more information, see Add Additional SAP HANA Systems on a Single SAP HANA Appliance [page 28]

● Change from a single-host SAP HANA system to a distributed SAP HANA system (multi-host) for scale out or high availability reasons. For more information, see Perform a Distributed SAP HANA Setup [page 46].

Related LinksRecommended File System Layout [page 12]Installation Parameters [page 16]Users Created During the Installation [page 21]Preparing the Installer Configuration File [page 14]

2.1.1 Recommended File System Layout

The installer requires a running operating system (OS) with file system partitions created as listed in the table below.

The directories for data- and log-volumes are not created automatically by the installer. You must create them manually before you start the installation.


SAP HANA Installation Guide with SAP HANA Unified InstallerRunning SAP HANA Unified Installer

Table 1: Required File SystemsFile System Description Recommended Disk

Space

/ The root partition 10 GB

/hana/shared/ The file system for the SAP mount directory for global files and profiles.

The default name for the SAP mount directory is /hana/shared/, however you can also specify another name. This directory needs to be accessible by each of the servers in the HANA cluster.

The /hana/shared/ volume needs not to exceed 5GB, but the /hana/shared/<SID> folder requires RAM equal to the default system RAM (1*RAM).

The directory /hana/shared/ must be physically shared. The path to the SAP mount directory is a mandatory parameter to be filled in the installer configuration file. For more information, see Installation Parameters [page 16] and Preparing the Installer Configuration File [page 14].

5 GB

/usr/sap The file system for local SAP system instance directories 50 GB

/hana/data/<SID> Data partition must be able to write at least 800 MB/s.

The directory for data-volumes of the SAP HANA database.

The path to the data directory depends on the configuration of the SAP HANA host.

NoteThis directory must exist before you start the installation.

The data path needs to have three times size of system RAM.

/hana/log/<SID> Data partition must have a bandwidth of at least 100,000 I/O ops.

The directory for log-volumes of the SAP HANA database.

The path to the log directory depends on the configuration of the SAP HANA host.

NoteThis directory must exist before you start the installation.

The log path needs to have RAM equal to the default system RAM.

We strongly recommend the following SAP HANA file system layout, which is illustrated in the picture below:



This is the most general case of a distributed multi SID landscape. All other types of installations can be derived from this general case.

However keep in mind that the production systems, which are always single SID installations, and single or multi SID installations used for other purposes (such as development, quality or testing), must not share any infrastructure. Multi SID installations have to be configured to use the amount of RAM and disk space together, and not only one of them. Additional customer requests may change the disk space requirements.

The file system /hana/shared will be visible on all hosts. 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-distributed file systems.

Backup directories have to be configured properly. By default, backup will go into the /hana/shared file system. This has to be a shared file system in a distributed landscape.

NoteThe configuration path for data and log backup must be defined system-wide and not host specific.

It is strongly recommended to execute initial system back up for later recovery of the initial system state. You can do this by mounting an external backup device/share into the file system of the SAP HANA server.

Related LinksInstallation Parameters [page 16]Preparing the Installer Configuration File [page 14]

2.1.1.1 Preparing the Installer Configuration File

Prerequisites

Make sure you have done the following before you start preparing the installer configuration file:



● You have set up the required file systems and directories. For more information, see Recommended File System Layout [page 12]

● You have specified installation parameters. For more information, see Installation Parameters [page 16].

1. Copy the file setuphana.slmodel.template, which is available in the HANA_IM_LINUX__X86_64 folder on the installation medium, to a local directory:

Example:

cp /HANA_DVD/DATA_UNITS/HANA_IM_LINUX__X86_64/setuphana.slmodel.template /tmp/setuphana.slmodel

The optional parameters are in comments by default. For example,. In order to use them you have to remove the comments.Regarding the values, the haGroup value can be any string that will be the name of a group of primary and secondary hosts, covering the high availability scenario. The storagePartition parameter can take any positive integer values, depending on the number of partitions you would like to have.There is also a second file with even simplified format that you can use. The name of the files is setuphana.slmodel.template.v2.In case you want to add additional host you can use the example below:

<?xml version="1.0" encoding="ISO-8859-1"?><systemParameters> <dataPath>/hana/shared/data</dataPath> <logPath>/hana/shared/log</logPath> <sapmntPath>/hana/shared</sapmntPath><instanceNumber>69</instanceNumber><sid>HAN</sid><hdbHost>hostname1</hdbHost> <timezone>UTC</timezone>

<distributedSystem> <additionalHostsRootUser>lroot</additionalHostsRootUser> <hosts> <host hostname="hostname2" hostType="worker" haGroup="11" storagePartition="3"/> </hosts> </distributedSystem>

</systemParameters>

2. Edit the setuphana.slmodel file and insert the required mandatory installation parameters. You can also use the optional parameters by removing the comment tags before and after the parameter in the file. For example, 

○ You can find the list of the mandatory parameters below. You can also also refer to Recommended File System Layout [page 12].

○ dataPath

○ logPath

○ sapmntPath

○ instanceNumber

○ sid

○ hdbHost

○ timezone○ The optional parameters are:

○ externalHost○ distributedSystem

You have prepared the setuphana.slmodel.v2 file. You can also see the descriptions in the file , marked by comment tags, to get more details.

Related LinksPerforming a Distributed System Installation (Optional) [page 18]Recommended File System Layout [page 12]Installation Parameters [page 16]

2.1.1.2 Installation Parameters

The installer requires the following parameters:

● Parameters to be inserted in the configuration file● Parameters to be entered on the command line

Table 2: Parameters to be inserted in the configuration fileParameter ID Description

sid The SAP system ID (SAPSID) is the identifier for the SAP HANA system.

● 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 SAPSID 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.

instanceNumber The instance number of the SAP HANA system

An instance is an administrative unit that comprises the server software components. It is started and stopped as a unit.

The instance number is a technical identifier for internal processes, and consists of a two-digit number between 00 and 97.

sapmntPath The path to the SAP mount directory



Parameter ID Description

The SAP mount directory can be used as a shared directory between multiple hosts.

The installer sets sapmntPath to /hana/shared by default. Ensure that the required file system is available on the installation host. For more information, see Recommended File System Layout [page 12].

If you want to install your SAP HANA system as a system distributed over several hosts, you have to set the sapmntPath to the path of the mount points on all hosts on which you want to install SAP HANA instances. For more information, see Performing a Distributed System Installation (Optional) [page 18].

The installer will automatically create corresponding symbols from local /hana/shared/ folder. The folder is also created during installation.

dataPath The path to the data directory of the SAP HANA system

We recommend that you name this directory /hana/shared/data/<SID>.

The path to the data directory depends on the configuration of the SAP HANA host. It is a mandatory parameter to be filled in the installer configuration file. For more information, see Installation Parameters [page 16] and Preparing the Installer Configuration File [page 14].

NoteThis directory must exist before you start the installation (see also Recommended File System Layout [page 12]).

logPath The path to the log directory of the SAP HANA system

We recommend that you name this directory /hana/shared/log/<SID>.

The path to the log directory depends on the configuration of the SAP HANA host. It is a mandatory parameter to be filled in the installer configuration file. For more information, see Installation Parameters [page 16] and Preparing the Installer Configuration File [page 14].

NoteThis directory must exist before you start the installation (see also Recommended File System Layout [page 12]).

hdbHost The fully qualified host name of the SAP HANA system

Make sure that a fully qualified host name is assigned to the local machine, that is, the SAP HANA host.

For more information about the restrictions that apply for host names in SAP systems, see SAP Note 611361 - Hostnames of SAP servers.



http://service.sap.com/sap/support/notes/611361

Parameter ID Description

externalHost Inserts the fully qualified host name that will be used for external access to the SAP HANA system. The fully qualified host name must be assigned to the local machine. For more information about the restrictions that apply for host names in SAP systems, see again SAP Note 611361 above.

timezone Inserts a valid time zone for the <sid>adm user. The default zone is set to UTC. For a list of valid time zones execute hanaconfig.sh -- print_timezones

storageConfigPath With this optional parameter the typical behavior of SAP HANA regarding shared resources can be changed (such as hana/shared/log, hana/shared/data). The parameter specifies a location where a global.ini is defined. In this configuration file it is possible to setup a Storage Connector allowing SAP HANA to use hardware vendor specific scripts for automated resource allocation and input/output fencing during failovers. The scripts strongly depend on the used hardware parameters, and therefore only the hardware partners can provide correct scripts.

Table 3: Parameters to be entered on the command lineParameter Description

master password Common password for all users that are created during the installation (see also Users Created During the Installation [page 21])

The master password must meet the following requirements:

● It must consist of at least eight characters● It must contain at least one lowercase character, one uppercase character, and

one number.

The master password is verified by the installer. It is prompted on the command line while you are running the installer.

Related LinksPerforming a Distributed System Installation (Optional) [page 18]Recommended File System Layout [page 12]Users Created During the Installation [page 21]

2.1.1.3 Performing a Distributed System Installation (Optional)

You want to install your SAP HANA system as a distributed installation, that is, a system distributed over several hosts. Make sure you read the following information for reference, before you proceed.

System is the name for one or more nodes of a SAP HANA database on one or more hosts that use the same server software installation:

● If there is only one node, it is called a single-host system.



● If there are multiple connected nodes, it is called a distributed system.

Every system has a unique SAP system ID, <SID>.

CautionChoose your SAP system ID carefully because changing it later as described in Renaming a SAP HANA Database System requires extra effort.

Make sure that your SAP system ID:

● Is unique throughout your organization. Do not use an existing <SID> when installing a new SAP system.● Consists of exactly three alphanumeric characters● Contains only uppercase letters● Has a letter for the first character● Does not include any of the following, which are reserved IDs:

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

The server software is based on a flexible architecture that enables a distributed installation. This means that load can be balanced between different hosts. If you want to create a distributed system, make sure that you set it up in a safe environment.

The server software has to be installed in a file system where all hosts that are part of the system can be mounted.

The following table shows a typical configuration for a distributed system:

Host Name Server

Configured Role

Name Server

Actual Role

Index Server

Configured Role

Index Server

Actual Role

Initial host Master 1 Master Worker Master

1st host added Master 2 Slave Worker Slave

2nd host added Master 3 Slave Worker Slave

3rd host added Slave Slave Worker Slave

4th host added Slave Slave Worker Slave



7th host added Slave Slave Standby Standby

When setting up a distributed system, you need to make sure that the servers are synchronized to the same time. To achieve this, you can set up a Network Time Protocol (NTP) service.

The following figure shows the architecture of a distributed system:



Instance - an instance is an administrative unit that comprises the server software components. It is started and stopped as a unit.

Instance number - an instance is defined by an instance number. This is a two-digit identifier that is unique on a host. Therefore, an instance number can only be assigned once on a host.

Since all instances of a system have the same instance number, only instances of different systems can be configured on the same host.

Host - host is the server or blade on which you create an individual node of a system.

For more information about the restrictions that apply to host names in SAP systems, see SAP Note 611361 Hostnames of SAP servers.

System Administrator -the system administrator, <sid>adm, is the operating system user that is needed for administrative tasks such as starting and stopping the system.

The user ID and password of the <sid>adm user are defined when installing the software and creating the system. The user ID and group ID of this operating system user must be unique and identical on each host of a distributed system.

System User - the SYSTEM user is the overall system administrator for the SAP HANA database. You specify the initial password during installation. The SYSTEM user is the initial bootstrap user for the SAP HANA database that is created during the installation of the SAP HANA database.

Do not use the SYSTEM user for day-to-day activities. Use this user to create dedicated administrator users and to assign privileges to the administrator users.

The SYSTEM user is also described in the SAP HANA Security Guide.

SAP officially supports multiple databases ("multi-SID") on one SAP HANA appliance in non-production environments for both single-host and distributed systems.

CautionSAP does not support running multiple SAP HANA databases on a production SAP HANA system.

For more information, see SAP Note 1681092 "Multiple SAP HANA databases on one appliance".






Procedure

1. Ensure that sapsys user group exists on all hosts and has one and the same ID.

2. On the secondary (additional) hosts, install the SAP Host Agent via the rpm package on the DVD. On the primary host it will be installed by SAP HANA unified installer.

3. Prepare the installer configuration file, complied with your landscape requirements. For more information, see Preparing the Installer Configuration File [page 14] .

NoteYou (as administrator) need to configure the file systems /hana/shared/, /hana/shared/data and /hana/shared/log, so that they are present and mounted on all hosts, including the primary host. This is a prerequisite to run SAP HANA unified installer. If they are not, you will not be able to continue with the installation.

NoteAlso keep in mind that the secure connection confirmation (done via RSA key fingerprint) is automatically accepted for all hosts in the distributed landscape.

4. On the primary host, run the SAP HANA unified installer as described in Running the Installer [page 22].5. Finalize installation by running the SAP HANA On-Site Configuration tool for adapting the existing

configuration, if necessary. For more information, see Using SAP HANA On-Site Configuration Tool [page 27].

6. Execute initial system backup for later recovery of the initial system state. For more information, see Performing Initial Backup of SAP HANA System [page 50].

Related LinksInstallation Parameters [page 16]Preparing the Installer Configuration File [page 14]Running the Installer [page 22]

2.1.1.4 Users Created During the Installation

The following users are automatically created during the installation. All these users are assigned the master password:

User Description

<sid>adm The system administrator, <sid>adm is the operating system user required for administrative tasks such as starting and stopping the system.

The user ID and password of the <sid>adm user are 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 distributed system.

sapadm The SAP Host Agent administrator



User Description

If there is no SAP Host Agent available on the installation host, it is created during the installation along with user sapadm.

If the host agent is already available on the installation host, the installer neither modifies the host agent, nor its sapadm user, nor the password of the sapadm user.

User Description

SYSTEM The database superuser

Initially, the SYSTEM user has all system permissions. Additional permissions can be granted to this user or revoked. However, only those permissions can be revoked that were granted in addition to to the initial permissions.

2.2 Running the Installer

Prerequisites:

● Make sure you have installed the following rpm packages:

○ SAP Host Agent○ GTK2○ Java-1_6_0-ibm (java_home path variable must be set)○ Libicu○ Mozilla-xulrunner1.9.2○ Network Time Protocol (NTP time server must be configured)○ Sudo○ Syslog-ng○ Tcsh○ Libssh2

● You have specified the required installation parameters. For more information, see Installation Parameters [page 16].

● You have prepared the installer configuration file. For more information, see Preparing the Installer Configuration File [page 14].

● You have specified a <WORKING_DIRECTORY> for the installer. For more information, see Recommended File System Layout [page 12]Example:

/tmp/hanainst

Make sure that the <WORKING_DIRECTORY> meets the following requirements:

○ It has at least 200 MB of free disk space.○ It is empty before you start or restart the installer.

1. Log on to the installation host as a user with root authorization.



2. Start the installer from the installation medium. To do this, proceed as follows:

1. Change to the directory HANA_IM_LINUX__X86_64 on the installation medium where the setup.sh script is located.

2. Start the installer from the command line by entering the following command:./setup.sh <WORKING_DIRECTORY> <MODEL_FILE> where <WORKING_DIRECTORY> is the path to the directory where the installer is to be unpacked and <MODEL_FILE> is the path to the installer configuration file.Example:

./setup.sh /tmp/hanainst /tmp/setuphana.slmodel

3. During the installation process, you are prompted to enter and repeat the master password on the command line.

Result:

The installation progress is displayed on the command line.

If the installation is successful, you see this message at the end of the command line output:Finished successfullyThe SAP HANA system is now up and running.

Related LinksRecommended File System Layout [page 12]Installation Parameters [page 16]Preparing the Installer Configuration File [page 14]Installed SAP HANA Components and Directories [page 23]Troubleshooting [page 25]

2.2.1 Installed SAP HANA Components and Directories

Component Directory Description

SAP Host Agent /usr/sap/hostctrl For more information about the host agent and its elements, see SAP Note 1031096 - Installing Package SAPHOSTAGENT

SAP HANA database /hana/shared/<SID> Contains the following sub-directories:

● exeContains executable kernel programs

● globalContains globally shared data

● profileContains the profiles of all instances

● HDB <instancenr>Contains HDB executables

● lm_structureContains the landscapeDescription.xml file





Component Directory Description

SAP HANA database /usr/sap/<SID> Contains the following sub-directories:

● homeThe home directory of the <sid>adm user

● SYSContains system executables

SAP HANA client /hana/shared/<SID>/hbdclient

Only the client for the SAP HANA system, not clients on related SAP ERP systems

SAP HANA studio repository

/hana/shared/<SID>/hdbstudio_update

Only the SAP HANA studio repository is installed (not the complete SAP HANA studio). You can use this repository to update your local SAP HANA studio installation.

SUM for SAP HANA /hana/shared/<SID>/SUM The Software Update Manager (SUM) for SAP HANA downloads new Support Package Stacks (SPS) for SAP HANA from the SAP Service Marketplace (SMP) and updates the components on your SAP HANA system.

The automated update is performed with the Software Update Manager (SUM) for SAP HANA , which is installed and configured with a default security configuration with the SAP HANA unified installer.

SAP HANA studio /hana/shared/<SID>/hdbstudio

SAP HANA studio installation configured to work with Software Update Manager for SAP HANA.

Related LinksConfiguring the Software Update Manager for SAP HANA [page 52]

2.2.2 Uninstall

If required, you can also uninstall the SAP HANA components that have been set up by the installer. You can do this using the uninstall.sh script.

NoteThe uninstall.sh script does not remove the SAP Host Agent and the SMD agent. In case you need to uninstall the SMD agent, do this with the SAP HANA On-Site Configuration tool, before running the uninstall.sh.

Prerequisites

Make sure you have done the following before you start the installer:

● You have specified the required installation parameters. For more information, see Installation Parameters [page 16].



● You have specified a <WORKING_DIRECTORY> for the uninstall. For more information, see Recommended File System Layout [page 12]Example:

/tmp/hanainst

Make sure that the <WORKING_DIRECTORY> meets the following requirements:

○ It has at least 200 MB of free disk space.○ It is empty before you start or restart the uninstall.

1. Log on to the host where you want to perform the uninstall as a user with root authorization.

2. Start the uninstall.sh script from the installation medium. To do this, proceed as follows:

1. Change to the directory HANA_IM_LINUX__X86_64 on the installation medium where the uninstall.sh script is located.

2. Start the uninstaller from the command line by entering the following command:./uninstall.sh <WORKING_DIRECTORY> <SID> <HANA_ROOT_USER>where <WORKING_DIRECTORY> is the path to the directory to which the installer is to be unpacked, <SID> is the system ID of the installed SAP HANA system, and <HANA_ROOT_USER> is an optional parameter that provides the HANA root user for the additional hosts when uninstalling distributed system.Example:

./uninstall.sh /tmp/hanainst <SID>

Result:

The uninstall progress is displayed on the command line.

If the uninstall is successful, you see this message at the end of the command line output:Finished successfully

Related LinksInstallation Parameters [page 16]Preparing the Installer Configuration File [page 14]Troubleshooting [page 25]

2.2.3 Troubleshooting

Prerequisites: The installation or uninstall did not finish with the messageFinished successfully

Check the installation log file as follows:

1. Change to the <WORKING_DIRECTORY>/log directory, where <WORKING_DIRECTORY> is the path to the directory where the installer has been unpacked.Example:

/tmp/hanainst/log/setup.glf

2. Open the installation log file setup.glf.

3. Try to analyze the error.



CautionIf you need to restart the installation from scratch, make sure that the working directory is empty before your restart the installer.



3 Using SAP HANA On-Site Configuration Tool

You can use the SAP HANA On-Site Configuration tool to perform additional (post-installation) steps. Such post-installation steps are done after you have finished the initial installation with the SAP HANA unified installer.

The On-Site Configuration tool is started via the hanaconfig.sh program. Before you run the tool, you need to meet these prerequisites:

● You identify an existing SAP HANA system, created by an installation or a file system copy, that is to be configured.

● You are logged in as the root user.

There are three levels of command hierarchy in the hanaconfig.sh program:

● Level 1 - global call options. For more information, see Global Call Options for the On-Site Configuration Tool [page 27].

● Level 2 - these are all tasks listed within the On-Site configuration structure. For example, Adding Additional SAP HANA Systems on a single SAP HANA appliance and Renaming a SAP HANA System.

● Level 3 - specific call options for each task. You can find them in the task description.

3.1 Global Call Options for the On-Site Configuration Tool

Global Option Name Value Mandatory Description

--gui - no Launches the configuration tool in GUI mode

--batch - no Runs the configuration tool in batch mode

--interactive - no Runs the configuration tool in interactive mode mode

--version - no Displays configuration tool version

--help - no Displays configuration tool help

--temp_dir path to a temp directory no Temporary work folder for the configuration tool

--print_timezones - no Displays the available time zones

SAP HANA Installation Guide with SAP HANA Unified InstallerUsing SAP HANA On-Site Configuration Tool


3.2 Add Additional SAP HANA Systems on a Single SAP HANA Appliance

For installing multiple SAP HANA systems in GUI mode, you are prompted to enter the required parameters.

NoteContact your hardware partner if you plan to add an additional SAP HANA system to an existing single-host SAP HANA system. The individual hardware partners provide hardware partner specific technologies and best practices to ensure the feasibility of the enhancement and provide sufficient system performance.

If you specify the host name, make sure that it is fully qualified, such as myhost.sap.com (not just myhost).

1. Connect to the system with an X server client to enable GUI system access.2. Open a root shell and go to the directory where you mounted the SAP HANA DVD, by entering a command like

the following:

cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_643. Call the script in GUI mode to perform the rename:

./hanaconfig.sh --gui 4. Choose Additional HANA Systems , and then Next to continue.

5. Choose Add HANA System,and then Next to continue.

6. Specify the required entries by following the instructions of the wizard.

NoteYou have the option to specify a dedicated time zone. By default, the time zone is set to UTC (Coordinated Universal Time).

For installing multiple SAP HANA systems in interactive mode, use the command ./hanaconfig.sh addhanasystem. You can use as a general guidance the procedure Configuring Connection to SLD in Interactive Mode [page 42].

For installing multiple SAP HANA systems in batch mode, use the command ./hanaconfig.sh --batch addhanasystem. You can use as a general guidance the procedure Configuring Connection to SLD in Batch Mode [page 42].

Related LinksCall Options for Adding SAP HANA Systems [page 28]

3.2.1 Call Options for Adding SAP HANA Systems

Syntax



Option Name Value Mandatory Default Value

Description

add_system_sapmntpath directory yes - This is the installation path to the hana/shared volume

add_system_sid SID yes - System ID

add_system_number instance number yes - Instance number

add_system_hostname hostname yes - Fully qualified host name

add_system_datapath directory yes - Path to the data directory

add_system_logpath directory yes - Path to the log directory

add_system_master_password password yes - Master password

add_system_memory <<SID1>=<memory in MB>,<SID2>=<memory in MB>,...>

yes - Specifies how to distribute the available memory between the installed HANA instances.

add_system_timezone timezone (see --print_timezones)

no UTC New system administrator time zone

add_system_contentpath directory no - Custom content directory

add_system_external_hostname external hostname no - Fully qualified host name for external usage

3.3 Remove Additionally Added SAP HANA Systems From a Single SAP HANA Appliance

To remove additionally added SAP HANA systems in GUI mode, you are prompted to enter the required parameters.

NoteKeep in mind that the originally installed SAP HANA system cannot be uninstalled from the SAP HANA On-Site Configuration tool. This can be performed only to the additionally installed systems (instances) with the SAP HANA On-Site Configuration tool.




the following:


./hanaconfig.sh --gui 4. Choose Additional HANA Systems, and then Next to continue.

5. Choose Remove HANA System , then select a system from the displayed list, and then Next to continue.


For uninstalling multiple SAP HANA systems in interactive mode, use the command ./hanaconfig.sh removehanasystem.

For uninstalling multiple SAP HANA systems in batch mode, use the command ./hanaconfig.sh --batch removehanasystem.

Related LinksCall Options for Removing Additionally Added SAP HANA Systems [page 30]

3.3.1 Call Options for Removing Additionally Added SAP HANA Systems

Syntax

Option Name Value Mandatory Default Value Description

remove_sid SID yes - System ID

remove_system_memory <<SID1>=<memory in MB>,<SID2>=<memory in MB>,...>

no The memory on the uninstalled system remains unallocated.

Specifies how to distribute the available memory between the installed HANA systems (instances).

Example:

The following example will uninstall additional SAP HANA system with SID "FC1" and its memory will be added to the already installed SAP HANA system:

./hanaconfig.sh --batch removehanasystem --uninst_sid FC1 --uninst_memory HAN=25000



3.4 Installing and Configuring Solution Manager Diagnostics (SMD) Agent on a SAP HANA System

Make sure you meet these prerequisites:

● You identify the existing system, created by an installation or a file system copy, that is to be installed with SMD.

● You mount the DVD with the HANA configuration tool, which you can find at the following location on the SAP HANA DVD:<HANA_DVD>\DATA_UNITS\HANA_IM_LINUX__X86_64

● You are logged in as the root user● SMD <sid>adm user password must contain only ASCII symbols and must be at least 8 characters long.

1.

3.4.1 Installing SMD on a SAP HANA System with the GUI

Make sure that you meet the prerequisites in Installing and Configuring Solution Manager Diagnostics (SMD) Agent on a SAP HANA System [page 31].

In GUI mode, you are prompted to enter the required parameters.



the following:

cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_643. Call the script in GUI mode to perform the installation:

./hanaconfig.sh --guiThe wizard starts.

4. Choose Setup Diagnostics Agent and then follow the instructions of the wizard.

5. Leave the root shell after the reconfiguration has finished.

The installation of SMD diagnostics agent is now finished.

Related LinksCall Options for Installing SMD [page 32]

3.4.2 Installing SMD on a SAP HANA System in Interactive Mode




In interactive mode, the program queries all essential parameters that are not defined using command line options and if invalid parameters are entered the program interrupts the process.

If you specify the host name, make sure that is fully qualified, such as myhost.sap.com (not just myhost).

1. Open a root shell and go to the directory where you mounted the SAP HANA DVD, by entering a command like the following:

cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_642. Call the hanaconfig program in interactive mode by entering this command.

./hanaconfig.sh smdsetup3. Specify the required data.


3.4.3 Installing SMD on a SAP HANA System in Batch Mode


In batch mode, you specify all required values using command line options. If you omit required values or specify invalid values the program interrupts the process.



cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_642. Call the hanaconfig program in batch mode by entering a command like the following:

./hanaconfig --batch smdsetup <smdsetup options>

For the list of all available options, you can call the tool help by entering ./hanaconfig --help.


3.4.4 Call Options for Installing SMD

Syntax


smd_sid system Id no DAA SMD system id

smd_number instance number no 98 SMD instance number




smd_virtual_host virtual host name no - Virtual host name

smd_user_password password yes - SMD administrator user password

smd_user_id user id no - SMD administrator user id

smd_user_shell shell no - SMD administrator login shell

smd_sld_conn_type sld|no no - SLD system connection type

smd_sld_host host name yes if smd_sld_conn_type=sld

- SLD HTTP hostname

smd_sld_port port number yes if smd_sld_conn_type=sld

- SLD HTTP port

smd_sld_user username yes if smd_sld_conn_type=sld

- SLD data supplier user name

smd_sld_password password yes if smd_sld_conn_type=sld

- SLD data supplier password

sm_conn_type ms : P4 Connection via SCS message server

p4 : Direct P4 Connection via Java EE Dispatcher Node

ms_ssl : P4 SSL Connection via SCS message server

p4_ssl : Direct P4 SSL Connection via Java EE Dispatcher Node

no : No connectivity to Solution Manager

no - Solution Manager connection type




sm_host host name yes if sm_conn_type != no

- The fully-qualified host name of the SM Server

sm_port port yes if sm_conn_type != no

- Depending on the connection type either HTTP SCS Message Port, or the Dispatcher P4 Port

sm_user username yes if sm_conn_type != no

- Solution Manager administrator user name

sm_password password yes if sm_conn_type != no

- Solution Manager administrator password

sm_route route string no - Route between the Diagnostics Agent and Solution Manager

sm_route_password password no - SAP router password

3.5 Uninstalling the Solution Manager Diagnostics (SMD) Agent from a SAP HANA System

You can use the hanaconfig.sh program to uninstall the SMD agent from a SAP HANA system.


● You identify the existing system, created by an installation or a file system copy, from which the SMD agent is to be uninstalled.

● You mount the DVD with the HANA On-Site Configuration tool, which you can find at the following location on the SAP HANA DVD:<HANA_DVD>\DATA_UNITS\HANA_IM_LINUX__X86_64

● You are logged in as the root user



3.5.1 Uninstalling SMD Agent in GUI mode

Make sure that you meet the prerequisites in Uninstalling the Solution Manager Diagnostics (SMD) Agent from a SAP HANA System [page 34].

1. Connect to the system with an X server client to enable GUI system access.


cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_64

3. Call the script in GUI mode and select the uninstall task:

./hanaconfig.sh --gui

4. Choose Uninstall Diagnostics Agent.

Follow the instuctions of the wizard.

Related LinksCall Options for Uninstalling SMD [page 36]

3.5.2 Uninstalling SMD Agent in Interactive Mode



1. Open a root shell.

2. In a single-host system, go to this directory:


3. Enter this command:

./hanaconfig.sh smduninstall

NoteNone of the additional call options is mandatory here, only smduninstall. If there is only one host installed with a SMD agent, it is automatically found and uninstalled. If there are more hosts, you need to specify from which one the SMD agent should be uninstalled. You can do this by choosing one from the displayed list of hosts.

4. Specify the data requested by the program.




3.5.3 Uninstalling SMD Agent in Batch Mode


To call the smduninstall program in batch mode, specify all required values using command line options.


NoteIf there is only one host installed with a SMD agent, it is automatically found and uninstalled. If there are more hosts, you need to specify from which one the SMD agent should be uninstalled.


cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_642. Call the hanaconfig program in batch mode by entering a command like the following:

./hanaconfig --batch smduninstall <smduninstall options>


The SMD agent is removed from the selected host.


3.5.4 Call Options for Uninstalling SMD


smd_sid System Id no detected SMD System Id

smd_number Instance number no detected SMD Instance Number

smd_virtual_host virtual host name no detected Virtual Host Name

3.6 Renaming a SAP HANA System

You can rename a SAP HANA system using the hanaconfig.sh program. When you use the rename functionality (also called task), you can:

● change SID, instance number, hostname● change system administrator password



● change database user password● change SUM for SAP HANA SSL keystore password

The tool updates the landscape management (LM) structure folder, and generates new SSL certificates.

NoteIf you rename a SAP HANA system, this normally invalidates the permanent SAP license. You therefore need to reinstall the SAP license. For more information about how to install the license key, see the SAP HANA Database Administration Guide at http://help.sap.com/hana.

Before performing the rename, you need to meet these prerequisites:

● You identify an existing SAP HANA system, created by an installation or a file system copy, that is to be renamed.

● You mount the DVD with the SAP HANA On-Site Configuration tool, which you can find at the following location on the SAP HANA DVD:<HANA_DVD>\DATA_UNITS\HANA_IM_LINUX__X86_64

● The target system ID (SID) must not exist.● The target instance number must not exist.● You are logged in as the root user.● <sapsid>adm user password must contain only ASCII symbols and be at least 8 characters long, and must

contain at least one digit, one lowercase character and one uppercase character. Only the following 3 special characters are allowed: $ _ #.

3.6.1 Renaming a SAP HANA System with GUI

Make sure that you meet the prerequisites in Renaming a SAP HANA System [page 36].




the following:


./hanaconfig.sh --gui 4. Choose Rename HANA System, and then choose Next to continue.

5. Specify the required entries.

NoteYou have the option to specify a dedicated time zone. By default, the time zone is set to UTC (Coordinated Universal Time). In case you want to change only the time zone of the system without renaming it, refer to SAP Note: 1801227.



http://help.sap.com/hana


6. Leave the root shell after the rename has finished.

3.6.2 Renaming a SAP HANA System in Interactive Mode

Make sure that you meet the prerequisites in Renaming a SAP HANA System [page 36] .

In interactive mode, the program queries all essential parameters that are not defined using command line options as well as parameters that have invalid values.

1. Open a root shell and go to the directory where you mounted the SAP HANA DVD, by entering a command like the following:cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_64

2. Call the hanaconfig program with the hanarename task by entering this command:./hanaconfig.sh hanarename

3. Specify the required data.

The system is now renamed.

Related LinksCall Options for Renaming a SAP HANA System [page 38]

3.6.3 Renaming a SAP HANA System in Batch Mode

Make sure that you meet the prerequisites in Renaming a SAP HANA System [page 36].

In batch mode, you specify all required values using command line options. If you omit required values or specify invalid values, the program displays an error message and terminates.


cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_642. Call the hanaconfig program.

./hanaconfig --batch hanarename <rename options>


Related LinksCall Options for Renaming a SAP HANA System [page 38]

3.6.4 Call Options for Renaming a SAP HANA System

Syntax




Description

source_sid current SID

no detected Current system id

target_sid new SID no - New system id

number instance number

no current instance number

New instance number

source_password password yes - Current system administrator password

target_password password yes if the SID is being renamed

New system administrator password

home home directory

no if current home follows the pattern /usr/sap/<SID>/home the SID is changed to the value of "--target_sid"

New system administrator home directory

shell shell no current shell

New system administrator login shell

userid user id no detects free user id

New system administrator user id

timezone time zone name

no - New system administrator time zone (see --print_timezones

hostmap hostname=new hostname

no - Rename hosts<current hostname>=<new fully qualified hostname>

remote_root_user remote root user

Root user for additional hosts

remote_root_user_password remote root user password

Password for the remote root user




Description

ext_host hostname no - New external hostname

keep_user - no - Keeps current system administrator user

change_keystore_password - no no Changes the SSL keystore password

keystore_password password yes, if the hostname is being renamed

- Current SSL keystore password

new_keystore_password password yes, if --change_keystore_password present

- New SSL keystore password

change_system_user_password - no - Changes the database User SYSTEM password

source_system_user_password password yes if --change_system_user_password present

- Current database User SYSTEM password

target_system_user_password password yes if --change_system_user_password present

- New database User SYSTEM password

datapath directory no Renames your old data directories, set by the installer.

Available since Single SP 02 for SPS 05 and for batch mode only. As prerequisites you need to do the following steps in advance:

● mount the new datapath manually to point to the new location. For example, /hana/shared/<new_data>.This location will be used only if the old location data is not accessible.

● copy the content from the old datapath location to the new one

logpath directory no Renames your old log directories, set by the installer.




Description

Available since Single SP 02 for SPS 05 and for batch mode only. As prerequisites you need to do the following steps in advance:

● mount the new logpath manually to point to the new location. For example, /hana/shared/<new_log>. This location will be used only if the old location data is not accessible.

● copy the content from the old logpath location to the new on

In case of rename errors, see the following SAP Note 1792151.

3.7 Configuring a SAP HANA System to Connect to System Landscape Directory (SLD)

With the provided SLD functionality you can configure the connection parameters for the central SLD system. When a SAP HANA system is connected to SLD, it can report its status and provide details and information for the system itself.

You can use the hanaconfig.sh program to configure a SLD connection.

For more related information, see SAP notes 1673424 and also 1649323.


● You identify the existing system, created by an installation or a file system copy, that is to be configured with SLD.

● You mount the DVD with the HANA configuration tool, which you can find at the following location on the SAP HANA DVD:<HANA_DVD>\DATA_UNITS\HANA_IM_LINUX__X86_64

● You are logged in as the root user

3.7.1 Configuring Connection to SLD in GUI










3. Call the script in GUI mode:

./hanaconfig.sh –gui

The wizard starts.

4. Choose <Configure SLD Connection>, then <Next> . Follow the instructions of the wizard.

Related LinksCall Options for Connecting to SLD [page 43]

3.7.2 Configuring Connection to SLD in Interactive Mode

Before you continue, make sure that you meet these prerequisites:

• You are logged on to the host where the server software is installed.

• You are logged on as the root user.



2. Go to the following directory:


3. Enter the following command:

./hanconfig.sh sldconfig



3.7.3 Configuring Connection to SLD in Batch Mode

Before you continue, make sure that you meet these prerequisites:

• You are logged on to the host where the server software is installed.

• You are logged on as the root user.





2. Go to the following directory:


3. Run the hanaconfig program in batch mode using the sldconfig task:

./hanconfig.sh --batch sldconfig <sldconfig options>

For the list of all available options, you can call the tool help, by entering ./hanaconfig --help



3.7.4 Call Options for Connecting to SLD

Option Name Value Mandatory Description

sld_host Host name yes SLD Host name

sld_port Port number yes SLD Port [80,443,1024..65535]

sld_user User name yes SLD Username (Administrator role)

sld_password Password yes SLD Password

sld_use_https - no Use https instead of http connection

hana_sid sid yes, if there is more than one SAP HANA systems installed

System ID

3.8 Installing Application Function Libraries (AFLs) on a SAP HANA System

For installing AFLs in GUI mode, you are prompted to enter the required parameters.


the following:


./hanaconfig.sh --gui



4. Choose Install AFL, and then Next to continue.


For installing AFLs in interactive mode, use the command ./hanaconfig.sh --interactive aflinstall.

You can use as a general guidance the procedure Configuring Connection to SLD in Interactive Mode [page 42].

For installing AFLs in batch mode, use the command ./hanaconfig.sh --batch aflinstall.

You can use as a general guidance the procedure Configuring Connection to SLD in Batch Mode [page 42].

NoteKeep in mind that, after AFLs are installed or updated, the SAP HANA database server is restarted.

Related LinksCall Options for Installing AFLs on SAP HANA System [page 44]

3.8.1 Call Options for Installing AFLs on SAP HANA System

Syntax


--afl_sid system Id yes detected SAP HANA System Id

--afl_path afl path yes Path to AFL archive

--afl_sidadm_pwd password yes SID password of the installed SAP HANA System.

Example./hanaconfig.sh --batch aflinstall --afl_sid ABC --afl_path /usr/local/AFL.SAR

3.9 Installing SAP liveCache Applications (SAP LCA) on a SAP HANA System

You can now install SAP liveCache applications via SAP On-Site Configuration tool. This is currently only supported for the integrated SAP liveCache, single-node scenario.

To install SAP LCA using graphical user interface, follow the procedure below:




2. Open a root shell and go to the directory where you mounted the SAP HANA DVD, by entering a command like the following:cd <HANA_DVD>/DATA_UNITS/HANA_IM_LINUX__X86_64

3. Call the script in GUI mode to perform the install:./hanaconfig.sh --gui

4. Choose Additional Components, and then Next to continue.5. Choose Install LCA, and then Next to continue.6. Specify the required entries by following the instructions of the wizard.

For installing SAP LCA in interactive mode, use the command ./hanaconfig.sh lcainstall. You can use as a general guidance the procedure Configuring Connection to SLD in Interactive Mode [page 42].

For installing SAP LCA in batch mode, use the command ./hanaconfig.sh –batch lcainstall. You can use as a general guidance the procedure Configuring Connection to SLD in Batch Mode [page 42].

3.9.1 Call Options for Installing SAP liveCache Applications

Table 4:Option Name Value Mandatory Default Value Description

--lca_sid system ID yes detected SAP HANA system id

--lca_path path yes Path to LCA archive

--lca_sidadm_pwd password yes System ID password for the installed HANA system

3.10 Changing SAP HANA System Edition

To change SAP HANA system edition in GUI mode, you are prompted to enter the required parameters. The possible options are ENTERPRISE and PLATFORM.


the following:


./hanaconfig.sh --gui 4. Choose Change HANA Edition, and then Next to continue.




For changing SAP HANA system edition in interactive mode, use the command ./hanaconfig.sh changehanaedition. You can use as a general guidance the procedure Configuring Connection to SLD in Interactive Mode [page 42].

For changing SAP HANA system edition in batch mode, use the command ./hanaconfig.sh --batch changehanaedition. You can use as a general guidance the procedure Configuring Connection to SLD in Batch Mode [page 42].

Related LinksCall Options for Changing SAP HANA System Edition [page 46]

3.10.1 Call Options for Changing SAP HANA System Edition

Syntax


--hana_sid system Id no detected SAP HANA System Id

--hana_edition <Platform | Enterprise>

yes SAP HANA Edition Id

Example./hanaconfig.sh --batch changehanaedition --hana_sid ABC --hana_edition ENTERPRISE

3.11 Perform a Distributed SAP HANA Setup

You have the possibility to add (or remove) additional hosts to your SAP HANA system with the On-Site Configuration tool. To do this, follow the procedure below:

Prerequisites

NoteContact your hardware partner if you plan to enhance your existing single-host SAP HANA system to a distributed SAP HANA system (multi-host). The individual hardware partners provide hardware partner specific technologies and best practices to ensure the feasibility of the enhancement and to provide sufficient system performance.

● Ensure that sapsys user group exists on all hosts and has one and the same ID.● On the secondary (additional) hosts, install the SAP Host Agent via the rpm package on the DVD. On the

primary host it will be installed by SAP HANA unified installer.




the following:


./hanaconfig.sh --gui 4. Choose HANA Distributed Setup, and then Next to continue.

5. Choose Add Additional Host (or Remove Additional Host), and then choose Next to continue.

When adding additional host you need to specify what its role is: worker or standby.

6. Specify the required entries.For adding additional host in interactive mode, use the command ./hanaconfig.sh addhost(or removehost). You can use as a general guidance the procedure Configuring Connection to SLD in Interactive Mode.

For adding additional host in batch mode, use the command ./hanaconfig.sh --batch addhost(or removehost) . You can use as a general guidance the procedure Configuring Connection to SLD in Batch Mode.

3.11.1 Call Options for Adding/Removing Hosts

Syntax

Table 5: Add Host OptionsOption Name Value Mandatory Default Value Description

addhost_sid System ID No Detected System ID of the new host

addhost_hostname Hostname Yes Hostname

addhost_master_password Password Yes System administrator password

addhost_root_user Root user Yes Root user

addhost_root_user_password Root user password

Yes Root user password

addhost_role Role Yes Additional host role

addhost_ha_group High availability group

No Failover group in High Availability scenarios

addhost_storage_partition Storage partition No Storage partition number



Table 6: Remove Host OptionsOption Name Value Mandatory Default Value Description

removehost_sid System ID No Detected System ID of the existing host

removehost_hostname Hostname Yes Hostname of the existing host

removehost_root_user Root user Yes Root user of the existing host

removehost_root_user_password Root user password

Yes Root user password of the existing host



4 Post-InstallationYou can perform the post-installation steps of your choice, described in the following sections, after the SAP HANA unified installer has finished:

Related LinksStarting and Stopping the SAP HANA System [page 49]Displaying the Process List [page 51]Logging on to the SAP HANA System Using the SAP HANA Studio [page 52]Ensuring User Security [page 52]Configuring the Software Update Manager for SAP HANA [page 52]Accessing the SAP HANA Studio Repository [page 54]Enabling Automatic Start of the SAP HANA Database [page 54]Applying Updates and Support Packages [page 54]Monitoring the SAP HANA System Landscape [page 55]

4.1 Starting and Stopping the SAP HANA System

After the installation has finished successfully, the SAP HANA system is up and running. So you do not need to start the SAP HANA system.

However, if required, you can start and stop the SAP HANA system from the command line in one of the following ways:

● By using the sapcontrol program:

a) Log on to the SAP HANA system host as a user with root authorization.b) Execute one of the following commands:

○ Start the SAP HANA system by entering the following command: /usr/sap/hostctrl/exe/sapcontrol -nr <Instance_Number> -function Start

○ Stop the SAP HANA system by entering the following command: /usr/sap/hostctrl/exe/sapcontrol -nr <Instance_Number> –function Stop

● By using the HDB program:

a) Log on to the SAP HANA system host as user <sapsid>adm.b) Execute one of the following commands:

○ Start the SAP HANA system by entering the following command: /usr/sap/<SAPSID>/<Instance_Name>/HDB start Example:/usr/sap/KB1/HDB26/HDB start

○ Stop the SAP HANA system by entering the following command: /usr/sap/<SAPSID>/<Instance_Name>/HDB stop Example:/usr/sap/KB1/HDB26/HDB stop

Note

SAP HANA Installation Guide with SAP HANA Unified InstallerPost-Installation


The SAP HANA database does not start automatically by default when the SAP HANA system is started. But you can enable such automated start. For more information, see Enabling Automatic Start of the SAP HANA Database [page 54].

4.2 Performing Initial Backup of SAP HANA System

We strongly recommend you to perform initial backup of your system, once you have finished the installation.

For more information, see the section Backing Up Systems in the SAP HANA Database Administration Guide.

4.3 Enabling Persistence Encryption

To ensure that the SAP HANA database can always be restored to its most recent committed state, all data is periodically copied to disk. Privacy of data on disk can be ensured by enabling persistence encryption.

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 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.

NoteYou must be logged on to the SAP HANA host as the operating system user, <sid>adm.

1. Generate a root encryption key using the hdbnsutil program.

CautionDo 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=ALL2. Enable persistence encryption by executing the following SQL command:

ALTER SYSTEM PERSISTENCE ENCRYPTION ON

Encryption is now active. We recommend that you periodically change the encryption key used to encrypt pages in the data area in line with your organization's security policy.Related LinksSAP HANA Security GuideSAP HANA Administration Guide



http://help.sap.com/hana/hana_admin_en.pdf



4.4 Displaying the Process List

Prerequisites

You are logged on to the SAP HANA host as user root .

Procedure

You can display SAP HANA system processes by executing the following commands 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 Windows PC.

ExampleDisplaying the Process List

myhost.sap.com:/mnt/HANA_DVD/DATA_UNITS/HANA_IM_LINUX__X86_64 # /usr/sap/hostctrl/exe/sapcontrol -nr 39 -function GetProcessList

18.07.2011 13:13:34

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

hdbdaemon, HDB Daemon, GREEN, Running, 2011 07 18 11:02:30, 2:11:04, 1598

hdbnameserver, HDB Nameserver, GREEN, Running, 2011 07 18 11:02:32, 2:11:02, 1627

hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2011 07 18 11:02:39, 2:10:55, 1671

hdbindexserver, HDB Indexserver, GREEN, Running, 2011 07 18 11:02:42, 2:10:52, 1688

hdbstatisticsserver, HDB Statisticsserver, GREEN, Running, 2011 07 18 11:02:44, 2:10:50, 1696

wdflbmd0417:/mnt/HANA_DVD/DATA_UNITS/HANA_IM_LINUX__X86_64 #



4.5 Logging on to the SAP HANA System Using the SAP HANA Studio

Prerequisites

● The installation has finished successfully.● You have installed and started the SAP HANA studio on your local PC as described in the SAP HANA Database

- Studio Installation and Update Guide.

Procedure

1. Open the Administration Console perspective .2. Right-click on the Navigator view and select Add System.3. Specify the required parameters, such as host name, instance number, and SAP system ID (SAPSID).4. Choose Authentication by database user and enter SYSTEM for User Name .

Result

You see your SAP HANA system in the Navigator view.

Related LinksEnsuring User Security [page 52]

4.6 Ensuring User Security

After the installation has finished, the master password is assigned to all users that were created by the installer. Make sure that you replace the master password with passwords that comply with your security guidelines. For more information, see the SAP HANA Security Guide.

Related LinksLogging on to the SAP HANA System Using the SAP HANA Studio [page 52]Users Created During the Installation [page 21]

4.7 Configuring the Software Update Manager for SAP HANA

In addition to the SUM default configuration, you have to provide the server certificate for the SAP HANA Update UI.

You have to do this for each SAP HANA studio installation where the SAP HANA Update UI is to be used.

NoteFrom SPS 04 version (or newer), the certificates are automatically imported, and you do not need to import them. If your SAP HANA studio is SPS 03 or older, do the following procedure:



https://service.sap.com/~sapidb/011000358700000604592011.pdf



1. Copy the server certificate sumforhana.cer from /usr/sap/<SID>/SUM/config/sumforhana.cer to the host where the SAP HANA studio is installed.

2. Run the following command using administrator's privileges from the directory where you have copied sumforhana.cer:keytool -importcert -keystore "<JRE_DIR>\lib\security\cacerts" -alias sumforhana_$<hostname>_$<SAPSID> -file sumforhana.cer

Note

<JRE_DIR> is the path to the Java runtime used by the SAP HANA studio. To find this path, choose Help About SAP HANA Studio Installation Details Configuration and check the value of the java.home

property.

If the SAP HANA studio is installed on a UNIX/LINUX system, use forward slashes / in the command above.

You are asked for the key store password. Note that this is different from the password for the server key store. The default password for the cacerts key store is changeit, but if it has been changed you have to find out what it is and provide it here.

3. Restart the SAP HANA studio.

If the default security configuration is not suitable for your organization, see the SAP HANA Automated Update Guide for detailed configuration information. For security considerations, see the SAP HANA Security Guide.

ExampleContents of the SUM config directory after the installation has finished

wdflbmd7674:/usr/sap/S51/SUM/config # ll

total 32

drwxr-xr-x 2 s51adm sapsys 4096 Sep 2 00:30

drwxr-xr-x 23 s51adm sapsys 4096 Sep 2 00:30 .

-r-------- 1 s51adm sapsys 33 Sep 2 00:30 catalina.properties

-rw-r--r-- 1 s51adm sapsys 1238 Sep 2 00:30 keystore.jks

-rw-r--r-- 1 s51adm sapsys 449 Sep 2 00:30 sumforhana.cer

-rw-r--r-- 1 root root 4111 Aug 18 19:21 tomcat-server.xml






4.8 Accessing the SAP HANA Studio Repository

The Software Update Manager (SUM) for SAP HANA server also hosts the p2 update site for the SAP HANA studio.

1. Make sure that the SUM for SAP HANA server is up and running.If required, start the SUM for SAP HANA as described in the SAP HANA Automated Update Guide.

2. Access the SAP HANA Studio p2 update site using the following URL:https://<hostname>:8080/studio_repository

Related LinksConfiguring the Software Update Manager for SAP HANA [page 52]

4.9 Enabling Automatic Start of the SAP HANA Database

By default the SAP HANA database is configured so that it is not started automatically when the SAP HANA host is rebooted.

If required, you can change this configuration by modifying the profile of the SAP HANA database as follows:

1. Log on to the SAP HANA host as a user with root authorization.

2. Change to the system profile directory /usr/sap/<SAPSID>/SYS/profile.

3. Edit the profile <SID>_HDB<Instance_No>_<host_name>.

4. Change the parameter setting Autostart = 0 to Autostart = 1 .5. Save the profile <SID>_HDB<Instance_No>_<host_name>.

The SAP HANA database is started automatically when the SAP HANA host is rebooted.

4.10 Applying Updates and Support Packages

Prerequisite:

You have configured the SUM for SAP HANA as described in Configuring the Software Update Manager for SAP HANA [page 52]

Procedure:

Use the Lifecycle Management perspective in the SAP HANA studio to update your system. For more information, see the SAP HANA Automated Update Guide.





4.11 Monitoring the SAP HANA System Landscape

Install and configure the required monitoring tools:

● SAP HANA studio for monitoring the SAP HANA database - see SAP HANA Administration Guide● SAP NetWeaver monitoring tools● Monitoring tools of other SAP HANA components (for example SAP BusinessObjects monitoring tools)

NoteFor more information, see SAP HANA Technical Operations Manual, section Monitoring the SAP HANA System Landscape.




http://help.sap.com/hana/hana_tom_en.pdf

5 Installing Trigger-Based ReplicationFor information about SAP HANA installation and upgrade for the trigger-based replication, see the SAP HANA Installation Guide - Trigger-Based Replication.

NoteFor trigger-based replication, no additional components will be installed on the SAP HANA system.

Related LinksSAP HANA Installation Guide - Trigger-Based Replication


SAP HANA Installation Guide with SAP HANA Unified InstallerInstalling Trigger-Based Replication


6 Installing the SAP HANA Direct Extractor Connection (DXC)For information about SAP HANA installation and configuration for the extractor-based data acquisition, see SAP HANA Direct Extractor Connection Implementation Guide.

Related LinksSAP HANA Direct Extractor Connection Implementation Guide

SAP HANA Installation Guide with SAP HANA Unified InstallerInstalling the SAP HANA Direct Extractor Connection (DXC)



7 Installing ETL-Based ReplicationYou can add existing SAP BusinessObjects products to the SAP HANA landscape. The information below provides a list of the available documentation to integrate SAP Data Services to your SAP HANA landscape.

In addition to these SAP HANA components, the customer can add existing SAP BusinessObjects products to the SAP HANA landscape to use SAP BusinessObjects end user clients like SAP BusinessObjects Explorer or SAP BusinessObjects Xcelsius on top to analyze the data.

If you are not using BusinessObjects Enterprise with SAP Data Services, you need information platform services installed together with SAP Data Services.

Related LinksInformation Platform Services Installation Guide for UNIXInformation Platform Services Installation Guide for WindowsData Services Installation Guide for UNIXData Services Installation Guide for WindowsData Services Upgrade Guide


SAP HANA Installation Guide with SAP HANA Unified InstallerInstalling ETL-Based Replication






8 Appendix

8.1 Applying Single Support Package 02 for SAP HANA Unified Installer SPS 05

The following topic describes how to apply Single Support Package 02 (Single SP 02) for SAP HANA SPS 05 unified installer.

1. Go to SAP Service Marketplace using the following URL: https://service.sap.com/swdc.2. Choose Software Downloads, then Support Packages and Patches.3. Choose Browse our Download Catalog.4. Choose SAP In-Memory (SAP HANA) , then your SAP HANA edition. For example, SAP HANA Enterprise

Edition and its version SAP HANA Enterprise Edition 1.0.5. Choose SAP HANA Installation & Update, then HANA Unified Installer 1.0,6. Choose Linux on x86 64 64bit, then double-click on the HANAINSTALL05_3-20009106.TAR.7. Save the archive to your custom location and extract it there.8. Copy the HANA_IM_LINUX__X86_64 folder, contained in the archive, and replace the original

HANA_IM_LINUX__X86_64 folder in the SAP HANA SPS 05 DVD.9. Continue with the installation of SAP HANA as usual.

In case you extract the archive on another location and you want to start the installation from there, you can use the -d dvd_location option to specify the location of the DVD content.

For example, ./setup.sh -d custom_folder/ /tmp/hana_setup/ /tmp/setuphana.slmodel

SAP HANA Installation Guide with SAP HANA Unified InstallerAppendix


https://service.sap.com/swdc

www.sap.com/contactsap

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

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

hana sps5 inst en

Documents