Prerequisites for creating a remote recovery resiliency group for Oracle database replicated by Data Guard
Before you create a remote recovery resiliency group for Oracle database replicated by data guards, ensure that the following prerequisites are fulfilled.
Data Guard Broker needs to be configured so that Resiliency Platform can manage the replication.
Flashback database needs to be configured in databases in both data centers. This is required for fast resync after recover operation.
It is recommended to configure one Oracle Data Guard application per resiliency group.
After creating the application, you will be able to perform DR operations such as migrate, recover, resync, and rehearsal on it. Resiliency Platform uses sqlplus and dgmgrl commands in the operations. Following table shows the commands issued by Resiliency Platform using each operation:
Table:
Operation | Commands |
|---|---|
Migrate | Uses dgmgrl commands: validate database, switchover to |
Recover | Uses dgmgrl commands: validate database, failover to |
Resync | Uses dgmgrl commands: validate database, reinstate database |
Rehearsal | Uses sqlplus commands: alter database recover managed standby database cancel alter database convert to snapshot standby |
Cleanup | Uses sqlplus commands: alter database convert to snapshot standby alter database recover managed standby database using current logfile disconnect |
The stop resiliency group operation will stop the database, but not the listeners if the Oracle database instances are managed from Oracle discovery host. But since the database is shut down, the Data Guard replication will be stopped and thus, migrate operation will not be allowed until you start the resiliency group again.
• Far Sync configurations are supported in Data Guard. Resiliency Platform will identify the Far Sync sites but will not make any changes to the Far Sync configuration.