Skip to Content

This blog offers a chronological list of features for database migration option (DMO)
of Software Update Manager (SUM), starting with SUM 1.0 SP09 up to the latest release.

As a prerequisite, you should read the introductionary document about DMO:
Database Migration Option (DMO) of SUM – Introduction
Check this page once in a while for updates with new SUM SPs.
Always check the restrictions and conditions for a specific feature in the respective SAP Note, e.g.

  • SAP Note 2426315 for DMO with SUM 1.0 SP 21
  • SAP Note 2472850 for DMO with SUM 2.0 SP 01

SUM 2.0 was introduced with SL Toolset 1.0 SPS 21 in September 2017,
see https://blogs.sap.com/2017/08/10/sum-in-the-family-way/

  • SUM 2.0 SP 01: released on Jan 15 2018, maintenance planned until SP 02 is available
  • SUM 1.0 SP 21: released on Sep 11 2017, maintenance planned until SP 22 is available
  • SUM 1.0 SP 20 & SUM 2.0 SP 00 are in phase patch-on-request, planned until SL Toolset 1.0 SPS 23 is available, see PDF “Maintenance Strategy” attached to SAP Note 2530522 on SL Toolset 1.0 SPS 22
SUM 2.0
SP 01
Details More Information
new folder doc New folder doc for static UI content, parallel to htdoc SUM guide
SUM 2.0
SP 00
Details More information
Prereq. check New scenario: prerequisite check for System Conversion SUM conversion guide
R3load R3load now provided as part of SUM 2.0  SAP Note 2472835
SP 21 Details More information
(no news)
SP 20 Details More information
DMO with System Move Change the host of PAS instance during DMO DMO guide
& this blog
SP 19 Details More information
DMO without software change DMO to SAP HANA possible without system update,
so no stack.xml is required
DMO guide
& this blog
DMO for SAP Solution Manager DMO to be used for upgrade & migrate SAP Solution Manager 7.1 to 7.2 on SAP HANA database
(procedure is now generally available)
SAP Solution Manager 7.2: Simplified Upgrade and Migration to SAP HANA
HANA partitioning via file Partitioning information can be provided via file DMO guide
section 4.3.8
HANA schema: SAPABAP# HANA schema will be SAPABAP# (instead of SAP<SID>), i.e. like SWPM names the schema.
SP 18 Details More information
target db type Target database type SAP ASE is available (without registration); target database type DB6 is available on request
Migration monitoring Realtime Migration Graph allows to adapt the number of R3loads for migration directly
SL UI Buttons for Reset and for Cleanup are now only available via menu “More”
SP 17 Details More information
DMO for SAP
Solution Manager
DMO to be used for upgrade & migrate SAP Solution Manager 7.1 to 7.2 on HANA (available on request) SAP Solution Manager 7.2: Simplified Upgrade and Migration to SAP HANA
Sub progress bar Shown for some phases (like migration phases)
Migration Preparation Illustrates table split result, available in menu Utilities
Notification icon On main UI on “failed buckets”, with link to bucket process monitor
SP 16 Details More information
Process Monitor Restart of broken packages is possible without the need to wait until migration phase is done
Observer mode Allows to monitor the process with non-<SID>adm user (“just look, don’t touch” possible)
SP 15 Details More information
7.50 support SUM SP 15 is exclusively for scenarios targeting SAP NetWeaver 7.50 based systems, and is available parallel to SUM SP 14. SAP Note 2161396 is relevant for DMO with SUM SP 15.
SP 14 Details More information
MS SQL as target The list of target database types is extended to MS SQL. Like with SAP ASE as target database, this is only available on request. (For a request, create an incident on BC-UPG-TLS-TLA). Respective SAP Note for DMO
MDC support Support for Multi Database Containers (MDC) on SAP HANA DB DMO guide section 4.5.5
non-UC SCM Support for non-Unicode SAP SCM systems Respective SAP Note for DMO
Monitoring Improved monitoring for R3load usage DMO guide section 4.2
Test cycle Test cycle option for quick migration repeat DMO guide section 4.5.2
DMO notes The SAP Notes on DMO are now SP-specific: SAP Note 2161397 is specific for DMO with SUM SP 14 (SAP Note 1813548 was for DMO with SUM up to SP 13).
SP 13 Details More information
Benchmarking Benchmarking tool for testing migration performance DMO: introducing the benchmarking tool
R/3 as start Start release SAP R/3 4.6C is now supported. Respective SAP Note for DMO
ROWID export ROWID-based export for Oracle source database.
Win: pipe mode Pipe mode for R3load is now also used for SUM on Windows OS DMO: comparing pipe and file mode for R3load.
SUM on AAS It is possible to run SUM (and DMO of SUM) on an Additional Application Server (AAS, fka DI).
Restrictions are described in the SAP Note for DMO, e.g. it is only supported if your system has a separate ASCS instance.
Respective SAP Note for DMO
New SL UI

The “DMO UI” is replaced by the “Software Logistics User Interface” (SL UI).

Note that the URL suffix has changed from /doc/gui to /doc/sluigui.

DMO guide section 6.1
Duration files Table duration files can now simply be put into the download folder to be considered for the next DMO run. DMO guide section 2.3
SP 12 Details More information
SAP ASE as target SAP ASE is a possible target database type for DMO, apart from SAP HANA – this is available on request. Check the SAP Note on DMO for details and restrictions, e.g. it is only supported if you have a separate ASCS instance. Respective SAP Note for DMO
SP 11 Details More information
Table comparison With table comparison, it is possible to optionally compare not only the number of rows for the migrated tables, but also the content of tables during a DMO run. It should not be used for the DMO run on a productive system as it increases the downtime. DMO guide section 4.5.1
SP 10 Details More information
Unicode Conversion It is now possible to include the Unicode Conversion (for single code page systems only) as part of the DMO procedure. The manual activities required before the actual technical conversion remain the same. SAP Note 2108396
Reset button The reset button is now shown on all dialogs. Previously, it was only available on a roadmap switch dialog, like from Preprocessing to Execution.
SP 09 Details More information
DMO available Database Migration Option (DMO) is available as a new scenario for Software Update Manager (SUM). It offers the combined update/upgrade of the SAP software with the database migration to SAP HANA DB. DMO is available for SAP Business Suite systems, SAP NetWeaver systems, and for SAP BW systems. Database Migration Option (DMO) of SUM – Introduction
To report this post you need to login first.

9 Comments

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

  1. Avinash Venkateshaiah

    Hi Boris,

    Thanks for sharing.

    Can you please help me understanding when start release 4.6 C is supported from SP14 means can we upgrade and migrated with Single step to ECC 6 EHP8 with target database MSSQL with SUM DMO SP17 ,Also seems SAP Note 2161397 is not released to customers,Please any updates when the note will be released

    Thanks,

    Avinash

    (0) 
    1. Boris Rubarth Post author

      Hi Avinash,

      thanks for asking.

      1) Any path that targets a product version based on SAP_BASIS 7.50 has to be on Unicode already (see Why EHP 8 is different). Even though the Unicode conversion can in general be covered by DMO, this is not possible for targeting EHP 8.

      2) SAP Note 2161397 is no longer visible as it is outdated, I will adapt the text. Actual SAP note for DMO with SUM SP 17 is SAP note 2257362.

      Regards, Boris

      (0) 
      1. Avinash Venkateshaiah

        Thanks Boris for the reply.

        So when my system start release 4.6C using SUM SP17 with single step can we go for target database HANA and Product  EHP 6 SAP ERP 6 with combine unicode conversion,upgrade and Migration as in blog it updates SUM SP13 -R/3 as startStart release SAP R/3 4.6C is now supportedCapture.JPG

        Thanks,

        Avinash

        (0) 
        1. Boris Rubarth Post author

          Hi Avinash,

          in general start release 4.6C is supported, and DMO can cover the unicode conversion. Still you have to check all requirements and restrictions listed in the relevant SAP Note (e.g. 2257362 for DMO with SUM SP 17) to know whether your scenario works. As an example, the Unicode conversion of DMO requires a single code page source system.

          Regards, Boris

          (0) 
  2. Pedersen Torben R

    Really nice Boris, I hope you will keep on updating this blog.

    One suggestion, it would be nice to have the release date mentioned as well for the individual SPs as many of the notes related to the SPs are not released for customers anymore (looking at the older versions).

    (0) 
    1. Boris Rubarth Post author

       

      Thank you for the proposal – I have now listed the status for the actual SUM SPs on top of the table, to show which SUM version is currently supported. Hope that this fits to your proposal.

      (0) 
  3. Ranjith RKC

    Hi Boris

    We are facing performance issues in the DMO. EU_CLONE_MIG_DT_RUN phase is running for more than 5 days now (with Downtime minimized strategy). It is a combined migration of NUC to UC, Oracle to HANA & EHP6 to EHP7. System details are given below.

    Source system : ERP 6.06, NW 7.31, Non-Unicode, Oracle 12c (OLTP compressed), DB Size 4.5TB, HP rx6600, 4CPU (8 core, 1.6GHz), 64GB RAM, HPUX 11.31 & 2Gb Ethernet.

    SUM Host : SUM is run in AAS, HP rx2600, 2CPU (4 core, 1.6GHz)), 32GB RAM, HPUX 11.31 & 2Gb Ethernet

    Target system : ERP 6.07, NW 7.4, Unicdoe, HANA 2.0, HP BL460c G9, 2 CPU (28 core), 512GB RAM, SLES 12 SP2, 20Gb Ethernet

    SUM version : 1.0 SP 21 (PL5)

    R3load : 749 Patch 301

    No. of R3load processes : 16 (80 to 90% CPU load in SUM host)

    There is no resource bottleneck in CPU, Memory, Disk & Network in Source DB server, SUM host & Target HANA DB.

    Cluster tables like RFBLG, CDCLS etc. are transferred at very slow rate.

    In the export log, the PIPE time is very high compared to DB time as below (one example). DB time : 25668 sec & Pipe time : 41360 sec.

    We are unable to figure out where exactly the issue is as there is no bottleneck in Hardware resource.

    Can you pl help us to isolate the issue?

    Thanks

    Suresh

    (0) 
    1. Boris Rubarth Post author

      Hi Suresh,

      sorry to read that you are experiencing issues.

      Unfortunately I do not have the capacity to analyze such issues, so hopefully you have meanwhile created an incident.

      Thanks, Boris

       

      (0) 

Leave a Reply