Database Migration Option (DMO) of SUM – Introduction

Scenario:
  • You want to migrate your existing SAP ABAP system to the SAP HANA database
  • Your SAP release needs to be upgraded prior to migration
Use the database migration option (DMO) of the Software Update Manager (SUM):
it combines SAP upgrade and database migration to SAP HANA in one tool!

Benefits:
  • Migration steps are simplified
  • System update, Unicode Conversion, and database migration are combined in one tool
  • Business downtime is reduced
  • The source database remains consistent, so a fast fallback is possible

Motivation
If you want to migrate an existing SAP system (running on anyDB) to a SAP HANA database, required steps may be a dual-stack split, a unicode conversion, a database upgrade of anyDB, an upgrade of your SAP software, and a database migration to SAP HANA. The Software Update Manager (SUM) includes an option that combines the upgrade with the database migration “database migration option” (DMO) for SUM. It is sometimes referred to as the one-step migration procedure, compared to the classical migration (i.e. heterogenous system copy,  using Software Provisioning Manager).
The DMO is an inplace-migration (instead of a new installation): it upgrades and migrates the existing system while keeping the system-ID, host name, and connectivity settings stable.
DMO_intro.jpg
DMO for SAP NetWeaver BW and for SAP Business Suite systems
DMO is available with Software Update Manager 1.0 SP09 and higher, and can be used for systems based on AS ABAP. It can be used for SAP BW systems from 7.0 SP17 (and higher) to migrate to 7.31 (and higher). And it can be used for systems like SAP R/3 4.6C or systems part of the SAP Business Suite 7.0 (and higher) to migrate to a level corresponding to SAP BASIS 7.40 (for example “SAP enhancement package 7 for SAP ERP 6.0”).

DMO processing overview
The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the traditional database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). Then the shadow repository is copied to SAP HANA,  the database connection of the SAP system is switched to SAP HANA database, and then the downtime starts. After migration of the application data (including data conversion), the upgrade is finalized and the SAP system runs on SAP HANA. The traditional database continues to run and the application data in it are not modified, so it remains a fallback throughout the complete process.
Please note that for a SAP Business Suite system based on SAP NetWeaver 7.40 (i.e. systems part of SAP Business Suite 7 Innovations 2013), your SAP NetWeaver Hubs must be on 7.30 or higher. For details, see http://wiki.scn.sap.com/wiki/display/SLGB/Strategy+beyond+SAP+Business+Suite+7+Innovations+2011


Further information


SAP Note 2377305 on Database Migration Option for SUM 1.0 SP 20

DMO Guide

Blogs on DMO

Blogs on related topics
SAP Education offering
  • HA250: “Migration to SAP HANA using DMO” – two days classroom training

1 comment:

Alfred Avina said...

Though it is challenging to transform the data from one computer to another, that is, data migration , but with the help of this program, I had not felt any need to change the source code for uploading the several database tables.