23

SAP DMO use for update and migrate to anyDB

 2 years ago
source link: https://blogs.sap.com/2021/06/23/sap-dmo-use-for-update-and-migrate-to-anydb/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Technical Articles
Posted on June 23, 2021 5 minute read

SAP DMO use for update and migrate to anyDB

0 Likes 1,045 View 0 Comments

Introduction:

SAP introduced a one-step procedure that combines the system update and the database migration. This is provided with the Database Migration Option (DMO) feature, which is delivered with the Software Update Manager (SUM) tool, a part of the Software Logistics Toolset (SLToolset).

SAP system on anyDB, update the SAP system and migrate the anyDB with help of DMO.

  • Dual stack split
  • Database update of anyDB
  • Update of your SAP software
  • Database migration to target database

Supported DB:- SAP MaxDB, Microsoft SQL, IBM Db2 for z/OS (DB2), IBM Db2 for i (DB4), IBM Db2 for Linux, Unix, and Windows (DB6), SAP HANA SAP ASE, Oracle.

From SUM 1.0 SP26 update and migrate to anyDB supported.

DISCLAIMER

The content of this blog post is provided “AS IS”. This information could contain technical inaccuracies, typographical errors, and out-of-date information. This document may be updated or changed without notice at any time. Use of the information is therefore at your own risk. In no event shall SAP be liable for special, indirect, incidental, or consequential damages resulting from or related to the use of this document.

DMO Benefits:

  • Simplified migration steps
  • System update and database migration combined in one tool
  • Reduced business downtime
  • A comfortable and fast reset option

Describes specifics, when you want to update your existing SAP systems based on SAP NetWeaver Application Server for ABAP with subsequent migration of your database to the database platform supported DB for Linux, UNIX, and Windows

A further benefit of DMO is its comfortable and fast reset functionality provided that the source database remains consistent throughout the procedure.

SAP system on anyDB, and you want to update the SAP system and to migrate the anyDB may be necessary, Source and target DB can’t be same.

The processing sequence is based on the shadow system functionality of SUM:

The SUM creates the shadow repository on the traditional database until the downtime phase, while in parallel the target database is being set up (such as client, schema).

The shadow repository is copied to the target database. Then the downtime starts.

After the migration of the application data (including data conversion), the update is finalized and the SAP system runs on the target database.

The source database continues to run, remains consistent, and application tables are not modified. It remains as a fallback database for the Reset Option throughout the complete DMO procedure. After the successful DMO procedure, however, it cannot be used anymore as a production database for an SAP system in parallel with the target database.

DMO Working principle for AnyDB

Untitled-8.png

  • DMO supports migration to SAP HANA DB, as well as SAP ASE, MaxDB, MS SQL Server, and IBM DB2.
    • A homogenous migration is not supported, for example, HANA to HANA
    • You may need to apply at least one SP, for example, ST-PI
  • Using DMO for migration across the data center is not supported. There are no technical restrictions, but it comes with a high performance and latency impact. You may use it at your own risk. No support is provided in case of performance issues or broken procedures due to network/latency issues

Source database supports which target database:-

Target DB: SAP HANA SAP ASE MS SQL DB6 SAP MaxDB Supported Source DB:

Oracle X X X X X SAP MaxDB X X X X

Microsoft SQL X X

X X IBM Db2 for z/OS (DB2) X X

IBM Db2 for i (DB4) X

IBM Db2 for Linux, Unix, and Windows (DB6) X X X

X SAP HANA

SAP ASE X

X X X

Requirements for Source System and Source Database:

  • Source Database: All source databases excluding SAP HANA database
  • Operating System (OS) of source primary application server (PAS) host: Any Unix-based or Windows operating system. In the case of an IBM Db2 for I database, the PAS must always run on an IBM I Host.
  • The operating system of the application server on the source host has to be supported for the source SAP release according to PAM. The operating system of the application server on the target host has to be supported for the target SAP release according to PAM.
  • During a “DMO with System Move” run, dump files are created in the SUM folder that contains the contents of source database tables in compressed form. Since the entire source database is exported, make sure that there is enough space available.
  • SUM requires a database-independent kernel archive for the target release which can be executed on the source Operating System. You must put this archive into the download directory.
  • As of SUM 2.0, a particular phase checks for left-over data in physical table pools. This means that SAP Note 2930154 no longer needs to be applied before the start of the procedure.

Requirements for Target System and Target Database:

  • OS of PAS host: Any Unix-based or Windows operating system
  • Install Target DB and client as per requirement.

Restrictions With regard to operating systems:

  • If the OS of the source and the target PAS hosts are different, you have the following options:

On condition that

  • The phase HOSTCHANGE_MOVE_SOT is finished on the source system, you have copied the SUM directory from the source to the target application server (either manually, or using the script provided by the tool)
  • Extract the SUM archive for the target OS over the target SUM directory to replace the executables.
  • Make sure that you use the same SUM version (including patch level) in the source and the target system. You have to consider this already when downloading the SUM archives!
  • As a workaround, install in the source system an additional application server (AAS) that runs on the same OS as the target PAS host. In this way, source OS and target OS are identical.

Resetting the procedure on the target system:

This allows you to repeat the DMO procedure, but it does not restore the initial state of the target system. For this, remove the SUM directory from the target system and transfer the SUM directory data from the source system again.

Resetting the procedure on the source system:

This works directly by using the reset option as described in the DMO guide.

  • Support package (SP) version of SUM:
  • You need the identical SP and patch level version of SUM in both the source and target system. Pay particular attention to this when you download the SUM archive.
  • Do not use the AzCopy tool for file transfers when using the parallel mode:
  • The AzCopy tool creates the target file immediately with the target file size. SUM always uses the file size to check whether the copy process for a file has been completed or not. Therefore, SUM cannot recognize whether the file transfer has also been completed. Instead, we recommend using other file transfer techniques such as ftp, rsync, or the SUM tool internal script based on rsync.

Reference Documents: – 

2743769      Database migration option (DMO) of SUM 2.0 SP05

2976921   Database Migration Option (DMO) of SUM 2.0 SP10

2690522      Central Note – Software Update Manager 2.0 SP05

3024408   Database Migration Option (DMO) of SUM 2.0 SP11

dmo_of_sum2_to_db6, dmo_of_sum2_to_Maxdb, dmo_of_sum2_to_ASE guide

SUM 2.0 With DMO:-

Untitled-9.png

Untitled-10.png

I hope this document will help you to understand the use of DMO for update and migrate to other DB.

Cheers!

Anikesh Jyotishi


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK