Monitoring a Data Guard Configuration
(Doc ID 2064281.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 18.1.0.0.0 [Release 11.2 to 18]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
When monitoring Data Guard configurations a DBA must be able to be alerted to conditions that may potentially risk violating the business recovery point objects and/or the recover time objective requirements. Monitoring a Data Guard environment involves monitoring both the primary and all associated standby databases. This note outlines basic methods to monitoring a Data Guard configuration.
This Document discusses
Detecting a Transport or Apply Lag using SQL.
Detecting a Transport or Apply Lag using Dataguard broker.
Monitoring Data Guard Configuration Health Using the Broker.
Monitoring Data Guard Configuration Health Using the SQL.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Detecting a Transport or Apply Lag using SQL: |
| Detecting a Transport or Apply Lag using Data Guard Broker: |
| Monitoring Data Guard Configuration Health |
| Monitoring Data Guard Configuration Health Using the Broker: |
| Monitoring Data Guard Configuration Health Using SQL: |
| Primary Database Queries |
| Physical Standby Database Queries |