kentoh - Fotolia

How can SAP Software Provisioning Manager foster migration success?

If you're moving to Business Suite on HANA, you'll want to know how to use Software Provisioning Manager for a successful migration. Here's important advice.

If you're looking to significantly cut time and effort when implementing Business Suite on SAP HANA, the SAP Software Provisioning Manager is a database migration tool that can help.

SWPM is part of Solution Manager and is activated when you install Solution Manager in the SAP ERP Central Component (ECC) system.

Companies that are planning to use Software Provisioning Manager need to first ensure that their existing SAP ECC is upgraded to the latest software version, such as Enhancement Package 7 or later, to ensure successful HANA database migration. Older SAP ECC versions do not support HANA database migration, nor the latest support packages or enhancement packages.

Using SWPM is also known as a classical migration approach since this tool enables any third-party database, which SAP refers to as AnyDB, to be migrated to SAP HANA. In a classical migration approach, the system administrator can import and export database activities, which makes Software Provisioning Manager an attractive option to cut costs and save time.

Here are some important tips that will ensure the most-effective use of SWPM, and, in turn, a trouble-free and smoother migration.

Tips for export

  1. Before starting the actual migration process, be sure to download the latest kernel for the source and the target database systems.
  2. Since HANA migration will convert the source database's cluster and pool tables into transparent tables, be sure to run relevant utilities in the source database to identify any errors during conversion. Errors found while converting to transparent tables can be fixed well ahead of time. Implement SAP Notes 1077403, 1087959 and 1921023 to identify and fix all errors found during table conversions.
  3. Split the existing database tables to manageable limits. Use Transaction DBACOCKPIT in the source SAP ERP system for this purpose. It's recommended to split database tables to under 2 GB or under 10 million rows.
  4. Tend to all errors found in the source system and existing database during updates and prior to using SWPM, otherwise you can face errors in actual migration.
  5. Lock out all SAP users from the system prior to database migration and hold off any running background jobs such as printing or data transfer taking place through interfaces.

Tips for import

  1. Be sure to switch the HANA database to "overwrite" mode.
  2. Choose the "tables splitting" option and the number of parallel processing sessions that SAP HANA will run simultaneously. Be sure to run at least two parallel sessions to speed up the database migration process, but don't run too many. For example, 10 will lead to an overload on HANA's resources and network and will significantly slow down the database migration activity. Four to six parallel sessions is optimal.
  3. Be sure to monitor progress. SAP will automatically initiate the Migration Monitor program so you can view the database progress being made. Only under exceptional circumstances will you need to manually start the Migration Monitor.
  4. If the database import performance is progressing satisfactorily, you can add a few more migration sessions to reduce the migration time.
  5. Use the SAP-provided tool MIGTIME, also called Time Analyzer, to get text and graphical display of database export and import performances.

HANA database migration is much more than a technical project. However, with the right groundwork, database migration tool and processes, you can foster success.

Next Steps

Backup and recovery essentials for Business Suite on HANA

Does aging infrastructure affect HANA migrations?

Steps to implementing HANA

Dig Deeper on SAP implementation