Data Pump Import provides data and metadata filtering capability to help you limit the type of information that is imported.
Data specific filtering is implemented through the
SAMPLE parameters, which specify restrictions on the table rows that are to be imported. Data filtering can also occur indirectly because of metadata filtering, which can include or exclude table objects along with any associated row data.
Each data filter can only be specified once per table and once per job. If different filters using the same name are applied to both a particular table and to the whole job, then the filter parameter supplied for the specific table takes precedence.
Data Pump Import provides much greater metadata filtering capability than was provided by the original Import utility. Metadata filtering is implemented through the
INCLUDE parameters. The
INCLUDE parameters are mutually exclusive.
Metadata filters identify a set of objects to be included or excluded from a Data Pump operation. For example, you could request a full import, but without Package Specifications or Package Bodies.
To use filters correctly and to get the results you expect, remember that dependent objects of an identified object are processed along with the identified object. For example, if a filter specifies that a package is to be included in an operation, then grants upon that package will also be included. Likewise, if a table is excluded by a filter, then indexes, constraints, grants, and triggers upon the table will also be excluded by the filter.
If multiple filters are specified for an object type, then an implicit
AND operation is applied to them. That is, objects participating in the job must pass all of the filters applied to their object types.
The same filter name can be specified multiple times within a job.
To see a list of valid object types, query the following views:
DATABASE_EXPORT_OBJECTS for full mode,
SCHEMA_EXPORT_OBJECTS for schema mode, and
TABLE_EXPORT_OBJECTS for table and tablespace mode. The values listed in the
OBJECT_PATH column are the valid object types. Note that full object path names are determined by the export mode, not by the import mode.