X

An Oracle blog about Database and Grid Infrasructure Maintenance

  • February 11, 2015

Cross-Site Load Balancing - Prerequisites and Steps to Be Performed

Summary of the Prerequisites and Steps to Be Performed


Let’s consider the following
configuration:

Site A: Primary is replicated by
Active Data Guard to Site B: Secondary

Site B: Primary is replicated by
Active Data Guard to Site A: Secondary

Let's assume that we have a pdb (MY_PDB) which runs on Site A: Primary. If, for example the workload is too high on Site A: Primary and a specific SLA can not be fulfilled, we can perform the following steps in order to move MY_PDB to Site B: Primary where the SLA can be met:

1. Stop MY_PDB
on Site A: Primary and Site B: Secondary(Log files will continue to apply in
MOUNT DB Mode)

2. Unplug
MY_PDB from Site A: Primary

3. Copy XML
manifest to the other site – Site B: Primary

4. Setup
aliases on Site B: Primary and Site A: Secondary

5. Ensure
media recovery (MRP) is running on the Site A: Secondary

6. Plugin
MY_PDB on Site B: Primary

7. Check
MY_PDB was replicated on Site A: Secondary

8. Open MY_PDB
on Site B: Primary

9. Open MY_PDB
(Read Only) on Site A: Secondary (if Active DG is running)

10. Drop MY_PDB on Site A: Primary (keep Datafiles)

These steps show that load balancing across sites is possible using a combination of Oracle Multitenant and Oracle Data Guard. When coupled with the flexibility offered by Oracle Real Application Clusters for local site management, it is an excellent example of the level agility and flexibility that enable a full-featured Database as a Service deployment.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.