DataPump Export (expdp) Is Slower Than Original Export (exp) (Doc ID 783093.1)

Last updated on JULY 10, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 10-Jul-2014***

Symptoms

DataPump export (expdp) takes more time than conventional export of the full database, specifically spends more time at a particular package execution.

Setting expdp tracing with TRACE=480300 the following trend in the worker process trace files can be observed:

KUPW: 00:13:26.681: 1: DBMS_LOB.TRIM called
KUPW: 00:13:26.681: 1: DBMS_LOB.TRIM returned 
KUPW: 00:13:26.681: 1: DBMS_METADATA.FETCH_XML_CLOB Handle is: 200001 called
*** 2007-09-21 00:35:15.145 
KUPW: 00:35:15.135: 1: DBMS_METADATA.FETCH_XML_CLOB returned 
KUPW: 00:35:15.145: 1: Object seqno just fetched is: 281 
KUPW: 00:35:15.145: 1: Object path just fetched is:
DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms