Skip to Main Content
  • Questions
  • Will DataPump STOP_JOB or KILL_JOB do data rollback upon table-space issues?

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Alex.

Asked: January 08, 2018 - 6:09 pm UTC

Last updated: January 09, 2018 - 1:06 am UTC

Version: 11G

Viewed 1000+ times

You Asked

Half way through data load using impdp (DataPump) got index partition space error.

So I did the following:

1. Attached to job.
2. Issued KILL_JOB
3. Restarted DataPump load.

After this got duplicates.

How do I rollback partial DataPump loads?

and Connor said...

If you got an error on index space, then presumably that table load portion has been completed.

So on your next run (ie, re-run) of your import you can use the TABLE_EXISTS_ACTION option to determine which you wish to do:

TABLE_EXISTS_ACTION=[SKIP | APPEND | TRUNCATE | REPLACE]

The default for this option is SKIP, but since you are seeing duplicates, I suspect you were also using CONTENT=DATA_ONLY, because in that circumstance the default becomes APPEND.

It may have been better in your case to have run a STOP_JOB (rather than kill), fix the space issue, and then run START_JOB to resume processing.


Is this answer out of date? If it is, please let us know via a Comment

More to Explore

Data Pump

All of the database utilities including Data Pump are explained in the Utilities guide.