ORA-16854 IN BROKER AND GV$RECOVERY_PROGRESS ON STANDBY SHOWING NO ROWS PERIODICALLY WHEN IT'S IN SYNC
(Doc ID 2371648.1)
Last updated on JULY 05, 2021
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
-
Issue reported on 12.2.0.1 version, Oracle Data Guard.
-
DGMGRL reports ORA-16854 for the standby standby_b and v$recovery_progress view it shows "No rows".
-
Other standby's standby_c returns it's SCN ,MRP is applying the same redo and v$standby_log shows ACTIVE for same redo.
-
If they switch a logfile it will get applied to the standby_b as well.
DGMGRL> show configuration verbose
Configuration - <CONFIGURATION_NAME>
Protection Mode: MaxAvailability
Members:
<PRIMARY_NAME>- Primary database
<STANDBY-C>- Physical standby database
<STANDBY-B> - Physical standby database
Warning: ORA-16854: apply lag could not be determined
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 |