Hi, I have shipped an archived redo log from my Primary to my physical standby.
I can see the log arriving at my Standby and being applied
select thread#, max(sequence#) "Last Standby Seq Received"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
group by thread# order by 1;
returns
THREAD# Last Standby Seq Received
---------- -------------------------
1 151
select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
THREAD# Last Standby Seq Applied
---------- ------------------------
1 150
select stamp,name,applied
from v$archived_log
where applied != 'YES'
STAMP
----------
NAME
--------------------------------------------------------------------------------
APPLIED
---------
827498375
/home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_09_30/o1_mf_1_151_9
4lrqpj3_.arc
IN-MEMORY
This log continually sits like this
I know that Redo Appply is active
select * from v$managed_standby where process = 'MRP0';
PROCESS PID STATUS CLIENT_P
--------- ---------- ------------ --------
CLIENT_PID
----------------------------------------
CLIENT_DBID
----------------------------------------
GROUP# RESETLOG_ID THREAD# SEQUENCE#
---------------------------------------- ----------- ---------- ----------
BLOCK# BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
---------- ---------- ---------- ------------ -------------
MRP0 3068 APPLYING_LOG N/A
N/A
N/A
N/A 820252586 1 152
5038 102400 0 3 3
It looks as if 151 has been applied - yet
select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
still shows 150 !
151 is not that big, I still would have expected it to have applied by now ( in excess of 30 mins )
Also I know there is no defer or time delay on the archive_destination setting on the Primary.
Any ideas why this standby redo log just sits IN-MEMORY ?
thanks,
Jim