Databases Reference
In-Depth Information
Now, place the following commands in the
exp.par
file:
userid=mv_maint/foo
directory=dp_dir
dumpfile=exp.dmp
logfile=exp.log
tables=inv
reuse_dumpfiles=y
Next, the export operation references the parameter file via the
PARFILE
command line option:
$ expdp parfile=exp.par
Data Pump processes the parameters in the file as if they were typed on the command line. If you find yourself
repeatedly typing the same commands or using commands that require quotation marks, or both, then consider using
a parameter file to increase your efficiency.
■
Don't confuse a Data pump parameter file with the database initialization parameter file. a Data pump parameter
file instructs Data pump as to which user to connect to the database as, which directory locations to read/write files
to and from, what objects to include in the operation, and so on. In contrast, a database parameter file establishes
characteristics of the instance upon database startup.
Tip
Exporting and Importing with Granularity
Recall from the section “Data Pump Architecture,” earlier in this chapter, that there are several different modes in
which you can invoke the export/import utilities. For instance, you can instruct Data Pump to export/import in the
following modes:
•
Entire database
•
Schema level
•
Table level
•
Tablespace level
•
Transportable tablespace level
Before diving into the many features of Data Pump, it's useful to discuss these modes and ensure you're aware of
how each operates. This will further lay the foundation for understanding concepts introduced later in the chapter.
Exporting and Importing an Entire Database
When you export an entire database, this is sometimes referred to as a full export. In this mode the resultant export
file contains everything required to make a copy of your database. Unless restricted by filtering parameters (see the
section “Filtering Data and Objects,” later in this chapter), a full export consists of
