Database Migration Option (DMO) and Downtime Optimization

Keep this: job aid

DMO planning and tuning card

• DMO = software update or S/4HANA conversion + database migration in one SUM run, one downtime.
• Standard DMO is in place (PAS host stays); not supported across data centers due to latency.
• Variants: without system update (migration only, SAP HANA target); with system move (target set up first, file export, serial or parallel transfer); move variant for S/4HANA conversion.
• Prerequisites: Maintenance Planner with target-database kernels and HANA client, download folder, migration key, sized target, fast network, fresh source statistics.
• Fallback: source data not modified; SUM Reset; the window closes when users post in the target.
• Practice and time the reset in a mock; set the point of no return from measured times; name the decision owner.
• Downtime-optimized DMO: large tables in uptime with record and replay; source not on SAP HANA; not with DMO with system move.
• Tuning: export-only benchmark (100 percent), export and import (about 10 percent), vary R3loads with the test cycle option, reuse duration files, fix the optimum.
• Rule of thumb (SAP 2022): about 300 GB per hour plus about 8 hours for the update; replace it with measurements.
• Prove the transfer with table count and comparison checks, and the meaning with process-owner reconciliations.