Within SAP HANA SP9, everything is about the new feature “multitenant database containers“.

The latest software provisioning manager SP 7 provided with SL Toolset 1.0 SPS 12 already supports this new feature. This is a brief overview about how to work through the corresponding dialog phase, when you are using the new SAP HANA SP9 feature: Multi-Tenant Database Containers.

StartScreen.png

Choose the procedure you want to execute like you normally do.

TenantConnectivityData.png

In case of MultiDB, on the dialog you are used to enter the connectivity data for the SAP HANA database, you now have to enter the connectivity data for the specific database tenant. In this example, the SAP HANA database I installed is called MUL. But the name of the tenant inside shall be MU1.

ErrorTenantNotExists.png

As the tenant does not exist, an error message shows up. In one of the next deliveries of the software provisioning manager, it will be possible to create the tenant within the procedure.

CreateTenant.png

Right now, you have to create the database tenant by hand using the SAP HANA studio or hdbsql.The statement for creating a tenant is shown above.

  SystemDatabaseConnectivityData.png

Once the tenant is created, the error will not appear again and you proceed to the next dialog. Here, you have to enter the password of the Administrator of the System database. That is the password you entered while you installed the SAP HANA instance. After this, the installation is the same as it is on a single SAP HANA database.

Unfortunately, you might encounter the following error during the installation:

ErrorR3loadTestconnect.png

The reason for this is a change in the version handling of SAP HANA. If you execute “R3trans –x” as user sidadm, you will receive the same error:

R3transX.png

The trans.log would look similar to the following:

transLog.png

To fix this, you can simply update the dbsl in the exe directory of the new SAP system.

ExtractDbsl.png
After that, the installation moves on after pressing the Retry button.

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Andy Silvey

    Hi Stefan,

    we are about to migrate a BW to Hana.

    We’re thinking to use the Hana MultiTenant Database Containers to enable both the BW ABAP DB and the Bi Java DB to be on the same Hana Instance.

    As you know with MultiTenant Database Containers, once this has been enabled on the Hana Appliance/Instance there is no way to revoke it and go back.

    Question:

    For our BW ABAP migration to Hana we are planning to use the SUM with DMO Database Migration Option.

    Does SUM with DMO work if the Hana Appliance/Instance is enabled for MultiTenant Database Containers ?

    Obviously we need to know the answer to this one before we enable the Hana MDC on the Appliance/Instance.

    Thanks and kind regards,

    Andy Silvey.

    (0) 
      1. Andy Silvey

        Hi Boris,

        yes, I see my confusion now, this blog is about SAP Provisioning Manager support ing MDC and we’re talking about SAP Upgrade Manager & DMO – two different things.

        Thanks for confirming, don’t stay up too late, we’ve a lot of work again tomorrow.

        Best regards,

        Andy.

        (0) 
  2. Chandrakanth Angannagari

    hi Boris

    Not related to this blog precisely , but how are on-premise and cloud options going to change with MDC . I understood from the notes that its not anymore restricted for customers to put both their ERP and BW in two tenants on the same HANA DB (provided the right sizing is done). Its clear customers will go for consolidation/TCO reduction etc. Also more interested in what options does this bring in for Cloud hosting providers who service multiple customers. (probably some licensing / sales answers are also required to completely answer this )

    (0) 

Leave a Reply