Scribd
Upload
65 views

Database Migration Option

The Database Migration Option (DMO) allows customers to migrate an existing SAP system to SAP HANA in a simplified and reduced downtime process. The DMO tool within the Software Update Manager combines the SAP upgrade and database migration to HANA into a single process. It upgrades the system and migrates the data to HANA while keeping the system ID and connectivity settings stable. The DMO uses R3load to export data from the source database and import it into HANA in parallel processes to reduce migration time.

Uploaded by

Raghav Kamati
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
65 views

Database Migration Option

The Database Migration Option (DMO) allows customers to migrate an existing SAP system to SAP HANA in a simplified and reduced downtime process. The DMO tool within the Software Update Manager combines the SAP upgrade and database migration to HANA into a single process. It upgrades the system and migrates the data to HANA while keeping the system ID and connectivity settings stable. The DMO uses R3load to export data from the source database and import it into HANA in parallel processes to reduce migration time.

Uploaded by

Raghav Kamati
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Database Migration Option (DMO)

Scenario:

 You want to migrate your existing SAP ABAP system to the SAP HANA database

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!
Benefits:

 Migration steps are simplified


 System update, Unicode Conversion (*), and database migration are combined in one tool
(*: only possible for a target based on 7.40)
 Business downtime is reduced
 The source database remains consistent, so a fast fallback is possible
Motivation
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. heterogenous 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.
Data Migration
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.
More information
DMO Guide

 Use quicklink http://support.sap.com/sltoolset and navigate to section System Maintenance

Blogs on DMO

 Migration to SAP HANA: Overview Video of Database Migration Option DMO


 DMO: technical background
 DMO: background on table split mechanism
 DMO: comparing pipe and file mode for R3load
 DMO: table comparison and migration tools
 DMO: Handling table comparison checksum errors
 DMO, SAP HANA and the Target DB SID
 Short history of DMO
Blogs on other DMO use cases:

 DMO without software change


 DMO with System Move – the use case to change PAS host during DMO
 Your SAP on Azure – Part 2 – DMO with System Move
Blogs on DMO downtime aspects:
 Optimizing DMO Performance
 DMO: optimizing system downtime …
 DMO: introducing the benchmarking tool
 DMO: downtime optimization by migrating app tables during uptime (preview)
 Phases behind DMO R3load parallel export/import during UPTIME and DOWNTIME to target
HANA DB
Blogs on related topics

 Migration of SAP Systems to SAP HANA


 Comparing SAP migration procedures to SAP HANA database
 A better way to migrate your SAP NetWeaver BW from any database to SAP HANA
 Decision Matrix to Choose Best Migration Option of ABAP Systems to SAP HANA
 Software Update Manager (SUM): introducing the tool for software maintenance
 Best Practice Guide – Classical Migration of SAP NetWeaver AS ABAP to SAP HANA
SAP Education offering

 HA250: “Migration to SAP HANA using DMO” – two days classroom training

You might also like