IP]]OPen windwsOpen E

PUBLIC

SAP HANA Platform SPS 12

Document Version: 1.1 – 2016-09-13

SAP HANA Server Installation and Update Guide

Open Word

Content

1 SAP HANA Installation and Update Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1 SAP HANA Platform Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.2 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

2 Concepts and Requirements for an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 SAP HANA System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

2.2 SAP HANA System Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3 SAP HANA Deployment Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.4 SAP HANA Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Recommended File System Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.5 SAP HANA and Virtualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

3 Using the SAP HANA Platform LCM Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.1 Choosing the Correct SAP HANA HDBLCM for Your Task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

3.2 Performing LCM Tasks by Program Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Use the Graphical User Interface to Perform Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . 29 Use the Command-Line Interface to Perform Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . .30

Using the Web User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.3 Performing LCM Tasks by Program Interaction Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Use Interactive Mode to Perform Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Use Advanced Interactive Mode to Perform Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . . 38

Use Batch Mode to Perform Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.4 Performing LCM Tasks by Parameter Entry Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Entering Platform LCM Parameters Interactively. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Use LCM Configuration Files to Enter Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Entering Platform LCM Parameters as Call Options from the Command Line. . . . . . . . . . . . . . . 45

3.5 Executing Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Centralized Execution of Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Decentralized Execution of Platform LCM Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.6 Additional Information About Using the SAP HANA Platform LCM Tools. . . . . . . . . . . . . . . . . . . . . 52 Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Linux Kernel Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

General Troubleshooting for the SAP HANA Platform LCM Tools. . . . . . . . . . . . . . . . . . . . . . . . 54

4 Installing an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

4.1 Getting Started with SAP HANA System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Mandatory Installation Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Changeable Default Values for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Users Created During Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Specifying Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.2 Installing a Single-Host System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Install a Single-Host SAP HANA System Using the Graphical User Interface. . . . . . . . . . . . . . . . 62

Install a Single-Host SAP HANA System Using the Command-Line Interface. . . . . . . . . . . . . . . .64

4.3 Installing a Multiple-Host System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Multiple-Host System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Install a Multiple-Host SAP HANA System Using the Graphical User Interface. . . . . . . . . . . . . . . 70

Install a Multiple-Host SAP HANA System Using the Command-Line Interface. . . . . . . . . . . . . . 73

4.4 Installing a Multitenant Database Container SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Install a Multitenant Database Container System Using the Graphical User Interface. . . . . . . . . . 77

Install a Multitenant Database Container System Using the Command-Line Interface. . . . . . . . . 79

4.5 Installing XS Advanced Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 System Concepts for XS Advanced Runtime Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Install the XS Advanced Runtime Using the Graphical Interface. . . . . . . . . . . . . . . . . . . . . . . . . 85

Install the XS Advanced Runtime Using the Command-Line Interface. . . . . . . . . . . . . . . . . . . . .89 4.6 System Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

5 Updating the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5.1 Changeable Default Values for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.2 Preparing for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Preparing for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Prepare for Update Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

5.3 Prepare an Update for Reduced SAP HANA System Downtime. . . . . . . . . . . . . . . . . . . . . . . . . . . 106

5.4 Perform an Optimized Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

5.5 Update an SAP HANA System Using the Graphical User Interface. . . . . . . . . . . . . . . . . . . . . . . . . .111

5.6 Update an SAP HANA System Using the Command-Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . 113 5.7 Update an SAP HANA System Using the Web User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

6 Managing SAP HANA System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

6.1 Installing or Updating SAP HANA Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Install or Update SAP HANA Components Using the Graphical User Interface. . . . . . . . . . . . . . 122

Install or Update SAP HANA Components Using the Command-Line Interface. . . . . . . . . . . . . .124 Install or Update SAP HANA Components Using the Resident Program. . . . . . . . . . . . . . . . . . .125

Install or Update SAP HANA Components Using the Web User Interface. . . . . . . . . . . . . . . . . . 128

6.2 Uninstalling SAP HANA Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 Uninstall SAP HANA Components Using the Graphical User Interface. . . . . . . . . . . . . . . . . . . . 131 Uninstall SAP HANA Components Using the Command-Line Interface. . . . . . . . . . . . . . . . . . . 133

Uninstall an SAP HANA Component on a System Missing the SAP HANA Resident Program

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Uninstall SAP HANA Components Using the Web User Interface. . . . . . . . . . . . . . . . . . . . . . . 135

7 Uninstalling the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

7.1 Uninstall the SAP HANA System Using the Graphical User Interface. . . . . . . . . . . . . . . . . . . . . . . 138 7.2 Uninstall the SAP HANA System Using the Command-Line Interface. . . . . . . . . . . . . . . . . . . . . . . 139

8 Uninstalling the SAP HANA System with XS Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

8.1 Uninstall the SAP HANA System with XS Advanced Using the Graphical User Interface. . . . . . . . . . 141

8.2 Uninstall the SAP HANA System with XS Advanced Using the Command-Line Interface. . . . . . . . . 142

8.3 Uninstall XS Advanced Using the Graphical User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 8.4 Uninstall XS Advanced Using the Command-Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

9 Managing the SAP HANA System After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

9.1 Start and Stop the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

9.2 Display the Process List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

9.3 Create a Lesser-Privileged Database User for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

9.4 Enable Data Volume Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Enable Data Volume Encryption with System Reinstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Enable Data Volume Encryption Without System Reinstallation. . . . . . . . . . . . . . . . . . . . . . . . 154

9.5 Change the Root Encryption Key for Data Volume Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

9.6 Change the Root Key of the Internal Data Encryption Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

10 Tutorials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

10.1 Tutorial: Using Custom Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

10.2 Tutorial: Installing a Multiple-Host System Using a Configuration File in Batch Mode. . . . . . . . . . . . 161

10.3 Tutorial: Overwriting Configuration File Parameters with Command Line Parameters. . . . . . . . . . . 162

10.4 Tutorial: Installing a Single-Host System with Passwords Read from XML Standard Input Stream

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 10.5 Tutorial: Automating Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

11 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

11.1 Accessing the Underlying Installer Components (pass_through_help). . . . . . . . . . . . . . . . . . . . . . 173

11.2 Locating all SAP HANA File System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

11.3 Enabling the Installer Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

11.4 Checking the Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

11.5 Adding hdblcm to an Existing SAP HANA Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

11.6 Disabling the Optimized Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

11.7 Dealing with a Failed Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177

11.8 Removing a Partially Installed System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178

11.9 Adjusting the System Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

11.10 Skipping the Import of Initial XS Advanced Runtime Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 11.11 Proxy Server Settings for SAP HANA Installations with XS Advanced Runtime. . . . . . . . . . . . . . . . 178

12 Parameter Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

12.1 action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

12.2 addhosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

12.3 add_local_roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

12.4 add_roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

12.5 ase_datapath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

12.6 ase_logpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

12.7 ase_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

12.8 autoadd_xs_roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

12.9 autostart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

12.10 basepath_streaming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

12.11 batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

12.12 certificates_hostmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

12.13 change_system_user_password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

12.14 check_installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

12.15 checkmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

12.16 check_only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

12.17 client_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

12.18 component_dirs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

12.19 component_medium. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

12.20 component_root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

12.21 components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

12.22 configfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

12.23 continue_update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

12.24 copy_repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192

12.25 custom_cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

12.26 databackuppath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193

12.27 datapath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

12.28 db_isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

12.29 db_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

12.30 dump_configfile_template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

12.31 es_datapath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

12.32 es_logpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

12.33 extract_components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

12.34 groupid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

12.35 help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

12.36 home. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

12.37 hostmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

12.38 hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

12.39 https. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

12.40 ignore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

12.41 import_content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

12.42 import_xs_content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

12.43 init_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

12.44 init_user_home_dir. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

12.45 install_hostagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

12.46 install_ssh_key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

12.47 internal_network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

12.48 isc_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

12.49 keep_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

12.50 keep_user_home_dir. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

12.51 listen_interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

12.52 list_systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

12.53 load_initial_xs_content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

12.54 logbackuppath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

12.55 logpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

12.56 max_mem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

12.57 nostart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

12.58 nostart_tenant_db. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

12.59 number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

12.60 org_manager_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

12.61 org_name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

12.62 prepare_update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

12.63 prod_space_name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

12.64 rdsync_downloadpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

12.65 rdsync_uploadpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

12.66 read_password_from_stdin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

12.67 remote_execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

12.68 removehosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

12.69 repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

12.70 restrict_max_mem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

12.71 root_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

12.72 sapmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

12.73 scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

12.74 shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

12.75 sid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

12.76 skip_modify_sudoers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

12.77 sld_hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

12.78 sld_password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

12.79 sld_port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

12.80 sld_username. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215

12.81 source_sid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

12.82 sso_cert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

12.83 storage_cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

12.84 studio_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217

12.85 studio_repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

12.86 system_usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218

12.87 system_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218

12.88 target_sid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

12.89 timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

12.90 update_execution_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

12.91 userid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

12.92 version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

12.93 vm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

12.94 xs_components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

12.95 xs_components_cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

12.96 xs_customer_space_isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

12.97 xs_customer_space_user_id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

12.98 xs_domain_name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

12.99 xs_routing_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

12.100 xs_sap_space_isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 12.101 xs_sap_space_user_id. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

13 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

1 SAP HANA Installation and Update Overview

This SAP HANA Installation and Update Guide describes how to install or update an SAP HANA system and its components with the SAP HANA database lifecycle manager (HDBLCM).

The SAP HANA database lifecycle manager is used to install either individual or multiple SAP HANA components in combination with the server. Compared to previous SAP HANA installers, the SAP HANA database lifecycle manager provides an efficient and optimized installation path, allowing you to customize your SAP HANA installation by selecting which components should be installed and updated. It is also now possible to perform installation in interactive graphical or interactive command-line interfaces, as well as configure the SAP HANA installation to be automated, using command line, the configuration file, and batch mode.

It is worth noting, that the SAP HANA component installation concept has changed significantly with the fastpaced development of SAP HANA itself. In the early SAP HANA Support Package Stack (SPS) releases, the

SAP HANA components had to be installed individually, which proved to be a time-consuming task. Then, the SAP HANA unified installer was developed to streamline the installation process by installing all required components from one call to the installer. As of SPS 08, the unified installer is no longer shipped with SAP

HANA.

With SAP HANA SPS 07, the SAP HANA database lifecycle manager was introduced to offer the efficiency of installing all components at one time, while providing further flexibility to customize and automate the installation. The components can now be installed, upgraded, or uninstalled from one tool, in both commandline or graphical user interface.

As of SAP HANA SPS 08, it is possible to also perform post-installation configurations tasks, such as renaming the system, adding or removing hosts, and reconfiguring the system, using the SAP HANA database lifecycle manager. For more information, see the SAP HANA Administration Guide.

With the SAP HANA SPS 09 release, the SAP HANA database lifecycle manager offers a third user interface - the Web user interface - in addition to graphical user and command-line interfaces. The Web user interface can be accessed in a standalone Web browser or in the Platform Lifecycle Management view in the SAP HANA studio. Therefore, as of SPS 09, the SAP HANA database lifecycle manager is capable of performing all actions offered in the SAP HANA platform lifecycle management portfolio and is the only recommended tool for these actions. As of SPS 09, SAP HANA supports IBM Power systems.

Before starting the installation of SAP HANA, make sure that you have reviewed the SAP HANA Master Guide.

Related Information

SAP HANA Master Guide

SAP HANA Administration Guide

1.1 SAP HANA Platform Software Components

SAP HANA platform is composed of several components.

The SAP HANA platform edition is the technical foundation of the SAP HANA platform and various SAP HANA editions. The SAP HANA platform edition comprises among others:

● SAP HANA Database

● SAP HANA Client

● SAP HANA Studio

● SAP HANA XS advanced runtime

● SAP HANA XS Engine

● SAP HANA Advanced Data Processing

● SAP HANA Spatial

SAP HANA features, SAP HANA capabilities, SAP HANA options provide additional functions. To use the SAP HANA options and SAP HANA capabilities you need a dedicated license for the options or capabilities you want to use (see disclaimer below). SAP HANA options and SAP HANA capabilities are among others:

● SAP HANA Accelerator for SAP ASE

● SAP HANA Dynamic Tiering

● SAP HANA Remote Data Sync

● SAP Landscape Transformation Replication Server ● SAP HANA Smart Data Streaming

Note

For information about the availability of the SAP HANA features, SAP HANA capabilities, SAP HANA options on Intel-based hardware platforms or on IBM Power servers, see SAP HANA Hardware and Software Requirements in the SAP HANA Master Guide.

Caution

SAP HANA server software and tools can be used for several SAP HANA platform and options scenarios as well as the respective capabilities used in these scenarios. The availability of these is based on the available SAP HANA licenses and the SAP HANA landscape, including the type and version of the back-end systems the SAP HANA administration and development tools are connected to. There are several types of licenses available for SAP HANA. Depending on your SAP HANA installation license type, some of the features and tools described in the SAP HANA platform documentation may only be available in the SAP HANA options and capabilities, which may be released independently of an SAP HANA Platform Support Package Stack (SPS). Although various features included in SAP HANA options and capabilities are cited in the SAP HANA platform documentation, each SAP HANA edition governs the options and capabilities available. Based on this, customers do not necessarily have the right to use features included in SAP HANA options and capabilities. For customers to whom these license restrictions apply, the use of features included in SAP HANA options and capabilities in a production system requires purchasing the corresponding software license(s) from SAP. The documentation for the SAP HANA optional components is available in SAP Help Portal at http://help.sap.com/hana_options. If you have additional questions about what your particular license provides, or wish to discuss licensing features available in SAP HANA options, please contact your SAP account team representative.

SAP HANA Server Installation and Update Guide

SAP HANA Installation and Update Overview

Related Information

SAP HANA Hardware and Software Requirements [page 19]

1.2 Software Download

In the SAP Software Download Center, you have access to the installation media and components for SAP HANA.

Installation Media and Components for SAP HANA

Installation Media for an SAP HANA SPS

1. Open the SAP Software Download Center.

2. Choose Software Downloads.

3. Choose INSTALLATIONS & UPGRADES.

4. Choose By Alphabetical Index (A-Z).

5. Choose H.

6. Choose SAP HANA PLATFORM EDITION.

7. Choose DOWNLOADS.

8. Choose SAP HANA PLATFORM EDIT. 1.0.

9. Choose DOWNLOADS.

10. Choose INSTALLATION.

Support Packages and Patches for SAP HANA

1. Open the SAP Software Download Center.

2. Choose Software Downloads.

3. Choose SUPPORT PACKAGES & PATCHES.

4. Choose By Alphabetical Index (A-Z).

5. Choose H.

6. Choose SAP HANA PLATFORM EDITION.

7. Choose DOWNLOADS.

8. Choose SAP HANA PLATFORM EDIT. 1.0.

9. Choose DOWNLOADS.

10. Choose ENTRY BY COMPONENT or SUPPORT PACKAGE STACK DOWNLOAD.

For more information, see Application Overview and Help on SAP Software Download Center.

SAP HANA Server Installation and Update Guide

SAP HANA Installation and Update Overview

Responsibilities

The responsibility for acquiring and installing SAP HANA depends on the chosen deployment model:

● If a customer chooses the SAP HANA Tailored Datacenter Integration, the components of SAP HANA must be installed on validated hardware by a certified administrator or official SAP HANA hardware partner.

● If a customer chooses an SAP HANA appliance, then the components of SAP HANA can only be installed by certified hardware partners on validated hardware running a specific operating system. Any other system or content developed with systems of this type is not supported by SAP. For more information, see the information page of the product version. Support Package Stacks (SPS) can be downloaded and applied to appliances in accordance with agreements with the respective hardware partner.

Related Information

SAP Software Download Center

Application Overview and Help

2 Concepts and Requirements for an SAP HANA System

Before installing or updating an SAP HANA system, it is important to understand the basic system concepts and SAP HANA database lifecycle manager (HDBLCM) features in order to optimize the installation or update process and avoid unnecessary reconfiguration.

An SAP HANA system is made up of the SAP HANA server and its components. The system can be installed on one or multiple system hosts, which are configured to operate as worker or standby hosts. As of SAP HANA Support Package Stack (SPS) 09, the SAP HANA system can be installed or configured to be a multitenant database container enabled system. Where a single tenant database container system contains exactly one database, a multitenant database container enabled system contains one system database and can contain multiple tenant databases.

The SAP HANA database lifecycle manager offers three user interfaces: graphical, command-line, and Web. System installation can be performed using the graphical user or command-line interface. System update, or component installation or update can be performed using any of the three user interfaces.

The SAP HANA database lifecycle manager can be run interactively, requiring step-by-step input, or it can be run in batch mode, requiring no subsequent input. Defining installation and update parameters can be entered interactively, in a configuration file, or in combination with the call to the program on the command line.

Note

The components of SAP HANA can only be installed by certified hardware partners, or any person holding E_HANAINS certification, on validated hardware running an approved operating system.

2.1 SAP HANA System Concepts

An SAP HANA system is composed of three main components: the host, the system, and the instance.

Host

A host is the operating environment in which the SAP HANA database runs. The host provides all the resources and services (CPU, memory, network, and operating system) that the SAP HANA database requires. The storage for an installation does not have to be on the host. For multiple-host systems, a shared storage or a storage that is accessible on-demand from all hosts is required.

For more information about the restrictions that apply to host names in SAP systems, see SAP Note 611361 in Related Information.

Instance (HDB)

An SAP HANA instance (HDB) is the smallest operational unit on a host. It is the set of SAP HANA system components that are installed on one host. A single-host system contains one instance on the one host. A multiple-host system contains several instances distributed across the multiple hosts (one per host). Every system has an instance number, which is a two-digit identifier. Each instance in a multiple-host system must have the same instance number.

System

A system is one or more instances with the same number. The term "system" is interchangeable with the term "SAP HANA database". If a system has more than one instance, they must be dispersed over several hosts as a multiple-host system. Every system has a unique SAP system ID (SID).

Related Information

SAP Note 611361 - Hostnames of SAP Servers

2.2 SAP HANA System Types

An SAP HANA system can be configured as a single-host or multiple-host system using the SAP HANA database lifecycle manager.

The SAP HANA system type definitions are as follows:

● Single-host system - One SAP HANA instance on one host.

● Multiple-host (distributed) system - Multiple SAP HANA instances distributed over multiple hosts, with one instance per host.

A single-host system is the simplest system installation type. It is possible to run an SAP HANA system entirely on one host and then scale the system up as needed. The SAP HANA database lifecycle manager can be used to install an SAP HANA single-host system in one of the program interfaces, and with a combination of parameter specification methods.

The following graphic shows the file system for a single-host installation:

A multiple-host system is a system with more than one host, which can be configured as active worker hosts or idle standby hosts. The SAP HANA database lifecycle manager can be used to install an SAP HANA multiple-host system in one of the program interfaces, and with a combination of parameter specification methods. To add hosts to an existing system, use the SAP HANA resident HDBLCM. For more information about installing a multiple-host system, see the Related Information.

The following graphic shows the file system for a multiple-host system installed on a shared file system with three hosts:

The server software is based on a flexible architecture that enables a distributed installation. This means that load can be balanced between different hosts. The server software has to be installed in a shared file system. This file system has to be mounted by all hosts that are part of the system.

Related Information

Installing a Multiple-Host System [page 66]

2.3 SAP HANA Deployment Types

SAP HANA can be deployed in a number of configurations that are approved in varying degrees for production environments (or not approved for production at all).

The server installation documentation is mainly written for SAP HANA deployment types which are completely approved for production environments, that is to say, an SAP HANA system running on dedicated hardware, or multitenant database container systems (also known as MDC systems).

Multitenant Database Containers (MDC)

The multitenant database container deployment type was introduced with SAP HANA Support Package Stack (SPS) 09, and makes it possible to run several SAP HANA instances on the same hardware in a production environment. It provides an alternative to a virtualized deployment, which is only production approved in some scenarios, and the MCOS (Multiple Components One System) deployment, which is not approved for production environments.

It is possible to install an SAP HANA as a multitenant database container system using the SAP HANA database lifecycle manager (HDBLCM). As of SPS 10, you can specify a database isolation type during installation of a multitenant database container system. High isolation can be configured to protect against unauthorized access at the operating-system level by separating system administrator users and providing authenticated communication within databases. For more information, see Database Isolation in the SAP HANA Administration Guide or the SAP HANA Security Guide and db_isolation in Related Information.

If you have an SAP HANA system which you would like to update to support multitenancy, you must first update the SAP HANA system to revision 90 or later, and then convert the SAP HANA system to support multitenant database containers. For more information, see Convert an SAP HANA System to Support Multitenant Database Containers in the SAP HANA Administration Guide.

Multiple Components on One Database (MCOD)

MCOD deployments are characterised by multiple applications on one SAP HANA system. SAP supports deploying and running multiple applications on a single SAP HANA production database only for packaged applications and scenarios listed on the "White List" included in SAP Note 1661202. If a particular packaged application or scenario is not on the "White List", then it is not supported to run together on the same SAP HANA database with any other packaged application or scenario. For more information, see SAP Note 1661202 in Related Information.

Virtualized

SAP HANA systems can be run on virtual machines with restrictions to the hypervisor (including logical partitions). For more information about running SAP HANA virtualized, see SAP Note 1788665, 2230704 and 2024433 in Related Information.

Multiple Components on One System (MCOS)

MCOS deployments are characterized by multiple SAP HANA systems on one host. This configuration is approved for production environments as of SAP HANA Support Package Stack (SPS) 09. This is restricted to single host / scale-up scenarios only. Please keep in mind that multi-SID requires significant attention to various detailed tasks related to system administration and performance management. For more information about running SAP HANA virtualized, see SAP Note 1681092 in Related Information.

It is approved for production environments for SAP HANA systems to share hardware between the SAP HANA server and SAP HANA options. As of SPS 10, you have the option to install SAP HANA systems with multiple host roles - including database server roles and SAP HANA option host roles - on one host, or give an existing SAP HANA host additional roles during system update. For more information about configuring additional host roles, see add_local_roles and add_roles in Related Information.

Caution

Related Information

Install a Multitenant Database Container System Using the Graphical User Interface [page 77]

Install a Multitenant Database Container System Using the Command-Line Interface [page 79]

SAP HANA Administration Guide

SAP Note 1661202 - Support for multiple applications on SAP HANA

SAP Note 1681092 - Multiple SAP HANA DBMSs (SIDs) on one SAP HANA system

SAP Note 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments

SAP Note 2230704 - SAP HANA on IBM Power Systems with multiple - LPARs per physical host

SAP Note 2024433 - Multiple SAP HANA VMs on VMware vSphere in production

add_local_roles [page 182] add_roles [page 183] db_isolation [page 194]

2.4 SAP HANA Hardware and Software Requirements

For SAP HANA, a number of hardware and software requirements apply.

Note

You can find a complete list of all SAP HANA components and the corresponding SAP HANA hardware and software requirements in the Product Availability Matrix (PAM) on the SAP Service Marketplace, in the SAP HANA Hardware Directory and in the SAP Community Network.

Software Requirements

Note

Only software installed by certified hardware partners, or any person holding certification, is recommended for use on the SAP HANA system. Do not install any other software on the SAP HANA system. The components of SAP HANA can only be installed by certified hardware partners, or any person holding certification. Furthermore, it must be installed on validated hardware running an approved operating system. Check the SAP Education resources for information about the SAP HANA certification exams.

Supported Hardware Platforms

SAP HANA is available for:

● Intel-Based Hardware Platforms

● IBM Power Systems

Note

You can perform a system copy of an SAP system with SAP HANA database as the source database and also SAP HANA database as the target database. This is relevant if you want to change the hardware platform on SAP HANA system.

For more information, see the SAP NetWeaver Documentation for your SAP NetWeaver release under

Installation

System Copy

The following SAP HANA features, SAP HANA capabilities, and SAP HANA options are supported on Intelbased hardware platforms only:

● SAP HANA Accelerator for SAP ASE

● SAP HANA Hadoop Controller

● SAP HANA Remote Data Sync

● SAP HANA Smart Data Streaming

● SAP HANA Data Provisioning Agent

● Hive ODBC Driver

For detailed information about the supported hardware, see Related Information in On-Premise in the SAP HANA Master Guide.

Supported Operating Systems for SAP HANA

For information about supported operating systems for SAP HANA, see SAP Note 2235581 - SAP HANA: Supported Operating Systems.

Hardware Requirements

The supported hardware for SAP HANA depends on the deployment method (appliance or TDI). For more information, see the Related Information in this section and in On-Premise in the SAP HANA Master Guide.

Network Time Protocol (NTP)

We strongly recommend setting up an NTP server for the SAP HANA system landscape.

Note

If an NTP sever is not available, this means for example that trace files from distributed hosts cannot be displayed in the correct chronological order.

Hardware Requirements for SAP HANA Network Connection

For information about hardware requirements for SAP HANA network connections, see SAP HANA Network Requirements.

For installations on IBM Power Servers, Ethernet virtualization using dual VIOS is normally deployed. Natively attached Ethernet cards can also be used however.

Related Information

SUSE Linux Enterprise Server (SLES)

SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System

SAP Note 1855805 - Recommended SLES 11 packages for HANA support on OS level

SAP Note 1824819 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP2

SAP Note 1954788 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP3

SAP Note 2240716 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP4

Red Hat Enterprise Linux (RHEL)

SAP Note 2009879 - SAP HANA Guidelines for Red Hat Enterprise Linux (RHEL) Operating System

SAP Note 2013638 - SAP HANA DB: Recommended OS settings for RHEL 6.5

SAP Note 2136965 - SAP HANA DB: Recommended OS settings for RHEL 6.6

SAP Note 2247020 - SAP HANA DB: Recommended OS settings for RHEL 6.7

SAP Note 2292690 - SAP HANA DB: Recommended OS settings for RHEL 7.2

SLES and RHEL

SAP Note 2001528 - Linux: SAP HANA Database SPS 08 revision 80 (or higher) on RHEL 6 or SLES 11

SAP Note 2228351 – Linux: SAP HANA Database SPS 11 revision 110 (or higher) on RHEL 6 or SLES 11

SAP HANA Network Requirements

Supported Hardware Platforms

SAP Certified and Supported SAP HANA Hardware

SAP Note 1943937 - Hardware Configuration Check Tool - Central Note

SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note

SAP Note 2218464 - Supported products when running SAP HANA on IBM Power Systems

General Links

SAP Training & Education

SAP Note 52505 - Support after end of mainstream/extended maintenance

SAP Note 2235581 - SAP HANA: Supported Operating Systems

Product Availability Matrix

2.4.1 Recommended File System Layout

The SAP HANA database lifecycle manager (HDBLCM) requires certain file systems in order to successfully install an SAP HANA system.

The file systems can be defined manually before installation and then specified during installation, or the default file systems can be used. It is important that the file systems listed below are available and have the recommended disk space before starting the SAP HANA database lifecycle manager.

Table 1: Default File Systems

File System	Default Path	Recommendations
Root	/
Installation path (sapmnt)	/hana/shared/	The mount directory is used for shared files between all hosts in an SAP HANA system. This directory needs to be accessible to each of the servers in the SAP HANA cluster. Subdirectories: ● /hana/shared/<SID> - Contains executable programs (exe), globally shared data (global), instance profiles (profile), and SAP HANA configuration files. ● /hana/shared/<SID>/hdbclient - The SAP HANA client installation path. The following paths apply when the SAP HANA studio is installed: ● /hana/shared/<SID>/hdbstudio_update - The studio repo sitory installation path. The studio repository is used to update the local SAP HANA studio installation. ● /hana/shared/<SID>/hdbstudio - The SAP HANA studio installation path.
System instance	/usr/sap	This is the path to the local SAP system instance directories. It is possible to join this location with the Linux installation. Subdirectories: ● /usr/sap/hostctrl - The SAP host agent directory. ● /usr/sap/<SID> - Contains symbolic links to system executables (SYS) and the home directory (home) of the <sid>adm user.
Data volume	/hana/data/ <SID>	The default path to the data directory depends on the system ID of the SAP HANA host.
Log volume	/hana/log/ <SID>	The default path to the log directory depends on the system ID of the SAP HANA host.

It is strongly recommended to use the SAP HANA file system layout shown in the figure below:

Note

An SAP HANA system in a production environment must not share any infrastructure with another SAP HANA system.

Hosts running more than one SAP HANA system (sometimes referred to as multiple-SID installations) can only be used for non-production purposes such as development, quality assurance, or testing.

The installation path, data path, and log path must not point to the same directory.

As of SAP HANA Support Package Stack (SPS) 11, a SAP HANA system cannot be installed under /usr/sap/<SID>. The directory /usr/sap must not be shared across other hosts.

For production systems with high availability, it is possible to share some temporarily unused resources from the standby hosts. As soon as the standby resources are needed, they must become exclusively available for the production system and no longer shared. For more details, refer to the high availability information in the SAP HANA Administration Guide.

The file systems /hana/data/<SID> and /hana/log/<SID> may use shared file systems like NFS, or block storage using the SAP HANA storage connector API with non-shared file systems. For more details, see Related Information.

The installation path (/hana/shared) is visible on all hosts. By default, the installation path is also used for backup. However, backup directories should be manually configured, and must belong to a shared file system. For more details, refer to the backup information in the SAP HANA Administration Guide.

Related Information

SAP HANA Administration Guide

Multiple-Host System Concepts [page 67]

2.5 SAP HANA and Virtualization

SAP HANA is supported on bare-metal and virtualized platforms.

Note

Some of the virtualization platforms that are available for SAP HANA are only supported in non-production environments. For more information on supported versions, see 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments in Related Information.

VMware vSphere

SAP HANA is supported on VMware vSphere for scale-up, multi-VM and scale-out production environments, including SAP HANA Tailored Datacenter Integration deployments. For more information, see Best Practices and Recommendations for Scale-up Deployments of SAP HANA on VMware vSphere and Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware vSphere in Related Information.

Hitachi LPAR

Hitachi Unified Compute Platform for the SAP HANA Platform with logical partitioning (LPAR) in a scale-up or multi-VM configuration is a pre-configured virtual appliance ready to plug into a network to provide real-time access to operational data for use in analytic models. SAP HANA on Hitachi solutions with logical partitioning are based on a number of bare metal appliance configurations with modifications that are required for running logical partitions (LPARs) in dedicated mode. For more information, see Hitachi Unified Compute Platform for the SAP HANA Platform with Logical Partitioning in a Scale-up Configuration using Hitachi Compute Blade 500 and Hitachi Unified Storage VM in Related Information.

Huawei FusionSphere

SAP HANA is supported for production and non-production use in a virtualized environment using Huawei

FusionSphere. For more information, see Best Practices for Deploying SAP HANA on Huawei FusionSphere Virtualization Platform and Guide for Deploying SAP HANA on Huawei FusionSphere Virtualization in Related Information.

Red Hat Enterprise Linux KVM Hypervisor

SAP HANA is supported on the KVM (Kernel-based Virtual Machine) hypervisor in a non-production environment. For more information, see SAP HANA on KVM: Best Practices Resource Guide in Related Information.

SUSE Linux Enterprise Hypervisor

SAP HANA can be run in virtualized environments using XEN and KVM for virtual single VM deployments for test and development scenarios. Both the XEN and KVM hypervisor are built into SUSE Linux Enterprise Server for SAP Applications. For more information, see SAP Note 2284516 - SAP HANA virtualized on SUSE Linux Enterprise hypervisors in Related Information.

IBM PowerVM

SAP HANA can be deployed on IBM PowerVM for IBM Power Systems. PowerVM is a combination of hardware, PowerVM Hypervisor, and software, which includes other virtualization features, such as the Virtual I/O Server. For more information, see IBM PowerVM Best Practices in Related Information.

Related Information

SAP Note 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments

Best Practices and Recommendations for Scale-up Deployments of SAP HANA on VMware vSphere

Best Practices and Recommendations for Scale-Out Deployments of SAP HANA on VMware vSphere

Hitachi Unified Compute Platform for the SAP HANA Platform with Logical Partitioning in a Scale-up

Configuration using Hitachi Compute Blade 500 and Hitachi Unified Storage VM

Best Practices for Deploying SAP HANA on Huawei FusionSphere Virtualization Platform

Guide for Deploying SAP HANA on Huawei FusionSphere Virtualization

SAP HANA on KVM: Best Practices Resource Guide

SAP Note 2284516 - SAP HANA virtualized on SUSE Linux Enterprise hypervisors

IBM PowerVM Best Practices

SAP HANA Master Guide

3 Using the SAP HANA Platform LCM Tools

The SAP HANA database lifecycle manager (HDBLCM) is used to perform SAP HANA platform lifecycle management (LCM) tasks, including installing, updating, and configuring an SAP HANA system. The SAP HANA database lifecycle manager is designed to accommodate hardware partners and administrators, and so it offers a variety of usage techniques.

The SAP HANA database lifecycle manager is used by means of program interface type, program interaction mode, and parameter entry mode. Before using the SAP HANA database lifecycle manager, you should choose which user interface you prefer to use and how you want to modify the platform LCM task to achieve your desired result. You modify the actions of the platform LCM tools using parameters. Parameters can be modified in a number of ways, for example, in the entry field of a graphical interface, as a call option with the program call, or in a configuration file. These options can be mixed and matched depending on the parameters you need to use and the program interaction mode you choose.

● Performing LCM Tasks by Program Interface [page 29]

● Use the Web User Interface to Perform Platform LCM Tasks [page 34]

● Use the Graphical User Interface to Perform Platform LCM Tasks [page 29]

● Use the Command-Line Interface to Perform Platform LCM Tasks [page 30]

● Performing LCM Tasks by Program Interaction Mode [page 37]

● Use Interactive Mode to Perform Platform LCM Tasks [page 37]

● Use Advanced Interactive Mode to Perform Platform LCM Tasks [page 38]

● Use Batch Mode to Perform Platform LCM Tasks [page 40]

● Performing LCM Tasks by Parameter Entry Method [page 42]

● Entering Platform LCM Parameters Interactively [page 43]

● Entering Platform LCM Parameters as Call Options from the Command Line [page 45]

● Use LCM Configuration Files to Enter Parameters [page 43]

The first choice to make is which SAP HANA database lifecycle manager (HDBLCM) interface type you prefer to use. The SAP HANA HDBLCM program can be run as a graphical user interface, a command-line interface, or as Web user interface in a Web browser or from the SAP HANA studio (the Web user interface is not available for all platform LCM tasks).

Once you've chosen the graphical user, command-line, or Web user interface, you can decide if you prefer to interactively enter parameter values, or give all required parameters with the call to the platform LCM tool, and let it run unattended to completion. Interactive mode is available for all user interfaces, and is the default mode for program interaction. To use interactive mode, you simply call the SAP HANA HDBLCM user interface, and enter parameter values as they are requested by the program. Advanced interactive mode involves entering some parameter values interactively and providing some parameter values as call options or in a configuration file. This is the recommended interaction mode if you'd like to modify parameter default values which are not requested in interactive mode. Batch mode is an advanced platform LCM interaction method because all required parameters must be provided with the call to the LCM program on the command line. Batch mode is designed for large-scale platform LCM tasks, which would be time consuming to perform interactively.

Platform LCM parameters can be entered interactively (only available for interactive mode or advanced interactive mode), as a call option on the command line, or via a configuration file. If you are performing platform LCM tasks in advanced interactive mode, you can choose any of the three parameter entry methods (or use more than one). If you are using batch mode, you must enter parameter values either as call options to the SAP HANA database lifecycle manager or from a configuration file. The syntax for the parameters as call options can be found in the Parameter Reference. The configuration file is generated as a blank template, then edited, and called as a call option.

3.1 Choosing the Correct SAP HANA HDBLCM for Your Task

It is important to distinguish between the version of the SAP HANA database lifecycle manager (HDBLCM) that is available on the installation medium and the version that is unpacked during installation, and subsequently used to perform administration and configuration tasks after the SAP HANA system has been installed.

The SAP HANA database lifecycle manager is available in two varieties - an installation medium version to perform installation and update, and a resident version for update and configuration that is unpacked on the SAP HANA host during installation or update. The SAP HANA resident HDBLCM has been designed to be version-compatible. That means, every time you install or update an SAP HANA system, you can be sure that any subsequent configuration tasks performed with the SAP HANA database lifecycle manager will work as expected because the installation or update tool and the configuration tool are of the same version and have been tested together. The SAP HANA resident HDBLCM is located at <sapmnt>/<SID>/hdblcm.

3.2 Performing LCM Tasks by Program Interface

SAP HANA platform lifecycle management tasks can be performed from a graphical, command-line and Web user interface.

Related Information

Use the Graphical User Interface to Perform Platform LCM Tasks [page 29]

Use the Command-Line Interface to Perform Platform LCM Tasks [page 30]

Using the Web User Interface [page 32]

3.2.1 Use the Graphical User Interface to Perform Platform LCM Tasks

SAP HANA platform lifecycle management tasks can be performed from a graphical interface.

Procedure

1. Change to the directory where the SAP HANA database lifecycle manager is located:

Option	Description
Installation Medium (Intel-Based Hardware Platforms)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_X86_64

Installation Medium (IBM Power Systems)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_PPC64

SAP HANA resident HDBLCM
	cd <sapmnt>/<SID>/hdblcm

In general, installation and update is carried out from the installation medium. Configuration tasks are performed using the SAP HANA resident HDBLCM. For more information about the two SAP HANA database lifecycle manager types, see Related Information.

2. Start the SAP HANA platform lifecycle management tool:

./hdblcmgui

3. Enter parameter values in the requested fields. In addition, you can specify parameter key-value pairs as call options or in the configuration file template.

Note

If parameter key-value pairs are specified as command-line options, they override the corresponding parameters in the configuration file. Parameters in the configuration file override default settings.

Order of parameter precedence:

Command Line > Configuration File > Default

For more information about program interaction modes and parameter values entry methods, see Related Information.

Related Information

Choosing the Correct SAP HANA HDBLCM for Your Task [page 28]

Entering Platform LCM Parameters as Call Options from the Command Line [page 45]

3.2.2 Use the Command-Line Interface to Perform Platform LCM Tasks

SAP HANA platform lifecycle management tasks can be performed from the command line.

Procedure

1. Change to the directory where the SAP HANA database lifecycle manager is located:

Option	Description
Installation Medium (Intel-Based Hardware Platforms)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_X86_64

Installation Medium (IBM Power Systems)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_PPC64

SAP HANA resident HDBLCM
	cd <sapmnt>/<SID>/hdblcm

2. Start the SAP HANA platform lifecycle management tool:

./hdblcm

3. Enter parameter values in one of the following ways.

○ Interactive parameter entry - If you call the SAP HANA platform LCM tool only, the program runs in interactive mode. Parameter default values are suggested in brackets, and can be accepted with Enter. Otherwise, enter a non-default value, then select Enter.

○ Command-line parameter entry as call options - If you enter parameter key-value pairs as call options with the call to the SAP HANA platform LCM tool, the program runs in interactive mode and requests values for any parameter values which you didn't specify in the original input. If you entered the batch mode call option, the program runs to completion without any further requests, unless a mandatory parameter was left out of the original input, in which case, the program fails to perform the platform LCM task.

○ Configuration file parameter entry - If you enter parameter key-value pairs in the configuration file template, and enter the configuration file path as a call option with the call to the SAP HANA platform LCM tool, the program runs in interactive mode and requests values for any parameter values which you didn't specify in the original input. If you entered the batch mode call option, the program runs to completion without any further requests, unless a mandatory parameter was left out of the original input, in which case, the program fails to perform the platform LCM task.

Note

Order of parameter precedence:

Command Line > Configuration File > Default

For more information about program interaction modes and parameter values entry methods, see Related Information.

Related Information

Choosing the Correct SAP HANA HDBLCM for Your Task [page 28]

Performing LCM Tasks by Parameter Entry Method [page 42]

Performing LCM Tasks by Program Interaction Mode [page 37]

Entering Platform LCM Parameters as Call Options from the Command Line [page 45]

3.2.3 Using the Web User Interface

SAP HANA platform lifecycle management tasks can be performed using the SAP HANA database lifecycle manager (HDBLCM) Web user interface.

Related Information

About the Web User Interface [page 32]

Use the Web User Interface to Perform Platform LCM Tasks [page 34]

Log Off From an SAP HANA System [page 36]

Troubleshooting the Web User Interface [page 37]

3.2.3.1 About the Web User Interface

The SAP HANA database lifecycle manager (HDBLCM) Web user interface is hosted by the SAP Host Agent, which is installed on the SAP HANA host. When installing or updating the SAP HANA system, as part of the SAP HANA resident HDBLCM configuration, the SAP HANA system deploys its artifacts on the SAP Host Agent, thus enabling the Web user interface.

All Web user interface actions are always performed in the context of an already installed and registered SAP HANA system. In order to access the SAP HANA database lifecycle manager Web user interface you need to log on as the system administrator user <sid>adm.

The communication between the Web browser and the SAP Host Agent is always done over HTTPS, which requires that the SAP Host Agent has a secure sockets layer (SSL) certificate (PSE) in its security directory. For more information about SSL certificate handling, see Related Information.

The backend is provided by the special executable hdblcmweb, which is started automatically by the SAP Host Agent as soon as an action is triggered from the Web user interface and terminates after the action completes.

Note

You should never start hdblcmweb manually. For security reasons, hdblcmweb is always started with system administrator user <sid>adm privileges. If you require logging with individual users (to ensure personalized logging), use the SAP HANA database lifecycle manager graphical user or command-line interface.

Note

Make sure that the system administrator user <sid>adm has permissions to read the paths, passed as parameters in the Web user interface (for example, the SAP HANA database installation kit or locations with SAP HANA components).

One platform LCM task, which is worth special attention is the update of the SAP HANA system and components. The SAP HANA system updates are always performed by the installation kit SAP HANA database lifecycle manager in the graphical user and command-line interfaces, (and not the SAP HANA resident HDBLCM). This is because the SAP HANA database lifecycle manager, in the graphical user and command-line interfaces, is not forward compatible. Meaning that only the new version of the tool knows how to update an older system.

On the other hand, all scenarios in the Web user interface are handled by the SAP HANA resident HDBLCM, which is part of the system. For this reason, as a first step before even starting the update process, you are required to enter a location of an SAP HANA database installation kit. After detecting the kit, the update Web user interface is loaded from the installation kit and the installation kit SAP HANA database lifecycle manager starts serving as backend until the update process finishes. It is as if you start the SAP HANA database lifecycle manager directly from the installation kit in graphical user or command-line interface.

Related Information

Secure Sockets Layer (SSL) Certificate Handling [page 48]

3.2.3.2 Use the Web User Interface to Perform Platform LCM Tasks

The SAP HANA database lifecycle manager (HDBLCM) can be accessed as a Web user interface in either a standalone browser or in the Platform Lifecycle Management view within the SAP HANA studio.

Prerequisites

You should verify that the following prerequisites are fulfilled before trying to access the SAP HANA database lifecycle manager from a Web browser.

● The communication port 1129 is open.

Port 1129 is required for the SSL communication with the SAP Host Agent in a standalone browser via HTTPS.

● The following Web browser requirements are fulfilled: ○ Microsoft Windows

○ Internet Explorer - Version 9 or higher

If you are running Internet Explorer version 9, make sure that your browser is not running in compatibility mode with your SAP HANA host. You can check this in your browser by choosing

Tools Compatibility View Settings

○ Mozilla Firefox - Latest version and Extended Support Release

○ Google Chrome - Latest version

○ SUSE Linux - Mozilla Firefox with XULRunner 10.0.4 ESR

○ Mac OS - Safari 5.1 or higher

Note

For more information about supported Web browsers for the SAP HANA database lifecycle manager Web interface, see the browser support for sap.m library in the SAPUI5 Developer Guide in Related Information.

● You are logged on as the system administrator user <sid>adm.

You should verify that the following additional prerequisites are fulfilled before trying to access the SAP HANA database lifecycle manager from the SAP HANA studio.

● The SAP HANA studio revision is 120 or higher.

● For Linux:

○ The system property org.eclipse.swt.browser.XULRunnerPath should be set in hdbstudio.ini to point to the path of XULRunner, for example:

-Dorg.eclipse.swt.browser.XULRunnerPath=<path to xulrunner>.

This hdbstudio.ini file is located in the same folder as the executable that is used to start the SAP HANA studio. For Linux, the default location is hana/shared/<SID>/hdbstudio..

Context

The Web user interface supports only the following SAP HANA platform lifecycle management tasks:

● View system information

● Update system and components

● Install or update additional components

● Configure System Landscape Directory (SLD) registration

● Configure inter-service communication

When performing installation and update tasks, various parameters can be set in the Advanced Parameters Configuration dialog. To access the Advanced Parameters Configuration dialog, click on the gear icon in the footer bar of the SAP HANA HDBLCM Web user interface.

Procedure

Access the SAP HANA HDBLCM Web user interface.

Option	Description
Web Browser	Enter the SAP HANA database lifecycle manager (HDBLCM) URL in an HTML5-enabled browser: https://<hostname>:1129/lmsl/HDBLCM/<SID>/index.html
		Note The URL is case sensitive. Make sure you enter upper and lower case letters correctly.

SAP HANA Studio	1. Start the SAP HANA studio. 2. In the SAP HANA studio, add the SAP HANA system. 3. Open the context menu (right-mouse click) in the Systems view, and select Add System. For more information about adding a system, see Add an SAP HANA System in the SAP HANA Administration Guide in Related Information. 4. In the SAP HANA studio, log on to the system. 5. From the context menu of the selected system, select Lifecycle Management Platform Lifecycle Management SAP HANA Platform Lifecycle Management .
SAP HANA Cockpit	1. Enter the SAP HANA cockpit URL in your browser. The URL depends on whether you are connecting to a single-container system or to a database in a multiple-container system. A single-container system is accessed through the URL: http://<host_FQDN>: 80<instance>/sap/hana/admin/cockpit For more information about the URLs in multiple-container systems, see Configure HTTP Access to Multitenant Database Containers in the SAP HANA Administration Guide in Related Information.
			Note FQDN = fully qualified domain name

Option	Description
	2. The SAP HANA Platform Lifecycle Management tiles are visible on the homepage of the SAP HANA cockpit. If they are not, you can add them from the SAP HANA Platform Lifecycle Management tile catalog. For more information, see Customizing the Homepage of SAP HANA Cockpit.

Results

The SAP HANA database lifecycle manager is displayed as a Web user interface in either a standalone browser or in the SAP HANA studio.

Related Information

SAPUI5 Developer Guide

SAP HANA Administration Guide

3.2.3.3 Log Off From an SAP HANA System

In the SAP HANA database lifecycle manager (HDBLCM) Web user interface, you can log off from an SAP HANA system and close all connections to the system. To be able to connect to system again, you must log on.

Procedure

● To log off from a system click the Log out button. All open connections to the system are closed.

Note

Currently, this feature is not available for browsers on mobile devices.

3.2.3.4 Troubleshooting the Web User Interface

If you have problems with the Web user interface, see SAP Note 2078425 for steps you can take to troubleshoot and resolve them.

Note

The Web browser used to render the platform lifecycle management Web user interface in the SAP HANA studio cannot be changed via

Windows

Preferences

General

Web Browser

Related Information

SAP Note 2078425 - Troubleshooting note for SAP HANA Platform Management tool hdblcm

3.3 Performing LCM Tasks by Program Interaction Mode

SAP HANA platform lifecycle management tasks can be performed in interactive mode, advanced interactive mode and batch mode.

Related Information

Use Interactive Mode to Perform Platform LCM Tasks [page 37]

Use Advanced Interactive Mode to Perform Platform LCM Tasks [page 38]

Use Batch Mode to Perform Platform LCM Tasks [page 40]

3.3.1 Use Interactive Mode to Perform Platform LCM Tasks

Context

To access the SAP HANA database lifecycle manager Web user interface, see Related Information.

Procedure

1. Change to the directory where the SAP HANA database lifecycle manager is located:

Option	Description
Installation Medium (Intel-Based Hardware Platforms)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_X86_64

Installation Medium (IBM Power Systems)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_PPC64

SAP HANA resident HDBLCM
	cd <sapmnt>/<SID>/hdblcm

2. Start the SAP HANA platform lifecycle management tool:

Option	Description
Graphical Interface
	./hdblcmgui

Command-line Interface
	./hdblcm

To start the SAP HANA platform LCM tools in interactive mode, simply do not enter the parameter for batch mode (--batch or -b) as a call option. You can enter any other required parameters as call options or load a configuration file. The program runs in interactive mode and requests any missing parameters values, which must be verified or changed. You are provided with a summary of parameter values, which you can accept to run the program to completion, or reject to exit the program.

Related Information

Choosing the Correct SAP HANA HDBLCM for Your Task [page 28]

Use the Web User Interface to Perform Platform LCM Tasks [page 34]

3.3.2 Use Advanced Interactive Mode to Perform Platform LCM Tasks

Interactive mode is a method for running SAP HANA platform lifecycle management (LCM) tools which starts the program and requires you to enter parameter values successively before the program is run. If you would like to perfom platform LCM tasks in interactive mode, but would like to enter call options not available in interactive mode, or make use of the configuration file, you can use a combination of interactive mode and advanced parameter entry methods.

Context

The SAP HANA platform LCM tools offer a wide variety of parameters which can modify the platform LCM task you are performing. Some parameters can be modified in interactive mode when the graphical user, command-line, or Web user interface requests a value for a given parameter. However, some parameters are not available in interactive mode, and must be specified either as a call option with the call to the platform LCM tool, or from within a configuration file.

Procedure

1. Review which parameters are offered in interactive mode.

If the parameter you want to configure is not available in interactive mode, you have two options. You can either enter the parameter key-value pair as a call option with the call to the platform LCM tool. Alternatively, you can generate a configuration file template, and edit the parameters value in the configuration file. Then call the configuration file as a call option with the call to the platform LCM tool.

Using the configuration file for interactive mode is recommended if you plan to perform the exact same platform LCM task multiple times.

2. Change to the directory where the SAP HANA database lifecycle manager is located:

Option	Description
Installation Medium (Intel-Based Hardware Platforms)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_X86_64

Installation Medium (IBM Power Systems)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_PPC64

SAP HANA resident HDBLCM
	cd <sapmnt>/<SID>/hdblcm

3. If you plan to use a configuration file, prepare it with the following steps:

a. Generate the configuration file template using the SAP HANA platform lifecycle management tool:

Run the SAP HANA platform LCM tool using the parameter dump_configfile_template as a call option. Specify an action and a file path for the template. A configuration file template and a password file template are created.

./hdblcm --action=<LCM action> --dump_configfile_template=<file path>

b. Edit the configuration file parameters. Save the file.

c. Edit the password file. Save the file.

4. Start the SAP HANA platform lifecycle management tool:

Start the SAP HANA database lifecycle manager in either the graphical user interface or in the commandline interface, with a call option:

./hdblcmgui --<parameter key>=<parameter value>

./hdblcm --<parameter key>=<parameter value>

If you are using a configuration file, you must you the call option --configfile=<file path>.

Related Information

Choosing the Correct SAP HANA HDBLCM for Your Task [page 28]

3.3.3 Use Batch Mode to Perform Platform LCM Tasks

Batch mode is a method for running SAP HANA platform lifecycle management (LCM) tools which starts the program and runs it to completion without requiring you to interacte with it any further. Batch mode must be run with the SAP HANA platform LCM command-line tools. All required parameter values must be passed as call options or from a configuration file.

Prerequisites

● When using batch mode, passwords must either be defined in the configuration file, or passed to the installer using an XML password file and streamed in via standard input. In both cases, it is necessary to prepare the passwords. For more information, see Specifying Passwords.

Context

If you are new to performing the desired SAP HANA platform LCM task in batch mode, it is recommended to run some tests before using batch mode in a production environment.

Procedure

1. Change to the directory where the SAP HANA database lifecycle manager is located:

Option	Description
Installation Medium (Intel-Based Hardware Platforms)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_X86_64

Installation Medium (IBM Power Systems)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_PPC64

SAP HANA resident HDBLCM
	cd <sapmnt>/<SID>/hdblcm

2. Start the SAP HANA platform lifecycle management tool:

./hdblcm --batch <additional parameters>

./hdblcm -b <additional parameters>

It is mandatory to provide an SAP HANA system ID (SID) and user passwords during installation. In batch mode, you are restricted to providing these parameter values as call options on the command line (for passwords, by means of an XML file) or in a configuration file. If you don't provide parameter values for the other required parameters, you implicitly accept the default values.

Example

The following example installs the SAP HANA server and client as a single-host system. The SAP system ID and instance number are also specified from the command line. The system passwords are read from a standard input stream by the installer. All other parameter defaults are automatically accepted and no other input is requested in order to complete the installation.

cat ~/hdb_passwords.xml | ./hdblcm --batch --action=install --

components=client,server --sid=DB1 --number=42 --read_password_from_stdin=xml

If a configuration file is used in combination with batch mode, an identical system can be installed with a simplified call from the command line. In the following example, passwords are defined in the configuration file, in addition to the action, components, SAP system ID, and instance number.

./hdblcm --batch --configfile=/var/tmp/H01_configfile

Related Information

Specifying Passwords [page 60] read_password_from_stdin [page 210] sid [page 213]

Use LCM Configuration Files to Enter Parameters [page 43]

Entering Platform LCM Parameters as Call Options from the Command Line [page 45]

3.4 Performing LCM Tasks by Parameter Entry Method

SAP HANA platform lifecycle management (LCM) parameter values can be entered in a variety of methods: interactively by iteratively providing values in either the graphical interface of command prompt, as commandline options with the call to the platform LCM tool, or in a configuration file.

SAP HANA platform lifecycle management parameter values allow you to customize your SAP HANA installation, update, or configuration. Parameter values can be entered by one or more of the following methods:

	Interactively (Default)	Using either command line interface or graphical interface, most parameters are requested interactively. Default parameter values are proposed in brackets and can be changed or confirmed. Parameters that are not requested (or specified via another method) accept the default value.
	Command Line Options	Parameters are given in their accepted syntax as a space delimited list after the program call (for example, hdblcm or hdblcmgui). The specified parameters replace the defaults. If any mandatory parameters are excluded, they are requested interactively (unless batch mode is specified). All parameters can be entered from the command line. For more details about the accepted parameter syntax, see the inline help output (--help) for the individual SAP HANA lifecycle management tool.
	Configuration File	The configuration file is a plain text file, for which a template of parameter key-value pairs can be generated, edited, and saved to be called in combination with the program call. If any mandatory parameters are not specified, they are requested interactively (unless batch mode is used). All parameters can be entered in the configuration file. For more information about the configuration file, see Related Information.
Note If parameters are specified in the command line, they override the corresponding parameters in the configuration file. Parameters in the configuration file override default settings. Order of parameter precedence: Command Line > Configuration File > Default

Related Information

Entering Platform LCM Parameters Interactively [page 43] Use LCM Configuration Files to Enter Parameters [page 43]

Entering Platform LCM Parameters as Call Options from the Command Line [page 45]

3.4.1 Entering Platform LCM Parameters Interactively

SAP HANA platform LCM interactive mode is default interaction mode for all platform LCM programs and interfaces.

You can run the graphical, command-line, or Web user interface in interactive mode by simply starting the program, and entering parameter values as they are requested by the program. In interactive mode, parameter default values are suggested in brackets and can be accepted with Enter .

Not all parameters are requested in interactive mode. If you would like to configure a parameter not offered in interactive mode, you must enter it as a call option with the call to the platform LCM program, or use corresponding configuration file for the platform LCM task.

3.4.2 Use LCM Configuration Files to Enter Parameters

By defining a prepared configuration file during installation, specified parameter values are used by the SAP HANA platform lifecycle management (LCM) tools to build a customized SAP HANA system.

Context

The configuration file is a plain text file of specified parameters, written in the same syntax as in the command line (except without the leading two dashes --). A configuration file template can be generated, edited, and saved to be called with the call to the SAP HANA database lifecycle manager (HDBLCM).

The configuration file template provides a brief, commented-out summary of each parameter. Each parameter is set to its default value.

Procedure

1. Change to the directory where the SAP HANA database lifecycle manager is located:

Option	Description
Installation Medium (Intel-Based Hardware Platforms)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_X86_64

Installation Medium (IBM Power Systems)
	cd <installation medium>/DATA_UNITS/ HDB_LCM_LINUX_PPC64

SAP HANA resident HDBLCM
	cd <sapmnt>/<SID>/hdblcm

2. Generate the configuration file template using the SAP HANA platform lifecycle management tool:

./hdblcm --action=<LCM action> --dump_configfile_template=<file path>

3. Edit the configuration file parameters. Save the file.

It is recommended that at least the SAP system ID (sid) and the instance number (number) are uniquely defined. There are several required parameters, that are provided default values in case they are not customized. For more information, refer to the default values.

Some file path parameters have automatic substitution values as part of the default file path, using the sid (SAP HANA system ID) and sapmnt (installation path) parameters, so that the substituted values create file paths that are unique and system-specific. For example, the default for the data file path is: datapath=/hana/data/${sid}, where sid is automatically replaced by the unique SAP HANA system ID.

4. Start the SAP HANA platform lifecycle management tool:

Run the SAP HANA platform LCM tool using the parameter configfile as a call option. Specify the file path of the edited template.

./hdblcm --configfile=<file path>

You can specify the path to a directory in which custom configuration files are saved using the parameter custom_cfg as a call option.

Related Information

configfile [page 191] custom_cfg [page 192]

Choosing the Correct SAP HANA HDBLCM for Your Task [page 28]

3.4.3 Entering Platform LCM Parameters as Call Options from the Command Line

Call options are available for every SAP HANA platform LCM program.

You can use call options for a number of reasons:

● The parameter is not available in interactive mode, but can be entered as a call option.

● You are using batch mode.

● You are using a configuration file, but would like to override a parameter in the configuration file with a new value.

● You are installing an SAP HANA multiple-host system from the command line.

A call option is entered with the following notation:

./<program call> --<parameter1 key>=<parameter1 value> --<parameter2 key>=<parameter2 value>

Call options start with a double dash (--) if they are written in long-form syntax. Some parameters also have short-form syntax, in which they are preceded with a single dash (-). For more information about call option syntax, see the Parameter Reference topics.

Related Information

Parameter Reference [page 180]

SAP HANA Server Installation and Update Guide

3.5 Executing Platform LCM Tasks

SAP HANA platform lifecycle management tasks can be performed on multiple-host systems centrally, by running the SAP HANA database lifecycle manager (HDBLCM) from any worker host and using remote execution to replicate the call on all remaining system hosts. Otherwise, the platform LCM tasks can be executed first on a worker host, and then re-executed manually on each remaining host. This method is considered decentralized execution.

The following is an example of an SAP HANA system update performed centrally and decentrally.

Related Information

Centralized Execution of Platform LCM Tasks [page 46]

Decentralized Execution of Platform LCM Tasks [page 51]

3.5.1 Centralized Execution of Platform LCM Tasks

SAP HANA platform lifecycle management (LCM) tasks can be performed centrally on multiple-host SAP HANA systems in a number of ways depending on the available certificate keys and the remote execution configuration.

3.5.1.1 Using Secure Shell (SSH) to Execute Platform LCM Tasks

An SAP HANA system must be installed with root user credentials. During installation a secure shell (SSH) key is configured so that future platform LCM tasks can be performed remotely on multiple-host SAP HANA systems without requiring the root user password.

By default, the SAP HANA database lifecycle manager (HDBLCM) uses SSH during SAP HANA system installation or update install the SAP Host Agent on all system hosts. In order to use SSH, the SFTP subsystem must be active. Once the SAP Host Agent is installed, it is used to perform any platform LCM tasks executed from the Web user interface or as the system administrator user <sid>adm.

Note

Platform LCM tasks cannot be executed remotely via SSH as the system administrator user <sid>adm.

Related Information

1944799 - SAP HANA Guidelines for SLES Operating System Installation

2009879 - SAP HANA Guidelines for Red Hat Enterprise Linux (RHEL) Operating System

3.5.1.2 Using SAP Host Agent to Execute Platform LCM Tasks

In previous SAP HANA releases, it was only possible to perform multiple-host system tasks by providing root credentials and executing platform on remote hosts via secure shell (SSH). Since SAP HANA Support Package Stack (SPS) 09, it has been possible to perform platform LCM tasks without root credentials by using the SAP Host Agent.

Even though the SAP Host Agent is not required to be installed on the SAP HANA system, the SAP HANA database lifecycle manager (HDBLCM) heavily relies on it for the following functionality to work:

● Execution as the system administrator user <sid>adm

● Connectivity to remote hosts via HTTPS (when no SSH or root user credentials are available)

● Execution from the SAP HANA database lifecycle manager Web user interface

Note

The SAP HANA cockpit for offline administration also uses the SAP Host Agent to execute tasks as the system administrator user <sid>adm, for example, stopping and starting the system, or troubleshooting a system experiencing performance problems. For more information, see SAP HANA Cockpit for Offline Administration.

The SAP Host Agent is installed and updated by default during SAP HANA system installation and update, unless the call option --install_hostagent=off is used. We recommend installing and updating the SAP Host Agent with the SAP HANA server to ensure version compatibility, however in some cases you may need to install or update only the SAP Host Agent. For information about installing or updating the SAP Host Agent individually, see Installing SAP Host Agent Manually and Upgrading SAP Host Agent Manually in Related Information.

If execution on the remote hosts is done via SSH (default, --remote_execution=ssh), the SAP HANA database lifecycle manager is able to connect to a remote host via SSH and install and configure the SAP Host

Agent. In contrast, the remote execution via SAP Host Agent (--remote_execution=saphostagent) requires that the SAP Host Agent is installed and configured on all involved hosts in advance, which includes: ● Install SAP Host Agent

● Configure a Secure Sockets Layer (SSL) certificate for the SAP Host Agent, so that the HTTPS port 1129 is accessible. For more information about SSL configuration for the SAP Host Agent, see Related

Information. If you don’t want to configure HTTPS, it is also possible to use the call option --use_http. It tells the SAP HANA database lifecycle manager to communicate with the SAP Host Agent via HTTP. During addition of new host to an SAP HANA system (also during installation of a multiple-host system), the HTTPS of the SAP Host Agent is automatically configured by the SAP HANA database lifecycle manager.

Caution

Use the call option --use_http with caution, because passwords are also transferred in plain text via HTTP.

Related Information

Installing SAP Host Agent Manually

Updating SAP Host Agent Manually

SSL Configuration for the SAP Host Agent

3.5.1.2.1 Secure Sockets Layer (SSL) Certificate Handling

To enable secure communication with the SAP Host Agent over HTTPS, the SAP Host Agent needs a secure sockets layer (SSL) certificate in its security directory. This certificate is also used by the SAP HANA database lifecycle manager (HDBLCM) Web-based user interface and the SAP HANA cockpit for offline administration because the Web pages are served by the SAP Host Agent.

The SAP HANA database lifecycle manager handles certificate management during system installation, update, or rename, as well as during the addition of new hosts as follows:

● If there is no certificate in the SAP Host Agent security directory, the SAP HANA database lifecycle manager generates one. The SAP HANA host name is used as the default certificate owner. The certificate owner can be changed by using the call option --certificates_hostmap.

● If there is an existing certificate, the following applies:

○ If the certificate host name is not passed to the SAP HANA database lifecycle manager, or if the certificate host name is the same as the owner of the current certificate, the current certificate is preserved.

○ If the certificate host name is passed via the call option --certificates_hostmap and it differs from the owner of the current certificate, a new certificate is generated.

○ During update of an SAP HANA system, if the certificates on all hosts are in place, the call option -certificates_hostmap is ignored and the current certificates are preserved.

If you want to use your own SSL certificates, see the SAP Host Agent documentation in Related Information.

Related Information

certificates_hostmap [page 187]

SAP HANA Server Installation and Update Guide

SSL Configuration for the SAP Host Agent

3.5.1.2.2 Starting Platform LCM Tasks as the System Administrator User <sid>adm

When starting platform LCM tasks as the system administrator user <sid>adm, the SAP HANA database lifecycle manager (HDBLCM) requires the usage of SAP Host Agent for execution of remote and local operations.

The following tasks in the SAP HANA database lifecycle manager can be performed as the system administrator user <sid>adm:

● System update from the installation medium

● Installation or update of additional components from the SAP HANA resident HDBLCM

● Host addition and host removal

● System Landscape Directory (SLD) registration configuration

● Inter-service communication configuration

Note

Saturday, April 15, 2017

SAP Hana Installation Server (to HTML)

Content

1 SAP HANA Installation and Update Overview

Related Information

1.1 SAP HANA Platform Software Components

1.2 Software Download

Installation Media and Components for SAP HANA

Installation Media for an SAP HANA SPS

Support Packages and Patches for SAP HANA

Responsibilities

Related Information

2 Concepts and Requirements for an SAP HANA System

2.1 SAP HANA System Concepts

Related Information

2.2 SAP HANA System Types

2.3 SAP HANA Deployment Types

Related Information

2.4 SAP HANA Hardware and Software Requirements

Software Requirements

Supported Hardware Platforms

Supported Operating Systems for SAP HANA

Hardware Requirements

Network Time Protocol (NTP)

Hardware Requirements for SAP HANA Network Connection

Related Information

2.4.1 Recommended File System Layout

Related Information

2.5 SAP HANA and Virtualization

VMware vSphere

Hitachi LPAR

Huawei FusionSphere

Red Hat Enterprise Linux KVM Hypervisor

SUSE Linux Enterprise Hypervisor

IBM PowerVM

Related Information

3 Using the SAP HANA Platform LCM Tools

3.1 Choosing the Correct SAP HANA HDBLCM for Your Task

3.2 Performing LCM Tasks by Program Interface

Related Information

3.2.1 Use the Graphical User Interface to Perform Platform LCM Tasks

Procedure

Related Information

3.2.2 Use the Command-Line Interface to Perform Platform LCM Tasks

Procedure

Related Information

3.2.3 Using the Web User Interface

Related Information

3.2.3.1 About the Web User Interface

3.2.3.2 Use the Web User Interface to Perform Platform LCM Tasks

Prerequisites

Context

Procedure

Results

Related Information

3.2.3.3 Log Off From an SAP HANA System

Procedure

3.2.3.4 Troubleshooting the Web User Interface

Related Information

3.3 Performing LCM Tasks by Program Interaction Mode

Related Information

3.3.1 Use Interactive Mode to Perform Platform LCM Tasks

Procedure

Related Information

3.3.2 Use Advanced Interactive Mode to Perform Platform LCM Tasks

Context

Procedure

3.3.3 Use Batch Mode to Perform Platform LCM Tasks

Prerequisites

Context

Procedure

Related Information

3.4 Performing LCM Tasks by Parameter Entry Method

Related Information

3.4.1 Entering Platform LCM Parameters Interactively

3.4.2 Use LCM Configuration Files to Enter Parameters

Context

Procedure

Related Information

3.4.3 Entering Platform LCM Parameters as Call Options from the Command Line