Standby MRP is looking for very old archive log sequence even after restore new incremental backup at standby site. (Doc ID 1542907.1)

Last updated on JANUARY 27, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Dec-2015***

Symptoms

Ct applied incremental backup, but still standby MRP is looking for very old sequence.

SQL>SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
  FROM (SELECT THREAD# ,SEQUENCE#
  FROM V$ARCHIVED_LOG
  WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME)
  FROM V$ARCHIVED_LOG
  GROUP BY THREAD#)) ARCH,
  (SELECT THREAD# ,SEQUENCE#
  FROM V$LOG_HISTORY
  WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME)
  FROM V$LOG_HISTORY
  GROUP BY THREAD#)) APPL
  WHERE ARCH.THREAD# = APPL.THREAD#
  ORDER BY 1;


  Thread Last Sequence Received Last Sequence Applied Difference
---------- ---------------------- --------------------- ----------
  1 23861 23057 804
  2 8553 8259 294
  3 8542 8248 294

SQL>select process,status,sequence# from v$managed_standby where PROCESS ='MRP0';

PROCESS STATUS SEQUENCE#
--------- ------------ ----------
MRP0 WAIT_FOR_GAP 17353

Changes

 Standby db has just been restored from incremental backup taken from primary.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms