When to use DMO option for SUM

[antonio_nunes1]

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 😎

 

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