1/1

The dual-stack split is relevant for systems combined in a dual-stack, like SAP ERP with SAP
Enterprise Portal. DMO cannot be used for SAP Solution Manager for SAP NetWeaver PI
(classical installation as dual-stack).
The figure, Introduction of DMO Phases, illustrates a brief overview of the DMO phases that
are executed by the SUM tool.
Figure 3: Introduction of DMO Phases
Step 1 includes some preparations that are done, like providing stack.xml, passwords, and
download folder. On the SAP HANA database, the DMO procedure only creates required
users and schema.
Step 2 includes the creation of the shadow repository on the source database. This is still
uptime processing, so the system is available for end users. The shadow repository is then
copied to the SAP HANA database.
Step 3 is the switch to the downtime. The 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 upgrade 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 artefacts are reset as well.

Check Source System Status

Business Example
You have to check the status of the ABAP source system prior to a DMO procedure.
Check ABAP Source System for Status and Release
Check the status, number of instances, and the release of the ABAP source system.
1. Log on to the operating system (OS) of your source system host.
2. Use the SAP Microsoft Management Console (SAP MMC) to check the system status, the
number of instances, and the number of work processes.
3. Log on to the ABAP source system and check the component and software component
versions.
4. Check the level of SPAM/SAINT.

Check the status, number of instances, and the release of the ABAP source system.
1. Log on to the operating system (OS) of your source system host.
a) Connect to the Common Training WTS .
b) From within the Common Training WTS , open a remote desktop connection to connect
to your system landscape TH-HA250SPSxx-###.
c) Log on with train##.
d) From within TH-HA250SPSxx-###, open a remote desktop connection to the host of
the ABAP source system.
e) Log on with user <SID>adm and the password provided by your instructor.
2. Use the SAP Microsoft Management Console (SAP MMC) to check the system status, the
number of instances, and the number of work processes.
a) Open the SAP Microsoft Management Console on the ABAP source system host, by
using the shortcut on the desktop for example.
b) Check that the system is running.
If the system is listed with a green icon, the system is running.
If the system is not running, start the system using the context menu with the
systemID icon, and choose All Tasks → Start ..... You will have to provide the password
of the <SID>adm user.
c) Check the number of instances listed. In the left area of the screen, below Console
Root→ SAP Systems → <SID>, there is only one instance listed: <hostname> 0.
Note:
<hostname> has to be replaced by the host name of your ABAP source
system.
d) Check the number of work processes of type Dialog (DIA) and Batch (BTC), by using
the menu entry AS ABAP WP Table .
There are 10 DIA and 10 BTC work processes.
e) Check if the system has a separate ASCS instance.
There is only one instance which includes the message server, so the system