The lag time between updates to the primary database and application of the redo data on the standby database, as computed by the reporting database.
Example: {@code 9 seconds}
The rate at which redo logs are synced between the associated databases.
Example: {@code 180 Mb per second}
The OCID of the Autonomous Database that has a relationship with the peer Autonomous Database.
The OCID of the Autonomous Dataguard created for Autonomous Container Database where given Autonomous Database resides in.
Indicates whether Automatic Failover is enabled for Autonomous Container Database Dataguard Association
Additional information about the current lifecycleState, if available.
The current state of Autonomous Data Guard.
The OCID of the peer Autonomous Database.
The current state of the Autonomous Database.
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
The protection mode of this Autonomous Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
The Data Guard role of the Autonomous Container Database or Autonomous Database, if Autonomous Data Guard is enabled.
The date and time the Data Guard association was created.
The date and time when the last role change action happened.
The date and time of the last update to the apply lag, apply rate, and transport lag values.
The approximate number of seconds of redo data not yet available on the standby Autonomous Container Database, as computed by the reporting database.
Example: {@code 7 seconds}
The properties that define dataguard association between two different Autonomous Databases. Note that Autonomous Databases inherit DataGuard association from parent Autonomous Container Database. No actions can be taken on AutonomousDatabaseDataguardAssociation, usage is strictly informational.