Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I did a start_job=skip_current on a large import because I thought it was hanging on some bad data. It turns out it was just a really large index so I'd like to re-run it but I don't want to do the entire import again. I know I can have it skip tables that are already there using the table_exists_action parameter, but does that apply to other objects, like indexes? If not, is there any way to just import the items I skipped?

share|improve this question
up vote 1 down vote accepted

extract the SQL (sqlfile=xxxx) and create the index(es) by hand ?

share|improve this answer
That's what I ended up doing so I'm accepting this answer, although I think setting table_exists_action=skip would work. I know it works for tables, but I'm not sure about indexes. – Brian Deterling Dec 1 '09 at 3:53

If you know what index is missing, Datapump supports an "include=" parameter that should allow you to import just this one object.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.