Professional Documents
Culture Documents
HA250 - Database Migration Using DMO - SAP HANA 2.0 SPS05
HA250 - Database Migration Using DMO - SAP HANA 2.0 SPS05
HA250 - Database Migration Using DMO - SAP HANA 2.0 SPS05
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 17
Course Duration: 2 Day(s)
e-book Duration: 5 Hours 55 Minutes
Material Number: 50155260
SAP Copyrights, Trademarks and Disclaimers
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/
corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software
vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which
speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
Demonstration
Procedure
Warning or Caution
Hint
Facilitated Discussion
vi Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
Technology Consultant
Systems Architect
Lesson 1
Listing DMO Benefits 2
Lesson 2
Explaining DMO Basics 5
UNIT OBJECTIVES
LESSON OVERVIEW
This lesson discusses the benefits of the database migration option (DMO) compared to a
classical migration.
Business Example
As a member of the implementation team for a system migration, you need to know more
about DMO.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
DMO Benefits
The following list provides an overview of the database migration option (DMO):
DMO Overview
Scenario
You want to migrate your existing AS ABAP-based SAP system to SAP HANA DB, SAP
ASE, MS SQL Server, IBM DB2, or SAP MaxDB. You choose the in-place migration
avoiding landscape changes (SID, host name). A classical migration is complex and
requires several steps to be considered.
Solution
Use the database migration option (DMO) of the Software Update Manager (SUM).
Benefits
SAP system update, Unicode conversion (in some cases), and database migration are
combined in one tool.
Classical migration is the sequence of an SAP software update (using SUM) and
heterogeneous system copy (using Software Provisioning Manager (SWPM)).
DMO simplifies the migration and is often referred to as the one-step procedure to, for
example, SAP HANA.
Running an SAP system with an SAP HANA database requires a specific SAP software level.
This means that in some cases, the SAP system has to be updated before the migration takes
place.
Note:
An update can be the applying of SAP Support Packages, or a release change
(SAP enhancement package installation, or upgrade).
If the SAP system is updated, this may result in requirements for the database host software,
especially the database software release. So, for some scenarios, the source database
software has to be updated before the SAP system is updated.
As with the SAP HANA database, non-Unicode SAP systems are no longer supported.
Therefore, the migration procedure may also have to cover the Unicode conversion.
Now with the DMO of the SUM, the procedure is simplified. SAP system update and database
migration are combined in one tool and in one procedure. If required, the Unicode conversion
can also be included. For some source database types, you do not have to update the source
database software for the migration.
Note:
DMO of SUM can only handle the Unicode conversion if the target release is AS
ABAP 7.40 and below.
The figures, Steps for Classical Migration and DMO Simplifies Migration , illustrate a process in
which the SAP application server is separate from the database host, which is referred to as a
distributed installation. The DMO procedure works independently of the installation type. It
can be used for a central installation, in which the database runs on the same host as the SAP
application server.
The benefits of DMO are as follows:
DMO Benefits
In-place migration keeps the application server and SAP system ID stable:
Low impact on SAP system landscape because only the database server is new
Reduced risk
No restore required
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson provides a more technical introduction to DMO.
Business Example
As an administrator, you want to learn more about the technical basics of DMO.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Select the corresponding scenario, for example, Database Migration Option (DMO) .
Depending on the type of your SAP system (AS ABAP-based or AS Java-based) and the target
release of the DMO procedure, you have to choose the correct SUM version.
For the heterogeneous SAP system copy, a certification is required. For DMO, this is different.
The differences are as follows:
A migration key has to be entered during DMO run: R3load requires the key.
Certification training TADM70 (SAP System: Operating System and Database Migration) is
useful.
DMO is an option inside of SUM. Consider the supported start releases for DMO, listed in the
attachment of the major SUM note.
The required start release levels are described in the respective SAP Note on DMO.
Check the SAP Note for DMO for information on which database types require an update for
DMO and which do not.
DMO supports migration to SAP HANA and SAP ASE. MS SQL Server, IBM DB2, and SAP
MaxDB are supported on request.
A homogeneous migration is not supported, for example, SAP HANA SAP HANA.
DMO only works for AS ABAP-based SAP systems. There is no dual-stack split option as
part of the DMO procedure. DMO does work on SAP Solution Manager 7.1 – but only on the
AS ABAP part.
By default, DMO keeps the application server and SID, the In-place Migration .
A switch of the application server, the DMO with System Move , is possible in some
scenarios.
For a target SAP system based on SAP NetWeaver 7.50 and above (such as SAP ECC 6.0
EHP 8), the source SAP system has to be on Unicode already (see SAP Note 2033243).
For this scenario, DMO is not able to cover the Unicode conversion.
The dual-stack split is relevant for SAP systems combined in a dual-stack, like SAP ECC with
SAP Enterprise Portal.
The figure, Introduction of DMO phases , illustrates a brief overview of the DMO phases that
are executed by the SUM tool.
Step 1 includes some preparations that are done, like providing stack.xml, passwords, and the
download folder. On the target database, the DMO procedure only creates required users and
schema.
Step 2 includes the creation of the shadow repository on the target database. This is still
uptime processing, so the SAP system is available for end users.
Step 3 is the switch to the downtime. The SAP system is no longer available. The source
database is still running, but is no longer used to store new or changed data.
Step 4 is the migration of application data.
Step 5 finalizes the update and migration, like switching the SAP system to the new kernel.
Step 6 starts the SAP system, which is now running on the new database and on the new SAP
software release.
During the complete procedure, the source database continues to run. The DMO procedure
offers an easy reset, in case this may be required. As the source database was not changed,
the reset is fast and does not require manual interactions. The DMO reset deletes the shadow
repository from the source database, and all other artifacts are also reset.
Running SUM on AAS host is possible (restrictions apply, see SAP note on DMO)
Benefit: run SUM on host with best resources
DMO not supported for data center migration due to latency issues
DMO with System Move : use case to move complete SAP system
Allows to switch PAS host
Allows to migrate across data centers
Allows to migrate to cloud (IAAS)
Requirements:
Target database and target PAS are set up prior to start
Target database type is SAP HANA or SAP ASE
Sequence:
Start SUM in source, export happens
Copy and start SUM on target, import happens
Can be combined with DMO without Software Update and with SUM on AAS
LESSON SUMMARY
You should now be able to:
Learning Assessment
1. Which steps can be combined in a DMO procedure, targeting an AS ABAP 7.50-based SAP
system?
Choose the correct answers.
1. Which steps can be combined in a DMO procedure, targeting an AS ABAP 7.50-based SAP
system?
Choose the correct answers.
You are correct! During a DMO procedure, an SAP software update and a migration to a
target database can be performed. Performing a Unicode conversion is not possible
targeting an AS ABAP 7.50-based SAP system. An upgrade of the source database is not
part of the DMO procedure.
You are correct! DMO does combine several steps, offers an easy reset, and it is an inplace
procedure by default. The requirements concerning the target release on SAP HANA
database are not changed by DMO.
Lesson 1
Preparing the File System for DMO 12
Lesson 2
Configuring SAP Host Agent for DMO 17
Lesson 3
Examining the SUM UI 23
UNIT OBJECTIVES
LESSON OVERVIEW
This lesson explains the required steps on the host to prepare a DMO procedure.
Business Example
You have the task of preparing a DMO procedure and need to know the required steps.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
DMO Prerequisites
The required considerations for DMO are as follows:
In case of a dual-stack SAP system, the dual stack has to be split beforehand, because
DMO works on AS ABAP-based SAP systems only.
In case of an SAP software update, the stack.xml file and software files have to be
downloaded.
DMO Specifics
For a DMO procedure, you have to select both the kernel files for the source database and the
target database because the DMO procedure requires and uses both.
SAP Note 1912445: ABAP custom code migration for SAP HANA
Dual-stack split
Only pure AS ABAP-based SAP systems can be migrated by DMO. If the SAP system is a
dual-stack system, the dual stack has to be split beforehand.
Note:
The dual-stack split procedure is part of the Software Provisioning Manager
(SWPM). There are no plans to include the dual-stack split procedure in the
DMO procedure.
Unicode conversion
With SUM 1.0 SP 10, the DMO procedure allows for the inclusion of the Unicode
Conversion (for single code page systems), if the SAP target release is AS ABAP 7.40 and
below.
OS/DB software update
Depending on the update path, the operating system and the database software may
have to be updated prior to the DMO procedure. For specific source databases, the DMO
procedure has lower requirements than the classical migration. The DMO documentation
lists the actual requirements.
stack.xml and software files
These files are provided by Maintenance Planner, when performing a maintenance
transaction.
Web browser
The user interface (UI) of the SUM procedure is based on SAPUI5 and requires a specific
web browser version. The SUM guide lists the actual requirements. The supported web
browser versions for SUM UI are as follows:
The required software download from SAP Support Portal for DMO is as follows:
The latest SPAM/SAINT update for SAP source release has to be downloaded (if not
applied already).
The latest patch for SAP Host Agent 7.21 has to be downloaded (if not installed already).
Caution:
In case of SAP HANA: The SAP HANA client has to match the SP level of the
SAP HANA DB. See SAP Note 2339267 on HANA client version manifest vs.
HANA server version.
Although the Maintenance Planner can add the SAP Host Agent into the download
basket, we recommend that you always check for the latest update of the SAP Host
Agent in SAP Support Portal.
Task: Execute a self-update.
SAP HANA Client installation files
The SUM establishes a connection to the SAP HANA database and requires the SAP
HANA client software for this. The installation files have to be provided and the SUM asks
for the location of these files during the DMO procedure.
Task: Extract the SAP HANA client software installation archive.
Migration key
For a heterogeneous database migration, a migration key is required. The kernel tool
R3load is used for the migration and requires this migration key. The DMO procedure
asks for the key and provides it to the R3load tool. Use the link https://support.sap.com/
migrationkey to request the migration key for your SAP system.
Task: Provide the migration key when the SUM procedure asks for it.
SAP license file
The SUM can install a new license on the target SAP system. The SUM asks for the
license file. Use the quick link https://support.sap.com//licensekey to request the
license file for your SAP system.
Task: Provide the license file location when the DMO procedure asks for it.
The figure, Prepared Files for Exercise, shows the folders /usr/sap/D00/MP_Download
and /usr/sap/D00/HA250_17 that have been prepared on the ABAP host in the training
landscape.
5. Extract the SAP HANA client software installation archive in the folder /usr/sap/D00 .
6. Keep the migration key ready (SUM will ask for it).
The figure, Planned Structure of Files and Folders for DMO, illustrates the target state of the
exercise.
Figure 7: Planned Structure of Files and Folders for DMO in this Course
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson explains the necessary preparation steps to configure the SAP Host Agent for a
DMO run.
Business Example
You are responsible for preparing a DMO run, so you have to prepare the communication
between the SAP Host Agent and the SUM.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Collaboration Between SAP Host Agent and Software Update Manager (SUM)
The SUM is the tool for SAP system maintenance of SAP systems, based on AS ABAP. SUM
can also handle AS Java based SAP systems – but it works completely different there, for
example, no SAPup process, and so on.
The same tool SUM can be used for an SAP system maintenance or for a DMO procedure. The
DMO procedure was the first SUM use case to use the new UI, which is based on SAPUI5.
Note:
SAPUI5 is based on jQuery, a JavaScript library.
Use a web browser to start the SUM for a DMO procedure by sending an appropriate HTTP
request to the SAP Host Agent. The URL that you use contains the information for the SAP
Host Agent about what to do.
Note:
LMSL is the abbreviation for Lifecycle Management Software Logistics.
<host> is the host name of the primary application server host of the source SAP system.
<port> is the port of the SAP Host Agent (1129 for HTTPS, or 1128 for plain HTTP).
<SID> has to be replaced with the SAP system ID of the source SAP system.
Before the SAP Host Agent starts the SUM, it requests the user and password of the user
<sid>adm. This is required to start the SUM.
Note that if you enter a wrong password or a wrong URL, you get an error message which
depends on the browser type. Some browser output states: File cannot be found.
With the user and password of the <sid>adm user, the SAP Host Agent starts the SAPup. The
SAPup is the part of the SUM that is responsible for AS ABAP-based SAP systems. Because
DMO only works on AS ABAP-based SAP systems, the SAPup is used for the DMO procedure
(and some SUM scripts, as described below).
The SAPup process is started with option gt=httpchannel and it acts as a type of dispatcher,
because it handles all requests coming from the SAP Host Agent. This SAPup process starts a
second SAPup, which triggers additional tools such as R3load or tp.
Both SAPup processes are visible in the process list of the PAS host.
In the unlikely situation that you want to end the SAPup process the hard way, you have to
end the process tree for the SAPup with mode httpchannel .
The HTTP communication between SUM and SAP Host Agent requires a minimum patch level
for SAP Host Agent. That is why it is important to know how to update the SAP Host Agent. In
addition, the SAP Host Agent has to be configured so that for starting the SUM, it knows the
location of the SUM directory.
Hint:
The existing SAP Host Agent needs patch level 134 (or higher) to support the
direct upgrade from an archive. For lower patch levels, you have to unpack the
archive first.
In case of SUM 1.0, the syntax is: From the directory .../SUM STARTUP confighostagent
<SID>
On a Unix/Linux operating system, you execute this command as root user. On a Windows
operating system, you execute this command as user <sid>adm – so specifying the SID is
optional.
The interconnection is illustrated in the figure, Creating SAP Host Agent Configuration File for
Starting SUM.
Figure 13: Creating SAP Host Agent Configuration File for Starting SUM
Note:
The option confighostagent does not start the SUM or SAPup permanently, only
for the short time it takes to create the file.
Note:
Depending on the version of SUM, the option confighostagent is optional.
Note:
Do not replace the placeholder terms in square brackets because they are
interpreted by SAP Host Agent.
You have to be able to check whether the file exists. If it does not exist, the SAP Host Agent
returns an error message when you try to start the SUM procedure from within a web browser
window.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson introduces the SUM UI.
Business Example
As an administrator, you have to configure the DMO procedure and need to know about the
new UI and its features.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
SUM UI
SUM UI is Based on SAPUI5
SAPUI5 is an SAP library used in apps and offered for own development.
LESSON SUMMARY
You should now be able to:
Learning Assessment
1. Your source SAP system is running on Windows with an SAP MaxDB database. You want
to use the DMO procedure to migrate to SAP HANA database, using the inplace migration.
Which up to date SAP kernel is needed for the DMO procedure?
Choose the correct answers.
2. The configuration of SAP Host Agent to start SUM is mandatory, because the SAP Host
Agent is needed to connect the SUM UI to SAPup.
Determine whether this statement is true or false.
X True
X False
1. Your source SAP system is running on Windows with an SAP MaxDB database. You want
to use the DMO procedure to migrate to SAP HANA database, using the inplace migration.
Which up to date SAP kernel is needed for the DMO procedure?
Choose the correct answers.
You are correct! The up to date SAP kernel for Windows, SAP MaxDB is needed for the
shadow system. The up to date kernel for Windows, SAP HANA is needed for the target
SAP system. No SAP kernel for Linux is needed, because the source and the target
operating system of the SAP application server host is Windows – due to the inplace
migration.
2. The configuration of SAP Host Agent to start SUM is mandatory, because the SAP Host
Agent is needed to connect the SUM UI to SAPup.
Determine whether this statement is true or false.
X True
X False
You are correct! The SAP Host Agent connects the SUM UI to SAPup. Therefore the SAP
Host Agent must be configured to reach the SUM directory, which contains SAPup.
You are correct! A progress bar, the active roadmap step, and the content of log files is
provided via the SUM UI. The memory consumption of SUM cannot be seen.
Lesson 1
Starting with Roadmap Step 1 - Extraction 32
Lesson 2
Continuing with Roadmap Step 2 - Configuration 38
Lesson 3
Continuing with Roadmap Step 3 - Checks 47
Lesson 4
Continuing with Roadmap Step 4 - Preprocessing 51
Lesson 5
Listing DMO Procedure Steps 55
Lesson 6
Monitoring the Migration 61
Lesson 7
Continuing with Roadmap Step 5 - Execution 67
Lesson 8
Continuing with Roadmap Step 6 - Postprocessing 69
UNIT OBJECTIVES
LESSON OVERVIEW
This lesson explains how to start the DMO run.
Business Example
As an administrator, you are responsible for starting and executing the DMO procedure.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Hint:
Start the web browser from the WTS, not from the host of the AS ABAP based
source SAP system.
You have to supply the <SID>adm user and password because the SAP Host Agent needs
these to start the SAPup.
The first DMO dialog is the specification of the stack.xml file.
Figure 24: Choose Scenario specific Options and Provide first Passwords
If you want to provide a SPAM update after the DMO procedure has started, you have to
extract the archive manually, and place the update into the .../trans/EPS/in directory.
Caution:
Do not forget to choose the SAP HANA radio button in the first dialog box,
otherwise only the SAP system update is executed – without migrating the
database.
Hint:
Target database types MS SQL, IBM DB2, SAP MaxDB, and Oracle are only
available on request, and are therefore not shown by default. Therefore, a
specific configuration is required.
Landscape reorganization for the SAP HANA database is required during DMO: it
partitions and distributes tables across different SAP HANA nodes
Two scenarios exist, depending on the number of existing SAP HANA nodes (without
standby-node): scale-up (only one node) and scale-out (several nodes)
If the target database is a scale-out database, on the Migration Parameters dialog, the
DMO procedure offers a section called SAP HANA SCALE OUTwith a Landscape
Reorganization checkbox
Scale-out: Another dialog is shown before table creation, asking you to import a file to SAP
HANA. SAPup later triggers the distribution of the tables across SAP HANA nodes
(between table creation and table content migration).
DMO always compares the number of rows (count *). The table comparison compares the
content of rows.
Tool checks the content of source and target database tables, using cyclic redundancy
check sums (CRC).
Tool generates check sums for every 10000 rows, for example, on source and target side.
It then compares these.
Tool digs deeper where check sums do not match, until conflicting rows are found.
Tool stops after discovering more than 200 differences, as this points to systematic
errors.
Any decisions are made in the Database Migration Option dialog, and cannot be switched
off later.
Checking all tables is for test SAP systems only, due to performance load.
Checking happens in parallel for one table and multiple tables, using table splits.
Checking is for application tables only, repository tables are not allowed.
You may have to use transaction SNOTEto apply SAP Notes required by SUM.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson explains further configuration steps in DMO.
Business Example
As an administrator, you are responsible for configuring the DMO procedure.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
These amount of parallel processes during uptime (a small number should be selected
because the productive operation is running in parallel) and downtime (as many as the
hardware is capable of) have to be chosen.
Hint:
Configuring a number of 12 R3load processes means that 6 R3load pairs will be
used for the migration.
Additional parameters can be set, but they are not DMO specific.
You can adapt the number of processes later in the DMO procedure, even during the
migration, as follows:
Use the SUM Utilities menu and choose SUM Parameters SUM Process Parameters .
The SAP HANA client is required for the SUM to access the target database. You can install
the client manually, or provide the installation files. The SUM asks for the password of user
<SID>adm because this user is used for the installation.
Now, the details of the target database have to be provided, including the location of the
target SAP system license file (optional).
Hint:
The system-ID of the SAP HANA DB is different to the system-ID of the SAP
system. This does not mean that the SAP system changes its system-ID.
In case of SAP HANA, SUM needs the passwords for the user SYSTEM of the target DB tenant
and user SYSTEM of the target system DB.
Now, two users are created on the target database and you have to provide the password that
will be used for these users. Note that the passwords have to adhere to the SAP HANA DB
password policy.
The dialog for the password of user DBACOCKPIT is only shown if this user does not yet exist
on the SAP HANA DB.
As a standard SUM functionality (independent of the migration), the tool offers to include
customer transport requests.
As a standard SUM functionality (independent of the migration), the tool offers to include
SPDD and SPAU transport requests.
ASCS Split-Off
SAP recommends the use of an SAP system architecture with a separate ASCS setup. For a
target SAP system based on SAP_BASIS 7.50 with more than one application server, the SUM
automatically splits off ASCS if it is not yet separate (and if the SAP system has more than
one application server). In addition, SUM shows a dialog if the target SAP system is based on
SAP_BASIS 7.40, also offering to split off the ASCS if it is not yet separate.
Note:
This action is listed in the logs, but not shown on a dialog.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson covers some configuration steps for DMO step Preprocessing.
Business Example
As an administrator, you have to configure the DMO procedure.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Figure 43: Unresolved SPDD and SPAU from Previous SUM Run
Performing the steps from the ASU Toolbox is necessary only when performing a release
change – for example, an upgrade.
SUM ABAP Observer Monitor for SUM (including DMO) for monitoring the progress
Colleagues use a non-admin user for monitoring, but are not allowed to configure the DMO
process
2. Optional: Create OS user <SID>obs on the application server host to use for log on.
Note:
Port 1129 has to be used with https if SSL is configured.
LESSON SUMMARY
You should now be able to:
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Hint:
The dialog about open repair is only shown if the transport includes objects that
are affected by the update of the SAP system.
After some time, the DMO procedure proposes to lock the development environment. After
this point, no further development or transports are allowed. The shadow repository will be
created now, and any changes on the repository would not be included in the shadow
repository, and thus will not be part of the target SAP system.
After a while, the SUM asks to prepare the table partitioning for the scale up scenario if you
have not selected the Landscape Reorganization option (for scale-out). If you chose
landscape reorganization for scale-out scenarios, a similar dialog appears, which is not shown
here.
Until now, the DMO procedure executed the uptime processing, so the SAP system was still
available for end users. Now, the preparation for downtime has to be performed.
Depending on the archive mode of the source and target database, a backup has to be done
before and after the downtime.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson gives an overview of the general steps of the DMO procedure.
Business Example
You are responsible for the execution of a DMO procedure, and you have to explain to the
upper management how the DMO procedure works, and why the procedure can easily be
reset.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
The SAP Host Agent requests authorization from the browser. This user is used to start the
SUM. Because the DMO procedure is only working on AS ABAP based SAP systems (for
which the SAPup is the relevant SUM part), the SAPup is started.
After some basic configuration settings, such as checking the stack.xml, the SAPup will start
to create the shadow system. The shadow system consists of a shadow repository and a
shadow instance.
The shadow repository is created on the target database. It contains the basic tables and
some customizing tables, which will already be updated to the target release during uptime.
The shadow repository does not influence the PRD repository. The SAP system is still
running, and end users can work in the SAP system and use functionality (like a transaction)
that can change application data on the database.
The shadow instance is running on the PAS host, and is based on the shadow kernel.
Because the shadow repository is being built up on the target release, changes on the PRD
repository are no longer allowed, as they would not be considered on the shadow repository.
This is why in this phase, the SAP system is running and available for end users (uptime
processing), but the development environment is locked.
For the migration of the application data, two R3load processes are running as a pair. The first
R3load of the shadow kernel exports the data from the source database, and the second
R3load process imports the data into the target database. Both R3load processes are running
on the PAS host. The DMO configuration includes configuring the number of R3load pair
processes to run in parallel.
After the migration of the application data, the shadow instance is removed. The target kernel
is now used for the SAP system, and the SAP system is started. The SAP system is still in
downtime because it cannot be used by end users.
Now the application tables are updated to the target release.
R3load Modes
The DMO procedures uses R3load for the migration, like the classical migration based on the
Software Provisioning Manager (tool inside: SAPinst) does. For the typical classical migration,
the R3load file mode is used.
The file mode means that the export files are created, and imported later. Meanwhile, it is also
possible to use a parallel export and import for the classical migration.
Another possibility for the classical migration is to use the R3load socket mode, which
transfers the files using a socket connection.
With the DMO procedure, using the inplace migration approach, both R3load processes are
executed on the same host, the PAS host. This allows the use of the R3load pipe mode, which
transfers the data using the main memory of the host. No files are created, and so no
directory has to be prepared to host all export files.
Figure 61: R3load for DMO Using Pipe Mode (Inplace Migration)
In case the R3load stops, the SAPup will restart the process without the need for manual
intervention by a user.
In case an inplace migration is not desired, you can perform DMO with system move.
DMO of SUM offers the move of the primary application server (PAS) from the source SAP
system landscape to a target SAP system landscape during the DMO procedure.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson explains the table split and migration procedure.
Business Example
As an administrator, you are responsible for the DMO procedure and you would like to analyze
how the SAPup is migrating the tables.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Uptime processing
The shadow repository is created on the target database (on target release). This is
called Shadow on Target (SOT). In older SUM versions – and with SUM 1.0 – the shadow
repository was created on the source database and migrated to the target database
during uptime.
Downtime processing
The application tables are migrated (on source release) to the target database, and
converted to the target release later (for example, in phases PARCONV_UPG and
PARMVNT_UPG).
Note:
A bucket is a work package for an R3load pair.
Figure 63: Monitoring Migration Using Sub Progress Bar and Log Tail
Buckets have different sizes, so the percentage is not directly correlated to the number of
buckets.
The SUM Utilities window offers an area to monitor the R3load processes: the Process
Buckets monitor. It is even possible to reschedule a process that is in status error. That way,
you do not have to wait until all the packages are processed and an error message is
displayed on the SUM UI. The Process Buckets monitor also lists the export and import
duration, and offers easy access to the log file of the respective process.
Note that some new tables are only imported, so there is only one R3load working on that
bucket (instead of two). This is visible in the Process Buckets monitor because only the import
duration is listed, and only the import log is made available.
The two parts on the repository, and on the application data, consist of respective phases
with extension sizes, create , prp, and run.
SIZES
SAPup determines the table sizes (used by PRP phases later)
CREATE
SAPup triggers the tables creation on the target database (empty tables)
PRP
SAPup triggers the creation of directories (migrate_*) and control files (required for
R3load execution: STR, TSK, CMD files)
RUN
SAPup triggers migration of tables into the target database (based on control files)
Hint:
In case of an error, there is no need to adapt files. SAPup recreates a valid *.TSK
file by itself.
After the table creation on the target database, the DMO procedure shows a dialog proposing
the landscape reorganization.
The sequence of the migration phases is as follows:
1. EU_CLONE_EXT_PRP
2. EU_CLONE_EXT_RUN
3. EU_CLONE_MIG_SOT_PRP
4. EU_CLONE_MIG_SOT_RUN
5. EU_CLONE_MIG_DT_SIZES
6. EU_CLONE_MIG_DT_PRP
7. EU_CLONE_MIG_DT_CREATE
(DT starts afterwards)
8. EU_CLONE_MIG_DT_RUN
Only the migration of the application data is done during downtime (phase
EU_CLONE_MIG_DT_RUN).
Hint:
Some phases with DT in the name are executed during uptime processing.
load/migrate_sot
Prep and run of repository table content migration.
load/migrate_dt_create
Creation of application tables.
load/migrate_dt
Prep and run of application table content migration.
log
Log files, especially EU MIGRATE <x> PRP.LOG and EU MIGRATE <x> RUN.LOG (<x>
stands for SOT and DT, without blanks)
Hint:
For the create parts, the folder creation and execution are handled together in
one phase (no split into prep and run).
EU MIGRATE DT PRP.LOG
Number of buckets, total size:
1 ETQ399 Command file 'MIGRATE_DT.BUC': 108492 tables in 136 tasks,
size 29929.5 MB (estimated duration 223010,9 sec).
EU MIGRATE DT RUN.LOG
Details of R3load process execution:
3 ETQ123 <n> (n): PID n exited with status 0 (time n.nnn real)
3 ETQ399 ============= <n>, Progress n/n (n.nn%)
Summary on migration rate (for example):
2 ETQ399 Summary (export+import): time elapsed 1:32:05, total size
29930 MB, 5.42 MB/sec (19.50 GB/hour).
Note:
If the run was interrupted, the migration rate in the log file considers only the run
of the last part (a .SAV file contains previous rates). In general, only the migration
rate for a run without issues is considered as meaningful.
Big tables must be handled in several buckets, so they must be split. For table splitting in
DMO, the following applies:
The name of log file does not resemble the table name.
SAPup uses its own logic for table split calculation (without using R3ta).
Tables and table parts are organized in buckets (executed by an R3load pair).
The number of segments per table is the number of buckets per table.
For a target release 7.40 (and above), the information about row or column store is part of
the dictionary. For customer tables, this information may have to be set manually in the
shadow repository after it has been created on the source database.
For a target release 7.31, SUM will use a file that contains the row/column information
(SUM/abap/bin/ROWSTORELIST_DMO.txt ). Customer tables can be added manually
into this file to provide the row or column store assignment.
Note:
The migration sequence will start with the nametabs (runtime table
definitions), then migrate the column store tables, then the row store tables.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson covers the DMO steps in roadmap step Execution.
Business Example
As an administrator, you are responsible for finishing the DMO procedure, so you need to
know the sequence of steps in roadmap step Execution.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Don't get mixed up: The end of the SUM technical downtime is reached. The technical
downtime ends later, when all technical steps are performed, including the technical follow-on
activities. The business downtime ends even later – when the business-related steps are
performed, and all tests are positive.
LESSON SUMMARY
You should now be able to:
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Finally, the DMO procedure is completed. A dialog box with the evaluation form is shown.
LESSON SUMMARY
You should now be able to:
Learning Assessment
X True
X False
2. You are applying SAP Support Packages during an SUM DMO run to SAP HANA. Which
options are possible to select during configuration?
Choose the correct answers.
X A Single System
X B Standard
X C Expert Mode
3. As a result of Roadmap Step 3 - Checks, it can be necessary to extend the freespace in the
source database.
Determine whether this statement is true or false.
X True
X False
4. After confirming Lock the development environment now , which actions are still possible?
Choose the correct answer.
X C Creating and changing application data (for example, VA01) and user master
records ( SU01)
X D Releasing and importing transport requests via the Transport Manager ( SE09) and
Transport Management System ( STMS)
5. During a standard DMO run, the creation of the shadow repository is performed during
uptime, the migration of the application data is performed during downtime.
Determine whether this statement is true or false.
X True
X False
6. During downtime migration, which information can you receive in the Charts Control
Center, via the SUM Utilities of the SUM UI?
Choose the correct answers.
X D Interfaces from other SAP systems cannot log on to the SAP system
8. When a standard DMO run is completed, you can still reset the procedure.
Determine whether this statement is true or false.
X True
X False
X True
X False
You are correct! SUM relies on an up to date version of SPAM/ SAINT in the source release,
because SUM calls functions of SPAM/ SAINT.
2. You are applying SAP Support Packages during an SUM DMO run to SAP HANA. Which
options are possible to select during configuration?
Choose the correct answers.
X A Single System
X B Standard
X C Expert Mode
You are correct! You can select Standard . You can also switch the Expert Mode on. You
cannot choose Single System.
3. As a result of Roadmap Step 3 - Checks, it can be necessary to extend the freespace in the
source database.
Determine whether this statement is true or false.
X True
X False
You are correct! It can be necessary to extend the freespace in the source database.
4. After confirming Lock the development environment now , which actions are still possible?
Choose the correct answer.
X C Creating and changing application data (for example, VA01) and user master
records ( SU01)
X D Releasing and importing transport requests via the Transport Manager ( SE09) and
Transport Management System ( STMS)
You are correct! You cannot use the ABAP workbench, you cannot use the Note Assistant,
and you cannot release and import transport requests. But you can still change
application data and user master records.
5. During a standard DMO run, the creation of the shadow repository is performed during
uptime, the migration of the application data is performed during downtime.
Determine whether this statement is true or false.
X True
X False
You are correct! During a standard DMO run, the creation of the shadow repository is
performed during uptime, the migration of the application data is performed during
downtime.
6. During downtime migration, which information can you receive in the Charts Control
Center, via the SUM Utilities of the SUM UI?
Choose the correct answers.
You are correct! In the Charts Control Center , you can monitor the configured maximum
number of parallel R3load processes, the actual number of running R3load processes, and
the process buckets being processed. To see the memory consumption of the target
database, you would have to check the target database host, for example, using the SAP
HANA Administration Console, in case of an SAP HANA database.
X D Interfaces from other SAP systems cannot log on to the SAP system
You are correct: During the downtime phases of SUM, you have to prevent end users from
logging on, prevent batch jobs from the business from starting, and prevent interfaces
from other SAP systems from logging on to the SAP system. But the database must be up
and running during downtime, because it is accessed, for example, during downtime
migration.
8. When a standard DMO run is completed, you can still reset the procedure.
Determine whether this statement is true or false.
X True
X False
You are correct! Even if a standard DMO run is completed, you can still reset the
procedure.
Lesson 1
Resetting the DMO Procedure 77
Lesson 2
Tuning the DMO Downtime 81
Lesson 3
Explaining the SUM Release Schedule 92
Lesson 4
Listing Migration Options to SAP HANA 95
UNIT OBJECTIVES
LESSON OVERVIEW
This lesson explains how to reset the DMO procedure.
Business Example
As an administrator, you are responsible for configuring the DMO procedure. You want to
restart the DMO procedure and need to know how the reset functionality in DMO works.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Hint:
A reset is possible even after productive use of an SAP system has started,
but this will lead to a loss of data.
When you choose Reset, the next dialog requests that you confirm that you want to reset.
After you have confirmed that you want to start the reset, the DMO procedure will take a
while, before displaying a success message.
Of course, the duration of the reset depends on the progress. The more phases that have
already been executed, the longer it takes to reset the DMO procedure. In some cases, you
will have to provide passwords – for user DDIC in client 000, for example.
Some changes are not reset.
SPAM/SAINT update
Choose Cleanup to clean up the SUM folders, like the log folder.
After the cleanup, you can start the tool again (using the same SUM folder) to start a new
DMO procedure.
A command line reset is possible as well. This is especially important if the SUM UI is not
available.
4. Choose Reset:
01) * Exit
02) - Reset
03) – Cleanup and start afresh
[Exit]: 02
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson shows you how to tune the DMO downtime and improve the DMO procedure
runtime.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Migration is influenced by
- Number of R3loads configured for downtime
- Network bandwidth: use 10 Gbit/s network card, use no firewall
Rule of thumb: migration rate of ~ 300 GB/hours should be possible in standard set up
with an estimated additional ~8 hours for the update part, technical downtime can be
estimated
Optimize table split calculation by providing table duration file from previous run
Benchmarking
You execute it prior to the DMO run to test the migration rate, and adjust the number of
R3loads
Options allow to only export data, or to only migrate part of the database
Recommended Procedure
Continue with DMO, reuse duration file from benchmarking run, use migration repetition
option
Vary number of R3loads to find optimum, use migration repetition option (test cycle) for
fast repeat
Then keep optimum number of R3load processes fixed during complete procedure
Note:
For tables with more than 2 billion (2 000 000 000) entries, the benchmarking
run will lead to an SAP HANA error because the report SMIGR_CREATE_DDLis not
triggered for the benchmarking run.
This report SMIGR_CREATE_DDLconsiders the table size for the CREATE statements on SAP
HANA.
The last step of benchmarking is to drop the tables from target database.
At the end of the benchmarking run, any data migrated to target database is already
deleted.
During the migration, you should monitor the performance of the PAS host on which the
SAPup is executed, and adjust the number of R3load processes to make best use of the
host’s performance.
Using table migration durations for next run
SAPup stores the table migration durations in dedicated files. These files can be used for
the next DMO run (on the same SAP system) to speed up the migration because SAPup
will then start the migration for the tables with the longest runtime first. It is more
effective to sort the tables based on their migration duration than on their size.
During the first run, the file MIGRATE_DT_DUR.XML(downtime: application tables) is created
in directory .../SUM/abap/doc/analysis . It has to be copied to the download folder of the
next run.
File has to be copied to the download folder of the next DMO run.
Note:
When the Test Cycle option is used, SUM will automatically use the duration
file, and consider it for the split determination of the next run.
It is possible to put the UPGANA.XML file into the download directory for the next run. SAPup
will use it for a more precise runtime estimation (based on previous runtime for the phases,
instead of only the number of phases).
SUM restrictions apply: not all tables can be chosen, for example, SAP_BASIS tables are
not suitable.
Change rate is relevant: tables with high change rate shall not be selected, as replication
may not be fast enough to work against change rate.
The start of the procedure and the uptime processing does not change.
Due to end user activity, the triggered tables may have been changed. This delta has to be
transferred.
Finally, there will be a balance between ongoing table changes and delta transfer. You will
decide to enter the downtime.
The kernel is switched. All application tables are updated to the target release.
The triggers on the (largest) tables with online replication write into log tables.
Figure 89: Downtime Minimized Approach for SAP BW Systems (aka Delta Queue Cloning)
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson explains the DMO release schedule.
Business Example
As an administrator, you need to know the release schedule for the SUM so that you can plan
your migration projects accordingly.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
SUM 1.0 is Available Since 2011, and SUM 2.0 Since 2017
SUM 2.0 must be used if the target release is AS ABAP 7.50 and above
SUM is delivered with the Software Logistics (SL) Toolset. The following list provides a basic
overview of the SL Toolset:
For further information about the delivered software logistics tools, the supported
implementation processes, and SAP application products, see Central Release Note for
Software Logistics Toolset 1.0 – 1563579.
Note:
Don't get mixed up with SAP HANA DB and SAP S/4HANA!
Note:
SUM can only convert an SAP ECC system to SAP S/4HANA Server. no other SAP
Business Suite systems can be converted. No other SAP S/4HANA systems can
be targeted using SUM.
New Implementation
The SAP S/4HANA Conversion is based on the Software Update Manager, with or without
DMO – depending on whether the source SAP system is already running on SAP HANA
database or not.
LESSON SUMMARY
You should now be able to:
LESSON OVERVIEW
This lesson gives an overview about all of the possible ways to run an SAP system on an SAP
HANA database.
Business Example
You are asked to give a recommendation on how to migrate an existing SAP system to an SAP
HANA database and you need to know the options.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Migration Options
There are three main migration options as follows:
Migration Options
Hint:
Note that SAP also offers migration services.
This option allows for the addressing of changes to an existing solution landscape by
transformation with SAP Landscape Transformation software, with reduced effort to build
targeted landscape (such as via shell creation with carve-out options and system
consolidation). It is complemented by transformation services (such as Data Management
Services or System Landscape Optimization consulting services). For more information on
these services, see the SAP Help Portal at https://help.sap.com/viewer/product/
SAP_LANDSCAPE_TRANSFORMATION.
LESSON SUMMARY
You should now be able to:
Learning Assessment
X True
X False
2. Which are tuning methods for the database migration, using DMO of SUM?
Choose the correct answers.
3. Which of the following are part of the Software Logistics (SL) Toolset?
Choose the correct answers.
4. For a migration to SAP HANA database, it is generally recommended to use DMO of SUM.
Determine whether this statement is true or false.
X True
X False
X True
X False
You are correct! Resetting the DMO procedure can be done by SUM itself – it does not
require a database restore/recovery.
2. Which are tuning methods for the database migration, using DMO of SUM?
Choose the correct answers.
You are correct! To tune the database migration, you can adapt the number of parallel
R3load processes, use the table migration duration files from a previous run, and perform
a benchmark using the benchmarking options of SUM. nZDM is not possible using DMO of
SUM – it is available for SUM runs without DMO, only.
3. Which of the following are part of the Software Logistics (SL) Toolset?
Choose the correct answers.
You are correct! SUM, SWPM and SPAM are part of the SL Toolset. TMS is not part of the
SL Toolset, it is a transaction inside an AS ABAP based SAP system: transaction STMS.
4. For a migration to SAP HANA database, it is generally recommended to use DMO of SUM.
Determine whether this statement is true or false.
X True
X False
You are correct! In general, you should use DMO of SUM to migrate to SAP HANA
database.