#SAP HANA Tenant DB convertion **PremG**

Convert to Tenant Databases Using the Graphical User Interface

Access the #SAP HANA HDBLCM Web user interface

1-Web Browser

Enter the #SAP HANA database lifecycle manager (HDBLCM) URL in an HTML5-enabled browser:

https://<hostname>:1129/lmsl/HDBLCM/<SID>/index.html

2-#SAP HANA Studio.

Start the #SAP HANA studio.

In the #SAP HANA studio, add the #SAP HANA system.

Open the context menu (right-mouse click) in the Systems view, and select Add System.

For more information about adding a system,

In the #SAP HANA studio, log on to the system.

From the context menu of the selected system, select Lifecycle Management Platform Lifecycle Management #SAP HANA Platform Lifecycle Management.

3-#SAP HANA Cockpit

Change to the #SAP HANA resident HDBLCM directory:

cd <sapmnt>/<SID>/hdblcm

By default, <sapmnt> is /hana/shared.

Start the #SAP HANA database lifecycle manager interactively in the graphical user interface:

./hdblcmguiThe #SAP HANA database lifecycle manager graphical user interface appears.3.

Select Convert to Tenant Databases from the activity options. Then select Next.4.

Provide the password of the <sid>adm user and the SYSTEM user of SYSTEMDB, then select Next.5.

Review the summary, and select Run to finalize the configuration.

Your #SAP HANA system is a tenant database system with one system database and one tenant database, both of which are running. You can verify this by adding both databases to #SAP HANA cockpit and querying the public view M_DATABASES from the system database. The result will look like this:

| DATABASE_NAME |DESCRIPTION | ACTIVE_STATUS |

|-----------------|----------------------------------|---------------|

| SYSTEMDB | SystemDB-<SID>-<INSTANCE> | YES |

| <SID> | SingleDB-<SID>-<INSTANCE> | YES

Note the following about the tenant database:

It contains all the data (including users, configuration, and connection properties) of the original system (but not the original backup history).

Configuration files that are tenant-specific (e.g. indexserver.ini, xsengine.ini, etc.) are now stored at the following location: /usr/sap/<SID>/SYS/global/hdb/custom/config/DB_<database_name>.

Its trace files are now stored at the following location: /usr/sap/<SID>/HDB<instance>/<host>/trace/DB_<database_name>.

Note

Any trace files that were in the trace directory before the system was converted are not moved

Note

If you configured the properties of the index server, script server, or xsengine server in your original system, these settings initially apply to all new tenant databases. You must explicitly configure tenant database if required

If HTTP access via the #SAP HANA XS classic server is required, update the configuration of the Web Dispatcher.

Prerequisites

The difference between the system time set on the hosts is not greater than 180 seconds.

The #SAP HANA system has been installed with its server software on a shared file system (export options rw, no_root_squash).

The host has access to the installation directories <sapmnt> and <sapmnt>/<SID>.

The #SAP HANA system has been installed or updated with the SAP HANA database lifecycle manager (HDBLCM).

The #SAP HANA database server is up and running.

You should verify that the following prerequisites are fulfilled before trying to access the #SAP HANA database lifecycle manager from a Web browser.

The communication port 1129 is open.

Port 1129 is required for the SSL communication with the #SAP Host Agent in a standalone browser via HTTPS

SUSE Linux - Mozilla Firefox with XULRunner 10.0.4 ESR

The #SAP HANA studio revision is 120 or higher.

For Linux:

The system property org.eclipse.swt.browser.XULRunnerPath should be set in hdbstudio.ini to point to the path of XULRunner, for example:-Dorg.eclipse.swt.browser.XULRunnerPath=<path to xulrunner>.

This hdbstudio.ini file is located in the same folder as the executable that is used to start the #SAP HANA studio. For Linux, the default location is hana/shared/<SID>/hdbstudio.

If all prerequisites are met we can start the migration. First change to the #SAP HANA HDBLCM directory: cd <sapmnt>/<SID>/hdblcm. By default <sapmnt> is /hana/shared. From here I will start the HDBLCM in the command line: ./hdblcm –action=convert_to_multidb

Before you will continue, be aware that converting to a multiple-container system is permanent and cannot be reversed.

Unlike in the past, you don’t need to stop the system manually. All processes will be stopped automatically. After conversion all processes are up and running and you can work with the database immediately.

If the single-container system was converted successfully, you will have one system DB and one tenant DB. The name of this tenant is <SID>@<SID>, my tenant has then a name----.

You can add the system DB to your workspace in the #SAP HANA studio and using Configuration tab in Administration editor have a look at how it is configured now. The global.ini->multidb->mode has been set to ‘multidb’.

So, what happens with my schema, tables and users which I created in the single-container system?

My single-container system was converted to a tenant DB. You can add it to your workspace in #SAP HANA studio as well. Use the same host, SID and SYSTEM user credentials of the original single-container system.

Conversion using HDBLCM GUI

The next possibility to convert a single-container system to multiple-container system is via the HDBLCM GUI.

If all prerequisites, described above, have been met, you can start the HDBLCM GUI.

First change to the #SAP HANA HDBLCM directory: cd <sapmnt>/<SID>/hdblcm. By default <sapmnt> is/hana/shared. With ./hdblcmgui start the HDBLCM GUI. On the first page I can choose the activity Convert to Multitenant Database.

And the last, but not least, option to convert is using Web UI. Again, the prerequisites, described above, should be met. Then be sure that communication port 1129 is open. I will run the HDBLCM Web UI for migration in Google Chrome

Using the URL https://<host_name>:1129/lmsl/HDBLCM/<SID>/index.html  you can open Launchpad of #SAP HANA Platform Lifecycle Management.

After conversion you can work with the tenant DB like you worked with the single-container system. You can also create additional tenants in the multiple-container system