Working with Oracle Data Guard - Oracle Database on AWS

Working with Oracle Data Guard

After completing the deployment, you can change Oracle Data Guard configurations and also perform a switchover.

Viewing Your Configuration

You can use the Oracle command-line interface (DGMGRL) to administer your Data Guard solution. To view your configuration, log into DGMGRL and use the SHOW CONFIGURATION command. See if the protection mode is MaxPerformance, which means that it has asynchronous replication in place. In this example, the primary instance is orcl and the standby instance is orclsb.

For a more detailed view, you can show the database replication configurations. In the following example, notice that LogXptMode='async'.

# dgmgrl sys/pass@instance show database verbose 'databasename';

Changing Your Configuration

If you would like to change the protection mode from maximum performance (MaxPerformance) to maximum availability (MaxAvailability) for synchronous replication, you can change it with DGMGRL, and then monitor your performance. This will set up synchronous replication from the primary database (orcl) to the standby database (orclsb) with the lowest recovery point objective (RPO) in the event of primary database failure.

edit database databasename set property 'LogXptMode'='sync'; edit database standbydatabase set property 'LogXptMode'='sync'; EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;

For more information about performance modes, see the section HA Scenarios with Oracle Data Guard on AWS previously in this guide.

Switching to the Standby Database

You can use the DGMGRL SWITCHOVER command to switch from the primary database (orcl) to the secondary database (orclsb).

If you have not logged in with the SYS password, you may receive the following error.

After the primary orcl instance is shut down and started back up, you may see the configuration switchover.

If you are logged in with the SYS password, you may fail over without the need for manual shutdown and startup.

You can also enable fast-start failover by following the instructions in the Oracle documentation.

Switching Your DNS Configuration

When you switch over to the standby database, you should also update your record set in the Route 53 private hosted zone to point to the standby database:

  1. Sign in to the AWS Management Console and open the Route 53 console at

  2. Find your IP record inside your private hosted zone and change it to your standby (new primary) IP, so your application can continuously reach your primary database on the private hosted zone, and then save the record.

        Switching your DNS

Figure 11: Switching your DNS