Hi,

Import is Always take more time then export. i'd prefer to take the export at Query level and then Import, it must be faster.

check the alert log for details. may you can get some hint there

HTH

Do you really need query parameter to import in? I guess you want to import in all data...

Did you try to disable foreign key constraints before import?

Do you have triggers on the target table? You may want to disable those too.

Yes, there could be a locking issue here as well.

Check for blocking sessions etc.

How big is the export dump file and how many records it is importing?

While importing , oracle runs simple inserts statements. Check what else going on in database? Are there any locks? Check your alert.log file to check if you are running out of space in any of your tablespace.

Also, check if this note can help:

Checklist For Slow Performance Of DataPump Export (expdp) And Import (impdp) (Doc ID 453895.1)

hm use this query instead of yours

SELECT oracle_username || ' (' || s.osuser || ')' AS "Username",
       s.sid || ',' || s.serial# AS "Session ID",
       owner || '.' || object_name AS "Object",
       object_type AS "Object type",
       decode(l.block, 0, 'Not Blocking', 1, 'Blocking', 2, 'Global') As "Status",
       decode(v.locked_mode, 0, 'None', 1, 'Null', 2, 'Row-S (SS)', 3, 'Row-X (SX)', 4, 'Share', 5, 'S/Row-X (SSX)', 6, 'Exclusive', to_char(lmode)) As "Mode held"
  FROM v$locked_object v, dba_objects d, v$lock l, v$session s
 WHERE v.object_id = d.object_id
   AND v.object_id = l.id1
   AND v.session_id = s.sid
 ORDER BY oracle_username, session_id

Hi,

As other people have already suggested - it's likely doing something 'after' the actual table load. Try looking in v$session_longops to see what it thinks is happening.

Import will always be slower than export - primarily because an export just expots index definitions - the import has to actually create them - which can be a very long operation on big tables even if done in parallel.

Cheers,

Harry