Skip to Content

Scenario:

  • You want to migrate your existing SAP ABAP system to the SAP HANA database
  • Your SAP release needs to be upgraded prior to migration

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
  • 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, host name, and connectivity settings stable.

DMO_intro.jpg

DMO for SAP NetWeaver BW and for SAP Business Suite systems

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 SAP BW systems from 7.0 SP17 (and higher) to migrate to 7.31 (and higher). And it can be used for systems like SAP R/3 4.6C or systems part of the SAP Business Suite 7.0 (and higher) to migrate to a level corresponding to SAP BASIS 7.40 (for example “SAP enhancement package 7 for SAP ERP 6.0”).

 

DMO processing overview

The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the traditional database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). Then the shadow repository is copied to SAP HANA,  the database connection of the SAP system is switched to SAP HANA 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 SAP HANA. The traditional database continues to run and the application data in it are not modified, so it remains a fallback throughout the complete process.

Please note that for a SAP Business Suite system based on SAP NetWeaver 7.40 (i.e. systems part of SAP Business Suite 7 Innovations 2013), your SAP NetWeaver Hubs must be on 7.30 or higher. For details, see http://wiki.scn.sap.com/wiki/display/SLGB/Strategy+beyond+SAP+Business+Suite+7+Innovations+2011

 

 

Further information

 

  • SAP Note 2426315 on Database Migration Option for SUM 1.0 SP 21
  • SAP Note 2428170 on Database Migration Option for SUM 2.0 SP 00

Check the following blog to learn about SUM 2.0: https://blogs.sap.com/2017/08/10/sum-in-the-family-way/

 

DMO Guide

 

Blogs on DMO

 

Blogs on related topics

SAP Education offering

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

 

Watch out for more details in further blogs that will be listed here as well.

 

Boris Rubarth
Product Management, Software Logistics, SAP AG

To report this post you need to login first.

171 Comments

You must be Logged on to comment or reply to a post.

  1. Massimiliano De Mola

    Hello Boris,
    we have source system SAP ECC6 EHP6 unicode with ase 15.7 on HP-UX 11.31 IA 64 bit
    Could we use DMO (upgrade EHP7&migration to suite on hana) with actual DB ase release?
    Thanks.
    Massimiliano

    (0) 
  2. Delia Ciurgauan

    Hello Boris,

    Any advice on migrating to HANA that is in a cluster setup? With a standby-failover node.
    Is there something in particular that is different from single-node setup?

    I couldn’t find yet in the guides or notes any mention on this.

    Thank you,
    Delia
     

    (0) 
  3. J. Behera

    Hi, Can we use this option to migrate Non sap / ABAP system ( in this case ASE from Sybase) to  HANA  as a pure data base migration tool ( migrate DB objects like procedure, functions, triggers, catalog objects,etc..?

    (0) 
  4. Jonathan Ma

    Thank you Boris for the blog.

    We are planning to migrate to Hana from Solaris/Oracle to Redhat/Hana, both the DB and PAS. From the OSS note 2377305, it says we can install an additional Linux apps server on the source system. Therefore, the source and destination R3load will run on the same version. However, since Solaris and Linux are on different code page, would that cause an issue?

    I am also not sure if installing an additional Linux apps server helps us. My understanding is that it is an option for source systems like Windows not certified with the system move DMO option? We could potentially run the Hana migration on the source Linux host without the server move and then install the PAS on the “real” target host later. However, is this a supported alternative?

     

    (0) 
    1. Boris Rubarth Post author

      Hi Jonathan,

      I can think of two scenarios in which an Additional Application Server (AAS) can be relevant:
      1) for plain DMO if you want to use a hardware with more performance for the time of the migration
      2) as you say for “DMO with System Move” to fulfil the current requirements on linux OS

      Sure it is a valid approach to first run plain DMO, and afterwards install a new PAS on the real target host.

      Regards, Boris

      (0) 

Leave a Reply