sap hana administration guide en

PUBLICSAP HANA Platform SPS 08Document Version: 1.1 - 2014-08-21

SAP HANA Administration Guide

Table of Contents1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 The SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1.1 Open the SAP HANA Administration Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1.2 Execute SQL Statements in the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1.3 Authorization for Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.1.4 SAP HANA Studio Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

2 System Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252.1 Managing SAP HANA Systems in the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

2.1.1 Systems View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.1.2 Add an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1.3 Add an SAP HANA System with a Different User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.1.4 Link a Centrally-Stored Archive of SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . 332.1.5 Log Off From/Log On To an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.1.6 Disable Password Storage in Eclipse Secure Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362.1.7 Organize the Systems View Using Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372.1.8 Search for SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.1.9 Export a List of SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.1.10 Import a List of SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392.1.11 Disable Default Filtering of Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.1.12 Start the SAP HANA Studio with Immediate System Logon. . . . . . . . . . . . . . . . . . . . . . . 402.1.13 Configure SSL for SAP HANA Studio Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2.2 Starting and Stopping SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.2.1 Start a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.2.2 Stop a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442.2.3 Restart a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.2.4 Stop and Start a Database Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.2.5 Monitoring SAP HANA Systems During Stop and Start. . . . . . . . . . . . . . . . . . . . . . . . . . 49

2.3 Configuring SAP HANA System Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.3.1 Change a System Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512.3.2 Reset a System Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522.3.3 Change the Global Memory Allocation Limit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.3.4 Configure Trace File Rotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .542.3.5 Reserve Connections for Administrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .552.3.6 Configure System Usage Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562.3.7 Change the Default SLD Data Supplier Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

2.4 Managing SAP HANA Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.4.1 License Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.4.2 Check the Current License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

2P U B L I C 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Administration GuideTable of Contents

2.4.3 Install a Permanent License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.4.4 Delete an Existing Permanent License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2.5 Monitoring SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.5.1 System Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642.5.2 Monitoring Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.5.3 Administration Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.5.4 Monitoring System Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .692.5.5 Monitoring Overall System Status and Resource Usage. . . . . . . . . . . . . . . . . . . . . . . . . . 712.5.6 Monitoring Status and Resource Usage of System Components. . . . . . . . . . . . . . . . . . . . 732.5.7 Monitoring Host Status and Auto-Failover Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 762.5.8 Monitoring Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812.5.9 Monitoring System Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892.5.10 Monitoring Disk Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992.5.11 Monitoring Memory Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1052.5.12 Monitoring Using System Views and Historical Data Tables. . . . . . . . . . . . . . . . . . . . . . . 1172.5.13 Use User-Defined SQL Statements for System Monitoring. . . . . . . . . . . . . . . . . . . . . . . 1192.5.14 Analyze Resource Utilization Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212.5.15 Basic Monitoring Checklist for SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

2.6 Managing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1272.6.1 Column-Based and Row-Based Storage in the SAP HANA Database. . . . . . . . . . . . . . . . 1272.6.2 Memory Management in the Column Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312.6.3 The Delta Merge Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1362.6.4 Data Compression in the Column Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1472.6.5 Opening Tables and Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1512.6.6 Viewing Options for Tables and Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522.6.7 Export Tables and Other Catalog Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1562.6.8 Import Tables and Other Catalog Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582.6.9 Import ESRI Shapefiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602.6.10 Table Partitioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1622.6.11 Table Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1812.6.12 Table Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1842.6.13 Table Consistency Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1882.6.14 Catalog Consistency Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

2.7 Hardware Checks for Tailored Data Center Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1912.7.1 Install the SAP HANA HW Configuration Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1922.7.2 Using the SAP HANA HW Configuration Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932.7.3 Run the HW Configuration Check Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

2.8 Configuring an SAP HANA System and Components After Installation. . . . . . . . . . . . . . . . . . . . . 2022.8.1 About the SAP HANA Lifecycle Management Tool Set. . . . . . . . . . . . . . . . . . . . . . . . . . 2022.8.2 Configuring the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2222.8.3 Changing the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251


P U B L I C 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

2.8.4 Managing SAP HANA System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2722.9 SAP Solution Manager for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

2.9.1 Integrating SAP HANA Administration with SAP Solution Manager. . . . . . . . . . . . . . . . . 2792.10 Getting Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

2.10.1 Diagnosis Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2802.10.2 Configure Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2822.10.3 Collecting Diagnosis Information for SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2922.10.4 Troubleshooting an Inaccessible or Unresponsive SAP HANA System . . . . . . . . . . . . . . 3002.10.5 Problem Analysis Using hdbcons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3012.10.6 Open a Support Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

3 Security Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3033.1 Managing SAP HANA Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303

3.1.1 Database Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3033.1.2 Operating System User adm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3073.1.3 User Authentication and Single-Sign On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3073.1.4 User Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3243.1.5 Provisioning Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

3.2 Auditing Activity in SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3603.2.1 Activate and Configure Auditing for an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . 3613.2.2 Create an Audit Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3623.2.3 Delete Audit Entries from the Audit Trail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

3.3 Managing Encryption of Data Volumes in the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . 3663.3.1 Enable Data Volume Encryption in an Existing SAP HANA System. . . . . . . . . . . . . . . . . .3663.3.2 Change the Page Encryption Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3703.3.3 Disable Data Volume Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

3.4 Changing Encryption Keys for Secure Storage of Logon Information. . . . . . . . . . . . . . . . . . . . . . . 3723.4.1 Change the SSFS Master Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3733.4.2 Change the Secure User Store Encryption Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

4 Availability and Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3764.1 About High Availability for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376

4.1.1 SAP HANA Disaster Recovery Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3774.1.2 SAP HANA Fault Recovery Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3804.1.3 Set up System Replication with hdbnsutil. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3814.1.4 Managing System Replication in the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . 4094.1.5 Setting up Host Auto-Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

4.2 SAP HANA Database Backup and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4244.2.1 The Backup Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4254.2.2 Data Storage Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4264.2.3 Authorization for Backup and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4274.2.4 Database Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429



4.2.5 Database Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4454.2.6 Backing Up SAP HANA Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4524.2.7 Housekeeping for Storage Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4554.2.8 Monitoring the Backup Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4594.2.9 Checking Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4604.2.10 Performing Data Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4694.2.11 Recovering the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4824.2.12 Copying a Database Using Backup and Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4884.2.13 SQL Syntax for Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

4.3 Scaling SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5104.3.1 About Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5114.3.2 Configuring the Network for Multiple Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5124.3.3 Mapping Host Names for Database Client Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5144.3.4 Add or Remove Hosts from an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5154.3.5 Scaling SAP HANA Extended Application Services (XS). . . . . . . . . . . . . . . . . . . . . . . . . 5164.3.6 Starting and Stopping Distributed SAP HANA Systems Using SAPControl. . . . . . . . . . . . 5174.3.7 Table Distribution in SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5174.3.8 Monitor Table Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5194.3.9 Redistribution of Tables in a Distributed SAP HANA System. . . . . . . . . . . . . . . . . . . . . . 520

5 SAP HANA XS Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5295.1 SAP HANA XS Administration Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5295.2 Maintaining Application Runtime Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

5.2.1 Create an Application Runtime Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5335.2.2 Edit an SQL Connection Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5355.2.3 Edit an HTTP Destination Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5365.2.4 Maintain XS Job Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

5.3 Managing Trust Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5405.3.1 Add/Edit a Trust Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5415.3.2 Create your own Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5425.3.3 Import a Server Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544

5.4 Maintaining SAML Providers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5455.4.1 Configure an SAP HANA System as an SAML Service Provider. . . . . . . . . . . . . . . . . . . . 5475.4.2 Add an SAML Identity Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5485.4.3 Modify an Existing SAML Identity Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550

5.5 Configuring HTTPS (SSL) for Client Application Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5515.6 Using Standard HTTP Port Numbers with SAP HANA XS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5555.7 Maintaining Single Sign-On for SAP HANA XS Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

5.7.1 Maintain the SAP HANA Trust Stores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5595.7.2 Configure the SAP Web Dispatcher Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5605.7.3 Configure SSO with X.509 Authentication for SAP HANA XS Applications. . . . . . . . . . . . 5615.7.4 Configure SSO with SAML Authentication for SAP HANA XS Applications. . . . . . . . . . . . 564



5.7.5 Configure SSO with SAP Logon Tickets for SAP HANA XS Applications. . . . . . . . . . . . . . 5675.7.6 Configure Outbound SSO with Assertion Tickets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570

6 Administration of SAP HANA Data Provisioning Technologies. . . . . . . . . . . . . . . . . . . . . . . . 5746.1 SAP HANA Data Provisioning Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .574

6.1.1 About SAP HANA Smart Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5746.1.2 Creating Data Flows for Provisioning Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5946.1.3 Starting Data Provisioning Jobs for Modeled Data Flows. . . . . . . . . . . . . . . . . . . . . . . . .595

7 SAP HANA HDBSQL (Command Line Reference). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5987.1 HDBSQL Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5987.2 HDBSQL Command Line Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6017.3 Logging On to a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6047.4 Executing Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6057.5 Executing Long Commands in Multiple Line Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6077.6 Editing Long Commands in an External File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6087.7 Redirecting Results to a File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609



1 Getting StartedThe SAP HANA Administration Guide describes the main tasks and concepts necessary for the ongoing operation of SAP HANA.The following areas are covered: SAP HANA studio as an SAP HANA administration tool Starting and stopping SAP HANA systems System configuration License management User provisioning Monitoring (for example, performance, memory usage, disk usage, alert situations) Backup and recovery Distributed system management High availability Remote data access using SAP HANA smart data access Other administrative tasks, for example, managing tables, managing persistence encryption, auditing

database activity, and so on.For more information about the SAP HANA landscape, security, and installation, see SAP Help Portal.

Related Information

http://help.sap.com/hana_platform

1.1 The SAP HANA StudioThe SAP HANA studio runs on the Eclipse platform and is both the central development environment and the main administration tool for SAP HANA.Administrators use the SAP HANA studio, for example, to start and stop services, to monitor the system, to configure system settings, and to manage users and authorizations. The SAP HANA studio accesses the servers of the SAP HANA database by SQL. Developers can use the SAP HANA studio to create content such as modeled views and stored procedures. These development artifacts are stored in the repository, which is part of the SAP HANA database. The SAP HANA studio is developed in Java and based on the Eclipse platform.The SAP HANA studio presents its various tools in the form of perspectives. Database administration and monitoring features are available primarily within the SAP HANA Administration Console perspective. Additional perspectives include the SAP HANA Modeler perspective and the SAP HANA Development perspective. For more information about these perspectives, see the SAP HANA Developer Guide and the SAP HANA Modeler Guide.

NoteDepending on how you installed the studio, all features may not be available. During installation, you can specify which features you require depending on your role. For system administration, only the feature SAP

SAP HANA Administration GuideGetting Started


HANA Studio Administration is necessary. For more information see SAP HANA Studio Features in the SAP HANA Studio Installation and Update Guide.

Updating the SAP HANA Studio

To ensure that you are working with the most recent version of the SAP HANA studio, you need to check regularly for updates. You can update the SAP HANA studio using several methods. For example, you can use SAP HANA Software Lifecycle Manager, or you can set up a central update site.For more information, see the SAP HANA Studio Installation and Update Guide.

Related Information

SAP HANA Developer GuideSAP HANA Modeler GuideSAP HANA Studio Installation and Update Guide

1.1.1 Open the SAP HANA Administration ConsoleTo access the database administration and monitoring features of the SAP HANA studio, you open the SAP HANA Administration Console perspective.

Procedure

1. From your file explorer, start hdbstudio.exe.2. On the Welcome page, choose Open SAP HANA Administration Console.

Results

The SAP HANA Administration Console opens. The Systems view is open by default. This view is the central access point for performing system-specific administration and monitoring activities. From this view, you can access the other views and editors used for administration.

NoteOnce you have closed the Welcome page, you can always change from another perspective to the SAP HANA Administration Console perspective by choosing Window Open Perspective SAP HANA



Administration Console or by choosing the SAP HANA Administration Console button in the perspective switcher in the upper-right corner of the screen.

1.1.1.1 Screen Areas of the SAP HANA Administration Console

The database administration and monitoring features of the SAP HANA studio are presented in the SAP HANA Administration Console perspective according to a default screen layout.The following figure shows the screen areas of the SAP HANA studio with the SAP HANA Administration Console perspective open:

Figure 1: Screen Areas of the SAP HANA Administration Console

The following is a brief overview of the various screen areas:Screen Area DescriptionMain menu and main toolbar The main menu contains standard Eclipse functions.

The main toolbar is located beneath the main menu. The contents of this toolbar change based on the active perspective. Items in the toolbar might be enabled or disabled based on the state of either the active view or editor. The perspective switcher is an additional toolbar normally located on the top-right of the screen, next to the main toolbar. It allows



Screen Area Description

quick access to perspectives that are currently open. It also has a button that can open new perspectives.

Editor area Each perspective has editors for editing and browsing resources. Editors are displayed as tabs in the editor area. Several editors can be open at the same time.Important editors available in the SAP HANA Administration Console include: The System Monitor The Administration editor The Backup editor The Security editor The SQL console

Views Views support editors and provide alternative presentations as well as ways to navigate the information in the SAP HANA studio. Important views available in the SAP HANA Administration Console include: Systems, which is the central access point for performing system

administration and monitoring activities Error Log, which contains error and information messages Properties, which shows the detailed properties of the active re

source (for example, the SAP HANA system selected in the Systems view)

To open a view, from the main menu, choose Window Show View .

For more information about the Eclipse platform, see the Eclipse documentation.

1.1.1.2 Editors and Views of the SAP HANA Administration ConsoleSeveral editors and views are available in the Administration Console for the administration and monitoring of SAP HANA databases.The following table describes the main system-level editors and views available in the Administration Console and how to access them. Other editors are available for specific resources (for example users, roles, tables and so on).View/Editor Description How to OpenSystems The Systems view provides you with a hi

erarchical view of all the SAP HANA systems managed in the SAP HANA studio and their contents. It is the central access point for performing system-specific ad

The Systems view is open by default when you open the Administration Console. If it is closed, you can open it from the main menu by choosing Window Show View Systems .



View/Editor Description How to Openministration and monitoring activities using the other available editors.

System Monitor The System Monitor is an editor that provides you with an overview of all your SAP HANA systems at a glance. From the System Monitor, you can drill down into the details of an individual system in the Administration editor.

In the toolbar of the Systems view, choose the button.

Administration The Administration editor the main tool for performing administration and monitoring activities.

You can access the Administration editor in several ways: From the Systems view toolbar,

choose the Open Default Administration button.

In the Systems view, double-click the system.

In the context menu of the Systems view, choose Configuration and Monitoring Open Administration .

Administration Diagnosis Mode

The Administration editor diagnosis mode allows you to monitor and perform emergency operations on systems to which either no SQL connection is available or the SQL connection is overloaded.

The Administration editor opens automatically in diagnosis mode in the following situations: When you open the Administration ed

itor for a system that cannot be reached by SQL

When you initiate the start, stop, or restart of a system

You can also open the Administration editor in diagnosis mode from the Systems view toolbar by choosing the Open Diagnosis Mode button.

Monitoring Dashboard

The Monitoring Dashboard visualizes key aspects of system health and configuration on a single screen with the option to drill down to more detailed views.

From the Systems view, choose Configuration and Monitoring

Dashboard .

Backup The Backup editor is the main tool for performing administration and monitoring activities related to backup.

You can access the Backup editor in several ways: Expand the system in the Systems

view and choose the Backup entry In the context menu of the Systems

view, choose Backup and RecoveryOpen Backup Console .



View/Editor Description How to OpenSecurity The Security editor is the main tool for

managing the following aspects of security administration: Password policy Auditing Data volume encryption

You can access the Security editor in several ways: Expand the system in the Systems

view and choose the Security entry In the context menu of the Systems

view, choose Security Open Security Console .

SQL Console Some tasks may require you to work with SQL statements, for example, certain administration tasks can only be performed using SQL. You can enter, execute, and analyze SQL statements in the SQL console.

You can access the SQL console in several ways: From the Systems view toolbar,

choose the button. In the context menu of the Systems

view, choose Open SQL Console.

Related Information

Systems View [page 26]The Systems view provides you with a hierarchical view of all the SAP HANA systems managed in the SAP HANA studio and their contents. It is the central access point for performing system-specific administration and monitoring activities.

System Monitor [page 64]The System Monitor is an editor that provides you with an overview of all your SAP HANA systems at a glance. From the System Monitor, you can drill down into the details of an individual system in the Administration editor.

Monitoring Dashboard [page 66]The Monitoring Dashboard visualizes key aspects of system health and configuration on a single screen with the option to drill down to more detailed views.

Administration Editor [page 68]To identify problems early and avoid disruptions, you need to monitor your systems continuously. While the System Monitor provides you with an overview of all systems at a glance, the Administration editor allows you to drill down into the details of resource usage and performance for each system.

The Backup Console [page 425]The Backup Console is the main tool for performing administration and monitoring tasks related to backup. You can start the Backup Console from the SAP HANA Systems view in SAP HANA studio.

Execute SQL Statements in the SAP HANA Studio [page 13]In the SAP HANA studio, you can execute SQL statements using the SQL console.



1.1.2 Execute SQL Statements in the SAP HANA StudioIn the SAP HANA studio, you can execute SQL statements using the SQL console.

Prerequisites

You have the required privileges to perform the operation. (Optional) You have customized the behavior of SQL statement execution in the SQL console. You can do

this in the SAP HANA studio preferences.

Procedure

1. Open the SQL console.The SQL console displays the connected system and user in the header. If you opened the SQL console from a specific catalog object, the schema is also displayed.

To connect to a different system from within the SQL console, choose the (Choose Connection) button in the toolbar in the top-right of the editor and choose another system.

2. Enter the SQL statement or statements.The following rules apply: You can write SQL syntax elements in either upper or lower case. You can add any number of spaces and line breaks. To force the system to distinguish between upper/lower-case letters in database object names (such

as table names), enter the name between double quotation marks: "My_Table" To comment out a line, use - - (double hyphens) at the start of the line. To use name completion, press the key combination CTRL + SPACE .

This opens a list from which you can choose schema and table names, SQL keywords, and user-defined templates.

NoteYou define templates in the preferences ( SAP HANA Runtime Templates ).

Enter multiple SQL statements, separated by the configured separator character, semicolon (;) by default.

3. Execute the statement(s) in one of the following ways: In the context menu, choose Execute. Choose the Execute button in the toolbar. Press F8 .If you have entered several statements, you can execute them individually by simply highlighting the statement and executing. If you do not highlight an individual statement, all statements are executed.



Results

The Result tab appears with the statement's results. Multiple Result editors may open depending on the statement(s) executed.

NoteTo prevent performance issues with the SAP HANA studio, by default only 50 Result editors can open. Once this number is reached, statement execution stops.

Information about statement execution is displayed in the lower part of the screen, for example:

Started: 2013-11-27 14:22:16Statement 'SELECT * FROM "PUBLIC"."M_CS_TABLES"' Successfully executed in 260 ms 932 s (server processing time: 258 ms 868 s) Fetched 583 row(s) in 16 ms 602 s (server processing time: 11 ms 278 s)

NoteSAP HANA implements a prefetch mechanism that returns the head of the result together with the execute command. By default, 32 rows are prefetched. This means that if the result set is smaller than the number of rows prefetched, the subsequent fetch command can simply take the rows from the prefetch buffer in the client library without any further processing on the server.

Related Information

SAP HANA Studio Preferences [page 18]The preferences of the SAP HANA studio include many options for customizing the features of the SAP HANA Administration Console.

SAP HANA SQL and System Views Reference



1.1.3 Authorization for Administration TasksTo perform administration tasks in the SAP HANA studio, you require certain privileges and/or roles. These must be granted to your database user or relevant role by a user administrator.

System Administration and Monitoring

Table 1: System Monitoring TasksTask Required AuthorizationOpen the SAP HANA Administration Console perspective with read-only access to the system tables and monitoring views.

System privilege CATALOG READ

View alert information Object privilege SELECT on the schema _SYS_STATISTICS

View system information in the System Monitor System privilege CATALOG READ and object privilege SELECT on the schema _SYS_STATISTICS

Open the Web-browser-based Monitoring Dashboard Role sap.hana.admin.roles::MonitoringMonitor table distribution in the Table Distribution editor

System privilege CATALOG READ

Open the Web-browser-based editors Resource Utilization, Memory Overview, and Memory Allocation Statistics

Role sap.hana.admin.roles::Monitoring

NoteThe standard MONITORING role contains the system privilege CATALOG READ and object privilege SELECT on the schema _SYS_STATISTICS. However, the MONITORING role does not contain the role sap.hana.admin.roles::Monitoring

System Administration

Table 2: General System Administration TasksTask Required AuthorizationStop, start, restart system Operating system user (adm) credentialsStop and start database services System privilege SERVICE ADMINCancel operations System privilege SESSION ADMINMark disk-full events as handled System privilege MONITOR ADMIN



Task Required AuthorizationChange the properties of a system as defined in the parameters of the configuration (*.ini) files

System privilege INIFILE ADMIN

Configure system checks (e-mail notification, alter thresholds)

System privilege INIFILE ADMIN

Execute table redistribution operations System privilege RESOURCE ADMIN and at least the object privilege ALTER for all schemas involved

Configure hosts for auto-failover RESOURCE ADMIN

Table 3: Catalog Object Administration TasksTask Required AuthorizationPerform a delta merge operation on a table (manually)

Object privilege UPDATE for the table

Compress a table Object privilege UPDATE for the tableManually move tables and table partitions to another host in a distributed system

Object privilege ALTER for the table

Partition a non-partitioned table Object privileges ALTER and UPDATE for the tableChange a partitioned table into a non-partitioned table by merging all partitions

Object privilege ALTER for the table

Import catalog objects Depending on the import, object privilege INSERT/UPDATE, DROP, and CREATE for the catalog objects in question

Export catalog objects Object privilege SELECT for the catalog objects in question

Table 4: License Management TasksTask Required AuthorizationCheck license information System privilege LICENSE ADMINInstall and delete license keys System privilege LICENSE ADMIN

Troubleshooting

Table 5: Diagnosis TasksTask Required AuthorizationConfigure traces (except kernel profiler) System privilege TRACE ADMINConfigure kernel profiler Standard role SAP_INTERNAL_HANA_SUPPORTDelete trace files System privilege TRACE ADMIN



Task Required AuthorizationTroubleshoot offline system (including access diagnosis files) using Administrator editor diagnosis mode

Operating system user (adm) credentials

Security Administration

Table 6: User and Role Management TasksTask Required AuthorizationCreate, change, and delete users System privilege USER ADMINCreate, change, and delete roles in runtime System privilege ROLE ADMINGrant and revoke privileges/roles to/from users and roles

To grant SQL privileges and roles, you must have the privilege and/or role yourself and be authorized to grant it to others. To grant privileges on activated repository objects, you must be authorized to execute certain stored procedures. For more information, see Prerequisites for Granting and Revoking Privileges and Roles.

Configure the password policy and the password blacklist

System privilege INIFILE ADMIN and object privileges INSERT and DELETE for either the _SYS_PASSWORD_BLACKLIST table or the _SYS_SECURITY schema

View procedures and calculation views in the authorization dependency viewer

System privilege CATALOG ADMIN

Table 7: Additional Security Administration TasksTask Required AuthorizationActivate and configure auditing System privilege AUDIT ADMIN or AUDIT OPERATOR

or INIFILE ADMINCreate and manage audit policies System privilege AUDIT ADMIN or AUDIT OPERATORRead the audit trail database table SYS.AUDIT_LOG System privilege AUDIT OPERATORDelete entries from the audit trail System privilege AUDIT OPERATOREnable persistence encryption and access the encryption monitoring views M_PERSISTENCE_ENCRYPTION_STATUS and M_PERSISTENCE_ENCRYPTION_KEYS

System privilege RESOURCE ADMIN

Change the page encryption key used for data volume encryption and re-encrypt the data

System privilege RESOURCE ADMIN



Backup and Recovery

Table 8: Backup and Recovery TasksTask Required AuthorizationPerform backups BACKUP ADMIN and CATALOG READ or BACKUP

OPERATOR and CATALOG READOpen the Backup editor BACKUP ADMIN and CATALOG READDelete data and log backups from the backup catalog and physically from the backup location

BACKUP ADMIN

Recover Operating system user (adm) credentials

Related Information

Prerequisites for Granting and Revoking Privileges and Roles [page 359]To be able to grant and revoke privileges and roles to and from users and roles, several prerequisites must be met.

Create and Authorize a User [page 350]You create a database user for every user who wants to work with the SAP HANA database. When you create a user, you configure how the user will be authenticated, as well as grant the privileges and roles necessary for the user's function.

1.1.4 SAP HANA Studio PreferencesThe preferences of the SAP HANA studio include many options for customizing the features of the SAP HANA Administration Console.

To open the preferences of the SAP HANA studio, choose Window Preferences . The preferences related to SAP HANA perspectives are all available under SAP HANA.The following preferences pages contain administration-related settings.

Administration

Table 9: AdministrationOption DescriptionShow user-defined SQL statements on the System Information tab

If you select this option, user-defined SQL statements contained in the specified XML file are displayed on the System Information tab of the Adminis



Option Descriptiontration editor. You can also change the default location and name of the XML file.

Table 10: Backup EditorOption DescriptionNumber of SQL objects to retrieve This setting determines the number of backups dis

played on the Backup Catalog tab of the Backup editor.

Refresh interval in seconds This setting determines the refresh interval of the Overview tab of the Backup editor.

Connection timeout in seconds This setting sets a timeout for the connection to the backup editor.If the specified timeout is exceeded, no further attempt is made to establish a connection to the Backup editor. As a consequence, the Backup editor is not displayed in the Systems view. The other information about the SAP HANA database is still shown in SAP HANA studio.

Global Settings

Table 11: Global SettingsOption DescriptionRestore logged-on/logged-off status of systems on startup

This option determines whether or not you are automatically logged on to systems registered in the Systems view. By default, if you were logged on when you closed the studio (and your password is saved in the Eclipse secure store), you are logged on automatically on restart. Similarly, if you logged off before closing the studio, you are not logged on restart and you must actively log on.If you deselect this option, you must always log on after restart.

Request confirmation before a user is deleted When a user is deleted, all dependent objects are also deleted. Select this option if you want a confirmation message to appear before a user is deleted.

Show Management Console for hdbcons If you select this option, an additional tab Console is available in the Administration editor. You can execute hdbcons commands directly in this console.



Option Description

CautionTechnical expertise is required to use hdbcons. To avoid incorrect usage, use hdbcons only with the guidance of SAP HANA development support.

Runtime

Table 12: CatalogOption DescriptionFetch all database catalog objects By default the SAP HANA studio fetches a limited

number of catalog objects when folders in the Systems view such as Tables and Views are opened.If you select this option, all catalog objects are loaded in the corresponding folder. This may affect system performance as it may take some time to fetch all database catalog objects.

Number of database catalog objects to display If you do not select the Fetch all database catalog objects option, you can specify the maximum number of catalog objects to be fetched. If the number of available objects exceeds the number specified here, the message Object limit reached appears.The default number is 1,000.

Show table comment before table name (Modeler) If you select this option, a table's description appears before its name in the Systems view if the SAP HANA Modeler perspective is active.

Table 13: CommonOption DescriptionConfirm saving editors If you select this option, the system displays a confir

mation dialog when an editor is closed with content that was not saved.

Autosaving of SQL Console Content Save content when SAP HANA Studio is closed Content save interval minutes

If you select this option, the content of SQL console sessions is saved automatically when the SAP HANA studio is closed. No dialog requesting the user to save is displayed.Additionally, it is possible to have the content saved at a specified interval. If the SAP HANA studio is



Option Description

closed unexpectedly, the last version can be recovered.

Copy options: Data separator Tab separated Align copied values with space Copy cell in editor by using [CTRL] C Copy editor content with column header

These are formatting options for copying content from the table editor.

Representation of null value This option specifies the character used to display NULL values

Database identifier upper case This option specifies that the IDs of database objects can be entered only in uppercase letters.

Default action for database tables: Show content Show definition

This setting specifies which view of a table is opened when it is double-clicked in the Systems view: its definition or its content.

Table Distribution EditorMaximum Number of Tables Displayed

This setting specifies the maximum number of tables that are displayed when you show table distribution.

Table 14: ResultOption DescriptionLimit for LOB columns (bytes) This option specifies the maximum number of bytes

that are loaded from the database for one large object (LOB) column.

Limit for zoom (bytes) This option specifies the maximum number of bytes that the SAP HANA studio displays when you zoom the LOB column in the result table in the Result tab of the SQL console.

Append exported data to file If you select this option, then when you export the result table to a file, the system attaches the content of the current result table to the existing file content.

Display character byte value as hex If you select this option, data of the data type CHAR BYTE is displayed as hexadecimal digits. If you do not select this option, this data is displayed in binary format.

Format values If you select this option, country-specific formatting is applied (for example, numeric values or dates).

Display duration result row fetch If you select this option, you can see in the SQL console how long it took to fetch one row of a result set.



Option DescriptionMaximum number of rows displayed in result This option specifies the maximum number of rows

fetched from the database and displayed in the result table of the Result tab.

Enable zoom of LOB columns You must select this option if you want to be able to zoom LOB columns in the result table of the Result tab. You can zoom an LOB column by right-clicking and choosing Export Cell To Zoom .Note that if you zoom an LOB column, it is automatically closed after 15 minutes or when the Result tab is closed.

NoteThe options available under Result relate to the display of results following execution of a SELECT statement the SQL console.

Table 15: SQLOption DescriptionStop batch SQL statement execution if an error occurs

If you select this option, then when you execute a series of SQL statements separated by comment characters, the system stops the execution when an error occurs.

Clear SQL console log before SQL statement execution

If you select this option, the log from the last SQL statement is deleted before the next SQL statement is executed.

Close results before SQL statement execution If you select this option, then when you execute an SQL statement in the SQL console, all old results tabs in the same SQL console session are closed.

Display time of statement execution start If you select this option, you can see in the SQL console the time at which statement was executed.

Display duration of failed statements If you select this option, you can see in the SQL console how long a statement took to execute in the SAP HANA studio even if the statement failed.

Connection parameters for SQL console: Auto-commit mode Isolation level Confirm change of connection

Auto-commit mode: If on, the system performs all COMMIT ac

tions automatically If off, you have to enter COMMIT statements

explicitly. The isolation level determines how the system

implicitly controls locking and versioning of database objects.

Confirm change of connection



Option DescriptionIn the SQL console, you can change the SQL connection you are working on. When you change a connection, cursors may be closed or transactions may be rolled back. If you select this option, a change of SQL connection must first be confirmed.

SQL console settingsCommand separator This option specifies the separator for SQL state

ments in the SQL console.Maximum number of characters for multiple statement execution

When you enter multiple statements in the SQL console for execution, the content must be parsed and the individual statements for execution recognized. However, if there is too much content, out-of-memory situations or a long parse time may result. When the number of characters specified with this option is reached, parsing does not take place and the content is executed as a single statement.

Number of tables for table name completion This option specifies the number of tables that are displayed in the list when you use name completion in the SQL console.

Number of open Result editors The results of statement execution may be returned in multiple Result editors. Once the number of open Result editors specified with this option is reached (by default 50), statement execution stops. We recommend that you do not increase the default value of this option as it may cause performance issues in the studio.

Table 16: TemplatesOption DescriptionName Word to be completed when you press the key com

bination CTRL + SPACE .You can create more than one template with the same name. If more than one template exists for one word, the system displays a list.

Context Editor in which you can use the template.Description Template descriptionAuto insert If on, the code assist automatically inserts the tem

plate if it is the only proposal available at the cursor position.



NoteThe options available under Templates always refer to the editor that is currently open.

Table Viewer

Table 17: Table ViewerOption DescriptionShow gridlines Use these options to customize the appearance of list

displays in the Administration editor, for example, the list of files on the Diagnosis Files tab.Alternating colored rows



2 System AdministrationAs a database administrator you are responsible for operational tasks related to the administration, monitoring, and maintenance of your SAP HANA systems.Several tools are available for system administration: The SAP HANA Administration Console perspective of the SAP HANA studio is main tool for general

system administration and monitoring tasks. Specific tasks related to the configuration of system components after installation (such as adding and

removing hosts, renaming systems) are performed using the SAP HANA lifecycle management tools. If you are using SAP HANA in conjunction with other SAP business applications, it is possible to integrate

with SAP Solution Manager. The SAP HANA HW Configuration Check Tool allows you to check the interoperability of SAP HANA with

your existing enterprise storage in production environments.In addition to the above-mentioned tools, there are also Web-based administration tools for various tasks related to SAP HANA XS applications, for example, application security configuration and application lifecycle management. The server side parts of these tools are system applications that run in the XS server. For more information, see SAP HANA XS Administration Tools and SAP HANA Application Lifecycle Management.

Related Information

SAP HANA XS Administration Tools [page 529]SAP HANA XS includes a Web-based tool that enables you to maintain important parts of the application-development environment, for example, security and authentication methods.

SAP HANA Developer Guide

SAP HANA Administration GuideSystem Administration


2.1 Managing SAP HANA Systems in the SAP HANA Studio

The SAP HANA studio allows you to work efficiently and conveniently with SAP HANA systems.

2.1.1 Systems View

The Systems view provides you with a hierarchical view of all the SAP HANA systems managed in the SAP HANA studio and their contents. It is the central access point for performing system-specific administration and monitoring activities.

Figure 2: The Systems View

The Systems view comprises the following elements: A hierarchical view of all your systems and their contents. For administration and monitoring purposes,

the following are the most important elements: The Catalog folder, which contains all activated database objects, grouped by schema The Security folder, which contains all database users and activated rolesDouble-clicking the top-level system entry in the hierarchical view opens it in the Administration editor. From the hierarchical view, you can also access the Backup ( ) and Security ( ) editors.

A toolbar that provides you with quick access to several editors and functions. A context menu that provides you quick access to a range of system-specific functions.



Related Information

Toolbar Options in the Systems View [page 27]The Systems view toolbar provides you with quick access to several editors and functions.

2.1.1.1 Toolbar Options in the Systems ViewThe Systems view toolbar provides you with quick access to several editors and functions.Icon Option Description

Add System... Opens the Add System dialog in which you can create and configure a connection to a system

Add System Archive Link... Opens the Add System Archive Link dialog in which you can add a link to a centrally-stored archive of SAP HANA systems

Open System Monitor Opens the System Monitor to see an overview of all systems in the Systems view

Open Default Administration Opens the Administration editor for the selected system

Open Diagnosis Mode Opens the Administration editor for the selected system in diagnosis mode

Open SQL Console Opens the SQL console for the selected system

Find System Opens the Find System dialog in which you can search for a system in the Systems view

Collapse All Collapses the tree expansion state of all systems in the Systems view

Link with Editor Toggles whether the entry selected in the Systems view is linked to the active editor. When this option is selected, changing the active editor will automatically update the selected system.

View Menu Provides menu items that allow you to sort or filter the contents of the Systems view

Related Information

Add an SAP HANA System [page 28]To work with and manage an SAP HANA system in the SAP HANA studio, you must create and configure a connection to the system.

Link a Centrally-Stored Archive of SAP HANA Systems [page 33]To allow users who work in the SAP HANA studio to connect efficiently to multiple SAP HANA systems, you can manage a list of all systems in a centrally-accessible archive. Users can then simply link to this archive.



System Monitor [page 64]The System Monitor is an editor that provides you with an overview of all your SAP HANA systems at a glance. From the System Monitor, you can drill down into the details of an individual system in the Administration editor.

Administration Editor [page 68]To identify problems early and avoid disruptions, you need to monitor your systems continuously. While the System Monitor provides you with an overview of all systems at a glance, the Administration editor allows you to drill down into the details of resource usage and performance for each system.

Troubleshooting an Inaccessible or Unresponsive SAP HANA System [page 300]When a system cannot be reached by SQL or is experiencing performance problems, you cannot use the Administration editor to troubleshoot and/or resolve issues. By opening the Administration editor in diagnosis mode you or an SAP support engineer can access diagnosis information and perform emergency operations to resolve the situation.

Execute SQL Statements in the SAP HANA Studio [page 13]In the SAP HANA studio, you can execute SQL statements using the SQL console.

2.1.2 Add an SAP HANA SystemTo work with and manage an SAP HANA system in the SAP HANA studio, you must create and configure a connection to the system.

Prerequisites

The relevant ports in your firewall are open. If you want to secure communication between the SAP HANA server and the SAP HANA studio using the

Secure Sockets Layer (SSL) protocol, you have configured the server for SSL and imported the trust store file that contains the server root certificate into either the Java keystore or your user keystore on the client.

You must have a database user, or the necessary infrastructure for Kerberos-based user authentication must be in place.

Procedure

1. From the Systems view toolbar, choose (Add System...).The System wizard opens.

2. Enter the following system information:Option DescriptionHost name Name of the host where the system is installed



Option DescriptionIf you are adding a distributed system, specify the master host. You do not have to enter all host names explicitly as they are determined automatically. If the master host becomes unavailable, the connection is automatically established through one of the other hosts. Hosts that are added to the system later are also detected automatically.

TipOnce you have finished adding the system, you can see all available hosts in the system properties. Right-click the system in the Systems view and choose Properties. All hosts are listed on the Hosts Used to Connect tab of the Database User Logon page.

NoteThe host name of the server that hosts the database must be accessible from the client on which the SAP HANA studio is running, even if you add the system using its IP address.

Instance number

Instance number of the system

Description Description of the system that you want to appear next to the system name in the Systems viewFolder System folder

If you are organizing your systems in the Systems view using folders and have already created folders, choose the folder to which you want to add the system.

Locale Your locationThis setting specifies the language of objects created in the SAP HANA repository.

3. Choose Next.4. Choose the authentication type for user logon to the database:

If you are integrating the SAP HANA studio into a Kerberos-based single sign-on environment, choose Authentication by current operating system user.

If you are implementing user name/password authentication, choose Authentication by database user and enter the database user name and password. You can choose to have your password stored in the Eclipse secure storage so that you do not have re-enter it every time you open the studio.

5. Indicate whether you want to use a secure connection to the system by choosing Connect using SSL.

NoteYou must select this option to be able to modify the SSL connection properties (step 9).

6. Configure the connection of the SAP start service (sapstartsrv) to the system.An HTTP connection to the system using the SAP start service is automatically enabled. You can choose to disable this connection if it is not required.



NoteIf you disable this connection, administrative actions that require operating system access are not possible in the SAP HANA studio (for example, stopping and starting the system, performing a recovery, or opening the Administration editor in diagnosis mode).

If you want the SAP start service to communicate with the system via a secure connection, choose Use HTTPS.

7. Choose Next.8. Modify the following advanced connection properties for your system if necessary:

Option DescriptionOption JDBC connection parameter(s)Auto-Reconnect Auto-reconnect option

If you select this option, the SAP HANA studio automatically reconnects if the connection to the system fails.

9. Configure SSL communication: To have the identity of the server validated during connection, choose Validate SSL Certificate.

The server's public-key certificate is validated against the root certificate stored in the trust store.If you want to override the system host name specified in the server certificate, enter a host name with a defined certificate.

Use user key store as trust storeThe Java SSL property trustStore specifies the trust store containing the certificate used to validate that the server certificate is issued by a trusted entity. Each user can import certificates into a user keystore in Java using the keytool command line tool (part of the JRE installation). The user keystore is located in the home directory of the current operating system user. The file name is .keystore.The set of root certificates delivered with the JRE from well-known issuers (for example, Verisign, Thawte, Deutsche Telekom) is used when this option is not selected.

10. Choose Finish.The system is added in the Systems view. The system entry displays the following information: SID Connected user System usage if it is a production system System description if availableInformation about system availability and user connection status are indicated by icons.

Results

You can now access the system in the SAP HANA studio.



Related Information

User Authentication and Single-Sign On [page 307]The identity of database users accessing SAP HANA is verified through a process called authentication. SAP HANA supports several authentication mechanisms, several of which can be used for the integration of SAP HANA into single sign-on environments (SSO).

Provisioning Users [page 347]As a user administrator, you create and configure users, as well as authorize them to work with the SAP HANA database.

Configure System Usage Type [page 56]You can configure the usage type of an SAP HANA system (for example, production, development) during installation with the system_usage parameter or later by changing the system properties. Clients such as the SAP HANA studio can use this property to alter behavior.

Configure SSL for SAP HANA Studio Connections [page 41]It is recommended to secure communication between the SAP HANA studio and the SAP HANA database using the secure sockets layer (SSL) protocol.

2.1.3 Add an SAP HANA System with a Different UserIf you want to work with an SAP HANA system using several database users, you can create a connection to the system in the SAP HANA studio with the credentials of different users.

Prerequisites

The system has already been added once in the Systems view. If you want to secure communication between the SAP HANA server and the SAP HANA studio using the

Secure Sockets Layer (SSL) protocol, you have configured the server for SSL and imported the trust store file that contains the server root certificate into either the Java keystore or your user keystore on the client.

The relevant ports in your firewall are open. You must have a database user, or the necessary infrastructure for Kerberos-based user authentication

must be in place.

Procedure

1. In the Systems view, right-click the system and choose Add System with Different User.2. Choose the authentication type for user logon to the system:

If you are integrating the SAP HANA studio into a Kerberos-based single sign-on environment, choose Authentication by current operating system user.



If you are implementing user name/password authentication, choose Authentication by database user and enter the database user name and password. You can choose to have your password stored in the Eclipse secure storage so that you do not have re-enter it every time you open the studio.

3. Indicate whether you want to use a secure connection to the system by choosing Connect using SSL.

NoteYou must select this option to be able to modify the SSL connection properties (step 7).

4. Configure the connection of the SAP start service sapstartsrv to the system.An HTTP connection to the system using the SAP start service is automatically enabled. You can choose to disable this connection if it is not required.

NoteIf you disable this connection, administrative actions that require operating system access are not possible in the SAP HANA studio (for example, stopping and starting the system, performing a recovery, or opening the Administration editor in diagnosis mode).

If you want the SAP start service to communicate with the system via a secure connection, choose Use HTTPS.

5. Choose Next.6. Modify the following advanced connection properties for your system if necessary:

Option DescriptionOption JDBC connection parameter(s)Auto-Reconnect Auto-reconnect option

If you select this option, the SAP HANA studio automatically reconnects if the connection to the system fails.

7. Configure SSL communication: To have the identity of the server validated during connection, choose Validate SSL Certificate.

The server's public-key certificate is validated against the root certificate stored in the trust store.If you want to override the system host name specified in the server certificate, enter a host name with a defined certificate.

Use user key store as trust storeThe Java SSL property trustStore specifies the trust store containing the certificate used to validate that the server certificate is issued by a trusted entity. Each user can import certificates into a user keystore in Java using the keytool command line tool (part of the JRE installation). The user keystore is located in the home directory of the current operating system user. The file name is .keystore.The set of root certificates delivered with the JRE from well-known issuers (for example, Verisign, Thawte, Deutsche Telekom) is used when this option is not selected.

8. Choose Finish.The system is added in the Systems view. The system entry displays the following information: SID Connected user System usage if it is a production system System description if available



Information about system availability and user connection status are indicated by icons.

Results

You can now access the system in the SAP HANA studio.

Related Information

User Authentication and Single-Sign On [page 307]The identity of database users accessing SAP HANA is verified through a process called authentication. SAP HANA supports several authentication mechanisms, several of which can be used for the integration of SAP HANA into single sign-on environments (SSO).

Provisioning Users [page 347]As a user administrator, you create and configure users, as well as authorize them to work with the SAP HANA database.

Configure System Usage Type [page 56]You can configure the usage type of an SAP HANA system (for example, production, development) during installation with the system_usage parameter or later by changing the system properties. Clients such as the SAP HANA studio can use this property to alter behavior.

Configure SSL for SAP HANA Studio Connections [page 41]It is recommended to secure communication between the SAP HANA studio and the SAP HANA database using the secure sockets layer (SSL) protocol.

2.1.4 Link a Centrally-Stored Archive of SAP HANA SystemsTo allow users who work in the SAP HANA studio to connect efficiently to multiple SAP HANA systems, you can manage a list of all systems in a centrally-accessible archive. Users can then simply link to this archive.

Prerequisites

An XML file containing a list of all SAP HANA systems and their connection information exists at a centrally-accessible location, for example, a network file server.You can create this file by exporting a list of systems from your installation of the SAP HANA studio to the required location.



Context

A centrally-stored archive of SAP HANA systems is an efficient way to deploy system information to all users of the SAP HANA studio, for example, developers, content modelers, and other administrators. It avoids users having to obtain the connection details of all systems individually and then having to add them all individually. In addition, if you change the central file, for example to add new systems or change the host of an existing system, you can ensure that users always have up-to-date system access.

Procedure

1. Form the Systems view toolbar, choose (Add System Archive Link...).2. Specify the following link details:

Link name Path to the system archive containing the system information Optional: A folder in the Systems view

3. Choose Finish.

Results

The system archive appears in the Systems view as a link node ( ). By expanding the link node, you can see all the systems contained within.To be able to access a system in the system archive, the password of the connecting user specified in the system properties must be available in the user's local Eclipse secure storage. If this is not the case, you must log on to the system.

NoteThe system archive file does not contain user passwords.

As the system archive is only linked, note the following: Systems are not added to the user's local workspace. Users cannot edit the connection properties of systems in the system archive. Users cannot change the order or hierarchical structure of systems in the system archive.

Related Information

Export a List of SAP HANA Systems [page 38]You can export a list of your SAP HANA systems from the SAP HANA studio as an XML file and then import it into another instance of the SAP HANA studio or use it as system archive to which other users can link.



2.1.5 Log Off From/Log On To an SAP HANA SystemIn the SAP HANA studio, 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 right-click it in the Systems view and choose Log Off.All open connections to the system are closed, and in the Systems view, the system appears disabled. No information regarding its operational status is available; you cannot expand it and browse its contents.

NoteEditors connected to the system at the time of log-off may close as a result. If an editor contains any unsaved work, you will be prompted to save it first.

To log on to a system, simply double click it in the Systems view or from the context menu, choose Log On.If your password is saved in the Eclipse secure store, you are logged on to the system immediately and can connect to it again. If have disabled the storing of passwords in the Eclipse secure store, you must re-enter your password.

Related Information

Disable Password Storage in Eclipse Secure Store [page 36]When an SAP HANA system is added in the SAP HANA studio, the user can choose to store his or her password in the Eclipse secure storage. To improve security, you can disable this password storage. Users must then log on to the system every time they open the studio.

2.1.5.1 User Logon Behavior on SAP HANA Studio StartupWhether or not you are logged on to your SAP HANA systems when you start the SAP HANA studio depends on whether or not you were logged on when you closed the studio.If you logged off from a system before closing the studio, you are still logged off and must log on explicitly. If you were logged on when you closed the studio, you are logged on automatically. This is the default behavior.However, you can change this behavior so that no automatic logon takes place when the studio is started: explicit logon is always required.

To do so, choose Preferences SAP HANA Global Settings and deselect the option Restore logged-on/logged-off status of systems on startup.



NoteAutomatic logon on studio startup can only take place if the connecting user's password is stored in the Eclipse secure store. If it is not, explicit logon is always required.

2.1.6 Disable Password Storage in Eclipse Secure Store

When an SAP HANA system is added in the SAP HANA studio, the user can choose to store his or her password in the Eclipse secure storage. To improve security, you can disable this password storage. Users must then log on to the system every time they open the studio.

Prerequisites

You are logged on to the computer on which the SAP HANA studio is installed as either the root user (Linux) or local administrator (Windows).

Context

The Eclipse secure storage stores user passwords securely to disk on the SAP HANA studio client. To connect to a system in the SAP HANA studio, the user does not have to enter his or her password; the stored password is used. This behavior may not be desired for security reasons in some cases, for example: To prevent individuals from being able to access systems using another user's credentials

This is possible if several users share the computer on which the SAP HANA studio is installed. To prevent users from locking their accounts

This is possible if a user's password for a system has expired but the old password is stored in the secure store. The user may lock their account due to too many failed logon attempts.

Procedure

Disable password storage by specifying the command -noPwdStore in one of the following ways: As a start-up parameter of hdbstudio.exe (for example, in the program shortcut properties of a

Windows installation) As a parameter in the hdbstudio.ini configuration file



Results

User passwords cannot be stored in the Eclipse secure storage. When the SAP HANA studio is opened, systems appear in a logged-off state in the Systems view.To connect to the system, the user must log on to it by choosing Log On from the context menu and then entering his or her password. The password is stored temporarily for the duration of the session only. The session ends when the user closes either the SAP HANA studio or the individual system by choosing Log Off from the context menu.

2.1.7 Organize the Systems View Using FoldersIf you add several SAP HANA systems in the Systems view, you can define a folder structure to organize them.

Procedure

1. From the main menu, choose New Folder .2. Enter a folder name.3. In the Systems view, move your system to the new folder using drag and drop.4. Repeat this procedure until you have added all your systems.

Results

Once folders have been created, you can assign any new systems to a folder when you add them.

2.1.8 Search for SAP HANA SystemsIf you have a large number of systems registered in the Systems view, you can search for a specific system to access it more quickly.

Procedure

1. From the Systems view toolbar, choose the (Find System) button.2. Enter a search string.

You can also use * or ? as wildcards.Matching systems are displayed.



3. Select the system you were searching for.You can select several systems in the search results by pressing the CTRL key while selecting. You can use this, for example, to mark duplicate systems.

4. Choose whether you want to open the selected system in the Administration editor and/or the SQL console.

Results

The system opens in the Administration editor and/or SQL console. If you did not select either of these options, the system is only highlighted in the Systems view.

2.1.9 Export a List of SAP HANA SystemsYou can export a list of your SAP HANA systems from the SAP HANA studio as an XML file and then import it into another instance of the SAP HANA studio or use it as system archive to which other users can link.

Procedure

1. From the main menu, choose File Export... .2. Expand the SAP HANA folder and choose Landscape.3. Choose Next.4. Select the systems you want to export and enter a target file location.5. Choose Finish.

Results

The list of systems and their properties (name, description, host name, instance, and so on) is exported as an XML file to the specified location.

Related Information

Link a Centrally-Stored Archive of SAP HANA Systems [page 33]To allow users who work in the SAP HANA studio to connect efficiently to multiple SAP HANA systems, you can manage a list of all systems in a centrally-accessible archive. Users can then simply link to this archive.



2.1.10 Import a List of SAP HANA SystemsYou can import a list of SAP HANA systems that you previously exported from another instance of the SAP HANA studio.

Procedure

1. From the main menu, choose File Import... .2. Expand the SAP HANA folder and then choose Landscape.3. Choose Next.4. Choose Browse... and select the file containing the list of systems that you want to import.5. Select the folder into which you want to import the file.6. Choose Finish.

Results

The systems are added in the Systems view of the SAP HANA studio.To be able to access the systems, the password of the connecting user specified in the system properties must be available in the user's local Eclipse secure storage. If this is not the case, you must log on to the system.

NoteThe file containing the list of systems does not contain user passwords.

2.1.11 Disable Default Filtering of SchemasUsers with the system privilege DATA ADMIN and/or CATALOG READ, for example database administrators, may not see all schemas in the Systems view of the SAP HANA studio since a default filter is applied.

Context

In the Systems view of the SAP HANA studio, users only see those schemas for which at least one of the following criterion applies: The user has at least one object privilege on the schema. The user has at least one object privilege on at least one object in the schema.



The user owns at least one object in the schema.

NoteFor all privilege checks, not only privileges directly granted to the user but also privileges granted to one of his or her roles (or to roles in these roles) are considered.

As a result, users with the system privilege DATA ADMIN and/or CATALOG READ cannot see all available schemas.If, as a database administrator, you need to see all available schemas, you must disable this default schema filter.

Procedure

1. In the Systems view, right-click Catalog and choose FiltersThe Filter for Schema dialog box opens.

2. Select Display all schemas.3. Optional: Specify a filter pattern to reduce the number of schemas displayed.

This is useful if the total number of schemas exceeds the number of displayable items in the tree (configured under Preferences Catalog ). If this is the case, then you will not see all schemas at once and will have to browse.

4. Save and apply the filter by choosing OK.

Results

Schemas are displayed filtered according the specified filter pattern.

2.1.12 Start the SAP HANA Studio with Immediate System LogonThe SAP HANA studio program accepts command line parameters that allow you to specify the system to be connected to immediately on startup. This can be useful to system administrators, as well as to other programs that call the SAP HANA studio.

Prerequisites

You have a database user in the SAP HANA system that you want to log on to.



Procedure

1. Launch the SAP HANA studio from its installation directory passing the following start parameters:Option Description-h Host name-n Instance number-u User name

NoteUser names containing special characters that represent conjunction or redirection characters in the command line program must be enclosed in double quotation marks ("..."), regardless of where the special character appears in the user name.

Example hdbstudio.exe -h hana1 -n 02 -u DBADMIN hdbstudio.exe -h hana1 -n 02 -u "&test"

The SAP HANA studio opens.

2. If prompted, enter your user password.

Results

The system is added in the Systems view (if it is not already there), and you are logged on.

2.1.13 Configure SSL for SAP HANA Studio ConnectionsIt is recommended to secure communication between the SAP HANA studio and the SAP HANA database using the secure sockets layer (SSL) protocol.

Prerequisites

You have configured the SAP HANA database for secure external communication. For more information, see SSL Configuration on the SAP HANA Server in the SAP HANA Security Guide.

You have added the SAP HANA system in the SAP HANA studio. For more information, see Add an SAP HANA System.



Context

The SAP HANA studio communicates with the SAP HANA database via the JDBC client interface. The client-side configuration of the SAP HANA studio uses Java SSL properties.

Procedure

1. Using the keytool command line tool, import the trust store file that contains the server root certificate into either the Java keystore or your personal user keystore.By default, the SAP HANA studio client validates the server certificate(s) against the root certificate stored in the Java keystore of the running VM (virtual machine). This keystore is part of the Java installation and is located in the Java home directory under ${JAVA_HOME}/lib/security/cacerts (Linux) or %JAVA_HOME%/lib/security/cacerts (Windows).However, it is not recommended that you store the root certificate in this keystore, but in your personal user keystore instead. The user key store is located in the home directory of the current operating system user. The file name is .keystore.

2. Enable and configure SSL communication

sap hana administration guide en

Documents