DataPump Import Via NETWORK_LINK Is Slow With CURSOR_SHARING=FORCE
(Doc ID 421441.1)
Last updated on MARCH 11, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.6 to 10.2.0.3 [Release 9.2 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata 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
Information in this document applies to any platform.
Symptoms
DataPump import with NETWORK_LINK is being considered to migrate to a new database. But DataPump import is going slow while running a query for the estimation phase which tries to determine whether the table to be imported is empty or not.
Below query performs a full table scan which doubles the cost of DataPump import.
Changes
CURSOR_SHARING on the source site has been set to FORCE or SIMILAR.
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 |
| Changes |
| Cause |
| Solution |
| References |