HANA Multi Tenant | HANA MDC

 An SAP HANA system can now be installed in multiple-container mode, which means it is capable of containing multitenant database containers.

A multiple-container system always has exactly one system database and any number of multitenant database containers (including zero), also called Refer SAP HANA Administration Guide for more information.


  1. From which revision is multiple database containers supported?

As of SAP HANA Platform SPS 09 (Revision 90), SAP HANA supports multiple isolated databases or multitenant database containers in a single S

  1. Will my system automatically be converted to multiple container after I upgrade to SPS9?

No, after you upgrade to SPS9 from any lower revision your system will still be single container.

Most frequently Used Commands For SAP HANA Administrators

  1. How is installation different from single-container to multi-container?

Instalation is performed using the same tools (hdblcm/hdblcmgui), during SAP HANA installation you have an option to choose between single-conta



  1. What happens after the installation of a multi-container system?

Once the installation is complete, only SYSTEM DB is created. Tenant DB’s can be created from the System DB using SQL, refer SAP HANA Admin

  1. Is there any difference in the list of services running on System and Tenant DB?

The most notable difference is missing indexserver on the System DB.

  1. Usually we connect to SAP HANA Database through indexserver which also serves as SQL port so how do we connect to system DB

In a multi-container system the connection to System DB happens through Nameserver which serves as SQL port.


Though there is no difference in tenant databases, which still uses the indexserver port for the connection.

  1. Why do we see indexserver port other than 3<InstanceNr>03 on tenant databases?

By default, new tenant databases are assigned 3 port numbers, one for each of the following:

  • Internal communication port (3xx40-3xx97)
  • SQL (3xx41-3xx98)
  • HTTP (3xx42-3xx99)

So, the first tenant database is assigned ports 3xx40-42, the second ports 3xx43-45, the third 3xx46-48, and so on. Hence in tenant databases we will see ports greater than 3XX40 assigned to indexserver.

  1. How many tenant databases can be created per instance?

The main limitation is the resources required for each tenant database (CPU, Memory). Further there is a limitation with regards to the available ports databases.

  1. Is it possible to overcome this limitation of 20 tenants per instance in case there is sufficent resources available?

Yes, we can increase this number by reserving the port numbers of further instances.

We do this by configuring the property global.ini — [multidb] — reserved_instance_numbers

The default value of this property is 0. If you change the value to 1, the port numbers of one further instance are available (for example, 30040-30199 if (for example, 30040-30299 if the first instance is 00).

Thus we are reserving additional ports to one instance.

  1. Can I migrate my existing single-container to multi-container?

Yes, you can migrate from single-container to multi-container provide you fulfill the prerequisites.

Please note this action is irrevocable.

The prerequisites are:

  • The SAP HANA Database is upgraded to revision 090 or higher
  • Embedded statistics server is enabled
  1. How can I convert SAP HANA database from single-container to multi-container?

You need to execute the utility

hdbnsutil -convertToMultiDB

  1. Is it not possible to keep the stand-alone statisticsserver and migrate to multi-container?

No, the migration will fail as the prerequisite is not fulfilled.

  1. Which process are triggered during the conversion from single-container to multi-container?

The process triggers the following actions:

  1. Sets the “multidb mode” flag in configurations.
  2. Creates the system database and one tenant database.
  3. Updates the secure store in the file (SSFS) system.
  1. After I successfully converted from single-container to multi-container none of my user/password is valid, what is the reason?

All the user/password on the single-container is now valid on your tenant database only and NOT on system DB.

  1. What is the password for SYSTEM user in system DB after the conversion from single-container to multi-container?

The password for SYSTEM user in SYSTEM DB after the conversion is “manager

  1. Where is statisticsserver running on System DB when there is no indexserver?

Since there is no indexserver on System DB the statisticsserver is running within the Nameserver (port 30901).

The above is valid only for System DB, the statisticsserver on tenant DB is still running within the indexserver (port 30940) as seen the figure below

  1. Is it possible to allocate more resources to one tenant database compared to others?

Yes, you can assign more resources to one tenant database if required.

Refer section Managing Resources in Multiple-Container Systems in SAP HANA Administration Guide

  1. While performing an installation of SAP HANA multi-container database will a tenant DB also be created as in the case of conversion

No, when performing a multi-container database installation only system DB is created. You can create tenant DB by executing the SQL CREATE DATABASE <DATABASE NAME> SYSTEM USER PASSWORD <PASSWORD>

In case of scaleout landscape and you want to create a tenant DB on a specific host


  1. Is my tenant DB accessible when my System DB is down?

No, when System DB is not available all tenants are also not accessible.

  1. If Out of Memory (OOM) occurs on one tenant DB will it have an impact on other tenant databases?

No, there is complete isolation between one tenant database and another.

  1. Is there global_allocation_limit per tenant?

No, the global_allocation_limit is valid for the complete system including all tenant databases and all services.

  1. Where to find information regarding sizing of multitenant database containers?

Please refer to SAP Note 2096000

  1. How can I make sure tenant database administrators do not assign more resources to one tenant?

A configuration change blacklist exists to prevent tenant database administrators to make changes to parameters related to resource management.

  1. Is cross database access enabled by default?

No, cross database access is NOT enabled by default.

For information regarding enabling cross database access refer to SAP HANA Administration Guide.

  1. Which system privilege is required for administrating tenant databases?


Please note this privilege is only available on SYSTEM DB.

  1. Who can start/stop a tenant database?

Only a System DB user with DATABASE ADMIN system privilege can start/stop a tenant DB using following SQL.

  • ALTER SYSTEM STOP DATABASE <database_name>

Please note that tenant DB administrators cannot start/stop the tenant DB.

  1. Which trace files are specific to the tenant DB?

Since only the indexserver process runs additional on tenant DB compared to System DB, indexserver traces and backup.log are the ones specific to Trace directory of System DB (This also includes folder for different Tenant DB)

Now look into specific tenant DB trace directory (Folder — DB_TENANATDB)

Under the process list you would just see additional indexserver for each tenant DB in addition to the processes that are running under the System DB



Also read SAP HANA Multitenant Database Containers Architecture

Leave a Reply