v$archived_log: applied column is not marked if recovery applied the redo from SRL
(Doc ID 1481927.1)
Last updated on APRIL 03, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]Oracle Database Cloud Schema 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The "APPLIED" column of v$archived_log from the standby DB is not marked as "YES" if the recovery applied the log through the standby redo log.
Changes
Symptoms can be seen:
From Grid Control, it shows:
Primary DB -
The current log: 183
Standby DB -
Last Received Log: 182
Last Applied Log: 181
This is the confusion: There is no transport lag or apply lag, so the expected last applied log should be 182 instead of 181.
From the alert log, it actually showing the current applying log is 183:
Standby controlfile consistent with primary
RFS[41]: Selected log 16 for thread 1 sequence 181 dbid -895089905 branch 783031367
Mon Jul 28 22:00:37 2012
Archived Log entry 1840 added for thread 1 sequence 180 ID 0xcc18c492 dest 1:
Mon Jul 28 22:00:37 2012
Media Recovery Waiting for thread 1 sequence 181 (in transit)
Recovery of Online Redo Log: Thread 1 Group 16 Seq 181 Reading mem 0
Mem# 0: \<path>\ONLINELOG\O1_MF_16_7CJZCXJ4_.LOG
Mem# 1: \<path>\\ONLINELOG\O1_MF_16_7CJZCXQG_.LOG
Tue Jul 29 00:18:52 2012
Standby controlfile consistent with primary
RFS[41]: Selected log 15 for thread 1 sequence 182 dbid -895089905 branch 783031367
Tue Jul 29 00:18:53 2012
Archived Log entry 1841 added for thread 1 sequence 181 ID 0xcc18c492 dest 1:
Tue Jul 29 00:18:53 2012
Media Recovery Waiting for thread 1 sequence 182 (in transit)
Recovery of Online Redo Log: Thread 1 Group 15 Seq 182 Reading mem 0
Mem# 0: \<path>\ONLINELOG\O1_MF_15_7CJZCW8D_.LOG
Mem# 1: \<path>\ONLINELOG\O1_MF_15_7CJZCWJ6_.LOG
Tue Jul 29 02:19:18 2012
Standby controlfile consistent with primary
RFS[41]: Selected log 16 for thread 1 sequence 183 dbid -895089905 branch 783031367
Tue Jul 29 02:19:19 2012
Archived Log entry 1842 added for thread 1 sequence 182 ID 0xcc18c492 dest 1:
Tue Jul 29 02:19:19 2012
Media Recovery Waiting for thread 1 sequence 183 (in transit)
Recovery of Online Redo Log: Thread 1 Group 16 Seq 183 Reading mem 0
Mem# 0: \<path>\ONLINELOG\O1_MF_16_7CJZCXJ4_.LOG
Mem# 1: \<path>\ONLINELOG\O1_MF_16_7CJZCXQG_.LOG
Following queries from standby DB showed that MRP is working on sequence# 183.
No entry from v$archived_log for sequence#183 is expected, but the "Applied" column for the sequence#182 still marked as "NO".
THREAD# SEQUENCE# REGISTR APPLIED DEL S
---------- ---------- ------- --------- --- -
1 176 RFS YES NO A
1 177 RFS YES NO A
1 178 RFS YES NO A
1 179 RFS YES NO A
1 180 RFS YES NO A
1 181 RFS YES NO A
1 182 RFS NO NO A
SQL> select process, pid, status, thread#, sequence#, block# from v$managed_standby where process='MRP0';
PROCESS PID STATUS THREAD# SEQUENCE# BLOCK#
--------- ---------- ------------ ---------- ---------- ----------
MRP0 8200 APPLYING_LOG 1 183 13696
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 |
| Changes |
| Cause |
| Solution |
| References |