Export schema
Download dump file Download job definition
In Schema mode Data Pump exports all objects in the schema including user definition - unless something was explicitly flirted out.
This tutorial shows how to export schema OE, which is part of Oracle sample schemas.
- OE schema
- Oracle directory DATA_PUMP_DIR with WRITE access
- Job Creation Wizard: setting operation and mode, specifying dump file, specifying schema to export, submitting jobs.
- Main window: Job creation, job launching, progress log, job completion.
Tips:
- Schema is the default mode, it is used when mode is omitted.
- If SHEMA_LIST filter not specified, Data Pump processes schema of the user who launched job.
Schema mode is the default, AlderPump pre-selects it
for new jobs. All we need to do is select operation which is EXPORT.
Step 2/4: Specifying output file
We type in name of the output dump file. DIRECTORY object already set to
DATA_PUMP_DIR which is our destination, no need to change it. File type
was also pre-set to "dump file", no need to change that either. We click
on Add button to add dump file to the set. Like in Table-mode export,
we could limit maximum file size or use
substitution variable %U.
Download result file (zip archive, ~770K)
Step 3/4: Selecting schemas to be exported
We could create and launch job after specifying dump file; however that
would export schema of the connected user, i.e. SYSTEM. To export another
schema, SCHEMA_LIST or SCHEMA_EXPR filter is needed. There is no
restriction on number of schemas exported, but in this demo we only
specify one value: OE. We could launch Objects Picker and drag schema OE
to "add objects" hotspot, but it is quicker to just type it in.
Step 4/4: Running export
After job is created and entered DEFINING stage, we start it. Compared to
TABLE export, number of processed object types is significantly higher:
there are grants, roles, sequences, views, functions - we didn't see any
of those when ran TABLE mode export. Note the first type exported - it is
definition of OE user.
