uffiles.blogg.se - Sap ecc ehp7 upgrade guide

no impact on ongoing developments, however it comes with it’s own restrictions. The dual maintenance strategy has an advantage of minimizing change freeze i.e. It’s a dual system landscape where old systems (source SAP systems) on old hardware (SOURCE) run simultaneously un-till production Go-LIVE. The diagram below depicts the landscape strategy that we incorporated. So we ran a couple of more MOCK runs to improvise the downtime. We built QAS system with DB restore method and tested DR at this stage.ĭMO3 is another MOCK run with latest production data, the SUM run got smoother this time however, the downtime requirement could not be fulfilled, it took about 1 day and 9 hours. The downtime came out to be around 2 days and 11 hours.

Recreate all steps that would be performed in production systemĭMO1 is for migration of development system where we faced a lot of issues as expected and hence this SUM run took the longest time.ĭMO2 is for migration of a MOCK environment copied from production to the HANA server, here we faced few more issues which were known issues and SAP documentation proved quite helpful.

QAS system will be built from MOCK system using backup and restore.

Prepare and execute unit test, functional and interface testing.

In below table a DMO cycle denotes 1 full export/import SUM run for SUM DMO with SYSTEM MOVE.

The project planning was done for 3 DMO cycles till production migration as mentioned below except that the number of MOCK runs increased in the actual project.In this blog post I will share details on following :.

It was unachievable in the first look but “UNPRECEDENTED TIMES LEAD TO UNEXPECTED LEARNING” and it indeed did. Now, the challenge was to make this a successful execution within the expected downtime. The setting was a bit complex such that DOWNTIME optimized DMO route couldn’t have been opted for and multiple downtimes were not affordable at all.

Main objective for the project was to achieve a downtime between 8-12 hours for a source database of size 5TB. We have recently migrated from ECC6.0 EHP4 on oracle database to ECC6.0 EHP8.0 on HANA database with hardware migration ( DMO with SYSTEM MOVE) for a customer. This blog post covers one-step upgrade and migration approach, performance optimization and downtime minimization for migration of ECC on oracle database to HANA database with EHP upgrade via SUM DMO with SYSTEM MOVE option.