impdp import is stuck on:


How can you debug this?


2 Answers 2


During the impdp process, it doesn't import indexes, in fact it runs number of CREATE INDEX statements.

There could be various reasons of slow index creations such as inefficient PGA memory allocation and IO performance of underlying storage. Parallel(depending on available server resources-CPU,IO) option could improve performance of index-creation.

How can you debug this?

  • You can use the following query to check the status of the job.

     select * from dba_datapump_jobs;

  • Join dba_datapump_sessions with v$session_wait to know whether the impdp session is waiting for some resources.

  • Check alert log for possible error/warning messages.

  • 1
    • To check the alert log: login to sqlplus > show parameter background and look for the background_dump_dest directory. There should be a log like alert_XE.log. Commented Aug 27, 2021 at 17:49

    It's not stuck. It just does not print every rebuilded index. You can view status of the process using DBA_RESUMABLE.

    select * from dba_resumable;

    • 2
      I took a look at those suspended tasks and found that some indexes cannot be created because tablespace is full. Granting more space solve the problem.
      – ntahoang
      Commented Apr 27, 2018 at 3:57

    Your Answer

    By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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