Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

One Server Method Migration: Distribution Monitor Supported ?

Farid
Active Participant
0 Kudos

Hello,

We are about to start our Unicode Migration Project, using the one
server Method.
We will export our ECC6 Non-unicode system, uninstall the system,
reinstall it in Unicode Mode, and Import the ABAP dump.
Our Oracle database size is 2.2 GB, as you may imagine , since we will
be using the one server methode all the steps will be sequential, the
export/import downtime is expected to be quite consequent (2 days)
We have tried some optimizations methods like splitting the largests
tables, in addition to that, we were wondering whether we could use the
Distribution Monitor to distribute the CPU workload over several
servers.
But according to SAP note 855772, it appears that it is not possible in
our case. Do you confirma that if we perform our unicode migration
using the one server method, we cam not use the Distribution Monitor ?

"Do NOT use Distribution Monitor, if
You want to use only one host to do the Unicode Conversion
(use Sapinst or Migration Monitor instead)" Sap note 855772

Thank you for your help

1 REPLY 1

former_member189725
Active Contributor
0 Kudos

The basic idea behind using distribution monitor is to have a tool which can automate the process of parallel export and import using several application servers so that maximum hardware resources can be used to optimize the downtime as best as possible . Whether you use migration monitor or distribution monitor , the actual export and import will be performed by R3load which utilizes the available hardware resources . So if you do not have multiple application servers , it makes little sense to use Distribution monitor. Distribution monitor by itself does not do any speed up of the actual process , but acts as a facilitator for using multiple systems and making them work in sync. So just use migration monitor if you have a single system. The basic concept is to have as much as resources as possible to speed up the export/import process. Moreover , just for info  , the export is CPU bound whereas Import is I/O bound.

Regards

Ratnajit