SAP HANA SPS 08 - What’s New? Administration & Monitoring

1. SAP HANA SPS 08 - What’s New?
Administration & Monitoring
SAP HANA Product Management May, 2014
(Delta from SPS 07 to SPS 08)

2. © 2014 SAP AG. All rights reserved. 2Public
Content
This presentation provides an overview of the changes regarding administration, monitoring and
supportability of the SAP HANA database between the SPS 07 version and the SPS 08 version.
It covers changes to the SAP HANA studio administration perspective and changes to the SAP HANA
database.
Functionality of other SAP HANA studio perspectives (like the SAP HANA Modeler) is not covered in
this presentation.

3. © 2014 SAP AG. All rights reserved. 3Public
Agenda
Improved Monitoring and Supportability
 New monitoring overview: SAPUI5 based dashboard
 Improved diagnosis information for blocking situations
 New options to collect diagnosis information
 Improved resource monitoring
 Improved statement analysis
 More safety for production systems: warnings are displayed, when data is to be changed
 Improved usability
 Statistics service enhancements
 SLD extension

4. © 2014 SAP AG. All rights reserved. 4Public
Agenda
Additional Features
 Support for planning engine views/models
 Import of geospatial information (shapefiles)
 Extended system replication configuration
 New/enhanced monitoring views

5. Improved Monitoring and
Supportability

6. © 2014 SAP AG. All rights reserved. 6Public
Improved Monitoring and Supportability
New Monitoring Dashboard
New SAPUI5 Based Monitoring Dashboard
 Web-browser-based dashboard that visualizes key
aspects of system health and configuration, for example:
– Current high and medium priority alerts
– Memory and CPU usage
– Availability of data backups
 Drill down to views containing more detailed information
 Role sap.hana.admin.roles::Monitoring is required, which
is not granted by default to the standard MONITORING
role

7. © 2014 SAP AG. All rights reserved. 7Public
HANA
Improved Monitoring and Supportability
Improved Diagnosis Information for Blocking Situations
Emergency Support Mode
 SAP HANA studio collects
information about systems using SQL
 When a system cannot be reached
by SQL or it is experiencing major
performance issues due to high load
or blocking situations, information
can instead be collected using the
connection of the SAP start service
(sapstartsrv).
 The Administration editor diagnosis mode provides access to:
– The operational status of all services in the system
– Log and trace files
– The collection of diagnosis information into a zip file
– All connections, transactions, blocked transactions, and threads in the system
 If necessary, you can cancel individual connections and transactions, or even
cancel all transactions.
sapstartsrv
python
Indexserver
hdbcons

8. © 2014 SAP AG. All rights reserved. 8Public
Improved Monitoring and Supportability
Improved Diagnosis Information for Blocking Situations
Improved Information for Cancel Status
 System view M_CONNECTIONS, column CONNECTION_STATUS shows if the cancellation of a connection has been
requested and if the cancellation is already ongoing.
 The following values are possible:
– IDLE (CANCEL REQUESTED)
The connection is idle, a cancellation has been requested, but the connection is not yet canceling
– RUNNING (CANCEL REQUESTED)
The connection is working on a request, a cancellation has been requested, but the connection is not yet canceling (meaning
not in rollback yet)
– RUNNING (CANCELING)
The connection is working on a request, a cancellation has been requested, and the connection is already canceling
(meaning already in rollback)

9. © 2014 SAP AG. All rights reserved. 9Public
Improved Monitoring and Supportability
Improved Diagnosis Information for Blocking Situations
Runtime Environment Dump File Collection
 To analyze issues e.g. if the system is unresponsive, RTE dump files can
be created
 On the Diagnosis Files tab, choose Diagnosis Information -> Collect…
 You can specify:
– From which index server(s) RTE dump files are to be collected
– The number of RTE dump file sets to be collected
– The interval (in minutes) at which RTE dump files are to be collected
 For each specified index server, an RTE dump file containing information
about threads, stack contexts, and so on is created and stored in the file
indexserver_<SAPLOCALHOST>_<PORT>_runtimedump.trc.

10. © 2014 SAP AG. All rights reserved. 10Public
Improved Monitoring and Supportability
Enhanced Diagnosis Information Collection
New Options to Collect Diagnosis Information
 For the collection of all diagnosis information, it is now possible to
enter a specific time period, by default the last 7 days.
 Information from system views can be included when the database
is online (this option is not available in diagnosis mode).
Monitoring views for the planning engine are then included as well.

11. © 2014 SAP AG. All rights reserved. 11Public
Improved Monitoring and Supportability
Improved Resource Monitoring
Redesigned Memory
Allocation Statistics
 Components shown in
Memory Allocation Statistics
now have more
comprehensible names
 Allocator section has been
renamed to Subcomponents
and now also includes row
store information
 Subcomponents are now
grouped and displayed in a
collapsible tree view

12. © 2014 SAP AG. All rights reserved. 12Public
Improved Monitoring and Supportability
Improved Resource Monitoring
Statement Memory Tracking and Statement Memory Limitation:
Avoid Uncontrolled Statement Memory Allocation
 The peak memory consumption of a statement can be tracked und displayed in Expensive Statements.
 Resource consumption collection has to be enabled manually:
– Configuration file global.ini, parameters enable_tracking and memory_tracking
 Additionally the HANA administrator is able to define a global statement memory limit in the database:
– Configuration file global.ini, parameter statement_memory_limit
 If a statement exceeds the memory limit, it will be cancelled

13. © 2014 SAP AG. All rights reserved. 13Public
Improved Monitoring and Supportability
Improved Resource Monitoring
Enhanced Lock Classification
 Locks are classified by component
 Monitoring views M_SERVICE_THREADS and M_SERVICE_THREAD_SAMPLES contain this component in column
LOCK_WAIT_COMPONENT to provide a hint on the purpose of the lock blocking the current thread.
 Column Lock Wait Component can also be displayed on Performance tab -> Threads
 Examples are:
– Network IO
– File IO
– Basis System
– Calculation Engine
– Join Engine

14. © 2014 SAP AG. All rights reserved. 14Public
Improved Monitoring and Supportability
Improved Statement Analysis
Extended Content of Plan Visualizer
 For column store queries, the visualization of physical
table access plan is now completed
 This includes the display of inverted index access
and predicate evaluation

15. © 2014 SAP AG. All rights reserved. 15Public
Improved Monitoring and Supportability
Improved Statement Analysis
Operator List for Plan Visualizer
 The Operator List lists detailed characteristics of all operators within a current plan (visualized + executed).
 It can be used to dynamically explore the operator set along user defined filters in order to pinpoint specific operators of
interest.
 For example you might:
– Filter all operators
consuming a certain
minimal CPU time
– Then order those
operators along the
number of input rows
– Further restrict the filter
to a specific operator
type (e.g. "Column
Search”)
– And then double-click on an operator of interest in order to check its positioning within a visualized plan

16. © 2014 SAP AG. All rights reserved. 16Public
Improved Monitoring and Supportability
Improved Statement Analysis
Plan Cache: Keep Set of Parameters
 The parameter set of a prepared statement is stored in monitoring view M_SQL_PLAN_CACHE_PARAMETERS to allow for
the easy re-execution of a specific query:
– First parameter set is stored when the total execution time of the statement is greater than parameter
plan_cache_parameter_sum_threshold (default 1000ms).
– Afterwards, the parameter values will be updated if the statement’s single execution time is greater than parameter
plan_cache_parameter_threshold (default 100ms) and its last captured execution time.
 Parameters to enable this feature:
– plan_cache_parameter_enabled: Activate/deactivate
capture of parameter values of prepared statements
– plan_cache_parameter_for_lob_enabled: Activate/
deactivate capture of BLOB/CLOB/NCLOB
parameter values.
 In the Admin editor of SAP HANA Studio on tab
Performance -> SQL Plan Cache the stored parameter
set is used when you choose “Visualize Plan” or
“Prepare in SQL Console”

17. © 2014 SAP AG. All rights reserved. 17Public
Improved Monitoring and Supportability
Improved Statement Analysis
Direct Access to Plan Visualizer
 It is now possible to display the visualized plan for a specific statement in the Expensive Statements Trace or SQL Plan Cache
view

18. © 2014 SAP AG. All rights reserved. 18Public
Improved Monitoring and Supportability
Improved Statement Analysis
Link Between SQL Plan Cache and Expensive Statements Trace
 Navigation between the Expensive Statements Trace and the SQL Plan Cache view has been improved
 You can display a specific statement in the other view using the context menu option Navigate To

19. © 2014 SAP AG. All rights reserved. 19Public
Improved Monitoring and Supportability
System Usage Type
Display of System Usage Type
 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.
 SAP HANA studio evaluates this parameter to warn users when they
are about to perform critical operations on systems with usage type
production (for example, execute SQL statements, stop or restart the
system, perform a data backup, and so on)
 This does not prevent data manipulation in productive systems,
however it keeps reminding you to be careful

20. © 2014 SAP AG. All rights reserved. 20Public
Improved Monitoring and Supportability
Improved Usability
User-Defined SQL Statements for System Monitoring
 For customized monitoring, it is possible to save
your own SQL statements on the System Information
tab of the Administration editor for convenient
repeated execution.
 You can create and save individual statements
directly on the System Information tab.
 Alternatively, you can import multiple statements as
text or ZIP archive files
 To organize large numbers of statements
meaningfully, you can define a folder structure.
Predefined statements are stored in the System
folder.
 When you save the Administration editor, all
statements, together with the defined folder structure,
are saved to a single XML file and are available on
the System Information tab of the Administration
editor for all systems registered in the SAP HANA studio.

21. © 2014 SAP AG. All rights reserved. 21Public
Improved Monitoring and Supportability
Improved Usability
Reworked Systems View Context Menu
 The Systems View context menu has been re-structured by categories to provide a better overview and easy access to all
actions for the user.
 Old structure: New structure:

22. © 2014 SAP AG. All rights reserved. 22Public
Improved Monitoring and Supportability
Improved Usability
Command Line Parameters for SAP HANA Studio
 The SAP HANA studio program accepts command line parameters that allow you to specify the system to be connected to
immediately on startup.
 Call the SAP HANA studio executable with parameters for host, instance number and user:
dbstudio.exe -h <host> -n <instance number> -u <username>
 This can be useful to system administrators, as well as to other programs that call the SAP HANA studio, as this allows such
programs to pass connection information to the studio.

23. © 2014 SAP AG. All rights reserved. 23Public
Improved Monitoring and Supportability
Statistics Service
Improved Documentation
 All statistics service views are now commented in the catalog, check the view definition to see the comments
New Alerts
 Expiration of database user passwords: checks if any password expires soon
 Total memory usage of row store: determines the current memory size of the row store per host
 Table growth of row store tables: determines the growth rate of row store tables
 Row store fragmentation: check for fragmentation of row store
 Inconsistencies in schemas: check for schema inconsistencies
 Runtime of log backups currently running: determines if the most recent log backup terminates in the given time.
 Enablement of automatic log backups: determines whether automatic log backup is enabled.
 Storage snapshot is prepared: determines if the period, during which the database is prepared for a storage snapshot,
exceeds a given threshold.
 Total memory usage of table-based audit log: determines which percentage of the effective allocation limit is being
consumed by the database table used for table-based audit logging.
 Granting of SAP_INTERNAL_HANA_SUPPORT_ROLE: determines if the internal support role
(SAP_INTERNAL_HANA_SUPPORT) is currently granted to any database users. The administrator should check if the
corresponding users still need the role.

24. © 2014 SAP AG. All rights reserved. 24Public
Improved Monitoring and Supportability
Solution Manager Integration
SLD Extension
 A new (optional) software component can now be registered to SLD using the SAP HANA SLD Data Supplier: SAP HANA
Smart Data Access.
 The AFL package has been split into several packages. Therefore the AFL reporting for SLD has been adapted as well.

25. Additional Features

26. © 2014 SAP AG. All rights reserved. 26Public
Improved Monitoring and Supportability
Additional Features
Support for Planning Engine
 EPM models and EPM query sources are shown
in the Systems view in the catalog tree.
 If needed for support reasons, a planning engine
trace can be activated. If parameter
enable_export_wizard in section planningengine
of file indexserver.ini is set to true, the
Planning Engine Trace section is available on
the Trace Configuration tab.
 Monitoring views for planning engine are contained
in the diagnosis information collection.

27. © 2014 SAP AG. All rights reserved. 27Public
Improved Monitoring and Supportability
Additional Features
Import of Geospatial Information
(shapefiles)
 SAP HANA supports the ESRI shapefile format. ESRI
shapefiles are used to store geometry data and attribute
information for the spatial features in a data set.
 You can import ESRI shapefiles into dedicated column-
store tables using the import feature of SAP HANA studio:
– From the main menu, choose File -> Import.
– Select import source SAP HANA -> ESRI Shapefiles.
 The shapefiles are imported into column-store tables in
the specified schema.
 Each shapefile corresponds to one table.

28. © 2014 SAP AG. All rights reserved. 28Public
Improved Monitoring and Supportability
Additional Features
Extended system replication configuration
 To offer higher levels of availability you can link
together multiple systems in a multitier system
replication landscape.
 After setting up a basic system replication
scenario you add a third system to provide
another level of redundancy.
 In a multitier setup the primary system is
always on tier 1, a tier 2 secondary has a
primary system as its replication source and
a tier 3 secondary has the tier 2 secondary as
its replication source.
 The tier 3 secondary can now also be added
using SAP HANA studio.
 On each node only those actions are provided,
which are currently possible – depending on the
system status.

29. © 2014 SAP AG. All rights reserved. 29Public
Improved Monitoring and Supportability
Additional Features
Enhancements regarding monitoring views
 New monitoring view M_CS_LOADS shows when which column of a column store table has been loaded into memory
 New monitoring view M_MVCC_OVERVIEW provides information about the row store multi-version concurrency control
(MVCC) manager
 New monitoring view M_TABLE_SNAPSHOTS provides information about tables which are blocked by table-wise garbage
collection
 Monitoring view M_TRANSACTIONS column ACQUIRED_LOCK_COUNT now also contains statistics for column store
 System views can now be exported in CSV format

30. © 2014 SAP AG. All rights reserved. 30Public
Disclaimer
This presentation outlines our general product direction and should not be relied on in making
a purchase decision. This presentation is not subject to your license agreement or any other
agreement with SAP.
SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and
SAP’s strategy and possible future developments are subject to change and may be changed
by SAP at any time for any reason without notice.
This document is provided without a warranty of any kind, either express or implied, including
but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or
non-infringement. SAP assumes no responsibility for errors or omissions in this document,
except if such damages were caused by SAP intentionally or grossly negligent.

31. © 2014 SAP AG. All rights reserved. 31Public
How to find SAP HANA documentation on this topic?
SAP HANA Platform SPS
 What’s New – Release Notes
 Installation
– SAP HANA Server Installation Guide
 Security
 Administration
– SAP HANA Administration Guide
 Development
– SAP HANA Developer Guide
 References
– SAP HANA SQL Reference
• In addition to this learning material, you find SAP HANA documentation on
SAP Help Portal knowledge center at http://help.sap.com/hana_platform.
• The knowledge center is structured according to the product lifecycle: installation, security, administration,
development. So you can find e.g. the SAP HANA Server Administration Guide
in the Administration section and so forth …

32. Thank you
Contact information
Melanie Handreck
SAP HANA Product Management
AskSAPHANA@sap.com
To get the best overview of what’s new in SAP HANA SPS 08, read this blog.

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