Moving a Database Using Data Pump
Overview
Using a full database export/import is one of the most reliable ways to migrate, restore or even upgrade (11g to 12c) a database from one system to another. The basic steps are outlined here.
Procedure
Assuming you have performed a full database export from the source, on the destination database:
- Install the same version of Oracle that exists on the source or higher.
- Create the core database using DBCA (and database LISTENER) .
- When you create the database ensure the TEMP tablespaces has the same name as the source. This is because all user schema will be bound to the TEMP tablespaces of the source. Your import will fail if you do not do this.
- For another option you can add a second TEMP tablespace matching the sources name.
- Take the database out of archive log mode.
This makes import go faster using significantly less I/O. - Create user data tablespaces.
- The main reason for doing this here flexibility. You can create them on the new system in the location you desire. They must have the same names as your source tablespaces of course.
- Upon the full database import Data Pump will see the tablespace has been already created and use it, otherwise user data tablespaces will be created exactly as they are on the source (same drive and specs).
- Set any database parameters.
- Create a Directory Object for your exports/imports.
- Perform the full database import.
- Put the database back in archive log mode.
- Bounce the database to ensure all is well.