You can configure replication to a non-standby database. Replication uses the default subclient for the database that you want to replicate, so the default subclient must include the entire database, the log files, and the control file.
If no new backups have run since the last replication operation, then the scheduled replication operation does not run.
Note
For the best results, put the source database and the destination database in ARCHIVELOG mode.
Before You Begin
-
Set up an Oracle instance for the replication destination database.
For more information, see Setting Up an Oracle Instance for Replication.
-
Verify that the default subclient includes the entire database, the log files, and the control file.
-
If you plan to use a storage policy copy, or secondary media, verify that copy precedence exists for both the data and the log files, and that a scheduled auxiliary copy job exists.
-
Data backup for the replication destination database should already have been disabled when the destination instance was configured.
For more information, see Setting Up an Instance for Replication.
Procedure
-
From the navigation pane, go to Auto recovery > Replication groups.
The Replication groups page appears.
Note
You can also access the Replication groups page from the instance level.
-
In the upper-right area of the page, click Add.
The Select Workload Type page appears.
-
Select Oracle, and then click NEXT.
The Configure Replication Group - Oracle page for the Source appears.
-
In the Name box, type a name for the replication schedule that you are creating.
-
From the Servers list, select the server where the source Oracle instance is running.
-
From the Instances list, select the source Oracle instance.
-
Click NEXT.
The Target page appears.
-
From the Servers list, select the server where the destination Oracle instance is running.
-
From the Instances list, select the instance on which you want to replicate the data from the source computer.
-
Click NEXT.
The Override options page appears.
Note
-
The operating system of the source server and the destination server must be the same.
-
The software does not list Automatic Storage Management (ASM) instances.
-
-
If the destination database directory structure is different from the source database, under Redirect options select one of the following options to set the redirect path:
-
To redirect the database, click Database, and then enter the full path for the new location of the database.
-
To redirect individual tablespaces and datafiles, click Tablespaces and datafiles. For each tablespace that you want to redirect:
-
Expand the tablespace.
-
In the Datafiles box, change the path to the new location.
-
-
-
To configure the live sync option, under Advanced options select the live sync option you want to use for replication.
If you select the Use most recent full backup option, the software runs an incremental backup operation using the most recent full backup.
-
To change the number of streams to use, in the Number of streams box, enter the number of streams to use.
-
From the Copy Name list, select the copy to use for replication.
Note
If you select a Server plan snap copy the software replicates changes only when the source database backup is available on the server plan snap copy or the secondary media. The backup is available on the media after the auxiliary job completes, so that is when the software attempts the replication.
-
Click NEXT to create the replication group.
Results
-
After the job completes, the software opens the replication destination database in read-only mode.
If you want to perform a backup operation on the destination database after the replication operation completes, then you must open the database in read-write mode because Oracle does not allow a control file backup when the database is in read-only mode.
-
The Replication Monitor appears at the bottom of the instance page that you configured replication for.
What to Do Next
-
To view existing replication groups, go to Monitoring > Replication monitor.
-
You can view the global Replication Monitor table, which contains information about the status of replication groups and replication jobs.