Use the database migration option (DMO) of the Software Update Manager (SUM):
it combines SAP upgrade and database migration to SAP HANA in one tool!
If you want to migrate an existing SAP system (running on anyDB) to a SAP HANA database, required steps may be a dual-stack split, a unicode conversion, a database upgrade of anyDB, an upgrade of your SAP software, and a database migration to SAP HANA. The Software Update Manager (SUM) includes an option that combines the upgrade with the database migration “database migration option” (DMO) for SUM. It is sometimes referred to as the one-step migration procedure, compared to the classical migration (i.e. heterogeneous system copy, using Software Provisioning Manager).
The DMO is an inplace-migration (instead of a new installation): it upgrades and migrates the existing system while keeping the system-ID, PAS host name, and connectivity settings stable.
DMO is available with Software Update Manager 1.0 SP09 and higher, and can be used for systems based on AS ABAP. It can be used for other target database types meanwhile as well, see respective SAP note for details (see below).
DMO processing overview
The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the target database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). Then the database connection of the SAP system is switched to the target database, and then the downtime starts. After migration of the application data (including data conversion), the upgrade is finalized and the SAP system runs on the target database. The source database continues to run and the application data in it are not modified, so it remains a fallback throughout the complete process.
SUM delivers its own R3load tool which is used for the migration of the application table content. SUM starts several R3load pairs that work on buckets (work packages) to export data from source database and import data into target database. As both R3loads of a pair are running on the same host, they can directly exchange data using the pipe mode of R3load. The advantage is fast processing, as no dump files are created and no compression of files is required.
Reducing downtime with downtime-optimized DMO
With SUM 2.0, it is possible to further reduce the downtime of a migration by using the approach of "Uptime Migration", also known as "downtime-optimized DMO". See SAP Note 2547309 for details.
Blogs on DMO
Blogs on other DMO use cases:
Blogs on DMO downtime aspects:
Blogs on related topics
SAP Education offering