Considerations for Instantiating or Duplicating a Database on Exadata
(Doc ID 1206603.1)
Last updated on OCTOBER 29, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168.0 to 22.214.171.124 [Release 11.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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
As databases become larger and larger the time needed to create either a duplicate database or a standby database on a second cluster becomes considerably longer. There are two main areas to consider when optimizing the duplication process:
1.The network between the source and target systems
a. Using a dedicated Ethernet interface separate from the public interface
b. Using the InfiniBand network between two system
2. Using multiple instances and multiple RMAN commands to parallelize the work
Move network traffic to a separate network interface
This approach to eliminate contention between the different types of network traffic is to move the duplication traffic to a separate network. For example, client connections continue to use the eth1 Ethernet interface, but the duplication process instead uses the eth3 Ethernet interface to access a dedicated network between the two systems.
This approach may also be used to move network traffic to the InfiniBand network on Oracle Database Machine for duplicate databases that are within InfiniBand cable length specifications to the primary database.
- Up to 5m passive copper 4X QDR OSFP cables
- Up to 50m Fiber Optic 4x QDR OSFP cables
Consult MOS note 960510.1 for additional information and consideration on separating network traffic for the duplicate process.
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