Dedicated SAP HANA XS Advanced Runtime host installation through resident hdblcm on HANA 2 SPS 01

In this blog I will cover installation of XS Advanced Runtime on a dedicated host on HANA 2 SPS 01. Even though my example covers HANA 2 SPS 01, the process is similar on HANA 1 SPS 11+.

Prerequisites:

1. The SAP HANA system has been installed with its server software on a shared file system (export options rw, no_root_squash).
2. The host has access to the installation directories <sapmnt> and <sapmnt>/<SID>.

SAP HANA Multitenant Database Containers (MDC) Features Chart

Starting from HANA 2.0 SPS01, Multitenant Database Containers (MDC) will be the standard and only operational mode for SAP HANA systems, and definitely one of the significant changes that will have greater influence, affect directly or indirectly on customers’ systems that are currently running on single container but plan to update to HANA 2.0 SPS01+ and above anytime soon or in near future.

Want to know the differences and the developed of MDC with more supported features and less limitations compare to years ago when it first introduced on HANA 1.0 SPS09+ ?

What is really changing with SAP HANA 2.0 SPS 01?

This new release includes enhancements for database management, data management, analytical intelligence and application development.

This release also includes another important change which will have a greater influence on the landscape configuration and sizing of SAP HANA and will definitely encourage people to become more creative and flexible with the technical architecture.

Starting with SAP HANA 2.0 SPS 01, multitenant database containers (MDC) will be the only operational mode for SAP HANA systems. This means that if you upgrade to SAP HANA 2.0 SPS 01, you will no longer be able to run a single-container HANA system.

MDC conversion on HANA System Replication configured

MDC system can only be replicated as the whole system, it means that the system database and all tenant databases are part of system replication. A take over happen for the whole Hana database (system database + all tenant databases) and is not possible to take over just for a particular container.

In our scenario, we have system replication setup for single container systems running on 112.02, and we decided to convert them into MDC. As we know that primary and secondary must be identical (N+N, nodes (except Standby) and services) during system replication setup, there's no exception for MDC.

Adjust SLT connection to HANA MCD

After convert HANA to MCD (MultiTenant) some tasks must to be executed in SLT to connect with MCD Database.

In addition to Note 2101084 please check the SAP Note relevant for your DMIS version from the list below and ensure all corrections are applied to both source and SLT server where indicated in the note.

• 2016511 - Installation/Upgrade SLT - DMIS 2011 SP7
• 1958809 - Installation/Upgrade SLT - DMIS 2011 SP6 / DMIS 2010 SP10
• 1882433 - Installation/Upgrade SLT - DMIS 2011 SP5
• 1824710 - Installation/Upgrade SLT - DMIS 2011 SP4 / 2010 SP9
• 1759156 - Installation/Upgrade SLT - DMIS 2011 SP3 / 2010 SP8
• 1709225 - Installation/Upgrade SLT - DMIS 2010 SP7 / 2011 SP2
• 2191214 - Installation/Upgrade SLT - DMIS 2011 SP9 & SP10 

SAP HANA Multitenancy Multi-tenant Database encryption with change of encryption root key for SYSTEMDB

Why This Blog:

In this case, the high level security measure is to enable Data Volume Encryption on the Hana system.

This is the first time I have enabled Data Volume Encryption with a Hana Multitenant Database.

After we have executed steps described in SAP HANA Administration guide, for enabling Data Volume Encryption, the alert '57' was raised in our SYSTEMDB reporting "Inconsistent SSFS". At this point our tenant DB was working without issues including backup. For system DB we were experiencing all symptoms reported by SAP Note 2097613.