High-Level Documentation:
Oracle Database Import
Objective:
This document outlines the high-level steps for importing a database dump
file into an Oracle database using Oracle Data Pump (impdp). This is typically
required when moving data from one Oracle environment to another or
recovering a database from a dump file.
Prerequisites:
1. Target Database:
o Oracle Database 19c or later (ensure compatibility with the dump
file).
o Access to the target database as SYSDBA.
2. Dump File:
o The database dump file (e.g., wvly_dump.dmp) should be
available in the specified directory on the target machine.
3. Oracle Data Pump (impdp):
o Oracle Data Pump (impdp) must be installed and available on the
target system.
4. Directory Object in Oracle:
o Ensure a directory object pointing to the dump file location exists
in Oracle.
Assumptions:
This document assumes that Source and Target databases are
running Oracle database 19c (Editions may be different)
Table space details are set up the same on both databases.
There is adequate disk space for an Oracle DataPump dump (.DMP)
file on the Source and Target database servers
Import and export commands are to be run directly on database
servers logged in as Oracle user, other commands are to be run on
Bastion server with SQL Plus access to Source and Target databases.
The dump file is used only for user data and not for recreating the
client environment.
The dump file is being imported into an empty database and not an
existing database with user data.
We recommend that a trained Oracle DBA perform the following steps.
Database and OS Environment Details:
1. Operating System:
o OS Name: Red Hat Enterprise Linux
o OS Version: 8.7 (Ootpa)
2. Database:
o Database Version: Oracle Database 19c Standard Edition 2,
Release 19.18.0.0.0
o Database Configuration: Multitenant (PDBs
Steps to Import Database:
Step 1: Connect to the Target PDB
Connect to the target Pluggable Database (PDB) using SQL*Plus or a
similar Oracle client tool as SYSDBA.
Example:
sqlplus sys/<password>@<pdb_name> as sysdba
Step 2: Create a Directory Object
Create a directory object in Oracle pointing to the directory where the
dump file is located.
Example SQL command:
CREATE DIRECTORY DB_DUMP_DIRECTORY AS '/path/to/dumpfile/';
Step 3: Grant Permissions on Directory
Grant the necessary READ and WRITE privileges on the directory to the
user performing the import.
Example:
GRANT READ, WRITE ON DIRECTORY DB_DUMP_DIRECTORY TO <username>;
Step 4: Run Data Pump Import (impdp)
Execute the impdp command to start the import process. Ensure the
target database and directory are properly configured.
Example impdp command:
impdp "sys/<sys_password>@<pdb_name> as sysdba"
directory=DB_DUMP_DIRECTORY
schemas=QUERCUS,QUERCUS_PROXY,SOLAR,SOLAR_PROXY
dumpfile=wvly_dump.dmp logfile=wvly_import.log
Import only schemas QUERCUS, SOLAR, QUERCUS_PROXY, SOLAR_PROXY
Encountered the ORA-31684 errors due to the mentioned objects
already exists, client shouldn’t get these errors when they import
into new database.
Step 5: Monitor the Import Process
Monitor the import process by reviewing the log file (wvly_import.log)
to ensure there are no errors and the import completes successfully.
Example:
tail -f <output_file>
Conclusion:
This document provides a high-level overview of the necessary steps to
import an Oracle database dump file using the impdp utility. By following the
outlined steps, the import process can be completed smoothly. Errors
regarding the dependent objects can be ignored.
For more detailed information, refer to the official Oracle Data Import
Documentation.
