Hello and welcome to the SAP HANA Academy.
I am Denys van Kempen
and the topic of this video tutorial series
is SAP HANA 2.0
In this video tutorial, we will discuss
what's new for administration.
It is a big topic for this release
and to avoid the video getting too long
I have cut them up.
This is the first one about system administration.
The others will be out backup and recovery,
high availability,
and performance monitoring and analysis.
A good place to start to learn about what’s new with HANA 2.0
are the release notes,
which you can find on the SAP Help Portal
help.sap.com
Technology Platform
and then scroll down to SAP HANA Platform (Core).
There is a central SAP note for HANA 2.0
that's 23 80 257,
which displays in the SAP One Support Portal
and requires a SAP account
but there is also this guide,
which describes all new features
About documentation changes, we can be short.
Both the Technical Operation Manual (TOM)
and the Database Control Center Guide (DBCC)
are no longer included in the documentation set.
The topics of the TOM have been merged
with the HANA Administration guide
and the DBCC guide is obsolete
as it is now replaced by the HANA cockpit 2.0
Some changes as well to the Administration guide
Most significant, maybe, is that the whole description of network zones, and port and connections,
which before was documented in the Master Guide is now added to the chapter
Landscape Management and Network Administration of the Administration Guide.
The text has not changed, so if you are already familiar with this topic
there is nothing to do, but if you are not familiar yet, this is the place to read up about it.
Then for system administration we have three main topics:
HANA cockpit
Multitenant Database Containers
and Workload Management
and some smaller topics like client-side routing
and hdbsql.
Before we look at cockpit, two remarks
I already mentioned that the DBCC guide is gone,
well the tool is gone as well, of course
Database Control Center came as a delivery unit,
which you had to install and should you have done this
for HANA SPS 12 or 11
then SAP recommends that you remove it
and how you can do that is documented in this note 2385193
The HANA 1 cockpit also came as a delivery unit but was installed automatically.
and the packages are still there in HANA 2 but without any content, so just that you know.
Then before we switch to the new HANA cockpit, two remarks:
There is a central release note (2380291)
for the fine print
known issues and documentation corrections
and in the note is also mentioned that there is a
separate guide to install and update the HANA cockpit.
So what’s new?
Cockpit for HANA 1 was part of the HANA database.
So if you did a shutdown of the database your cockpit would also be gone
and if you had a couple of HANA systems
you also had a couple of HANA cockpits
with different URLs.
Now, the umbrella proposed at the time was the
was the Database Control Center,
I already mentioned it,
former Sybase technology
updated with a new Fiori UI.
but this has now been re-engineered
into a complete new cockpit.
It is no longer part of the HANA system
and it is no longer hosted by the classic XS engine either.
It runs on XS advanced and is hosted by a small HANA system
separately on the side, based on HANA express.
Supports both HANA SPS 12 and HANA 2.0.
Just like before, and just like with HANA studio, most of the activity uses a SQL client connection with a
named database user, except for some functionality that uses the HANA operating system account
adm.
For example, to stop and start a HANA system,
you cannot do that with SQL, obviously,
or to restore a database backup, load trace files, stuff like that.
You can create groups of systems using the HANA cockpit services,
this is the Database Control Center part.
and then with the cockpit manager
you can do the same type of cockpit administration
as with HANA 1 with some enhancements and
improvements.
So, let’s take a look.
Here we have the cockpit manager.
You connect with the cockpit admin user, created at install time.
And here you register resources
You specify the host, instance number
single container, multiple container
and then the technical user any resource group
and any contact information.
Then from the manager you open the SAP HANA cockpit.
Home page shows you high priority alerts
and here you can also monitor aggregate health
or compare system configurations.
New is also the Database Explorer to browse database objects or execute SQL
similar like HANA studio or the Web IDE for HANA
There is online help, of course, from the Administration Guide for the cockpit
and then, if you zoom in on your resource group
you get the high priority alerts
for that resource group
any availability issues
and from there on you can connect directly to your HANA system.
For those that have used cockpit before, this will look similar.
We have tiles for overal database status, for the alerts, performance KPI's like memory usage,
number of sessions and number of threads and when
you select a tile an app opens, for example, Manage Services
or the Performance Monitor
Scroll down a bit and you will find links to Manage Users, for example.
You can now create and configure your users directly from the HANA cockpit;
and you can also configure system properties, the INI files.
You can also launch the cockpit for offline administration.
This is for when HANA is not started
and this connects to the SAP host agent on the HANA server.
so it is the same URL as before
and here you get your trace files and troubleshoot
and we can also connect to the Platform Lifecycle Management tool
to install additional software and perform lifecycle management tasks
also connects to the SAP host agent.
Both of these tools are not new but what’s new it is all integrated with the HANA cockpit.
Then there are also sections about security, performance management,
and the HANA options, like smart data integration
and these topics will be addressed in other videos in this playlist.
So let's return to the What's New document.
We talked about the cockpit.
Then we have Multitenant Database Containers:
Three bullets: you can now restore a single container database to a tenant;
you can disable secure networking for copy/move operations;
and you enable the performance trace for cross database queries.
First of all, you can now restore a backup of regular, single-container system into a tenant database.
Before, this was way more complex as you had to setup replication first and convert single-container
system into multitenant and so one, lots of work.
Now, if you have a database backup, it doesn’t matter if it is from a single or multitenant
system, you can restore it into a tenant.
With the next release or so, multitenancy will be the default mode, so it is a good thing
that this has been made easy.
Another administration task that has been simplified is the copy and move process of
tenant databases.
Normally, this requires setting up certificate configuration first in order to enable communication
between the systems you want to copy from and copy to.
Now this is a good thing, of course, for production systems but for testing and training this
was a bit cumbersome.
With 2.0, you can now disable the secure network communication for the copy and move process.
Just set the system parameter enforce ssl database replication to off
and the prerequisite is that both source and target database are not configured for high isolation
Third enhancement is that you can now enable the performance trace for several tenant databases
at the same time so you can analyze cross-database queries.
As a reminder, by default, on a multitenant database system, the tenant databases are
completely isolated from each other.
You can even configure the tenant for high isolation, I just mentioned it, so the database
runs under its own operating system account.
If there is a requirement to query data from another tenant database, you have to explicitly set
this up and if you have done so and you want to investigate
response times for certain queries, you can now enable cross-database performance tracing.
Next, is Workload Management.
Great new feature here: admission control, to manage peak load.
As an administrator, you can set a limit to the amount of resources - CPU and memory - that
all the processes together are allowed to use
and this avoids that your system becomes unresponsive due to too much activity.
Prerequisite is that you enable in the global INI file in the section resource_tracking both enable_tracking and memory_tracking - this switches on, in fact, workload management
and then in the indexserver.ini, under admission_control you need to set enable to the value of true.
and set the threshold for CPU and memory
or except the defaults.
There is a queue threshold, at which point requests will no longer be accepted but will
be queued first and a reject threshold, which will reject
the request, of course.
There are some other parameters relevant to set this up:
averaging factor, dequeue size, which is all documented in the Administration
Guide, in the Workload Management section.
Here you can also read about the query timeout feature.
This allows a developer to programatically cancel client queries which take too long
to run, when the query appears to hang or loop or something.
It uses standard API’s, for example, for JDBC it is java.sql.statement.setQueryTimeout.
Then before wrapping up, two smaller topics:
Client-side statement routing for partitioned tables
and a couple of new command line options
vfor hdbsql.
Client-side routing for partition tables has been implemented
for both hash and range partitioning.
If the column in the WHERE equal clause matches the partitioning column, or columns
this optimisation is activated automatically
and this will improve performance as the client now routes the request directly
to the correct indexserver.
Here we see an example for range partitioning.
Then a couple of command line options have been added and changed
for hdbsql, the HANA interactive terminal command line tool
used mostly for scripting and batch processing.
The command line reference is included here in the Administration Guide
but these are also included with the tool itself.
hdbsql '-?'
'-V' for substitution variables is new
'-quiet'; do not print welcome screen
and the output format option: '-oldexectimes'
to get the HANA 1 execution timing.
HANA 2, by default, includes also the time to fetch the result set
then also the default length for binary and long columns is now 32 bytes or characters,
which you can change with this flag '-b' and '-b all' will get you the whole column.
So, now you know.
OK, so much for what’s new for administration with SAP HANA 2.0
part 1 system administration
You can find more video tutorials on our Youtube Channel,
If you would like to be informed about new video tutorials, please subscribe to our channel.
You can connect with us on LinkedIn or follow us on Twitter, as well for updates
and we also have a page on Facebook and Google+
If you are watching this video on YouTube,
do not hesitate to leave your comments to the video page
and if you like, give us your vote on his video.
Thank you for watching.