Skip to Content
Author's profile photo Denys van Kempen

SAP HANA SPS 12 What’s New: Platform Lifecycle Management – by the SAP HANA Academy

Introduction

 

In the upcoming weeks we will be posting new videos to the SAP HANA Academy to show new features and functionality introduced with SAP HANA Support Package Stack (SPS) 12.

 

For the complete list of blogs see: What’s New with SAP HANA SPS 12 – by the SAP HANA Academy

 

The topic of this blog is SAP HANA Platform Lifecycle Management new features.

 

For the related installation and update topics, see SAP HANA SPS 12 What’s New: Installation and Update – by the SAP HANA Academy

 

 

Tutorial Video

 

SAP HANA Academy – SAP HANA SPS 12: What’s New? – Platform Lifecycle Management – YouTube

 

 

 

What’s New?

 

Converting an SAP HANA System to Support Multitenant Database Containers

 

SAP HANA SPS 9 introduced the multitenant database container concept, where a single SAP HANA system contains one or more SAP HANA tenant databases. This allows for an efficient usage of shared resources, both hardware and database management.

 

At install time, you select the SAP HANA database mode: single container or multiple containers. Should you want to change the mode after the installation you have to perform a conversion. In earlier revisions, this task was performed on the command line with the tool hdbnsutil, as you can view in the following tutorial video:

 

 

As of SPS 12, an SAP HANA system can now be converted to support multitenant database containers using the SAP HANA database lifecycle manager (HDBLCM) resident program. With every installation of SAP HANA, hdblcm is included and enables you to perform common post-installation and configuration tasks. The tool is hosted by the SAP host agent and not, like the SAP HANA cockpit, by the SAP HANA database.

 

The Convert to Multitenant Database Containers task is available for all interfaces: web, windows and command line, but the web interface allows you to set advanced parameters:

  • Import delivery units into the system database (default = Y)
  • Do not start instance after reconfiguration
  • Do not start tenant database after reconfiguration
  • Set instance startup and shutdown timeout

 

During the conversion, the original system database is configured as tenant and a new system database is created. This operation is quick as we only need to shutdown the SAP HANA database, update a few settings and restart the instance. Importing the standard HANA content (web IDE, SAPUI5, cockpit, etc.) takes most time and can optionally be postponed or not performed all together.

 

Note that the conversion is permanent.

 

 

Screen Shot 2016-05-25 at 10.09.06.png

 

The web UI allows to set advanced parameters.

Screen Shot 2016-05-25 at 10.11.56.png

 

Adding and Removing Host Roles

 

It is now possible to add and remove host roles after installation in a single-host or multiple-host SAP HANA system using the SAP HANA database lifecycle manager (HDBLCM) resident program.

 

As of SPS 10, you have the option to install SAP HANA systems with multiple host roles – including database server roles and SAP HANA option host roles – on one host, or give an existing SAP HANA host additional roles during system update. This enables you to share hardware between the SAP HANA server and SAP HANA options. This concerns the MCOS deployment type: Multiple Components One System.

 

Typical roles are worker and standby and exist for the the SAP HANA database, dynamic tiering, accelerator for SAP ASE, and the XS advanced runtime. Additionally roles are available for smart data streaming and remote data sync.

 

Database worker is the default role. For distributed systems, with multiple SAP HANA hosts, systems can assigned the standby role for High Availability purposes.

 

Screen Shot 2016-05-25 at 10.36.03.png

 

System Verification Tool

 

You can check the installation of an SAP HANA system using the SAP HANA database lifecycle manager (HDBLCM) resident program in the command-line interface for troubleshooting. The check tool outputs basic information about the configuration of the file system, system settings, permission settings, and network configuration and you can use the generated log files as a reference in the case of troubleshooting.

 

Screen Shot 2016-05-25 at 10.05.38.png

 

Documentation

 

A new guide is available that documents how to configure, manage, and monitor an SAP HANA system that supports SAP HANA multitenant database containers

 

Screen Shot 2016-05-25 at 11.02.07.png

 

 

Documentation

 

For more information see:

 

SAP Help Portal

 

 

SAP Notes

 

 

 

SCN Blogs

 

 

 
 

Thank you for watching

The SAP HANA Academy provides free online video tutorials for the developers, consultants, partners and customers of SAP HANA.

Topics range from practical how-to instructions on administration, data loading and modeling, and integration with other SAP solutions, to more conceptual projects to help build out new solutions using mobile applications or predictive analysis.

For the full library, see SAP HANA Academy Library – by the SAP HANA Academy.

For the full list of blogs, see Blog Posts – by the SAP HANA Academy.

Assigned Tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Pikakala Sebastian
      Pikakala Sebastian

      Hi,

       

      Just a simple question that i have.. We are on HANA 1.0 SP12 and we are planning to get migrated to HANA 2.0 SP3...

      How do i see if my hana is single DB or MDC, how do i do this check ?

       

      Sebastian

      Author's profile photo Denys van Kempen
      Denys van Kempen
      Blog Post Author

      Hi Sebastian,

      SELECT * FROM M_DATABASES will list all your tenant databases.

      On MDC, you should see at least two of which one is SystemDB.

      On single-container mode, the view will show a single entry with the name of the SID.

      (there are many other ways, but this might be easiest).

      https://help.sap.com/viewer/4fe29514fd584807ac9f2a04f6754767/1.0.12/en-US/dbbdc0d96675470e80801c5ddfb8d348.html?q=M_DATABASES

      Author's profile photo Pikakala Sebastian
      Pikakala Sebastian

      Hi Denys,

      I upgraded my HDB from 1.0 SP12 to 2.0 SP3 MDC, however from the DB explorer it still shows as SingleDB and from my application it says 2.0 SP3, also during upgrade the installer showed that it is converting the DB from a single db to a MDC

       

      my LCAPPS is also updated

      Any suggestion why my db explorer is showing wrong info

       

      Regards,

      Sebastian

       

      Author's profile photo Dennis Padia
      Dennis Padia

      Hello Sebastian,

      It is just the description text (which didn't changed as you were on single container earlier) and I think you are executing the query in tenant database. If you execute the same query from SYSTEMDB, it will show you two database (SYSTEMDB and TENANTDB).

      You can check parameter global.ini > multidb > mode = multidb. If the value is multidb that means your database is in MDC.

      Regards,

      Dennis