Skip to Content

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.50 or lower)
  • 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_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 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 traditional database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). Then the shadow repository is copied to the target database,  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.

Further information

  • SAP Note 2426315 on Database Migration Option for SUM 1.0 SP 21
  • SAP Note 2472850 on Database Migration Option for SUM 2.0 SP 01

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 other DMO use cases:

Blogs on DMO downtime aspects:

Blogs on related topics

SAP Education offering

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

 

Boris Rubarth
Product Management, Software Logistics, SAP SE

To report this post you need to login first.

189 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) 
  5. Nikunj Thaker

    Hi,

    Nice Blog.

    Can you please clarify as below.

    During Classical migration when upgrading system i.e. SAP ERP 6.0 without EHP to SAP ERP 6.0 with EHP8. we have dependency to check OS, Database compatibility.

    Now if planning to update and migration using DMO i.e. SAP ERP 6.0 without EHP , ORACLE 11.2 to SAP ERP 6.0 with EHP8 on HANA 2.0

    Does we require to have same dependency for OS and database?

    Reason for asking as Sadow instance get created on PAS which is OLD server which has oracle 11.2 and EHP8 require oracle 11.3 or 12c

     

    Regards,

    Nikunj Thaker

     

    (0) 
    1. Boris Rubarth Post author

      Hi Nikunj,

      as you say, for an update (e.g. SAP ERP 6.0 without EHP to SAP ERP 6.0 with EHP8) you have to check OS/DB. This is true for a “pure” update with SUM, and true for a combined update and migration (DMO) with SUM.

      Not sure why you write “During Classical migration when upgrading system …” – for me, a classical migration is only the migration process as such, and this classical migration process itself does not include an update. Of course, typically you consider to have an update as a separate step in the same project.

      Regards,
      Boris

      (0) 
      1. Nikunj Thaker

        Hi Boris,

        Thanks for reply.

        I had wrote classical migration means without DMO.

        DMO based migration when moving to HANA.

        My question is when i am performing migration to HANA and update together still OS/DB dependency are applicable?

        EHP8 require Oracle database 12c.

        Planning update and migrate existing ERP 6.0 without any EHP with Oracle 11.2 to ERP 6.0 EHP8 with HANA DB.

        As Shdown instance get created on CI server which is old (ORACLE DB) hence i requiere to update oracle database to 12c prior EHP update and hana migration?

        Regards,

        Nikunj Thaker

        (0) 
        1. Boris Rubarth Post author

          Hi Nikunj,

          this is described in the respective SAP note for DMO. The relevant and actual note is listed on the landing page of the SL Toolset: http://support.sap.com/sltoolset, in section System Maintenance. As of today, it is SAP Note 2428170 for DMO with SUM 2.0 (SUM 2.0 because you target EHP 8). For target database type SAP HANA and source database type ORA, Oracle 11.2 is fine for the source db, in case of a target system based on 7.50 (EHP 8 is based on 7.50).

          Regards, Boris

          (0) 
  6. Scott Groth

    Hello Boris,

    We successfully used SUM w/DMO to migrate our BW 7.31 AnyDB system to BW 7.5 on HANA 1.0 on Power (BE). We had great success with the product and achieved transfer rates up to 1 TB per hour in the DMO phase.

    We would like to use SUM w/DMO again to apply BW 7.5 Support Packs and migrate to HANA 2.0 on Power (LE). I have heard that SUM currently does not support HANA as a source DB and my need could not be met by SUM. I want to avoid having to apply BW 7.5 Support Packs and then turn right around and complete a HANA 1.0 Big Endian => HANA 2.0 Litte Endian migration using the SDI Data Provisioning Server.

    THE ASK: Use SUM w/DMO where HANA is the source DB

    What can you do as a product manager for SUM w/DMO to make this a reality?

    Thank you for your consideration,

    Scott

    (0) 
    1. Boris Rubarth Post author

      Hello Scott,
      thank you for your suggestion. I understand you motivation.
      Nevertheless, I am sorry to tell you that running DMO on a source database SAP HANA will not be enabled.
      The migration from big to little endian is a specific nonrecurring scenario for which a specific tool is offered. Enabling this with SUM would be a huge development effort, and we have important other topics with high priority to work on.
      Kind regards,
      Boris

      (0) 
  7. Consultants Consultant

    Hi Boris,

    We are in process of migrating our systems to HANA enterprise cloud.

    Our source : CRM ehp3 , sql 2012 and windows 2012 r2.

    Is it possible to do a DMO from on premise to HEC  ? We know the restriction of DMO system move on windows source.

    Can we do this as two step?

    1.) Can we run a plain DMO from source .

    2.)Now our PAS will be on premise and HANA DB on SAP cloud at the end of the DMO process.

    3.) Then uninstall the PAS is on premise and install a new PAS on linux on HEC cloud.

    Our databse size is 2 TB

    we are from government services orgainsation and we cannot afford two downtimes.  Will DMO help on this scenario?

     

    Thanks

    Balaji

     

    (0) 
    1. Boris Rubarth Post author

      Hi Balaji,

      as listed in the respective SAP notes on DMO, this is not supported.

      “Using DMO for a migration across data center is not supported (PAS host and DB host in different data center). 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. Consider “DMO with System Move” instead.”

      Regards,
      Boris

      (0) 
  8. Consultants Consultant

    Hi Boris,

     

    Thanks for the update.

    Since system move with DMO is not supported on windows , shall we consider the DMO is not supported for cross datacenter migration on windows at all.

    So is this gives a conclusion only classical migration can be done on if we have PAS on windows and if we try to move to cloud?

     

    Thanks

    Balaji

     

    (0) 
    1. Boris Rubarth Post author
      Hi Balaji,
      support for these approaches depends on several factors, in your case it is not only Windows as OS, but also MS SQL as database type: this does not allow to run an Additional Application Server (AAS) on linux.
      Regards, Boris
      (0) 
  9. Krishna Pinisetty

    Hello Team

    We SAP HCM ECC 6.0 (no enhancement packs) would like to upgrade to HR Renewal 2.0 with SAP HANA BD migration. I’m new to this area, appreciate your advice what best way to plan this upgrade.

    1. Do we need to migrate database to HANA first ?
    2. Upgrade to HR renewal to with all Enhancement packs first and then migrate database to HANA ?
    3. Which is best recommended migration option ?

    Looking forward for your advice

    Thank you.

    (0) 
    1. Boris Rubarth Post author
      Hello Krishna,
      my assumption is: the product is a plain ABAP product with usual Add-Ons.
      Therefore, it should be possible to combine the upgrade with the migration to SAP HANA database, using DMO of SUM.
      Regards,
      Boris
      (0) 
  10. aamir rahman
    Hello Boris,
    We SAP ECC 6.0 EHP4 would like to upgrade to SAP HANA 2.0 migration. I’m new to this area, appreciate your advice what best way to plan this upgrade.
    Our OS: windows 2008 and DB: SQL Server 2008 and system is Unicode.
    1. Do we need to upgrade our windows and DB first before conversion to SAP HANA. or SAP had any tool that directly migrate to HANA 2.0
    2. Which is best recommended migration option ?
    Looking forward for your advice
    Thank you.
     
    (0) 
  11. Pablo Luque

    Hello,

    I need to upgrade a SCM system with livecache to Hana with DMO tool.

    Livecache version of system is 7.7 into a windows 2003 server.

     I’ve read the central DMO note (2532577 – Database Migration Option (DMO) of SUM 2.0 SP01) but we can’t find any information/restriction about the minimum version of livecache for the migration to a integrated livecache on hana.

     Are there any restriction about the livecache version for the migration to hana?

      

    Thanks a lot in advance

     

    (0) 
  12. Team Basis

    Hi Boris,

     

    When we are Migrating from ERP 6.0 EHP4 to EHP8 from oracle to HANA used below configuration

    App Server IBM P8 server : 20 CPU’S ( 180 Logical CPUss)

    Database Size : 8TB

    Network Connection between Source and HANA : 1 GBps.

    Question :

    when we are setting R3loads in configuration phase , we found the restriction is to max 1000 for R3loads and no further.

    I would like to know if there is any work around to increase this value. Appreciate your help in this regard.

    Regards,

    Shiva

     

     

    (0) 
    1. Boris Rubarth Post author

      Hi Shiva,

      thanks for asking. Let me see if I got the point: you have already used 1000 R3loads, you have checked the performance of your application server, and you think that it is possible to still increase the number of R3loads above 1000? I’d like to know what the migration rate is that you have achieved (especially as we recommend to use a 10 Gbits network card).

      Thanks,
      Boris

       

      (0) 
      1. Team Basis

        Hi Boris,

         

        Thanks for your reply and apologies for my delayed response.

        Yes, we have used 1000 R3loads and would like to use more than that like 1200 as we have sufficient resources available at hardware level.

        We used 1 Gbits network. to clarify more below is the landscape

        PAS : on HP-UX with oracle DB

        AAS : for migration purpouse we installed an AAS on AIX server with 220 Cpu and 200 GB RAM.

        HANA : 4 TB Server

        These there servers are connected with 1 Gbits network and we achieved 32.54 MB/sec which is from EUMIGRATEDTRUN.log

        iPlease let us know if there is possibility to use R3loads more than 1000.

        Thanks,

        Shiva

         

        (0) 

Leave a Reply