Oracle Cloud Infrastructure Documentation

Manage Remote Peer Network ACLs

You can independently modify network ACLs on a remote disaster recovery peer database.

By default the disaster recovery primary and remote peer databases use the same network Access Control Lists (ACLs). Optionally, you can configure ACLs independently on remote peer databases. This provides an option to use different ACLs on remote peer databases.

If you modify the ACLs on a remote peer, Autonomous Database no longer keeps the ACL configuration synchronized between the primary and the remote peer. After you modify the ACLs on a remote peer, Autonomous Database manages the ACLs on the remote peer independently.

To use different network ACLs on a remote Autonomous Database peer:

  1. On the primary database, on the Autonomous Database Details page, under Resources select Disaster recovery.
  2. Access the remote peer.

    The Disaster recovery information area shows the Peer Autonomous Database. The remote peer database by default has the same display name as the primary database, with an "_region" extension. Where region is the region name, such as IAD or BOM.

    Under Peer Autonomous Database, click the link to access a cross-region peer.

  3. On the remote peer database, edit the access control list.

    Before you change ACL values the dialog shows a message indicating that ACLs on the peer database are syncing from the Primary database. For example:

    Description of adb_remote_peer_sync_acls.png follows

    See Configure Access Control Lists for an Existing Autonomous Database Instance for more information.

  4. Add, remove, or modify one or more ACLs.
  5. Click Save.

After you modify ACLs, the ACLs on the primary and on the remote peer are managed separately.

If you want to restart the synchronization of ACLs between the primary and the remote peer, you have two options: