Skip to Content

DMO with System Move – the use case to change PAS host during DMO


With Software Update Manager (SUM) 1.0 SP 20 (and higher), a new use case is introduced for DMO of SUM: DMO with System Move. This blog provides an introduction into this use case, which is of course described in the respective DMO guide, section “DMO with System Move”.

Note: you should be familiar with the DMO introduction before reading this blog.

Scenario is that you want to change the host of your Primary Application Server (PAS) instance during the DMO procedure. Until now, this was not possible during DMO.


With this use case, it is possible

  • to change the PAS host inside your System landscape, or
  • to move your system to a different network area / data center, or
  • to migrate your system from on-premise to HANA Enterprise Cloud (HEC), or other cloud providers


  • for SAP internal colleagues, this procedure was known as “DMO to SAP Cloud”. It is now available not only for targeting SAP Cloud.
  • “DMO with System Move” works for target database type SAP HANA and SAP ASE.
  • Restrictions are listed in the SAP note for DMO, see



  • Before starting the DMO procedure, you have to set up the new PAS host in the target landscape, in addition to the target database
  • You do not have to set any specific control file or parameter before starting the SUM

Enabling the use case

  • On the dialog with DMO details (like Migration Key), an option “DMO with System Move” is offered.
  • When this option is selected, the SUM will execute some tasks in the source landscape (like export the data from the source database), and afterwards execute some tasks in the target landscape (like Import the data to the target database).
  • In the source landscape, the target database parameters (like database host name) do not have to be provided
  • Once the tasks in the source landscape are finished, the SUM will tell you on a dialog to copy the SUM directory to the target landscape, in which the procedure will be continued. The SUM directory contains all required files
  • Transfer of SUM directory can be done e.g. via network (if possible), or via USB disk.

To reduce the downtime, it is possible to use a parallel mode in which data export and data import is running in parallel. Interested? You have to consult the DMO guide anyhow – the parallel mode is described in there, and is beyond this short introduction.

Kind regards,

Boris Rubarth
Product Manager SUM, SAP SE

You must be Logged on to comment or reply to a post.
  • Hello Boris Rubarth,

    Can we move to Cloud provider using Classic DMO (no System Move) then uninstall PAS and ASCS in source datacenter and then install a new ASCS and PAS on cloud provider?

    Is this technically possible and/or supported? 

    Best regards,


    • Hello JAM,

      for standard DMO, this approach is not supported, and we have noted this in the respective SAP note on DMO:

      “Using DMO for a migration across data center is not supported (PAS host and DB host in different data center). …”

      You find the actual note listed in

      Best regards, Boris


      • Thank you for the input Boris Rubarth . Let me explain a little more the scenario:

        The system we want to migrate is currently on iSeries platform. We want to move the system to a cloud provider where there’s no iSeries Platform available. Thats why we can’t use the “System move” option.

        So we were thinkg about using the Standard DMO across datacenters until the migration process is done, Not for productive use. After the DMO process have finished, uninstall the PAS and ASCS on current datacenter and then install them in the Cloud datacenter, then Go Live. Can this be supported or work as an exception?

        Best regards,




  • Hi Boris,

    can you brief me about the serial mode of System move.I have selected serial mode and the SUM process is completed in source host and i have moved the SUM directory to target host and it has started in phase MAIN_MIGSERIALSETUP/HOSTCHANGE_MOVE.On my target host it is asking the PAS host and instance number ,so the input should be from my old host or new,when i proceed it search for usr/sap/SID/profile with new host but there is no new profile created yet.Do we need to do anything manually to bring it on the target host?I dont see any special step on guide for serial mode.



    • Hi Aamrin,

      all parameters that SUM asks for on target are about target PAS. If you have installed a PAS, then there are profiles created. This is independent on whether serial or parallel mode is used.

      Regards, Boris


      • Hi Boris,

        Thanks,i was missing the PAS instance,after installing it worked.

        Downtime migration phase is over  on target host but i am stuck with saplikey issue .here is the log,i tired to delete it manually but it is giving me error”Can’t delete any license keys because of an error when trying to retrieve all records from the store.”

        3 ETQ120 20180710093923: PID 10326 execute ‘~/exe/saplikey -get’, output written to ‘/usr/sap/SUM/abap/log/SAPLIKEY.OUT’.
        3 ETQ122 20180710093923: PID 10326 exited with status 0 ” (time: 0.0/ 0.0/ 0.0/766MB real/usr/sys/maxmem)
        2 ETQ399 Retrieved local hardware key from ‘saplikey’ call as ‘Q1488002337’.
        1 ETQ399 Installing new temporary license for system.
        3 ETQ120 20180710093923: PID 10327 execute ‘~/exe/saplikey pf=/usr/sap/D01/SYS/profile/D01_D00_uscls4hd01cs1 -delete D01 Q1488002337 *’, output written to ‘/usr/sap/SUM/abap/log/SAPLIKEY.LOG’.
        3WETQ122 20180710093924: PID 10327 exited with status 2 ” (time: 1.0/ 0.0/ 0.0/766MB real/usr/sys/maxmem)
        1EETQ399 Last error code set is: Process /usr/sap/SUM/abap/exe/saplikey exited with 2, see
        1EETQ399X’/usr/sap/SUM/abap/log/SAPLIKEY.LOG’ for details
        1EETQ204 Upgrade phase “INSTTEMPLIC_MIG” aborted with severe errors (“20180710093924”)

        In SAPLIKEY.OUT ,we are getting below logs:

        EXECUTING /usr/sap/SUM/abap/exe/saplikey -get
        ===…could not load SSF library /usr/sap//SYS/exe/run/ .

        E 543 likey_init_clt: Couldn’t load SAPSECULIB
        (“/usr/sap//SYS/exe/run/”) using function SsfSupInitEx (), rc
        = 10 (no library).
        E 542 likey_init_clt: At least one more attempt to load the SAPSECULIB will




          • Hi Boris,

            My issue was resolved .The solution to this was upgrading the kernel files in the /SUM/abap/exe/ directory .After the update I was able to proceed further and complete  my S/4 HANA conversion successfully.




  • Hello Mr. Rubarth,

    We want to perform a really big change on our SAP BW systems and I’m not sure if this is possible with the SAP DMO system move option. Maybe you can give me a hint if our plan is working or not:

    Source: SAP BW 7.4 SP13, on Oracle and HP-UX on ia64 machine

    Target: SAP BW/4HANA with HANA Database on SLES 12 and X86 -> completely different server and architecture

    Maybe the migration directly to SAP BW/4HANA is not possible. Then the we got to SAP BW 7.5 on HANA database on SLES 12 and X86. And in a second step with the SAP-BW/4HANA-Starter-Add-On to SAP BW/4HANA .

    Is this possible in general or do we need to make at first a heterogenous system copy from HP-UX to the new Server with SLES 12 on X86. And afterwards use DMO without system move option?


    Thank you very much!


    Best Regards






    • Hello Sebastian Simon,

      for targeting SAP BW/4HANA 1.0, SUM is not the tool of choice: you use SPAM/SAINT for that step.

      You may consider to use SUM 2.0 for the step from SAP BW 7.4 on Oracle to SAP BW 7.5 on HANA. In addition, you may check if “DMO with System Move” is an option to switch from HP-UX to SLES 12 on X86 in the same procedure.

      Best regards,

      • Thank you for your comment. You are right, to SAP BW/4HANA we hve to use SPAM/SAINT.

        But all in all the change from SAP BW 7.4 on Oracle to SAP BW 7.5 on HANA, together with system move to X86 (in one step) is possible, correct?



        • I looks to me as if this should work – please check the details in the respective notes so that we do not oversee any restriction. Regards, Boris

  • Hi Boris Rubarth,

    We are planning to migrate our system to HANA.

    We are running on windows 2008 with MSCS cluster and planning to move S4HANA1809/Suse Linux.

    for moving to S41809, Windows server should be on windows server 2016 but upgrading OS from 2008 to 2016 is 2 step process. 2008–> 2012 and 2012 –> 2016 but In place upgrade is not supported in case of 2008 –> 2012.

    Please suggest do we need to Install Additional Application server on windows 2016 and run SUM from there. Do we need to have ASCS on that new server or upgraded windows 2016 OS.




    • Hello Nikhil,


      We are in the exact same setup you described : did you find a solution regarding the installation of an additional Application Server running on windows 2016 OS. :

      Did you need to upgrade the instance hosting the ASCS to windows 2016 OS or was it sufficient to install and Additional Abap Instance on windows 2016 OS


  • Hello Boris,


    Can we use System Move option and keep Source and Target systems running as end result?


    We are required to build new landscape (N+1) on HANA keeping source landscape untouched until Production migration is done. Just to elaborate, we will follow below high level approach.

    1. Source system running on DB2 and have NW stack compatible for HANA. We will start DMO with ‘System Move’ option.
    2. We will build target skeleton (NW of HANA).
    3. When DMO on source reaches to end of HOSTCHANGE_MOVE stage, we will copy SUM folder to target server (considering Serial mode) would be selected.
    4. Launch SUM on target and proceed with import and proceed to Finalization/Cleanup phase.
    5. We assume this will still keep source system in consistent state and choosing ‘Reset’ option on Source will take Source system to original state and both systems would be in usable state.
    6. Further, we will use System Rename feature of SWMP on target system to change system SID. This would be followed up by few post build steps like BDLS etc.

    Another (most recommended) alternative would be to build target first as system copy (on DB2) and then carry out in-place DMO. But just wanted to see if we can follow above approach to achieve same results.



    Prasad Desai

  • Hello Boris,

    Thanks for your input in this blog,

    We are moving to azure cloud from Windows 2016/ SQL Server 2008 R2 / EHP4/NW7.01 to Linux/HANA/EHP8/NW75 , planning to use SUM DMO with system move ( PAS from Windows 2016 to SUSE Linux  12 ) using SUM 2.0 SP4, I read the manual and notes , so far I don’t see any restriction, currently I am also testing the process and  at prepare phase and SUM didn’t complain so far  but I am hearing that it is not possible, any restriction on DMO to move PAS from Windows to Linux ? Your reply will be appreciated.

    Thanks , Al Mamun

    • Hello Al Mamun,

      as always, any restrictions are mentioned in the respective SAP note for DMO, currently SAP Note 2644872 (for DMO with SUM 2.0 SP 04).

      You read the note, as I did – I do not see any restriction for your scenario, if you follow the description – but you better check again.

      Thanks, Boris

  • Hi Boris,

    in the features you list:

    • to migrate your system from on-premise to HANA Enterprise Cloud (HEC), or other cloud providers

    DMO with System Move works with a scenario from SAP ECC on premise to HANA Enterprise Cloud (HEC) Single Tenant Edition (STE) to go to S/4HANA as well correct?




    • Hi Mario,

      thanks for asking. SUM does not allow to convert an SAP ERP system (contains custom code, modifications, and esp. custom specific customizing) to „Single Tenant Edition“. For a conversion with SUM, the target SAP S/4HANA will always be the on-premise edition.

      Regards, Boris

      • Hi Boris,

        thanks for the quick response.

        Would it work to first do SUM with target S/4HANA on-premise and afterwards perform a DMO from on-premise to HEC “Single Tenant Edition”?

        Or does HEC “Single Tenant Edition” not allow a Database Migration Option and its always build from ground up in STE?



    • Hi Rainer,

      sorry to say that I do not see an easy way to achieve this. SUM does not offer a procedure for this. You may consider to adapt this manually, but I have no complete list of actions to be considered. Editing the /etc/hosts file would have to be done in downtime, the profile files have to be adapted, and maybe service registration as well.

      Kind regards, Boris