Skip to Content

Scenario

With Software Update Manager (SUM) 1.0 SP 20, 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.

Feature

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

Note:

  • 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 2377305 for DMO with SUM 1.0 SP 20.

Approach

Preparation

  • 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

To report this post you need to login first.

91 Comments

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

  1. Dharmendra Kumar

    Hi Boris,

    Thanks for this blog.

    I’m closely following SUM and DMO update from SP19 to SP20.

    Can you please confirm –

    1.With SP20, Is cross data center migration supported, from on-premise to Azure, AWS, etc..?

     

    2. Target DB would be HANA, Source is MaxDB in my scenario and with HANA as target DB, I believe we must have

    Linux  as OS for PAS, however can we have other OS like windows for AAS, within same landscape. So, HANA and PAS will run on Linux and AAS on Windows?

     

    Regards,

    Dharmendra Kumar.

    (0) 
    1. Boris Rubarth Post author

      Hi Dharmendra Kumar,

      thanks for your comment.
      1) This is what I tried to express with
      “With this use case, it is possible

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

      2) Concerning the (important) details, my recommendation is to check the respective note.
      As of now, this is SAP note 2377305 for DMO with SUM 1.0 SP 20, and target PAS has to be on Linux. Concerning the setup of AAS on windows, this is not determined by DMO – I guess it works, but you will have to check PAM on this.

      Regards,
      Boris

      (0) 
  2. Dharmendra Kumar

    Hi Boris,

    Point 1 is closed, – understood with SP20 cross DC migration is supported.

    For point 2, I should have NOT put here. I totally agree DMO has nothing to do with OS, and PAM is right tool to check.

    Thanks for your reply.

     

    Regards,

    Dharmendra Kumar.

     

     

     

     

     

    (0) 
  3. Nicholas Chang

    Thanks Boris! Been waiting and nice to have feature! Thanks for your team on the ongoing improvement and innovation.

    one question, any idea how big is the “SUM” directory to transfer if using serial mode? since all the contents are written to the dir *ut*, *dt*, compare to export dump on classical migration?

    And source system downtime starts once enter migration export phase?

    Hope to hear from you,

    Thanks,

    Nicholas Chang

    (0) 
    1. Boris Rubarth Post author

      Hi Nicholas,

      “how big is the SUM directory” -> how big is your database? 🙂

      Both SUM as well as SWPM (classical migration) trigger R3load to export the data (export dump). So for this approach, SUM will trigger R3load using the file mode instead of pipe mode, of course.

      Source system downtime starts once we enter the downtime 🙂 … in uptime, the repository is already exported, like for Standard DMO (where repository is already migrated to target DB during uptime).

      Regards, Boris

      (0) 
  4. Nicholas Chang

    Hi Boris,

    “Both SUM as well as SWPM (classical migration) trigger R3load to export the data (export dump). So for this approach, SUM will trigger R3load using the file mode instead of pipe mode, of course.”

    Does it means we’ll expect the SUM directory size is around the size with export dump by SWPM, taking in all the compression. For classical migration export dump, normally the size is around 20-30% of the DB size. Is it the same apply to export with SUM?

     

    Below pic is taken from the the guide for serial approach. Based on the explanation, looks like the source system are entering downtime once it start migration export on source db, to prevent any changes on the system while the contents are being exported?

    And the exported contents are only start importing into target HDB once the “SUM” directory is moved to target PAS?

     

    Thanks,
    Nicholas Chang

    (0) 
    1. Boris Rubarth Post author

      Hi Nicholas,

      the export files are created by R3load for both tools SUM and SWPM, so yes: the size is similar.
      The sequence of processing concerning migration is (for serial approach):
      • in uptime, development lock is set, shadow repository is created on source system
      • shadow repository is then exported (still uptime)
      • downtime starts, application tables are exported
      • SUM folder has to be copied to target landscape
      • you start SUM run in target landscape, it imports shadow rep and app tables
      Regards, Boris
      (2) 
  5. Gilberto Gangarossa

    Hi Boris. great blog, and very intresting topic.

    Reading the note 237738, I have a doubt about the step below

    ——————< D033068 02/JUL/14 >————————————-
    A new BR*Tools package is required for update or upgrade to NW 7.4 SP08 and higher
    If you want to update or upgrade your SAP system to SAP NetWeaver 7.4 SP08 and higher, install the latest
    BR*Tools package (7.40 patch level 10 or higher) beforehand.

    The new BR*Tools 749 are supported only  for AIX 7.1, but the operating system release of my source system is AIX 6.1.

    So I can’t install the new BR*Tools 749 (R3load, ecc ..)  on my source system, which is a prerequisite to start the Upgrade/Migration !

    I’m I rigth or it is a false problem ?

    Thanks in advance

     

    (0) 
    1. Boris Rubarth Post author

      Hi Gilberto,

      my information is that BRTOOLS are downward compatible – do you have a source that states something else?

      Regards, Boris

      (0) 
      1. Gilberto Gangarossa

        You rigth, a little explanation of what we are doing:

        Upgrade to ECC (HCM) EHP8 from ECC (HCM) EHP4 and move fron Oracle to HANA and from AIX 6.1 to SUSE 12.

        Now, we will execute the SUM SP 20, for system move with DMO, on the source system (AIX 6.1) wich we guess it will use the kernet 7.49 (ie.. R3load) , that is certified only for AIX 7.1.

        Our concern  is that is not possible unless we upgrade the Operating System of the source from AIX 6.1 to 7.1, which is not possible anymore, sigh sigh …

        Thanks for the qick response

        (0) 
        1. Boris Rubarth Post author

          Hi Gilberto,
          OK, now I got it … yes, there are these dependencies, as even for “DMO with System Move”, the shadow system (which is on the new release) is created on the source system.
          Regards, Boris

          (0) 
  6. Manas Srivastava

    Hi Boris,

    I was trying to use SUM 20 with system move option in my scenario where we have to migrate from BW 7.31 SP05 on SQL (On Prem) to BW 7.31 SP05 on HANA (in AWS). When i started the SUM tool it asks for stack.xml file, to bypass this since I was not planning to upgrade i used the option for using SUM for only migration by creating SAPup_add.par and adding migration_only = 1.

    Now the Extraction phase completed but I did not get any dialog screen in the phase PREP_INPUT/MIG2NDDB_INI. Also when I checked logs for this phase it said the Unsupported Target Vector, need atleast NW 740. I copied the target Kernel in the download directory which was provided to SUM.

    Do you have any inputs for this?

    Thanks,

    Manas

    (0) 
    1. Boris Rubarth Post author

      Hi Manas,

      according to SAP note 2377305 for DMO with SUM 1.0 SP 20, BW needs target release 7.40 or higher for DMO, but your target release is 7.31.

      Regards, Boris

      (0) 
  7. Arne Knöller

    Hi Boris,

    Thank you for sharing the updates! Great development of DMO over the last month.
    The restriction of data center boundaries has been removed with SP20 in note 2377305. My question is, what about the SAP support between on premise –> HEC/cloud providers with “classical” DMO, using pipe functionality for parallel export/import.
    Do you support such a scenario now as well ? Or is the support between data centers limited to the system move option?

    Regards, Arne

    (0) 
    1. Boris Rubarth Post author

      Hi Arne,
      thank you for the feedback, will pass it to the dev team!
      Support for “classic” DMO between data centers remains restricted, as we have this new Option “DMO with System Move” now.
      Regards, Boris

      (0) 
  8. Manoj Joshi

    Hi Boris,

    DMO with SP 20 is really wonderful benefits to SYSTEM move, we are planning to move IBM I 7.1 DB2 NW 731 to SAP HANA 2.0  NW 7.5 on cloud. DMO guide does not  mentioned any specific instruction or parameter optimization for DB2.  Any suggestion or pointer to note please.

    Regards,

    Manoj

    (1) 
    1. Boris Rubarth Post author

      Hi Manoj,
      apart from the guide, the respective SAP notes are to be considered.
      For SUM 1.0 SP 20, these are 2371752 (SUM) and 2371752 (DMO), and the notes referenced in there.
      Regards, Boris

      (0) 
    2. Amit Lal

      Hi Manoj,

      DB6 version 09.7 FP5 or higher, if target SAP_BASIS release is 740 SP8 or higher and lower than 751.

      Note: DB6 versions 10.1.0000 to 10.1.0003 are not supported

      Regards,

      Amit

      (0) 
  9. Sachin Digamber Pokalwar

    Hi Boris,

    Thanks for the update, could you also please confirm if we can use DMO for only HANA migration as typically DMO has been intorduced for performing Upgrade + HANA Migration.

    Best regards,

    Sachin

     

    (0) 
  10. Todd Scholes

    Hi Boris,

    Thanks for the blog and the replies to queries!

    A quick one – are scenarios able to be “combined”?  ie. We are looking to do both a “DMO without system Update” (move from ECC Ehp7 to HANA) and “DMO with system move” (migrate from HP-UX on premise to Windows in Azure (PAS and AAS Windows, HANA DB on Linux).

    In this case, would we simply set both the corresponding scenario flags to “1”?

    Todd

    (0) 
    1. Boris Rubarth Post author

      Hi Todd,

      thanks for asking.
      First approach is always to check the guide and the respective note … in this case this is covered by the section “DMO with System Move: Requirements and Restrictions” under “Note” in SAP Note 2377305 for DMO with SUM 1.0 SP 20 (=> yes, supported), and it includes an important note to be implemented.

      You simply set the flag for the scenario “DMO without System Update” – the other option is anyhow offered on the dialog (without flag).

      Please note that the scenario “DMO with system move” assumes that the target OS is linux,  as stated in the same section.

      Boris

      (0) 
  11. Ponnusamy P

    Hi Boris,

    Thanks for this blog.

    Need your confirmation on the below points. Currently we are planning to below migration using DMO with System Move

    Source System
    Application : BW 7.1 SP09
    OS/DB – IBM i 7.1 / DB2
    DC : On-premise

    Target System
    Application : BW 7.5 SP07
    OS/DB : Windows 2012 / HANA1.0 SP12.122.06
    DC : Virtustream
    1. With SUM SP20, Is migration supported from on-premise to Virtustream
    2. Our Target DB would be HANA and OS on Windows 2012, will it possible to run SUM 20 on Target window OS to run the DMO import.
    Gone through the Note – 2377305 ((c) DMO with System Move: Requirements and Restrictions)        under restrictions, we can see the point mentioned as below

    If the OS of the source PAS host is different than OS of the target PAS host, that is, the source OS is not Linux, proceed as follows:
    After the DMO procedure is finished on the source system, and you have copied the SUM folder from the source to the target application server, extract the SUM archive for the target OS over the SUM folder to replace the executables. Make sure that you use the same SUM version (including patch level) in the source and the target system landscape.

    Is this means that I can run SUM on windows 2012 on target PAS. Can you please confirm.

    Regards

    Ponnusamy

    (0) 
  12. Amit Lal

    Hello Boris,

    Thanks for your latest blog.

    As per DMO Guide, in section “Parallel data transfer mode using a script ” is available. Just to clarify what transfer method DMO is using – flat file or memory pipe with script  dmo2sapcloud.sh.?

    Secondly, DMO benchmarking tool still works in ‘DMO with System Move option’, to verify the network latency and transfer rate etc.? 

    Thank you in advance,

    Amit Lal

     

    (0) 
    1. Boris Rubarth Post author

      Hello Amit Lal,

      for scenario “DMO with System Move”, the R3loads will in any case work in file mode – independent on sequential or parallel mode. R3loads in source landscape are only exporting to file, R3loads in target landscape are only importing from file.
      Benchmarking works for this scenario as well, but it will only benchmark the respective part: either source or target SUM/R3load activity. It will not consider transfer rate or latency between the landscapes.
      Regards, Boris

      (1) 
      1. Amit Lal

        Hi Boris,

        Many Thanks for clarification.

        When we choose DMO with system move option, do we need to manually add ‘file mode’ parameter in SAPup_add.par file or it takes automatically? By default it look for memory pipe, correct?

        Can we use “Migration Repetition option” /migrate_option/OPTIMIZECLONING =0, with “DMO system move” option particularly for parallel transfer?

         

        Thanks & Best Regards,

        Amit Lal

         

        (0) 
        1. Boris Rubarth Post author

          Hi Amit Lal,

          no need to set a parameter for R3load mode for “DMO with system mode” as file mode is default and pipe mode does not work – that is why the guide does not mention any parameter.
          We do not recommend to use the “Test cycle” option for “DMO with System Move” in parallel mode, as it will interfere with the continuous data transfer.
          Please note that the Migration Repetition Option / Test cycle option is part of the dialogs since SUM 1.0 SP 14 already (see https://blogs.sap.com/2015/12/03/short-history-of-dmo/), so no parameter required.

          Regards, Boris

          (1) 
          1. Amit Lal

            Hi Boris,

            Thanks for great piece of information. This makes perfect sense for not using test cycle option for DMO with system move in parallel mode.

            One major concern in our case and looks like guide is not covering up is – “Flat file encryption and decryption” while data transfer to cloud, DMO has any build-in capability since its using SSH as prerequisite for serial or parallel data transfer?

            Thanks again, Amit Lal

            (0) 
            1. Boris Rubarth Post author

              Hi Amit,
              SUM is triggering R3load for export to file system – no encryption available for these tools.
              Regards, Boris

              (1) 
              1. Amit Lal

                Thanks a lot Boris.

                I’ll share my experience once I start migration with the move option sooner. Still I would suggest to have a separate SAP Note for DMO with move option with all details, like we have a separate notes available for “Downtime-Optimized DMO” just a thought.

                Also just to let you know our ‘cloud provider’ convincing us not to use RSYNC, instead their tool to place the exported dump which is way faster compare to dmo2cloud.sh and rsync script in parallel mode.

                We are exploring both options for placing 45+ TB of BW system on cloud, which is challenging task itself.

                Thanks again.

                Regards, Amit Lal

                 

                (0) 
  13. Gilberto Gangarossa

    Hi Boris, I have a quick one,

    I’m upgrading to ECC (HCM) EHP8 from ECC (HCM) EHP4 and move fron Oracle to HANA and from AIX 6.1 to SUSE 12.

    Now, we executed the SUM SP 20, for system move with DMO, on the source system the SUM finisched succesfully, but if I try to logon it says “Logon not possible Upgrade still running”.

    As my understanding, the system move option let you use the source system after the SUM ends.

    Did I miss something ?

     

    (0) 
    1. Boris Rubarth Post author

      Hi Gilberto,
      after finishing the SUM run on the source (and after all files are transferred to the target), you will have to reset the SUM run on the source system. This will restore the status of the source system – and start it automatically.
      Regards, Boris

      (0) 
  14. Vippin Chhibbar

    Hi Boris

    We are executing the SAP BW migration only with PAS move and using the parallel transfer mode. Can you please let us know if we can execute the DMO for the target system on the HANA database server it self to improve the performance?

    Thanks,

    Vipin

    (0) 
  15. Vippin Chhibbar

    Hi Boris,

     

    We are also considering migrating out SAP BW system from Oracle to HANA DB using the migration only option but without the PAS move:

    1. In this case we assume that the DMO will still use the default R3load mode as pipe mode and this the export/ import should be faster? Is this assumption correct?
    2. Does the parallel export/import still work with the pipe mode and not moving the PAS?
    3. We will install the PAS after the migration is completed if 1,2 assumptions are correct.

    Please suggest.

    Thanks,

    Vipin

    (0) 
  16. Ponnusamy P

    Hi Boris,

    Need to clarifications on DMO with System Move. This is for our BW 7.31 System DB02 to HANA.

    1. Can we use HANA DB Server as Target PAS host. becoz in new HANA Version, its supports running PAS on HANA DB
    2. Do we need to prepare Target PAS host with ASCS, DB and PAS with Vanila BW System to start SUM tool for import or when we start SUM tool, it will prepare ASCS, DB and PAS.

     

    Regards

    Ponnusamy

     

    (0) 
    1. Amit Lal

      Good question – You need to build vanila system on target and PAS can be used with HANA DB as standalone scenario.

      (0) 
    2. Boris Rubarth Post author

      Hi Ponnusamy,

      you can use the PAS on HANA host if you like. You will have to setup the target instances, as the SUM/DMO does not install any instances – the guide describes how to Setup the target PAS.

      Regards, Boris

      (0) 
  17. Vippin Chhibbar

    Thank you Boris.

    So If I execute the DMO for migration only scenario and not movng PAS (with the pipe mode), will I still be able to use the rsync script dmocloud.sh for parallel transfer of data files to target and trigger the import along with the export also running in parallel on source?

    Thanks,

    Vipin

    (0) 
    1. Boris Rubarth Post author

      Hi Vippin,

      the term “parallel transfer” and the rsync script are only valid in the context of scenario “DMO with System Move”. For the standard DMO (Migration only, or update&migration), the R3loads are anyhow running in parallel.

      Regards, Boris

      (1) 
      1. Amit Lal

        Hi Boris,

        Thanks for inputs.

        Idea is to use Standard DMO for migrating to cloud since we have dedicated express network route which is as per cloud provider is similar to on-premise server and debating for not using DMO wit system move option since only use flat file method.

        Just want understand any particular pointer for not using std. DMO for migrating to Cloud?

        Regards,

        Amit

        (0) 
        1. Boris Rubarth Post author

          Hi Amit,

          what we had stated in the note 2328517 for DMO with SUM 1.0 SP 19 is still true for standard DMO (not for “DMO with System Move”):
          “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.”

          Regards, Boris

          (1) 
          1. Amit Lal

            Hi Boris,

            Thanks a lot…This is really informative. We’ll try that option as well to prove the case to Cloud provider.

            Regards,

            Amit Lal

            (0) 
  18. Michele Donna

    hello

     

    Does this cover Java instances as well ? Or only ABAP ? I would like to try to migrate a Portal 740 SR2 from Oracle to Hana

     

    thanks and best regards

    Michele

    (0) 
  19. Todd Scholes

    Hi Boris,

    We are looking to migrate and change our ECC system to HANA DB from MaxDB, and DMO SP20 (system move) is attractive for us as (according to the note if I’ve read it correctly) it enables:

    – Running SUM on Source system AAS without needing to split ASCS; and

    – Allows running the source and target DB in parallel (which we would like to do for purposes of trials and testing).

    However, our end state target OS is Windows, and the note says target PAS must be Linux.

    Is the only way for us to “get around” this, to perform the DMO system move to a LINUX PAS, and then perform a SWPM System Copy to move the ASCS and PAS to Windows servers?

    Thanks a lot

    Todd

     

    (0) 
    1. Boris Rubarth Post author

      Hi Todd,
      yes and no:
      I agree to your two bullet points, and to the work around, but there is an important limitation in SAP note 2377305 that hits your scenario: SAP HANA as source database is not supported, sorry.
      Kind regards, Boris

      (0) 
      1. Todd Scholes

        Thanks for the reply Boris.

        I may not have explained things 100% clearly.

        Our proposal is that we would use SUM DMO SP20 to migrate our ECC system to HANA DB and Linux PAS.   Then, we would just use the standard/classical SWPM system copy tools to “migrate” the PAS and ASCS only to Windows servers.  HANA DB would not be changed.

        Does that make more sense?  From the note, the HANA as a source DB restriction seems only related to using the DMO tool..?

        Todd

        (0) 
        1. Boris Rubarth Post author

          Hi Todd,

          apologies – your text was clear, I just didn’t read well. Sure DMO from MaxDB to SAP HANA is possible, using “DMO with System Move” to PAS on linux OS, and afterwards using SWPM to move PAS & ASCS to Windows.

          Regards, Boris

          (1) 
  20. Ashish Prakash

    Hi Boris,

    -I Understand that in Serial Mode  transferring of Export(Repository+Application Table) directories (migrate_*)  can only be triggered after downtime phase completed on Source System

    -In my scenario where Source OS=AIX 7.1 and Target OS=RHEL 7,2  I wanted to use parallel mode of instead of serial , now since the Source and Platform has different flavor of Unix , automated scripts cannot be used as provided in DMO Guide.  Considering the above situation can I manually begin transferring the data using Rsync utility  at an interval of 30 min or so .

    Regards

    Ashish

    (0) 
  21. Vippin Chhibbar

    Hi Boris,

     

    Is it possible to distribute the R3load processes for export/import to additional application servers both on source and target size with DMO with PAS move option? This can certainly help in reducing the downtime and also with minimal impact to the production operations during the uptime export and other activities.

    Please advise?

    Thanks,

    Vipin

     

    (0) 
  22. Rajdeep Bhattacharjee

    Hi,

    We are trying to perform the Datacenter migration(using option system move) for the first time on oracle to HANA migration with SUM DMO.

    I was going through the additional steps mentioned in DMO document required for performing “system move” and i am not clear on the below point 1(install & update host agent) point 2(install the database instance) & point 3(Install the primary application server as SAP NetWeaver system).

    Can someone please help me here.

     

    1. install & update host agent in target server

    so do i need to install & update host agent manually in both Target Hana database server & target hana application server?

    2.Install the database instance.

    do you mean the database instance installation from SWPM or database installation from hdbinst/hdblcm & most important before which phase(extraction,configuration,check or pre processing) or step we need to have this done.

    3.Install the primary application server as SAP NetWeaver system

    Do i need to install the PAS instance from SWPM in the target application server & before which phase(extraction,configuration,check or pre processing) this needs to be done.

    & Its mentioned in the DMO document to install PAS as SAP NW system but we are working on the ECC system migration so should we chose PAS of NW system or PAS of ECC system

     

    Thanks,

    Rajdeep

    (0) 
    1. Boris Rubarth Post author

      Hi Rajdeep,

      the steps you are referring to are part of the section “System Move: Preparing Target System Landscape”. The text below the section title says “… you have to prepare the target system landscape beforehand”, that means before the SUM is started in the target landscape.
      All parts of the installation are done using the Software Provisioning Manager, apart from the SAP Host Agent. Like in the source landscape, the SAP Host Agent has to be up to date on the application server on which the SUM is running.
      Concerning your question on ECC system, the guide clearly states that “the installation should be … a pure AS ABAP system … [because] the database content will be deleted afterwards”

      Regards, Boris

      (0) 
      1. Rajdeep Bhattacharjee

        Hi Boris,

        Thank you so much for your reply.

        I have one last query: To which database should i connect the PAS post installation in the target server.To the target hana database or the source oracle database?

        and Just to summarize on the points,the below action i need to perform before the SUM is copied to the target application server.

        Let me know if i am wrong or missing somewhere.

        1.install host agent

        2.Install ASCS in the target server using Software Provisioning Manager,.

        3.Install Database in the target hana database server using Software Provisioning Manager.

        4.Install PAS in the target server using Software Provisioning Manager–-To which database should i connect the PAS post installation.To the target hana database or the source oracle database?

        (0) 
        1. Boris Rubarth Post author

          Hi Rajdeep,

          PAS is located in target landscape, and has to connect to the target database, SAP HANA.

          Imagine that the scenario allows a transition to other network areas or to Cloud where access to source database is not possible.

          Regards, Boris

          (0) 
          1. Rajdeep Bhattacharjee

            Thanks so much Boris for clearing my confusion. It was a great help as we are trying this for the first time.

            I will start the procedure and get back if i am facing any issue specific to this feature during implementation. 🙂

             

             

             

            (0) 
  23. Vippin Chhibbar

    Hi Boris,

    We are currently running the BW migration on HANA with PAS move option and currently running the parallel transfer with rsync process. We  observed in the downtime phase that for transfer of the files only one rsync process runs throughout the parallel export/import, which makes the import slower: (export is 50% done while import is still running at 6% )

    1. Is there a way we can execute the multiple rsync processes during the parallel transfer with DMO?
    2. In case we want to execute the multiple rsync processes manually what all files under migrate_dt* and migrate_ut* etc…. do we need to copy to the target.?

    Please advise.

    (0) 
  24. Vippin Chhibbar

    Hi Boris,

    With parallel transfer option while migrating BW to HANA on cloud, we noticed that only one rsync process is running on the source system during the export/import which makes the export faster but import slower (i.e. export is 50% completed while import is 6%)

    1. Is there a way we can increase the rsync processes in the script file using some parameter ?
    2. Can we execute the multiple rsync processes manually on the source system so as to migrated the already completed export packages to the target? if yes then what files can we migrate from migrate_dt folder from source  to target?

    Please advise.

    Regards,

    Vipin

    (0) 
    1. Boris Rubarth Post author

      Hi Vipin,

      the rsync script delivered with the SUM tool is a proposal, and it can be viewed and adapted according your priorities. This requires knowledge on rsync and on network transfer optimization, an area for which I can’t provide recommendations.
      the folders to be transferred are listed on the SUM dialog for phase HOSTCHANGE_MOVE.

      Regards, Boris

      (0) 
  25. Rajdeep Bhattacharjee

    Hi Boris,

     

    I am in process of installing the ASCS & PAS on the target server before copying the SUM folder in the target server.

    I have a question here. while installing the target PAS & ASCS instance in the target server is there any dependency that the SID of PAS & ASCS source application server should be same as the SID of target application server?

     

    Thanks,

    Rajdeep

    (0) 
    1. Boris Rubarth Post author

      Hi Rajdeep,

      SID has to be the SID of the source system.

      In general, the DMO procedure will keep the SID of the source system, and for the acenario “DMO with system move” the consequence is that the target sytem has to be build up with the same SID as the source system.

      Regards, Boris

      (0) 
      1. Rajdeep Bhattacharjee

        Hi Boris,

        Thanks for the reply.

        During the last mock ecc migration without “system move” we were using SUM 19 we got the configuration phase HDB_MIGCONFIG(database migration initialization) where it asked target database hostname,target system license, target SID,instance number & HDB_Prepare(required migration specific password) where it asked dbacockpit password, but this time while using SUM20 & “system move” option in that we are currently in preprocessing phase(MAIN_INIT/REPACHK1) & we didnot get any such phase/step till now. Is this something to do with SUM20 change of steps or this change related to “system move”.

         

        Thanks,

        Rajdeep

        (0) 
        1. Boris Rubarth Post author

          Hi Rajdeep,

          “DMO with System Move” will only ask for target database information once running on target PAS.

          Regards, Boris

          (0) 
  26. Bret Applegate

    Hi Boris,

    According to the DMO note, the source application server (central instance) also has Operating System restrictions (Unix based only).   Can you confirm whether or not it is being worked on to add Windows operating systems as an option for the source PAS?  Or will this remain Unix/Linux only long term?

    Thanks,

    Bret

    (0) 
    1. Boris Rubarth Post author

      Hi Bret,

      what I can confirm is that we are aware of the requirement to support more than Unix. I guess it will be a question of complexity and priorities of other requests.

      Regards, Boris

      (0) 
      1. Bret Applegate

        Thank you for the quick response!  This is a pretty major restriction for the SMB market in particular where a lot of the customers that I see are running on Windows/SQL Server.

        (0) 
  27. InfoSys InfoSys

    Hi Boris,

    Currently we have requirement to upgrade and migration BI Java Portal to HANA

    Source : OS400/DB2 NW 7.31

    Target  : Windows/HANA NW7.5 SP08

    Is there any options enabled in SUM DMO for Java (Migration and Upgrade) in single step in latest SUM version.

    or we have to use classical approach.

    Regards

    Ponnusamy

    (0) 
    1. Boris Rubarth Post author

      Hi Ponnusamy,

      DMO is only for AS ABAP based systems (as described in SAP Note 2377305). No plans to change this. So for AS Java based systems, you will have to use the classical approach.

      Regards, Boris

      (0) 
  28. Rajdeep Bhattacharjee

    Hi Boris,

     

    we are in the phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW/SUBMOD_MIG_SER_IMP/EU_CLONE_MIG_DT_IMP in the target server in the execution phase after copying the SUM & starting it in the target server.

     

    We are getting below error:

    EUMIGRATEDTIMP_NEW.LOG:

    1EETQ399 Last error code set is: Error in network interface: NIEINVAL (0/149042 written)
    1EETQ204 Upgrade phase “EU_CLONE_MIG_DT_IMP” aborted with severe errors (“20170808085305”)

    SAPup_NEW.log:

    Error message set: ‘Error in network interface: NIEINVAL (0/149042 written)’

    HDBMONITOR.LOG:

    EXECUTING /…/SUM/abap/bin_749/SAPuptool hdbmonitor sleep=30 outfile=/…/SUM/abap/htdoc/HDBMONITOR.CSV
    ** Parent died – exiting.

    HTTP.trc:

    20170808064114:HTTP:0:FATAL ERROR: pid file ‘/…/SUM/abap/srv/server_sumabap.pid’ contains different pid <> != <>
    20170808085248:HTTP:0:Starting trusted connection with ‘_lmsl_sumabap_<SID>’
    20170808085304:HTTP:0:FATAL ERROR: pid file ‘/../SUM/abap/srv/server_sumabap.pid’ contains different pid <> != <>

     

    I am thinking,could it be due to the reason of specifying more number of r3load(we used 300 r3load) while the CPU 4 & memory is 32 GB.

    We didnot get any update for this issue in SUM screen and it went to hang mode.

    Can you suggest How do i restart SUM in the target server now in this phase(MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW/SUBMOD_MIG_SER_IMP/EU_CLONE_MIG_DT_IMP) ? i see so many r3load process running in target server & its not possible for me to kill them one by one?

    (0) 
  29. Dominik Eggimann

     

    Hello Boris

    This is really cool.

    We have the following starting position:
    Source:
    ERP 6.0 EHP 8 NW 7.5 with DB2 on IBM i.

    target:
    DB Server: SLES with HANA DB
    App Server: SLES

    Will this scenario work?

    So the DB can be migrated to a server and the SAP instance migrated to a separate server?

    Many Thanks.
    Greeting
    nick

     

    (0) 
    1. Amit Lal

      This scenario will work for sure.

      Requirements for Source System and Source Database: (See SAP Note # 2377305)

      • Database: All source databases excluding SAP HANA
      • Operating System (OS) of source primary application server (PAS) host:  Any Unix-based operating system. In case of an IBM DB2 for i database, the PAS must always run on a IBM i Host.

      Regards,
      Amit

      (0) 
  30. Andreas Reuter

    Hello

    am facing an error during SUM DMO – system move.

    Soruce ERP60EHP7 / SLES 11SP4 / Oracle 12.x
    Target: SLES 12SP2 / HANA2.0 – Target: App NW7.5x and HANA2.0 is installed as descripted in SUM guide. App (ASCS&PAS are not running, HANA ist up and running).

    I am using Option 1 in “system move”, thats means: copy SUM directory at a specific point (all exports are written to disk) to target system and then in source “NEXT” and SAPup ends there and start SUM on target.

    After starting DMO on target I got the folling error:

    Start log of file SAPup_NEW.log

    #
    # ************************* SAPup started in UPGRADE mode *************************
    # This is SAPup release lmt_006 version 53.000 compile time 21:00:40 Aug 6 2017.
    # Command line: ‘/KWS/ERP/SBE/SUMT/abap/bin/SAPup guiconnect=127.0.0.1:29185’
    # Running in graphics mode server on host kwsvsbe1.
    STARTUP 20170823083749
    Current unit is ‘PRE-EXECUTE’, next unit is ‘PRE-EXECUTE’.
    -> decided to continue with unit PRE-EXECUTE.
    # WARNING: Could not create error file: Cannot read ‘/KWS/ERP/SBE/SUMT/abap/log/HOSTCHANGEMOVE_NEW.LOG’: No such file or directory!
    …begin dialog at 20170823084132

    End log

    this file is not on source nor on target.

    Any hints or solution for that

    Thanks in advane

    BR
    Andreas

    (0) 
    1. Amit Lal

      Hi Andreas,

      DId you copied SUM using <SID>ADM or ROOT? As per guidelines, it should copied with SBEADM only, please verify.

      Besides it clearly says, could not create error file means not able to read/write the SUM directory. Did you extracted target OS SUM after copy completed to replace the binaries?

      Regards,
      Amit Lal

      (0) 
  31. Martino Zocca

    Hello Boris,

     

    We are using DMO with System Move option,We are in the middle of DMO activity(Currently in Preprocessing phase) source  is on AS400 on IBM iseries and target is to migrate to Hana in SLES on IBM power. We are using the DMO with System move option. As per DMO guide the recommended method to transfer the SUM dump from source to target using RSYNC utility. Kindly let us know is RSYNC will work with two different OS (Source AS400 target SLES). If No, kindly let us know the other alternative for the same or do we have any other better option compared to RSYNC.

    Thanks

    Saurabh

     

    (0) 
  32. Saurabh Sharma

    Hello Boris,

    We are using DMO with System move option. Kindly let us know how can we check the consistence of the Dump in source and target system.(Like in conventional Migration we have package checker, Object Checker), in our case Source and Target OS were different so we have not selected the option for Table comparison. Is there any way to check if all buckets were transferred to target ?

    Thanks

    Saurabh

    (0) 
  33. Saurabh Sharma

    Hello,

     

    I have two questions for DMO with System move option.

    1. we have source and target OS of different endian. How can we compare the consistence of dump.
    2. It is recommended by SAP to use the same version of SUM including the PL level for both source and target system as per DMO guide SP20. We have used SUM 1.0 SP 20 PL 6 for source system. Now i can see that for target host the available SUM version is SUM 1.0 SP 20 PL9. I cannot find SUM 1.0 SP 20 PL 6 . Can you please confirm that even Patch level should also match. If yes from where can i get that?

    Thanks

    Saurabh

    (0) 
  34. Christian Schröder

     

    Hi there,

     

    Source-Release: SAP BW 7.4 SPS15

    Source-OS:  Windows2012

    Source-DB:  Oracle 12

     

    Target-Release: SAP BW 7.5 latest SPS

    Target-OS: SLES12

    Target-DB:  HANA 2.0

     

    is that possible with SUM 2.0 SP00?

     

    Best regards
    Christian

    (0) 
    1. Boris Rubarth Post author

      Hi Christian,

      you will have to check the respective SAP note for this. For DMO with SUM 2.0 SP 00, this is SAP note 2428170.

      To be explicit: not possible.
      searching for “DMO with system Move” will bring up the section “c) DMO with System Move: Requirements and Restrictions”. In there, you find “DMO with System Move is currently not supported for SAP source systems running with Windows operating system.”

      Best regards, Boris

      (1) 
  35. ALEXANDRE COUSTENOBLE

    Hello Boris,

     

    In the note 2428170 – Database Migration Option (DMO) of SUM 2.0 SP00 in paragraph c) DMO with System Move: Requirements and Restrictions, we find:

    Operating System (OS) of source primary application server (PAS) host: Any Unix-based operating system. In case of an IBM DB2 for i database, the PAS must always run on a IBM i Host.

     

    But, does the OS of source primary application server follow the restriction indicated in paragraph b1) Operating Systems and Platforms:

    Operating System of Application Server: The operating system of the application server(s) has to be supported for the target SAP release according to PAM.

     

    We have the source système:

    OS: RedHat EL 5

    DB: Ibm db2 9.1

    SAP ECC 6

     

    And we planned to migrate to ECC6 EHP8 on SuSE 12 / HANA DB with the procedure DMO with system move option. Is it possible in one step?

     

    Thanks

     

    Best regards

    Alexandre

     

     

     

    (0) 
    1. Boris Rubarth Post author

      Hi Alexandre,

      sorry for the delay.

      We have now extended the section on “DMO with System Move” in SAP note 2428170 on DMO with SUM 2.0 SP 00.

      It states now
      “Note that DMO requirements on source DB and OS versions apply to “DMO with System Move” as well”

      So that should answer your question: even for “DMO with System Move”, the source OS and DB has to be supported for the target product version, if not stated otherwise in the note.

      Best regards,
      Boris

       

      (0) 
  36. Jean-Luc Bauer

     

    Hello,

    I plan to use DMO to upgrade and migrate :

    Source system :

    ———————

    SCM EHP3 / hana 1 : running on IBM Power SLES11 (big endian)

    to

    Target system

    ——————-

    SCM EHP4 / hana 2 : running on IBM power SLES12 (Little endian)

    In the DMO guide it is written that all source databases and target listed in PAM are supported, but in note 2428170 it is written that source = target = hana is not supported. Does that also apply to my configuration as a migration is necessary to go from hana 1 to hana2 on IBM power ?

    So my question is : can I use DMO to perform my upgrade/migration ?

    Thanks

    Jean-Luc

    (0) 
    1. Boris Rubarth Post author

      Hello Jean-Luc,

      thanks for asking.
      The relevant information is listed in the respective note for DMO (2428170 for SUM 2.0 SP 00): homogenous migrations are not supported with DMO. So no migration from HANA to HANA, and no migration from HANA 1.0 to HANA 2.0.

      You reference the DMO guide: it is stating that you have to check the PAM to see if the OS/DB combination of your souce is supported, and if the OS/DB combination of the target is supported, if not specified in the note. it does not mean that “all source databases and target listed in PAM are supported”.
      Maybe you can send me the paragraph that gave you this impression, then we can check if we have to improve these statements.

      Thanks,
      Boris

      (0) 
  37. Jean-Luc Bauer

     

    Hello,

    thank you for your response.

    Here the situation is special as we are not doing an homogeneous migration as the code page changes from big endian (4102 on power SLES11) to little endian (4103 on Power SLES12) so for my understanding it should be supported. (endianness explained in note 552464)

    Regards

    Jean-Luc

    (0) 
    1. Boris Rubarth Post author

      Hello Jean-Luc,

      it is definitely not supported, as listed in the note.

      “Homogenous” is my word for “keeping the same database type”, independent on endianness.

      Regards, Boris

       

      (0) 
  38. Jean-Luc Bauer

     

    Hello,

    so I do not know how to go to EHP4 on hana 2.

    I can do a normal upgrade on SLES11 from EHP3 to EHP4 with SUM

    And afterwards I could do export/import with SWPM to go to Hana2 on SLES12. But I have exactly the same problem as according to the SWPM guide for Hana, migrating to hana does not support hana as source database.

    regards

    Jean-Luc

    (0) 
    1. Boris Rubarth Post author

      Hello,

      please check SAP note 2380257:

      Migration for SAP HANA on Power
      For migration information for IBM Power Systems (Big-Endian to Little-Endian), see the attached document “SAP_HANA_System_Migration_en.pdf”.

      Regards, Boris

       

      (0) 

Leave a Reply