Databases Reference
In-Depth Information
Data Pump restart capability
In case of failure or any other circumstances that prevent the Data Pump job from
successfully ending its work, an implicit recommencing feature is activated. The
job enters a suspended mode that allows the DBA to attach this feature to the job.
It is important to emphasize that the master job table must positively identify the
interrupted job, otherwise it won't be possible to restart the job once the circumstance
behind the failure has been properly corrected.
In order for the user to attach to the job, it must be connected with the
ATTACH
command line option properly set. At this point, it becomes evident why it is a
good practice to have a name for the data pump job, other than the default system
generated name.
Getting information about the export job
When a Data Pump task takes place, it can be monitored to find out if everything is
running fine with it. A view named
DBA_DATAPUMP_JOBS
can be queried to check the
task status.
SQL> select * from dba_datapump_jobs;
In this query it can be seen that a
FULL
(
C
)
EXPORT
(
B
) data pump job named
SYS_EXPORT_FULL_01
(
A
) is in
Executing
State
(
D
). It is executing with a default
parallel
degree
of
1
(
E
). In case of trouble, the status changes and it would be time to
work with the CLI mode to
ATTACH
to the job and take corrective action.
Search WWH ::
Custom Search