Then the database connection of the SAP system is switched to the target database, and then the downtime starts. The processing sequence is based on the shadow system functionality of SUM: the SUM creates the shadow repository on the target database until downtime phase, while in parallel the SAP HANA database is setup (client, schema, …). It can be used for other target database types meanwhile as well, see respective SAP note for details (see below). The DMO is an inplace-migration (instead of a new installation): it upgrades and migrates the existing system while keeping the system-ID, PAS host name, and connectivity settings stable.ĭMO for SAP NetWeaver BW and for SAP Business Suite systemsĭMO is available with Software Update Manager 1.0 SP09 and higher, and can be used for systems based on AS ABAP. heterogenous system copy, using Software Provisioning Manager). It is sometimes referred to as the one-step migration procedure, compared to the classical migration (i.e. The Software Update Manager (SUM) includes an option that combines the upgrade with the database migration “database migration option” (DMO) for SUM.
If you want to migrate an existing SAP system (running on anyDB) to a SAP HANA database, required steps may be a dual-stack split, a unicode conversion, a database upgrade of anyDB, an upgrade of your SAP software, and a database migration to SAP HANA. The source database remains consistent, so a fast fallback is possible.(*: only possible for a target based on 7.40) System update, Unicode Conversion (*), and database migration are combined in one tool.It combines SAP upgrade and database migration to SAP HANA in one tool! Use the database migration option (DMO) of the Software Update Manager (SUM): You want to migrate your existing SAP ABAP system to the SAP HANA database.
0 kommentar(er)
