Provision of connection parameters and users of the target database

Installation or update of target database client on the DMO host

Extraction of kernel for target database

Upload of additional packages, customer transport requests, and modifications

When you execute a migration to the target database, select either the Standard or Downtime-optimized scenario strategy in the initial dialogs of SUM. The option Single System is not intended for DMO. For more information about the options, see in the SUM Guide the section Planning  Initial Dialogs for the Specification of the Scenario.

The number of R3load processes, which you can set in the phase PREP_CONFIGURATION/INITSUBST, is the only visible parameter that affects the migration performance in the downtime. Note that you can configure the number of processes dynamically at a later point in time.

In the new DMO-specific phases, you provide connection data and user credentials for the target database.

In the phase PREP_CONFIGURATION/SUBMOD_MIG_CONFIG/HDB_INSTCLIENT, you provide details required for the installation of the target database client.

In phase SUMASK_LIVECACHE, a dialog box prompts you to decide on the configuration of your SAP liveCache. You can either specify that your SAP liveCache is migrated to the liveCache integrated in the SAP HANA database, or you can continue to use the external liveCache that is based on SAP MaxDB technology.

If you decide to migrate to the liveCache integrated in SAP HANA, you must still determine the execution mode of the report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD. The liveCache must be backed up before the downtime and restored afterwards. This is done with sections 'B' and 'C' of the report (see SAP Note 632357 for more information). You can choose whether the report is to be executed manually or automatically.