How To Use Parallel Capabilities To Improve Cross-Platform Migration Using Data Pump
(Doc ID 2071900.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle 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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Goal
Here customer wants to perform a cross-platform (HP-UX to Linux) / standalone to RAC migration for their 2 TB Database.
To avoid performance impact, they are initiating EXPDP with PARALLEL=2 and FILESIZE=100G, so it will create about 20 dump files of 100G each.
They want some clarification regarding parameters - PARALLEL, PARALLEL_FORCE_LOCAL and how they can effectively use these parameters during the migration task.
Q1. As we performed expdp with PARALLEL=2, can we use impdp with PARALLEL=8 (because the target system has more CPUs)?
Q2: Our Source is a standalone database but the Target will be a 2 Node RAC Instance.
So we use "PARALLEL_FORCE_LOCAL=FALSE" to run the impdp import on both the instances.
Does that give performance improvement OR will cache fusion activity be increased and is the setting not recommended ?
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 |