SAP Migration – Win/MaxDB Win & Linux/Oracle DB - PART 2

[joo_migueldimas]

Heterogeneous System Copy - R3load Method

As I described before, the source SAP system (W8M) is installed in Windows Server 2008 (R2) on a MaxDB 7.8 (x64) database. For this purpose, I need to use the SAP specific copy method - R3load (export and import) - because I will have a different database engine/vendor in the target platform. The R3load method consists of the export of all source database contents and then the import of all that content in the target SAP system database (Oracle database in this specific case). Therefore there are two stages:

s

• 1. Export Phase (source system)
• 2. Import Phase (target system)

1. Export Phase

This export phase was performed in the source server (sapwinmax). For this I used the Software Provisioning Manager tool (version 70SWPM*). For this purpose I ran the following two phases:

s

• 1.1. Export Preparation
• 1.2. Database Instance Export

1.1. Export Preparation

Finish with success:

1.2. Database Instance Export

Note: This warning is related with a task that I didn´t performed before and it is described in the system copy guide at chapter "Generating DDL Statements". So for this you need to go to transaction SE38 and run the ABAP report SMIGR_CREATE_DDL:

... export continuation:

As in my case was not generated any file, I selected the option "No, skip the report and run the export without SQL files"

You can see in the following video all the details of the "Parameter Summary" screen:

Finish with success:

- Size of the export directory that was generated at the end of this Export Phase:

=> CHECK THE CONTINUATION OF THIS DOCUMENT IN THE FOLLOWING LINK:

SAP Migration – Win/MaxDB <=> Win & Linux/Oracle DB - PART 3