Why DataPump Does Not Use Parallelism When Importing An IOT?
(Doc ID 2234596.1)
Last updated on MARCH 27, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.6 and laterOracle 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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Goal
NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
An Import DataPump job of an unpartitioned Index-Organized Table does not use parallelism when importing the table data. As a result, a slow performance is observed when importing IOT table data. The IOT does not have a physical rowed mapping table nor a materialized view on it:
Solution
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
| Goal |
| Solution |
| References |