DMO to SAP HANA – without software change
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