A company is running its on-premises SAP ERP Central Component (SAP ECC) production workload on SUSE Linux Enterprise Server. The SAP ECC workload uses an Oracle database that has 20 TB of data. The c

Question

Options

• AMigrate the SAP ECC workload to AWS by using AWS Application Migration Service.
• BInstall SAP ECC application instances on SUSE Linux Enterprise Server. Use AWS Database
• CMigrate the SAP ECC workload to AWS by using SAP Software Provisioning Manager on Oracle
• DInstall SAP ECC with an Oracle database on Oracle Enterprise Linux. Perform the migration by

• A
  11% (6)
• B
  5% (3)
• C
  2% (1)
• D
  82% (45)

Explanation

The two hard constraints are: (1) Oracle must remain the database technology, and (2) production downtime must be minimized. Installing SAP ECC with an Oracle database on Oracle Enterprise Linux on AWS and then using Oracle's native migration tooling (e.g., Oracle Data Guard standby, RMAN, or Transportable Tablespaces) allows near-zero-downtime cutover while keeping Oracle as-is. Option A (AWS Application Migration Service) performs a lift-and-shift at the OS level but does not handle Oracle licensing or schema migration cleanly for SAP. Option B (AWS Database Migration Service) does not support Oracle-to-Oracle homogeneous migration at the scale needed for an SAP production system. Option C (SAP SWPM on Oracle) performs an export/import, which requires extended downtime for 20 TB.

No community discussion yet for this question.