Configure for Database Migration
With the Oracle Cloud Infrastructure in place, you can instantiate the database and application.
About Configuring the Databases
You'll need to set up the future primary database and the future secondary database.
The scenario presented here requires three databases:
- The original on-premises database (
CDBHCM_sca6dp) - The physical standby to be created in the following sections, destined
to be the primary (
CDBHCM_iad1dx, in the Ashburn region - A second physical standby, destined to be our cloud-based disaster recovery database
(
CDBHCM_phx5s, in the Phoenix region)
This scenario uses two standby databases in Oracle Cloud Infrastructure (OCI) so that we're fully protected when we switch production operations to Oracle Cloud.
Oracle Data Guard keeps the databases current with changes made in the on-premises production database until we're ready to switch operations fully to OCI. At that point, Oracle Data Guard keeps the on-premises database and the OCI-based secondary database in sync with the new OCI-based primary. When ready, the on-premises database can be dropped from the configuration.
Constraints for this setup:
- All database homes must be on the same release update and patch level
- All databases must be registered into Oracle Clusterware
- All databases must be able to connect directly to each of the other databases involved in the Oracle Data Guard configuration, including the on-premises database
The software used in this example is listed in the table. Both primary and standby sites use the same versions.
| Software Component | Version |
|---|---|
| Oracle Exadata Database Service on Dedicated Infrastructure domU OS version | 22.1.10.0.0.230422 |
| Oracle Grid Infrastructure | 19.19.0.0.0 |
| Oracle Database | 19.19.0.0.0 |