Skip to Content

SUM DMO Migration in AIX 5.3

Dear All,

I need your advice on the following scenario.

We are planning to migrate the oracle database to HANA (SoH) using SUM DMO.

Current SAP System:

OS : AIX 5.3

DB: Oracle

SAP : ERP 6.0 (SAP APPL - 600/0028 & SAP Basis - SAPKB70033).

Note: We are planning to upgrade oracle from 10.2 to 11.2 in existing SAP system before starting SUM (DMO) in AIX 5.3.

Proposed SAP System:

OS: SUSE Linux 12

DB: HANA 2.0


Can we use SUM(DMO with system move) in source system AIX 5.3 to achieve proposed SAP System?

AIX 5.3 OS is supported for latest SUM tool (DMO with system move)?

Please advice on this query.

Thank you,

Sarat N

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Nov 10, 2018 at 02:19 PM

    Did you check SAP Note:

    2537452 - Database Migration Option (DMO) of SUM 2.0 SP02

    All restrictions are listed there. Basically all Unix-based systems are supported.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 10, 2018 at 02:44 PM

    Hello Bartosz Jarkowski,

    Thank you for the note.


    c) DMO with System Move: Requirements and Restrictions

    Requirements for Source System and Source Database:

    • Database: All source databases excluding SAP HANA
    • Operating System (OS) of source primary application server (PAS) host: Any Unix-based or Windows operating system. In case of an IBM Db2 for i database, the PAS must always run on a IBM i Host.

    Requirements for Target System and Target Database:

    • Database: SAP HANA and SAP ASE only
    • OS of PAS host: Linux only


    • The scenarioUpgrade of SAP Solution Manager 7.1 to 7.2 using DMO with System Moveis not supported.
    • Regarding the migration of SAP SCM with automated Livecache migration, consider the following:
      • Before you start the Software Update Manager, consider the consistency checks of report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD (part A and B) before starting the SUM to cleanup inconsistencies.
      • Install the LCAPPS plugin on the target database for the installation of the database instance in the target system landscape. Make sure that you install the compatible version of the plugin with respect to the SAP HANA database.
      • Note that part A and B of report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD run on the source system landscape, part C runs on target system landscape.
      • Note also that due to technical restrictions, part A and B of report /SAPAPO/OM_LC_DOWNLOAD_UPLOAD run in roadmap step "Preprocessing", but after the explicit decision to enter the downtime. Hence they run in the technical downtime.
    • If the OS of the source PAS host is different than OS of the target PAS host, that is, the source OS is not Linux, proceed as follows:
      • After the DMO procedure is finished on the source system, and you have copied the SUM folder from the source to the target application server, extract the SUM archive for the target OS over the SUM folder to replace the executables. Make sure that you use the same SUM version (including patch level) in the source and the target system landscape.
      • Consider the workaround to install an additional application server (AAS) on Linux OS in the source system landscape, so that source OS and target OS are identical.
    • The table comparison checks are only supported if both the source OS on which the SUM is running and the target platform have the same endianness. See SAP Note 552464 for more information on endianness.
    • A change of the System-ID (SID) is not possible.
    • Short host names for source and target PAS must be different (not the fully qualified domain name), otherwise the SUM tool will not recognize to run on the target system landscape.
    • If you run SAP HANA and SAP NetWeaver AS ABAP on one server (for more information, see SAP Note1953429): The system ID of the database must not the same like the system ID of the primary application server (PAS) on the source system landscape.


    • You maynotrun the SUM on an AAS if ASCS is not yet running separately (such as standard DMO).
    • The scenario DMO without System Update is supported for DMO with System Move. You must implement SAP Note 1903295 in the source system before you start the DMO procedure to prevent an abortion of phase OB_RS_DMO_HDB_CONTENT_ACTIVATE with the error message "Batchjob 'RS_DMO_HDB_CONTENT_ACTIVATE' ... is aborted".
    • A reset of the DMO procedure in the target system landscape allows you to repeat the DMO procedure, but it does not restore the initial state of the target system. For this, delete the SUM directory on the target system and transfer the SUM directory data from the source landscape again.
    • Resetting the system in the source landscape works by using the reset option of DMO directly (as described in the DMO guide).
    • You need the identical SP version of SUM in both the source and target landscape. Pay particular attention to this when you download the SUM archive.



    Sarat N

    Add comment
    10|10000 characters needed characters exceeded