This document purpose is to explain the way of duplicating MEGA data that are stored in an Oracle RDBMS and how to use this data to create a duplicate MEGA environment that will point on this duplicated data.

It is important to have no end user activity on the MEGA environment while the export procedure is carried out to avoid inconsistency in the exported data.

You can go through the whole document to carry out the entire scenario. You can also jump directly to the Oracle data import section if you already have the Oracle dump files containing the SCHEMAs hosting the MEGA environment data.

MEGA recommends using a different Oracle SCHEMA for each MEGA repository. For example, if you have to deal with a MEGA environment like this one

It would mean that there are 4 SCHEMAs involved (also 1 for the SystemDb). It is technically possible to have every repository hosted in the same SCHEMA but not recommended.

For the following scenario, a local installation of Oracle will be used for exporting and importing data. The service name of this instance is EDE2.

Refer to “Web Front-End Architecture Overview” or “Windows Front-End Architecture Overview” guides to find out the Oracle supported versions of your version.

The Oracle tools that will be used are:

- Oracle SQL Developer, a free graphical tool that can be used for Oracle administration tasks. See Oracle documentation for details.

- Oracle Data Pump to export and import the physical Oracle data. There are different Data Pump components but you will be using only the command-line clients expdp and impdp. See Oracle documentation for details.