Hi all
RAC primary with single-instance physical standby on version 11.2.0.2 using max performance with real time apply.
I discovered some warnings doing my RMAN backups of my archived redo logs on the primary database (done every second hour):
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
I've seen this before, but I noticed that the warning was for the same archived redo log file each time the backup ran, until a new log switch occured on the primary system.
So I looked into v$archived_log at both sides:
select thread#,sequence#,dest_id,to_char(first_time,'dd.mm hh24:mi') "first",to_char(next_time,'dd.mm hh24:mi') "next",to_char(completion_time,'dd.mm hh24:mi'), standby_dest,applied from v$archived_log where thread# = 1 and sequence# = 693 and dest_id = 2;
THREAD# SEQUENCE# DEST_ID first next TO_CHAR(COM STA APPLIED
---------- ---------- ---------- ----------- ----------- ----------- --- ---------
1 693 2 23.08 00:11 23.08 05:00 23.08 05:00 YES NO
Primary sees the sequence 693 as not applied. Why havent my Dataguard gap alarm sounded?
So I check v$archived_log at standby side:
THREAD# SEQUENCE# first next TO_CHAR(COM REGISTR APPLIED DEL
---------- ---------- ----------- ----------- ----------- ------- --------- ---
1 693 23.08 00:11 23.08 05:00 23.08 05:00 RFS IN-MEMORY NO
And refering to the reference manual they state that
If REGISTRAR = RFS and APPLIED = IN-MEMORY, then the log file has been applied in memory, but the datafiles have not yet been updated.
This column can be used to identify log files that can be backed up and deleted. When used for this purpose, the value IN-MEMORY should be treated as if it were NO.
Is this new behavior for 11g ? Is it a bug? Will the last log always have status "IN-MEMORY" ? I have the same thing for all my 11g standby databases and the status doesnt update to "APPLIED = YES" until a new log switch on primary.
Anyone seen this?
Any comment appricated :)