Skip to Content

When time comes to migrate from a AnyDB installation to HANA the easiest way is to use SUM with DMO option but it may be, however, that the classic migration with SWPM is the only way to do it. The information about when to use DMO is scattered across multiple sources and I just intend to summarize for better reference and to help on taking the right decision about which tool to use when the migration comes up.  This applies to DMO SP16 but also to former SP levels.

Characteristics:

  • Inplace-migration; To use when SID and application server (PAS/AAS) host name don’t need to change; No switch of application server is possible;
  • No need to update to latest EHP to be able to do the migration to HANA DB, the tool do it in just one step for a wide range of source releases;
  • The DMO procedure can be used for a central installation in which the database runs on the same host as the SAP application server;
  • Source system should be a single ABAP stack;
  • No dual-stack split option in DMO;
  • Unicode conversion; Restrictions when target system is based on SAP NetWeaver 7.50 (such as SAP ERP 6.0 EHP 8)

 

Restrictions:

  • DMO doesn’t split dual stacks;
  • nZDM option is not available (Near Zero Downtime Maintenance);
  • MDMP-systems are not supported for the unicode conversion;
  • Running DMO on AAS not supported if no ASCS instance exists.

 

Some relevant notes:

  • No certification required for consultants using DMO of SUM;
  • No migration check service required for DMO on productive systems.

 

Required software to download in advance:

  • Latest version of SUM – Software Update Manager;
  • SAP Host agent latest patch;
  • SAP HANA Client installation files;
  • Also needed: Migration key, SAP license file for target
To report this post you need to login first.

4 Comments

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

  1. Pieter Oosthuizen

    Hello!

    Can I use DMO for migration only, and not to include the (Ehp) upgrade part?  (As we are already on the latest on the source system.  Perhaps only include e.g. an SPS?)

    Thanks, Pieter.

    (0) 
    1. Antonio Almeida Nunes Post author

      As of SUM SPS19 we have a migration only feature available:

      You want to carry out only a migration of your SAP system to the SAP HANA database, but you do not intend to update the SAP system, and hence you do not need to provide a stack.xml file. For more information about this feature, see the topic “Using DMO without System Update” in the “2 Planning” section of the DMO Guide

      To enable a SUM with DMO run for the migration only scenario, add to file SAPup_add.par the following line, before you start the Software Update Manager: migration_only = 1

      (The file SAPup_add.par is located in the subdirectory abap\bin of the SUM directory. If this file does not exist yet, create it manually.)

       

      (0) 
  2. Rahul Sanghavi

    Hi Antonio,

    Is DMO option is only available for target database HANA ?

    OR we can use DMO option for migration of Oracle 12 form Windows to Oracle 12 on RH Linux.

    (0) 
    1. Antonio Almeida Nunes Post author

      Hi,

      DMO is available for the following target databases:

      • SAP HANA
      • SAP ASE
      • MS SQL Server (available on request)
      • IBM DB2 for Linux, UNIX, and Windows (DB6)  (available on request)
      • SAP MaxDB (available on request)

       

      You do not get the option you are searching for. For your case you should use SWPM.

      Hope this clarifies

      Best regards
      Antonio

      (0) 

Leave a Reply