My Oracle Support Banner

DataPump Performance Slow On Multithread CPU (Doc ID 1385135.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Solaris on SPARC (64-bit)

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.


When running a DataPump export job with only one worker (DW, for example, when metadata is extracted), the performance is slow on multithread CPU.

Hardware configuration: Sun SPARC Systems Sun-Fire-T200 CPU

DataPump export log:

Export: Release - Production on Wed Nov 23 10:50:36 2011

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_04":  system/******** directory=DATAPUMP dumpfile=test.dmp logfile=test.log schemas=TEST parallel=32 cluster=n METRICS=Y CONTENT=METADATA_ONLY
Processing object type SCHEMA_EXPORT/USER
     Completed 1 USER objects in 3 seconds
Processing object type SCHEMA_EXPORT/JOB
     Completed 5 JOB objects in 17 seconds
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_04" successfully loaded/unloaded
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_04 is:
Job "SYSTEM"."SYS_EXPORT_SCHEMA_04" successfully completed at 13:05:30

This shows that the DataPump export of metadata took 2 hours and 15 minutes.

The AWR report shows high CPU (only DataPump runs in the database):

Top 5 Timed Foreground Events
Event                    Waits Time(s) Avg wait (ms) % DB time Wait Class
DB CPU                              48                   90.99
db file sequential read  1,268       5            4      10.24   User I/O
db file scattered read     182       1            4       1.47   User I/O

Run the following query to identify database worker (DW):

This shows that the same metadata export took 35 minutes.




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.