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.
Choose the procedure you want to execute like you normally do.
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.
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.
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.
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:
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:
The trans.log would look similar to the following:
To fix this, you can simply update the dbsl in the exe directory of the new SAP system.