Hello and welcome to the SAP HANA
Academy. My name is Denys van Kempen and
in this video tutorial series we will
discuss what's new with SAP HANA
SPS 12. The topic of this video is system
administration Platform Lifecycle
Management. Apart from the smaller fry we
have three new main features for
Platform Lifecycle Management SPS 12.
First one is the conversion of a
standard SAP HANA system to a
Multitenant Database system. Second host
role configuration and third a new
option to perform a system verification.
Now Multitenant Databases were
introduced with SPS 9 or 10 in
production and there is a video out
there on the SAP HANA Academy that
explains how you could convert a
standard, a regular SAP HANA system to a
Multitenant Database system and for
that you need to perform several tasks
on the command line using the hbdnsutil
tool with the flag convert to
multiDB and then there are some other
activities you have to do. Which of
course are all explained in this video.
As of SPS 12 you no longer need to do
this. It’s far easier. You can use the
resident SAP HANA lifecycle
management tool to perform this with a
single click and it's available both on
the web, on the windows and on the
command line. Same is true for changing
host roles. Now what's a host rule. If you
have a distributed system so with
multiple hosts supporting a single SAP
HANA instances, a single SAP HANA
database. You can define different host
roles, default host role is a worker
host but you can also set it to a
standby host. In a high available
landscape this allows for some
flexibility. You will see the roles that
are available. Note that in production
environments a SAP HANA host must only
have one host role except for the XS
advanced runtime. So we have the database
worker. We have two database standby. We
have the extended storage worker, extended
storage stand by for dynamic tiering. We
have a standby in a worker for ASE
remote data sync streaming and XS
advanced. Rows are set at installation
times and could be changed in the
command line. As of SPS 12 we can also do
it with the resident lifecycle
management tool and we’ll take a look at that
in a moment. Then finally as you can see
documented here, this is a new feature.
You can check the installation of a SAP
HANA system using the lifecycle
management resident program in the
command line interface for
troubleshooting and that's with the -
- action = check installation
flag. So let's take a look. I've started
there the SAP HANA Platform Lifecycle
Management tool web interface. Which is
the same look and feel as the SAP HANA
cockpit but this one is actually hosted
by the SAP HANA host agent running on
port 11 28 or 29 and with this tool we
can perform several typically post
configuration tasks like performing a
system update or install or update
additional components. Now new as of SPS
12 apart from the download components
tab which we've discussed in another
video is convert to Multitenant
Database containers and here the at
host role and remove host roll. If we
briefly switch to the lifecycle
management Windows tool we see the same
options here. Convert to Multitenant
Database containers remove host roles
and add host rules and the same options
here on the command line. Regardless of
whether you're using command line
Windows or web the dialogues are the
same. Select the activity provide the
password for the operating system
account the system administrator SIDADM
and the password for the system database
user and it's typically system. Selecting
this gear will enable us to provide
advanced parameter configuration. Note
that this is only available on the web
UI. This is not available on command line
or in the Windows UI and here we
can for example select to import
delivery units in the system database to
not start an instance
after the reconfiguration and to
not start a tenant database after
reconfiguration. Plus the timeouts to
start and stop an instance. I will leave
the default values active here. I’ll
select next. Step two will show me the
review and confirm screen with the
notification that the HANA system
will be restarted and that converting to
a multiple container system is permanent.
It cannot be reversed. Select run and
will get a progress indication of the
conversion process which starts with the
shutdown of the HANA system here. Now
while this is running let's switch to
another SAP HANA instance and here
take a look at the add host roles and
remove host roles. As mentioned host
roles play role in a high availability
environment we have multiple hosts. This
is a single host system. So if I select
host roles I will be informed to throw
out any additional roles which can be
assigned. However I've added to the
system an XS advanced runtime
worker host and that's the one we can
remove. The database worker will stake as
that's the default role. I will be
prompted to provide the operating system
administration password with a review
and confirm screen and selecting remove
roles will remove that role. Now let's
switch back to our initial system. The
system where we started in a dedicated
mode and convert it to a Multitenant
Database container system and restarted
again. The original SAP HANA database
will be tenant one. So a new system
database has been created and because we
selected it it's the default flag the
delivery units that were initially
imported into the SAP HANA database are
now imported into this new system
database as well. This is all standard
content that ships with SAP HANA.
Removing host roles also involves
restarting SAP HANA. So that will take
some time and when that's done we get
our execution summary with a locked file
providing detailed information. A third
topic was the check installation action.
This is only available on the command
line for SPS 12. Run it you will be
prompted again to provide the system
administrator password. Note that I am
running this command as a root user and
here we can see that everything is fine
apart from the permissions on the SAPUI5
libs directory which has the mode 775
and 755 is the maximal mode allowed. This
for security purposes. Of course 7 is
read write execute and this should only
be granted to the system administrator
user, the SIDADM user. For the group and
for the others it should be 5. So only
read and execute but not write. If we run
it again. No more errors are returned and
our system is clean. Let's minimize this
screen and verify the execution summary
of the Multitenant Database container
conversion which took a couple of
minutes mainly to import the new
delivery units in the system DB. The
actual conversion is very quick. So now
we have a Multitenant Database system
and if we try to convert it we are
informed that the SAP HANA system is
already a Multitenant Database
container system because it's mentioned.
You can go from A to B but you can go
back. New features for Platform Lifecycle
Management are documented in what's new
guide the release notes and how to
actually perform the tasks is documented
in the SAP administration guide. Both
guides you can download or read free of
charge on the SAP help portal at help
.sap.com. Thank you for watching
this SAP HANA Academy video.