This blog introduces a new scenario available with SUM 1.0 SP 19: DMO without System Update.

You should be familiar with the general DMO procedure, as described in the blog https://blogs.sap.com/2013/11/29/database-migration-option-dmo-of-sum-introduction/

New scenario: DMO without System Update

We all know that Database Migration Option (DMO) of Software Update Manager (SUM) is the combination of the SAP software update with the migration to SAP HANA (or other databases like SAP ASE). The typical scenario is: your source system is not running on SAP HANA database, you want to migrate it to SAP HANA, and this requires an update of your SAP software (so that it fulfills the SAP HANA requirements).

Now the new scenario seems like a mystery:
combined update & migration – but without update?

We have taken your feedback: in case the software level of your source system is sufficient for SAP HANA db, you do not want to adapt the SAP software, not even one SP for any software component (e.g. to avoid regression tests). Independent on whether this is the best option (as you may use the downtime to apply required updates), this scenario is now supported.

So “DMO without System Update” does not require a stack.xml to start with.

Smallprint: the boundaries

Yes, the procedure is described in the DMO guide, section 2.3, listing restrictions like

  • target database type has to be SAP HANA (not available for DMO targeting e.g. SAP ASE)
  • download folder required with new kernel files for source and target database type
  • SUM will nevertheless create the shadow system and shadow repository (both in uptime)
  • it cannot be combined with “customer transport integration CTI”
  • it cannot be combined with downtime optimizations like “downtime optimized DMO”
    (as described in the follow blog https://blogs.sap.com/?p=113050)

“Heterogenous system copy” vs. “DMO without System Update”

You are familiar with the heterogenous system copy of Software Provisioning Manager? This scenario is still valid, and it has it’s advantages, depending on your priorities:

  • “DMO without software change” is still an inplace procedure:
    it keeps the application server (on which the SUM is started)
    -> heterogenous system copy can be used to switch to a new host
  • “DMO without software change” still creates the shadow system,
    so the uptime processing is not shortened compared to plain DMO

But if no stack.xml is required, how to overcome the very first SUM dialog: “feed me with a stack.xml”? Another reason to study the DMO guide thoroughly 🙂

Boris Rubarth, SAP SE
Product Manager SUM

To report this post you need to login first.

9 Comments

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

    1. Boris Rubarth Post author

       

      Yes, the workbench has to be locked, like in standard DMO.

      Yes, this may be cumbersome, but keeping the general procedure including the shadow system was the fast (and only) way to enable that scenario.

      (1) 
    1. Boris Rubarth Post author

      Hi Johnny,

      the conditions concerning Unicode are like for standard DMO: the Unicode conversion can be included, but only if the target release is lower than SAP_BASIS 7.50.

      Best, Boris

      (1) 
  1. Wei-Shang Ku

    Hi boris,

    Does SUM+DMO keep the original PAS after migration ?

    If so, is there any way to have new PAS on another host ?

    There are many SAP customers running very old, Unix based system. They want to migration everything to Linux (U2VL or U2L), It is not a good solution to migrate everything to Linux and let Central Instance on Unix.

    In addition, is that possible to run SUM on separate box (not on CI) ? Some customer with very

    old HP-UX/AIX don’t have enough resource to hold shadow process and db.

    (0) 
    1. Boris Rubarth Post author

      Hi Wei-Shang Ku,
      as stated in the respective SAP note for DMO (currently 2328517 for DMO with SUM 1.0 SP 19), DMO of SUM will keep the host stable: “DMO will keep the application server stable. This means that no switch of application server is possible.”
      You can switch the PAS of your system prior or after the DMO procedure, using the option of the Software Provisioning Manager.
      Running SUM for DMO on an Additional Application Server (AAS) instead of PAS is supported with restrictions, as stated in the SAP note as well, e.g. only if your system has a separate ASCS instance, and not supported for DB4 (DB2 for i).
      Regards, Boris

      (0) 
  2. Ambarish Satarkar

    Hi Boris,

    Thank you. This blog helps. Difference between DMO for pure migration against Classical migration using SoftWare Provisioning Manager looks to be  –

    Migration of data will happen over the network through network pipes so customers need to have good network bandwidth e.g. 10 Gbps. SWPM tool migrates data at file system level which is slow when compared to earlier option of data migration over the network.

    DMO’s inbuilt intelligence and table split mechanism will be far better than manual table splitting decisions. So we may expect good migration speeds compared to classical migration.

    Thanks,

    Ambarish

    (0) 

Leave a Reply