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 reporting database.
The OCID of the Data Guard association.
True if active Data Guard is enabled.
Additional information about the current lifecycleState, if available.
The current state of the Data Guard association.
The OCID of the peer database's Data Guard association.
The OCID of the associated peer database.
The OCID of the Database Home containing the associated peer database.
The OCID of the DB system containing the associated peer database.
The role of the peer database in this Data Guard association.
The protection mode of this Data Guard association. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
The role of the reporting database in this Data Guard association.
The date and time the Data Guard association was created.
The redo transport type used by this Data Guard association. For more information, see Redo Transport Services in the Oracle Data Guard documentation.
The properties that define a Data Guard association.
To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized, talk to an administrator. If you're an administrator who needs to write policies to give users access, see [Getting Started with Policies](https://docs.cloud.oracle.com/Content/Identity/Concepts/policygetstarted.htm).
For information about endpoints and signing API requests, see [About the API](https://docs.cloud.oracle.com/Content/API/Concepts/usingapi.htm). For information about available SDKs and tools, see [SDKS and Other Tools](https://docs.cloud.oracle.com/Content/API/Concepts/sdks.htm).