Support Spotlight: SAP Business One HANA Migration Tips for Large Databases
In this blog post we want to show you some helpful hints from real experiences of running the migration wizard for large databases.
We will look at Preparing the Database, Defining the Performance Settings and finally share some valuable documentation links.
You have decided that the time is right for you to migrate your MSSQL environment to SAP HANA. The migration wizard available in any patch download package for SAP Business One will help you with the process of migrating your company databases to SAP HANA.
In our Administrator’s Guide, SAP provide the required pre-requisites and step-by-step details of running the wizard.
1. Preparing your database
1.1 Firstly, on the server where you are performing the migration process, ensure there are adequate resources for a demanding workload. Assuming it’s a 64-bit OS, you should install the 64-bit version for Java 8, which is a pre-requisite for the wizard. Also check that there is lots of RAM capacity on the server, upwards of 64 GB.
- Make sure that you have sufficient hard drive space. The Space Required for an upgrade is = 3 x (the size sum of all the selected company databases) + the size of the common database. For example, we have 2 company databases, 50GB and 60GB, and SBO-COMMON, 5GB. The total hard drive space needed in this scenario is 335GB.
- Every time when migrating to HANA, it’s a good opportunity to clean up your records and bring only those master records that you really need.
1.2 Make sure the company status is V-valid
A common issue we see is a company database that has already gone through a failed upgrade process being used in the migration wizard. Run query “select companysta from CINF”, the result must be V. The database migration would not be possible for any other status. In this scenario you need find a valid backup of your customer database with status ‘V’, or you can create a new backup of the database which will have status V and try to migrate again.
Possible status for company databases:
V — Valid
I — Invalid
U — Upgrading
A — Archived
S — Inventory Valuation Utility
P — Upgrade Simulation
1.3 Shrink MSSQL DB, please follow SAP Note 1224089 – How to Shrink Database in Microsoft SQL Server
1.4 Data Archiving (DA) is another option we have, to reduce the DB size.
For the overall outcome of DA, the size reduction is dependent on DB content, version, DB age, the transactions, and the operations. Moreover, there is no opportunity to run DA after migration as it’s not supported in SAP Business One version for HANA.
1.5 Change Log and Master Data Cleanup Utilities
Both options can be run from the SAP Business One Client:
Go to Administration → Utilities → Master Data Cleanup Wizard/ Change Logs Cleanup
The Master Data Cleanup Wizard allows you to remove or deactivate business partners, item master data, G/L accounts, project codes, cost centers, distribution lists and tax codes.
Warning: Removing data is irreversible.
The Change Logs Cleanup Window allows you to delete the change log entries for various documents and master data up to a desired date. This helps to free up space within your company database.
Warning: Deleting the change log entries is irreversible. Back up all data before executing a cleanup.
Please refer to the SAP Business One 10.0 On-Line Help for further documentation .
2. Define performance settings
2.1 When it comes to the Migration Performance Settings window, we recommend the following values as per our Administrator’s Guide.
Please find below the recommendations.
So, a good approach here is to test these values first and then if needed increase as per our suggestion if the migration fails.
- Please use a high-spec environment where you are running the Migration Wizard – e.g. 32 GB RAM
- Make sure that 64-bit java is installed and the environment variables are updated for 64-bit java.
- In the Migration Wizard Performance Settings, change the values as described below:
- JAVA VM Memory Allocation (MB), this defines the upper limit of the memory used by the JVM, set value to 4096.
- Read/write batch size (no. of records), this defines the number of records for each read or write batch operation, set value to 5000.
- Max. blob size (MB), this defines the upper limit for binary large objects (BLOB), set value as 2048
One final point to consider!
Allow the Migration Wizard to complete the task. Eventually it will either complete successfully, or it will fail. If it does fail, you can check the migration log by clicking on the open log file button in the Migration Wizard summary window.
The final step of the migration is to perform and SAP Business One upgrade following the regular process.
Please note, if the upgrade fails on the SBOCOMMON schema, the upgrade is rolled back for all schemas; if the upgrade fails on a company schema, the upgrade is only rolled back for that company schema.
3. Documentation Links
We hope this read has been informative and beneficial. For more blogs and tips from the SAP Business One Support team, please visit our space on the communities: https://blogs.sap.com/tag/b1-support-spotlight/