Why Is Metadata DataPump Export Faster When Started Over A Network Link Than Locally?
(Doc ID 1357839.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.2 [Release 10.2 to 11.2]Oracle Database Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
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.
Symptoms
You started DataPump export (expdp) locally (on database server) to export the metadata of a certain schema containing partitioned/subpartitioned tables.
Later you started the same export but from a remote target machine/database (with same version) using a network link connected to the source server/database. This considerably needed fewer time to complete than the local export.
Let's follow the next test that demonstrates this:
=> only 52 seconds were needed to extract the tables from remote schema and create them into target schema.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |