The SAP DMO (Database Migration Option) suite of tools simplifies and dramatically streamlines the entire SAP migration with one process, one tool, one downtime. DMO allows SAP users to update an existing SAP system to a higher release version and/or can migrate to SAP HANA database. This blog post is a technical overview on all you need to know about DMO.

Benefits of DMO

DMO provides many benefits over other upgrade/migration options by combining ease of use, shortened number of steps, and additional tools for reducing downtime. Here’s a quick overview of the many benefits of DMO.

Migration steps are simplified

Before DMO (Database Migration Option), you needed to update the SAP software with SUM (Software Update Manager), and then migrate it to a new database with SWPM (Software Provisioning Manager).

DMO simplifies the migration with one tool (SUM with DMO) that will run the system update and database migration combined into one tool. If your systems weren’t already Unicode, a Unicode conversion can be included (for single-code-page systems).

  • Less regression test necessary
  • Reduces business downtime (TCO)
  • A combined procedure only needs one maintenance phase (not two)
  • In place migration keeps the application server and System-ID stable
  • As of SUM 2.0 SP1, the “DMO with System Move” option has been added to allow the migration of the application server if required
  • Original database is kept and can be reactivated as a fallback
    • Reduces risk
    • No restore required
    • More time for testing before cutover
  • The tool is easy to work with, as it’s just SUM with an improved UI (User Interface)
  • As of SUM 1.0 SP 13, the benchmarking tool has been added for use as a technique to tune the migration and reduce the technical downtime.
  • A certification is recommended, but is not required for consultants using DMO.

Before you get started

Before beginning a DMO project, there are a few critical items you should know. With any SAP project, knowing how to navigate the tool and proper planning are the key to success. Here’s a quick list of rules around DMO of SUM.

  • DMO supports a migration to SAP HANA DB, as well as SAP ASE, MaxDB, MS SQL Server, and IBM DB2.
    • A homogenous migration is not supported, for example HANA to HANA
    • You may need to apply at least one SP, for example ST-PI
  • SAP HANA requires a single stack.
    • DMO only works for AS ABAP based systems: no dual-stack spit option in DMO.
  • For a target system based on SAP Netweaver 7.5 (such as SAP ECC 6.0 EHP8), the source system must be on Unicode already. For this scenario, DMO is not able to cover the Unicode Conversion.
  • Using DMO for a migration across data center is not supported. There are no technical restrictions, but it comes with a high performance and latency impact. You may use it at your own risk. No support is provided in case of performance issues or broken procedures due to network/latency issues
  • DMO with System Move option is not supported on SAP source systems running Windows and can only be used to migrate to a target database of HANA or ASE
  • To use SUM 2.0 the target release must be based on SAP Netweaver 7.50 or higher and the source system must be Unicode

Supported SAP start releases for DMO

Currently, DMO does not cover all possible start releases, but it covers several popular versions. You’ll want to verify your start release is supported before starting the project. The following are supported SAP instances for DMO. Keep in mind that each SUM release has different source requirements:

  • SUM 1.0 SP21
    • SAP R/3 4.6C – SAP ECC 6.0 (or above)
    • SAP Business Suite 7 (or above)
    • SAP BW 7.0 (or above)
    • Sap Netweaver 7.0 systems (or above)
  • SUM 2.0 SP1
    • SAP ECC 6.0 (or above)
    • SAP Business Suite 7 (or above)
    • SAP BW 7.0 (or above)
    • Sap Netweaver 7.0 systems (or above)

The following are additional migration options for SAP HANA when not using DMO:

While SAP general migration option is to use DMO of SUM, it may not fit every company’s needs. It could be the case that your landscape just doesn’t meet a requirement for DMO. Whatever reason it may be, it’s important to know what options you have. Listed below are the current migration options supported by SAP.

New installation (using SWPM)

  • Install a new system on SAP HANA
  • Either without changing existing solutions
  • Or for transforming an existing solution to SAP HANA by performing (selective) data migration

Classical migration (using SUM and SWPM)

  • To bring original system on release supported by SAP HANA, you perform update/upgrade (if required)
  • Then, you classically migrate your traditional database to SAP HANA
  • Must pay for migration check service
  • Must be certified

One-step procedure with DMO (using SUM)

  • One process, one tool, one downtime.

>>> For more information regarding the DMO process and how the Managecore team can help contact our team today!

About the Author:

Chad Fischer
Senior SAP Basis Consultant
As a senior basis consultant for Managecore’s delivering team Chad is on the front lines with clients’ critical systems providing technical daily monitoring support, project leadership, and implementing SAP® best practices for Managecore’s valued customers. With 10 years of experience with SAP, Chad’s core strengths include his sound technical knowledge and ability to go above and beyond to provide the best in expert customer support. Chad is continuously learning new SAP trends, to advise clients of new technologies that will optimize their business needs. Most notably as a SAP HANA® certified consultant, Chad provides expert technical support and gets clients running faster than ever before on the SAP HANA platform. Chad’s infectious smile and ‘can do attitude’ embodies Managecore’s foundational principles to provide Trust/Transparency and Communication/Collaboration.