V$DATAGUARD_STATS Shows No APPLY LAG But OEM DG lag Alert Reports Incorrect APPLY LAG After Applying EM AGENT RU9 Patch
(Doc ID 2776957.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterEnterprise Manager for Oracle Database - Version 13.4.0.0.0 and later
Information in this document applies to any platform.
Symptoms
- Data Guard Broker does not report an apply lag but OEM DG lag alert shows incorrect lag. Issue reported after apply EM Agent RU9 patch.
- V$DATAGUARD_STATS Shows no Apply lag
- 13.4GC with OMS & Agents patched to RU9
- SIRA is been used and Apply is Running only in One Instance (In this example in Instance 1 )
- This is EM Agent issue since it's wrongly querying GV$DATAGUARD_STATUS instead of checking V$DATAGUARD_STATS. For example, we can see below, apply running on instance# 1 but since agent is querying GV$DATAGUARD_STATS it's reporting gap (due to previously apply running on instance 3)
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |