So, you're the admin, and you're ready to roll with an SAP HANA Cloud database instance. Great call! Let's map out the essentials to make sure you're all set.
Getting Subaccount Access Right
First things first – to deploy the database, you'll need access to a subaccount in your company's SAP Business Technology Platform (SAP BTP) global account. But, not just any access – you'll want the Subaccount Administrator role collection. If you find your user account missing this role, no worries. Just give a shout to your SAP BTP global account admin and ask them to hook you up. It's like getting the backstage pass for the deployment concert.
Unlocking the Toolbox: SAP HANA Cloud Administration Tools
Now, let's talk tools. To craft and manage your database instances, you're going to need the SAP HANA Cloud - tools plan in your subaccount. This magical plan opens the door to a trio of game-changers: SAP HANA Cloud Central, SAP HANA cockpit, and SAP HANA database explorer
To activate the new multi-environment SAP HANA Cloud tools, follow the instructions in the blog
Benefits and features of the multi-environment SAP HANA Cloud tools
The Old VS The NEW
HANA Cloud tools in Cloud Foundry are still hanging around, but here's the scoop – the Cloud Foundry edition of SAP HANA Cloud Central is waving goodbye. It's officially on the way out. SAP's advice? Make the shift to the new multi-environment SAP HANA Cloud tools. That's where the buzz is, and that's where the future is headed.
Implementation Starts here
In SAP BTP Cockpit, navigate to SAP HANA Cloud Central via: Instances and Subscription > Applications > SAP HANA Cloud > Instances for creating and managing database instances
To access the Self-Service Migration for SAP HANA Cloud tool in SAP HANA Cloud Central, no additional configuration is needed for SAP HANA Service scenarios (Neo and Cloud Foundry).
However, for SAP HANA on-premises scenarios, ensure the connectivity_proxy service plan is added to the connectivity service. If not available, contact the SAP BTP global account administrator to add this required service plan for self-service migration as this needs to be connected via cloud connector
To locate the Self-Service Migration Tool in SAP BTP Cockpit:
In the subaccount navigation, select Instances and Subscription.
From the Applications table, choose SAP HANA Cloud.
In the navigation area, click on Migrations to create and manage migrations to SAP HANA Cloud.
Deploy a SAP HANA Cloud Database
Creating a Migration user in source database
Migrating from an SAP HANA database to SAP HANA Cloud requires a dedicated user in your SAP HANA source database. The Self-Service Migration tool will check whether the provided user has all needed privileges to perform the migration. Any missing privileges and the objects on which they must be granted will be displayed in the user interface.
On the source database, open a SQL Console in the Database Explorer.
Create a migration user by executing the following statement in the Database Explorer -
1 CREATE USER <username> PASSWORD <password> NO FORCE_FIRST_PASSWORD_CHANGE;
2. Grant the necessary privileges to the migration user by running the following script in the Database Explorer
GRANT SELECT ON _SYS_REPO.DELIVERY_UNITS TO <username>;
GRANT SELECT ON _SYS_REPO.ACTIVE_OBJECT TO <username>;
GRANT CATALOG READ TO <username>;
GRANT INIFILE ADMIN TO <username>;
GRANT TRUST ADMIN TO <username>;
GRANT CERTIFICATE ADMIN TO <username>;
GRANT CREATE REMOTE SOURCE TO <username>;
3. For each schema you need to migrate add this scenario :
GRANT SELECT ON SCHEMA "<SCHEMA_NAME>" TO <username>;
The SQL statement must be executed by the owner of the schema or any user who has the permissions to grant the required privileges.
Install and Configure the Cloud Connector
The Cloud Connector allows you to set up a secure connection between the source SAP HANA on-premise database and the target SAP HANA Cloud database instance on SAP BTP
Installation of Cloud Connector on Linux
Note : For this you need require the connectivity_proxy service plan to be added to the connectivity service in your subaccount entitlements.
Fill the details in Self Migration Tools :-
Name | Description | Example |
Migration Name | Give a short descriptive migration project name. | Migration OP to HC |
Migration Description | Give a good description for the migration project. | Self-Service Migration SAP HANA on-premises to SAP HANA Cloud |
Source Instance Host | Virtual host name exposed to SAP BTP through Cloud Connector. | op-source-hana. The real host name wdflbmt7346 isn't exposed to the SAP BTP. |
Source Instance Port | Virtual port number exposed to SAP BTP through Cloud Connector. | 42015. The real port number 30015 isn't exposed to the SAP BTP. |
Cloud Connector Location ID | Location ID defined in the Cloud Connector. | SCC-OP-HANA |
Migration Username | Dedicated migration user account created on the source database. | MIGUSER |
Migration Username Password | Password specified during the creation of the migration user. | Welcome1 ( This is not a strong password ) |
Target Database Username | Database administrator user name created during SAP HANA Cloud database deployment. | DBADMIN |
Target Username Password | Password specified during the deployment of the SAP HANA Cloud database. | Welcome1 ( This is not a strong password ) |
Migrating from SAP HANA Service for BTP , Neo environment
Note : This scenario only migrates the catalog and data to SAP HANA Cloud. Migration of XS Classic and SAP HANA repository content or other design-time artifacts is not supported.
Field | Description | Example |
Migration Name | Descriptive name for the migration project. | Neo to HC Self-Service Migration |
SAP BTP Region | Region of the source database within SAP BTP. | Europe (Frankfurt) |
Technical Subaccount | Name of the technical subaccount in the Neo environment. | pvwaf4nsum |
Source Database ID | DB/Schema ID listed in the Databases & Schemas list. | neosource |
Account Username | User name for connecting to the SAP BTP Neo environment. | P1234567890 |
Account Password | Password for the specified user account (P1234567890). | Welcome1 |
Database Username | Dedicated migration user account on the source database. | MIGUSER |
Database Password | Password specified during the creation of the migration user. | Welcome1 |
Target Instance | Name of the SAP HANA Cloud target database. | HC_Neo_Target |
Migrating from SAP BTP Cloud Foundry
Note : For this scenario , the source and target database need to be located in the same region.
Name | Description | We will use Example |
Migration Name | Descriptive name for the migration project. | CF to HC Self-Service Migration |
Credentials for SAP BTP Cloud Foundry: |
|
|
Username | User name for connecting to the SAP BTP Cloud Foundry environment. | P1234567890 |
Password | Password for the specified user account (P1234567890). | Welcome1 |
Source Database Information: |
|
|
SAP BTP Region | Region of the source database within SAP BTP. | EU (Frankfurt) |
Cloud Foundry Space | Cloud Foundry space name where the SAP HANA Service is located. | dev |
Source Instance Name | SAP HANA Cloud Service instance name shown in the Service Instances list. | CF_Source |
Username (Source DB) | Dedicated migration user account created on the source database during preparations. | MIGUSER |
Password (Source DB) | Password specified during the creation of the migration user. | Welcome1 |
Target Database Information: |
|
|
Migrated Instance Prefix | Prefix for the new migrated instance (SAP HANA Schemas and HDI containers service). | demo_ |
Target Instance | Name of the SAP HANA Cloud target database. | HC_CF_Target |
Target DB Username | Database administrator user name created during deployment. | DBADMIN |
Target Username Password | Password specified during the deployment of the target database. | Welcome1 |
.png)
.png)
Comments
Post a Comment