A data guard configuration consists of several standby and far sync instances.
Similarly on the far sync alert log also there are entries corresponding to each log archive destination.
However, after applying DBRU 19.12 only one LAD is shown and that corresponds to local archive log destination. On primary
When ever there is a log switch the alert log would have entries corresponding to all remote log archive destinations (denoted LAD). For example in the above configuration primary write sto db1,db3 and fs1. On the primary alert log entries like below would be visible.
DGMGRL> show configuration
Configuration - db_dg
Protection Mode: MaxAvailability
Members:
db2 - Primary database
db1 - Physical standby database
db3 - Physical standby database
db4 - Physical standby database (receiving current redo)
fs1 - Far sync instance
db5 - Physical standby database
db6 - Physical standby database
db7 - Physical standby database
db8 - Physical standby database
db9 - Physical standby database
db10 - Physical standby database
db11 - Physical standby database
db12 - Physical standby database
db13 - Physical standby database
db14 - Physical standby database
Members Not Receiving Redo:
fs2 - Far sync instance (alternate of fs1)
Fast-Start Failover: Disabled
Configuration Status:
SUCCESS (status updated 57 seconds ago)
LGWR (PID:107336): SRL selected to archive T-1.S-3023The LAD:n where n corresponds to log archive detination parameter number (log_archive_dest_n).
LGWR (PID:107336): SRL selected for T-1.S-3023 for LAD:6
LGWR (PID:107336): SRL selected to archive T-1.S-3023
LGWR (PID:107336): SRL selected for T-1.S-3023 for LAD:4
LGWR (PID:107336): SRL selected to archive T-1.S-3023
LGWR (PID:107336): SRL selected for T-1.S-3023 for LAD:3
Similarly on the far sync alert log also there are entries corresponding to each log archive destination.
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:12
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:11
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:10
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:9
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:8
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:7
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:6
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:5
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:4
TT02 (PID:5781): SRL selected for T-1.S-36125 for LAD:3
However, after applying DBRU 19.12 only one LAD is shown and that corresponds to local archive log destination. On primary
NET (PID:27469): Archived Log entry 236855 added for T-1.S-77841 ID 0xfd561a70 LAD:1One far sync
ARC3 (PID:3874): Archived Log entry 712212 added for T-1.S-77842 ID 0xfd561a70 LAD:1LAD:1 corresponds to log_archive_dest_1 and has location=use_db_recovery_file_dest. No more remote LAD related entries are visible in the alert log.