Learn About Migrating a Multi-Node Database Cloud Service Deployment to Virtual Machine Database System
If you want to migrate a two-node Oracle Real Application Cluster (Oracle RAC) database created using Oracle Database Cloud Service to an Oracle Cloud Infrastructure Virtual Machine Database System, then you can perform the database migration by using Oracle Data Guard.
For more information about the source and target databases, see the following table:
Information | Source Database | Target Database |
---|---|---|
Platform | Oracle Cloud Infrastructure Compute Classic | Oracle Cloud Infrastructure Compute |
Database Type | Oracle Real Application Cluster (RAC) Database on Database Cloud Service Classic | Oracle RAC Database on Virtual Machine Database System |
Creation Mechanism | Database Cloud Service UI, CLI, API | Oracle Cloud Infrastructure UI, CLI, API |
Size | 2 Node | 2 Node |
Architecture
You can migrate Oracle Database releases 12.1.0.2 and 12.2.0.1. Before you migrate your database, you must have Oracle RAC database on Oracle Database Cloud Service and a two-node Oracle RAC Database running on Oracle Cloud Infrastructure.
When you use Oracle Data Guard to perform the migration, the source database is the primary database, and the target database is the standby database.
The following diagram shows the migration process:
To perform the migration, you must follow these general steps:
- Plan the migration.
When you plan the database migration, you begin by inventorying the source environment (the primary database) and then you decide on the best migration strategy. To inventory the source environment, you must perform tasks such as determining the sizes of database files and checking which disaster recovery plans are in place. To decide on the best strategy, you should plan, for example, the best time of day to perform the migration.
- Prepare for the migration.
To prepare to migrate the source database (the primary database) to the target environment (the standby database), you must perform tasks such as ensuring that the database that you want to migrate is running, installing the latest patches for both databases so that they are patched at the same level, and ensuring that the 1521 port is open between the primary database and the standby database. In this solution, the net service name for the source (primary) database is
OCIC-ORCL
and the net service name for the target (standby) database isOCI-ORCL
.Note:
Oracle recommends using the same database name for both databases so that applications can automatically fail over to the new database. - Perform the migration.
You can perform the database migration by configuring the primary database (the source database) and the standby database (the target database) for Oracle Data Guard, copying the TDE wallets from the primary database to the standby database, and then completing the standby database configuration.
Required Tools to Perform the Migration
Before you begin the database migration, in addition to knowledge of Oracle Cloud Infrastructure, you must have knowledge in several areas of Oracle Database tools.
The tools with which you must be familiar are as follows:
- SQL*Plus
- Oracle Data Guard
- Familiarity with using the
srvctl
anddgmgrl
utilities - Familiarity with editing the
tnsnames.ora
,listener.ora
,sqlnet.ora
, andoraenv
files - Familiarity with performing Oracle Data Guard switchover operations
- (Optionally) Familiarity with generating Oracle Automatic Workload Repository and Oracle Automatic Database Diagnostic Monitor reports
- (Optionally) Familiarity with Oracle Automatic Storage Management Cluster File System
About Required Services and Roles
This solution requires Oracle Cloud Infrastructure.
Role | Required to... |
---|---|
Administrator (SYSDBA and
SYSOPER privileges)
|
Perform SYS -related administration
tasks.
|
Administrator (SYSDBG
privilege)
|
Perform Oracle Data Guard tasks, if you are using Oracle Database 12c release 2 (12.1.0.2) or later. |
Administrator (SYSKM privilege)
|
Perform Transparent Data Encryption tasks, if you are using Oracle Database 12c release 2 (12.1.0.2) or later. |