Documente Academic
Documente Profesional
Documente Cultură
Unit 1: Monitoring
Monitoring
Individual database management Monitoring in the SAP HANA cockpit
Although SAP HANA databases can self-monitor and generate alerts, it is still critical that
database administrators regularly monitor the operation of SAP HANA databases
Change columns
displayed in table
View CPU usage in
Performance Monitor
Individually stop
Drill down to see services
Memory Allocation
Analysis application
Drill down from Overall System Database Status See key information about systems such as status,
tile on Overview page start time, alerts, CPU and memory usage
Start missing services, kill service, remove service Customize columns to show used memory, effective
or (only for tenant databases) add a service allocation limit, allocated shared memory, virtual
memory on host, size of caches, and more!
2017 SAP SE or an SAP affiliate company. All rights reserved. PUBLIC 4
Monitoring
Performance Monitor CPU usage Correlate alerts in
CPU usage with graph
Clicking the Memory Usage and Disk Usage tiles drills down
to the Performance Monitor
Graphs are automatically populated with relevant KPIs
Monitoring
Monitoring performance
Monitor table usage
Monitor expensive statements
Open SQL plan cache
Open blocked transactions
Monitor Network
open@sap.com
2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies st rategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 3: Managing Individual Databases
Unit 2: Security
Security
Individual database security in SAP HANA
DBA
Authentication Auditing
Authenticate users using Monitor and record selected
passwords and a diverse range Certificate Management actions performed in your
of SSO options Secure internal and external database
communication channels, user
authentication mechanisms
open@sap.com
2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies st rategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 3: Managing Individual Databases
Unit 3: Alert Management
Alert Management
Alerts in the SAP HANA cockpit
open@sap.com
2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies st rategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 3: Managing Individual Databases
Unit 4: Backup and Recovery
Backup and Recovery
Backup and recovery in SAP HANA
SAP HANA holds the bulk of its data in memory for maximum performance,
but still uses persistent storage to provide a fallback in case of failure
Full data backup A full data backup contains all current data
All data Old data that is no longer valid but might still be physically
present in the data volumes is not part of the data backup
Incremental backup
Delta backups contain data that was changed since an
Changed data since
the last data backup earlier data backup
(full or delta) Two types: incremental and differential
Delta backups contain actual data, in contrast to log backups,
Differential backup
which contain redo log entries (= sequence of changes)
Changed data since
Delta backups can be used together with a snapshot for system
the last full data
recovery
backup
Create complete,
differential, or
incremental backups
Set the recovery target to restore data from: Choose between default
backup catalog location
Most recent state or an alternative location
A specific point in time
Choose between different options for delta backup usage, If you have multiple
backups, you can choose
backup availability checks, and initialization of log area which one to use
SAP HANA databases must be offline to be recovered
Recovery is always initiated from the system database
Recovery for databases through SAP HANA cockpit is only
supported for SAP HANA 2 databases
It is highly recommended to back up SAP HANA cockpit prior to upgrades and after
registering a large amount of resources
Ensure important business information is not lost through regular backups
Backing up SAP HANA cockpit backs up the persistence and application server which
SAP HANA cockpit runs on
Recovering SAP HANA cockpit will restore the previous landscape configuration from
the selected backup
SAP HANA cockpit needs to be offline when recovering
open@sap.com
2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies st rategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Week 3: Managing Individual Databases
Unit 5: System Properties
System Properties
System properties in the SAP HANA cockpit
SAP HANA parameters are configuration options that can be used to influence the behavior
of SAP HANA in various ways
These parameters, which are contained in several configuration (*.ini) files, permit customization of the
system as a whole, individual tenant databases, hosts, and services
Configuration files are separated into sections. Sections bundle properties of the same category
Typical reasons for setting parameters are:
Individual security settings
Specific changes in behavior and operation of database services and components
Influencing system-wide resource consumption and workload execution
Properties can be configured at different levels or layers depending on the
configuration file. The following layers are available:
Default, host, system, database
INIFILE ADMIN
Add a new section
DATABASE ADMIN to
change the system
property of a tenant
database from the system
database
Compare configurations
between systems using the
Edit/delete
Configuration Manager changed values
(Week 2 Unit 3) Add new or restore their
key/values to a default value
selected section
Choose between
host, system, and
database level
Add a single or
multiple new
key/value pairs
open@sap.com
2017 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated
companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this docume nt or any related presentation, or to develop or release
any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies st rategy and possible future developments, products,
and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The
information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,
and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trade marks of SAP SE (or an SAP affiliate company)
in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companie s.
See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.