Database Migration Option: Target Database SAP MaxDB

Execution

In this roadmap step, the switch to the target system takes place.

The SUM completes the copy import action during downtime for all tables with set triggers. The EU_SWITCH phase completes the switch to the new system. All tables prepared in the shadow system are copied to the target system. The KX_SWITCH_1 phase switches the SAP kernel. The PARCONV_UPG phase converts the application table, and the phase TABIM_UPG imports the remaining data. Finally, the XPRAS_AIMMRG phase starts the XPRAs required by the system.

The following DMO-specific actions are carried out:

  • Migration of application data

  • Repository and kernel switch

  • Adoptions of structures to new release (phase PARCONV)

  • Main import (phase TABIM)

  • XPRAS

Further features:

  • Migration of application data from source database to target database

  • You can change the number of R3load processes dynamically in the SUM Utilities (Extended UI).

  • Consistency of the migrated content is checked by the command SELECT COUNT(*) FROM "<table_name>" on each table.

  • Time estimation for the overall process and for long-running phases is written to the file <SUM directory>/abap/log/SAPupStat.log