

If there are self-containment violations, then Export identifies all of the problems without actually performing the export. That is, all storage segments of all tables (and their indexes) defined within the tablespace set must also be contained within the set. Transportable tablespace mode requires that the specified tables be completely self-contained. Then, a transportable tablespace import is performed to import the dump file containing the metadata and to specify the data files to use. The tablespace data files are copied in a separate operation. In transportable tablespace mode, only the metadata for the tables (and their dependent objects) within a specified set of tablespaces is exported.

Interactive-command mode is also enabled when you attach to an executing or stopped job.įor a complete description of the commands available in interactive-command mode, see "Commands Available in Export's Interactive-Command Mode".Ī transportable tablespace export is specified using the TRANSPORT_TABLESPACES parameter. This mode is enabled by pressing Ctrl+C during an export operation started with the command-line interface or the parameter file interface. Interactive-Command Interface : Stops logging to the terminal and displays the Export prompt, from which you can enter various commands, some of which are specific to interactive-command mode. See "Use of Quotation Marks On the Data Pump Command Line". The use of parameter files is recommended if you are using parameters whose values require quotation marks. The only exception is the PARFILE parameter, because parameter files cannot be nested. Parameter File Interface: Enables you to specify command-line parameters in a parameter file. For a complete description of the parameters available in the command-line interface, see "Parameters Available in Export's Command-Line Mode". You can interact with Data Pump Export by using a command line, a parameter file, or an interactive-command mode.Ĭommand-Line Interface: Enables you to specify most of the Export parameters directly on the command line. To see some examples of the various ways in which you can use Data Pump Export, refer to "Examples of Using Data Pump Export".

See "Filtering During Export Operations". This is done using data filters and metadata filters, which are specified through Export parameters. See "Default Locations for Dump, Log, and SQL Files" for more information about directory objects.ĭata Pump Export enables you to specify that a job should move a subset of the data and metadata, as determined by the export mode. During an import operation, the Data Pump Import utility uses these files to locate each database object in the dump file set.īecause the dump files are written by the server, rather than by the client, the database administrator (DBA) must create directory objects that define the server locations to which files are written. The files are written in a proprietary, binary format.

The dump file set is made up of one or more disk files that contain table data, database object metadata, and control information. The dump file set can be imported on the same system or it can be moved to another system and loaded there. The dump file set can be imported only by the Data Pump Import utility. Data Pump Export (hereinafter referred to as Export for ease of reading) is a utility for unloading data and metadata into a set of operating system files called a dump file set.
